Explanation | First line response to a detailed registration listing command. |
Action | None |
Explanation | Second line response to a detailed registration listing command. |
Action | None |
Explanation | Third line response to a detailed registration listing command. |
Action | None |
Explanation | Header response for a tabulated registration listing command. |
Action | None |
Explanation | RGE row response for the tabulated command: MODIFY,DISPLAY,ADAPTER,RGE,* |
Action | None |
Explanation | Response to the command: MODIFY DISPLAY,ADAPTER,STATUS |
Action | None |
Explanation | Response to the command: MODIFY DISPLAY,ADAPTER,REGISTRATIONS |
Action | None |
Explanation | Response to the command: MODIFY DISPLAY,ADAPTER,DAEMONRGES |
Action | None |
Explanation | Response to an unknown ADAPTER command or HELP command |
Action | None |
Explanation | Displays a command or search option and its description |
Action | None |
Explanation | Displays an error message for an invalid option or token |
Action | None |
Explanation | Displays an error for an invalid boolean value |
Action | None |
Explanation | Displays an error for an invalid numeric value |
Action | None |
Explanation | Displays an error for an invalid attribute name when searching |
Action | None |
Explanation | Displays an error for a search option with more than 1 = sign |
Action | None |
Explanation | Displays a header for list of valid search options and their types |
Action | None |
Explanation | Displays a search option and its type |
Action | None |
Explanation | A description for the STATUS command |
Action | None |
Explanation | A description for the STATUS command |
Action | None |
Explanation | A description for the STATUS command |
Action | None |
Explanation | A description for the STATUS command |
Action | None |
Explanation | A description for the STATUS command |
Action | None |
Explanation | An error message for the DISPLAY,ADAPTER,REGISTRATIONS,servername command |
Action | None |
Explanation | A message that is displayed for a detailed RGE view without any connection handle |
Action | None |
Explanation | A header for the tabular display of connection handles |
Action | None |
Explanation | A row of display of connection handles for a registration |
Action | None |
Explanation | A row of white space |
Action | None |
Explanation | A description for the DETAILS command |
Action | None |
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. |
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. |
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. |
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 |
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 |
Explanation | The OTMA name pool for this system has not been created yet and cannot be displayed by the display command. |
Action | None |
Explanation | A description for the OTMANAMES command. |
Action | None |
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 |
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 |