Messages CTD900 through CTD9xx

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

CTD900E PLEASE FILL IN CATEGORY NAME

Explanation: The CATEGORY field is obligatory but missing from this screen.

Corrective Action: Fill in the CATEGORY field.

CTD901E INVALID TASK TYPE

Explanation: An invalid task type was specified. For valid task types, see the Control-D and Control-V User Guide.

Corrective Action: Correct the TASKTYPE field.

CTD902E INVALID OPTION (TRY "Y", "N" OR BLANK)

Explanation: An invalid option was specified. Valid options are Y for yes, and N or blank for no. The cursor points to the invalid value.

Corrective Action: Select Y, N or blank.

CTD903E FIELD SHOULD BE NUMERIC OR BLANK

Explanation: The field contains data that are neither numeric characters nor blanks. If numeric values are used, then no trailing or preceding blanks are allowed. The cursor points to the invalid field value.

Corrective Action: Correct field contents.

CTD904E INVALID TIME

Explanation: An invalid time was specified. The format of the TIME parameter should be hhmm. For more details, see the Control-D and Control-V User Guide.

Corrective Action: Correct the TIME field. Insert FROM or UNTIL.

CTD905E INVALID LEVEL

Explanation: The specified level is not defined in the installation as a valid tree level. Level must be a two letter code that is defined in the Control-D Installation Parameters (CTDPARM).

Corrective Action: For a list of valid level codes see option T on the Main Menu.

CTD906I REFRESH OF PERMANENT USER FILE FROM THE ACTIVE USER FILE STARTED

Explanation: This information message indicates that the CTDCA2P utility is copying the list of reports from the Active User Report List file to the Permanent User Report List file. Normal start message of the CTDCA2P utility.

Corrective Action: No action is required.

CTD907I REFRESH OF PERMANENT USER FILE FROM THE ACTIVE USER FILE ENDED OK

Explanation: This information message is the normal end message for the CTDCA2P utility. It indicates that the CTDCA2P utility successfully finished copying the list of reports from the Active User Report List file to the Permanent User Report List file.

Corrective Action: No action is required.

CTD908S fileType USER FILE ERROR RC=rc PGM pgm_csect ID xx /yyy FUNCTION func

Explanation: An error occurred while accessing a User Report List file.

The variables in this message are:

fileType - the type of User Reports List file component. Valid values for the data component are:
- ACT
- PRM
- HST
- MIG
- MG n, where n is the migrated partition number

Valid values for the index component are composed of the index component letter, followed the data component values.

rc - the return code from the user file interface routine.
pgm_csect - the program CSECT, which received the error.
xx/ yyy - an identifier for localizing the erroneous call.
function - the operation that caused the error.

Return codes may range from 004 through 399. The return codes from 300 through 399 relate to index components. Their explanations are the same as the corresponding return codes in the range from 100 through 199, which relate to data components.

Valid values of rc are:

rc	Explanation
004	Read operation: EOF. Add index operation: Duplicate Key. Update operation: Record was changed. Database already used by other task for strtacse.
008	Duplicate key.
012	Incorrect record for update.
016	The record was not found (probably deleted), or an invalid record was read, or the function is not correct.
020	Insufficient memory to open an IOA Access Method file.
024	Not enough space in data file.
028	Not enough space in index file.
032	The current call terminates because the previous open failed.
036	Incorrect record length.
040	Internal error.
044	Internal error.
052	Invalid key fields.
056	Key is too long.
058	For future use.
060	Index record does not match data record.
064	Wish WD1164 setting does not match file contents.
068	Incorrect parameter for Interface routine.
072	Incorrect file type.
076	Incorrect DBO version.
080	Incorrect ALT letter (or VSA type)
084	Incorrect ALT key length (Start)
088	Incorrect record version.
104	Record not found. No room to add record.
106	Record not found.
108	Record not found. Invalid extent number.
109	Record not found. Invalid block number.
110	Internal error. Record not found. Invalid extent number.
111	Internal error. Record not found. Invalid block number.
112	Insufficient memory for internal buffers.
113	Open failed for database file.
114	RDJFCB failed for database file.
116	Corrupted free list.
118	Corrupted record.
119	Record not found.
120	Invalid QNAME.
121	Bad record in free list.
122	Invalid data set name in control record.
124	Invalid function.
128	IOAPARM load failed.
132	Add failed. Record too long.
136	I/O error.
144	EXCP init error.
146	For future use.
148	Invalid data set name or DD name is too long.
150	Locate failed.
152	SVC 99 allocate failed.
154	SVC 99 unallocate failed.
156	Dual database not up to date - aborting.
158	For future use.
160	Link of IOADBF failed.
164	A dynamic allocation error occurred (for example, out of space condition, security problems). See dynamic allocation error messages in job log.
166	Control record cannot be updated because it is not enqueued.
168	Update failed. Record too long. No room in block.
170	IOADBSB# load failed.
172	READQ failed. Another block is already enqueued.
174	Function OPEN0 (exclusively) failed.
176	Function UPDATE0 failed. Data corrupted.
178	Function UPDATE0 failed. No appropriate enq.
180	Buffering not initialized. Internal error.
182	ENQ error.
184	Error during record compression / decompression.
186	Attempted to write the wrong extent of a multi-extent data set.
190	Attempt to write record to file opened for READ only.
204	Record not found.
208	Error accessing the file.
212	Insufficient memory for internal buffers.
216	Internal error.
218	The structure of the index tree is corrupted. A key on a higher level of the tree does not match the last key on a lower level.
219	The structure of the index tree is corrupted. The indicated key value, or a higher value, was not found in the block.
220	Invalid function.
224	Invalid timestamp
284	Invalid chain of index elements - rebuild index and rerun process.

The system action depends on which component was accessing the user file. Usually, the current routine terminates. Additional messages clarifying the source of the error are written to the IOA Log file before this message.

Corrective Action: Do the following:

For return codes 200 and higher,
- rebuild the index component
- rerun the process
For all other return codes,
- search the IOA Log file and the relevant job log for messages clarifying the source of the error
- correct the error
- rerun the job.
If the error persists, contact BMC Customer Support.

CTD909S REFRESH OF PERMANENT USER FILE FROM THE ACTIVE USER FILE ENDED WITH ERRORS

Explanation: An error occurred during the execution of the CTDCA2P utility.

Corrective Action: An earlier message describes the error.

CTD90AE FIELD SHOULD BE BLANK FOR GENERIC=Q

Explanation: A value has been typed in either the JOBID or the DSN field in the Report Decollating Mission screen (Screen R.S) or the Active Mission Zoom screen (Screen A.Z). If GENERIC is set to Q, these fields must be left blank.

For more information, see the Control-D and Control-V User Guide.

Corrective Action: Correct the contents of the fields.

CTD90BE "ON on_stmt" IS NOT VALID FOR GENERIC=x

Explanation: The value that has been set in an ON statement is invalid for the current setting of the GENERIC parameter.

If GENERIC is set to Q, the only valid value for ON is MQ.
If GENERIC is set to Y or N or is left blank, all values are valid for ON except MQ.

For more information, see the Control-D and Control-V User Guide.

Corrective Action: Correct the contents of the fields.

CTD90CE INVALID OPTION (TRY "U", "L" OR BLANK)

Explanation: An invalid option has been specified in the CS field in the Report Decollating Mission screen (Screen R.S) or the Active Mission Zoom screen (Screen A.Z). The cursor points to the invalid value.

The valid options are:

U - upper case
L or ' ' (Blank) - lower case

For more information, see the Control-D and Control-V User Guide.

Corrective Action: Correct the contents of the field, by typing U or L, or by leaving the field blank.

CTD90DE VARIABLE NAME TOO { LONG | SHORT }. LENGTH SHOULD BE 8 CHARACTERS

Explanation: A name has been specified for a variable that is either too long or too short. The variable name must consist of exactly 8 characters.

For more information, see the Control-D and Control-V User Guide.

Corrective Action: Correct the length of the variable name to 8 characters.

CTD90EE VALUE IS MORE THAN lim

Explanation: The value specified exceeds the maximum permitted.

In this message, lim is the maximum permitted value.

Possible causes are:

An invalid value was specified for the LINE or COL parameter in one of the following statements:
WHEN
DO USER
DO NAME
DO INDEX
MASK
SUBINDX

