Messages FRM400 through FRM4xx

This group includes messages for the Control-M for z/OS and Control-D products.

FRM450S OPEN OF WORK FILE FAILED - DDNAME "DAJOBLST". PLEASE CHECK THE MESSAGES AND CODES MANUAL

Explanation: The New Day procedure was unable to open the file pointed to by the DAJOBLST DD name for update.

After reading the list of CDAM files to be deleted from the file pointed to by DAJOBLST, the New Day procedure empties the file and writes one record indicating that there are no more entries. Possible causes are:

• File not found on the disk.
• Incorrect security authorization.

Corrective Action: Determine the reason for the problem, and correct it. Reinstall Control-M/Restart.

FRM451I taskType taskName ODATE odate ORDERID orderId DELETED - MAXWAIT EXCEEDED

Explanation: This information message is issued during the New Day procedure. It indicates that a job or group entity has been deleted from the Active Jobs file because the MAXWAIT of the job or group entity was exceeded.

The MAXWAIT parameter sets a maximum limit to the time that a task can wait for execution. For more information, see the description of the MAXWAIT parameter in the Control-M for z/OS User Guide.

The variables in this message are:

• taskType - the type of task that was deleted

Valid values are:

• taskName - the name of the job or group entity that was deleted
• odate - the ODATE of the job or group entity that was deleted
• orderId - the order ID of the job or group entity that was deleted

The taskName job or group entity is removed from the Active Jobs file.

Corrective Action: No action is required.

FRM452I FORMATTING OF activeFile STARTED

Explanation: This information message indicates that the Control-M Active Jobs file (AJF) or the Control-D Active Missions file (AMF) is currently being formatted.

Corrective Action: No action is required.

FRM453S OPEN OF DATES CONTROL RECORD FAILED. DDNAME "DACHK"

Explanation: Open of Control-M or Control-D Date Control record failed in the DACHK DD statement). This error message is issued by the CTMFRM (Control-M) or CTDFRM (Control-D) program as part of the New Day procedure.

Possible causes are:

• The DACHK DD statement is missing.
• The data set (member) described by the DACHK DD statement is not the Control-M or Control-D Date Control Record.

Corrective Action: Correct the JCL for the New Day procedure.

FRM454E FORMAT (format_pgm) ALREADY RUN TODAY

Explanation: An attempt was made to run the New Day procedure twice in the same day. The New Day procedure issues format_pgm. This program should not run more than once a day.

Possible values of format_pgm:

• CTMFRM - formats the Active Jobs file (AJF) in Control-M
• CTDFRM - formats the Active Missions file (AMF) in Control-D

The AJF or AMF is not formatted, but the New Day procedure continues to execute other programs in the program list.

Corrective Action: Check why the New Day procedure is being run twice, and whether jobs or missions were accidentally ordered twice because the General Date Control Record was erroneously modified.

FRM455S LAST FORMAT DATE GREATER THAN ORIGINAL SCHEDULING DATE IN DATES CONTROL RECORD

Explanation: The last format date is later than the original scheduling date in the Control-M Date Control record or the Control-D Date Control record. The New Day procedure issues this message. For more details refer to the appropriate user guide.

New Day processing stops.

Corrective Action: Correct the Control-M or Control-D Date Control record, and run the New Day procedure again.

FRM456S OPEN OF activeFile FAILED. DDNAME "ddName "

Explanation: Open of the Control-M Active Jobs file (AJF) or the Control-D Active Missions file (AMF) defined in the ddName DD statement failed. The New Day procedure calls the program that issues this message.

In Control-M, ddName is DACKPT and activeFile is the Active Jobs file (AJF).

In Control-D ddName is DAAMF and activeFile is the Active Missions file (AMF).

Possible causes of this message:

• The ddName DD statement is missing.
• The data set described by the ddName DD statement is not the AJF or the AMF.
• The data set described by the ddName DD statement is the AJF or the AMF, but of another Control-M or Control-D monitor, or of a different version of Control-M or Control-D.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the New Day procedure, and rerun it.

FRM457S OPEN OF BACKUP FILE FAILED. DDNAME "DABKUP"

Explanation: Open of backup file for the Active Jobs file (AJF) or Active Missions file (AMF) defined in the DABKUP DD statement failed.

This error message is issued by the CTMFRM (Control-M) or CTDFRM (Control-D) program, which is usually activated as part of the New Day procedure.

Possible causes of this message are:

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

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the New Day procedure, and rerun it.

FRM458S ERROR IN activeFile, RECORD 0. SHOULD BE FORMAT OR FREE

Explanation: Record 0 of the activeFile file contains incorrect data.

This error message is issued by the CTMFRM (Control-M) or CTDFRM (Control-D) program, which is usually activated as part of the New Day procedure.

