BBOA

BBOA0000I: TYPE: {0} JOBNAME: {1} NAME: {2}

Explanation

First line response to a detailed registration listing command.

Action

None

BBOA0001I: JOBNUM: {0} ACTIVE: {1} ACTIVE-CONNECTIONS: {2}

Explanation

Second line response to a detailed registration listing command.

Action

None

BBOA0002I: MIN-CONN: {0} MAX-CONN: {1} STATE: {2} TRACELEVEL: {3}

Explanation

Third line response to a detailed registration listing command.

Action

None

BBOA0003I: Name Jobname SWT TL Min Max Act State

Explanation

Header response for a tabulated registration listing command.

Action

None

BBOA0004I: {0} {1} {2} {3} {4} {5} {6} {7}

Explanation

RGE row response for the tabulated command: MODIFY,DISPLAY,ADAPTER,RGE,*

Action

None

BBOA0005I: STATUS: VER:{0} MAX-CONN:{1} DAEMON-GRP-NAME:{2}

Explanation

Response to the command: MODIFY DISPLAY,ADAPTER,STATUS

Action

None

BBOA0006I: SHOWING REGISTRATIONS FOR SERVER:

Explanation

Response to the command: MODIFY DISPLAY,ADAPTER,REGISTRATIONS

Action

None

BBOA0007I: SHOWING REGISTRATIONS FOR DAEMON GROUP:

Explanation

Response to the command: MODIFY DISPLAY,ADAPTER,DAEMONRGES

Action

None

BBOA0008I: POSSIBLE COMMANDS FOR ADAPTER: (EXAMPLE: DISPLAY,ADAPTER,STATUS)

Explanation

Response to an unknown ADAPTER command or HELP command

Action

None

BBOA0009I: {0} - {1}

Explanation

Displays a command or search option and its description

Action

None

BBOA0010I: INVALID OPTION OR TOKEN: {0}

Explanation

Displays an error message for an invalid option or token

Action

None

BBOA0011I: EXPLANATION: INVALID BOOLEAN VALUE: EXPECTED TRUE/FALSE OR 0/1

Explanation

Displays an error for an invalid boolean value

Action

None

BBOA0012I: EXPLANATION: INVALID NUMERIC VALUE

Explanation

Displays an error for an invalid numeric value

Action

None

BBOA0013I: EXPLANATION: INVALID ATTRIBUTE NAME

Explanation

Displays an error for an invalid attribute name when searching

Action

None

BBOA0014I: EXPLANATION: SHOULD NOT CONTAIN MORE THAN ONE =

Explanation

Displays an error for a search option with more than 1 = sign

Action

None

BBOA0015I: VALID SEARCH OPTIONS:

Explanation

Displays a header for list of valid search options and their types

Action

None

BBOA0016I: {0}

Explanation

Displays a search option and its type

Action

None

BBOA0017I: {0} DISPLAYS OLA STATUS

Explanation

A description for the STATUS command

Action

None

BBOA0018I: {0} DISPLAYS REGISTRATIONS FOR CURRENT SERVER

Explanation

A description for the STATUS command

Action

None

BBOA0019I: {0} DISPLAYS REGISTRATIONS FOR GIVEN SERVER NAME

Explanation

A description for the STATUS command

Action

None

BBOA0020I: {0} DISPLAYS REGISTRATIONS FOR DAEMON GROUP

Explanation

A description for the STATUS command

Action

None

BBOA0021I: {0} SEE DISPLAY,ADAPTER,SEARCHRGES,HELP FOR INFO

Explanation

A description for the STATUS command

Action

None

BBOA0022I: SERVER NOT FOUND WITH THE NAME {0}

Explanation

An error message for the DISPLAY,ADAPTER,REGISTRATIONS,servername command

Action

None

BBOA0023I: THIS REGISTRATION DOES NOT HAVE ANY CONNECTION HANDLES

Explanation

A message that is displayed for a detailed RGE view without any connection handle

Action

None

BBOA0024I: ID LSCB State

Explanation

A header for the tabular display of connection handles

Action

None

BBOA0025I: {0} {1} {2}

Explanation

A row of display of connection handles for a registration

Action

None

BBOA0026I:

Explanation

A row of white space

Action

None

BBOA0027I: {0} AFTER ENTIRE COMMAND WILL SHOW EXTENDED INFORMATION

Explanation

A description for the DETAILS command

Action

None