Valid values for the LINE parameter are any 5-digit number from 00001 through 39999.

Valid values for the COL parameter are any 5-digit number from 00001 through 32767.

For more information on these parameters, see the Control-D and Control-V User Guide.

An invalid index value was specified in the COL parameter in a DO INDEX or SUBINDEX statement when the value in the COL field began with a + or - sign. Valid values in this case are any 5-digit number from 00001 through 00050.

The system waits for the values to be corrected.

Corrective Action: Correct the value in the LINE or COL field.

CTD90FE LENGTH OF VALUE IS MORE THAN 200

Explanation: On setting values for the DO SET parameter, when setting a value for the list of node tag names (Xpath), too many characters were used.

Valid values for Xpath are from 4 through 200 characters (case sensitive) in length. For more information, see the DO SET parameter in the Control-D and Control-V User Guide.

Corrective Action: Correct the value of Xpath.

CTD90GE INVALID NAME OF VARIABLE

Explanation: An invalid %%variable name has been specified in the DO or WHEN statement in the decollation mission definition.

Valid names for user variables are from 1 through 8 alphanumeric characters, but cannot be the same as any system variable.

The %%$CELL system variable function is allowed in a DO SET statement only.

For more information, see DO SET in the Control-D and Control-V User Guide.

Corrective Action: Set a valid variable name.

CTD910E INVALID CONTROL-D ACCESS METHOD PARAMETER - parm

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

The parm Compressed Dataset Access Method (CDAM) parameter is invalid. For a list of valid CDAM parameters, see the Control-D and Control-V User Guide.

In the following example of an invalid parameter, BLOCKS should have been specified instead of BLOCS:

//PRINT DD SUBSYS=(CDAM,‘BLOCS=280’)

The CDAM data set is not created.

Corrective Action: Correct the invalid CDAM parameter, and rerun the job.

CTD910E INVALID CONTROL- R ACCESS METHOD PARAMETER - parm

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

The access method parameter is invalid. An internal error occurred during Control-M/Restart SYSDATA archiving.

Control-M terminates processing.

Corrective Action: Contact BMC Customer Support.

CTD911E INVALID VALUE OF CONTROL-D ACCESS METHOD PARAMETER parmValue

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

The value of the Compressed Dataset Access Method (CDAM) parameter is not valid. For a list of valid parameter values, see the Control-D and Control-V User Guide.

In the following example of an invalid parameter value, KKK must be a numeric value:

//PRINT DD SUBSYS=(CDAM,‘BLOCKS=KKK’)

The CDAM data set is not created.

Corrective Action: Correct the invalid CDAM parameter value, and rerun the job.

CTD911E INVALID VALUE OF CONTROL-R ACCESS METHOD PARAMETER parmValue

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

The Control-M/Restart access method parameter value is not valid. An internal error occurred during Control-M/Restart SYSDATA archiving.

Control-M stops processing.

Corrective Action: Contact BMC Customer Support for assistance.

CTD912S ERROR IN CONTROL-x INSTALLATION PARAMETERS - INVALID DAYTIME

Explanation: The format of the DAYTIME Control- x Installation parameter is invalid. DAYTIME is the start time of the work day in your installation. Valid formats are +hhmm or -hhmm.

For more details, see the section that describes installation parameters in the chapter for the appropriate products in the INCONTROL for z/OS Installation Guide.

The requested function terminates.

Corrective Action: Call your system programmer to correct the DAYTIME parameter in the CT xPARM member.

CTD913S OPEN OF DDNAME "SYSPRINT" FAILED

Explanation: The opening of a print file failed.

Possible causes are:

The DD statement SYSPRINT is missing.
The data set described by the DD statement SYSPRINT cannot be accessed for sequential write.

The program stops executing.

Corrective Action: Correct the JCL and submit again.

CTD914E COMPRESSED DATASET ACCESS METHOD SUBSYSTEM name DOES NOT EXIST

Explanation: The Compressed Dataset Access Method (CDAM) was not defined as a subsystem. For information on how to define CDAM as a subsystem, see the Control-D operational parameters and CDAM installation instructions in the Control-D chapter of the INCONTROL for z/OS Installation Guide.

The CDAM data set is not created.

Corrective Action: Do the following:

Define CDAM as a subsystem.
Initialize CDAM, using the IOASINIT started task procedure.
Rerun the job.

CTD914S ERROR OPENING SYSPRINT

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

An error occurred while opening the SYSPRINT DD statement. The DD statement is probably missing.

The IOADIG utility terminates with a return code of 8.

Corrective Action: Notify your INCONTROL administrator.

CTD914S ERROR IN CONTROL-D INSTALLATION PARAMETERS - INVALID DATETYP

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

Highlighted, unrollable message.

The DATETYP IOA Installation Parameter is invalid. DATETYP is the type of date format used in the installation. Valid formats are:

A - mmddyy
W - ddmmyy
J - yymmdd

For more details, see the section that describes how to set IOA installation parameters in the IOA chapter of the INCONTROL for z/OS Installation Guide.

The requested function stops.

Corrective Action: Call your system programmer to correct the DATETYP parameter in the IOAPARM member.

CTD915E COMPRESSED DATASET ACCESS METHOD SUBSYSTEM name IS NOT ACTIVE

Explanation: The Compressed Dataset Access Method (CDAM) subsystem is not active. To initialize the CDAM, see the section on installation of the CDAM in the Control-D chapter of the INCONTROL for z/OS Installation Guide.

The CDAM data set is not created.

Corrective Action: Do the following:

If necessary, modify SYS1.PARMLIB as specified in the guide so that Control-D is initialized properly after IPL.
Run the IOASINIT started task to initialize CDAM immediately.
Rerun the job.

CTD915S NO PARAMETERS PASSED

Explanation: No parameters were passed to the IOADIG utility.

The utility terminates with a return code of 24.

Corrective Action: Notify your INCONTROL administrator.

CTD916W PROGRAM pgm WAITING FOR resourceName

Explanation: One of the IOA monitor internal programs detected an IOA resource in use by a TSO user or batch job. This message normally appears a few times a day.

The variables in this message are:

pgm - the name of the internal program that is waiting for the resource that is in use
rname - the name of the resource that is in use

Valid values are:

rname	Meaning
CNDF	The IOA Conditions file
RESF	The Control-M Resources file
LOG	The IOA Log file
Control-M	The Control-M New Day procedure
JES_SSRQ	A JES subsystem request
CKPT	The Control-M Active Jobs file or the Control-D Active Missions file

The message is displayed on the operator console.

Corrective Action: The user response depends on the circumstances, as follows:

If the message appears many times every few seconds, the file may be hung. This situation must be resolved by determining which program is holding the specified rname. Look for the IOA QNAME that is specified in the IOA Installation Parameter and take appropriate corrective action.
If the program name pgm is CTMFRM and the rname is CONTROLM, some possible reasons are:
- there are several Control-M monitors running with the same QNAME
- there is a user daily job running that has a date control record in which columns 60 through 65 are not blank, meaning that it is acting as the Control-M New Day procedure and therefore Control-M has been enqueued
- the Control-M New Day procedure was started externally (manually) rather than being started by the monitor, and as a result waits for the monitor to be suspended

Take appropriate corrective action.

If the program name pgm is CTMJES and the resourceName is JES_SSRQ, then Control-M (in its postprocessing phase) has called the JES2 interface using IEFSSREQ (a JES2 subsystem request) and is waiting for some function to be executed by JES2, but the execution of that function is being delayed in JES2. If the message persists in this situation, prepare the Control-M monitor full output and contact BMC Customer Support.

CTD918S INSUFFICIENT MEMORY TO RUN CONTROL-x

Explanation: Highlighted, unrollable message.

More memory is required for the INCONTROL monitor.

The specified monitor will shut down.

Corrective Action: Increase the REGION size of the specified monitor.

CTD919E ERROR IN CDAM PROCESSING - LOADING OF MODULE loadModName FAILED

Explanation: CDAM failed to load the loadModName module, which is required for processing a CDAM data set.

CDAM data set fails to open.

Corrective Action: Check that the load modules with a VERID suffix that appear in IOAPARM are in a LINKLIST load library. If this is not the cause of the problem, supply BMC Customer Support with the IOA log file and this message.

CTD920E CDAM OPEN PROCESS FAILED

