Messages LNR0 through LNR0xx

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

LNR051S OPEN OF IOA LOG FILE FAILED

Explanation: Open of IOA Log file failed. This error message is issued by the IOALDNRS utility, which is used to load or create the Manual Conditions list. Possible causes are:

• The DALOG DD statement is missing.
• The file allocated to the DALOG DD statement is not the IOA Log file.
• The file allocated to the DALOG DD statement is the IOA Log file, but it is of a different version of IOA or of a different IOA monitor.

The IOALDNRS utility is not performed. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the JCL for the job.

LNR052S OPEN OF IOA MANUAL SYNC FILE FAILED

Explanation: Open of the IOA Manual Conditions Synchronization file failed. This error message is issued by the IOALDNRS utility, which loads or creates the Manual Conditions list. Possible causes are:

• The DANSINC DD statement is missing.
• The file allocated to the DANSINC DD statement is not the IOA Manual Conditions Synchronization file.
• The file allocated to the DANSINC DD statement is the IOA Manual Conditions Synchronization file, but it is of a different version or of a different IOA monitor.

The IOALDNRS utility terminates with a condition code of 08. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the JCL for the job.

LNR054I LOADING OF IOA MANUAL CONDITIONS FILE STARTED

Explanation: This information message indicates that loading of the IOA Manual Conditions file has started. The IOALDNRS utility will start collecting the Manual Conditions from the job orders on the Active Jobs file. These are all the prerequisite conditions which are suspected of requiring manual confirmation.

Corrective Action: No action is required.

LNR055I LOADING OF IOA MANUAL CONDITIONS FILE ENDED

Explanation: This information message indicates that the IOA Manual Conditions file has finished loading. The Manual Conditions file currently contains all the missing conditions for the job orders on the Active Jobs file.

Corrective Action: No action is required.

LNR056S IOA MANUAL CONDITIONS FILE WAS NOT LOADED

Explanation: The IOA Manual Conditions file was not loaded (the IOALDNRS utility). The utility output should contain a prior message which describes the cause of the problem.

Corrective Action: Correct the problem and rerun the utility.

LNR057S OPEN OF CONTROL-M ACTIVE JOBS FILE FAILED - DDNAME "DACKPT"

Explanation: Open of Control-M Active Jobs file failed (the DACKPT DD statement). The error message is issued by the IOALDNRS utility, which is used to load or create the Manual Conditions List, and is due to one of the following:

• The DACKPT DD statement is missing.
• The data set described by the DACKPT DD statement is not the Control-M Active Jobs file. The data set described by the DACKPT DD statement is the Control-M Active Jobs file, but of another Control-M monitor, or of a different version of Control-M.

The IOALDNRS utility will terminate with a condition code of 08. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the JCL for the job.

LNR058E FILE ALLOCATED TO DDNAME "DACKPT" IS NOT CONTROL-M ACTIVE JOBS FILE

Explanation: The file allocated to the DACKPT DD statement is not the Control-M Active Jobs file. This error message is issued by the IOALDNRS utility which is used to load/create the Manual Conditions List and may be due to one of the following:

• The file allocated to the DACKPT DD statement is not the Control-M Active Jobs file.
• The file allocated to the DACKPT DD statement is the Control-M Active Jobs file, but it is of a different version or of a different Control-M monitor.

The IOALDNRS utility will terminate with a condition code of 08. The IOA Manual Conditions file will not be loaded.

Corrective Action: Correct the JCL for the job.

LNR059E ACTIVE JOBS FILE IS BEING FORMATTED. PLEASE TRY AGAIN LATER

Explanation: The Active Jobs file is currently being formatted, which indicates that the New Day procedure is running. This error message is issued by the IOALDNRS utility (used to load or create the Manual Conditions List), which terminates with a condition code of 08. The IOA Manual Conditions file is not be loaded.

Corrective Action: Try again later. If the Control-D and Control-M New Day procedures start at the same time, you need to ensure that both procedures finish before running the IOALDNRS utility or the CTDLDNRS step. Use one of the following options:

• Set Control-D New Day time (DAYTIMED) long enough after Control-M New Day time (DAYTIME) to ensure that Control-M New Day is ended.
• Remove the CTDLDNRS step from the CTDNDAY procedure. Run the IOALDNRS utility after both Control-M and Control-D New Day procedures have finished.

LNR060W ACTIVE JOBS FILE IS EMPTY

Explanation: The IOA Manual Conditions file is not built. The Active Jobs file is empty. This error message is issued by the IOALDNRS utility which loads or creates the Manual Conditions List. No manual conditions are found because there are no job orders. The IOA Manual Conditions file will not be loaded.

Corrective Action: No action is required.

LNR061E FILE ALLOCATED TO DDNAME "DASINC" IS NOT THE IOA SYNCHRONIZATION FILE

Explanation: The data set described by the DASINC DD statement is not the IOA Conditions Synchronization file. This error message is issued by the IOALDNRS utility, which loads or creates the Manual Conditions List. Possible causes are:

• The file allocated to the DASINC DD statement is not the IOA Conditions Synchronization file.
• The file allocated to the DASINC DD statement is the IOA Conditions Synchronization file, but it is of a different version or of a different IOA monitor.

The IOALDNRS utility terminates with a condition code of 08. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the JCL for the job.

LNR062E FILE ALLOCATED TO DDNAME "DANSINC" IS NOT THE IOA MANUAL CONDS SYNC FILE

