Messages CTD0 through CTD0xx

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

CTD000I Control-V GLOBAL INDEX utilityName STARTED

Explanation: This information message indicates that the utilityName Global Index utility started.

Corrective Action: No action is required.

CTD001E PLEASE FILL IN LIBRARY NAME

Explanation: The library name is missing. The LIBRARY field must contain data.

Corrective Action: Enter a name for the library.

CTD001I Control-V GLOBAL INDEX utilityName ENDED OK

Explanation: This information message indicates that the utilityName Global Index utility finished successfully.

Corrective Action: No action is required.

CTD001S UNABLE TO OPEN BUNDLE TRACKING FILE.

Explanation: The CTDTBTR (Bundle Tracking System screen) program failed to open the Bundle Tracking file.

The CTDTBTR program ends.

Corrective Action: Check the messages in the sysout of the program, and correct the problem accordingly. Return to the Bundle Tracking System screen (DT screen).

CTD002E PLEASE FILL IN MEMBER NAME

Explanation: Missing member name. The MEMBER field is obligatory (tree name).

Corrective Action: Fill in the member name.

CTD003E MEMBER IS NOT A VALID RECIPIENT TREE

Explanation: The MEMBER entered is not a valid Recipient Tree.

Corrective Action: Fill in a member name which is a valid Recipient Tree.

CTD004E LIBRARY AND MEMBER NAME MUST BE ENTERED

Explanation: This is one of two messages with the same ID, but different text.

LIBRARY and MEMBER specifications are missing. The LIBRARY and MEMBER fields are obligatory.

Corrective Action: Fill in the LIBRARY and MEMBER fields.

CTD004E INVALID DO= FUNCTION SPECIFIED

Explanation: This is one of two messages with the same ID, but different text.

The function specified in a DO statement is not valid.

The current utility stops.

Corrective Action: Correct the function name in the DO statement and rerun the job.

CTD005E MEMBER IS IN USE BY ANOTHER USER

Explanation: This is one of two messages with the same ID, but different text.

Another Control-D user is currently working on the member tree. Two users cannot work on the same member simultaneously.

Corrective Action: Try again later.

CTD005E INVALID PARAMETER: parm

Explanation: This is one of two messages with the same ID, but different text.

The parm input parameter for the CTVUPGDB or CTDDBPRT utility is not valid.

The utility stops.

Corrective Action: Correct the invalid input parameter and rerun the job.

CTD006E REDUNDANT PARAMETER: parm

Explanation: The parm input parameter for the CTVUPGDB or CTDDBPRT utility was already specified. The same parameter is specified twice.

The utility stops.

Corrective Action: Delete the extra input parameter from the JCL and rerun the job.

CTD006S MEMBER IS EMPTY

Explanation: The designated Recipient Tree member does not contain any data.

Corrective Action: Delete this member from the library, then enter this member again.

CTD007E ERROR IN PARAMETERS: FODATE IS HIGHER THAN TODATE

Explanation: The specified starting order date FODATE is later than the specified ending order date TODATE.

The utility stops.

Corrective Action: Fix the value of either FODATE or TODATE in the JCL and rerun the job

CTD007S INSUFFICIENT STORAGE TO LOAD RECIPIENT TREE MEMBER

Explanation: Insufficient storage to load the member (the tree).

Corrective Action: Do one of the following:

• Log on again using a larger SIZE parameter.
• If you are using many Control-D screens concurrently, exit some of them using the END command.

CTD008E PLEASE FILL IN A VALID OPTION - "Y" OR "N"

Explanation: This is one of two messages with the same ID, but different text.

Invalid option. The valid options are:

• Y (Yes)
• N (No)

Corrective Action: Select Y or N.

CTD008E INVALID DATE SPECIFIED: date

Explanation: This is one of two messages with the same ID, but different text.

Either the starting order date FODATE or the ending order date TODATE is invalid. The correct format is DD/MM/YY.

In this message, date is the problematic FODATE or TODATE date.

The utility stops.

Corrective Action: Correct the value of the incorrect ODATE parameter and rerun the job.

CTD009E ONE (AND ONLY ONE) EXIT OPTION MUST BE MARKED AS "Y"

Explanation: Two exit options are marked as Y (Yes). Only one EXIT OPTION field can be marked as Y.

Corrective Action: Mark Y or N in one of the EXIT OPTION fields.

CTD00AE MEMBER IS NOT A VALID APPROVAL TREE

Explanation: The MEMBER entered is not a valid Approval Tree.

Corrective Action: Fill in a member name which is a valid Approval Tree.

CTD00BE INVALID PARAMETERS

Explanation: A parameter in the SYSIN stream for the CTVUPGDB utility is invalid. The error is detected during analysis of input parameters.

The CTVUPGDB utility stops.

Corrective Action: Check other messages for the utility to identify and fix the problem, and rerun the CTVUPGDB utility.

CTD00CE THE PARAMETER parm MUST BE SPECIFIED

Explanation: The parm input parameter for the CTVUPGDB utility is missing. The CTVUPGDB utility requires the parm parameter.

The CTVUPGDB utility stops.

Corrective Action: Insert the missing parameter in the JCL and rerun the job.

CTD00DE ERROR OPENING GLOBAL INDEX DATABASE. RC= rc

Explanation: The current utility or IOA application server could not open the Global Index database.

Global Index processing stops.

Corrective Action: Do the following:

• If rc is 0 (meaning OK), examine the file names for the DAGIR and DAGIRI DD statements. Correct them, if necessary, and rerun the job.
• If rc is not 0, for possible return code values and their meanings, see:
  • if the Global Index is an IOA Access Method file, the GIX010E message
  • if the Global Index is a DB2 database, the CTDGI0S message
