Executor Component (MME) Messages › MME0201-0210

MME0201-0210

MME0201S

Spawn of a program failed. Command: command Error code: ee error_description Errno2 code: ee2 Path: system_path

Reason:

The creation of a new process has failed. The most likely cause is incorrect installation of CA CSM. The CAGIMAPI program to execute GIMAPI queries is not found in the path or has insufficient privileges. Another likely cause is that CA CSM cannot spawn a new process (address space). ee is the error code, ee2 is the second error code in hexadecimal format.

Action:

Review the error codes in the z/OS UNIX System Services Messages and Codes. Contact your systems programmer or security administrator.

MME0202S

Data set allocation failed. DSN: data_set_name RC: xx Error code: eeeeeeee Info code: iiiiiiii.

Reason:

Dynamic allocation of the data set failed. xx is the return code. eeeeeeee is the error code. iiiiiiii is the information code. This problem can occur when CA CSM allocates new data sets during installing products, creating HFS data sets, and saving output of tasks.

Action:

Review the return code. The following return codes indicate typical situations:

020C, 0210

The data set is used by another job.

0214

The device is not available.

021C

Unit is invalid.

0220

Volser is invalid.

0448

The data set already exists.

Reassign the data set and rerun the task.

Note: For more information about the return codes, see the chapter Requesting Dynamic Allocation Functions in the IBM z/OS MVS Programming: Authorized Assembler Services Guide.

MME0203S

Load failed. EP: entry_point_name RC: xx.

Reason:

The specified load module was not found in STEPLIB. xx is the return code.

Action:

Check whether STEPLIB is propagated in the CA CSM startup job parameters (export STEPLIB=CURRENT). If this line is missing, contact your systems programmer.

MME0204S

Wait for process failed. Error code: ee error_description

Reason:

Waiting for a process started by CA CSM has failed. The error can be caused by a severe failure in the started process. ee is the error code.

Action:

Contact CA Support.

MME0205S

Invalid eye-catcher. Expected: eye_catcher_description

Reason:

The expected eye-catcher was not found in the started module (CAGIMAPI, CAGIMSMP). The error can be caused by a corrupted module or version mismatch.

Action:

Check configuration of the PATH environment variable in CA CSM startup JCL. If any path is invalid, contact your systems programmer.

MME0206S

Message queue operation failed. Function: message_queue_function Error code: ee error_description

Reason:

A call to the operating system to perform an operation with the message queue has failed. ee is the error code.

Action:

Contact CA Support.

MME0207S

Attach of a load module failed. EP: entry_point_name RC:xx

Reason:

The specified load module was not found in STEPLIB. xx is the return code.

Action:

Check whether STEPLIB is propagated in CA CSM startup JCL parameters (export STEPLIB=CURRENT). If this line is missing, contact your systems programmer.

MME0208S

Initialization of process failed. Module: module.

Reason:

The started process did not respond within 10 seconds.

Action:

Contact CA Support.

MME0209S

An error occurred during login. Userid: user_id Function: function. RC: xxxxxxxx Error code: eeeeeeee error_code_explanation

Reason:

Security setup for the started process has failed. The cause is described by the text following the error code. xxxxxxxx is the return code. eeeeeeee is the error code.

Action:

• Review the error code explanation. If the problem is caused by an invalid password, log out of CA CSM and log in to again with the valid password.
• Contact CA Support.

MME0210S

Invalid path system_path to be dynamically allocated. DD: DD_name.

Reason:

Dynamic allocation has failed because the specified path is invalid.

Action:

Contact CA Support.