In Control-M activeFile is the Active Jobs file (AJF).

In Control-D activeFile is the Active Missions file (AMF).

Possible causes of this message are:

• activeFile is corrupt.
• The data set described by the DACKPT DD statement (Control-M) or the DAAMF DD statement (Control-D) is not activeFile but is very similar to it.

Program execution stops with a condition code of 08.

Corrective Action: Check the validity of the data set described by the DACKPT or DDAMF DD statement. If necessary, correct the JCL, and rerun the New Day procedure.

If activeFile is corrupt, use a standard copy utility, like IEBGENER, to copy activeFile, and send it to BMC Customer Support. If necessary, run the FORMCKP utility to reformat the Active Jobs file or the CTDFRAMF utility to reformat the Active Missions file. However, these utilities also erase all the jobs or missions in the respective files.

FRM459I activeFile IS RESTORED FROM BACKUP

Explanation: This information message indicates the beginning of a rerun of the New Day procedure after an earlier abend during the format of activeFile.

In Control-M, activeFile is the Active Jobs file (AJF).

In Control-D activeFile is the Active Missions file (AMF).

activeFile is restored from the appropriate backup file and processing continues normally.

Corrective Action: No action is required.

FRM45AI taskType memName ODATE odate OID=orderId CYCLIC ATTRIBUTE REMOVED - MAXWAIT EXCEEDED

Explanation: This information message indicates that the New Day procedure removed the cyclic attribute of the job to prevent further recycling. The cyclic job identified in the message was executing when the New Day procedure was being run. Therefore, it could not be removed from the Active Jobs file (AJF), although its MAXWAIT period had expired. To prevent further recycling of the job, its cyclic attribute is removed.

The job remains in the AJF with its changed taskType.

Corrective Action: No action is required.

FRM45BI taskType memName ODATE odate CYCLIC ATTRIBUTE REMOVED - MAXWAIT EXCEEDED

Explanation: This information message indicates that the New Day procedure removed the cyclic attribute of the job to prevent its further recycling. The cyclic job identified in the message was executing when the New Day procedure was being run. Therefore, it could not be removed from the Active Jobs file (AJF), although its MAXWAIT period had expired. To prevent further recycling of the job, its cyclic attribute is removed.

The job remains in the AJF with its changed task type.

Corrective Action: No action is required.

FRM45CE func OPERATION FOR "COM" FILE FAILED. RC=rc

Explanation: An internal error occurred in the CTDCIO internal module while the Active Mission file was being formatted.

The Active Mission file is not formatted.

Corrective Action: Note the values of func and rc and contact BMC Customer Support.

FRM460S DATE CONTROL RECORD IS EMPTY

Explanation: The DACHKDD statement describes an empty data set or member.

For more information, see the descriptions of NEW DAY processing in the Control-M and Control-D chapters of the INCONTROL for z/OS Administrator Guide.

Program execution stops with a condition code of 08.

Corrective Action: Correct the Control-M or Control-D Date Control Record and run the New Day procedure again.

FRM461S ERROR WHILE FORMATTING IOA CONDITIONS FILE

Explanation: I/O error while formatting the IOA Conditions file. Possible causes are:

• The data set described by the DARESF DD statement is not the IOA Conditions file.
• An I/O error occurred while reading the IOA Conditions file.

Program execution stops with a condition code of 08.

Corrective Action: Correct and run the New Day procedure again. In case of an I/O error, you may need to recreate the IOA Conditions file. This erases all the conditions from the file.

FRM462S INVALID LAST FORMAT DATE IN DATE CONTROL RECORD

Explanation: Invalid format of last format date in the Date Control Record. This message is issued by the CTMFRM or CTDFRM program, which is activated as part of the New Day procedure. The valid format is ddmmyy or mmddyy.

Possible causes are:

• Someone has modified the contents of the Date Control Record incorrectly.
• The record described by the DACHK DD statement is not the Control-M Date Control Record or the Control-D Date Control Record.

For more information, see the sections that describe NEW DAY processing in the Control-M and Control-D chapters of the INCONTROL for z/OS Administrator Guide.

Program execution stops with a condition code of 08.

Corrective Action: Do one or both of the following, as necessary:

• Correct the JCL for the Daily Subsystem, and rerun it.
• Correct the format date in the Date Control Record, and rerun the New Day procedure.

FRM463S INVALID ORIGINAL SCHEDULING DATE IN DATE CONTROL RECORD

Explanation: Invalid original scheduling date in the Date Control Record. This message is issued by the CTMFRM (Control-M) or CTDFRM (Control-D) program, which is activated as part of the New Day procedure. The valid format is ddmmyy or mmddyy.

