|
|
|
|
|
This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.
Explanation: A sort program that has been activated internally by a report ended with an unexpected return code (rc).
The report stops executing with a condition code of 08 or 12.
Corrective Action: To clarify the reason, refer to the documentation for the sort program and to the sort messages of the job.
Explanation: Highlighted, unrollable message.
The Control-D monitor issued a MODIFY command for a Printing monitor to start processing a Printing Mission. The Printing monitor did not answer during the time frame defined by optional wish WD2344 (whose default is five minutes).
The problem can occur because the Printing monitor has a low priority and the computer is heavily loaded. Therefore, the Printing monitor does not get control during the time allowed for a response.
The Control-D monitor terminates the mission NOT-OK.
Corrective Action: Assign a higher priority, or change the performance group of the Printing monitor to provide better response time from this address space (or do both). In case of a batch printing mission, make sure that enough initiators are available for handling batch printing jobs. If this is impossible or undesirable, define a higher value for the time frame defined by optional wish WD2344 in the IOADFLTL member in the IOA PARM library or specify an appropriate time-out in the Printing Mission Definition screen (screen M.S).
Explanation: Highlighted, unrollable message.
Corrective Action: No action is required.
Explanation: Open of the file containing the User Date Control Record failed (the DACHK DD statement). Issued by the CTMCHK, CTDCHK, or CTBCHK program, which is usually activated by the New Day procedure.
Possible causes are:
The CTMCHK, CTDCHK, or CTBCHK program ends with errors.
Corrective Action: Correct the JCL for the job or CLIST.
Explanation: Invalid original scheduling date in User Date Control Record (positions 1 through 6). This date should be earlier than the current installation working date. The valid format is ddmmyy or mmddyy.
Valid formats are:
Possible causes are:
For more information, see the INCONTROL for z/OS Administrator Guide.
The New Day procedure ends with errors.
Corrective Action: Correct your Date Control Record (DD statement DACHK).
Explanation: The contents of the Date Control Record for this Daily are invalid.
Valid formats are:
This message usually indicates that the User Date Control Record was incorrectly modified. The date should be earlier than or equal to the original scheduling date (defined in positions 1 through 6).
The New Day procedure ends with errors.
Corrective Action: Correct the Date Control Record (the DACHK DD statement).
Explanation: Highlighted, unrollable message.
The difference between the current working date and the original scheduling date (positions 1 through 6 in the Date Control Record) is more than one day. The New Day procedure has not run for nnn days. A New Day procedure is expected to run once a day.
Common causes are:
The value of dailytype can be GENERAL for the New Day procedure or the job name of a regular User Daily job.
For User Daily jobs, processing continues. Missions are selected according to the RETRO parameter.
For the New Day procedure, this message appears highlighted on the operator console, together with the CTM427W or CTD427W and CTM428W or CTD428W messages. If the operator answers YES, processing continues, taking the RETRO parameter of each job into consideration. If the operator answers NO, the New Day procedure stops executing with an error message.
If a long period of Control-D inactivity (more than 28 days) is detected, message CTD42AW is issued before message CTD427W, and you must manually update the date in the Date Control Record (DDATEREC member) before proceeding.
Corrective Action: If the computer was IPLed with the wrong date, answer NO, correct the problem, and then activate the New Day procedure manually. Control-M or Control-D will not work until the problem is resolved.
Explanation: Highlighted, unrollable message.
The last run of the New Day procedure was more than 24 hours ago. This message appears together with the CHK426W, CTM426W, or CTD426W and CHK428W, CTM428W, or CTD428W messages. For more details, see the CHK426W message.
The General New Day procedure waits for the operator response.
Corrective Action: If the computer was IPLed with the wrong date, answer NO, correct the problem, and then activate the New Day procedure manually. Control-M or Control-D will not work until the problem is resolved.
Explanation: Highlighted, unrollable message.
The last run of the New Day procedure was more than 24 hours ago. This message appears together with the CHK426W, CTM426W, or CTD426W and CHK427W, CTM427W, or CTD427W messages. For details, see the CHK426W message.
The New Day procedure waits for the operator response.
Corrective Action: If the computer was IPLed with the wrong date, answer NO, correct the problem, and then activate the New Day procedure manually. Control-M or Control-D will not work until the problem is resolved.
Explanation: The CTMCHK, CTDCHK, or CTBCHK program ended with errors. It is activated as part of the New Day procedure. IOA Log should contain an earlier message about the error.
The New Day procedure finishes executing with a condition code of 08.
Corrective Action: Check the IOA Log for error messages. If necessary, manually correct the Date Control Record (date-3 and date-5) to allow the next run of the User Daily job. For details, see the INCONTROL for z/OS Administrator Guide.
Explanation: A long period of Control-D inactivity was detected. The last run of the New Day procedure was more than 28 days ago. This message appears after the CTD426W message and before the CTD427W message.
Corrective Action: Before proceeding, manually update the dates that appear in the DDATEREC member in the CTD PARM library and are pointed to by ddname DACHK in the Newday procedure.
Explanation: A previous run of the same New Day procedure probably abended.
The New Day procedure terminates with errors.
Corrective Action: Correct the Date Control Record and rerun the New Day procedure. As a result of the last abend, dates 2, 3 and dates 4, 5, in the Date Control Record are not identical - they should be. If you correct them to the values of date 3 or date 6, a rerun of the New Day procedure schedules all the jobs in the New Day procedure for the days after dates 2-5 until the date designated in date 1 (the current original scheduling date). Do not schedule the same job twice.
For more information, see the Control-M for z/OS User Guide or the Control-D and Control-V User Guide.
Explanation: This information message indicates that the CTMCHK, CTDCHK, or CTBCHK program, which is activated by the New Day procedure, started executing.
Corrective Action: No action is required.
Explanation: This information message indicates that the CTMCHK, CTDCHK, or CTBCHK program, which is activated by the New Day procedure, ended normally.
Corrective Action: No action is required.
Explanation: The current working date in the computer is before the last original scheduling date of this New Day procedure.
This message is issued by the New Day procedure as a result of incorrect dates in the Date Control Record. For more details, see the Control-M for z/OS User Guide or the Control-D and Control-V User Guide.
The New Day procedure stops executing with an error message.
Corrective Action: Correct the contents of the Date Control Record, and rerun the Daily. If this problem occurs under the New Day procedure, call your system programmer. The problem should be resolved immediately as the Control-M or Control-D monitor will not be able to operate. Check whether the computer has been IPLed with the correct date.
Explanation: The same New Day procedure has already been run today. The current working date in the computer is equal to the last original scheduling date - positions 1 through 6 in the Date Control Record (the DACHK DD statement).
For details, see the Control-M for z/OS User Guide or the Control-D and Control-V User Guide.
Processing terminates with a return code of 8.
Corrective Action: Check the result of the run carefully for possible errors. If the Control-M or Control-D monitor is up and running, there is no need to run the New Day procedure - it was probably started by accident. In any case, have your INCONTROL administrator look at the problem. It is possible that the computer was IPLed with the wrong date.
Explanation: The operator answered NO to the CHK428W, CTM428W, or CTD428W message.
The New Day procedure stops executing.
Corrective Action: Correct the problem (usually date related), and rerun the New Day procedure.
Explanation: The data set described by the DACHK DD statement is empty (the New Day procedure).
The New Day procedure terminates with errors.
Corrective Action: Correct the JCL for the job and rerun it.
Explanation: This information message indicates that the Control-D Communication file is almost full.
In this message, num is the number of free entries left in this file.
The printing of the reports will continue.
Corrective Action: At the earliest possible time, bring down Control-D, then follow these steps:
Explanation: The current print mission cannot obtain a free record in the communications file.
Each print mission requires one record in the COM file for communicating between the Control-D monitor and the print task. A free record is obtained before the print task is started released when it ends.
The print mission ends NOTOK.
Corrective Action: Increase the size of the COM file by increasing the value of the COMSIZE parameter in CTDPARM. You can do this using ICE, as follows:
You can now rerun the print mission.
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.
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:
Corrective Action: Correct the JCL for the New Day procedure.
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 are:
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.
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, see 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.
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 are:
Program execution stops with a condition code of 08.
Corrective Action: Correct the JCL for the New Day procedure, and rerun it.
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 are:
Program execution stops with a condition code of 08.
Corrective Action: Correct the JCL for the New Day procedure, and rerun it.
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:
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 the 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.
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 user action is required.
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.
Explanation: The DACHK DD statement describes an empty data set or member.
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: Correct the Control-M or Control-D Date Control Record and run the New Day procedure again.
Explanation: I/O error while formatting the IOA Conditions file.
Possible causes are:
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.
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:
For more information, see 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:
Explanation: Invalid original scheduling date in the Date Control Record. The valid format is ddmmyy or mmddyy.
Possible causes are:
This message is issued by the CTMFRM (Control-M) or CTDFRM (Control-D) program. These programs are activated as part of the New Day procedure.
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:
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:
Program execution stops with a condition code of 08.
Corrective Action: Correct the problem in the data set name indicated by the ddName DD statement, and run the New Day procedure again.
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:
Program execution stops with a condition code of 08.
Corrective Action: Correct the Control-M Date Control Record and rerun the affected procedure.
Explanation: There is not enough memory to format the activeFile file.
The New Day procedure issues this message.
In Control-M, activeFile is the Active Jobs file (AJF) or the History file (HST).
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, set REGION=0M and rerun the affected procedure. If the REGION is already set to 0M, then ensure that the MVS exit IEFUSI allows sufficient virtual storage memory to be allocated above the 16M line. For example, since each record of the above files requires 1024 bytes of storage, a file containing 200,000 records requires 200M of storage above the line.
Explanation: This information message indicates that the New Day procedure finished formatting the activeFile file.
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.
Explanation: An error occurred during formatting of the activeFile file.
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.
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:
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:
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:
Explanation: This information message indicates that a backup mission (or the CTDDELRP utility) is trying to synchronize with the Control-D monitor.
For an explanation of the synchronization process, see the MONA59I message.
Corrective Action: No action is required.
Explanation: This information message indicates that a backup mission or the CTDDELRP utility is trying to synchronize with the Control-D monitor.
The displayed timestamp is a hexadecimal representation of the time-of-day clock value used for synchronization. It is displayed for tracking and debugging purposes.
For an explanation of the synchronization process, see the MONA59I message.
Corrective Action: No action is required.
Explanation: The decollation task could not provide a timestamp during synchronization for the backup job, the CTDDELRP utility, or the CTVJAR utility.
Valid values for rc, and their explanations, are:
rc |
Explanation |
16 |
Error access the Active User file |
20 |
Internal error |
The backup job, the CTDELRP utility, or the CTVJAR utility fails.
Corrective Action: Do the following:
When the error occurs, perform the following steps:
Explanation: A migration file was opened for multistage migration but the migration file was formatted with an old compression table. A multistage migration mission stores log data about the last three migration stages in the SYSDATA record. If a migration file formatted with an old compression table is used, this data is lost.
The migration mission ends NOTOK.
Corrective Action: Reformat the migration file by unloading it by means of job CTDUFDUL and reloading it by means of job CTDUFRST from the Control-D JCL library.
Explanation: This information message indicates that the backup job, the CTDDELRP utility, or the CTVJAR utility waits for the decollation task to provide a timestamp.
Corrective Action: No action is required.
Explanation: While building a migration mission, the Control-D monitor found a request to migrate the CDAM name file from one OSS media to another OSS media, but this type of migration is not allowed.
This CDAM file is deleted from the list of CDAM files to be migrated.
Corrective Action: Change the migration path of the problematic migration mission.
Explanation: The open of the SYSIN DD statement failed. This message is produced by the ANALYZE step of the backup/migration job.
Possible causes are:
The requested backup or migration is not performed. The status of the Backup or Migration Mission is changed to ENDED NOTOK.
Corrective Action: Do the following:
Explanation: Open of the Active Missions file failed. This file is referenced by the DAAMF DD statement.
This message is produced by the ANALYZE step of the backup or migration job. This step executes the CTDBKC program, which analyzes the output of the backup or migration process.
Possible causes are:
Backup or migration of the requested data sets is not performed. The status of the backup or migration mission remains BACKUP or MIGRATE IN PROCESS. This status will change to ENDED OK after the backup or migration job is corrected and rerun.
Corrective Action: Do the following:
Explanation: where rc is the return code of the Active Mission file service.
Backup or migration job cannot update, in the Active Mission file, the status of the mission indicated in the message.
The mission remains in status IN PROCESS.
Corrective Action: Use the appropriate utility (BKPRESET or MIGRESET) to reset the mission status. If the problem recurs, prepare the IOA LOG and contact BMC Customer Support.
Parent Topic |