Messages CTD600 through CTD6xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

CTD646E PRINT PLAN FILE DOES NOT EXIST

Explanation: Attempt to enter the P (Print Control Option) failed. The Print Plan file was not yet created. Control-D allocates and builds the Print Plan file when it processes a Printing Mission. During this process, the Printing Mission status is BUILDING PRINT PLAN, and it is not possible to enter the Print Control Option until after the Print Plan file is created.

Request is rejected.

Corrective Action: Wait until the Printing Mission finishes building the Print Plan file, and then retry to enter the Print Control Option.

CTD647E PRINT CONTROL-IS VALID FOR PRINT MISSIONS ONLY

Explanation: The P (Print Control) option was specified for a mission that is not a Printing Mission. The P (Print Control) option may only be activated for Printing Missions.

Corrective Action: Specify an option which is valid for the required mission.

CTD649E CANNOT RERUN MISSION missionName ODATE date - TASK SUSPENDED

Explanation: A restart was attempted on a mission which was in SUSPENDED status. A SUSPENDED mission cannot be restarted.

The rerun order is rejected.

Corrective Action: Wait until the mission has finished and issue another rerun request.

CTD650S OPEN OF ACTIVE MISSIONS FILE FAILED. DDNAME "DAAMF"

Explanation: Open of Control-D Active Missions file failed (the DAAMF DD statement).

This is due to one of the following:

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

Corrective Action: Check the contents of the system log for additional messages which may clarify the picture, or logon again.

CTD651S READ ERROR ON CONTROL-D ACTIVE MISSIONS FILE. NOTIFY THE IOA ADMINISTRATOR

Explanation: I/O error while reading Control-D Active Missions file.

Possible causes are:

• 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 it is of a different version.
• Real I/O error.

Corrective Action: Check the contents of the system log for additional messages which may clarify the picture, or log on again.

CTD652S INTERNAL ERROR - INVALID REQUEST TO CTDUMS request

Explanation: Internal error. Invalid request to the CTDUMS Control-D internal program.

The function requested is not performed.

Corrective Action: Have your system programmer call BMC Customer Support.

CTD653E CANNOT action MISSION missionName ODATE odate - NOT HELD

Explanation: Result of DELETE or CHANGE commands. The missionName mission of the original scheduling date odate is not in HELD state and therefore cannot be deleted or changed.

Delete or change request ignored.

Corrective Action: Hold the mission using the H option. Wait until the REQUESTED HELD status is changed to HELD, and then you can perform the change or delete.

CTD654E CANNOT action MISSION missionName ODATE odate - ALREADY DELETED

Explanation: The missionName mission of the original scheduling date (odate) has already been deleted.

The user request is ignored.

Corrective Action: No action can be performed

CTD655E ACTIVE MISSIONS FILE IS IN USE, TRY AGAIN LATER

Explanation: Another user is currently updating the file. The file is temporarily in use by another user or by the Control-D monitor.

The requested action is not performed.

Corrective Action: Try again later.

CTD656E action OF MISSION missionName ODATE odate IGNORED - STATUS HAS CHANGED

Explanation: Result of HOLD (H), RERUN (R), FREE (F) or CHANGE (C) request for the missionName mission of the odate original scheduling date, the status of which has already been changed. While you were looking at the screen, another user or Control-D monitor changed the status of the mission, or the contents of the production parameters.

The requested action is ignored.

Corrective Action: Check the mission status and act accordingly.

CTD657E CANNOT action MISSION missionName ODATE odate - MAX CHANGES OVER, TRY AGAIN LATER

Explanation: Cannot carry out more actions on the missionName mission of the odate original scheduling date. The maximum number of requests for action has been exceeded. Control-D monitor must accept the requests before another action can be performed.

The user request is ignored.

Corrective Action: If the Control-D monitor is up, try again. If it is down, it should be brought up again.