• Examine the IOA log for messages clarifying the error.
• Correct the problem, and rerun the job.
• If the problem persists, contact your INCONTROL administrator.

CTD010S THE REQUESTED ENTRY NAME WAS NOT FOUND

Explanation: The requested recipient name for this level was not found in the tree. The Recipient Tree may contain hundreds, or thousands, of report recipients. To directly display a specific recipient in the tree, fill in the recipient name, or name prefix, next to the appropriate level.

Corrective Action: Enter a new recipient name at this level, or at some other level. If the recipient name is still not found, enter the tree without entering a recipient name, and use the FIND command to find the requested recipient.

CTD011S INSUFFICIENT STORAGE TO BUILD APPROVAL TREE MEMBER

Explanation: There is insufficient storage to build the Approval Tree member.

Corrective Action: Do one of the following:

• Log on again using a larger SIZE parameter.
• If you are using many Control-D screens concurrently, exit some of them using the END command.

CTD012S INTERNAL PROGRAM ERROR. NOTIFY THE IOA ADMINISTRATOR

Explanation: Internal Control-D error while processing Recipient Tree.

Possible causes are:

• The member requested is not a Recipient Tree (although its structure is very similar to one).
• There is an internal Control-D error.

Corrective Action: Use the following procedure to correct this problem:

1. Check the IOA log for other messages to determine the cause of the failure.
2. Fix the Recipient Tree
3. Rerun the process that issued the message
4. If the problem persists, collect all information related to the cause of the message and contact BMC Customer Support

CTD013E PLEASE ENTER A VALID OPTION

Explanation: An invalid option has been entered.

Valid options are:

• D - delete
• I - insert
• S - add synonym
• F - see or hide parent

Corrective Action: Enter a valid option.

CTD014E PLEASE ENTER A VALID LEVEL

Explanation: The Recipient Tree level is invalid. The Recipient Tree level must be a two-character code as shown on the third line of the screen.

Corrective Action: Enter a valid Recipient Tree level.

CTD015E PLEASE ENTER A VALID NAME

Explanation: The recipient name is invalid. The recipient name must be unique in the tree. It can be up to 8 characters. Embedded blanks are not allowed.

Corrective Action: Enter a valid recipient name.

CTD016E PLEASE ENTER A VALID SYNONYM

Explanation: The synonym is invalid. Synonyms can be up to 20 characters. Embedded blanks are allowed.

Corrective Action: Enter a valid synonym.

CTD017E PLEASE ENTER A VALID PARENT NAME

Explanation: The parent name is invalid. The parent of the current recipient can be up to 8 characters. Embedded blanks are not allowed.

Corrective Action: Enter a valid parent name.

CTD018E PLEASE ENTER A VALID SELECTION VALUE (Y/N)

Explanation: The level selection value option is invalid. Valid selection values are:

• Y - display recipients of the level
• N - do not display recipients of the level

Corrective Action: Enter either Y or N.

CTD019E AT LEAST ONE OF THE SELECTIONS MUST BE "Y"

Explanation: None of the level selection values are marked as Y. At least one of the level selection values must be Y.

Corrective Action: Enter Y for one of the level selections.

CTD020E RECIPIENT NAME NOT ENTERED IN ENTRY SCREEN

Explanation: The NEXT command was entered but no recipient has been specified in the Entry Panel.

Corrective Action: Locate the recipient name using the FIND command.

CTD021E BOTTOM OF DATA REACHED

Explanation: The bottom of the Recipient Definition Tree screen has been reached while performing a NEXT command.

Corrective Action: Use the scrolling conventions to scroll backward and forward.

CTD022I NEXT NAME FOUND

Explanation: This information message indicates that the recipient specified in the entry panel was found after the NEXT command and the recipient can be found at the top of the screen.

Corrective Action: No action is required.

CTD023E CTVGDB FAILED RC= rc

Explanation: The CTVGDB routine invoked by CTVUPGDB ended with errors.

CTVUPGDB issues this message whenever the CTVGDB routine it invokes ends with a return code other than 0.

Possible values for rc from CTVGDB, and their meanings, are:

CTVUPGDB ends with a return code of 08.

Corrective Action: Check the meaning of the return-code from CTVGDB to identify and fix the problem, and rerun the job. If necessary, contact your INCONTROL administrator.

CTD023I NEXT NAME FOUND, BUT THIS LEVEL IS NOT BEING DISPLAYED

Explanation: This information message indicates that the recipient name found by the NEXT command cannot be displayed because its level is specified as N in the level selection line.

Corrective Action: Enter Y in the level selection line.

CTD024E PLEASE ENTER THE PARENT LEVEL, OR ERASE THE PARENT NAME

Explanation: This is one of two messages with the same ID, but different text.

The parent name has been entered, but the parent level is missing. The parent level is obligatory with the parent name.

Corrective Action: Enter the parent level, or erase the parent name.

CTD024E parm PARAMETER INVALID. ONLY YES OR NO IS VALID

Explanation: This is one of two messages with the same ID, but different text.

The value of the parm input parameter is invalid. The value of the parm parameter must be YES or NO.

The current utility stops.

Corrective Action: Fix parm in the JCL and rerun the utility.

CTD025E PLEASE ENTER THE PARENT NAME, OR ERASE THE PARENT LEVEL

Explanation: The parent level has been entered, but the parent name is missing. The parent name is obligatory with the parent level.

Corrective Action: Enter the parent name, or erase the parent level.

CTD025W MAXIMUM NUMBER OF PROCESSED INDEXES procIndex REACHED. PROCESSING STOPPED

Explanation: The CTVUPGDB utility tried to add another main index to the Global Index database when it had already added the maximum number for this run. The MAXINDX parameter defines the maximum number of indexes that may be added to the Global Index database in each run of the CTVUPGDB utility.