Explanation: CDAM failed to open a CDAM data set. This message is preceded by messages which provide the reason for the failure.

One of the following actions occurs:

If this message is issued during the decollation process, the decollating mission terminates NOT OK and message REP256E is issued.
If this message is issued when an open report request is issued, the CDAM does not exist.

Corrective Action: Using the information from the preceding messages, correct the cause of the problem, and rerun a problematic application job, or Control-D monitor according to the one that was involved in the failure.

CTD921E DDNAME = ddName - OUTPUT LIMIT WAS REACHED

Explanation: The maximum number of records allowed in a CDAM data set was reached. The maximum number of records that can be written by an application program to a CDAM data set can be specified by either the OUTLIM parameter in the CDAM subsystem parameters of a program, or by applying optional Wish WD0699.

The application program abends with the code S722.

Corrective Action: Check the application program for an error that causes so many records to be written to one CDAM data set. If this is not the problem, increase the maximum number of records that can be written to a CDAM data set.

To do this only for a specific application program, specify the OUTLIM parameter in the CDAM subsystem parameters of the program. To perform this for all application programs, apply optional Wish WD0699.

CTD922E DDNAME=ddName, DYNAMIC ALLOCATION ERROR, RC =rc, REASON CODE=rsn

Explanation: An error occurred during the attempted dynamic allocation of a CDAM data set, and the allocation failed.

The variables in this message are:

ddName - the name of the CDAM data set
rc - the return code
rsn - the reason code

For more information on the return code and reason code, see the IBM manual MVS Programming: Authorized Assembler Services Guide.

The CDAM data set is not created.

Corrective Action: Do the following:

Try to correct the error, using the information provided by the return code and reason code.
If you cannot solve the problem, note the values of ddName, rc, and rsn, and contact BMC Customer Support.

CTD922S DYNAMIC ALLOCATION ERROR, RC=rc, REASON CODE=rsn

Explanation: In Control-D during an attempt to allocate a CDAM data set, or in Control-M/Restart during an attempt to allocate an archived SYSDATA data set, an error occurred.

In Control-D, an error caused dynamic allocation of the CDAM data set to fail. If I is 04A8, this message indicates that the IOA subsystem does not support CDAM.

In Control-M/Restart, Possible causes are:

When the Control-M monitor tried to archive the SYSDATA of the job (while processing it).
When the Control-M monitor tried to read an archived SYSDATA output of a job, while trying to analyze job execution results.
When the CONTROLR step tried to scan the archived SYSDATA output of the previous run or runs of the job.

In Control-D, the CDAM data set is not created.

In Control-M/Restart, after either of the first two causes, Control-M shuts down with an error message.

After the third cause, the CONTROLR step stops with a non-zero condition code or with an abend code, depending on the ABENDTYP Control-M/Restart Installation Parameter in CTRPARM. The job terminates after the CONTROLR step.

Corrective Action: In Control-D, if rc is 04A8, run the IOASINIT procedure with OPTIONS set to D.

In all other cases, for more information, see the IBM manual MVS Programming: Authorized Assembler Services Guide. If you cannot solve the problem, contact BMC Customer Support and provide the DD name, RC, and reason code.

CTD924E ENCRYPTION/DECRYPTION PROCESS FAILED FOR dsn RC= rc RSN= rsn

Explanation: Either the CDAM encryption process or the CDAM decryption process failed for the dsn CDAM data set being processed.

Corrective Action: Supply BMC Customer Support with the full output of the job or monitor STC.

CTD925E ERROR READING DATASET: dsn

Explanation: The data set being processed is not a CDAM data set. CDAM recognizes a CDAM data set by its control information block that appears at its beginning. In this case, either the control information block is missing, or it is not in the correct format.

During decollation, the decollating mission finishes NOT OK and the REP256E message is issued. During printing, the problematic report is marked NOT PRINTED, and the corresponding printing mission finishes NOT OK.

Corrective Action: Supply BMC Customer Support with the problematic data set.

CTD926E LOCATE FAILED FOR DATASET: dsn

Explanation: In Control-D, a CDAM data set was not found in the catalog. In Control-D, this message usually indicates that the physical data set was deleted from the disk, but there are still references to it in the Active User Report List.

In Control-M/Restart, the CONTROLR step could not find the specified archived SYSDATA output of the previous run or runs of the job.

In Control-D, the CDAM data set cannot be accessed.

In Control-M/Restart, the CONTROLR step terminates with a nonzero condition code or with an abend code (depending on the ABENDTYP Control-M/Restart Installation Parameter in CTRPARM). The job terminates after the CONTROLR step.

Corrective Action: In Control-D, try to find the cause of the inconsistency and fix it. In Control-M/Restart, try to determine why the archived MSGCLASS output of the previous runs was deleted.

CTD929W DDNAME=ddName, MIXING TYPES OF CONTROL-CHARS (ASA+MACHINE). USE ALLOCOPT=ONEDSN TO DECOLLATE

Explanation: A report with both ASA and Machine Control characters was produced by an application job. This kind of report can be processed by Control-D correctly only if it is written directly to a CDAM file.

Corrective Action: To print the report correctly, specify ALLOCOPT=ONEDSN in the PRINT/CDAM PARMS of the corresponding decollating mission.

CTD92AW ENCRYPTION HAS NOT BEEN PERFORMED FOR dsname RC=rc RSN=rsn

Explanation: This warning message indicates that the z/OS Integrated Cryptographic Service Facility (ICSF) detected an issue during CDAM data set creation by the Control-D Decollation monitor or directly by a job. The message provides the return code and reason code for the CDAM file. Control-D uses ICSF if CTDFIPS=YES is specified in the IOAPARM member of IOA PARM library.

The CDAM data set is created but not encrypted.

Corrective Action: Call your system programmer for assistance.

CTD92CS INVALID PARAMETER, VALID PARAMETERS ARE ACT=R/W, TYPE=F/V

Explanation: An invalid parameter was passed to the IOADIG utility.

Valid values for the ACT parameter are:

R - Perform a read-only check. Do not correct detected errors.
W - If an error is detected, correct it.

Valid values for the TYPE parameter are:

F - Fixed length records in data file.
V - Variable length records in data file.

The utility terminates with a return code of 24.

Corrective Action: Rerun the IOADIG utility after setting its parameters to valid values.

CTD930I DELETE OF UNNEEDED REPORTS STARTED

Explanation: This information message is the normal start message of the CTDDELRP utility. CTDDELRP is used to clean unnecessary entries from the Active User Report List file, and to erase the compressed sysout data sets that belong to them from the disk.

Corrective Action: No action is required.

CTD931I DELETE OF UNNEEDED REPORTS ENDED OK

Explanation: This information message is the normal end message of the CTDDELRP utility. CTDDELRP is used to clean unnecessary entries from the Active User Report List file, and to erase the compressed sysout data sets that belong to them from the disk.

Corrective Action: No action is required.

CTD932I REPORT ENTRY ADDED

Explanation: This information message is the normal message of the “I” (insert) option on the User Report List screen when a new user report entry has been added.

Corrective Action: No action is required.

CTD933E PLEASE ENTER VALID DATA FOR THIS FIELD

Explanation: Displayed after the “I” (insert) option on the User Report List screen was requested.

Corrective Action: Enter the appropriate data for this field.

CTD933S DELETE OF UNNEEDED REPORTS ENDED WITH ERRORS

Explanation: The CTDDELRP utility ended with errors. Earlier messages describe the problem.

The CTDDELRP utility ends with a return code of 08.

Corrective Action: Check the earlier messages, correct the problem, and rerun the job.

CTD934E COP# MUST BE 3 DIGITS (001-255)

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

An invalid value was entered in the User Report List PRINT window COP# screen field.

This field is numeric, and all its three digits must be entered. The value of this field must be from 001 through 255. The maximum number of copies allowed for this report is specified in the Report Decollating Mission Definition screen. The number of copies cannot be greater than the maximum number of copies on the Report Decollating Mission Definition screen.

Corrective Action: Correct the number of copies.

CTD934E INSUFFICIENT STORAGE. ATTEMPT TO RERUN

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

There is insufficient storage to run the CTDDELRP utility.

Corrective Action: Increase the REGION size of the utility and rerun.

CTD935E CANNOT VIEW/CHANGE ADDITIONAL USERS ON AN INSERTED LINE

