WebSphere Application Server messages
             Operating Systems: z/OS


BBOA

BBOA8000I: <Level 0 Trace: message>
Explanation This message is for informational purposes only.
Action None
BBOA8001I: <Level 1 Trace message>
Explanation This message is for informational purposes only with TRC=1.
Action None
BBOA8002I: <Level 2 Trace message>
Explanation This message is for informational purposes only with TRC=2.
Action None
BBOA8090E: An error occurred during TRUE enablement with reason code {1}.
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.
BBOA8091E: An error occurred during TRUE: extraction with reason code {1}.
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.
BBOA8092E: An error occurred during TRUE disablement with reason code {1}.
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.
BBOA8093E: The BBOATRUE is not active.
Explanation 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.
Explanation 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.
Explanation 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.
Explanation 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.
Explanation 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.
Explanation The BBOC MXC parameter cannot exceed 9999.
Action Change the parameter value and retry.
BBOA8099E: An error occurred because of incorrect TXN parameter data.
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.
BBOA8100E: An error occurred during Unregister with return code {1} and reason code {2}.
Explanation 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.
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.
BBOA8102E: An error occurred when writing to transient data queue (TDQ) {1} eibresp {2} eibresp2 {2}
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.
BBOA8103E: An error occurred during register with return code {1} and reason code {2}.
Explanation 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}.
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.
BBOA8105E: The register name length is greater than 12, which exceeds the maximum size of a register name.
Explanation 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.
Explanation This is an incorrect parameter length.
Action Change the parameter value and retry.
BBOA8107E: A Start Server REGISTER error occurred.
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.
BBOA8108E: The server task transaction length is greater than 4, which exceeds the maximum size of a server task transaction length.
Explanation 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.
Explanation 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.
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.
BBOA8111E: A Stop server UNREGISTER error occurred.
Explanation 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.
Explanation 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.
Explanation This is an incorrect parameter length.
Action Change the parameter value and retry.
BBOA8114E: The Trace parameter is not correct.
Explanation 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.
Explanation This is an incorrect parameter length.
Action Change the parameter value and retry.
BBOA8120E: An incorrect request occurred and is ending.
Explanation 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.
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.
BBOA8123E: A Disable exit error occurred.
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.
BBOA8124E: A Start Server error occurred.
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.
BBOA8125E: A Register error occurred.
Explanation 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.
Explanation 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.
Explanation 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}
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.
BBOA8130E: An error occurred when the required parameter {1} was not passed.
Explanation 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.
Explanation This is an incorrect parameter length.
Action Change the parameter value and retry.
BBOA8500I: <Level 0 Trace message>
Explanation This message is for informational purposes only.
Action None
BBOA8501I: <Level 1 Trace message>
Explanation This message is for informational purposes only with TRC=1.
Action None
BBOA8502I: <Level 2 Trace message>
Explanation 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.
Explanation 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.
Explanation When you process a BBOC STOP_SRVR, the BBO$ transaction and all related BBO# transactions terminate.
Action None
BBOA8590E: A Receive Request error occurred with return code {1} reason code {2}. The session is terminating.
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.
BBOA8591E: The link server has stopped because of errors with Regname: <register_name>.
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.
BBOA8592E: A Get Data Request error occurred with return code {1} and reason code {2}.
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.
BBOA8593E: A Get Context Request error occurred with a return code {1} and reason code {2}.
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.
BBOA8594E: An EXEC CICS GET NOD error occurred. eibresp: {1} eibresp2: {1}
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.
BBOA8595E: An EXEC CICS GET error occurred. eibresp: {1} eibresp2: {1}
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.
BBOA8596E: A Send Exception Response error occurred with return code {1} and reason code {2}.
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.
BBOA8598E: A Release Connection error occurred with return code {1} and reason code {2}.
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.
BBOA8600E: An error occurred with CICS START TRANSID: {1} RESP: {2} RESP2: {3}.
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.
BBOA8601E: A link transaction ID of {1} caused an error to occur with the link server set to REU=Y.
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.
BBOA8700I: <Level 0 Trace message>
Explanation This message is for informational purposes only.
Action None
BBOA8701I: <Level 1 Trace message>
Explanation This message is for informational purposes only with TRC=1.
Action None
BBOA8702I: <Level 2 Trace message>
Explanation 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}.
Explanation 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.
Explanation When you process a BBOC STOP_SRVR, the BBO# transaction terminates.
Action None
BBOA8781E: An EXEC CICS PUT CONTAINER {1} error occurred with eibresp: {2} eibresp2: {3}.
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.
BBOA8782E: An EXEC CICS GET CONTAINER {1} NODATA error occurred with eibresp: {2} eibresp2: {3}.
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.
BBOA8783E: An error occurred when allocating the response buffer size: {1}.
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.
BBOA8784E: An error occurred while freeing the request buffer size: {1}.
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.
BBOA8785E: An error occurred while freeing the response buffer at address: {1} with size: {2}.
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.
BBOA8786E: An EXEC CICS FREEMAIN RESP error occurred : {1} RESP2: {2}.
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.
BBOA8790E: An EXEC CICS GETMAIN RESP error occurred: {1} RESP2: {2}.
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.
BBOA8791E: An error occurred allocating the request buffer size: {1}
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.
BBOA8792E: An EXEC CICS GETMAIN RESP error occurred: {1} RESP2: {2}
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.
BBOA8794E: An EXEC CICS GET NOD error occurred. eibresp: {1} eibresp2: {2}.
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.
BBOA8795E: An EXEC CICS GET error occurred. eibresp: {1} eibresp2: {2}.
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.
BBOA8796E: A Send Exception Response error occurred with return code {1} and reason code {2}.
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.
BBOA8797E: A Get Data Request error occurred with return code {1} and reason code {2}.
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.
BBOA8798E: An EXEC CICS Handle Abend error occurred with eibresp: {1} eibresp2: {2}.
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.
BBOA8799E: A WRITEQ TSQ {1} error occurred with eibresp: {2} eibresp2: {3}.
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.
BBOA8800E: An EXEC CICS LINK PROGRAM {1} error occurred. eibresp: {2} eibresp2: {3}.
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.
BBOA8801E: An error occurred when writing transient data queue (TDQ) named {1} to eibresp {2} eibresp2 {3}.
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.
BBOA8802E: A Release Connection error occurred with return code {1} and reason code {2}.
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.
BBOA8803E: The link server stopped because of errors. Regname: {1}
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.
BBOA8804E: A Receive Request error occurred with return code {1} and reason code {2}. The link count is {3}.
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.
BBOA8805E: An error occurred when writing to transient data queue (TDQ) {1} eibresp {2} eibresp2 {3}
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.
BBOA8900I: <Level 0 Trace message>
Explanation This message is for informational purposes only.
Action None
BBOA8901I: <Level 1 Trace message>
Explanation This message is for informational purposes only with TRC=1.
Action None
BBOA8902I: <Level 2 Trace message>
Explanation 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}.
Explanation 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).
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.
BBOA8950I: Captured abend code: {1} in program {2}
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
BBOA8991E: An error occurred when writing transient data queue (TDQ) named {1} to eibresp {2} eibresp2 {3}.
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.
BBOA8994E: A Release Connection error occurred with return code {1} and reason code {2}.
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.
BBOA8995E: Error in EXEC CICS RETRIEVE eibresp: {1} eibresp2: {2}
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
BBOA8996E: A Send Exception Response error occurred with return code {1} and reason code {2}.
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.
BBOA8997E: EXEC CICS READQ TS error {1} eibresp: {2} eibresp2: {3}
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
Reference topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 8:32:57 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ejs.resources.ola_Messages_plx.html

© Copyright IBM Corporation 2006, 2010. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)