The utility adds MAXINDX main indexes and ends with a return code of 04. Other indexes will be added during the next run of the CTVUPGDB utility.

Increase the value of the MAXINDX parameter and run the CTVUPGDB utility again.

Corrective Action: No action is required.

CTD026E parm PARAMETER INVALID. ONLY YES, NO OR ALL IS VALID

Explanation: The value of the parm input parameter is invalid. The value of the parm parameter must be YES, NO, or ALL.

The current utility stops.

Corrective Action: Correct the parm input parameter in the JCL, and rerun the utility.

CTD026S OPEN OF MISSIONS ORDER LIST FILE FAILED. DDNAME = ddName

Explanation: The New Day procedure issues this message when open of the mission order list file fails (the ddName DD statement).

For more information, see the sections describing report decollating, printing, backup and restore missions in the INCONTROL for z/OS Administrator Guide.

Possible causes are:

• The ddName DD statement is missing.
• The data set (member) described by the ddName DD statement does not exist.

Processing of the mission order list terminates with a return code of 08.

Corrective Action: Call your INCONTROL administrator. After the problem is solved, rerun the job.

CTD027E JOBID PARAMETER INVALID. SHOULD BE Jnnnnn or Jnnnnnnn

Explanation: The JOBID input parameter is invalid. The format of the parameter name must be the character J followed by five or seven digits.

The utility stops.

Corrective Action: Correct the JOBID input parameter in the JCL, and rerun the utility.

CTD027S UNABLE TO LOAD MODULE modName

Explanation: Loading of the modName module failed.

Possible causes are:

• The IOA Load library is not in the load modules search list.
• There is not enough memory to load the module.
• The modName module does not exist in the Load library.
• The IOA Load library has been updated while you were working and the position of the modName module has changed.

The function requested is terminated.

Corrective Action: Look on the system log for additional messages related to the problem.

Try one of the following:

• If the IOA Load library is not in the search list, add a STEPLIB DD statement to the library.
• If the loading failed because of lack of memory do one of the following:
  • For batch jobs, increase the REGION size.
  • For TSO, try to logon again using a larger SIZE parameter.
  • If you are using many IOA screens concurrently, try to exit a few using the END command. This can release memory which is used by the screens.
• If the Load library has been modified and you are working under TSO, try to log on again. If you are working under ROSCOE, you may have to shut down ROSCOE and bring it up again. If the IOA Load library is in the Linklist, a refresh to the LLA is needed.

CTD028S MAXIMUM NUMBER OF MISSION ORDER CARDS HAS BEEN EXCEEDED. DDNAME = ddName

Explanation: The New Day procedure issues this statement when the ddName DD statement contains more than 500 mission order list statements.

For more information, see the sections describing report decollating, printing, backup and restore missions in the INCONTROL for z/OS Administrator Guide, and see also the sections describing New Day processing.

Processing of the mission order list terminates with a return code of 08.

Corrective Action: Ask the INCONTROL administrator to break the New Day procedure into more steps, with each step processing a maximum of 500 missions in the mission order list. After the problem is solved, rerun the New Day procedure.

CTD028W INDEX EXISTS IN GLOBAL INDEX DATABASE, USE FORCE PARAMETER TO ADD IT AGAIN

Explanation: The CTVUPGDB utility is trying to add an index that is already in the Global Index database. The CTD029I message, which follows the current message, provides details about the index that caused the error.

The index is not processed.

Corrective Action: To replace values in an existing index, run the CTVUPGDB utility with the FORCE input parameter set to YES.

CTD029I USER userName, REPORT reportName, JOBNAME jobName, JOBID jobId, ODATE odate

Explanation: This information message provides detailed information about the situation that caused the CTD028W message.

Corrective Action: No action is required.

CTD029S INTERNAL ERROR IN CTDCMI

Explanation: Internal error in the CTDCMI module.

Possible error situations include:

• CLISTs that schedule missions manually - for more information, see the INCONTROL for z/OS Administrator Guide
• New Day procedure - for more information, see the INCONTROL for z/OS Administrator Guide
• Force or Order in the Control-D Mission Definition screen
• when Control-M orders a Job Scheduling Table in which the CATEGORY field was already filled in

The Active Missions file is not updated. The New Day procedure ends with the return code 08.

Corrective Action: Collect the produced trace and contact BMC Customer Support.

CTD030S MISSION ORDER LIST IS EMPTY. DDNAME = ddName

Explanation: The ddName DD statement does not contain any mission order list statements. This message is issued by the New Day procedure.

For more information, see the INCONTROL for z/OS Administrator Guide sections on report decollating, printing, backup, and restore missions, and see also the sections describing New Day processing.

Processing of the mission order list terminates with return code 04.

Corrective Action: Add missions to be processed to the mission order list and rerun the job.

CTD031E MEMBER memName NOT FOUND

Explanation: The memName member is not in the library. Look for additional messages containing the library name or the DD statement.

This message is produced in one of the following components of Control-D:

• In the New Day procedure, in one of the following cases:
  • The requested mission name is not in library or DD name. For example, when the following statements are in a file referenced by the DAPRTLST DD statement of the CTDNDAY procedure:

    290988 CTD.PROD.PRTMIS MORNING1 *FORCE

    290988 *INPUTMORNING1 *FORCE

    If the MORNING1 member is not in the CTD.PROD.PRTMIS library, the CTM680E message is produced. If the MORNING1 member is not in the data set described by the INPUT DD statement, the CTM680E message is produced. See mission scheduling in the INCONTROL for z/OS Administrator Guide.

  • A Generic User Name List was coded, but the member name for this list was not in the data set described by the DAGENUSR DD statement. For more information, see the Control-D and Control-V User Guide.
  • A calendar to be read from the data set described by the DACAL DD statement was specified.