CTD658S CANNOT action MISSION missionName ODATE odate - UNEXPECTED CODE FROM CTDUMS

Explanation: Unexpected code from the CTDUMS Control-D internal utility.

The user request is ignored.

Corrective Action: Have your system programmer call Customer Support.

CTD659I action OF MISSION missionName ODATE odate PERFORMED

Explanation: This information message displays the result of BMC DELETE (D), RERUN (R), CHANGE (C), FREE (F), HOLD (H), or BYPASS (B) command.

The missionName mission has been:

• DELETED
• REQUESTED RERUN
• REQUESTED CHANGE (save in Zoom screen)
• REQUESTED FREE
• REQUESTED HELD
• BYPASSED (the input conditions and/or the time limit for the mission)

Corrective Action: No action is required.

CTD65AI AUTO REFRESH EVERY num SECONDS - counter

Explanation: This information message displays the current AutoRefresh interval and counter value. It is displayed whenever the screen is in AutoRefresh mode to indicate that the screen display is being updated automatically at the specified frequency (every num seconds). The counter value indicates the number of times that the screen was refreshed.

Corrective Action: No action is required.

CTD65BI AUTO REFRESH CANCELED

Explanation: This information message indicates that AutoRefresh mode was terminated. AutoRefresh mode is cancelled by a user request, or if an attempt is made to activate AutoRefresh mode in an environment that does not support it.

For more information, see the description of AutoRefresh mode in the Online Facilities chapter in the Control-D and Control-V User Guide.

Corrective Action: No action is required.

CTD65CE INVALID AUTO REFRESH INTERVAL

Explanation: An invalid AutoRefresh interval was specified. The number of seconds specified for the interval in the AUTO command must be between 1 and 99.

AutoRefresh mode is not activated.

Corrective Action: Re-enter the AUTO command, followed by a number between 1 and 99.

CTD660E INVALID VALUE, USE "Y" OR "N"

Explanation: Invalid value specified in the field. The cursor points to the field that contains the invalid value.

Corrective Action: Select Y for yes, or N for no.

CTD661E AT LEAST ONE TASKTYPE MUST BE "Y"

Explanation: At least one tasktype must be Y.

Corrective Action: Mark at least one of the task types as Y.

CTD662E AT LEAST ONE MESSAGE TYPE MUST BE "Y"

Explanation: At least one message type must be Y. All of the Y/N options were marked N.

Corrective Action: Mark at least one of the message types Y.

CTD663E AT LEAST ONE OF THE FIRST TWO TYPES OF MISSION STATUS MUST BE "Y"

Explanation: At least one of the first two types of mission status must be Y. Both are marked N.

Corrective Action: Mark at least one of the first two types of mission status as Y.

CTD664S INTERNAL ERROR BEFORE CALLING CTDUMS

Explanation: Internal error.

The function requested is not performed.

Corrective Action: Have your system programmer call BMC Customer Support.

CTD665E CANNOT RERUN MISSION missionName ODATE odate - TASK NOT ENDED

Explanation: The missionName mission of the odate original scheduling date did not finish executing, therefore it cannot be rerun.

The rerun request is ignored.

Corrective Action: Try again later.

CTD666S INTERNAL ERROR - UNEXPECTED RETURN CODE FROM CTDTDWY

Explanation: Internal error. Invalid return code from the CTDTDWY Control-D internal program (Why screen).

Corrective Action: Have your system programmer call BMC Customer Support.

CTD667E "WHY" OPTION CAN BE USED ONLY ON TASK IN "WAIT SCHEDULE/PROCESS" STATE

Explanation: The WHY option (?) is used to determine the reason a task is waiting to be scheduled. It cannot be used unless the task is in the WAIT SCHEDULE or WAIT PROCESS state.

The user request is ignored.

Corrective Action: No action is required.

CTD668S INTERNAL ERROR - UNEXPECTED RETURN CODE FROM CTDTAPR rc

