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.
A session name value, which is used in various messages in this section, appears in the message text as a (b.c), where:
A conversation name value, which is used in various messages in this chapter, appears in the message text as x (y.z), where:
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:
A communications manager subtask has terminated without a system shutdown. Subtasks are expected to end only at a request to do so.
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.
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.
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.
The system proceeds as if the WAIT function completed normally. This may lead to other processing errors and cause synchronization problems.
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.
The communications manager subtask named subtask has abended. The completion code is nnnn and is one of the following values:
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.
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.
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.
The CAS waits for the reply.
Reply with one of the following:
This informational message indicates that the CAS is waiting for VTAM initialization.
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.
None.
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.
VTAM is now active, and the CAS continues to initialize.
None.
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.
The CAS continues its initialization without waiting for VTAM to become active.
Find out why VTAM is inactive. Start VTAM to avoid future errors.
The communication component of the CAS encountered an internal error while setting up a timer.
The CAS terminates. Additional error messages are written to the system log.
Collect the error information from the system log, then contact your IBM Support Center.
The communication component of the CAS encountered an internal error while obtaining storage.
The CAS terminates. Additional error messages are written to the system log.
Collect the error information from the system log, then contact your IBM Support Center.
An invalid reply to message BBCSA010A was entered.
The reply is rejected. Message BBCSA010A is redisplayed and the CAS waits for a reply.
Specify a valid reply. See message BBCSA010A for a list of valid replies.
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.
The CAS's bid response is ignored. The conversation with the end user can malfunction.
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.
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.
The session terminates and the conversation can malfunction.
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.
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.
The session and conversation are canceled. An error message about a conversation failure appears in the window.
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.
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:
Possible status xx values are:
The system responds depending upon the event and session status combination. The session or conversation may be canceled.
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.
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:
Possible status xx values are:
The system responds depending upon the event and session status combination. The session or conversation may be canceled.
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.
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:
Possible status xx values are:
The system responds depending upon the event and session status combination. The session or conversation may be canceled.
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.
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:
Possible status xx values are:
The system responds depending upon the event and session status combination. The session or conversation may be canceled.
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.
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:
Possible status xx values are:
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.
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.
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.
The CAS assumes the session has ended and discontinues processing data for any conversations associated with the session. The user's session may malfunction.
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.
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.
The user session is not activated.
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 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:
The user session is terminated.
Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.
The system 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.
The user session is not activated.
Look for other messages that follow this message.
The address space aspace is no longer active, but a session on another system is attempting communication.
The inbound conversation for the session is terminated. The user on the other system has received a message that the conversation cannot be established.
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.
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.
The session and conversation are terminated.
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).
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.
The conversation is terminated because the session through which it must communicate cannot be located.
Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.
The parameter member member is missing from the data set defined by the BBIPARM DD statement in the coordinating address space (CAS) PROC.
The default parameters are used. These parameters default to a single system configuration.
Define other CASs to this system if you require cross-system communications.
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.
The default parameters are used. These parameters default to a single system configuration.
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.
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.
Any changes entered are valid until an IPL or the CAS is restarted. The parameter member is not updated.
Look for other messages to correct the problem that caused the update failure. Reenter changes and save them.
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:
Possible values for the event are:
The system responds depending upon the event and session status combination. The session may be canceled.
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.
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 depends upon the state of the session. The session can be terminated or a conversation on the session can be terminated.
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.
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.
The session is terminated.
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.
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.
The session is terminated.
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.
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.
Normal processing continues.
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.
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:
Possible values for the event, n, are:
Possible chain values, a, are:
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.
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.
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:
Possible values for the event, n, are:
Possible chain values, a, are:
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.
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.
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:
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.
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.
A positive response message containing the data data was received from the user's address space. No message requesting the data could be located.
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.
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.
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.
The bind request is rejected. If the user was attempting to log on, the logon is rejected.
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.
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.
The bind response is rejected.
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.
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.
The bind response is rejected.
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.
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:
The system proceeds as if the unbind was accepted.
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.
When processing a message, the SSCP PCB internal control block that points to VTAM could not be located.
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.
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.
When processing a message, the SSCP PCB internal control block that points to VTAM could not be located.
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.
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.
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.
Communications with other CASs is not possible. The CAS automatically retries the OPEN of the ACB.
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.
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:
Until the ACB can be opened, communications with local system address spaces are permitted; however, no cross-system communications are supported.
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.
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:
The CAS functions as if the module was deleted and continues processing.
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.
Only two saveareas are required for VTAM but a third savearea is being requested.
The system abends.
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.
VTAM is calling the TPEND exit for application ID applid. This can happen if VTAM is abending or applid has been varied inactive.
The coordinating address space (CAS) closes its application ID and automatically retries the ACB for applid.
See VTAM Programming in the Using Exit Routines chapter under TPEND Exit Routine for an explanation of the reason codes, then correct the problem.
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.
Any active conversations on the session are terminated.
See VTAM Programming in the Using Exit Routines chapter under LOSTERM Exit Routine for an explanation of the reason code, then correct the problem.
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.
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.
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.
None.
Certain debugging modes cause all VTAM requests to be traced. More messages may follow.
This message is issued only for Version 3.1. This message is a continuation of message BBCSJ015W.
None.
None at this time. More messages may follow.
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.
The individual modules will not process their requests. Other errors and session outages can occur as a result.
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.
A predefined, internal limit on the amount of storage that the communications manager can use has been exceeded.
The communications manager stops accepting requests until messages currently in its control space can be delivered.
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 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.
The CAS proceeds as if the unbind was successful.
None.
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:
Until the ACB can be opened, communication with local system address spaces is permitted; however, no cross-system communication is supported.
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.
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:
The local CAS cannot establish communications with the remote CAS having a VTAM application name of applid2.
Perform the following to determine the nature of the communication problem and then correct it:
If the problem persists, contact your IBM Support Center.
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.
The local CAS can communicate cross-system with the remote CAS.
None
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.
The system proceeds as if the WAIT function completed normally. This may lead to other processing errors and cause synchronization problems.
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.
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.
The system proceeds as if the POST function completed normally. This may lead to other processing errors and cause synchronization problems.
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.
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.
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.
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.
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.
The system proceeds as if the FREECB function completed normally. This may lead to other processing errors and cause synchronization problems.
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.
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.
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.
See message BBCZZ902E.
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.
Same as in message BBCZZ901E.
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.