• During manual scheduling of a mission using the following CLIST CTDMISRQ:
  • The requested mission name is not in the library. For example, during manual scheduling of a Printing Mission with the following parameters:

    PRINT MISSIONS LIBRARY ====> CTD.PROD.PRTMIS

    MISSION NAME ====> MORNING1

    If the MORNING1 member is not found in library CTD.PROD.PRTMIS, the CTM680E message is produced.

  • A Generic User Name List was coded, but the member name for this list was not in the data set described by DD statement DAGENUSR. For more information, see the Control-D and Control-V User Guide.
  • A calendar was specified to be read from the data set described by the DACAL DD statement.
  • During an attempt to schedule a decollating mission using the CATEGORY Control-M Job Production Parameter, the memName member in the Control-D Report Decollating Mission library was not found. For more information, see the CATEGORY basic scheduling parameter in the Control-M for z/OS User Guide.

The system action depends on the component that issued the message, as follows:

• New Day procedure - The mission is not placed on the Active Missions file. Processing of the other missions continues.
• Scheduling a mission manually using CLISTs - The mission is not placed on the Active Missions file.
• Control-M - The job is placed on the Active Jobs file, but the decollating mission is not placed on the Active Missions file.

Corrective Action: The correct response depends on the component that issued the message, as follows:

• New Day procedure -
  • If the requested mission name is not found in the library or DD name, determine the correct name of the mission, and add this mission to the library, if necessary. Use the appropriate CLIST to schedule the mission manually.
  • If the Generic User Name List member is not found, determine the correct name of the member, and add this member to the library, if necessary. Use the appropriate CLIST to schedule the mission manually.
  • If the calendar member is not found, determine the correct name of the calendar, and add this member to the library if necessary. Use the appropriate CLIST to schedule the mission manually.
  • If the error occurred during scheduling of a mission manually using CLISTs, take the same action as for A.
• If the error occurred in Control-M, the member is not in the library. Add a decollating mission with the name of the member displayed in the message to the Decollating Mission library, or erase the CATEGORY screen entry from the Control-M Scheduling Definition. Then schedule this job using the CTDMISRQ CLIST.

CTD031I TO GLOBAL INDEX DATABASE WERE ADDED: reportsQuantity REPORTS, indexQuantity INDEXES, indexValueNum INDEX VALUES

Explanation: This information message describes data that was added to the Global Index database.

Corrective Action: No action is required.

CTD032E ERROR IN CARD: text

Explanation: This message displays the erroneous data card referred to by the message CTD145E.

Corrective Action: No action is required.

CTD033E INVALID ORIGINAL SCHEDULING DATE

Explanation: The original scheduling date in this mission order list statement is in error. The New Day procedure issues this message.

For more information, see the sections on report decollating, printing, backup and restore missions in the INCONTROL for z/OS Administrator Guide), and see also the sections on New Day processing.

This invalid mission order list statement is bypassed. Other valid mission order list statements are processed. The New Day procedure ends with a return code of 04.

Corrective Action: Correct faulty mission statements, and rerun the New Day procedure.

CTD034E ONE OR MORE MISSIONS ENDED WITH ERRORS

Explanation: One or more mission order list statements is invalid. The New Day procedure issues this message, if at least one CTD032E message was previously issued.

For more information, see the sections on report decollating, printing, backup and restore missions in the INCONTROL for z/OS Administrator Guide, and see also the sections on New Day processing.

The New Day procedure ends with a return code of 04.

Corrective Action: Correct faulty mission statements, and check for any other error messages relating to the New Day procedure. After fixing any problems, rerun the New Day procedure.

CTD034S INTERNAL ERROR CREATING TABLE tableName

Explanation: An internal error occurred in the CTVUPGDB utility. CTVUPGDB did not find the SYSDATA entry in the internal table.

The CTVUPGDB utility ends with a return code of 8.

Corrective Action: Contact your INCONTROL administrator.

CTD035E INDEX tableName HAS INCORRECT LENGTH

Explanation: The CTVUPGDB utility tried to add a path that was already in the Global Index database with different length parameters. This message occurs during an attempt to change the length of the index value in the definition of the decollation mission for a path that is already in the Global Index database.

CTVUPGDB continues without adding the values in the indicated path to the Global Index database.

Corrective Action: Change the length of the index value in the definition of the decollation mission that is causing the incorrect path or delete the old path from the Global Index database.

CTD036I GLOBAL INDEX HOUSEKEEPING UTILITY STARTED

Explanation: This information message indicates that the CTVGICL Global Index housekeeping utility started.

Corrective Action: No action is required.

CTD037I GLOBAL INDEX HOUSEKEEPING UTILITY ENDED

Explanation: This information message indicates that the CTVGICL Global Index housekeeping utility ended.

Corrective Action: No action is required.

CTD038I SEARCHING THE ACTIVE AND MIGRATED USER FILES

Explanation: This information message indicates that the CTVGICL Global Index housekeeping utility started searching active and migrated user files. Use this message to calculate how long each stage of the utility takes.

Corrective Action: No action is required.

CTD039I DELETING VSA ENTRIES

Explanation: This information message indicates that the CTVGICL Global Index housekeeping utility started deleting VSA entries from the Global Index database. Use this message to calculate how long each stage of the utility takes.

Corrective Action: No action is required.

CTD041S SMFWTM RETURNED RC= 4 - SMF RECORD TOO LONG

Explanation: Highlighted, unrollable message.

Control-D attempted to write an SMF record which could not fit completely in an SMF data set.

The user modified Control-D exit CTDX006, but moved an incorrect value to the SMFLEN field (DSECT CTDUSMF). This field contains the length of the SMF record.

