Messages IOAD00 through IOADxx

This group includes messages for the IOA (infrastructure) product.

IOAD01I EXTERNAL TRACE LEVELS SET AS FOLLOWS:

Explanation: This information message indicates that either a TRACE modify command was issued or a TRACE request was received from a DATRCIN/DATRCBF input data stream for external trace, and the trace parameters are successfully processed. It is a header for subsequent IOAD02I messages.

Corrective Action: No action is required.

IOAD02I lvl1[:lvl2] - TURNED status

Explanation: This information message follows messages IOAD01I (or IOAT0CI followed by IOAT0DI) and indicates the specific trace level or number of levels following one after another that are set to either ON or OFF status. Sometimes, more than one IOAD02I messages are issued.

The variables in this message are:

• lvl1 - a specific trace level that is set to status status. In cases when : lvl2 also appears in a message, it is a starting trace level set to status status.
• lvl2 - the string : lvl2 may or may not appear in a message. In cases when : lvl2 also appears in a message, lvl1 and lvl2 indicate an interval of trace levels from lvl1 through lvl2 that is set to status status.
• status - may be either ON or OFF:
  • ON--trace was activated
  • OFF--trace was deactivated

Corrective Action: No action is required.

IOAD03I THE FOLLOWING LEVELS ARE SET FOR xtrace :

Explanation: xtrace can equal EXTERNAL TRACE or TRACE BUFFER: bufid. This message is issued as a result of command TRACE=SHOW or TRACE=DISP. It is a header for subsequent IOAD04I messages.

Corrective Action: No action is required.

IOAD04I lvl1:lvl2 - status

Explanation: This information message follows messages IOAD03I and indicates specific trace level or number of levels following one after another that are in either ON or OFF status.

The variables in this message are:

• lvl1 - a specific trace level that is in status status. In cases when : lvl2 also appears in a message, its starting trace level is set to status status.
• lvl2 - the string : lvl2 may or may not appear in a message. In cases when : lvl2 also appears in a message, lvl1 and lvl2 indicate an interval of trace levels from lvl1 through lvl2 that is set to status status.
• status - may be either ON or OFF.

Several IOAD04I messages may be issued for a single IOAD03I message.

Corrective Action: No action is required.

IOAD45E AT LEAST ONE VALID COND MUST BE SPECIFIED IN THE ISCPARM MEMBER

Explanation: No conditions to be passed to the other CPU were specified in the ISCPARM member allocated to one of the Control-M monitors. The DAISCPRM DD statement should point to a library containing the ISCPARM member. This member should contain at least one COND= cond statement, where cond is a condition name up to 20 characters. Masking characters * and ? are allowed. Only these conditions are passed to the other CPU.

CTMISR routine returns a return code of 24 to the calling IOA Exit 7. No conditions are passed to the other CPU.

Corrective Action: Add at least one COND=cond statement in the ISCPARM member and then shut down and restart the monitor. COND=* is valid for passing all the conditions.

IOAD46S CTMBLT ENDED WITH ERRORS

Explanation: The CTMBLT utility ended due to errors. CTMBLT creates Control-M scheduling tables. If CTMBLT ended with errors, messages in the Error Messages file DAPRINT DD statement explain the reasons. The Error Table Definitions file DATABERR DD statement contains the input definition statements that have the errors.

The utility ends with a non-zero return code.

Corrective Action: Correct all problems, and rerun the job.

IOAD48I CTMBLT ENDED OK

Explanation: This information message indicates that the CTMBLT utility ended normally. The CTMBLT utility creates Control-M scheduling tables.

Corrective Action: No action is required.

IOAD90E INVALID PARM WAS PASSED TO IOALLOC

Explanation: Invalid parameters were passed to load the IOALLOC module.

The IOA session is ended.

Corrective Action: No action is required.

IOAD91E UNABLE TO OBTAIN ENQ FOR IOALLOC

Explanation: The IOALLOC module was unable to obtain an exclusive lock for processing.

The IOA session is ended.

Corrective Action: No action is required.

IOAD92E DAPARM DD STATEMENT MISSING

Explanation: The IOALLOC module is unable to continue its processing because the DAPARM DD statement is missing.

The IOA session is ended.

Corrective Action: No action is required.

IOAD93E GETMAIN FAILED, INSUFFICIENT STORAGE

Explanation: The IOALLOC module is unable to continue its processing because of a storage shortage.

The IOA session is ended.

Corrective Action: No action is required.

IOAD94E IOALLOC BUFFERS ARE EXHAUSTED

Explanation: The IOALLOC module is unable to continue its processing because of a storage shortage.

The IOA session is ended.

Corrective Action: No action is required.

IOAD95E IOAPRS INITIALIZATION FAILED

Explanation: The IOALLOC module is unable to continue its processing because the initialization of IOAPRS module failed.

The IOA session is ended.

Corrective Action: No action is required.

IOAD96E PARSE ERROR OR MANDATORY PARAMETER IS MISSING, LINE lineNum MEMBER memName

Explanation: The IOALLOC module is unable to continue its processing because there is an incorrect member memName in line lineNum.

The IOA session is ended.

Corrective Action: No action is required.

IOAD97E PARSING ERROR IN LINE : num MEMBER : memName

Explanation: The IOALLOC module is unable to continue its processing because there is an incorrect member memName in line lineNum.

The IOA session is ended.

Corrective Action: No action is required.

IOAD98E EITHER DDNAME OR DSNAME WAS NOT SUPPLIED FOR KEY keyName

Explanation: The IOALLOC module is unable to continue its processing because of an incorrect key.

The IOA session is ended.

Corrective Action: No action is required.

