Configuration (MSMC) Messages › MSMC0501-0592

MSMC0501-0592

MSMC0501E

SQL_statement for task_name failed. SQLCODE: SQL_code, SQLSTATE: SQL_state, RETCODE: return_code, IRETCODE: internal_return_code

Reason:

The task shown in the message attempted to execute the SQL statement shown in the message. However, the statement failed with the SQL return codes shown in the message.

The message text also shows the CA Datacom/DB return code and internal return code. These codes further describe the error condition.

Action:

Review the JES message log, SCS message log, and system log for other messages describing the failure.

For an explanation of the return codes shown in the message, see the CA Datacom/DB Message Reference Guide. Take the action suggested in the publication.

MSMC0502W

SQL_statement for task_name completed, SQLCODE: SQL_code, SQLSTATE: SQL_state, RETCODE: return_code, IRETCODE:internal_return_code

Reason:

The task shown in the message attempted to execute the SQL statement shown in the message. However, the statement completed with the SQL return codes shown in the message. The SQL return codes describe a warning condition.

The message text also shows the CA Datacom/DB return code and internal return code. These codes further describe the warning condition.

Action:

Review the JES message log, SCS message log, and system log for other messages describing the warning condition.

For an explanation of the return codes shown in the message, see the CA Datacom/DB Message Reference Guide. Take the action suggested in the publication.

MSMC0503E

SQL error message: error_message_name

Reason:

The SQL error message is displayed that corresponds to the error message shown before this message.

Action:

Review the JES message log, SCS message log, and system log for other messages describing the failure.

For an explanation of the return codes shown in the message, see the CA Datacom/DB Message Reference Guide. Take the action suggested in the publication.

MSMC0521E

Unrecognized event, TYPE: event_type, NAME: event_name, SOURCE: source_name

Reason:

An event record was received by the implementation engine component of the CA CSM address space. However, the event type in the record is not recognized. The message text shows the event type, event name, and the event record source.

Action:

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.

MSMC0541I

Service subtask started. CID: container_identifier, VERS: container_version, RID: run_identifier, OID: operation_identifier, AID: action_identifier, UID: user_identifier, FUNCCD: function_code

Reason:

A subtask was started to execute a service request used to configure an instance of a CA Technologies product.

Action:

No action is required. This message is informational.

MSMC0542I

Service subtask ended, CID: container_identifier, VERS: container_version, RID: run_identifier, OID: operation_identifier, AID: action_identifier, UID: user_identifier, FUNCCD: function_code, CMPCODE: completion_code, RETCODE: return_code

Reason:

A subtask started to execute a service request used to configure an instance of a CA Technologies product has ended.

Action:

No action is required. This message is informational.

MSMC0544E

Service subtask ended abnormally, CID: container_identifier, VERS: container_version, RID: run_identifier, OID: operation_identifier, AID: action_identifier, UID: user_identifier, FUNCCD: function_code, CMPCODE: completion_code

Reason:

A subtask started to execute a service request used to configure an instance of a CA Technologies product has ended abnormally.

Action:

Review the JES message log and SCS message log for other messages describing the abnormal termination. 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.

MSMC0551I

Agent subtask started, TYPE: type_name, UID: user_identification

Reason:

A subtask was started to execute a system information agent request.

Action:

No action is required. This message is informational.

MSMC0552I

Agent subtask ended, TYPE: type_name, UID: user_identification, CMPCODE: completion_code

Reason:

A subtask started to execute a system information agent request has ended.

Action:

No action is required. This message is informational.

MSMC0554E

Agent subtask ended abnormally, TYPE: type_name, UID: user_identification, CMPCODE: completion_code

Reason:

A subtask started to execute a system information agent request has ended abnormally.

Action:

Review the JES message log and SCS message log for other messages describing the abnormal termination. 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.

MSMC0561E

XML parse initialization for task_name failed. RETCODE: return_code, RSNCODE: reason_code

Reason:

The task shown in the message attempted to initialize a parse instance using the z/OS XML System Services GXL1INI callable service. However, the attempt failed with the return code and reason code shown in the message.

Action:

For an explanation of the return codes shown in the message, see the IBM z/OS XML System Services User's Guide and Reference. Take the action suggested in the publication.

MSMC0562E

XML parse termination for task_name failed. RETCODE: return_code, RSNCODE: reason_code

Reason:

The task shown in the message attempted to terminate a parse instance using the z/OS XML System Services GXL1TRM callable service. However, the attempt failed with the return code and reason code shown in the message.

Action:

For an explanation of the return codes shown in the message, see the IBM z/OS XML System Services User's Guide and Reference. Take the action suggested in the publication.

MSMC0563E

XML parse reset for task_name failed. RETCODE: return_code, RSNCODE: reason_code

Reason:

The task shown in the message attempted to reset a parse instance using the z/OS XML System Services GXL1CTL callable service. However, the attempt failed with the return code and reason code shown in the message.

Action:

For an explanation of the return codes shown in the message, see the IBM z/OS XML System Services User's Guide and Reference. Take the action suggested in the publication.

MSMC0581I

Implementation engine requests

Container ID. . . . . . container_identifier

Version . . . . . . . . . container_version

Run ID . . . . . . . . . run_identifier

Type . . . . . . . . . configuration_flags

Flags . . . . . . . . configuration_flags

Userid . . . . . . . . requesting user_identification

Operation ID . . . . . operation_identifier

SYSMOD ID . . . . . . FMID_SYSMOD_identifier

Process ID . . . . . process_identifier

Flags . . . . . . . . operation_flags

Stage . . . . . . . . operation_stage_number

Prereqs defined . . . prerequisite_name

Prereqs complete . . prerequisite_complete

Actions aborted . . . aborted_actions_value

Actions scheduled . . scheduled_actions_value

Actions successful . successful_actions_value

Actions in error . . action_error_value

Dependent OID . . . . dependent_operation_identifier

Action ID . . . . . . action_identifier

Flags . . . . . . . action_flag_value

Set . . . . . . . . . action_flag_set

Completion code . . action_service_request_completion_code

Return code . . . . . action_service_request_return_code

Library . . . . . . program_library_data_set_name

Volume . . . . . . action_service_request_program_library_volume_serial_number

Flags . . . . . . . . action_service_request_program_library_flags

End of implementation engine requests

Reason:

In response to a DISPLAY IEREQ operator command, the attributes shown are one or more of the active implementation engine requests needed to configure an instance of a CA Technologies product.

Action:

No action is required. This message is informational.

MSMC0582E

Implementation engine is inactive

Reason:

A DISPLAY IEREQ operator command was issued but the implementation engine is inactive.

Action:

No action is required. This message is informational.

MSMC0591W

SCS termination delayed for active configuration requests

Reason:

The SCS address space termination processing has begun, but is being delayed because one or more configuration requests are active.

Action:

1. Verify that the CA Datacom/DB Multi-User Facility (MUF) is started.
2. Verify that all resources required by active configuration requests (for example, devices, data sets) are available.
3. Cancel the SCS address space if the CA Datacom/DB Multi-User Facility (MUF) cannot be started or if all required resources cannot be made available, and the SCS address space must be stopped.