The SMF record is not written, but Control-D continues processing. Control-D sets an internal indication that a permanent error is present on SMF recording, and will not continue to attempt SMF recording. From this point on, instead of writing to SMF, the SMF049I message is written to the IOA Log. This log message is a replacement for SMF recording, and can be entered into SMF after the problem is fixed.

Corrective Action: Correct the problem in CTDX006, assemble and link-edit this exit, and bring down Control-D. When Control-D is brought up again, SMF recording will resume.

CTD042I PATH DELETED: pathName

Explanation: This information message indicates that the CTVGICL Global Index utility deleted the specified path from the Global Index database.

Corrective Action: No action is required.

CTD042S SMFWTM RETURNED RC= 8 - SMF RECORD TOO SHORT

Explanation: Highlighted, unrollable message.

Control-D attempted to write an SMF record which is smaller than 18 characters long.

The user modified the Control-D Exit CTDX006, but moved an incorrect value to the SMFLEN field (DSECT CTDUSMF). This field contains the length of the SMF record.

The SMF record is not written, but Control-D continues processing. Control-D sets an internal indication that a permanent error is present on SMF recording, and will not continue to attempt SMF recording. From this point on, instead of writing to SMF, the SMF049I message is written to the Control-D log. This log message is a replacement for SMF recording, and can be entered into SMF after the problem is fixed.

Corrective Action: Correct the problem in CTDX006, assemble and link-edit this exit, and bring down Control-D. When Control-D is brought up again, SMF recording will resume.

CTD043E ERROR IN DELPATH FOR pathName RC rc

Explanation: The DELPATH Global Index function could not delete the specified path. CTVGICL invokes the DELPATH function to delete paths.

DELPATH skips the path that caused the error and continues to delete the next path.

Corrective Action: This error message may be issued because the PATH to be deleted is in use when DELPATH tries to delete it. Check other messages for the job to identify and fix any errors. For possible return code values and their meanings, see the CTD010E message. Rerun the CTVGICL utility.

CTD043S SMFWTM RETURNED RC= 16 - SMF IS NOT ACTIVE

Explanation: Highlighted, unrollable message.

Control-D attempted to write an SMF record, but SMF is not active.

The SMF record is not written, but Control-D continues processing. Control-D sets an internal indication that a permanent error is present on SMF recording, and will not continue to attempt SMF recording. From this point on, instead of writing to SMF, the SMF049I message is written to the IOA Log. This log message is a replacement for SMF recording, and can be entered into SMF after the problem is fixed.

Corrective Action: Initiate SMF recording, then bring down Control-D. When Control-D is brought up again, SMF recording will resume.

CTD044E parmName PARAMETER INVALID. SHOULD BE AFTER PATH PARAMETER

Explanation: The parmName input parameter for the CTVUPGDB Global Index housekeeping utility is in the wrong position. The ALT and BASELEN parameters may be specified only once each and must appear after the PATH parameter because they refer to a specific path.

The CTVUPGDB utility stops.

Corrective Action: Fix the input parameters in the JCL and rerun the job.

CTD044S SMFWTM RETURNED RC= 20 - SMF EXIT IEFU83 SUPPRESSED THE RECORD

Explanation: Highlighted, unrollable message.

Control-D attempted to write an SMF record, but the IEFU83 SMF exit suppressed the record.

The SMF record is not written, but Control-D continues processing. Control-D sets an internal indication that a permanent error is present on SMF recording, and will not continue to attempt SMF recording. From this point on, instead of writing to SMF, the SMF049I message is written to the IOA Log. This log message is a replacement for SMF recording, and can be entered into SMF after the problem is fixed.

Corrective Action: Correct the IEFU83 SMF exit to allow Control-D to write SMF records. When Control-D is brought up again, SMF records will resume.

CTD045S SMFWTM RETURNED RC= 24 - THE SMF FILES ARE FULL

Explanation: Highlighted, unrollable message.

Control-D attempted to write an SMF record, but the SMF files are full.

The SMF record is not written, but Control-D continues processing. Control-D will write the SMF049I message to the IOA Log file. This log message is a replacement for SMF recording, and can be entered into SMF later.

Control-D will keep attempting to write to the SMF file. If the SMF file is still full, the SMF049I message will be written to the log.

Please note that Control-D does not have to be taken down. As soon as room is found on an SMF file, SMF recording will take place automatically.

Corrective Action: The operator should clear SMF files according to the conventions of the site. As soon as this is done, Control-D will automatically continue with SMF recording.

CTD045W NO RECORDS WERE ADDED TO THE GLOBAL INDEX DATABASE

Explanation: The CTVUPGDB Global Index housekeeping utility did not add any records to the Global Index database.

The CTVUPGDB utility continues processing.

Corrective Action: To add records to the Global Index database, correct the input parameters in the JCL for the CTVUPGDB utility and rerun it.

CTD046S BLDL/LOAD FAILED FOR THE MODULE " modName "

Explanation: This is one of two messages with the same ID, but different text.

Loading of the modName module failed.

Possible causes are:

• IOA Load library is not in the load modules search list (STEPLIB + Linklist).
• There is insufficient memory.
• There is some other system-oriented reason, which may be found in the syslog.

Execution might stop.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support.

CTD046S INTERNAL PROBLEM IN MVS. SMF RECORD NOT WRITTEN

Explanation: This is one of two messages with the same ID, but different text.

Highlighted, unrollable message.

Control-D attempted to write an SMF record, but there is an internal problem in MVS.

This is due to one of the following return codes from MVS:

For the return code, refer to the SMF047S message.