IOAD99E UNABLE TO CREATE TOKEN

Explanation: The IOALLOC module is unable to continue its processing because the creation of a token failed.

The IOA session is ended.

Corrective Action: No action is required.

IOAD9AE INVALID RECORD FOUND IN ALC MEMBER memName- LINE lineNum

Explanation: The IOALLOC module is unable to continue its processing because of an incorrect member memName in line lineNum.

The IOA session is ended.

Corrective Action: No action is required.

IOAD9BE REQUESTED KEY keyName WAS NOT FOUND IN IOADSN/IOADSNL

Explanation: The IOALLOC module is unable to continue its processing because of a missing key in the IOADSN or IOADSNL members.

The IOA session is ended.

Corrective Action: No action is required.

IOAD9CE ALLOCATION FAILED FOR DDNAME : ddName

Explanation: The IOALLOC module is unable to continue its processing because the allocation of DDNAME ddName failed.

The IOA session is ended.

Corrective Action: No action is required.

IOAD9DE DD "DAALOCIN" IS MISSING OR CONTAINS A NON PDS DATASET

Explanation: The IOALLOC module is unable to continue its processing because the allocation of a DD NAME failed.

The IOA session is ended.

Corrective Action: No action is required.

IOAD9FE MEMBER memName WAS NOT FOUND IN THE "DAPARM" DD STATEMENT CONCATENATION

Explanation: The IOALLOC module is unable to continue its processing because the memName member is missing in the DAPARM DD concatenation.

The IOA session is ended.

Corrective Action: No action is required.

IOADB1E PARAMETER parm WAS NOT FOUND BY IOADEFP (CALLER: progName)

Explanation: The progName program failed to find the parm parameter.

The action fails. Additional error messages follow.

Corrective Action: Make sure that:

• The DAPARM dd statement points to the correct IOA.PARM library.
• The parm parameter is defined correctly in the DEFPARM member in IOA PARM.

IOADB2E IOADEFP FOR parm FAILED WITH RC=rc (CALLER: progName MCT: address)

Explanation: The IOADEFP service failed when it was requested to retrieve the value of the parm DEFPARM parameter.

The variables in this message are:

• parm - the name of the DEFPARM parameter
• rc - the return code
• progName - the name of the calling program
• address - the address of the IOA main control block

The action fails. Additional error messages follow.

Corrective Action: Contact BMC Customer Support for assistance.

IOADJ1E COMMAND IS NOT RECOGNIZED

Explanation: An invalid line command was issued.

Corrective Action: Correct the command.

IOADJ2E COMMAND CONFLICT

Explanation: A conflicting line command was issued. For example, a block was marked for copying, and an M (Move) command was then issued.

The system waits for the command to be corrected.

Corrective Action: Erase the conflicting line command.

IOADJ3E UNABLE TO OBTAIN ENOUGH STORAGE FOR EDITING THE MEMBER

Explanation: There is insufficient storage available to edit the requested member.

Access is denied.

Corrective Action: Contact your INCONTROL administrator.

IOADJ4I MEMBER SAVED

Explanation: This information message is issued when a member has been saved.

Corrective Action: No action is required.

IOADJ5I MEMBER NOT SAVED

Explanation: This information message is issued when the user exits the EDIT screen without editing the member.

Corrective Action: No action is required.

IOADJ6E MEMBER NAME HAS NOT BEEN SUPPLIED

Explanation: An edit command was issued, but the name of the member to be edited was not supplied.

Access is denied.

Corrective Action: Supply a member name.

IOADJ7E DSNAME HAS NOT BEEN SUPPLIED OR IS NOT ALLOCATED

Explanation: The library name was not supplied.

Access is denied.

Corrective Action: Supply a library name.

IOADJ8E BLOCK COMMAND INCOMPLETE

Explanation: In a block command (CC, MM, RR, DD), only one line was marked. Two lines must be marked.

The system waits for the command to be corrected.

Corrective Action: Complete the block definition.

IOADJ9E COPY/MOVE IS PENDING

Explanation: A block copy or move command was issued with a line or block marked, but with no target line specified.

The system waits for the command to be corrected.

Corrective Action: Identify the target line, using the command A (After) or B (Before).

IOADJAS INTERNAL ERROR

Explanation: An internal error has occurred.

Access is denied.

Corrective Action: Contact BMC Customer Support.

IOADJBI MEMBER NOT COPIED

Explanation: This information message is issued when a request to copy a member is cancelled.

Corrective Action: No action is required.

IOADJCE ACCESS DENIED TO THE REQUESTED LIBRARY AND/OR MEMBER

Explanation: A request was made to access a member, but the user is not authorized to access the member.

Access is denied.

Corrective Action: If you consider that you ought to be authorized to access the library or member, contact your INCONTROL security administrator.

IOADJDE WRONG PARAMETERS

Explanation: An internal error has occurred.

Access is denied.

Corrective Action: Contact BMC Customer Support.

IOADJEE NUMBER IS NOT ALLOWED

Explanation: An attempt was made to type numbers in a line command in which numbers are not allowed.

The system waits for the line command to be corrected.

Corrective Action: Remove the numbers from the line command.

IOADJFE CONFLICTING NUMBERS

Explanation: A block command was issued, but with different repetition, for example, RR4 and RR5.

The system waits for the block command to be corrected.

Corrective Action: Correct the block command so as to specify the same repetition.

IOADJGE THE REQUESTED MEMBER IS IN USE BY ANOTHER USER

Explanation: The user tried to edit a member, but that member is held by another user.

Access is denied.

Corrective Action: Try again later. If the problem persists, try to identify the user holding the member.