BBOA0028I: The Optimized Local Adapters RAR file used by this server needs to be updated

Explanation

An updated RAR file for the Optimized Local Adapters (OLA) feature of WebSphere Application Server for z/OS has been supplied with this service pack. The version which is currently installed may not be compatible with this service pack.

Action

Replace the Optimized Local Adapters (OLA) RAR file installed in this server instance with the one supplied by the currently installed service level of WebSphere Application Server for z/OS. Installation instructions can be found in the WebSphere Applicatin Server for z/OS Information Center.

BBOA0029E: An error was encountered performing transaction resynchronization with OLA registration {0}

Explanation

WebSphere Application Server for z/OS is requesting transaction resynchronization with the Optimized Local Adapters registration name identified in the message. The resynchronization process did not complete due to an exception.

Action

When resynchronizing with CICS, be sure that the Optimized Local Adapter link server corresponding to the registration name is started. Look in the WebSphere Application Server for z/OS logs and FFDC for an exception associated with this resynchronization operation. If the problem persists, contact your next level of support.

BBOA0030E: An exception was raised when {0} a transaction with OLA registration {1}

Explanation

WebSphere Application Server for z/OS attempted to complete a two phase commit transaction, and encountered an error when communicating with an Optimized Local Adapters registration. This message may be supressed if repeated errors occur to the same registration.

Action

Be sure that the Optimized Local Adapters registration named in the message is started. During resynchronization at server startup, this message does not necessarily indicate that a failure has occurred, due to the nature of the two phase commit and presume abort protocols. Check the WebSphere Application Server for z/OS logs and FFDC for details pertaining to the exception which caused this mesasge to be issued. The exception may contain the transaction XID identifying the specific transaction and operation which failed. If the problem persists, contact your next level of support.

BBOA0031I: DETAILS FOR IMS {0} / {1}

Explanation

Displays the XCF group ID and XCF server name used by OTMA for an IMS system which WebSphere Application Server for z/OS is connected to. Individual client names will follow using message BBOA0032I.

Action

None

BBOA0032I: {0} {1}

Explanation

Displays the WebSphere Application Server for z/OS server name and the OTMA client name that are used to connect to the IMS system identified by the preceeding BBOA0031 message.

Action

None

BBOA0033I: OTMA NAME POOL DOES NOT EXIST

Explanation

The OTMA name pool for this system has not been created yet and cannot be displayed by the display command.

Action

None

BBOA0034I: {0} DISPLAYS THE OTMA NAME POOL

Explanation

A description for the OTMANAMES command.

Action

None

BBOA0035I: MAX NAMES PER IMS {0}

Explanation

Displays the maximum number of OTMA client name that WebSphere Application Server for z/OS can use to connect to each IMS system.

Action

None

BBOA0036I: SET BY {0} AT {1}

Explanation

Displays the WebSphere Application Server for z/OS daemon group name that set the maximum number of OTMA client names. The OTMA client names can be used to see which IMS systems a WebSphere Application Server for z/OS instance is connected to. The time that the maximum number of OTMA client names was set, in STCK format, is also displayed. The maximum number of OTMA client names was displayed using message BBOA0035I.

Action

None

BBOA0037W: The Optimized Local Adapters RAR is operating in proxy mode and will not participate in local or global transactions.

Explanation

When the Optimized Local Adapters RAR is installed on a platform other than z/OS, it operates in proxy mode, communicating with a WebSphere Application Server for z/OS server which has the proxy EJB installed. When running in this mode, transactions are not supported. The resource adapter will ignore any transaction protocol messages it receives.

Action

None. This message is issued the first time the resource adapter attemps to enlist in a transaction while in proxy mode.

BBOA0038E: An error was encountered while attempting to process a WebSphere Optimized Local Adapter (WOLA) remote work request on the Enterprise Java Bean target identified with the JNDI name of {0}. The exception encountered is {1}.

Explanation

An error was encountered while attempting to process a WebSphere Optimized Local Adapter (WOLA) remote work request on the remote Enterprise Java Bean target.

Action

Verify that the Java Naming and Directory Interface (JNDI) name provided is correct. Verify that the Enterprise Java Bean target is within the scope that the caller can see and reach. Look in the WebSphere Application Server for z/OS logs and First Failure Data Capture (FFDC) for an exception associated with the remote Enterprise Java Bean call.

BBOA0039E: The transaction XID for the failed request is: {0}

Explanation

