Messages NS59900 through NS59999

Dynamic Information Failure <date> : Date <time> : Time <data set name> : Dataset Name x'<error code>' : Error Code x'<info code>' : Info Code returnCode : Return code

Explanation: The dynamic information retrieval service routine failed. Surrounding messages indicate whether this condition is critical. Processing continues

User response: None.

Unable to locate entry point of required IMS routine <module name> : Module Name <routine> : Routine Name

Explanation: The routine name name was not found within the specified module. Processing is terminated.

User response: Contact BMC IMS Software Support Personnel.

Dynamic Information Failure <date> : Date <time> : Time <ddname> : DDName x'<error code>' : Error Code x'<info code>' : Info Code returnCode : Return code

Explanation: The dynamic information retrieval service routine failed. Surrounding messages indicate whether this condition is critical. Processing continues

User response: None.

Invalid program name in attach request <program> : Requesting CSECT Name <subroutine> : Requesting Subroutine <routine> : Program Name

Explanation: The job attempted to attach a subtask with an invalid subtask program name. Processing terminates.

User response: Contact BMC Technical Support.

Command processing failed. <function> : Function returnCode : Return code reasonCode : Reason code Address space termination started.

Explanation: While attempting to process a command, the running job experienced an internal processing error. Processing terminates

User response: Contact BMC IMS Software Support Personnel.

<date> <time> Dynamic deconcatenation failed <ddname> : DD Name <error code> : Error Code <info code> : Information Code returnCode : Return Code

Explanation: An attempt to deconcatenate the specified DD name failed. Processing continues.

User response: Review the MVS Authorized Assembler Services Guide (Interpreting DYNALLOC Return Codes) to identify the cause of the error. If you cannot determine an environmental cause for the error, contact BMC Technical Support.

Task <program> detached.

Explanation: During termination processing, an attached task was forcibly detached. Tasks are forcibly detached when the running job is forced to terminate by the MVS STOP command (P jobname). Termination processing continues.

User response: No action is required.

Attached task terminated. <program> : Program Name <date> <time> : Date/Time Started <date> <time> : Date/Time Ended returnCode : Return Code reasonCode : Reason Code

Explanation: This message indicates that an attached subtask terminated. Processing continues.

User response: No action required.

<program> terminated. RC= returnCode

Explanation: The application program completed with the specified returned code Processing continues

User response: None

Latch obtain error <error> : Failure Reason <date> : Date Terminated <time> : Time Terminated <program> : CSECT Name <subroutine> : Subroutine Name <latch number> : Latch Number

Explanation: This BMC product uses MVS Latch Services for high-speed process serialization. An attempt to obtain a latch failed. Processing terminates.

User response: Contact BMC Technical Support.

<program> <text>. RC= returnCode

Explanation: The application program terminated with a non-zero return code. Processing continues

User response: None

Dynamic Allocation Failure <date> : Date <time> : Time <task> : Task <program> : Caller <ddname> : DDName <data set name> : Dataset Name <member> : Member Name x'<error code>' : Error Code x'<info code>' : Info Code returnCode : Return code

Explanation: The dynamic allocation service routine failed. Surrounding messages indicate whether this condition is critical. The system response depends on the purpose of the dynamic allocation.

• If the dynamic allocation call attempted to identify whether a DD name is allocated, processing continues.

• If the dynamic allocation call attempted to dynamically allocate or deallocate a data set, processing terminates.

User response: Correct the cause of the dynamic allocation failure and submit the job again.

Dynamic Deallocation Failure <date> : Date <time> : Time type : Element Type <element> : Element Name x'<error code>' : Error Code x'<info code>' : Info Code returnCode : Return code

Explanation: The dynamic allocation service routine failed. Subsequent messages indicate whether this error is critical. Processing terminates.

User response: Correct the cause of the dynamic deallocation failure and submit the job again.

Dynamic Allocation Failure <data set name> : Dataset Name

Explanation: While attempting to allocate the library which contains the BMC Data Collection Facility modules, an allocation failure occurred. Processing terminates

User response: You will need to look in the BMC IMS Software Server log for any messages pertaining to the cause of the dynamic allocation failure. These messages will include the DAIR return, reason and information codes. Review these codes to ascertain whether or not a transient system condition may have prevented the successful allocation of the library. If so, re-submit the job. If not, contact BMC IMS Software support personnel with the aforementioned information.

Duplicate Queue Create Request <program> : Requesting CSECT Name <subroutine> : Requesting Subroutine <queue name> : Queue Name

Explanation: The job experienced an internal processing error. Processing terminates.

User response: Contact BMC Technical Support.

ALET Create Error <program> : Requesting CSECT Name <subroutine> : Requesting Subroutine <data space name> : Dataspace Name returnCode : Return code reasonCode : Reason Code

Explanation: The running job could not create an ALET for a dataspace. Processing terminates.

User response: Contact BMC Technical Support.

Dataspace Create Error <program> : Requesting CSECT Name <subroutine> : Requesting Subroutine <data space name> : Dataspace Name returnCode : Return Code reasonCode : Reason Code

Explanation: The running job could not create a dataspace. Processing terminates.

User response: Contact BMC Technical Support.

Internal Error. Invalid Parameter List <program> : CSECT Name <subroutine> : Subroutine Name <routine> : Called Subroutine

Explanation: The running job experienced an internal processing error. Processing terminates with a S0C3-3 abend.

User response: Contact BMC Technical Support.

MVS Latch Services Create Failed <program> : Calling CSECT Name <subroutine> : Calling Subroutine returnCode : Return code

Explanation: The running job failed when it attempted to create an MVS latch set to facilitate high-speed internal serialization. Processing terminates.

User response: A latch services failure can indicate significant MVS system problems. Contact your MVS System Administrator and have them review the return and reason codes in the MVS Authorized Assembler Services Reference ENF - IXG manual under ISGLCRT. If you do not feel that this is the result of an MVS problem, Contact BMC Technical Support.

<product> Module Version Error <program> : Loading CSECT Name <subroutine> : Loading Subroutine <routine> : Error CSECT Name

Explanation: The running job encountered an error when it validated the versions of its processing modules. The message displays information about the module that was found to be a different version than the main routine (NSOMAIN). Processing terminates.

User response: Verify that you have not mixed libraries. If not, Contact BMC Technical Support.

<product> Load Error <program> : Loading CSECT Name <subroutine> : Loading Subroutine <routine> : Error CSECT Name returnCode : Return Code reasonCode : Reason Code

Explanation: The running job experienced an error while attempting to load a requisite module. Processing terminates

User response: Contact BMC Technical Support.

<product> termination complete. RC=returnCode, Reason=x'reasonCode'

Explanation: The running job has terminated processing. No additional action is taken.

User response: No action is required.