[z/OS]

BBOA

BBOA8000I: <Level 0 Trace: message>
Explication This message is for informational purposes only.
Action None
BBOA8001I: <Level 1 Trace message>
Explication This message is for informational purposes only with TRC=1.
Action None
BBOA8002I: <Level 2 Trace message>
Explication This message is for informational purposes only with TRC=2.
Action None
BBOA8090E: An error occurred during TRUE enablement with reason code {1}.
Explication 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.
BBOA8091E: An error occurred during TRUE: extraction with reason code {1}.
Explication 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.
BBOA8092E: An error occurred during TRUE disablement with reason code {1}.
Explication 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.
BBOA8093E: The BBOATRUE is not active.
Explication The BBOC request cannot be processed since the BBOATRUE is not active.
Action Issue the BBOA START_TRUE and retry.
BBOA8094E: The daemon group name length is greater than 8, which exceeds the maximum size of a daemon group name.
Explication This is an incorrect parameter length.
Action Change the parameter length and retry.
BBOA8095E: The node name length is greater than 8, which exceeds the maximum size of a node name.
Explication This is an incorrect parameter length.
Action Change the parameter length and retry.
BBOA8096E: The server name length is greater than 8, which exceeds the maximum size of a server name.
Explication This is an incorrect parameter length.
Action Change the parameter length and retry.
BBOA8097E: An error occurred because the minimum connections value is greater than 9999, which exceeds the largest minimum connections value.
Explication The BBOC MNC parameter cannot exceed 9999.
Action Change the parameter value and retry.
BBOA8098E: An error occurred because the maximum connections value is greater than 9999, which exceeds the largest maximum connections value.
Explication The BBOC MXC parameter cannot exceed 9999.
Action Change the parameter value and retry.
BBOA8099E: An error occurred because of incorrect TXN parameter data.
Explication An error occurred with the BBOC TXN parameter. This parameter must be set to Y or N.
Action Change the parameter value and retry.
BBOA8100E: An error occurred during Unregister with return code {1} and reason code {2}.
Explication An error occurred during BBOC UNREGISTER.
Action Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages.
BBOA8101E: An error occurred because of incorrect SEC parameter data.
Explication An error occurred with the BBOC SEC parameter. This parameter must be set to Y or N.
Action Change the parameter value and retry.
BBOA8102E: An error occurred when writing to transient data queue (TDQ) {1} eibresp {2} eibresp2 {2}
Explication 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.
BBOA8103E: An error occurred during register with return code {1} and reason code {2}.
Explication This is a BBOC REGISTER error.
Action Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages.
BBOA8104E: An error occurred during default register with return code {1} and reason code {2}.
Explication 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.
BBOA8105E: The register name length is greater than 12, which exceeds the maximum size of a register name.
Explication This is an incorrect parameter length.
Action Change the parameter value and retry.
BBOA8106E: Service name length is greater than 8, which exceeds the maximum size of a service name.
Explication This is an incorrect parameter length.
Action Change the parameter value and retry.
BBOA8107E: A Start Server REGISTER error occurred.
Explication 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.
BBOA8108E: The server task transaction length is greater than 4, which exceeds the maximum size of a server task transaction length.
Explication This is an incorrect parameter length.
Action Change the parameter value and retry.
BBOA8109E: The link task transaction length is greater than 4, which exceeds the maximum size of a link task transaction length.
Explication This is an incorrect parameter length.
Action Change the parameter value and retry.
BBOA8110E: An error with return code {1} and reason code {2} occurred when the server was started.
Explication 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.
BBOA8111E: A Stop server UNREGISTER error occurred.
Explication This is a BBOC UNREGISTER error.
Action Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages.
BBOA8112E: The transient data queue (TDQ) parameter length is greater than 4, which exceeds the maximum size of a transient data queue (TDQ) length.
Explication This is an incorrect parameter length.
Action Change the parameter value and retry.
BBOA8113E: The Trace parameter length is greater than 1, which exceeds the maximum size of a Trace parameter length.
Explication This is an incorrect parameter length.
Action Change the parameter value and retry.
BBOA8114E: The Trace parameter is not correct.
Explication The Trace parameter must be TRC=|1|2
Action Change the parameter and retry.
BBOA8116E: The Register name length is greater than 12, which exceeds the maximum size of a Register name length.
Explication This is an incorrect parameter length.
Action Change the parameter value and retry.
BBOA8120E: An incorrect request occurred and is ending.
Explication This request was an unrecognized BBOC request.
Action You entered an unrecognized BBOC command. Change the command and retry.
BBOA8122E: An Enable exit error occurred.
Explication An error occurred during BBOC START_TRUE.
Action Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages.
BBOA8123E: A Disable exit error occurred.
Explication An error occurred during BBOC STOP_TRUE.
Action Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages.
BBOA8124E: A Start Server error occurred.
Explication An error occurred during BBOC START_SRVR
Action Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages.
BBOA8125E: A Register error occurred.
Explication An error occurred during BBOC REGISTER.
Action Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages.
BBOA8126E: An Unregister error occurred.
Explication An error occurred during BBOC UNREGISTER.
Action Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages.
BBOA8127E: An error occurred because of incorrect XTR parameter data.
Explication An error occurred with the BBOC XTR parameter. This parameter must be Y or N.
Action Change the parameter and retry.
BBOA8128E: An error occurred with the CICS START transaction {1} EIBRESP: {2} EIBRESP2: {3}
Explication 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.
BBOA8130E: An error occurred when the required parameter {1} was not passed.
Explication The specified parameter must be present and is not.
Action Specify the correct parameter and retry.
BBOA8131E: The Reuse length is greater than 4, which exceeds the maximum size of a Reuse length.
Explication This is an incorrect parameter length.
Action Change the parameter value and retry.
BBOA8132E: An error was encountered adding new link server {1}
Explication 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.
BBOA8133E: The Reuse count length is greater than 8, which exceeds the maximum size of this parameter.
Explication An improper value was passed for the REUC parameter.
Action Correct this and make it a numeric value with no more than 8 digits.
BBOA8134E: The Reuse count > 2GB and exceeds the maximum value of this parameter.
Explication An improper value was passed for the REUC parameter.
Action This must be a numeric value no larger than 2G.
BBOA8135E: The Reuse timeout length is greater than 8, which exceeds the maximum size of this parameter.
Explication An improper value was passed for the REUT parameter.
Action Correct this and make it a numeric value with no more than 8 digits.
BBOA8136E: The Reuse time > 2GB and exceeds the maximum value of this parameter.
Explication An improper value was passed for the REUT parameter.
Action This must be a numeric value no larger than 2G.
BBOA8137E: An error occurred when querying the size of transient data queue (TDQ) {1} eibresp {2} eibresp2 {3}
Explication The link server attempted to issue the EXEC CICS INQUIRE TDQUEUE() API to determine the default record size of the BBOQ queue, but received the response codes indicated in the message. The queue name is also indicated in the message.
Action Verify that the named queue exists and that the user ID which started the link server has the authority to invoke the EXEC CICS INQUIRE TDQUEUE() API. Messages will continue to be written to this queue using the default queue record length. If your queue record length is larger than the default, some messages may be truncated at the default length.
BBOA8140W: Start server completed with warnings.
Explication The start server command completed with warnings.
Action Look for messages in the CICS log file indicating conflicting parameters in the start server command.
BBOA8201E: Unable to locate requested Registration Name : {1}
Explication An error occurred while searching for named Registration.
Action Ensure there is an external address space currently executing with this registration name.
BBOA8500I: <Level 0 Trace message>
Explication This message is for informational purposes only.
Action None
BBOA8501I: <Level 1 Trace message>
Explication This message is for informational purposes only with TRC=1.
Action None
BBOA8502I: <Level 2 Trace message>
Explication This message is for informational purposes only with TRC=2.
Action None
BBOA8510I: The server is terminating because a request was received to stop the adapters server.
Explication When you process a BBOC STOP_SRVR, the BBO$ transaction terminates.
Action None
BBOA8511I: The connection handle was made invalid or a STOP request was received.
Explication When you process a BBOC STOP_SRVR, the BBO$ transaction and all related BBO# transactions terminate.
Action None
BBOA8587E: An error occurred when querying the size of transient data queue (TDQ) {1} eibresp {2} eibresp2 {3}
Explication The link server attempted to issue the EXEC CICS INQUIRE TDQUEUE() API to determine the default record size of the BBOQ queue, but received the response codes indicated in the message. The queue name is also indicated in the message.
Action Verify that the named queue exists and that the user ID which started the link server has the authority to invoke the EXEC CICS INQUIRE TDQUEUE() API. Messages will continue to be written to this queue using the default queue record length. If your queue record length is larger than the default, some messages may be truncated at the default length.
BBOA8588E: Link server {1} lost connectivity to {2}
Explication 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.
BBOA8589E: A Receive Request error occurred with return code {1} and reason code {2}
Explication 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.
BBOA8590E: A Receive Request error occurred with return code {1} reason code {2}. The session is terminating.
Explication 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.
BBOA8591E: The link server has stopped because of errors with Regname: <register_name>.
Explication 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.
BBOA8592E: A Get Data Request error occurred with return code {1} and reason code {2}.
Explication 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.
BBOA8593E: A Get Context Request error occurred with a return code {1} and reason code {2}.
Explication 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.
BBOA8594E: An EXEC CICS GET NOD error occurred. eibresp: {1} eibresp2: {1}
Explication 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.
BBOA8595E: An EXEC CICS GET error occurred. eibresp: {1} eibresp2: {1}
Explication 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.
BBOA8596E: A Send Exception Response error occurred with return code {1} and reason code {2}.
Explication 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.
BBOA8598E: A Release Connection error occurred with return code {1} and reason code {2}.
Explication 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.
BBOA8600E: An error occurred with CICS START TRANSID: {1} RESP: {2} RESP2: {3}.
Explication 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.
BBOA8601E: A link transaction ID of {1} caused an error to occur with the link server set to REU=Y.
Explication 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.
BBOA8700I: <Level 0 Trace message>
Explication This message is for informational purposes only.
Action None
BBOA8701I: <Level 1 Trace message>
Explication This message is for informational purposes only with TRC=1.
Action None
BBOA8702I: <Level 2 Trace message>
Explication This message is for informational purposes only with TRC=2.
Action None
BBOA8710I: The server is terminating because a request was received to stop the adapters server. The link count is {1}.
Explication When you process a BBOC STOP_SRVR, the BBO# transaction terminates.
Action None
BBOA8711I: The connection handle was made invalid or a STOP request was received.
Explication When you process a BBOC STOP_SRVR, the BBO# transaction terminates.
Action None
BBOA8755E: An error occurred when querying the size of transient data queue (TDQ) {1} eibresp {2} eibresp2 {3}
Explication The link server attempted to issue the EXEC CICS INQUIRE TDQUEUE() API to determine the default record size of the BBOQ queue, but received the response codes indicated in the message. The queue name is also indicated in the message.
Action Verify that the named queue exists and that the user ID which started the link server has the authority to invoke the EXEC CICS INQUIRE TDQUEUE() API. Messages will continue to be written to this queue using the default queue record length. If your queue record length is larger than the default, some messages may be truncated at the default length.
BBOA8756E: CICS version {1} does not support transaction propagation over OLA
Explication 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.
BBOA8757E: Could not parse CICS TS version {1}
Explication 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.
BBOA8758E: An error occurred invoking EC INQUIRE SYSTEM CICSTSLEVEL: {1}
Explication 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.
BBOA8759E: Error starting UOWLINK iteration for UOW {1} ({2})
Explication 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.
BBOA8760E: Did not find UOWLINK in UOW {1} to delete
Explication 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
BBOA8761E: Error deleting UOWLINK {1} in UOW {2} ({3})
Explication 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.
BBOA8762E: Failure deleting UOWLINK during iteration ({1})
Explication 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.
BBOA8763E: Error finding Recovery UOW in UOWLIST ({1})
Explication 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.
BBOA8764E: Recovery UOW is in the wrong state ({1}) or wrong waitstate ({2}) for resolution
Explication 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.
BBOA8765E: Cannot {1} recovery UOW due to EC SET UOW error ({2})
Explication 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.
BBOA8766E: Cannot return {1} XIDs to WebSphere due to EC GETMAIN error ({2})
Explication 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.
BBOA8767E: Recovery of UOWs ended prematurely due to EC INQUIRE UOWLINK NEXT error ({1})
Explication 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.
BBOA8768E: Cannot recover UOW {1} due to EC INQUIRE UOW error ({2})
Explication 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.
BBOA8769E: Cannot recover UOW {1} due to EC GETMAIN error ({2})
Explication 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.
BBOA8770E: Link parms received are version {1}, expecting version {2}
Explication 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.
BBOA8771E: Transaction TID is too long to import ({1})
Explication 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.
BBOA8772E: The link task is exiting due to a COMM failure. The link count is {1}
Explication 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.
BBOA8773E: Commit failed RC = {1} RSN = {2}
Explication 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.
BBOA8774E: Prepare failed RC = {1} RSN = {2}
Explication 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.
BBOA8775E: Received new method in a prepared transaction
Explication New work for a UOW was received after the UOW was prepared.
Action If the problem persists, contact IBM support.
BBOA8776E: Prepare voted heuristic
Explication 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.
BBOA8777E: Prepare voted backout
Explication 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.
BBOA8778E: Backout failed RC = {1} RSN = {2}
Explication 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.
BBOA8779E: CommitOnePhase failed RC = {1} RSN = {2}
Explication 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.
BBOA8780E: Link server task must process methods for existing TID
Explication 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.
BBOA8781E: An EXEC CICS PUT CONTAINER {1} error occurred with eibresp: {2} eibresp2: {3}.
Explication 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.
BBOA8782E: An EXEC CICS GET CONTAINER {1} NODATA error occurred with eibresp: {2} eibresp2: {3}.
Explication 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.
BBOA8783E: An error occurred when allocating the response buffer size: {1}.
Explication 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.
BBOA8784E: An error occurred while freeing the request buffer size: {1}.
Explication 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.
BBOA8785E: An error occurred while freeing the response buffer at address: {1} with size: {2}.
Explication 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.
BBOA8786E: An EXEC CICS FREEMAIN RESP error occurred : {1} RESP2: {2}.
Explication 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.
BBOA8787E: Transaction state incorrect for {1}
Explication 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.
BBOA8788E: TID does not match existing transaction
Explication 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.
BBOA8790E: An EXEC CICS GETMAIN RESP error occurred: {1} RESP2: {2}.
Explication 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.
BBOA8791E: An error occurred allocating the request buffer size: {1}
Explication 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.
BBOA8792E: An EXEC CICS GETMAIN RESP error occurred: {1} RESP2: {2}
Explication 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.
BBOA8794E: An EXEC CICS GET NOD error occurred. eibresp: {1} eibresp2: {2}.
Explication 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.
BBOA8795E: An EXEC CICS GET error occurred. eibresp: {1} eibresp2: {2}.
Explication 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.
BBOA8796E: A Send Exception Response error occurred with return code {1} and reason code {2}.
Explication 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.
BBOA8797E: A Get Data Request error occurred with return code {1} and reason code {2}.
Explication 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.
BBOA8798E: An EXEC CICS Handle Abend error occurred with eibresp: {1} eibresp2: {2}.
Explication 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.
BBOA8799E: A WRITEQ TSQ {1} error occurred with eibresp: {2} eibresp2: {3}.
Explication 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.
BBOA8800E: An EXEC CICS LINK PROGRAM {1} error occurred. eibresp: {2} eibresp2: {3}.
Explication 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.
BBOA8801E: An error occurred when writing transient data queue (TDQ) named {1} to eibresp {2} eibresp2 {3}.
Explication 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.
BBOA8802E: A Release Connection error occurred with return code {1} and reason code {2}.
Explication 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.
BBOA8803E: The link server stopped because of errors. Regname: {1}
Explication 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.
BBOA8804E: A Receive Request error occurred with return code {1} and reason code {2}. The link count is {3}.
Explication 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.
BBOA8805E: An error occurred when writing to transient data queue (TDQ) {1} eibresp {2} eibresp2 {3}
Explication 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.
BBOA8900I: <Level 0 Trace message>
Explication This message is for informational purposes only.
Action None
BBOA8901I: <Level 1 Trace message>
Explication This message is for informational purposes only with TRC=1.
Action None
BBOA8902I: <Level 2 Trace message>
Explication This message is for informational purposes only with TRC=2
Action None
BBOA8941W: The parameter {1} was not passed and is set to the default {2}.
Explication The specified parameter was not passed and is set to the default.
Action Processing of the parameter continues.
BBOA8942W: The Reuse request is disabled due to SEC(Y).
Explication 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.
BBOA8950I: Captured abend code: {1} in program {2}
Explication 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
BBOA8991E: An error occurred when writing transient data queue (TDQ) named {1} to eibresp {2} eibresp2 {3}.
Explication 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.
BBOA8994E: A Release Connection error occurred with return code {1} and reason code {2}.
Explication 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.
BBOA8995E: Error in EXEC CICS RETRIEVE eibresp: {1} eibresp2: {2}
Explication 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
BBOA8996E: A Send Exception Response error occurred with return code {1} and reason code {2}.
Explication 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.
BBOA8997E: EXEC CICS READQ TS error {1} eibresp: {2} eibresp2: {3}
Explication 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
Rubrique de référence    

Conditions d'utilisation | Commentaires

Dernière mise à jour : Jan 2, 2018 8:48:33 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ejs.resources.ola_Messages_plx.html

© Copyright IBM Corporation 2006, 2011. All Rights Reserved.
Technologie Eclipse. (http://www.eclipse.org)