Configuration (MSMC) Messages › MSMC1000-1025

MSMC1000-1025

MSMC1000I

Auxiliary AS Scheduler Started

Reason:

This message is issued when the Auxiliary address space scheduler has completed initialization and is waiting for work.

Action:

No action is required. This message is informational.

MSMC1001I

Auxiliary AS Scheduler Terminating

Reason:

This message is issued when the Auxiliary address space scheduler is terminating processing.

Action:

No action is required. This message is informational.

MSMC1002I

Auxiliary AS Scheduler Quiescing

Reason:

This message is issued when the Auxiliary address space scheduler is terminating, but there is work remaining in the queues. The scheduler will end when the work is complete.

Action:

No action is required. This message is informational.

MSMC1010I

Auxiliary AS successfully started. ASID: address_space_identifier, STOKEN: address_space_token

Reason:

An SCS auxiliary address has been started to perform configuration services work. The message shows the address space identifier (ASID) and address space token (STOKEN) of the auxiliary address space.

Action:

No action is required. This message is informational.

MSMC1011I

Auxiliary AS stop scheduled. ASID: address_space_identifier, STOKEN: address_space_token

Reason:

An SCS auxiliary address has been notified to stop and will end shortly. The message shows the address space identifier (ASID) and address space token (STOKEN) of the auxiliary address space.

Action:

No action is required. This message is informational.

MSMC1012E

Auxiliary AS create failed, RETCODE: return_code, RSNCODE: reason_code

Reason:

The SCS address space was unable to create an auxiliary address space in which to schedule services work. The ASCRE system service failed with an unexpected return code and reason code.

Action:

1. Use the return code and reason code to diagnose the ASCRE system service failure.
2. Review the JES message log, SCS message log, and system log for other messages describing the failure.
3. 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.

MSMC1013E

Auxiliary AS create failed due to system resource shortage

Reason:

The SCS address space was unable to create an auxiliary address space in which to schedule services work. The ASCRE system service indicated that there is currently a system resource shortage.

Action:

Review the system log for other messages describing the resource shortage. E/SQA shortages, real storage shortages and MAXUSER number of address spaces are all potential reasons that the system cannot create a new address space.

MSMC1014E

Auxiliary AS failed during initialization. JOBNAME: job_name, PROCNAME: process_name, ASID: address_space_identifier

Reason:

The SCS address space successfully created an auxiliary address space in which to schedule services work. However, the auxiliary address space suffered a failure during initialization and terminated unexpectedly.

Action:

1. Review the system log for other messages describing the resource shortage.
2. Review the JES message log for the failing auxiliary address space.
3. Check for JCL error conditions or ABEND conditions that caused the premature failure of the auxiliary address space.

MSMC1015I

Auxiliary AS terminated. ASID: address_space_identifier, STOKEN: address_space_token, RETCODE: return_code, RSNCODE: reason_code

Reason:

An SCS auxiliary address has been force terminated. The message shows the address space identifier (ASID), the address space token (STOKEN), and the return and reason code from the ASDES system service.

Action:

No action is required. This message is informational.

MSMC1016E

Auxiliary AS was not attached in system key

Reason:

The SCS auxiliary address space was not attached to execute in a system key.

Action:

1. Verify that the SCS auxiliary address space program, MSMCAUX, is correctly defined in the z/OS program properties table.
2. Review the SYSLOG for message IEF188I during the start of the auxiliary address space, if the program properties table MSMCAUX entry is correct. This message indicates that the MSMCAUX program was not fetched from an APF authorized library.
3. Verify that each data set in the STEPLIB concatenation is an APF authorized data set, if the auxiliary address space JCL includes a STEPLIB DD statement.
4. Verify that the data set is an APF authorized data set, if the MSMCAUX program resides in a linklist data set.

MSMC1021I

SCS auxiliary AS initialization in progress

Reason:

An SCS auxiliary address space has been started and is beginning the initialization process.

Action:

No action is required. This message is informational.

MSMC1022I

SCS auxiliary AS initialization complete

Reason:

The SCS auxiliary address space has completed the initialization process.

Action:

No action is required. This message is informational.

MSMC1023E

SCS auxiliary AS initialization failed

Reason:

The SCS auxiliary address space initialization process was unable to successfully complete.

Action:

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

MSMC1024I

SCS auxiliary AS termination in progress

Reason:

An SCS auxiliary address space termination processing has begun.

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.

MSMC1025I

SCS auxiliary AS termination complete

Reason:

The SCS auxiliary address space has completed the termination process.

Action:

No action is required. This message is informational.