Configuration (MSMC) Messages › MSMC0001-0099 › MSMC0017E

MSMC0017E

Program Management Binder request failed, FUNCTION: IEWBIND_function, PROGRAM: program_name, RETCODE: return_code, RSNCODE: reason_code

Reason:

A request to the Program Management Binder using the IEWBIND macro interface failed with the return code and reason code shown in the message. The message text also shows IEWBIND function and the name of the program for which the request was made.

Action:

Determine the cause of the IEWBIND macro failure and correct it. 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.

MSMC0031I

SVS dump for task_name captured

Reason:

As a result of an operator DUMP command, a program error, or the abnormal termination of an SCS address space task, PROGRAM CALL routine, or SRB routine, an SVC dump was captured for the task shown in the message.

Action:

No action is required. This message is informational.

MSMC0032I

SVC dump for task_name suppressed by z/OS_component_name

Reason:

As a result of an operator DUMP command, a program error, or the abnormal termination of an SCS address space task, PROGRAM CALL routine, or SRB routine, an attempt was made to capture an SVC dump for the task shown in the message. However, the SVC dump was suppressed by the z/OS component shown in the message.

Action:

No action is required. This message is informational.

MSMC0033E

SVC dump for task_name failed. RETCODE: return_code, RSNCODE: reason_code

Reason:

As a result of an operator DUMP command, a program error, or the abnormal termination of an SCS address space task, PROGRAM CALL routine, or SRB routine, an attempt was made to capture an SVC dump for the task shown in the message. However, the attempt failed with the return code and reason code shown in the message.

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.

MSMC0035E

Symptom dump for task_name failed. RETCODE: return_code

Reason:

As a result of the abnormal termination of an SCS address space task, PROGRAM CALL routine, or SRB routine, an attempt was made to capture a symptom dump for the task shown in the message. However, the attempt failed with the return code shown in the message.

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.

MSMC0036I

Symptom dump output for task task_name

abnormal_termination_type

Completion code= ABEND completion_code

Reason code= ABEND reason_code

Time= time_of_error

Seq= sequence_number

CPU= central_processor_identifier

ASID= address_space_identifier

PSW at time of error= program_status_word_content, ILC: instruction_length_code, INTC: interrupt_code

PSW load module name= load_module_name, address: load_point_address, offset: offset_name

No active load module found

PSW section name= control_section_name, address= load_point_address, offset= offset_name

Data at PSW next_sequential_instruction_address - contents_of_the_three_full_words

Data at PSW

BEA at time of error= breaking_event_address_register_content_at_time_of_error

BEA load module name= load_module_name, address= load_point_address, offset= offset_name

No active load module found

BEA section name= control_section_name, address=load_point_address, offset= offset_name

Data at BEA breaking_event_address_register control_section_name full_words_content

Data at BEA virtual_storage_status

AR/GPR register_number:

access_register_contents_at_time_of_error/general_purpose_register_content_

at_time_of_error register_number

access_register_contents_at_time_of_error/general_purpose_register_

content_at_time_of_error

End of symptom dump for task task_name

Reason:

As a result of the abnormal termination of an SCS address space task, PROGRAM CALL routine, or SRB routine, a symptom dump was captured for the task shown in the message.

abnormal_termination_type

Identifies the abnormal termination type as System or User.

Reason code= ABEND reason_code

Identifies the ABEND reason code or None (if none was provided).

CPU: central_processor_identifier

Identifies the central processor on which the error occurs. A CPU identifier of 0000 indicates that the operating system was unable to determine on which processor the error occurred.

No active load module found

Indicates that the PSW next sequential instruction address is not within an active load module.

Data at PSW next_sequential_instruction_address - contents_of_the_three_full_words

Indicates the PSW next sequential instruction address minus six-the contents of the three full words beginning at the PSW next sequential instruction address minus six.

Data at BEA virtual_storage_status

Indicates that the virtual storage at the breaking-event-address is unavailable at the time (unallocated) or it is inaccessible by the failing task.

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.

MSMC0041I

SCS task_name started

Reason:

The task shown in the message was successfully attached.

Action:

No action is required. This message is informational.

MSMC0042I

SCS task_name ended. CMPCODE: completion_code

Reason:

The task shown in the message was scheduled for termination and has ended with the completion code shown in the message.

Action:

No action is required. This message is informational.

MSCM0043E

SCS task_name ended unexpectedly. CMPCODE: completion_code

Reason:

The task shown in the message has ended unexpectedly with the completion code shown in the message.

Action:

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

MSMC0044E

SCS task_name ended abnormally. CMPCODE: completion_code

Reason:

The task shown in the message has ended abnormally with the completion code shown in the message.

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.

MSMC0051I

SCS task_name initialization in progress

Reason:

The task shown in the message is beginning the initialization process.

Action:

No action is required. This message is informational.

MSMC0052E

SCS task_name initialization failed

Reason:

The initialization process for the task shown in the message was unsuccessful.

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.

MSMC0053I

SCS task_name initialization complete

Reason:

The task shown in the message has completed the initialization process.

Action:

No action is required. This message is informational.

MSMC0054I

SCS task_name scheduled for termination

Reason:

The task shown in the message has been scheduled for termination.

Action:

No action is required. This message is informational.

MSMC0060W

RACROUTE VERIFY for user_ID failed. SAF RC: SAF_return_code, RC: security_subsystem_return_code RSN: security_subsystem_reason_code

Reason:

An attempt was made to create a trusted user security environment for the current address space using the indicated user ID. The RACROUTE VERIFY service returned the unexpected SAF return code and security subsystem return and reason codes as shown in the message. See the IBM Security Server RACROUTE Macro Reference publication for an explanation of the return and reason codes.

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.

MSMC0061W

program_name attribute is not defined in the program properties table

Reason:

The SCS auxiliary address space control program is defined in the system program properties table (PPT), however, the required program attributes are not correctly defined. The SCS auxiliary address space control program requires specific attributes, assigned through the program properties table, to execute configuration service requests.

Action:

Define the SCS auxiliary address space program in the system program properties table. See the SCS installation guide for the required program attributes to assigned to the SCS auxiliary address space control program.

MSMC0062W

program_name required attributes not defined in program properties table

Reason:

The SCS auxiliary address space control program is defined in the system program properties table (PPT); however, the required program attributes are not correctly defined. The SCS auxiliary address space control program requires specific attributes, assigned through the program properties table, to execute configuration service requests.

Action:

Define the SCS auxiliary address space program in the system program properties table. See the SCS installation guide for the required program attributes to assign to the SCS auxiliary address space control program.

MSMC0099E

message_number is not defined

Reason:

A program attempted to format and write the message with the number shown in this message, but the message is not defined in the SCS message tables.

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.