Explanation: The A (ADDITIONAL INFO) option was entered with the cursor on an inserted line. The ADDITIONAL INFO option must be entered from a non-inserted line.

Corrective Action: Move the cursor up to the last non-inserted line in the User Report List entry, and reissue the A option.

CTD936E THIS ENTRY CANNOT BE VIEWED

Explanation: There was an attempt to view an entry that was not associated with a CDAM file.

Corrective Action: No action is required.

CTD937E INVALID PARAMETER: - parm

Explanation: Invalid parameter for the CTDDELRP Control-D utility. This error message is issued by the CTDDELRP Control-D utility, which cleans unnecessary entries from the Active User Report List file. For more details, see the section on the CTDDELRP utility in the INCONTROL for z/OS Utilities Guide.

The CTDDELRP Control-D utility terminates with a condition code of 08. The Active User Report List file is not cleaned.

Corrective Action: Correct the parameter syntax in the CTDDELRP utility.

CTD938E ONLY "Y" "N" OR " " ARE ALLOWED IN THIS FIELD

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

The user entered an invalid value. Y, N, or blank are the only values valid in this field.

Corrective Action: Correct the value entered.

CTD938E MISSING PARAMETER AFTER: - parm

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

The subparameter after parm is missing. This error message is issued by the CTDDELRP Control-D utility, which cleans unnecessary entries from the Active User Report List file. For details, see the CTDDELRP utility in the INCONTROL for z/OS Utilities Guide.

The CTDDELRP Control-D utility terminates with condition code of 08. The Active User Report List file is not cleaned.

Corrective Action: Correct the parameter syntax in the CTDDELRP utility.

CTD939E OPTION/COMMAND INVALID FOR THIS TYPE OF USER/REPORT ENTRY

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

An invalid option or command was entered in the User Report List screen. The list of allowed options or commands in the User Report List is shown at the bottom of the screen. Only one of these options or commands can be entered on this screen.

Note:

If $SYSDATA records are listed, not all displayed options are available.

Corrective Action: Enter a valid option or command.

CTD939E REDUNDANT PARAMETER: - parm

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

There is a redundant parameter for the CTDDELRP Control-D utility. The CTDDELRP Control-D utility, which deletes unnecessary entries from the Active User Report List file, issues this message. For details, see the CTDDELRP utility in INCONTROL for z/OS Utilities Guide.

The CTDDELRP Control-D utility terminates with a condition code of 08. The Active User Report List file is not cleaned.

Corrective Action: Correct the parameter syntax in the CTDDELRP utility.

CTD93AE ONLY 'I' 'E' 'A' OR 'S' ARE ALLOWED FOR PRINT MISSION TYPE

Explanation: The user entered an invalid value. Only I, E, A, or S are valid values for this field.

Corrective Action: Enter the correct value.

CTD93DS THERE ARE REPORTS REQUESTED FOR MIGRATION. CONTROL-V SHOULD BE INSTALLED

Explanation: The CTDDELRP utility discovered that although in the Active User Reports file there are reports requested for migration, no Control-V environment is installed. CTDDELRP is terminated.

Corrective Action: Install a Control-V environment.

CTD940E OPTION INVALID FOR A "WAIT " DECOLLATION REPORT

Explanation: An invalid option was entered in the User Report List screen for an entry which is in WAIT DECOLLATION status. There are some options which are not valid for an entry that is in WAIT DECOLLATION status. For example, an entry in WAIT DECOLLATION status cannot be viewed or printed.

Corrective Action: Enter a valid option.

CTD941I REPORT DELETED: jobName /usr /name

Explanation: This information message indicates that the requested deletion was completed. It is the normal message of the D (delete) option of the User Report List screen.

Corrective Action: No action is required.

CTD942E "E" AND "P" OPTIONS ARE VALID ONLY ON ENTRIES WITH REPORTS

Explanation: An invalid option was entered in the User Report List screen. The EDIT (E) and PRINT (P) options can be specified only for entries that have already been decollated.

Corrective Action: Enter a valid option.

CTD943E ONLY "W" OR " " ARE ALLOWED IN THIS FIELD

Explanation: An invalid value was entered in the User Report List W field. This field must have a value of W, or be blank. If W is specified in this field, then the DEST or WTR field is the name of an external writer on which the report should be printed.

For more information, see the section on User Reports and Reports List in the Control-D and Control-V User Guide.

Corrective Action: Correct the W field.

CTD944E RULER TYPE CAN BE "VIEW", "PRINT" OR "MASK"

Explanation: Invalid ruler type was defined in the Exit Option Window. Ruler type must be VIEW, PRINT, or MASK.

Corrective Action: Specify a valid ruler type.

CTD944S IMMEDIATE PRINT FAILED, INVALID DESTINATION

Explanation: An invalid destination was entered on the User Report List PRINT window. This field must be blank, or contain a valid remote printer JES destination.

The report is not printed.

Corrective Action: Correct the DEST (destination) field.

CTD945E IMMEDIATE PRINT CANCELLED, NUMBER OF ALLOWED PAGES EXCEEDED

Explanation: Control-D security exit (CTDX004) determined that the number of pages to be printed exceeds the maximum allowable for immediate printing.

This security check prevents printing of large numbers of pages to remote printers. In the case of the main printer, it forces the use of Printing Mission, because of performance considerations. The function RECIPRT in Control-D exit CTDX004 can be modified by the installation to restrict the number of pages that can be printed immediately.

The report is not printed.

Corrective Action: Modify the FROM PAGE/TO PAGE numbers to print a smaller section of the report.

CTD946E SPECIFIED RULER DOES NOT EXIST

Explanation: An attempt was made to copy a nonexistent ruler. There is no ruler with corresponding ruler name, job name, report name, and user name.

Copy is performed.

Corrective Action: Specify valid ruler parameters.

CTD946S SYSOUT ALLOCATION FAILED, RC=rc, ERROR=error

Explanation: Internal error. Control-D was unable to dynamically allocate a sysout file in order to print a report immediately.

The report is not printed.

Corrective Action: See the IBM manual MVS Programming: Authorized Assembler Services Guide.

CTD947E INTERNAL ERROR WHILE READING A RULER

Explanation: An error occurred during ruler file format conversion.

Requested operation is not performed

Corrective Action: See your Control-D administrator for assistance.

CTD947I REPORT PRINTED OK - FROM fileName FILE: jobName / userName / reportName

Explanation: This information message indicates that the immediate printing of the report was successful.

The specified report is printed.

Corrective Action: No action is required.

CTD948E PLEASE FILL IN RULER NAME

Explanation: A ruler name was not specified in the Exit Option Window of ruler definition screen. A ruler name must be specified.

Corrective Action: Specify a ruler name.

CTD949E THE SAMPLE PAGE IS TOO SMALL TO SHOW THIS RULER. RULER CLEARED

Explanation: The current ruler cannot be applied to the current page because the ruler definition contains references to lines that are not on the page.

The current page is shown without the ruler formatting.

Corrective Action: No action is required.

CTD94AE ERROR WHILE READING CDAM

Explanation: An I/O error was encountered during processing of an Immediate Print request. If the report is a migrated report, a more detailed message can be produced by viewing the report.

One of the following errors was encountered by the CTDTUSR program during processing of an Immediate Print request:

A CDAM file or extent associated with the report being printed does not exist or is not cataloged.
A CDAM file was restored to a DASD device with a different track size than the DASD device on which the CDAM file was created.

The report is not printed.

Corrective Action: Be sure all CDAM files exist on appropriate DASD devices. Retry the Immediate Print request. Try viewing the report to see if an error is also encountered during view.

CTD94BE INTERNAL ERROR IN CTDDPR. RC=rc

Explanation: An internal error occurred while processing an Immediate Print request.

In this message, rc is the return code. Valid values are:

rc	Explanation
28	An internal error occurred while processing an Immediate Print request. This return code is issued when printing to an EMAIL type of CTDS destination, if no e-mail addresses can be resolved from the CTDS destination RECIPIENT attribute.
48	The problem occurred during printing a binary report. It can be caused by one of the following: Resources required for printing AFP or XEROX normalized report are unavailable. Printed report has incorrect internal structure.
52	The error occurred during the GETINX function of the CTVDPC program.
56	The error occurred during the WRTINX function of the CTVDPC program.
60	The error occurred during the GETINX function of the CTVDPC program when data sets are uncataloged.
64	An allocation error of the index file occurred during the GETINX function of the CTVDPC program.