Explanation: Internal error. Invalid return code from the CTDTAPR Control-D internal program (Printing Mission Zoom screen).

Corrective Action: Have your system programmer call BMC Customer Support.

CTD669E ERROR ON ACTIVE MISSIONS FILE. CANNOT BUILD ZOOM SCREEN

Explanation: Result of the ZOOM (Z) command. Error in the contents of the Active Missions file.

Possible causes are:

• The Active Missions file has been corrupted, perhaps by incorrect usage of one of the Control-D user exits.
• An internal Control-D error occurred.

Corrective Action: Call your system programmer for assistance. A dump of the file will be needed to solve the problem.

CTD66AE "BYPASS" OPTION CAN BE USED ONLY ON MISSION IN "WAIT SCHEDULE/PROCESS"

Explanation: The "BYPASS" option is used for ignoring the conditions that prevent a mission from starting. The "BYPASS" option cannot be used unless a mission is in a WAIT SCHEDULE or WAIT PROCESS state.

Corrective Action: Cancel the "BYPASS" option.

CTD670S INTERNAL ERROR. CANNOT BUILD ZOOM SCREEN

Explanation: Internal Control-D error while building the Zoom screen.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

CTD671E CANNOT action MISSION missionName ODATE odate - IN REQUESTED CHANGE MODE

Explanation: A user tried to FREE or DELETE a task which is still in the REQUESTED CHANGE mode.

The request is ignored.

Corrective Action: Wait until the REQUESTED CHANGE status disappears and then try again.

CTD672E CANNOT SAVE MISSION. INSUFFICIENT SPACE IN MISSION RECORD - USE LESS DATA

Explanation: Additional data were added to the mission on the Zoom screen, and the message appears as a result of the SAVE command. When a mission order is placed on the Active Missions file, space is reserved for possible future addition of data by the user. This message appears whenever this space is exhausted.

New mission data are not saved.

Corrective Action: Try to delete some data in the Zoom screen. If you are trying to add ON statements, try to delete other ON statements. For OUT conditions, delete unnecessary OUT statements, and so on. Deletion of all SHOUT WHEN messages, usually releases enough space. If all these actions fail, delete the mission order, and re-issue it manually with the new data using the CLIST CTDMISRQ.

If the problem persists, consult BMC Customer Support.

CTD673E CANNOT action MISSION missionName ODATE odate - MISSION IN PROCESS

Explanation: Result of DELETE (D) request for the missionName mission of the odate original scheduling date, which is in process. You can only delete a mission that awaits scheduling, or that has finished executing (ended).

The request is ignored.

Corrective Action: Free the mission, let Control-D analyze it and bring it to the ENDED status.

CTD675E OPTION NOT SUPPORTED YET FOR THIS TYPE OF MISSION

Explanation: The Zoom option for this type of mission is not yet supported.

The requested Zoom action is not performed.

Corrective Action: No action is required.

CTD680E THERE ARE NO RESTORE REQUESTS FOR MISSION misName (TIMESTAMP=misTime)

Explanation: This error message indicates that no reports were assigned to the Restore Mission (misName).

The following variables are used in this message:

• misName - the name of the Restore Mission
• misTime - the time stamp of the Restore Mission

The Restore Mission terminates with a status of NOTOK.

Corrective Action: No action is required.

CTD682E RC=rc FROM CTMMEM. MISSION misName TIMESTAMP=misTime TERMINATED

Explanation: This error message indicates an error occurred during the processing of a Control-D SKL or JOB library that prevented the Restore Mission (misName) from continuing.

The following variables are used in this message:

• rc - the return code passed back from the program that was processing the library
• misName - the name of the Restore Mission
• misTime - the time stamp of the Restore Mission

The Restore Mission terminates with a status of NOTOK.

Corrective Action: Look in the IOA log for other messages to determine the cause of the failure. Call your INCONTROL Administrator.

CTD686E DSN dsn NOT IN CATALOG