WebSphere Application Server for z/OS reported a failed WebSphere Optimized Local Adapters (WOLA) transaction resolution request in the BBOA0030E message. This message contains the transactional identifier for the request that failed.

Action

No action is required. The information in this message may be useful in resolving the failure reported in the BBOA0030E message.

BBOA0040E: An attempt to locate service {0} hosted by registration name {1} failed.

Explanation

An application obtained a connection to the WebSphere Optimized Local Adapters (WOLA) registration specified in the message. The application attempted to invoke the service name specified in the message, but the service was not being hosted by the registration.

Action

Verify that the register name and service name specified in the message are correct. Verify that the client program that established the registration is also hosting the service name specified. If using the CICS link server, verify that the link server is started and is configured with enough connections to handle the volume of work being sent by the WebSphere Application Server for z/OS server instance.

BBOA0041W: The supplied value for OTMAMaxRecvSize of {0} is not compatible with the value for OTMAMaxSegments {1}. The value for OTMAMaxRecvSize is changed to {2}. The OTMAMaxRecvSize value was taken from the {3} and the OTMAMaxSegments value was taken from the {4}.

Explanation

An application obtained a connection to an IMS system from an Optimized Local Adapters (WOLA) connection factory. The effective values for OTMAMaxRecvSize and OTMAMaxSegments are not compatible. The maximum value for OTMAMaxRecvSize is 32768 * OTMAMaxSegments. The value of OTMAMaxRecvSize is adjusted to be the maximum size that can be supported by OTMAMaxSegments. The values for these properties is supplied in the ManagedConnectionFactory configuration, or over-ridden by a ConnectionSpecImpl. The message indicates where the values were taken from.

Action

Verify that the values provided for OTMAMaxRecvSize and/or OTMAMaxSegments in the ManagedConnectionFactory and/or ConnectionSpecImpl are correct. If both values are taken from a ManagedConnectionFactory, the ManagedConnectionFactory definition should be changed. If either value is taken from a ConnectionSpecImpl, an application change might be required. An FFDC record is written to help determine which application might be using incorrect values.

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

BBOA8080E: An error occurred during GETINFO API call with return code {1} and reason code {2}.

Explanation

The BBOC LIST_SRVR call failed during the call for Get WOLA Information.

Action

Check BBOQ log for further messages. Verify that the WAS server is running at the level at or above where the LIST_SRVR support was added.

BBOA8081E: The temporary storage queue (LTSQ) parameter length is greater than 8, which exceeds the maximum size of a temporary storage queue name length.

Explanation

This is an incorrect parameter length.

Action

Change the parameter length and retry.

BBOA8082E: EXEC CICS WRITEQ error. Queue name: {1} respcode: {2}

Explanation

An error occurred in attempting to write data to the named CICS temporary storage queue.

Action

Verify the passed TSQ name is valid. Check the CICS log in order to determine the error associated.

BBOA8083E: INQUIRE SYSTEM error. respcode: {1}

Explanation

An error occurred during the BBOC request.

Action

Check BBOQ log for further messages. Look up the EIBRESP code for the EXEC CICS INQUIRE SYSTEM API call in the CICS Information Center

BBOA8084E: List Server returned with errors

Explanation

This is a general error message related to the BBOC LIST_SRVR operation.

Action

Check BBOQ log for further messages or if using EXEC CICS LINK PROGRAM(BBOACLINK), check the return and reason code from the call.

BBOA8085E: A TX RESYNC error occurred.

Explanation

An error occurred processing a RESYNC request.

Action

Check BBOQ log for further messages.

BBOA8086E: The RESYNC could not complete because the UOW was ommitted.

Explanation

The UOW parameter is required for TXRESYNC.

Action

Specify the UOW parameter and retry.

BBOA8087E: An error occurred because of incorrect UOW parameter data length.

Explanation

The UOW parameter length is incorrect for TXRESYNC.

Action

Change the parameter length and retry.

BBOA8088E: An error occurred because of incorrect UOW parameter data.

Explanation

The UOW parameter data is incorrect for TXRESYNC.

Action

Correct the parameter data and retry.

BBOA8089E: An error occurred calling EXEC CICS RESYNC. RESPCODE = {1}

Explanation

The EXEC CICS RESYNC for BBOATRUE failed.

Action

Refer to the CICS error codes in the CICS documentation to determine the corrective action.

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.

BBOA8115E: An error occurred because of incorrect LSYNC parameter data.

Explanation

