Messages CTDB00 through CTDBxx

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

CTDB06E OUTGRP INFORMATION IS UNAVAILABLE

Explanation: Highlighted, unrollable message.

The OUTGRP parameter is specified in CTDPARM, but the function cannot be performed.

An attempt to get the GROUPID parameter failed due to one of the following:

• The OUTGROUP OUTPUT statement was not specified in the CTDPRINT procedure.
• The corresponding control blocks cannot be found in the current release of MVS.

A special snap is sent to the DD name DADUMP.

Corrective Action: Check that the OUTGROUP OUTPUT statement is specified in the CTDPRINT procedure. If the error persists, contact your INCONTROL administrator and supply the snaps.

CTDB07E OUTGRP COULD NOT BE SET

Explanation: Highlighted, unrollable message.

The GROUPID parameter could not be set for the current chunk according to the OUTGROUP parameter in CTDPARM.

Corrective Action: Notify your INCONTROL administrator.

CTDB08E ERROR ACCESSING BARCODE TRACKING FILE RC=rc

Explanation: A print mission failed to access the Barcode Tracking (BTR) file.

The current print mission terminates NOT OK.

Corrective Action: Correct the source of the problem using the IOAF70I or IOAF71I message to be found in the JES log. Rerun the mission.

CTDB0DE OUTPUT CARD DYNAMIC ALLOCATION FAILED, RC=rc, REASON=rsn, KEY=key_code

Explanation: The dynamic allocation (pursuant to optional wish WD3133) of an output statement during a printing mission failed.

The variables in this message are:

• rc - the return code
• rsn - the reason code
• key_code - the key code

These codes are the standard system return, reason, and key codes that are returned when dynamic allocation of an output statement occurs. For more information on these codes, see the description of the OUTADD macro in the IBM manual MVS Programming: Authorized Assembler Services Reference.

The printing mission does not use the dynamic allocation of an output statement for the current report.

Corrective Action: Examine the values of the return, reason, and key codes, and take appropriate corrective action.

CTDB10E "FE" PRINT SUPPORT ERROR. RETURN CODE rc

Explanation: An executing Printing Mission failed to delete an internal Printing Mission record in the Active User Report file.

If the DO PRINT parameter is specified in a Decollation Mission Definition, the Control-D Decollation monitor writes an internal Printing Mission record to indicate that there are reports waiting to be printed by the Printing Mission specified in the DO PRINT parameter.

These records have the following key:

X‘FE’,C‘PRINTMS’,Printing-Mission-Name

In this message, rc is the return code from the CTDXRP routine.

Control-D encountered an error when attempting to delete the record for the current Printing Mission during Printing Mission termination processing.

The Printing Mission continues.

Corrective Action: If the problem persists, report the return code to BMC Customer Support.

CTDB21I CTVACDB UTILITY STARTED IN mode MODE

Explanation: This information message indicates the normal start of the CTVACDB utility in the mode specified.

In this message, mode is the mode in use. Valid values are:

• TEST--simulation mode
• PROD--production mode

Corrective Action: No action is required.

CTDB22I PARM=TEST SPECIFIED - SIMULATION MODE

Explanation: This information message indicates that the CTVGDBB or CTVGICL utility ran in simulation mode. In this mode, messages are generated that indicate what actions would normally be performed. These actions are not performed, nor are any files changed.

Corrective Action: Check the SYSOUT of the CTVGDBB or CTVGICL utility before running it in production mode.

CTDB23I CTVACDB UTILITY ENDED OK

Explanation: This information message indicates the normal termination of the CTVACDB utility.

Corrective Action: No action is required.

CTDB24S CTVACDB UTILITY ENDED WITH ERRORS

Explanation: (severe general message) The CTVACDB utility ended with errors.

Corrective Action: See the IOA LOG and the job sysout.

CTDB25E OPEN OF SORT FILE FAILED. DDNAME "dd_Name"

Explanation: The SORT utility invoked by the CTVACDB utility failed to open the dd_Name DD statement.

The CTVACDB utility stops.

Corrective Action: Ensure that all DD statements are valid and then restart the CTVACDB utility.

CTDB26E INVALID PARAMETER: parmValue

Explanation: An invalid parameter parmValue was encountered in the input data stream of the CTVACDB utility.

The utility terminates with a condition code of 08.

Corrective Action: Correct the parameter syntax and resubmit the job. For more information, see the section on the CTVACDB utility in the INCONTROL for z/OS Utilities Guide.

CTDB27E MISSING PARAMETER AFTER: parmValue

Explanation: A subparameter of a parameter to the CTVACDB utility is missing. A subparameter is expected after the parmValue parameter.

The utility terminates with a condition code of 08.

Corrective Action: Correct the parameter syntax and resubmit the job. For more information, see the section on the CTVACDB utility in the INCONTROL for z/OS Utilities Guide.

CTDB28E OPEN OF PARAMETERS FILE FAILED. DDNAME "SYSIN"

Explanation: The open of the SYSIN DD statement failed. Possible causes are:

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

The CTVACDB utility terminates with a return code of 08.