Explanation: The requested DSN dsn is not in the catalog. Possible causes are:

• Control-M AutoEdit facility - failure to read a symbols member (%%GLOBAL statement, or %%LIBSYM %%MEMSYM statement).
• IOA Online facility - schedule, calendar or rule definition.
• New Day procedure - failure to read a calendar from the data set described by the DACAL DD statement.

The system action depends on the cause, as follows:

• AutoEdit facility - job submission stops.
• IOA Online facility - reading or updating of the table, calendar or rule is not performed.
• New Day procedure ends with errors.

Corrective Action: The appropriate response depends on the cause, as follows:

• AutoEdit facility - correct the JCL for the job and rerun it.
• Online facility - correct the library name and retry.
• New Day procedure - correct the New Day procedure and retry.

CTD688I RESTORE TASK STARTED.

Explanation: This information message indicates that the Control-D internal restore task has begun. This is the normal message that the application should issue when a restore task starts.

Corrective Action: No action is required.

CTD689E [[taskType memName] jobName|jobId orderId] MAXIMUM NUMBER OF MEMBERS/LINES IN MEMBER EXCEEDED

Explanation: There is insufficient memory to read a large member from the library.

The system action and appropriate user response depend on the circumstances at the time the message is issued, as follows:

• If this message was issued during the New Day procedure, the cause is failure to read a calendar from the data set described by the DCAL DD statement. In this case, job submission fails. Increase the REGION size or LOGON size, and try again.
• If this message was issued while you were using the Control-M AutoEdit facility, the cause is failure to read one of the following symbols members:
• a %%GLOBAL statement
• a %%LIBSYM %%MEMSYM statement

In this case, job submission fails. Increase the REGION size or LOGON size, and try again.

• If this message was issued while you were using the Control-M Online facility, the cause is failure to access a schedule or calendar definition. Increase the REGION size or LOGON size, and try again.
• If this message was issued while you were using the CTMTBUPD or CTMXRF Control-M utilities, the cause is failure to access a schedule definition. In this case, utility execution fails. Increase either the SLINMAX or the SCHDMAX utility control statements, as appropriate. For more information, see the INCONTROL for z/OS Utilities Guide.

Corrective Action: No action is required.

CTD691E INVALID PARAMETERS FOR RESTORE ANALYZE PROGRAM

Explanation: An invalid parameter was passed to the restore job. This message is produced by the last step of the restore job, which executes the CTDRSC program. CTDRSC analyzes the output of the restore process. The parameters passed to this program are wrong. For further details, see the INCONTROL for z/OS Administrator Guide.

The restore of the requested data sets will not be performed. The status of the Restore Mission will remain RESTORE IN PROCESS.

Corrective Action: Do the following:

1. Check the last step of the restore job which can be found on the library allocated to the DADJOB DD statement. This step executes the CTDRSC program, and has two parameters, timestamp and mission name. For the correct format of these two parameters, see the RSTDFDSS sample skeleton job in the Control-D SKL library, modify the JCL, and rerun the job. The status of the Restore Mission will then change to ENDED OK.
2. In order to prevent this problem from occurring again, modify the last step of the restore job which can be found on the library allocated to the DADSKL DD statement.

CTD693E CATEGORY=cat NOT FOUND IN MEMBER=memName LIBRARY=libName

Explanation: A mission in cat category that was specified in the mission order list has not been found in the memName member of libName library.

The indicated mission is not entered into the Active Mission file.

Corrective Action: Correct the mission order list and re-order the indicated mission.

CTD694E MISSION misName TIMESTAMP=misTime FAILED TO OPEN RESTORE UTILITY MESSAGES FILE

Explanation: The restore job executing the specified restore mission was unable to open the messages file of the invoked restore utility.

The variables in this message are:

• misName - the name of the restore mission
• misTime - the time stamp of the restore mission

The restore mission ends NOTOK.

Corrective Action: Check the additional messages issued from the restore job.