The report is not printed.

Corrective Action: Check the IOA Log file and job log for additional messages associated with the error. Correct the problem and re-execute the program. If the error persists, contact BMC Customer Support.

CTD94CE MISSING OUTPUT STATEMENT stmtName

Explanation: An output statement is missing in the IOA Online environment. The report could not be printed because the output statement specified for the report is missing from the IOA Online environment.

The report is not printed.

Corrective Action: Add the output statement to the IOA Online environment. Then, log on again and/or restart the IOA Online monitor.

CTD94DE ERROR IN READING PAGEDEF/FORMDEF MEMBER

Explanation: An error was encountered while trying to read a PAGEDEF or FORMDEF value. Either the PAGEDEF or the FORMDEF specified does not exist in the libraries defined for Control-D or Control-V.

The report is not printed.

Corrective Action: Add the missing PAGEDEF and/or FORMDEF member to the relevant library.

CTD94EE ABEND IN IMMEDIATE PRINT sysabend usrabend

Explanation: The Immediate Print request abended.

The variables in this message are:

sysabend - System abend code
usrabend - user abend code

The print request terminates.

Corrective Action: Check the system log for other error messages associated with this problem and proceed accordingly.

For abend code S000 U0186: Restart the online session prior to retrying the print request.

CTD94GE REQUESTED TCP/IP STACK UNAVAILABLE

Explanation: ISTACK parameter was specified in IOAPARM member and the system has TCP/IP dual stack mode, but the specified stack is not running.

The message is preceded by a full screen message that contains the stack name.

Corrective Action: Either bring up the started task named 'stack', or remove the ISTACK parameter from IOAPARM and restart the online session.

CTD94HE OPTION IS NOT SUPPORTED FOR Ruler_type RULER

Explanation: The option is not supported for ruler type Ruler_type.

Corrective Action: Choose supported option.

CTD94II INCORRECT MASK RULER NAME Ruler_name THE FOUND NAME SET.

Explanation: An incorrect MASK RULER name was specified in the Edit screen. A MASK RULER with a different name already exists for the current report. The correct MASK RULER name is automatically set in the RULER NAME field.

Corrective Action: No action is required.

CTD94JE RC=xxxx FROM CTDSMSK. MASK RULER Ruler_name WAS NOT APPLIED FOR REPORT usr/jobName/name

Explanation: MASK RULER with Ruler_name defined for the report usr/jobName/name was not applied for viewing or printing. Optional wish WDM065 determines if the report can be retrieved for viewing or printing without applying the MASK RULER.

Corrective Action: If the MASK ruler is redundant or its name was changed, use the CTDUFUPD utility to remove or change the MASK ruler name in the VSA User records. Otherwise collect IOALOG and SYSLOG for the problematic period of time, print the problematic User record using the CTDUFPRT utility and call your IOA representative for assistance.

CTD94KE THE MASK RULER NOT APPLIED. THE REPORT CANNOT BE ACCESSED.

Explanation: The special MASK RULER defined for the report was not applied.

The report cannot be accessed for viewing or printing.

Corrective Action: Contact your Control-D administrator.

CTD94LE INSUFFICIENT MEMORY TO APPLY MASK RULER. THE REPORT CANNOT BE ACCESSED.

Explanation: The special MASK RULER defined for the report was not applied due to insufficient memory.

The report cannot be accessed.

Corrective Action: Contact your Control-D administrator.

CTD94ME THE MASK RULER Ruler_name NOT FOUND. THE REPORT CANNOT BE ACCESSED.

Explanation: The special MASK RULER defined for the report was not found.

The report cannot be accessed for viewing or printing.

Corrective Action: Contact your Control-D administrator.

CTD94NE INSUFFICIENT MEMORY TO APPLY MASK RULER Ruler_name FOR REPORT usr/jobName/name

Explanation: MASK RULER with Ruler_name defined for the report usr/jobName/name was not applied due to insufficient memory. Optional wish WDM065 determines if the report can be retrieved for viewing or printing without applying the MASK RULER.

Corrective Action: If the MASK ruler is redundant, use the CTDUFUPD utility to remove the MASK ruler name from the VSA User records. Otherwise, increase the REGION size for the LOGON procedure or ON-LINE monitor.

CTD94OE THE MASK RULER Ruler_name NOT FOUND FOR REPORT usr/jobName/name

Explanation: MASK RULER with Ruler_name defined for the report usr/jobName/name was not found. Optional wish WDM065 determines if the report can be retrieved for viewing or printing without applying the MASK RULER.

Corrective Action: Restore missing MASK ruler. If the MASK ruler is redundant or its name was changed, use the CTDUFUPD utility to remove or change the MASK ruler name in the VSA User records.

CTD94PE MASK RULER CANNOT BE APPLIED FOR DEFERRED PRINT TO SEQUENTIAL DATA SET

Explanation: MASK RULER option is not available in PRINT missions for reports stored in sequential data sets.

Corrective Action: Exclude the problematic report from PRINT missions that store reports in sequential data sets.

CTD950E THIS FIELD MUST BE NUMERIC AND GREATER THAN ZERO

Explanation: An invalid value was entered in this User Report List field. This field must be numeric and greater than zero. Leading zeroes must be supplied.

Corrective Action: Correct the field.

CTD951E INVALID OPTION (TRY "Y" OR "N")

Explanation: The user entered an invalid value. Y or N are the only values valid in this field.

Corrective Action: Correct the value entered.

CTD952E ENTRY DELETED - DSN dsn NOT FOUND

Explanation: Compressed data set dsn was not found after deleting a report entry from the User Report List file. The report (SYSDATA) entry was deleted from the User Report List file. However, the attempt to delete all the associated compressed data sets for this report entry was not successful.

Corrective Action: Notify the INCONTROL administrator. Additional messages may be found on the system log.

CTD953E FROM DATE GREATER THAN TO DATE

Explanation: The FROM date entered on the User Reports Entry Panel is greater than the TO date. You can specify that only record entries within a date range are to be displayed for the Active and History User Report List file using the DATEFROM and TO screen fields.

Corrective Action: Correct the DATEFROM or TO date fields.

CTD954I REPORT SET FOR RESTORE: jobName / userName / reportName

Explanation: This information message indicates that a backed up (migrated) report has been assigned to the restore mission for restoration.

Corrective Action: No action is required.

CTD955E FUNCTION NOT SUPPORTED ON THIS SCREEN

Explanation: An invalid function was entered on the User Report List screen. Not all functions are supported on all User Report List screens. For example, the View (V) function can be used on the Active User Report List file, but not on the Permanent and History files.

Corrective Action: Enter a different function.

CTD956E CANNOT MIX RESTORE/WAIT-RESTORE/WAIT- BACKUP RETRIEVAL OPTIONS

Explanation: More than one of the Definition options (Permanent, Active, or History) on the User Report List Entry Panel was specified with Y.

Corrective Action: Leave the Y next to one of the three Definition options, but specify the other two as N.

CTD958E COP# MUST BE 3 DIGITS (000-255) OR "DFT" (FOR DEFAULT)

Explanation: An invalid value was entered in the User Report List COP# screen field.

Valid values are:

a 3-digit number from 000 through 255The maximum number of copies allowed for this report is specified in the Report Decollating Mission Definition screen. The number of copies on the User Report List screen cannot be greater than the maximum number of copies on the Report Decollating Mission Definition screen.
DFT - the default number of copies

The number of copies is taken from the PRT COPIES field of the Report Decollating Mission Definition screen. Note that the COP# field will be changed from DFT to the default numeric value after decollation.

Corrective Action: Correct the number of copies.

CTD959S ENTRY DELETED, BUT ALLOC ERROR err OCCURRED ON COMPRESSED DSN

Explanation: An allocation error occurred on a compressed data set after deleting a report entry from the User Report List file. The report (SYSDATA) entry was deleted from the User Report List file. However, the attempt to delete all the associated compressed data sets for this file was not successful.

Corrective Action: Notify the INCONTROL administrator. Additional messages will appear on the system log.

CTD95AE HEX INOPERABLE FOR FULL PAGE MODE RULERS

Explanation: The attempt to view the report in hexadecimal format using a full page mode ruler failed. The HEX command is not supported when viewing reports using a full page mode ruler.

