BBCxxnnn messages

This section lists the communications manager messages. The communications manager controls the communication tasks between the coordinating address space (CAS) and other address spaces and MVS™ systems.

Session name values

A session name value, which is used in various messages in this section, appears in the message text as a (b.c), where:

a
Is a unique number of variable length that identifies the session between this coordinating address space (CAS) and a partner CAS.
b
Is the system ID of the partner CAS. The partner system ID is derived from the name defined to this partner CAS.
c
Is the LU6.2 mode type, which has a valid value of DEFAULT; other values are not supported.

Conversation name values

A conversation name value, which is used in various messages in this chapter, appears in the message text as x (y.z), where:

x
Is a unique number of variable length that identifies the conversation internally. This value is used to correlate messages to sessions.
y
Is a 1- to 8-character value identifying the TSO user ID or the name of the address space service that owns the conversation.
z
Is a 1- to 8-character value, used internally, to uniquely identify the conversation. For TSO users, this value is assigned as nondisplayable.

Sense code values

Sense codes are displayed in several of the messages prefixed with BBCS. The BBCS codes are closely related to the standard meanings assigned to VTAM® sense codes, as described in the VTAM Format and Protocol Reference Manual: Architecture Logic for LU Type 6.2. Sense codes that are not in that manual or that have a slightly different meaning when used in a BBCS message are documented here. If you cannot find a sense code that appears in a BBCS message in the following list, refer to the VTAM documentation for the standard meaning:

08350001
Same as LU6.2 sense code 08350000; see the VTAM documentation.
08350002
Same as LU6.2 sense code 08350000; see the VTAM documentation.
08350003
Same as LU6.2 sense code 08350000; see the VTAM documentation.
08350004
Same as LU6.2 sense code 08350000; see the VTAM documentation.
08350005
Same as LU6.2 sense code 08350000; see the VTAM documentation.
084c0000
The requested user or application is not active.
08640000
The conversation terminated abnormally because either the user terminated abnormally or the coordinating address space (CAS) is stopping and is terminating all conversations.
08ff0001
Internal error occurred sending the BIND.
1008600b
Resource failure; no retry is attempted.
10086021
Allocation error; transaction is not recognized.
20030001
Same as LU6.2 sense code 20030000; see the VTAM documentation.
20030002
Same as LU6.2 sense code 20030000; see the VTAM documentation.
20030003
Same as LU6.2 sense code 20030000; see the VTAM documentation.
20030004
Same as LU6.2 sense code 20030000; see the VTAM documentation.
20120000
Invalid sense code received.
BBCSA002S
A SUBTASK ENDED UNEXPECTEDLY
Explanation:

A communications manager subtask has terminated without a system shutdown. Subtasks are expected to end only at a request to do so.

System action:

Either the system terminates or existing sessions continue, but they might encounter processing problems. New sessions might not be established and existing sessions might not terminate.

User response:

Restart the coordinating address space (CAS) and contact your IBM® Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBCSA005E
WAIT FAILED, RC=X'n'
Explanation:

A communications manager WAIT function has failed while the function was waiting to be posted. The return code is indicated by n and is always a value of 8, which means either an error recovery failed or an invalid control block was detected.

System action:

The system proceeds as if the WAIT function completed normally. This may lead to other processing errors and cause synchronization problems.

User response:

See other messages to determine whether or not to restart the coordinating address space (CAS). 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.

BBCSA006E
subtask ABENDED, COMPLETION CODE=X'nnnn'
Explanation:

The communications manager subtask named subtask has abended. The completion code is nnnn and is one of the following values:

1600
PC call to unavailable service.
17xx
Recovery manager abends.
1799
"Should Not Occur" condition (see note).
1800
"C" housekeeping failure.
1801
GSI housekeeping failure.
1802
GSI router housekeeping failure.
1803
Transaction manager housekeeping failure.
1804
SAS/C resident module failure.
1899
Improper event for DYNAEC "EPD".
1900
Storage manager abend code.
3000
Built-in service function error.
4000
Pseudo GSI service failure.
4080
Unrecoverable control task error.
4090
Server/application initialization error.
4095
Task terminated by PGTERM.
System action:

Either the system terminates or existing sessions continue, but they might encounter processing problems. New sessions might not be established and existing sessions might not terminate.

Note:
In the case of completion code 1799 (Should Not Occur), an abend occurs and a record is written to the SYS1.LOGREC data set; no additional messages are issued and no SDUMP is taken.
User response:

See messages that follow to determine whether the coordinating address space (CAS) is terminating.

If the CAS is not terminating, restart it and contact your IBM Support Center with the name of the subtask in this message.

If the CAS is terminating, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBCSA010A
VTAM IS NOT ACTIVE. REPLY R TO RETRY, C TO CONTINUE WITHOUT VTAM, OR T TO TERMINATE
Explanation:

This is a WTOR message that prompts the user to take an action concerning the initialization of the CAS. The CAS uses VTAM for cross system communication. If VTAM is inactive, the CAS can't communicate with other defined CAS(s) running on different systems.

System action:

The CAS waits for the reply.

User response:

Reply with one of the following:

R
To restart the CAS if VTAM has completed its initialization or has been started.
C
To continue initialization of the CAS without cross-system communication.
T
To terminate the CAS. When the CAS terminates, message BBMZC012E is displayed and the CAS is abended with code of U4090.
BBCSA011I
VTAM IS NOT ACTIVE YET, CAS IS DELAYED UNTIL VTAM IS UP
Explanation:

This informational message indicates that the CAS is waiting for VTAM initialization.

System action:

The CAS checks the status of VTAM every 30 seconds for three minutes. If VTAM is still not active after three minutes, message BBCSA010A is displayed. If VTAM becomes active within three minutes, the CAS continues its initialization.

User response:

None.

BBCSA013I
VTAM IS NOW ACTIVE, CAS IS STARTING
Explanation:

VTAM was inactive when the CAS was started. However, VTAM completed its initialization and the CAS continues to initialize. This message normally follows message BBCSA011I.

System action:

VTAM is now active, and the CAS continues to initialize.

User response:

None.

BBCSA014W
VTAM IS INOPERATIVE, CAS IS CONTINUING. ERRORS MAY OCCUR
Explanation:

The user specified C when message BBCSA010A was issued. The CAS continues to initialize without VTAM. If cross system communication is enabled and VTAM is still inactive, errors may occur. If this is a standalone CAS, no errors occur.

System action:

The CAS continues its initialization without waiting for VTAM to become active.

User response:

Find out why VTAM is inactive. Start VTAM to avoid future errors.

BBCSA015E
ERROR IN SETTING TIMER, BBC TERMINATED
Explanation:

The communication component of the CAS encountered an internal error while setting up a timer.

System action:

The CAS terminates. Additional error messages are written to the system log.

User response:

Collect the error information from the system log, then contact your IBM Support Center.

BBCSA016E
CSZ_GETCB ERROR IN CSA40, BBC TERMINATED
Explanation:

The communication component of the CAS encountered an internal error while obtaining storage.

System action:

The CAS terminates. Additional error messages are written to the system log.

User response:

Collect the error information from the system log, then contact your IBM Support Center.

BBCSA017E
INVALID REPLY
Explanation:

An invalid reply to message BBCSA010A was entered.

System action:

The reply is rejected. Message BBCSA010A is redisplayed and the CAS waits for a reply.

User response:

Specify a valid reply. See message BBCSA010A for a list of valid replies.

BBCSB004E
BID RSP FAILURE ON SESSION a (b.c) CONVERSATION x (y.z)
Explanation:

The coordinating address space (CAS) received a bid response (RSP) for this session and conversation, but the session resource cannot be located in the free session pool, so the bid response failed.

Sessions occur between CASs and CICSPlex® SM address spaces (CMASs) and user address spaces. The session name is described in Session name values. Conversations are always initiated when a user opens a window. The conversation name is described in Conversation name values.

System action:

The CAS's bid response is ignored. The conversation with the end user can malfunction.

User response:

Attempt logging off the system and then reconnecting. If the conversation is malfunctioning and a logoff is not possible, contact the system operator to cancel the TSO 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.

BBCSB006E
CANNOT FIND BIDDING CONVERSATION FOR SESSION a (b.c)
Explanation:

The coordinating address space (CAS) received a bid response for a session and located the session resource in the free session pool, but could not find the conversation associated with the session. The conversation name is unknown because it cannot be found. The session name is described in Session name values.

System action:

The session terminates and the conversation can malfunction.

User response:

Look for other messages on the partner CAS system for more information about the session failure. The partner CAS is identified in the session name. 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.

BBCSB009I
SESSION a (b.c) WITH CONVERSATION x (y.z) IS BEING CANCELED DUE TO SENSE=xx
Explanation:

Due to the reason specified by the sense code xx, the coordinating address space (CAS) is cancelling the session. This message can be caused by a user logging off abnormally (S522 and so on). See Sense code values for possible sense code values. The indicated conversation terminates when the session is canceled. The session name is described in Session name values. Conversations are always initiated when a user opens a window. The conversation name is described in Conversation name values.

This message can be caused by a user logging off abnormally (S522 and so on). See the Format and Protocol Reference Manual: Architecture Logic for LU Type 6.2 for details on possible sense code values.

System action:

The session and conversation are canceled. An error message about a conversation failure appears in the window.

User response:

Close the window and retry the request. If the problem persists, contact your IBM Support Center with the sense code from this message and any of the information that is available from the list shown in Diagnostic information for BB messages.

BBCSB010E
PROGRAMMING SEQUENCE ERROR ON BIDDER SESSION a (b.c) WITH CONVERSATION x (y.z), EVENT=n, SESSION STATUS=xx
Explanation:

A programming sequence error occurred when the bidder session, with a status of xx, had an event of n. The session name is described in Session name values. Conversations are always initiated when a user opens a window. The conversation name is described in Conversation name values.

Possible event n values are:

0
Receive positive bid response
1
Receive bid
2
Receive attach
3
Receive security message
4
Receive free session message
5
Receive yield session message
6
Receive session activation for first speaker
7
Receive session activation for bidder
8
Receive session activation security

Possible status xx values are:

0
Session activation
1
Free
2
Pending attach
3
In use
4
Pending security message
5
Waiting for a bid
System action:

The system responds depending upon the event and session status combination. The session or conversation may be canceled.

User response:

Look for additional messages and respond to those actions. If the problem continues, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBCSB011E
PROGRAMMING SEQUENCE ERROR ON FIRST SPEAKER SESSION a (b.c) WITH CONVERSATION x (y.z), EVENT=n, SESSION STATUS=xx
Explanation:

A programming sequence error occurred when the first speaker session, with a status of xx, had an event of n. The session name is described in Session name values. Conversations are always initiated when a user opens a window. The conversation name is described in Conversation name values.

Possible event n values are:

0
Send get session message
1
Receive bid
2
Receive attach
3
Receive security message
4
Receive free session message
5
Receive yield session message
6
Receive session activation for first speaker
7
Receive session activation for bidder
8
Receive session activation security

Possible status xx values are:

0
Session activation
1
Free
2
Pending attach
3
In use
4
Pending security message
5
Pending a bid
System action:

The system responds depending upon the event and session status combination. The session or conversation may be canceled.

User response:

Look for additional messages and respond to those actions. If the problem continues, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBCSB012E
PROGRAMMING SEQUENCE ERROR FOR BIDDER CONVERSATION x (y.z) ON SESSION a (b.c), EVENT=n, CONVERSATION STATUS=xx
Explanation:

A programming sequence error occurred when the bidder conversation, with a status of xx, had an event of n. The session name is described in Session name values. Conversations are always initiated when a user opens a window. The conversation name is described in Conversation name values.

Possible event n values are:

0
Send get session message
1
Receive positive bid response
2
Receive negative bid response
3
Receive attach
4
Send deallocate conversation message

Possible status xx values are:

0
Free conversation
1
Conversation in use
2
Conversation waiting for a session
System action:

The system responds depending upon the event and session status combination. The session or conversation may be canceled.

User response:

Look for additional messages and respond to those actions. If the problem continues, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBCSB013E
PROGRAMMING SEQUENCE ERROR FOR FIRST SPEAKER CONVERSATION x (y.z) ON SESSION a (b.c), EVENT=n, CONVERSATION STATUS=xx
Explanation:

A programming sequence error occurred when the first speaker conversation, with a status of xx, had an event of n. The session name is described in Session name values. Conversations are always initiated when a user opens a window. The conversation name is described in Conversation name values.

Possible event n values are:

0
Send allocate session message
1
Send get session message
2
Receive remote attach
3
Receive local attach
4
Send deallocate conversation message

Possible status xx values are:

0
Free conversation
1
Conversation in use
2
Conversation waiting for a session
System action:

The system responds depending upon the event and session status combination. The session or conversation may be canceled.

User response:

Look for additional messages and respond to those actions. If the problem continues, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBCSB014E
BEGIN INPUT SEQUENCE ERROR OCCURRED FOR SESSION a (b.c) WITH CONVERSATION x (y.z), EVENT=n, SESSION STATUS=xx
Explanation:

The Begin Input Sequence was the event that occurred when the session had a status of xx causing a sequence error. The session name is described in Session name values. Conversations are always initiated when a user opens a window. The conversation name is described in Conversation name values.

Possible event n values are:

0
Send Begin Input Sequence request
1
Receive Begin Input Sequence reply
2
Receive Begin Input Sequence request
3
Send Begin Input Sequence reply

Possible status xx values are:

0
Reset state
1
Begin Input Sequence sent
2
Begin Input Sequence received
3
Closed state
System action:

The system responds depending upon the event and session status combination. The session or conversation may be canceled. The error can be corrected when the session or conversation is canceled.

User response:

Look for additional messages and respond to those actions. If the problem continues, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBCSB016E
RRB IGNORED ON SESSION a (b.c) CONVERSATION x (y.z) DATA=data
Explanation:

A Response/Request Block (RRB) containing the information specified as data was ignored because the data could not be processed. The data could not be processed because it arrived after the conversation had terminated. Typically, this occurs when the coordinating address space (CAS) is processing a session outage condition on a session that was supporting the conversation.

The session name is described in Session name values. Conversations are always initiated when a user opens a window. The conversation name for which the data could not be processed is described in Conversation name values.

System action:

The CAS assumes the session has ended and discontinues processing data for any conversations associated with the session. The user's session may malfunction.

User response:

Attempt logging off and then logging back on to the system. If this message condition continues, restart the CAS. If the error persists after restarting, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBCSB017E
LU6.2 MODE NAME modename NOT VALID FOR SESSION a (b.c)
Explanation:

The session a (b.c) has requested an invalid LU6.2 mode name of modename. The mode name is not supported because it is incorrectly defined. This is an application error.

The session name is described in Session name values.

System action:

The user session is not activated.

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.

BBCSB022E
LU6.2 MODE NAME id.sysname.modename NOT FOUND FOR SESSION a (b.c) with CONVERSATION x (y.z)
Explanation:

The session a (b.c) with a conversation of x (y.z) cannot locate an LU6.2 mode name of id.sysname.modename. The mode name is not supported because it is not valid. This is an application error.

The session name is described in Session name values. Conversations are always initiated when a user opens a window. The conversation name is described in Conversation name values. The LU6.2 mode name shows the following information:

id
The internal system ID
sysname
The name of the system
modename
The LU6.2 mode name
System action:

The user session is terminated.

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.

BBCSB023I
LU6.2 MODE NAME modename NOT VALID FOR system sysname
Explanation:

The system sysname has requested an invalid LU6.2 mode name of modename. The mode name is not supported because it is incorrectly defined. This message is issued with other messages about the system. The sysname is the name of the system.

System action:

The user session is not activated.

User response:

Look for other messages that follow this message.

BBCSB024E
THE ADDRESS SPACE aspace IS NOT AVAILABLE
Explanation:

The address space aspace is no longer active, but a session on another system is attempting communication.

System action:

The inbound conversation for the session is terminated. The user on the other system has received a message that the conversation cannot be established.

User response:

Attempt the request when the address space is active. If the address space is active and this message is issued, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBCSB028E
PROTOCOL ERROR WITH SENSE nn ON SESSION a (b.c) CONVERSATION x (y.z)
Explanation:

The communications protocol between two coordinating address spaces (CASs) has been violated with a sense code of nn. The protocol violation has occurred on the partner CAS for the indicated session and conversation. This message can be issued when a user session terminates abnormally or a timeout condition is incurred, because the CAS may deliberately force a protocol error to end the session connection.

See Sense code values for possible sense code values. The session name is described in Session name values. Conversations are always initiated when a user opens a window. The conversation name is described in Conversation name values.

System action:

The session and conversation are terminated.

User response:

If possible, find out if the user session timed out or logged off improperly. If this error occurred for any other reason, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages for both coordinating address spaces (CASs).

BBCSB030E
SESSION a (b.c) CANNOT BE FOUND FOR CONVERSATION x (y.z)
Explanation:

The session a (b.c) for conversation x (y.z) is not where it is supposed to be. A programming error has occurred. The session name is described in Session name values. Conversations are always initiated when a user opens a window. The conversation name is described in Conversation name values.

System action:

The conversation is terminated because the session through which it must communicate cannot be located.

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.

BBCSB036E
PARAMETER MEMBER member MISSING, DEFAULT PARAMETERS USED
Explanation:

The parameter member member is missing from the data set defined by the BBIPARM DD statement in the coordinating address space (CAS) PROC.

System action:

The default parameters are used. These parameters default to a single system configuration.

User response:

Define other CASs to this system if you require cross-system communications.

BBCSB037E
PARAMETER MEMBER member INVALID, DEFAULT PARAMETERS USED
Explanation:

The contents of the parameter member member are invalid. This condition can occur if ISPF Edit was used to attempt to update this member. The parameter member member contains binary data and cannot be modified.

System action:

The default parameters are used. These parameters default to a single system configuration.

User response:

Delete the parameter member member in the data set defined by the BBIPARM DD statement in the CAS PROC. Redefine other CASs to this system, if you require cross-system communications. The parameter member is dynamically created when you save your changes.

BBCSB038E
UPDATE TO PARAMETER MEMBER member FAILED
Explanation:

Changes were made to parameter member member, but the changes were not saved to this member. These changes are temporarily in effect, but only while the coordinating address space (CAS) continues to execute. Other messages should indicate the cause of the update failure.

System action:

Any changes entered are valid until an IPL or the CAS is restarted. The parameter member is not updated.

User response:

Look for other messages to correct the problem that caused the update failure. Reenter changes and save them.

BBCSC001E
PROGRAMMING SEQUENCE ERRPR ON LU SESSION a (b.c) AN INVALID STATE OCCURRED WHEN LU=luID WITH CID=cid had session status=xx and event=n
Explanation:

A programming sequence error occurred when the LU session a (b.c) on LU luID had a status of xx and attempted to process event n.

The session name is described in Session name values. The luID value is the LU6.2 conversation ID. The CID (connection identifier) value for the LU is cid, which is a 4-byte field.

Possible values for the session status are:

0
Reset
1
Pending initiation response, PLU
2
Pending initiation response, SLU
3
Pending CINIT
4
Pending bind
5
Pending local path control response
6
Pending local bind response
7
Pending local initiation half-session response
8
Pending remote path control response
9
Pending remote bind response
10
Pending remote initiation half-session response
11
Active
12
Pending unbind response

Possible values for the event are:

0
Activate session as a PLU
1
Activate session as an SLU
2
Positive response to initialize session
3
Negative response to initialize session
4
Notify message
5
CINIT okay
6
CINIT no good
7
Positive response to path control connect
8
Negative response to path control connect
9
Positive response to bind, format okay
10
Positive response to bind, format no good
11
Negative response to bind, format okay
12
Negative response to bind, format no good
13
Positive response from initialize half-session
14
Negative response from initialize half-session
15
Bind okay
16
Bind did not work
17
Session deactivation pending
18
Session deactivation active
19
Session deactivation cleanup active
20
Half-session aborting
21
Positive response to unbind
22
Negative response to unbind
23
Session cleanup
24
CTERM orderly
25
CTERM forced
26
Reset, session outage notification
27
Reset, normal
System action:

The system responds depending upon the event and session status combination. The session may be canceled.

User response:

Look for additional messages and respond to those actions. If the problem continues, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBCSC002E
RU=n RECEIVED NEGATIVE RESPONSE DUE TO SENSE=code
Explanation:

A negative response has been received from the partner coordinating address space (CAS) that was attempting to send an RU of n, with a sense code of code, through the session to this CAS. An RU is a request unit, which is the smallest sized VTAM protocol message unit that is processed on a VTAM link. The sense code is documented in either the Format and Protocol Reference Manual: Architecture Logic for LU Type 6.2 or in VTAM Messages and Codes.

System action:

System action depends upon the state of the session. The session can be terminated or a conversation on the session can be terminated.

User response:

Check for related VTAM messages or other CAS messages to determine problem. 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.

BBCSC003E
UNABLE TO CORRELATE BIND FOR RU=n, SENSE=code
Explanation:

A bind response was received by the coordinating address space (CAS), but no corresponding bind was sent requesting a bind response. The RU n identifies the bind response that was received. An RU is a request unit, which is the smallest sized VTAM protocol message unit that is processed on a VTAM link. This RU has a sense code of code. The sense code is documented in either the Format and Protocol Reference Manual: Architecture Logic for LU Type 6.2 or in VTAM Messages and Codes.

System action:

The session is terminated.

User response:

Check for related VTAM messages or other CAS messages to determine problem. 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.

BBCSC004E
UNABLE TO CORRELATE UNBIND FOR RU=n, SENSE=code
Explanation:

An unbind response was received by the coordinating address space (CAS), but no corresponding unbind was sent requesting an unbind response. The RU n identifies the unbind response that was received. An RU is a request unit, which is the smallest sized VTAM protocol message unit that is processed on a VTAM link. This RU has a sense code of code. The sense code is documented in either the Format and Protocol Reference Manual: Architecture Logic for LU Type 6.2 or in VTAM Messages and Codes.

System action:

The session is terminated.

User response:

Check for related VTAM messages or other CAS messages to determine problem. 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.

BBCSD002W
RRB DISCARDED, HS_ID=N/A, LU_ID=N/A, CID=N/A, DATA=message text
Explanation:

A message with the text of message text was directed to a session that no longer exists. The session had a VTAM RRB (Request Reply Buffer) that was discarded once the session ended.

System action:

Normal processing continues.

User response:

Check for related VTAM or coordinating address space (CAS) messages that could indicate a problem. If none are issued, this is an isolated occurrence and no action is required.

BBCSD005E
PROGRAMMING SEQUENCE ERROR ON RECEIVE FOR HALF SESSION hsID, WHERE RH=rh AND DATA=data. INVALID STATE OCCURRED WITH SENSE OF code WHEN LU=luID with CID=cid HAD STATUS=xx AND EVENT=n WITH CHAIN=a.
Explanation:

A programming sequence error with a sense code of code occurred for half session hsID. The half session was on LU luID with a status of xx and attempted to process event n with a chain value of a when the error occurred. See Sense code values for possible sense code values.

The half session ID, hsID, is an internal value representing the coordinating address space's connection to VTAM, which is half of a session between two CASs. The error occurred while the CAS was attempting to process an RU (VTAM request unit), which contains two parts: an RH (request header) and data. In this case the RH value was rh and the data value was data.

The luID value is the LU6.2 conversation ID. The CID (connection identifier) value for the LU is cid, which is a 4-byte field.

Possible values for the half session status, xx, are:

00
Between chain
01
In chain
02
Negative response sent
03
Pending response
04
Pending send reply

Possible values for the event, n, are:

0
Receive request to begin chain
1
Receive request to end chain, definite response
2
Receive request to end chain, exception response with conditional end bracket
3
Receive request to end chain, exception response with change direction
4
Receive request to end chain, Begin Input Sequence
5
Send a negative response, Function Management Data with LU status
6
Send a positive response, Function Management Data with LU status
7
Send a response of ready to receive
8
Send a request reply
9
Receive a request to begin chain
10
Receive a request to not begin chain

Possible chain values, a, are:

0
Begin chain
1
End chain
2
Not specified
System action:

The system responds depending upon the half session status, event, and chain combination. The half session is canceled and, as a result, the partner half session on the other CAS also is canceled. Any conversations on the session are terminated.

User response:

Look for additional messages and respond to those actions. If the problem continues, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBCSD006E
PROGRAMMING SEQUENCE ERROR ON SEND FOR HALF SESSION hsID, WHERE RH=rh AND DATA=data. INVALID STATE OCCURRED WITH SENSE OF .code WHEN LU=luID WITH CID=cid HAD STATUS=xx AND EVENT=n WITH CHAIN=a.
Explanation:

A programming sequence error with a sense code of code occurred for half session hsID. The half session was on LU luID with a status of xx and attempted to process event n with a chain value of a when the error occurred. See Sense code values for possible sense code values.

The half session ID, hsID, is an internal value representing the coordinating address space (CAS)'s connection to VTAM, which is half of a session between two CASs. The error occurred while the CAS was attempting to process an RU (VTAM request unit), which contains two parts: an RH (request header) and data. In this case the RH value was rh and the data value was data.