Possible causes are:

• The record described by the DACHK DD statement is not the Control-M General Date Control Record or the Control-D General Date Control Record.
• Someone modified the contents of the General Date Control Record incorrectly.

See the sections that describe NEW DAY processing in the Control-M and Control-D chapters of the INCONTROL for z/OS Administrator Guide for more information.

Program execution stops with a condition code of 08.

Corrective Action: Do one or both of the following, as necessary:

• Correct the JCL for the New Day procedure and rerun it.
• Correct the original scheduling date in the General Date Control Record and rerun the New Day procedure.

FRM464S FILE ALLOCATED TO DDNAME "ddName " IS NOT YOUR activeFile

Explanation: The data set described by the ddName DD statement is not the file specified by activeFile.

In Control-M, ddName is DACKPT and activeFile is the Active Jobs file (AJF).

In Control-D ddName is DAAMF and activeFile is the Active Missions file (AMF).

Possible causes are:

• The data set described by the ddName DD statement is not the AJF or the AMF.
• The data set described by the ddName DD statement is the AJF or the AMF, but of another Control-M or Control-D monitor, or of a different version of Control-M or Control-D.

Program execution stops with a condition code of 08.

Corrective Action: Correct the problem in the data set name indicated by the specified DD statement, and run the New Day procedure again.

FRM465S FILE ALLOCATED TO DDNAME "DABKUP" IS NOT A BACKUP OF THE activeFile

Explanation: The data set described by the DABKUP DD statement is not a backup of activeFile.

In Control-M, activeFile is the Active Jobs file (AJF).

In Control-D activeFile is the Active Missions file (AMF). Possible causes are:

• The data set described by the DABKUP DD statement is not the AJF or the AMF.
• The data set described by the DABKUP DD statement is the AJF or the AMF, but of another Control-M or Control-D monitor, or of a different version of Control-M or Control-D.

Program execution stops with a condition code of 08.

Corrective Action: Correct the Control-M Date Control Record and rerun the affected procedure.

FRM466S NEED MORE MEMORY TO FORMAT activeFile

Explanation: There is not enough memory to format activeFile.

In Control-M, activeFile is the Active Jobs file (AJF).

In Control-D activeFile is the Active Missions file (AMF).

Program execution stops with a condition code of 08. Control-M and Control-D monitors will not start after this error.

Corrective Action: To enable monitors to start, increase REGION size and rerun the affected procedure.

FRM467I taskType memName ODATE odate OID=orderId DISREGARDED - MAXWAIT EXCEEDED

Explanation: The New Day procedure issues this information message to indicate that the MAXWAIT of a task was exceeded. The maximum waiting time for a task or mission is specified in the MAXWAIT parameter.

For more information, see MAXWAIT in the Control-M for z/OS User Guide or the Control-D and Control-V User Guide.

The task or mission is erased from the AJF or AMF. In the case of a task, the memName member of the odate original date is removed from the AJF.

Corrective Action: No action is required.

FRM468I FORMATTING OF activeFile ENDED

Explanation: This information message indicates that the New Day procedure finished formatting activeFile. This message is issued by the CTMFRM (Control-M) or CTDFRM (Control-D) program, which is activated as part of the New Day procedure.

In Control-M, activeFile is the Active Jobs file (AJF).

In Control-D activeFile is the Active Missions file (AMF).

Corrective Action: No action is required.

FRM469S OPEN OF IOA LOG FILE FAILED

Explanation: Open of IOA Log file failed. The message is produced by the New Day procedure. 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 or of a different IOA monitor.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL and run the Daily again.

FRM46AI memName ODATE odate DISREGARDED - MAXWAIT EXCEEDED

Explanation: This information message is issued by the Control-D New Day procedure. It indicates that the MAXWAIT of a job or mission has been exceeded.

The memName member is deleted from the Active Jobs file or Active Missions file.

Corrective Action: No action is required.

FRM470S ERROR WHILE FORMATTING THE activeFile, FILE WAS NOT FORMATTED

Explanation: An error occurred during formatting of activeFile. The New Day procedure issues this message.

In Control-M, activeFile is the Active Jobs file (AJF).

In Control-D activeFile is the Active Missions file (AMF).

Program execution stops with a condition code of 08.

Corrective Action: Look for a previous message that describes the type of error. Correct it and rerun the New Day procedure.

FRM475S DATE IN AMF FILE GREATER THAN CURRENT DATE

Explanation: The DATE field in the Active Mission file is incorrect because it is greater than the current date. This message is issued by the AMF formatting program during the NEWDAY procedure.

The NEWDAY procedure terminates.

Corrective Action: Perform one of the following actions:

• Reformat the Active Mission file using the CTDFRAMF utility.
• Fix the DATE field (YYMMDD format). Set the DATE to yesterday in block 0 of the Active Mission file.

FRM476S DATE IN AMF FILE WAS MORE THAN 28 DAYS AGO

Explanation: The Control-D monitor was inactive for more than 28 days. The DATE field in the Active Mission file differs from the current date by more than 28 days. This message is issued by the AMF formatting program during the NEWDAY procedure.

The NEWDAY procedure terminates.

Corrective Action: Perform one of the following actions:

• Reformat the Active Mission file using the CTDFRAMF utility.
• Fix the DATE field (YYMMDD format). Set the DATE to yesterday in block 0 of the Active Mission file.

FRM477S INVALID DATE IN AMF FILE

Explanation: The DATE field in the Active Mission file is incorrect. This message is issued by the AMF formatting program during the NEWDAY procedure.

The NEWDAY procedure terminates.

Corrective Action: Perform one of the following actions:

• Reformat the Active Mission file using the CTDFRAMF utility.
• Fix the DATE field (YYMMDD format). Set the DATE to yesterday in block 0 of the Active Mission file.

FRM481S OPEN OF WORK FILE FAILED - DDNAME "DAJOBLST". DELETE OF ARCHIVED SYSOUTS FAILED

Explanation: Open for the DAJOBLST file failed during the execution of the Control-M New Day procedure.

This error message is issued by the CTMDAS program, which is usually activated as part of the New Day procedure. The DAJOBLST DD statement is probably missing.

Program execution stops with a condition code of 16.

Corrective Action: Make sure that CTR (CONTROL-M/Restart) is set to Y in IOAPARM, in the PRODUCTS section.

FRM482S INIT OF RES FILE FAILED

Explanation: The New Day procedure failed to initialize the Control-M Resources file. An accompanying message identifies the reason for the failure.

The New Day procedure stops with an error, a return code of 12.

Corrective Action: Check the accompanying message to determine the reason for the problem, and correct the problem accordingly.

FRM484I FORMAT OF RESOURCE FILE HAS STARTED

Explanation: This information message indicates that the Control-M Resources file is currently being formatted. This procedure is usually part of the New Day procedure.

Corrective Action: No action is required.

FRM485I RESOURCE quantResource QUANTITY num WAS RELEASED BY CTMFRM

Explanation: This information message indicates that the CTMFRM format program cannot find the job that holds the specified quantity (num) of quantResource quantitative resources.

The system releases the quantitative resources for use by other jobs.

Corrective Action: No action is required.

FRM486E RESOURCE quantResource FOUND TO BE NOT BALANCED BY CTMFRM. CHECK AND ADJUST MANUALLY

Explanation: The number of quantResource quantitative resources currently in use exceeds the maximum defined for this resource. An error probably occurred during the monitor run on the previous day, since it is supposed to keep the resources balanced.

Corrective Action: Use the ADD, CHANGE and DELETE options on screen 4 to balance the Control-M Resources file.

FRM487I RESOURCE contResource IS HELD type - RELEASED BY FORMAT

Explanation: This information message indicates that the specified Control resource was released.

Valid values for type are:

The system releases the resource.

Corrective Action: No action is required.

FRM488I FORMAT OF RESOURCE FILE HAS ENDED

Explanation: This information message indicates that formatting of the new Control-M Resources file is complete and the resource is available.

Corrective Action: No action is required.

FRM489E OID=orderId FORMAT DETECTED MIT AND RESOURCE quantResource MISMATCH

Explanation: The quantResource Quantitative resource points to a job record (MIT) that is not its owner. Each resource in the Control-M Resources file points to the job record that owns it.

The system deletes the specified quantitative resource from the Control-M Resources file.

Corrective Action: No action is required.

FRM48AE FORMAT DETECTED MIT AND RESOURCE contResource MISMATCH

Explanation: The contResource Control resource points to a job record (MIT) that is not its owner. Each resource in the Control-M Resources file points to the job record that owns it.

The system deletes the specified Control resource from the Control-M Resources file.

Corrective Action: No action is required.

FRM48CI Preceding clear history did not complete. Process may run longer.

Explanation: During the AJF compression process, Control-M detected that the last clear process of the history file (HST), which followed the preceding AJF compression, did not successfully complete or did not run at all.

The AJF compression process continues, but the process might take longer than usual to complete.

Corrective Action: Usually the issue is resolved automatically by the next run of the history clear process, which either runs by default as part of the Control-M Daily run (step CLRHIST, program CTMHSC) or as a standalone utility (CTMHCLN). Make sure that the clear history process is included in the Control-M Daily run, or that the CTMHCLN utility runs on a daily basis. Make sure the process ends without errors.