The parameter data supplied was incorrect.

Action

Change the parameter data 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.

BBOA8117E: LSYNC=Y is not compatible with TXN=Y.

Explanation

This is an incompatible combination of parameters.

Action

Change one of the incompatible parameters 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 REU parameter length is incorrect.

Explanation

This is an incorrect parameter length. Either no value was supplied or the value supplied exceeded the maximum length of defined values.

Action

Change the parameter value and retry.

BBOA8132E: An error was encountered adding new link server {1}

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.

BBOA8133E: The Reuse count length is greater than 8, which exceeds the maximum size of this parameter.

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.

BBOA8134E: The Reuse count > 2GB and exceeds the maximum value of this parameter.

Explanation

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.

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.

BBOA8136E: The Reuse time > 2GB and exceeds the maximum value of this parameter.

Explanation

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}

Explanation

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.

BBOA8138E An error occurred in CICS for the {0} function with the following values: EIBRCODE = {1}; RESP = {2}; RESP2 = {3}.

Explanation

The specified CICS EXEC function did not complete successfully.

Action

Refer to the CICS error codes in the CICS documentation to determine the corrective action.

BBOA8140W: Start server completed with warnings.

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.

BBOA8141E: The link invocation task parameter RTXP was set to a value other than Yes (Y) or No (N).

Explanation

The BBOC RTXP parameter must be Yes (Y) or No (N).

Action

Re-submit the request with a valid RTXP option.

BBOA8142E: An error occurred because of incorrect REU parameter data.

Explanation

The supplied parameter data was incorrect.

Action

Change the parameter data and retry.

BBOA8201E: Unable to locate requested Registration Name : {1}

Explanation

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>

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

BBOA8586E: The link server is unable to generate a unique REQID and will terminate.

Explanation

The link server attempted to generate a unique REQID which is to be used on the EXEC CICS START TRANSID API. The common storage used to hold the unique identifier could not be found.

Action

Be sure that the control task (BBOACNTL) 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.

BBOA8587E: An error occurred when querying the size of transient data queue (TDQ) {1} eibresp {2} eibresp2 {3}

Explanation

Action

BBOA8588E: Link server {1} lost connectivity to {2}

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.

BBOA8589E: A Receive Request error occurred with return code {1} and reason code {2}

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.

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.

BBOA8602I: Link server {1} regained connectivity to {2}

Explanation

Communication with the WebSphere Application Server for z/OS server instance indicated in the message has been regained.

Action

Ensure that the WebSphere Application Server for z/OS server instance has been running.

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

BBOA8753E: XID GTRID {1}

Explanation

Additional information on a recovery UOW that was detected to be in a wrong state.

Action

More information can be found the BBOA8764E message. The operation will be retried. If the problem persists, contact IBM support.

BBOA8754E: UOW {1}

Explanation

Additional information on a recovery UOW that was detected to be in a wrong state.

Action

More information can be found the BBOA8764E message. The operation will be retried. If the problem persists, contact IBM support.

BBOA8755E: An error occurred when querying the size of transient data queue (TDQ) {1} eibresp {2} eibresp2 {3}

Explanation

Action

BBOA8756E: CICS version {1} does not support transaction propagation over OLA

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.

BBOA8757E: Could not parse CICS TS version {1}

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.

BBOA8758E: An error occurred invoking EC INQUIRE SYSTEM CICSTSLEVEL: {1}

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.

BBOA8759E: Error starting UOWLINK iteration for UOW {1} ({2})

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.

BBOA8760E: Did not find UOWLINK in UOW {1} to delete

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

BBOA8761E: Error deleting UOWLINK {1} in UOW {2} ({3})

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.

BBOA8762E: Failure deleting UOWLINK during iteration ({1})

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.

BBOA8763E: Error finding Recovery UOW in UOWLIST ({1})

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.

BBOA8764E: Recovery UOW is in the wrong state ({1}) or wrong waitstate ({2}) for resolution

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.

BBOA8765E: Cannot {1} recovery UOW due to EC SET UOW error ({2})

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.

BBOA8766E: Cannot return {1} XIDs to WebSphere due to EC GETMAIN error ({2})

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.

BBOA8767E: Recovery of UOWs ended prematurely due to EC INQUIRE UOWLINK NEXT error ({1})

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.

BBOA8768E: Cannot recover UOW {1} due to EC INQUIRE UOW error ({2})

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.

