Объяснение | This message is for informational purposes only. |
Действие | None |
Объяснение | This message is for informational purposes only with TRC=1. |
Действие | None |
Объяснение | This message is for informational purposes only with TRC=2. |
Действие | None |
Объяснение | The EXEC CICS START TRUE for BBOATRUE failed. |
Действие | Check BBOQ log for further messages.Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Объяснение | The EXEC CICS EXTRACT TRUE for BBOATRUE failed. |
Действие | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Объяснение | The EXEC CICS DISABLE TRUE for BBOATRUE failed. |
Действие | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Объяснение | The BBOC request cannot be processed since the BBOATRUE is not active. |
Действие | Issue the BBOA START_TRUE and retry. |
Объяснение | This is an incorrect parameter length. |
Действие | Change the parameter length and retry. |
Объяснение | This is an incorrect parameter length. |
Действие | Change the parameter length and retry. |
Объяснение | This is an incorrect parameter length. |
Действие | Change the parameter length and retry. |
Объяснение | The BBOC MNC parameter cannot exceed 9999. |
Действие | Change the parameter value and retry. |
Объяснение | The BBOC MXC parameter cannot exceed 9999. |
Действие | Change the parameter value and retry. |
Объяснение | An error occurred with the BBOC TXN parameter. This parameter must be set to Y or N. |
Действие | Change the parameter value and retry. |
Объяснение | An error occurred during BBOC UNREGISTER. |
Действие | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Объяснение | An error occurred with the BBOC SEC parameter. This parameter must be set to Y or N. |
Действие | Change the parameter value and retry. |
Объяснение | Unable to write messages to the named TDQ. |
Действие | 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. |
Объяснение | This is a BBOC REGISTER error. |
Действие | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Объяснение | The default link server registration could not complete. |
Действие | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. Verify that WebSphere Application Server is available. |
Объяснение | This is an incorrect parameter length. |
Действие | Change the parameter value and retry. |
Объяснение | This is an incorrect parameter length. |
Действие | Change the parameter value and retry. |
Объяснение | The BBOC START_SRVR REGISTER API call failed. |
Действие | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Объяснение | This is an incorrect parameter length. |
Действие | Change the parameter value and retry. |
Объяснение | This is an incorrect parameter length. |
Действие | Change the parameter value and retry. |
Объяснение | An error occurred during a BBOC START_SRVR request. |
Действие | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Объяснение | This is a BBOC UNREGISTER error. |
Действие | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Объяснение | This is an incorrect parameter length. |
Действие | Change the parameter value and retry. |
Объяснение | This is an incorrect parameter length. |
Действие | Change the parameter value and retry. |
Объяснение | The Trace parameter must be TRC=|1|2 |
Действие | Change the parameter and retry. |
Объяснение | This is an incorrect parameter length. |
Действие | Change the parameter value and retry. |
Объяснение | This request was an unrecognized BBOC request. |
Действие | You entered an unrecognized BBOC command. Change the command and retry. |
Объяснение | An error occurred during BBOC START_TRUE. |
Действие | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Объяснение | An error occurred during BBOC STOP_TRUE. |
Действие | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Объяснение | An error occurred during BBOC START_SRVR |
Действие | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Объяснение | An error occurred during BBOC REGISTER. |
Действие | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Объяснение | An error occurred during BBOC UNREGISTER. |
Действие | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Объяснение | An error occurred with the BBOC XTR parameter. This parameter must be Y or N. |
Действие | Change the parameter and retry. |
Объяснение | Unable to issue the EXEC CICS START for the specified link server transaction. |
Действие | Refer to the CICS reference material for EIBRESP and EIBRESP2 meanings for EXEC CICS START TRANSACTION for more information. |
Объяснение | The specified parameter must be present and is not. |
Действие | Specify the correct parameter and retry. |
Объяснение | This is an incorrect parameter length. |
Действие | Change the parameter value and retry. |
Объяснение | A new link server entry could not be created by this control task. |
Действие | Try to create the link server again. If the problem persists, contact IBM support. |
Объяснение | An improper value was passed for the REUC parameter. |
Действие | Correct this and make it a numeric value with no more than 8 digits. |
Объяснение | An improper value was passed for the REUC parameter. |
Действие | This must be a numeric value no larger than 2G. |
Объяснение | An improper value was passed for the REUT parameter. |
Действие | Correct this and make it a numeric value with no more than 8 digits. |
Объяснение | An improper value was passed for the REUT parameter. |
Действие | This must be a numeric value no larger than 2G. |
Объяснение | The start server command completed with warnings. |
Действие | Look for messages in the CICS log file indicating conflicting parameters in the start server command. |
Объяснение | This message is for informational purposes only. |
Действие | None |
Объяснение | This message is for informational purposes only with TRC=1. |
Действие | None |
Объяснение | This message is for informational purposes only with TRC=2. |
Действие | None |
Объяснение | When you process a BBOC STOP_SRVR, the BBO$ transaction terminates. |
Действие | None |
Объяснение | When you process a BBOC STOP_SRVR, the BBO$ transaction and all related BBO# transactions terminate. |
Действие | None |
Объяснение | Communication with the WebSphere Application Server for z/OS server instance indicated in the message has been lost. |
Действие | Ensure that the WebSphere Application Server for z/OS server instance is running. If the problem persists, contact IBM support. |
Объяснение | 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. |
Действие | 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. |
Объяснение | The BBOA1RCA receive request returned with non-zero return and reason code. |
Действие | 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. |
Объяснение | An exception occurred while the optimized local adapters link server was running. |
Действие | None Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Объяснение | The BBOA1GET get data request returned with a non-zero return and reason code. |
Действие | 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. |
Объяснение | Unable to retrieve message context data. |
Действие | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. Verify that WebSphere Application Server is available. |
Объяснение | An error occurred in GET from channel IBM-WAS-ADAPTER and container IBM-WAS-EXCEPTN. |
Действие | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. Contact IBM support and report the problem. |
Объяснение | An error occurred in GET from channel IBM-WAS-ADAPTER and container IBM-WAS-EXCEPTN. |
Действие | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. Contact IBM support and report the problem. |
Объяснение | BBOA1SRX send exception response request returned with non-zero return and reason code. |
Действие | 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. |
Объяснение | The BBOA1CNR release connection request returned with a non-zero return and reason code. |
Действие | 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. |
Объяснение | Unable to issue EXEC CICS START for specified link transaction identifier. |
Действие | Refer to the CICS reference material for EIBRESP and EIBRESP2 meanings for EXEC CICS START TRANSACTION for more information. |
Объяснение | Propagation of a link transaction ID into CICS from WebSphere Application Server is not supported while running the link server with REU=Y. |
Действие | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Объяснение | This message is for informational purposes only. |
Действие | None |
Объяснение | This message is for informational purposes only with TRC=1. |
Действие | None |
Объяснение | This message is for informational purposes only with TRC=2. |
Действие | None |
Объяснение | When you process a BBOC STOP_SRVR, the BBO# transaction terminates. |
Действие | None |
Объяснение | When you process a BBOC STOP_SRVR, the BBO# transaction terminates. |
Действие | None |
Объяснение | The link server received a request that included a transaction context. This version of CICS does not support transaction propagation over OLA. |
Действие | 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. |
Объяснение | The version of CICS Transaction Server for z/OS could not be determined by the link server. |
Действие | Verify that you are using a supported version of CICS Transaction Server for z/OS. If the problem persists, contact IBM support. |
Объяснение | The link server attempted to invoke the EXEC CICS INQURE SYSTEM CICSTSLEVEL API, and received the error code indicated in the message. |
Действие | 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. |
Объяснение | The link server attempted to invoke the EXEC CICS INQUIRE UOWLINK START command but received the error code indicated in the message. |
Действие | Contact IBM support. |
Объяснение | 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. |
Действие | None |
Объяснение | 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. |
Действие | 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. |
Объяснение | 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. |
Действие | Contact IBM support. |
Объяснение | 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. |
Действие | The operation will be retried. If the problem persists, contact IBM support. |
Объяснение | An attempt was made to resolve an in-doubt UOW which was in the wrong state. |
Действие | The operation will be retried. If the problem persists, contact IBM support. |
Объяснение | 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. |
Действие | 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. |
Объяснение | 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. |
Действие | 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. |
Объяснение | 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. |
Действие | The operation will be retried. If the problem persists, contact IBM support. |
Объяснение | 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. |
Действие | The operation will be retried. If the problem persists, contact IBM support. |
Объяснение | 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. |
Действие | 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. |
Объяснение | The version of the link server and link tasks are different. |
Действие | 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. |
Объяснение | 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. |
Действие | Contact IBM support. |
Объяснение | A communication error occurred while communicating with WebSphere Application Server for z/OS. The link server task will end. |
Действие | Ensure that the WebSphere Application Server for z/OS process used by this link task is running. If the problem persists, contact IBM support. |
Объяснение | 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. |
Действие | If the problem persists, contact IBM support. |
Объяснение | 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. |
Действие | If the problem persists, contact IBM support. |
Объяснение | New work for a UOW was received after the UOW was prepared. |
Действие | If the problem persists, contact IBM support. |
Объяснение | 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. |
Действие | If the problem persists, contact IBM support. |
Объяснение | 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. |
Действие | None. |
Объяснение | 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. |
Действие | If the problem persists, contact IBM support. |
Объяснение | 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. |
Действие | None. |
Объяснение | The link task was processing a UOW in a global transaction, but received a request that was not part of that global transaction. |
Действие | If the problem persists, contact IBM support. |
Объяснение | An error in PUT container for channel IBM-WAS-ADAPTER and the specified container. |
Действие | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Объяснение | An error in GET container for channel IBM-WAS-ADAPTER and the specified container. |
Действие | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. |
Объяснение | The EXEC CICS GETMAIN for response buffer with specified size failed. |
Действие | 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. |
Объяснение | The EXEC CICS FREEMAIN for the request buffer with specified size failed. |
Действие | 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. |
Объяснение | The EXEC CICS FREEMAIN for the response buffer with specified size failed. |
Действие | 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. |
Объяснение | The EXEC CICS FREEMAIN EIBRESP and EIBRESP2 values. |
Действие | 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. |
Объяснение | 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. |
Действие | If the problem persists, contact IBM support. |
Объяснение | 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. |
Действие | If the problem persists, contact IBM support. |
Объяснение | EXEC CICS GETMAIN EIBRESP and EIBRESP2 values. |
Действие | Refer to the CICS documentation to help in identifying the cause of the GETMAIN error. If unable to determine the cause, contact IBM support. |
Объяснение | The EXEC CICS GETMAIN for the request buffer with a specified size failed. |
Действие | 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. |
Объяснение | The EXEC CICS GETMAIN for an exception response buffer with a specified size failed. |
Действие | 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. |
Объяснение | An error occurred in GET container from channel IBM-WAS-ADAPTER and container IBM-WAS-EXCEPTN. |
Действие | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. Contact IBM support and report the problem. |
Объяснение | An error occurred in GET container from channel IBM-WAS-ADAPTER and container IBM-WAS-EXCEPTN. |
Действие | Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. Contact IBM support and report the problem. |
Объяснение | The BBOA1SRX send exception response request returned with a non-zero return and reason code. |
Действие | 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. |
Объяснение | The BBOA1GET Get Data Request returned with a non-zero return and reason code. |
Действие | 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. |
Объяснение | EXEC CICS HANDLE ABEND call. |
Действие | Refer to CICS documentation to help in identifying the cause of the HANDLE ABEND error. If unable to determine the cause, contact IBM support. |
Объяснение | EXEC CICS WRITEQ TS MAIN call. |
Действие | Refer to CICS documentation to help in identifying the cause of the WRITEQ TS error. If unable to determine the cause, contact IBM support. |
Объяснение | An error occurred during the EXEC CICS LINK to the target program. |
Действие | 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. |
Объяснение | Unable to write messages to the named TDQ. |
Действие | 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. |
Объяснение | The BBOA1CNR Release Connection Request returned with a non-zero return and reason code. |
Действие | 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. |
Объяснение | An exception occurred while the optimized local adapters link server was running. |
Действие | No user action is required. Check the BBOQ log for further messages. |
Объяснение | The BBOA1RCS receive request returned with a non-zero return and reason code. |
Действие | 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. |
Объяснение | Unable to write messages to the named TDQ. |
Действие | 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. |
Объяснение | This message is for informational purposes only. |
Действие | None |
Объяснение | This message is for informational purposes only with TRC=1. |
Действие | None |
Объяснение | This message is for informational purposes only with TRC=2 |
Действие | None |
Объяснение | The specified parameter was not passed and is set to the default. |
Действие | Processing of the parameter continues. |
Объяснение | The BBOC START_SRVR requested with SEC(Y) and REU(Y). |
Действие | REU(Y) is not supported when SEC(Y) is specified. REU is set to N and processing continues. |
Объяснение | Link invocation task abend handler intercepted an application abend. |
Действие | 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 |
Объяснение | Unable to write messages to the named TDQ. |
Действие | 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. |
Объяснение | The BBOA1CNR Release Connection Request returned with a non-zero return and reason code. |
Действие | 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. |
Объяснение | 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. |
Действие | 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 |
Объяснение | BBOA1SRX send exception response request returned with non-zero return and reason code. |
Действие | 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. |
Объяснение | 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. |
Действие | 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 |