CTD695E NO PENDING RESTORE MISSION misName TIMESTAMP=misTime FOUND IN ACTIVE MISSION FILE

Explanation: The restore job intended for execution of the specified restore mission did not find that mission in the Active Mission file.

The variables in this message are:

• misName - the name of the restore mission
• misTime - the time stamp of the restore mission

This may occur because the restore mission was removed from the Active Mission file or was reset by the CTDRESET utility before the job finished.

The restore job only prints the restore utility log.

Corrective Action: Check the IOALOG.

CTD696E MISSION misName TIMESTAMP=misTime FAILED TO OPEN ACTIVE MISSION FILE

Explanation: The restore job executing the specified restore mission was unable to open the Active Mission file.

The variables in this message are:

• misName - the name of the restore mission
• misTime - the time stamp of the restore mission

The restore job only prints the restore utility log.

Corrective Action: Call your INCONTROL Administrator.

CTD696I ALL MISSIONS PROCESSED SUCCESSFULLY

Explanation: This information message is issued when terminating the selection and placing missions on the Active Missions file. This message appears even if no missions were placed on the Active Missions file.

This message is issued by:

• CLISTs that schedule missions manually
• New Day procedure

For more information, see the relevant section of the INCONTROL for z/OS Administrator Guide.

Corrective Action: No action is required.

CTD697S SEVERE ERROR IN PROCESSING MISSIONS - PROCESSING TERMINATED

Explanation: The processing of the missions ended with errors. There is at least one earlier message concerning the errors.

The New Day procedure or CLIST ends with a return code of 08.

Corrective Action: Check the previous error messages and correct accordingly. If necessary, correct the Date Control record manually to allow the next run of the New Day procedure. For more details, see the INCONTROL for z/OS Administrator Guide.

CTD698S UNABLE TO PROCESS ANY MISSION

Explanation: The CTDRRQ, CTDPRQ, CTDBRQ, or CTDSRQ module was unable to open the IOA Log file or DD name SYSPRINT. There is a prior message concerning the error.

The New Day procedure or CLIST ends with a return code of 12.

Corrective Action: Check the previous error message. Correct the error, then rerun the New Day procedure or CLIST.

CTD69AI NO MISSIONS WERE SCHEDULED DURING ORDERING REQUEST

Explanation: This information message indicates that the user ordered missions. However, the missions were not scheduled because the scheduling dates defined in the missions do not match the current working date.

Corrective Action: No action is required.

CTD69BE UNABLE TO ORDER OLD MIGRATION MISSION DEFINITION. UPDATE THE MISSION AND REORDER

Explanation: A migration mission with a definition that does not support multistage migration paths was ordered. The STAGE parameter must be specified for at least stage 01. Migration mission definitions that do not contain the STAGE parameter do not satisfy this requirement.

The migration mission is not ordered.

Corrective Action: Redefine the migration mission with the STAGE parameter and reorder the migration mission.

CTD69EE misname: ONE OR MORE MANDATORY FIELDS ARE MISSING IN ON CLASS/TRNCLASS STATEMENT

Explanation: Mandatory fields are missing in the ON CLASS/TRNCLASS statement in the specified mission, as defined in the WDN130 optional wish.

Corrective Action: Fix the decollation mission definition according to the WDN130 optional wish.

CTD69HW PENDING MISSION misName TIMESTAMP=misTime NOT FOUND IN AMF. ONE MORE ATTEMPT WILL BE PERFORMED.

Explanation: The restore job intended for execution of the specified restore mission did not find that mission in the Active Mission file.

The variables in this message are:

• misName - the name of the restore mission
• misTime - the time stamp of the restore mission

This warning message might be issued because the restore mission was removed from the Active Mission file or was reset by the CTDRESET utility before the job finished.

The restore job only prints the restore utility log. Ten attempts will be performed then message CTD695E will be issued.

Corrective Action: No action is required.