This group includes messages for the IOA (infrastructure) product.
Explanation: This information message indicates that the IOA Application server has been initiated and is ready to receive requests.
Corrective Action: No action is required.
Explanation: The Control-D Recipient Tree could not be loaded during initialization of the Application server.
The IOA Application server is terminated.
Corrective Action: Correct the problem with the Recipient Tree and restart the Application server.
Explanation: The Control-D Approval Tree could not be loaded during initialization of the Application server.
The IOA Application server is terminated.
Corrective Action: Correct the problem with the Approval Tree and restart the Application server.
Explanation: The user sent an invalid MODIFY (F) command to the IOA Application server. The list of valid MODIFY commands is displayed on the operator console.
The invalid command is ignored.
Corrective Action: Reissue a valid MODIFY command.
Explanation: This warning message indicates that an invalid timeout value was passed by IOAGATE when the IOA Application server was started.
The invalid value is ignored and default value will be used.
Corrective Action: No action is required.
Explanation: This message indicates that a control message of an invalid type was passed by IOAGATE.
The control message is ignored.
Corrective Action: Report the problem.
Explanation: Since an invalid value was specified for the MAXMSGSZ parameter in the ECAAPPL member, MAXMSGSZ is set to its default value instead.
Corrective Action: Specify a correct value for the MAXMSGSZ parameter in the ECAAPPL member of the IOAENV library.
Explanation: The specified Mailbox operation (READ or WRITE) failed. The IOA Gateway and the IOA Application server communicate through mailboxes.
The Application server subtask is terminated.
Corrective Action: Report the problem, the return code, and any additional relevant messages to BMC Customer Support.
Explanation: The IOA Application server received a request of an unknown type. The request is probably not recognized by the Application server because the software on the mainframe and the PC are not the same release level.
The request is ignored and this error message is sent to the client.
Corrective Action: Do not use the feature that is discussed in this message until the appropriate software is upgraded.
Explanation: The IOA Application server received a request from a client, but a corresponding session did not exist. The session was probably terminated due to a timeout, a restart of the IOA Gateway, or a restart of the IOA Application server.
The request is ignored and this error message is sent to the client.
Corrective Action: Exit the problematic session and start a new session.
Explanation: An unauthorized user attempted to log in to the IOA Application server. The user name or password is checked by Security Exit IOAX016 through the security subsystem, for example, RACF, ACF2SAF, or Top Secret.
The request is ignored and this error message is sent to the client.
Corrective Action: If the user is authorized to use the server, set the authorized user name and password in the client software.
Explanation: This information message indicates that the IOA Application server terminated a session that was dormant longer than the specified timeout interval. The timeout interval is specified in the TIMEOUT parameter in the Application server declaration. For details see the parameters for IOAGATE.
The session is terminated. All storage areas connected with the session in the Application Server are freed.
Corrective Action: Exit the problematic session and start a new session.
Explanation: This information message indicates that the Application server started a new session for the specified user.
Corrective Action: No action is required.
Explanation: This information message indicates that the Application server terminated a session for the specified user. This message reports the CPU time used.
Corrective Action: No action is required.
Explanation: This information indicates that the IOA Application server processed the DISPLAY (D) command successfully. This message displays the column headings for information supplied by message IOAQ18I, which follows. The DISPLAY (D) command displays a list of active sessions.
Corrective Action: No action is required.
Explanation: This information message displays information about a currently open session for the IOA Application server. The first occurrence of this information message always follows the IOAQ17I message. Multiple occurrences of this information message display a table of currently open sessions. IOAQ18I is displayed in response to a DISPLAY (D) command. The IOAQ19I message follows immediately after the last occurrence of this message. The following information is included in each occurrence of this message:
Corrective Action: No action is required.
Explanation: This information message indicates the total number of sessions open for the IOA Application server. This message marks the end of a table displayed by IOAQ18I and IOAQ17I messages. These messages are displayed in response to a DISPLAY command sent to the IOA Application server.
Corrective Action: No action is required.
Explanation: This message is issued because of an internal error.
Performance statistics cannot be accumulated.
Corrective Action: Report the problem.
Explanation: This message can be issued if the IOAPFST module, which accumulates performance statistics, is absent from the STEPLIB library, or because of an internal error. This message can appear at the start of the application server or after the STATINIT MODIFY command.
Performance statistics collection is not initiated.
The MODIFY command is ignored.
Corrective Action: If the module is present, report the problem to BMC Customer Support.
Explanation: This information message is normal reaction on MODIFY command STATINIT.
Corrective Action: No action is required.
Explanation: This information message is a normal reaction to the MODIFY command STATTERM.
Corrective Action: No action is required.
Explanation: This message is issued because of an internal error.Trace cannot be limited.
Corrective Action: Report the problem to BMC Customer Support.
Explanation: This message can be issued if the IOATRSRP module, which performs perfomance trace limitation commands, is absent from the STEPLIB library, or because of an internal error. This message can appear after MODIFY command TRCSHARP.
Performance statistics collection is not initiated.
The MODIFY command is ignored.
Corrective Action: If the module is present, report the problem to BMC Customer Support.
Explanation: A user tried to log on to the IOA Application server. However, the IOASE16 security module or the IOAX016 user exit rejected the request. The message displays the reason provided by the security package for rejecting the user. Your security software documentation will have an explanation of the reason code.
The login request is rejected.
Corrective Action: Check that the user name and password are spelled correctly and retry. If necessary, contact your security administrator.
Explanation: The OUTPUT message created by Application Server for Control-D/WebAccess server, is longer than the value defined by the MAXMSGSZ parameter in the ECAAPPL member of the IOAENV library. The request is not performed. Additional information is written to DATRACE.
Corrective Action: Check the IOA Log and the system log for additional error messages. Report the problem, DATRACE content, and any additional error messages to BMC Customer Support.
Explanation: Application U, specified in the IOA Application Server declaration (see IOAGATE parameters), could not be initiated. The message can be preceded with other messages, which provide further explanation.
The application is not initiated and is available for requests.
Corrective Action: If possible, correct the problem and restart the Application server. Otherwise, report the problem, supplying all appropriate messages.
Explanation: The amount of CPU required for processing the Control-D/WA request exceeds the value set in the optional wish WD3473. The request processing has terminated.
Corrective Action: Examine the selection parameters for the report list request to find the probable cause of the long processing time. Alternately, try increasing the value of the WD3473 optional wish.
Explanation: A user tried to log on to the IOA Application server. However, his request can be served. The user sent a request with the code of an application that has not been initiated in this Application server. The reasons can be as follows:
The request is ignored and this error message is sent to the client.
Corrective Action: Do not use the feature that explains this message until the appropriate software is upgraded, or repeat the request after the Application server restart if the reason for the IOAQ22E message can be corrected.
Explanation: This warning message indicates that the number of sessions opened in Application Server exceeded the limit of 800 sessions. This limit is designed to prevent insufficient memory problems in Application Server.
Corrective Action: Define an additional Control-D Application Server for the IOA Gateway.
Explanation: The IOA Application server executor subtask failed to retrieve a request from the queue. The executor subtask processes requests such as OPEN/CLOSE operations from other subtasks inside the Application server address space.
The Application server abends with code U0005.
Corrective Action: Contact BMC Customer Support.
Explanation: The Application Server executor subtask detected an error while processing a request. The executor subtask processes requests such as OPEN/CLOSE operations from other subtasks inside the Application Server address space.
The current request abends. Processing continues with the next request.
Corrective Action: Report the problem to BMC Customer Support. Supply the abend sysout produced at the time of the problem.
Parent Topic |