MSMC0401-0441

Configuration (MSMC) Messages › MSMC0401-0441

MSMC0401-0441

MSMC0401E

EVTINIT for task_name failed. RETCODE: return_code

Reason:

The task shown in the message attempted to create a connection to the communications section of the SCS address space. However, the attempt failed with the return code shown in the message.

The communications section is in the process of starting, or has ended unexpectedly, in which case it can be restarted.

This transient condition resolves itself when the communications section is fully initialized.

Action:

Review the JES message log, SCS message log, and system log for other messages describing the failure. Search problem reporting data bases for a fix for the problem. If unable to resolve the problem, save and report this message to CA Support.

MSMC0402E

EVTRGSTR for task_name failed. RETCODE: return_code

Reason:

The task shown in the message attempted to register to receive event records. However, the attempt failed with the return code shown in the message.

Action:

MSMC0403S

EVTCREAT for task_name failed. RETCODE: return_code

Reason:

The task shown in the message attempted to create an event record. However, the attempt failed with the return code shown in the message.

Action:

MSMC0404S

EVTPARSE for task_name failed. RETCODE: return_code

Reason:

The task shown in the message attempted to parse an event record. However, the attempt failed with the return code shown in the message.

Action:

MSMC0405S

EVTFREE for task_name failed. RETCODE: return_code

Reason:

The task shown in the message attempted to free an event record. However, the attempt failed with the return code shown in the message.

Action:

MSMC0406E

EVTSEND for task_name failed. RETCODE: return_code

Reason:

The task shown in the message attempted to send an event record. However, the attempt failed with the return code shown in the message.

Action:

MSMC0407E

EVTRCWRE for task_name failed. RETCODE: return_code

Reason:

The task shown in the message attempted to receive an event record. However, the attempt failed with the return code shown in the message.

Action:

MSMC0408E

EVTRECVE for task_name failed. RETCODE: return_code

Reason:

The task shown in the message attempted to receive an event record. However, the attempt failed with the return code shown in the message.

Action:

MSMC0409E

EVTREPLY for task_name failed. RETCODE: return_code

Reason:

The task shown in the message attempted to acknowledge receipt of an event record. However, the attempt failed with the return code shown in the message.

Action:

MSMC0410E

EVTDEREG for task_name failed. RETCODE: return_code

Reason:

The task shown in the message attempted to deregister from receiving event records. However, the attempt failed with the return code shown in the message.

Action:

MSMC0411E

EVTCLOSE for task_name failed. RETCODE: return_code

Reason:

The task shown in the message attempted to close a connection to the communications section of the SCS address space. However, the attempt failed with the return code shown in the message.

Action:

MSMC0421E

DBOPEN for task_name failed. RETCODE: return_code, IRETCODE: internal_return_code

Reason:

The task shown in the message attempted to open a connection to the CA CSM database. However, the attempt failed with the return code and internal return code shown in the message.

The following are possible conditions of the CA Datacom/DB Multi-User Facility (MUF) at the time of the error:

MUF was not started.
MUF is in the process of starting.
MUF ended unexpectedly, in which case, it can be restarted.

These transient conditions resolve themselves when the MUF is fully initialized.

Action:

Review the JES message log and system log for other messages describing the failure. See the CA Datacom/DB Message Reference Guide for an explanation of the return codes shown in the message and take the action suggested in the publication.

MSMC0422E

DBCLOSE for task_name failed. RETCODE: return_code, IRETCODE: internal_return_code

Reason:

The task shown in the message attempted to close a connection to the CA CSM database. However, the attempt failed with the return code and internal return code shown in the message.

Action:

Review the JES message log and system log for other messages describing the failure. See the, CA Datacom/DB Message Reference Guide for an explanation of the return codes shown in the message and take the action suggested in the publication.

MSMC0423I

SCS task_name database connection opened

Reason:

The task shown in the message opened a connection to the CA CSM database.

Action:

No action is required. This message is informational.

MSMC0424I

SCS task_name database connection closed

Reason:

The task shown in the message closed the connection to the CA CSM database.

Action:

No action is required. This message is informational.

MSMC0425E

SCS task_name database connection lost

Reason:

The task shown in the message lost the connection to the CA CSM database. The CA Datacom/DB Multi-User Facility (MUF) possibly has ended.

Action:

Verify that the CA Datacom/DB Multi-User Facility (MUF) is running.

MSMC0426I

SCS task_name database connection restored

Reason:

The task shown in the message restored the connection to the CA CSM database.

Action:

No action is required. This message is informational.

MSMC0441E

SCS task_name registry error, SYSNAME: system_name, CCINAME: CAICCI_name

Reason:

The task shown in the message attempted to query the CA CSM registry to identify the defined attributes of the system on which the SCS address space was started. However, the system either is not defined or is defined ambiguously.

The message text also shows the system name and CAICCI name for the system on which the SCS address space was started.

Action:

Update the CA CSM registry to properly define the system on which the SCS address space was started.