Corrective Action: Correct the JCL for the CTVACDB and rerun the utility. For more information, see the section on the CTVACDB utility in the INCONTROL for z/OS Utilities Guide.

CTDB29E LOCATE ERROR FOR DSN dsn

Explanation: The CTVACDB utility encountered a CDAM file name that does not exist in the catalog. The dsn data set might have been deleted or uncataloged.

The dsn data set is ignored.

Corrective Action: Check the output of the CTVACDB utility, and then try to resolve the problem.

CTDB2AE ACD FOR DATASET dsn IS NOT CORRECT

Explanation: The CTVACDB utility found incorrect ACD data for the migrated data set dsn on the volume.

If the CTVACDB utility works in PROD mode, incorrect ACB will be updated.

Corrective Action: If the CTVACDB utility works in PROD mode, looks for corresponding CTDB2CE message. If the CTVACDB utility works in TEST mode, resubmit the CTVACDB utility in PROD mode to fix the problematic ACD.

CTDB2BE INVALID RETURN CODE FROM SORT, RC=rc

Explanation: A sort program activated internally by the CTVACDB utility ended with an unexpected return code of rc.

The CTVACDB utility terminates with a condition code of 08.

Corrective Action: For details about the reason for the failure, see the documentation for the sort program and the job's sort messages.

CTDB2CE ACD WILL BE UPDATED FOR DATASET dsn

Explanation: The CTVACDB utility will update incorrect ACD data for the migrated data set dsn. This message appears after corresponding CTDB2AE message.

Corrective Action: No action is required.

CTDB2DE NO CDAM/INDEX DATASET WERE MIGRATED ON volume VOLUME

Explanation: The specified volume does not contain a migrated CDAM/INDEX.

The CTVACDB utility terminates with a condition code of 08.

Corrective Action: Correct input parameter VOL and resubmit the CTVACDB utility.

CTDB2FI ACD WILL BE CLEANED FOR DATASET dsn

Explanation: This information message is issued for each relevant data set when FUNCTION=CLEAN is specified for the CTVACDB utility. It indicates that the ACD data will be cleaned for the migrated data set dsn.

Corrective Action: No action is required.

CTDB45I CONTROL-D ACTIVE MISSIONS FILE IS COPIED TO BACKUP FILE

Explanation: This information message is the normal start message of the CTDCAMF utility for the COPY option.

Corrective Action: No action is required.

CTDB46I COMPRESSING OF CONTROL-D ACTIVE MISSIONS FILE STARTED

Explanation: This information message is the normal start message of the CTDCAMF utility for the COMPRESS option.

Corrective Action: No action is required.

CTDB47I COMPRESSING OF CONTROL-D ACTIVE MISSIONS FILE ENDED

Explanation: This information message is the normal termination message of the CTDCAMF utility for the COMPRESS option.

Corrective Action: No action is required.

CTDB48S ERROR WHILE COMPRESSING ACTIVE MISSIONS FILE, FILE WAS NOT COMPRESSING

Explanation: The CTDCAMF Control-D utility failed.

This could be 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, but for another Control-D monitor or from a different Control-D version.
• The DABKUP DD statement is missing.
• The SYSPRINT DD statement is missing. See the CTM913S message.

The utility terminates with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

CTDB55E ERROR WHILE OPENING DD "DASCRLST". OLD PRINT PLAN FILES WILL NOT BE DELETED

Explanation: An error occurred while trying to write a print plan file name to the scratch list. The message is issued by the AMF formatting program. This program could not open the file referenced by DD DASCRLST. This could be because the entire corresponding DD statement is missing.

AMF formatting program continues processing.

Corrective Action: Verify that the DD DASCRLST statement exists in the JCL and that it references an existing file.

CTDB60I MISSION missionName NOT ORDERED. MISSION ALREADY IN ACTIVE MISSIONS FILE

Explanation: This information message indicates that the specified mission already exists on the Active Missions file. Therefore there is no need to order it again. This situation is common during the product test period.

Corrective Action: No action is required.

CTDB70S OPEN FAILED fileName

Explanation: The Online Print Control Program was unable to open the Print Plan file of the selected Printing Mission, probably because the file name has not yet been created.

The Print Plan file is a sequential file that contains the information required by the Control-D Printers Control monitor to print a specific Printing Mission, such as report names, user names, and job names of the reports that are scheduled to be printed by this Printing Mission. This file is built during the initial Printing Mission processing.

Corrective Action: Retry to enter the Print Control option. If the problem recurs, enter the Log option for this Printing Mission to view the error messages.

CTDB71S ALLOCATION FAILED fileName

Explanation: The Online Print Control Program was unable to dynamically allocate the Print Plan file of the selected Printing Mission, probably because the filename has not yet been created. It is also possible that the Print Plan file was manually deleted.

The Print Plan file is a sequential file that contains the information required for the Control-D Printers Control monitor to print a specific Printing Mission, such as report names, user names, and job names of the reports that are scheduled to be printed by this Printing Mission. This file is built during the initial Printing Mission processing.

Corrective Action: Notify your INCONTROL administrator.

CTDB72S OPEN OF COMMUNICATION FILE FAILED (DDNAME DACOM)