The attempt fails.

Corrective Action: View the report without a full page mode ruler.

CTD95BI jobname/recipient/report ID=recordId SET TO RESTORE WITH MISSION misName

Explanation: This information message indicates that backed up (migrated) report is assigned to the misName mission for restoration.

The variables in this message are:

jobname - the name of the job that created the report
recipient - the user for whom the report was created
report - the name of the report
recordId - the internal database identifier of the report
misName - the name of the mission

Corrective Action: No action is required.

CTD95CE THIS FIELD IS NOT RELEVANT FOR RECIPIENT $SYSDATA

Explanation: The field cannot be used as a selection criterion for recipient $SYSDATA defined on the User Reports Entry Panel. The cursor points to the invalid field.

Corrective Action: Check that recipient $SYSDATA was entered improperly or clear the field.

CTD960E INSUFFICIENT STORAGE TO BUILD REPORTS LIST - USE ANOTHER SELECTION CRITERIA

Explanation: There is insufficient memory to build the User Report List. There is insufficient memory to build a list using the selection criteria on the User Reports Entry Panel.

Corrective Action: Do one of the following:

Change the selection criteria so that the User Report List to be built is shorter. For instance, select only a specified job name instead of selecting all jobs.
If you are using many IOA screens concurrently, exit some of them using the END command.
Increase region size, or reduce the maximum number of sessions allowed simultaneously under an online monitor, or take both these steps.

CTD961E INSUFFICIENT STORAGE TO BUILD REPORTS LIST - USE ANOTHER SELECTION CRITERIA

Explanation: There is insufficient memory to build the User Report List. The user entered selection criteria on the User Reports Entry Panel. However, there is insufficient memory to build a list using these selection criteria.

Corrective Action: Do one of the following:

Change the selection criteria so that the User Report List to be built is shorter. For instance, select only a specified job name instead of selecting all jobs.
If you are using many IOA screens concurrently, exit some of them using the END command.
Increase region size and/or reduce the maximum number of sessions allowed simultaneously under an online monitor.

CTD962E INTERNAL PROGRAM ERROR - CTDCLS - INVALID PARM

Explanation: Internal error in the CTDCLS module.

The user will be unable to see any entries on the User Report List file.

Corrective Action: Call BMC Customer Support.

CTD963E FOR "U" OPTION YOU MUST CHANGE AN EDITABLE FIELD OF THE ENTRY

Explanation: The U (update) option was selected, but no change was made to an editable field. After U (update) is selected, Control-D expects a change to be made to editable fields such as DEST, COP#, or ADDITIONAL USERS.

Corrective Action: Update the appropriate field or fields.

CTD964I REPORT MODIFIED: jobName/user /name

Explanation: This information message indicates that an entry in the User Report List screen was updated.

Corrective Action: No action is required.

CTD965E ONLY ONE "I" OPTION CAN BE ACTIVE AT A TIME

Explanation: Multiple insert (“I” functions) were entered on the User Report List screen. Only one record can be inserted at one time into the Report List file.

Corrective Action: Make sure that only one insert function is present on the screen.

CTD967E ENTER A VALID VTAM DESTINATION, OR CHANGE "W" TO BLANK

Explanation: There is a W in the User Report List W field, indicating that a VTAM destination must be entered in the DEST or WTR field. If the W option is specified in the User Report List W field, then the name of an external writer on which the report should be printed must be specified in the DEST or WTR field.

For more information, see the section on User Reports or Reports List in the Control-D and Control-V User Guide.

Corrective Action: Enter a VTAM destination in the DEST or WTR field, or blank out the W field.

CTD968E SEVERE ERROR WHILE READING A RULER

Explanation: When reading the ruler from the Control-D database, a read error occurred. When reading the ruler from the Control-D database, a VSAM read I/O error occurred.

The ruler is set to OFF. In addition, the CTD908S message is issued.

Corrective Action: For additional information about the VSAM I/O error, see the CTD908S message.

CTD969E CANNOT PERFORM AN INSERT ON AN INSERTED LINE

Explanation: User tried to insert perform an additional insert on an inserted line. Insert on an already inserted line is not supported.

Corrective Action: Insert the additional line in a different line.

CTD970I PLEASE FILL IN THE REPORT ENTRY DATA

Explanation: This information message indicates that mandatory report data was not entered.

Corrective Action: Fill in the report entry data.

CTD971I REPORT IS BEING RESTORED

Explanation: This information message indicates that a report is being restored by a process called from Control-D user exit CTDX004. This process is used for restoring reports created by CA-DISPATCH, CA-View and INFOPACK and converted to Control-D.

Corrective Action: No action is required.

CTD971S OPEN OF CONTROL-D ACTIVE MISSIONS FILE FAILED

Explanation: The CTDFRAMS Control-D utility, which is used to allocate and format the Active Missions file, failed to open the file for formatting.

Possible causes are:

The DAAMF DD statement is missing.
There is insufficient memory for the job.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

CTD972E ERROR DURING PROCESSING RESTORE REQUEST

Explanation: An error occurred when a restore job was submitted by a process called from the CTDX004 Control-D user exit. This process is used for restoring reports created by CA-DISPATCH, CA-View and INFOPACK and converted to Control-D.

The report is not restored.

Corrective Action: Determine why the job could not be submitted. Correct the problem and rerun the restore request.

CTD972I BUILDING OF CONTROL-D ACTIVE MISSIONS FILE STARTED

Explanation: This information message indicates that the CTDFRAMS utility, which allocates and formats the Active Missions file, has started.

Corrective Action: No action is required.

CTD973I BUILDING OF CONTROL-D ACTIVE MISSIONS FILE ENDED

Explanation: This information message indicates that the CTDFRAMS utility, which allocates and formats the Active Missions file, has ended normally.

Corrective Action: No action is required.

CTD974S CONTROL-D ACTIVE MISSIONS FILE WAS NOT BUILT.

Explanation: The CTDFRAMS utility failed.

Corrective Action: Look for additional clarification messages on the IOA Log.

CTD975E PLEASE SPECIFY A VALID RULER NAME, OR "ON"/"OFF"

Explanation: Ruler name is not specified, and ruler command ON is specified.

Corrective Action: Enter a ruler name, or set the ruler to OFF.

CTD975S CONTROL-D ACTIVE MISSIONS FILE WRITE ERROR

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

This error may occur when there is incompatibility between the definition of the Active Missions file in the Installation Parameters (CTDPARM) and the JCL SPACE or DCB parameters.

The utility stops executing with a condition code of 08.

Corrective Action: Correct either the JCL or the Installation Parameters.

CTD976E INTERNAL ERROR WHILE READING A RULER

Explanation: An internal error occurred during reading of a ruler.

No ruler is in effect.

Corrective Action: Ask your INCONTROL administrator to call BMC Customer Support for assistance.

CTD977I REPORT SET FOR DEFERRED PRINT: jobName / userName / reportName

Explanation: This information message indicates that the deferred print has been successfully requested and that the report will be printed by the specified Printing Mission.

Corrective Action: No action is required.

CTD978E "FROM PAGE" NUMBER CANNOT BE GREATER THAN "TO PAGE" NUMBER

Explanation: An invalid FROM PAGE definition was entered. The FROM PAGE number that was specified is greater than the TO PAGE number.

Corrective Action: Correct the FROM PAGE/TO PAGE values.

CTD979E RESTORE IN PROCESS, OR CANNOT RESTORE THIS TYPE OF ENTRY

Explanation: This entry on the History User Report List file cannot be restored.

The attempt to restore a SYSDATA entry or reissue a restore request that is already in REQUESTED RESTORE state fails.

Corrective Action: Restore another entry on the file.

CTD97AI PLEASE CONFIRM:'R'-RETRY/'S'-SCRATCH TAPE/'C'-CANCEL

Explanation: During a migration job, the operator rejected a system request to mount a specific tape. For example, the operator typed CANCEL on receiving an IEF238D message, or NO on receiving an IEF455D message.

The migration job waits for a reply to this message.

Corrective Action: Type one of the following replies, which have the meaning shown in parentheses:

R (Try again to mount the same tape.)
S (Try to mount a scratch tape instead of the specific tape.)
C (Cancel the migration job.)

CTD97BI INVALID REPLY TO CTD97AI.