The SMF record is not written, but Control-D continues processing. Control-D sets an internal indication that a permanent error is present on SMF recording, and will not continue to attempt SMF recording. From this point on, instead of writing to SMF, the SMF049I message is written to the IOA Log. This log message is a replacement for SMF recording, and can be entered into SMF after the problem is fixed.

Corrective Action: Call the system programmer. After the problem is fixed by the system programmer, bring down Control-D. When Control-D is brought up again, SMF recording will resume.

CTD047S RC= rc RECEIVED FROM MACRO SMFWTL

Explanation: Highlighted, unrollable message.

Control-D is unable to write SMF records. Possible causes are:

• The SMF046S message was issued. This message specifies the return code issued by SMF.
• An unknown return code was issued by SMF. This message specifies that return code.

The SMF record is not written, but Control-D continues processing. Control-D sets an internal indication that a permanent error is present on SMF recording, and will not continue to attempt SMF recording. From this point on, instead of writing to SMF, the SMF049I message is written to the Control-D log. This log message is a replacement for SMF recording, and can be entered into SMF after the problem is fixed.

Corrective Action: Call the INCONTROL administrator.

CTD048S THE Control-D SMF RECORDING IS TERMINATED - PLEASE TAKE CORRECTIVE ACTION

Explanation: Highlighted, unrollable message.

Control-D is unable to write SMF records.

This message is issued whenever a permanent error is present on SMF recording. This message is issued for the SMF041S through SMF050S messages.

The SMF record is not written, but Control-D continues processing.

Corrective Action: Refer to the SMF041S through SMF050S messages.

CTD049I MISSIONS PROCESSING STARTED

Explanation: This information message indicates that processing of missions started.

This message is issued by:

• CLISTs which schedule missions manually - for more information, see the INCONTROL for z/OS Administrator Guide.
• New Day procedure - for more information, see the relevant section of the INCONTROL for z/OS Administrator Guide.

Corrective Action: No action is required.

CTD050S INVALID VALUE val IN THE INSTALLATION PARAMETER "SMF"

Explanation: Highlighted, unrollable message.

Control-D attempted to write an SMF record, but an invalid value (val) is present on the SMF field in CTDPARM.

The SMF field in CTDPARM can contain the following values:

• Character string, length of three, value NO.
• A 3-digit number from 128 through 255.

The SMF record is not written, but Control-D continues processing. Control-D sets an internal indication that a permanent error is present on SMF recording, and will not continue to attempt SMF recording. From this point on, instead of writing to SMF, the SMF049I message is written to the IOA Log. This log message is a replacement for SMF recording, and can be entered into SMF after the problem is fixed.

Corrective Action: Call your INCONTROL administrator.

CTD051S ALL OF THE MISSIONS HAVE ENDED WITH ERRORS

Explanation: All mission order list statements were flagged as being invalid. The New Day procedure issues this message, if CTD032E messages were previously issued for all the mission order list statements or if CTD032E messages were previously issued because scheduling was cancelled by user exit CTDX001.

See sections on report decollating, printing, backup and restore missions in the INCONTROL for z/OS Administrator Guide. See also New Day processing.

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

Corrective Action: Correct all mistakes in mission statements and rerun the New Day procedure.

CTD052E ERROR IN LIBRARY= libName MEMBER= memName CATEGORY= catName

Explanation: This message indicates the erroneous mission definition. The erroneous data it contains are displayed in the preceding messages.

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

Corrective Action: Correct the mission definition and re-order it.

CTD053S MODULE modName ABENDED - CODE = abCode

Explanation: An abend occurred in the modName module.

Certain Control-D functions may fail. There will probably be additional messages on the system log or on the IOA log.

Corrective Action: If possible, correct the cause of the abend. Otherwise, call BMC Customer Support.

CTD054S OPEN OF USER DATE CONTROL-RECORD FAILED - DDNAME "DACHK"

Explanation: Open of the file containing the User Date Control Record failed (the DACHK DD statement). This message is issued by the CTDRRQ, CTDPRQ, CTDBRQ, or CTDSRQ program, which is activated by the New Day procedure.

This error may be due to one of the following:

• The DACHK DD statement is missing.
• The data set (member) described by the DACHK DD statement does not exist.

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

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

CTD055S DATE CONTROL-RECORD IS EMPTY

Explanation: The data set described by the DACHK DD statement is empty. This message is issued by the CTDRRQ, CTDPRQ, CTDBRQ, or CTDSRQ program, which is activated by the New Day procedure.

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

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

CTD056S PREVIOUS RUN OF pgm DID NOT FINISH OK

Explanation: A previous run of the New Day procedure probably abended. This message is issued by the pgm program (CTDRRQ, CTDPRQ, CTDBRQ, or CTDSRQ), which is activated by the New Day procedure.

Before a pgm program starts operating, it compares Date-2 with Date-3 (Date-4 with Date-5, and so on). If they are not equal, a previous run of the pgm program of the New Day procedure probably abended. See the Date Control record in the INCONTROL for z/OS Administrator Guide.

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

Corrective Action: Correct the value of the Date Control record and rerun the job. Make sure the same mission is not scheduled twice on the same day.

CTD057S LAST MONTHLY SCHEDULING DATE GREATER THAN THE CURRENT ORIGINAL SCHEDULING DATE

Explanation: Invalid current (or last) original scheduling date.

Date-2 (or Date-4/Date-6/Date-8) in the Date Control record is greater than Date-1. Someone probably modified the Date Control record incorrectly (the DACHK DD statement).

For more information, see the Date Control record in the INCONTROL for z/OS Administrator Guide.

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

Corrective Action: Correct the Date Control record (the DACHK DD statement), and rerun the New Day procedure.

CTD058S LAST MONTHLY SCHEDULING DATE WAS MORE THAN 28 DAYS AGO, CHECK IT

