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).
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.
User session initialization fails; the user cannot connect to the coordinating address space (CAS).
Obtain a copy of your logon procedure and contact your IBM® Support Center with the 'string' value in this message.
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.
User session initialization fails; the user cannot connect to the coordinating address space (CAS).
Obtain a copy of your logon procedure and contact your IBM Support Center with the 'string' value in this message.
The TSO CALL command parameter string passed to the user session initialization service module (BBM9ZB00) exceeds the maximum length supported by the service.
User session initialization fails; the user cannot connect to the coordinating address space (CAS).
Obtain a copy of your logon procedure and contact your IBM Support Center.
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.
User session initialization fails; the user cannot connect to the coordinating address space (CAS).
Obtain a copy of your logon procedure and contact your IBM Support Center.
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:
Session initialization fails; the address space cannot connect to the coordinating address space (CAS).
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.
An abend occurred when a local dispatcher queue was being processed.
Processing continues as if the abend did not occur; however, other problems may result from this abend.
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.
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 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.
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 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 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 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.
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.
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.
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.
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.
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.
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.
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.
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.
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 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.
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 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.
The server program library identified by the BBILINK DD statement failed to open.
The address space is disconnected from the coordinating address space (CAS).
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.
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.
The user session is disconnected from the CAS.
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.
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.
Depends on the task that terminated.
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.
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:
Depends on the task that terminated.
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.