Explanation: The system issued the CTD97AI message, but the reply typed by the operator was invalid.

The CTD97AI message is reissued.

Corrective Action: Type a valid reply to the CTD97AI message.

Valid replies, which have the meaning shown in parentheses, are:

R (Try again to mount the same tape.)
S (Try to mount a scratch tape instead of the specific tape.)
C (Cancel the migration job.)

CTD980S monName LOAD OF CONTROL-D SPECIAL ROUTINES FAILED

Explanation: Highlighted, unrollable message.

Initialization of the Printers Control monitor monName failed because of missing modules.

The Control-D Printers Control monitor and the Control-D monitor will shut down.

Corrective Action: Determine who deleted the missing load modules and why. Restore these modules from a backup tape of the IOA Load library, and bring up the Control-D monitor.

CTD981S proc RECIPIENT TREE WAS NOT LOADED BECAUSE OF ERROR - CONTROL-D PRINTERS Control-MONITOR IS TERMINATING

Explanation: Highlighted, unrollable message.

The Recipient Tree was not loaded because of an error.

The Control-D Printers Control monitor and the Control-D monitor will shut down.

Corrective Action: Look at the IOA Log and the computer log for additional error messages. These additional messages pinpoint the specific problem encountered while loading the Recipient Tree.

CTD982I monName CONTROL-D PRINTERS MONITOR IS WAITING FOR ONE OR MORE PRINT SUBTASKS TO TERMINATE

Explanation: This information message indicates that a shutdown process command was issued from the Control-D monitor, but the Control-D Printers Control monitor is still printing.

The Printing Mission that is still printing can be found in the Active Missions Status screen.

If the Printers Control monitor is still printing when a shutdown request is issued, it continues to print. The Control-D monitor does not shut down until printing is finished.

Corrective Action: If you allow the Printing Mission to finish printing, no action is required.

To shut down the Control-D monitor immediately, change the status of the active Printing Mission in the Active Missions Status screen (AMS) to HOLD. Free it after the Control-D monitor has restarted.

CTD983E monName CONTROL-D PRINTERS MONITOR IS TERMINATING EVEN THOUGH ONE OR MORE PRINT SUBTASKS HAS NOT TERMINATED.

Explanation: Highlighted, unrollable message.

The Control-D monitor is shutting down the monName Control-D Printers Control monitor.

The Control-D monitor issued a command to shut down the monName Printers Control monitor. The Printers Control monitor was not shut down because one or more print subtasks were awaiting completion. Under certain circumstances, the Control-D monitor forces shutdown of the Printers Control monitor after a default site-specific length of time.

The monName Control-D Printers Control monitor shuts down.

Corrective Action: No action is required.

CTD98AI PRINT MISSION POSTPONED. MAX NUMBER OF SUBTASKS IS REACHED IN THE CURRENT MONITOR

Explanation: This information message indicates that the current print mission cannot be processed because the print monitor is already processing the maximum number of missions as defined in optional Wish WD2618.

The print mission is delayed until one of the missions being processed terminates.

Corrective Action: If this message appears frequently, it is recommended to increase the maximum number of print missions the print monitor can process concurrently.

CTD98BI PRINT MISSION CONTINUES PROCESSING

Explanation: This information message indicates that the print monitor resumed processing a mission that was postponed (see the CTD98AI message)

Corrective Action: No action is required.

CTD990I PRINTING MISSION missionName STARTED PRINTING

Explanation: This information message indicates that the Control-D Printers Control monitor started printing for the missionName mission.

Corrective Action: No action is required.

CTD991I PRINTING MISSION missionName FINISHED PRINTING

Explanation: This information message indicates that the Control-D Printers Control monitor completed the missionName printing mission successfully.

Corrective Action: No action is required.

CTD993E ERROR IN CTDCIO FUNCTION func RC rc - PRINTING STOPPED

Explanation: An internal error occurred in the CTDCIO internal module. The error occurred within the Control-D Printers Control monitor.

The printing for this mission will stop. The status of this Printing Mission is changed to NOTOK.

Corrective Action: Contact BMC Customer Support. Please provide the values of FUNCTION and RC.

CTD994E ERROR IN CTDRSV FUNCTION func RC rc - PRINTING STOPPED

Explanation: Internal error.

An internal error occurred in the CTDRSV internal module. The error occurred within the Control-D Printers Control monitor.

The printing for this mission will stop. The status of this Printing Mission is changed to NOTOK.

Corrective Action: Contact BMC Customer Support. Please provide the values of FUNCTION and RC.

CTD995E ERROR IN CTDALC RC rc S99RC s99rc FUNCTION func - PRINTING STOPPED

Explanation: Internal error. The allocation of the PLAN file failed.

An internal error occurred in the CTDALC internal module. The error occurred within the Control-D Printers Control monitor.

The printing for this mission will stop. The status of this Printing Mission is changed to NOTOK.

Corrective Action: Contact BMC Customer Support. Please provide the values of rc, s99rc, and func.

CTD997E ERROR IN UPDATE OF PRINTED USERS, STATUS OF USER REPORTS MAY BE INVALID

Explanation: Internal error.

After printing a bundle, Control-D updates the status of all printed user reports in the Active User Report List file from WAIT PRINT to PRINTED. This message is produced if an error occurs in this update process.

The status of this Printing Mission is changed to NOTOK. All the reports are printed, but the entries in the Active Report List file have not been updated. This could result in duplicate printing.

Corrective Action: Look for VSAM related messages on the system log or on the syslog of the Control-D monitor. Contact BMC Customer Support.

CTD998E ALLOC FAILED FOR fileName - FILE WAS NOT FOUND

Explanation: Internal error.

The Control-D Printers Control monitor was unable to dynamically allocate the fileName file.

The status of this Printing Mission is changed to NOTOK.

Corrective Action: Contact BMC Customer Support. Please provide the value of file.

CTD9A3I BUILDING OF CONTROL-D ACTIVE TRANSFER FILE STARTED

Explanation: This information message indicates that the CTDBAT program, which is used for formatting the Active Transfer file, has started.

Corrective Action: No action is required.

CTD9A4I BUILDING OF CONTROL-D ACTIVE TRANSFER FILE ENDED

Explanation: This information message indicates that the CTDBAT program, which is used for formatting the Active Transfer file, has ended normally.

Corrective Action: No action is required.

CTD9A5S CONTROL-D ACTIVE TRANSFER FILE WAS NOT BUILT

Explanation: An error occurred during formatting of the Active Transfer file (the CTDBAT program).

Formatting is terminated.

Corrective Action: Check the system log for a previous message regarding the error. Correct the problem, and reformat the file.

CTD9A6S OPEN OF CONTROL-D ACTIVE TRANSFER FILE FAILED

Explanation: The probable cause is a missing DAATF DD statement.

Formatting is terminated.

Corrective Action: Check and correct DD statement DAATF.

CTD9A7S CONTROL-D ACTIVE TRANSFER FILE WRITE ERROR

Explanation: Format routine received I/O error accessing ATF file. An I/O error was encountered by the CTDBAT program when accessing the Active Transfer file.

Possible causes are:

A hardware failure may have occurred.
Active Transfer file specification contains invalid parameters.

Formatting is terminated.

Corrective Action: Do one of the following:

After the hardware problem has been resolved, reformat the file.
Check and correct the DCB parameters specified in the DAATF DD statement; reformat the file.

CTD9A9S NUMBER OF RECORDS IN ACTIVE TRANSFER FILE IS LESS THAN 3

Explanation: The CTDBAT program determines the number of records for the Active Transfer file from the ATFBLK Installation Parameter in CTDPARM. This value cannot be less than three.

Formatting is terminated.

Corrective Action: Correct CTDPARM; reformat the Active Transfer file.

CTD9B1S RELEASE OF ATF FILE NOT SUPPORTED BY THIS RELEASE OF CONTROL-D

Explanation: The release defined in the Active Transfer file is not the same as the release defined in the Control-D Load library.

Control-D checks that the release number defined in the Active Transfer file is the same release number that is defined in the Control-D Load library. An error occurs when trying to allocate an Active Transfer file that belongs to a different Control-D release, for example, a test or production release.

The requested function is not performed.

Corrective Action: Backup the Active Transfer file and reformat it. You can do this using ICE, as follows:

In the IOA Installation Menu, select Customization.
Select the environment to customize.
In the Customization screen, set Product ID to CTD and select Product Customization.
Select Major Step 6, Customize Control-D Dataset Parameters.
Select Minor Step 6, Format the A.T.F File.

CTD9B2S OPEN OF CONTROL-D ATF FILE FAILED

Explanation: An attempt by Control-D to open the Active Transfer file failed. The DAATF DD statement for the Active Transfer file is missing in the logon or Print monitor procedure.

Requested function is not performed.

Corrective Action: Check the DAATF DD statement in the Control-D and logon procedures.

CTD9B3S CONTROL-D ATF FILE IS FULL

Explanation: An overflow was detected in the Active Transfer file. The Active Transfer file is full and requires enlargement or compression.

Requested function is not performed.

Corrective Action: Compress or enlarge the Active Transfer file using the CTDCATF utility. For more information, see the INCONTROL for z/OS Utilities Guide.

CTD9B7S FILE ALLOCATED TO DDNAME "DAATF" IS NOT YOUR CONTROL-D ATF

Explanation: The QNAME defined in the Active Transfer file is not the same as the QNAME defined in CTDPARM. Either a file from another Control-D installation was accessed, or there was an error in the current installation.

Requested function is not performed.

Corrective Action: Check CTDPARM. If the QNAME was changed after installation procedures were performed, specify the original QNAME and rerun CTDPARM. If two different Control-D installations are running concurrently, then make sure that the files do not mix between the two different monitors.

CTD9B8S FILE ALLOCATED TO DDNAME "DAATF" IS NOT A CONTROL-D ATF

Explanation: The Active Transfer file does not have a valid identification. The Active Transfer file must contain the characters ATF in the first block (offset 18).

Requested function is not performed.

Corrective Action: Backup the Active Transfer file and reformat it. You can do this using ICE, as follows:

In the IOA Installation Menu, select Customization.
Select the environment to customize.
In the Customization screen, set Product ID to CTD and select Product Customization.
Select Major Step 6, Customize Control-D Dataset Parameters.
Select Minor Step 6, Format the A.T.F File.

CTD9B9S CONTROL-D ATF FILE IS FORMATTING/ CTDBAT PROBABLY ABENDED

Explanation: A compression or formatting of the Active Transfer file was started, but did not end successfully. The Active Transfer file contains an indicator that the format or compression processing was incomplete.

Requested function is not performed.

Corrective Action: Backup the Active Transfer file and reformat it. You can do this using ICE, as follows:

In the IOA Installation Menu, select Customization.
Select the environment to customize.
In the Customization screen, set Product ID to CTD and select Product Customization.
Select Major Step 6, Customize Control-D Dataset Parameters.
Select Minor Step 6, Format the A.T.F File.

CTD9C0I CTDUPBKP UTILITY STARTED

Explanation: This information message indicates that the CTDUPBKP utility has started.

Corrective Action: No action is required.

CTD9C1I CTDUPBKP UTILITY COMPLETED SUCCESSFULLY

Explanation: This information message indicates that the CTDUPBKP utility has completed without errors.

Corrective Action: No action is required.

CTD9C2S CTDUPBKP UTILITY ENDED WITH ERRORS

Explanation: This information message indicates that the CTDUPBKP utility has ended with errors.

Corrective Action: Check all the messages issued by the CTDUPBKP utility and proceed accordingly.

CTD9C3I FILE=ACT WAS SPECIFIED. ACTIVE USER FILE WILL BE PROCESSED

Explanation: This information message indicates that FILE was set to ACT in the input parameters of the CTDUPBKP utility, and as a result the Active User file is processed.

Corrective Action: No action is required.

CTD9C4I FILE=HST WAS SPECIFIED. HISTORY USER FILE WILL BE PROCESSED

Explanation: This information message indicates that FILE was set to HST in the input parameters of the CTDUPBKP utility and, as a result, the History User file is processed.

Corrective Action: No action is required.

CTD9C5I FILE=MIG WAS SPECIFIED. MIGRATION USER FILE WILL BE PROCESSED

Explanation: This information message indicates that FILE was set to MIG in the input parameters of the CTDUPBKP utility and, as a result, the Migration User file is processed.

Corrective Action: No action is required.

CTD9C6E NO FILE PARAMETER WAS SPECIFIED

Explanation: The FILE parameter was not specified in the input parameters of the CTDUPBKP utility.

The FILE parameter is mandatory.

The CTDUPBKP utility terminates

Corrective Action: Specify the FILE parameter and rerun the utility.

CTD9C7E NO $SYSDATA RECORDS FOUND IN THE {ACTIVE | HISTORY | MIGRATION} USER FILE

Explanation: The CTDUPBKP utility did not find any $SYSDATA records in the specified user file to update.

The CTDUPBKP utility terminates.

Corrective Action: Check the input FILE parameter of the utility for the correct user file and rerun the utility.

CTD9C8E SELECT CARD WAS NOT SPECIFIED

Explanation: A SELECT statement was omitted from the CTDUPBKP utility input parameters.

The CTDUPBKP utility terminates.

Corrective Action: Add a SELECT statement to the CTDUPBKP utility input statements and rerun the utility. For more information, see the INCONTROL for z/OS Utilities Guide.

CTD9C9I input_parm WAS SPECIFIED

Explanation: This information message displays the input parameter that the user specified for the CTDUPBKP utility.

Corrective Action: No action is required.

CTD9CAI NO VOLSER WAS FOUND FOR THE {ACTIVE | PERMANENT | HISTORY} USER FILE

Explanation: This information message indicates that a detailed report ordered by the user was not produced because the $SYSDATA record of the identified user file was not found.

Corrective Action: No action is required.

CTD9CCE ERROR IN CONTROL-STATEMENT

Explanation: An error was found in the input control statement specified by the user for the CTDUPBKP utility.

The input control statement is displayed in message UBK9CBI which precedes this message.

The CTDUPBKP utility terminates.

Corrective Action: Correct the input control statement and rerun the utility.

For a description of the input parameters of the CTDUPBKP utility, see the description of the utility in the INCONTROL for z/OS Utilities Guide.

CTD9CDW THERE IS NO CONTROL-RECORD FOR BKPMIS backupMissionName

Explanation: The CTDUPBKP utility could not find the Backup Control record for the backup mission of the current $SYSDATA record.

When FILE is set to HST in the input parameters of the CTDUPBKP utility, the utility attempts to read the backup control record for the backup mission of the current $SYSDATA record. In this case, the backup control record could not be found in the History file.

The CTDUPBKP utility continues with processes that do not require the backup control record.

Corrective Action: To create a backup control record, in the input parameters of the CTDUPBKP utility specify the backup mission name in the BKPMIS parameter, and the number of backup generations to retain in the GENER parameter. Rerun the CTDUPBKP utility.

For further details, see the CTDUPBKP utility in the INCONTROL for z/OS Utilities Guide.

CTD9CEE RETPD CANNOT BE CHANGED

Explanation: The RETPD parameter was specified as an input parameter for the CTDUPBKP utility, but the generation number found in the Backup Control record was not 0.

When activating the CTDUPBKP utility, the user specified the RETPD parameter without setting GENER to NONE. The backup mission in question was previously run using the NUMBER OF DAYS TO KEEP method. Once a mission has been run using NUMBER OF DAYS TO KEEP method, it cannot be run using the RETPD method.

The CTDUPBKP utility continues with other processes.

Corrective Action: Either change the method in the parameters to NUMBER OF DAYS TO KEEP then rerun the utility, or define a new backup mission defined with the RETPD parameter.

CTD9CFE INVALID RETURN CODE FROM SORT. RC=rc

Explanation: The SORT utility called by the CTDUPBKP utility ended with errors.

For information on the return code (rc), see the section on return codes in the SORT utility documentation in the INCONTROL for z/OS Utilities Guide.

The CTDUPBKP utility terminates.

Corrective Action: Correct the cause accordingly and rerun the CTDUPBKP utility.

CTD9F0I CONTROL-RECORD FOR BKPMIS backupMissionName HAS BEEN CREATED

Explanation: This information message indicates that a backup control record was recreated for the backupMissionName backup mission.

A backup control record is recreated when the FILE parameter is set to HST for the backup mission, and when the original backup control record is missing.

Corrective Action: No action is required.

Parent Topic

CTD messages