Explanation: The Online Print Control Program was unable to open the Communication file, which is used for communication with the Printers Control monitor. The file must be available for the Online Print Control program.

Corrective Action: Notify your INCONTROL administrator.

CTDB73E INVALID VALUE, TRY "N" or "Y"

Explanation: User specified an invalid value in a Yes/No field. Valid values are Y (for Yes) or N (for no).

Corrective Action: Specify Y or N.

CTDB74E SKIP TO REPORT COMMAND IS INVALID AFTER STOP COMMAND LOCATION

Explanation: SKIP TO REPORT option was specified after a STOP AT REPORT option. A SKIP TO REPORT option may not be specified after a STOP AT REPORT option.

Corrective Action: Reposition the SKIP TO REPORT and STOP AT REPORT options. For example, reposition the STOP AT REPORT option to the end of the Report List and re-enter the SKIP TO REPORT option.

CTDB75E INVALID VALUE. TRY "C" or "R"

Explanation: The specified value is invalid.

Valid values are:

• C - The Printing Mission should skip to the specified report at the end of the current chunk.
• R - The Printing Mission should skip to the specified report at the end of the current report.

Corrective Action: Specify C or R.

CTDB76E STOP COMMAND IS INVALID BEFORE SKIP TO REPORT COMMAND LOCATION

Explanation: STOP AT REPORT option was specified before a SKIP TO REPORT option. A STOP AT REPORT option may not be specified before a SKIP TO REPORT option.

Corrective Action: Reposition the STOP AT REPORT and SKIP TO REPORT options. For example, reposition the existing SKIP TO REPORT option to the start of the Report List and re-enter the STOP AT REPORT option.

CTDB77E SKIP FROM PC REPORT TO NON-PC REPORT IS FORBIDDEN

Explanation: SKIP TO REPORT option was positioned on a non-PC report when the Printing Mission was processing PC reports. The SKIP TO REPORT option cannot be specified on a non-PC report when the printing mission is processing PC reports.

Corrective Action: Enter the SKIP TO REPORT option after the printing mission completes printing, and rerun the mission.

CTDB78I OPTION opt PROCESSED FOR PRINT MISSION missionName CATEGORY cat. USER userName JOB jobName /jobId REPORT reportName

Explanation: This information message is written to the IOA Log file when a user specifies a Print Control option (>, <, D, or U) on the Print Plan screen.

Corrective Action: No action is required.

CTDB79E ONLY ONE IMMEDIATE COMMAND (P, T, H, R) IS ALLOWED

Explanation: An Immediate Printing Control command was issued before a previous command had been passed to the Control-D Functional Subsystem (FSS) monitor. Immediate Printing Control commands can be issued under the Print Plan screen for printing missions that use the Control-D/Writer facility. These commands are SKIP, STOP, TEST, HALT, RESUME and PRINT.

The Immediate Printing Control command is ignored.

Corrective Action: Wait a little while and then reissue the Immediate Printing Control command.

CTDB7AE COMMAND IS NOT SUPPORTED YET

Explanation: A B (BACK) command was entered in the Print Plan screen (screen A.P) for a printing mission that uses the Control-D/Writer facility. This command is not supported yet.

The B (BACK) command is ignored.

Corrective Action: Use the SKIP command instead of the BACK command.

CTDB7BE FIELD MUST BE NUMERIC AND GREATER THAN ZERO

Explanation: An invalid number of pages was specified in a Printing Control command in the Print Plan screen (screen A.P) for a printing mission that uses the Control-D/Writer facility.

The Print Plan screen cannot be saved.

Corrective Action: Specify a valid number of pages - numeric and greater than zero.

CTDB7DE COMMAND FAILED. POST RETURN CODE prc

Explanation: An error occurred in passing a Printing Control command to the Control-D Functional Subsystem (FSS) monitor. The Print Plan uses the POST command in a cross-memory environment to pass commands under Print Plan screen for printing missions that use the Control-D/Writer facility.

The Printing Control command is ignored.

Corrective Action: Repeat the command. Save the return code issued in the message, the job log of the FSS monitor, and the IOA Log of the printing mission. Contact BMC Customer Support.

CTDB7EE IMMEDIATE COMMANDS ARE NOT AVAILABLE WHEN PRINT MISSION IS NOT ACTIVE

Explanation: An immediate Printing Control command under the Print Plan screen was issued for a non-active printing mission. Immediate Printing Control commands, SKIP, STOP, TEST, HALT, RESUME and PRINT, are only available for active running printing missions. They are issued under the Print Plan screen for printing missions that use the Control-D/Writer facility.

The command is ignored.

Corrective Action: Issue the immediate Printing Control command only after the printing mission enters the printing stage.

CTDB7FE TEST COMMAND IS AVAILABLE ONLY IN HALTED STATUS

Explanation: Printing Control command TEST was issued for a printing mission that did not have HALTED status.

Printing Control command TEST can be issued in the Print Plan screen for a printing mission that uses the Control-D/Writer facility. However, this command can only be issued for a printing mission whose status is HALTED.

The TEST Printing Control command is ignored.

Corrective Action: Halt the printing mission by means of the HALT command and then issue the TEST command.