This section lists the common control function (CCF) messages. The CCF manages the initialization of the controller tasks for an address space at start-up time. These messages are issued when an error occurs during initialization.
The initialization sequence table (IST) error recovery routine ESTAE has been entered due to an abend that occurred during an IST interpreter process. The IST interpreter looks at the contents of the IST for the initialization instructions for an address space.
Additional messages are issued by the common control function.
Look for one of the following about this abend condition: BBMZC005E, BBMZC006E, BBMZC007E, or BBMZC008E.
Either a program load (PGLOAD) module or task initiation (PGEXEC) function failed during address space initialization. If a PGLOAD module failed, then module indicates the name of the service component initialization module that failed to load; if a PGEXEC function failed, then module indicates the name of server task that failed to initiate.
Address space initialization fails.
Verify that the product installation was completed according to the documented installation procedure. If the error condition persists, contact your IBM® Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.
A server component task abended during address space initialization due to either a system-related (SYSTEM) or user-related (USER) abend. If the abend is system-related, the server task system abend code is shown as scode and the ucode value appears as 000. Likewise, if the abend is user-related, the server task user abend code is shown as ucode and the scode value appears as 0000.
A system abend code means an MVS™ operating system error has occurred.
A user abend code can be one of the following values:
Initialization fails for address space controller task.
For system (SYSTEM) abends, refer to the MVS Message Library: System Codes manual for abend code information.
For user (USER) abends, do one of the following:
A component initialization module (CIM) instructs the controller task, which performs IST interpretation functions. During controller task initialization, an invalid IST entry was detected when a noncontrol task specified an invalid ATTACH=YES operand for the CIM named module. The entry directed the IST interpreter to initiate an unregistered component as an independent execution unit. This is an illegal operation representing an internal product logic error.
The CIM is not executed, so controller task initialization fails.
Obtain any of the information that is available from the list shown in Diagnostic information for BB messages and contact your IBM Support Center.
During address space initialization, the initialization sequence table (IST) interpreter attempted to establish an error recovery routine ESTAE. The operating system ESTAE service rejected the IST interpreter's recovery exit definition request with a hexadecimal return code value of code.
The IST interpreter fails.
Refer to the MVS Application Development Reference: Services for Assembler Language Programs manual for information about ESTAE service return codes. If the return code does not indicate a possible MVS system failure, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.
The initialization sequence table (IST) interpreter abended during address space initialization. A complete system dump (SDUMP) was taken to one of the system dump data sets.
The IST interpreter fails.
Obtain a copy of the dump and contact your IBM Support Center with any other information that is available from the list shown in Diagnostic information for BB messages.
The initialization sequence table (IST) interpreter abended during address space initialization. There was not enough space allocated to the system dump data set, so only a partial system dump (SDUMP) was taken.
The IST interpreter fails.
Obtain a copy of the dump and then increase the size of your SYS1.DUMP data set. Contact your IBM Support Center with the dump information any other information that is available from the list shown in Diagnostic information for BB messages.
The initialization sequence table (IST) interpreter abended during address space initialization. An attempt to take a system dump (SDUMP) failed.
The IST interpreter fails.
Ensure that at least one system dump data set has been allocated and does not already contain a dump. If a dump data set was not available at the time of the failure, make one available and attempt to recreate the problem that precipitated the dumping operation. Contact your IBM Support Center with the dump information any other information that is available from the list shown in Diagnostic information for BB messages.
If a dump data set was available at the time of the failure, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.
The initialization sequence table (IST) interpreter abended with a code of tnnnn during address space initialization. The component initialization module (CIM) that was dispatched when the abend occurred is named module.
The abend code is either Snnnn or Unnnn, where:
Additional messages are issued.
See messages BBMZC017E, BBMZC018E, and BBMZC019E for more information.
This message is a continuation of message BBMZC019E. An abend occurred from which the initialization sequence table (IST) interpreter recovered and one of the following retry action values indicates the action that was taken:
System Action: The IST interpreter terminates.
User Response: Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.
System Action: The function's retry routine is scheduled.
User Response: If the retry is unsuccessful, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.
System Action: The IST interpreter terminates.
User Response: Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.
System Action: The IST interpreter fails.
User Response: Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.
This message is a continuation of message BBMZC019E. The initialization sequence table (IST) interpreter ESTAE exit was entered to analyze an abend condition. The IST interpreter recovery routine determined that a retry is not possible because the MVS Recovery/Termination Manager (RTM) did not provide a System Diagnostic Work Area (SDWA). Recovery is not attempted.
The IST interpreter fails.
Increase the address space's region size to prevent this situation from occurring in the future. Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.
During address space initialization, the server component initialization load module named module failed with a completion code of nn. The nn value is a hexadecimal value that is dependent upon the failed module. See Completion code values for information about the code value.
IST initialization fails; the address space is not connected.
Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.
During address space initialization, the IST interpreter detected an IST structure error for an entry. The module containing the invalid IST entry is module and the entry is named entry. If the entry name cannot be determined, this value appears as ********.
The reason for the IST structure error in the named module and entry is shown as Reason Text and can be one of the following:
The IST interpreter terminates.
If the Reason Text is UNSUPPORTED VERSION, ensure that all JOBLIB, STEPLIB, and BBILINK libraries are at the same version and maintenance level.
If any other Reason Text value is displayed in the message, contact your IBM Support Center with any of the information available from the list shown in Diagnostic information for BB messages.
A storage block get (SBGET) function failed when attempting to secure storage for a server task queue element (STQE) block. The SBGET function failed with a completion code of xx. See Completion code values for information about the code value. The n value describes the internal load failure that occurred. This is an 8-character value made up of:
The address space does not initialize.
Increase the address space's region size and restart the task or process. If the problem persists, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.
This message issues with messages BBMZC018E and BBMZC019E to provide snap dump information about an abend that occurred during address space initialization. This message also issues with message BBMZC008E. Message BBMZC017E provides the hexadecimal offset value, X'xxxx', from the failing module's entry point where the abend occurred. If the offset cannot be determined, the X'xxxx' value appears as ****. The failing module is identified as module.
Additional messages are issued.
See messages BBMZC018E and BBMZC019E, which contain further snap dump information.
This message issues with messages BBMZC017E and BBMZC019E to provide snap dump information about an abend that occurred during address space initialization. This message also issues with message BBMZC008E. Message BBMZC018E provides information related to storage when the initialization abend occurred.
The program status word (PSW) is the area in storage containing the order in which program instructions were processing when the failure occurred. The active PSW area for the initialization module is PSword. The length, in decimal, of the instruction that failed is il; The hexadecimal interrupt code at completion of the last instruction executed before the abend condition was signaled is code.
Additional messages are issued.
See messages BBMZC017E and BBMZC019E, which contain further snap dump information.
This message issues with messages BBMZC017E and BBMZC018E to provide snap dump information about an abend that occurred during address space initialization. This message also issues with message BBMZC008E. The initialization sequence table (IST) interpreter ESTAE exit has been entered to analyze the abend condition.
The ERR registers are always displayed; the RB registers are displayed only if they are different from the ERR register contents.
The nn-nn values are the starting and ending register numbers and are always:
The reg1 through reg4 values are the 8-digit hexadecimal general registers.
Either message BBMZC010E or BBMZC011E is issued.
See information for either message BBMZC010E or message BBMZC011E, whichever message is issued.
An address space is unable to connect to the coordinating address space (CAS) (system server) known as ssid. The ssid value is the same value defined to the ssid= parameter of the CAS PROC. The address space connection fails with a hexadecimal completion code of X' xxxx', which is one of the following internal values:
The address space is unable to connect to the designated CAS.
Correct the problem, if possible, and restart the CAS.
If the problem persists or if you are unable to correct it, contact IBM Support Center with the text of this message and any of the available information listed in Diagnostic information for BB messages.
An invalid parameter list was used during synchronization of an address space's started server. The reason the parameter list is invalid is shown as a hexadecimal completion code value of X'xxxx'. The X'xxxx' value can be one of the following:
The server cannot be started.
Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.
The system CONNECT service rejected an attempt to initiate a new session. The CONNECT failed for the reason shown as Reason Text, which can be one of the following:
System Action: The user session does not initialize.
User Response: Start the CAS defined as ssid or update the initialization parameter string to specify the subsystem ID, ssid, of an active CAS.
System Action: The session does not initialize.
User Response: Contact your IBM Support Center with this message text and any of the information that is available from the list shown in Diagnostic information for BB messages.
System Action: The session does not initialize.
User Response: Contact your IBM Support Center with this message text and any of the information that is available from the list shown in Diagnostic information for BB messages.
System Action: The user session does not initialize.
User Response: Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.
System Action: The session does not initialize.
User Response: Inspect the BBILINK DD statement to ensure that a valid server program library is specified. If not, correct the file allocation and attempt to establish the session.
If the server program library is valid, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.
System Action: The session does not initialize.
User Response: Update the appropriate IEAAPFxx member of SYS1.PARMLIB to contain the server task library data set name and volume serial, then attempt to establish the session.
System Action: The session does not initialize.
User Response: Ensure that all required file allocations are correct and all required product components have been properly installed.
If the allocations and installation are valid, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.
System Action: The session does not initialize.
User Response: Ensure that all required file allocations are correct and all required product components have been properly installed.
If the allocations and installation are valid, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.
System Action: The session does not initialize.
User Response: Refer to the MVS Application Development Reference: Services for Assembler Language Programs for information about the MVS ATTACH macro to determine the reason for the ATTACH failure. The failure may be caused by either a product installation or local operating system malfunction.
If the problem persists, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.
System Action: The session does not initialize.
User Response: Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.
System Action: The session does not initialize.
User Response: Increase the address space region size and attempt to establish the session.
If the problem persists, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.
System Action: The session does not initialize.
User Response: Refer to the MVS Application Development Reference: Services for Assembler Language Programs manual for information about ESTAEs to determine the reason for the failure. If the failure is not the result of improper product installation or a local MVS operating system problem, obtain any of the information that is available from the list shown in Diagnostic information for BB messages and contact your IBM Support Center.
System Action: The session does not initialize.
User Response: Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.
System Action: The session does not initialize.
User Response: Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.
System Action: The session does not initialize.
User Response: Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.
System Action: The session does not initialize.
User Response: Ensure that all required file allocations are correct and all required product components have been properly installed. Specifically, ensure that all server modules (those targeted to the BBILINK library) reside in an APF authorized library.
If the allocations and installation are valid, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.
System Action: The session does not initialize.
User Response: Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.
System Action: The session does not initialize.
User Response: Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.
The local dispatcher executes work for an address space from a queue. While processing the queue, the local dispatcher encountered an error and reset the queue.
The local dispatching queue is reset and normal processing continues.
None.
The local dispatcher executes work for an address space from a queue. The local dispatcher failed and truncated the queue at the address indicated by address.
Some functions in the queue were lost. This might cause other processing problems later if the local dispatcher attempts to request one of the lost functions.
None.
A function dispatched by the local dispatcher abended. The address address indicates the address of the function.
This message is followed by message BBMZC803E.
Look for message BBMZC803E.
This message is preceded by message BBMZC802E, which shows the address of a failed function. This message shows further diagnostic information about the function failure.
The address of the dispatcher request queue element (DRQE) is drqe; the address space control block (ASCB) for the function is ascb; the task control block (TCB) for the address space is tcb; and the event complete block (ECB) or event notification block (ENB) is address. The ECB/ENB= text only appears in this message when an address value is available in the diagnostic information.
Contact your IBM Support Center with this message text and any of the information that is available from the list shown in Diagnostic information for BB messages.