BBMZCnnn messages

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.

BBMZC000E
IST INTERPRETER ESTAE EXIT ENTERED
Explanation:

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.

Note:
This message is issued with one of the following messages: BBMZC005E, BBMZC006E, BBMZC007E, or BBMZC008E.
System action:

Additional messages are issued by the common control function.

User response:

Look for one of the following about this abend condition: BBMZC005E, BBMZC006E, BBMZC007E, or BBMZC008E.

BBMZC001E
PGLOAD|PGEXEC FAILED FOR COMPONENT MODULE ’module
Explanation:

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.

System action:

Address space initialization fails.

User response:

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.

BBMZC002E
COMPONENT SUBTASK ABENDED (SYSTEM scode/USER ucode)
Explanation:

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:

X20
Module not found
X21
Insufficient storage
X22
Local work pool allocation failure
X23
Local DRQE pool build failure
X24
Initialization sequence table (IST) header error
X25
Unsupported IST level
X26
No component initialization module (CIM) entries in IST
X27
Nonzero reserved IST/ISTE field
X28
Invalid CIM name in IST entry
X29
Local EWRK pool build failure
X2A
Area too small
X2B
Member not found
X2C
Indirect IST load failure
XFF
Abend condition
System action:

Initialization fails for address space controller task.

User response:

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:

BBMZC003E
ATTACH=YES FOR CIM ’module’ REQUESTED BY NON-CONTROL TASK FUNCTION
Explanation:

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.

System action:

The CIM is not executed, so controller task initialization fails.

User response:

Obtain any of the information that is available from the list shown in Diagnostic information for BB messages and contact your IBM Support Center.

BBMZC004E
IST INTERPRETER ESTAE REQUEST FAILED with RC=code
Explanation:

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.

System action:

The IST interpreter fails.

User response:

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.

BBMZC005E
IST INTERPRETER FAILED (COMPLETE DUMP AVAILABLE)
Explanation:

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.

Note:
Message BBMZC000E appears with this message.
System action:

The IST interpreter fails.

User response:

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.

BBMZC006E
IST INTERPRETER FAILED (PARTIAL DUMP AVAILABLE)
Explanation:

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.

Note:
Message BBMZC000E appears with this message.
System action:

The IST interpreter fails.

User response:

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.

BBMZC007E
IST INTERPRETER FAILED (DUMP NOT AVAILABLE)
Explanation:

The initialization sequence table (IST) interpreter abended during address space initialization. An attempt to take a system dump (SDUMP) failed.

Note:
Message BBMZC000E appears with this message.
System action:

The IST interpreter fails.

User response:

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.

BBMZC008E
IST INTERPRETER ABEND tnnnn (LAST CIM DISPATCHED WAS ’module’)
Explanation:

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:

S
Indicates an MVS component issued the abend code.
U
Indicates a user or vendor process could not continue so the product or user code invoked its own ABEND macro.
nnnn
Is the abend code value.
System action:

Additional messages are issued.

User response:

See messages BBMZC017E, BBMZC018E, and BBMZC019E for more information.

BBMZC010I
IST INTERPRETER RECOVERY COMPLETE retry action
Explanation:

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:

UNRECOVERABLE ERROR
The error is unrecoverable.

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.

RETRY SCHEDULED
The procedure is attempted again.

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.

RETRY PROHIBITED
No retry is allowed.

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.

NO RETRY
No retry is possible.

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.

BBMZC011E
IST INTERPRETER RECOVERY FAILED (NO SDWA - RETRY IMPOSSIBLE)
Explanation:

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.

System action:

The IST interpreter fails.

User response:

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.

BBMZC012E
COMPONENT MODULE ’module’ FAILED (COMPLETION CODE=nn)
Explanation:

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.

System action:

IST initialization fails; the address space is not connected.

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.

BBMZC013E
IST ERROR - NAME=module ENTRY=entry (Reason Text)
Explanation:

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:

INVALID HEADER ID
Indicates a serious IST structural error.
UNSUPPORTED VERSION
Indicates that the IST is at a higher level than the IST interpreter is capable of handling.
NO CIM ENTRIES
Indicates that the IST does not contain any entries (probable IST generation error).
NON-ZERO RESERVED FIELD
Indicates that one or more reserved IST header or entry fields contains a non-zero value.
INVALID CIM NAME
Indicates that an IST entry name contains invalid (that is, non-alphanumeric and non-national) characters.
System action:

The IST interpreter terminates.

User response:

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.

BBMZC014E
SBGET FAILED FOR STQE BLOCK; CC=xx ZERR=n
Explanation:

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:

System action:

The address space does not initialize.

User response:

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.

BBMZC017E
ABEND OCCURRED AT OFFSET X’xxxx’ FROM ENTRY POINT ’module
Explanation:

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.

System action:

Additional messages are issued.

User response:

See messages BBMZC018E and BBMZC019E, which contain further snap dump information.

BBMZC018E
PSW=PSword WHERE IC=code/IL=il
Explanation:

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.

System action:

Additional messages are issued.

User response:

See messages BBMZC017E and BBMZC019E, which contain further snap dump information.

BBMZC019E
ERR|RB REGISTERS nn-nn reg1 reg2 reg3 reg4
Explanation:

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.

System action:

Either message BBMZC010E or BBMZC011E is issued.

User response:

See information for either message BBMZC010E or message BBMZC011E, whichever message is issued.

BBMZC101E
UNABLE TO CONNECT TO SYSTEM SERVER ssid CC=X'xxxx'
Explanation:

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:

X'8'
The target CAS subsystem is not defined and the caller did not request a deferred connection.
X'9'
The target CAS subsystem is defined but not active, and the caller did not request a deferred connection.
X'A'
A DEFER, WAIT, or NOTIFY was requested by the caller, but sufficient APF authorization does not exist to process the deferred connect request.
X'B'
The target CAS subsystem was not defined and/or active before the caller-specified RETRY count was exhausted.
X'C'
The server structure exists within the address space, but the server is not active.
X'D'
The server structure exists within the address space and is active, but a dynamic connect was not requested.
X'10'
The server structure exists within the address space, it is active, and a dynamic connect was requested, but the request was for a different CAS.
X'13'
A WAIT was requested by the caller and the target CAS subsystem is defined and is inactive, but initialization of the CAS failed.
X'14'
A WAIT was requested by the caller, the target CAS subsystem is defined and is inactive, and initialization of the CAS was successful, but the CAS became inactive again.
X'20'
The target CAS subsystem is defined and appears to be active, but the CONNECT request failed due to some other unknown error.
System action:

The address space is unable to connect to the designated CAS.

User response:

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.

BBMZC102E
INVALID SYNC PARAMETER LIST FOR SERVER START, CC=X’xxxx
Explanation:

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:

X'101'
Bad parameter list address
X'102'
Incorrect control block ID
X'103'
Unsupported version level
X'104'
Insufficient block length
X'105'
Nonzero reserved field
X'109'
Invalid CAS subsystem name
X'10A'
Invalid CONNECT specification
X'10B'
Invalid TYPE specification
X'10C'
Invalid parameter library member suffix
X'10D'
SHUT and/or TERM ECB address is nonzero and dynamic connection was specified
X'10E'
SHUT and TERM ECB addresses are zero and dynamic connection was not specified
X'10F'
Invalid/missing SHUT ECB address
X'110'
Invalid or missing TERM ECB address
X'111'
Invalid or missing INIT ECB address
X'112'
Out of range RETRY count
X'113'
Out of range RETRY interval
System action:

The server cannot be started.

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.

BBMZC108E
CONNECT FAILED Reason Text
Explanation:

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 SERVER ’ssid’ NOT ACTIVE
The coordinating address space (CAS) named ssid either has not been started or is not fully initialized and ready to establish sessions with other address spaces.

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.

INVALID CPL - RC=X’xxxx
A CONNECT parameter list (CPL) for the MVS CONNECT service was not in the correct form, so the MVS CONNECT service reported an internal hexadecimal return code of X'xxxx'. The return code indicates the reason the parameter list was considered to be invalid. The code can be one of the following:
0001
The CPL version is incorrect.
0002
The CPL reserved field is nonzero.
0003
A mutually exclusive field was encountered.

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 SERVER DENIED ACCESS - RC=X'xxxx'
The address space requesting to connect to the CAS is not authorized to establish a session with the CAS. The CAS reported the precise reason access was denied as an internal hexadecimal return code of X'xxxx'.

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.

MAXIMUM USER CONNECTIONS EXCEEDED
Each CAS accommodates up to 50 user sessions simultaneously. A user is attempting to establish a session with a CAS that already has 50 user sessions active.

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.

