BBMZBnnn messages

This section lists the user session messages. These messages are associated with address spaces that are attempting to connect to the coordinating address space (CAS).

BBMZB010E
INVALID EXEC PARAMETER 'string' ENCOUNTERED
Explanation:

A syntax error was detected in the JCL EXEC or TSO CALL command that was passed to the user session initialization service module, BBM9ZB00. The syntax error is that either a keyword or value associated with a keyword is invalid. The invalid keyword or value is shown as 'string' in the message.

System action:

User session initialization fails; the user cannot connect to the coordinating address space (CAS).

User response:

Obtain a copy of your logon procedure and contact your IBM® Support Center with the 'string' value in this message.

BBMZB012E
'string' VALUE IS TOO SHORT
Explanation:

A parameter keyword value specification in the JCL EXEC or TSO CALL command parameter string passed to the user session initialization service module (BBM9ZB00) is too short. The 'string' value in this message shows the value that is too short.

System action:

User session initialization fails; the user cannot connect to the coordinating address space (CAS).

User response:

Obtain a copy of your logon procedure and contact your IBM Support Center with the 'string' value in this message.

BBMZB013E
MAXIMUM PARAMETER STRING/COMMAND LENGTH (247 BYTES) EXCEEDED
Explanation:

The TSO CALL command parameter string passed to the user session initialization service module (BBM9ZB00) exceeds the maximum length supported by the service.

System action:

User session initialization fails; the user cannot connect to the coordinating address space (CAS).

User response:

Obtain a copy of your logon procedure and contact your IBM Support Center.

BBMZB014E
CMD AND PGM PARAMETERS CANNOT BOTH BE DEFINED
Explanation:

The JCL EXEC or TSO CALL command parameter string passed to the user session initialization service module (BBM9ZB00) specifies both the CMD and PGM keywords. CMD and PGM are mutually exclusive keywords, so both cannot be defined in the same string.

System action:

User session initialization fails; the user cannot connect to the coordinating address space (CAS).

User response:

Obtain a copy of your logon procedure and contact your IBM Support Center.

BBMZB800E
CONTROL TASK FAILURE FOR (reason text)
Explanation:

A failure occurred during the session control task initialization process which prevented successful initiation of the session. The reason for the failure is indicated by the reason text, which is one of the following:

ENVIRONMENT CREATE WHERE CC=X’xxxx’ / ZERR=n
The common environment create service reported an error with a hexadecimal completion code of X'xxxx'. 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:
  • Component
  • Module procedure
  • Attempted function
  • Return code
COMPONENT X’ii’ WHERE CC=X’xxxx’ / ZERR=n
A required service component with the hexadecimal value X'ii', which identifies the component's internal registration number, encountered an error while attempting to initialize. The service component had a hexadecimal completion code of X'xxxx'. See Completion code values for information about the code value. The n value describes the internal initialization failure that occurred. This is an 8-character value made up of:
  • Component
  • Module
  • Attempted function
  • Return code
IST ’module’ WHERE PGLOAD CC=X’xxxx’ / ZERR=n
PGLOAD encountered an error while attempting to load the required initialization sequence table (IST); named module. PGLOAD reported the error with a hexadecimal completion code of X'xxxx'. 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:
  • Component
  • Module procedure
  • Attempted function
  • Return code
System action:

Session initialization fails; the address space cannot connect to the coordinating address space (CAS).

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.

BBMZB801E
ABEND PROCESSING LOCAL DISPATCHER QUEUE
Explanation:

An abend occurred when a local dispatcher queue was being processed.

System action:

Processing continues as if the abend did not occur; however, other problems may result from this abend.

User response:

Look for preceding messages that indicate the nature of this abend. 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.

BBMZB880E
CONNECT FAILED (reason text)
Explanation:

The system connect service rejected an attempt to initiate an address space session. The reason for the session request failure is indicated by the reason text, which is shown in the following list:

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 accept sessions.

System Action: The 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 address space 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 address space 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 a user 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 address space 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 identified by the BBILINK DD statement has not been designated in SYS1.PARMLIB as an APF-authorized data set.

System Action: The address space 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 user 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 task library defined by the BBILINK DD statement, or in an authorized JOBLIB or STEPLIB library or any authorized system linklist library.

System Action: The address space 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 address space 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 user 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 address space does not initialize.

User Response: Refer to the MVS Application Development Reference: Services for Assembler Language Programs manual 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 user session control task initialization routine encountered an error condition with an internal hexadecimal return code of X'xxxx' indicating the reason the session initiation operation was terminated.

System Action: The address space does not initialize.

User Resonse: 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 user 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 address space 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 address space does not initialize.

User Response: Refer to the MVS Application Development Reference: Services for Assembler Language Programs 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 an 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 address space does not initialize.

User Resonse 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 user's TSO address space task structure to be incompatible with the current product implementation.

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.

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 address space 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 address space 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.

BBMZB881E
OPEN FAILED FOR TASKLIB DCB
Explanation:

The server program library identified by the BBILINK DD statement failed to open.

System action:

The address space is disconnected from the coordinating address space (CAS).

User response:

Inspect the task library file allocation to ensure it specifies a valid (application) program library. If not, update the file allocation and attempt to reestablish the user 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.

BBMZB882E
ATTACH FAILED FOR APPLICATION PROGRAM ’program’ - RC=X’xxxx
Explanation:

The session initiator successfully established a connection with the designated coordinating address space (CAS), however, the session initiator was unable to complete an MVS ATTACH service for program. The program value is the name of a TSO command or application program load module specified in the initialization parameter string. The MVS ATTACH service reported a hexadecimal return code value of X'xxxx' when it rejected the application task initiation request.

System action:

The user session is disconnected from the CAS.

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. Ensure that JOBLIB/STEPLIB and/or TASKLIB allocations are correct.

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.

BBMZB883E
taskname TASK TERMINATED - COMPLETION CODE=X'nnnn'
Explanation:

A task named taskname has terminated with a hexadecimal value indicating a completion code of X'nnnn'. The taskname value is a 1- to 8-character value. The completion code value depends on the application. See Completion code values for information about the code value.

System action:

Depends on the task that terminated.

User response:

Look for other related messages. If the taskname value begins with BB, then contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages; otherwise, see the appropriate product documentation for more information.

BBMZB884E
taskname TASK ABNORMALLY TERMINATED - CODE=tnnnn
Explanation:

A task named taskname has abended with a value indicating an abend code of tnnnn. The taskname value is a 1- to 8-character value defined on the session initialization parameter string which indicates the TSO command or program that has abended. 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:

Depends on the task that terminated.

User response:

Look for other related messages. If the taskname value begins with BB, then contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages; otherwise, see the appropriate product documentation for more information.

[[ Contents Previous Page | Next Page Index ]]