The luID value is the LU6.2 conversation ID. The CID (connection identifier) value for the LU is cid, which is a 4-byte field.

Possible values for the half session status, xx, are:

00
Between chain
01
In chain
02
Negative response received
03
Pending response
04
Pending receive reply

Possible values for the event, n, are:

0
Receive request to begin chain
1
Receive request end chain, definite response
2
Receive request to end chain, exception response with conditional end bracket
3
Receive request to end chain, exception response with change direction
4
Receive request to end chain, Begin Input Sequence
5
Send a negative response, Function Management Data with LU status
6
Send a positive response, Function Management Data with LU status
7
Send a response of ready to receive
8
Send a request reply

Possible chain values, a, are:

0
Begin chain
1
End chain
2
Not specified
System action:

The system responds depending upon the half session status, event, and chain combination. The half session is canceled and, as a result, the partner half session on the other CAS also is canceled. Any conversations on the session are terminated.

User response:

Look for additional messages and respond to those actions. If the problem continues, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBCSI001E
LDISP FAILED, RC=n, REASON CODE=reason
Explanation:

A communications manager LDISP (local dispatch) function has failed while the function attempted to schedule a receive. The return code is indicated by n and is always a value of 8, which occurs when the user terminates suddenly (x22) while the coordinating address space (CAS) is attempting to send data to the user.

Possible reason code values, reason, are:

0101
Nonzero reserved field
0102
Unsupported version ID
0201
Nonzero reserved field
0202
Invalid or conflicting options
0203
Invalid target memory ID
0301
Nonconnected memory
0302
System work cell size is less than the minimum allowed
0303
Unable to obtain work cell
0304
Local dispatcher not active
System action:

The system ignores that it cannot schedule a receive for the user and waits for the user to terminate. If the problem is not due to an x22, the user may experience a loss of data. This error may lead to other processing errors and cause synchronization problems.

User response:

If the reason code (reason) is 0301, ignore this message. For all other reason codes, contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBCSI002E
INVALID RECEIVE, DATA=data
Explanation:

A positive response message containing the data data was received from the user's address space. No message requesting the data could be located.

System action:

The system proceeds as if the data request could be located. Storage used to hold the data may not be released. This can lead to other processing errors.

User response:

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

BBCSJ001E
UNABLE TO CORRELATE BIND REQUEST TO CID=cid OR TO URC=urc
Explanation:

The coordinating address space (CAS) cannot locate the VTAM INIT_SELF for a bind request. Typically, a user has attempted to log on to the CAS through VTAM directly. The bind request contains a URC (user request correlation) value of urc and is directed at the LU with a CID (connection identifier) value of cid, which is a 4-byte field. The URC is the part of the bind request that is used to locate the originator of a request when a response is received.

System action:

The bind request is rejected. If the user was attempting to log on, the logon is rejected.

User response:

Access to the CAS should be attempted through TSO, if the user was attempting to log on. If this message is issued for any other reason, look for other messages and contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBCSJ002E
UNABLE TO CORRELATE BIND RESPONSE TO CID=cid OR TO URC=urc
Explanation:

The coordinating address space (CAS) cannot locate the VTAM INIT_SELF for a bind response. This is a programming error. The bind response contains a URC (user request correlation) value of urc and is directed at the LU with a CID (connection identifier) value of cid, which is a 4-byte field. The URC is the part of the bind response that is used to locate the originator of a request for the response.

System action:

The bind response is rejected.

User response:

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

BBCSJ003E
UNABLE TO CORRELATE BIND RESPONSE TO CID=cid
Explanation:

The coordinating address space (CAS) cannot locate the VTAM INIT_SELF for a bind response. This is a programming error. The bind response is directed at the LU with a CID (connection identifier) value of cid, which is a 4-byte field.

System action:

The bind response is rejected.

User response:

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

BBCSJ004E
UNBIND FAILED FOR CID=cid, RC='n'
Explanation:

When the coordinating address space (CAS) attempted to unbind the session with the CID (connection identifier) value of cid, the internal VTAM unbind routine failed with a return code of n. The cid is a 4-byte field. Typically, this problem is caused when the session does not exist because VTAM has terminated the session. Possible return code values, n, are:

4
Could not obtain storage for RPL
8
TERMSESS failed
System action:

The system proceeds as if the unbind was accepted.

User response:

Correct the error by referring to the VTAM Programming manual for information about the return code value. Also look for VTAM messages indicating VTAM failures that may have caused this problem.

BBCSJ006S
UNABLE TO LOCATE SSCP PCB
Explanation:

When processing a message, the SSCP PCB internal control block that points to VTAM could not be located.

System action:

The coordinating address space (CAS) cannot communicate with other address spaces. The message being processed when this error occurred is not issued. User sessions can malfunction.

User response:

Restart the CAS. 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.

BBCSJ007S
UNABLE TO LOCATE SSCP PCB
Explanation:

When processing a message, the SSCP PCB internal control block that points to VTAM could not be located.

System action:

The coordinating address space (CAS) cannot communicate with other address spaces. The message being processed when this error occurred is not issued. User sessions can malfunction.

User response:

Restart the CAS. 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.

