Explanation | This message is for informational purposes only. |
Action | None |
Explanation | This message is for informational purposes only with TRC=1. |
Action | None |
Explanation | This message is for informational purposes only with TRC=2. |
Action | None |
Explanation | The EXEC CICS START TRUE for BBOATRUE failed. |
Action | Check BBOQ log for further messages.Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Explanation | The EXEC CICS EXTRACT TRUE for BBOATRUE failed. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Explanation | The EXEC CICS DISABLE TRUE for BBOATRUE failed. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Explanation | The BBOC request cannot be processed since the BBOATRUE is not active. |
Action | Issue the BBOA START_TRUE and retry. |
Explanation | This is an incorrect parameter length. |
Action | Change the parameter length and retry. |
Explanation | This is an incorrect parameter length. |
Action | Change the parameter length and retry. |
Explanation | This is an incorrect parameter length. |
Action | Change the parameter length and retry. |
Explanation | The BBOC MNC parameter cannot exceed 9999. |
Action | Change the parameter value and retry. |
Explanation | The BBOC MXC parameter cannot exceed 9999. |
Action | Change the parameter value and retry. |
Explanation | An error occurred with the BBOC TXN parameter. This parameter must be set to Y or N. |
Action | Change the parameter value and retry. |
Explanation | An error occurred during BBOC UNREGISTER. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Explanation | An error occurred with the BBOC SEC parameter. This parameter must be set to Y or N. |
Action | Change the parameter value and retry. |
Explanation | Unable to write messages to the named TDQ. |
Action | Ensure that the subject TDQ is defined to CICS. Refer to BBOACSD definition sample file for BBOQ that is located in the /<smpe_root>/mso/OLA/samples directory. |
Explanation | This is a BBOC REGISTER error. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Explanation | The default link server registration could not complete. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. Verify that WebSphere Application Server is available. |
Explanation | This is an incorrect parameter length. |
Action | Change the parameter value and retry. |
Explanation | This is an incorrect parameter length. |
Action | Change the parameter value and retry. |
Explanation | The BBOC START_SRVR REGISTER API call failed. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Explanation | This is an incorrect parameter length. |
Action | Change the parameter value and retry. |
Explanation | This is an incorrect parameter length. |
Action | Change the parameter value and retry. |
Explanation | An error occurred during a BBOC START_SRVR request. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Explanation | This is a BBOC UNREGISTER error. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Explanation | This is an incorrect parameter length. |
Action | Change the parameter value and retry. |
Explanation | This is an incorrect parameter length. |
Action | Change the parameter value and retry. |
Explanation | The Trace parameter must be TRC=|1|2 |
Action | Change the parameter and retry. |
Explanation | This is an incorrect parameter length. |
Action | Change the parameter value and retry. |
Explanation | This request was an unrecognized BBOC request. |
Action | You entered an unrecognized BBOC command. Change the command and retry. |
Explanation | An error occurred during BBOC START_TRUE. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Explanation | An error occurred during BBOC STOP_TRUE. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Explanation | An error occurred during BBOC START_SRVR |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Explanation | An error occurred during BBOC REGISTER. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Explanation | An error occurred during BBOC UNREGISTER. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Explanation | An error occurred with the BBOC XTR parameter. This parameter must be Y or N. |
Action | Change the parameter and retry. |
Explanation | Unable to issue the EXEC CICS START for the specified link server transaction. |
Action | Refer to the CICS reference material for EIBRESP and EIBRESP2 meanings for EXEC CICS START TRANSACTION for more information. |
Explanation | The specified parameter must be present and is not. |
Action | Specify the correct parameter and retry. |
Explanation | This is an incorrect parameter length. |
Action | Change the parameter value and retry. |
Explanation | A new link server entry could not be created by this control task. |
Action | Try to create the link server again. If the problem persists, contact IBM support. |
Explanation | An improper value was passed for the REUC parameter. |
Action | Correct this and make it a numeric value with no more than 8 digits. |
Explanation | An improper value was passed for the REUC parameter. |
Action | This must be a numeric value no larger than 2G. |
Explanation | An improper value was passed for the REUT parameter. |
Action | Correct this and make it a numeric value with no more than 8 digits. |
Explanation | An improper value was passed for the REUT parameter. |
Action | This must be a numeric value no larger than 2G. |
Explanation | The start server command completed with warnings. |
Action | Look for messages in the CICS log file indicating conflicting parameters in the start server command. |
Explanation | This message is for informational purposes only. |
Action | None |
Explanation | This message is for informational purposes only with TRC=1. |
Action | None |
Explanation | This message is for informational purposes only with TRC=2. |
Action | None |
Explanation | When you process a BBOC STOP_SRVR, the BBO$ transaction terminates. |
Action | None |
Explanation | When you process a BBOC STOP_SRVR, the BBO$ transaction and all related BBO# transactions terminate. |
Action | None |
Explanation | Communication with the WebSphere Application Server for z/OS server instance indicated in the message has been lost. |
Action | Ensure that the WebSphere Application Server for z/OS server instance is running. If the problem persists, contact IBM support. |
Explanation | An error was encountered while receiving a request from WebSphere Application Server for z/OS. The return code and reason code are indicated in the message. |
Action | The return code and reason code in the message corresponds with a return and reason code for the BBOA1RCA service. Look up the explanation for this return and reason code, and attempt to correct the problem as desribed. If the problem persists, contact IBM support. |
Explanation | The BBOA1RCA receive request returned with non-zero return and reason code. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. Refer to the optimized local adapters API reference return codes for BBOA1RCA. |
Explanation | An exception occurred while the optimized local adapters link server was running. |
Action | None Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Explanation | The BBOA1GET get data request returned with a non-zero return and reason code. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. Refer to the optimized local adapters API reference return codes for BBOA1GET. Verify that WebSphere Application Server is available. |
Explanation | Unable to retrieve message context data. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. Verify that WebSphere Application Server is available. |
Explanation | An error occurred in GET from channel IBM-WAS-ADAPTER and container IBM-WAS-EXCEPTN. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. Contact IBM support and report the problem. |
Explanation | An error occurred in GET from channel IBM-WAS-ADAPTER and container IBM-WAS-EXCEPTN. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. Contact IBM support and report the problem. |
Explanation | BBOA1SRX send exception response request returned with non-zero return and reason code. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. Refer to the optimized local adapters API reference return codes for BBOA1SRX. Verify that WebSphere Application Server is still available. |
Explanation | The BBOA1CNR release connection request returned with a non-zero return and reason code. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. Refer to the optimized local adapters API reference return codes for BBOA1CNR. Verify that WebSphere Application Server is still available. |
Explanation | Unable to issue EXEC CICS START for specified link transaction identifier. |
Action | Refer to the CICS reference material for EIBRESP and EIBRESP2 meanings for EXEC CICS START TRANSACTION for more information. |
Explanation | Propagation of a link transaction ID into CICS from WebSphere Application Server is not supported while running the link server with REU=Y. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Explanation | This message is for informational purposes only. |
Action | None |
Explanation | This message is for informational purposes only with TRC=1. |
Action | None |
Explanation | This message is for informational purposes only with TRC=2. |
Action | None |
Explanation | When you process a BBOC STOP_SRVR, the BBO# transaction terminates. |
Action | None |
Explanation | When you process a BBOC STOP_SRVR, the BBO# transaction terminates. |
Action | None |
Explanation | The link server received a request that included a transaction context. This version of CICS does not support transaction propagation over OLA. |
Action | In order to propagate transactions to CICS Transaction Server using OLA, you must be using version 4.1 or higher of CICS Transaction Server for z/OS. |
Explanation | The version of CICS Transaction Server for z/OS could not be determined by the link server. |
Action | Verify that you are using a supported version of CICS Transaction Server for z/OS. If the problem persists, contact IBM support. |
Explanation | The link server attempted to invoke the EXEC CICS INQURE SYSTEM CICSTSLEVEL API, and received the error code indicated in the message. |
Action | Verify that the user running the link server has the authority to invoke the INQUIRE SYSTEM CICSTSLEVEL API. If the problem persists, contact IBM support. |
Explanation | The link server attempted to invoke the EXEC CICS INQUIRE UOWLINK START command but received the error code indicated in the message. |
Action | Contact IBM support. |
Explanation | After resolving an in-doubt UOW, the link server attempted to delete the UOWLINK which it created to record its interest in the UOW. The UOWLINK could not be found and has already been deleted. |
Action | None |
Explanation | After resolving an in-doubt UOW, the link server attempted to delete the UOWLINK which it created to record its interest in the UOW. An error code was received when invoking the EXEC CICS SET UOWLINK() DELETE API. |
Action | Make sure that the user running the link server has the authority to invoke the EXEC CICS SET UOWLINK() DELETE API. Verify that the UOWLINK specified in the message has been deleted. If the problem persists, contact IBM support. |
Explanation | After resolving an in-doubt UOW, the link server attempted to find the UOWLINK which it created to record its interest in the UOW. An error code was received when invoking the EXEC CICS INQUIRE UOWLINK() NEXT API. |
Action | Contact IBM support. |
Explanation | The link server was attempting to resolve an in-doubt UOW corresponding to an XID received from WebSphere Application Server for z/OS. An error was encountered while iterating the UOWs using the EXEC CICS INQUIRE UOW() NEXT API. |
Action | The operation will be retried. If the problem persists, contact IBM support. |
Explanation | An attempt was made to resolve an in-doubt UOW which was in the wrong state. |
Action | The operation will be retried. If the problem persists, contact IBM support. |
Explanation | An attempt was made to commit or backout an in-doubt UOW using the EXEC CICS SET UOW() API, but an error code was received. |
Action | The operation will be retried. Make sure that the user running the link server has the authority to invoke the EXEC CICS SET UOW() API. If the problem persists, contact IBM support. |
Explanation | WebSphere Application Server for z/OS requested a list of in-doubt XIDs from CICS Transaction Server for z/OS. The link server tried to obtain storage to hold the XIDs but an error code was received when invoking the EXEC CICS GETMAIN API. |
Action | The number of XIDs to be returned is listed in the message. The amount of storage to return a single XID is about 140 bytes. Calculate the amount of storage required and ensure that much storage is available in the CICS Transaction Server address space, and available to the link server transaction. If the problem persists, contact IBM support. |
Explanation | WebSphere Application Server for z/OS requested a list of in-doubt XIDs from CICS Transaction Server from z/OS. While using the EXEC CICS INQUIRE UOWLINK NEXT API to iterate UOWLINK objects, an error code was received. |
Action | The operation will be retried. If the problem persists, contact IBM support. |
Explanation | WebSphere Application Server for z/OS requested a list of in-doubt XIDs from CICS Transaction Server for z/OS. While using the EXEC CICS INQUIRE UOW() API to get information about a UOW, an error code was received. |
Action | The operation will be retried. If the problem persists, contact IBM support. |
Explanation | WebSphere Application Server for z/OS requested a list of in-doubt XIDs from CICS Transaction Server for z/OS. While using the EXEC CICS GETMAIN API to build the list of XIDs, an error code was received. |
Action | The operation will be retried. The amount of storage required by this call is about 144 bytes. Make sure that this much storage is available to the link server. If the problem persists, contact IBM support. |
Explanation | The version of the link server and link tasks are different. |
Action | Be sure that the link task (BBOACLNK) and link server (BBOACSRV) were both obtained from the same version of WebSphere Application Server for z/OS. If the problem persists, contact IBM support. |
Explanation | A request was read by the link task which contains a transaction XID. The XID is longer than the maximum length allowable by CICS Transaction Server for z/OS. The length (in bytes) of the XID is displayed in the message. |
Action | Contact IBM support. |
Explanation | A communication error occurred while communicating with WebSphere Application Server for z/OS. The link server task will end. |
Action | Ensure that the WebSphere Application Server for z/OS process used by this link task is running. If the problem persists, contact IBM support. |
Explanation | A request to commit a UOW was received from WebSphere Application Server for z/OS. When directing CICS to perform the commit operation, a return and reason code were received. The UOW will be backed out. |
Action | If the problem persists, contact IBM support. |
Explanation | A request to prepare a UOW was received from WebSphere Application Server for z/OS. When directing CICS to perform the prepare operation, a return and reason code were received. The link task will abend and the UOW will be backed out. |
Action | If the problem persists, contact IBM support. |
Explanation | New work for a UOW was received after the UOW was prepared. |
Action | If the problem persists, contact IBM support. |
Explanation | A request to prepare a UOW was received from WebSphere Application Server for z/OS. When directing CICS to perform the prepare, a return code indicated that a heuristic condition has occurred. The most likely cause of this error is that one of the resource managers involved in the UOW has committed or backed out its resources before receiving the prepare message. |
Action | If the problem persists, contact IBM support. |
Explanation | A request to prepare a UOW was received from WebSphere Application Server for z/OS. When directing CICS to perform the prepare, a return code indicated that CICS backed out the UOW. The most likely cause of this error is that one of the resource managers could not perform its updates, and backed out. |
Action | None. |
Explanation | A request to backout a UOW was received from WebSphere Application Server for z/OS. When directing CICS to perform the backout, a return code indicated that an error had occurred. |
Action | If the problem persists, contact IBM support. |
Explanation | A request to commit a UOW was received from WebSphere Application Server for z/OS. When directing CICS to perform the commit, a return code indicated that an error had occurred. The most likely cause of this error is that one of the resource managers involved in the UOW was not able to commit its updates. |
Action | None. |
Explanation | The link task was processing a UOW in a global transaction, but received a request that was not part of that global transaction. |
Action | If the problem persists, contact IBM support. |
Explanation | An error in PUT container for channel IBM-WAS-ADAPTER and the specified container. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Explanation | An error in GET container for channel IBM-WAS-ADAPTER and the specified container. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Explanation | The EXEC CICS GETMAIN for response buffer with specified size failed. |
Action | Ensure that the CICS EDSALIM is set high enough to support this message response. Check the BBOQ log that is running CICS job messages for the BBOOUT for the EIBRESP and EIBRESP2 values associated with this request. |
Explanation | The EXEC CICS FREEMAIN for the request buffer with specified size failed. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for the EIBRESP and EIBRESP2 values. If unable to determine the cause, contact IBM support. |
Explanation | The EXEC CICS FREEMAIN for the response buffer with specified size failed. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for the EIBRESP and EIBRESP2 values. If unable to determine the cause, contact IBM support. |
Explanation | The EXEC CICS FREEMAIN EIBRESP and EIBRESP2 values. |
Action | Refer to CICS documentation for help in identifying the cause of the FREEMAIN error. If you are unable to determine the cause, contact IBM support. |
Explanation | A request from WebSphere Application Server for z/OS was received to commit or backout a UOW. The UOW was not in the correct state to process a commit or backout request. |
Action | If the problem persists, contact IBM support. |
Explanation | The link task was processing requests for a UOW involved in a global transaction. A request was received which was participating in a different global transaction. This request cannot be processed by this link task. |
Action | If the problem persists, contact IBM support. |
Explanation | EXEC CICS GETMAIN EIBRESP and EIBRESP2 values. |
Action | Refer to the CICS documentation to help in identifying the cause of the GETMAIN error. If unable to determine the cause, contact IBM support. |
Explanation | The EXEC CICS GETMAIN for the request buffer with a specified size failed. |
Action | Ensure that the CICS EDSALIM is set high enough to support this message response. Check the BBOQ log for the EIBRESP and EIBRESP2 values associated with this request. |
Explanation | The EXEC CICS GETMAIN for an exception response buffer with a specified size failed. |
Action | Ensure that the CICS EDSALIM is set high enough to support this message response. Check the BBOQ log for the EIBRESP and EIBRESP2 values associated with this request. |
Explanation | An error occurred in GET container from channel IBM-WAS-ADAPTER and container IBM-WAS-EXCEPTN. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. Contact IBM support and report the problem. |
Explanation | An error occurred in GET container from channel IBM-WAS-ADAPTER and container IBM-WAS-EXCEPTN. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. Contact IBM support and report the problem. |
Explanation | The BBOA1SRX send exception response request returned with a non-zero return and reason code. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. Refer to the optimized local adapters API reference return codes for BBOA1SRX. Verify that WebSphere Application Server is available. |
Explanation | The BBOA1GET Get Data Request returned with a non-zero return and reason code. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. Refer to the optimized local adapters API reference return codes for BBOA1GET. Verify that WebSphere Application Server is available. |
Explanation | EXEC CICS HANDLE ABEND call. |
Action | Refer to CICS documentation to help in identifying the cause of the HANDLE ABEND error. If unable to determine the cause, contact IBM support. |
Explanation | EXEC CICS WRITEQ TS MAIN call. |
Action | Refer to CICS documentation to help in identifying the cause of the WRITEQ TS error. If unable to determine the cause, contact IBM support. |
Explanation | An error occurred during the EXEC CICS LINK to the target program. |
Action | The error is logged on the BBOQ and an exception response is created describing the error and returned to calling application. This response is passed back with a ResourceException. |
Explanation | Unable to write messages to the named TDQ. |
Action | Ensure that the subject TDQ is defined to CICS. Refer to BBOACSD definition sample file for BBOQ that is located in the /<smpe_root>/mso/OLA/samples directory. |
Explanation | The BBOA1CNR Release Connection Request returned with a non-zero return and reason code. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. Refer to the optimized local adapters API reference return codes for BBOA1CNR. Verify that WebSphere Application Server is available. |
Explanation | An exception occurred while the optimized local adapters link server was running. |
Action | No user action is required. Check the BBOQ log for further messages. |
Explanation | The BBOA1RCS receive request returned with a non-zero return and reason code. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. Refer to the optimized local adapters API reference return codes for BBOA1RCS. |
Explanation | Unable to write messages to the named TDQ. |
Action | Ensure that the subject TDQ is defined to CICS. Refer to BBOACSD definition sample file for BBOQ that is located in the /<smpe_root>/mso/OLA/samples directory. |
Explanation | This message is for informational purposes only. |
Action | None |
Explanation | This message is for informational purposes only with TRC=1. |
Action | None |
Explanation | This message is for informational purposes only with TRC=2 |
Action | None |
Explanation | The specified parameter was not passed and is set to the default. |
Action | Processing of the parameter continues. |
Explanation | The BBOC START_SRVR requested with SEC(Y) and REU(Y). |
Action | REU(Y) is not supported when SEC(Y) is specified. REU is set to N and processing continues. |
Explanation | Link invocation task abend handler intercepted an application abend. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. The abend code and application program involved with the abend are written there. An exception message is returned and thrown back to the calling |
Explanation | Unable to write messages to the named TDQ. |
Action | Ensure that the subject TDQ is defined to CICS. Refer to BBOACSD definition sample file for BBOQ that is located in the /<smpe_root>/mso/OLA/samples directory. |
Explanation | The BBOA1CNR Release Connection Request returned with a non-zero return and reason code. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. Refer to the optimized local adapters API reference return codes for BBOA1CNR. Verify that WebSphere Application Server is available. |
Explanation | Link invocation task abend handler intercepted an application abend and was unable to retrieve the required adapter information passed from the Link server BBO$ task. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. The abend code and application program involved with the abend are written there. In this case, the exception returned to the application will mo |
Explanation | BBOA1SRX send exception response request returned with non-zero return and reason code. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. Refer to the optimized local adapters API reference return codes for BBOA1SRX. Verify that WebSphere Application Server is still available. |
Explanation | Link invocation task abend handler intercepted an application abend and was unable to retrieve the required adapter information passed from the Link server BBO$ task. |
Action | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. The abend code and application program involved with the abend are written there. In this case, the exception returned to the application will mo |