|
|
|
|
|
This group includes messages for the IOA (infrastructure) product.
Explanation: BLDL for the modName module failed.
This is due to one of the following:
The requested module is not activated. Control is returned to the calling program. The IOA Online Facilities may abend on initialization.
Corrective Action: Verify whether the module appears in IOA Load library or any other concatenated load module library.
Explanation: More than one program has been marked for selection.
Only one program may be selected at a time.
Corrective Action: Select one program only.
Explanation: No program selection specified.
Corrective Action: Mark S near the program name for selection of program.
Explanation: This entry is in use by a program which is currently active.
Enter the active program, and terminate its execution normally, so that the entry can be used for another program.
Corrective Action: Exit the program using the END command or use a new entry.
Explanation: An invalid input parameter (parm), was supplied to the main IOA online module (modName).
The modName module expects a series of parameters to be input, which describe the environment in which it is to be activated.
The expected parameters are:
APPLTYPE=type,APPLID=id,
where
However, these parameters were missing or invalid.
The IOA online environment is not built.
Corrective Action: Check for errors in the CLIST which activates the IOA online interface.
Explanation: Highlighted, unrollable message.
The DD name specified in the error message was not allocated before the user entered IOA.
The IOA Online facility terminates.
Corrective Action: Allocate the specified DD name and reenter IOA.
Explanation: Highlighted, unrollable message.
A user tried to enter IOA using a user-defined transaction member which contained a definition of a product not recognized by IOA.
The IOA Online facility stops.
Corrective Action: Correct the product definition in the transaction member and reenter IOA.
Explanation: Highlighted, unrollable message.
A user tried to enter IOA using a user-defined transaction.
In this message, transMem is a member that pointed to a PGM member name that did not exist in the parameter library referenced by the DD name DAONLPRM.
The Online facility terminates.
Corrective Action: Check that the PGM member is correctly specified in the transaction member. If it is correctly specified in this member, add it to the parameter library. Reenter IOA.
Explanation: The user tried to enter IOA using a user-defined transaction.
In this message, transMem is a member that does not exist in the parameter library referenced by the DAONLPRM DD name.
The IOA Online facility stops.
Corrective Action: Add the transaction member identified in the message to the parameter library and reenter IOA.
Explanation: The user tried to enter IOA using a user-defined transaction.
In this message, transMem is the member that contained an invalid keyword.
The Online facility stops.
Corrective Action: Check the keywords in the transaction member and correct them accordingly. See the section on Transaction Members in the INCONTROL for z/OS Administrator Guide. Reenter the IOA Online facility.
Explanation: An internal error occurred when a user tried to enter IOA using a user-defined transaction.
The internal error occurred when the IOA Online facility tried to initiate the IOA session using the transMem transaction member.
The IOA Online facility stops.
Corrective Action: Supply BMC Customer Support with a printout of the transMem member.
Explanation: IOA online system failed to allocate a file.
When the IOA Online facility starts up, it allocates all the files needed for the current session. At least one of these files could not be allocated.
Preceding messages detail the files that could not be allocated.
The IOA Online system stops.
Corrective Action: Correct the ALCxxx members according to information from the preceding messages and reenter IOA.
Explanation: The file whose DD name is specified in the error message was already allocated to the IOA Online environment when the IOA Online facility started up.
When the IOA Online facility starts up, certain files are dynamically allocated by it to the IOA environment. In this case, the file identified in the message was already allocated to the IOA environment when IOA started up.
The Online facility terminates.
Corrective Action: Deallocate this DD name from the IOA environment.
Explanation: This is one of two messages with the same ID, but different text.
A severe error occurred in the modName module when the user tried to enter an IOA option. In most cases, the called program could not issue an error message.
Valid values for rc are:
rc |
Explanation |
|---|---|
8 |
There is no region below the line for the application |
12 |
There is no region above the line for the application |
16 |
A severe error occurred. The called program issued an error message |
20 |
A severe error occurred. An error message could not be issued |
The called program abends.
Corrective Action: If modName is CTDTOBJ and RC=12, check the IOA LOG for message CTDE12E. If CTDE12E was issued, see “CTDE12E RESOURCE LIBRARY HAS AN INCORRECT FORMAT” in the INCONTROL for z/OS Messages Manual.
Otherwise, consider the following actions, according to the return code:
Explanation: This is one of two messages with the same ID, but different text.
Either the msgId message is missing from the memName member, or the msgId message member is missing from the IOA MSG library.
Corrective Action: No action is required.
Explanation: TSO user tried to activate a fifth IOA session in his TSO address space.
In the TSO environment, the user can activate IOA sessions by executing the IOATSO or IOAISPF CLISTs. IOA allows a maximum of 4 sessions to be activated. If the user tries to activate a fifth session, this error message is generated.
The fifth session is not established.
Corrective Action: Terminate one of the previous sessions in order to initiate a new session.
Explanation: IOA could not access the user profile member during IOA online initialization.
The IOA online session terminates.
Corrective Action: Call your INCONTROL administrator.
Explanation: The msgId message is missing from the IOA MSG library.
Corrective Action: No action is required.
Explanation: The message processing facility was not initialized properly. It is therefore impossible to issue any messages.
The IOA session is ended.
Corrective Action: No action is required.
Explanation: The message processing facility encountered a problem while trying to obtain an exclusive lock in order to issue a message.
The IOA session is ended.
Corrective Action: No action is required.
Explanation: The message processing facility is unable to open the IOA MSG library.
The IOA session is ended.
Corrective Action: No action is required.
Explanation: The message processing facility is unable to process any more messages because of a storage shortage.
The IOA session is ended.
Corrective Action: No action is required.
Explanation: The message processing facility is unable to process any more messages because of a storage shortage.
The IOA session is ended.
Corrective Action: No action is required.
Explanation: An attempt to access the $PROFILE member in the IOAENV library failed.
The most common cause is that the member is held by another user or program.
The IOA Online facility is not entered.
Corrective Action: Determine which user or program is holding the member, and try to obtain its release.
Explanation: An irrelevant option was specified in the memName transaction member.
The IOA online session terminates.
Corrective Action: Change the memName transaction member and log on again to the IOA online session.
Explanation: IOA was unable to write the user profile member.
The write process is ignored.
Corrective Action: Check whether or not there is enough space in the profile library.
Parent Topic |