Explanation: The current or last original scheduling date is more than 28 days ago. Date-1 in the Date Control record is greater than Date-2, Date-4, Date-6, or Date-8, by 28 days.

Possible causes are:

• The New Day procedure has not been used for more than 28 days. Correct the date in the record to “yesterday.”
• The contents of the Date Control record may have been modified incorrectly.

For details about the Date Control record, see the INCONTROL for z/OS Administrator Guide.

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

Corrective Action: Correct the DACHK DD statement in the Date Control record, and rerun the New Day procedure.

CTD059W LIBRARY lib SHOULD BE COMPRESSED

Explanation: The lib library, which is specified in the PDS parameter, contains fewer free tracks than the number specified in the MINIMUM parameter.

The PDS and MINIMUM parameters are used for automatically compressing a library. If the MINIMUM condition is satisfied, CTDRRQ, CTDPRQ, CTDBRQ, or CTDSRQ issues this message, and the mission is placed in the Active Missions file. For more details, see the Control-D and Control-V User Guide.

The mission is placed on the Active Missions file.

Corrective Action: No action is required.

CTD061S INVALID YEAR IN DATE CONTROL-RECORD

Explanation: Either an invalid year was specified in the Date Control record used by the New Day procedure, or the current year is not defined in the calendar specified in the mission.

This message can be issued in either of the following cases.

• If the New Day procedure is running, Date1 in the Date Control record does not contain a valid year, or the year is not yet (or no longer) supported by the Control-D release currently in use or the DACHK DD statement does not point to the correct file.
• If a mission is running, the current year is not defined in the calendar specified in the mission.

The program terminates with a return code of 08.

Corrective Action: If the message is issued when the New Day procedure is running:

• Make sure DD statement DACHK points to the correct file.
• Make sure that Date1 in the Date Control Record contains a valid year.
• Make sure that the specified year is supported by the Control-D release.

If the message is issued when a mission is running, either add the current year to the calendar specified in the mission, or correct the calendar specification in the mission by specifying a different or no calendar.

CTD062S INVALID ORIGINAL SCHEDULING DATE IN DATE CONTROL-RECORD (POSITIONS 1-6)

Explanation: Invalid original scheduling date in the User Date Control record (positions 1-6). This error message is issued by the CTDRRQ, CTDPRQ, CTDBRQ or CTDSRQ program, which is activated by the New Day procedure.

Valid formats are mmddyy or ddmmyy. The contents of the DACHK DD statement in the Date Control record may have been incorrectly modified.

For more details see the INCONTROL for z/OS Administrator Guide.

The CTDRRQ, CTDPRQ, CTDBRQ, or CTDSRQ program ends with a return code of 08.

Corrective Action: Correct the DACHK DD statement in the Date Control record, and rerun the New Day procedure.

CTD063S INVALID CURRENT (OR LAST) ORIGINAL SCHEDULING DATE OF type MISSIONS

Explanation: Invalid original scheduling date in the Date Control record for type missions.

In this message, type missions are those of the following types:

• report
• print
• backup
• restore

This message is issued by the appropriate CTDRRQ, CTDPRQ, CTDBRQ, or CTDSRQ program, which is activated by the New Day procedure.

Date-2, Date-4, Date-6, or Date-8 in the Date Control record is invalid. The valid format is mmddyy or ddmmyy. The contents of the DACHK DD statement in the Date Control record may have been incorrectly modified.

For more details, see the INCONTROL for z/OS Administrator Guide.

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

Corrective Action: Correct the DACHK DD statement in the Date Control record and rerun the New Day procedure.

CTD065E SEVERE ERROR IN CALENDAR calName OR YEAR NOT FOUND IN CALENDAR

Explanation: Either the year is not defined in the calendar, or the calendar was corrupted.

This message is issued by:

• CLISTs which schedule missions manuallyFor more information, see the INCONTROL for z/OS Administrator Guide.
• New Day procedureFor more information, see New Day processing in the INCONTROL for z/OS Administrator Guide.
• The Online Facility when a FORCE or ORDER is issued from the Mission List screen.

The Active Missions file is not updated with this mission. If a New Day procedure is running, processing of other missions continues.

Corrective Action: Check the contents of the mission and the calendar.

CTD070E CANNOT MIX "# OF DAYS TO KEEP" WITH "# OF GENERATIONS TO KEEP"

Explanation: Both # OF DAYS TO KEEP and # OF GENERATIONS TO KEEP are specified. Only one of these options may be specified. They cannot be combined in one backup mission.

Corrective Action: Select only one of the options and blank out the other option.

CTD071S BLDL FAILED FOR PROGRAM pgm

Explanation: The pgm Control-D internal module is not present on the IOA Load library.

The Control-D monitor is shut down.

Corrective Action: Determine who deleted the pgm module and why. Restore this module from a backup tape of the IOA Load library. Then bring up Control-D.

CTD073E PLEASE FILL IN "# OF DAYS TO KEEP" OR "# OF GENERATIONS TO KEEP"

Explanation: There is no value for # OF DAYS TO KEEP or # OF GENERATIONS TO KEEP. A value greater than zero must be specified for one and only one of the fields.

Corrective Action: Specify a value greater than zero for one of the fields.

CTD077E SECONDARY SKELETON NAME MUST BE DIFFERENT THAN MIGRATION MISSION NAME

Explanation: The same name is specified for the secondary skeleton and the migration mission. The name of the secondary skeleton must be different from that of the migration mission.

Corrective Action: Change the secondary skeleton name.

CTD078E MEDIA NAME IS NOT FOUND IN IOASPRM MEMBER