BBOA8769E: Cannot recover UOW {1} due to EC GETMAIN error ({2})

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.

BBOA8770E: Link parms received are version {1}, expecting version {2}

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.

BBOA8771E: Transaction TID is too long to import ({1})

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.

BBOA8772E: The link task is exiting due to a COMM failure. The link count is {1}

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.

BBOA8773E: Commit failed RC = {1} RSN = {2}

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.

BBOA8774E: Prepare failed RC = {1} RSN = {2}

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.

BBOA8775E: Received new method in a prepared transaction

Explanation

New work for a UOW was received after the UOW was prepared.

Action

If the problem persists, contact IBM support.

BBOA8776E: Prepare voted heuristic

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.

BBOA8777E: Prepare voted backout

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.

BBOA8778E: Backout failed RC = {1} RSN = {2}

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.

BBOA8779E: CommitOnePhase failed RC = {1} RSN = {2}

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.

BBOA8780E: Link server task must process methods for existing TID

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.

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: Error freeing request buffer addr {1} size: {2}

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.

BBOA8787E: Transaction state incorrect for {1}

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.

BBOA8788E: TID does not match existing transaction

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.

BBOA8789E: An EXEC CICS STARTBROWSE CONTAINER error occurred with eibresp: {1} eibresp2: {2}.

Explanation

The EXEC CICS STARTBROWSE CONTAINER failed.

Action

Refer to the CICS reference material for EIBRESP and EIBRESP2 meanings for CICS STARTBROWSE CONTAINER for more information. If 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.

BBOA8793E: An EXEC CICS GETNEXT CONTAINER error occurred with eibresp: {1} eibresp2: {2}.

Explanation

The EXEC CICS GETNEXT CONTAINER error occurred while determining the response size.

Action

Refer to the CICS reference material for EIBRESP and EIBRESP2 meanings for CICS GETNEXT CONTAINER for more information. If unable to determine the cause, contact IBM support.

BBOA8794E: Could not retrieve transaction context for next method

Explanation

The link task was notified for a new request. Information about the transaction could not be extracted.

Action

Contact IBM support.

BBOA8795E: Import global transaction failed with RC = {1} (hex) RSN ={2} (hex)

Explanation

A request was read by the link task which contains a transaction XID. Information about the transaction could not be extracted.

Action

Contact IBM support.

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

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

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

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.

BBOA8806E: An EXEC CICS DELETE CONTAINER {1} error occurred with eibresp: {2} eibresp2: {3}.

Explanation

A CICS DELETE CONTAINER error occurred while building the response.

Action

Refer to the CICS reference material for EIBRESP and EIBRESP2 meanings for CICS DELETE CONTAINER for more information.

BBOA8807E: An EXEC CICS GET CONTAINER {1} error occurred with eibresp: {2} eibresp2: {3}.

Explanation

A CICS GET CONTAINER error occurred while building the response.

Action

Refer to the CICS reference material for EIBRESP and EIBRESP2 meanings for CICS GET CONTAINER for more information.

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 program in WebSphere. The message contains the program name and abend code.

BBOA8960I: <Level 0 Trace message>

Explanation

This message is for informational purposes only.

Action

None

BBOA8961I: Listing all servers in region {1}

Explanation

A BBOC LIST_SRVR operation was requested. The list of active WOLA Linke Servers are about to be listed for this indicated region.

Action

None

BBOA8962W: No Link Servers are active in region {1} at this time.

Explanation

A BBOC LIST_SRVR operation was requested searching for all Link Servers and no Link Servers were located.

Action

None

BBOA8963W: No matching Link Servers are active in region {1} at this time.

Explanation

A BBOC LIST_SRVR operation was requested with the RGN parameter and no matching Link Servers were located.

Action

None

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

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

BBOA9920I: WAS z/OS OLA CICS PLT init start.

Explanation

WOLA CICS PLT program BBOACPLT started.

Action

None

BBOA9921I: WAS z/OS OLA CICS TRUE enabled.

Explanation

WOLA CICS PLT program BBOACPLT successfully invoked BBOC START_TRUE.

Action

None

BBOA9925I: WAS z/OS OLA CICS PLT init ending.

Explanation

WOLA CICS PLT program BBOACPLT ending normally.

Action

None

BBOA9930W: Invalid CICS release. Requires CICS TS 3.1+

Explanation

WOLA CICS PLT program BBOACPL2, BBOACPLS, or BBOACPLT requires CICS version 3.1 or higher.