SERVER TASKLIB OPEN FAILED - RC=X’xxxx
The server program library identified by the BBILINK DD statement failed to OPEN when an address space was attempting to establish a session. The MVS OPEN service reported an internal hexadecimal return code of X'xxxx', which indicates the reason for the OPEN failure.

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.

SERVER TASKLIB NOT APF AUTHORIZED
The server program library defined by the BBILINK DD statement has not been designated in SYS1.PARMLIB as an APF-authorized data set.

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.

Note:
You must reinitialize the system to activate the SYS1.PARMLIB change, or use an installation or vendor-provided utility to update the system authorized library list.
SERVER CONTROL PROGRAM program NOT FOUND
The server control task program named program could not be located in the server program library identified by the BBILINK DD statement, or in an authorized JOBLIB or STEPLIB library, or any authorized system linklist library.

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.

PROGRAM ’module’ LIBRARY AUTHORIZATION ERROR - RC=X’xxxx
A server load module named module was located in a non-APF authorized library. A library authorization error occurred with an internal hexadecimal return code of X'xxxx'.

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.

ATTACH FAILED FOR SERVER CONTROL PROGRAM ’module’ - RC=X’xxxx
The MVS ATTACH service failed in its attempt to initiate the session control task load module named module. The MVS ATTACH service reported the failure with a hexadecimal return code of X'xxxx'.

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.

SERVER CONTROL PROGRAM INITIALIZATION FAILED - RC=X’xxxx
The address space session control task initialization routine encountered an error condition with an internal hexadecimal return code of X'xxxx', which indicates the reason the session initiation operation failed.

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.

INSUFFICIENT WORKING STORAGE - GETMAIN RC=x’xxxx
The address space initialization session procedure was unable to acquire the storage necessary to support the requested session. The MVS storage manager, in response to an RC type GETMAIN request, reported the error as a hexadecimal return code of X'xxxx'.

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.

UNABLE TO DEFINE RECOVERY ROUTINE - ESTAE RC=x’xxxx
The MVS CONNECT service was unable to establish an ESTAE for the recovery routine. The MVS ESTAE service reported the failure as a hexadecimal return code of X'xxxx'.

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.

UNEXPECTED ABEND tnnnn
An unexpected abend occurred with a abend code of tnnnn. The abend code is either Snnnn or Unnnn, where:
S
Indicates an MVS component issued the abend code.
U
Indicates a user or vendor process could not continue so the product or user code invoked its own ABEND macro.
nnnn
Is the abend code value.

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.

UNEXPECTED TSO TASK STRUCTURE
The MVS CONNECT service determined the TSO address space task structure is incompatible with the current product implementation.

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.

ENVIRONMENT ERROR CODE X’xxxx
The MVS CONNECT service detected an environmental error which prohibits successful establishment of the requested session. The CONNECT service reported the environment error as an internal hexadecimal value of X'xxxx', which indicates the precise reason for the failure.

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.

'LOAD' FAILED FOR EOT EXIT - RC=X’xxxx
A LOAD function failed for the end-of-task exit. The return code for the failure is a hexadecimal value of X'xxxx'.

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.

MAXIMUM SERVER NUMBER REACHED AT X’xxxx
The maximum number of servers that the CAS can support has been reached. A hexadecimal value showing the maximum server limit is indicated by X'xxxx'.

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.

UNDEFINED ’CONNECT’ RC=X’xxxx
The initiation session request was terminated due to an unknown cause. The MVS CONNECT service reported the failure as an internal hexadecimal return code value of X'xxxx'.

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.

BBMZC800E
LOCAL DISPATCHER FAILURE (QUEUE RESET)
Explanation:

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.

System action:

The local dispatching queue is reset and normal processing continues.

User response:

None.

BBMZC801E
LOCAL DISPATCHER FAILURE (QUEUE TRUNCATED AT address)
Explanation:

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.

System action:

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.

User response:

None.

BBMZC802E
LOCAL DISPATCHED FUNCTION AT address ABENDED
Explanation:

A function dispatched by the local dispatcher abended. The address address indicates the address of the function.

System action:

This message is followed by message BBMZC803E.

User response:

Look for message BBMZC803E.

BBMZC803E
DRQE AT drqe, ASCB= ascb, TCB= tcb, ECB/ENB=address
Explanation:

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.

Note:
Depending on the function that abended, there is either an ECB or an ENB value, but not both.
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.

[[ Contents Previous Page | Next Page Index ]]