BBCSJ008W
A VTAM OPEN FOR ACB applid FAILED WITH AN ERROR CODE OF X'nnnn'
Explanation:

VTAM is reporting to the coordinating address space (CAS) that an OPEN of an ACB with the application ID of applid failed with an error code of nnnn. The CAS had attempted to open the ACB to connect to VTAM. The applid is a 1- to 8-character value.

System action:

Communications with other CASs is not possible. The CAS automatically retries the OPEN of the ACB.

User response:

Correct the problem associated with the indicated OPEN error code. Error codes are discussed in the VTAM Programming manual in the OPEN macro instruction section.

BBCSJ009E
LOAD FOR module FAILED, ZERR=n
Explanation:

The coordinating address space (CAS) cannot open its own VTAM ACB during processing because the program module is required and it could not be loaded. The n value describes the internal load failure that occurred. This is an 8-character value comprised of:

System action:

Until the ACB can be opened, communications with local system address spaces are permitted; however, no cross-system communications are supported.

User response:

Check to see if one of the following problems is the cause of this error:

If the problem persists, 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.

BBCSJ010W
DELETE FOR module FAILED, ZERR=n
Explanation:

The program module loaded during coordinating address space (CAS) processing to open the VTAM ACB was not deleted. The n value describes the internal delete failure that occurred. This is an 8-character value comprised of:

System action:

The CAS functions as if the module was deleted and continues processing.

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.

BBCSJ011S
ALL SAVEAREAS ARE IN USE
Explanation:

Only two saveareas are required for VTAM but a third savearea is being requested.

System action:

The system abends.

User response:

Restart the coordinating address space (CAS) and 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.

BBCSJ012W
TPEND EXIT ENTERED FOR applid, REASON CODE IS xx
Explanation:

VTAM is calling the TPEND exit for application ID applid. This can happen if VTAM is abending or applid has been varied inactive.

System action:

The coordinating address space (CAS) closes its application ID and automatically retries the ACB for applid.

User response:

See VTAM Programming in the Using Exit Routines chapter under TPEND Exit Routine for an explanation of the reason codes, then correct the problem.

BBCSJ013W
LOSTERM EXIT ENTERED FOR applid SESSION WITH CID=cid AND URC=urc, REASON CODE IS reason
Explanation:

VTAM is calling the LOSTERM exit for the session with a connection identifier (CID) value of cid and a user request correlation (URC) value of urc for application applid.

The cid is a 4-byte field. The URC is used to locate the originator of a request for the response.
VTAM is calling the LOSTERM exit for the reason identified in reason.

System action:

Any active conversations on the session are terminated.

User response:

See VTAM Programming in the Using Exit Routines chapter under LOSTERM Exit Routine for an explanation of the reason code, then correct the problem.

BBCSJ014W
A VTAM CLOSE FOR ACB applid FAILED WITH AN ERROR CODE OF X'nnnn'
Explanation:

VTAM is reporting to the coordinating address space (CAS) that a CLOSE of an ACB with the application ID of applid failed with an error code of nnnn. The CAS had attempted to close the ACB to disconnect from VTAM. The applid is a 1- to 8-character value.

System action:

The CAS proceeds as if the CLOSE was successful. Potential problems can occur if the CAS later attempts to reopen the ACB application ID defined as applid.

User response:

Correct the problem associated with the indicated CLOSE error code. Error codes are discussed in VTAM Programming in the CLOSE macro instruction section. If the problem persists, contact your IBM Support Center.

BBCSJ015I
The RPL macro encountered an error while attempting operation on applid applid for destination destination. Detected by module module.
Explanation:
System action:

None.

User response:

Certain debugging modes cause all VTAM requests to be traced. More messages may follow.

BBCSJ016E
R0=rrrr, R15=ssss, FDBK=ffff, FDBK2=kkkk
Explanation:

This message is issued only for Version 3.1. This message is a continuation of message BBCSJ015W.

System action:

None.

User response:

None at this time. More messages may follow.

BBCSJ017W
MODULE module HAS DETECTED AN UNEXPECTED EVENT FOR DATA=data, RC='nnnn'
Explanation:

A programming error has occurred. The module module detected the error that had a return code of nnnn for the associated data at storage location data.

System action:

The individual modules will not process their requests. Other errors and session outages can occur as a result.

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.

BBCSJ018I
SYSTEM UNDER STRESS
Explanation:

A predefined, internal limit on the amount of storage that the communications manager can use has been exceeded.

System action:

The communications manager stops accepting requests until messages currently in its control space can be delivered.

User response:

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.

BBCSJ019W
UNBIND NOT PROCESSED FOR CID=cid ON PATH path
Explanation:

The coordinating address space (CAS) was attempting to end a session by processing an unbind on path path with the CID (connection identifier) value of cid. The cid value is a 4-byte field. The unbind request cannot be processed because the session has already ended or because a TPEND has occurred on VTAM. The path value is the path control ID for the LU associated with the session.

System action:

The CAS proceeds as if the unbind was successful.

User response:

None.

BBCSJ020E
MODULE module DETECTED A TIMER SERVICE FAILURE WITH AN INTERNAL ERROR of n
Explanation:

The coordinating address space (CAS) could not OPEN its own VTAM ACB during processing, so a timer service is automatically set to retry the OPEN of the ACB. The module module detected that the attempt to set the timer service failed with an internal error of n. The internal error, n, is an 8-character value comprised of:

System action:

Until the ACB can be opened, communication with local system address spaces is permitted; however, no cross-system communication is supported.

User response:

If the problem does not correct itself, restart the CAS. If the problem persists, 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.

BBCSJ021W
LOCAL CAS(ssid) USING APPLID(applid1) IS UNABLE TO COMMUNICATE WITH REMOTE CAS AT DESTINATION applid2
Explanation:

During initialization or execution, the local CAS with a subsystem ID of ssid and a VTAM application ID of applid1 could not communicate with a remote CAS having a VTAM application ID of applid2.

The local CAS, using VTAM application applid1, attempted to establish communication with a defined remote CAS known to the local CAS as applid2. This message issues for each remote CAS the local CAS cannot connect to, where applid2 is a unique VTAM application ID for each remote CAS. When a remote CAS becomes available and the local CAS can establish communication, message BBCSJ022I is issued for the remote CAS.

When the local CAS is already active and has communications established with remote CASs, this message is issued when communications are disrupted because a remote CAS, with a VTAM application ID of applid2, becomes unavailable for some reason. When a remote CAS becomes available again and the local CAS can establish communications, message BBCSJ022I is issued for the remote CAS.

Possible reasons that the local CAS cannot communicate with a remote CAS include:

System action:

The local CAS cannot establish communications with the remote CAS having a VTAM application name of applid2.

User response:

Perform the following to determine the nature of the communication problem and then correct it:

If the problem persists, contact your IBM Support Center.

BBCSJ022I
COMMUNICATION BETWEEN LOCAL CAS(ssid) USING APPLID(applid1) AND REMOTE CAS AT DESTINATION applid2 IS NOW ACTIVE
Explanation:

The local coordinating address space (CAS) with a subsystem ID of ssid and a VTAM application ID of applid1 has established communications with a remote CAS having a VTAM application ID of applid2.

System action:

The local CAS can communicate cross-system with the remote CAS.

User response:

None

BBCSZ001S
WAIT FAILED, RC='n'
Explanation:

A communications manager WAIT function has failed while the function was waiting to be posted. The return code is indicated by n and is always a value of 8, which means either an error recovery failed or an invalid control block was detected.

System action:

The system proceeds as if the WAIT function completed normally. This may lead to other processing errors and cause synchronization problems.

User response:

See other messages to determine whether or not to restart the coordinating address space (CAS). 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.

BBCSZ002S
POST FAILED, RC='n'
Explanation:

A communications manager POST function has failed when the coordinating address space (CAS) attempted to post. The return code is indicated by n and is always a value of 8, which means either an error recovery failed or an invalid control block was detected.

System action:

The system proceeds as if the POST function completed normally. This may lead to other processing errors and cause synchronization problems.

User response:

See other messages to determine whether or not to restart the CAS. 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.

BBCSZ003E
GETCB FAILED FOR xxxx BYTES, RC='n'
Explanation:

A communications manager GETCB function has failed when the coordinating address space (CAS) attempted to get storage for a control block. The return code is indicated by n and is always a value of 8, which means an error recovery failed, an invalid control block was detected, or an out-of-storage condition exists.

System action:

The system attempts to proceed normally, although sessions and conversations requiring the storage from the failed GETCB function are terminated. Other sessions and conversations in process may be affected.

User response:

Attempt to free storage by reducing the current number of connected users to see if the problem corrects itself. If freeing storage does not correct the problem, look for other messages and contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBCSZ004E
FREECB FAILED, RC='n'
Explanation:

A communications manager FREECB function has failed when the coordinating address space (CAS) attempted to free a control block. The return code is indicated by n and is always a value of 8, which means either an error recovery failed or an invalid control block was detected.

System action:

The system proceeds as if the FREECB function completed normally. This may lead to other processing errors and cause synchronization problems.

User response:

See other messages to determine whether or not to restart the CAS. 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.

BBCZZ901E
THE MESSAGE MACRO HAS FAILED, PARAMETER AREA=
Explanation:

This is a diagnostic message for the coordinating address space's message macro, which is used to issue all messages. The message macro failed when attempting to issue a message about a system function. This message always appears with message BBCZZ902E.

System action:

The function message that the CAS was attempting to issue when the message macro failed is not issued, but messages BBCZZ901E and BBCZZ902E are issued. CAS processing continues unless an unrecoverable error has occurred.

Note:
If the CAS is being brought down by operator request, this message might appear.
User response:

See message BBCZZ902E.

BBCZZ902E
hexvalue hexvalue hexvalue hexvalue
Explanation:

This message is always issued with message BBCZZ901E. This message contains four 8-character hexadecimal values, hexvalue, that represent the parameter area of the function message that did not get issued because the message macro failed. This message line can appear up to 7 times, as needed, to show the parameter area information for the function message.

System action:

Same as in message BBCZZ901E.

User response:

Contact your IBM Support Center with the variable information shown in this message and any of the information that is available from the list shown in Diagnostic information for BB messages.

[[ Contents Previous Page | Next Page Index ]]