Action

Retry the target program on CICS version 3.1 or higher.

BBOA9931E: Error in OLA Start TRUE request. Check BBOQ.

Explanation

WOLA CICS PLT program BBOACPLT detected an error after invoking BBOC START_TRUE.

Action

Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages.

BBOA9940I: WAS z/OS OLA CICS PLT init 2 start.

Explanation

WOLA CICS PLT program BBOACPL2 started.

Action

None

BBOA9941I:WAS z/OS OLA CICS Request Successful.

Explanation

WOLA CICS PLT program BBOACPL2 completed the INITPARM request without error.

Action

None

BBOA9944I: Issuing OLA REGISTER request ...

Explanation

WOLA CICS PLT program BBOACPL2 is about to drive a OLA REGISTER call after parsing it from the INITPARM data.

Action

None

BBOA9945I: Issuing OLA START_SRVR request ...

Explanation

WOLA CICS PLT program BBOACPL2 is about to drive a OLA START_SRVR call after parsing it from the INITPARM data.

Action

None

BBOA9951E: Error in OLA BBOC request. Check BBOQ.

Explanation

WOLA CICS PLT program BBOACPL2 or BBOACPLS detected an error after invoking BBOC.

Action

Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages.

BBOA9952E: Readq TS {1} EIBRESP: {2}

Explanation

WOLA CICS PLT Shutdown program BBOACPLS issued a READQ for TSQ BBOALTSQ and received the error shown.

Action

Look up the EIBRESP code for the EXEC CICS READQ TS CICS API in the CICS Information Center to determine the reason for the error.

BBOA9953E: Readq TS Record length: {1}

Explanation

WOLA CICS PLT Shutdown program BBOACPLS issued a READQ for TSQ BBOALTSQ and received a record length error.

Action

The call to BBOACNTL for operation LIST_SRVR failed. This should not occur and should be reported to the IBM support center.

BBOA9955W: No INITPARM data. Ending with no action.

Explanation

WOLA CICS PLT program BBOACPL2 started without INITPARM.

Action

Check that the INITPARM string is available to CICS and retry.

BBOA9956E: Bad OLA INITPARM data. Ending with no action.

Explanation

WOLA CICS PLT program BBOACPL2 started with an INITPARM that did not contain a recognized START or REGISTER request.

Action

Check that the INITPARM string contains a supported request.

BBOA9960I: WAS z/OS OLA CICS PLT shutdown start.

Explanation

WOLA CICS PLT Shutdown program BBOACPLS started.

Action

None

BBOA9961I: Issuing OLA STOP_SRVR for: {1}

Explanation

WOLA CICS PLT Shutdown program BBOACPLS is issuing a BBOC STOP_SRVR for the named registration.

Action

None

BBOA9963I: Readq TS {1}

Explanation

WOLA CICS PLT Shutdown program BBOACPLS progress message during READQ loop.

Action

None.

BBOA9965I: WAS z/OS OLA CICS PLT shutdown ending.

Explanation

WOLA CICS PLT Shutdown program BBOACPLS ending.

Action

None

BBOA9966I: WAS z/OS OLA CICS PLT init 2 ending.

Explanation

WOLA CICS PLT Shutdown program BBOACPL2 ending.

Action

None

BBOA9967I: No Link servers active in this region.

Explanation

WOLA CICS PLT Shutdown program BBOACPLS found no active servers to stop.

Action

None

BBOA9968I:WAS z/OS OLA CICS Request Successful.

Explanation

WOLA CICS PLT program BBOACPLS successfully issued all stop server requests.

Action

None

BBOA9969E: The length of the CICS transaction ID parameter CTID is greater than 4, which exceeds the maximum size of a CICS transaction ID.

Explanation

This is an incorrect parameter length.

Action

Change the parameter value and retry.

BBOA9970W: A CICS transaction identifier with the CPLT value was used to start the task related user exit (TRUE). To avoid errors, BBOC is used.

Explanation

A CICS transaction identifier with the CPLT value was encountered when the TRUE was established. If the TRUE uses the CPLT value for transaction recovery, CICS issues an error. To avoid the error, the TRUE uses BBOC for transaction recovery.

Action

If you do not want BBOC used as the transaction identifier, use the CTID= parameter in the CICS PLT initialization program to specify a different transaction identifier. A sample of a CICS PLT initialization program is in the <install_root>/util/zos/OLASamples/bboacplt.jclsam file.