Explanation: A migration target media that is not defined in the IOASPRM member is specified in the IOA PARM library. Each target media specified in the migration mission definition must be defined with media-specific parameters (NAME, TYPE, DSNPREF, UNITNAME, DEVADDR, and so on) in the IOASPRM member.

For information about these parameters, see the Control-V chapter in the INCONTROL for z/OS Installation Guide.

The migration mission is not saved or updated.

Corrective Action: Verify that the target media is spelled correctly in the migration mission definition. Specify a target media which is defined in the IOASPRM member, or define the desired target media in the IOASPRM member, and then use that target media in the migration mission definition.

CTD079E AGE MUST BE MORE THAN PREVIOUS AGE + REFRESH DAYS (IF ANY)

Explanation: A value for the AGE parameter was not larger than the value in the AGE parameter plus the value, if any, in the REFRESH EVERY parameter for the preceding stage.

At least one migration process and one refresh process (if any is specified) must be performed for each stage. Therefore, the age of the report, in days at each migration, must be greater than its age at the previous migration, and greater than its age at a subsequent refresh operation, if one was specified for the previous migration).

The migration mission is not saved or updated.

Corrective Action: Modify the AGE parameter, or the REFRESH EVERY parameter, or both, to comply with the age requirements.

CTD080E MEDIA NAME MUST BE SPECIFIED

Explanation: A migration mission is missing the MEDIA NAME subparameter. The MEDIA NAME subparameter must be specified for primary migration. If a migration stage has secondary migration, the MEDIA NAME subparameter must also be specified for secondary migration.

The migration mission is not saved or updated.

Corrective Action: In the MEDIA NAME subparameter, specify a target media which is defined in the IOASPRM member in the IOA PARM library.

CTD081E AGE IN DAYS MUST BE LESS THAN RETENTION DAYS

Explanation: The AGE subparameter was not smaller than the value in the RETENTION DAYS parameter. When a report reaches the age specified in the RETENTION DAYS parameter, it is deleted. Therefore, a report cannot migrate on that day or any subsequent day.

The migration mission is not saved or updated.

Corrective Action: Modify the AGE subparameter or the RETENTION DAYS parameter, or both, so that the value in the AGE subparameter is less than the value in the RETENTION DAYS parameter.

CTD082E AGE IN DAYS FOR MIGRATION MUST BE SPECIFIED

Explanation: A migration mission is missing an AGE subparameter. The age at which the report will migrate must be specified for each migration stage. The age is specified in days from the date the report was created.

The migration mission is not saved or updated.

Corrective Action: In the AGE subparameter, specify the age of the report in days when migration should occur.

CTD083E FIRST MIGRATION LEVEL MUST BE SPECIFIED

Explanation: A migration mission is missing mandatory parameters for migration stage 01. Parameters must be specified for migration stage 01.

The migration mission is not saved or updated.

Corrective Action: Specify the AGE and PRIMARY MEDIA NAME mandatory parameters for stage 01 migration.

CTD084E MIGRATION LEVELS MUST BE CONSECUTIVE. PLEASE FILL IN PREVIOUS LEVEL

Explanation: There is no block containing the STAGE parameter and its subparameters. Migration stage numbers from 1 through 10 are generated automatically. You must define migration stages in sequence without skipping a stage.

The migration mission is not saved or updated.

Corrective Action: Specify the migration path stages in sequential order.

CTD085E REFRESH DAYS MUST NOT EXCEED RETENTION DAYS MINUS AGE

Explanation: The number of days specified for the refresh interval in the REFRESH EVERY subparameter exceeds the difference between the age at time of migration and the age at which the report is deleted (RETENTION DAYS). The media on which a report is stored cannot be refreshed after the age at which the report should be deleted.

The migration mission is not saved or updated.

Corrective Action: Respecify one or more of the following

• the RETENTION DAYS parameter
• the AGE subparameter
• the REFRESH EVERY subparameter

so that the value in the REFRESH EVERY subparameter does not exceed the difference between the values specified in the AGE subparameter and the RETENTION DAYS parameter.

CTD0A1E PARENT NAME AND PARENT LEVEL MUST BE BOTH FILLED IN OR BOTH BLANKS

Explanation: Either the PARENT NAME or the PARENT LEVEL is defined, but not both fields. PARENT NAME and PARENT LEVEL fields must be specified together if they are specified at all.

The user is prompted to correct the PARENT field.

Corrective Action: Specify the missing value, or blank out both fields.

CTD0A2I FORCED BROWSE DUE TO USER EXIT SPECIFICATION

Explanation: This information message indicates that an attempt was made to edit a Recipient Tree member that may only be browsed.

User exit CTDX021 specifies that the requested Recipient Tree member may only be browsed. In Browse mode, no changes may be made to the tree member. However, all recipients may be selected, and the member may perform a tree validity check using the CHKTREE command.

The Recipient Tree member is accessed in Browse mode.

Corrective Action: No action is required.

CTD0A3E OPTIONS "D" "I" AND "P" ARE INVALID UNDER BROWSE

Explanation: An invalid option was entered while accessing a Recipient Tree member under Browse mode. The only valid option is S (Select). The D (Delete), I (Insert) and P (Parent) options are not valid in Browse mode.

The requested option is not performed.

Corrective Action: No action is required.

CTD0A4E PLEASE FILL IN AUTHORIZE BEFORE FILLING IN $SYSDATA

Explanation: A Y or N was entered in the $SYSDATA field without specifying a user name in the AUTHORIZE field.

The AUTHORIZE field is used to specify who may view the reports of the recipient. Additionally, the $SYSDATA field on the same line is used to indicate whether or not the authorized user may also view $SYSDATA records. The $SYSDATA field must be blank if no user is specified in the AUTHORIZE field.

Corrective Action: Fill in a user name in the AUTHORIZE field, or blank out both fields.