Explanation: The data set described by the DANSINC DD statement is not the IOA Manual Conditions Synchronization file. This error message is issued by the IOALDNRS utility, which loads or creates the Manual Conditions List. Possible causes are:

• The file allocated to the DANSINC DD statement is not the IOA Manual Conditions Synchronization file.
• The file allocated to the DANSINC DD statement is the IOA Manual Conditions Synchronization file, but it is of a different version or of a different IOA monitor.

The IOALDNRS utility terminates with a condition code of 08. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the JCL for the job.

LNR063E NO MORE PLACE IN MANUAL CONDS FILE FOR COND cond ODATE odate

Explanation: The Manual Conditions file is full. This error message is issued by the IOALDNRS utility which loads or creates the Manual Conditions List. No more conditions are added to the Manual Conditions List.

Corrective Action: The IOALDNRS utility reads the complete NRS file and processes it in memory. When processing completes successfully, the records are written to the file itself. Thus, message LNR063E indicates that no more space was available in the record in memory. Even though the IOAVERFY utility may show that there is still sufficient room in the file, this is because IOAVERFY only displays the initial status of the file. Increasing the size of the NRS file resolves the problem. See the NRSREC# parameter in the IOAPARM member of the IOA PARM library for details.

LNR064E INVALID PARAMETER:- parm

Explanation: Invalid parameter for the IOALDNRS utility. This error message is issued by the IOALDNRS utility, which is used to load or create the Manual Conditions List. For more details, please refer to the IOALNDRS utility in the INCONTROL for z/OS Utilities Guide. The IOALDNRS utility terminates with a condition code of 08. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the parameter syntax (the IOALDNRS utility).

LNR065E MISSING PARAMETER AFTER:- parm

Explanation: Missing subparameter after parm. This error message is issued by the IOALDNRS utility which is used to load or create the Manual Conditions List. For more details, please refer to the IOALDNRS utility in the INCONTROL for z/OS Utilities Guide. The IOALDNRS utility terminates with a condition code of 08. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the parameter syntax (the IOALDNRS utility).

LNR066E REDUNDANT PARAMETER: - parm

Explanation: Redundant parameter for the IOALDNRS utility. This error message is issued by the IOALDNRS utility which loads or creates the Manual Conditions List. For more details, please refer to the IOALDNRS utility in the INCONTROL for z/OS Utilities Guide. The IOALDNRS utility will terminate with a condition code of 08. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the parameter syntax (the IOALDNRS utility).

LNR067W CONTROLM YES PARAMETER WILL BE IGNORED.

Explanation: The CONTROLM YES parameter has been specified, but the indication in the IOAPARM Installation Parameters is that Control-M is not installed.

Corrective Action: No action is required.

LNR069E OPEN OF ACTIVE MISSIONS FILE FAILED - DDNAME "DAAMF"

Explanation: Open of Control-D Active Missions file failed (the DAAMF DD statement). This error message is issued by the IOALDNRS utility which is used to load/create the Manual Conditions List and is due to one of the following:

• The DAAMF DD statement is missing.
• Data set described by the DAAMF DD statement is not the Control-D Active Missions file.
• Data set described by the DAAMF DD statement is the Control-D Active Missions file, but of another Control-D monitor, or of a different version of Control-D.

The IOALDNRS utility terminates with a condition code of 08. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the JCL for the job.

LNR070E FILE ALLOCATED TO DDNAME "DAAMF" IS NOT THE EXPECTED ACTIVE MISSIONS FILE

Explanation: The file allocated to the DAAMF DD statement is not the Control-D Active Missions file. This error message is issued by the IOALDNRS utility which is used to load or create the Manual Conditions List and may be due to one of the following:

• The file allocated to the DAAMF DD statement is not the Control-D Active Missions file.
• The file allocated to the DAAMF DD statement is the Control-D Active Missions file, but of another Control-D monitor, or of a different version of Control-D.

The IOALDNRS utility terminates with a condition code of 08. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the JCL for the job.

LNR071E ACTIVE MISSIONS FILE IS FORMATTING NOW

Explanation: The Control-M Active Missions file is currently formatting, meaning that the Control-D New Day procedure is running. This error message is issued by the IOALDNRS utility which is used to load or create the Manual Conditions List. The IOALDNRS utility terminates with a condition code of 08. The IOA Manual Conditions file will not be loaded.

Corrective Action: Try again later.

LNR072E ACTIVE MISSIONS FILE IS DAMAGED - NOTIFY THE IOA ADMINISTRATOR

Explanation: The Active Missions file is probably damaged. The program stops executing with a condition code of 08.

Corrective Action: Check whether the file allocated to the DAAMF DD statement is the Control-D Active Missions file. If it is, it has been damaged - consult your IOA administrator or BMC Customer Support.

LNR073S OPEN DDNAME "SORTIN" FAILED

Explanation: Open of work file failed (the SORTIN DD statement) -- the IOALDNRS utility. This is due to one of the following:

• The SORTIN DD statement is missing.
• Data set described by the SORTIN DD statement cannot be opened for sequential read.

The program stops executing with a condition code of 08.

Corrective Action: Correct the JCL for the job.

LNR074S OPEN OF DDNAME "SORTOUT" FAILED

Explanation: Open of work file failed (the SORTOUT DD statement) - the IOALDNRS utility. This is due to one of the following:

• The SORTOUT DD statement is missing.
• The data set described by the SORTOUT DD statement cannot be opened for sequential read.

The program stops executing with a condition code of 08.

Corrective Action: Correct the JCL for the job.