CTB–CTD

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

CTB MessagesLink copied to clipboard

This group includes messages for the Control-M/Analyzer product.

Messages CTB0 through CTB0xxLink copied to clipboard

This group includes messages for the Control-M/Analyzer product.

CTB001I CONTROL-M/ANALYZER RUNTIME ENVIRONMENT STARTED - MODE IS modeType SCOPE IS scopeLink copied to clipboard

Explanation: This information message indicates that the Control-M/Analyzer Runtime Environment has been invoked in modeType mode, and is executing using the identified scope.

The Control-M/Analyzer Runtime Environment can be invoked in STANDALONE mode (as a job step or as a call from a user program), or from within the Control-M or Control-D monitors.

In this message, scope is the type of call used to invoke the environment. Valid values are:

UNSCHEDULED - a direct rule call
SINGLE - a call through a balancing mission
STEP - a call through a balancing mission
JOB - a call through a balancing mission

For more information, see the SCOPE parameter in the Control-M/Analyzer User Guide.

Corrective Action: No action is required.

CTB002I CONTROL-M/ANALYZER RUNTIME ENVIRONMENT ENDEDLink copied to clipboard

Explanation: This information message indicates that the Control-M/Analyzer Runtime Environment terminated normally.

Corrective Action: No action is required.

CTB003S INTERNAL ERROR IN COMMAND DO `cmd`Link copied to clipboard

Explanation: An internal error occurred while executing the DO command identified in the message. Earlier messages indicate the reason for the error.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Ask your INCONTROL administrator to give the information contained in occurrences of the CTB200S message to BMC Customer Support.

CTB004E LEVEL SPECIFIED IN DO EXTRACT (`lvl1`) IS GREATER THAN HIGHEST EXISTING LEVEL (`lvl2`)Link copied to clipboard

Explanation: Statement DO EXTRACT specified a level (lvl1) which exceeds the highest existing level (lvl2).

The DO EXTRACT level must refer to a preceding WHEN statement in the current sub-block. The WHEN statements of the sub-block are numbered starting from 1. The error occurred because the LEVEL parameter specified a non existing WHEN statement. For more information, see the WHEN statement in the Control-M/Analyzer User Guide.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the error and invoke Control-M/Analyzer again.

CTB005E LINE FROM WHICH TO EXTRACT (`lin`) NOT WITHIN THE LINE RANGE (`fromline-toline`) CURRENTLY IN MEMORYLink copied to clipboard

Explanation: The line specified in statement DO EXTRACT must refer to a report line that exists in the current Control-M/Analyzer internal buffers, but it does not. Control-M/Analyzer currently has lines fromline to toline in memory.

Control-M/Analyzer keeps a number of pages from the currently processed report in memory. This is usually sufficient for backward and forward references of WHEN and DO EXTRACT statements.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Ask your INCONTROL administrator to increase the number of pages Control-M/Analyzer stores in memory by changing the RTEBUF parameter in the CTBPARM member.

CTB006E LENGTH TO EXTRACT (`charas`) EXCEEDS THE MAXIMUM ALLOWABLE LENGTH (`max_charas`)Link copied to clipboard

Explanation: The number of characters to extract that was specified in a DO EXTRACT statement exceeded the maximum number of characters that may be extracted.

A DO EXTRACT statement extracts values that are subsequently stored in a variable. The maximum length that may be extracted is the maximum length of the variable value.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the DO EXTRACT statement and invoke Control-M/Analyzer again.

CTB007E LINE TO FIND (`lin`) NOT WITHIN THE LINE RANGE (`fromline-toline`) CURRENTLY IN MEMORYLink copied to clipboard

Explanation: The line specified in a WHEN statement must refer to a report line that exists in the current Control-M/Analyzer internal buffers, but does not. Control-M/Analyzer currently has lines fromline to toline in memory.

Control-M/Analyzer keeps a number of pages from the currently processed report in memory. This is usually sufficient for backward and forward references of WHEN and DO EXTRACT statements.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Ask your INCONTROL administrator to increase the number of pages Control-M/Analyzer stores in memory by changing the RTEBUF parameter in the CTBPARM member.

CTB008E FROM COL (`fromcol`) SHOULD BE GREATER THAN TO COL (`tocol`)Link copied to clipboard

Explanation: The FROM COL value exceeded the TO COL value in a DO EXTRACT statement. The specified FROM COL value must be less than or equal to the TO COL value.

The variables in this message are:

fromcol - the FROM COL value in the DO EXTRACT statement
tocol - the TO COL value in the DO EXTRACT statement

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the DO EXTRACT statement and invoke Control-M/Analyzer again.

CTB009I GROUP-MODE IS `modeType`Link copied to clipboard

Explanation: This information message indicates that the Control-M/Analyzer Runtime Environment has been invoked using the modeType Group mode.

Corrective Action: No action is required.

CTB00AI INVOKED RULE= memName [- lib]

Explanation: This information message indicates that the Control-M/Analyzer Runtime Environment has been invoked with the memName rule member (from the lib library).

Corrective Action: No action is required.

CTB00BI CONTROL-M/ANALYZER IS RUNNING IN "DEFINE" MODE (NO ACTIONS PERFORMED)Link copied to clipboard

Explanation: This information message indicates that the Control-M/Analyzer Runtime Environment has been invoked in Define mode.

In Define mode, Control-M/Analyzer does not perform any balancing activity. All calls to Control-M/Analyzer routines are immediately returned with status END OK and a return code of 0.

For more information, see Define mode in the Control-M/Analyzer User Guide.

Corrective Action: No action is required.

CTB010E COMPILATION ERROR FOR RULE `ruleName` RC= `rc`Link copied to clipboard

Explanation: The Control-M/Analyzer Runtime Environment was invoked with a rule member that contains invalid syntax.

During execution, all invoked rules are checked (compiled) for valid syntax. Whenever invalid syntax is encountered, an error occurs.

The variables in this message are:

ruleName - the problematic rule member
rc - the return code

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the specified rule and invoke Control-M/Analyzer again.

CTB011E MEMORY ALLOCATION ERROR WHILE LOADING RULE `ruleName`Link copied to clipboard

Explanation: The Control-M/Analyzer Runtime Environment has insufficient memory to load a rule.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Increase the REGION size and invoke Control-M/Analyzer again. If the problem persists, notify your INCONTROL administrator.

CTB012I WHILE PROCESSING COMMAND DO `cmd`Link copied to clipboard

Explanation: This information message accompanies other error messages. It identifies the DO command that was in process when the error specified in the other message occurred.

In this message, cmd is the DO command in process when the error occurred.

Corrective Action: No action is required.

CTB013I ENDED `result` COMMITTED `num` VARIABLE(S) USER RC= `rc`Link copied to clipboard

Explanation: This information message is a normal termination message of the Control-M/Analyzer Runtime environment. This message accompanies other normal termination messages.

The variables in this message are:

result - the status when the Control-M/Analyzer Runtime environment ended Valid values are:
- OK
- TOLER
- NOTOK
- ABEND
num - the number of variables committed
rc - the return code

Corrective Action: No action is required.

CTB014E GROUP grp IS NOT DEFINED

Explanation: A non-existing group was specified when the Control-M/Analyzer Runtime Environment was invoked.

The Control-M/Analyzer Runtime Environment must be invoked with an existing group name. Groups can be defined and viewed using the Control-M/Analyzer Online Facility.

For information on the methods that can be used to specify the group under which Control-M/Analyzer is to run, see the Control-M/Analyzer chapter of the INCONTROL for z/OS Administrator Guide.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Specify an existing group and invoke Control-M/Analyzer again.

CTB015E NO GROUP SPECIFIED FOR CONTROL-M/ANALYZER INVOCATIONLink copied to clipboard

Explanation: No group name was specified when the Control-M/Analyzer Runtime Environment was invoked.

The Control-M/Analyzer Runtime Environment must be invoked with an existing group name. Groups can be defined and viewed using the Control-M/Analyzer Online Facility.

For information on the methods that can be used to specify the group under which Control-M/Analyzer is to run, see the Control-M/Analyzer chapter of the INCONTROL for z/OS Administrator Guide.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Specify an existing group, and invoke Control-M/Analyzer again.

CTB016E BLOCK `blk` DOES NOT EXISTLink copied to clipboard

Explanation: The block identified in the message does not exist in the current rule. The rule contained a reference to a nonexisting block, such as the block specified as a parameter to the DATASTAMP function.

In this message, blk is the non-existing block specified in the rule.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the reference and invoke Control-M/Analyzer again.

CTB017E COLUMN RANGE TO EXTRACT `col1-col2` IS BEYOND LINE LENGTH `len`Link copied to clipboard

Explanation: The column range specified in statement DO EXTRACT referred to columns beyond the record length of the input source.

The variables in this message are:

col1 - the first column in the specified range
col2 - the last column in the specified range
len - the record length of the input source

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Correct the column range or verify that the block refers to the correct input source.

CTB020W NEGATIVE COLUMN VALUE (`col_val`) SPECIFIED WHEN SEARCHING FOR "`string`"Link copied to clipboard

Explanation: This warning message indicates that a WHEN statement was specified with a negative column number when searching for the string identified in the message.

WHEN statement column numbers can be relative to the location of previously found data in previous WHEN statements. The negative column number may be the result of such a reference.

The variables in this message are:

col_val - the problematic column number
string - the string that was being searched for

Control-M/Analyzer assumes a column number of 1 and continues execution.

Corrective Action: Make sure that this warning message is not the result of a rule definition error.

CTB021E STRING IN WHEN DOES NOT FIT THE SPECIFIED COLUMN RANGELink copied to clipboard

Explanation: The length of a WHEN statement search string exceeds the number of characters in the specified column range. Strings specified in the WHEN criteria are compared with the contents of the specified line and column range. The strings must not be longer than the specified column range.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Widen the column range or shorten the string which caused the problem.

CTB022E FROM LINE (`fromline`) GREATER THAN TO LINE (`toline`) IN WHEN, LEVEL= `lvl`, SEARCH STRING=" `string`"Link copied to clipboard

Explanation: The FROM LINE value exceeded the TO LINE value in a WHEN statement.

When WHEN statement line numbers are relative to previously found data in previous WHEN statements, the calculated FROM LINE value might be greater than the calculated TO LINE value.

The variables in this message are:

fromline - the FROM LINE value
toline - the TO LINE value
lvl - the level
string - the search string

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the reference and invoke Control-M/Analyzer again.

CTB023E FROM COL (`fromcol`) GREATER THAN TO COL (`tocol`) IN WHEN, LEVEL= `lvl`, SEARCH STRING="`string`"Link copied to clipboard

Explanation: The FROM COL value exceeded the TO COL value in a WHEN statement. When WHEN statement line numbers are relative to previously found data in previous WHEN statements, the calculated FROM COL value might be greater than the calculated TO COL value.

The variables in this message are:

fromcol - the FROM COL value
tocol - the TO COL value
lvl - the level
string - the search string

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the reference and invoke Control-M/Analyzer again.

CTB024E FROM LINE (`fromline`) GREATER THAN TO LINE (`toline`) IN STOP, LEVEL= `lvl`, SEARCH STRING="`string`"Link copied to clipboard

Explanation: The FROM LINE value exceeded the TO LINE value in a STOP statement. When STOP statement line numbers are relative to previously found data in previous STOP statements, the calculated FROM LINE value might be greater than the calculated TO LINE value.

The variables in this message are:

fromline - the FROM LINE value
toline - the TO LINE value
lvl - the level
string - the search string

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the reference and invoke Control-M/Analyzer again.

CTB025E FROM COL (`fromcol`) GREATER THAN TO COL (`tocol`) IN STOP, LEVEL= `lvl`, SEARCH STRING="`string`"Link copied to clipboard

Explanation: The FROM COL value exceeded the TO COL value in a STOP statement. When STOP statement line numbers are relative to previously found data in previous STOP statements, the calculated FROM COL value might be greater than the calculated TO COL value.

The variables in this message are:

fromline - the FROM COL value
toline - the TO COL value
lvl - the level
string - the search string

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the reference and invoke Control-M/Analyzer again.

CTB026E NO DATA MATCHING WHEN CRITERIALink copied to clipboard

Explanation: The input data set does not contain lines that match the WHEN criteria.

Corrective Action: Verify that the WHEN criteria and the data source are correctly specified.

CTB030E DATABASE VARIABLE NOT FOUND: DB_ `grp.var` (GEN= `generationNum` DATE= `date` KEY= `key`)Link copied to clipboard

Explanation: The Control-M/Analyzer Runtime Environment referenced the database, but could not find a variable matching the user-specified criteria. The user can optionally specify a generation number, date or key for the variable indicated in the message. Either the group or variable does not exist, or a variable generation with the specified generation number, date, or key does not exist, in the database.

The variables in this message are:

grp - the group containing the variable that could not be found
var - the variable that could not be found
generationNum - the generation number of the variable that could not be found
date - the date of the variable that could not be found
key - the key of the variable that could not be found

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the reference and invoke Control-M/Analyzer again.

CTB031E VARIABLE NOT FOUND: `varName`Link copied to clipboard

Explanation: The specified local, system or AutoEdit variable does not exist in the Control-M/Analyzer Runtime Environment’s memory.

In this message, varName is the variable that did not exist.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the reference and invoke Control-M/Analyzer again.

CTB032E DATABASE VARIABLES ALREADY COMMITTED. RUN ID " `runId`" CANNOT BE SETLink copied to clipboard

Explanation: An attempt was made to change the value of the SYSRUNID system variable, using a DO SET or DO EXTRACT statement, after database variables had already been committed.

The SYSRUNID system variable contains the run ID of the current Control-M/Analyzer run. The value of the run ID must be the same for all the database variables committed in this run. Therefore, the run ID cannot be changed during the run after a database variable has been committed.

In this message, runId is the run ID of the current Control-M/Analyzer run.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Remove the problematic DO statement and invoke Control-M/Analyzer again.

CTB033E CANNOT SET SYSTEM VARIABLE `varName`Link copied to clipboard

Explanation: An attempt was made to set a system variable that cannot be set.

Most system variables, such as SYSDATE and SYSTIME, cannot be set during Control-M/Analyzer execution because they receive their values only from the system. The Control-M/Analyzer User Guide contains a complete list of system variables, and identifies those that the user can set.

In this message, varName identifies the variable that a user tried to set.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the error and invoke Control-M/Analyzer again.

CTB034E DATABASE VARIABLE DB_ `grp`.var DOES NOT EXISTLink copied to clipboard

Explanation: A nonexisting database variable was specified in a DO SET or DO EXTRACT statement. Either the required database variable exists but its name was specified incorrectly, or the required database variable does not exist.

The variables in this message are:

grp - the group of the problematic database variable
var - the problematic database variable

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: If the database variable name was specified incorrectly, correct it and invoke Control-M/Analyzer again.

To create a database variable, either use the Control-M/Analyzer Online facility, or enable the Automatic Variable Creation Facility to dynamically create the nonexisting database variable during the rule’s execution. For information about the Automatic Database Variable Creation facility, see the Control-M/Analyzer User Guide.

CTB035E ERROR PARSING LINE " `line`". LINE SKIPPEDLink copied to clipboard

Explanation: Control-M/Analyzer encountered an invalid data line while loading an AutoEdit member. AutoEdit member lines must have the format %%VAR=value.

In this message, line identifies the problematic line.

Control-M/Analyzer skips the problematic line, and continues to load the rest of the lines of the AutoEdit member.

Corrective Action: Correct the problematic line, and invoke Control-M/Analyzer again.

CTB036E ERROR PARSING VARIABLE: VAR= `varName` VAL=" `value`"Link copied to clipboard

Explanation: While writing an AutoEdit member, the maximum number of output lines was exceeded. By default, Control-M/Analyzer can write a maximum of 1000 lines of variables in an AutoEdit member.

The variables in this message are:

varName - the problematic variable
value - the value from the line that exceeded the limit.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Notify the INCONTROL administrator.

CTB037E AUTOEDIT MEMBER `lib` (`memName`) ALREADY LOADEDLink copied to clipboard

Explanation: A DO GETMEM statement attempted to load the indicated AutoEdit member, but the member was already loaded in the Control-M/Analyzer Runtime Environment memory by a previous DO GETMEM statement. Loaded AutoEdit members remain in memory until unloaded by a DO PUTMEM statement.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the error and invoke Control-M/Analyzer again.

CTB038E AUTOEDIT MEMBER `lib` (`memName`) NOT PREVIOUSLY LOADEDLink copied to clipboard

Explanation: A DO PUTMEM statement attempted to unload the indicated AutoEdit member, but the member is not in the Control-M/Analyzer Runtime Environment memory.

An AutoEdit member cannot be written back to disk unless it exists in memory. An AutoEdit member is placed in memory when it is loaded using a DO GETMEM statement, or when it is created by using a DO ADDSYM statement to add variables to it.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the error and invoke Control-M/Analyzer again.

CTB03AI WHILE PROCESSING AUTOEDIT MEMBER `lib` (`memName`)Link copied to clipboard

Explanation: This information message accompanies other error messages. This message identifies the AutoEdit member that was being processed when the error specified in any other message occurred.

Corrective Action: No action is required.

CTB03BW AUTOEDIT VARIABLE `varName` ALREADY EXISTS IN MEMBER `lib` (`memName`)Link copied to clipboard

Explanation: An attempt was made, using a DO ADDSYM statement, to add a variable to the specified AutoEdit member, but the variable already exists in the AutoEdit member. Variables names must be unique within an AutoEdit member.

Control-M/Analyzer ignores the current DO ADDSYM statement and continues processing.

Corrective Action: Check whether the parameters of the DO ADDSYM statement are correct, and proceed accordingly.

CTB03CE AUTOEDIT VARIABLE `varName` ALREADY EXISTS IN ANOTHER MEMBER: `memName`Link copied to clipboard

Explanation: An attempt was made to add an AutoEdit variable (varName) to a member but the variable already exists in the memName member. An AutoEdit variable can be stored in only one member.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Do one of the following:

Store the variable only in the memName member.
Change the name of the variable.
Delete the variable in the memName member.

CTB03DE VARIABLE `varName` IS NOT AN AUTOEDIT VARIABLE. CANNOT PERFORM ADDSYMLink copied to clipboard

Explanation: A DO ADDSYM statement specifies a variable that already exists as a non-AutoEdit variable. The name cannot refer to an existing variable.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Rename either the existing variable or the variable to be added to an AutoEdit member.

CTB040E INVALID SEARCH CRITERIA FOR DATABASE VARIABLELink copied to clipboard

Explanation: An invalid variable reference statement was specified.

For information about variable reference statements, see the Control-M/Analyzer User Guide.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the error and invoke Control-M/Analyzer again.

CTB041S INTERNAL ERROR IN `modName`: OPT= `optn` RC= `rc`Link copied to clipboard

Explanation: An error occurred in the module identified in the message when invoked with the reported option.

The variables in this message are:

modName - the name of the module in which the error occurred
optn - the option used when the module was invoked
rc - the return code

The Control-M/Analyzer Runtime environment terminates with an error.

Corrective Action: Record the information in the message and notify your INCONTROL administrator.

CTB045E ERROR COMMITTING DB `_grp.var`Link copied to clipboard

Explanation: An error occurred while the specified database variable was being committed. Preceding messages provide additional information regarding the error.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Notify the INCONTROL administrator.

CTB046E DATABASE VARIABLE NOT PREVIOUSLY SET: DB_ `grp.var`Link copied to clipboard

Explanation: A DO COMMIT statement is attempting to commit a database variable that was not previously set. A database variable cannot be committed unless it was previously given a value by means of a DO SET or DO EXTRACT statement.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the error and invoke Control-M/Analyzer again.

CTB047E ERROR CREATING DB_ `grp.var`Link copied to clipboard

Explanation: An error occurred while trying to dynamically create a database variable using the Automatic Variable Creation Facility. Preceding messages provide additional information regarding the error.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Notify the INCONTROL administrator.

CTB048E UNABLE TO COMMIT `var`. VARIABLE WAS PASSED AS AN ARGUMENT TO THE BLOCK/RULELink copied to clipboard

Explanation: A database variable could not be committed using option DELETE or NOW because it was passed as an argument to the current block or rule.

In this message, var is the database variable that could not be committed.

When variables are passed as arguments in a DO BLOCK or RULE statement, their values are copied into BARGnn and RARGnn variables and restored upon block or rule completion. Committing a database variable deletes it from the runtime environment. A database variable passed as an argument cannot be committed using the DELETE or NOW option because it would be meaningless to restore its value after it is deleted.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Place the DO COMMIT statement outside the called block or rule.

CTB050E MEMORY ALLOCATION ERROR IN AUTOEDITLink copied to clipboard

Explanation: There was insufficient storage to resolve AutoEdit symbols. Subsequent messages provide additional information regarding the error.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Increase the REGION size and invoke Control-M/Analyzer again. If the problem persists, notify your INCONTROL administrator.

CTB051E UNRESOLVED AUTOEDIT SYMBOL: " `string`"Link copied to clipboard

Explanation: A variable that could not be resolved was encountered while trying to resolve AutoEdit variables in the specified string. A reference was probably made to a variable that was not previously set, and, therefore, does not exist.

To resolve AutoEdit symbols in a string, the AutoEdit resolve mechanism searches for local or AutoEdit variables with the specified name. The %% operator must not prefix a database variable. To use the value of a database variable in AutoEdit substitution, the value must first be set to a local variable.

In this message, string is the problematic string.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the error and invoke Control-M/Analyzer again.

CTB052E EMPTY AUTOEDIT SYMBOL: " `string`"Link copied to clipboard

Explanation: A %% AutoEdit operator was specified without an attached variable name.

A %% AutoEdit operator cannot stand alone. A variable name must be appended to the %% operator.

In this message, string identifies the string containing the problematic %% operator.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the error and invoke Control-M/Analyzer again.

CTB053E INVALID AUTOEDIT SYNTAX: " `string`"Link copied to clipboard

Explanation: A syntax error was detected while trying to resolve the specified string. An invalid AutoEdit expression was specified. Control-M/Analyzer cannot continue resolving the AutoEdit symbols in the string.

In this message, string is the problematic string.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the error and invoke Control-M/Analyzer again.

CTB054E RESOLVED AUTOEDIT STATEMENT EXCEEDS MAXIMUM LENGTH. ORIGINAL STATEMENT=" `string`"Link copied to clipboard

Explanation: The outcome of the AutoEdit processing of the specified string results in a string that exceeds the maximum allowed length. Subsequent messages indicate the context in which the error occurred.

In this message, string is the problematic string.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the logical error and invoke Control-M/Analyzer again.

CTB055E TOO MANY BLANKS TO RESOLVE IN AUTOEDIT: " `string`"Link copied to clipboard

Explanation: An nn value greater than 99 was specified for the AutoEdit symbol %%BLANKnn. Subsequent messages indicate the context in which the error occurred.

In this message, string is the problematic string.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the error and invoke Control-M/Analyzer again.

CTB056S INTERNAL ERROR IN CTBCAE: STRING= `string` RC= `rc`Link copied to clipboard

Explanation: An internal error occurred while trying to resolve AutoEdit symbols in the specified string.

The variables in this message are:

string - the problematic string
rc - the return code

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Do the following:

Collect any information contained in CTB200S messages that precede this message.
Ask your INCONTROL administrator to contact BMC Customer Support.

CTB057W VALUE `val` OF `varName` DOES NOT FIT ITS FORMATLink copied to clipboard

Explanation: The format specified for variable varName in statement DO PRINT was not long enough to accommodate the value val. The value of the variable was larger than expected, or a minus sign caused the value to occupy more characters than expected.

A sequence of asterisks is printed instead of the variable’s value. The number of asterisks indicates the specified format length.

Corrective Action: Check why the value of the variable did not fit within the varName variable. If necessary, lengthen the format specified for the varName variable.

CTB058E LENGTH HAS TO BE GREATER THAN PRECISION IN FORMAT OF `varName`Link copied to clipboard

Explanation: The length specified in the format of the varName variable was less than or equal to the precision.

For numeric data, the precision field specifies the number of digits following the decimal character. If the precision is not zero, the entire figure should include the decimal character in addition to the digits that follow it. Therefore, the total length must be greater than the precision.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Either lengthen the format of the variable or decrease the precision.

CTB060E INVALID GROUP NAME IN: " `dbRefStatement`"Link copied to clipboard

Explanation: An invalid group name was found while parsing the dbRefStatement database reference statement.

A group name must be alphanumeric, and may not exceed 20 characters. For more information, see the Control-M/Analyzer User Guide.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the group name and invoke Control-M/Analyzer again.

CTB061E INVALID VARIABLE NAME IN: " `dbRefStatement`"Link copied to clipboard

Explanation: An invalid variable name was found while parsing the dbRefStatement database reference statement.

The variable name must be alphanumeric and may not exceed 20 characters. For more information, see the Control-M/Analyzer User Guide.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the variable name and invoke Control-M/Analyzer again.

CTB062E INVALID GENERATION ID IN: " `dbRefStatement`"Link copied to clipboard

Explanation: An invalid generation number was found while parsing the dbRefStatement database reference statement.

The generation number must be an integer between 0 and 999. For more information, see the Control-M/Analyzer User Guide.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the generation number and invoke Control-M/Analyzer again.

CTB063E INVALID KEY VALUE IN: " `dbRefStatement`"Link copied to clipboard

Explanation: An invalid key value was found while parsing the dbRefStatement database reference statement.

The key value must be alphanumeric and may not exceed 20 characters. For more information, see the Control-M/Analyzer User Guide.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the key value and invoke Control-M/Analyzer again.

CTB064E INVALID RUN ID IN: " `dbRefStatement`"Link copied to clipboard

Explanation: An invalid run ID was found while parsing the dbRefStatement database reference statement.

The run ID must be alphanumeric and may not exceed 20 characters. For more information, see the Control-M/Analyzer User Guide.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the run ID value and invoke Control-M/Analyzer again.

CTB065E INVALID DATE IN: " `dbRefStatement`"Link copied to clipboard

Explanation: An invalid date was found while parsing the dbRefStatement database reference statement.

The date must be in yymmdd format. For more information, see the Control-M/Analyzer User Guide.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the date and invoke Control-M/Analyzer again.

CTB066E A CATEGORY APPEARS TWICE IN: " `dbRefStatement`"Link copied to clipboard

Explanation: A duplicate category was found while parsing the dbRefStatement database reference statement.

Valid categories in a database reference statement are group, variable name, generation, date, key, and run ID. No more than one of each of these categories may be specified in a database reference statement. For more information, see the Control-M/Analyzer User Guide.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the database reference statement and invoke Control-M/Analyzer again.

CTB067E INVALID PLACEMENT OF "." IN: " `dbRefStatement`"Link copied to clipboard

Explanation: The period character (.) was found in an invalid location while parsing the dbRefStatement database reference statement.

The database reference statement can contain a period only between the group and variable name. For more information, see the Control-M/Analyzer User Guide.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the database reference statement and invoke Control-M/Analyzer again.

CTB068E SPECIFIED CATEGORY INVALID IN CURRENT CONTEXT. STRING= " `dbRefStatement`"Link copied to clipboard

Explanation: A category that is invalid in the current context was found while parsing the dbRefStatement database reference statement.

The validity of categories (components) in the database reference statement is determined by the context in which the statement is used. For example, if a database variable is assigned a value by a DO SET statement, the run ID should not be specified as part of the database reference statement because the run ID is taken from the SYSRUNID system variable. For more information, see the Control-M/Analyzer User Guide.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the database reference statement and invoke Control-M/Analyzer again.

CTB069E INVALID CATEGORY IDENTIFIER IN: " `dbRefStatement`"Link copied to clipboard

Explanation: A invalid category identifier was found while parsing the dbRefStatement database reference statement.

Valid category identifiers are:

G - Generation
K - Key
R - Run ID
D - Date

Category identifiers must always be preceded by the character @. For more information, see the Control-M/Analyzer User Guide.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the database reference statement and invoke Control-M/Analyzer again.

CTB06AS INTERNAL ERROR. INVALID PREFIX IN: " `dbRefStatement`"Link copied to clipboard

Explanation: An internal error occurred while parsing the dbRefStatement database reference statement.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.

CTB06BS INTERNAL ERROR IN CTBCNMP: STRING= " `dbRefStatement`" RC= `rc` IS INVALIDLink copied to clipboard

Explanation: An internal error occurred while parsing the dbRefStatement database reference statement.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.

CTB06CE USER MODULE `modName` NOT FOUNDLink copied to clipboard

Explanation: Control-M/Analyzer is unable to load a user routine specified in the CALLUSER command. Before Control-M/Analyzer can call a user routine, it must first load the routine.

Control-M/Analyzer terminates with a runtime error.

Corrective Action: Check that a module with the name modName exists in the STEPLIB library or in the LINKLIST.

CTB070E SYNTAX ERROR IN EVALUATION ROUTINE (POS `n`), INPUT=" `expression`"Link copied to clipboard

Explanation: Control-M/Analyzer attempted to evaluate the expression identified in the message, but the expression syntax was invalid.

For a detailed description of expression syntax, see the Control-M/Analyzer User Guide.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the syntax error and invoke Control-M/Analyzer again.

CTB071E UNBALANCED PARENTHESES IN EVALUATION ROUTINE (POS `n`), INPUT=" `expression`"Link copied to clipboard

Explanation: While evaluating the expression identified in the message, Control-M/Analyzer encountered unbalanced parentheses.

For a detailed explanation of expression syntax, see the Control-M/Analyzer User Guide.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the syntax error and invoke Control-M/Analyzer again.

CTB072E SYMBOL ERROR IN EVALUATION ROUTINE (POS `n`), INPUT=" `expression`"Link copied to clipboard

Explanation: An internal evaluation error occurred while evaluating the expression identified in the message.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.

CTB073E TOO MANY COMMAS IN EVALUATION ROUTINE (POS `n`), INPUT=" `expression`"Link copied to clipboard

Explanation: The expression identified in the message contains a function call that has too many commas. This means that too many arguments are passed to the function.

Each Control-M/Analyzer function has a defined number of arguments. For a description of expression syntax and Control-M/Analyzer functions, see the Control-M/Analyzer User Guide.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the syntax error and invoke Control-M/Analyzer again.

CTB074E INVALID NUMBER OF COMMAS IN EVALUATION ROUTINE (POS `n`), INPUT=" `expression`"Link copied to clipboard

Explanation: The expression identified in the message contains a function call that has an invalid number of commas. This means that the number of arguments passed to the function is incorrect.

Each Control-M/Analyzer function has a defined number of arguments. For a description of expression syntax and Control-M/Analyzer functions, see the Control-M/Analyzer User Guide.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the syntax error and invoke Control-M/Analyzer again.

CTB075E INTERNAL ERROR IN EVALUATION ROUTINE (ERR `error`), INPUT=" `expression`"Link copied to clipboard

Explanation: An internal evaluation error occurred while evaluating the expression identified in the message.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.

CTB076E VARIABLE NOT FOUND IN EVALUATION ROUTINE (POS `num`), INPUT= `expr`Link copied to clipboard

Explanation: The variable specified in the expr expression does not exist. Control-M/Analyzer can not evaluate an expression if one of the variables it contains does not exist.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Correct the expression or create the missing variable.

CTB077E SCAN ERROR IN EVALUATION ROUTINE (POS `n`), INPUT=" `expr`"Link copied to clipboard

Explanation: Control-M/Analyzer attempted to evaluate the expression identified in the message (expr), but the expression syntax was invalid.

For a detailed description of expression syntax, see the Control-M/Analyzer User Guide.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the syntax error and invoke Control-M/Analyzer again.

CTB078E INTERNAL ERROR IN CTBEVAL: INPUT=" `expr`" RC= `rc` IS INVALIDLink copied to clipboard

Explanation: An internal evaluation error occurred while evaluating the expression identified in the message (expr).

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.

CTB079E MAXIMUM VARIABLE SIZE EXCEEDED (POS `n`), INPUT=" `expr`"Link copied to clipboard

Explanation: While evaluating the expression identified in the message (expr), a calculation result that exceeded the maximum size was produced.

Evaluation results are stored in a variable. The length of the evaluation results cannot exceed the maximum allowable length of the value of the variable.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the error and invoke Control-M/Analyzer again.

CTB07AE UNABLE TO ALLOCATE MEMORY IN EVALUATION ROUTINE (POS `n`), INPUT=" `expr`"Link copied to clipboard

Explanation: While evaluating the expression identified in the message (expr), the Control-M/Analyzer Runtime Environment had insufficient memory to continue with the evaluation.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Increase the REGION size and invoke Control-M/Analyzer again. If the problem persists, notify your INCONTROL administrator.

CTB07BE VARIABLE NOT FOUND IN EVALUATION ROUTINE (POS `n`), INPUT=" `expr`"Link copied to clipboard

Explanation: The expression identified in the message (expr) contains a reference to a local variable that was not previously set, or to a database variable that does not exist in the Control-M/Analyzer database. The name of the nonexisting variable appears in a preceding message.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the error and invoke Control-M/Analyzer again.

CTB07CE VARIABLE NOT NUMERIC IN EVALUATION ROUTINE (POS `n`), INPUT=" `expr`"Link copied to clipboard

Explanation: The expression identified in the message (expr) contains a reference to a variable that should, but does not, contain a numeric value.

Some Control-M/Analyzer functions require that numeric arguments be supplied in predefined positions. For a description of expression syntax, see the Control-M/Analyzer User Guide.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the error and invoke Control-M/Analyzer again.

CTB07DE ERROR WHILE EVALUATING EXPRESSION (POS `n`), INPUT=" `expr`"Link copied to clipboard

Explanation: Control-M/Analyzer encountered an error while evaluating one of the Control-M/Analyzer functions in the expression identified in the message (expr).

Probably one of the arguments passed to the function was incorrect. For a description of expression syntax and Control-M/Analyzer functions, see the Control-M/Analyzer User Guide.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the error and invoke Control-M/Analyzer again.

CTB07EE DIVISION BY ZERO IDENTIFIED IN EVALUATION ROUTINE (POS `n`), INPUT=" `expr`"Link copied to clipboard

Explanation: The expression identified in the message (expr) required Control-M/Analyzer to divide by 0.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Correct the arithmetic error and invoke Control-M/Analyzer again.

CTB07FS `req` IS AN INVALID REQUEST TO FUNCTION `func`Link copied to clipboard

Explanation: The DBINFO or DDINFO function was called with an invalid request.

For more information on the DBINFO and DDINFO functions, see the Control-M/Analyzer User Guide.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Correct the request string.

CTB080S INTERNAL ERROR IN CTBXALC: RC= `rc`Link copied to clipboard

Explanation: An internal error occurred in the CTBXALC routine.

Control-M/Analyzer terminates with a runtime error.

Corrective Action: Ask your INCONTROL administrator to contact BMC Customer Support.

CTB081E ALLOCATION ERROR IN CTBXALC: `rcerrCode infoCode`Link copied to clipboard

Explanation: A problem occurred during dynamic allocation of a file.

The variables in this message are:

rc - IBM dynamic allocation error code
errCode - IBM dynamic text unit error code
infoCode - IBM dynamic text unit information code

For more information on the error and information codes, see the IBM manual MVS Programming: Authorized Assembler Services Guide.

Control-M/Analyzer terminates with a runtime error.

Corrective Action: Notify your INCONTROL administrator.

CTB082S ALLOCATION ERROR IN CTBXALC: ABEND `abend`Link copied to clipboard

Explanation: The dynamic allocation program abended with the abend code abend.

Control-M/Analyzer terminates with a runtime error.

Corrective Action: For information about the abend, refer to IBM message and code documentation, and correct the problem accordingly. If you need assistance, ask your INCONTROL administrator to contact BMC Customer Support.

CTB083S INTERNAL ERROR IN CTBXALC: RC `rc` INVALIDLink copied to clipboard

Explanation: An internal error occurred. The return code issued is not valid.

Control-M/Analyzer terminates with a runtime error.

Corrective Action: Note the identity of this message and the invalid return code, and ask your INCONTROL administrator to contact BMC Customer Support.

CTB084I DURING PROCESSING OF DSN= `dsn` DD= `ddName`Link copied to clipboard

Explanation: This information message accompanies other messages which indicate a problem. This message indicates the data set name and DD statement associated with any accompanying message.

Corrective Action: No action is required.

CTB085E INVALID MEMBER NAME: `string`Link copied to clipboard

Explanation: The specified value is not valid for use as a member name.

Control-M/Analyzer terminates with a runtime error.

Corrective Action: Correct the member name and rerun the rule.

CTB090S INTERNAL ERROR IN CTBXSIO: RC= `rc`Link copied to clipboard

Explanation: An internal error occurred.

Control-M/Analyzer terminates with a runtime error.

Corrective Action: Ask your INCONTROL administrator to contact BMC Customer Support.

CTB091E OPEN ERROR IN CTBXSIOLink copied to clipboard

Explanation: Control-M/Analyzer was unable to open a sequential file. This message is accompanied by other messages which provide additional information.

Control-M/Analyzer terminates with a runtime error.

Corrective Action: Check the accompanying messages to determine the problem. Resolve accordingly.

CTB092S PROCESSING ERROR IN CTBXSIO: ABEND `abend`Link copied to clipboard

Explanation: An abend occurred while performing I/O to a sequential file.

Control-M/Analyzer terminates with a runtime error.

Corrective Action: For information about the abend, refer to IBM message and code documentation and correct the error accordingly. If you need further assistance, ask your INCONTROL administrator to contact BMC Customer Support.

CTB093S INTERNAL ERROR IN CTBXSIO: RC `rc` INVALIDLink copied to clipboard

Explanation: An internal error occurred. The return code issued (rc) is not valid.

Control-M/Analyzer terminates with a runtime error.

Corrective Action: Note the identity of this message and the invalid return code, and ask your INCONTROL administrator to contact BMC Customer Support.

CTB094I DURING PROCESSING OF DD= `ddName`Link copied to clipboard

Explanation: This information message accompanies other messages which indicate a problem. This message indicates the data set name and DD statement associated with any accompanying message.

Corrective Action: No action is required.

CTB095S INTERNAL ERROR `err_num` IN CTBXVSM: RC= `rc` REASON= `rsn`Link copied to clipboard

Explanation: An error occurred while reading data in an ON VSAM statement.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: For the meaning of the return and reason codes, examine your IBM documentation for VSAM programming, and correct the problem accordingly.

CTB096E OPEN ERROR IN CTBXVSM: RC= `rc` REASON= `rsn`Link copied to clipboard

Explanation: The VSAM file specified in an ON VSAM statement could not be opened.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: For the meaning of the return and reason codes, refer to your IBM documentation for VSAM programming, and correct the problem accordingly.

CTB097E FIRST KEY `key1` IS GREATER THAN LAST KEY `key2`Link copied to clipboard

Explanation: The first key was greater than the last key in the key range specified in statement ON VSAM.

The variables in this message are:

key1 - the first key in the key range
key2 - the last key in the range

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Correct the values specified for the FIRSTKEY and LASTKEY parameters as appropriate.

CTB098S INTERNAL ERROR IN CTBXSPL: RC= `rc`Link copied to clipboard

Explanation: An internal error occurred while reading from the spool.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.

CTB099S INTERNAL ERROR IN CTBXSPL: RC= `rc` INVALIDLink copied to clipboard

Explanation: An internal error occurred while reading from spool.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.

CTB09AI DURING PROCESSING OF PROC= `proc` PGM= `pgm` DD= `ddName`Link copied to clipboard

Explanation: This information message accompanies other error messages. This message identifies the sysout that was being processed when the error specified in any other message occurred.

Corrective Action: No action is required.

CTB09BE REQUESTED SYSOUT NOT FOUNDLink copied to clipboard

Explanation: The specified SYSOUT was not found during reading of the SYSOUT. Subsequent messages indicate the exact SYSOUT specification.

For a discussion of Control-M/Analyzer SYSOUT processing methods, see the Control-M/Analyzer chapter of the INCONTROL for z/OS Installation Guide and the Control-M/Analyzer User Guide.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Do the following:

Correct the error. Check the following matters:
- The FREE parameter must be set to CLOSE in the DD statement that created the SYSOUT. If your site is a JES3 site, read the JES3 considerations in the INCONTROL for z/OS Installation Guide.
- If ON_SYSOUT is in use, make sure that the required SYSOUT was created by the specified pgmstep or procstep. For information on the ON_SYSOUT parameter see the Control-M/Analyzer User Guide.
Invoke Control-M/Analyzer again.

CTB09CE RELEASE/NEW CLASS/NEW DEST FAILEDLink copied to clipboard

Explanation: The specified operation could not be performed. This message follows a more detailed message that identifies the problem.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Record the information in the accompanying message and consult your INCONTROL administrator.

CTB0A1S INTERNAL ERROR IN CTBCLCK: RC= `rc` INVALIDLink copied to clipboard

Explanation: Control-M/Analyzer Runtime environment could not lock a database variable or release a previously locked one.

A database variable is locked by the user accessing it to avoid simultaneous update by other users. Either a variable used in the rule or the whole Control-M/Analyzer database is currently in use.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Schedule the rule execution so that it does not conflict with other rules using the same database variables or with utilities using the entire database.

CTB0A5E INTERNAL ERROR IN CTBXLOG (SEE ERLG)Link copied to clipboard

Explanation: An internal error occurred while processing the IOA log.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.

CTB0A6S INTERNAL ERROR IN CTBXLOG: RC= `rc` INVALIDLink copied to clipboard

Explanation: An internal error occurred while processing the IOA Log File.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.

CTB0A7E INTERNAL ERROR IN CTBXINI (SEE ERLG)Link copied to clipboard

Explanation: An internal error occurred while initializing the Control-M/Analyzer environment.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.

CTB0A8S INTERNAL ERROR IN CTBXINI: RC= `rc` INVALIDLink copied to clipboard

Explanation: An internal error occurred while initializing the Control-M/Analyzer environment.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.

CTB0A9E INTERNAL ERROR IN CTBXWTO (SEE ERLG)Link copied to clipboard

Explanation: An internal error occurred while performing a WTO operation.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.

CTB0AAS INTERNAL ERROR IN CTBXWTO: RC= `rc` INVALIDLink copied to clipboard

Explanation: An internal error occurred while performing a WTO operation.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.

CTB0ABE INTERNAL ERROR IN CTBXINF (SEE ERLG)Link copied to clipboard

Explanation: An internal error occurred while gathering information from the system.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.

CTB0ACS INTERNAL ERROR IN CTBXINF: RC= `rc` INVALIDLink copied to clipboard

Explanation: An internal error occurred while gathering information from the system.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.

CTB0B1S INSUFFICIENT STORAGE. INCREASE JOB/STEP REGION SIZE PARAMETERLink copied to clipboard

Explanation: Control-M/Analyzer could not run because of insufficient storage.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Increase the value of the REGION parameter.

CTB0B2E MEMBER NOT FOUNDLink copied to clipboard

Explanation: The requested member is not found in the library.

Possible causes are:

Control-M/Analyzer failed to read a rule
the AutoEdit Facility failed to read an AutoEdit Symbols member

Rule processing stops and Control-M/Analyzer terminates.

Corrective Action: Correct the library name for the rule or AutoEdit member and rerun the rule.

CTB0B3E DSN IS NOT A LIBRARYLink copied to clipboard

Explanation: The requested member is not a partitioned data set.

Possible causes are:

Control-M/Analyzer failed to read a rule
the AutoEdit Facility failed to read an AutoEdit Symbols member

Rule processing stops and Control-M/Analyzer terminates.

Corrective Action: Correct the library name for the rule or AutoEdit member, and rerun the rule.

CTB0B4E DSN IS NOT WITH FIXED DSORGLink copied to clipboard

Explanation: The record format of the requested data set name (DSN) is not fixed. Probably the DSN does not refer to the correct file.

Possible causes are:

Control-M/Analyzer failed to read a rule
the AutoEdit Facility failed to read an AutoEdit Symbols member

Rule processing stops and Control-M/Analyzer terminates.

Corrective Action: Ensure that the DSN points to the correct file. If it is already pointing to the correct file, determine why the file does not have a fixed format.

CTB0B5E LRECL IS NOT 80Link copied to clipboard

Explanation: The record length of the requested data set is not 80. The probable cause is that the data set name (DSN) does not refer to the correct file.

Possible causes are:

Control-M/Analyzer failed to read a rule
the AutoEdit Facility failed to read an AutoEdit Symbols member

Rule processing stops and Control-M/Analyzer terminates.

Corrective Action: Ensure that the DSN points to the correct file. If it is already pointing to the correct file, determine why the file does not have a record length of 80.

CTB0B6E DSN IS IN USELink copied to clipboard

Explanation: The data set is held exclusively by another user.

Possible causes are:

Control-M/Analyzer failed to read a rule
the AutoEdit Facility failed to read an AutoEdit Symbols member

Rule processing stops and Control-M/Analyzer terminates.

Corrective Action: Try again.

CTB0B7S INTERNAL ERROR IN CTBXMEMLink copied to clipboard

Explanation: A Control-M/Analyzer internal error occurred while trying to read a member from a library.

Possible causes are:

Control-M/Analyzer failed to read a rule
the AutoEdit Facility failed to read an AutoEdit Symbols member

Rule processing stops and Control-M/Analyzer terminates.

Corrective Action: Look for additional messages on the IOA Log that may clarify the situation. You or your INCONTROL administrator should refer to IBM message and code documentation for information about the abend, and make corrections accordingly. In any case, your INCONTROL administrator should contact BMC Customer Support.

CTB0B8E DSN IS NOT CATALOGEDLink copied to clipboard

Explanation: The requested data set name (DSN) is not in the catalog.

Possible causes are:

Control-M/Analyzer failed to read a rule
the AutoEdit Facility failed to read an AutoEdit Symbols member

Rule processing stops and Control-M/Analyzer terminates.

Corrective Action: Ensure that the DSN is cataloged. Rerun the rule.

CTB0B9E DYNAMIC ALLOCATION FAILEDLink copied to clipboard

Explanation: Dynamic allocation for the requested data set name (DSN) failed.

Possible causes are:

Control-M/Analyzer failed to read a rule
the AutoEdit Facility failed to read an AutoEdit Symbols member

Rule processing and Control-M/Analyzer terminates.

Corrective Action: Ask your INCONTROL Administrator to contact BMC Customer Support.

CTB0BAS INVALID REQUEST IN CTBXMEMLink copied to clipboard

Explanation: Internal error while trying to read a member from a library.

Possible causes are:

Control-M/Analyzer failed to read a rule
the AutoEdit Facility failed to read an AutoEdit Symbols member

Rule processing stops and Control-M/Analyzer terminates.

Corrective Action: Ask your INCONTROL Administrator to contact BMC Customer Support.

CTB0BBE TOO MANY LINES TO READLink copied to clipboard

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

Possible causes are:

Control-M/Analyzer failed to read a rule
the AutoEdit Facility failed to read an AutoEdit Symbols member

Rule processing stops and Control-M/Analyzer terminates.

Corrective Action: Increase the REGION size or logon size, and try again.

CTB0BCS ERROR WHILE PROCESSING DIRECTORYLink copied to clipboard

Explanation: A Control-M/Analyzer internal error occurred while trying to read a directory of a library. This message can appear under the Control-M/Analyzer Online Facility.

Rule processing stops and Control-M/Analyzer terminates.

Corrective Action: Ask your INCONTROL Administrator to contact BMC Customer Support.

CTB0BDS ABEND OCCURRED IN CTBXMEMLink copied to clipboard

Explanation: A Control-M/Analyzer internal error occurred while trying to read a member from a library.

Possible causes are:

Control-M/Analyzer failed to read a rule
the AutoEdit Facility failed to read an AutoEdit Symbols member

Rule processing stops and Control-M/Analyzer terminates.

Corrective Action: Ask your INCONTROL Administrator to contact BMC Customer Support.

CTB0BEE MEMBER TO SAVE CANNOT BE FOUNDLink copied to clipboard

Explanation: You are trying to save an AutoEdit member which does not exist.

The AutoEdit member is not saved.

Corrective Action: Create the member.

CTB0BFE MEMBER ALREADY EXISTSLink copied to clipboard

Explanation: You are trying to create an AutoEdit member which already exists.

The AutoEdit member is not created.

Corrective Action: Save the member.

CTB0C0S INTERNAL ERROR - INVALID TYPE IN CTBXMEMLink copied to clipboard

Explanation: The record format of the library to be opened differs from the requested format.

Possible causes are:

Control-M/Analyzer failed to read a rule
the AutoEdit Facility failed to read an AutoEdit Symbols member

Rule processing stops and Control-M/Analyzer terminates.

Corrective Action: Notify your INCONTROL administrator.

CTB0C1S INTERNAL ERROR IN CTBXMEM: RC `rc`Link copied to clipboard

Explanation: Internal error while trying to read a member from a library.

Possible causes are:

Control-M/Analyzer failed to read a rule
the AutoEdit Facility failed to read an AutoEdit Symbols member

Rule processing stops and Control-M/Analyzer terminates.

Corrective Action: Ask your INCONTROL Administrator to contact BMC Customer Support.

CTB0C2I DURING PROCESSING OF DSN(`memName`), DD= `ddName`Link copied to clipboard

Explanation: This information message accompanies other messages which indicate the problem.

The variables in this message are:

memName - the name of the problematic data set
ddName - the name of the problematic DD statement

Corrective Action: No action is required.

CTB0D0E INPUT TOO LONG FOR CTBCWRD. INPUT=" `string`"Link copied to clipboard

Explanation: An internal error occurred while trying to parse the string (string) identified in the message.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.

CTB0D1E A WORD PARSED BY CTBCWRD EXCEEDS THE MAXIMUM ALLOWABLE LENGTH. INPUT=" `string`"Link copied to clipboard

Explanation: An internal error occurred while trying to parse the string (string) identified in the message. One of the resulting words was longer then the maximum allowable word length.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.

CTB0D2E TOO MANY WORDS FOR CTBCWRD. INPUT=" `string`"Link copied to clipboard

Explanation: Control-M/Analyzer found too many arguments while parsing the argument list of a DO BLOCK, DO CALLUSER or DO RULE statement.

A maximum of 50 arguments can be passed in a DO BLOCK, DO CALLUSER or DO RULE argument list.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the error and invoke Control-M/Analyzer again.

CTB0D3S INTERNAL ERROR IN CTBCWRD: RC= `rc` INVALIDLink copied to clipboard

Explanation: An internal error occurred while parsing a string.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.

CTB0D8S PROBLEM DURING DB2 CONNECT. SUBSYSTEM ID = `id`Link copied to clipboard

Explanation: The DB2 subsystem could not be connected.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Consult your DB2 administrator.

CTB0D9S PROBLEM DURING DB2 OPEN THREAD. SUBSYSTEM ID= `id`Link copied to clipboard

Explanation: The DB2 subsystem could not be opened.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Consult your DB2 administrator.

CTB0DAW SQL WARNING. CODE= `warningCode`. SUBSYSTEM ID= `id`Link copied to clipboard

Explanation: DB2 issued a warning code.

For the explanation of the warning code, refer to DB2 literature.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Try to correct the error on the information provided by the warning code and the DB2 literature. If necessary, consult your DB2 administrator.

CTB0DBE SQL ERROR, CODE= `error`, SUBSYSTEM ID= `id`Link copied to clipboard

Explanation: DB2 issued a SQL error code.

For the explanation of the warning code, refer to DB2 literature.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Try to correct the error on the information provided by the warning code and the DB2 literature. If necessary, consult your DB2 administrator.

CTB0DCE NO VALID COLUMNS FOUND, SUBSYSTEM ID= `id` (`rc`=12)Link copied to clipboard

Explanation: None of the arguments specified by the user in the SQL SELECT statement refer to a valid column in one of the selected DB2 tables.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Include at least one column name belonging to one of the selected DB2 tables in the SQL statement in your rule.

CTB0DDE INVALID COLUMN TYPE. ERROR IN DB2 DATABASE SUBSYSTEM ID= `id` (`rc`=20)Link copied to clipboard

Explanation: One of the columns specified in the SQL statement has an unrecognized column type as defined in the DB2 catalog.

Possible causes are:

a DB2 catalog error
a new version of DB2 that introduces new column types

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Do the following:

Make a list of the DB2 table names of the selected tables in the rule.
Have your DB2 database administrator generate a list of the columns and column types of these tables from the DB2 catalog.
Contact your INCONTROL administrator and provide this information.

CTB0DES PROBLEM DURING DB2 CLOSE THREAD, REASON CODE= `rsn` SUBSYSTEM ID= `subId`Link copied to clipboard

Explanation: The DB2 CLOSE THREAD call did not succeed. The DB2 CONNECT, OPEN THREAD and SQL calls succeeded, but the CLOSE THREAD call did not. This indicates either a change in the availability of the DB2 subsystem or an internal error.

Possible causes are:

the DB2 subsystem identified in the message is currently inactive
an internal error in DB2

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Have your DB2 database administrator check the status of the DB2 subsystem identified in the message, and the status of the open threads under it. If necessary, close the thread for CTBDB2 manually.

CTB0DFS PROBLEM DURING DB2 DISCONNECT, REASON CODE= `rsn` SUBSYSTEM ID= `subId`Link copied to clipboard

Explanation: The DB2 DISCONNECT call did not succeed.

Possible causes are:

the DB2 subsystem identified in the message is currently inactive
an internal error in DB2

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Have your DB2 database administrator verify that the DB2 subsystem identified in the message is active.

CTB0E0S INTERNAL ERROR IN CTBXCDM: RC= `rc`Link copied to clipboard

Explanation: An internal error occurred while reading a CDAM data set.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.

CTB0E1S INTERNAL ERROR IN CTBXCDM: RC= `rc` INVALIDLink copied to clipboard

Explanation: An internal error occurred while reading a CDAM data set.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.

CTB0E2I DURING PROCESSING OF CDAM-CRT= `cdam_crit`Link copied to clipboard

Explanation: This information message accompanies other error messages.

In this message cdam_crit identifies the CDAM criteria that were being processed when the error specified in any other message occurred.

Corrective Action: No action is required.

CTB0E3E REQUESTED CDAM FILE NOT FOUNDLink copied to clipboard

Explanation: The requested CDAM file was not found. The error occurred while attempting to read the requested CDAM file. Subsequent messages indicate the CDAM criteria that were being used when the error occurred.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the errors and invoke Control-M/Analyzer again.

CTB0E7S INTERNAL ERROR IN CTBXCKP: OPT= `option` RC= `rc`Link copied to clipboard

Explanation: An internal error occurred while Control-M/Analyzer was accessing the Rule Activity File.

The variables in this message are:

option - the type of operation being performed when the error occurred
rc - the return code

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Contact your INCONTROL administrator.

CTB0EAS INTERNAL ERROR IN CTBXREP: OPT= `option` RC= `rc`Link copied to clipboard

Explanation: An internal error occurred while Control-M/Analyzer was accessing the Report file.

The variables in this message are:

option - the type of operation being performed when the error occurred
rc - the return code

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Contact your INCONTROL administrator.

CTB0EBS REPORT FILE IS FULL. PLEASE RUN UTILITY CTBJAFDLLink copied to clipboard

Explanation: Reports cannot be written to the Control-M/Analyzer report file because the file has become full.

The Control-M/Analyzer Runtime Environment continues executing, but a report for the current Control-M/Analyzer invocation is not created.

Corrective Action: Contact your INCONTROL administrator.

BMC recommends that you run the CTBJAFDL Control-M/Analyzer utility periodically, to erase unneeded reports in the report file. For more information about this utility, see the INCONTROL for z/OS Utilities Guide.

CTB0EDS INTERNAL ERROR IN CTBXGRP: OPT= `option` RC= `rc`Link copied to clipboard

Explanation: An internal error occurred while Control-M/Analyzer was accessing the Group file. The error occurred while performing an operation of type option.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Contact your INCONTROL administrator.

CTB0F0W CONDITION TO ADD ALREADY EXISTS: COND= `cond` ODATE= `odate`Link copied to clipboard

Explanation: This warning indicates that a condition cond already exists in the IOA Conditions file. It does not usually indicate a problem.

The SYSRC system variable is set to 4 and processing continues.

The condition is not added to the IOA Conditions file.

Corrective Action: No action is required.

CTB0F1W CONDITION TO DELETE DOES NOT EXIST. COND= `cond` ODATE = `date`Link copied to clipboard

Explanation: This message indicates that the cond condition cannot be deleted because it does not currently exist in the IOA Conditions file. The cond condition was previously deleted or never created.

The condition is not deleted again.

Corrective Action: No action is required.

CTB0F5S INTERNAL ERROR IN CTBXABF: OPT= `option` RC= `rc`Link copied to clipboard

Explanation: An internal error occurred while Control-M/Analyzer was accessing the Active Balancing file, during an operation of type option.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Contact your INCONTROL administrator.

CTB0F6S ACTIVE BALANCING FILE IS FULL. USE CTBFRM TO COMPRESS ITLink copied to clipboard

Explanation: The Control-M/Analyzer Active Balancing file is full and needs to be compressed. It is not possible to order Control-M/Analyzer missions into the file, or run unscheduled Control-M/Analyzer invocations that also need to add an entry to this file.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Contact your INCONTROL administrator.

Run the CTBFRM Control-M/Analyzer utility once a day to compress the Active Balancing file. If the Active Balancing file needs to be compressed more than once a day, it is advisable to enlarge the size of the file.

CTB0F7S INTERNAL ERROR IN SYSDATA: RC= `rc`Link copied to clipboard

Explanation: An internal error occurred while Control-M/Analyzer was reading a Control-M SYSDATA data set.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.

CTB0F8S INTERNAL ERROR IN SYSDATA: RC= `rc` INVALIDLink copied to clipboard

Explanation: An internal error occurred while Control-M/Analyzer was reading a Control-M SYSDATA data set.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.

CTB0F9I DURING PROCESSING OF SYSDATALink copied to clipboard

Explanation: This information message follows a more detailed message issued when a problem occurs using ON SYSDATA.

Corrective Action: No action is required.

CTB0FAE REQUESTED SYSDATA FILE NOT FOUNDLink copied to clipboard

Explanation: Control-M/Analyzer could not find the requested Control-M/Analyzer SYSDATA data set. The error occurred during an attempt to read the SYSDATA data set of the current job. Either Control-M or Control-M/Restart was not installed or ARCHIVE was not set to Y in the scheduling table.

The Control-M/Analyzer Runtime Environment terminates with an error.

Corrective Action: Correct the error and invoke Control-M/Analyzer again.

Messages CTB100 through CTB1xxLink copied to clipboard

This group includes messages for the Control-M/Analyzer product.

CTB101E LINE `lineNum`: KEYWORD " `keywd`" IS REQUIREDLink copied to clipboard

Explanation: During rule compilation or runtime an expected key word was missing in the specified line.

Relevant text appears in an accompanying message.

The variables in this message are:

lineNum - has one of the following meanings:
If the error occurred during rule compilation, lineNum identifies the line from which keywd was missing.
If the error occurred during runtime, lineNum identifies the line in the DD name file referenced by the MSUBSTMASK function from which keywd was missing.
keywd - the missing key word

The system action depends on the point at which the error occurs, as follows:

If the error occurs during rule compilation, the compiler continues processing at the next block, but issues syntax error messages when it ends.
If the error occurs during runtime execution, Control-M/Analyzer stops executing and issues an error message.

Corrective Action: Correct all errors in the rule, or in the DD name referenced by MSUBSTMASK, and recompile.

CTB102E LINE `lin`: KEYWORD " `keywd`" MUST APPEAR ONCE AND ONLY ONCE IN THIS STATEMENTLink copied to clipboard

Explanation: During rule compilation the keyword keywd was expected to appear once in the line lin. The keyword either was not found or was found more than once in the statement. Relevant text appears in an accompanying message.

The compiler continues processing the next block but terminates with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB103E LINE `lin`: KEYWORD " `keywd`" CAN APPEAR ONLY ONCE IN THIS STATEMENTLink copied to clipboard

Explanation: A syntax error was detected during rule compilation. Relevant text appears in an accompanying message. The keyword keywd was expected to appear once in the lin line, but was found more than once in the statement.

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct any errors in the rule member and recompile the rule.

CTB104E NUMERIC VALUE EXPECTEDLink copied to clipboard

Explanation: A syntax error was detected during rule compilation. Relevant text appears in an accompanying message. The parameter value should be, but is not, numeric.

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB105E EXPECTED PARAMETER MISSING IN LINE `lin`Link copied to clipboard

Explanation: During rule compilation, a required parameter value was missing from the lin line. Relevant text appears in an accompanying message.

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB106E PARAMETER STARTING ON LINE `lin` IS TOO LONGLink copied to clipboard

Explanation: During rule compilation, the length of a parameter that starts on the lin line exceeded the maximum length for this parameter. Relevant text appears in an accompanying message.

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB107E KEYWORD " `keyName1`" CANNOT FOLLOW " `keyName2`"Link copied to clipboard

Explanation: During rule compilation, keyName1 incorrectly follows keyName2. Relevant text appears in an accompanying message.

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB108E KEYWORD EXPECTED IN LINE: `lin` BEFORE " `string`"Link copied to clipboard

Explanation: During rule compilation, a keyword was expected in the lin line before the string string, but the keyword was missing from the lin line. The probable cause is misspelling of a keyword. Relevant text appears in an accompanying message.

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB109I COMPILATION STARTEDLink copied to clipboard

Explanation: This information message indicates that the compiler has started compiling a rule.

Corrective Action: No action is required.

CTB110I COMPILATION COMPLETED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that a rule was compiled without any errors. Warnings may have been issued.

Corrective Action: No action is required.

CTB111I HIGHEST ERROR CODE WAS `code`Link copied to clipboard

Explanation: This information message indicates the highest error code issued during a rule compilation. The error code is 0 if the rule compiled without warnings. The error code is nonzero if warnings were issued or errors were detected.

Corrective Action: No action is required.

CTB112E STATEMENT `line`: IS INVALID IN THIS CONTEXTLink copied to clipboard

Explanation: During rule compilation, the statement line was incorrect. Relevant text appears in an accompanying message.

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB113I SKIPPING TO NEXT BLOCKLink copied to clipboard

Explanation: This information message indicates that the compiler found a syntax error in the current block and is skipping to the next block before continuing with syntax checking.

Corrective Action: No action is required.

CTB114E MEMORY ALLOCATION FAILEDLink copied to clipboard

Explanation: Control-M/Analyzer could not allocate sufficient memory to compile a rule.

Compilation is terminated immediately.

Corrective Action: Increase the REGION size of the job or the TSO session. If this does not help, ask your INCONTROL Administrator to contact BMC Customer Support.

CTB115E DUPLICATE BLOCK NAME `blk` AT LINE `lin`Link copied to clipboard

Explanation: During rule compilation, a duplicate block name was found at the line indicated in the message. Block names within a rule must be unique. Relevant text appears in an accompanying message.

The variables in this message are:

blk - the duplicate block name
lin - the line in which the duplicate block name was found

The compiler continues processing the next block, but will terminate with syntax errors.

Corrective Action: Do the following:

Rename one of the blocks.
Correct any other errors in the rule member,
Recompile the rule.

CTB116E DUPLICATE LABEL `label` BEFORE LINE `lin`Link copied to clipboard

Explanation: During rule compilation, a duplicate label name was found in the line indicated in the message.

Label names within a rule must be unique. Relevant text appears in an accompanying message.

The variables in this message are:

label - the duplicate label name
lin - the line in which the duplicate label name was found

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Do the following:

Rename one of the labels.
Correct any other errors in the rule member.
Recompile the rule.

CTB117E UNRESOLVED REFERENCE FOR `label` IN OR BEFORE LINE `lin`Link copied to clipboard

Explanation: During rule compilation, a DO GOTO statement references an undefined label or a DO BLOCK statement references a block that does not exist. Relevant text appears in an accompanying message.

The variables in this message are:

label - the problematic label or block
lin - the line in or before which either the problematic label was found, or in or before which the problematic block was found not to exist

The compiler terminates with syntax errors.

Corrective Action: Correct errors in the rule member. Recompile the rule.

CTB118E THE MAXIMUM OF `num` "DO GOTO" STATEMENTS PER RULE HAS BEEN EXCEEDEDLink copied to clipboard

Explanation: During rule compilation, the maximum number of DO GOTO statements for a rule was exceeded. Relevant text appears in an accompanying message.

In this message, num is the maximum number of DO GO statements for a rule.

The compiler terminates with syntax errors.

Corrective Action: Do the following:

Either reduce the number of DO GOTO statements in the rule, or split the rule into multiple rules.
Correct any other errors in the rule member.
Recompile the rule.

CTB119E THE MAXIMUM OF `num` "DO BLOCK" STATEMENTS PER RULE HAS BEEN EXCEEDEDLink copied to clipboard

Explanation: During rule compilation, the indicated maximum number of DO BLOCK statements for a rule was exceeded. Relevant text appears in an accompanying message.

In this message, num is the maximum number of DO BLOCK statements for a rule.

The compiler terminates with syntax errors.

Corrective Action: Do the following:

Either reduce number of DO BLOCK statements in the rule, or split the rule into multiple rules.
Correct any other errors in the rule member.
Recompile the rule.

CTB120E LABEL `label` MUST OCCUR WITHIN THE SAME BLOCK AS THE REFERENCE TO ITLink copied to clipboard

Explanation: During rule compilation, a DO GOTO statement referenced a label outside the block in which it occurs. A DO GOTO statement can only reference labels within the same block. Relevant text appears in an accompanying message.

In this message, label identifies the problematic label.

The compiler continues processing the next block, but terminates with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB121E MAXIMUM LENGTH OF THE PARAMETER OF KEYWORD `keyName` IS `num`Link copied to clipboard

Explanation: During rule compilation, the value specified for the keyName keyword exceeded the indicated maximum length. Relevant text appears in an accompanying message.

The compiler continues processing the next block, but terminates with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB122W WARNING: RECURSIVE CALL TO BLOCK: " `blk`" IN OR BEFORE LINE `lin`Link copied to clipboard

Explanation: The rule being compiled has a block that calls itself. This is a warning, that there might be a problem.

The variables in this message are:

blk - the problematic block
lin - the line in or before which block appears

Corrective Action: Check the rule to verify that it does what you intend it to do.

CTB123E UNEXPECTED END OF SOURCE AFTER LINE `lin`Link copied to clipboard

Explanation: During rule compilation, there was an unfinished command at the end of the source member, or the source did not contain any blocks. Relevant text appears in an accompanying message.

The compiler terminates with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB124E SYNTAX ERROR ENCOUNTERED IN LINE `lin`Link copied to clipboard

Explanation: A syntax error occurred during rule compilation or runtime.

In this message, the variable lin has two possible meanings:

During rule compilation, lin identifies the line in the rule in which the error occurs.
During runtime, lin identifies the line in the DD name referenced by the MSUBSTMASK function in which the error occurs.

The system action varies according to the stage at which the error occurs, as follows:

If the error occurs during rule compilation, the compiler continues compiling at the next block, but issues syntax errors when it ends.
If the error occurs during runtime execution, Control-M/Analyzer stops executing and issues an error.

Corrective Action: Correct all errors in the rule, or in the DD name referenced by MSUBSTMASK, and recompile.

CTB125E NO BLANK CHARACTERS ALLOWED IN PARAMETER: " `parm`"Link copied to clipboard

Explanation: During rule compilation, the parm parameter contained embedded blanks.

Embedded blanks are not permitted in this parameter. Relevant text appears in an accompanying message.

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB126E FIRST CHARACTER MUST BE ALPHABETIC. SYNTAX ERROR IN LINE `lin`Link copied to clipboard

Explanation: During rule compilation, the first character of the parameter in the lin line should be, but was not, alphabetic. Relevant text appears in an accompanying message.

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB127E CHARACTERS MUST BE ALPHANUMERIC. SYNTAX ERROR IN LINE `lin`Link copied to clipboard

Explanation: During rule compilation, a non-alphanumeric character was found in the parameter in the lin line. The parameter must be alphanumeric. Relevant text appears in an accompanying message.

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB128I SRC: " `lin`"Link copied to clipboard

Explanation: This information message prints rule source lines that are rejected by the compiler. This message accompanies compilation error messages.

Corrective Action: No action is required.

CTB129I SRC: " `lin`"Link copied to clipboard

Explanation: This information message prints rule source lines that are rejected by the final syntax checker.

Corrective Action: No action is required.

CTB129W EXIT `exitName` WAS NOT LOADEDLink copied to clipboard

Explanation: Control-M failed to load the exitName user exit. Common reasons for failure are:

The IOA Load library is in the Linklist, and someone has updated the library without performing a refresh for the LLA.
The last assembly or linkage of the exit failed.
There is insufficient memory to load the new exit.

Control-M will continue to run, bypassing the exit.

Corrective Action: Check the computer Log for the cause of the failure.

CTB130I INTERNAL ERROR. SHOW THE FOLLOWING INFORMATION TO YOUR LOCAL IOA REPRESENTATIVE.Link copied to clipboard

Explanation: This message indicates that a Control-M/Analyzer internal error occurred.

The rule is not saved.

Corrective Action: Do the following:

Perform a screen print of the information shown.
Ask your IOA administrator to report the information to BMC Customer Support.
Press PF03/PF15 ( END ) to return to the editing screen.
Change the rule so that it can be saved.

CTB131I ADDR: `info`Link copied to clipboard

Explanation: This information message accompanies the CTB130I message.

Corrective Action: Ask your INCONTROL administrator to report the information in this message to BMC Customer Support.

CTB132E ERR: `asterisks`Link copied to clipboard

Explanation: This information message accompanies the message containing the text of the line in error. This message places an asterisk directly under the error in the text line.

Corrective Action: No action is required.

CTB133E NUMERIC VALUE MUST BE LESS THAN 256Link copied to clipboard

Explanation: During rule compilation, the numeric value indicated in the accompanying message must be less than 256. Relevant text appears in an accompanying message.

The compiler continues processing the next block, but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB134E NUMERIC VALUE MUST BE LESS THAN 4000Link copied to clipboard

Explanation: During rule compilation, the numeric value indicated in the accompanying message should be, but is not, less than 4000. Relevant text appears in an accompanying message.

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB135E VALID VALUES FOR URGENCY ARE R, U AND VLink copied to clipboard

Explanation: During rule compilation, the value of the URGENCY parameter in the SHOUT statement was found to be invalid.

Valid values for the URGENCY parameter are:

R - Regular
U - Urgent
V - Very Urgent

Relevant text appears in an accompanying message.

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB136E ABSOLUTE COLUMN NUMBER MUST BE NONZEROLink copied to clipboard

Explanation: During rule compilation, the value zero was specified for a column number. Column number values are absolute and must be greater than zero. Relevant text appears in an accompanying message.

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB137E LINE NUMBER MUST BE RELATIVELink copied to clipboard

Explanation: During rule compilation, a non-relative line number was specified. Relevant text appears in an accompanying message.

A line number must be relative, and must start with plus (+) or minus (-).

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB138E SUBSYSTEM ID MUST BE ALPHANUMERIC, @, $, OR #. FIRST CHARACTER MUST NOT BE A DIGITLink copied to clipboard

Explanation: The subsystem ID contains invalid characters.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Correct the specification of the subsystem ID.

CTB139E VALID VALUES FOR THIS FIELD ARE Y AND NLink copied to clipboard

Explanation: The value of the field in error was neither Y nor N. This field must contain Y for choosing a certain feature or N (or blank) for not choosing it.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Specify Y or N in the field, or leave it blank.

CTB13AE NUMERIC VALUE MUST NOT EXCEED 100Link copied to clipboard

Explanation: The specified value exceeded 100. The value specified in the field in error cannot exceed 100.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Specify a value of 100 or less.

CTB13BE NUMERIC VALUE MUST BE POSITIVELink copied to clipboard

Explanation: The specified value was zero. The value specified in the field in error cannot be zero.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Specify a positive number for the value.

CTB13CE VALID VALUES FOR DATASTAMP ARE 1, 2, AND BLANKLink copied to clipboard

Explanation: The DATASTAMP parameter contained an invalid value. Valid values for the DATASTAMP parameter are blank, 1 and 2, depending on whether or not a data stamp should be calculated and on the calculation technique that should be used.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Assign a valid value to the DATASTAMP parameter.

CTB13DE VSAM FILE TYPE MAY BE KSDS, RRDS OR ESDSLink copied to clipboard

Explanation: The VSAM file type specified in statement ON VSAM was invalid.

The TYPE parameter in an ON VSAM statement specifies the VSAM file type. Valid values are:

KSDS
RRDS
ESDS

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Correct the file type specification.

Messages CTB200 through CTB2xxLink copied to clipboard

This group includes messages for the Control-M/Analyzer product.

CTB200S ERLG AT `loc` (HEX- `xxxx`) INFO= `nn`Link copied to clipboard

Explanation: The general system Error Logger detected an error which occurred at a certain location. This message is issued when rare or unexpected errors occur.

The variables in this message are:

loc - the location within the Control-M/Analyzer runtime environment where the error occurred
xxxx - the hexadecimal equivalent of loc
nn - a number used for tracing the error

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Record the content of this message and consult your INCONTROL administrator.

CTB201S ERLG AT `name` LINE `lin`, INFO= `nnn`Link copied to clipboard

Explanation: The general system Error Logger detected an error which occurred at the location indicated in the message (name and line). This message is issued when rare or unexpected errors occur.

The variables in this message are:

name - the location in the Control-M/Analyzer runtime environment where the error occurred
lin - the line in the Control-M/Analyzer runtime environment where the error occurred
num - a number used for tracing the error

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Record the content of this message and consult your INCONTROL administrator.

CTB210E VARIABLE NAME `varName` TOO LONG (`num` CHARACTERS). MAXIMUM: `maxNum` CHARACTERSLink copied to clipboard

Explanation: The resolved length of the variable name exceeds the maximum valid length. The variable name was specified using AutoEdit symbols.

The variables in this message are:

varName - the first twenty characters of the resolved variable name
num - the length of the resolved variable name
maxNum - the maximum valid length of the resolved variable name

Control-M/Analyzer terminates.

Corrective Action: Correct the problem and rerun the rule.

CTB211E LIBRARY NAME `lib` TOO LONG (`num` CHARACTERS). MAXIMUM: `maxNum` CHARACTERSLink copied to clipboard

Explanation: The resolved length of the library name exceeds the maximum valid length. The library name was specified using AutoEdit symbols in a DO GETMEM, PUTSYM, or ADDSYM statement.

The variables in this message are:

lib - the first 44 characters of the resolved library name
num - the length of the resolved library name
maxNum - the maximum valid length of the resolved library name

Control-M/Analyzer terminates.

Corrective Action: Correct the problem and rerun the rule.

CTB212E MEMBER NAME `memName` TOO LONG (`num` CHARACTERS). MAXIMUM: `maxNum` CHARACTERSLink copied to clipboard

Explanation: The resolved length of the member name exceeds the maximum valid length. The member name was specified using AutoEdit symbols in a DO GETMEM, PUTSYM, or ADDSYM statement.

The variables in this message are:

memName - the first eight characters of the resolved member name
num - the length of the resolved member name
maxNum - the maximum length of the resolved member name

Control-M/Analyzer terminates.

Corrective Action: Correct the problem and rerun the rule.

CTB214E VALUE `val` for VARIABLE `varName` TOO LONG (`num` CHARACTERS). MAXIMUM: `maxNum` CHARACTERSLink copied to clipboard

Explanation: The resolved length of the variable exceeds the maximum valid length. The variable was specified using AutoEdit symbols in a DO SET or EXTRACT statement.

The variables in this message are:

varName - the first 100 characters of the resolved variable name
num - the length of the resolved variable name
maxNum - the maximum valid length of the resolved variable name

Control-M/Analyzer terminates.

Corrective Action: Correct the problem and rerun the rule.

CTB215I AUTOEDIT MEMBER `lib`(`memName`) WAS READ BUT NOT WRITTENLink copied to clipboard

Explanation: This information message indicates that a DO GETMEM statement, but not a DO PUTMEM statement, was requested and performed for an AutoEdit member. This could, but does not necessarily, indicate a problem.

Corrective Action: If this is not what you intended correct the rule.

CTB216I RUN-TIME ERROR OCCURRED. VARIABLES NOT COMMITTED FOR RULE `rule_name`Link copied to clipboard

Explanation: This information message indicates that, because Control-M/Analyzer encountered an error during rule processing, variables not explicitly committed by a DO COMMIT NOW statement will not be committed.

This message follows other messages that describe the error.

Control-M/Analyzer terminates. Variables not explicitly committed by statement DO COMMIT NOW are not committed.

Corrective Action: Using the information provided in the other messages, correct the problem and rerun the rule.

CTB217E VARIABLE NAME CANNOT CONTAIN BLANKS. VARIABLE=" `varName`"Link copied to clipboard

Explanation: The resolved variable name contains embedded blanks. The variable name was specified using AutoEdit symbols. Its resolved value should not, but does, contains embedded blanks.

In this message, varName is the first 20 characters of the problematic variable name.

Control-M/Analyzer terminates.

Corrective Action: Correct the problem and rerun the rule.

CTB218E VARIABLE " `varName`" IN DO RULE/BLOCK/CALLUSER NOT INITIALIZEDLink copied to clipboard

Explanation: An attempt was made to pass a variable to a rule, block or user routine without previously initializing the variable.

The variable name may be incorrectly specified in the DO RULE, BLOCK, or CALLUSER statement and the intended variable name was used. Before a variable can be passed to another rule, block, or user routine, or used in a DO RULE, BLOCK, or CALLUSER statement, the variable must be used at least once in the rule.

Control-M/Analyzer terminates.

Corrective Action: Correct the variable name if it is in error. Ensure that the variable name is initialized, that is, specified in a DO SET statement, prior to its usage in a DO RULE or BLOCK or CALLUSER statement.

CTB219E VALUE IS NOT NUMERIC: `val`Link copied to clipboard

Explanation: A value extracted by a DO EXTRACT statement for averaging or summing is not numeric. The extracted value must be numeric. This message is accompanied by either the CTB220E message or the CTB221E message.

Control-M/Analyzer terminates.

Corrective Action: Correct the problem and rerun the rule.

CTB220E WHILE AVERAGING VARIABLE `varName`Link copied to clipboard

Explanation: This message accompanies the CTB219E message and indicates precisely which operation was being attempted when the error occurred.

Control-M/Analyzer terminates.

Corrective Action: Correct the problem and rerun the rule.

CTB221E WHILE SUMMING VARIABLE `varName`Link copied to clipboard

Explanation: This message accompanies the CTB219E message and indicates precisely which operation was attempted when the error occurred.

Control-M/Analyzer terminates.

Corrective Action: Correct the problem and rerun the rule.

CTB222E ERROR WHILE PROCESSING VALUE: `val.` PROCESS: `procName`Link copied to clipboard

Explanation: The requested process cannot be applied to the value obtained by the DO EXTRACT statement.

The variables in this message are:

val - the value obtained by the DO EXTRACT statement
procName - the process that was requested, but that cannot be applied to val

For information about permitted processes and valid input for processes, see the Control-M/Analyzer User Guide.

Control-M/Analyzer terminates.

Corrective Action: Correct the problem and rerun the rule.

CTB223E AUTOMATIC CREATION OF DATABASE VARIABLES IS NOT ENABLED. CHANGE VARCRET TO "Y" IN CTBPARMLink copied to clipboard

Explanation: An attempt was made to use a database variable not previously defined in the database.

Control-M/Analyzer allows you to automatically create new database variables only if the VARCRET parameter in the CTBPARM member is set to Y.

Control-M/Analyzer terminates.

Corrective Action: If the variable name was specified incorrectly, correct it and rerun the rule. To create a new database variable, set the VARCRET parameter in the CTBPARM member to Y and rerun the rule.

CTB224E NUMBER OF GENERATIONS FOR SYSDBVGENS SYSTEM VARIABLE IS TOO HIGH: `num`. MAXIMUM IS 1000Link copied to clipboard

Explanation: An attempt was made to set the SYSDBVGENS parameter to a value higher than the maximum allowed.

The SYSDBVGENS parameter determines the number of generations of automatically generated database variables. The maximum number allowed is 1000.

Control-M/Analyzer terminates.

Corrective Action: Correct the problem and rerun the rule.

CTB225E INVALID NUMBER OF GENERATIONS FOR SYSDBVGENS SYSTEM VARIABLE: `num`Link copied to clipboard

Explanation: An attempt was made to set the value of the SYSDBVGENS parameter to a nonnumeric value.

The SYSDBVGENS parameter is used to determine the number of generations of automatically generated database variables. Its value must be numeric.

Control-M/Analyzer terminates.

Corrective Action: Correct the problem and rerun the rule.

CTB226S INTERNAL ERROR IN CTBVARS: RC= `rc` INVALIDLink copied to clipboard

Explanation: An internal error occurred while processing variables.

Control-M/Analyzer terminates.

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

CTB227E PROCESS `procName` HAS INVALID LENGTH (`invalidNum`). LENGTH SHOULD BE `validNum`Link copied to clipboard

Explanation: The input variable is not the correct length for the selected DO EXTRACT statement process.

The following DO EXTRACT statement processes require variables with the lengths indicated:

BBINF - variable length 4
BBINH - variable length 2
BBINC - variable length 1

Control-M/Analyzer terminates.

Corrective Action: Correct the problem and rerun the rule.

CTB229E UNKNOWN [BUILT-IN] PROCESS `procName`Link copied to clipboard

Explanation: The requested process is unknown to Control-M/Analyzer. The process name was incorrectly specified. The type descriptor BUILT-IN appears in the message only if the process is a BUILT-IN process.

Control-M/Analyzer terminates.

Corrective Action: Correct the process name and rerun the rule.

CTB22AE AUTOMATIC CREATION OF DATABASE VARIABLES IS ALLOWED ONLY FOR THE CURRENT GROUPLink copied to clipboard

Explanation: An attempt was made to use a database variable that was one of the following:

not previously defined in the database
assigned to a group that is not the current group

Control-M/Analyzer allows you to automatically create new database variables within the group of the current rule if the VARCRET parameter in the CTBPARM member is set to Y.

Control-M/Analyzer terminates.

Corrective Action: If the variable was specified incorrectly, correct it and rerun the rule. Otherwise, predefine the variable and rerun the rule.

CTB22BE ACCESS TO VARIABLE DATABASE DENIED. OPERATION= `opn`Link copied to clipboard

Explanation: The Control-M/Analyzer security interface does not permit you to perform the requested operation (opn) on the Control-M/Analyzer database.

Control-M/Analyzer terminates.

Corrective Action: If you think you should be authorized to perform the requested operation, contact your security administrator.

CTB22CE YOU ARE NOT AUTHORIZED TO USE THIS GROUP. GROUP= `grp`Link copied to clipboard

Explanation: The Control-M/Analyzer security interface does not permit you to use the grp group.

Control-M/Analyzer terminates.

Corrective Action: If you think you should be authorized to use the specified group, contact your security administrator.

CTB22DE VALUE `val` IS ILLEGAL FOR SYSTEM VARIABLE `varName`Link copied to clipboard

Explanation: An invalid value (val) was assigned to the varName system variable. The varName system variable can have only certain values.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Consult the Control-M/Analyzer User Guide for information about the varName system variable.

CTB22EE VARIABLE `varName` IS NOT ALLOWED AS A DO RULE/BLOCK/CALLUSER ARGUMENT BECAUSE OF ITS TYPELink copied to clipboard

Explanation: The AutoEdit variable or System variable varName was specified as an argument in a DO RULE, BLOCK, or CALLUSER statement.

AutoEdit and System variables may not be passed as arguments to DB2.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Assign the value of the argument in error to a user variable and pass that user variable to DB2 instead.

CTB22FE UNABLE TO CREATE VARIABLE `varName`, THE PREFIX OF ITS NAME IS INVALIDLink copied to clipboard

Explanation: The name (varName) of a variable to be created has the prefix of a variable that the DO SET command cannot create. The DO SET command can create user and AutoEdit variables only. In this case, a prefix was specified which marks another type of variable, for example, a system variable.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Correct the variable name.

CTB230I NO MATCHING MISSION IN ACTIVE BALANCING FILE. MISSION: `missionName`Link copied to clipboard

Explanation: This message indicates that the Active Balancing file does not contain the missionName mission specified in the call to Control-M/Analyzer.

Control-M/Analyzer terminates.

Corrective Action: Either correct the name of the mission, or order the mission to the Active Balancing file. Rerun the Control-M/Analyzer rule.

CTB231E COULD NOT ADD AN ENTRY TO THE ACTIVE BALANCING FILELink copied to clipboard

Explanation: Control-M/Analyzer was unable to add information to the Active Balancing file. This message usually indicates that the Active Balancing file is full.

Control-M/Analyzer terminates.

Corrective Action: Contact your INCONTROL administrator.

CTB232E `dsn` FILE IS FULL. UNABLE TO ADD `recordType`Link copied to clipboard

Explanation: Control-M/Analyzer failed to add a record to the file identified in the message because it was full.

The variables in this message are:

dsn - the name of the data set that was found to be full
recordType - the type of record that failed to be added to dsn

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Increase the size of the data set referenced by the dsn DD statement.

CTB233E `dsn` FILE FORMATTED WITH A ZERO-LENGTH KEYLink copied to clipboard

Explanation: The dsn Control-M/Analyzer database index file could not be opened. Index files must have a positive key length.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Reformat the data set referenced by the dsn DD statement and rerun the job.

CTB234E UNABLE TO OPEN FILE `dsn` . CONFLICTING INSTALLATION PARAMETER QNAMELink copied to clipboard

Explanation: The QNAME specified in the dsn Control-M/Analyzer database file was different than the expected QNAME. The version of the Control-M/Analyzer runtime environment is different than the version of the utility which was used to format the file.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Verify that the correct Control-M/Analyzer database was allocated and rerun the job.

CTB235S ENQUEUE PROBLEM IN FILE `dsn` Link copied to clipboard

Explanation: Control-M/Analyzer could not lock the database file for update.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Check the reason for the conflict and rerun the Control-M/Analyzer job after the current applications have finished running.

CTB236S DUAL DATABASE PROBLEM IN FILE `dsn`. RC= `rc`Link copied to clipboard

Explanation: Control-M/Analyzer failed due to an integrity error in the dsn mirror database file.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Disable the mirror database installed for this particular file. Record the content of this message and report it to your INCONTROL administrator. If the situation allows, the Control-M/Analyzer job can be rerun.

CTB237E `opn` FAILED FOR FILE `ddName` INDEX OR DATA. RC= `rc`Link copied to clipboard

Explanation: An error occurred while performing an operation on the specified file.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Provide the sysout and contents of this message to your INCONTROL administrator.

CTB239S `opn` FAILED FOR FILE `ddName`. RC= `rc`Link copied to clipboard

Explanation: An error occurred while performing the operation on the ddName file.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Record the contents of this message and consult your INCONTROL administrator.

CTB23AS LINK OF IOADBF FAILED IN IOADBSLink copied to clipboard

Explanation: The IOADBF load module cannot be found.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Check the concatenated load libraries referenced by the DDNAME STEPLIB statement and rerun the Control-M/Analyzer job.

CTB23BE dsn FILE IS FORMATTED INCORRECTLY. KEY LENGTH SHOULD BE ZEROLink copied to clipboard

Explanation: The data component of the dsn Control-M/Analyzer database file was formatted with a positive-length key. Data files must not be keyed.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Reformat the data set referenced by the dsn DD statement and rerun the job.

CTB23CE `ddName` FILE IS FORMATTED INCORRECTLY. `key/record` LENGTH SHOULD BE `len`Link copied to clipboard

Explanation: A length of a key or record specified when formatting the file was incorrect. Each Control-M/Analyzer database file must adhere to specific length specifications.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Reformat the data set referenced by the ddName DD statement and rerun the job.

CTB240E ON `blk` BLOCK CANNOT BE USED UNDER `environmt`Link copied to clipboard

Explanation: The specified ON block cannot be used in the specified environment. ON blocks are restricted to specific environments, as follows:

If Control-M/Analyzer is running standalone, neither ON PAGE nor ON SYSDATA statements can be used in the rule.
If Control-M/Analyzer is running under Control-M, ON PAGE, ON SYSOUT, ON CLASS and ON DSN statements cannot be used in the rule.
If Control-M/Analyzer is running under Control-D, ON SYSDATA, ON SYSOUT, ON CLASS and ON DSN statements cannot be used in the rule.

Control-M/Analyzer terminates.

Corrective Action: Correct the error, and rerun the rule.

CTB241E `posn` MUST BE NUMERICLink copied to clipboard

Explanation: The record offset (for RRDS files) or the RBA (for ESDS files) specified in the FIRSTKEY or the LASTKEY parameter was not numeric.

The format of the record offset or RBA format is C nnn, where nnn is any 3-digit numeric string.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Set the FIRSTKEY or the LASTKEY parameter to a value in the format C nnn, where nnn is any 3-digit numeric string.

CTB242E VSAM CRITERIA `crit` DOES NOT COMPLY WITH THE REQUIRED FORMATLink copied to clipboard

Explanation: The criteria specified in either the FIRSTKEY or the LASTKEY parameter, or both these parameters, of the ON VSAM statement were not in the correct format.

The values of the FIRSTKEY and LASTKEY parameters must be in the format C cccc ,X xxxx ,... for all VSAM file types.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Correct the values of the FIRSTKEY and LASTKEY parameters into the required format.

CTB243E FILE `fileName` WAS NOT FOUNDLink copied to clipboard

Explanation: The fileName file specified in an ON statement was not found.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Correct the file name specification. If it includes AutoEdit variable substitution, make sure the variables have valid values.

CTB248E NON-NUMERIC OR ZERO `n` SPECIFIED IN PROCESS BW `n`Link copied to clipboard

Explanation: The character specified after BW in a DO EXTRACT statement was not a positive integer.

The n in the BW n process in a DO EXTRACT statement specifies the number of the word to be extracted, and must be a positive integer.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Verify that only a positive integer follows BW in the BW n specification.

CTB249W WORD COUNT (`num`) SMALLER THAN `nnn` IN PROCESS BW `n` (SYSRC SET TO 4)Link copied to clipboard

Explanation: The number of words in the text to be examined was less than the value of n specified in the BW n process in a DO EXTRACT statement. This message may indicate either an error in specifying the BW n process, or unexpectedly short data.

The SYSRC system variable is set to 4, and processing continues.

Corrective Action: Examine all the following and ensure that they are correct:

the EXTRACT column limits
the BW n process specification
the supplied input data

CTB24AE VARIABLE SYSEXTUPROC FOR EXTRACT PROCESS BUPROC IS NOT DEFINEDLink copied to clipboard

Explanation: The SYSEXTUPROC system variable was not assigned a value when the BUPROC process was requested in a DO EXTRACT statement. The BUPROC process in a DO EXTRACT statement requires the SYSEXTUPROC system variable to be defined.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Use a DO SET statement to store the desired user-defined process in the SYSEXTUPROC system variable prior to specifying the BUPROC process.

CTB24BE INVALID COMBINED PROCESS NAME `procName`. USE BCPROC`n` WITH `n` = 1 to 10Link copied to clipboard

Explanation: The user-defined combined EXTRACT process name was not in the format BCPROC n, where n is an integer from 1 to 10.

The combined EXTRACT process invokes a sequence of processes specified in the SYSCPROC n system variable. This variable can be defined only when n is an integer from 1 through 10.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Set the combined EXTRACT process name in the format BCPROC n, where n is an integer from 1 through 10.

CTB24CE VARIABLE SYSCPROCn DOES NOT EXIST FOR PROCESS `procName`Link copied to clipboard

Explanation: The combined EXTRACT process referred to an undefined system variable (SYSCPROC n).

The combined EXTRACT process BCPROCn invokes a sequence of processes specified in the SYSCPROC n system variable. This system variable must be defined before executing an EXTRACT statement that refers to it.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Set the SYSCPROC n system variable to a sequence of EXTRACT processes or change the reference in the EXTRACT statement to a defined system variable.

CTB250E FILE `ddName` CANNOT BE OPENEDLink copied to clipboard

Explanation: During a Control-M/Analyzer run, the file referenced by the ddName DD statement could not be opened.

Probable causes are:

The ddName DD statement is missing.
The data set referenced by the ddName DD statement cannot be accessed.

Execution continues. If the error occurred during a DO PRINT statement, then output to the file referenced by the ddName DD statement is rerouted to the file referenced by SYSUSERDD statement.

Corrective Action: Correct the JCL and rerun the job.

CTB250S FILE `ddName` CANNOT BE OPENEDLink copied to clipboard

Explanation: During a Control-M/Analyzer run, the file referenced by the ddName DD statement could not be opened.

Probable causes are:

The ddName DD statement is missing.
The data set referenced by the ddName DD statement cannot be accessed.

The Control-M/Analyzer runtime environment ends with an error.

Corrective Action: Correct the JCL and rerun the job.

CTB255E OCCURRENCE MUST BE POSITIVE IN `func`Link copied to clipboard

Explanation: An occurrence specified in the func function was zero or negative.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Specify a positive occurrence value.

CTB256E WORD NUMBER MUST BE POSITIVE IN FUNCTION WORDLink copied to clipboard

Explanation: The word number specified in the WORD function was zero or negative.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Specify a positive word number.

CTB257E ENTRY NUMBER MUST BE POSITIVE IN DDINFOLink copied to clipboard

Explanation: The data set entry number specified in the DDINFO function was zero or negative.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Specify a positive data set entry number.

CTB258E STARTING OCCURRENCE MUST NOT EXCEED ENDING OCCURRENCE IN `func`Link copied to clipboard

Explanation: The starting occurrence exceeds the ending occurrence in the specified occurrence range.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Set the occurrence range in the func function to begin with the lower occurrence.

CTB259W WORD NUMBER `num` REQUESTED BUT INPUT STRING CONTAINS ONLY `nnn` WORDS (SYSRC SET TO 4)Link copied to clipboard

Explanation: The number of words in the input string to the WORD function was smaller than the requested word number.

This message may indicate either an error in coding the call to the WORD function or an unexpectedly short input string.

The SYSRC system variable is set to 4 and processing continues.

Corrective Action: Ensure that the parameters of the WORD function are specified correctly.

CTB25AE DDNAME `ddName` WAS NOT FOUND IN STEP `procStep`. `pgmStep` (SYSRC SET TO 4)Link copied to clipboard

Explanation: The DD name (ddName) specified in the DDNUM or the DDINFO function was not found.

There is no DD statement with the ddName DD name in the procStep.pgmStep job step.

The SYSRC system variable is set to 4 and processing continues.

Corrective Action: Verify that the parameters specified in the DDNUM or DDINFO function are correct.

CTB25BE INFORMATION FOR DATASET NUMBER `num` IN DD STATEMENT `ddName` WAS REQUESTED BUT ONLY `nn` DATASETS ARE ALLOCATED (SYSRC SET TO 8)Link copied to clipboard

Explanation: The number of data sets allocated to the ddName DD statement is less than the requested entry number in the DDINFO function.

The SYSRC system variable is set to 8 and processing continues.

Corrective Action: Specify a smaller data set entry number or verify that the JCL is correct.

CTB25CE UNABLE TO GET NUMBER OF LINES OF MEMBER `mem` IN LIBRARY `lib` - ISPF STATISTICS DO NOT EXISTLink copied to clipboard

Explanation: The MEMLINES function failed to retrieve the number of lines of a member, because ISPF statistics did not exist for the member. The MEMLINES function obtains the member line-count from the ISPF statistics of the member. When the statistics are missing, the MEMLINES function cannot obtain the line-count.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Save the member using ISPF so that statistics for it are created.

CTB260E IN THIS MODE, GROUP `grp` CANNOT READ VARIABLE `varName`Link copied to clipboard

Explanation: A DO SET expression could not read a database variable belonging to the grp group, due to group mode differences between the specified group and the current group. Control-M/Analyzer determines if it can read database variables belonging to other groups based on the modes of the groups.

When the current group is in ACTIVE mode, Control-M/Analyzer can read variables belonging to other groups in ACTIVE mode. It cannot read variables belonging to other groups in SIMULATION or DEFINE mode.

When the current group is in SIMULATION mode, Control-M/Analyzer can read variables from other groups in ACTIVE or SIMULATION mode. It cannot read variables belonging to other groups in DEFINE mode.

This message follows the CTB262I message, which specifies the name and mode of the group that Control-M/Analyzer attempted to access in order to read the variable. For more information about group modes, see the Control-M/Analyzer User Guide.

Control-M/Analyzer terminates.

Corrective Action: Ensure that the groups which Control-M/Analyzer attempts to access for a read operation are in an appropriate mode. Invoke Control-M/Analyzer again.

CTB261E IN THIS MODE, GROUP `grp` CANNOT SET VARIABLE `varName`Link copied to clipboard

Explanation: The indicated database variable belonging to the grp group could not be set, due to group mode differences between that group and the current group. Control-M/Analyzer determines if it can set database variables belonging to other groups based on the modes of the groups.

When the current group is in ACTIVE mode, Control-M/Analyzer can set variables belonging to other groups that are in ACTIVE mode. It cannot set variables belonging to other groups in SIMULATION or DEFINE mode.

When the current group is in SIMULATION mode, Control-M/Analyzer can set variables belonging to other groups in SIMULATION mode. It cannot set variables belonging to other groups in ACTIVE or DEFINE mode.

This message follows the CTB262I message, which specifies the name and mode of the group that Control-M/Analyzer tried to access to set the variable. For more information about group modes, see the Control-M/Analyzer User Guide.

Control-M/Analyzer terminates.

Corrective Action: Ensure that the groups which Control-M/Analyzer attempts to access for a set operation are in an appropriate mode. Invoke Control-M/Analyzer again.

CTB262I GROUP `grp` IS IN `modeType` MODELink copied to clipboard

Explanation: This information message indicates the name and mode of the group that Control-M/Analyzer tried to access for either a read or a set operation.

This message accompanies the CTB260E message or the CTB261E message, issued when the requested operation could not be performed because of mode differences between the group to be accessed and the current group.

Corrective Action: No action is required.

CTB270W THE VARIABLE SET `varset` IS EMPTY (SYSRC SET TO 8)Link copied to clipboard

Explanation: No variables were found whose names belong to the specified set. This message is issued by the SUM, HOWMANY, and NEXTVAR functions when no variable names match the name-mask arguments or the database criteria.

The HOWMANY and SUM functions return zero. The NEXTVAR function returns a blank string. The SYSRC system variable is set to 8.

Corrective Action: Verify that this situation is not a result of improper coding or improper input data.

CTB271E NON-NUMERIC VALUES WERE FOUND IN THE VARIABLE SETLink copied to clipboard

Explanation: One of the variables in the set contains a nonnumeric value. The SUM function expects a name-mask or database criteria that specifies only numeric variables.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Eliminate non-numeric values from the variable set in one of the following ways:

Verify that only numeric values are assigned to the variables in the set specified in the SUM function.
Redefine the set accordingly.
Rename the non-numeric variables so that they will not be included in the set.
Verify that all the variables in the set specified in the SUM function contain numeric values.

CTB272E VARIABLE `startvar` IS NOT IN `varset` OR DOES NOT EXISTLink copied to clipboard

Explanation: The startvar starting variable specified in the NEXTVAR function does not belong to the varset set, or the startvar variable was not found. The startvar starting variable specified in the NEXTVAR function must exist, and it must belong to the identified variable set.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Verify that the startvar variable is contained in the varset set. Either respecify the criteria or change the startvar variable name.

CTB282I text (userId`userId`)Link copied to clipboard

Explanation:Highlighted, unrollable message.

This information message is activated by the SHOUT facility.

In this message, userId is the user ID of the job order requesting the SHOUT.

Corrective Action: No action is required.

CTB284I NEW DYNAMIC DESTINATION TABLE LOADEDLink copied to clipboard

Explanation: This information message indicates that a new Dynamic Destination Table has been loaded by the IOA Runtime environment. This message is also generated when the SHOUT Facility is initialized under the IOA Runtime environment.

Corrective Action: No action is required.

CTB285W DYNAMIC DESTINATION TABLE NOT LOADEDLink copied to clipboard

Explanation: Loading of the Dynamic Destination Table by the IOA Runtime Environment failed.

This could be due to one of the following:

insufficient memory for loading the table
the IOADEST table does not exist in the IOA PARM library

If the failure occurs during the initialization of the IOA Runtime Environment, SHOUT notifications will not be controlled by the Dynamic Destination Table.

Corrective Action: Check the MVS Log for the reason for the failure (probably a system abend code). Correct the problem and then run the job again.

Messages CTB300 through CTB3xxLink copied to clipboard

This group includes messages for the Control-M/Analyzer product.

CTB303E FILL IN THE REQUIRED FIELDLink copied to clipboard

Explanation: A required field has not been filled in. The cursor points to the required field.

Corrective Action: Fill in the required field.

CTB304E FIELD MUST BE `num` DIGITS IN LENGTHLink copied to clipboard

Explanation: The value in the field is not the required length. The field must contain num digits.

Corrective Action: Correct the field value.

CTB305E FILL IN THE LINE/COL RANGELink copied to clipboard

Explanation: Line/column range data has not been specified.

Corrective Action: Fill in the line/column range.

CTB306E "ON DATA" STATEMENT CANNOT BE REPLACED BY ANOTHER "ON" STATEMENTLink copied to clipboard

Explanation: The user attempted to overwrite the ON DATA statement with another ON statement. After an ON DATA statement has been specified, it cannot be overwritten by another ON statement. It can be replaced by an empty ON statement. Then a new ON statement can be defined in its place.

For more information, see the ON DATA statement in the Control-M/Analyzer User Guide.

Corrective Action: Delete the keyword DATA from the ON DATA statement and press Enter. Then define the desired ON statement.

CTB307E "ON DATA" STATEMENT CANNOT REPLACE ANOTHER "ON" STATEMENTLink copied to clipboard

Explanation: The user attempted to overwrite an existing ON statement with an ON DATA statement. After an ON statement is specified, it cannot be overwritten by an ON DATA statement. The ON statement can, be replaced by an empty ON statement. Then an ON DATA statement can be defined in its place.

Corrective Action: Delete the keyword from the ON statement and press Enter:. Then define the ON DATA statement.

CTB308E FIELD MUST BE NUMERIC OR BLANKLink copied to clipboard

Explanation: The field contains nonnumeric data. The field must be blank or contain numeric data. If numeric values are used, then no trailing and leading blanks are not allowed.

Corrective Action: Correct the value in the field.

CTB309E FIRST CHARACTER CANNOT BE NUMERICLink copied to clipboard

Explanation: The first column in the field contains a numeric value. It should be alphabetic.

Corrective Action: Correct the value in the field.

CTB310E INVALID NAMELink copied to clipboard

Explanation: The field contains characters not permitted in a name specification, for example, - s, +, !.

Corrective Action: orrect the name.

CTB311I PLEASE PLACE CURSOR WITHIN AN "ON" BLOCKLink copied to clipboard

Explanation: This information message indicates that the user attempted to open an empty comment line outside of an ON block. A comment line can only be placed within an ON block.

Corrective Action: Open the comment line within an ON block.

CTB312E VALID VALUE IN THIS POSITION IS "+" OR "- "Link copied to clipboard

Explanation: The value specified at the cursor position must be either + or - . The cursor points to the position requiring the + or - value.

Corrective Action: Correct the value at the cursor position.

CTB313E INVALID FORMATLink copied to clipboard

Explanation: The value in the field referenced by the cursor has an invalid format.

Corrective Action: Refer to the Control-M/Analyzer User Guide to determine the correct format for the field. Correct the value in the field.

CTB314E INVALID VALUE. SPECIFY "OK", "NOTOK", "TOLER", OR "ABEND"Link copied to clipboard

Explanation: The field does not contain a valid value.

Valid values are:

OK
NOTOK
TOLER
ABEND

Corrective Action: Correct the value in the field.

CTB315E INVALID VALUELink copied to clipboard

Explanation: The field pointed to by the cursor does not contain a valid value.

Corrective Action: Refer to the Control-M/Analyzer User Guide to determine valid values for the field. Correct the value.

CTB316E TOO MANY CONTINUATION LINESLink copied to clipboard

Explanation: The maximum number of continuation lines for the line type has been exceeded.

The cursor points to the first extra line.

Corrective Action: Delete the extra line.

CTB317E "DO EXTRACT" NOT PERMITTED IN "ON DATA" BLOCKLink copied to clipboard

Explanation: A DO EXTRACT action was specified within an ON DATA block. This action is not permitted in an ON DATA block.

Corrective Action: Remove the DO EXTRACT statement from the ON DATA block.

CTB318E "DO GOTO" PERMITTED ONLY IN "ON DATA" BLOCKLink copied to clipboard

Explanation: A DO GOTO action was specified outside an ON DATA block. This action is only permitted within an ON DATA block.

Corrective Action: Remove the invalid DO GOTO statement.

CTB319E TYPE IN CHARACTER "=" AFTER VARIABLE NAMELink copied to clipboard

Explanation: The = character is missing from the DO SET statement. The = character is required to separate the variable value from the variable name.

Corrective Action: Correct the DO SET statement.

CTB320E ONLY TRAILING BLANKS ALLOWED IN VARIABLE VALUELink copied to clipboard

Explanation: Statement DO SET contains blanks immediately following the = character. The variable value, which follows the = character, cannot contain leading blanks. Trailing blanks are permitted in the variable value.

Corrective Action: Remove the leading blanks in the variable value.

CTB321E AMBIGUOUS ABBREVIATION SPECIFIEDLink copied to clipboard

Explanation: The abbreviation specified in the DO/ON line is ambiguous. There is more than one statement type starting with this abbreviation.

Corrective Action: Specify a longer, unique statement name.

CTB322E INVALID FORMAT. SHOULD BE "+/- NNN"Link copied to clipboard

Explanation: The value specified is not in a valid format. The value must consist of a 3-digit number preceded by either a + or - character.

Corrective Action: Specify the value using the correct format.

CTB323E VALID OPTIONS ARE "C", "D", "N" AND "R"Link copied to clipboard

Explanation: An invalid value is specified in the OPT field in the DO SYSOUT statement. The OPT field in the DO SYSOUT statement can accept only the values listed in the message.

Corrective Action: Correct the contents of the OPT field accordingly.

CTB324E INVALID CLASS. SHOULD BE BETWEEN A-Z OR 0-9Link copied to clipboard

Explanation: An invalid value is specified in the FRM field in the DO SYSOUT statement. The FRM field in the DO SYSOUT statement can accept only the values listed in the message.

Corrective Action: Correct the contents of the FRM field accordingly.

CTB325E FOR OPTIONS "R" AND "D" FIELD MUST BE BLANKLink copied to clipboard

Explanation: A value is specified in the PRM field in the DO SYSOUT. The PRM field in the DO SYSOUT statement must remain empty when the user specifies either R or D in the OPT field.

Corrective Action: Delete the value in the PRM field.

CTB326E FIRST CHARACTER MUST BE ALPHABETIC OR "$","#","@" SIGNSLink copied to clipboard

Explanation: The parameter or variable contains invalid characters.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Correct the subsystem parameter or variable specification.

CTB327E DUPLICATE LABEL NAMES NOT ALLOWED. PLEASE CHANGE ITLink copied to clipboard

Explanation: The LABEL field on which the cursor is positioned contains a name that already appears in the rule definition.

Corrective Action: Change the label name.

CTB328E INVALID OPTION (USE "R", "L" OR BLANK)Link copied to clipboard

Explanation: The value specified for the field on which the cursor is positioned is invalid.

Corrective Action: Specify either R, L, or leave the field empty.

CTB329E INVALID OPTION (USE "Y" OR "N")Link copied to clipboard

Explanation: Y or N is not specified in the field on which the cursor is positioned.

Corrective Action: Specify either Y or N.

CTB330E INVALID LENGTH. SHOULD BE BETWEEN 1-133Link copied to clipboard

Explanation: The length specified in the LEN field is invalid.

The length can be only in the range from 1 to 133.

Corrective Action: Specify a value within the range from 1 to 133.

CTB331E PRECISION MUST BE LESS THAN LENGTHLink copied to clipboard

Explanation: The value specified in the PREC field exceeds the value specified in LEN field. The precision cannot be greater than the length.

Corrective Action: Correct the value of the PREC field.

CTB332E FILL IN AT LEAST ONE FORMAT PARAMETERLink copied to clipboard

Explanation: No value is specified in the OUTDD or the FORMAT VAR fields. At least one of the OUTDD or the FORMAT VAR fields appearing on the screen must have a value.

Corrective Action: Specify a value in either the OUTDD or the FORMAT VAR fields.

CTB333E INVALID OPTION (USE "1", "2" OR BLANK)Link copied to clipboard

Explanation: value specified for the field on which the cursor is positioned is invalid.

Corrective Action: Specify 1 or 2, or leave the field empty.

CTB334E INVALID FILE TYPE (USE "KSDS", "RRDS" OR "ESDS")Link copied to clipboard

Explanation: The value specified for the FILE TYPE field is invalid.

Corrective Action: Specify KSDS, RRDS, or ESDS.

CTB335E INVALID VARIABLE NAME. NO BLANKS IN THE VARIABLE NAME ARE ALLOWEDLink copied to clipboard

Explanation: The ARG field of a DO RULE, DO BLOCK or DO CALLUSER statement contains one or more blanks in a variable name. Trailing blanks are not allowed in the ARG field of a DO RULE, BLOCK, or CALLUSER statement, and blanks are not allowed in a variable name.

Corrective Action: Correct the invalid variable name.

CTB336E FIRST CHARACTER MUST BE ALPHABETIC (A-Z)Link copied to clipboard

Explanation: The variable name begins with a non-alphabetical symbol.

Corrective Action: Correct the invalid variable name.

CTB337E TOO MANY ARGUMENTS. A MAXIMUM OF 50 ARGUMENTS EXCEEDEDLink copied to clipboard

Explanation: The ARG field in a DO RULE, DO BLOCK or DO CALLUSER contains more than 50 arguments. A maximum of 50 arguments can be specified.

Corrective Action: Decrease the number of arguments specified.

CTB350E OPTION "D" CANNOT BE USED WITH OTHER OPTIONSLink copied to clipboard

Explanation: An attempt has been made to use the D option with other options. Option D cannot be mixed with other options.

Corrective Action: Perform the D option, and then perform other options.

CTB351E WHEN OPTION "C" OR "I" IS USED, ONLY ONE OPTION IS ALLOWEDLink copied to clipboard

Explanation: User tried to specify more than one Option C or Option I. Multiple occurrences of Option C or Option I are not permitted, nor can these options be specified with other options.

Corrective Action: Perform Option C or Option I alone.

CTB352S UNABLE TO INITIALIZE THE "C" ENVIRONMENTLink copied to clipboard

Explanation: The Control-M/Analyzer Online Facility is unable to initialize the C language environment. The C language environment must be initialized when entering the Rule Definition screen.

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

CTB353E RULE COMPILATION UNSUCCESSFULLink copied to clipboard

Explanation: The rule could not be compiled because it contains invalid data. The rule was prepared by means of the ISPF editor. Its contents do not conform to Control-M/Analyzer standards.

Compilation error messages are displayed.

Corrective Action: Use the ISPF editor to correct the rule.

CTB354E NONZERO RC FROM THE FINAL SYNTAX CHECKLink copied to clipboard

Explanation: Errors were detected in the rule definition during the final syntax check. Although the rule was prepared using the Control-M/Analyzer Online Facility, due to an internal error its contents do not conform to Control-M/Analyzer standards.

Error messages from the final syntax check are displayed.

Corrective Action: Use the Control-M/Analyzer Online Facility to correct the rule.

CTB355E SELECTED MEMBER IS NOT A VALID RULE MEMBERLink copied to clipboard

Explanation: The selected member is not a valid Control-M/Analyzer rule member.

The message could result from one of the following:

The member requested is not a rule.
The member requested is a rule, but the rule has been incorrectly modified by means of an editor or program, and now its contents do not conform to Control-M/Analyzer standards.

Corrective Action: Enter a valid Control-M/Analyzer rule. If the specified rule has been incorrectly modified, try to restore it to its original state or correct it.

CTB356E ERROR IN RULE MEMBER. ZOOM SCREEN CANNOT BE BUILTLink copied to clipboard

Explanation: The rule contains invalid data.

The rule contains invalid data. Possible causes are:

The member requested is not a rule, although its structure is similar to one.
The member requested is a rule, but the rule has been incorrectly modified by means of an editor or program, and now its contents do not conform to Control-M/Analyzer standards.

Corrective Action: If the contents of the rule have been modified, try to restore the rule to its original state. If you cannot or if this is not the problem, ask your INCONTROL administrator to call BMC Customer Support.

CTB357E INSUFFICIENT STORAGE TO LOAD RULE MEMBERLink copied to clipboard

Explanation: Insufficient storage to load the rule member.

Corrective Action: Do one the following:

Log on again using a larger SIZE parameter.
If you are using many IOA screens concurrently, exit some of them using the END command.
Split the rule into two rules.

CTB358E INSUFFICIENT STORAGE TO SHOW RULE DETAILSLink copied to clipboard

Explanation: Insufficient storage to display the rule on the ZOOM screen.

Corrective Action: Do one of the following:

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

CTB359E INSUFFICIENT STORAGE TO PROCESS CHANGES TO RULE PARAMETERS.Link copied to clipboard

Explanation: There is insufficient storage to process the changes to rule parameters in the Zoom screen.

All changes to the rule are ignored. The Rule List screen is displayed.

Corrective Action: Do one, or both, of the following:

If you are using many IOA screens concurrently, exit some of them using the END command. Then, try to save the rule.
Log on again using a larger SIZE parameter.

CTB360E RULE IS IN USE BY ANOTHER USERLink copied to clipboard

Explanation: Another Control-M/Analyzer user is currently working on the rule. Two users cannot work on the same rule simultaneously. The other user may be using the rule either by means of the Control-M/Analyzer Online Facility or by means of the ISPF editor.

Corrective Action: Try again later.

CTB361E NO RULES FOUND IN THE LIBRARY. PLEASE ENTER RULE NAMELink copied to clipboard

Explanation: The library is empty. Control-M/Analyzer did not build the rule list as no rules were found in the library.

Corrective Action: Specify a new rule name.

CTB362E PLEASE FILL IN RULE NAMELink copied to clipboard

Explanation: No value was specified in the RULE field. The RULE field is obligatory.

Corrective Action: Specify the name of the rule member in the RULE field.

Messages CTB400 through CTB4xxLink copied to clipboard

This group includes messages for the Control-M/Analyzer product.

CTB401E INTERNAL PROGRAM ERROR - INVALID FUNCTIONLink copied to clipboard

Explanation: An internal error has occurred.

The requested function is not performed.

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

CTB402E INSUFFICIENT STORAGE FOR INVOCATION LISTLink copied to clipboard

Explanation: There is insufficient storage to perform the requested action.

Corrective Action: Either ask your INCONTROL administrator to call BMC Customer Support, or adjust the selection criteria so that fewer records are selected.

CTB403E INTERNAL PROGRAM ERROR IN ROUTINE CTBCKPLink copied to clipboard

Explanation: An internal error occurred.

The requested action is not performed.

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

CTB405E OPEN OF DDNAME `ddName` FAILED. RC= `rc`Link copied to clipboard

Explanation: Control-M/Analyzer was unable to open the file referenced by the ddName DD statement.

The requested action is not performed.

Corrective Action: Check that the ddName DD statement exists and refers to the correct file. Check the system log for messages which indicate the reason that the open failed. If you are unable to solve the problem, report the contents of the message to your INCONTROL administrator.

CTB406E DISPLAY TYPE " `type`" NOT FOUNDLink copied to clipboard

Explanation: The user specified a display type (type) which has not been defined. Valid display types are defined in the $$JBL member.

Corrective Action: Specify a valid display type.

CTB407E PLEASE SPECIFY A GROUP NAME, OR "*" FOR ALL GROUPSLink copied to clipboard

Explanation: A value was not specified in the GROUP field. GROUP is a required field.

Corrective Action: Specify a group name (or *: for all groups).

CTB408E REPORT NOT FOUND FOR THIS JOBLink copied to clipboard

Explanation: The report for this invocation cannot be located in the report file. The report file is not synchronized with the Active Balancing file.

The requested action is not performed.

Corrective Action: Notify your INCONTROL administrator.

CTB409E REPORT NOT CREATED FOR THIS JOBLink copied to clipboard

Explanation: No report was created for this invocation of Control-M/Analyzer. Either the report file is full, or an internal error occurred in the early stages of Control-M/Analyzer invocation.

The requested action is not performed.

Corrective Action: Notify your INCONTROL administrator.

CTB40AI NO VARIABLES WERE COMMITTED FOR THIS ENTRYLink copied to clipboard

Explanation: This information message indicates that the mission did not commit any variables.

Corrective Action: No action is required.

CTB40BE INVALID RETURN CODE FROM `modName` RC = `rc` FUNCTION `func`Link copied to clipboard

Explanation: An internal error occurred.

The requested action is not performed.

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

CTB40CI ROLLBACK COMPLETED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that rollback was performed successfully.

Corrective Action: No action is required.

CTB40DE ROLLBACK DENIED BY SECURITY EXITLink copied to clipboard

Explanation: This information message indicates that you are not authorized to roll back this invocation.

Corrective Action: If you think you should be authorized to roll back this invocation, contact your security administrator.

CTB40EI ALL COMMITTED VARIABLES HAVE BEEN OVERWRITTENLink copied to clipboard

Explanation: This information message indicates that all the variables that were committed by this invocation have been overwritten.

Corrective Action: No action is required.

CTB40FI PRINT REQUEST COMPLETED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the requested report has been sent to the spool or to a file.

Corrective Action: No action is required.

CTB410S SYSOUT ALLOCATION FAILED, RC= `rc`, ERROR= `error`Link copied to clipboard

Explanation: Control-M/Analyzer was unable to perform the dynamic allocation required to print your report.

Corrective Action: Refer to the IBM manual MVS Programming: Authorized Assembler Services Guide. If you still cannot solve the problem, ask your INCONTROL administrator to call BMC Customer Support.

CTB411S SYSOUT OPEN FAILEDLink copied to clipboard

Explanation: SYSOUT could not be opened for report printing.

Corrective Action: Notify your INCONTROL administrator.

CTB413E COP# MUST BE 3 DIGITS (001-255)Link copied to clipboard

Explanation: An invalid number of copies of the report was requested. The number of copies of a report must be a three digit number between 001 and 255.

Corrective Action: Correct the request and try again.

CTB414E SECOND PART OF DESTINATION AND WRITER NAME CANNOT BE MIXEDLink copied to clipboard

Explanation: A value was specified in both the WTR field and the second part of the destination field. Values for both cannot be used together; they are mutually exclusive.

Corrective Action: Specify either value, but not both values.

CTB415E YOU ARE NOT AUTHORIZED TO PERFORM THIS ACTIONLink copied to clipboard

Explanation: The security exit prevents you from performing the action you have requested.

Corrective Action: If you think you should be authorized to perform this action, contact your security administrator.

CTB416E DATASET NAME CANNOT BE BLANKLink copied to clipboard

Explanation: A data set name was not specified with the request to print a file. If you choose to print a file, you must specify a data set name.

Corrective Action: Specify the data set name if you want to print the file.

CTB417S FILE OPEN FAILEDLink copied to clipboard

Explanation: While processing the print request, Control-M/Analyzer was unable to open the specified file.

The requested action is not performed.

Corrective Action: Check that the data set is cataloged. Check the system log for error messages which may indicate a reason for the problem, and correct accordingly.

CTB418S UNABLE TO PRINT REPORTLink copied to clipboard

Explanation: This error occurs when there are no lines to be printed.

Corrective Action: Notify your INCONTROL administrator.

CTB419S INSUFFICIENT FREE SPACE IN THE OUTPUT FILELink copied to clipboard

Explanation: Control-M/Analyzer was unable to print the report because there was insufficient space in the output file.

Corrective Action: Enlarge the output file and try again.

CTB41AI THIS INVOCATION HAS ALREADY BEEN ROLLED BACKLink copied to clipboard

Explanation: This information message indicates that a roll back request was made for an invocation that has already been rolled back.

Corrective Action: No action is required.

CTB41BE REQUESTED FILE IS NOT CATALOGEDLink copied to clipboard

Explanation: Control-M/Analyzer was unable to open the specified file.

The requested operation is not performed.

Corrective Action: Make sure the data set is cataloged.

CTB41CE REQUESTED FILE IS NOT SEQUENTIALLink copied to clipboard

Explanation: The user specified a nonsequential file for the online print option. Control-M/Analyzer cannot print the balancing report into nonsequential file.

Corrective Action: Correct the DSN specified in the Print Option panel.

CTB484I POST DAILY CHECKPOINT WRITTENLink copied to clipboard

Explanation: This information message indicates that Post-daily checkpoint was written and that the New Day procedure ended normally.

Corrective Action: No action is required.

Messages CTB500 through CTB5xxLink copied to clipboard

This group includes messages for the Control-M/Analyzer product.

CTB501I CTBBAO STARTEDLink copied to clipboard

Explanation: This information message signals the normal start of the CTBBAO program. The Control-M/Analyzer Online Facility produces this message when it orders or forces a balancing mission to the Active Balancing file.

Corrective Action: No action is required.

CTB502S OPEN OF SCHEDULE DATA FAILED. DDNAME "DABAL"Link copied to clipboard

Explanation: Open of Control-M/Analyzer BALMIS library failed.

Failure is due to one of the following:

The DABAL DD statement is missing.
Either the data set pointed to by the DAJOB DD statement cannot be opened for sequential read, or its record length is not 80.

The CTBBAO program ends with errors.

Corrective Action: Consult your INCONTROL administrator.

CTB503S OPEN OF USER DATE CONTROL RECORD FAILED - DDNAME "DACHK"Link copied to clipboard

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

Possible causes are:

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

The CTMJOB program ends with errors.

Corrective Action: Correct the JCL for the job/CLIST.

CTB504S USER DATE CONTROL RECORD IS EMPTYLink copied to clipboard

Explanation: The data set described by the DACHK DD statement is empty.

The CTMJOB program ends with errors.

Corrective Action: Correct the JCL for the job/CLIST.

CTB505E VALID VALUES ARE "I" or "H"Link copied to clipboard

Explanation: An invalid value was specified for the GEN TYPE (generation type) field. Valid values for the GEN TYPE field are

I (Independent)
H (Hierarchical)

Corrective Action: Specify a valid value, or use the CANCEL command to exit without saving the database variable definition.

CTB505S PREVIOUS RUN OF CTBBAO DID NOT FINISH OKLink copied to clipboard

Explanation: A previous run of the CTBBAO program did not finish OK. This program is usually activated as part of the New Day procedure.

date-2 and date-3 (or date-4 and date-5) of the Date Control Record are not equal. Possible causes are:

The previous run of the CTBBAO program did not finish OK.
The contents of the User Date Control Record (DD statement DACHK) have been manually modified.

The CTBBAO program ends with errors.

Corrective Action: Set date-3 (or date-5), positions 25-30 (or 50-55) in the Date Control Record (the DACHK DD statement), to the values of date-2 (or date-4). To rerun the same New Day procedure, change all the dates to the value of the day before.

Do not order the same mission twice on the same day when rerunning the New Day procedure. First delete previously ordered missions from the Active Balancing file, and then rerun the New Day procedure.

CTB506S SCHEDULING FAILED FOR MEMBER `memName`Link copied to clipboard

Explanation: Scheduling failed for the memName member. This error message is issued by the CTMJOB program which is usually activated as part of the New Day procedure.

The IOA Log or the output of the job should contain an additional message concerning the reason for failure.

The job order of member is not placed in the Active Jobs file. Depending on the severity of the problem, the New Day procedure will continue to the next job order or terminate with a condition code of 08.

Corrective Action: Check the IOA Log or the job’s output for the reason.

CTB507S LAST MONTHLY SCHEDULING DATE GREATER THAN THE CURRENT ORIGINAL SCHEDULING DATELink copied to clipboard

Explanation: Invalid last monthly Scheduling Date.

The last monthly Scheduling Date (positions 18-23) in the User Date Control Record is greater than the current original Scheduling Date (positions 1-6). Possible causes are:

The previous run of the CTMJOB program did not finish OK.
Someone has modified the contents of the User Date Control Record (the DACHK DD statement).

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

The CTMJOB program ends with errors.

Corrective Action: Correct the User Date Control Record (the DACHK DD statement).

CTB508S LAST MONTHLY SCHEDULING DATE WAS MORE THAN 28 DAYS AGO, CHECK ITLink copied to clipboard

Explanation: The last monthly scheduling date is more than 28 days ago.

Possible causes are:

The User New Day procedure has not been used for more than 28 days. Correct the dates in the record to “yesterday.”
Someone has modified the contents of the General Date Control Record incorrectly.

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

Program execution stops with a condition code of 08.

Corrective Action: Correct the dates in the User Date Control Record (the DACHK DD statement).

CTB510S SEVERE ERROR IN THE BALANCING DATA. NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: A severe error was detected in the scheduling data. This message is issued by the New Day procedure. This message is produced when a scheduling mission (pointed to by the DABAL DD statement) contains erroneous data.

Possible causes are:

The contents of the mission were incorrectly modified using an editor or program, and the format of the mission is invalid.
Internal error in Control-M/Analyzer.

The New Day procedure terminates with a condition code of 08.

Corrective Action: Try to restore the mission to its original state. If you cannot, have your IOA administrator call BMC Customer Support for assistance. If the mission is a batch New Day procedure using a permanent Date Control Record, correct the contents of the Date Control record before running the New Day procedure again. For more information, see the BAO505S message.

CTB513E ONLY TRAILING BLANKS ALLOWED IN FIELDLink copied to clipboard

Explanation: The name specified in the field contains leading or embedded blanks. Only trailing blanks are valid in this field. The cursor points to the invalid value.

Corrective Action: Specify a valid value, or use the CANCEL command to exit without saving the database variable definition.

CTB513I SCHEDULE FAILED FOR `num` CONTROL-M/ANALYZER CATEGORIESLink copied to clipboard

Explanation: This information message displays the number of Control-M/Analyzer balancing missions categories that were not found in the library allocated to the DABAL DD statement.

In this message, num is the number of balancing missions categories that were not found.

The Control-M/Analyzer New Day procedure continues processing.

Corrective Action: Examine the IOA Log file for the failed categories and associated reasons for failure.

CTB514S INSUFFICIENT STORAGE FOR THE BALANCING MISSIONLink copied to clipboard

Explanation: There is insufficient storage for processing the mission order.

The CTBBAO program (of the New Day procedure) terminates with a condition code of 08.

Corrective Action: Increase the REGION size of the New Day procedure.

CTB515E FIELD MUST START WITH AN ALPHA CHARACTERLink copied to clipboard

Explanation: The value specified in the field does not start with an alphabetic character. The first character in the value must be alphabetic. The cursor points to the invalid value.

Corrective Action: Specify a valid value, or use the CANCEL command to exit without saving the database variable definition.

CTB515S ERROR IN SCHEDULING DATA - TOO MANY STATEMENTS FOR ONE MISSIONLink copied to clipboard

Explanation: The scheduling mission contains too many statements. Scheduling data describing the mission order is too large to be processed by Control-M/Analyzer.

The mission order is not placed on the Active Balancing file. The New Day procedure terminates with a condition code of 08.

Corrective Action: Check the contents of the mission order using the Online Scheduling Facility and omit unnecessary scheduling data. Report this to your INCONTROL administrator.

CTB516E FIELD MUST CONTAIN ONLY ALPHANUMERIC CHARACTERSLink copied to clipboard

Explanation: The value specified in the field contains non-alphanumeric characters. Only alphanumeric characters are valid in this field. The cursor points to the invalid value.

Corrective Action: Specify a valid value, or use the CANCEL command to exit without saving the database variable definition.

CTB516S ERROR IN SCHEDULING DATA - FIRST STATEMENTS SHOULD START WITH "B"Link copied to clipboard

Explanation: Invalid scheduling data was detected in the first data set pointed to by the DABAL DD statement. The first statement of a valid balancing mission should start with B.

The error could be due to one of the following:

The data set pointed to by the DABAL DD statement is not a Balancing Mission.
The Balancing Mission has been manually modified incorrectly.

The CTBBAO program ends with errors.

Corrective Action: Check that the DABAL DD statement refers to a valid Balancing Mission definition.

CTB517E MAXIMUM NUMBER OF GENERATIONS MUST BE BETWEEN 1 AND 1000Link copied to clipboard

Explanation: An invalid number of generations was specified. Values for the MAXIMUM ACTIVE GENERATIONS field must be from 1 through 1000.

Corrective Action: Specify a valid value, or use the CANCEL command to exit without saving the database variable definition.

CTB517S SCHEDULING DATA NOT AVAILABLELink copied to clipboard

Explanation: The DD statement pointing to the job scheduling tables is empty or missing.

The program ends with errors.

Corrective Action: Correct the JCL for the job or CLIST.

CTB518S INVALID YEAR IN USER DATE CONTROL RECORDLink copied to clipboard

Explanation: Invalid year in the User Date Control record used by the New Day procedure.

This year is not supported by the release of Control-M you are using.

The CTMJOB program ends with errors.

Corrective Action: Correct the YEAR field (the DACHK DD statement).

CTB519S INVALID PREVIOUS WEEKLY SCHEDULING DATE IN USER DATE CONTROL RECORD (POSITIONS 43-48)Link copied to clipboard

Explanation: Invalid previous weekly Scheduling Date in the User Date Control record (positions 43-48). This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure.

This date (date-4 of User Date Control record) might not be equal to date-5 (positions 50-55) or in invalid format. Valid format is ddmmyy or mmddyy. Possible causes are:

The previous run of the CTMJOB program did not finish OK.
Someone has incorrectly modified the contents of the User Date Control Record (the DACHK DD statement).

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

The New Day procedure will end with errors.

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

CTB520E NAME MUST BE SPECIFIEDLink copied to clipboard

Explanation: No name was specified for the variable. The NAME field is mandatory in the Variable Definition screen.

Corrective Action: Specify a valid name, or use the CANCEL command to exit without saving the database variable definition.

CTB521E UPDATE OF VARIABLE DEFINITION FAILEDLink copied to clipboard

Explanation: An error occurred while attempting to update a variable in the database Variable Definition screen. The database variable definition is not updated.

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

CTB522E INTERNAL ERROR IN CTBDBV#Link copied to clipboard

Explanation: An error occurred while attempting to update or create a variable in the database Variable Definition screen.

The database variable definition is not updated.

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

CTB522S INVALID ORIGINAL SCHEDULING DATE IN USER DATE CONTROL RECORD (POSITIONS 1-6)Link copied to clipboard

Explanation: Invalid original scheduling date in the User Date Control Record (positions 1-6). This error message is issued by the CTMJOB program which is usually activated as part of the New Day procedure.

Valid format is ddmmyy or mmddyy. The message may be due to one of the following:

The previous run of the CTMJOB program did not finish OK.
Someone has incorrectly modified the contents of the User Date Control Record (the DACHK DD statement).

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

The New Day procedure will end with errors.

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

CTB523E PLEASE FILL IN A SPECIFIC GROUP NAME, OR OMIT THE VARIABLE NAMELink copied to clipboard

Explanation: A database variable name was specified in the database Entry Panel, but a specific group name was not specified.

There are four possible system actions:

If the VARIABLE field is filled in on the database Entry Panel, and the GROUP field is blank or contains a prefix value, the database Variable Definition screen is displayed.
If the GROUP and VARIABLE fields in the Entry Panel are both blank, the Group List is displayed.
If a prefix is specified in the GROUP field, and the VARIABLE field is blank, an abbreviated Group List, listing only groups matching the prefix, is displayed.
If a specific group name is specified, and the VARIABLE field is blank, the database Variable List is displayed.

Corrective Action: Specify a group name or delete the database variable name.

CTB523S INVALID PREVIOUS MONTHLY SCHEDULING DATE IN USER DATE CONTROL RECORD (POSITIONS 18-23)Link copied to clipboard

Explanation: Invalid previous monthly scheduling date in the User Date Control Record (positions 18-23). This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure.

This date (date-2 of User Date Control Record) should be equal to date-3 (positions 24-29) or in valid format. The valid format is ddmmyy or mmddyy.

Possible causes are:

The previous run of the CTMJOB program did not finish OK.
Someone has incorrectly modified the contents of the User Date Control Record (the DACHK DD statement).

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

The CTMJOB program ends with errors.

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

CTB524E OPERATION FAILED. ERROR DURING FILE ACCESS RC= `rc`, FUNCTION= `func`Link copied to clipboard

Explanation: An error occurred during an attempt to open or read the Control-M/Analyzer database. The error occurred during online processing from a screen under Main Menu option BV (database Variables).

No information is retrieved. The screen is exited.

Corrective Action: Ask your INCONTROL administrator to notify BMC Customer Support of the error message, return code and function.

CTB524S CTBBAO ENDED WITH ERRORSLink copied to clipboard

Explanation: The CTBBAO program ended with errors. It is activated as part of the New Day procedure.

The New Day procedure finishes executing with a condition code of 08. The IOA Log File contains one or more prior messages concerning the errors.

Corrective Action: Examine the IOA Log File for the errors. If necessary, correct the Date Control Record (date-3 and date-5) manually for the next run of the New Day procedure.

CTB525E VARIABLE ALREADY EXISTS. IT CANNOT BE CREATED.Link copied to clipboard

Explanation: An attempt was made to create a variable, but a variable with the same name already exists in the group. The variable cannot be created because it already exists. It cannot be saved because it was specified using the Insert command.

The Exit Option Window is closed. The database Variable Definition screen remains displayed.

Corrective Action: Either specify a database variable name that does not currently exist in the group, or use the CANCEL command to exit without saving the database variable definition.

CTB525I CTBBAO ENDEDLink copied to clipboard

Explanation: This information message indicates that the CTBBAO terminating program, which is activated as part of the New Day procedure, has terminated.

Corrective Action: No action is required.

CTB526E SAVE CAN ONLY BE PERFORMED FOR ALREADY-EXISTING VARIABLESLink copied to clipboard

Explanation: A request was made to save a database variable which was not yet created in the group. After inserting a variable in a group and exiting, the Exit Option Window is displayed. The SAVE option in the window is valid only for existing database variables. The CREATE option must be used to create new database variables.

Corrective Action: Either specify option CREATE to create the database variable, or press the RESET key (PF04) to close the window without saving the database variable.

CTB527E ONE (AND ONLY ONE) EXIT OPTION MUST BE MARKED AS "Y" OR "N"Link copied to clipboard

Explanation: More than one option was specified in the Exit Option Window. When exiting the database Variable Definition screen, the Exit Option Window is opened. It contains two options: SAVE and CREATE. A value can be specified for only one of the exit options. Valid values are Y (Yes) or N (No).

Corrective Action: Specify Y or N for either SAVE or CREATE (but not both), or press the RESET key (PF04) to close the window without saving the database variable.

CTB528E VALID VALUES ARE "N" OR "Y"Link copied to clipboard

Explanation: An invalid value was specified in the CREATE or UPDATE field in the Group Window.

Valid values for CREATE or UPDATE in the Group Window are

Y (Yes - create or update the group)
N (No - do not create or update the group).

Corrective Action: Specify Y or N in the CREATE or UPDATE field.

CTB529E SPECIFIED GROUP NAME IS INVALID OR MISSINGLink copied to clipboard

Explanation: An invalid value was specified in the GROUP field in the New Group Window. When inserting a new group in the Group List, the GROUP field in the New Group Window must contain an alphanumeric value with no leading blanks.

Corrective Action: Specify a valid name in the GROUP field.

CTB529S LAST WEEKLY SCHEDULING DATE GREATER THAN THE CURRENT ORIGINAL SCHEDULING DATELink copied to clipboard

Explanation: The last weekly scheduling date in the Date Control Record is greater than the current original scheduling date.

This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure. Date-4 (positions 43-48) should not be greater than date-1 (positions 1-6) in the Date Control Record. The message may be due to one of the following:

The previous run of the CTMJOB program did not finish OK.
Someone modified the contents of the User Date Control Record (the DACHK DD statement).

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

Program execution stops with a condition code of 08.

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

CTB530E SPECIFIED GROUP NAME ALREADY EXISTSLink copied to clipboard

Explanation: A group with the name specified in the New Group Window already exists. Group names must be unique. When inserting a new group, the name of an existing group cannot be specified in the GROUP field of the New Group Window.

Corrective Action: Specify a unique group name, or cancel the create request by specifying N (No) in the CREATE field of the window.

CTB530S LAST WEEKLY SCHEDULING DATE WAS MORE THAN 28 DAYS AGO, CHECK ITLink copied to clipboard

Explanation: The last weekly scheduling date is more than 28 days ago.

Possible causes are:

The User New Day procedure has not been used for more than 28 days. Correct the dates in the record to yesterday.
Someone has modified the contents of the General Date Control Record incorrectly.

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

Program execution stops with a condition code of 08.

Corrective Action: Correct the dates in the Date Control Record (the DACHK DD statement) and rerun.

CTB531E INVALID OR MISSING GROUP MODELink copied to clipboard

Explanation: An invalid value was specified in the GROUP MODE field in the Group Window.

Valid values for the GROUP MODE field in the Group Window are:

D (Define)
A (Active)
S (Simulate)

Corrective Action: Specify a valid GROUP MODE value.

CTB532I ADD/UPDATE COMPLETED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that a group was successfully updated or added to the database Group List.

Corrective Action: No action is required.

CTB532S OPEN OF CONTROL-M/ANALYZER ACTIVE BALANCING FILE FAILED. DDNAME "DAABF"Link copied to clipboard

Explanation: Open of Control-M/Analyzer Active Balancing file failed. This error message is issued by the CTBBAO program, which is usually activated as part of the New Day procedure.

Possible causes are:

the DAABF DD statement is missing.
The data set pointed to by the DAABF DD statement is not the Control-M/Analyzer Active Balancing file.
The data set pointed to by the DAABF DD statement is a Control-M/Analyzer Active Balancing file, from a different version of Control-M/Analyzer.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the mission/ CLIST and rerun it.

CTB533E NO VARIABLES IN GROUP. ONLY "INSERT" IS VALIDLink copied to clipboard

Explanation: An option other than Insert was requested in an empty Group. If the Variables List for a group contains no variables, Insert is the only operation permitted. Insert is the first operation which should be performed in a new group, in order to insert the first variable and to add it to the list of variables.

Corrective Action: Either request option Insert, or exit the database Variable List screen.

CTB534E PLEASE FILL IN A DESCRIPTIONLink copied to clipboard

Explanation: The DESCRIPTION field in the New Group Window is empty. The DESCRIPTION field is mandatory when creating a new group.

Corrective Action: Fill in the DESCRIPTION field.

CTB534S SEVERE ERROR ON CONTROL-M/ANALYZER ACTIVE BALANCING FILE. NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: Severe error on Control-M/Analyzer Active Balancing file. This error message is issued by the CTBBAO program, which is usually activated as part of the New Day procedure.

Possible causes are:

An I/O error.
The file allocated to the DAABF DD statement is not the Control-M/Analyzer Active Balancing file.
The Active Balancing file has been corrupted.

The CTBBAO Control-M/Analyzer program ends with errors.

Corrective Action: Ask your IOA administrator to check whether the Active Balancing File has been updated from two computers without global ENQ control, or by an unauthorized program.

CTB535I NO CHANGES PERFORMEDLink copied to clipboard

Explanation: This information message is issued when the database Variable Definition screen is exited without saving changes (for example, by specifying CANCEL, or by specifying N (No) in the SAVE or CREATE field in the Exit Option Window).

Corrective Action: No action is required.

CTB536E GROUP NAME DOES NOT EXIST IN THE DATABASELink copied to clipboard

Explanation: The name of the group specified in the database Entry Panel does not exist. Only names of existing groups can be specified in the Entry Panel. To define a new group, use the Insert option in the Group List.

Corrective Action: Either specify an existing group name, or clear the GROUP field and define the new group in the Group List.

CTB536S SEVERE ERROR IN SCHEDULING DATA CARDSLink copied to clipboard

Explanation: Severe error was found in the scheduling data statements. This error message is issued by the CTMJOB program which is usually activated as part of the New Day procedure.

Scheduling fails for the job order. The CTMJOB program terminates with a condition code of 08.

Corrective Action: Look for additional messages concerning the error, correct the error and rerun.

CTB537I NO VARIABLES MATCH THE SPECIFIED PREFIXLink copied to clipboard

Explanation: This information message indicates that a prefix was specified in the VARIABLE field in the database Entry Panel, but no matches were found in the specified group. A prefix specified in the VARIABLE field must match at least one existing database variable.

The database Variable Definition screen can be accessed directly from the database Entry Panel by specifying an existing group and an existing variable prefix. If only a group name is specified, the database Variable List for the group is displayed.

Corrective Action: Specify the prefix of an existing variable to display the database Variable Definition screen, or clear the VARIABLE field to display the database Variable List for the group.

CTB537S NO MORE INTERNAL WORK AREA. SEE MESSAGES AND CODES FOR REQUIRED ACTIONLink copied to clipboard

Explanation: Internal work areas of the New Day procedure have been exhausted.

The job order contains more data than can be handled by the current release of Control-M.

The New Day procedure terminates with a condition code of 08.

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

CTB538I NO GROUPS MATCH THE SPECIFIED PREFIXLink copied to clipboard

Explanation: This information message indicates that a prefix was specified in the GROUP field in the database Entry Panel but no matches were found in the database. A prefix specified in the GROUP field must match at least one existing group. The matching Group List is then displayed.

If the GROUP and VARIABLE fields are both blank in the Entry Panel, the entire Group List is displayed.

Corrective Action: Specify the prefix of an existing group to display an abbreviated Group List, or clear the GROUP field to display the entire Group List.

CTB538S LOADING OF CONTROL-M/ANALYZER INSTALLATION PARAMETERS FAILEDLink copied to clipboard

Explanation: Loading of Control-M/Analyzer Installation Parameters, which are in the CTBPARM member in the IOA PARM library, failed.

Possible causes are:

There is insufficient memory to load the IOA Installation Parameters.
The CTBPARM member does not exist in the IOA PARM library.
The IOA PARM library was updated while you were working and the position of the CTBPARM member has changed.

The requested function is terminated.

Corrective Action: Look in the system log for additional related messages. Try one of the following:

If loading failed because of lack of memory: increase the REGION size for batch missions; for TSO, try to log on again using a larger SIZE parameter.
If you are using many IOA screens concurrently, try to exit a few using the END command. This releases memory used by the screens.
If the PARM 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.

CTB539S ERROR IN CONTROL-M/ANALYZER INSTALLATION PARAMETERS - INVALID DATETYPLink copied to clipboard

Explanation: Invalid DATETYP Control-M/Analyzer Installation Parameter. The DATETYP parameter specifies the date format used at installation.

Valid values are:

For more details, see the section on operational parameters in the IOA installation chapter in the INCONTROL for z/OS Installation Guide.

The requested function is terminated.

Corrective Action: Contact your INCONTROL administrator. Set the DATETYP parameter in the IOAPARM member to a valid value.

CTB540E VIEW OPTION FAILEDLink copied to clipboard

Explanation: An attempt to view generations of database variables failed. Option V (View) was specified in the Variables List Panel to display all active generations of the selected specific database variable.

The View operation is not performed.

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

CTB540S CONTROL-M/ANALYZER ACTIVE BALANCING FILE IS FULL. NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation:Highlighted, unrollable message.

Control-M/Analyzer Active Balancing file is full. There is no more space in the Active Balancing file for new missions.

The mission order is not placed in the Active Balancing file.

Corrective Action: Contact your IOA administrator immediately. It may be necessary to increase it size. Compress the Active Balancing files.

CTB540W LOAD OF SECURITY MODULE `modName` FAILED. SECURITY CHECKING WILL BE BYPASSEDLink copied to clipboard

Explanation: Loading of the specified IOA security module failed. Possible causes are:

The installation is not using the specified user security module, and has erased the default IOA-supplied module.
IOA Load library is not in the JOBs load modules search list (STEPLIB + Linklist).
Insufficient memory.
Another system oriented reason which can be found in the syslog.

As a result, no security checking is performed. For more details, refer to the sections on Security Interface Modules in the appropriate security guides.

Corrective Action: Notify the INCONTROL administrator. This is a potentially serious situation. Someone may be attempting to violate security.

CTB541E DATABASE EMPTY. ONLY "INSERT" MAY BE SPECIFIEDLink copied to clipboard

Explanation: An operation other than Insert was attempted although there are no groups in the database.

When the database is empty and there are no existing groups, the only operation permitted is Insert. Insert is the first operation that must be performed in the Group List. After the first group is created, Select and Update operations are also permitted.

Corrective Action: Specify an Insert operation, or exit the Group List screen.

CTB542E INSUFFICIENT SPACE IN THE VARIABLES FILELink copied to clipboard

Explanation: An attempt was made to Insert a new variable, but there is not enough space in the database. No new variables can be defined until sufficient space is provided.

The new variable is not created.

Corrective Action: It may be possible to create the variable by requesting fewer generations. In any case, more free file space should be provided. Use the CTBDBVCP utility to copy the file to a new enlarged file, or use the CTBDBVDL utility to compress the file. For more information, see the INCONTROL for z/OS Utilities Guide.

CTB543E INSUFFICIENT SPACE IN THE MODELS FILELink copied to clipboard

Explanation: An attempt was made to Insert a new variable, but there is insufficient space in the database Variable Basic file. The file is full or nearly full. No new variables can be defined until sufficient space is provided.

The new variable is not created.

Corrective Action: You must provide more file space. Use the CTBDBVCP utility to copy the file to a new enlarged file, or use the CTBDBVDL utility to compress the file. For more information, see the INCONTROL for z/OS Utilities Guide.

CTB544E INSUFFICIENT SPACE IN THE INDEX FILELink copied to clipboard

Explanation: An attempt was made to Insert a new variable, but there is insufficient space in the database Variable Basic Index file. The file is full or nearly full. No new variables can be defined until sufficient space is provided.

The new variable is not created.

Corrective Action: Use the CTBDBVCP utility to copy the file to a new enlarged file, or use the CTBDBVDL utility to compress the file. For more information, see the INCONTROL for z/OS Utilities Guide.

CTB545E NO AUTHORIZATION FOR PERFORMING THIS OPERATIONLink copied to clipboard

Explanation: The user is unauthorized to perform the requested Insert or Update on the variable.

The new variable is not created or updated.

Corrective Action: If you think you should be authorized to perform the attempted operation, contact your INCONTROL administrator.

CTB546E GRAPH OPTION FAILEDLink copied to clipboard

Explanation: The user attempted to view a graph of a specific variable, but the variable was empty, and as a result, the graph option failed. A variable must have a value to be viewed as a graph.

Corrective Action: Verify that the variable specified has a value.

Messages CTB600 through CTB6xxLink copied to clipboard

This group includes messages for the Control-M/Analyzer product.

CTB601S ERROR READING ACTIVE BALANCING FILE REASON `rc`Link copied to clipboard

Explanation: An error occurred while trying to read status information in the Active Balancing file.

The Active Balancing Environment screen is not built. The IOA Primary Option Menu is displayed.

Corrective Action: If the reason code is 0012, more storage is required. Exit from screens which are not in use and increase the REGION size if necessary. For other reason codes, ask your INCONTROL administrator to notify BMC Customer Support of the problem and the reason code.

CTB602S UNABLE TO OPEN ACTIVE BALANCING FILELink copied to clipboard

Explanation: An error occurred while trying to open the Active Balancing file. Status information about balancing missions resides in the Active Balancing file.

The Active Balancing Environment screen is not built. The IOA Primary Option Menu is displayed.

Corrective Action: Make sure that the DAABF DD statement references the Active Balancing file. If the name was correct when the error occurred, ask your INCONTROL administrator to contact BMC Customer Support.

CTB603E OPTION CANNOT BE PERFORMED. INTERNAL ERRORLink copied to clipboard

Explanation: An internal error occurred when trying to perform a line command on one of the balancing mission entries.

The requested line command is not performed.

Corrective Action: Ask your INCONTROL administrator to notify BMC Customer Support.

CTB604E UNABLE TO LOAD CTBTLOGLink copied to clipboard

Explanation: The CTBTLOG load module cannot be found.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Check the concatenated load libraries referenced by the DDNAME STEPLIB statement and rerun the Control-M/Analyzer job.

CTB605E LOG COMMAND FAILED. RC= `rc`Link copied to clipboard

Explanation: The L (Log) line command could not be performed.

The requested line command is not performed.

Corrective Action: Ask your INCONTROL administrator to notify BMC Customer Support of the problem and the return code.

CTB606E ENTRY IS IN USE. PLEASE TRY `opt` OPTION AGAIN IN A FEW MOMENTSLink copied to clipboard

Explanation: An attempt was made to HOLD, DELETE, or FREE a balancing mission that was in use. The balancing mission was being held to be updated by either another user, or by the Control-M/Analyzer Runtime Environment.

The requested status change of the balancing mission is not performed.

Corrective Action: Wait a few moments for the balancing mission to become free, and try again.

CTB607E CANNOT PERFORM `opt` DUE TO STORAGE ALLOCATION FAILURELink copied to clipboard

Explanation: Available storage is not sufficient to perform the opt HOLD, FREE or DELETE option on the balancing mission.

The requested status change of the balancing mission is not performed.

Corrective Action: Exit any screens which are not in use, and increase the REGION size if necessary.

CTB608I ENQ PROBLEM ON THE ACTIVE BALANCING FILELink copied to clipboard

Explanation: This information message indicates that an attempt to free a balancing mission failed during performance of a line command when an ENQ was made to the balancing mission.

Corrective Action: Solve the immediate ENQ/FREE problem by exiting Control-M/Analyzer entirely, and then reentering. Ask your INCONTROL administrator to notify BMC Customer Support of the problem.

CTB609E AN ENTRY MAY NOT BE DELETED DURING "BALANCING"Link copied to clipboard

Explanation: A D (Delete) line command was specified for a balancing mission while the mission was balancing. A mission cannot be deleted during balancing.

The requested delete is not performed.

Corrective Action: When the mission is not balancing, place the mission in HELD status, and then delete it.

CTB60AE INTERNAL ERROR ACTIVATING "WHY" OPTIONLink copied to clipboard

Explanation: An error occurred while performing the requested ? (Why) line command.

The? (Why) line command is not performed.

Corrective Action: Ask your INCONTROL administrator to notify BMC Customer Support.

CTB60BE ACTIVE BALANCING FILE IS BEING FORMATTEDLink copied to clipboard

Explanation: The Active Balancing file cannot be read because it is being formatted. Status information about balancing missions resides in the Active Balancing file. When this file is being formatted, status information cannot be retrieved.

An empty Balancing Status screen is displayed.

Corrective Action: Every few moments press Enter until a non-empty Balancing Status screen is displayed.

CTB665E INPUT PARAMETER (ADDRESS SPACE NAME) ERROR DETECTEDLink copied to clipboard

Explanation: The PARM parameter is missing or is too large. The PARM input parameter is not present in the invocation JCL, or is too large.

The CTOCTA utility terminates.

Corrective Action: Add or correct the input parameter and rerun the job.

CTB666I PROGRAM `pgm` FOUND IN THE RB CHAINLink copied to clipboard

Explanation: This information message indicates that the CTOCTA utility found the address space running the pgm program.

The CTOCTA utility found at least one task in the address space running the pgm program.

Corrective Action: No action is required.

CTB667I SVC `svcno` (TYPE 2 NUCLEUS SVC) FOUND IN AN SVRBLink copied to clipboard

Explanation: This information message indicates that the CTOCTA utility found the address space running the svcno SVC.

Corrective Action: No action is required.

Messages CTB700 through CTB7xxLink copied to clipboard

This group includes messages for the Control-M/Analyzer product.

CTB701E PLEASE SPECIFY MISSION NAME, OR OMIT CATEGORYLink copied to clipboard

Explanation: A category was specified, but a mission name is missing. A category can only be defined for a specified mission.

Corrective Action: Either fill in a mission name, or omit the category to get a list of missions in the library.

CTB718E NO MISSIONS FOUND IN THE LIBRARY. PLEASE ENTER THE MISSION NAMELink copied to clipboard

Explanation: The library is empty. Control-M/Analyzer did not build the missions list because no missions were found in the library.

Corrective Action: Specify a new mission name.

CTB720E INVALID OPTION. USE "SINGLE", "STEP" OR "JOB"Link copied to clipboard

Explanation: An invalid option was specified in the SCOPE field.

Valid options are:

SINGLE
STEP
JOB
ALL

Corrective Action: Specify a valid option.

Messages CTB800 through CTB8xxLink copied to clipboard

This group includes messages for the Control-M/Analyzer product.

CTB800E PLEASE SPECIFY JOBNAMELink copied to clipboard

Explanation: The JOBNAME field has not been filled in. The JOBNAME field is mandatory.

Corrective Action: Fill in the JOBNAME field.

CTB801E OPTION " `opt`" NOT ALLOWED IN THIS MODELink copied to clipboard

Explanation: The opt option is not valid. This message is usually issued during an attempt to update or delete a generation when viewing the variables related to a rule invocation. When the Variables screen is used under the Job Activity screen, it can only be used in browse mode.

Corrective Action: Specify another option.

CTB802E CANNOT PERFORM AN INSERT ON AN INSERTED LINELink copied to clipboard

Explanation: An attempt was made to insert a new record before entering the required information for the current record. Until all the required information has been entered for the current record, a new record cannot be inserted.

Corrective Action: Fill in the required fields in the inserted record before attempting to insert a new record.

CTB803E FORMAT MUST INCLUDE THE "GROUP" FIELDLink copied to clipboard

Explanation: When defining the display type, the GROUP field was not included. GROUP is a mandatory field in all display type formats.

Corrective Action: Ask your INCONTROL administrator to correct the display type in the $$DBV member.

CTB804E THIS "GROUP" AND "VARIABLE" CANNOT BE INSERTEDLink copied to clipboard

Explanation: Due to an internal error, there is a problem with the GROUP and VARIABLE fields.

Corrective Action: Have your system programmer to call your INCONTROL administrator.

CTB805E FORMAT MUST INCLUDE THE "VARIABLE" FIELDLink copied to clipboard

Explanation: When defining the display type, the VARIABLE field was not included. VARIABLE is a mandatory field in all display type formats.

Corrective Action: Ask your INCONTROL administrator to correct the display type in the $$DBV member.

CTB806E GROUP NAME AND/OR VARIABLE NAME CANNOT BE UPDATEDLink copied to clipboard

Explanation: An attempt was made to update the GROUP or VARIABLE (or both) fields. These fields cannot be updated.

The update is not performed.

Corrective Action: No action is required.

CTB807E A DELETED GENERATION CANNOT BE UPDATEDLink copied to clipboard

Explanation: An attempt was made to update a deleted generation.

The requested action is not performed.

Corrective Action: No action is required.

CTB808E FILE ERROR `rc` IN ACTION actionLink copied to clipboard

Explanation: An error occurred while the Control-M/Analyzer database was being accessed.

Corrective Action: Notify your INCONTROL administrator.

CTB809E GENERATION ALREADY DELETEDLink copied to clipboard

Explanation: An attempt was made to delete a generation that is already marked deleted. A deleted generation cannot be deleted again.

The requested action is not performed.

Corrective Action: No action is required.

CTB810I GENERATION DELETEDLink copied to clipboard

Explanation: This information message indicates that the specified generation was deleted.

Corrective Action: No action is required.

CTB811I CREATION DATE/TIME OF RECORD HAS CHANGEDLink copied to clipboard

Explanation: This information message indicates that generation information in the file has been updated since your screen was last refreshed. Since your request was based on outdated information on the screen, Control-M/Analyzer did not perform your request.

The requested action is not performed.

Corrective Action: Refresh the screen. If you still want to perform the action, specify it again.

CTB812E CREATION DATE/TIME OF GENERATION 0 HAS CHANGEDLink copied to clipboard

Explanation: A new generation was created by another user since your screen was last refreshed. Since your insert request is based on an older generation, Control-M/Analyzer does not perform your insert request.

The requested insert is not performed.

Corrective Action: Refresh the screen. If you still want to perform the insert, specify it again.

CTB813E UNABLE TO OBTAIN ENQ ON VARIABLE. TRY AGAIN LATERLink copied to clipboard

Explanation: The database variable is temporarily locked while in use by another user. The locking mechanism prevents database corruption.

The requested action is not performed.

Corrective Action: Wait a short while and then try again.

CTB814E INSERT IS NOT ALLOWED IN THIS MODELink copied to clipboard

Explanation: Insert is only allowed under option BV. This message is most commonly issued when a user tries to insert a generation when viewing the variables related to a rule invocation. The Variables screen, when used under the Job Activity screen, can only be used in browse mode.

The requested insert is not performed.

Corrective Action: No action is required.

Messages CTB900 through CTB9xxLink copied to clipboard

This group includes messages for the Control-M/Analyzer product.

CTB902E INVALID OPTION (TRY "Y", "N" OR BLANK)Link copied to clipboard

Explanation: The user specified an invalid value in a field which may only contain Y (Yes), N (No) or blank.

Corrective Action: Correct the input field and press enter.

CTB912S ERROR IN CONTROL- `x` INSTALLATION PARAMETERS - INVALID DAYTIMELink copied to clipboard

Explanation: The format of the DAYTIME Control- x Installation parameter is invalid. DAYTIME is the start time of the Control-M 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.

CTB913S OPEN OF DDNAME "SYSPRINT" FAILEDLink copied to clipboard

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.

CTB971I CONTROL-M/ANALYZER UTILITY CTBJAFIG STARTEDLink copied to clipboard

Explanation: This information message indicates the normal start of the CTBJAFIG Control-M/Analyzer utility.

Corrective Action: No action is required.

CTB971S ERROR OPENING SYSPRINTLink copied to clipboard

Explanation: This information message indicates that the CTBDBIV Control-M/Analyzer utility failed to open the print file referenced by the SYSPRINT DD statement.

Possible causes are:

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

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

CTB972I CHECKING OF THE JOB ACTIVITY FILE IN PROGRESSLink copied to clipboard

Explanation: This information message indicates that CTBJAFIG Control-M/Analyzer utility has begun checking the Control-M/Analyzer Rule Activity File.

Corrective Action: No action is required.

CTB973I CHECKING OF THE REPORT FILE IN PROGRESSLink copied to clipboard

Explanation: The CTBJAFIG Control-M/Analyzer utility has begun checking the Control-M/Analyzer report file.

Corrective Action: No action is required.

CTB974I LOGICAL RELATION BETWEEN THE JOB ACTIVITY AND THE REPORT FILES NOW BEING CHECKEDLink copied to clipboard

Explanation: This information message indicates that the CTBJAFIG Control-M/Analyzer utility has begun checking the logical relation between the Job Activity and report files.

Corrective Action: No action is required.

CTB975E INVALID INPUT PARAMETERLink copied to clipboard

Explanation: The CTBJAFIG Control-M/Analyzer utility failed to analyze the FILE= name job input statement.

The utility stops executing with a condition code of 12.

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

CTB976S ERROR OPENING SYSPRINTLink copied to clipboard

Explanation: The CTBJAFIG Control-M/Analyzer utility failed to open the print file referenced by the SYSPRINT DD statement.

Possible causes are:

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

The utility stops executing with a condition code of 16.

Corrective Action: Correct the JCL and rerun the job.

CTB977S ERROR OPENING THE JOB ACTIVITY FILELink copied to clipboard

Explanation: The CTBJAFIG Control-M/Analyzer utility failed to open the Job Activity Data file referenced by the DAJAF DD statement.

Possible causes are:

The DAJAF DD statement is missing.
The data set referenced by the DAJAF DD statement is not the Control-M/Analyzer Job Activity Data file.
An internal error occurred while the Control-M/Analyzer Job Activity Data file was being opened.

The utility stops executing with a condition code of 16.

Corrective Action: Correct the JCL and rerun the job. If an error occurred while opening the file, notify your INCONTROL administrator.

CTB978S ERROR OPENING THE REPORT FILELink copied to clipboard

Explanation: The CTBJAFIG Control-M/Analyzer utility failed to open the report Data file referenced by the DAREP DD statement.

Possible causes are:

The DAREP DD statement is missing.
The data set referenced by the DAREP DD statement is not the Control-M/Analyzer Report Data file.
An internal error occurred while the Control-M/Analyzer Report Data file was being opened.

The utility stops executing with a condition code of 16.

Corrective Action: Correct the JCL and rerun the job. If an error occurred while opening the file, notify your INCONTROL administrator.

CTB979S INSUFFICIENT STORAGE FOR PROCESSING THE REPORT FILELink copied to clipboard

Explanation: The CTBJAFIG Control-M/Analyzer utility requires more storage to check the Control-M/Analyzer Report Data file.

The utility stops executing with a condition code of 08.

Corrective Action: Increase the REGION size and rerun the job.

CTB97AS INSUFFICIENT STORAGE FOR PROCESSING THE JOB ACTIVITY FILELink copied to clipboard

Explanation: The CTBJAFIG Control-M/Analyzer utility requires more storage to check the Control-M/Analyzer Job Activity Data file.

The utility stops executing with a condition code of 08.

Corrective Action: Increase the REGION size and rerun the job.

CTB97BS INSUFFICIENT STORAGE FOR COMPARING THE JOB ACTIVITY AND REPORT FILESLink copied to clipboard

Explanation: The CTBJAFIG Control-M/Analyzer utility requires more storage to check the logical relation between the Control-M/Analyzer Job Activity and Report Data files.

The utility stops executing with a condition code of 08.

Corrective Action: Increase the REGION size and rerun the job.

CTB97CS CORRECTION OF THE JOB ACTIVITY FILE FAILEDLink copied to clipboard

Explanation: The CTBJAFIG Control-M/Analyzer utility failed to correct errors detected in the Control-M/Analyzer Job Activity Data file.

The utility stops executing with a nonzero condition code.

Corrective Action: Notify your INCONTROL administrator.

CTB97DS CORRECTION OF THE REPORT FILE FAILED

Explanation: The CTBJAFIG Control-M/Analyzer utility failed to correct errors detected in the Control-M/Analyzer Report Data file.

The utility stops executing with a nonzero condition code.

Corrective Action: Notify your INCONTROL administrator.

CTB97ES CORRECTION OF THE LOGICAL RELATION BETWEEN THE JOB ACTIVITY AND REPORT FILES FAILEDLink copied to clipboard

Explanation: The CTBJAFIG Control-M/Analyzer utility failed to correct errors detected in the logical relation between the Job Activity and Report Data files.

The utility stops executing with a nonzero condition code.

Corrective Action: Notify your INCONTROL administrator.

CTB97FS INVALID RECORD TYPE IN THE JOB ACTIVITY FILELink copied to clipboard

Explanation: The CTBJAFIG Control-M/Analyzer utility detected an error in the Job Activity Data file. This message is followed by the CTB98FI message which displays the address of the invalid record.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB980S INCORRECT NUMBER OF RECORDS IN THE JOB ACTIVITY FILELink copied to clipboard

Explanation: The CTBJAFIG Control-M/Analyzer utility detected an error in the Job Activity Data file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB981S INCORRECT NUMBER OF FREE RECORDS IN THE JOB ACTIVITY FILELink copied to clipboard

Explanation: The CTBJAFIG Control-M/Analyzer utility detected an error in the Job Activity Data file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB982S ERROR IN INFO RECORD:Link copied to clipboard

Explanation: The CTBJAFIG Control-M/Analyzer utility detected an error in a record in the Job Activity Data file. This message is followed by other messages which display information about the record in error.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB983S ERROR IN INVOCATION RECORD:Link copied to clipboard

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB984S ERROR IN JOB RECORD:Link copied to clipboard

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB985S INVALID RECORD TYPE IN THE REPORT FILELink copied to clipboard

Explanation: The CTBJAFIG Control-M/Analyzer utility detected an error in the Report Data file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB986S INCORRECT NUMBER OF RECORDS IN THE REPORT FILELink copied to clipboard

Explanation: The CTBJAFIG Control-M/Analyzer utility detected an error in the Report Data file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB987S INCORRECT NUMBER OF FREE RECORDS IN THE REPORT FILELink copied to clipboard

Explanation: The CTBJAFIG Control-M/Analyzer utility detected an error in the Report Data file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB988S ERROR IN SECONDARY REPORT RECORD:Link copied to clipboard

Explanation: The CTBJAFIG Control-M/Analyzer utility detected an error in a record in the Report Data file. This message is followed by other messages which display information about the record in error.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB989S ERROR IN PRIMARY REPORT RECORD:Link copied to clipboard

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB98AS INVOCATION RECORD FOR THIS REPORT DOES NOT EXISTLink copied to clipboard

Explanation: While checking the logical relation between the Control-M/Analyzer Job Activity and Report Data files, The CTBJAFIG Control-M/Analyzer utility found a record in the Report Data file, but did not find the corresponding record in the Job Activity Data file.

This message is followed by a message that displays the address of the unmatched record.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB98BS REPORT RECORD FOR THIS INVOCATION RECORD DOES NOT EXISTLink copied to clipboard

Explanation: While checking the logical relation between the Control-M/Analyzer Job Activity and Report Data files, the CTBJAFIG Control-M/Analyzer utility found a record in the Job Activity Data file, but did not find the corresponding record in the Report Data file.

This message is followed by a message that displays the address of the unmatched record.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB98CI INTEGRITY CHECKING ENDED WITH RETURN CODE `rc`Link copied to clipboard

Explanation: This information message indicates normal termination of the CTBJAFIG Control-M/Analyzer utility.

Corrective Action: No action is required.

CTB98DE NO JOB RECORDS IN THE JOB ACTIVITY FILELink copied to clipboard

Explanation: The CTBJAFIG Control-M/Analyzer utility did not check the Job Activity Data file because it did not find any Job records in the file. It is likely that the file is empty.

The utility stops executing with a condition code of 32.

Corrective Action: Check whether or not the file is empty. If the file is empty, there is no problem. If the file is not empty, notify your INCONTROL administrator.

CTB98EE NO PRIMARY REPORT RECORDS IN THE REPORT FILELink copied to clipboard

Explanation: The CTBJAFIG Control-M/Analyzer utility did not check the Report Data file because it did not find any Primary Report records in the file. It is likely that the file is empty.

The utility stops executing with a condition code of 32.

Corrective Action: Check whether or not the file is empty. If the file is empty, there is no problem. If the file is not empty, notify your INCONTROL administrator.

CTB98FI RBA = `rba`Link copied to clipboard

Explanation: This information message displays the address of the record when the CTBJAFIG Control-M/Analyzer utility detects a record in error. This message follows the error message which contains details about the error.

Corrective Action: No action is required.

CTB990S INVALID REFERENCE TO THE FIRST ELEMENT IN THE SUB-SEQUENCELink copied to clipboard

Explanation: A problem occurred while the CTBJAFIG Control-M/Analyzer utility was accessing the Job Activity or Report Data file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB991S INVALID REFERENCE TO THE LAST ELEMENT IN THE SUB-SEQUENCELink copied to clipboard

Explanation: A problem occurred while the CTBJAFIG Control-M/Analyzer utility was accessing the Job Activity or Report Data file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB992S INVALID KEY OR BACK-POINTER IN THE SUB-SEQUENCELink copied to clipboard

Explanation: A problem occurred while the CTBJAFIG Control-M/Analyzer utility was accessing the Job Activity or Report Data file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB993S ERROR IN THE RECORD SUB-SEQUENCELink copied to clipboard

Explanation: A problem occurred while the CTBJAFIG Control-M/Analyzer utility was accessing the Job Activity or Report Data file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB994S INVALID BACK-POINTER IN THE RECORDLink copied to clipboard

Explanation: A problem occurred while the CTBJAFIG Control-M/Analyzer utility was accessing the Job Activity or Report Data file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB995S INVALID RECORD TYPE IN THE RECORD SEQUENCELink copied to clipboard

Explanation: A problem occurred while the CTBJAFIG Control-M/Analyzer utility was accessing the Job Activity or Report Data file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB996S LOOP DETECTED IN INFO RECORD SEQUENCELink copied to clipboard

Explanation: The CTBJAFIG Control-M/Analyzer utility detected a loop in the Information record sequence in the Job Activity Data file. This message is followed by the CTB98FI message, which displays the addresses of the records included in the loop.

The utility bypasses the loop and continues normal execution.

Corrective Action: Notify your INCONTROL administrator about the loop.

CTB997S LOOP DETECTED IN INVO RECORD SEQUENCELink copied to clipboard

Explanation: The CTBJAFIG Control-M/Analyzer utility detected a loop in the Invocation record sequence in Rule Activity File. This message is followed by the CTB98FI message, which displays the addresses of the records included in the loop.

The utility bypasses the loop and continues normal execution.

Corrective Action: Notify your INCONTROL administrator about the loop.

CTB998S LOOP DETECTED IN SECONDARY REPORT RECORD SEQUENCELink copied to clipboard

Explanation: The CTBJAFIG Control-M/Analyzer utility detected a loop in the Secondary Report record sequence in report file. This message is followed by the CTB98FI message, which displays the addresses of the records included in the loop.

The utility bypasses the loop and continues normal execution.

Corrective Action: Notify your INCONTROL administrator about the loop.

CTB999S INVALID KEY FOUND IN RECORDLink copied to clipboard

Explanation: A problem occurred while the CTBJAFIG Control-M/Analyzer utility was accessing the Job Activity or Report Data file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB99AS JOB RECORD HAS NO INVOCATION RECORDSLink copied to clipboard

Explanation: No Invocation records were found for the job record in the Job Activity Data file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB99BI CORRECTION OF JOB ACTIVITY FILE IS IN PROGRESSLink copied to clipboard

Explanation: This information message indicates that the CTBJAFIG Control-M/Analyzer utility has begun correcting the Control-M/Analyzer Job Activity Data file.

Corrective Action: No action is required.

CTB99CI CORRECTION OF REPORT FILE IS IN PROGRESSLink copied to clipboard

Explanation: This information message indicates that the CTBJAFIG Control-M/Analyzer utility has begun correcting the Control-M/Analyzer Report Data file.

Corrective Action: No action is required.

CTB99DI LOGICAL RELATION BETWEEN THE JOB ACTIVITY AND REPORT FILES NOW BEING CORRECTEDLink copied to clipboard

Explanation: This information message indicates that the CTBJAFIG Control-M/Analyzer utility has begun correcting the logical relation between the Control-M/Analyzer Job Activity and Report Data files.

Corrective Action: No action is required.

CTB99EI JOB RECORD HAS BEEN DELETED `record`Link copied to clipboard

Explanation: This information message indicates that the CTBJAFIG Control-M/Analyzer utility deleted the record job record from the Job Activity Data file because the record was in error. This message is followed by other messages that give additional information about the deleted record.

Corrective Action: No action is required.

CTB99FI INVOCATION RECORD HAS BEEN DELETED `record`Link copied to clipboard

Explanation: This information message indicates that the CTBJAFIG Control-M/Analyzer utility deleted the record invocation record from the Job Activity Data file because the record was in error. This message is followed by other messages that give additional information about the deleted record.

Corrective Action: No action is required.

CTB9A1E INVALID STATEMENT IN CRITERIA DEFINITIONLink copied to clipboard

Explanation: The CTBDBVCP Control-M/Analyzer utility failed due to syntax errors in criteria definition input statements.

The utility stops executing with a condition code of 16.

Corrective Action: Correct the input statements and rerun the job.

CTB9A2E INVALID GROUP SPECIFIED IN CRITERIA DEFINITIONLink copied to clipboard

Explanation: The CTBDBVCP Control-M/Analyzer utility failed due to error in the GROUP input statement.

The utility stops executing with a condition code of 16.

Corrective Action: Correct the GROUP input statement and rerun the job.

CTB9A3E INVALID VARIABLE NAME SPECIFIED IN CRITERIA DEFINITIONLink copied to clipboard

Explanation: The CTBDBVCP Control-M/Analyzer utility failed due to an error in the VARIABLE input statement.

The utility stops executing with a condition code of 16.

Corrective Action: Correct the VARIABLE input statement and rerun the job.

CTB9A4S ERROR OPENING DATABASELink copied to clipboard

Explanation: The CTBDBVCP Control-M/Analyzer utility was unable to open the Control-M/Analyzer database.

Possible causes are:

One of the DD statements DIMOD, DIVAR, DOMOD, or DOVAR is missing.
One of the data sets referenced by the DD statements listed above cannot be opened for sequential read or write.

The utility stops executing with a nonzero return code.

Corrective Action: Correct the problem and rerun the job.

CTB9A5S INSUFFICIENT STORAGE TO RUN CONTROL-M/ANALYZER UTILITY CTBDBVCPLink copied to clipboard

Explanation: The CTBDBVCP Control-M/Analyzer utility requires more storage in order to copy the requested entries from the source Control-M/Analyzer database.

The utility stops executing with a condition code of 12.

Corrective Action: Increase the REGION size and rerun the job.

CTB9A6S ERROR ACCESSING TARGET DATABASELink copied to clipboard

Explanation: The CTBDBVCP Control-M/Analyzer copy utility was unable to access the target Control-M/Analyzer database.

The utility stops executing with a nonzero return code.

Corrective Action: Notify your INCONTROL administrator.

CTB9A7S ERROR ACCESSING SOURCE DATABASELink copied to clipboard

Explanation: The CTBDBVCP Control-M/Analyzer copy utility was unable to access the source Control-M/Analyzer database.

The utility stops executing with a nonzero return code.

Corrective Action: Notify your INCONTROL administrator.

CTB9A8I CONTROL-M/ANALYZER UTILITY CTBDBVCP STARTEDLink copied to clipboard

Explanation: This information message indicates the normal start of the CTBDBVCP Control-M/Analyzer copy utility.

Corrective Action: No action is required.

CTB9A9I COPY PERFORMED: `numVariables` VARIABLES, `numGroups` GROUPS WERE COPIEDLink copied to clipboard

Explanation: This information message indicates the normal termination of the CTBDBVCP Control-M/Analyzer copy utility. This message includes statistics.

Corrective Action: No action is required.

CTB9AAI VARIABLE ALREADY EXISTS IN TARGET DATABASE GROUP: `grp` VARIABLE: `varName`Link copied to clipboard

Explanation: This information message indicates that the CTBDBVCP Control-M/Analyzer utility did not copy the indicated variable because it already exists in the target database.

The utility continues executing.

Corrective Action: To replace the variable, rerun the job with the REPLACE parameter set to YES.

CTB9ABI GROUP: `grp` ALREADY EXISTS IN TARGET DATABASELink copied to clipboard

Explanation: This information message indicates that the CTBDBVCP Control-M/Analyzer utility did not copy the grp group because it already exists in the target database.

The utility continues executing.

Corrective Action: To replace the group, rerun the job with the REPLACE parameter set to YES.

CTB9ACS OPEN OF SYSIN FAILED. CHECK DD CARD "DACMD"Link copied to clipboard

Explanation: The CTBDBVCP Control-M/Analyzer utility could not open the input file (the SYSIN DD statement).

Possible causes are:

The SYSIN DD statement or the DACMD DD statement is missing.
The data set referenced by the SYSIN DD statement cannot be accessed for sequential read.

The utility stops executing with a condition code of 36.

Corrective Action: Fix the problem and rerun the job.

CTB9ADE INVALID NUMGEN/FROMGEN/TOGEN STATEMENT DEFINITIONLink copied to clipboard

Explanation: The CTBDBVCP Control-M/Analyzer utility could not process the NUMGEN, FROMGEN, or TOGEN input statement.

The utility stops executing with a condition code of 40.

Corrective Action: Correct the input statements and rerun the job.

CTB9AEE FROMGEN/TOGEN RANGE SIZE EXCEEDS NUMBER OF GENERATIONS REQUESTED FOR TARGET VARIABLELink copied to clipboard

Explanation: The CTBDBVCP Control-M/Analyzer utility was unable to process the input statements. The range of generations requested for copying to the newly created variable, exceeds the total number of generations requested for creation in the target database.

The utility stops executing with a condition code of 44.

Corrective Action: Increase the value specified in input statement NUMGEN= value, or decrease the range specified in statements FROMGEN= value and TOGEN= value. Rerun the job.

CTB9AFS INITIALIZATION ERROR. UNABLE TO CONTINUE PROCESSINGLink copied to clipboard

Explanation: The CTBDBVDL Control-M/Analyzer utility failed to initialize processing.

The utility stops executing with a nonzero condition code.

Corrective Action: Notify your INCONTROL administrator.

CTB9B0S ERROR OPENING SYSPRINTLink copied to clipboard

Explanation: The CTBDBVCP Control-M/Analyzer utility failed to open the print file referenced by the SYSPRINT DD statement.

Possible causes are:

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

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

CTB9B1E INVALID STATEMENT IN CRITERIA DEFINITIONLink copied to clipboard

Explanation: The CTBDBVDL Control-M/Analyzer utility failed due to one or more errors in the criteria definition input statement.

The utility stops executing with a condition code of 16.

Corrective Action: Correct the input statement and rerun the job.

CTB9B2E INVALID GROUP SPECIFIED IN CRITERIA DEFINITIONLink copied to clipboard

Explanation: The CTBDBVDL Control-M/Analyzer utility failed due to error in the GROUP input statement.

The utility stops executing with a condition code of 16.

Corrective Action: Correct the GROUP input statement and rerun the job.

CTB9B3E INVALID VARIABLE NAME SPECIFIED IN CRITERIA DEFINITIONLink copied to clipboard

Explanation: The CTBDBVDL Control-M/Analyzer utility failed due to an error in the VARIABLE input statement.

The utility stops executing with a condition code of 16.

Corrective Action: Correct the VARIABLE input statement and rerun the job.

CTB9B4S ERROR OPENING DATABASELink copied to clipboard

Explanation: The CTBDBVDL Control-M/Analyzer utility is unable to open the Control-M/Analyzer database.

Possible causes are:

One of the DD statements DIMOD, DIVAR, DOMOD or DOVAR is missing.
One of the data sets referenced by the DD statements listed above cannot be opened for sequential read or write.

The utility stops executing with a nonzero condition code.

Corrective Action: Correct the problem and rerun the job.

CTB9B5S ERROR OPENING SYSPRINTLink copied to clipboard

Explanation: The CTBDBVDL Control-M/Analyzer utility failed to open the print file referenced by the SYSPRINT DD statement.

Possible causes are:

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

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

CTB9B6S I/O ERROR UPDATING DATABASELink copied to clipboard

Explanation: The CTBDBVDL Control-M/Analyzer utility failed to update the Control-M/Analyzer database.

The utility stops executing with a nonzero condition code.

Corrective Action: Notify your INCONTROL administrator.

CTB9B7S I/O ERROR READING DATABASE RECORDLink copied to clipboard

Explanation: The CTBDBVDL Control-M/Analyzer utility failed to read the Control-M/Analyzer database.

The utility stops executing with a nonzero condition code.

Corrective Action: Notify your INCONTROL administrator.

CTB9B8I CONTROL-M/ANALYZER UTILITY CTBDBVDL STARTEDLink copied to clipboard

Explanation: This information message indicates the normal start of the CTBDBVDL Control-M/Analyzer compression utility.

Corrective Action: No action is required.

CTB9B9I UTILITY CTBDBVDL ENDED: `num` VARIABLES, `num` GROUPS WERE DELETEDLink copied to clipboard

Explanation: This information message indicates the normal termination of the CTBDBVDL Control-M/Analyzer compression utility. This message includes statistics.

Corrective Action: No action is required.

CTB9BAS ERROR DURING CTBGRP CALL. OPERATION: `opn`Link copied to clipboard

Explanation: The CTBDBVDL Control-M/Analyzer utility failed to execute the indicated operation on the Control-M/Analyzer Group file.

In most cases, this utility stops executing with a nonzero condition code. However, if the error occurs while deleting a group, processing continues with the next group.

Corrective Action: Notify your INCONTROL administrator.

CTB9BBS ERROR DURING CTBDBV CALL. OPERATION: `opn`Link copied to clipboard

Explanation: The CTBDBVDL Control-M/Analyzer utility failed to execute the indicated operation on the Control-M/Analyzer database.

The utility continues processing but it will end with a nonzero condition code.

Corrective Action: Notify your INCONTROL administrator.

CTB9BCE GROUP FILE CONTAINS NO RECORDS WHICH SATISFY THE SPECIFIED CRITERIALink copied to clipboard

Explanation: The CTBDBVDL or CTBDBVDL Control-M/Analyzer utility did not delete any records because no records matching the specification were found in the Control-M/Analyzer Group file.

The utility stops executing with a condition code of 04.

Corrective Action: Specify the correct group name or mask in the GROUP input statement and rerun the jobname.

CTB9BDE UNABLE TO DELETE THE REQUESTED GROUP. PLEASE SPECIFY ASTERISK (*) INSTEAD OF THE VARIABLE NAMELink copied to clipboard

Explanation: The CTBDBVDL Control-M/Analyzer utility could not delete the requested record from the Control-M/Analyzer Group file because the specified group still contains variables.

The utility stops executing with a condition code of 20.

Corrective Action: Specify asterisk instead of the variable name in the VARIABLE input statement and rerun the job.

CTB9BEE NO CRITERIA SPECIFIED. UNABLE TO CONTINUE PROCESSINGLink copied to clipboard

Explanation: The CTBDBVDL Control-M/Analyzer utility is unable to continue processing because no input statements were specified.

The utility stops executing with a condition code of 28.

Corrective Action: Specify input statements and rerun the job.

CTB9BFS OPEN OF SYSIN FAILED. CHECK DD CARD "DACMD"Link copied to clipboard

Explanation: The CTBDBVDL Control-M/Analyzer utility failed to open the input file referenced by the SYSIN DD statement.

This failure may be due to one of the following:

The SYSIN DD statement or the DACMD DD statement is missing.
The data set referenced by the SYSIN DD statement cannot be accessed for sequential read.

The utility stops executing with a condition code of 28.

Corrective Action: Correct the JCL and rerun the job.

CTB9C0I CONTROL-M/ANALYZER ACTIVE BALANCING FILE FORMATTING STARTEDLink copied to clipboard

Explanation: This information message indicates that the Control-M/Analyzer Active Balancing file is currently being formatted by the CTBFRM program, which is usually activated as part of the New Day procedure.

Corrective Action: No action is required.

CTB9C1I Control-M/ANALYZER ACTIVE BALANCING FILE FORMATTING ENDEDLink copied to clipboard

Explanation: This information message indicates that formatting of the Control-M/Analyzer Active Balancing file by the CTBFRM program ended successfully.

Corrective Action: No action is required.

CTB9C2I PREVIOUS FORMAT RUN FAILED. BACKUP COPY WILL BE USEDLink copied to clipboard

Explanation: This information message indicates that the Control-M/Analyzer New Day procedure is currently being rerun after abending which formatting the Active Balancing file.

The Active Balancing file is restored from the Active Balancing Backup file and processing continues normally.

Corrective Action: No action is required.

CTB9C3S OPEN OF CONTROL-M/ANALYZER ACTIVE BALANCING FILE FAILED. DDNAME "DAABF"Link copied to clipboard

Explanation: Open of the Control-M/Analyzer Active Balancing file failed (the DAABF DD statement). This error message is issued by the CTBFRM program, which is usually activated as part of the New Day procedure, and is due to one of the following:

The DAABF DD statement is missing.
The data set referenced by the DAABF DD statement is not the Control-M/Analyzer Active Balancing file.

Program execution stops with a nonzero condition code.

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

CTB9C4S INTERNAL ERROR WHILE PROCESSING ACTIVE BALANCING FILE. FILE NOT FORMATTEDLink copied to clipboard

Explanation: Processing of the Control-M/Analyzer Active Balancing file failed. This error message is issued by the CTBFRM program, which is usually activated as part of the New Day procedure.

Program execution stops with a nonzero condition code.

Corrective Action: Notify your INCONTROL administrator.

CTB9C5S INTERNAL ERROR FROM THE CTBDBF ROUTINE. RC= `rc`Link copied to clipboard

Explanation: Processing of the Control-M/Analyzer Active Balancing Backup file failed. This error message is issued by the CTBFRM program, which is usually activated as part of the New Day procedure. It is caused by an error during initialization of the Active Balancing file.

Program execution stops with a nonzero condition code.

Corrective Action: Notify your INCONTROL administrator.

CTB9C6S INTERNAL ERROR DURING INITIALIZATION. ACTIVE BALANCING FILE NOT FORMATTEDLink copied to clipboard

One of the following may occur, depending on the situation:

Program execution stops with a condition code of 16 indicating failure to load the CTBINFO routine.
Program execution stops with a condition code of 20 indicating failure to load the CTBINI routine.
Program execution stops with some other nonzero condition code.

Corrective Action: Notify your INCONTROL administrator.

CTB9C7S INSUFFICIENT MEMORY TO FORMAT THE CONTROL-M/ANALYZER ACTIVE BALANCING FILELink copied to clipboard

Explanation: Insufficient memory is available for the CTBFRM program to format the Control-M/Analyzer Active Balancing file. Clarification program CTBFRM is usually activated as part of the New Day procedure.

The utility stops executing with a condition code of 12.

Corrective Action: Increase the REGION size and rerun the New Day procedure.

CTB9C8S READING OF THE ACTIVE BALANCING BACKUP FILE FAILEDLink copied to clipboard

Explanation: An error occurred while reading the Control-M/Analyzer Active Balancing Backup file by the CTBFRM program, which is usually activated as part of the New Day procedure.

The utility stops executing with a nonzero condition code.

Corrective Action: Notify your INCONTROL administrator.

CTB9C9S INVALID JOB ID IN ACTIVE BALANCING FILE RECORD: BLOCK= `block` RECORD= `record`Link copied to clipboard

Explanation: The CTBFRM program encountered an invalid job ID in a record in the Control-M/Analyzer Active Balancing file. The CTBFRM program is usually activated as part of the New Day procedure.

The record that contains the error is deleted. The utility continues executing with the next record.

Corrective Action: Notify your INCONTROL administrator.

CTB9CAS INVALID ODATE IN ACTIVE BALANCING FILE RECORD: BLOCK= `blk` RECORD= `record`Link copied to clipboard

Explanation: The CTBFRM program encountered an invalid ODATE in a record in the Control-M/Analyzer Active Balancing file. The CTBFRM program is usually activated as part of the New Day procedure.

The record that contains the error is deleted. The utility continues executing with the next record.

Corrective Action: Notify your INCONTROL administrator.

CTB9CBS CONTROL-M/ANALYZER DATE CONTROL RECORD IS EMPTYLink copied to clipboard

Explanation: The CTBFRM program encountered an empty Date Control Record. The CTBFRM program is usually activated as part of the New Day procedure.

The problem may be due to one of the following:

The record referenced by the DACHK DD statement is not the Control-M/Analyzer Date Control Record.
The contents of the Date Control Record have been manually modified incorrectly.

The utility stops executing with a condition code of 28.

Corrective Action: Depending on the cause of the problem, do one of the following:

Correct the JCL for the New Day procedure and rerun the procedure.
Correct the Date Control Record and rerun the New Day procedure.

CTB9CCS OPEN OF CONTROL-M/ANALYZER DATE CONTROL RECORD FAILED. DDNAME "DACHK"Link copied to clipboard

Explanation: The file containing the Control-M/Analyzer Date Control Record could not be opened. This message is issued by the CTBFRM program, which is usually activated as part of the New Day procedure.

The problem may be due to one of the following:

The record referenced by the DACHK DD statement is not the Control-M/Analyzer Date Control Record.
the DACHK DD statement is missing.
An internal error occurred during opening of the file referenced by the DACHK DD statement.

The utility stops executing with a condition code of 32.

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

CTB9CDS INVALID LAST FORMAT DATE IN THE DATE CONTROL-RECORDLink copied to clipboard

Explanation: The last date in the Control-M/Analyzer Date Control Record has an invalid format. The valid format is ddmmyy. This message is issued by the CTBFRM program which is usually activated as part of the New Day procedure.

The problem may be due to one of the following:

The record referenced by the DACHK DD statement is not the Control-M/Analyzer Date Control Record.
The contents of the Date Control Record have been manually modified incorrectly.

The utility stops executing with a condition code of 36.

Corrective Action: Depending on the cause of the problem, do one of the following:

Correct the JCL for the New Day procedure and rerun the procedure.
Correct the format of the Date Control Record and rerun the New Day procedure.

CTB9CES INVALID ORIGINAL SCHEDULING DATE IN THE DATE CONTROL RECORDLink copied to clipboard

Explanation: The original scheduling date in the Control-M/Analyzer Date Control Record has an invalid format. The valid format is ddmmyy. This message is issued by the CTBFRM program, which is usually activated as part of the New Day procedure.

The problem may be due to one of the following:

The record referenced by the DACHK DD statement is not the Control-M/Analyzer Date Control Record.
The contents of the Date Control Record have been manually modified incorrectly.

The utility stops executing with a condition code of 40.

Corrective Action: Depending on the cause of the problem, do one of the following:

Correct the JCL for the New Day procedure and rerun the procedure.
Correct the format of the Date Control Record and rerun the New Day procedure.

CTB9CFE FORMAT PROGRAM CTBFRM WAS ALREADY RUN TODAYLink copied to clipboard

Explanation: An attempt was made to run the New Day procedure (which executes the CTBFRM format program) twice in the same day. After the CTBFRM program executes successfully, it should not normally be re-executed the same day.

The CTBFRM program stops executing with a condition code of 44. The Active Balancing file is not reformatted. The New Day procedure continues to execute other programs.

Corrective Action: Check the reason that the New Day procedure is being run twice.

CTB9D0S LAST FORMAT DATE GREATER THAN ORIGINAL SCHEDULING DATE IN THECONTROL-M/ANALYZER DATE CONTROL RECORDLink copied to clipboard

Explanation: The last format date is greater then the original scheduling date in the Control-M/Analyzer Date Control Record. This message is produced by the New Day procedure. For more details, refer to the INCONTROL for z/OS Administrator Guide.

The utility stops executing with a condition code of 48.

Corrective Action: Correct the Control-M/Analyzer Date Control Record and run the New Day procedure again.

CTB9D1S OPEN OF IOA LOG FILE FAILEDLink copied to clipboard

Explanation: Open of the IOA Log File failed. The message is produced by the New Day procedure.

The failure may be due to one of the following:

The DALOG DD statement is missing.
The file referenced by the DALOG DD statement is not the IOA Log File.
The file referenced by the DALOG DD statement is the IOA Log File, but from a different version or of a different IOA environment.

The utility stops executing with a condition code of 52.

Corrective Action: Correct the JCL and run the New Day procedure again.

CTB9D2S ENQ ON THE ACTIVE BALANCING FILE FAILEDLink copied to clipboard

Explanation: The CTBFRM program, which is usually activated as part of the New Day procedure, could not get exclusive control of the Control-M/Analyzer Active Balancing file, because a Control-M/Analyzer job or mission was executing with exclusive control at the same time. Exclusive control is required for file formatting.

The utility stops executing with a condition code of 56.

Corrective Action: Rerun the New Day procedure when the Active Balancing file is free for exclusive control.

CTB9D3S INVALID RC FROM CTBINFO ROUTINE: RC= `rc`, JOBNAME= `jobName`Link copied to clipboard

Explanation: The New Day procedure could not detect the status of the indicated job in the Control-M/Analyzer Active Balancing file. The job is not deleted because it may still be executing.

The job is not deleted. The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB9D4S OPEN OF CONTROL-M/ANALYZER ACTIVE BALANCING BACKUP FILE FAILED. DDNAME "DABKP"Link copied to clipboard

Explanation: Open of Control-M/Analyzer Active Balancing Backup file failed (the DABKP DD statement). This error message is issued by the CTBFRM program, which is usually activated as part of the New Day procedure.

Probable causes:

The DABKP DD statement is missing.
The data set referenced by the DABKP DD statement is not the Control-M/Analyzer Active Balancing file.

Program execution stops with a nonzero condition code.

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

CTB9D5S INTERNAL ERROR WHILE PROCESSING ACTIVE BALANCING BACKUP FILE. FORMATTING FAILEDLink copied to clipboard

Explanation: Processing of the Control-M/Analyzer Active Balancing Backup file failed. This message is issued by the CTBFRM program which is usually activated as part of the New Day procedure.

Program execution stops with a nonzero condition code.

Corrective Action: Notify your INCONTROL administrator.

CTB9D6S ERROR OPENING SYSPRINTLink copied to clipboard

Explanation: An error occurred while opening the print file referenced by the SYSPRINT DD statement. This message is issued by the CTBFRM program which is usually activated as part of the New Day procedure.

The error may be due to one of the following:

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

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

CTB9D7E THE SIZE OR LRECL PARAMETER OF THE ABFBKP FILE DIFFERS FROM THE ABF FILELink copied to clipboard

Explanation: The CTBFRM Control-M/Analyzer utility detected that the Control-M/Analyzer file for the ABF backup (ABFBKP) was either not large enough for all the records, or that it did not have the same record length as the ABF file.

The CTBFRM utility stops executing with a condition code of 64.

Corrective Action: According to the source of the problem, either reallocate the Control-M/Analyzer ABFBKP file with the LRECL parameter the same as that of the ABF file, or increase the size of the ABFBKP file. Rerun the job.

CTB9E1I INFORMATION RECORD HAS BEEN DELETED `record`Link copied to clipboard

Explanation: This information message indicates that in correcting the Job Activity Data file, the CTBJAFIG Control-M/Analyzer utility deleted the record Information record from the file because the record was in error. This message is followed by other messages that display additional information about the deleted record.

Corrective Action: No action is required.

CTB9E2I PRIMARY REPORT RECORD HAS BEEN DELETED `record`Link copied to clipboard

Explanation: This information message indicates that in correcting the Report Data file, the CTBJAFIG Control-M/Analyzer utility deleted the record Primary Report record from the file because the record was in error. This message is followed by other messages that display additional information about the deleted record.

Corrective Action: No action is required.

CTB9E3I SECONDARY REPORT RECORD HAS BEEN DELETED `record`Link copied to clipboard

Explanation: This information message indicates that in correcting the Report Data file, the CTBJAFIG Control-M/Analyzer utility deleted the record Secondary Report record because the record was in error.

This message is followed by other messages that display additional information about the deleted record.

Corrective Action: No action is required.

CTB9E4I INVOCATION RECORD HAS BEEN CORRECTED `record`Link copied to clipboard

Explanation: This information message indicates that the CTBJAFIG Control-M/Analyzer utility corrected the record Invocation record in the Rule Activity File because the record had been in error.

This message is followed by other messages that display additional information about the deleted record.

Corrective Action: No action is required.

CTB9E5I REPORT RECORD HAS BEEN DELETED `record`Link copied to clipboard

Explanation: This information message indicates that in correcting the report file, the CTBJAFIG Control-M/Analyzer utility deleted the record report record from the file because the record was in error.

This message is followed by other messages that display additional information about the deleted record.

Corrective Action: No action is required.

CTB9E6S ERROR DURING THE CORRECTION PROCESS BY ROUTINE CTBCKPLink copied to clipboard

Explanation: An error occurred while the CTBJAFIG Control-M/Analyzer utility was trying to correct a record in the Job Activity Data file.

This message is followed by the CTB9E8S message, which displays the failed operation, and by the CTB9E9I message, which displays the error code.

The CTBJAFIG utility continues executing with the next record.

Corrective Action: Notify your INCONTROL administrator.

CTB9E7S ERROR DURING THE CORRECTION PROCESS BY ROUTINE CTBREPLink copied to clipboard

Explanation: An error occurred while the CTBJAFIG Control-M/Analyzer utility was trying to correct a record in the Report Data file.

This message is followed by the CTB9E8S message, which displays the failed operation, and by the CTB9E9I message, which displays the error code.

The CTBJAFIG utility continues executing with the next record.

Corrective Action: Notify your INCONTROL administrator.

CTB9E8S OPERATION IS: `opn`Link copied to clipboard

Explanation: While the CTBJAFIG Control-M/Analyzer utility was correcting a record, the operation indicated in the message failed.

This message follows the CTB9E7S or CTB9E6S message.

Corrective Action: Notify your INCONTROL administrator.

CTB9E9I RETURN CODE IS: `rc`Link copied to clipboard

Explanation: This information message displays the return code for the failed operation indicated in the CTB9E8S message. This message follows the CTB9E8S message.

Corrective Action: No action is required.

CTB9EAS INVOCATION RECORD IS NOT IN SEQUENCELink copied to clipboard

Explanation: While reading the Job Activity Data file, the CTBJAFIG Control-M/Analyzer utility encountered an Invocation record which does not belong to any Job record.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB9EBS INFORMATION RECORD IS NOT IN SEQUENCELink copied to clipboard

Explanation: While reading the Job Activity Data file, the CTBJAFIG Control-M/Analyzer utility encountered an Information record which does not belong to any Invocation record.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB9ECS SECONDARY REPORT RECORD IS NOT IN SEQUENCELink copied to clipboard

Explanation: While reading the Report Data file, the CTBJAFIG Control-M/Analyzer utility encountered a Secondary Report record which does not belong to any Primary Report record.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB9EDI APPLICATION GROUP `grpname`Link copied to clipboard

Explanation: This information message indicates the group name from the record deleted by the CTBJAFIG Control-M/Analyzer utility.

Corrective Action: No action is required.

CTB9EEI JOBNAME `jobName`Link copied to clipboard

Explanation: This information message indicates the job name from the record deleted by the CTBJAFIG Control-M/Analyzer utility.

Corrective Action: No action is required.

CTB9EFI DATE `date`Link copied to clipboard

Explanation: This information message indicates the date from the record deleted by the CTBJAFIG Control-M/Analyzer utility.

Corrective Action: No action is required.

CTB9F0I TIME `time`Link copied to clipboard

Explanation: This information message indicates the time from the record deleted by the CTBJAFIG Control-M/Analyzer utility.

Corrective Action: No action is required.

CTB9F1I JOBID `jobId`Link copied to clipboard

Explanation: This information message indicates the job id from the record deleted by the CTBJAFIG Control-M/Analyzer utility.

Corrective Action: No action is required.

Messages CTBA00 through CTBAxxLink copied to clipboard

This group includes messages for the Control-M/Analyzer product.

CTBA00I CONTROL-M/ANALYZER UTILITY CTBJAFDL STARTEDLink copied to clipboard

Explanation: This information message indicates the normal start of the CTBJAFDL utility.

Corrective Action: No action is required.

CTBA01E PLEASE CHECK THE SYNTAX OF STATEMENT `stmt`Link copied to clipboard

Explanation: The CTBJAFDL or CTBJAFCP utility failed because of a syntax error in the stmt statement.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the indicated statement and rerun the job.

CTBA02S ERROR OPENING SYSPRINTLink copied to clipboard

Explanation: The CTBJAFDL or CTBJAFCP utility failed to open the print file referenced by the SYSPRINT DD statement.

The failure may be due to one of the following:

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

The utility stops executing with a condition code of 16.

Corrective Action: Correct the JCL and rerun the job.

CTBA03S ERROR OPENING SYSINLink copied to clipboard

Explanation: The CTBJAFDL or CTBJAFCP utility failed to open the input file referenced by the SYSIN DD statement.

The failure may be due to one of the following:

The SYSIN DD statement, or the DACMD DD statement, is missing.
The data set referenced by the SYSIN DD statement cannot be accessed for a sequential read.

The utility stops executing with a condition code of 16.

Corrective Action: Correct the JCL and rerun the job.

CTBA04S ERROR DURING JAF FILE PROCESSING. OPERATION: `opn`Link copied to clipboard

Explanation: The CTBJAFDL or CTBJAFCP utility failed to perform the opn operation on the Rule Activity file. The accompanying return code is indicated in the CTBA07I message.

If processing of the current record fails, processing continues with the next record. In some cases, for example, if the file could not be opened, processing stops.

Corrective Action: Notify your INCONTROL administrator.

CTBA05S ERROR DURING REPORT FILE PROCESSING. OPERATION: `opn`Link copied to clipboard

Explanation: The CTBJAFDL or CTBJAFCP utility failed to perform the opn operation on the Control-M/Analyzer report file. The accompanying return code is indicated in the CTBA07I message.

If processing of the current record fails, processing continues with the next record. In some cases, for example if the file could not be opened, processing is stopped.

Corrective Action: Notify your INCONTROL administrator.

CTBA06S DDNAME: `ddName`, REQUESTED FUNCTION CANNOT BE PERFORMED SINCE FILE IS BEING ACCESSED BY ANOTHER USERLink copied to clipboard

Explanation: The CTBJAFDL or CTBJAFCP Control-M/Analyzer utility could not lock a database file referenced by the DD name in the DD statement when trying to update it.

The CTBJAFDL or CTBJAFCP Control-M/Analyzer utility stops execution with a nonzero return code.

Corrective Action: Check the reason for a conflict and rerun the Control-M/Analyzer utility after the concurrent applications have finished running.

CTBA07I RC= `rc`Link copied to clipboard

Explanation: This information message indicates the return code resulting from execution of the CTBJAFDL or CTBJAFCP utility.

Corrective Action: No action is required.

CTBA08E FIRST INPUT STATEMENT FOR CONTROL-M/ANALYZER UTILITY CTBJAFDL MUST BE A "DAYS" STATEMENTLink copied to clipboard

Explanation: The first input statement for the CTBJAFDL utility must be, but was not, statement DAYS.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the input statement and rerun the job.

CTBA09S ERROR DURING FREEMAIN OPERATIONLink copied to clipboard

Explanation: The CTBJAFDL or CTBJAFCP utility failed to perform a FREEMAIN operation. The accompanying return code is indicated in the CTBA07I message.

The utility stops executing.

Corrective Action: Notify your INCONTROL administrator.

CTBA0AI THE FOLLOWING JOB RECORDS HAVE BEEN DELETED:Link copied to clipboard

Explanation: This information message indicates the successful deletion of jobs by the CTBJAFDL utility. This message precedes the CTBA11I, CTBA12I, and CTBA13I messages, which display the list of deleted jobs.

Corrective Action: No action is required.

CTBA0BI `num` JOB RECORDS HAVE BEEN COPIEDLink copied to clipboard

Explanation: This information message indicates the number of job entries that have been copied to the target Rule Activity file by the CTBJAFCP Control-M/Analyzer utility.

Corrective Action: No action is required.

CTBA0CI `num` PRIMARY REPORT RECORDS HAVE BEEN COPIEDLink copied to clipboard

Explanation: This information message indicates the number of primary report entries that have been copied to the target report file by the CTBJAFCP Control-M/Analyzer utility.

Corrective Action: No action is required.

CTBA0DE JOB ACTIVITY FILE IS FULL. PLEASE RUN CONTROL-M/ANALYZER UTILITY CTBJAFDLLink copied to clipboard

Explanation: The CTBJAFCP utility failed to copy of the Rule Activity file because the target file is full. The accompanying return code is indicated in the CTBA07I message.

The utility stops executing.

Corrective Action: Compress the Report file by running the CTBJAFDL Control-M/Analyzer utility.

CTBA0EE REPORT FILE IS FULL. PLEASE RUN CONTROL-M/ANALYZER UTILITY CTBJAFDLLink copied to clipboard

Explanation: The CTBJAFCP utility failed to copy of the Rule Activity file because the target file is full. The accompanying return code is indicated in the CTBA07I message.

The utility stops executing.

Corrective Action: Compress the Report file by running the CTBJAFDL utility.

CTBA0FI `num` JOB RECORDS HAVE BEEN DELETEDLink copied to clipboard

Explanation: This information message indicates the number of job entries that were deleted from the Rule Activity File by the CTBJAFDL Control-M/Analyzer utility.

Corrective Action: No action is required.

CTBA12I | JOBNAME | JOBID | DATE | TIME |Link copied to clipboard

Explanation: This information message consists of a series of titles for the information provided in the CTBA13I message.

Corrective Action: No action is required.

CTBA13I `|jobName|jobId|date|time|`Link copied to clipboard

Explanation: The CTBA12I and CTBA13I information messages form a chart listing job entries that were deleted from the Rule Activity file by the C TBJAFDL Control-M/Analyzer utility.

The CTBA13I message is repeated once for each job entry that was deleted.

Corrective Action: No action is required.

CTBA16I CONTROL-M/ANALYZER UTILITY CTBJAFCP STARTEDLink copied to clipboard

Explanation: This information indicates the normal start of the CTBJAFCP Control-M/Analyzer utility.

Corrective Action: No action is required.

CTBA17S INSUFFICIENT STORAGE TO RUN CONTROL-M/ANALYZER UTILITY CTBJAFDLLink copied to clipboard

Explanation: The CTBJAFDL utility requires more memory to compress the Rule Activity file and the report file.

The utility stops executing with a condition code of 12.

Corrective Action: Increase the REGION size and rerun the job.

CTBA18S INSUFFICIENT STORAGE TO RUN CONTROL-M/ANALYZER UTILITY CTBJAFCPLink copied to clipboard

Explanation: The CTBJAFCP utility requires more memory to copy the Rule Activity file and the report file.

The utility stops executing with a condition code of 12.

Corrective Action: Increase the REGION size and rerun the job.

CTBA22S UNABLE TO OPEN FILE. FORMAT FAILEDLink copied to clipboard

Explanation: The CTBDBF4 Control-M/Analyzer utility failed to open the target file referenced by the DAOUT DD statement.

The failure may be due to one of the following:

The DAOUT DD statement is missing.
The data set referenced by the DAOUT DD statement does not exist.

The utility terminates with a condition code of 116.

Corrective Action: Correct the JCL and rerun the job.

CTBA23S ERROR OPENING SYSPRINT. UNABLE TO CONTINUE PROCESSINGLink copied to clipboard

Explanation: The CTBDBF4 Control-M/Analyzer utility failed to open the print file referenced by the SYSPRINT DD statement.

The failure may be due to one of the following:

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

The utility terminates with a condition code of 120.

Corrective Action: Correct the JCL and rerun the job.

CTBA24S INSUFFICIENT STORAGE TO RUN FORMATLink copied to clipboard

Explanation: The CTBDBF4 Control-M/Analyzer utility requires more memory to format the target file.

The utility terminates with a condition code of 112.

Corrective Action: Increase the REGION size and rerun the job.

CTBA30I A PROBLEM WAS FOUND IN LINE linLink copied to clipboard

Explanation: This information message indicates that the lin input line was erroneous. An error message detailing the problem follows this message.

Corrective Action: No action is required.

CTBA31E INVALID LINE. item=VALUE EXPECTED

Explanation: The line structure was not in the format item= value. Input lines with parameters for the CTBVXRF cross-reference utility must be formatted item= value.

The CTBVXRF cross-reference utility terminates with an error.

Corrective Action: Correct the utility parameters and rerun the utility.

For more information, see the CTBVXRF cross-reference utility in the INCONTROL for z/OS Utilities Guide.

CTBA32E AN INPUT LINE OF THE FORM LIB= `rule-lib` IS EXPECTEDLink copied to clipboard

Explanation: The input statement to the CTBVXRF cross-reference utility did not include the parameter identified in the message.

The CTBVXRF cross-reference utility terminates with an error.

Corrective Action: Correct the error and rerun the CTBVXRF utility.

For more information, see the CTBVXRF cross-reference utility in the INCONTROL for z/OS Utilities Guide.

CTBA33E AN INPUT LINE OF THE FORM RULE=NAME-MASK IS EXPECTEDLink copied to clipboard

Explanation: The input statement to the CTBVXRF cross-reference utility did not include the parameter identified in the message.

The CTBVXRF cross-reference utility terminates with an error.

Corrective Action: Correct the error and rerun the CTBVXRF utility.

For more information, see the CTBVXRF cross-reference utility in the INCONTROL for z/OS Utilities Guide.

CTBA34E AN INPUT LINE OF THE FORM SORT=RULE/VAR IS EXPECTEDLink copied to clipboard

Explanation: The input statement to the CTBVXRF cross-reference utility did not include the parameter identified in the message.

The CTBVXRF cross-reference utility terminates with an error.

Corrective Action: Correct the error and rerun the CTBVXRF utility.

For more information, see the CTBVXRF cross-reference utility in the INCONTROL for z/OS Utilities Guide.

CTBA35E AN INPUT LINE OF THE FORM BLOCKS=YES/NO IS EXPECTEDLink copied to clipboard

Explanation: The current input line specified an unexpected parameter. The input to cross-reference The CTBVXRF utility consists of parameters specified in a predefined order.

The CTBVXRF cross-reference utility terminates with an error.

Corrective Action: Correct the error and rerun the CTBVXRF utility. See the CTBVXRF cross-reference utility in the INCONTROL for z/OS Utilities Guide for more information.

CTBA36E INCORRECT SORT OPTION. SPECIFY "RULE" OR "VAR"Link copied to clipboard

Explanation: The sort option was incorrect. The Cross-Reference Report may be sorted either by rule name (option RULE) or by variable name (option VAR).

The CTBVXRF cross-reference utility terminates with an error.

Corrective Action: Correct the error and rerun the utility.

For more information, see the CTBVXRF cross-reference utility in the INCONTROL for z/OS Utilities Guide.

CTBA37E INCORRECT BLOCKS OPTION, SPECIFY "YES" OR "NO"Link copied to clipboard

Explanation: The value of the BLOCKS option for the CTBVXRF cross-reference utility was not YES or NO.

The BLOCKS option specifies whether or not to include the block name in the cross-reference report. Its value must be YES or NO.

The CTBVXRF cross-reference utility terminates with an error.

Corrective Action: Correct the error and rerun the utility. For more information, see the CTBVXRF cross-reference utility in the INCONTROL for z/OS Utilities Guide.

CTBA3AI CONTROL-M/ANALYZER UTILITY CTBDBVCG STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTBDBVCG Control-M/Analyzer utility, which changes the number of generations, has started running.

Corrective Action: No action is required.

CTBA3BE INVALID GROUP CRITERIA SPECIFIEDLink copied to clipboard

Explanation: The CTBDBVCG Control-M/Analyzer utility detected an error in the GROUP input statement.

The CTBDBVCG Control-M/Analyzer utility stops executing with a condition code of 32.

Corrective Action: Correct the GROUP input statement and rerun the job. For more information, see the description of the GROUP input statement in the Control-M/Analyzer User Guide.

CTBA3CE INVALID VARIABLE CRITERIA SPECIFIEDLink copied to clipboard

Explanation: The CTBDBVCG Control-M/Analyzer utility detected an error in the VARIABLE input statement.

The CTBDBVCG Control-M/Analyzer utility stops executing with a condition code of 32.

Corrective Action: Correct the VARIABLE input statement and rerun the job. For more information, see the description of the VARIABLE input statement in the Control-M/Analyzer User Guide.

CTBA3DS INTERNAL ERROR READING DATABASE RECORD. ERROR CODE `rc`Link copied to clipboard

Explanation: Processing of the Control-M/Analyzer Model failed.

The utility stops executing with a nonzero condition code.

Corrective Action: Provide your INCONTROL administrator with the sysout of the CTBDBVCG utility.

CTBA3ES INTERNAL ERROR UPDATING DATABASE RECORD, ERROR CODE `rc`Link copied to clipboard

Explanation: Processing of the Control-M/Analyzer Variables Definition or Variables Generations failed.

The utility stops executing with a nonzero condition code.

Corrective Action: Provide your INCONTROL administrator with the sysout of the CTBDBVCG. utility.

CTBA3FS INSUFFICIENT SPACE IN THE CONTROL-M/ANALYZER VAR FILELink copied to clipboard

Explanation: The CTBDBVCG utility could not update the Control-M/Analyzer Variables Generations file because it was full.

The CTBDBVCG utility stops executing with a nonzero condition code.

Corrective Action: Enlarge the Control-M/Analyzer Variables Generations file or decrease the value of the NUMGEN input parameter and rerun the job.

CTBA40S INSUFFICIENT SPACE IN THE CONTROL-M/ANALYZER MOD FILELink copied to clipboard

Explanation: The CTBDBVCG utility could not update the Control-M/Analyzer Variables Definition file because it was full.

The CTBDBVCG utility stops executing with a nonzero condition code.

Corrective Action: Enlarge the Control-M/Analyzer Variables Definition file or decrease the value of the NUMGEN input parameter and rerun the job.

CTBA41E INVALID NUMGEN PARAMETER SPECIFIEDLink copied to clipboard

Explanation: The CTBDBVCG Control-M/Analyzer utility detected an error in the NUMGEN input statement.

The CTBDBVCG Control-M/Analyzer utility stops executing with a condition code of 32.

Corrective Action: Correct the NUMGEN input statement and rerun the job. For more information, see the description of the NUMGEN input statement in the Control-M/Analyzer User Guide.

CTBA42S OPEN OF SYSIN FAILED. CHECK DD CARD "DACMD"Link copied to clipboard

Explanation: The CTBDBVCG Control-M/Analyzer utility failed to open the input file referenced by the DACMD DD statement.

Possible causes are:

The DACMD DD statement is missing.
The data set referenced by the DACMD DD statement cannot be written to sequentially.

The utility stops executing with a condition code of 16.

Corrective Action: Correct the JCL accordingly and rerun the job.

CTBA43S ERROR OPENING CONTROL-M/ANALYZER DATABASELink copied to clipboard

Explanation: The CTBDBVCG Control-M/Analyzer utility failed to open the Control-M/Analyzer database.

The utility stops executing with a nonzero condition code.

Corrective Action: Verify that the correct Control-M/Analyzer database was allocated to the CTBDBVCG utility and rerun the job.

CTBA44S INSUFFICIENT STORAGE TO RUN CONTROL-M/ANALYZER UTILITY CTBDBVCGLink copied to clipboard

Explanation: There is insufficient memory for the CTBDBVCG Control-M/Analyzer utility to update the database.

The CTBDBVCG utility stops executing with a condition code of 12.

Corrective Action: Increase the region size for the CTBDBVCG utility, and rerun the job.

CTBA45S OPEN OF SYSPRINT FAILED. CHECK DD CARD "DCBOUT"Link copied to clipboard

Explanation: The CTBDBVCG Control-M/Analyzer utility failed to open the print file referenced by the DCBOUT DD statement.

The failure might be due to one of the following reasons:

The DCBOUT DD statement is missing.
The data set referenced by the DCBOUT DD statement cannot be written to sequentially.

The CTBDBVCG utility stops executing with a condition code of 8.

Corrective Action: Correct the JCL accordingly and rerun the job.

CTBA46I NO INPUT PARAMETERS SPECIFIED. SYSIN FILE IS EMPTYLink copied to clipboard

Explanation: This information message indicates that no input statements were specified for the CTBDBVCG Control-M/Analyzer utility.

The CTBDBVCG utility stops executing with a condition code of 4.

Corrective Action: Insert GROUP and/or VARIABLE input statements in the JCL and rerun the job.

CTBA47I NO CONTROL-M/ANALYZER VARIABLES SATISFIED THE SPECIFIED CRITERIALink copied to clipboard

Explanation: This information message indicates that the CTBDBVCG Control-M/Analyzer utility found no database records that satisfy the specified input criteria.

The CTBDBVCG utility stops executing with a condition code of 4.

Corrective Action: Correct the GROUP and/or VARIABLE input statements in the JCL and rerun the job.

Messages CTBB00 through CTBBxxLink copied to clipboard

This group includes messages for the Control-M/Analyzer product.

CTBB01S ERROR OCCURRED WHILE PROCESSING FILE `fileName` IN MSUBSTMASKLink copied to clipboard

Explanation: The MSUBSTMASK function failed to process the fileName file.

Possible causes are:

The DD statement for the file is missing
The data set referenced by the DD statement cannot be read sequentially.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Correct the JCL an rerun the job.

CTBB02S USERBLOCK `usrblk` IN ON_COMPARE IS NOT DECLAREDLink copied to clipboard

Explanation: The usrblk userblock is not specified in the current Control-M/Analyzer rule. An ON_COMPARE statement referenced a nonexistent user block.

The Control-M/Analyzer runtime environment ends with an error.

Corrective Action: Correct the reference and re-invoke Control-M/Analyzer.

CTBB03S ERROR WHILE PROCESSING USERBLOCK `usrblk` IN ON_COMPARELink copied to clipboard

Explanation: Control-M/Analyzer encountered an error while processing the usrblk userblock during execution of an ON_COMPARE statement.

The Control-M/Analyzer runtime environment ends with an error.

Corrective Action: Correct the error and restart Control-M/Analyzer.

CTD messagesLink copied to clipboard

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

Messages CTD0 through CTD0xxLink copied to clipboard

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

CTD000I Control-V GLOBAL INDEX `utilityName` STARTEDLink copied to clipboard

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

Corrective Action: No action is required.

CTD001E PLEASE FILL IN LIBRARY NAMELink copied to clipboard

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 OKLink copied to clipboard

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.Link copied to clipboard

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 NAMELink copied to clipboard

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 TREELink copied to clipboard

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 ENTEREDLink copied to clipboard

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 SPECIFIEDLink copied to clipboard

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 USERLink copied to clipboard

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`Link copied to clipboard

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`Link copied to clipboard

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 EMPTYLink copied to clipboard

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 TODATELink copied to clipboard

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 MEMBERLink copied to clipboard

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"Link copied to clipboard

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`Link copied to clipboard

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"Link copied to clipboard

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 TREELink copied to clipboard

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 PARAMETERSLink copied to clipboard

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 SPECIFIEDLink copied to clipboard

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`Link copied to clipboard

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 FOUNDLink copied to clipboard

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 MEMBERLink copied to clipboard

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 ADMINISTRATORLink copied to clipboard

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:

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

CTD013E PLEASE ENTER A VALID OPTIONLink copied to clipboard

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 LEVELLink copied to clipboard

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 NAMELink copied to clipboard

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 SYNONYMLink copied to clipboard

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 NAMELink copied to clipboard

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)Link copied to clipboard

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"Link copied to clipboard

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 SCREENLink copied to clipboard

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 REACHEDLink copied to clipboard

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 FOUNDLink copied to clipboard

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`Link copied to clipboard

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:

rc	Explanation
OK	OK
4	End of file. No values for subindex.
8	Error during open
12	Error during close
16	Error during GETMAIN operation
20	Error during FREEMAIN operation
24	Error during dynamic allocation
28	Error during dynamic deallocation
32	Error during load
36	DBO error message
40	Internal error in path tree
44	Internal error during OPENSUB operation
48	Internal error. Path not found for sort record
52	Sort failed
56	GIM error message
60	Two paths with different index names
64	Sort file is full

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 DISPLAYEDLink copied to clipboard

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 NAMELink copied to clipboard

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 VALIDLink copied to clipboard

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 LEVELLink copied to clipboard

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 STOPPEDLink copied to clipboard

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 VALIDLink copied to clipboard

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`Link copied to clipboard

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 J`nnnnn` or J`nnnnnnn`Link copied to clipboard

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`Link copied to clipboard

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`Link copied to clipboard

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 AGAINLink copied to clipboard

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`Link copied to clipboard

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 CTDCMILink copied to clipboard

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`Link copied to clipboard

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 FOUNDLink copied to clipboard

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 VALUESLink copied to clipboard

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`Link copied to clipboard

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

Corrective Action: No action is required.

CTD033E INVALID ORIGINAL SCHEDULING DATELink copied to clipboard

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 ERRORSLink copied to clipboard

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`Link copied to clipboard

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 LENGTHLink copied to clipboard

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 STARTEDLink copied to clipboard

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

Corrective Action: No action is required.

CTD037I GLOBAL INDEX HOUSEKEEPING UTILITY ENDEDLink copied to clipboard

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 FILESLink copied to clipboard

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 ENTRIESLink copied to clipboard

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 LONGLink copied to clipboard

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`Link copied to clipboard

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 SHORTLink copied to clipboard

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`Link copied to clipboard

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 ACTIVELink copied to clipboard

Explanation:Highlighted, unrollable message.

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

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 PARAMETERLink copied to clipboard

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 RECORDLink copied to clipboard

Explanation:Highlighted, unrollable message.

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

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 FULLLink copied to clipboard

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 DATABASELink copied to clipboard

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` "Link copied to clipboard

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 WRITTENLink copied to clipboard

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:

Return Code:	Explanation:
26	Record is not currently being recorded.
40	Buffer storage caused data to be lost.
44	SVC 83 unable to establish recovery.

For the return code, refer to the SMF047S message.

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 SMFWTLLink copied to clipboard

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 ACTIONLink copied to clipboard

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 STARTEDLink copied to clipboard

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"Link copied to clipboard

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.

Corrective Action: Call your INCONTROL administrator.

CTD051S ALL OF THE MISSIONS HAVE ENDED WITH ERRORSLink copied to clipboard

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`Link copied to clipboard

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`Link copied to clipboard

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"Link copied to clipboard

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 EMPTYLink copied to clipboard

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 OKLink copied to clipboard

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 DATELink copied to clipboard

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 ITLink copied to clipboard

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 COMPRESSEDLink copied to clipboard

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-RECORDLink copied to clipboard

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)Link copied to clipboard

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` MISSIONSLink copied to clipboard

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 CALENDARLink copied to clipboard

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"Link copied to clipboard

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`Link copied to clipboard

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 NAMELink copied to clipboard

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 MEMBERLink copied to clipboard

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)Link copied to clipboard

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 SPECIFIEDLink copied to clipboard

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 DAYSLink copied to clipboard

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 SPECIFIEDLink copied to clipboard

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 SPECIFIEDLink copied to clipboard

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 LEVELLink copied to clipboard

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 AGELink copied to clipboard

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 BLANKSLink copied to clipboard

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 SPECIFICATIONLink copied to clipboard

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 BROWSELink copied to clipboard

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 $SYSDATALink copied to clipboard

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.

Messages CTD100 through CTD1xxLink copied to clipboard

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

CTD100I CONTROL-D MONITOR STARTED IN mode MODELink copied to clipboard

Explanation: This general information message is issued when the Control-D monitor is started in one of the following modes:

INT - internal mode
EXT - external mode

Corrective Action: No action is required.

CTD102E INVALID PARM GIVEN TO MONITOR. PARM CAN BE " " OR "1" FOR PRIMARY MONITOR AND "2-9" FOR SECONDARY MONITORSLink copied to clipboard

Explanation:Highlighted, unrollable message.

The value of the PARM field in the Control-D monitor procedure or the secondary monitor procedure is invalid.

The Control-D monitor or the secondary monitor shuts down.

Corrective Action: Check the value defined in the CTDMON# field in CTDPARM. Change the PARM field in the appropriate procedure to correspond to this value and start Control-D.

For example, for the CONTROL2 procedure: //CONTROLD EXEC PGM=CTMMON,PARM=‘2’

CTD103E INVALID MODIFY PARAMETER. VALID PARAMETERS ARE:Link copied to clipboard

Explanation: An invalid parameter was passed to the File Transfer monitor by an operator modify command. A list of valid modify parameters is displayed on the operator console following this message.

The operator modify command is rejected.

Corrective Action: Enter an operator modify command with valid parameters.

CTD107I SHUT DOWN UPON REQUEST FROM OPERATORLink copied to clipboard

Explanation: This information message is a Control-D monitor shut down message when the shut down was requested by the operator.

Control-D monitor shuts down.

Corrective Action: No action is required.

CTD113W CONTROL-D MONITOR SHUTTING DOWN FOR A NEW DAYLink copied to clipboard

Explanation:Highlighted, unrollable message.

Normal message of Control-D monitor shutting down for the New Day procedure.

The Control-D monitor shuts down once a day at a specific time for the New Day procedure. For more information on the New Day procedure, see the Control-D and Control-V User Guide.

Control-D monitor will shut down and start the New Day procedure (CTDNDAY). When it finishes executing, it will start the Control-D monitor again.

Corrective Action: No action is required.

CTD116S OPEN OF ACTIVE MISSIONS FILE FAILED - DDNAME "DAAMF"Link copied to clipboard

Explanation:Highlighted, unrollable message.

Open of Control-D Active Missions file failed (DD statement DAAMF). Possible causes are:

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 it is of another Control-D monitor, or of a different Control-D version.

The Control-D monitor will shut down.

Corrective Action: Correct the JCL for the Control-D monitor.

CTD117S ACTIVE MISSIONS FILE IS BEING FORMATTED NOWLink copied to clipboard

Explanation:Highlighted, unrollable message.

Control-D monitor has been brought up while the Active Missions file is under formatting.

The New Day procedure did not finish formatting the file, either because it was still working, or because it abended. It is impossible to start the Control-D monitor until the New Day procedure finishes executing successfully.

The Control-D monitor shuts down.

Corrective Action: Check how the New Day procedure finished executing. All the problems of the New Day procedure must be corrected before restarting the Control-D monitor. Note, however, that if an IPL occurred during the previous run of the New Day procedure, it will correct itself when restarted. Therefore, it can be restarted without correction.

CTD118S FILE ALLOCATED TO DDNAME "DAAMF" IS NOT THE EXPECTED ACTIVE MISSIONS FILELink copied to clipboard

Explanation:Highlighted, unrollable message.

The data set described by the DAAMF DD statement is not the expected Control-D Active Missions file.

This could be due to one of the following:

The file allocated to the DAAMF DD statement is not the Control-D Active Missions file.
The file allocated to the DAAMF DD statement is the Control-D Active Missions file, but it is of a different version or of a different Control-D monitor.

Control-D monitor will shut down.

Corrective Action: Correct JCL for the Control-D monitor.

CTD119S ACTIVE MISSIONS FILE IS DAMAGED - NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation:Highlighted, unrollable message.

The contents of the Active Missions file have been corrupted.

The Active Missions file is marked as FORMAT during New Day procedure processing, and marked as FREE at successful completion. Currently, the file is not marked as FORMAT, nor as FREE.

Control-D monitor will shut down.

Corrective Action: Call your system programmer for assistance. Examine messages issued during the NEWDAY procedure, take appropriate corrective action, and then rerun the NEWDAY procedure. If the problem recurs, take appropriate action on the Active Mission file: To compress or copy the Active Mission file, use the CTDCAMF utility. To reformat the Active Mission file use the CTDFRAMF utility.

CTD120I CONTROL-D MONITOR SHUTTING DOWNLink copied to clipboard

Explanation:Highlighted, unrollable message.

This information message is a general Control-D message issued when shutting down the Control-D monitor by a P command, or on certain internal Control-D events.

The IOA Log should contain additional messages concerning the reason for shutting down.

Control-D monitor shuts down.

Corrective Action: No action is required.

CTD121S CONTROL-D MONITOR ENDED WITH ERRORLink copied to clipboard

Explanation:Highlighted, unrollable message.

Control-D monitor ended with an error. The IOA Log should contain additional messages concerning the specific error.

Control-D monitor shuts down.

Corrective Action: Check the IOA Log or the computer log for the reason. Call the system programmer for assistance if needed. Try to start the Control-D monitor again as soon as possible.

CTD122W YOUR CONTROL-D IS ALREADY ACTIVE. QNAME `qName`Link copied to clipboard

Explanation:Highlighted, unrollable message.

Corrective Action: No action is required.

CTD123I CONTROL-D INTERVAL IS SET TO `nn` SECONDSLink copied to clipboard

Explanation: This information message is produced as a result of setting a Control-D sleeping interval by an operator command.

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

Control-D monitor will “wake up” every nn seconds and check what it has to do.

Corrective Action: No action is required.

CTD124E INTERVAL MUST BE A TWO DIGIT NUMBER BETWEEN 03-99 SECONDSLink copied to clipboard

Explanation: An invalid Control-D sleeping interval was specified in an operator modify command. The Control-D sleeping interval must be a 2-digit number from 03 through 99 seconds. For more details, see the INCONTROL for z/OS Administrator Guide.

Corrective Action: Enter a valid interval.

CTD125I `validModifyParm`Link copied to clipboard

Explanation: This message displays a valid parameter that can be used in MODIFY.

Corrective Action: No action is required.

CTD126I NEW EXIT `exitName` LOADEDLink copied to clipboard

Explanation: This information message indicates a successful execution of the EXIT REFRESH operator modify command.

A new copy of a Control-D user exit was loaded successfully.

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

Corrective Action: No action is required.

CTD127I NEWDEST COMMAND ACCEPTEDLink copied to clipboard

Explanation: This information message is the result of acceptance of an operator NEWDEST command passed to the Control-D monitor.

The next time that the Control-D monitor tries to SHOUT a message, it will load a new dynamic destination table.

Corrective Action: No action is required.

CTD128S RECIPIENT TREE WAS NOT LOADED BECAUSE OF ERROR - CONTROL-D IS TERMINATINGLink copied to clipboard

Explanation: The loading of the Control-D Recipient Tree was unsuccessful.

As part of its initialization processing, the Control-D monitor attempts to load the Recipient Tree. However, the loading of the Recipient Tree was not successful.

The Control-D monitor will shut down.

Corrective Action: There are additional messages describing the problem on the IOA Log and the system log.

CTD129I ERROR WHILE LOADING EXIT `exitName`. EXIT NOT LOADEDLink copied to clipboard

Explanation: This information message indicates that the Control-D monitor failed to load the exitName user exit.

Common reasons for failure include:

The IOA Load library is in the Linklist, and someone has updated the library without performing a refresh for the LLA.
The last assembly or linkage of exitName failed.
There is insufficient memory to load this exit.

The Control-D monitor will continue to run. However, the exitName user exit will not be activated.

Corrective Action: Check the system log for the reason for the failure.

CTD12AI CONTROL-D MONITOR IS SUSPENDING BY OPERATOR REQUESTLink copied to clipboard

Explanation:Highlighted, unrollable message.

This information message indicates that the Control-D monitor is being suspended while the New Day procedure is running in internal mode.The Control-D monitor is suspended once a day at a specific time for the New Day procedure when it runs in internal mode. For more information on the New Day procedure, see the INCONTROL for z/OS Administrator Guide.

The Control-D monitor suspends all mission processes. When it finishes, message MON12CI is issued.

Corrective Action: No action is required.

CTD12BI CONTROL-D MONITOR IS SUSPENDING BY OPERATOR REQUESTLink copied to clipboard

Explanation:Highlighted, unrollable message.

This information message indicates that the Control-D monitor is being suspending due to an operator request.

The Control-D monitor suspends all mission processes. When it finishes, message MON12CI is issued.

Corrective Action: No action is required.

CTD12CI CONTROL-D MONITOR SUSPENDEDLink copied to clipboard

Explanation:Highlighted, unrollable message.

This information message indicates that the Control-D monitor is being suspended while the New Day procedure is running in internal mode.

The Control-D monitor has started the New Day subtask. When it finishes executing, the monitor will resume and start the New Day procedure (CTDNDAY).

Corrective Action: No action is required.

CTD12DI CONTROL-D MONITOR RESUMEDLink copied to clipboard

Explanation:Highlighted, unrollable message.

This information message indicates that the Control-D monitor has resumed after being suspended for the New Day procedure or by operator request.

The Control-D monitor resumes all mission processes.

Corrective Action: No action is required.

CTD12EI CONTROL-D NEW DAY TIME STAMP IS `timeStamp`Link copied to clipboard

Explanation: This information message indicates that the New Day process has set the timeStamp time stamp as the time of a new day.

The timeStamp timestamp is a hexadecimal representation of the time-of-day clock value used for synchronization for the CTDDELRP utility and for backup missions. It is displayed for tracking and debugging purposes.

For an explanation of the synchronization process, see message MONA59I.

Corrective Action: No action is required.

CTD12FE UNABLE TO UPDATE THE MISSION STATUSLink copied to clipboard

Explanation: The Control-D monitor is unable to update the status of a decollation mission, which was suspended during a New Day procedure that was executing in internal mode. The monitor begins to process such a mission before the New Day procedure begins, but only finishes after the procedure ends. The reason is that the mission was updated outside of the Control-D monitor.

The Control-D monitor continues to run. However, the mission status is not updated.

Corrective Action: Restart the Control-D monitor.

CTD12GS NEWDAY SUBTASK ENDED WITH ERRORLink copied to clipboard

Explanation: A New Day subtask ended with an error or abended.

The Control-D monitor shuts down with user abend 0006.

A dump of the abending task which is needed for problem resolution is also included in the output.

Corrective Action: No action is required.

CTD12HS INVALID NEWDAY MODELink copied to clipboard

Explanation: The incorrect NDAYMODE parameter was specified in the start command for the Control-D monitor or the CTDNDAY procedure.

Valid values are:

INT - internal mode. The Control-D or Control-V monitors execute simultaneously with the New Day procedure.
EXT - external mode. The Control-D monitor starts the New Day procedure, and then shuts down the Control-D monitor or the CTDNDAY procedure.

The Control-D monitor or the CTDNDAY procedure shuts down.

Corrective Action: Restart the Control-D monitor or the CTDNDAY procedure with the correct parameter.

CTD130I COMMAND `cmd` ACCEPTED FOR PRINTER `prtr`Link copied to clipboard

Explanation: This information message indicates acceptance of an operator STARTPRT or STOPPRT command passed to the Control-D monitor.

The requested printer is opened (started) or closed (stopped).

Corrective Action: No action is required.

CTD131I TREE WAS NOT LOADED BECAUSE IT IS IN USE BY ONE OF THE SUBTASKS - TRY AGAIN LATERLink copied to clipboard

Explanation: This information message is a result of an operator LOADTREE command passed to the Control-D monitor.

The Recipient Tree is used by several subtasks of the Control-D monitor. One of the subtasks had exclusive control of the Recipient Tree for a short period of time.

The new Recipient Tree is not loaded. Control-D continues using the old Recipient Tree.

Corrective Action: Try to load a new Recipient Tree later.

CTD132E PRINTER `prtr` IS NOT DEFINED TO CONTROL-DLink copied to clipboard

Explanation: Result of an operator STARTPRT or STOPPRT command passed to the Control-D monitor.

The PRINTER Control-D Installation Parameter defines the logical printers on which Control-D can print. However, the prtr printer name is not defined in the PRINTER Installation Parameter.

The requested STARTPRT or STOPPRT function is not performed.

Corrective Action: Enter the correct printer name in the STARTPRT or STOPPRT command.

CTD133I STARTING THE CONTROL-D PRINTERS CONTROL-MONITOR - `prtr`Link copied to clipboard

Explanation: This information message is issued during normal initialization processing in the Control-D monitor.

The Control-D monitor activates the Printers Control monitor prtr as an independent started task.

The Control-D monitor invokes the prtr started task. This name is taken from the PRTSTC Control-D Installation Parameter.

Corrective Action: No action is required.

CTD134I WAITING FOR THE CONTROL-D PRINTERS CONTROL-STC (`name`) TO STARTLink copied to clipboard

Explanation: This information message indicates that the Printers Control monitor has been activated by the Control-D monitor.

The Control-D monitor waits for the Printers Control started task to start executing. This message can appear more than once. If, after a number of times, the Control-D monitor cannot find the Printers Control monitor, it assumes that it has failed and the Control-D monitor shuts down.

Corrective Action: No action is required.

CTD135E CONTROL-D PRINTERS CONTROL-MONITOR `monName` ENDED ABNORMALLY. CONTROL-D SHUTTING DOWNLink copied to clipboard

Explanation:Highlighted, unrollable message.

The Printers Control monitor monName was shut down due to errors.

The Control-D monitor will shut down.

Corrective Action: Check the IOA Log for additional clarification messages on the reason for the shutdown.

CTD136I STOPPING THE PRINTERS CONTROL-MONITORLink copied to clipboard

Explanation: This information message indicates that a shutdown process has been issued from the Control-D monitor.

Before the Control-D monitor shuts itself down, it will shut down the Printers Control monitor first.

Control-D will shut down.

Corrective Action: No action is required.

CTD137I WAITING FOR THE PRINTERS CONTROL-STC (`name`) TO TERMINATELink copied to clipboard

Explanation: This information message indicates that a shutdown process has been issued from the Control-D monitor.

The Control-D monitor has issued the command to shut down the Printers Control monitor, and is now waiting for a response. This message can appear more than once, but not more than 10 times.

Corrective Action: No action is required.

CTD138E WAITING TOO LONG FOR THE PRINTERS CONTROL-STC (`name`). STC BEING CANCELLEDLink copied to clipboard

Explanation:Highlighted, unrollable message.

A shutdown process issued from the Control-D monitor.

The Control-D monitor has issued the command to the Printers Control monitor to shut itself down, but there was no response from the Printers Control monitor.

The Printers Control monitor is cancelled (operator command C name).

Corrective Action: Check the system log, the IOA Log, and the JCL of the Control-D monitor and the Printers Control monitor.

CTD139I GENERIC JOB DECOLLATION IS ACTIVE ON CLASSES (`classList`)Link copied to clipboard

Explanation: This information message indicates that the Generic decollation from the classList Generic classes is now active. The Control-D monitor issues this message when starting, after new day processing and after successfully executing the STARTGEN command.

Control-D will start decollating sysouts from the classList Generic classes. For more information, see the description of generic processing in the INCONTROL for z/OS Administrator Guide.

Corrective Action: No action is required.

CTD13AE GENERIC DECOLLATION CANNOT BE ACTIVATED. GENCLAS IS NOT DEFINED IN CTDPARMLink copied to clipboard

Explanation: The operator issued the command F CONTROLD,STARTGEN but no generic classes were defined in CTDPARM.

The command is ignored.

Corrective Action: For details on specifying generic classes in CTDPARM, see the Control-D chapter of the INCONTROL for z/OS Installation Guide and proceed accordingly.

CTD13BI PRINTER `prtrId` DEST `dest` TYPE `type` IS OPENLink copied to clipboard

Explanation: This information message indicates that the prtrId logical printer has opened following a STARTPRT command issued by the operator.

The variables in this message are:

prtrId - the identity of the logical printer that has opened
dest - the value of the Dest Printer Definition parameter
type - the value of the Type Printer Definition parameter

For more information on these Printer Definition parameters, see the Control-D chapter of the INCONTROL for z/OS Installation Guide.

Corrective Action: No action is required.

CTD13CI STOPPING THE MONITOR `monName`Link copied to clipboard

Explanation: This information message is issued when the monitor stops as a result of receiving the modify command /F CONTROLD,STOP=monName.

Corrective Action: No action is required.

CTD13DE THE MONITOR `monName` WAS NOT ORIGINALLY ACTIVE.Link copied to clipboard

Explanation: The modify command /F CONTROLD,STOP=monName was issued, but the monName monitor was not activated when Control-D started.

Control-D cannot start a new monitor that was not activated when Control-D started.

The new monitor is not started.

Corrective Action: Correct the value of monName in the modify command.

CTD13EI MQ DECOLLATION IS ACTIVELink copied to clipboard

Explanation: This information message indicates a successful execution of the STARTMQ operator modify command.

MQ decollation for MQ Queues is now active.

Corrective Action: Control-D will start decollating messages from MQ Queues.

CTD140I GENERIC JOB DECOLLATION IS BEING DEACTIVATEDLink copied to clipboard

Explanation: This information message indicates a successful execution of the STOPGEN operator modify command.

Deactivation of Generic decollation from all Generic classes is in process.

Control-D will not start new decollations from Generic classes. Currently executing (decollating) missions will finish the processing of jobs whose output processing has already started.

Corrective Action: No action is required.

CTD141I STARTING THE SECONDARY CONTROL-D MONITOR `monName`Link copied to clipboard

Explanation: This information message is a normal start message for initialization processing of the monName Control-D monitor.

The Control-D monitor activates the secondary monitor as an independent started task.

The Control-D monitor invokes the started task name, CONTROL?, where ? indicates the number of the monitor.

Corrective Action: No action is required.

CTD142I WAITING FOR THE SECONDARY CONTROL-D MONITOR `monName` TO STARTLink copied to clipboard

Explanation: This information message indicates that although a start command has been issued by the Control-D monitor, the monName Control-D secondary monitor has not yet started.

This is due to one of the following:

JES queues are busy.
The secondary monitor procedure does not exist in the procedure library (PROCLIB).
There is a JCL error in the secondary monitor procedure.

If this situation is not corrected, the Control-D monitor makes up to eight (8) attempts to initialize. After eight (8) unsuccessful attempts, the Control-D monitor shuts down.

Corrective Action:

If JES queues are busy, no action is required.
If there is a problem with the secondary monitor procedure, correct it, and start Control-D.

CTD143E SECONDARY CONTROL-D MONITOR `monName` ENDED ABNORMALLY. Control-D SHUTTING DOWNLink copied to clipboard

Explanation:Highlighted, unrollable message.

The monName secondary Control-D monitor ended with errors. The IOA Log should contain additional messages concerning specific errors.

The Control-D monitor and the monName secondary monitor shut down.

Corrective Action: Check the IOA Log and the system log for the cause of the problem. If necessary, call the system programmer for assistance. Try to start the Control-D monitor again as soon as possible.

CTD144I WAITING FOR CONTROL-D SECONDARY MONITOR `monName` TO TERMINATELink copied to clipboard

Explanation: This information message indicates that a shutdown process command was issued from the Control-D monitor.

The Control-D monitor has issued a shutdown command to the secondary monitor monName, and is now waiting for the secondary monitor to shut down. This message may appear more than once. The secondary monitor will shut down at the end of the currently executing decollation.

Corrective Action: No action is required.

CTD145E LIBRARY= `libName` MEMBER= `memName` CONTAINS INVALID DATALink copied to clipboard

Explanation: The memName member in the libName library, which should contain a mission definition, actually contains improper mission identification data. The erroneous data card is displayed in message CTD032E, which follows this message.

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

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

CTD145I UNABLE TO READ THE MEMBER CTDPLEX FROM THE CTD PARM LIBRARY. RC= `rc`. THE SYSPLEX OPTION IS NOT ACTIVE.Link copied to clipboard

Explanation: The CTDPLEX member was not found in the Control-D PARM library.

In this message, rc is the error return code. For more information on these codes, see the description of IOAMEM in the INCONTROL for z/OS Administrator Guide.

The use of multiple monitors using SYSPLEX support is not activated.

Corrective Action: Ensure that the CTDPLEX member is present in the Control-D PARM library.

CTD145S type MISSION `missionName` CONTAINS INVALID DATALink copied to clipboard

Explanation: There is a mismatch between the mission type identified in the message to be processed, and the mission data contained in missionName. For instance, the user attempted to schedule a printing mission, but the mission data contains backup data.

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

Processing of all mission order list statements stops. The New Day procedure ends with a return code of 08.

Correct any incorrect mission statements and rerun the New Day procedure. Make sure you only run the New Day procedure once.

Corrective Action: No action is required.

CTD146I MQ DECOLLATION IS BEING DEACTIVATEDLink copied to clipboard

Explanation: This information message indicates a successful execution of the STOPMQ operator modify command.

Deactivation of MQ decollation from all MQ QUEUES is in process.

Corrective Action: Control-D will not start new decollations from MQ QUEUES, although currently existing decollating missions will finish the processing of messages whose output processing has already begun.

CTD146S INVALID DATA IN THE "PARM" FIELDLink copied to clipboard

Explanation: There is an error in the parameter input to the CTDRRQ, CTDPRQ, CTDBRQ, or CTDSRQ program.

This message is issued by:

CLISTs that schedule missions manually - The supplied CLIST was incorrectly modified. For more information, see the INCONTROL for z/OS Administrator Guide.
New Day procedure - The supplied JCL procedures were incorrectly modified. For more information, see New Day processing in the INCONTROL for z/OS Administrator Guide.

Processing of all mission data stops. The New Day procedure ends with return code 08.

Corrective Action: Correct the CLIST or job and rerun.

CTD147E INVALID PARAMETER PASSED TO CTDMIS - NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: Internal error in the CTDMIS module.

This message is issued by:

CLISTs that schedule missions manually. For more information, see the INCONTROL for z/OS Administrator Guide.
New Day procedure. For more information, see New Day processing in the INCONTROL for z/OS Administrator Guide.

The Active Missions file is not updated. The module ends with return code 08.

Corrective Action: Notify your IOA administrator.

CTD147I CONTROL-D MONITOR RESTARTED IN `nday_mode` MODELink copied to clipboard

Explanation: This is a general information message that is issued when the Control-D monitor is restarted on a new LPAR in the specified NEWDAY procedure mode nday_mode.

The valid values are:

INT - internal mode
EXT - external mode.

Corrective Action: No action is required.

CTD148E INVALID RETURN CODE FROM CTDMIS - NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: The CTDMIS module has an internal error.

This message is issued by:

CLISTs that schedule missions manually.
New Day procedure.

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

The Active Missions file is not updated. The module issues return code 08.

Corrective Action: Call your IOA administrator.

CTD148I CONTROL-D MONITOR SHUTTING DOWN FOR RESTARTLink copied to clipboard

Explanation: Highlighted, unrollable message. This information message is a general Control-D message issued when shutting down the Control-D monitor by a RESTART command.

Control-D monitor shuts down, then restarts on a new LPAR.

Corrective Action: No action is required.

CTD149E ERROR IN MISSION ORDER LISTLink copied to clipboard

Explanation: There is an error in a mission order list entry. The preceding message describes the error.

Processing of the other mission order list statements continues. The New Day procedure ends with a return code of 04.

Corrective Action: Check the preceding error message. Correct the error, then rerun the New Day procedure.

CTD14BI NUMBER OF DECOLLATION MONITORS FOR GENERIC PROCESS WILL BE CHANGED AUTOMATICALLYLink copied to clipboard

Explanation: Control-D will automatically change the number of active Control-D decollation monitors based on the number of JOBs in the JES spool that are waiting for decollation in the generic class.

Corrective Action: No action is required.

CTD14CW GENJOBM >= GENJOBX. QUEUE IN JES SPOOL WILL NOT BE CHECKED FOR CHANGING NUMBER OF DECOLLATION MONITORS FOR GENERIC PROCESSLink copied to clipboard

Explanation: Parameter GENJOBM (Threshold of QUEUE size to stop a secondary Control-D monitor) is bigger than GENJOBX (Threshold of QUEUE size to start a secondary Control-D monitor). Control-D will not automatically change the number of active Control-D decollation monitors.

Corrective Action: Correct GENJOBM and/or GENJOBX and restart the Control-D monitor.

CTD14DW QUEUE IN JES SPOOL IS TOO LONG. INCREASE NUMBER OF DECOLLATION MONITORS FOR GENERIC PROCESS IN PARAMETER CTDMON#Link copied to clipboard

Explanation: Based on queue size, Control-D tries to start a secondary Control-D monitor for generic process. However, the maximum number of secondary monitors was reached.

Corrective Action: Increase the number of Control-D monitors in parameter CTDMON# in CTDPARM.

CTD14EE THE NUMBER OF MONITORS IS CHANGED AUTOMATICALY. RESTART COMMAND IS REJECTEDLink copied to clipboard

Explanation: Control-D monitor rejected the RESTART command to restart itself because the number of active Control-D decollation monitors was automatically changed.

Corrective Action: No action is required.

CTD14FE MONITOR IS NOT STARTED ON LPAR `lpar_name.` RESTART COMMAND IS REJECTEDLink copied to clipboard

Explanation: The Main Control-D monitor has not started successfully on the new LPAR after the RESTART command. The monitor continues to work on the current LPAR.

Corrective Action: Check error messages on the new LPAR, fix the problem, and repeat the RESTART command.

CTD14GI WAITING FOR THE CONTROL-D MONITOR TO RESTART ON LPAR `lpar_name`Link copied to clipboard

Explanation: The old Main Control-D monitor is waiting for the new one to start successfully on the new LPAR after the RESTART command. If it starts, the old monitor shuts down. If it does not start, the old monitor continues to work on the current LPAR.

Corrective Action: No action is required.

CTD14HI RESTART IS WAITING FOR SYNCHRONIZATION FOR BACKUP/CTDDELRP/NEWDAYLink copied to clipboard

Explanation: The Main Control-D monitor has received a RESTART command, but one of the BACKUP/CTDDELRP/NEWDAY processes are executing. The RESTART command will be processed after the other process has finished.

Corrective Action: No action is required.

CTD14IE RESTART OF MONITOR FAILED ON NEW LPAR BECAUSE `parmname` IS CHANGEDLink copied to clipboard

Explanation: The Main Control-D monitor is not started successfully on the new LPAR after the RESTART command because the parmname parameter of the CTDPARM member was changed. The monitor continues to work on the current LPAR.

Corrective Action: Restore the CTDPARM member to the status of the starting of the Control-D monitor and repeat the RESTART command.

CTD14JE RESTART OF MONITOR FAILED ON NEW LPAR BECAUSE I/O AUF ERRORLink copied to clipboard

Explanation: The Main Control-D monitor is not started successfully on the new LPAR after the RESTART command because of an I/O error for the Active User File. The monitor continues to work on the current LPAR.

Corrective Action: See the preceding CTDU99E message.

CTD14KE THE SYSPLEX OPTION IS NOT ACTIVE. RESTART COMMAND IS REJECTED.Link copied to clipboard

Explanation: Control-D monitor rejected the RESTART command to restart a monitor on another LPAR because the z/OS SYSPLEX option is not active.

Possible reasons are:

CTDPLEX member is missing in the CTD PARM library.
ENABLE=NO is defined in the CTDPLEX member.
LPAR name specified for the secondary decollation monitor or Print monitor is not specified in the CTDPLEX member for this monitor.
SYSPLEX is really inactive.

Corrective Action: No action is required.

CTD14LE MONITOR `monName` IS NOT ACTIVE. RESTART COMMAND IS REJECTED.Link copied to clipboard

Explanation: The Restart command failed because the Control-D monitor is currently not active.

Corrective Action: Activate the Control-D monitor and then try again.

CTD14ME LPAR `lpar_name` IS NOT DEFINED IN CTDPLEX FOR THIS MONITORLink copied to clipboard

Explanation: Control-D monitor rejected the RESTART command to restart the monitor on another LPAR, because LPAR lpar_name is not specified for this monitor.

Corrective Action: Use only those LPARs that are defined for this monitor in CTDPLEX.

CTD151S OPEN OF RECIPIENT TREE MEMBER FAILED - DDNAME "DATREE"Link copied to clipboard

Explanation: An attempt to open the Recipient Tree definition member failed.

Possible causes are:

The DATREE DD statement is missing.
The file allocated to the DATREE DD statement is not the Control-D Recipient Tree.
The attempt to open the tree member referenced by the DATREE DD statement failed.

This message can be produced in the following situations:

Initialization of the Control-D monitor and Printers Control monitor: The Control-D monitor will shut down.
Security checking in the Online User Report List screen: The user will not be able to enter the User Report List screen.
Using the KeyStroke Language (KSL) scripts: The job will end with errors. KSL reports will not be produced.
Issuing Control-D operator command LOADTREE to a Control-D component: The new Recipient Tree will not be loaded. Control-D (or another component) will continue using the “old” Recipient Tree.

Corrective Action:

Initialization of the Control-D monitor and Printers Control monitor: Modify the JCL procedure (CONTROLD/ CTDPRINT) the DATREE DD statement to point to the correct library and member, and bring up Control-D.
Security checking in the Online User Report List screen:Modify the CLIST (CTDISPF, CTMISPFD, DMAN, ROSDMAN, ROSTMAND, TMAND) the DATREE DD statement to point to the correct library and member, exit from the Control-D Online Facility, and reenter the Online Facility.
The KeyStroke Language: Modify the JCL procedure (CTDRKSL/ CTMRKSLD) to point to the correct library and member name, and rerun the job.
The Control-D operator command LOADTREE was issued: Modify the Recipient Tree using the Online Recipient Tree Definition screen, and re-enter the LOADTREE operator command.

CTD152E PARENT `parent` OF RECIPIENT `recip` IS NOT IN THE TREE OR PARENT LEVEL IS INCORRECT - RECIPIENT IGNOREDLink copied to clipboard

Explanation: The recipient entry with the name and level specified in the parent name and parent level fields is not found in the Recipient tree.

Control-D has searched the entire tree and failed to find the parent name specified for the new recipient.

This message can be produced in the following situations:

when entering the Online User Report List screen
the KeyStroke Language
the Control-D operator command LOADTREE was issued
the IOAOMON1 operator command LOADTREE was issued
when IOAOMON1 is initialized
when saving an edited tree
when executing the CHECK command to verify the tree
during the initialization of the Control-D monitor and Printers Control monitor

The loading of the Recipient Tree will continue. However, this particular recipient will not become part of the Recipient Tree.

Corrective Action: Correct the parent name in the Recipient Tree using the Online Recipient Tree Definition screen. Depending on the situation, take one of the following actions:

Initialization of the Control-D monitor and Printers Control monitor: Issue a LOADTREE operator command to load in the new Recipient Tree.
Entering the Online User Report List screen: Exit from the Control-D Online Facility, and re-enter the Online Facility.
The KeyStroke Language: Rerun the job.
The Control-D operator command LOADTREE was issued: Re-enter the LOADTREE operator command.
The IOAOMON1 operator command LOADTREE was issued: Re-enter the LOADTREE operator command.
When IOAOMON1 is initialized: Issue a LOADTREE operator command for IOAOMON1.
When saving an edited tree: Correct the tree and resave.
When executing a CHECK command: Correct the tree and re-issue the command.

CTD153E INVALID LEVEL `lvl` OF RECIPIENT `recip` - RECIPIENT IGNOREDLink copied to clipboard

Explanation: An invalid Recipient Tree level has been entered.

The Recipient Tree levels are installation defined (the CTDPARM member). The valid levels are displayed at the top of the Control-D Recipient Tree screen. This message can be produced under in one of the following situations:

when entering the Online User Report List screen
the KeyStroke Language
the Control-D operator command LOADTREE was issued
the IOAOMON1 operator command LOADTREE was issued
when IOAOMON1 is initialized
when saving an edited tree
when executing the CHECK command to verify the tree
during the initialization of the Control-D monitor and Printers Control monitor

The loading of the Recipient Tree will continue. However, this particular recipient will not become part of the Recipient Tree.

Corrective Action: Enter a valid Recipient Tree level in the Recipient Tree using the Online Recipient Tree Definition screen. Depending on the situation, take one of the following actions:

Initialization of the Control-D monitor and Printers Control monitor: Issue a LOADTREE operator command to load in the new Recipient Tree.
Entering the Online User Report List screen: Exit from the Control-D Online Facility, and re-enter the Online Facility.
The KeyStroke Language: Rerun the job.
The Control-D operator command LOADTREE was issued: Re-enter the LOADTREE operator command.
The IOAOMON1 operator command LOADTREE was issued: Re-enter the LOADTREE operator command.
When IOAOMON1 is initialized: Issue a LOADTREE operator command for IOAOMON1.
When saving an edited tree: Correct the tree and resave.
When executing a CHECK command: Correct the tree and re-issue the command.

CTD154S INSUFFICIENT MEMORY TO LOAD THE RECIPIENT TREE - LOADING ABORTEDLink copied to clipboard

Explanation: Insufficient memory to load the Recipient Tree.

The loading of the Recipient Tree is aborted. This message can be produced in the following situations:

Initialization of the Control-D monitor and Printers Control monitor: The Control-D monitor will shut down.
Security checking in the Online User Report List screen: The user will not be able to enter the Online Recipient Tree Definition screen.
The KeyStroke Language: The job will end with errors. KSL reports will not be produced.
The Control-D operator command LOADTREE was issued: The new Recipient Tree will not be loaded. Control-D will continue using the “old” Recipient Tree.

Corrective Action:

Initialization of the Control-D monitor and Printers Control monitor: Increase the REGION parameter of the Control-D monitor and Printers Control monitor - JCL procedures CONTROLD and CTDPRINT.
Security checking in the Online User Report List screen: Log on again using a larger SIZE parameter.
The KeyStroke Language: Increase the REGION parameter of the job, and rerun.
The Control-D operator command LOADTREE was issued: Increase the REGION parameter of the Control-D monitor and Printers Control monitor - JCL procedures CONTROLD and CTDPRINT. Bring down Control-D, and then up again.

CTD155S THE RECIPIENT TREE IS EMPTY. LOADING ABORTEDLink copied to clipboard

Explanation: The Recipient Tree is empty. Loading is aborted.

The Recipient Tree must be defined using the Installation Parameters. This message can be produced in the following situations:

Initialization of the Control-D monitor and Printers Control monitor: The Control-D monitor will shut down.
Security checking in the Online User Report List screen: The user will not be able to enter the Online Recipient Tree Definition screen.
The KeyStroke Language: The job will end with errors. KSL reports will not be produced.
The Control-D operator command LOADTREE was issued: The new Recipient Tree will not be loaded. Control-D will continue using the “old” Recipient Tree.

Corrective Action: Delete this Recipient Tree member from the library, then generate a new Recipient Tree using the Online Recipient Tree Definition screen. Depending on the situation, take one of the following actions:

Initialization of the Control-D monitor and Printers Control monitor: Bring up the Control-D monitor.
Security checking in the Online User Report List screen: Exit from the Control-D Online Facility, and re-enter the Online Facility.
The KeyStroke Language: Rerun the job.
The Control-D operator command LOADTREE was issued: Re-enter the LOADTREE operator command.

CTD156E USER "DEMO" IS RESERVED FOR CONTROL-DLink copied to clipboard

Explanation: There is an attempt to add the user DEMO to the Control-D recipient tree. The Control-D environment reserves user name DEMO for demonstration and training purposes. It may not be specified as a user in the production system.

The operation is not performed.

Corrective Action: Specify a different user name to be added.

CTD157E INVALID LEVEL `lvl` OF PARENT `parent` IN RECIPIENT `recip`Link copied to clipboard

Explanation: The Recipient Tree level entered for the parent of this recipient is invalid.

The valid levels are displayed at the top of the Recipient Tree screen. This message can be produced in the following situations:

during the initialization of the Control-D monitor and Printers Control monitor
when entering the Online User Report List screen
the KeyStroke Language
the Control-D operator command LOADTREE was issued
the IOAOMON1 operator command LOADTREE was issued
when IOAOMON1 is initialized
when saving an edited tree
when executing the CHECK command to verify the tree

The loading of the Recipient Tree will continue. However, this particular recipient will not become part of the Recipient Tree.

Corrective Action: Correct the level for the parent using the Online Recipient Tree Definition screen. Depending on the situation, take one of the following actions:

Initialization of the Control-D monitor and Printers Control monitor: Issue a LOADTREE operator command to load in the new Recipient Tree.
Entering the Online User Report List screen: Exit from the Control-D Online Facility, and re-enter the Online Facility.
The KeyStroke Language: Rerun the job.
The Control-D operator command LOADTREE was issued: Re-enter the LOADTREE operator command.
The IOAOMON1 operator command LOADTREE was issued: Re-enter the LOADTREE operator command.
When IOAOMON1 is initialized: Issue a LOADTREE operator command for IOAOMON1.
When saving an edited tree: Correct the tree and resave.
When executing a CHECK command: Correct the tree and re-issue the command.

CTD158E LEVEL `lvl` OF THE PARENT `parent` IS LOWER THAN THE LEVEL OF RECIPIENT `recip`Link copied to clipboard

Explanation: The level of the parent of the recipient is lower than the level of the recipient being defined.

The level of the parent must be higher than the level of the “child.” (Note that the order can be seen in the Recipient Tree Entry screen).

Corrective Action: Enter a parent name with a different level or give the recipient a lower level.

CTD159E ERROR IN FREEMAIN OF PREVIOUS TREE, LOADING OF NEW TREE CONTINUEDLink copied to clipboard

Explanation: The freeing of the memory for the previous Recipient Tree failed.

The Control-D operator command LOADTREE was issued in order to load in a new Recipient Tree. After loading memory for the “new” Recipient Tree, Control-D attempts to free the memory assigned to the “old” Recipient Tree.

The loading of the “new” Recipient Tree will be accepted. However, the memory allocated to the “old” tree will not be freed until Control-D is shut down.

Corrective Action: No action is required.

CTD160I CONTROL-D RECIPIENT TREE LOADED - `num` RECIPIENTSLink copied to clipboard

Explanation: This information message indicates that the Recipient Tree was successfully loaded.

Corrective Action: No action is required.

CTD161E RECIPIENT `recip` ALREADY IN TREE - CURRENT RECIPIENT ENTRY IGNOREDLink copied to clipboard

Explanation: The recipient entered is already in the Recipient Tree. The current recipient entry is ignored.

A recipient name (not synonym) can only appear once in the Recipient Tree. This message can be produced in the following situations:

when entering the Online User Report List screen
the KeyStroke Language
the Control-D operator command LOADTREE was issued
the IOAOMON1 operator command LOADTREE was issued
when IOAOMON1 is initialized
when saving an edited tree
when executing the CHECK command to verify the tree
during the initialization of the Control-D monitor and Printers Control monitor

The loading of the Recipient Tree will continue. However, this particular recipient will not become part of the Recipient Tree (the first one will).

Corrective Action: Delete the duplicate recipient using the Online Recipient Tree Definition screen. Depending on the situation, take one of the following actions:

Initialization of the Control-D monitor and Printers Control monitor: Issue a LOADTREE operator command to load in the new Recipient Tree.
Entering the Online User Report List screen: Exit from the Control-D Online Facility, and re-enter the Online Facility.
The KeyStroke Language: Rerun the job.
The Control-D operator command LOADTREE was issued: reenter the LOADTREE operator command.
The IOAOMON1 operator command LOADTREE was issued: Re-enter the LOADTREE operator command.
When IOAOMON1 is initialized: Issue a LOADTREE operator command for IOAOMON1.
When saving an edited tree: Correct the tree and resave.
When executing a CHECK command: Correct the tree and re-issue the command.

CTD163E MAXIMUM NUMBER OF PC USERS IS EXCEEDED. PC INFO FOR USER `usr` IS IGNOREDLink copied to clipboard

Explanation: The number of users authorized for PC file transfer exceeds the maximum number of PC users defined in the PASDPC member in the IOA PARM library.

Maximum number of PC users in PARM library is defined at the time the license is received to use Control-D/WebAccess Server.

All users over maximum will not be able to use file transfer option.

Corrective Action: Set AUTHORIZED TO USE PC to N for some users in screen T, or obtain a new license with a greater number of PC users.

CTD177E INVALID LEVEL `lvl` OF PARENT `parent` IN APPROVAL `approval`Link copied to clipboard

Explanation: The Approval Tree level entered for the parent of this Approval name is invalid.

The valid levels are displayed at the top of the Approval Tree screen. This message can be produced in the following situations:

during the initialization of the Control-D monitor and Printers Control monitor
when entering the Online User Report List screen
the KeyStroke Language
the Control-D operator command LOADTREE was issued
the IOAOMON1 operator command LOADTREE was issued
when IOAOMON1 is initialized
when saving an edited tree
when executing the CHECK command to verify the tree

The loading of the Approval Tree will continue. However, this particular Approval name will not become part of the Approval Tree.

Corrective Action: Correct the level for the parent using the Online Approval Tree Definition screen. Depending on the situation, do as shown in the following table:

When Message Issued	User Response
During initialization of the Control-D monitor and Printers Control monitor	Issue a LOADTREE operator command to load in the new Approval Tree.
When entering the Online User Report List screen	Exit from the Control-D Online Facility, and reenter the Online Facility.
The KeyStroke Language	Rerun the job.
When the Control-D operator command LOADTREE was issued	Reenter the LOADTREE operator command.
When the IOAOMON1 operator command LOADTREE was issued	Reenter the LOADTREE operator command.
When IOAOMON1 is initialized	Issue a LOADTREE operator command for IOAOMON1.
When saving an edited tree	Correct the tree and resave.
When executing a CHECK command to verify the tree	Correct the tree and reissue the command.

TRECTD1T0I FILE TRANSFER STARTEDLink copied to clipboard

Explanation: This information message indicates that the File Transfer monitor was started.

Corrective Action: No action is required.

CTD1T3E INVALID MODIFY PARAMETER. VALID PARAMETERS ARE:Link copied to clipboard

The modify command is rejected.

Corrective Action: Enter an operator modify command with valid parameters.

CTD1T4S BLDL/ATTACH FAILED FOR TASK `taskName`Link copied to clipboard

Explanation: Initialization of a File Transfer monitor internal task failed. The reason, system code, is on the computer log. Possible causes are:

The task is not in the IOA Load library.
There is insufficient memory for File Transfer monitor.

The File Transfer monitor shuts down.

Corrective Action: Refer to your system programmer for assistance. If necessary, increase the monitor REGION size.

CTD1T5S UNRECOVERABLE ERROR ENCOUNTEREDLink copied to clipboard

Explanation: An unrecoverable error occurred during operation of the File Transfer monitor, while trying to access to the Active Transfer file.

The File Transfer monitor shuts down.

Corrective Action: Examine relevant CTD9B1S-CTD9B9S messages, and take appropriate corrective action. If the problem is not resolved, send the IOA log and the CTDFTM file transfer monitor print-out to BMC Customer Support.

Messages CTD200 through CTD2xxLink copied to clipboard

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

CTD200I CTDCBTR STARTED.Link copied to clipboard

Explanation: This information message indicates that the CTDCBTR Control-D utility has started.

Corrective Action: No action is required.

CTD201I CTDCBTR ENDED OK.Link copied to clipboard

Explanation: This information message indicates that the CTDCBTR Control-D utility has ended normally.

Corrective Action: No action is required.

CTD202S INSUFFICIENT MEMORY FOR CONTROL-D MONITOR.Link copied to clipboard

Explanation: Insufficient memory for the initiation of Control-D monitor.

Control-D monitor will shut down.

Corrective Action: Increase the Control-D monitor region size.

CTD202S CTDCBT ENDED WITH ERRORS.Link copied to clipboard

Explanation: The CTDCBTR Control-D utility ended with errors.

The utility stops executing.

Corrective Action: Check the job sysout for any error messages, and correct the problem accordingly. Rerun the job.

CTD203S DELETE FAILED FROM BTR FILELink copied to clipboard

Explanation: The CTDCBTR utility failed to delete a record from the Bundle Tracking (BTR) file.

The CTDCBTR utility terminates.

Corrective Action: Check for other messages relating to this problem, and correct accordingly. Rerun the utility.

CTD204S PROBLEM DETECTED IN UTILITY CTDCBTR PARAMETERS.Link copied to clipboard

Explanation: A problem was detected in the input parameters of the CTDCBTR utility. This message can be triggered by a number of causes, for example, if no parameters were specified at all, or if the DABTRIN DD statement is absent.

The CTDCBTR utility ends.

Corrective Action: Check the parameters specified for the utility, and check for a DABTRIN DD statement. Correct the input accordingly and rerun the job.

CTD205I NUMBER OF DELETED RECORDS: `num`Link copied to clipboard

Explanation: This information message indicates the number of records deleted by the CTDCBTR utility.

Corrective Action: No action is required.

CTD206I INPUT CARDS: `inputStmts`.Link copied to clipboard

Explanation: This information message displays the input parameters which were specified in the JES log of the job for the CTDCBTR utility.

Corrective Action: No action is required.

CTD207E REDUNDANT PARAMETER: `inputStmt`.Link copied to clipboard

Explanation: A superfluous parameter was specified for the CTDCBTR utility.

The CTDCBTR utility ends.

Corrective Action: Remove the superfluous input parameter and rerun the utility.

CTD229S OPEN FAILED FOR DDNAME "DARES".Link copied to clipboard

Explanation: Open of a debugging output file failed (the DARES DD statement).

This is probably because the DARES DD statement is missing in the Control-D procedure.

Control-D monitor will shut down with error message.

Corrective Action: Correct the JCL for the Control-D monitor procedure and start it again.

CTD230S OPEN FAILED FOR DDNAME "DARESC" OR "DASINC".Link copied to clipboard

Explanation: Open of IOA Conditions file failed (the DARESC DD statement or the DASINC DD statement).

Possible causes are:

The DARESC DD statement is missing.
The DASINC DD statement is missing.
The data set described by the DARESC DD statement is not the IOA Conditions file.
The data set described by the DASINC DD statement is not the IOA Conditions synchronization file.
The data set described by the DARESC DD statement is the IOA Conditions file, but it is of a different version or of a different Control-D monitor.

Control-D monitor shuts down with error message.

Corrective Action: Correct the JCL for the Control-D procedure, and start the procedure again.

CTD241W OUTPUT CONDITION `cond_date` NOT UPDATED - NO MORE SPACE. NOTIFY THE IOA ADMINISTRATOR.Link copied to clipboard

Explanation:Highlighted, unrollable message.

No more space to add output conditions to the conditions file. The date is in mmdd format.

The record for that specific day of the month is full. For example, if a condition with date reference of January 3rd cannot be added, an entry in the Conditions file that contains conditions for January 3rd, February 3rd, March 3rd, and so on, is full.

The condition is not added, and a highlighted message is displayed on the operator console. Control-D continues to function, but missions that depend on the condition are not submitted.

Corrective Action:

Immediate action:

Enter Control-D Online Facility Resource Map (screen 4). By changing the date range limit, look for conditions with the same day (but of a different month) as the condition that could not be added, and delete them manually - providing that they are not needed.
Add the failing condition manually in order to maintain production flow.
Report the event to your system programmer.

Long term action:

You should run the IOACLCND Control-M utility more often.
You may want to increase the record length of the IOA Conditions file. For more information on how to do this, see the section on expanding IOA files in the INCONTROL for z/OS Administrator Guide.

CTD256E ERROR WHILE READING SYSOUT FROM SPOOL OR FROM CDAM FILESLink copied to clipboard

Explanation: Internal Control-D error.

The status of this decollating mission is set to ENDED NOTOK.

Corrective Action: Look for additional messages on the IOA Log. Call BMC Customer Support for assistance.

CTD260E ERROR IN ACTIVE USER REPORTS LIST FILE. USER UPDATE FAILED.Link copied to clipboard

Explanation: The update to the Active User Report List file failed. Perhaps the Active User Report List file is full or the Index component is corrupted.

The status of this decollating mission is set to ENDED NOTOK.

Corrective Action: Examine relevant CTDU99E and CTD908S messages, take appropriate corrective action, and then rerun the decollating mission. Use the CTDDIG utility to check the integrity of the user file. If the problem persists, contact BMC Customer Support.

CTD261E SEVERE ERROR WHILE LOCATING SYSOUT PARAMETERS FROM JESLink copied to clipboard

Explanation:Highlighted, unrollable message.

An internal test of the JES control blocks failed.

Control-D retrieves data set characteristics from the JES2 control blocks. These blocks are release-dependent. To avoid abends, Control-D tests the blocks at the beginning of its process. If the test fails, the CTD261E message is displayed.

This error is often caused by MSGCLASS for started tasks being set to PURGE or DUMMY. Control-D uses the settings of MSGCLASS for started tasks for test SYSOUT.

Snaps are produced and put in the DADUMP DD statement. Control-D continues to process without retrieving characteristics from the JES Control Blocks.

Corrective Action: Do the following:

Ensure that the MSGCLASS output class for the started task (STC) in the JES2PARM member of the SYS1.PARMLIB library is not set to PURGE or DUMMY.
If MSGCLASS is set correctly, collect the relevant snaps from the DADUMP DD statement and contact BMC Customer Support.

CTD266E CTDPARM GENOTFND SETTING INVALID FOR CURRENT ENVIRONMENT
CTD266I GENERIC DECOLLATION PROCESSING STOPPED.Link copied to clipboard

Explanation: The setting of the GENOTFND parameter in CTDPARM is not supported by the MVS/JES configuration of the computer. These two messages are always issued together.

Some options of the GENOTFND parameter in CTDPARM are valid only in certain MVS/JES configurations. For example, JES3 supports only CLASS and DELETE as values for the GENOTFND parameter.

For a description of the GENOTFND parameter, see the Control-D chapter of the INCONTROL for z/OS Installation Guide.

The unmatched sysout file remains unchanged.

Corrective Action: Do the following:

Manually remove the problematic sysout from the generic class.
Correct the GENOTFND parameter in CTDPARM.
Restart the Control-D monitor after compiling CTDPARM.

CTD26AE MISSION ABENDED S `nnn` U `nnnn`.Link copied to clipboard

Explanation:Highlighted, unrollable message.

The decollation mission abended with the system code or the user code or both these codes displayed in this message.

The decollation mission finishes NOTOK. Control-D tries to process other missions.

Corrective Action: If Control-D cannot process other missions, stop and restart the Control-D monitor. Save the job log of the Control-D decollation monitors and the output referenced by DD statement IOADUMP of the decollation monitor which processed the problematic mission. Call BMC Customer Support.

CTD26BE SUBSYSTEM REQUEST FAILED FOR JOB `jobName`. RC15= `rc`, SSOBRETN= `rtrn_code`.Link copied to clipboard

Explanation: A “sysout processing” request caused an unexpected return code to be received from JES. JES was unable to satisfy the request.

The variables in this message are:

jobName - the name of the relevant job
rc - the code returned in register 15
rtrn_code - the contents of the SSOBRETN field of the request block

Corrective Action: Verify that JES is active and functions normally. If JES is functioning normally, save all sysouts of this execution of the Control-D monitor and contact BMC Customer Support. Request RESTORE of the problematic report again.

CTD26HE GENERIC MISSION ABENDED SXXX UXXXX. GENERIC DECOLLATION PROCESSING STOPPEDLink copied to clipboard

Explanation:Highlighted, unrollable message.

The generic decollation mission abended with the system code or the user code or both these codes displayed in this message. The decollation mission finishes NOTOK. CONTROL-D deactivates the Generic decollation process.

Corrective Action: Save the job log of the CONTROL-D decollation monitors and the output referenced by DD statement IOADUMP of the decollation monitor that processed the problematic mission. Call BMC Software Customer Support.

CTD271I GENERIC JOB DECOLLATION IS INACTIVELink copied to clipboard

Explanation: This information message indicates that Generic Processing is not active. The reason the message is issued depends in which of the following formats the message is issued.

regular, rollable message - indicates that the corresponding Control-D monitor does not perform the Generic Processing. The Control-D monitor issues the message when it is started and after new day processing.
highlighted, unrollable message - indicates that a job is waiting to be decollated in one of the Generic classes, but Generic Processing is not active. This message will appear every 10 minutes, until Generic Processing is activated.

Control-D continues processing, but no Generic Processing will be done.

Corrective Action: Use the following guidelines to resolve the problem:

If you have Generic Missions that CTDNDAY processing should order, ensure that the GENLIST member contains the library and table name for your Generic Missions
If you have a Library and table names in the GENLIST member, ensure that the MEMBERS really exist in the library. Also verify that the library is the correct name.
Check to see if CTDNDAY processing had an error during the ordering of GENLIST. If an error occurred the deactivation of Generic Processing is automatic.
Check to see if someone issued the STOPGEN command.

Issue the following command, to activate Generic Processing:

F CONTROLD,STARTGEN

The application will respond by displaying the following message:

CTD139I GENERIC JOB DECOLLATION IS ACTIVE ON CLASSES (claslist)

To verify your classes, check the GENCLAS= parameter in the CTDPARM member.

If there are NO Generic Missions being ordered during the CTDNDAY processing, you need to manually activate Generic Processing if you are manually Forcing/Ordering Generic Missions.
For more information on activating and deactivating generic processing, see the INCONTROL for z/OS Administrator Guide.

CTD272W SYSOUT REMOVED FROM QUEUE
CTD272I GENERIC DECOLLATING MISSION NOT FOUND FOR JOB `jobName`.Link copied to clipboard

Explanation: Control-D found a non-held output on one of the classes dedicated for Generic processing. There is a Generic decollating mission for the class, but there is no applicable decollating mission for the sysout. These two messages are always issued together.

Whenever a non-held output appears on the spool in one of the classes defined for Generic processing, Control-D looks for a Generic decollating mission (on the Active Missions file) which matches the job name. If a match is not found, the sysout is processed according to the GENOTFIND Control-D installation parameter. For more information, see the Control-D chapter in the INCONTROL for z/OS Administrator Guide.

Corrective Action: Check to see if the Generic decollating mission for this job should be on the Active Missions file. If so, order the decollating mission. If not, purge the sysout.

CTD273I SYSOUT CLASS CHANGED FROM CLASS `x` TO ESCAPE CLASS y.Link copied to clipboard

Explanation: This information message indicates that Control-D found a non-held output on one of the classes dedicated for Generic processing. There is a Generic decollating mission for the class, but there is no applicable decollating mission for the sysout.

Whenever a non-held output appears on the spool in one of the classes defined for Generic processing, Control-D looks for a Generic decollating mission on the Active Missions file that matches the job name. If a match is not found under JES3, Control-D changes the sysout’s class to an Escape Class as specified in the GENOTFND Control-D installation parameter, and the output remains on the spool. For more information, see the INCONTROL for z/OS Administrator Guide.

Corrective Action: Check to see if the Generic decollating mission for this job should be Active on the Active Missions file. If so, order the decollating mission. If not, purge the sysout.

CTD276I MESSAGE MOVED TO MQ ESCAPE QUEUE `queueName`Link copied to clipboard

Explanation: This information message indicates that the message was moved to the queueName queue that was defined in the CTDMQPRM parameter of the MQNOTFIND CTD PARM member.

Corrective Action: No action is required.

CTD277W THE DATA LENGTH IS ZERO IN THE MESSAGE FROM MQ QUEUE `queueName`Link copied to clipboard

Explanation: The message from the IBM WebSphere MQ queue cannot be decollated because the message data length is zero. The message will be moved to the IBM WebSphere MQ escape queue.

The name of the escape queue must be defined with the CTDMQPRM parameter in the MQNOTFIND CTD PARM member.

Corrective Action: No action is required.

CTD278E SYSOUT ALLOCATION FAILED, `JobName`,`JobId`,`DDName`, RC=`rc`, ERROR=`rsn`Link copied to clipboard

Explanation: An error was encountered when Control-D tried to allocate a sysout for decollation.

The variables in this message are:

jobName - the name of the job with the problematic sysout
jobId - the job ID of the job with the problematic sysout
DDName - the name of the DD statement with the problematic sysout
rc - dynamic allocation return code
rsn - dynamic allocation reason code

Corrective Action: Try to correct the sysout. If the problem persists, contact your system programmer for assistance. Keep all sysouts from this execution of the Control-D monitor, and contact BMC Customer Support.

CTD27FI `jobId,jobName,ddName` SYSOUT IS HELD IN GENERIC CLASS `clss`Link copied to clipboard

Explanation: The sysout of the identified job cannot be decollated by a generic decollation mission. The reason is an error identified in a previous message.

The variables in this message are:

jobName - the name of the job with the problematic sysout
jobId - the job ID of the job with the problematic sysout
ddName - the name of the DD statement with the problematic sysout
clss - the spool class of the sysout

Processing continues, but the status of the sysout is set to HELD.

Corrective Action: Examine the log for the previous message that identifies the error, and proceed according to the User Response for that message.

CTD27GE `jobId,jobName,ddName` JES I/O ERROR RSN `rsn` FOR SYSOUT CLASS `clss`Link copied to clipboard

Explanation: A JES I/O error occurred during the reading of sysout from the spool.

The variables in this message are:

jobName - the name of the job with the sysout that was being read when the mismatch occurred
jobId - the job ID of the job with the sysout that was being read when the mismatch occurred
ddName - the name of the DD statement with the sysout that was being read when the mismatch occurred
rsn - the reason code from the FDBK field of JES
clss - the spool class of the sysout

The decollation mission finishes NOTOK.

Corrective Action: Try to correct the sysout. If the problem persists, keep all sysouts of this execution of the Control-D monitor, and contact BMC Customer Support.

CTD27HI ZIIP ISN'T USEDLink copied to clipboard

Explanation: This information message indicates that the zIIP processor is not being used by the Control-D decollation monitor, as it is defined in the CTDPARM.

Additional messages identify the specific reason why the zIIP processor is not being used.

Corrective Action: Check the IOA log file and the system log for the reason. Contact your system programmer for assistance if needed.

CTD27II ZIIP IS USEDLink copied to clipboard

Explanation: This information message indicates that the zIIP processor is being used by the Control-D decollation monitor.

Corrective Action: No action is required.

CTD27JE `jobName, jobId, ddName` OPEN ERROR RS `rs` ERFLG `err` FOR SYSOUT CLASS `clss`Link copied to clipboard

Explanation: An error occurred while attempting to open a SYSOUT for decollation.

The variables in this message are:

jobName - the name of the job with the sysout that caused the problem
jobId - the job ID of the job with the sysout that caused the problem
ddName - the name of the DD statement with the sysout that caused the problem
rc - the return code from the OPEN
err - the reason code from the ACBERFLG field
clss - the spool class of the sysout

The decollation mission finishes NOTOK. The CTD27FI message, which follows, indicates that the status of the problematic SYSOUT is set to HELD.

Corrective Action: Try to correct the sysout. If the problem persists, keep all sysouts of this execution of the Control-D monitor, and contact BMC Customer Support.

CTD280E CANNOT SAVE. MASK RULER ALREADY EXISTS FOR THIS REPORT.Link copied to clipboard

Explanation: Only one MASK RULER can be defined for a report with the same RECIPIENT NAME, JOBNAME, and REPORT NAME.

Corrective Action: Use existing MASK RULER for editing. If you want to create a new MASK RULER with a different name, first delete the original MASK RULER.

CTD281E A MASK RULER HAS NOT BEEN SPECIFIED FOR THIS REPORT.Link copied to clipboard

Explanation: The user entered the RULER MASK command, but there was no MASK RULER defined in the VSA USER record.

Corrective Action: If the MASK RULER exists, update the VSA USER record, either manually or using the CTDUFUPD utility. If the MASK RULER has not yet been defined, use the Edit screen to create a MASK RULER.

CTD282I `text` (`usr`).Link copied to clipboard

Explanation:Highlighted, unrollable message.

This information message is activated by the SHOUT Facility.

The variables in this message are:

text - the information
usr - the user ID of the job order requesting the SHOUT

Corrective Action: No action is required.

CTD284I NEW DYNAMIC DESTINATION TABLE LOADED.Link copied to clipboard

Explanation: This information message indicates that a new Dynamic Destination Table has been loaded by the Control-D monitor. The message also appears on initialization of the SHOUT Facility under the Control-D monitor

Corrective Action: No action is required.

CTD285W DYNAMIC DESTINATION TABLE NOT LOADED.Link copied to clipboard

Explanation: Loading of the Dynamic Destination Table by the Control-D monitor failed.

It could be due to one of the following:

There is insufficient memory for loading the table.
The IOADEST table does not exist in the IOA PARM library.

If the failure happens during the initialization of the Control-D monitor, then SHOUT notifications will not be controlled by the Dynamic Destination Table. If this happens as a result of an F CONTROLD,NEWDEST command (operator command instructing the Control-D monitor to load a new Destination Table), the old destination table will remain in effect.

Corrective Action: Check the MVS Log for the reason for the failure (probably a system abend code). Correct the problem and then, in order to load the table, issue the operator command F CONTROLD,NEWDEST.

CTD286E RULER DEFINITION TOO LONG (NOT SAVED). TRY TO OMIT "INSERTED" LINESLink copied to clipboard

Explanation: Ruler definition exceeded the maximum allowed length.

The rule is not saved.

Corrective Action: Decrease size of the ruler by omitting Inserted lines.

CTD295E PLEASE FILL IN STRING, FROM COLUMN AND UNTIL COLUMNLink copied to clipboard

Explanation: One of the obligatory fields was not specified in the ruler definition screen. String and column fields must be filled in.

Corrective Action: Fill in these fields.

CTD296E COLUMN MUST BE A THREE DIGIT NUMBER (001-256)Link copied to clipboard

Explanation: Column specification is incorrect. Column number must contain only digits.

Corrective Action: Enter correct column number.

CTD297E "TO COL" MUST BE GREATER THAN "FROM COL"Link copied to clipboard

Explanation: Column specification is incorrect. FROM column number must be not greater than TO column number.

Corrective Action: Enter correct column numbers.

CTD298E LINE MUST BE A THREE DIGIT NUMBER 001-256 OR L99-L01Link copied to clipboard

Explanation: The specified line is out of range. Line range is 001-255 or L99-L01 (from the bottom of the page).

Corrective Action: Correct the line range specification.

CTD299E "TO LINE" MUST BE GREATER THAN "FROM LINE"Link copied to clipboard

Explanation: The specified FROM LINE is greater than the specified TO LINE. The TO LINE value must be greater than or equal to the FROM LINE value.

Corrective Action: Correct the TO LINE and/or FROM LINE values.

CTD29BW INSUFFICIENT MEMORY TO COMPLETE PROCESSING OF THE PRINT RULER `rulerName` FOR REPORT `recipientName` `/` `jobName` `/` `reportName`Link copied to clipboard

Explanation: This warning message is issued if there is insufficient memory for using PRINT RULER rulerName for report recipientName / jobName / reportName. The report is printed without the ruler formatting.

Corrective Action: Increase region size of the corresponding address space and rerun printing.

CTD2T0I FILE TRANSFER MONITOR SHUTTING DOWNLink copied to clipboard

Explanation:Highlighted, unrollable message.

This information message indicates that the File Transfer monitor is shutting down.

Corrective Action: No action is required.

CTD2T1S FILE TRANSFER MONITOR ENDED WITH ERRORLink copied to clipboard

Explanation: This information message indicates that the File Transfer monitor ended with an error.

Corrective Action: In the printout of the File Transfer monitor, check the messages which preceded this FTM121S message for an indication of the cause of the error, and take appropriate corrective action.

CTD2T2W FILE TRANSFER MONITOR IS ACTIVE. QNAME " `qName` "Link copied to clipboard

Explanation:Highlighted, unrollable message.

The user attempted to activate the File Transfer monitor when it was already active. More than one File Transfer monitor cannot be active at the same time.

The new File Transfer monitor is not activated.

Corrective Action: No action is required.

CTD2T5I `validModifyParm`Link copied to clipboard

Explanation: This information message displays a valid modify parameter that can be used in File Transfer monitor operator commands. It is issued together with the FTM103E message.

Corrective Action: No action is required.

CTD2T8S RECIPIENT TREE WAS NOT LOADED BECAUSE OF ERROR - MONITOR IS TERMINATINGLink copied to clipboard

Explanation: The attempt to load the Recipient Tree failed. As part of the initialization process, the File Transfer monitor attempts to load the Recipient Tree.

The File Transfer monitor shuts down.

Corrective Action: Check other messages in the IOA log and JES log to determine why the Recipient Tree could not be loaded. Fix the Recipient Tree. Then try again to start the File Transfer monitor.

CTD2T9S NO RECIPIENTS WERE FOUND WITH IP ADDRESS. MONITOR IS TERMINATINGLink copied to clipboard

Explanation: The File Transfer monitor was unable to find a recipient with an IP address.

The File Transfer monitor terminates.

Corrective Action: Contact BMC Customer Support.

CTD2TAS SUBTASK IS TERMINATED BY TIMEOUT FOR IPA = `ipAdd`.'Link copied to clipboard

Explanation: The subtask has timed out and been terminated.

The monitor main task periodically checks the status of all its subtasks. When the CPU of a subtask has not changed since the last check, the subtask is considered to be inactive ("hanging"), and the main task of the monitor interrupts the subtask.

The subtask is terminated.

Corrective Action: In the printout of the File Transfer monitor, and in the log of your PC session manager, check the messages which preceded this FTM121S message for an indication of the reason why the subtask was left inactive, and take appropriate corrective action.

CTD2TBS SUBTASK IS TERMINATED BY CANCEL REQUEST FOR IPA = `ipAdd`. PORT = `portNumber`.Link copied to clipboard

Explanation: The File Transfer monitor subtask with the IP address identified in this message has been terminated by an operator modify CANCEL command.

The identified subtask is terminated.

Corrective Action: No action is required.

CTD2TCS THERE ARE NO ACTIVE SUBTASKSLink copied to clipboard

Explanation: This information message indicates that the File Transfer monitor has no active subtasks.

Corrective Action: No action is required.

CTD2TDS FORMAT OF THE MODIFY COMMAND IS NOT CORRECTLink copied to clipboard

Explanation: An invalid operator modify command has been entered.

The command is rejected.

Corrective Action: Correct and reissue the operator modify command.

For more information, see the File Transfer Monitor section in the Control-D chapter in the INCONTROL for z/OS Administrator Guide.

CTD2TES THE SUBTASK NUMBER IS NOT DIGITALLink copied to clipboard

Explanation: An invalid subtask number has been specified in an operator modify CANCEL command.

The command is rejected.

Corrective Action: Enter a valid subtask number and reissue the command.

CTD2TFS THE SUBTASK NUMBER EXCEEDS THE TOTAL NUMBER OF THE ACTIVE SUBTASKSLink copied to clipboard

Explanation: The subtask number entered in an operator modify CANCEL command is invalid, because it is greater than the total number of active subtasks.

For more information, see the File Transfer Monitor section in the Control-D chapter in the INCONTROL for z/OS Administrator Guide.

The command is rejected.

Corrective Action: Enter a valid subtask number in the operator modify CANCEL command and reissue the command.

CTD2TGS SUBTASK IS ALREADY NOT ACTIVE FOR IPA = `ipAdd` PORT = `portNumber`Link copied to clipboard

Explanation: The File Transfer monitor subtask with the ipAdd IP address and portNumber port number is already inactive.

The command is rejected.

Corrective Action: No action is required.

CTD2THS SUBTASK IS TERMINATED BY SUSPEND FOR IPA = `ipAdd` PORT = `portNumber`Link copied to clipboard

Explanation: The File Transfer monitor subtask with the ipAdd IP address and portNumber port number has been terminated by an operator modify SUSPEND command.

The subtask is terminated.

Corrective Action: No action is required.

CTD2TIS IPA SPECIFIED IN THE CANCEL COMMAND IS NOT CORRECT.Link copied to clipboard

Explanation: An invalid IP address was specified in an operator modify CANCEL command.

The command is rejected.

Corrective Action: Enter a correct IP address in the CANCEL command and reissue the command.

CTD2TJS THE INTERVAL PARAMETER VALUE IS NOT DIGITAL.Link copied to clipboard

Explanation: An invalid File Transfer monitor sleeping interval has been specified in an operator modify command.

The File Transfer monitor sleeping interval must be a 3-digit number from 1 through 999 seconds.

For more information, see the File Transfer Monitor section in the Control-D chapter in the INCONTROL for z/OS Administrator Guide.

The operator modify command is rejected.

Corrective Action: Enter a valid value for the File Transfer monitor sleeping interval and reissue the command.

CTD2TKI THE MODIFY COMMAND `cmdText` IS ACCEPTEDLink copied to clipboard

Explanation: This information message indicates that the cmdText modify command has been accepted by the File Transfer monitor.

Corrective Action: No action is required.

Messages CTD300 through CTD3xxLink copied to clipboard

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

CTD304E `func` NOT OK WITH `cc` Y REASON CODE `rsn` MQ NAME `uuuuuuu`Link copied to clipboard

Explanation: An error was detected during interface with IBM WebSphere MQ Series.

The variables in this message are:

func - can be one of the following interface functions:
- MQCONN
- MQDISC
- MQOPEN
- MQGET
- MQPUT
- MQCLOS
- MQCOMMT
cc - the completion code, which can be one of the following:
- 0
- 1,,,
- 2
rsn - the reason code, which can have many different values. More detailed information about reason codes is included in the IBM WebSphere MQ Series documentation set.

System action is determined by the completion code and reason code combination. More detailed information about these codes is included in the IBM WebSphere MQ Series documentation set.

Corrective Action: User response to a particular completion and reason code combination is determined by that combination. More detailed information about these codes is included in the IBM WebSphere MQ Series documentation set.

CTD305E INSUFFICIENT MEMORY TO DECOLLATE MESSAGE FROM MQLink copied to clipboard

Explanation: Insufficient memory to decollate the message from the IBM WebSphere MQ queue.

Corrective Action: Increase the Control-D monitor REGION size.

CTD306E IOAUCODE INITIALIZATION FAILED RC `rc` REASON `rsn` Link copied to clipboard

Explanation: An error was detected during initialization of the table used in the translation of an XML report or in the checking of Xpath values of the mission definition. The message can be issued from

the R screen
the A.Z screen
the Control-D monitor

Possible causes of this error are:

the ENCODTBL member was not found in the IOA IOAENV library
the ENCODTBL member contains more than 100 entries
some other internal error

The system performs the following actions:

Mission definition edition is terminated. The IOAE2FS (International format) issues on the R.S and A.Z screens.
The translation of the XML report does not proceed. Control-D continues processing.

Corrective Action:

Check the ENCODTBL member in the IOA IOAENV library, make any necessary corrections, reactivate the IOA Online facility, and continue the mission definition edition.

Check the ENCODTBL member in the IOA IOAENV library, make any necessary corrections, reactivate Control-D, and run this mission again.

If the problem persists contact BMC Customer Support.

CTD307E UNICODE TRANSLATION FAILED RC `rc` REASON `rsn` Link copied to clipboard

Explanation: An error was detected during translation of an XML report to EBCDIC or during the checking of Xpath-values of the mission definition for XML reports. The message can be issued from

the R screen
the A.Z screen
the Control-D monitor

The variables in this message are:

rc - the return code. Valid values of rc are:

rc	Meaning
4	Incomplete translation, due to separator (FF)
8	The encoding pair that was specified in ENCODTBL is not supported
12	The input data in the XML report was incorrect
16	Internal error: incorrect parameters
20	One of the members that was specified in ENCODTBL was not found in the IOA IOAENV library

rsn - the code that disclosed the detailed reason for the internal error

The system performs the following actions:

Mission definition edition is terminated. The IOAE2FS (International format) is issued on the R.S and A.Z screens.
The translation of the XML report does not proceed. Control-D continues processing.

Corrective Action:

Check the ENCODTBL member in the IOA IOAENV library, make any necessary corrections, reactivate the IOA Online facility, and continue the mission definition edition.

Check the ENCODTBL member in the IOA IOAENV library, make any necessary corrections, reactivate Control-D and run this mission again.

If the problem persists contact BMC Customer Support.

CTD30AI MQ DECOLLATION IS STOPPEDLink copied to clipboard

Explanation: The MQ interface process has stopped.

This message can appear for two reasons:

The STOPMQ modify command was issued
Errors occurred during MQ interface

Corrective Action: If errors occurred during MQ interface, review the LOG to determine the cause, make appropriate corrections, and issue the STARTMQ modify command.

CTD30BE LOADING OF MODULE OF MQ STUB IS FAILED, THE NAME IS `mmmmmmmm`Link copied to clipboard

Explanation: The prefix.LOAD library is not installed or the IBM WebSphere MQ Series is not installed for the user, but an MQ decollation mission was defined.

The CTD30AI message will be issued and IBM WebSphere MQ decollation will be stopped.

Corrective Action: If the IBM WebSphere MQ Series is not installed, delete the MQ mission. Otherwise correct your installation configuration and then issue the STARTMQ modify command.

CTD30CE ANY OF MQ QUEUES CAN NOT BE OPENEDLink copied to clipboard

Explanation: Control-D tried to retrieve a message from every IBM WebSphere MQ queue, but all attempts failed.

The CTD30AI message will be issued and IBM WebSphere MQ decollation will be stopped.

Review previous messages and issue appropriate responses. After you perform the necessary corrections, issue the STARTMQ modify command.

Corrective Action: No action is required.

CTD30DI MQ QUEUE IS BEING CLOSED BECAUSE PUT/GET IS FAILED, QUEUE NAME `dddddd`Link copied to clipboard

Explanation: The access to this IBM WebSphere MQ Series queue is being closed because of failure of MQPUT for the ESCAPE MQ queue, or failure of MQGET for the MQ queue.

Control-D continues processing MQ decollations until this message is issued for all MQ queues.

Corrective Action: For additional information see the IBM WebSphere MQ Series documentation set.

CTD30EE MEMBER CTDMQPRM IS NOT FOUND IN CTD PARM OR VALUE OF MQNOTFIND PARAMETER IS NOT DEFINEDLink copied to clipboard

Explanation: The CTDMQPRM member was not found in CTD PARM, or the value of the MQNOTFIND parameter has not been defined.

The CTD30AI message will be issued and IBM WebSphere MQ decollation will be stopped.

Define the CTDMQPRM member or add the name of the MQNOTFIND parameter; then issue the STARTMQ modify command.

Corrective Action: No action is required.

CTD310S OPEN OF RECIPIENT TREE (DD STATEMENT "DATREE") FAILEDLink copied to clipboard

Explanation: Open of the Control-D Recipient Tree failed. There is a problem with the DATREE DD statement in the Control-D CLIST.

It is due to one of the following:

The DD statement DATREE is missing.
If the DD statement DATREE is allocated to a library, the requested member name is not found.

You will not be able to use the User Report List screen.

Corrective Action: Correct the Control-D entry CLIST DMAN (or TMAND or other) to include the DD statement DATREE. Then exit the Control-D Online Facility, and reenter.

CTD311S SECURITY VIOLATION - YOU ARE TRYING TO BYPASS THE RECIPIENT TREELink copied to clipboard

Explanation: The Recipient Tree data set name or member name is incorrect. Control-D security exit CTDX004 checks if the data set name and member name of the DATREE DD statement are correct.

You will not be able to use the User Report List screen.

Corrective Action: Do one of the following

Correct the Control-D entry CLIST by changing the data set name or the member name of the Recipient Tree. Then exit from the Control-D Online Facility, and reenter it.
Correct security exit CTDX004 in the SAMPEXIT library by checking for the correct Recipient Tree data set name or member name. The called routine is TREEVER. Then exit the Control-D Online Facility, and reenter it.

CTD312S ERROR WHILE LOADING THE RECIPIENT TREELink copied to clipboard

Explanation: The loading of the Control-D Recipient Tree failed. An appropriate error message is displayed on the operator console and the IOA Log. The error message specifies the exact cause of the problem.

ll error messages relating to the Recipient Tree on the IOA Log start with TRE.

You will not be able to use the User Report List screen.

Corrective Action: Correct the Recipient Tree. Then exit from the Control-D Online Facility, and re-enter it.

CTD313E YOU ARE NOT AUTHORIZED TO RECEIVE REPORTS FOR THIS RECIPIENTLink copied to clipboard

Explanation: The user has specified a value in a filter for the RECIPIENT field, and is not authorized to view report entries for recipients that match this value.

The requested function is not performed.

Corrective Action: To obtain authorization to view these report entries, contact your INCONTROL administrator.

CTD314E YOU ARE NOT AUTHORIZED TO DO THIS ACTIONLink copied to clipboard

Explanation: You are not authorized to perform this function on the User Report List file.

The attempt to perform one of the following functions does not have the required authorization:

add an entry
update an entry
delete an entry
restore a report
reprint a report

The requested function is not performed.

Corrective Action: To get authorization to perform this function, call your INCONTROL administrator.

This message is the result of the action of the Control-D Security Exit CTDX004. For more information, refer to the following routines within this exit:

RECINS - add an entry
RECUPD - update an entry
RECDEL - delete an entry
RECRST - restore a report
RECRPRT - reprint a report

CTD315I SOME REPORTS WERE HIDDEN BY USER SECURITY EXITLink copied to clipboard

Explanation: This information message indicates that, for security reasons, one or more reports on the User Report List file was not displayed. The RECCONF routine of Control-D security exit CTDX004 determined that the requestor is not authorized to look at some report entries on the User Report List screen.

One or more report entries on the User Report List file is hidden.

Corrective Action: No action is necessary. All entries for which there is authorization will be visible. To see all report entries, call your INCONTROL administrator.

CTD316E YOU CANNOT UPDATE THE COP# ABOVE THE MAXIMUM SPECIFIED ON DECOLLATIONLink copied to clipboard

Explanation: The number of copies on the User Report List screen is above the maximum. The 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.

The User Report List file is not updated.

Corrective Action: Do one of the following:

Change the number of copies to a lower value.
Ask the INCONTROL administrator to increase the maximum number of copies allowed.

CTD317E USER DOES NOT EXIST IN THE RECIPIENT TREELink copied to clipboard

Explanation: This user to be added or deleted to the User Report List file is not defined in the Control-D Recipient Tree.

The User Report List file is not updated.

Corrective Action: Do one of the following:

Correct the user to be added or updated.
Request the INCONTROL administrator to add the user to the Recipient Tree.

CTD318S YOU ARE NOT AUTHORIZED TO USE THIS SCREENLink copied to clipboard

Explanation: You are not authorized to use the User Report List screen. Control-D security exit CTDX004 checks the Recipient Tree to determine authorization to look at entries on the User Report List screen.

You cannot enter the User Report List screen.

Corrective Action: To get authorization to enter the User Report List screen, contact your INCONTROL administrator.

CTD319E YOU ARE NOT AUTHORIZED TO LOOK AT $SYSDATA RECORDSLink copied to clipboard

Explanation: You are not authorized to look at $SYSDATA records on the User Report List screen. Control-D security exit CTDX004 (routine USERLIST) determined that you cannot look at $SYSDATA records.

The requested $SYSDATA entries are not displayed.

Corrective Action: To get authorization to look at $SYSDATA records, contact your INCONTROL administrator.

CTD31AE YOU ARE NOT AUTHORIZED FOR THIS APPROVALLink copied to clipboard

Explanation: The user has specified a value in a filter for the APPROVAL NAME field, and is not authorized to view report entries for Approval names that match this value.

The requested function is not performed.

Corrective Action: To obtain authorization to view these report entries, contact your INCONTROL administrator.

CTD320S UNABLE TO VIEW THIS REPORT - ALL COMPRESSED DATASETS WERE DELETEDLink copied to clipboard

Explanation: There are no compressed data sets for this report entry on the User Report List screen. You attempted to perform the V (View) function on the User Report List screen. The IOATOLV Control-D internal program was unable to find any compressed data sets for this report entry.

The view function is not performed.

Corrective Action: Ask the INCONTROL administrator to check why all the compressed data sets for this report were deleted.

CTD321S UNABLE TO VIEW THIS REPORT - RC FROM IOATOLV=`rc`Link copied to clipboard

Explanation: The report cannot be viewed due to an error in the IOATOLV internal module or in a routine called by it, which resulted in return code rc. The V(View) option was specified on the User Report List screen. The IOATOLV internal module was called to perform the view function.

The following table shows the problem indicated by each return code, the routine in which it occurred, and the suggested action to take.

rc	Routine	Explanation	Action
04	IOATOLV	Internal error in module.	1
08	IOATOLV	Internal error in module.	1
12	IOATOLV	Internal error in module.	1
20	IOATOLV	Too many GETMAINs - report too large.	2
24	IOATOLV	Internal error in module.	1
28	IOATOLV	Internal error in module.	1
32	IOATOLV	All compressed data sets were deleted.	1
204	CTVINX#	Index access internal error. Invalid function code passed to routine.	1
220	CTVINX#	Index access internal error. Unexpected end of file reached on index file.	1
224	CTVINX#	Index access internal error. Open error on the index file.	1
236	CTVINX#	Index access, internal error. Error in reading the continuation records.	1
240	CTVINX#	Index access, internal error. Unexpected end of file reached on index file.	1
244	CTVINX#	Index access, internal error. Invalid parameter passed to read index routine.	1
248	CTVINX#	Index access, internal error. Problem in the search for the index value.	1
252	CTVINX#	Index access, internal error. Dynamic deallocation of index file failed.	1
280	CTVINX#	Index access, internal error. Open of subindex failed. Invalid code from CTVSRTN.	1
284	CTVINX#	Index access, internal error. Close of subindex failed. Invalid code from CTVSRTN.	1
288	CTVINX#	Index access, internal error. Locate subindex failed. Invalid return code from CTVLSUB.	1
292	CTVINX#	Index access, internal error. Close subindex was requested but no subindexes are open.	1
296	CTVINX#	Index access, internal error. Error in FREEMAIN.	1
300	CTVINX#	Index access, internal error. Locate of value failed under Quick Access.	1
304	CTVINX#	Index access, internal error. Open subindex failed under Quick Access.	1
316	CTVINX#	Index access, internal error. PREPINX failed under Quick Access.	1
324	CTVINX#	Index access, internal error. Inconsistent IXA table and IXT table under Quick Access.	1
328	CTVINX#	Index access, internal error. Invalid request code passed to CTVSINX.	1
332	CTVINX#	Index access, internal error. Internal error in CTVSINX.	1
336	CTVINX#	The IOA Archive Server not active.	4
340	CTVINX#	Index access, internal error. Block not in cache.	1
344	CTVINX#	Error in cache routine. OSIS (open session entry) was not active.	4
348	CTVINX#	Index access, internal error. Error moving $index record or user RBA ranges to IOA Archive Server.	1
368	CTVINX#	Index access, internal error. GETMAIN failed.	1
400	CTVINXR	Index access, internal error. Invalid function code passed to routine.	1
404	CTVINXR	Index access internal error. Load of CTVINX# failed.	1
424	CTVINXR	Index access internal error. No more room for IXP entries.	1
428	CTVINXR	Index access, internal error. Problem reading continuation error.	1
432	CTVINXR	Index access, internal error. Index name found in IXA table not found in $INDEX record.	1
444	CTVINXR	GETMAIN failed.	1
448	CTVINXR	Index access internal error. Error in IXA table. IXAXCNT is 0.	1
604	CTDTFLL	OK, but one or more continuation records were not found.	None
620	CTDTFLL	Insufficient memory. Too many RBA ranges in the report to be viewed.	2
1004	CTDBOX	Internal error in module.	1
1008	CTDBOX	Internal error in module.	1
1012	CTDBOX	Internal error in module.	1
1016	CTDBOX	Internal error in module.	1
1020	CTDBOX	Internal error in module.	1
1024	CTDBOX	Compressed Dataset Access Method not active.	3
1028	CTDBOX	Compressed Dataset Access Method not active.	3
1104	IOASCRQ	Error in cache routine. OSE (open session entry) was not active.	4
1108	IOASCRQ	Error in cache routine. Another request was issued with this OSE.	4
1124	IOASCRQ	The IOA Archive Server not active.	4
1204	IOASAOS	Error in cache routine. ENQ query for user existence failed.	4
1208	IOASAOS	Compressed Dataset Access Method not active. The Compressed Dataset Access Method was terminated or not started.	3
1212	IOASAOS	IOA Archive Server not active. The IOA Archive Server was terminated or not started.	5
1216	IOASAOS	Error in cache routine. No free OSE exists (open session entry).	4
1308	IOAXPC5	Error in cache routine. REQ (request queue element) error.	4
1404	IOAXPC5	The media to which the report migrated is not active in IOA Archive Server.	6
1408	IOAXPC7	Error in cache routine. Requested media not defined in the IOASPRM member.	4
1502	IOASCAW	Error in cache routine. Cannot copy the OSE (open session entry).	4
1504	IOASCAW	The report migrated to a media which is not active in IOA Archive Server.	6
1508	IOASCAW	Error locating migrated report. Requested report not found in the catalog.	7
1512	IOASCAW	Requested volume not in OSS Database. Report migrated to a volume that was manually deleted from the OSS database.	8
1516	IOASCAW	Requested platter not in OSS Database. Report migrated to a volume on a platter that was exported or manually deleted from the OSS Database.	8
1520	IOASCAW	Cache request failed. Media error in adding request to chain.	4
1524	IOASCAW	Cache request failed. Media error in GETMAIN for TVL.	4
1528	IOASCAW	Cache request failed. Media error handling multivolume file.	4
1532	IOASCAW	No devices active for this media. The media to which the report migrated has no currently active device in the IOA Archive Server.	9
1536	IOASCAW	Cache request failed. Media error: File resides on more than five volumes.	4
1560	IOASCAW	Cache request failed. Media error: An RQC was queued without RBAs.	4
1564	IOASDVT	Cache request failed. An RQC was queued with a zeroed RBA.	4
1568	IOASDVT	Cache request failed. Media error during deallocation. See the DVT191E or IOA191E and DVT192E or IOA192E messages in the IOA Log file for the error code and more information.	4
1572	IOASDVT	Error allocating device. IOA Archive Server could not allocate a device to retrieve a migrated report. See the DVT191E or IOA191E and DVT192E or IOA192E messages in the IOA Log file for error code and information about the failed allocation.	10
1576	IOASDVT	Cache request failed. Media error: Open failed.	4
1580	IOASDVT	Cache request failed. Media error: Task abended during open. See the DVT194E/IOA194E message in the IOA Log file for the abend code.	4
1584	IOASDVT	Cache request failed. Media error: I/O error on device. See the DVT193E/IOA193E message in the IOA Log file for I/O error description.	4
1592	IOASDVT	Cache request failed while reading descriptor block of migrated CDAM file.	4
1596	IOASDVT	Cache request failed while acquiring storage for a migrated CDAM descriptor block. See the DVT180S message in the IOA Log file for more information.	4
1600	IOASDVT	Cache request failed while reading the first block from a migrated CDAM file.	4
1604	IOASDVT	Cache request failed while acquiring storage for the first block of a migrated CDAM file. See the DVT180S message in the IOA Log file for more information.	4
1608	IOASDVT	Cache request failed while acquiring storage. See the DVT180S message in the IOA Log file for more information.	4
1612	IOASDVT	Cache request failed. An extent number in the RBA is out-of-range.	4
1616	IOASDVT	Cache request failed while translating RBA to BBB.	4
1620	IOASDVT	Cache request failed. Block number is out-of-range.	4
1624	IOASDVT	Cache request failed while translating BBB to RBA.	4
1628	IOASDVT	Cache request failed while issuing ENQ to test user existence. See the DVT181E or IOA181E message in the IOA Log file for more information.	4
1632	IOASDVT	Task abended during cache request processing.	4
1636	IOASDVT	Operator did not mount the tape volume requested by the IOA Archive Server. Operator could not find requested volume or did not mount the volume for some other reason.	11
1640	IOASDVT	Cache request failed. Media error: Assigned device could not be allocated because it is unavailable. See the DVT191E or IOA191E and DVT192E or IOA192E messages in the IOA Log file for more information.	4
1644	IOASDVT	Cache request failed. Index Access. Internal error in index cache chaining.	4
1648	IOASDVT	Cache request failed. Index Access. Internal error, invalid call to CTVSRTN.	4
1652	IOASDVT	Cache request failed. Index Access. Internal error, invalid call to CTVLSUB.	4

The report is not displayed or only partially displayed.

Corrective Action: Do one of the following, as indicated in the preceding table:

Report the message number and return code to BMC Customer Support.
This report is too large to view online. Report this to your INCONTROL administrator.
Ask your INCONTROL administrator to bring up the Compressed Dataset Access Method (CDAM) so you can view this report.
Examine the IOA Log file for messages regarding the event. Use the return code to determine what caused the IOA Archive Server cache mechanism to fail. If the error cannot be resolved, contact BMC Customer Support.
Ask the operator to start the IOA Archive Server.
Ask the operator to activate the required media in the IOA Archive Server.
Contact your INCONTROL administrator to find out what happened to the required data set.
Contact your OSS operator to find out what happened to the required volume or platter.
Ask the operator to activate at least one device of the required media in the IOA Archive Server.
Correct the problem that caused the allocation to fail and retry.
Contact the operator to determine why the requested volume was not mounted.

CTD322S UNABLE TO VIEW THIS REPORT BECAUSE OF AN INTERNAL ERRORLink copied to clipboard

Explanation: The IOATOLV routine encountered a problem, and returned an invalid return code. Control-M/Tape called the IOATOLV routine when the user specified the V (View) option in the User Report List screen.

The report cannot be viewed.

Corrective Action: Check the IOA Log and the system log for additional error messages. Report the problem and any additional error messages to BMC Customer Support.

CTD32BE NUMBER OF PRINT MISSIONS EXCEEDS THE ALLOWED MAXIMUMLink copied to clipboard

Explanation: A large number of PRINT missions were specified in the deferred print request for reports created by a Decollation Mission with STORED=Y in the DO PRINT parameter.

The PRINT mission name specified in the DO PRINT parameter, is hidden in both the User Report List Print Window and the Control-D/WebAccess Host PRINT Window. Nevertheless, since the PRINT mission name is stored in the report entry it is included in the total number of PRINT missions stored in the report entry. The maximum number of PRINT missions, whether immediate or deferred, that are stored in one report entry cannot exceed 5.

The print request is not performed.

Corrective Action: Perform the deferred print request again with less PRINT missions.

CTD323E VIEW|MASK RULER `rulerName` DOES NOT EXIST FOR THIS USER/REPORT/JOBLink copied to clipboard

Explanation: The rulerName ruler was not located. The name may have been misspelled, or the ruler has not been defined.

No ruler is activated.

Corrective Action: Specify a valid ruler name.

CTD324E AT LEAST ONE PRINTING MISSION NAME MUST BE ENTEREDLink copied to clipboard

Explanation: No Printing Mission was defined. At least one Printing Mission name must be entered in the MISSION NAME field for deferred printing.

An error message is issued, and the cursor is positioned at the MISSION NAME field.

Corrective Action: Enter at least one mission name.

CTD325E DEFERRED PRINTING - RULER NAME MUST BE "DEFAULT"Link copied to clipboard

Explanation: The RULER NAME field does not contain the value DEFAULT. In case of deferred printing, the ruler name must be DEFAULT to use an existing DEFAULT ruler.

An error message is issued and the cursor is positioned at the RULER NAME field.

Corrective Action: Correct the ruler name to DEFAULT.

CTD326E DEFERRED PRINTING - FROM PAGE NUMBER MUST BE EQUAL TO 1Link copied to clipboard

Explanation: The FROM PAGE field contains a value other than 1. In case of deferred printing, the FROM PAGE must be defined as the first page.

An error message is issued and the cursor is positioned at the FROM PAGE field.

Corrective Action: Correct the value in the FROM PAGE field to 1.

CTD327E YOU CAN ONLY SELECT THE ENTIRE PAGE RANGE FOR DEFERRED PRINTINGLink copied to clipboard

Explanation: An invalid page range was defined for deferred printing. For deferred printing, the entire page range must be defined.

An error message is issued, and the cursor is positioned at the PAGE RANGE field.

Corrective Action: Correct the page range.

CTD328S UNABLE TO EDIT A RULER - INVALID RC `rc` FROM CTDTEXTLink copied to clipboard

Explanation: An internal error occurred that caused the CTDTEXT subroutine to return an invalid return code.

The ruler is set to OFF.

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

CTD329E INVALID `parm` PARAMETERLink copied to clipboard

Explanation: An invalid value was specified in the User Report List Print window. Control-D Exit 4 found an invalid value in the parm parameter.

The report is not printed.

Corrective Action: Correct the parameter.

CTD330I COMPRESSED DATASET ACCESS METHOD MAINTENANCE UTILITY STARTEDLink copied to clipboard

Explanation: This information message indicates the normal start of the CTDAMUTI utility.

Corrective Action: No action is required.

CTD331I COMPRESSED DATASET ACCESS METHOD MAINTENANCE UTILITY ENDED OKLink copied to clipboard

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

Corrective Action: No action is required.

CTD332S COMPRESSED DATASET ACCESS METHOD MAINTENANCE UTILITY ENDED WITH ERRORSLink copied to clipboard

Explanation: The CTDAMUTI Compressed Dataset Access Method utility ended with errors.

This is a general message when the CTDAMUTI utility ends with errors. The job sysout should contain prior messages detailing the reasons.

Corrective Action: No action is required.

CTD333E INVALID CDAM MAINTENANCE UTILITY FUNCTION: `func`Link copied to clipboard

Explanation: An invalid function (func) was given to the CTDAMUTI Control-D utility.

For more information, see the section on the CTDAMUTI CDAM maintenance utility in the Control-D and Control-V User Guide.

The CTDAMUTI utility terminates with a return code of 08.

Corrective Action: Correct the function, and rerun the CTDAMUTI utility.

CTD334W NO CDAM FILES FOUND FOR THE SPECIFIED SELECTION CRITERIALink copied to clipboard

Explanation: No CDAM data sets were found that match the data set identification parameters given to the CTDAMUTI utility.

The CDAMUTI utility attempts to locate CDAM data sets based on the data set identification parameters given to it. One of the following problems is present:

An error was made by the user in the data set identification parameter.
Someone deleted the required CDAM data sets.

For more information, see the section on the CDAMUTI CDAM maintenance utility in the Control-D and Control-V User Guide.

The CTDAMUTI utility will terminate with a return code of 04.

Corrective Action: Do one of the following, then rerun the utility:

Correct the data set identification parameter.
Restore the requested CDAM data sets.

CTD335S OPEN OF PARAMETERS FILE FAILED. DDNAME "SYSIN"Link copied to clipboard

Explanation: The open of the SYSIN DD statement failed.

Possible causes are:

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

For more information, see the section on the CDAMUTI CDAM maintenance utility in the Control-D and Control-V User Guide.

The CTDAMUTI utility terminates with a return code of 12.

Corrective Action: Correct the CTDAMUTI JCL and rerun the utility.

CTD339S OPEN OF OUTPUT (SPOOL PRINT) FILE FAILEDLink copied to clipboard

Explanation: Internal error in the CTDAMUTI utility.

The dynamic allocation of a sysout print file by the CTDAMUTI utility failed.

The CTDAMUTI utility terminates with a return code of 12.

Corrective Action: Have your system programmer call your IOA representative for assistance.

CTD33AS NO SELECTION PARAMETERS ARE SPECIFIEDLink copied to clipboard

Explanation: No CDAM selection parameters were specified in the input of the CTDAMUTI utility.

At least one CDAM selection parameter must be specified in the input of the CTDAMUTI utility.

The CTDAMUTI utility ends with an error.

Corrective Action: Rerun the CTDAMUTI utility specifying CDAM selection parameters.

CTD364I WAITING FOR ACTIVE PRINTING MISSION(S) IN ORDER TO SHUT DOWNLink copied to clipboard

Explanation:Highlighted, unrollable message.

This information message indicates that the Control-D monitor was shut down, but is waiting for print tasks to finish in order to complete the shut down.

The Control-D internal Printing Missions Manager task received a request from the Control-D monitor to shut down. However, one or more of the print tasks under the control of the Printing Missions Manager is still printing. As soon as all the print tasks are completed, the Printing Missions Manager task will shut itself down.

Corrective Action: No action is required.

CTD390S OPEN OF DDNAME `ddName` FAILED.Link copied to clipboard

Explanation: Open of the ddName DD name failed. Possible causes are:

The ddName DD statement is missing.
The data set described by the ddName DD statement does not exist.

Execution stops.

Corrective Action: Correct the JCL of the job and rerun.

CTD394S INVALID PARAMETER - `parm`Link copied to clipboard

Explanation: An invalid parameter was specified to the report or utility.

If this message was issued during execution of the CTMBLT utility, it is followed by message BLT895I and/or BLT896I, which identify the problematic job, keyword, and value.This message may also be issued by the CTMBUPD utility.

The report or utility stops executing with a condition code of 08 or 12.

Corrective Action: For the syntax of the parameter for the report or utility, see either the INCONTROL for z/OS Administrator Guide or the INCONTROL for z/OS Utilities Guide, as appropriate.

Messages CTD400 through CTD4xxLink copied to clipboard

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

CTD400S INVALID RETURN CODE FROM SORT = `rc`. CHECK THE SORT MANUAL.Link copied to clipboard

Explanation: A sort program that has been activated internally by a report ended with an unexpected return code (rc).

The report stops executing with a condition code of 08 or 12.

Corrective Action: To clarify the reason, refer to the documentation for the sort program and to the sort messages of the job.

CTD403E PRINT MISSION HAS NOT STARTED DURING APPROPRIATE TIME FRAMELink copied to clipboard

Explanation:Highlighted, unrollable message.

The Control-D monitor issued a MODIFY command for a Printing monitor to start processing a Printing Mission. The Printing monitor did not answer during the time frame defined by optional wish WD2344 (whose default is five minutes).

The problem can occur because the Printing monitor has a low priority and the computer is heavily loaded. Therefore, the Printing monitor does not get control during the time allowed for a response.

The Control-D monitor terminates the mission NOT-OK.

Corrective Action: Assign a higher priority, or change the performance group of the Printing monitor to provide better response time from this address space (or do both). In case of a batch printing mission, make sure that enough initiators are available for handling batch printing jobs. If this is impossible or undesirable, define a higher value for the time frame defined by optional wish WD2344 in the IOADFLTL member in the IOA PARM library or specify an appropriate time-out in the Printing Mission Definition screen (screen M.S).

CTD40AE ALTERNATE INDEX ACTXREP DOES NOT MATCH THE MAIN CLUSTER ACTUSER. REBUILD ITLink copied to clipboard

Explanation:Highlighted, unrollable message.

Corrective Action: No action is required.

CTD412I DAILY STARTED IN mode MODELink copied to clipboard

Explanation: This general information message is issued when the Control-D monitor starts the DAILY (New Day) process in one of the following modes:

INT - internal mode. The Control-D monitor executes simultaneously with the New Day procedure.
EXT - external mode. The Control-D monitor starts the New Day procedure, and then shuts down the Control-D monitor.

Corrective Action: No action is required.

CTD422S OPEN OF USER DATE CONTROL-RECORD FAILED - DDNAME "DACHK"Link copied to clipboard

Explanation: Open of the file containing the User Date Control Record failed (the DACHK DD statement). Issued by the CTMCHK, CTDCHK, or CTBCHK program, which is usually activated by the New Day procedure.

Possible causes are:

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

The CTMCHK, CTDCHK, or CTBCHK program ends with errors.

Corrective Action: Correct the JCL for the job or CLIST.

CTD424S INVALID ORIGINAL SCHEDULING DATES IN USER DATE CONTROL-RECORD (POSITIONS 1-6)Link copied to clipboard

Explanation: Invalid original scheduling date in User Date Control Record (positions 1 through 6). This date should be earlier than the current installation working date. The valid format is ddmmyy or mmddyy.

Valid formats are:

ddmmyy
mmddyy

Possible causes are:

The previous run of the CTDCHK or CTMCHK program did not finish OK.
Someone has incorrectly modified the contents of the User Date Control Record (the DACHK DD statement).

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

The New Day procedure ends with errors.

Corrective Action: Correct your Date Control Record (DD statement DACHK).

CTD425S INVALID POST DATE IN USER DATES CONTROL RECORD (POSITIONS 67-72 -72)Link copied to clipboard

Explanation: The contents of the Date Control Record for this Daily are invalid.

Valid formats are:

ddmmyy
mmddyy

This message usually indicates that the User Date Control Record was incorrectly modified. The date should be earlier than or equal to the original scheduling date (defined in positions 1 through 6).

The New Day procedure ends with errors.

Corrective Action: Correct the Date Control Record (the DACHK DD statement).

CTD426W CONTROL-D (`dailytype`) DID NOT RUN FOR `nnn` DAYSLink copied to clipboard

Explanation:Highlighted, unrollable message.

The difference between the current working date and the original scheduling date (positions 1 through 6 in the Date Control Record) is more than one day. The New Day procedure has not run for nnn days. A New Day procedure is expected to run once a day.

Common causes are:

The computer has not been working for at least one day.
The Control-M or Control-D monitor has not been working for over 24 hours.
The contents of the Date Control Record were incorrectly modified for this Daily.
In the case of the New Day procedure, the computer may have been IPLed with the wrong date.
In the case of a User Daily, the Daily has not run for a few days.

The value of dailytype can be GENERAL for the New Day procedure or the job name of a regular User Daily job.

For User Daily jobs, processing continues. Missions are selected according to the RETRO parameter.

For the New Day procedure, this message appears highlighted on the operator console, together with the CTM427W or CTD427W and CTM428W or CTD428W messages. If the operator answers YES, processing continues, taking the RETRO parameter of each job into consideration. If the operator answers NO, the New Day procedure stops executing with an error message.

If a long period of Control-D inactivity (more than 28 days) is detected, message CTD42AW is issued before message CTD427W, and you must manually update the date in the Date Control Record (DDATEREC member) before proceeding.

Corrective Action: If the computer was IPLed with the wrong date, answer NO, correct the problem, and then activate the New Day procedure manually. Control-M or Control-D will not work until the problem is resolved.

CTD427W IS IT TRUE? (ANSWER "YES" OR "NO")Link copied to clipboard

Explanation:Highlighted, unrollable message.

The last run of the New Day procedure was more than 24 hours ago. This message appears together with the CHK426W, CTM426W, or CTD426W and CHK428W, CTM428W, or CTD428W messages. For more details, see the CHK426W message.

The General New Day procedure waits for the operator response.

CTD428W YOUR ANSWER IS:Link copied to clipboard

Explanation:Highlighted, unrollable message.

The last run of the New Day procedure was more than 24 hours ago. This message appears together with the CHK426W, CTM426W, or CTD426W and CHK427W, CTM427W, or CTD427W messages. For details, see the CHK426W message.

The New Day procedure waits for the operator response.

CTD429S {CTMCHK | CTDCHK | CTBCHK} ENDED WITH ERRORSLink copied to clipboard

Explanation: The CTMCHK, CTDCHK, or CTBCHK program ended with errors. It is activated as part of the New Day procedure. IOA Log should contain an earlier message about the error.

The New Day procedure finishes executing with a condition code of 08.

Corrective Action: Check the IOA Log for error messages. If necessary, manually correct the Date Control Record (date-3 and date-5) to allow the next run of the User Daily job. For details, see the INCONTROL for z/OS Administrator Guide.

CTD42AW PLEASE UPDATE THE DDATEREC MEMBER BEFORE YOU ANSWERLink copied to clipboard

Explanation: A long period of Control-D inactivity was detected. The last run of the New Day procedure was more than 28 days ago. This message appears after the CTD426W message and before the CTD427W message.

Corrective Action: Before proceeding, manually update the dates that appear in the DDATEREC member in the CTD PARM library and are pointed to by ddname DACHK in the Newday procedure.

CTD430E POSSIBLE ABEND OF PREVIOUS DAILY RUN!Link copied to clipboard

Explanation: A previous run of the same New Day procedure probably abended.

The New Day procedure terminates with errors.

Corrective Action: Correct the Date Control Record and rerun the New Day procedure. As a result of the last abend, dates 2, 3 and dates 4, 5, in the Date Control Record are not identical - they should be. If you correct them to the values of date 3 or date 6, a rerun of the New Day procedure schedules all the jobs in the New Day procedure for the days after dates 2-5 until the date designated in date 1 (the current original scheduling date). Do not schedule the same job twice.

For more information, see the Control-M for z/OS User Guide or the Control-D and Control-V User Guide.

CTD431I {CTMCHK | CTDCHK | CTBCHK} STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTMCHK, CTDCHK, or CTBCHK program, which is activated by the New Day procedure, started executing.

Corrective Action: No action is required.

CTD432I {CTMCHK | CTDCHK | CTBCHK} ENDEDLink copied to clipboard

Explanation: This information message indicates that the CTMCHK, CTDCHK, or CTBCHK program, which is activated by the New Day procedure, ended normally.

Corrective Action: No action is required.

CTD433S DIFFERENCE BETWEEN CURRENT AND LAST RUN OF THIS DAILY IS NEGATIVE BY `num` DAYSLink copied to clipboard

Explanation: The current working date in the computer is before the last original scheduling date of this New Day procedure.

This message is issued by the New Day procedure as a result of incorrect dates in the Date Control Record. For more details, see the Control-M for z/OS User Guide or the Control-D and Control-V User Guide.

The New Day procedure stops executing with an error message.

Corrective Action: Correct the contents of the Date Control Record, and rerun the Daily. If this problem occurs under the New Day procedure, call your system programmer. The problem should be resolved immediately as the Control-M or Control-D monitor will not be able to operate. Check whether the computer has been IPLed with the correct date.

CTD434W THIS DAILY HAS ALREADY BEEN RUN TODAYLink copied to clipboard

Explanation: The same New Day procedure has already been run today. The current working date in the computer is equal to the last original scheduling date - positions 1 through 6 in the Date Control Record (the DACHK DD statement).

For details, see the Control-M for z/OS User Guide or the Control-D and Control-V User Guide.

Processing terminates with a return code of 8.

Corrective Action: Check the result of the run carefully for possible errors. If the Control-M or Control-D monitor is up and running, there is no need to run the New Day procedure - it was probably started by accident. In any case, have your INCONTROL administrator look at the problem. It is possible that the computer was IPLed with the wrong date.

CTD435S OPERATOR RESPONDED "NO"Link copied to clipboard

Explanation: The operator answered NO to the CHK428W, CTM428W, or CTD428W message.

The New Day procedure stops executing.

Corrective Action: Correct the problem (usually date related), and rerun the New Day procedure.

CTD436S USER DATE CONTROL-RECORD IS EMPTYLink copied to clipboard

Explanation: The data set described by the DACHK DD statement is empty (the New Day procedure).

The New Day procedure terminates with errors.

Corrective Action: Correct the JCL for the job and rerun it.

CTD439I ONLY (`num`) FREE ENTRIES ARE LEFT ON THE COMMUNICATION FILE - PLEASE INCREASE ITS SIZELink copied to clipboard

Explanation: This information message indicates that the Control-D Communication file is almost full.

In this message, num is the number of free entries left in this file.

The printing of the reports will continue.

Corrective Action: At the earliest possible time, bring down Control-D, then follow these steps:

Increase the COMSIZE Installation Parameter. For more information, see the section on setting Control-D installation parameters in the Control-D chapter of the INCONTROL for z/OS Installation Guide.
Run the CTDFRCOM utility in order to create a new communication file.
Bring up Control-D.

CTD43AE NO FREE RECORDS IN COM FILE. PRINT MISSION TERMINATES ABNORMALLYLink copied to clipboard

Explanation: The current print mission cannot obtain a free record in the communications file.

Each print mission requires one record in the COM file for communicating between the Control-D monitor and the print task. A free record is obtained before the print task is started released when it ends.

The print mission ends NOTOK.

Corrective Action: Increase the size of the COM file by increasing the value of the COMSIZE parameter in CTDPARM. You can do this using ICE, as follows:

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 2, Control-D Dataset Parameters.
Increase the size of the COMSIZE parameter.
Return to the Minor Steps Selection screen, and select Minor Step 3, Save Parameters into Product Libraries.
Select Minor Step 5, Format the Communication File.

You can now rerun the print mission.

CTD452I FORMATTING OF `activeFile` FILE STARTEDLink copied to clipboard

Explanation: This information message indicates that the Control-M Active Jobs file (AJF) or the Control-D Active Missions file (AMF) is currently being formatted.

Corrective Action: No action is required.

CTD453S OPEN OF DATES CONTROL-RECORD FAILED. DDNAME "DACHK"Link copied to clipboard

Explanation: Open of Control-M or Control-D Date Control record failed in the DACHK DD statement). This error message is issued by the CTMFRM (Control-M), or CTDFRM (Control-D) program as part of the New Day procedure. Possible causes are:

The DACHK DD statement is missing.
The data set (member) described by the DACHK DD statement is not the Control-M or Control-D Date Control Record.

Corrective Action: Correct the JCL for the New Day procedure.

CTD454E FORMAT (`format_pgm`) ALREADY RUN TODAYLink copied to clipboard

Explanation: An attempt was made to run the New Day procedure twice in the same day. The New Day procedure issues format_pgm. This program should not run more than once a day.

Possible values of format_pgm are:

CTMFRM - formats the Active Jobs file (AJF) in Control-M
CTDFRM - formats the Active Missions file (AMF) in Control-D

The AJF or AMF is not formatted, but the New Day procedure continues to execute other programs in the program list.

Corrective Action: Check why the New Day procedure is being run twice, and whether jobs or missions were accidentally ordered twice because the General Date Control Record was erroneously modified.

CTD455S LAST FORMAT DATE GREATER THAN ORIGINAL SCHEDULING DATE IN CONTROL-D DATES CONTROL-RECORDLink copied to clipboard

Explanation: The last format date is later than the original scheduling date in the Control-M Date Control record or the Control-D Date Control record. The New Day procedure issues this message. For more details, see the appropriate user guide.

New Day processing stops.

Corrective Action: Correct the Control-M or Control-D Date Control record, and run the New Day procedure again.

CTD456S OPEN OF `activeFile` FILE FAILED. DDNAME "`ddName` "Link copied to clipboard

Explanation: Open of the Control-M Active Jobs file (AJF) or the Control-D Active Missions file (AMF) defined in the ddName DD statement failed. The New Day procedure calls the program that issues this message.

In Control-M, ddName is DACKPT and activeFile is the Active Jobs file (AJF).

In Control-D ddName is DAAMF and activeFile is the Active Missions file (AMF).

Possible causes are:

The ddName DD statement is missing.
The data set described by the ddName DD statement is not the AJF or the AMF.
The data set described by the ddName DD statement is the AJF or the AMF, but of another Control-M or Control-D monitor, or of a different version of Control-M or Control-D.

Program execution stops with a condition code of 08.

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

CTD457S OPEN OF BACKUP FILE FAILED. DDNAME "DABKUP"Link copied to clipboard

Explanation: Open of backup file for the Active Jobs file (AJF) or Active Missions file (AMF) defined in the DABKUP DD statement failed. This error message is issued by the CTMFRM (Control-M) or CTDFRM (Control-D) program, which is usually activated as part of the New Day procedure.

Possible causes are:

The DABKUP DD statement is missing.
The data set described by the DABKUP DD statement is not the Active Jobs Backup file or Active Missions Backup file.
The data set described by the DABKUP DD statement is the Control-M Active Jobs Backup file or the Control-D Active Missions Backup file, but of another Control-M or Control-D monitor, or of a different version of Control-M or Control-D.

Program execution stops with a condition code of 08.

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

CTD458S ERROR IN `activeFile` - RECORD 0. SHOULD BE FORMAT OR FREELink copied to clipboard

Explanation: Record 0 of the activeFile file contains incorrect data. This error message is issued by the CTMFRM (Control-M) or CTDFRM (Control-D) program, which is usually activated as part of the New Day procedure.

In Control-M activeFile is the Active Jobs file (AJF).

In Control-D activeFile is the Active Missions file (AMF).

Possible causes of this message are:

The activeFile file is corrupt.
The data set described by the DACKPT DD statement (Control-M) or the DAAMF DD statement (Control-D) is not the activeFile file, but is very similar to one.

Program execution stops with a condition code of 08.

Corrective Action: Check the validity of the data set described by the DACKPT or DDAMF DD statement. If necessary, correct the JCL, and rerun the New Day procedure.

If the activeFile is corrupt, use a standard copy utility, like IEBGENER, to copy activeFile, and send it to BMC Customer Support. If necessary, run the FORMCKP utility to reformat the Active Jobs file or the CTDFRAMF utility to reformat the Active Missions file. However, these utilities also erase all the jobs or missions in the respective files.

CTD459I `activeFile` IS RESTORED FROM BACKUPLink copied to clipboard

Explanation: This information message indicates the beginning of a rerun of the New Day procedure after an earlier abend during the format of activeFile.

In Control-M, activeFile is the Active Jobs file (AJF).

In Control-D activeFile is the Active Missions file (AMF).

activeFile is restored from the appropriate backup file and processing continues normally.

Corrective Action: No user action is required.

CTD45CE `func` OPERATION FOR "COM" FILE FAILED. RC=`rc`Link copied to clipboard

Explanation: An internal error occurred in the CTDCIO internal module while the Active Mission file was being formatted.

The Active Mission file is not formatted.

Corrective Action: Note the values of func and rc and contact BMC Customer Support.

CTD460S DATE CONTROL-RECORD IS EMPTYLink copied to clipboard

Explanation: The DACHK DD statement describes an empty data set or member.

For more information, see the sections that describe NEW DAY processing in the Control-M and Control-D chapters of the INCONTROL for z/OS Administrator Guide.

Program execution stops with a condition code of 08.

Corrective Action: Correct the Control-M or Control-D Date Control Record and run the New Day procedure again.

CTD461S ERROR WHILE FORMATTING IOA CONDITIONS FILELink copied to clipboard

Explanation: I/O error while formatting the IOA Conditions file.

Possible causes are:

The data set described by DD statement DARESF is not the IOA Conditions file.
An I/O error occurred while reading the IOA Conditions file.

Program execution stops with a condition code of 08.

Corrective Action: Correct and run the New Day procedure again. In case of an I/O error, you may need to recreate the IOA Conditions file. This erases all the conditions from the file.

CTD462S INVALID LAST FORMAT DATE IN DATE CONTROL RECORDLink copied to clipboard

Explanation: Invalid format of last format date in the Date Control Record. This message is issued by the CTMFRM or CTDFRM program, which is activated as part of the New Day procedure. The valid format is ddmmyy or mmddyy.

Possible causes are:

Someone has modified the contents of the Date Control Record incorrectly.
The record described by the DACHK DD statement is not the Control-M Date Control Record or the Control-D Date Control Record.

For more information, see NEW DAY processing in the Control-M and Control-D chapters of the INCONTROL for z/OS Administrator Guide.

Program execution stops with a condition code of 08.

Corrective Action: Do one or both of the following, as necessary:

Correct the JCL for the Daily Subsystem, and rerun it.
Correct the format date in the Date Control Record, and rerun the New Day procedure.

CTD463S INVALID ORIGINAL SCHEDULING DATE IN DATE CONTROL RECORDLink copied to clipboard

Explanation: Invalid original scheduling date in the Date Control Record. The valid format is ddmmyy or mmddyy.

Possible causes are:

The record described by the DACHK DD statement is not the Control-M General Date Control Record or the Control-D General Date Control Record.
Someone modified the contents of the General Date Control Record incorrectly.

This message is issued by the CTMFRM (Control-M) or CTDFRM (Control-D) program. These programs are activated as part of the New Day procedure.

For more information, see the sections that describe NEW DAY processing in the Control-M and Control-D chapters of the INCONTROL for z/OS Administrator Guide.

Program execution stops with a condition code of 08.

Corrective Action: Do one or both of the following, as necessary:

Correct the JCL for the New Day procedure and rerun it.
Correct the original scheduling date in the General Date Control Record and rerun the New Day procedure.

CTD464S FILE ALLOCATED TO DDNAME "`ddName` " IS NOT YOUR `activeFile`Link copied to clipboard

Explanation: The data set described by the ddName DD statement is not the file specified by activeFile.

In Control-M, ddName is DACKPT and activeFile is the Active Jobs file (AJF).

In Control-D ddName is DAAMF and activeFile is the Active Missions file (AMF).

Possible causes are:

The data set described by the ddName DD statement is not the AJF or the AMF.
The data set described by the ddName DD statement is the AJF or the AMF, but of another Control-M or Control-D monitor, or of a different version of Control-M or Control-D.

Program execution stops with a condition code of 08.

Corrective Action: Correct the problem in the data set name indicated by the ddName DD statement, and run the New Day procedure again.

CTD465S FILE ALLOCATED TO DDNAME "DABKUP" IS NOT A BACKUP OF `activeFile`Link copied to clipboard

Explanation: The data set described by the DABKUP DD statement is not a backup of activeFile.

In Control-M, activeFile is the Active Jobs file (AJF).

In Control-D activeFile is the Active Missions file (AMF).

Possible causes are:

The data set described by the DABKUP DD statement is not the AJF or the AMF.
The data set described by the DABKUP DD statement is the AJF or the AMF, but of another Control-M or Control-D monitor, or of a different version of Control-M or Control-D.

Program execution stops with a condition code of 08.

Corrective Action: Correct the Control-M Date Control Record and rerun the affected procedure.

CTD466S NEED MORE MEMORY TO FORMAT `activeFile`Link copied to clipboard

Explanation: There is not enough memory to format the activeFile file.

The New Day procedure issues this message.

In Control-M, activeFile is the Active Jobs file (AJF) or the History file (HST).

In Control-D activeFile is the Active Missions file (AMF).

Program execution stops with a condition code of 08. Control-M and Control-D monitors will not start after this error.

Corrective Action: To enable monitors to start, set REGION=0M and rerun the affected procedure. If the REGION is already set to 0M, then ensure that the MVS exit IEFUSI allows sufficient virtual storage memory to be allocated above the 16M line. For example, since each record of the above files requires 1024 bytes of storage, a file containing 200,000 records requires 200M of storage above the line.

CTD468I FORMATTING OF `activeFile` ENDEDLink copied to clipboard

Explanation: This information message indicates that the New Day procedure finished formatting the activeFile file.

This message is issued by the CTMFRM (Control-M) or CTDFRM (Control-D) program, which is activated as part of the New Day procedure.

In Control-M, activeFile is the Active Jobs file (AJF).

In Control-D activeFile is the Active Missions file (AMF).

Corrective Action: No action is required.

CTD470S ERROR WHILE FORMATTING THE `activeFile`, FILE WAS NOT FORMATTEDLink copied to clipboard

Explanation: An error occurred during formatting of the activeFile file.

The New Day procedure issues this message.

In Control-M, activeFile is the Active Jobs file (AJF).

In Control-D activeFile is the Active Missions file (AMF).

Program execution stops with a condition code of 08.

Corrective Action: Look for a previous message that describes the type of error. Correct it and rerun the New Day procedure.

CTD475S DATE IN AMF FILE GREATER THAN CURRENT DATELink copied to clipboard

Explanation: The DATE field in the Active Mission file is incorrect because it is greater than the current date. This message is issued by the AMF formatting program during the NEWDAY procedure.

The NEWDAY procedure terminates.

Corrective Action: Perform one of the following actions:

Reformat the Active Mission file using the CTDFRAMF utility.
Fix the DATE field (YYMMDD format). Set the DATE to yesterday in block 0 of the Active Mission file.

CTD476S DATE IN AMF FILE WAS MORE THAN 28 DAYS AGOLink copied to clipboard

Explanation: The Control-D monitor was inactive for more than 28 days. The DATE field in the Active Mission file differs from the current date by more than 28 days. This message is issued by the AMF formatting program during the NEWDAY procedure.

The NEWDAY procedure terminates.

Corrective Action: Perform one of the following actions:

Reformat the Active Mission file using the CTDFRAMF utility.
Fix the DATE field (YYMMDD format). Set the DATE to yesterday in block 0 of the Active Mission file.

CTD477S INVALID DATE IN AMF FILELink copied to clipboard

Explanation: The DATE field in the Active Mission file is incorrect. This message is issued by the AMF formatting program during the NEWDAY procedure.

The NEWDAY procedure terminates.

Corrective Action: Perform one of the following actions:

Reformat the Active Mission file using the CTDFRAMF utility.
Fix the DATE field (YYMMDD format). Set the DATE to yesterday in block 0 of the Active Mission file.

CTD485I ATTEMPTING TO OBTAIN SYNCHRONIZATION TIMESTAMPLink copied to clipboard

Explanation: This information message indicates that a backup mission (or the CTDDELRP utility) is trying to synchronize with the Control-D monitor.

For an explanation of the synchronization process, see the MONA59I message.

Corrective Action: No action is required.

CTD486I SYNCHRONIZATION TIMESTAMP OBTAINED: `timeStamp`Link copied to clipboard

Explanation: This information message indicates that a backup mission or the CTDDELRP utility is trying to synchronize with the Control-D monitor.

The displayed timestamp is a hexadecimal representation of the time-of-day clock value used for synchronization. It is displayed for tracking and debugging purposes.

For an explanation of the synchronization process, see the MONA59I message.

Corrective Action: No action is required.

CTD487E SYNCHRONIZATION FAILURE. RC: `rc`Link copied to clipboard

Explanation: The decollation task could not provide a timestamp during synchronization for the backup job, the CTDDELRP utility, or the CTVJAR utility.

Valid values for rc, and their explanations, are:

rc	Explanation
16	Error access the Active User file
20	Internal error

The backup job, the CTDELRP utility, or the CTVJAR utility fails.

Corrective Action: Do the following:

If the return code is 16, see the preceding CTDU99E message.
If the return code is 20, notify BMC Customer Support.

When the error occurs, perform the following steps:

Enter the log screen.
Use the SHOW command.
Change the value of the ALL MESSAGE TYPES field to Y.
Print the log.

CTD487S MIGRATION FILE WAS FORMATTED WITH INCORRECT COMPRESSION TABLELink copied to clipboard

Explanation: A migration file was opened for multistage migration but the migration file was formatted with an old compression table. A multistage migration mission stores log data about the last three migration stages in the SYSDATA record. If a migration file formatted with an old compression table is used, this data is lost.

The migration mission ends NOTOK.

Corrective Action: Reformat the migration file by unloading it by means of job CTDUFDUL and reloading it by means of job CTDUFRST from the Control-D JCL library.

CTD488I PROCESS IS WAITING FOR SYNCHRONIZATIONLink copied to clipboard

Explanation: This information message indicates that the backup job, the CTDDELRP utility, or the CTVJAR utility waits for the decollation task to provide a timestamp.

Corrective Action: No action is required.

CTD488W MIGRATION OF "CDAM `name` " FROM OSS TO OSS REJECTEDLink copied to clipboard

Explanation: While building a migration mission, the Control-D monitor found a request to migrate the CDAM name file from one OSS media to another OSS media, but this type of migration is not allowed.

This CDAM file is deleted from the list of CDAM files to be migrated.

Corrective Action: Change the migration path of the problematic migration mission.

CTD494E OPEN OF BACKUP UTILITY MESSAGES FILE FAILEDLink copied to clipboard

Explanation: The open of the SYSIN DD statement failed. This message is produced by the ANALYZE step of the backup/migration job.

Possible causes are:

The SYSIN DD statement has been deleted or its JCL has been modified incorrectly.
The data set referenced by SYSIN DD statement cannot be opened for sequential read.

The requested backup or migration is not performed. The status of the Backup or Migration Mission is changed to ENDED NOTOK.

Corrective Action: Do the following:

Check the ANALYZE step of the backup or migration job in the library referenced by the DADSKL DD statement.
Modify the JCL as required. For the correct format for SYSIN JCL, see the BKPDFDSS sample skeleton job in the Control-D or Control-V SKL library.
Rerun the Backup or Migration Mission.

CTD496E OPEN OF ACTIVE MISSIONS FILE FAILED. DDNAME "DAAMF"Link copied to clipboard

Explanation: Open of the Active Missions file failed. This file is referenced by the DAAMF DD statement.

This message is produced by the ANALYZE step of the backup or migration job. This step executes the CTDBKC program, which analyzes the output of the backup or migration process.

Possible causes are:

The DAAMF DD statement is missing.
The data set referenced by the DAAMF DD statement is not the Active Missions file.
The data set referenced by DAAMF DD statement is the Active Missions file for another Control-D or Control-V monitor or a different version of Control-D or Control-V.

Backup or migration of the requested data sets is not performed. The status of the backup or migration mission remains BACKUP or MIGRATE IN PROCESS. This status will change to ENDED OK after the backup or migration job is corrected and rerun.

Corrective Action: Do the following:

Check the ANALYZE step of the backup or migration job in the library referenced by the DADJOB DD statement.
Modify or add the DAAMF DD statement.
Rerun the job.
To prevent a recurrence of this problem, make the same modification to the backup or migration skeleton JCL in the library referenced by the DADSKL DD statement.

CTD497E UNABLE TO UPDATE STATUS OF MISSION `misName` ODATE=`misoDate` TIMESTAMP=`misTime` (RC=`rc`)Link copied to clipboard

Explanation: where rc is the return code of the Active Mission file service.

Backup or migration job cannot update, in the Active Mission file, the status of the mission indicated in the message.

The mission remains in status IN PROCESS.

Corrective Action: Use the appropriate utility (BKPRESET or MIGRESET) to reset the mission status. If the problem recurs, prepare the IOA LOG and contact BMC Customer Support.

Messages CTD500 through CTD5xxLink copied to clipboard

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

CTD506S SCHEDULING FAILED FOR MISSION `missionName`Link copied to clipboard

Explanation: Scheduling failed for the missionName mission.

This error message is issued by the CTDMIS program, which is usually activated as part of the New Day procedure. The IOA Log contains additional messages concerning the reason for failure.

The mission is not placed in the Active Missions file. The system action depends on the severity of the problem. If the New Day procedure ends, it issues a return code of 08.

Corrective Action: Check the IOA Log for the reason.

CTD511I PLACED ON ACTIVE MISSIONS FILE - `descr`Link copied to clipboard

Explanation: This information message indicates that a mission was placed on the Active Missions file and the mission is now in the WAIT SCHEDULE state.

Corrective Action: No action is required.

CTD520S INVALID FUNCTION CODE PASSED TO CTDMIS - NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: Internal error. Invalid function code from the CTDMIS New Day procedure internal program.

The mission is not scheduled.

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

CTD521S UNEXPECTED END OF SCHEDULING CARDS.Link copied to clipboard

Explanation: The table has been corrupted; mission data ended unexpectedly.

The CTDMIS program (the New Day procedure) terminates with a condition code of 08.

Corrective Action: Try to restore the table to its original state. If you cannot, have your system programmer call BMC Customer Support for assistance.

CTD526S ERROR IN SCHEDULING DATA FORMAT Link copied to clipboard

Explanation: The mission definition has been corrupted. Scheduling data do not conform to Control-D valid format.

This message is followed by a number of CTD527 messages, which contain all the statements that belong to the damaged mission order. The symbol * appears in the line under the erroneous data.

The CTDMIS program will terminate with a condition code of 08.

Corrective Action: Try to restore the original mission definition. If you cannot, have your system programmer call BMC Customer Support for assistance. If it is a batch New Day procedure using a permanent Date Control Record, correct the contents of the record before running the New Day procedure again. See also the CTD056S message.

CTD527S CARD = `card`Link copied to clipboard

Explanation: The mission definition has been corrupted. This message follows the CTD526 message, and displays each statement in the damaged mission order in the scheduling table. An asterisk * appears in the line under a damaged statement.

The CTDMIS program ends with errors.

CTD528I MISSION `missionName` ODATE `odate` PLACED ON ACTIVE MISSIONS FILE-`description`Link copied to clipboard

Explanation: This information message indicates that the missionName mission was placed on the Active Missions file, and the task is now in WAIT SCHEDULE state.

Corrective Action: No action is required.

CTD531W MISSION `missionName` ODATE `odate` - SCHEDULING CANCELLED BY USER EXITLink copied to clipboard

Explanation: Scheduling cancelled by User Exit CTDX001, because the member did not pass user checking. User Exit CTDX001 is activated for a mission order before it is placed on the Active Missions file. If the exit specifies to the New Day procedure not to place the mission on the Active Missions file, this message is issued.

The mission order is not placed on the Active Missions file.

Corrective Action: Look for additional messages in the IOA Log clarifying the reason for the cancel. It is usually security. If you cannot find a reason, consult your system programmer.

CTD532S OPEN OF CONTROL-D ACTIVE MISSIONS FILE FAILED. DDNAME "DAAMF"Link copied to clipboard

Explanation: Open of Control-D Active Missions file failed. This error message is issued by the CTDMIS program, which is usually activated as part of the New Day procedure.

Possible causes are:

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 of a different version of Control-D, or of a different Control-D monitor.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the job or CLIST and rerun it.

CTD533S CONTROL-D ACTIVE MISSIONS FILE IS FULL. NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation:Highlighted, unrollable message.

Control-D Active Missions file is full. No more space in the Active Missions file for new mission orders.

The mission order is not placed in the Active Missions file.

Corrective Action: Consult your system programmer immediately. Maybe you need to increase the size of the Active Missions file.

CTD534S SEVERE ERROR ON CONTROL-D ACTIVE MISSIONS FILE. NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: Severe error on Control-D Active Missions file.

Possible causes are:

An I/O error.
The file allocated to the DAAMF DD statement is not the Control-D Active Missions file.
The Active Missions file was corrupted.

The CTDMIS Control-D program, which is activated as part of the New Day procedure, ends with errors.

Corrective Action: Have your system programmer call BMC Customer Support for assistance. Check whether the file was updated from two computers without global ENQ control, or perhaps by an unauthorized program.

CTD535S CONTROL-D ACTIVE MISSIONS FILE IS BEING FORMATTED. TRY AGAIN LATERLink copied to clipboard

Explanation: The Control-D Active Missions file is currently being formatted. The New Day procedure (CTDNDAY) is currently running and is formatting the file.

This error message is issued by the CTDMIS program, which is usually activated as part of the New Day procedure.

Corrective Action: Try again later.

CTD536S SEVERE ERROR IN SCHEDULING DATA CARDSLink copied to clipboard

Explanation: A severe error was found in the scheduling data statements.

This error message is issued by the CTDMIS program, which is usually activated as part of the New Day procedure.

Scheduling fails for the mission order. The New Day procedure terminates with a condition code of 08.

Corrective Action: Look for additional messages concerning the error, correct the error and rerun.

CTD537S NO MORE INTERNAL WORKAREA. SEE MESSAGES AND CODES FOR REQUIRED ACTIONLink copied to clipboard

Explanation: Internal work areas of the New Day procedure have been exhausted. The mission order contains more data than can be handled by the current release of Control-D.

The New Day procedure terminates with a condition code of 08.

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

CTD538E `type memName` ODATE `odate` SCHEDULING FAILEDLink copied to clipboard

Explanation: Scheduling failed for the memName mission. This message is issued by the CTDMIS program, which is usually activated as part of the New Day procedure. The IOA Log or the New Day procedure output contains an earlier message concerning the reason for failure.

The mission member is not placed in the Active Missions file.

Corrective Action: Check the IOA Log and the New Day procedure output for the reason.

CTD539W `type memName` ODATE `odate` SCHEDULING CANCELLED BY USER EXITLink copied to clipboard

Explanation: Scheduling was cancelled by User Exit CTDXOO1. The specified member did not pass user checking. User Exit CTDX001 is activated for each mission order before it is placed on the Active Missions file. If the exit specifies to the New Day procedure not to place the mission order on the Active Missions file, this message is issued.

The mission order is not placed on the Active Missions file.

Corrective Action: Look for additional messages in the IOA Log clarifying the reason for the cancel. It is usually security. If you cannot find a reason, consult your system programmer.

CTD540W LOADING OF USER EXIT "CTDX001" FAILED. NO USER EXIT PROCESSING WILL BE PERFORMEDLink copied to clipboard

Explanation: Loading of Control-D User Exit CTDX001 by the New Day procedure failed.

This could be due to one of the following:

The installation is not using User Exit CTDX001, and erased the default exit supplied with Control-D.
IOA Load library is not in the missions load modules search list (STEPLIB + Linklist).
There is insufficient memory.
Another system-oriented reason described in the syslog of the New Day procedure.

As a result, no user checking is performed for the mission order. For more details, see Control-D exits in the Control-D chapter of the INCONTROL for z/OS Installation Guide.

Corrective Action: Notify the INCONTROL administrator. This is a potentially serious situation that may be an attempt to violate security.

CTD541S INTERNAL ERROR - INVALID RETURN CODE FROM CTDINPLink copied to clipboard

Explanation: An internal error has occurred. The CTDINP module of Control-D issued an unknown return code.

The mission is not placed on the Active Missions file. The New Day procedure terminates with a condition code of 08.

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

CTD542S INTERNAL ERROR - INVALID PARAMETER CODE PASSED TO CTDINPLink copied to clipboard

Explanation: An internal error has occurred. An invalid parameter was passed to the CTDINP Control-D module.

The mission is not placed on the Active Missions file. The New Day procedure terminates with a condition code of 08.

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

CTD543S THE FILE ALLOCATED TO DDNAME "DAAMF" IS NOT A VALID ACTIVE MISSIONS FILELink copied to clipboard

Explanation: The Active Missions file is not valid. This error message is issued by the CTDMIS program, which is usually activated as part of the New Day procedure.

Possible causes are:

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 of a different version of Control-D, or of a different IOA installation.

Program execution stops with a condition code of 08.

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

CTD555S INSUFFICIENT STORAGE. INCREASE THE REGION SIZELink copied to clipboard

Explanation: There was insufficient memory to perform a task.

The action that could not be performed accompanies this message. It may vary depending on the environment in which the message was issued.

Corrective Action: For jobs, increase the REGION size. For TSO, log on again using a larger SIZE parameter or exit one of the screens.

CTD567E USER NOT AUTHORIZEDLink copied to clipboard

Explanation: The function requested is not authorized for the user.

This message is issued by the IOA security mechanism.

Corrective Action: Check with your system security administrator.

CTD5A0W `mediaName` - DEVICE `number` - ERROR IN CONNECTION TO STORAGE MACHINE: `st. maName`, SUBSYSTEM: `smName`, RC: `rc`Link copied to clipboard

Explanation: The IOASMON monitor, a migration job, or the CTVCLMIG utility, failed to connect to the Filetek storage machine because the CONNECT function failed.

The probable cause for this failure is that the maximum number of connections to the storage machine was reached.

The variables in this message are:

mediaName - name of the Filetek storage machine media as defined in IOASPRM
number - number of the IOASMON device in which the error occurred
st.maName - name of the Filetek storage machine When it does not appear in the message, the name used is that of the storage machine as defined in the storage machine configuration member.
smName - SM subsystem name
rc - return code from the CONNECT function

If an IOASMON monitor fails, the monitor continually retries to connect until it succeeds, or until the device task is brought down. If a migration job or CTVCLMIG failed, it terminates with errors.

Corrective Action: Check the return code of the CONNECT function against the Filetek documentation, and correct the problem accordingly. This might require reducing the number of active device tasks to reduce the number of connections to the storage machine. If a migration job or CTVCLMIG failed, rerun the job or utility.

CTD5A3I `mediaName` - DEVICE `num` - EMSG `msgText`, RC: `rc`Link copied to clipboard

Explanation: This information message is issued when a message is received from the Filetek storage machine subsystem.

The variables in this message are:

mediaName - the name of Filetek storage machine media defined in IOASPRM
num - presently not in use
msgText - the message received from the storage machine
rc - the return code from the function

Corrective Action: No action is required.

CTD5A5E `mediaName` - DEVICE `num` - ERROR IN DISCONNECT TO STORAGE MACHINE: `st.maName`, SUB SYSTEM `smName`, RC: `rc`Link copied to clipboard

Explanation: The IOASMON monitor, migration job, or the CTVCLMIG utility failed to disconnect from the Filetek storage machine because the DISCONNECT function failed.

The variables in this message are:

mediaName - the name of the Filetek storage machine media as defined in IOASPRM
num - the number of the IOASMON device in which the error occurred
st.maName - the name of the Filetek storage machine When this is omitted, the name of the storage machine defined in the storage machine configuration member is used.
smName - the SM subsystem name
rc - the return code from the DISCONNECT function

The connection remains active. In the case of a migration job, or if the CTVCLMIG utility fails to disconnect, the job or utility terminate with errors.

Corrective Action: Check the return code of the DISCONNECT function against the Filetek documentation, and correct the problem accordingly. In the case of a migration job or CTVCLMIG utility failure, rerun the job or utility correspondingly.

CTD5ACE ERROR INITIALIZING INPUT MEDIA `mediaName`Link copied to clipboard

Explanation: Initialization of an input media for multistage migration failed.

The attempt to initialize the mediaName media, in order to copy files from it to the target media, failed.

Files that should have been copied from this input media to the target media are skipped. Subsequent files are processed.

Corrective Action: Check other messages received in the migration job to determine the cause for the failure. Fix the problem and reorder or rerun the migration mission.

CTD5ADE ERROR TERMINATING INPUT MEDIA `mediaName`Link copied to clipboard

Explanation: The process of terminating the mediaName input media for a multistage migration failed.

Subsequent files in the migration job are processed.

Corrective Action: Check other messages received in the migration job to determine the cause for the failure. Fix the problem, and reorder or rerun the migration mission.

CTD5AEE ERROR ALLOCATING MIGRATED FILE `fileName`Link copied to clipboard

Explanation: A failure occurred while attempting to allocate the fileName input media file that should have been moved to another media.

Subsequent files in the migration job are processed.

Corrective Action: Check other messages generated by the migration job to determine the cause for the failure. Fix the problem and reorder or rerun the migration mission.

CTD5AFE ERROR OPENING MIGRATED FILE `fileName`Link copied to clipboard

Explanation: A failure occurred while attempting to open the fileName input media file that should have been moved to another media.

Subsequent files in the migration job are processed.

Corrective Action: Check other messages generated by the migration job to determine the cause for the failure. Fix the problem and reorder or rerun the migration mission.

CTD5AGE ERROR CLOSING MIGRATED FILE `fileName`Link copied to clipboard

Explanation: A failure occurred while attempting to close the fileName input media file that should have been moved to another media.

Subsequent files in the migration job are processed.

Corrective Action: Check other messages generated by the migration job to determine the cause for the failure. Fix the problem and reorder or rerun the migration mission.

CTD5AHE ERROR READING MIGRATED FILE fileName

Explanation: A failure occurred while attempting to read the fileName input media file that should have been moved to another media.

The migration of the fileName file is stopped. Subsequent files in the migration job are processed.

Corrective Action: Check other messages generated by the migration job to determine the cause for the failure. Fix the problem and reorder or rerun the migration mission.

CTD5ALE INVALID FUNCTION CODE SPECIFIED FOR CTVAMIGLink copied to clipboard

Explanation: An internal error has occurred. The CTVAMIG routine received an invalid function code.

The migration job continues processing but does not use “continuous migration”. A scratch volume is used for files migrated in this migration job.

Corrective Action: Notify BMC Customer Support. Reorder or rerun the migration mission.

CTD5AME CTVAMIG TERMINATED WITH ERROR. RC: `rc`Link copied to clipboard

Explanation: A failure occurred in the CTVAMIG routine.

The CTVAMIG routine reads and updates migration stages in sequence without skipping a stage.

The migration job continues processing but does not use “continuous migration”. A scratch volume is used for files migrated in this migration job.

Corrective Action: Check other messages generated by the migration job to determine the cause for the failure. Fix the problem and rerun or reorder the migration mission.

CTD5ANI UNABLE TO ALLOCATE TAPE VOLUME `volser`, SCRATCH TAPE WILL BE USED INSTEADLink copied to clipboard

Explanation: This information message indicates that an attempt to allocate a tape volume in order to perform continuous migration failed.

The migration job attempted to allocate a specific volume that was used in a previous migration job in order to add files migrated by the current migration job after the last file on the volume.

In this message, volser identifies the tape volume that could not be allocated.

A scratch volume is allocated for the files migrated by current migration job.

Corrective Action: Check other messages to determine the cause for the failure.

CTD5B0E OPTFILE=`dsn` -FDB REWRITE FAILEDLink copied to clipboard

Explanation: The migration process failed while rewriting the File Definition Block (FDB).

During the migrate-to-disk process, several extents may be written. After writing the last extent, the FDB is rewritten to the first extent.

All migrated file extents are deleted. The migration for this CDAM terminates with an error.

Corrective Action: Determine the cause of the rewrite failure and rerun the migration job.

CTD5B3S DEVTYPE FAILED FOR DDNAME `ddName`, RC = `rc`Link copied to clipboard

Explanation: A tape migration job failed to obtain the file’s device type.

The DEVTYPE macro for the DDOPT DD statement failed. This macro is used after a file is written to tape so that the device type can be used for cataloging the file. The return code is the hexadecimal return code in register 15 from the DEVTYPE macro.

The migration process is terminated.

Corrective Action: Record the return code (rc). Consult your system programmer. If necessary, contact BMC Customer Support.

CTD5B4E CATALOGING `dsn` FAILED, RC: `rc`Link copied to clipboard

Explanation: Tape migration failed to catalog the dsn migrated file. The return code (rc) is the hexadecimal return code in register 15 from the CATALOG macro.

This CDAM data set is not migrated. The migration process continues to migrate other CDAM files.

Corrective Action: Record the DSN (dsn) and the return code (rc). Contact BMC Customer Support.

CTD5B5S IOAT2A FAILED IN JFCBEXAD TRANSLATION - RC: `rc`Link copied to clipboard

Explanation: Tape migration failed to get the JFCB extension.

Routine IOAT2A, which translates JBCBEXAD from token to address, received the return code rc.

This CDAM data set is not migrated. The migration process continues to migrate other CDAM files.

Corrective Action: Record the return code. Contact BMC Customer Support.

CTD5B6S IOASLOS - SORT ENDED WITH RC OTHER THAN 0Link copied to clipboard

Explanation: OSS migration failed to build platter and volume tables using the IOASLOS routine. The IOASLOS routine failed to sort platter and volume tables.

The migration process is terminated.

Corrective Action: Check the migration skeleton job. If you cannot resolve the problem, contact BMC Customer Support.

CTD5B8S INVALID RC FROM CTVTPCP - UNABLE TO CALCULATE DATASET LENGTH IN FEETLink copied to clipboard

Explanation: The CTVTPCP routine, which calculates tape lengths, returned a non-zero return code.

Tape migration failed to calculate the length of the data set on tape.

The migration process is terminated.

Corrective Action: Record the return code. Contact BMC Customer Support.

CTD5B9E UNABLE TO MIGRATE `dsn` - HAS MORE THAN 32767 BLOCKSLink copied to clipboard

Explanation: The number of CDAM blocks exceeds 32767.

The OSS migration process cannot migrate files which contain more than 32767 blocks.

The dsn CDAM data set is not migrated. The migration process continues to migrate other CDAM files.

Corrective Action: Reduce the report size or divide the report so that the number of CDAM blocks required does not exceed 32767.

CTD5BAS PARM IS OMITTED - PLEASE SPECIFY REQUIRED PARAMETERSLink copied to clipboard

Explanation: The PARM parameter is not specified in the migration job.

The user must specify a media name and prefix or the keyword “NOCHECK”.

The migration process is terminated.

Corrective Action: Add the PARM parameter and specify a media name and prefix or the NOCHECK keyword.

CTD5BBS INVALID MEDIA = `mediaName` WAS SPECIFIED IN PARM - CALL ADMINISTRATORLink copied to clipboard

Explanation: The migration process received an invalid media name in the PARM field.

The media name should be specified in the NAME parameter of the IOASPRM member in the IOA PARM library.

The migration process is terminated.

Corrective Action: Change the IOASPRM member or the migration skeleton job so a valid media name is specified in the migration job.

CTD5C0S CANNOT ALLOCATE DEVICE: `deviceId`Link copied to clipboard

Explanation: The OSS device could not be obtained for OSS migration, or the tape drive could not be allocated for tape migration.

The CTVSRVD program must execute before OSS migration to ensure that the IOA Archive Server releases the first device defined for OSS. A tape drive must be allocated for tape migration.

The migration process is terminated.

Corrective Action: For OSS migration, ensure that the CTVSRVD program executes before the migration step. For tape migration, check if the device is available for allocation. If no error is discovered, contact BMC Customer Support.

CTD5C2E LOCATE ERROR FOR FILE `dsn` - FILE SKIPPEDLink copied to clipboard

Explanation: The migration process encountered a data set that could not be located.

A CDAM extent or index file was not cataloged.

The entire CDAM data set or index file is not migrated. Other data sets continue to migrate.

Corrective Action: Correct the problem and rerun the Migration Mission.

CTD5C7S INVALID UNIT NAME DEFINED IN IOASPRM: `unitName`Link copied to clipboard

Explanation: The unit name of the target media is unknown to the migration process.

The TYPE parameter in the IOASPRM member contains an invalid value.

The migration process is terminated.

Corrective Action: Correct the TYPE parameter. Rerun the Migration Mission.

CTD5C8S DEVICE `deviceId` IS OUT OF SPACELink copied to clipboard

Explanation: No more space is available on the deviceId device.

There is no volume with enough space for this migration.

The migration process is terminated.

Corrective Action:Free space on the volumes available to the migrated files allocation. Rerun the migration mission.

CTD5C9S IOASLOS RETURNED NON-ZERO RC: `rc`Link copied to clipboard

Explanation: The IOASLOS module failed.

OSS migration uses the IOASLOS module to load OSS platter and volume tables to memory.

The migration process is terminated.

Corrective Action: Check the OSS migration skeleton for errors and rerun the Migration Mission. If the problem persists, contact BMC Customer Support.

CTD5CBS OPEN OF DDNAME `ddName` FAILEDLink copied to clipboard

Explanation: The data set referenced by the ddName DD statement could not be opened.

Possible causes are:

The ddName DD statement is missing.
The data set referenced by the ddName DD statement does not exist.

The migration process is terminated.

Corrective Action: Check the migration skeleton job for errors and rerun the Migration Mission.

CTD5CFI STOP TIME FOR MIGRATION PROCESS WAS REACHED - EXITINGLink copied to clipboard

Explanation: This information message indicates that the time for ending the migration process has passed. The stop time defined in the MIGENDTM parameter in the IOASPRM member in the IOA PARM library prevents the migration process from interfering with online work during the day.

The migration process is terminated when the currently migrating CDAM data set finishes migrating.

Corrective Action: In the future, start the migration process earlier, or change the MIGENDTM parameter to a later time. Order the migration mission again the next night to complete the migration.

CTD5CGS ERROR IN `routineName`. RC IN R15: `rc`Link copied to clipboard

Explanation: The routineName internal routine failed.

The migration process terminates with a return code of 16 in register 15.

Corrective Action: Contact BMC Customer Support.

CTD5CHS NO MORE ROOM ON DISKS WITH PREFIX: `prefix`Link copied to clipboard

Explanation: An attempt to write a data set on disk failed because the data set requires more space than is available on any disk with the prefix prefix.

The data set is not written or cataloged.

Corrective Action: Do one or more of the following:

Assign the prefix prefix to one or more additional disks.
Delete unneeded data sets from disks with the prefix prefix.
Specify a different disk prefix for the data set that was not written.

CTD5CIE ERROR DELETING FILE `dsn` - FILE SKIPPEDLink copied to clipboard

Explanation: The migration job has encountered a file which could not be deleted.

The migration job could not delete the dsn file during cleanup after an error occurred while writing a migrated file to DASD.

The file is not deleted.

Corrective Action: Determine why the delete failed. Delete the dsn file before rerunning the migration process.

CTD5D0E `mediaName` - DEVICE `devicenam` - ERROR IN ACCESS TO OAM. RC = `rc` REASON CODE = `rsn`Link copied to clipboard

Explanation: The OSREQ IBM macro was unable to carry out ACCESS for the specified OAM.

The variables in this message are:

mediaName - the OAM media name as defined in IOASPRM Blanks are indicated if issued by means of a migration process.
devicenam - the task ID that issued the messageBlanks are indicated if the ID was issued by means of a migration process.

The system terminates any activity with OAM.

Corrective Action: Refer to IBM documentation. Consult either the OAM Programmer’s Reference or the DFSMSdfp Diagnosis Reference.

CTD5D1E `mediaName` - DEVICE `devicenam` - ERROR IN UNACCESS TO OAM. RC = `rc` REASON CODE = `rsn`Link copied to clipboard

Explanation: The OSREQ IBM macro was unable to carry out UNACCESS for the specified OAM.

The variables in this message are:

mediaName - OAM media name defined in IOASPRMBlanks indicated that it was issued by a migration process.
devicenam - the task ID that issued the messageBlanks indicate that the ID was issued by a migration process.
rc - OSREQ return code
rsn - OSREQ reason code

Corrective Action: For an explanation of the return and reason codes, refer to OAM programmer reference material or DFSMSdfp diagnosis reference material, and take appropriate corrective action.

CTD5D5E ERROR DURING QUERY - `objName collName` RC=`rc` REASON CODE=`rsn`Link copied to clipboard

Explanation: The OSREQ IBM macro was unable to QUERY the objName object in the collName collection.

The variables in this message are:

objName - the object requested by OSREQ (and in collection collName)
collName - the transformed name of the CDAM file being migrated
rc - the return code issued by OAM
rsn - the reason code issued by OAM

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

If the migration job issues the message, LOCATE for collName fails, and collName does not migrate.
If IOASMON issues the message, collName is not retrieved for viewing or printing.

Corrective Action: For an explanation of the return and reason codes, refer to OAM programmer reference material or DFSMSdfp diagnosis reference material, and take appropriate corrective action.

CTD5DFI MEDIANM DEVICE `devicenam` - DB2 MSG RECEIVED - `db2msg`Link copied to clipboard

Explanation: This information message relays a message returned from DB2 while processing IBM macro OSREQ.

The variables in this message are:

devicenam - the ID of the media device
db2msg - the message returned from DB2 using OSREQ

Corrective Action: For an explanation of DB2 messages, refer to IBM documentation.

CTD5DGS OAM IS NOT ACTIVE IN SYSTEMLink copied to clipboard

Explanation: IBM OAM software was not active. Control-V attempted to initiate a connection to OAM.

The system terminates the action attempted by Control-V.

Corrective Action: Activate OAM.

CTD5DIS FAILED TO LOAD DSNALI MODULE OF DB2Link copied to clipboard

Explanation: Control-V was unable to load the DSNALI module.

The DSNALI module verifies updates to OAM files. There are two responses to an attempt to update an OAM file:

If an OAM file is successfully updated, the migration program performs a DB2 COMMIT action.
If an OAM file fails to update, the migration program performs an ABORT (terminates) and does not load the DSNALI module.

The migration program terminates.

Corrective Action: Make the DSNALI module available to Control-V. Note the error message and consult your DB2 administrator.

CTD5DJE DB2 TABLES CORRUPTED - COLLECTION MATCHED AN OLD OBJECT `objName` collNameLink copied to clipboard

Explanation: An IBM OAM utility attempted to store an object over a different object with the same name. During migration to OAM, an OAM utility detected an object with the same name but different content. OAM DB2 tables may have been deleted by the user, and objects in the deleted tables may be connected to new collections. The MIG5CUE message immediately follows this message.

The variables in this message are:

objName - the object name that caused the error
collName - the collection name where the original objName resides

The system stops migration for objNamecollName. DB2 undoes migration actions performed for this collection. A LOCATE Failed Error message is issued for the OAM migrated file.

Corrective Action: Consult your DB2 administrator. Check and fix the DB2 tables.

CTD5E4E CENTERA INIT ERROR: RC=`rc`, REASON CODE=`rsn`Link copied to clipboard

Explanation: Connection to EMC Centera cannot be established. This message is followed by message CTD5E9I, which issues the Centera pool value used for connection.

The variables in this message are:

rc - return code from the EMC Centera API.
rsn - reason code from the EMC Centera API.

The job terminates with a nonzero return code.

Corrective Action: Refer to EMC Centera documentation for a description of the received reason code.

Check the pool value printed in the accompanying CTD5E9I message. If the IP addresses are not correct, update them in parameters POOL1-POOL4 in the IOASPRM member. Then rerun the migration mission or the utility that issued this message.

CTD5E5E CENTERA CLIP CREATE ERROR: RC=`rc`, REASON CODE=`rsn`, DSN=`dsn`Link copied to clipboard

Explanation: An error was detected during creation of a new EMC Centera clip for a migrated CDAM or index file.

The variables in this message are:

rc - return code from the EMC Centera API
rsn - reason code from the EMC Centera API
dsn - the name of the migrated dataset

The dsn dataset is not migrated.

Corrective Action: Refer to the EMC Centera documentation for a description of the received reason code. If you cannot resolve the problem, contact the EMC Centera experts.

CTD5E6E CENTERA BLOCK WRITE ERROR: RC=`rc`, REASON CODE= `rsn`, DSN=`dsn`Link copied to clipboard

Explanation: An error was detected while writing a block of the migrated dataset to the EMC Centera clip.

The variables in this message are:

rc - return code from the EMC Centera API
rsn - reason code from the EMC Centera API
dsn - the name of the migrated dataset

The dsn dataset is not migrated.

Corrective Action: Refer to the EMC Centera documentation for a description of the received reason code. If you cannot resolve the problem, contact the EMC Centera experts.

CTD5E7E CENTERA CLIP CLOSE ERROR: RC=`rc`, REASON CODE= `rsn`, DSN=`dsn`Link copied to clipboard

Explanation: An error was detected while closing an EMC Centera clip.

The variables in this message are:

rc - return code from the EMC Centera API
rsn - reason code from the EMC Centera API
dsn - the name of the migrated dataset

The dsn dataset is not migrated.

Corrective Action: Refer to the EMC Centera documentation for a description of the received reason code. If you cannot resolve the problem, contact the EMC Centera experts.

CTD5E8E CENTERA TERMINATE ERROR- RC=`rc`, REASON CODE= `rsn`Link copied to clipboard

Explanation: An error was detected during termination of the EMC Centera device.

The variables in this message are:

rc - return code from the EMC Centera API
rsn - reason code from the EMC Centera API

The EMC Centera connection is not terminated.

Corrective Action: Refer to the EMC Centera documentation for a description of the received reason code. If you cannot resolve the problem, contact the EMC Centera experts.

CTD5E9I POOL=`pool`Link copied to clipboard

Explanation: This information message follows message CTD5E4E.

The variable in this message is:

pool - the pool value specified in parameters POOL1-POOL4 in the IOASPRM member.

Corrective Action: No action is required.

CTD5F0E INVALID MEDIA = `mediaName` WAS SPECIFIED FOR FILE `fileName`Link copied to clipboard

Explanation: The media name specified for a file to be deleted is invalid. The CTVCLMIG utility calls the CTVDEL program to delete specified files and the media on which they reside. Some of the input for CTVDEL was invalid.

The system skips the problematic file, and continues processing.

Corrective Action: Check the media name in IOASPRM, correct the problem, and try again.

CTD5F0E INVALID MEDIA = `mediaName` WAS SPECIFIED FOR FILE `fileName`Link copied to clipboard

The system skips the problematic file, and continues processing.

Corrective Action: Check the media name in IOASPRM, correct the problem, and try again.

Messages CTD600 through CTD6xxLink copied to clipboard

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

CTD646E PRINT PLAN FILE DOES NOT EXISTLink copied to clipboard

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

Request is rejected.

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

CTD647E PRINT CONTROL-IS VALID FOR PRINT MISSIONS ONLYLink copied to clipboard

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

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

CTD649E CANNOT RERUN MISSION `missionName` ODATE `date` - TASK SUSPENDEDLink copied to clipboard

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

The rerun order is rejected.

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

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

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

This is due to one of the following:

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

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

CTD651S READ ERROR ON CONTROL-D ACTIVE MISSIONS FILE. NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

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

Possible causes are:

The file allocated to the DAAMF DD statement is not the Control-D Active Missions file.
The file allocated to the DAAMF DD statement is the Control-D Active Missions file, but it is of a different version.
Real I/O error.

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

CTD652S INTERNAL ERROR - INVALID REQUEST TO CTDUMS `request`Link copied to clipboard

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

The function requested is not performed.

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

CTD653E CANNOT `action` MISSION `missionName` ODATE `odate` - NOT HELDLink copied to clipboard

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

Delete or change request ignored.

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

CTD654E CANNOT `action` MISSION `missionName` ODATE `odate` - ALREADY DELETEDLink copied to clipboard

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

The user request is ignored.

Corrective Action: No action can be performed

CTD655E ACTIVE MISSIONS FILE IS IN USE, TRY AGAIN LATERLink copied to clipboard

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

The requested action is not performed.

Corrective Action: Try again later.

CTD656E action OF MISSION `missionName` ODATE `odate` IGNORED - STATUS HAS CHANGEDLink copied to clipboard

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

The requested action is ignored.

Corrective Action: Check the mission status and act accordingly.

CTD657E CANNOT `action` MISSION `missionName` ODATE `odate` - MAX CHANGES OVER, TRY AGAIN LATERLink copied to clipboard

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

The user request is ignored.

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

CTD658S CANNOT `action` MISSION `missionName` ODATE `odate` - UNEXPECTED CODE FROM CTDUMSLink copied to clipboard

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

The user request is ignored.

Corrective Action: Have your system programmer call Customer Support.

CTD659I `action` OF MISSION `missionName` ODATE `odate` PERFORMEDLink copied to clipboard

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

The missionName mission has been:

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

Corrective Action: No action is required.

CTD65AI AUTO REFRESH EVERY `num` SECONDS - `counter`Link copied to clipboard

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

Corrective Action: No action is required.

CTD65BI AUTO REFRESH CANCELEDLink copied to clipboard

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

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

Corrective Action: No action is required.

CTD65CE INVALID AUTO REFRESH INTERVALLink copied to clipboard

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

AutoRefresh mode is not activated.

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

CTD660E INVALID VALUE, USE "Y" OR "N"Link copied to clipboard

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

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

CTD661E AT LEAST ONE TASKTYPE MUST BE "Y"Link copied to clipboard

Explanation: At least one tasktype must be Y.

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

CTD662E AT LEAST ONE MESSAGE TYPE MUST BE "Y"Link copied to clipboard

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

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

CTD663E AT LEAST ONE OF THE FIRST TWO TYPES OF MISSION STATUS MUST BE "Y"Link copied to clipboard

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

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

CTD664S INTERNAL ERROR BEFORE CALLING CTDUMSLink copied to clipboard

Explanation: Internal error.

The function requested is not performed.

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

CTD665E CANNOT RERUN MISSION `missionName` ODATE `odate` - TASK NOT ENDEDLink copied to clipboard

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

The rerun request is ignored.

Corrective Action: Try again later.

CTD666S INTERNAL ERROR - UNEXPECTED RETURN CODE FROM CTDTDWYLink copied to clipboard

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

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

CTD667E "WHY" OPTION CAN BE USED ONLY ON TASK IN "WAIT SCHEDULE/PROCESS" STATELink copied to clipboard

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

The user request is ignored.

Corrective Action: No action is required.

CTD668S INTERNAL ERROR - UNEXPECTED RETURN CODE FROM CTDTAPR `rc`Link copied to clipboard

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

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

CTD669E ERROR ON ACTIVE MISSIONS FILE. CANNOT BUILD ZOOM SCREENLink copied to clipboard

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

Possible causes are:

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

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

CTD66AE "BYPASS" OPTION CAN BE USED ONLY ON MISSION IN "WAIT SCHEDULE/PROCESS"Link copied to clipboard

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

Corrective Action: Cancel the "BYPASS" option.

CTD670S INTERNAL ERROR. CANNOT BUILD ZOOM SCREENLink copied to clipboard

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

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

CTD671E CANNOT `action` MISSION `missionName` ODATE `odate` - IN REQUESTED CHANGE MODELink copied to clipboard

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

The request is ignored.

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

CTD672E CANNOT SAVE MISSION. INSUFFICIENT SPACE IN MISSION RECORD - USE LESS DATALink copied to clipboard

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

New mission data are not saved.

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

If the problem persists, consult BMC Customer Support.

CTD673E CANNOT `action` MISSION `missionName` ODATE `odate` - MISSION IN PROCESSLink copied to clipboard

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

The request is ignored.

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

CTD675E OPTION NOT SUPPORTED YET FOR THIS TYPE OF MISSIONLink copied to clipboard

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

The requested Zoom action is not performed.

Corrective Action: No action is required.

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

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

The following variables are used in this message:

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

The Restore Mission terminates with a status of NOTOK.

Corrective Action: No action is required.

CTD682E RC=`rc` FROM CTMMEM. MISSION `misName` TIMESTAMP=`misTime` TERMINATEDLink copied to clipboard

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

The following variables are used in this message:

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

The Restore Mission terminates with a status of NOTOK.

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

CTD686E DSN `dsn` NOT IN CATALOGLink copied to clipboard

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

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

The system action depends on the cause, as follows:

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

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

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

CTD688I RESTORE TASK STARTED.Link copied to clipboard

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

Corrective Action: No action is required.

CTD689E [[`taskType memName`] `jobName|jobId orderId`] MAXIMUM NUMBER OF MEMBERS/LINES IN MEMBER EXCEEDEDLink copied to clipboard

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

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

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

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

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

Corrective Action: No action is required.

CTD691E INVALID PARAMETERS FOR RESTORE ANALYZE PROGRAMLink copied to clipboard

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

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

Corrective Action: Do the following:

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

CTD693E CATEGORY=`cat` NOT FOUND IN MEMBER=`memName` LIBRARY=`libName`Link copied to clipboard

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

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

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

CTD694E MISSION `misName` TIMESTAMP=`misTime` FAILED TO OPEN RESTORE UTILITY MESSAGES FILELink copied to clipboard

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

The variables in this message are:

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

The restore mission ends NOTOK.

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

CTD695E NO PENDING RESTORE MISSION `misName` TIMESTAMP=`misTime` FOUND IN ACTIVE MISSION FILELink copied to clipboard

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

The variables in this message are:

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

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

The restore job only prints the restore utility log.

Corrective Action: Check the IOALOG.

CTD696E MISSION `misName` TIMESTAMP=`misTime` FAILED TO OPEN ACTIVE MISSION FILELink copied to clipboard

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

The variables in this message are:

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

The restore job only prints the restore utility log.

Corrective Action: Call your INCONTROL Administrator.

CTD696I ALL MISSIONS PROCESSED SUCCESSFULLYLink copied to clipboard

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

This message is issued by:

CLISTs that schedule missions manually
New Day procedure

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

Corrective Action: No action is required.

CTD697S SEVERE ERROR IN PROCESSING MISSIONS - PROCESSING TERMINATEDLink copied to clipboard

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

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

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

CTD698S UNABLE TO PROCESS ANY MISSIONLink copied to clipboard

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

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

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

CTD69AI NO MISSIONS WERE SCHEDULED DURING ORDERING REQUESTLink copied to clipboard

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

Corrective Action: No action is required.

CTD69BE UNABLE TO ORDER OLD MIGRATION MISSION DEFINITION. UPDATE THE MISSION AND REORDERLink copied to clipboard

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

The migration mission is not ordered.

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

CTD69EE `misname:` ONE OR MORE MANDATORY FIELDS ARE MISSING IN ON CLASS/TRNCLASS STATEMENTLink copied to clipboard

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

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

CTD69HW PENDING MISSION `misName` TIMESTAMP=`misTime` NOT FOUND IN AMF. ONE MORE ATTEMPT WILL BE PERFORMED.Link copied to clipboard

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

The variables in this message are:

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

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

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

Corrective Action: No action is required.

Messages CTD700 through CTD7xxLink copied to clipboard

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

CTD701E PLEASE FILL IN REPORT/JOB NAME OR OMIT CATEGORYLink copied to clipboard

Explanation: A category name is specified, but the report or job name is missing. A report or job must be specified as well as a category name.

Corrective Action: Either fill in a report or job name or omit the category to get a list of reports or jobs in the library.

CTD702E CTLG N CAN NOT BE SPECIFIED FOR THIS MEDIA TYPELink copied to clipboard

Explanation: The CTLG subparameter is specified as N (do not catalog the migrated files) for a medium type that is not CART. This option can be used only for a cartridge type specified as CART in the IOASPRM member.

Corrective Action: Specify Y or blank in the CTLG subparameter.

CTD710E JOBID CAN BE JOB`num` TSU`num` STC`num` * OR BLANKLink copied to clipboard

Explanation: There is an invalid value in a decollation mission JOBID field.

The JOBID field in a Decollation mission can take one of the following values only:

JOB num
TSU num
STC num
* (Asterisk )
' ' (Blank )

where num is a 5-digit value

Corrective Action: Specify a JOBID in one of the above formats, or leave the field empty.

CTD711E ON CLASS IS VALID ONLY WITH IN QUEUE=Y/E OR WITH JOBIDLink copied to clipboard

Explanation: ON CLASS is specified in the Control-D Report Definition Screen (screen R) without Y or E in the WHEN IN QUEUE field, or without specifying the JOBID. To define an ON CLASS in a report definition, the WHEN IN QUEUE field must be either Y or E, or the job ID must be specified in the JOBID field.

Corrective Action: Specify Y or E in the WHEN IN QUEUE field, or the job ID in the JOBID field, or delete the ON CLASS definition.

CTD712E VALID VALUES FOR IN QUEUE ARE "Y" "N" "E" OR BLANKLink copied to clipboard

Explanation: There is an invalid value in the WHEN IN QUEUE Decollation mission field. Valid values for WHEN IN QUEUE field in a decollation mission are Y, N, E or BLANK only.

Corrective Action: Specify either Y, N, or E in the WHEN IN QUEUE field, or leave it empty.

CTD713E JOBID CAN BE JOBnum TSUnum STCnum OR BLANK

Explanation: There is an invalid value in a decollation mission JOBID field. The JOBID field in Decollation mission can take one of the following values only:

JOB num
TSU num
STC num
' ' (Blank)

where num is a 5-digit value.

Corrective Action: Specify a JOBID in one of the above formats, or leave the field empty.

CTD714E UNTIL LINE SHOULD BE BLANK WHEN FROM LINE IS *Link copied to clipboard

Explanation: There is an invalid value in the WHEN TO LINE field in a decollation mission. If an asterisk is specified in the second WHEN FROM LINE field, the WHEN TO LINE field must be blank.

Corrective Action: Clear the WHEN TO LINE field with a blank, or change the value of the WHEN FROM LINE field.

CTD715E MASK IN JOBNAME IS ALLOWED ONLY FOR GENERIC DECOLLATIONSLink copied to clipboard

Explanation: A mask character in the JOBNAME parameter for a decollation mission is not generic. In a non-generic decollation mission, the JOBNAME parameter must be unique and cannot contain mask characters.

Corrective Action: Either make the decollation generic, or specify a unique value in the JOBNAME parameter.

CTD716E FOR RECORD LEVEL INDEX, MASK MUST HAVE LINE RANGE AND INDEX LINE +/-Link copied to clipboard

Explanation: The DO INDEX statement is invalid. A record level index was specified without a line range for the mandatory mask, or without an index line location defined as a +/- offset from the location of the line containing the mandatory mask.

If a DO INDEX statement contains the REC parameter set to Y or C, it must also contain both of the following:

a mask for the record-level index with a line range for that mask
a line offset for the index value which begins with a + or - sign.

The decollation mission is not saved or updated.

Corrective Action: Specify a page-level index (set REC to N), or specify a mask with a mask line range and an index value location which is defined as a + or - offset from the mask line.

CTD719E FOR JOBNAME_DDNAMES INDEX MIGRATION MISSION MUST BE "JOBARC"Link copied to clipboard

Explanation: A migration mission name other than JOBARC was specified in a JOB ARCHIVE decollation mission definition. Decollation definitions for the JOB ARCHIVE utility must include both the special index JOBNAME_DDNAMES and the migration mission name JOBARC.

The cursor stays in the field until the correct migration mission name is specified.

Corrective Action: Change the migration mission name to JOBARC.

CTD71AE MASK `mparm` CONFLICTS WITH INDEX `iparm` +/-Link copied to clipboard

Explanation: There is a conflict between the values specified for the following parameters, because one of these values is invalid:

the LINE or COL parameter in a MASK statement
the LINE or COL parameter in a DO INDEX or SUBINDEX statement where the value started with a + or - sign

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

The variables in this message are:

mparm - the value of the LINE or COL parameter of the MASK statement
iparm - the value of the LINE or COL parameter of the DO INDEX or SUBINDEX statement

The system waits for the parameter values to be corrected.

Corrective Action: Correct the parameter values.

CTD725I TOP OF CATEGORIES LISTLink copied to clipboard

Explanation: This information message indicates that a user attempted to jump to the previous category (using PF10) but the current category is the first category in the member.

Corrective Action: No action is required.

CTD726I BOTTOM OF CATEGORIES LISTLink copied to clipboard

Explanation: This information message indicates that a user attempted to jump to the previous category (using PF11) but the current category is the last category in the member.

Corrective Action: No action is required.

CTD751E PLEASE FILL IN MISSION NAME OR OMIT CATEGORYLink copied to clipboard

Explanation: Category name specified, but mission name missing. A mission name must be defined.

Corrective Action: Either fill in mission name or omit category name to get a list of missions in the library.

CTD769E VALID MISSION TYPE IS PRT/BKP/RSTLink copied to clipboard

Explanation: An invalid mission type was entered.

Valid mission types:

PRT - Printing Mission
BKP - Backup Mission
RST - Restore Mission

Corrective Action: Correct the mission type field.

CTD770E MISSION TYPE MUST BE SPECIFIED WHEN ENTERING A NEW MISSIONLink copied to clipboard

Explanation: Missing the mission type field on the Mission Definition screen. The mission type (PRT, BKP or RST) must be entered when defining a new mission.

Corrective Action: Enter the appropriate mission type.

CTD770S OPEN OF CONTROL-D COMMUNICATION FILE FAILEDLink copied to clipboard

Explanation: The CTDFRCOM utility, which is used to allocate and format the Control-D Communication file, could not open the file.

Possible causes are:

The DACOM 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.

CTD771I FORMATTING OF CONTROL-D COMMUNICATION FILE STARTEDLink copied to clipboard

Explanation: This information message indicates that the Control-D Communication file is currently being formatted.

Corrective Action: No action is required.

CTD772I FORMATTING OF CONTROL-D COMMUNICATION FILE ENDEDLink copied to clipboard

Explanation: This information message indicates that the formatting of Control-D Communication file by the CTDFRCOM utility ended.

Corrective Action: No action is required.

CTD773S FORMATTING OF CONTROL-D COMMUNICATION FILE - WRITE I/O ERRORLink copied to clipboard

Explanation: An I/O error occurred during formatting of the Control-D Communication file. This may occur when there is incompatibility between the definition of the Communication file in the Installation Parameters (COMSIZE in 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.

CTD774S CONTROL-D COMMUNICATION FILE WAS NOT BUILTLink copied to clipboard

Explanation: Due to a problem described by other messages, the Control-D communication file was not built. The CTDFRCOM utility stops executing with a condition code of 08.

Corrective Action: Examine the contents of the system log for additional messages that may clarify the cause of the error. If the CTD913S message is issued, follow the explanation contained in the CTD913S message. If this does not solve the problem, record all related information, including the contents of the CTD913S message, and contact BMC Customer Support.

CTD775I `monName` CONTROL-D PRINTERS CONTROL-MONITOR STARTEDLink copied to clipboard

Explanation: This information message indicates that the monName Control-D Printers Control monitor started.

Corrective Action: No action is required.

CTD776E `monName` CONTROL-D PRINTERS CONTROL-MONITOR ALREADY ACTIVELink copied to clipboard

Explanation:Highlighted, unrollable message.

Someone tried to start the monName Control-D Printers Control monitor, which is already active. The Control-D Printers Control monitor is automatically activated from the Control-D monitor. It should not be activated manually.

The monName Control-D Printers Control monitor will shut down.

Corrective Action: No action is required.

CTD777S `monName` CONTROL-D PRINTERS CONTROL-MONITOR ENDED WITH ERRORSLink copied to clipboard

Explanation:Highlighted, unrollable message.

The monName Control-D Printers Control monitor ended with errors. The IOA Log should contain additional messages concerning each specific error.

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

Corrective Action: Check the IOA Log and the system log for the reason. Call the system programmer for assistance if needed. Try to start the Control-D monitor again as soon as possible.

CTD778I `monName` ALL MODIFY/STOP COMMANDS MUST BE ISSUED BY CONTROL-D MAIN MONITOR ONLYLink copied to clipboard

Explanation: This information message indicates that the user tried to issue a MODIFY or STOP command to either the Control-D Printers Control monitor or to a Control-D secondary monitor. A MODIFY or STOP command to the Control-D Printers Control monitor or a Control-D secondary monitor can only be issued by the Control-D primary monitor.

The MODIFY or STOP command is ignored.

Corrective Action: No action is required.

CTD779I `monName` CONTROL-D PRINTERS CONTROL-MONITOR ENDEDLink copied to clipboard

Explanation:Highlighted, unrollable message.

This information message is the general message which is issued when the Control-D Printers Control monitor ends.

Corrective Action: In this message, monName is the name of the Printers Control monitor that has ended.

CTD781E FIELD MUST BE NUMERIC AND IN RANGE OF 1-255Link copied to clipboard

Explanation: An invalid value has been specified in the INTERVAL parameter. The INTERVAL parameter must be numeric, and must contain three digits in the range from 000 through 254.

Corrective Action: Correct the INTERVAL parameter.

CTD782E INVALID PRINTER NAME. YOU CAN USE ONLY NAMES DEFINED TO CONTROL-DLink copied to clipboard

Explanation: An invalid printer name has been specified in the PRINTER parameter of the Printing Mission Definition screen. The printer name specified must be defined in the Control-D Installation Parameters.

Corrective Action: Correct the PRINTER parameter.

CTD783E PLEASE FILL IN THE PRINTER NAMELink copied to clipboard

Explanation: Missing the PRINTER parameter in the Printing Mission Definition screen. The PRINTER parameter is obligatory if the DEST parameter is specified.

Corrective Action: Specify the printer name to be used for printing the bundle.

CTD784E FORM NAME MUST BE SPECIFIED FOR REQUESTLink copied to clipboard

Explanation: Missing the FORM parameter in the Printing Mission Definition screen. The FORM parameter is required if the REQUEST parameter is specified.

Corrective Action: Specify the form number or name to be used in printing the bundle.

CTD785E PLEASE FILL IN THE REQUESTLink copied to clipboard

Explanation: Missing the REQUEST parameter in the Printing Mission Definition screen. The REQUEST parameter is obligatory if the FORM parameter has been specified.

Corrective Action: Specify the REQUEST to be used in printing the bundle.

CTD788E PLEASE FILL IN THE PRINTING MISSION NAMELink copied to clipboard

Explanation: The MISSION NAME parameter on the Printing Mission Definition screen has not been specified. The MISSION NAME parameter is obligatory.

Corrective Action: Specify the Printing Mission name.

CTD789E INVALID FORMAT OF SORT PARAMETERSLink copied to clipboard

Explanation: The format of the SORT SEQ parameter of the Printing Mission Definition screen is invalid. Sort sequence numbers (1-9) must be separated by commas. For details, see the SORT parameter in the Control-D and Control-V User Guide.

Corrective Action: Correct the SORT SEQ parameter.

CTD790E INVALID SORT SEQUENCE NUMBERLink copied to clipboard

Explanation: The sort sequence number in the SORT parameter of the Printing Mission Definition screen is invalid. Valid sort sequence numbers are from 1 through 9. For details, see the SORT parameter in the Control-D and Control-V User Guide.

Corrective Action: Correct the SORT SEQ parameter.

CTD791E DUPLICATE SORT SEQUENCE NUMBERLink copied to clipboard

Explanation: The same sort sequence number was entered twice in the SORT parameter of the Printing Mission Definition screen. Each sort sequence number must be used only once.

Corrective Action: Correct the SORT SEQ parameter.

CTD795E SKELETON MEMBER NAME MUST BE FILLED IN WHEN BATCH=YLink copied to clipboard

Explanation: A value of Y was entered in the BATCH parameter, but the name of the skeleton member was not specified. When defining a batch print mission, you must specify the skeleton member name.

Corrective Action: Specify the skeleton member name or change the batch parameter to N.

CTD796E SKELETON MEMBER NAME MUST BE BLANK WHEN BATCH=NLink copied to clipboard

Explanation: The skeleton member name was specified, but the BATCH parameter was specified as N. The skeleton member name is valid only when the BATCH parameter is Y

Corrective Action: Erase the skeleton member name or change the BATCH parameter to Y.

CTD797E FREE FIELD CAN BE "CLOSE" OR "END" ONLYLink copied to clipboard

Explanation: An invalid value was specified in the FREE field.

Valid values for the FREE field are:

Corrective Action: Specify either CLOSE or END in the FREE field.

CTD798E FREE FIELD CANNOT BE "END" WHEN BATCH=NLink copied to clipboard

Explanation: END was specified in the FREE field, but the BATCH parameter was N. END is valid in the FREE parameter for batch print missions only. That is, BATCH must be set to Y.

Corrective Action: Change the value of the FREE parameter to CLOSE, or change the value of the BATCH parameter to N.

CTD79AE "MONITOR" FIELD SHOULD BE BLANK OR NUMERIC (1 - 9)Link copied to clipboard

Explanation: An invalid value was specified in the MONITOR parameter of the Printing Mission Definition.

The MONITOR Printing Mission Definition parameter specifies which Control-D Printing monitor address space processes the Printing Mission. The MONITOR parameter can be blank to allow Control-D or Control-V to automatically select the next available Printing monitor, or it can be a number from 1 through 9 to specify the Printing monitor that should process the Printing Mission.

The Printing Mission Definition is not created or saved until a valid value is entered for the MONITOR parameter.

Corrective Action: Enter a number from 1 to 9 in the field for the MONITOR parameter or leave the field blank, then save the Printing Mission Definition.

CTD79CI FORMATTING OF CONTROL-D PAGE COUNTER FILE ENDEDLink copied to clipboard

Explanation: This information message indicates that the Page Counter file was formatted successfully by the CTDFRPGC utility.

The CTDFRPGC utility terminates with a return code of 0.

Corrective Action: No action is required.

CTD79DS CONTROL-D PAGE COUNTER FILE WAS NOT BUILTLink copied to clipboard

Explanation: The Page Counter file was not formatted by the CTDFRPGC utility because an error was encountered.

The CTDFRPGC utility terminates with a return code of 8.

Corrective Action: For an explanation of the problem, see the previously issued message (CTM910S or CTM913S). Correct the problem and rerun the utility.

CTD79ES OPEN OF CONTROL-D PAGE COUNTER FILE FAILEDLink copied to clipboard

Explanation: The CTDFRPGC utility could not open the Page Counter file for formatting.

The Page Counter file is not formatted. The CTDFRPGC utility terminates with a return code of 8.

Corrective Action: Check the system log output of the job that executed the CTDFRPGC utility for messages associated with the open error. Correct the problem and rerun the utility.

CTD79FS FORMATTING OF CONTROL-D PAGE COUNTER FILE - WRITE I/O ERRORLink copied to clipboard

Explanation: The CTDFRPGC utility could not write a record to the Page Counter file during format processing.

The Page Counter file is not formatted. The CTDFRPGC utility terminates with a return code of 8.

Corrective Action: Check the system log output of the job that executed the CTDFRPGC utility for messages associated with the open error. Correct the problem and rerun the utility.

CTD7A0S PAGE COUNTER FILE FULL. PAGE COUNTING TERMINATESLink copied to clipboard

Explanation: An attempt was made to add a record to the Page Counter file during decollation processing, but no space remains.

Processing of the Page Counter file terminates. The decollation process continues.

Corrective Action: Ignore this message if Page Counter file processing is not needed because the ON PAGE parameter is not specified in any Printing Mission Definition. If Page Counter file processing is needed, stop the Control-D Decollation monitor, delete the Page Counter file (CTD PGC), and use job CTDFRPGC to format a new CTD PGC file with a larger PGCSIZE value. Then restart the Control-D Decollation monitor.

CTD7A1I DDCARD "DAPGC" MISSING. PAGE COUNTING TERMINATESLink copied to clipboard

Explanation: This information message indicates that the DAPGC DD statement was not defined in the Control-D Decollation monitor JCL. The Control-D Decollation monitor could not initialize Page Counter file processing because the Page Counter file is not referenced by the DAPGC DD statement.

The Control-D Decollation and Printing monitors continue normal execution but Page Counter file processing is disabled.

CTD7A2S INTERNAL ERROR IN FUNCTION `func`. PAGE COUNTING TERMINATESLink copied to clipboard

Explanation: The Control-D Decollation monitor encountered an internal error during Page Counter file processing. The following are possible causes of the problem:

Page Counter file corruption
Insufficient space allocated for the Page Counter file (usually due to a large number of PRINT missions)

The Control-D Decollation and Printing monitors continue normal execution but Page Counter file processing is disabled.

Messages CTD800 through CTD8xxLink copied to clipboard

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

CTD800E PLEASE FILL IN JOBNAME Link copied to clipboard

Explanation: Missing job name. The JOBNAME field is obligatory.

Corrective Action: Fill in the name of the job. This decollating mission will process the reports (outputs) of the specified job name.

CTD801E PLEASE FILL IN OWNER ID Link copied to clipboard

Explanation: Missing owner ID. The owner ID field is obligatory.

Corrective Action: Fill in the owner ID. This parameter identifies the user who requests Control-D services. This parameter is mainly used by the Control-D security mechanism.

CTD802E INVALID FORMAT OF DAYS PARAMETER Link copied to clipboard

Explanation: Invalid format specified in the DAYS parameter. The DAYS parameter should contain 1-31, ALL, +1, +3, and so on. For more details, see the DAYS parameter in the Control-D and Control-V User Guide.

Corrective Action: Correct the contents of the field.

CTD803E "ALL" PARAMETER MIXED WITH SPECIFIC - CORRECT Link copied to clipboard

Explanation: The ALL parameter was specified together with specific days in the DAYS parameter or the WDAYS parameter. You cannot specify WDAYS or DAYS with the ALL option.

Corrective Action: Omit either the ALL option or the SPECIFIC DAYS option.

CTD804E INVALID FORMAT OF WDAYS PARAMETER Link copied to clipboard

Explanation: Invalid format of WDAYS parameter. WDAYS parameter should contain 0-6, ALL, +1, and so on. For more details, see the WDAYS parameter in the Control-D and Control-V User Guide.

Corrective Action: Correct the WDAYS field.

CTD805E MAXWAIT SHOULD BE 00-31 OR 99 Link copied to clipboard

Explanation: The MAXWAIT parameter value is invalid. MAXWAIT should be in the range from 00 through 31 (days in which to execute the mission) or 99 (forever).

Corrective Action: Correct the MAXWAIT field.

CTD806E EXPECTED CONTINUATION NOT RECEIVED (AFTER ",") Link copied to clipboard

Explanation: The DAYS or WDAYS parameter ended with a comma. Additional data is expected after the comma.

Corrective Action: Correct the parameter.

CTD807E DAYS OPTION AND WDAYS OPTION CANNOT BE MIXED Link copied to clipboard

Explanation: The DAYS parameter and the WDAYS parameter were specified together. The WDAYS parameter cannot appear with the DAYS parameter.

Corrective Action: Select either WDAYS or DAYS.

CTD808E DATES PARAMETER CONFLICTS WITH DAYS, WDAYS OR MONTHS OPTION Link copied to clipboard

Explanation: The DATES parameter was mixed with DAYS, WDAYS or MONTHS parameters. The DATES parameter must appear alone.

Corrective Action: Erase any data in the DAYS, WDAYS and MONTHS parameters.

CTD809E CANNOT MIX DATES OPTIONS WITH CONFCAL OPTION Link copied to clipboard

Explanation: The DATES and CONFCAL parameters were both specified. These parameters cannot be specified together.

Corrective Action: Omit either the DATES or CONFCAL specification.

CTD810E CANNOT MIX MINIMUM/PDS WITH OPTIONS DAYS, WDAYS, MONTHS, DATES OR CONFCALLink copied to clipboard

Explanation: The MINIMUM and PDS parameters were specified with DAYS, WDAYS, MONTHS, DATES or CONFCAL parameters. The MINIMUM and PDS parameters must appear without any date-related parameters.

Corrective Action: Specify either the MINIMUM and PDS parameters or the date-related parameters, but not both.

CTD811E MINIMUM AND PDS MUST BE FILLED IN TOGETHERLink copied to clipboard

Explanation: The MINIMUM parameter was specified, but the PDS field is empty, or vice versa. MINIMUM and PDS parameters must be filled in together.

Corrective Action: Fill in both the MINIMUM and PDS fields.

CTD812E INVALID CONDITION DATE REFERENCELink copied to clipboard

Explanation: Invalid condition date reference specified. Date reference should be ODAT, PREV, ****, or mmdd (ddmm). For more details, see these parameters in the Control-D and Control-V User Guide.

Corrective Action: Correct the date reference.

CTD813E MISSING/INVALID CONDITION OPTION. TRY "+"- ADD OR "- "- DELETELink copied to clipboard

Explanation: Invalid or missing condition option. Condition option should be + for ADD, or - for DELETE. For more details, see these parameters in the Control-D and Control-V User Guide.

Corrective Action: Insert + or - in the condition option field.

CTD814E INVALID ACTIONLink copied to clipboard

Explanation: Invalid action specified in DO statement. For valid actions, see the Control-D and Control-V User Guide.

Corrective Action: Correct the DO action field.

CTD815E INVALID URGENCY. USE "R"- REGULAR, "U"- URGENT OR "V"- VERY URGENTLink copied to clipboard

Explanation: Invalid SHOUT urgency specified. SHOUT urgency should be R for regular, U for urgent, or V for very urgent. For more details, see these parameters in the Control-D and Control-V User Guide.

Corrective Action: Fill in R, U, or V in the SHOUT urgency field.

CTD816E INVALID "WHEN" ATTRIBUTELink copied to clipboard

Explanation: Invalid WHEN attribute of SHOUT statement.

WHEN should be one of the following:

OK
NOTOK

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

Corrective Action: Correct the WHEN field.

CTD817E INVALID SHOUT DESTINATION CODELink copied to clipboard

Explanation: Invalid SHOUT destination code.

SHOUT destination code should be one of the following:

OPER
OPER2
USERID-usrid
TSO-logonid

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

Corrective Action: Correct the SHOUT destination field.

CTD818E PLEASE FILL IN THE "IN" PREREQUISITE CONDITION NAMELink copied to clipboard

Explanation: Missing IN prerequisite condition name. The condition date reference was specified without a corresponding condition name.

Corrective Action: Fill in the IN prerequisite condition name field.

CTD819E PLEASE FILL IN THE PREREQUISITE CONDITION NAMELink copied to clipboard

Explanation: Missing prerequisite condition name in DO COND statement. At least one condition is expected in DO COND statement.

Corrective Action: Fill in the prerequisite condition name.

CTD820E USE OF PREV/NEXT DATE REFERENCE CONFLICTS WITH PDS/MINIMUM OPTIONSLink copied to clipboard

Explanation: A PREV (or NEXT) date reference was specified for a job scheduled by the PDS parameter. There is no next date or previous date when the job is scheduled according to the status of the library.

Corrective Action: Use another valid date reference.

CTD821E ONLY CODE OPTION "- " ALLOWED FOR DATE REFERENCE $$$$/****Link copied to clipboard

Explanation: Code option + was specified for a generic date reference. You cannot add a prerequisite condition to all possible dates of the year.

Corrective Action: Enter "-" in the code option or use a different date reference.

CTD822E REDUNDANT TEXT IN SHOUT PARAMETERLink copied to clipboard

Explanation: The SHOUT WHEN parameter contains data which is not relevant to the SHOUT option specified, or the SHOUT WHEN is empty.

Corrective Action: Erase the redundant text.

CTD823E PLEASE FILL IN THE SHOUT LINE BEFORE THIS MESSAGE LINELink copied to clipboard

Explanation: A message is filled in, but the SHOUT line before it is empty.

Corrective Action: Fill in the SHOUT WHEN field. If necessary, fill in the TO destination field as well.

CTD824E PLEASE FILL IN THE MESSAGELink copied to clipboard

Explanation: There is no message in the SHOUT statement.

Corrective Action: Fill in the message.

CTD827E INVALID DATA, ONLY "A","P","N" AND BLANK ARE ACCEPTABLELink copied to clipboard

Explanation: Invalid data specified for the SEARCH parameter.

The SEARCH parameter has the following options:

A - Search the Active User Report List.
P - Search the Permanent User Report List.
N - Do not search the Report Lists.
" " (Blank) - The default value, which is taken from optional Wish WD0933, is used.

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

Corrective Action: Correct the SEARCH field.

CTD829E REDUNDANT TEXT, OR FILL IN THE PREVIOUS "ON" LINELink copied to clipboard

Explanation: A WHEN page identification criterion or a DO USER statement was entered without an ON statement. On the following Report Decollating screen, If there is data on the WHEN (line 2) or DO line (line 3), there must be data on the ON line (line 1).

Copy

=================================================================
                DEF COPIES 01 LVL USER 05 DEST MAX COPIES
                1. ON (CLASS, DSN, SYSDATA, SYSLOG, SYSJCL, SYSMSG) PRT DEST MAX COPIES 05 PRINTING PARAMETERS
                2. WHEN LINE 001- 005 COL 010- 070 PRINT Y ...... STRING = MONTHLY A/R
                3. DO PRINT BY MORNING
            =================================================================

Corrective Action: Fill in the ON line (line 1), or erase the data from the WHEN (line 2) or DO line (line 3).

CTD830E INVALID "ON" VALUELink copied to clipboard

Explanation: Invalid ON statement.

ON should be one of the following:

CLASS
DSN
SYSOUT
SYSDATA
SYSLOG
SYSJCL
SYSMSG

Corrective Action: Correct the ON parameter.

CTD832E PLEASE FILL IN THE CLASSLink copied to clipboard

Explanation: ON CLASS has been specified without the letter of the class.

Corrective Action: Fill in the letter of the class.

CTD833E PLEASE FILL IN THE DSNLink copied to clipboard

Explanation: ON DSN has been specified without the Compressed Dataset Access Method selection criteria. The selection criteria specified must be a valid Compressed Dataset Access Method (CDAM) retrieval parameter, such as PREFIX, PGMSTEP, and so on.

For a list of valid CDAM parameters, see the Control-D and Control-V User Guide.

Corrective Action: Fill in the selection criteria.

CTD834E FROM LINE GREATER THAN UNTIL LINELink copied to clipboard

Explanation: The FROM line is greater than the UNTIL line in the page identification criteria.

Corrective Action: Change either the FROM line or the UNTIL line.

CTD835E FROM COL GREATER THAN UNTIL COLLink copied to clipboard

Explanation: The FROM column is greater than the UNTIL column in the page identification criteria.

Corrective Action: Change either the FROM column or the UNTIL column.

CTD836E INVALID VALUE. TRY "O"- OR "A"- AND OR BLANKLink copied to clipboard

Explanation: Invalid AND/OR option specified. The valid options are A for and relation O for or relation, blank for no additional WHEN line.

Corrective Action: Fill in A, O, or blank.

CTD837E EXPECTING ADDITIONAL "WHEN" DATA. AND/OR FIELD IS MARKED IN PREVIOUS "WHEN" LINELink copied to clipboard

Explanation: An additional WHEN line has been displayed due to an A or O in the AND/OR parameter, but the line is empty.

Corrective Action: Fill in the additional WHEN line or delete the A or O in the previous WHEN line.

CTD838E PLEASE FILL IN A SEARCH STRINGLink copied to clipboard

Explanation: WHEN LINE/COLUMN references have been entered, but the search string is missing. If line and column references are used, the search string is obligatory.

Corrective Action: Fill in the search string.

CTD839E INVALID VALUE. TRY "E", "A", "S" OR BLANKLink copied to clipboard

Explanation: The user entered an invalid value. E, A, S, or blank are the only values valid in this field.

Corrective Action: Enter the correct value.

CTD83AE INVALID VALUE. TRY "Y", "N", "S" OR BLANKLink copied to clipboard

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

Corrective Action: Enter the correct value.

CTD841E PLEASE FILL IN AT LEAST ONE PRINTING MISSION NAMELink copied to clipboard

Explanation: DO PRINT has been selected, but the Printing Mission name is missing. The Printing Mission name is obligatory when DO PRINT is used.

Corrective Action: Enter the Printing Mission name.

CTD842E PLEASE FILL IN AT LEAST ONE BACKUP MISSION NAMELink copied to clipboard

Explanation: DO BACKUP has been selected, but the Backup Mission name is missing. The Backup Mission name is obligatory when DO BACKUP is used.

Corrective Action: Enter the Backup Mission name.

CTD843E PLEASE FILL IN THE REPORT NAMELink copied to clipboard

Explanation: DO NAME has been selected, but the report name is missing. The report name is obligatory when DO NAME is used.

Corrective Action: Enter the report name, or *. For more details, see the Control-D and Control-V User Guide.

CTD847E REDUNDANT TEXT IN "WHEN" LINE. ERASE OR FILL IN LINE/COL RANGELink copied to clipboard

Explanation: There is data in the WHEN page identification criteria line AND/OR field, but no data in the LINE or COL range. In the following Report Decollating screen, if there is data in the PRINT, REF NEXT PAGE, CONT ID, AND/OR, or STRING fields, then LINE and COL must also be filled in.

WHEN LINE 001- 005 COL 010- 070 PRINT Y ......AND/OR A STRING = MONTHLY A/R

Corrective Action: Fill in the LINE or COL range, or erase the PRINT, REF NEXT PAGE, and so on, data fields.

CTD848E PLEASE FILL IN THE AND/OR FIELD IN THE PREVIOUS "WHEN" LINELink copied to clipboard

Explanation: Two consecutive WHEN lines are specified without AND/OR relations between them.

Corrective Action: Erase the second WHEN line or do as the message says.

CTD849E EITHER "LEVEL" OR "USER" CAN BE MARKED AS "*" BUT NOT BOTHLink copied to clipboard

Explanation: An asterisk (*) has been inserted in both the LEVEL field and the USER field of a DO USER statement.

Corrective Action: Choose one field, and clear the other.

CTD84AE THE VALUE CONFLICTS WITH MULTI-SLink copied to clipboard

Explanation: The value S for the MUTLI parameter and the value Y for the STORE parameter are invalid.

Corrective Action: Leave the value of the MULTI parameter blank and set the value of the STORE parameter to N.

CTD84BE INVALID VALUE. TRY “S” OR BLANKLink copied to clipboard

Explanation: The value specified for the field where the cursor is positioned is invalid.

Corrective Action: Set the value of the field to S or leave it blank.

CTD84CE FILL IN THE MASK RULER NAMELink copied to clipboard

Explanation: DO MASKRUL has been selected, but the MASK ruler name is missing. A MASK ruler name is required when using DO MASKRUL.

Corrective Action: Enter a MASK ruler name. For more details, see the INCONTROL for z/OS Administrator Guide, and the Control-D and Control-V User Guide.

CTD850E "USER" MUST BE MARKED AS "*"Link copied to clipboard

Explanation: There is data in the DO USER LINE or COL field, but the USER data field is not set to *.

If either the DO USER LINE or COL field is specified, then the USER data field must be set to *. For more information, see DO USER in the Control-D and Control-V User Guide.

Corrective Action: Enter * in the USER data field, or clear the LINE and COL fields.

CTD851E "USER" MUST BE FILLED INLink copied to clipboard

Explanation: DO USER is specified, but the USER field is blank. When DO USER is specified, the USER field must be filled in.

Corrective Action: Fill in the USER field.

CTD852E FROM/UNTIL COL ARE OBLIGATORY WHEN USING "*" USER/LEVEL REFERENCELink copied to clipboard

Explanation: An asterisk (*) was entered in the USER field in the DO USER parameter, but the FROM and UNTIL COL fields are unspecified. FROM and UNTIL COL fields must be specified when * is used for the USER field.

Corrective Action: Fill in the FROM and UNTIL column references.

CTD853E FROM/UNTIL COL ARE OBLIGATORY WHEN USING "*" NAME REFERENCELink copied to clipboard

Explanation: An asterisk (*) has been entered in the DO NAME field, but the FROM and UNTIL COL fields are unspecified. FROM and UNTIL COL fields must be specified when * is used for DO NAME.

Corrective Action: Fill in the FROM and UNTIL column references.

CTD854E "NAME" MUST BE MARKED AS "*"Link copied to clipboard

Explanation: There is data in the DO NAME LINE and COL fields, but the NAME data field is not set to *.

If the DO NAME LINE and COL fields are entered, then the NAME data field must be set to *. For more information, see DO NAME in the Control-D and Control-V User Guide.

Corrective Action: Enter * in the NAME data field, or erase the LINE and COL fields.

CTD855E WHEN USING CLASS "*", NO OTHER CLASS CAN BE SPECIFIEDLink copied to clipboard

Explanation: Invalid class mixture specified. When specifying class *, no other class can be specified. For more information, see the Control-D and Control-V User Guide.

Corrective Action: Correct the CLASS field.

CTD856E THIS CLASS IS INVALID FOR GENERIC JOB NAMESLink copied to clipboard

Explanation: Y was entered in the GENERIC field, but the data entered in the ON CLASS field contradicts the installation parameters. If Y was entered in the GENERIC field, then the ON CLASS option must contain one of the Generic classes specified during Control-D installation.

Corrective Action: Check the GENCLAS parameter of the CTDPARM and enter the correct one in the ON CLASS field.

CTD857E INVALID CLASS. THIS CLASS IS DEDICATED FOR GENERIC JOBNAMES ONLYLink copied to clipboard

Explanation: N was entered in the GENERIC field, but the data entered in the ON CLASS field contradicts the Installation Parameters. If N was entered in the GENERIC field, then the ON CLASS option must not contain one of the Generic classes specified during Control-D installation.

Corrective Action: Check the GENCLAS parameter of the CTDPARM and enter the correct one in the ON CLASS field.

CTD858E ONLY "ON CLASS" IS VALID FOR GENERIC DECOLLATING MISSIONSLink copied to clipboard

Explanation: Y was entered in the GENERIC field, but the ON statement does not contain the CLASS option. A Generic decollating mission can contain ON statements only with the CLASS option.

Corrective Action: Correct the ON statement. For more information, see the Report Decollating Parameters chapter in the Control-D and Control-V User Guide.

CTD859E IN Q "N" IS INVALID FOR GENERIC DECOLLATING MISSIONSLink copied to clipboard

Explanation: N was entered in the WHEN IN QUEUE field despite the fact that Y was entered in the GENERIC field. The parameter specified in the WHEN IN QUEUE field for Generic decollating missions must be either Y or blank.

Corrective Action: Enter Y or blank in the WHEN IN QUEUE field. For more information, see the Report Decollating Parameters chapter in the Control-D and Control-V User Guide.

CTD85AE "APPROVAL NAME" MUST BE FILLED INLink copied to clipboard

Explanation: DO APPROV is specified, but the APPROV field is blank. When DO APPROV is specified, the APPROV field must be filled in.

Corrective Action: Fill in the APPROV field.

CTD860E PREVIOUS "ON" STATEMENT HAS ONLY EMPTY "DO" AND "WHEN" LINESLink copied to clipboard

Explanation: The user started to enter data in the fields of the new ON statement without entering data in the DO and/or WHEN fields of the previous ON statement. The ON statement must contain at least one non-empty WHEN or DO field.

Corrective Action: Enter data in the WHEN or DO fields of the previous ON statement, or erase data from the fields of the current ON statement.

CTD861E INVALID FORMAT OF `%%varname`, OR POS+LTH NOT IN RANGELink copied to clipboard

Explanation: An invalid format of parameters was detected for a variable or variable function. The variable or variable function was specified in a DO or WHEN statement.

For variable %%varname:

The statement has the following valid format, where POS (startpos) and LTH (len) must both be numeric and not greater than 9.

DO doname %%variable(startpos,len)

or

WHEN …
STRING %%variable(startpos,len)

The specified range may be invalid for one of the following reasons:
- No range is present.
- Range was not enclosed in parentheses.
- Range contains non-numeric values.
- Range is logically wrong.
For variable function %%varname:

Currently, only the %%$CELL function is supported.

The $CELL function has the following valid format, where col is the Excel column letter in a range from A to IU and row is the Excel row, a number greater than 0 and not greater than 255.

DO SET %%$CELL(col[row])

The specified column and row may be invalid for one of the following reasons:
- Both col and row are not present.
- No col is present.
- Col contains a digit.
- Row contains a letter.
- Col or row is out of range.

Corrective Action: Correct the DO or WHEN statement. For more information, see the DO or WHEN parameters in the Control-D and Control-V User Guide.

CTD863E MONITOR CAN BE " " OR "1" FOR PRIMARY MONITOR OR "2-9" FOR SECONDARY MONITORSLink copied to clipboard

Explanation: Invalid monitor number specified. The MONITOR field should be blank or 1 for the primary monitor, or 2-9 for secondary monitors.

Corrective Action: Correct the MONITOR field.

CTD864E INVALID MONITOR SPECIFIED FOR GENERIC MISSIONLink copied to clipboard

Explanation: Invalid monitor specified for generic mission. Generic missions can only be processed by the monitor specified in the GENMON Installation Parameter (in CTDPARM).

Corrective Action: Change the MONITOR field of the decollating mission to the value specified in the GENMON parameter.

CTD865E INVALID MONITOR SPECIFIED. MONITOR NOT DEFINED IN CTDPARMLink copied to clipboard

Explanation: Invalid monitor specified. The number of Control-D monitors is defined in the CTDMON# Installation Parameter (in CTDPARM).

Corrective Action: Change the MONITOR field of the decollating mission to a value not higher than that specified in the CTDMON# parameter.

CTD866E INVALID LINE OPTIONLink copied to clipboard

Explanation: An invalid option was typed.

Valid options are:

H - header option
F - footer option
D - delete option
I - insert after line option
B - header before line option
C - column editing option
Blank - no option

Corrective Action: Specify a valid option.

CTD867E HEADER/FOOTER CANNOT CONTAIN A REGULAR SCROLLABLE (BLANK) LINELink copied to clipboard

Explanation: Either the H option was specified after a scrollable line, or the F option was specified before a scrollable line. Header and footer sections must be entirely unscrollable. Header lines may not be preceded by scrollable unmarked lines, and the footer lines may not be followed by scrollable unmarked lines.

Corrective Action: Correct the header or footer specifications.

CTD868E AT LEAST ONE LINE MUST BE DEFINED AS A SCROLLABLE (BLANK) LINELink copied to clipboard

Explanation: No line in the page was left unmarked. At least one line must be scrollable and unmarked.

Corrective Action: Unmark at least one line in the page.

CTD869E INVALID CHARACTER IN "CUT" SPECIFICATION LINELink copied to clipboard

Explanation: An invalid range ID was specified in the Cut line. Range ID must be a digit or any letter except the letter E.

Corrective Action: Correct the Cut line.

CTD870E EXPECTING AN "E" CHARACTER TO TERMINATE THIS RANGELink copied to clipboard

Explanation: A specified range was not terminated with the letter E.

Corrective Action: Correct the Cut line.

CTD871E A RANGE WITH THIS LETTER IDENTIFIER IS ALREADY DEFINEDLink copied to clipboard

Explanation: The same letter was already used as a range ID. The same letter may not be used to specify more than one range ID. Range ID must be unique.

Corrective Action: Correct the Cut line.

CTD872E THIS "E" DOES NOT TERMINATE ANY OPEN RANGELink copied to clipboard

Explanation: A letter E that does not terminate any range was specified. The letter E may only terminate a range; it may not be used to specify a range ID.

Corrective Action: Correct the Cut line.

CTD873E NOT ENOUGH MEMORY TO SAVE COLUMNS EDITING. LAST CHANGES ARE IGNOREDLink copied to clipboard

Explanation: Insufficient memory to save the column editing specifications in memory.

All the latest changes are ignored.

Corrective Action: Exit from all the other screens (screen A, screen 5, and so on) and try again to specify the column editing. If it happens again, notify your INCONTROL administrator.

CTD874E USE "F" TO FREEZE COLUMN, OR BLANK FOR REGULAR COLUMNLink copied to clipboard

Explanation: An invalid value was specified in the FREEZE LINE field. The FREEZE LINE describes the columns to be frozen or not frozen.

Valid FREEZE LINE options are:

F - to freeze a column
' ' (Blank) - for a regular column

Corrective Action: Put a valid FREEZE LINE option in the FREEZE LINE field.

CTD877E INVALID OPTION USE BLANK OR "TEST"Link copied to clipboard

Explanation: An invalid value was specified for the WRITER OPTION parameter in the Print Mission Definition screen. The only valid WRITER OPTION values are blank and TEST.

The cursor stays in the field until a valid WRITER OPTION value is specified.

Corrective Action: Specify a valid WRITER OPTION value

CTD881I COPYING PERMANENT USER FILE TO ACTIVE USER FILE STARTEDLink copied to clipboard

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

Corrective Action: No action is required.

CTD882I COPYING PERMANENT USER FILE TO ACTIVE USER FILE ENDED OKLink copied to clipboard

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

Corrective Action: No action is required.

CTD884S COPYING PERMANENT USER FILE TO ACTIVE USER FILE ENDED WITH ERRORSLink copied to clipboard

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

Corrective Action: A previous message should describe the error.

CTD885E INVALID DATE SUPPLIED IN THE PARM FIELDLink copied to clipboard

Explanation: The content of the date parameter passed to the CTDCP2A utility is invalid. The valid format is ddmmyy or mmddyy.

Corrective Action: Correct the date, and rerun the CTDCP2A utility.

Messages CTD900 through CTD9xxLink copied to clipboard

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

CTD900E PLEASE FILL IN CATEGORY NAMELink copied to clipboard

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

Corrective Action: Fill in the CATEGORY field.

CTD901E INVALID TASK TYPELink copied to clipboard

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)Link copied to clipboard

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 BLANKLink copied to clipboard

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 TIMELink copied to clipboard

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 LEVELLink copied to clipboard

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 STARTEDLink copied to clipboard

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 OKLink copied to clipboard

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`Link copied to clipboard

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 ERRORSLink copied to clipboard

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=QLink copied to clipboard

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=xLink copied to clipboard

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)Link copied to clipboard

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 CHARACTERSLink copied to clipboard

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`Link copied to clipboard

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 200Link copied to clipboard

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 VARIABLELink copied to clipboard

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`Link copied to clipboard

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:

Copy

//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`Link copied to clipboard

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`Link copied to clipboard

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:

Copy

//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`Link copied to clipboard

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 DAYTIMELink copied to clipboard

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" FAILEDLink copied to clipboard

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 EXISTLink copied to clipboard

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 SYSPRINTLink copied to clipboard

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 DATETYPLink copied to clipboard

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 ACTIVELink copied to clipboard

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 PASSEDLink copied to clipboard

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`Link copied to clipboard

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`Link copied to clipboard

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` FAILEDLink copied to clipboard

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 FAILEDLink copied to clipboard

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 REACHEDLink copied to clipboard

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`Link copied to clipboard

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`Link copied to clipboard

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`Link copied to clipboard

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`Link copied to clipboard

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`Link copied to clipboard

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 DECOLLATELink copied to clipboard

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`Link copied to clipboard

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/VLink copied to clipboard

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 STARTEDLink copied to clipboard

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 OKLink copied to clipboard

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 ADDEDLink copied to clipboard

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 FIELDLink copied to clipboard

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 ERRORSLink copied to clipboard

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)Link copied to clipboard

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 RERUNLink copied to clipboard

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 LINELink copied to clipboard

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 VIEWEDLink copied to clipboard

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`Link copied to clipboard

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 FIELDLink copied to clipboard

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`Link copied to clipboard

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 ENTRYLink copied to clipboard

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.

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

Corrective Action: Enter a valid option or command.

CTD939E REDUNDANT PARAMETER: - `parm`Link copied to clipboard

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 TYPELink copied to clipboard

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 INSTALLEDLink copied to clipboard

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 REPORTLink copied to clipboard

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`Link copied to clipboard

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 REPORTSLink copied to clipboard

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 FIELDLink copied to clipboard

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"Link copied to clipboard

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 DESTINATIONLink copied to clipboard

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 EXCEEDEDLink copied to clipboard

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 EXISTLink copied to clipboard

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`Link copied to clipboard

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 RULERLink copied to clipboard

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`Link copied to clipboard

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 NAMELink copied to clipboard

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 CDAMLink copied to clipboard

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`Link copied to clipboard

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`Link copied to clipboard

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 MEMBERLink copied to clipboard

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`Link copied to clipboard

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 UNAVAILABLELink copied to clipboard

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` RULERLink copied to clipboard

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.Link copied to clipboard

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`Link copied to clipboard

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.Link copied to clipboard

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.Link copied to clipboard

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.Link copied to clipboard

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`Link copied to clipboard

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`Link copied to clipboard

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 SETLink copied to clipboard

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 ZEROLink copied to clipboard

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")Link copied to clipboard

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 FOUNDLink copied to clipboard

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 DATELink copied to clipboard

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`Link copied to clipboard

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 SCREENLink copied to clipboard

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 OPTIONSLink copied to clipboard

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)Link copied to clipboard

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 DSNLink copied to clipboard

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 RULERSLink copied to clipboard

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`Link copied to clipboard

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 $SYSDATALink copied to clipboard

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 CRITERIALink copied to clipboard

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 CRITERIALink copied to clipboard

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 PARMLink copied to clipboard

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 ENTRYLink copied to clipboard

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`Link copied to clipboard

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 TIMELink copied to clipboard

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 BLANKLink copied to clipboard

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 RULERLink copied to clipboard

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 LINELink copied to clipboard

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 DATALink copied to clipboard

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

Corrective Action: Fill in the report entry data.

CTD971I REPORT IS BEING RESTOREDLink copied to clipboard

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 FAILEDLink copied to clipboard

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 REQUESTLink copied to clipboard

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 STARTEDLink copied to clipboard

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 ENDEDLink copied to clipboard

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.Link copied to clipboard

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"Link copied to clipboard

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 ERRORLink copied to clipboard

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 RULERLink copied to clipboard

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`Link copied to clipboard

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" NUMBERLink copied to clipboard

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 ENTRYLink copied to clipboard

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'-CANCELLink copied to clipboard

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.Link copied to clipboard

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 FAILEDLink copied to clipboard

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 TERMINATINGLink copied to clipboard

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 TERMINATELink copied to clipboard

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.Link copied to clipboard

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 MONITORLink copied to clipboard

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 PROCESSINGLink copied to clipboard

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 PRINTINGLink copied to clipboard

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 PRINTINGLink copied to clipboard

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 STOPPEDLink copied to clipboard

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 STOPPEDLink copied to clipboard

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 STOPPEDLink copied to clipboard

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 INVALIDLink copied to clipboard

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 FOUNDLink copied to clipboard

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 STARTEDLink copied to clipboard

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 ENDEDLink copied to clipboard

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 BUILTLink copied to clipboard

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 FAILEDLink copied to clipboard

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 ERRORLink copied to clipboard

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 3Link copied to clipboard

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-DLink copied to clipboard

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 FAILEDLink copied to clipboard

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 FULLLink copied to clipboard

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 ATFLink copied to clipboard

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 ATFLink copied to clipboard

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 ABENDEDLink copied to clipboard

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 STARTEDLink copied to clipboard

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

Corrective Action: No action is required.

CTD9C1I CTDUPBKP UTILITY COMPLETED SUCCESSFULLYLink copied to clipboard

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

Corrective Action: No action is required.

CTD9C2S CTDUPBKP UTILITY ENDED WITH ERRORSLink copied to clipboard

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 PROCESSEDLink copied to clipboard

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 PROCESSEDLink copied to clipboard

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 PROCESSEDLink copied to clipboard

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 SPECIFIEDLink copied to clipboard

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 FILELink copied to clipboard

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 SPECIFIEDLink copied to clipboard

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 SPECIFIEDLink copied to clipboard

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 FILELink copied to clipboard

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-STATEMENTLink copied to clipboard

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`Link copied to clipboard

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 CHANGEDLink copied to clipboard

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`Link copied to clipboard

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.

CTD9CGW THE NEW RETENTION PERIOD (`numDaysNew`) DIFFERS FROM THE VALUE (`numDaysOld`) IN THE MIGRATION MISSION `missionName`Link copied to clipboard

Explanation: The new retention period that you set through the CTDUPBKP utility is compared with the current value in the corresponding migration mission. This warning message alerts you that the newly specified value differs from the value in the corresponding migration mission.

Corrective Action: Ensure that the new retention period matches your needs or adjust it as necessary.

CTD9F0I CONTROL-RECORD FOR BKPMIS `backupMissionName` HAS BEEN CREATEDLink copied to clipboard

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.

Messages CTDA00 through CTDAxxLink copied to clipboard

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

CTDA00E YOU ARE UNAUTHORIZED TO SAVE THIS RULERLink copied to clipboard

Explanation: You are not authorized to save the current ruler. Control-D security exit CTDX004, routine RULSAVE, determined that you cannot save rulers.

The ruler is not saved.

Corrective Action: If you think you should be able to save rulers, contact your INCONTROL administrator.

CTDA01E CTDX004: ERROR IN CTMMEM RC=`rc` READING SKELETONLink copied to clipboard

Explanation: The RESTORE skeleton that is used for restoring reports converted to Control-D from other products (CA-View, CA Dispatch, and so on) cannot be read from the SKL library.

The restore request ends NOT OK.

Corrective Action: Proceed according to the CTMMEM return code displayed in the message. CTMMEM return codes are described in the DOCIMEM member in the IOA DOC library. After correcting the action, request RESTORE of the problematic report.

CTDA02E MISSING SMF DATA SELECTION CRITERIALink copied to clipboard

Explanation: The DASYSIN file for the CTDSMFRP utility contains a blank statement. The DASYSIN file should contain selection criteria statements for the SMF report.

The CTDSMFRP utility terminates with a return code of 08.

Corrective Action: Provide correct selection criteria statements.

CTDA03E NO SMF RECORDS MET THE SELECTION CRITERIALink copied to clipboard

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

There are no Control-D SMF records to match the selection criteria for the SMF report (the CTDSMFRP utility), or no selection criteria were specified when running the CTDSMFRP utility, or SMF was not set to YES in CTDPARM.

The CTDSMFRP utility terminates with a return code of 04.

Corrective Action: No action is required.

CTDA03E CTDX004: ERROR IN GETMAIN FOR SKELETONLink copied to clipboard

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

There is insufficient memory to read the RESTORE skeleton that is used for restoring reports converted to Control-D from other products (for example, CA-View, CA Dispatch).

The current restore request ends NOT OK.

Corrective Action: Increase the REGION size of the online environment.

CTDA04E CTDX004: UNABLE TO DYNAMICALLY ALLOCATE INTRDR `rc`Link copied to clipboard

Explanation: Dynamic allocation of the internal reader (INTRDR) by a Control-D command failed during an attempt to submit a restore job for reports converted to Control-D from other products (such as, CA-View, CA Dispatch).

In this message, rc is the return code of the failed dynamic allocation.

The restore job is not submitted. The current restore request ends NOT OK.

Corrective Action: Refer to the IBM manual that deals with information returned from an SVC 99. Take appropriate action based on the return code displayed in the message.

CTDA05E CTDX004: ERROR IN GETMAIN FOR SYSDATA RECORDLink copied to clipboard

Explanation: There is insufficient memory for the SYSDATA record that is needed to restore reports converted to Control-D from other products (for example, CA-View, CA Dispatch).

The current restore request ends NOT OK.

Corrective Action: Increase the REGION size of the Online environment.

CTDA11S OPEN OF SCRATCH LIST FAILED. DDNAME "DASCRLST"Link copied to clipboard

Explanation: Open of scratch list file issued by the CTDDELRP utility in the DASCRLST DD statement failed.

Possible causes are:

The DASCRLST DD statement is missing.
The data set described by the DASCRLST DD statement cannot be opened for sequential processing.

The CTDDELRP utility ends with errors.

Corrective Action: Check the JCL for the job; correct and rerun the utility.

CTDA12I DELETE OF UNNEEDED DATASETS STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTDDCD program of the CTDDELRP utility, which deletes unneeded CDAM data sets, has started.

Corrective Action: No action is required.

CTDA13I SCRATCH LIST IS EMPTYLink copied to clipboard

Explanation: This information message indicates that the CDAM scratch list is empty. This message is issued by the CTDDCD program of the CTDDELRP utility, which is used to delete unneeded compressed sysout data sets.

Corrective Action: No action is required.

CTDA141 DELETE OF UNNEEDED DATASETS ENDED OKLink copied to clipboard

Explanation: Normal termination message of the CTDDCD program (of the CTDDELRP utility) which is used to delete unneeded compressed sysout data sets.

Corrective Action: No action is required.

CTDA15E DELETE OF UNNEEDED DATASETS ENDED WITH ERRORSLink copied to clipboard

Explanation: The CTDDCD program (used in the CTDDELRP utility and in the New Day procedure), which is used to delete unneeded data sets, ended with errors.

The CTDDCD program continues processing and completes with a condition code of 04.

Corrective Action: Refer to previous messages and the CTDA18E message.

CTDA16I DATASET `dsn` DELETEDLink copied to clipboard

Explanation: This information message is issued by the CTDDCD program of the CTDDELRP utility to indicate that the dsn compressed sysout data set was deleted successfully.

Corrective Action: No action is required.

CTDA17E DATASET `dsn` COULD NOT BE DELETED DUE TO:Link copied to clipboard

Explanation: Warning message from the CTDDCD program (of the CTDDELRP utility) indicating that the dsn compressed sysout data set could not be deleted. The reason for the failure is described in the CTDA18E message.

Corrective Action: No action is required.

CTDA18E `rsn` FUNC=`func`, RC=`rc`, STATUS=`statusCode`Link copied to clipboard

Explanation: This warning from the CTDDCD program indicates that a data set could not be deleted and displays the reason for the message, the related system function, the return code, and the status code. The header for this message is provided by the CTDA17E message.

Possible values for rsn are:

DATASET IS IN USE
DATASET NOT IN CATALOG
DATASET NOT ON VOLUME
RACF PREVENTED THE SCRATCH
GENERAL SCRATCH ERROR
GENERAL UNCATALOG ERROR

The CTDDELRP utility or the New Day procedure continues processing and completes with a condition code of 04.

Corrective Action: Perform the action described below as appropriate for the reason in the message.

DATASET IS IN USE - If the data set was in use by an online user, ignore the warning. The data set remains on the scratch list and is deleted during the next run of the CTDDELRP utility.
DATASET NOT IN CATALOG or DATASET NOT ON VOLUME - Someone may have removed the specified CDAM data set manually (for example, ISPF 3.2). Investigate the cause and ensure that the files are deleted with standard Control-D procedures. Edit the scratch list file and remove the relevant DSNs. This is necessary because the scratch list accumulates the DSNs that could not be deleted and they will cause the same error the next time it runs.
RACF PREVENTED THE SCRATCH - The job was not authorized to delete the file. Correct the security authorization. The DSN remains on the scratch list and is deleted the next time the CTDDELRP utility runs.
GENERAL SCRATCH ERROR or GENERAL UNCATALOG ERROR - These rare errors indicate a structural problem in the system catalog or VTOC. Contact your systems programmer for assistance.

If you cannot solve the problem, refer to the IBM manual System Programming Library: Data Management for an explanation of reason and status codes. See the LOCATE, SCRATCH, or UNCATALOG section, depending upon the function displayed in the message:

LOCATE - retrieving catalog information by data set name
SCRATCH - deleting a data set
UNCATALOG - uncataloging a data set

CTDA19S OPEN OF SCRATCH REJECTS FAILED. DDNAME "DASCRREJ"Link copied to clipboard

Explanation: CTDDCD issues this message to report that open of scratch rejects file failed (the DASCRREJ DD statement).

Possible causes are:

The DASCRREJ DD statement is missing.
The data set described by the DASCRREJ DD statement does not exist.

The CTDDELRP utility or the New Day procedure ends with errors.

Corrective Action: Correct the JCL, and rerun the job.

CTDA21S OPEN OF INPUT FILE FAILED. DDNAME "DAIN"Link copied to clipboard

Explanation: There may be a missing DAIN DD statement in the JCL job.

The CTDCRL program terminates.

Corrective Action: Add a DAIN DD statement to the job.

CTDA22S OPEN OF OUTPUT FILE FAILED. DDNAME "DAOUT"Link copied to clipboard

Explanation: There may be a missing DAOUT DD statement in the job JCL.

The CTDCRL program terminates.

Corrective Action: Add a DAOUT DD statement to the job.

CTDA23I FILE CONVERSION STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTDCRL program started processing.

Corrective Action: No action is required.

CTDA24I INPUT RECORDS - `num`Link copied to clipboard

Explanation: This information message indicates that the CTDCRL program ended and read num records.

Corrective Action: No action is required.

CTDA25I OUTPUT RECORDS - `num`Link copied to clipboard

Explanation: This information message indicates that the CTDCRL program ended and wrote num records.

Corrective Action: No action is required.

CTDA26I FILE CONVERSION ENDEDLink copied to clipboard

Explanation: This information message indicates that the CTDCRL program finished processing.

Corrective Action: No action is required.

CTDA30E OPEN OF SORT FILE FAILED. DDNAME `ddName`Link copied to clipboard

Explanation: The SORT utility invoked by the CTDDELRP utility failed to open the ddName DD statement.

The CTDDELRP utility stops.

Corrective Action: Ensure all DD statements are valid. Restart the CTDDELRP utility.

CTDA31E INVALID RETURN CODE FROM SORT, RC=`rc`Link copied to clipboard

Explanation: Internal sort program ended with errors. This message is from the CTDDELRP utility, which cleans unnecessary entries from the Active User Report List file. The utility uses the site sort program internally.

The utility terminates with a condition code of 08.

Corrective Action: Refer to the sort messages for the job and to the user guide for the sort facility used at your site.

CTDA34E OPEN OF SCRATCH LIST FAILED. DDNAME "DASCRLST"Link copied to clipboard

Explanation: The CTDDELRP Control-D utility, which cleans unnecessary entries from the Active User Report List file, failed to open the scratch list file using the DASCRLST DD statement. Possible causes are:

The DASCRLST DD statement is missing.
The data set described by the DASCRLST DD statement cannot be opened for a sequential write.

The utility terminates with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

CTDA35I WAITING FOR ANOTHER CTDDELRP OR RESTORE JOB TO TERMINATELink copied to clipboard

Explanation: This information message indicates that the CTDDELRP utility is waiting for another CTDDELRP job or a restore job to terminate. CTDDELRP is cleans unnecessary entries from the Active User Report List file. To maintain data integrity, CTDDELRP cannot run concurrently with another CTDDELRP or a restore job.

When the contending job terminates, CTDDELRP resumes processing.

Corrective Action: No action is required.

CTDA36E OPEN OF "DAWORK" DD CARD FAILEDLink copied to clipboard

Explanation: Open of the Active Transition file failed. This file is referenced by the DAWORK DD statement. The DAWORK DD statement is probably missing. This error message is issued by the CTDDSO program, which is the first step of the CTDDELRP utility.

CTDDSO terminates with a condition code of 08.

Corrective Action: Check for previous messages indicating the reason for the open failure. Correct the problem, and rerun the CTDDELRP utility.

CTDA37I JOB `jobName` JOBID `jobId` IS WAITING FOR MIGRATION BY `missionName`Link copied to clipboard

Explanation: This information message is produced by the CTDDELRP utility. It indicates the jobName job is ready for migration by the missionName Migration Mission.

The sysout compressed data sets for the jobName job will not be deleted until the Migration Mission runs successfully.

Corrective Action: No action is required.

CTDA38I SYSDATA RECORD IS MISSING FOR INDEX `index`. JOB `jobName` JOBID `jobId` WILL BE DELETEDLink copied to clipboard

Explanation: This information message indicates that the CTDDELRP utility, which cleans unnecessary entries from the Active User Report List file, cannot find a SYSDATA record that corresponds to an index record in the Active User Report List file.

The SYSDATA record was probably manually deleted from the Active User Reports List file.

The index record and index file are deleted to maintain database integrity. Processing continues.

Corrective Action: No action is required.

CTDA39E NO INPUT PARAMETERS WERE SUPPLIEDLink copied to clipboard

Explanation: The CTDDELRP utility, which is used to clean unnecessary entries from the Active User Report List file, did not receive input parameters from a DADELIN DD statement. The CTDDELRP utility should be supplied with input parameters indicating actions for the utility to perform.

The CTDDSO program terminates with a condition code of 08.

Corrective Action: Verify that input parameters are specified by means of the DADELIN DD statement, and rerun the job.

CTDA3AE OPEN OF "DAXREP" FAILEDLink copied to clipboard

Explanation: The CTDDELRP utility, which cleans unnecessary records from the Active User Report List file, failed to open the Print Control Record Scratch file referenced by the DAXREP DD statement. The DAXREP DD statement is probably missing. This error message is issued by the CTDDSO program, which is the first step of the CTDDELRP utility.

The CTDDSO program terminates with a condition code of 08.

Corrective Action: Correct the error, and rerun the CTDDELRP utility.

CTDA3BE I/O ERROR WRITING TO XREP DELETE FILE. DDNAME "DAXREP"Link copied to clipboard

Explanation: An I/O error occurred while writing the file referenced by the DAXREP DD statement. This message is issued by the CTDDSO program, which is the first step of the CTDDELRP utility.

The CTDDELRP utility terminates.

Corrective Action: Run the CTDBLXRP utility to rebuild the Print Control Record. Rerun the CTDDELRP utility.

CTDA3CE INSUFFICIENT SPACE ALLOCATED TO XREP DELETE FILE. DDNAME "DAXREP"Link copied to clipboard

Explanation: The file referenced by the DAXREP DD statement has insufficient space allocated. This message is issued by the CTDDSO program, which is the first step of the CTDDELRP utility.

The CTDDELRP utility continues processing.

Corrective Action: To prevent this problem in the future, allocate more space to the file referenced by the DAXREP DD statement. Run the CTDBLXRP utility to rebuild the Print Control Record.

CTDA3DE "FE" PRINT SUPPORT ERROR. RETURN CODE `rc`Link copied to clipboard

Explanation: An error was encountered while trying to delete a Print Control Record. This message is issued by the CTDDSO program, which is the first step of the CTDDELRP utility.

Possible values of rc are:

016 - invalid function
024 - open error
028 - error in sort

The CTDDELRP utility continues processing.

Corrective Action: Run the CTDBLXRP utility to rebuild the Print Control Record.

CTDA3EI * PARM=TEST SPECIFIED - SIMULATION MODE *Link copied to clipboard

Explanation: This information message indicates that the CTDDELRP utility is running in SIMULATION mode. In SIMULATION mode, the CTDDELRP utility produces a report that indicates which entries would have been deleted and which data sets would have been erased if the utility were running in PRODUCTION mode.

Corrective Action: Examine the output of the CTDDELRP utility to determine if the proper entries would have been deleted from the Active User Report List file and the proper CDAM data sets would have been erased. Make any changes required to prevent the deletion of needed Active User Report List entries or CDAM data sets.

Rerun the utility in PRODUCTION mode to delete unneeded entries in the Active User Report List file and to erase CDAM data sets that no longer have references in that file.

CTDA40E WHEN USING CLASS *, ONE OF THE FOLLOWING THREE FIELDS MUST BE ENTEREDLink copied to clipboard

Explanation: If an asterisk (*) was entered in the CLASS field, a value must be inserted in the EXTWTR field, the DEST field, or the FORM field.

Corrective Action: Insert a value in the EXTWTR, DEST, or FORM field.

CTDA41E MIXED GENERIC AND NON-GENERIC CLASSES IS NOT ALLOWEDLink copied to clipboard

Explanation: Mixed generic and non-generic classes were specified. When setting GENERIC to Y, only the classes specified in the GENCLAS Installation Parameter are allowed. When setting GENERIC to N, only classes not specified by the GENCLAS Installation Parameter are allowed.

Corrective Action: Correct the CLASS field.

CTDA42E INVALID OPTION (USE "Y", "N", "W", "E" OR BLANK)Link copied to clipboard

Explanation: User entered an invalid value in the CONTID field in the Decollating Mission Definition screen.

Corrective Action: Enter a valid option in the CONTID field.

CTDA43E USER IS NOT FOUND IN THE RECIPIENT TREELink copied to clipboard

Explanation: A recipient that was defined in a DO USER parameter of the decollating mission does not appear in the Control-D Recipient Tree. This message appears while exiting the Decollating Mission Definition screen, or after using the CHKUSR command.

The Decollating Mission Definition screen is not exited; an error message containing the invalid user name is displayed.

Corrective Action: Correct the invalid user name in the decollating mission definition, or add a new user to the Control-D Recipient Tree.

CTDA44E PLEASE ENTER TEXT OF THE REMARKLink copied to clipboard

Explanation: A value was set for the DO REMARK parameter in the Decollating Mission Definition screen, but no text was entered for the remark.

Corrective Action: Enter text in the DO REMARK parameter field.

CTDA45E ENTER "U", "C", "A", "B", OR BLANKLink copied to clipboard

Explanation: There is an invalid value in the T field on a DO USER line in the Decollating Mission Definition screen.

Valid values are:

U (Unconditional) - The user receives the report page regardless of whether or not the user’s children receive the page.
C (Conditional) - The user only receives the report page if the user’s children do not receive the page. Default.
A (Accept all users) - The user receives the report page even if the user’s name is not in the Recipient Tree.
B - The user does not need to search for the recipient in the Recipient Tree. This option can be used to improve the performance of the decollation when the site has a large Recipient Tree.
" " (Blank) - The default (Conditional) is assumed.

Corrective Action: Enter a valid option in the T field.

CTDA46E THIS FEATURE IS NOT SUPPORTED IN YOUR SYSTEMLink copied to clipboard

Explanation: User entered the SYSOUT option in the ON statement line on the Decollating Mission Definition screen, in a JES3 site. DO SYSOUT is supported in JES2 sites only. Your site must be a JES3 site.

Corrective Action: Specify any valid option other than SYSOUT in the ON statement, for example, ON CLASS, ON DSN, and so on.

CTDA47E PLEASE FILL IN RULE NAMELink copied to clipboard

Explanation: DO CTBRULE has been specified without a rule name. If a DO CTBRULE statement is specified, a rule name must be included in the statement.

Corrective Action: Specify the rule name, or delete the DO CTBRULE statement.

CTDA48E FIRST CHARACTER CANNOT BE NUMERICLink copied to clipboard

Explanation: The first character specified in the rule name in the DO CTBRULE statement is, but should not be, numeric. The rule name must be a member name, and member names cannot begin with a numeric character.

Corrective Action: Correct the specified rule name so that the first character is not numeric.

CTDA49E "COPIES" VALUE EXCEEDS "MAX COPIES" VALUELink copied to clipboard

Explanation: The value of the MAX COPIES field must be, but is not, greater than or equal to the value of the COPIES field.

Corrective Action: Change the value of either COPIES or MAX COPIES so that MAX COPIES is greater than or equal to COPIES.

CTDA4BE THE FOLLOWING FIELDS SHOULD BE ENTERED: `fieldlist`Link copied to clipboard

Explanation: Mandatory fields are missing in the ON CLASS/TRNCLASS statement. The list of mandatory fields is defined in the WDN130 optional wish. A list of missing mandatory fields is provided in this message. This list contains one or more of the following fields: EXTWTR, DEST, FORM

Corrective Action: Fill in the missing mandatory fields.

CTDA50E SYNONYM=`synonym` IS NOT ALLOWED WITH USER=*FORCELink copied to clipboard

Explanation: Option A (All) is specified for the SYNONYM parameter for use with the DO USER=*FORCE action. When SYNONYM is set to A, report pages are sent to all users in the Recipient Tree that have the specified synonym. This parameter cannot be specified when the statement DO USER=*FORCE is chosen, because USER=*FORCE causes the Recipient Tree to be searched until the first user with the specified synonym is found.

Corrective Action: Change the parameter to F (first), or clear it.

CTDA51E ENTER "F", "A" OR BLANKLink copied to clipboard

Explanation: The user specified an invalid SYNONYM parameter.

The valid options for the SYNONYM parameter:

F (First) or blank - The Recipient Tree is searched until the first user with the specified synonym is found. The report pages are sent to that user only.
A (All) - The report pages are sent to all users with the specified synonym in the Recipient Tree.

Corrective Action: Change the parameter to F, A or blank.

CTDA53E "FE" PRINT SUPPORT ERROR. RETURN CODE `rc`Link copied to clipboard

Explanation: An executing Restore Mission failed to created or update an internal Printing Mission record in the Active User Report file.

When a record with status WAITING FOR PRINT is restored, 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 are produced with the following key:

Copy

X’FE’,C’PRINTMS’,Printing_Mission_Name.

rc is the return code from the CTDXRP routine.

The Restore Mission restores the reports but terminates with NOTOK status. The restored reports will not be selected by any Printing Mission whose name is specified in the DO PRINT Decollation Mission parameter.

Corrective Action: These reports can be manually scheduled for Deferred Printing by using the P line command to display the Print Window under Option U and then specifying the Printing Mission name. If the problem persists, report the return code to BMC Customer Support.

CTDA54I RSTRESET PROCESSING STARTEDLink copied to clipboard

Explanation: This information message denotes the normal start of the RSTRESET Control-D utility.

The RSTRESET utility changes the status of all active restore missions to ENDED NOT OK, and changes the status of all reports selected for restoring to BACKED UP.

Corrective Action: No action is required.

CTDA55I RSTRESET PROCESSING ENDEDLink copied to clipboard

Explanation: This information message indicates that the RSTRESET Control-D utility ended normally.

Corrective Action: No action is required.

CTDA58S OPEN OF ACTIVE MISSIONS FILE FAILED.Link copied to clipboard

Explanation: The CTDRESET utility has failed to open the Active Mission file.

The utility does not reset reports restore processing.

Corrective Action: Call your INCONTROL Administrator.

CTDA60E RESTORE MISSION NOT IN LIBRARY `lib`Link copied to clipboard

Explanation: The specified Restore Mission name is not defined in the Restore Mission Definition library.

When you request a Restore, a validity check is done for the Restore Mission name. A search is made for the $$PARMS member in the library allocated to the DACMD xx DD statement, where xx is the application ID. The member contains a RSTLIB parameter, which specifies the name of the Restore Mission Definition library. If the Restore Mission name is not found in this library, this message is issued.

Corrective Action: Specify a Restore Mission name which exists in the Restore Mission Definition library. If you are not familiar with the names used in your data center, consult your INCONTROL administrator.

CTDA61E MISSING "RSTLIB=" PARAMETER IN $$PARMS MEMBER (DD DACMDxx)Link copied to clipboard

Explanation: Internal error in the Restore Mission validation process.

When you request a Restore, a validity check is done for the Restore Mission name. A search is made for the $$PARMS member in the library allocated to the DACMD xxDD statement, where xx is the application ID. The member contains a RSTLIB parameter, which specifies the name of the Restore Mission Definition library. The parameter was missing from the member.

Corrective Action: Consult your INCONTROL administrator who will specify the RSTLIB parameter in the $$PARMS member.

CTDA62S ERROR WHILE PREPARING FORMATSLink copied to clipboard

Explanation: Syntax errors were detected in the Display Types definition member. The Display Type definition member was loaded and analyzed and syntax errors were detected. Specific errors were previously displayed with the erroneous source lines.

The User Reports Entry Panel is not displayed.

Corrective Action: Correct the Display Types definition errors in the $$FRM member of the PARM library, and try to reenter the User Reports Entry Panel.

CTDA63S INTERNAL ERROR IN CTMTJOB RC=`rc`Link copied to clipboard

Explanation: An internal error occurred while attempting to display the error messages that resulted from the syntax check of the Display Type definitions.

The error messages are not displayed.

Corrective Action: Ask your INCONTROL administrator to notify BMC Customer Support.

CTDA64E DISPLAY TYPE `type` FOR `report-list-type` [`sysdata`] NOT FOUNDLink copied to clipboard

Explanation: There was an attempt to display an invalid User Report List display combination. Available Report List display combinations are predefined in the $$FRM member of the PARM library. The exact combination must exist in the member.

For each combination, the following three characteristics are defined:

ID - Display Type letter (for example, D (Default), U (User), and so on).
TYPE - Permanent, Active or History Report List.
CLASS - Usual, Sysdata or Ruler.

The User Report List screen is not displayed.

Corrective Action: Specify a valid (existing) display combination.

CTDA65E INTERNAL ERROR WHILE SETTING HEADER RC=`rc`Link copied to clipboard

Explanation: An internal error occurred while attempting to place the Display Type’s header in the screen.

The User Report List screen is not displayed.

Corrective Action: Have your INCONTROL administrator notify BMC Customer Support.

CTDA66E USER FIELD MUST EXIST IN FORMATLink copied to clipboard

Explanation: An INSERT operation was attempted on a User Report List whose current Display Type does not contain the USER field. To insert a new user record in a User Report List, the USER field must be specified.

The new record is not inserted.

Corrective Action: Insert a record when using a Display Type that contains the USER field, or add this field to the definition of the current Display Type.

CTDA67E USER FIELD MUST BE EDITABLE IN FORMATLink copied to clipboard

Explanation: An INSERT operation was attempted on a User Report List whose current Display Type contains a protected USER field. To insert a new user record in a User Report List, the USER field must be specified.

The new record is not inserted.

Corrective Action: Either insert the record when using a Display Type that contains an unprotected USER field, or define the USER field in the current Display Type as unprotected.

CTDA68E JOBNAME FIELD MUST EXIST IN FORMATLink copied to clipboard

Explanation: An INSERT operation was attempted on a User Report List whose current Display Type does not contain the JOBNAME field. To insert a new user record in a User Report List, the JOB field must be specified.

The new record is not inserted.

Corrective Action: Either insert a record when using a Display Type that contains the JOB field, or add this field to the definition of the current Display Type.

CTDA69E JOBNAME FIELD MUST BE EDITABLE IN FORMATLink copied to clipboard

Explanation: An INSERT operation was attempted on a User Report List whose current Display Type contains a protected JOBNAME field. To insert a new user record in a User Report List, the JOB field must be specified.

The new record is not inserted.

Corrective Action: Either insert the record when using a Display Type that contains an unprotected JOB field, or define the JOB field in the current Display Type as unprotected.

CTDA70E "OPT" FIELD MUST EXIST IN FORMATLink copied to clipboard

Explanation: An attempt was made to specify an option (for example, Insert, Update, and so on) however, the OPTION field is not present in the current Display Type. The OPTION field must be defined in a Display Type in order to specify a required operation or option on a record of the User Report List.

No operations are performed on the User Report List.

Corrective Action: Add the OPTION field to the Display Type.

CTDA71E INTERNAL ERROR - FORMAT DOES NOT EXISTLink copied to clipboard

Explanation: An internal error occurred while attempting to process the User Report List.

The User Report List screen is not processed.

Corrective Action: Have your INCONTROL administrator notify BMC Customer Support.

CTDA72E USER OR JOBNAME CANNOT BE UPDATEDLink copied to clipboard

Explanation: The user attempted to update or modify the contents of the USER field, the JOB field, or both. The USER and the JOB fields may not be modified when updating a record.

The record is not updated.

Corrective Action: Try updating the record again without modifying the USER or JOB fields.

CTDA73E INTERNAL ERROR - DATA FIELD TOO SHORTLink copied to clipboard

Explanation: The user modified or updated the contents of a field, but the field length defined in the Display Type definition is shorter than the size of the field in the Control-D database.

A field can be updated in the Control-D database only if its length in the screen is not less then its database length. While this is normally the case, an error might have been made if the Display Type field was defined especially for the site.

The record is not updated.

Corrective Action: Modify the length of the field in the DISPLAY TYPE definition to the recommended length. A list of field lengths can be found in the $$FIELD member in the PARM library.

CTDA74E INTERNAL ERROR UNIDENTIFIED RC - RC=`rc`Link copied to clipboard

Explanation: An internal error occurred while attempting to insert or update a user record.

The record is not inserted or updated.

Corrective Action: Have your INCONTROL administrator notify BMC Customer Support.

CTDA75E INTERNAL ERROR - IN WEDTQRY - RC=`rc`Link copied to clipboard

Explanation: An internal error occurred while attempting to insert a user record.

The record is not inserted.

Corrective Action: Have your INCONTROL administrator notify BMC Customer Support.

CTDA76E AN EDIT FIELD ENDS AFTER SCREEN BOUNDSLink copied to clipboard

Explanation: The contents of a field that do not fit on the physical screen were modified or updated. Display formats with a logical length of 132 columns may be used on a physical screen of 80 columns, but some of the fields are not displayed at all, and some are truncated. An editable field that is truncated may not have its contents modified or updated.

The record is not updated. The cursor is positioned on the problematic field.

Corrective Action: Modify the Display Type definition to allow the entire field to be displayed, or use a physical screen which displays the entire field.

CTDA77E YOU ARE NOT AUTHORIZED TO USE THIS FORMATLink copied to clipboard

Explanation: This Display Type is not authorized for the current user. The INCONTROL administrator can authorize (or deny) the use of certain Display Types for certain users.

The User Report List screen is not displayed.

Corrective Action: Request a Display Type for which you are authorized, or see your INCONTROL administrator for authorization and access to specified Display Type.

CTDA78E YOU MUST FILL IN THE DISPLAY TYPE FIELDLink copied to clipboard

Explanation: Entry to the User Report List attempted without specifying a Display Type in the User Reports Entry Panel. To view the User Report List, specify a valid Display Type in the DISPLAY TYPE field.

The User Report List is not displayed.

Corrective Action: Specify a valid Display Type.

CTDA79E INVALID NUMBER OF DAYSLink copied to clipboard

Explanation: A date in the FROM DATE or TO DATE field of the User Reports Entry Panel is invalid. The specified date must be a valid date in the format used in your installation. For more information, see the Control-D and Control-V User Guide.

The User Report List is not displayed.

Corrective Action: Correct the date specification and retry.

CTDA80E NUMBER OF DAYS SHOULD BE 365 OR LOWERLink copied to clipboard

Explanation: The relative date in the FROM DATE or TO DATE field of the User Reports Entry Panel is invalid.

For information about valid combinations for this field, see the Control-D and Control-V User Guide.

The User Report List is not displayed.

Corrective Action: Correct the date specification and retry.

CTDA81E COND. CODE COMPARISON SHOULD BE ">C" AND 4 DIGITS, EXAMPLE: >C0004Link copied to clipboard

Explanation: The value in the REMARK or CC field of the User Reports Entry Panel is invalid.

For information about valid combinations for this field, see the Control-D and Control-V User Guide.

The User Report List is not displayed.

Corrective Action: Correct the REMARK or CC specification and retry.

CTDA82E YOU MUST GIVE A ONE LETTER DISPLAY TYPE NAMELink copied to clipboard

Explanation: The Display Type code specified in the DISPLAY command in the User Report List is invalid. The DISPLAY command requires a one letter Display Type parameter. This parameter must indicate an existing Display Type.

The current Display Type is not changed.

Corrective Action: Specify a valid Display Type with the DISPLAY command.

CTDA83E DISPLAY TYPE NAME SHOULD BE ONE LETTER ONLYLink copied to clipboard

Explanation: More than one letter is specified for the Display Type code in the DISPLAY command in the User Report List. The DISPLAY command requires a 1-letter Display Type parameter. This parameter must indicate an existing Display Type.

The current Display Type is not changed.

Corrective Action: Specify a valid, 1-letter Display Type with the DISPLAY command.

CTDA84E DISPLAY TYPE SHOULD HAVE AT LEAST ONE LINE IN SHORT FORMATLink copied to clipboard

Explanation: The Display Type specified contains only Long format lines. A Display Type cannot have all its lines defined as Long format lines. At least one line must be defined for Short format. Long format lines are used only when Additional Information is requested for a record. Short format lines are always displayed.

For information on customizing IOA display format members, see the INCONTROL for z/OS Administrator Guide.

The User Report List is not displayed.

Corrective Action: Modify the Display Type definition to contain at least one Short format line.

CTDA85E CANNOT CHANGE DISPLAY TYPE WHILE INSERTINGLink copied to clipboard

Explanation: There is an attempt to change the Display Type using the DISPLAY command, while a new record is being inserted using the Insert line option. The insert operation must be complete before a Display Type is changed.

The DISPLAY command is not performed.

Corrective Action: Complete the insert operation, and then retry the DISPLAY command.

CTDA86E FIELD SHOULD BE NUMERICLink copied to clipboard

Explanation: There was an attempt to modify or update the contents of a numeric field with a non-numeric value. The updated field must have a numeric value.

The record is not updated.

Corrective Action: Specify a numeric value in the field before updating the record.

CTDA87E REPORT EMPTY. CHECK INCLUDE/EXCLUDE RULER DEFINITIONSLink copied to clipboard

Explanation: The report for which view is requested contains no report lines. An empty report usually indicates that a ruler was applied to a report, which contained a combination of Include and Exclude criteria that left no lines in the report.

The VIEW option is not performed.

Corrective Action: Check the ruler or rulers for the report. Request that the report be displayed without problematic rulers or without rulers entirely.

CTDA88E ENTRY SHOULD BE IN "WAIT-RESTORE" STATELink copied to clipboard

Explanation: You cannot un-restore a record that is not scheduled to be restored. Only records in the WAIT-RESTORE state can be un-restored.

The un-restore operation is not performed.

Corrective Action: No action is required.

CTDA89W WARNING: CTDTUSR SHOULD RUN ABOVE THE 16MB LINE - CONTACT SYS-PROGLink copied to clipboard

Explanation: The CTDTUSR User Report List program resides below the 16MB line. The CTDTUSR User Report List program is designed to run above the 16MB line to achieve better resource utilization, especially when running under the Online monitor. For some reason, the program is not taking advantage of this ability.

The system continues as usual.

Corrective Action: Have your INCONTROL administrator notify BMC Customer Support.

CTDA8AI REPORT UNRESTORED: `jobname/recipient report` ID=`recordId`Link copied to clipboard

Explanation: This information message indicates that the restore request to the backed up (migrated) report is canceled.

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

Corrective Action: No action is required.

CTDA8BE OPERATION NOT AUTHORIZED WHEN IN DEMO MODELink copied to clipboard

Explanation: An unauthorized operation was attempted on a DEMO record. DEMO records are reserved for demonstration and training purposes, and are normally accessed by specifying DEMO in the User Reports Entry Panel. Some operations are not permitted on DEMO records. To protect the integrity of the DEMO records, Update and Delete operations are not permitted on these records.

The unauthorized operation is not performed.

Corrective Action: No action is required.

CTDA8CE ENTRY IN "WAIT-RESTORE" CANNOT BE DELETEDLink copied to clipboard

Explanation: There was an attempt to delete a report entry from the History User Report List file that has a status of WAIT RESTORE. Report entries in WAIT RESTORE state cannot be deleted.

The delete operation is not performed.

Corrective Action: User should first use the No Restore option to change the status of the report entry to BACKEDUP, and then perform the delete again.

CTDA8DE UNABLE TO OBTAIN NOTES - RC FROM CTDNPS=`rc`Link copied to clipboard

Explanation: The Control-D Notepad Facility received a nonzero return code from the CTDNPS routine; notes cannot be obtained. The message usually accompanies another error message that defines a specific error according to the return code (rc).

Corrective Action: Contact your system programmer for assistance.

CTDA8EE UNABLE TO SHOW NOTES - RC FROM CTDTNTP=`rc`Link copied to clipboard

Explanation: The Control-D Notepad Facility received a nonzero return code from routine CTDTNTP; notes cannot be displayed. The message represents an internal error in the Control-D Notepad Facility. The return code (rc) indicates the error.

Corrective Action: Contact BMC Customer Support for assistance.

CTDA8FE YOU ARE NOT AUTHORIZED TO WORK WITH TAG NOTESLink copied to clipboard

Explanation: The CTDX004 Control-D security exit determined that you are not authorized to read or write tag notes in the displayed report.

Corrective Action: If you think you should be able to read or write tag notes, contact your INCONTROL administrator.

CTDA91E INVALID MISSION TYPE. ONLY BKP OR RST ALLOWEDLink copied to clipboard

Explanation: An invalid mission type was specified.

Corrective Action: Correct the mission type and continue.

CTDA92I MEMBER `memName` SAVEDLink copied to clipboard

Explanation: This information message indicates that the memName member has been saved successfully. All missions are stored on members.

Corrective Action: No action is required.

CTDA95E VALUE OF CNDREC# PARAMETER IN IOAPARM IS NOT EQUAL TO ACTUAL FILE SIZELink copied to clipboard

Explanation: The CNDREC# parameter in IOAPARM has been changed but the IOA Conditions file has not been rebuilt.

A difference was detected between the length of the IOA Conditions file and the length specified in the IOAPARM member of the PARM library.

This is usually due to using the IOAPARM member (read from the IOA Load library) for the wrong monitor.

The monitor shuts down.

Corrective Action: To correct this situation, do one of the following:

Rebuild the IOA Conditions file, so that its length is as specified in IOAPARM.
Modify the CNDREC# parameter in IOAPARM so that its length is the length of the existing IOA Conditions file.

After correcting the problem, restart the monitor.

CTDA96W LOAD OF SECURITY MODULE CTDSE01 FAILED. SECURITY CHECKING WILL BE BYPASSEDLink copied to clipboard

Explanation: The CTDSE01 module was not found and was not linked into the CTDCMI module. To perform security checking during ordering of missions, Control-D calls the CTDSE01 security exit. If your security checking is performed by CTDX001, link a dummy security exit into CTDCMI to prevent this message from being issued.

The mission is ordered.

Corrective Action: Check whether or not the security exit should exist.

CTDAA0I DELETE OF UNNEEDED INP RECORDS STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTDNDAY process started deleting unneeded INP records from the Control-D Active User File.

Corrective Action: No action is required.

CTDAA1I DELETE OF UNNEEDED INP RECORDS ENDED OKLink copied to clipboard

Explanation: This information message indicates that the CTDNDAY process completed deleting unneeded INP records from the Control-D Active User File.

Corrective Action: No action is required.

CTDAA2E DELETE OF UNNEEDED INP RECORDS WITH ERRORSLink copied to clipboard

Explanation: This error message indicates that the CTDNDAY process failed to delete the unneeded INP records from the Control-D Active User File. The CTDNDAY process finished executing with a conditional code of 08.

Corrective Action: Examine the SYSPRINT and IOA Log File for error messages to clarify the cause of the problem. If possible, fix the problem and rerun CTDNDAY.

CTDAA3I n INP RECORDS WERE DELETEDLink copied to clipboard

Explanation: This information message indicates the number of INP records deleted from the Active User File during the CTDNDAY run.

Corrective Action: No action is required.

CTDAD1E ERROR IN MEMBER AUDTPARM LINE= `line_number`, BLOCK= `block_name`, PARAMETER= `parameter_name`Link copied to clipboard

Explanation: This error message is issued during Control-D audit service initialization if an error is detected in the AUDTPARM audit configuration member.

The variables in this message are:

line_number - number of the line in the AUDTPARM member where the error is detected
block_name - name of the block where the error is detected
parameter_name - name of the invalid parameter

The audit service initialization stops, but the component continues to work without Control-D auditing.

Corrective Action: Examine the following message that explains the reason for the error. For Control-D auditing to work properly, correct the invalid line in the AUDTPARM member and restart the task.

CTDAD2E INVALID BLOCK NAMELink copied to clipboard

Explanation: An invalid block name is detected in the AUDTPARM audit configuration member.

The audit service initialization stops, but the component continues to work without Control-D auditing.

Corrective Action: Examine the preceding CTDAD1E message where the invalid block coordinates are specified. For Control-D auditing to work properly, correct the error in the AUDTPARM member and restart the task.

CTDAD3E INVALID PARAMETER NAMELink copied to clipboard

Explanation: An invalid parameter name is detected in the AUDTPARM audit configuration member.

The audit service initialization stops, but the component continues to work without Control-D auditing.

Corrective Action: Examine the preceding CTDAD1E message where the invalid parameter coordinates are specified. For Control-D auditing to work properly, correct the error in the AUDTPARM member and restart the task.

CTDAD4E INVALID PARAMETER VALUE `value`Link copied to clipboard

Explanation: An invalid parameter value is detected in the AUDTPARM audit configuration member.

The audit service initialization stops, but the component continues to work without Control-D auditing.

CTDAD5E PARAMETER VALUE LENGTH EXCEEDEDLink copied to clipboard

Explanation: A parameter value length in the AUDTPARM audit configuration member exceeds the maximum allowable length for this parameter.

The audit service initialization stops, but the component continues to work without Control-D auditing.

CTDAD6E A MANDATORY PARAMETER IS MISSINGLink copied to clipboard

Explanation: A mandatory parameter is missing from a block of the AUDTPARM audit configuration member.

The audit service initialization stops, but the component continues to work without Control-D auditing.

CTDAD7E SPECIFIED LEVEL `level` IS NOT DEFINED IN ANY EVENT BLOCKLink copied to clipboard

Explanation: An EVENT block is not defined in the AUDTPARM audit configuration member for the level specified by the LEVELA parameter of the LEVEL block.

The audit service initialization stops, but the component continues to work without Control-D auditing.

CTDAP0I CTDAPRV UTILITY STARTEDLink copied to clipboard

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

Corrective Action: No action is required.

CTDAP1I CTDAPRV UTILITY COMPLETED SUCCESSFULLYLink copied to clipboard

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

Corrective Action: No action is required.

CTDAP2E CTDAPRV UTILITY ENDED WITH ERRORSLink copied to clipboard

Explanation: This error message indicates that the CTDAPRV utility discovered problems during processing and the utility has stopped running.

Corrective Action: Examine the job log for error messages describing the problem. Make any necessary corrections and rerun the utility.

CTDAP4E INVALID PARAMETER: `parm`Link copied to clipboard

Explanation: The parm input parameter specified in the JCL for the CTDAPRV utility is not valid and the utility has stopped running.

Corrective Action: Correct the invalid input parameter (parm) in the JCL and rerun the job.

CTDAP6E REDUNDANT PARAMETER: `parm`Link copied to clipboard

Explanation: The parm input parameter for the CTDAPRV utility has already been specified. The parameter which can be specified only once is specified twice in the current statement. The utility has stopped running.

Corrective Action: Remove the extra input parameter from the input parameters stream in JCL and rerun the job.

CTDAP7E `parm` PARAMETER LENGTH EXCEEDEDLink copied to clipboard

Explanation: The parm input parameter for the CTDAPRV utility exceeds the maximum allowable length. The utility has stopped running.

Corrective Action: Correct the invalid input parameter (parm) in the JCL and rerun the job.

CTDAP8E EMPTY `stat` STATEMENTLink copied to clipboard

Explanation: The statement stat is specified for the CTDAPRV utility without any parameters. The utility has stopped running.

Corrective Action: Add the required parameters to the statement in the JCL and rerun the job.

CTDAP9E INPUT PARAMETERS ERRORLink copied to clipboard

Explanation: This error message indicates that the CTDRETC utility discovered errors in the input parameters. Additional information about the errors is available in the job log.

Corrective Action: Examine the job log for error messages describing the problem. Make any necessary corrections in the input parameters and rerun the utility.

CTDAPAE CTDAPRV UTILITY TERMINATES DUE TO AN ERROR IN THE SORTLink copied to clipboard

Explanation: The CTDAPRV utility issues this error message when the invoked SORT utility ends with errors. The utility has stopped running.

Corrective Action: Examine the messages issued by the SORT utility to SYSOUT to identify the problem. Make appropriate changes to the JCL and rerun the job.

CTDAPBE EMAIL FOR APPROVAL=`approval name` IS NOT FOUND IN THE APPROVAL TREELink copied to clipboard

Explanation: The SHOUT command without parameter EMAIL is specified for the CTDAPRV utility, and the EMAIL destination is not specified for the corresponding Approval entry in the Approval Tree. The utility does not send the SHOUT message and continues to work.

Corrective Action: Specify the EMAIL destination in the Approval Tree or in the input parameter and rerun the job.

CTDAPCI `nnnnn` REPORTS WERE SELECTEDLink copied to clipboard

Explanation: This information message indicates that the CTDAPRV utility selected nnnnn reports for processing.

Corrective Action: No response required.

CTDAU0I CTDAUTR UTILITY STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTDAUTR utility has begun.

Corrective Action: No action is required.

CTDAU1I CTDAUTR UTILITY COMPLETED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the CTDAUTR utility has finished without errors

Corrective Action: No action is required.

CTDAU2E CTDAUTR UTILITY ENDED WITH ERRORSLink copied to clipboard

Explanation: This error message indicates that the CTDAUTR utility has finished with errors. The problem is described by previous error messages issued to the job log.

The utility stops.

Corrective Action: Examine the job log for error messages describing the reason for the problem. Fix the problem and rerun the utility.

CTDAU3E PARAMETER LENGTH EXCEEDED: `parm`Link copied to clipboard

Explanation: The value of the parm input parameter specified for the CTDAUTR utility is longer then the maximum allowed.

The utility stops.

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

CTDAU4E INVALID PARAMETER: `parm`Link copied to clipboard

Explanation: The parm input parameter specified for the CTDAUTR utility is not valid.

The utility stops.

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

CTDAU5E THE PARAMETER `parm` MUST BE SPECIFIEDLink copied to clipboard

Explanation: The required parm input parameter for the CTDAUTR utility is missing.

The utility stops.

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

CTDAU6E REDUNDANT PARAMETER: `parm`Link copied to clipboard

Explanation: The parm input parameter for the CTDAUTR utility has been specified more then once.

The utility stops.

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

CTDAU7E NUMBER OF USERID-S IN THE INPUT STREAM EXCEEDED MAXIMUM `max_number`Link copied to clipboard

Explanation: The number of USERID input parameters specified for the CTDAUTR utility is more than the allowed maximum number. The utility stops.

Corrective Action: Correct the input parameters and rerun the job.

CTDAU8E SORT FAILED WITH RETURN CODE `rc`Link copied to clipboard

Explanation: The SORT utility invoked by the CTDAUTR utility ended with errors. The CTDAUTR utility issues this message whenever the SORT utility ends with a return code (rc) other than 0.

Refer to the documentation for your SORT utility for an explanation of the return code (rc) value.

The utility stops.

Corrective Action: To correct this problem, use the following procedure:

Examine the return code (rc) and the messages issued to SYSOUT by the SORT utility to identify the problem
Make appropriate changes to the JCL
Rerun the job

CTDAU9E THE FILE PARAMETER IS NOT ALLOWED FOR ACTION=RECIPIENTSLink copied to clipboard

Explanation: This error message is issued if the FILE parameter is specified for the CTDAUTR utility when the required action is to receive list of authorized recipients (ACTION=RECIPIENTS). The FILE parameter can be specified only in case the required action is to receive the list of available reports (ACTION=REPORTS).

The utility stops.

Corrective Action: Correct the input parameters and rerun the job.

CTDAUAI ALL RECIPIENTS ARE AUTHORIZED FOR THE USER `user-id`Link copied to clipboard

Explanation: This information message is issued when the CTDAUTR utility has been submitted to receive a list of authorized recipients and all recipients are authorized for the specified User ID (user-id). This situation can occur in the following cases:

The user and security exits are missing for the environment specified by the ENV parameter.
The user and security exits called with the function USERLIST for the specified User ID return RC=0.
The specified User ID is authorized for the Recipient '*' in the Control-D Recipient tree.

The utility ends with a return code of zero without issuing the requested report.

Corrective Action: No action is required.

CTDAUBI ALL REPORTS ARE AUTHORIZED FOR THE USER `user-id`Link copied to clipboard

Explanation: This information message is issued when the CTDAUTR utility has been submitted to receive list of available reports and all available reports are authorized for the specified User ID (user-id). This situation can occur when the user and security exits are missing from the environment specified in the ENV parameter.

The utility ends with a return code of zero and a list of all Control-D reports available from the User files specified in the FILE parameter is issued.

Corrective Action: No action is required.

CTDAUCI NO RECIPIENTS ARE AUTHORIZED FOR THE USER `user-id`Link copied to clipboard

Explanation: This information message is issued when the CTDAUTR utility has been submitted to receive a list of authorized recipients and no recipients are authorized for the specified User Id (user-id) according to the Control-D Recipient tree and security definitions.

The utility ends with a return code of zero without issuing the requested report.

Corrective Action: No action is required.

CTDAUDI NO REPORTS ARE AUTHORIZED FOR THE USER `user-id`Link copied to clipboard

Explanation: This information message is issued when the CTDAUTR utility has been submitted to receive a list of available reports and no reports are authorized for the specified User Id (user-id) according to the Control-D Recipient tree and security definitions.

The utility ends with a return code of zero without issuing the requested report.

Corrective Action: No action is required.

Messages CTDB00 through CTDBxxLink copied to clipboard

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

CTDB06E OUTGRP INFORMATION IS UNAVAILABLELink copied to clipboard

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 SETLink copied to clipboard

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`Link copied to clipboard

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`Link copied to clipboard

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`Link copied to clipboard

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:

Copy

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` MODELink copied to clipboard

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 MODELink copied to clipboard

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 OKLink copied to clipboard

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

Corrective Action: No action is required.

CTDB24S CTVACDB UTILITY ENDED WITH ERRORSLink copied to clipboard

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`"Link copied to clipboard

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`Link copied to clipboard

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`Link copied to clipboard

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"Link copied to clipboard

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`Link copied to clipboard

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 CORRECTLink copied to clipboard

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`Link copied to clipboard

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`Link copied to clipboard

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` VOLUMELink copied to clipboard

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`Link copied to clipboard

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 FILELink copied to clipboard

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 STARTEDLink copied to clipboard

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 ENDEDLink copied to clipboard

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 COMPRESSINGLink copied to clipboard

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 DELETEDLink copied to clipboard

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 FILELink copied to clipboard

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`Link copied to clipboard

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`Link copied to clipboard

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)Link copied to clipboard

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"Link copied to clipboard

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 LOCATIONLink copied to clipboard

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"Link copied to clipboard

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 LOCATIONLink copied to clipboard

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 FORBIDDENLink copied to clipboard

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`Link copied to clipboard

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 ALLOWEDLink copied to clipboard

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 YETLink copied to clipboard

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 ZEROLink copied to clipboard

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`Link copied to clipboard

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 ACTIVELink copied to clipboard

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 STATUSLink copied to clipboard

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.

Messages CTDC00 through CTDCxxLink copied to clipboard

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

CTDC01I UPDATING OF ACTIVE USER REPORTS FILE STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTDDSM program started. The CTDDSM program is the second step of the CTDDELRP utility. It updates and deletes records from the Active User Report file according to information in the work file built by the first step of the CTDDELRP utility.

Corrective Action: No action is required.

CTDC02I UPDATING OF ACTIVE USER REPORTS FILE ENDED OKLink copied to clipboard

Explanation: This information message indicates that the CTDDSM program ended without errors. The CTDDSM program is the second step of the CTDDELRP utility. It updates and deletes records from the Active User Report file, according to information in the work file built by the first step of the CTDDELRP utility.

Corrective Action: No action is required.

CTDC03S UPDATING OF ACTIVE USER REPORTS FILE ENDED WITH ERRORSLink copied to clipboard

Explanation: An unrecoverable processing error was encountered by the CTDDSM program. The CTDDSM program, which is the second step of the CTDDELRP utility, updates and deletes records from the Active User Report file, according to information in the work file built by the first step of the CTDDELRP utility.

The CTDDSM program terminates with a condition code of 8.

Corrective Action: Check previously issued IOA Log file and system log messages to determine the cause of the error. Correct the problem and rerun the job.

CTDC05E OPEN OF INPUT FILE FAILED. DDNAME "DADSOIN"Link copied to clipboard

Explanation: The CTDDSM program failed to open the work file referenced by the DADSOIN DD statement. The CTDDSM program is the second step of the CTDDELRP utility. It updates and deletes records from the Active User Report file, according to information in the work file built by the first step of the CTDDELRP utility.

The CTDDSM program terminates with a condition code of 08.

Corrective Action: Check previously issued IOA Log file and system log messages to determine the cause of the error. Correct the problem and rerun the job.

CTDC28E ERROR CREATING CCIF FILE FOR PRINTING, RC=`rc`Link copied to clipboard

Explanation: An internal error occurred during an attempt to create a CCF report for immediate printing required in Page On Demand mode, while the print job created by the Control-D Application Server was creating a temporary CCF data set by means of the DVS DV_Subset function.

The print job terminates with an error.

Corrective Action: Check the DVS error messages issued together with the CTDC28E message. For information about these messages, see the DVS programmer's guide. If you cannot resolve the problem, save the return code and the DVS error messages and contact BMC Customer Support.

CTDC40I DATA BASE CONVERSION STARTEDLink copied to clipboard

Explanation: This information message indicates that the IOA Access Method (IAM) conversion program started. The IAM conversion program moves records from Active, Permanent, History, or Migrated VSAM files to the new IAM and converts these records to the new format.

Corrective Action: No action is required.

CTDC41I DATA BASE CONVERSION ENDED. RC=`rc`Link copied to clipboard

Explanation: This information message indicates that the IOA Access Method (IAM) conversion program has ended.

Corrective Action: If the conversion program ends with a non-zero return code, check the system log file for additional messages that describe the error. Correct the problem before rerunning the program.

CTDC43S DCBOUT OPEN ERRORLink copied to clipboard

Explanation: The IOA Access Method (IAM) conversion program could not open the SYSOUT file or the data set referenced by the SYSPRINT DD statement, which is used by the program to write message output during execution.

The IAM conversion program terminates.

Corrective Action: Check the system log file for additional messages that describe the error. Correct the problem before rerunning the program.

CTDC45S RC=`rc` DURING `func` OPERATIONLink copied to clipboard

Explanation: An internal error occurred during IOA Access Method (IAM) file access while the func function was executing.

The IAM conversion program terminates.

Corrective Action: Check the IOA Log file and the system log file for additional messages that describe the error. Correct the problem before rerunning the program. If the error persists, contact BMC Customer Support.

CTDC46S VSAM OPEN ERRORLink copied to clipboard

Explanation: The IOA Access Method (IAM) conversion program encountered an error while opening the VSAM input file which contains the records to be converted.

The IAM conversion program terminates.

Corrective Action: Check the system log file for additional messages that describe the error. Correct the problem before rerunning the program.

CTDC48S PARAMETER ERROR. THE PARAMETER SHOULD BE A/P/H/MLink copied to clipboard

Explanation: The Database conversion program encountered an error while reading the input parameter. The parameter that specifies the user file to be converted is invalid. Valid values are A, P, H or M to specify the Active, Permanent, History, or Migrated User file as input.

The Database conversion program terminates.

Corrective Action: Specify a valid input parameter before rerunning the program.

CTDC49S NUMBER OF CONVERSION ERRORS EXCEEDS THE MAXIMUM ALLOWEDLink copied to clipboard

Explanation: The number of errors which occurred during a Database conversion is more than the permitted maximum. This maximum number of errors permitted is specified in the Database conversion program.

The Database conversion program terminates.

Corrective Action: Check the system log file for additional messages that describe the error. Correct the problem before rerunning the Database conversion program.

CTDC51I THE PRIMARY RECORD IS NOT FOUND FOR THE CONTINUATION RECORDLink copied to clipboard

Explanation: This information message indicates that the Database conversion program encountered a continuation record that has no corresponding primary record. The Database conversion program checks all continuation records in the Database. If no primary record exists for a continuation record, the continuation record is not converted to the new Database.

The Database conversion program continues.

Corrective Action: No action is required.

CTDC52I CONVERTED:Link copied to clipboard

Explanation: This information message is issued when the Database conversion program terminates. This message is the header for data displayed by the CTDC53I message, which indicates the number of records converted.

Corrective Action: No action is required.

CTDC53I `recordType` RECORDS: `num`Link copied to clipboard

Explanation: This information message is issued when the Database conversion program terminates. A separate message indicates the number of records converted for each type of record converted. This message follows the CTDC52I message.

The Database conversion program terminates.

Corrective Action: No action is required.

CTDC54I USER NAME IN RECORD IS ZERO. RECORD IS IGNOREDLink copied to clipboard

Explanation: This information message indicates that the utility that converts Control-D or Control-V VSAM files to the IOA Access Method Database could not convert a user record found in the VSAM file. The user record has a key (user name) of binary zeros, which is invalid.

The record is passed over, and is not transferred to the IOA Access Method Database. Processing continues.

Corrective Action: No action is required.

CTDC56S ERROR IN CTV RECORD CONVERSIONLink copied to clipboard

Explanation: During index record conversion, the CTVCVI program, which converts the index records, ended with a return code greater than 4.

The database conversion program terminates.

Corrective Action: Correct the problem according to the messages which are issued with this message, and rerun the conversion job.

Messages CTDD00 through CTDDxxLink copied to clipboard

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

CTDD69E QUOTES WITHIN QUOTED STRING MUST BE PAIREDLink copied to clipboard

Explanation: Quotation marks in the STRING field were not paired. When quotes are specified in the STRING field, they must be paired.

Corrective Action: Correct the quotation marks in the STRING field.

CTDD6AE EMPTY STRING IN QUOTES NOT PERMITTEDLink copied to clipboard

Explanation: An empty string between two quotation marks (" ") was specified in the Include, Exclude, or Color Lines screens. An empty string is not a valid criterion for Include or Exclude lines.

Corrective Action: Correct the string specification.

CTDD70E COLOR SHOULD BE BLANK OR: B,G,P,R,T,W,YLink copied to clipboard

Explanation: An invalid value was specified in the COLOR field.

Valid COLOR options are:

Blank - no color
B - blue
G - green
P - pink
R - red
T - turquoise
W - white
Y - yellow

Corrective Action: Specify a valid COLOR option in the COLOR field.

CTDD71E HILITE SHOULD BE BLANK OR B,R,ULink copied to clipboard

Explanation: An invalid value was specified in the HILITE field.

Valid HILITE options are:

B - blink
R - reverse video
U - underscore

Corrective Action: Specify a valid HILITE option in the HILITE field.

CTDD72E PLEASE SPECIFY ONLY ONE ON INSTRUCTIONLink copied to clipboard

Explanation: An object for coloring or highlighting is not defined, or two or more objects are specified. Only one object - a string, line or column/line range - may be specified for coloring or highlighting.

Corrective Action: Select only one type of object to be colored or highlighted.

CTDD90S OPEN OF ACTIVE TRANSFER FILE FAILED. DDNAME "DAATF"Link copied to clipboard

Explanation: The Active Transfer file cannot be opened. The DAATF DD statement is missing.

Requested function is not performed.

Corrective Action: Check that the DAATF DD statement is defined in the logon or Online monitor procedure.

CTDD91S ERROR ON CONTROL-D ACTIVE TRANSFER FILELink copied to clipboard

Explanation: An error was detected while attempting to access the Active Transfer file. This is probably caused by an I/O error.

Requested function is not performed.

Corrective Action: Fix the I/O error and retry the action.

CTDD92E CANNOT `func` PACKET `pktName` - NOT HELDLink copied to clipboard

Explanation: An attempt was made to FREE or DELETE a packet while the packet was not in the HELD status. A packet must be in the HELD state before it may be freed or deleted.

Requested function is not performed.

Corrective Action: Place the packet in the HELD state using the H option, and retry the required action.

CTDD93E CANNOT `func` PACKET `pktName` - ALREADY DELETEDLink copied to clipboard

Explanation: An action was attempted on a deleted packet.

The requested action is not performed.

Corrective Action: If a function is required for a deleted packet, then order a new packet.

CTDD94I func OF PACKET `pktName` PERFORMEDLink copied to clipboard

Explanation: This information message indicates that the requested action was processed successfully.

Corrective Action: No action is required.

CTDD95E CANNOT ZOOM PACKET `userName` - INTERNAL ERROR `rc`Link copied to clipboard

Explanation: An internal error occurred in the zoom operation in the PC Packet Status screen (F Screen).

The zoomed record remains unchanged.

Corrective Action: Supply BMC Customer Support with the return code identified in the message.

CTDD96E CANNOT HOLD PACKET `pktName` - ALREADY HELDLink copied to clipboard

Explanation: A HOLD request was issued for a packet that was already held. A packet that is already held cannot be held again until after it is freed.

Requested function is not performed.

Corrective Action: Correct the action required and retry.

CTDD97E COPIES FIELD MUST CONTAIN A NUMBER FROM 1 TO 255Link copied to clipboard

Explanation: An invalid number was entered in the COPIES field on the Confirm Print Window of the file Transfer Control screen. Valid values are from 1 through 255.

Corrective Action: Enter a valid value in the COPIES field.

CTDD98I PRINT COMPLETED OKLink copied to clipboard

Explanation: This information message indicates that the Immediate Printing for the PC user ENDED OK.

Corrective Action: No action is required.

CTDD99E I4NVALID DESTINATIONLink copied to clipboard

Explanation: An invalid destination was entered in the Confirm Print Window of the file Transfer Control screen. Only destinations that are defined in JES parameters for the site are valid.

Corrective Action: Correct the entry in the DEST field on the window.

CTDD9AE SYSOUT ALLOCATION ERROR, CODE=`rc rsn`Link copied to clipboard

Explanation: The Immediate Printing request ENDED NOTOK due to an error in allocating the SYSOUT file. The SYSOUT parameters for one of the reports to be printed may be invalid

Printing stops. Reports processed before the error were already sent to JES.

Corrective Action: Check the characteristics of the reports contained in this packet. If necessary, check MVS documentation for an explanation of the return code for Dynamic Allocation and the reason code.

CTDD9BE FILE ALLOCATION ERROR, CODE=`rc rsn`Link copied to clipboard

Explanation: The Immediate Printing request ENDED NOTOK due to an error in allocating the input files. The CDAM file and/or the index file may have been manually deleted. The variables in this message are:

rc - the error return code
rsn - the error reason code

Printing is not performed.

Corrective Action: No action is required.

CTDD9CE PRINT INTERNAL ERRORLink copied to clipboard

Explanation: Immediate Printing failed due to internal error.

Printing stops. Part of the files may be printed.

Corrective Action: Notify your INCONTROL administrator.

CTDD9DE ENTER "Y" OR "N"Link copied to clipboard

Explanation: The CONFIRM field of the Confirm Print Window of the file Transfer Control screen contains an invalid value. Valid values are Y (Yes) and N (No).

Corrective Action: Enter Y to perform printing or N to exit the window without printing.

CTDD9EE YOU ARE NOT AUTHORIZED TO PERFORM `func`Link copied to clipboard

Explanation: The Security Exit denied the request to perform a function in the file Transfer Control screen.

The requested function is not performed.

Corrective Action: Notify the INCONTROL administrator.

CTDD9FE CANNOT `func` PACKET `packet-name` - PACKET CHANGED WHILE ZOOMINGLink copied to clipboard

Explanation: The Zoom screen from which the change is requested is no longer up-to-date because packet packet-name was changed by another user after the Zoom screen was displayed. To prevent possible overlaying of the changes made by another user, or because the requested changes may no longer be valid, the requested changes are not performed.

The requested changes are not saved.

Corrective Action: Refresh the Zoom screen and repeat the changes if desired.

CTDD9GE PIX FILE ALLOCATION ERROR, CODE=`rc rsn`Link copied to clipboard

Explanation: An error occurred while trying to allocate a Pix file.

The variables in this message are:

rc - the return code from dynamic allocation
rsn - the reason code from dynamic allocation.

Corrective Action: See the IBM manual MVS Programming: Authorized Assembler Services Guide. If you still cannot resolve the problem, have your INCONTROL administrator provide BMC Customer Support with the return code and reason code.

CTDD9HE INTERNAL INDEX ERRORLink copied to clipboard

Explanation: Processing of the Index file failed due to an internal error.

Failure may be due to one of the following:

insufficient storage
Pix file Open failure

The Index screen is not displayed.

Corrective Action: Notify your INCONTROL administrator.

Messages CTDE00 through CTDExxLink copied to clipboard

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

CTDE01W $$TRNRES CTD PARMLink copied to clipboard

Explanation: During initialization of the IOA Application Server, the loading or parsing of the $$TRNRES member in the Control-D PARM library failed.

The $$TRNRES member is used for extracting print resources.

Initialization of the Application Server continues.

Corrective Action: If you need to use this feature, ensure that the $$TRNRES member is provided or corrected.

CTDE02E IOAUPDS FAILED-RC=`rc` F=`func` M=`memName` D=`dsn`Link copied to clipboard

Explanation: An error occurred during the processing of the memName member in the dsn resource library.

The variables in this message are:

rc - the internal error code
func - the code of the operation that failed
memName - the member that was being processed when the error occurred
dsn - the name of the resource library that contains memName

The transforming decollation mission fails.

Corrective Action: Call your INCONTROL administrator.

CTDE03E LIBSET `libsetname` NOT FOUND IN TRNTABLink copied to clipboard

Explanation: The report that is being decollated requires the libsetname resource libraries set, but that resource library set is not present in the $$TRNRES member in the Control-D PARM library.

The decollation mission fails.

Corrective Action: Ensure that the name of the libsetname resource library set is included in the $$TRNRES member, and redecollate the report.

CTDE04E NO TRNTAB AVAILABLE - CHECK IF $$TRNRES EXISTSLink copied to clipboard

Explanation: The $$TRNRES member is missing from the Control-D PARM library.

The transforming decollation mission fails.

Corrective Action: Call your INCONTROL administrator.

CTDE05E REPORTTYPE= PARAM IS MISSING - ADD REPORT CLIQUE FAILEDLink copied to clipboard

Explanation: An internal error occurred during a decollation that transforms the format of the decollated report.

The decollation mission ends NOT OK.

Corrective Action: Call your INCONTROL administrator.

CTDE06E INTERNAL ERROR - REPORT CLIQUE MUST BE ADDED IN ONE SECTIONLink copied to clipboard

Explanation: An internal error occurred during a decollation that transforms the format of the decollated report.

The decollation mission ends NOT OK.

Corrective Action: Call your INCONTROL administrator.

CTDE07E RESOURCE NOT FOUND: `res_req res_name res_typ rep_format res_spec res_sum lib_set_name`Link copied to clipboard

Explanation: During a decollation that transforms the format of the decollated report, a required resource was not found in the specified resource library set.

The variables in this message are:

res_req - the code of the resource request
res_name - the name of the requested resource
res_typ - the code of the type of the requested resource
rep_format - the code of the format of the decollated report
res_spec - the specification of the requested resourceValid values are:
- S - a specific resource
- D - a default resource
res_sum - the checksum of the requested resource (only where a specific resource was requested)
lib_set_name - the name of the resource library set that is currently being used

An attempt is made to perform the decollation mission without the res_name resource, or to substitute a similar resource that is available. If this attempt fails, the decollation mission ends NOT OK.

Corrective Action: Ensure that all necessary resources are available in the specified resource library set before launching the decollation mission.

CTDE08E INCORRECT SIZE OF RESOURCE'S `res` MEMBER `memName` IN LIBRARY `dsn`Link copied to clipboard

Explanation: During a decollation that transforms the format of the decollated report, the size of the required resource member did not correspond with the size recorded in the Control-D database.

The variables in this message are:

res - the name of the problematic resource
memName - the name of the resource member
dsn - the data set name of the library that contains memName

The probable cause is corruption of the memName resource member.

The decollation mission ends NOT OK.

Corrective Action: Restore the memName resource member from a backup copy.

CTDE09E RESOURCE LIBRARY `dsn` CONTAINS A MEMBER WITH AN INCORRECT NAME `memName`Link copied to clipboard

Explanation: During a transforming decollation mission, a resource library has been found to contain a member with a name that is in an invalid format.

The name of a member in a resource library must be in the format lccccccc, where l is a letter and c is a digit.

The probable cause is that a data set has been incorrectly named in the $$TRNRES member.

The variables in this message are:

dsn - the name of the resource library containing the problematic member
memName - the name of the problematic member

The decollation mission fails.

Corrective Action: Correct the name of the problematic data set in the $$TRNRES member and rerun the decollation mission.

CTDE0AE RESOURCE LIBRARY `dsn` IS INACCESSIBLE OR HAS AN INCORRECT FORMATLink copied to clipboard

Explanation: The dsn data set that was specified as a resource library in the $$TRNRES member in the Control-D PARM library is either inaccessible or in an inappropriate format.

This error message may be issued during any of the following:

a decollation mission: the mission ends NOT OK
a DO screen operation: the operation fails
the processing of a Control-D/WebAccess request: the request fails

Corrective Action: Do the following:

Ask your INCONTROL administrator to recreate the dsn data set in the correct format and ensure its accessibility
Retry the mission, operation or request.

CTDE0BI RESOURCE LIBRARY `dsn` IS SUBMITTED FOR HSM RECALL. PLEASE RETRY YOUR REQUEST AFTER A FEW MINUTESLink copied to clipboard

Explanation: The required resource library, dsn, has been migrated by HSM.

This message may be issued during a DO screen operation or the processing of a Control-D/WebAccess request.

A request is issued to HSM RECALL to recall dsn and make it available.

Corrective Action: Wait for a few minutes, and then retry the operation or reissue the request.

CTDE0CE ERROR WHILE PROCESSING RESOURCE LIBRARY. F=`req` L=`dsn` M=`memName`. IOAMEM RC+RSN=`rsn`Link copied to clipboard

Explanation: A complicated error occurred during one of the following:

a decollation mission: the mission ends NOT OK
a DO screen operation: the operation fails
the processing of a Control-D/WebAccess request: the request fails

The variables in this message are:

req - the code of the request
dsn - the data set name of the relevant resource library
memName - the name of the resource member that is being processed
rsn - the combined return and reason code received from IOAMEM

Corrective Action: Contact your INCONTROL administrator.

CTDE0DE ALLOCATION ERROR FOR THE RESOURCE LIBRARY `dsn`. RSN=`rsn`Link copied to clipboard

Explanation: A required resource library could not be accessed.

The variables in this message are:

dsn - the data set name of the required resource library
rsn - the dynamic allocation failure reason code

This error message may be issued during any of the following:

a decollation mission: the mission ends NOT OK
a DO screen operation: the operation fails
the processing of a Control-D/WebAccess request: the request fails

Corrective Action: Contact your INCONTROL administrator.

CTDE0EE HSM RECALL ERROR FOR THE RESOURCE LIBRARY `dsn`. RC=`rc`Link copied to clipboard

Explanation: A request to recall a required resource library was submitted to HSM RECALL to ensure its accessibility, but the request failed.

The variables in this message are:

dsn - the name of the required resource library that was the subject of the failed HSM request
rc - the return code received from HSM
If this message was issued during a decollation mission, the mission ends NOT OK.
If this message was issued during a screen DO operation, the operation fails.
If this message was issued during the processing of a Control-D/WebAccess user request, the request fails.

Corrective Action: Contact your INCONTROL administrator.

CTDE10E INVALID VALUE, USE "Y" OR "N"Link copied to clipboard

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

Corrective Action: Select Y for Yes, or N for No.

CTDE11E PARAMETER MEMBER $$TRNRES IS TOO LARGELink copied to clipboard

Explanation: The size of the $$TRNRES member exceeds the allowed maximum.

The Control-D monitor fails and the decollation mission ends NOTOK.

Corrective Action: Decrease the size of the $$TRNRES member.

CTDE12E RESOURCE LIBRARY HAS AN INCORRECT FORMATLink copied to clipboard

Explanation: The Control-D resource library has an inappropriate RECFM or LRECL value.

Control-D uses the CTD RESLIB library to store resources used for Control-D Transformer. The name of the CTD RESLIB library is saved in the User file, which causes a limitation during upgrade (you need to use a constant data set name in all releases). To prevent incorrect use of different CTD RESLIB library names, Control-D installs RESLIB with an incorrect RECFM parameter.

The system performs one of the following actions:

The decollation mission ends NOTOK.
The online environment fails with one of more of the following messages: IOAE42E, MAN85ES.

Corrective Action: If the message was issued after upgrade to a new release, in order to use CTD RESLIB from the previous release, do the following:

Delete the CTD RESLIB allocated in the new environment.
In the IOADSNL member of the IOA PARM library, add a reference to the relevant CTD RESLIB data set.

If you did not previously work with transformers, create a new CTD RESLIB file for resource management, as follows:

Delete the CTD RESLIB allocated during installation.
Use job CTDFRESL to allocate a new file.

CTDE13E RESOURCE LIBRARY ACCESS ERRORLink copied to clipboard

Explanation: An internal error occurred while accessing the Control-D resource library. It may be supplemented with system messages explaining the cause of the problem in more detail.

The Control-D monitor fails and the decollation mission ends NOTOK.

Corrective Action: Contact your INCONTROL administrator.

CTDE14E PROCESSING MEMBER $$TRNRES FAILSLink copied to clipboard

Explanation: A general error occurred while processing the Control-D resource library. It is supplemented with other IOA messages explaining the cause of the problem in more detail.

The Control-D monitor fails and the decollation mission ends NOTOK.

Corrective Action: Contact your INCONTROL administrator.

Messages CTDF00 through CTDFxxLink copied to clipboard

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

CTDF01I CDAM CLEAN-UP UTILITY STARTEDLink copied to clipboard

Explanation: This information message indicates the normal start of the CTDCCU Control-D utility. This utility identifies CDAM files that can be deleted from disk because they are no longer referenced by the Active User Report List file.

Corrective Action: No action is required.

CTDF01S INSUFFICIENT STORAGE FOR TRANSFER SUBTASKLink copied to clipboard

Explanation: A request for additional storage to attach a new transfer subtask failed.

The request is ignored, and the transfer subtask is not stored. Other processing continues.

Corrective Action: Increase the value of the REGION parameter to increase the region size.

CTDF02I CDAM CLEAN-UP UTILIT4Y ENDED OKLink copied to clipboard

Explanation: This information message is the normal end message of the CTDCCU Control-D utility CTDCCU. This utility identifies CDAM files that can be deleted from disk because they are no longer referenced by the Active User Report List file.

Corrective Action: No action is required.

CTDF02S ERROR IN DYNALLOC FUNCTION: `func` RC =`rc rsn`Link copied to clipboard

Explanation:An error occurred under FTO Application Server during the attempted dynamic allocation of an output SYSOUT or CDAM data set, and the allocation failed.

The variables in this message are:

func – the failed function
rc – the return code
rsn – the reason code

For more information on the return code and reason code, refer to IBM manuals about interpreting dynamic allocation error return and reason codes.

The SYSOUT or CDAM data set is not created.

Corrective Action: Do the following:

1. Try to correct the error, using the information provided by the return code and reason code.

2. If you cannot solve the problem, note the values of func, rc, and rsn, and contact BMC Customer Support.

CTDF03S CDAM CLEAN-UP UTILITY ENDED WITH ERRORSLink copied to clipboard

Explanation: The CTDCCU Control-D utility ended with errors. The sysout of the job should contain other messages detailing the reasons.

The utility stops executing with a return code which depends on the severity of the error.

Corrective Action: Check the previous error message or messages, correct the problem and rerun the job.

CTDF05E OPEN OF INPUT FILE FAILED. DDNAME "DACCUIN"Link copied to clipboard

Explanation: Open of the file containing input parameters failed (the DACCUIN DD statement). This error message is issued by the CTDCCU Control-D utility, which is used to identify CDAM files that are no longer referenced by the Active User Report List file.

It may be due to one of the following:

The DACCUIN DD statement is missing.
The data set pointed to by the DACCUIN DD statement cannot be opened for sequential read.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

CTDF05S `text`Link copied to clipboard

Explanation: An error occurred during transmission of a file to the PC. The message text (text) describes the reason for the problem.

The file is not transmitted.

Corrective Action: Correct the problem, and restart the File Transfer monitor.

CTDF06I FILES ARE TRANSMITTED OK FOR USER `userId` IPA=`ipAdd:port` FILE=`fileName`.CDMLink copied to clipboard

Explanation: This information message indicates that the specified files were successfully transmitted to the PC.

The variables in this message are:

userId - the identity of the user to whom the report belongs
ipAdd - the IP address
port - the port number
fileName - the name of the file being transferred

Corrective Action: No action is required.

CTDF0AI FILE TRANSFER STARTED. FOR USER `userId` IPA=`ipAdd :port` FILE=`fileName`.CDMLink copied to clipboard

Explanation: This information message is displayed when the File Transfer monitor starts to transfer a package to the identified IP address.

The variables in this message are:

userId - the identity of the user to whom the report belongs
ipAdd - the IP address
port - the port number
fileName - the name of the file being transferred

Corrective Action: No action is required.

CTDF0BI WAITING FOR CTDDELRP OR RESTORE JOB TO TERMINATELink copied to clipboard

Explanation: This information message indicates that the CTDCCU utility is waiting for a CTDDELRP job or a restore job to terminate before the utility can resume executing.

This error message is issued by the CTDCCU Control-D utility, which is used to identify CDAM files that are no longer referenced by the Active User Report List file.

To ensure data integrity, do not run the CTDCCU utility concurrently with a CTDDELRP job or a restore job.

When the contending job terminates, the CTDCCU utility resumes processing.

Corrective Action: No action is required.

CTDF0CI UNRECOVERABLE ERROR ENCOUNTERED.Link copied to clipboard

Explanation: During the operation of the File Transfer monitor, an unrecoverable error occurred when access was attempted to the Active Transfer file.

The File Transfer monitor shuts down.

Corrective Action: Contact your INCONTROL administrator.

CTDF0DS SECURITY VIOLATION IN THE FILE TRANSFER MONITOR.Link copied to clipboard

Explanation: A serious error occurred while the File Transfer monitor was working. The transfer of the package was rejected by a security exit, or by User Exit 23.

Every transfer request is sent to both the security exit and the user exit, if they exist. Either exit can reject a transfer request.

The package is not transferred.

Corrective Action: If you consider that you ought to have authority to transfer the package, contact your INCONTROL administrator.

CTDF0EW ATF IS REFRESHED. SUBTASK IPA=`IP address` IS CLOSED.Link copied to clipboard

Explanation: This warning message is issued when the transfer process fails because the status of the corresponding record in the ATF can not be updated. It can occur if a package, whose time has come for transfer, can not find the corresponding record in the ATF because it was reformatted and refreshed during the NEWDAY process.

CTDFTM continues to work and the subtask with the specified IP address is closed.

Corrective Action: If the package remains at the status NOT TRANSMITTED, reorder the package.

CTDF10E OPEN OF SORT FILE FAILED. DDNAME `ddName`Link copied to clipboard

Explanation: The site sort utility, which was invoked by the CTDCCU Control-D utility, failed to open the data set pointed to by the ddName DD statement. This error message is issued by the CTDCCU Control-D utility, which identifies CDAM files that are no longer referenced by the Active User Report List file.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

CTDF11E INVALID RETURN CODE FROM SORT. RC=`rc`Link copied to clipboard

Explanation: The sort utility of the site, which was invoked by the CTDCCU Control-D utility, has ended with errors.

This error message is issued by the CTDCCU Control-D utility, which is used to identify CDAM files that are no longer referenced by the Active User Report List file.

The utility stops executing with a condition code of 08.

Corrective Action: Refer to the sort messages of the job and to the user guide for the sort facility used at your site. Call your system programmer for assistance if necessary.

CTDF12E INVALID RETURN CODE FROM IDCAMSLink copied to clipboard

Explanation: The site IDCAMS program, which was invoked by the CTDCCU Control-D utility, has ended with errors. The error is usually caused by corrupted data in the system catalog.

This error message is issued by the CTDCCU Control-D utility, which is used to identify CDAM files that are no longer referenced by the Active User Report List file.

The utility stops executing with a condition code of 08.

Corrective Action: Use TSO command LISTC LVL (prefix) HISTORY to produce more detailed messages about the problem and correct accordingly.

CTDF13E OPEN OF WORK FILE FAILED. DDNAME "DAWORK"Link copied to clipboard

Explanation: The CTDCCU Control-D utility, which is used to identify CDAM files that are no longer referenced by the Active User Report List file, failed to open the Work List file (the DAWORK DD statement).

Possible causes are:

The DAWORK DD statement is missing.
The data set pointed to by the DAWORK DD statement cannot be opened for sequential write.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

CTDF14E INVOCATION OF PROGRAM `pgm` FAILED. PROGRAM COULD NOT BE ACCESSEDLink copied to clipboard

Explanation: Invocation of the pgm program ended with errors. This error message is issued by the CTDCCU Control-D utility, which is used to identify CDAM files that are no longer referenced by the Active User Report List file.

The utility stops executing with a condition code of 08.

Corrective Action: Look for previous error messages which describe the type of error. Call your system programmer for assistance if necessary.

CTDF20E OPEN OF SCRATCH FILE FAILED. DDNAME "DASCRLST"Link copied to clipboard

Explanation: The CTDCCU Control-D utility, which is used to identify CDAM files that are no longer referenced by the Active User Report List file, was unable to open the Scratch List file (the DASCRLST DD statement).

Possible causes are:

The DASCRLST DD statement is missing.
The data set pointed to by the DASCRLST DD statement cannot be opened for sequential write.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

CTDF20I COPYING APAPARM LIBRARY TO LIBRARY WITH RECFM VARIABLE STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTDCNVAP utility started copying the APAPARM library to a library with variable RECFM.

Corrective Action: No action is required.

CTDF21I COPYING APAPARM LIBRARY TO LIBRARY WITH RECFM VARIABLE ENDED OKLink copied to clipboard

Explanation: This information message indicates that the CTDCNVAP utility successfully finished copying the APAPARM library to a library with variable RECFM.

Corrective Action: No action is required.

CTDF22S COPYING APAPARM LIBRARY TO LIBRARY WITH RECFM VARIABLE ENDED WITH ERRORSLink copied to clipboard

Explanation: When attempting to copy the APAPARM library to a library with variable RECFM, the CTDCNVAP utility ended with errors.

Corrective Action: Notify your INCONTROL administrator.

CTDF24S UNABLE TO READ DIRECTORY. INSUFFICIENT STORAGELink copied to clipboard

Explanation: The CTDCNVAP utility could not copy the APAPARM library to a library with variable RECFM because of insufficient storage.

Corrective Action: Notify your INCONTROL administrator.

CTDF26S UNABLE TO READ A MEMBER FROM THE APAPARM LIBRARYLink copied to clipboard

Explanation: Due to an internal error while attempting a read operation, the CTDCNVAP utility could not copy a member from the APAPARM library to a library with variable RECFM.

Corrective Action: Notify your INCONTROL administrator.

CTDF27S UNABLE TO PUT A MEMBER TO THE NEW APAPARM LIBRARYLink copied to clipboard

Explanation: Due to an internal error while attempting a write operation, the CTDCNVAP utility could not copy a member from the APAPARM library to a library with variable RECFM.

Corrective Action: Notify your INCONTROL administrator.

CTDF28S INPUT APAPARM LIBRARY IS EMPTYLink copied to clipboard

Explanation: The CTDCNVAP utility could not copy a member from the APAPARM library to a library with variable RECFM because the input library is empty.

Corrective Action: Notify your INCONTROL administrator.

CTDF30E INTERNAL CONSOLE ERROR. FUNCTION `func`. RETURN CODES `rc`, `rc`. REASON CODE `rsn`. USING THE INTERNAL CONSOLE TERMINATESLink copied to clipboard

Explanation: An error occurred when using the extended MCS console.

Control-D terminates the extended MCS console and starts using a standard method for preventing the mixing of chunks during deferred printing.

Corrective Action: Keep a system log of the problem, and a job log of the Control-D printer monitor. It is recommended to stop, then restart, the Control-D monitor to prevent a possible mixing chunks problem.

CTDF31I THE INTERNAL OPERATOR CONSOLE IS ACTIVATEDLink copied to clipboard

Explanation: This information message is generated when Control-D activates an extended MCS console to prevent the mixing of chunks during deferred printing.

When APPLY is set to YES for optional wish WD2624, Control-D uses an extended MCS console to prevent the mixing of chunks during deferred printing.

Corrective Action: No action is required.

CTDF32E NO RESPONSE OF INTERNAL CONSOLE. USING THE CONSOLE TERMINATESLink copied to clipboard

Explanation: There is no response from the extended MCS console used by Control-D to prevent the mixing of chunks during deferred printing.

Control-D stops using the extended MCS console and starts using a standard method for preventing the mixing of chunks during deferred printing.

Corrective Action: Keep a system log of the problem, and a job log of the Control-D printer monitor. It is recommended to stop, then restart, Control-D monitor to prevent a possible mixing chunks problem.

CTDF40I ACIF PRINTING INTERFACE STARTEDLink copied to clipboard

Explanation: This information message indicates that the Control-D ACIF Interface Facility has started for a report being processed by the Printing Mission that issued the message.

A report destined for PC file transfer that was decollated with the ACIF CDAM parameter set to YES will be converted by ACIF into AFP Category 5 data stream format.

The Printing Mission begins initialization of the ACIF Interface Facility.

Corrective Action: No action is required.

CTDF41I ACIF PRINTING INTERFACE COMPLETED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the Control-D ACIF Interface Facility has successfully converted a report being processed by the Printing Mission that issued the message.

A report destined for PC file transfer that was decollated with the ACIF CDAM parameter set to YES was converted by ACIF into AFP Category 5 data stream format.

The Printing Mission terminates processing of the ACIF Interface Facility and completes processing of the report.

Corrective Action: No action is required.

CTDF42E ACIF PRINTING INTERFACE ENDED IN ERRORLink copied to clipboard

Explanation: The Control-D ACIF Interface Facility encountered an error condition while attempting to convert a report being processed by the Printing Mission that issued the message.

This message is followed by the ACIF43E and ACIF44E messages that describe the cause of the error.

The Printing Mission terminates processing of the ACIF Interface Facility and ends in error.

Corrective Action: Examine the ACIF43E and ACIF44E messages to determine why the Control-D ACIF Interface Facility ended in error and correct the problem accordingly.

CTDF43E CODE=`err_cod`, R15=`reg _`15, R0=`reg _`0, R1=`reg _`1Link copied to clipboard

Explanation: The Control-D ACIF Interface Facility encountered an error condition while attempting to convert a report being processed by the Printing Mission that issued the message. This message displays the Control-D internal error code and the contents of registers 15, 0 and 1 at the time of error.

The variables in this message are:

err_cod - the Control-D internal error code
reg_15 - the contents of register 15
reg_0 - the contents of register 0
reg_1 - the contents of register 1

The Control-D ACIF Interface Facility issues this message in combination with the ACIF44E message to describe the error and to assist in diagnosing its cause.

The Control-D ACIF Interface Facility terminates processing of the report. The Printing Mission ends in error.

Corrective Action: Examine the ACIF44E message for a description of the problem encountered.

CTDF44E `descr`Link copied to clipboard

The Control-D ACIF Interface Facility issues this message in combination with the ACIF43E message to describe the error and to assist in diagnosing its cause.

The Control-D ACIF Interface Facility terminates processing of the report. The Printing Mission ends in error.

Corrective Action: Use the information displayed in this message and in the ACIF43E message to determine the cause of the error and correct the problem. If the problem persists, contact your INCONTROL administrator.

CTDF45I MAXIMUM CONCURRENT ACIF PRINTING MISSIONS ALREADY EXECUTINGLink copied to clipboard

Explanation: This information message indicates that the Control-D ACIF Interface Facility is temporarily unavailable because, within a Print monitor address space, the maximum number of Printing Missions that can concurrently use the facility has been reached.

The Control-D ACIF Interface Facility limits the total number of ACIF subtasks that can execute at the same time. This limit is defined by means of customization setting WD2375. The wait interval is defined by means of customization setting WD2377.

When the time specified in the wait interval has elapsed, the Printing Mission again tries to access the Control-D ACIF Interface Facility.

Corrective Action: No action is required.

CTDF46I WAITING FOR AN EXECUTING ACIF PRINTING MISSION TO COMPLETELink copied to clipboard

Explanation: This information message indicates that the Printing Mission detected that the maximum number of ACIF subtasks permitted to execute simultaneously has been reached.

When the time specified in the wait interval has elapsed, the Printing Mission again tries to access the Control-D ACIF Interface Facility.

Corrective Action: No action is required.

CTDF47E MAXIMUM RETRIES LIMIT TO START AN ACIF PRINTING MISSION REACHEDLink copied to clipboard

Explanation: The Printing Mission failed to access the Control-D ACIF Interface Facility after making the maximum number of attempts allowed.

The Control-D ACIF Interface Facility was being used by the maximum number of ACIF subtasks allowed to execute concurrently. The Printing Mission tried to access the Control-D ACIF Interface Facility without success more than the maximum retry value specified by means of customization setting WD2378.

The Printing Mission ends in error.

Corrective Action: Increase the maximum retry value specified by means of customization setting WD2378 and/or increase the wait interval value specified by means of customization setting WD2377. Reorder the Printing Mission. If the problem persists, contact your INCONTROL administrator.

CTDF48W ACIFPARM MEMBER `memName` NOT FOUND - SEARCHING FOR MEMBER $$$$DFLTLink copied to clipboard

Explanation: No matching member was found in the Control-D ACIFPARM library for the report being processed by the Control-D ACIF Interface Facility.

Control-D failed to find an ACIFPARM library member whose name matches either the report’s job, Printing Mission or Recipient name. The member name search convention used is determined by the setting of optional wish WD2376. The default is J for job name.

Control-D will attempt to obtain default ACIF execution parameters from the $$$$DFLT ACIFPARM member.

Corrective Action: Check the setting for optional wish WD2376. Add a member to the ACIFPARM library with the appropriate name or verify that the default ACIF execution parameters in the $$$$DFLT ACIFPARM member are appropriate for the report.

CTDF49W ACIF ISSUED WARNING MESSAGES - PROCESSING CONTINUESLink copied to clipboard

Explanation: The Control-D ACIF Interface Facility has detected that ACIF completed processing with a noncritical return code of 4.

The Control-D ACIF Interface Facility has successfully completed converting the report to AFP Category 5 data stream format. However, a warning condition was detected by ACIF that may affect the data stream’s contents.

Corrective Action: Inspect the ACIF message output to determine the cause of the warning and whether or not its effect on the report data stream can be ignored.

CTDF63W ACTIVE MISSIONS FILE IS NEARLY FULLLink copied to clipboard

Explanation:Highlighted, unrollable message.

The Active Missions file is over 90% full. When the Active Missions file is 90% full, Control-D alerts the user. If the Active Missions file is 100% full, new missions cannot be ordered.

Corrective Action: Notify the INCONTROL administrator. The Active Missions file size should be increased.

CTDF64I PLEASE NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation:Highlighted, unrollable message.

Usually issued after a severe Control-D error which needs to be handled by an experienced Control-D person.

Corrective Action: Call your IOA administrator immediately.

CTDF90S OPEN OF DDCARD `ddName` FAILEDLink copied to clipboard

Explanation: Open for the ddName DD statement pointing to the password member failed.

Possible causes are:

The ddName DD statement is missing.
The file allocated to the ddName DD statement is not a sequential file nor a member in a PDS.

Authorization to access the product is denied.

Corrective Action: Correct the JCL statement for the procedure or the allocations for the CLIST.

CTDF91S PASSWORD MEMBER TOO LARGE (DD `ddName`)Link copied to clipboard

Explanation: The password member (or sequential data set) has too many lines.

In this message, ddName is the identity of the DD statement that points to the password member.

Authorization to access the product is denied.

Corrective Action: Remove unnecessary lines from the member.

CTDF92S SYNTAX ERROR IN PASSWORD MEMBER (DD `ddName`)Link copied to clipboard

Explanation: A syntax error was found in the password member. When this message is issued by the monitor, it is generally followed by message CTDF9DS, which describes the erroneous line in the member.

In this message, ddName is the identity of the DD statement that points to the password member.

Authorization to access the product is denied.

Corrective Action: Correct the text in the password member.

CTDF93S VALUE ERROR IN PASSWORD MEMBER (DD `ddName`)Link copied to clipboard

Explanation: A field in the password member contains invalid data. When this message is issued by the monitor, it is generally followed by message CTDF9DS, which describes the erroneous line in the member.

In this message, ddName is the identity of the DD statement that points to the password member.

Authorization to access the product is denied.

Corrective Action: Correct the text in the password member.

CTDF94S PASSWORD INVALID, PLEASE RECHECK PASSWORD MEMBER (DD `ddName`)Link copied to clipboard

Explanation: Data in the password member was not consistent with the specified password.

In this message, ddName is the identity of the DD statement that points to the password member.

Authorization to access the product is denied.

Corrective Action: Check the contents of the password member against the text received from BMC Customer Support. If it checks, contact the representative.

CTDF95S PASSWORD FOR `Control-x` IS ABOUT TO EXPIRE IN `n` DAYSLink copied to clipboard

Explanation:Highlighted, unrollable message.

The password expiration period is about to end. An expiration date is specified in the password member for the product.

Corrective Action: Contact BMC Customer Support for a new password.

CTDF96S PASSWORD FOR `Control-x` HAS EXPIREDLink copied to clipboard

Explanation:Highlighted, unrollable message.

The password expiration period has ended.

An expiration date is specified in the password member for the product.

Authorization to access the product is denied.

Corrective Action: Contact BMC Customer Support for a new password.

CTDF97S INTERNAL ERROR OCCURRED ON DD `ddName`. PLEASE NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: An internal error has occurred while analyzing the password member pointed to by the ddName DD statement.

Authorization to access the product is denied.

Corrective Action: Notify the IOA administrator.

CTDF98S OBLIGATORY FIELD MISSING FROM PASSWORD MEMBER (DD `ddName`)Link copied to clipboard

Explanation: An obligatory field is missing from a password member.

The ddName DD statement points to the password member. The fields PROD, START, CPUID, PASS and TYPE should appear at least once in a password member. For Control-D/WebAccess Server, the CTD_PC_USERS field is also obligatory.

Authorization to access the product is denied.

Corrective Action: Check the contents of the password member against the text received from your INCONTROL administrator.

CTDF9AS PASSWORD FOR `Control-x` NOT DEFINED IN MEMBER (DD `ddName`)Link copied to clipboard

Explanation: The member pointed to by the ddName DD statement does not contain the password for the appropriate product.

In this message, ddName is the identity of the DD statement that points to the password member.

Authorization to access the product is denied.

Corrective Action: Check that the specified password member is the correct member for this product.

CTDF9BS AUTHORIZATION PERIOD HAS NOT STARTED YET (DD `ddName`)Link copied to clipboard

Explanation: The start date of the password has not yet arrived.

The ddName DD statement points to the password member. The START field contains the starting date of the password.

Authorization to access the product is denied.

Corrective Action: Check that the specified password member is the correct member for this period.

CTDF9CS CPUID/MODEL NOT FOUND IN AUTHORIZED CPU LIST (DD `ddName`)Link copied to clipboard

Explanation: The current CPU is not defined in the CPU list.

The ddName DD statement points to the password member. Each entry in the CPU list in the password member contains the CPUID of the CPU and its model.

Authorization to access the product is denied.

Corrective Action: Check that the specified password member is the correct member for this CPU.

CTDF9DS CARD = `text`Link copied to clipboard

Explanation: This message supplies additional information for a previous error message.

This message may appear after the CTDF92S or CTDF93S message which indicates an error has occurred in one of the lines of the password member. The CTDF9DS message displays the erroneous line.

Corrective Action: See the CTDF92S or CTDF93S messages.

CTDF9ES PASSWORD DDCARD `ddName` POINTS TO A NON EXISTING MEMBER (ABEND S013-18)Link copied to clipboard

Explanation: The ddName DD statement is allocated to a nonexisting member in a PDS file.

In this message, ddName is the identity of the DD statement that points to the password member.

Authorization to access the product is denied.

Corrective Action: Correct the name of the member in the DD statement or create a member with the specified name.

CTDF9FS PASSWORD FOR `Control-x` EXPIRED, TEMPORARY AUTHORIZATION GRANTEDLink copied to clipboard

Explanation: The password for Control- x has expired. Nonetheless, Control- x can be run on the current date.

Despite password expiration, Control- x can be run on the 28th, 29th, 30th, 31st, 1st, 2nd, and 3rd days of each month for special purposes.

Control- x processing continues.

Corrective Action: Contact BMC Customer Support to obtain password renewal.

Messages CTDG00 through CTDGxxLink copied to clipboard

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

CTDG01E INDEX CREATION ERROR. RC = `rc`, INTERNAL RC = `int_rc`, REASON = `rsn`Link copied to clipboard

Explanation: Control-V was unable to create an index file.

Even though the index file is not created, the decollated report is produced.

Possible values for rc are shown in the following table:

rc	Explanation
16	Insufficient memory.
20	Insufficient space on the volumes to create the index file.
28	Size of the index file calculated internally is not big enough for all entries.
40	Dynamic allocation error.
44	Dynamic deallocation error.
48	Sort error.
Other	Internal error.

This message is followed by the REPG06E message.

The index is not created.

Corrective Action: Take appropriate actions to correct the problem associated with the specified return code:

rc	Explanation
16	Increase the REGION size of the Control-D or Control-V Decollation monitor.
20	Clear space on the volumes defined for index files in Control-V Installation Parameters or add another volume to the Control-V Installation Parameters.
28	First check that definition of every subindex is correctly defined in the decollation mission. If this is not the source of the problem, contact BMC Customer Support with the decollation mission definition and sample pages of the report.
40	For a description of the return code received, see the IBM manual `MVS Programming: Authorized Assembler Services Guide`. If you cannot resolve the problem, record the return code, internal return code and reason code. Contact BMC Customer Support.
44	Take the same action outlined for return code 40 above.
48	Check the sort messages in the Control-D or Control-V Decollation monitor sysout. If you cannot resolve the problem, record the sort messages and contact BMC Customer Support.
other	Record the return code, internal return code and reason code and contact BMC Customer Support.

CTDG01S ACTION SUSPENDED. PREVIOUS ACTION PENDINGLink copied to clipboard

Explanation: Option H (Hold), F (Free), D (Delete), R (Rerun) or C (Change) was requested for a Report decollating mission. The status of the mission, as displayed on the Status screen, has not been updated completely by all the Control-D monitors.

This message is relevant only for Report decollating missions that can be processed by any active Control-D monitor (that is, the MONITOR field of the Report decollating mission definition was left blank).

The request is ignored.

Corrective Action: Try again later.

CTDG10E PLACE CURSOR ON REPORT LINESLink copied to clipboard

Explanation: The user pressed PF06 in order to specify a new tag note. However, the cursor is not on a report line. When specifying a new tag note, the cursor must point to the report line for which a note will be written.

Corrective Action: Place cursor in the desired position within a report line.

CTDG11E SPECIFY END POSITION FOR NOTE STRING, OR PF5 TO CANCELLink copied to clipboard

Explanation:PF6 was pressed to define a new tag note. The Control-D Notepad Facility is waiting for further actions. To define a new tag note, specify start and end positions in the string for which a note will be written. Specify start and end positions separately, by setting the cursor in the desired position, and pressing PF6.

Corrective Action: Put cursor at the end of the specified string, or press PF5 to cancel the current tag note specification.

CTDG12E MULTIPLE LINES ARE NOT ALLOWED FOR NOTELink copied to clipboard

Explanation: Start and end positions for the tag note string are specified on different report lines. In the current release of the Control-D Notepad Facility, start and end positions for the tag note string must be specified in the same report line.

Corrective Action: Specify start and end positions for the tag note string in the same report line.

CTDG13E INTERNAL ERROR WHEN SPECIFYING A NEW NOTELink copied to clipboard

Explanation: An internal program error was detected by the Control-D Notepad Facility when specifying a new tag note.

Corrective Action: Call BMC Customer Support.

CTDG14E RULER CHANGED. TO GET INVISIBLE NOTES PRESS PF6Link copied to clipboard

Explanation: The ruler was changed, and there were tag notes defined for the old ruler. After applying the new ruler, tag note strings are moved to other positions.

Specify tag notes after a ruler is defined, verified and applied to a report, because tag notes are related to the applied ruler.

If the strings being moved by a new ruler are related to tag notes, they will not be marked as note strings.

Corrective Action: In order to have these strings marked as note strings in their former positions, press PF6. After that the notes will be available.

CTDG15E PLEASE ENTER THE REQUIRED DATALink copied to clipboard

Explanation: You must specify the Restore Mission name in the displayed Restore Window when you request restoration of a report.

Corrective Action: Specify the Restore Mission name.

CTDG16E CANNOT GIVE TO THE SAME USERLink copied to clipboard

Explanation: The user name specified in the GIVETO Option prompt window is the user name to which the report belongs. The GIVETO Option allows a copy of a report to be given to another user but not to the owner of the report.

Corrective Action: Specify another user name in the GIVETO Option prompt window or cancel the GIVETO request by specifying N (for NO) in the CONFIRM field of the GIVETO window.

CTDG17I REPORT GIVEN TO `user2: jobName / user1 / reportName`Link copied to clipboard

Explanation: This information message indicates the normal completion of the GIVETO Option (option G) of the User Report List screen.

Corrective Action: No action is required.

CTDG18I REPORT VIEWED FROM `fileType` FILE, RC=`rc: jobName / JOBID / userName / reportName`Link copied to clipboard

Explanation: This information message indicates that a VIEW request was performed. The text of the message specifies the report name, job name, jobID, user name, file type, and return code.

Corrective Action: No action is required.

CTDG21E LOAD FAILURE OF XCOMJOB MODULELink copied to clipboard

Explanation: The FT Control monitor could not load the XCOMJOB module.

The FT Control monitor shuts down.

Corrective Action: Make sure XCOMJOB exists on the STEPLIB DD statement of the CTD2AS4 member in the PROCLIB library.

CTDG22E DYNALLOC FAILURE. DSN=`dsn`Link copied to clipboard

Explanation: The data set identified by dsn could not be dynamically allocated.

The FT Control monitor shuts down.

Corrective Action: If the DSN name is the AS4LOG file, ensure that the AS4LOG file exists with that data set name. Otherwise, notify BMC Customer Support.

CTDG24E BAD RETURN CODE FROM XCOM, RC=`rc`Link copied to clipboard

Explanation: XCOM is currently not available.

The FT Control monitor continues its regular cycles, issuing requests to the XCOM server.

Corrective Action: Check XCOM availability. Refer to the Application Program Interface chapter in the XCOM manual. If XCOM stops and restarts between FT Control monitor cycles, the transfer process will continue.

CTDG25E FAILURE LOADING CTDAS4USLink copied to clipboard

Explanation: The Control-D AS/400 Users Table (CTDAS4US) was not loaded.

The FT Control monitor shuts down.

Corrective Action: Make sure that the library pointed to by the AS4NMDD DD name includes the CTDAS4US member.

CTDG29I INVALID MODIFY `num` (where `num` is COMMAND or TIME INTERVAL)Link copied to clipboard

Explanation: This message indicates that an invalid MODIFY command was issued.

The FT Control monitor continues without modification.

Corrective Action: Reissue the MODIFY command with the correct syntax.

CTDG2BI MONITOR STOPPEDLink copied to clipboard

Explanation: This information message indicates that the FT Control monitor stopped due to operator request. The F CTD2AS4,STOP or P CTD2AS4 command was executed.

The FT Control monitor shuts down.

Corrective Action: Use the S CTD2AS4 command to restart the file Transfer monitor when the report packet transfer process should resume.

CTDG2EE IOA LOG NOT AVAILABLELink copied to clipboard

Explanation: Attempt to open the IOA Log file failed.

The FT Control monitor shuts down.

Corrective Action: Notify your local INCONTROL administrator.

CTDG30I THE REPORT IS BEING RECALLED. PLEASE TRY LATERLink copied to clipboard

Explanation: This information message indicates that some or all of the CDAM files of the report to be viewed or printed migrated, and are not immediately available. At installations using DF/HSM, a request for online viewing or printing of a report causes sending direct HSM recall request for the HSM migrated files. Optional wish WD1623 defines whether the running program should wait for request completion or continue running and try to access the report later.

HSM recall request is sent to recall these migrated CDAM files for later access. Then, according to optional wish WD1623, either wait for the request completion or continue running.

Corrective Action: Wait until the recall request has successfully completed. Then, according to optional wish WD1623, either regain access to the report or try again to view the report.

CTDG31E YOU ARE NOT AUTHORIZED TO SPECIFY THIS PARAMETERLink copied to clipboard

Explanation: Online Viewing Security Exit 4 denied your request to display a report list by setting a non-zero return code when called with function code SELFUNC. Function code SELFUNC normally grants or denies access to display a report list depending on the selection criteria specified on the Option U Selection screen.

Corrective Action: Modify the selection criteria on the Option U Selection screen or contact your IOA or security administrator to determine why the request was denied.

CTDG32E NO INDEX EXISTS FOR THIS REPORTLink copied to clipboard

Explanation: Option X to list a report indexes in the Index Window was specified in the Active Report List screen but the selected report has no index.

Corrective Action: Define one or more indexes with DO INDEX statements in the Report Decollation Mission if this report should be indexed.

CTDG3AE DYNAMIC ALLOCATION OF INDEX FILE FAILED, REASON CODE=`rc`Link copied to clipboard

Explanation: Control-D or V failed to dynamically allocate an index file.

The index file is not allocated.

Corrective Action: For a description of the return code received, see the IBM manual MVS Programming: Authorized Assembler Services Guide. If you cannot resolve the problem, record the reason code and contact BMC Customer Support.

CTDG40E THERE ARE NO FIELDS FOR SELECTIONLink copied to clipboard

Explanation: No fields for selection were entered as input for the program.

Corrective Action: Enter at least one field for selection in the input.

CTDG41E USERFILE WAS NOT ASSIGNED PROPERLYLink copied to clipboard

Explanation: An invalid USERFILE was entered in the input.

Corrective Action: Check and correct the USERFILE given as input for the program.

CTDG42E UNEXPECTED EOFLink copied to clipboard

Explanation: Unexpected end of file.

Corrective Action: Check input parameters. For more information, see the description of the CTDUFUPD utility in the INCONTROL for z/OS Utilities Guide.

CTDG43E WRONG OPERATOR. KEY WORD 'SELECT' EXPECTEDLink copied to clipboard

Explanation: Key word ‘Select’ was not found as expected.

Corrective Action: Enter ‘Select’ keyword at the beginning of the input, followed by selection fields.

CTDG44E ERROR IN DEC_TIMELink copied to clipboard

Explanation: Decollation time is not valid.

Corrective Action: Enter only a numeric value for the DEC_TIME field.

CTDG45E FAILURE IN OPEN OF SORTIN FILELink copied to clipboard

Explanation: The utility could not open the SORTIN temporary sorting file.

Corrective Action: Examine the SYSPRINT and system log for other messages that describe the error, and correct the problem accordingly.

CTDG46E FAILURE IN OPEN OF SORTOUT FILELink copied to clipboard

Explanation: The utility could not open the SORTOUT temporary sorting file.

Corrective Action: Examine the SYSPRINT and system log for other messages that describe the error, and correct the problem accordingly.

CTDG47E INSUFFICIENT MEMORY FOR BUFFER OF USER REPORTS FILELink copied to clipboard

Explanation: There is insufficient memory for the buffer of the user reports file.

Corrective Action: Increase the REGION size and rerun the job.

CTDG48E LENGTH OF THE VALUE > MAX_LENGTH_FIELDLink copied to clipboard

Explanation: The length of the given value in the input is higher than the maximum valid length of the field.

Corrective Action: Ensure that all input parameter lengths are valid. For more information, see the description of the the CTDUFUPD utility in the INCONTROL for z/OS Utilities Guide.

CTDG49E OPERATOR IS NOT ALLOWED IN THIS CONTEXTLink copied to clipboard

Explanation: Invalid operator in the section. For example: ‘only selection’ fields are used in a ‘change to’ section.

Corrective Action: Ensure that all input parameters are specified correctly, as described for the CTDUFUPD utility in the INCONTROL for z/OS Utilities Guide.

CTDG4AE FAILURE IN WRITE TO SORTIN FILELink copied to clipboard

Explanation: The utility could not write in the SORTIN temporary sorting file.

Corrective Action: Examine the SYSPRINT and system log for other messages that describe the error, and correct the problem accordingly.

CTDG4BE FAILURE IN READ FROM SORTOUT FILELink copied to clipboard

Explanation: The utility could not read from the SORTOUT temporary sorting file.

Corrective Action: Examine the SYSPRINT and system log for other messages that describe the error, and correct the problem accordingly.

CTDG4CE FAILURE IN OPEN OF USERFILELink copied to clipboard

Explanation: The utility could not open the USERFILE file.

Corrective Action: Examine the SYSPRINT and system log for other messages that describe the error, and correct the problem accordingly.

CTDG4DE FAILURE IN OPEN OF WR2FILELink copied to clipboard

Explanation: The utility could not open the WR2FILE file.

Corrective Action: Examine the SYSPRINT and system log for other messages that describe the error, and correct the problem accordingly.

CTDG4EE FAILURE IN READ FROM USERFILELink copied to clipboard

Explanation: The utility could not read from the USERFILE file.

Corrective Action: Examine the SYSPRINT and system log for other messages that describe the error, and correct the problem accordingly.

CTDG4FE FAILURE IN WRITE TO WR2FILELink copied to clipboard

Explanation: The utility could not write in the WR2FILE file.

Corrective Action: Examine the SYSPRINT and system log for other messages that describe the error, and correct the problem accordingly.

CTDG4GE CTVX001 COULD NOT ACCESS INDEXESLink copied to clipboard

Explanation: The CTVX001 exit, could not retrieve an index value from a non-Control-V index file.

The system stops.

Corrective Action: Contact BMC Customer Support.

CTDG50E TOO MANY FILE DEFINITIONSLink copied to clipboard

Explanation: There are too many file definitions in the input.

Corrective Action: Check the input parameters. For more information, see the description of the CTDUFUPD utility in the INCONTROL for z/OS Utilities Guide.

CTDG51E UNKNOWN OPERATORLink copied to clipboard

Explanation: Invalid field parameter or syntax in input.

Corrective Action: Ensure that the fields are entered correctly and in the form field=value.

CTDG52E VALUE MISSEDLink copied to clipboard

Explanation: Invalid value given for field.

Corrective Action: Ensure that all values for fields are valid, as described for the CTDUFUPD utility in the INCONTROL for z/OS Utilities Guide.

CTDG53E WRONG FILE SPECIFIEDLink copied to clipboard

Explanation: Invalid value in FILE parameter in input.

Corrective Action: Enter a correct value for the FILE parameter in the input, as described for the CTDUFUPD utility in the INCONTROL for z/OS Utilities Guide.

CTDG54E WRONG FORMAT OF DEC_TIME VALUELink copied to clipboard

Explanation: Decollation time format is not valid.

Corrective Action: Ensure correct format for the value in the DEC_TIME field ( Hours, Minutes, Date) as described for the CTDUFUPD utility in the INCONTROL for z/OS Utilities Guide.

CTDG55E USERFILE IS EMPTYLink copied to clipboard

Explanation: The file specified in the USERFILE parameter is empty.

Corrective Action: Check the contents of the file entered in the USERFILE parameter, change it if necessary, and run the job again.

CTDG56E NUMBER OF THE SPECIFIED PARAMETERS EXCEEDS THE ALLOWED MAXIMUMLink copied to clipboard

Explanation: The number of the specified parameters exceeded the allowed maximum.

Corrective Action: Check input parameters. For more information, see the description of the CTDUFUPD utility in the INCONTROL for z/OS Utilities Guide.

CTDG57E INCORRECT VALUE OF PARAMETER PRINTLink copied to clipboard

Explanation: Invalid value for the Print parameter in the input.

Corrective Action: Enter a correct value for the PRINT parameter in the input, as described for the CTDUFUPD utility in the INCONTROL for z/OS Utilities Guide.

CTDG58E THE UTILITY ENDED WITH ERRORS.Link copied to clipboard

Explanation: The utility ended with at least one error.

Corrective Action: Examine the SYSPRINT and system log for other messages that describe the error, and correct the problem accordingly.

CTDG59E INSUFFICIENT MEMORY FOR USERFILE LISTLink copied to clipboard

Explanation: There is insufficient memory for the buffer of the user reports file.

Corrective Action: Increase the REGION size and rerun the job.

CTDG5AE FAILURE IN OPEN OF PRINTDET FILELink copied to clipboard

Explanation: The utility could not open the PRINTDET file.

Corrective Action: Examine the SYSPRINT and system log for other messages that describe the error, and correct the problem accordingly.

CTDG5BE SORT PROGRAM FAILED. SEE ITS REPORT.Link copied to clipboard

Explanation: The internal sort program ended with errors.

Corrective Action: Refer to the sort messages for the job and to the user guide for the sort facility used at your site.

CTDG5CE INVALID RECORD TYPE. APPROVAL FIELDS CAN BE UPDATED IN RECORDS TYPE 'U' ONLY.Link copied to clipboard

Explanation: Invalid record type. Record type must be ‘U’ if approval fields are specified in the input as ‘Change to’ parameters.

Corrective Action: To update approval fields, insert TYPE=U in the Selection section and rerun the utility.

CTDG61E ERROR IN FUNCTION NAME WHILE CALL CTDAMFMLink copied to clipboard

Explanation: The function requested during a call to the CTDAMFM module was invalid.

The request fails.

Corrective Action: Specify a valid function for the CTDAMFM module.

CTDG62E NOT ENOUGH MEMORY FOR GETMAIN IN CTDAMFMLink copied to clipboard

Explanation: There was not enough memory in the CTDAMFM module to perform GETMAIN.

The request fails.

Corrective Action: Specify the region size as 0.

CTDG63E ERROR WHILE LOADING CTDAMFM LOAD MODULELink copied to clipboard

Explanation: An error occurred during an attempt to load the CTDAMFM module. Either the CTDAMFM module is not in the appropriate library, or there was not enough space to load it.

Formatting of the Active Mission file (AMF) stops.

Corrective Action: Ensure that the CTDAMFM module exists in the appropriate library, and that there is enough space to load it.

CTDG66S INVALID VALUE IN PARAMETER DBFILE. VALID VALUES ARE: ACT, PRM, HST, MIG, MG1-MG9Link copied to clipboard

Explanation: The DBFILE parameter in the CTDDIB utility is not set to ACT, PRM, HST, MIG or MG n. The CTDDIB utility creates an index file from an existing data file. The user tried to run the CTDDIB utility without a valid DBFILE parameter.

The CTDDIB utility terminates.

Corrective Action: Rerun the CTDDIB utility after setting the DBFILE parameter to ACT, PRM, HST, MIG, or MGn depending on the type of file for which the index is being created, as follows:

ACT - Active User file
PRM - Permanent User file
HST - History User file
MIG - Migrated User file
MG n - Migrated User file partition, where n is the partition number

CTDG8NE INVALID EXPDATE PARAMETERLink copied to clipboard

Explanation: An invalid date is specified in the EXPDATE parameter or this parameter is specified in the PROD mode, although it must only be specified in the TEST mode.

The CTVCLMIG utility ends with a return code of 12.

Corrective Action: Correct the EXPDATE parameter and rerun the utility.

CTDGA0I DELETE OF UNNEEDED INDEX FILES STARTEDLink copied to clipboard

Explanation: This information message identified that the CTVDELI utility began execution. This utility scans the Migrated User Report List file and erases index files and index records that are no longer needed.

Corrective Action: No action is required.

CTDGA1I DELETE OF UNNEEDED INDEX FILES ENDED OKLink copied to clipboard

Explanation: This information message indicates that the CTVDELI utility finished executing without errors. This utility scans the Migrated User Report List file and erases index files and index records which are no longer needed.

Corrective Action: No action is required.

CTDGA2S DELETE OF UNNEEDED INDEX FILES ENDED WITH ERRORSLink copied to clipboard

Explanation: The CTVDELI utility ended with errors. This utility scans the Migrated User Report List file and erases index files and index records that are no longer needed. The problem is described in one or more preceding messages.

The CTVDELI utility terminates with a return code of 08.

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

CTDGA4E INVALID PARAMETER: - `parm`Link copied to clipboard

Explanation: The parm parameter is not valid for the CTVDELI utility. This message is issued by the CTVDELI Control-V utility, which scans the Migrated User Report List file, and erases index files that are no longer needed.

The CTVDELI utility terminates with a condition code of 08.

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

CTDGA5E MISSING PARAMETER AFTER: - `parm`Link copied to clipboard

Explanation: A subparameter of the parm parameter is missing. This message is issued by the CTVDELI Control-V utility, which scans the Migrated User Report List file, and erases index files that are no longer needed.

The CTVDELI utility terminates with a condition code of 08.

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

CTDGA6E REDUNDANT PARAMETER: - `parm`Link copied to clipboard

Explanation: The parm parameter is specified more than once in the CTVDELI utility. This message is issued by the CTVDELI Control-V utility, which scans the Migrated User Report List file, and erases index files that are no longer needed.

The CTVDELI utility terminates with a condition code of 08.

Corrective Action: Remove the redundant parameter, and resubmit the job. For more information, see the CTVDELI utility in the INCONTROL for z/OS Utilities Guide.

CTDGA7E OPEN OF MIGRATED USER REPORTS LIST FILE FAILED. DDNAME "DAVMIG"Link copied to clipboard

Explanation: Open of the Control-V Migrated User Report List file failed. This file is referenced by the DAMIG DD statement. This message is issued by the CTVDELI utility, which scans the Migrated User Report List file and erases index files that are no longer needed.

Possible causes are:

The DAMIG DD statement is missing.
The data set referenced by the DAMIG DD statement is not a Control-V Migrated User Report List file.
The Migrated User Report List file referenced by the DAMIG DD statement belongs to another monitor, or was produced by a different version of Control-V.

The CTVDELI utility terminates with a condition code of 08.

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

CTDGA8E OPEN OF PARAMETERS FILE FAILED. DDNAME DADELINLink copied to clipboard

Explanation: Open of the Parameters file for the CTVDELI utility failed. Possible causes are:

The DADELIN DD statement is missing.
The data set referenced by the DADELIN DD statement cannot be opened for sequential read.

The CTVDELI utility terminates with a condition code of 12.

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

CTDGA9E OPEN OF SORT FILE FAILED. DDNAME `ddName`Link copied to clipboard

Explanation: The SORT utility invoked by the CTVDELI utility failed to open the data set referenced by the ddName DD statement.

The CTVDELI utility stops.

Corrective Action: Ensure all DD statements are valid, and rerun the CTVDELI utility. For more information, see the CTVDELI utility in the INCONTROL for z/OS Utilities Guide.

CTDGAAE INVALID RETURN CODE FROM SORT, RC=`rc`Link copied to clipboard

Explanation: The internal sort program ended with errors. This message is issued by the CTVDELI utility, which scans the Migrated User Report List file and erases index files that are no longer needed. The utility uses the site sort program.

The CTVDELI terminates with a condition code of 08.

Corrective Action: Check the explanations of the sort messages for the job in the manual for your sort facility.

CTDGABI WAITING FOR A CTDDELRP, RESTORE OR ANOTHER CTVDELI JOB TO TERMINATELink copied to clipboard

Explanation: This information message indicates that the CTVDELI utility is waiting for a CTDDELRP job, a restore job, or another CTVDELI job to terminate.

The CTVDELI utility scans the Migrated User Report List file, and erases index files that are no longer needed. To ensure data integrity, CTVDELI cannot run concurrently with the CTDDELRP utility, a restore job, or another CTVDELI job.

When the contending job terminates, the CTVDELI utility resumes processing.

Corrective Action: No action is required.

CTDGACE NO INPUT PARAMETERS WERE SUPPLIEDLink copied to clipboard

Explanation: The CTVDELI utility did not receive input parameters by way of the SYSIN DD statement. The CTVDELI utility scans the Migrated User Report List file, and erases index files that are no longer needed. The utility requires input parameters indicating which actions it should perform.

The CTVDELI utility terminates with a condition code of 08.

Corrective Action: Verify that input parameters are specified by way of the SYSIN DD statement. Rerun the CTVDELI utility.

CTDGADI * PARM=TEST SPECIFIED - SIMULATION MODE *Link copied to clipboard

Explanation: This information message indicates that the CTVDELI utility is running in SIMULATION mode. In SIMULATION mode, the CTVDELI utility produces a report that indicates which indexes would have been deleted if the utility were running in PRODUCTION mode.

Corrective Action: Examine CTVDELI output to determine if the proper indexes would have been deleted from disk. Make any changes required to prevent the incorrect deletion of indexes that are needed for any reason. Rerun the utility in PRODUCTION mode to actually delete unneeded indexes from disk.

CTDGAEE LOCATE ERROR FOR INDEX `dsn`Link copied to clipboard

Explanation: The CTVDELI utility encountered index dsn, which could not be located, possibly because the data set is not cataloged. The CTVDELI utility scans the Migrated User Report List file and erases unneeded index files.

The index with the data set name dsn is not deleted.

Corrective Action: Determine why the data set could not be located. Correct the problem. Rerun the CTVDELI utility if necessary.

CTDGAFE ERROR DELETING INDEX `dsn` - FILE SKIPPEDLink copied to clipboard

Explanation: The CTVDELI utility encountered the dsn index, which could not be deleted. This message is issued by the CTVDELI utility, which scans the Migrated User Report List file, and erases index files that are no longer needed.

Possible causes include the following:

The data set was not found on the device indicated in the catalog.
The device on which the data set exists is not online.

The dsn index is not deleted.

Corrective Action: Determine why the data set could not be deleted. Correct the problem. Rerun the job if necessary.

CTDGAGE ERROR UNCATALOGING INDEX `dsn` - FILE SKIPPEDLink copied to clipboard

Explanation: The CTVDELI utility encountered the dsn index, which could not be uncataloged. This message is issued by the CTVDELI utility, which scans the Migrated User Report List file, and erases index files that are no longer needed.

The index is not uncataloged.

Corrective Action: Determine why the data set could not be uncataloged. Correct the problem. Rerun the job if necessary.

CTDGB6I NO VALUES EXIST FOR THIS INDEXLink copied to clipboard

Explanation: This information message indicates that no values of the specified index appear in the user’s report.

Corrective Action: No action is required.

CTDGB7E INVALID MEDIA SPECIFIED FOR REPORTLink copied to clipboard

Explanation: A migrated report could not be accessed because the media to which it was migrated was not found. The $SYSDATA entry that corresponds to this migrated report specifies a migrated media which does not appear in the IOASPRM.

The migrated report is not accessed.

Corrective Action: Have your INCONTROL administrator correct the IOASPRM to reference the migrated media that appears in the $SYSDATA entry.

CTDGB8E NO $SYSDATA ENTRIES EXIST FOR THIS USER ENTRYLink copied to clipboard

Explanation: The user attempted to handle (view, print, and so on) a report by means of a user entry but no corresponding $SYSDATA entry was found. The $SYSDATA record was probably deleted manually.

The user cannot view, print, and so on, the report.

Corrective Action: No action is required.

CTDGB9E INVALID VALUE. USE "Y", "N" OR "B"Link copied to clipboard

Explanation: The user entered an invalid value. The only values that are valid for this field are Y, N, or B.

Corrective Action: Correct the value entered.

CTDGBAE INVALID VALUE - FIELD NUMBER MUST BE 1 TO 12

Explanation: The value in the field is not valid. The value in this field must be from 1 through 12.

The SORT command is not performed.

Corrective Action: Correct the value specified for this field, and try again.

CTDGBBE INVALID VALUE - SORT ORDER MUST BE "A" OR "D"Link copied to clipboard

Explanation: The value that specifies the sort order is not valid. The value that specifies the sort order must be A (ascending) or D (descending).

The SORT command is not performed.

Corrective Action: Enter A or D to specify the sort order, and try again.

CTDGBCE TOO MANY PARAMETERS - UP TO 5 FIELDS CAN BE USED IN SORTLink copied to clipboard

Explanation: More that five fields specify the sort. The SORT command supports a maximum of five sort fields.

The SORT command is not performed.

Corrective Action: Redefine the sort using a maximum of five fields, and try again.

CTDGBDE INVALID PARAMETER - SHOULD BE FIELD # (1-12) AND "A" OR "D"Link copied to clipboard

Explanation: The sort field number is invalid, or the sort order, or both. Each field number must be a value from 1 through 12, and the sort order must be either A (ascending) or D (descending).

The SORT command is not performed.

Corrective Action: Correct the values, and try again.

CTDGBEE FILL FIELD NUMBERLink copied to clipboard

Explanation: The sort field number is missing. At least one sort field, and no more than five, must be specified.

The SORT command is not performed.

Corrective Action: Enter at least one value to specify the sort field, and no more than five, and try again.

CTDGBFS INTERNAL PROGRAM ERROR IN SORTLink copied to clipboard

Explanation: An internal error occurred in the sort program. At least one sort field, and no more than five, must be specified.

The SORT command is not performed.

Corrective Action: Ask your INCONTROL administrator to report this error to BMC Customer Support.

CTDGBGE CANNOT EDIT RULER - NO CORRESPONDING REPORT FOUNDLink copied to clipboard

Explanation: Attempt to edit a ruler failed, because no report entry exists that corresponds to the ruler.

Corrective Action: Either create a report entry that corresponds to the selected ruler, or create a ruler for the report entry you would like to edit by specifying ‘E’ next to the report entry.

CTDGBHE PRINT RULER `rulerName` DOES NOT EXIST FOR THIS USER/REPORT/JOBLink copied to clipboard

Explanation: The rulerName print ruler was not located. A print ruler with the specified name was not defined or the ruler name was misspelled.

The report is not printed.

Corrective Action: Verify that the desired ruler exists and is spelled correctly. If necessary, define the ruler, use another ruler that is already defined, or print the report without a ruler.

CTDGBIE COMMAND SPAGE NOT SUPPORTED WHEN VIEWING WITH INDEXLink copied to clipboard

Explanation: The SPAGE command was specified during viewing of a report with an index. Command SPAGE is not supported for viewing a report with an index.

The command is not performed.

Corrective Action: To print a report section pointed to by an index value, use either of the following:

the PRINT option from the List of Index Values panel
the PRINT command from the Quick Access panel.

CTDGBJI COMMAND "VALUE" NOT APPLICABLE WHEN VIEWING WITHOUT AN INDEXLink copied to clipboard

Explanation: This information message indicates that the command VALUE was entered to display the currently selected index value, but no index value had been used to view the report. If an index value is not used to view a report, the whole report is viewed and this command is not applicable.

The command is not performed.

Corrective Action: No action is required.

CTDGBKE "TO PAGE" IS GREATER THAN NUMBER OF PAGES IN REPORT (`reportName`)Link copied to clipboard

Explanation: The value of the TO PAGE parameter specified in the Print window is greater than the number of pages in the reportName report. The maximum value for the TO PAGE parameter is the number of pages in the report.

The reportName report is not printed.

Corrective Action: Specify a valid TO PAGE value in the Print window, and try again.

CTDGBLE CANNOT ACCESS NOTES - INTERNAL ERROR IN LINE NUMBERSLink copied to clipboard

Explanation: Tag notes for the report being viewed cannot be accessed because of an internal error. Each tag note is associated with a string in the report. The line numbers for the page are not correct. Therefore, the tag note strings cannot be located.

The tag notes and associated strings are not displayed.

Corrective Action: Record the report for which the error occurred and the actions taken while viewing the report. Contact BMC Customer Support.

CTDGBME CANNOT ACCESS NOTES - INTERNAL ERROR IN PAGE NUMBER TRANSLATIONLink copied to clipboard

Explanation: The tag notes of the report cannot be accessed because of an internal error. Each tag note is associated with a string in the report. The page number in which the string appears was not calculated correctly because of an internal error. Therefore, the tag note strings cannot be located.

The tag notes and associated strings are not displayed.

Corrective Action: Record the report for which the error occurred and the actions taken while viewing the report. Contact BMC Customer Support.

CTDGBNE NOTE CREATION FAILED - SPECIFY A STRING FROM THE ORIGINAL REPORTLink copied to clipboard

Explanation: A tag note cannot be created for the specified string. Each tag note is associated with a string in the original report, before it was edited by a Control-D ruler.

A tag note cannot be associated with any of the following types of strings:

A string on an inserted line.
A string that comes from a paste line (in the ruler definition), in a line that has column edit instructions.
A string that does not start and end in the same ‘Cut’ group, in a line that has column edit instructions.

The Notepad window is not displayed for note creation.

Corrective Action: Choose a different string to associate with the tag note.

CTDGBOE $SYSDATA RECORDS NOT SUPPORTED UNDER JCL ARCHIVINGLink copied to clipboard

Explanation: The value $SYSDATA was specified in the USER parameter in display type J of the Control-D or Control-V USER REPORTS ENTRY PANEL. It is not possible to display $SYSDATA records when using display type J (the JOB ARCHIVE display).

The User Report list is not displayed.

Corrective Action: Specify a valid user name or leave the USER parameter empty. To display $SYSDATA records, change the display type.

CTDGBPE UNABLE TO VIEW THIS REPORT - SOME COMPRESSED DATASET EXTENTS ARE MISSINGLink copied to clipboard

Explanation: Attempted to view a report stored in a CDAM file failed because at least one CDAM file extent is missing. It was probably deleted from the disk manually or by another process.

The report is not displayed.

Corrective Action: Attempt to find and restore any missing file extents.

CTDGBQE "WRAP" MODE AVAILABLE ONLY WITH "SHOWCC" MODE "ON"Link copied to clipboard

Explanation: WRAP was requested when SHOWCC was turned OFF. SHOWCC must be ON, when WRAP is requested.

WRAP is not activated.

Corrective Action: Set SHOWCC ON, and request WRAP again.

CTDGBRE RULERS NOT AVAILABLE WITH "WRAP" MODELink copied to clipboard

Explanation: WRAP was specified for a report when a ruler was turned ON. WRAP is not available when a ruler is turned ON.

WRAP is not activated.

Corrective Action: Turn OFF the ruler to use WRAP.

CTDGBSE INTERNAL ERROR DURING NOTE CREATIONLink copied to clipboard

Explanation: An internal error caused the application to try to create an empty note, or a note longer than 80 characters. A note cannot be empty or longer than 80 characters.

The note is not created.

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

CTDGBTE ERROR ACCESSING `fileName`, RC=`rc`Link copied to clipboard

Explanation: An error occurred while information was being read from the fileName CDAM file. The return code (rc) indicates why the error occurred.

Valid values for rc, and their explanations, are:

Return Code	Explanation
4	No data found
8	No space for data vector
12	Error during access of the active user file
20	Invalid function
24	Internal error in converting vsa
28	Insufficient memory to load the note pad
32	ENQ (enqueue) or dequeue error
36	USER not authorized to add, delete or update note
40	Record to replace or delete not found
080204	CDAM processing error. For more details, see CTD922E or CTD926E messages in the job log.

The report is not displayed.

Corrective Action: Ask your INCONTROL administrator for help.

CTDGBUI ADD USER `recipient` ADDED TO `username / jobName / reportName` IN {ACT | PRM} FILELink copied to clipboard

Explanation: This information message is issued if a recipient was added to the ADDITIONAL USER field.

ACT is the Active User Reports file.

PRM is the Permanent User Reports file.

Corrective Action: No action is required.

CTDGBVI ADD USER `recipient` DELETED FROM `userName / jobName / reportName` IN {ACT | PRM} FILELink copied to clipboard

Explanation: This information message is issued if a recipient was deleted from the ADDITIONAL USER field.

ACT is the Active User Reports file.
PRM is the Permanent User Reports file.

Corrective Action: No action is required.

CTDGBWI ADD USER `recipient1` REPLACED BY `recipient2` IN `userName / jobName / reportName` IN {ACT | PRM} FILELink copied to clipboard

Explanation: This information message indicates that the ADDITIONAL USER field was modified.

ACT is the Active User Reports file.
PRM is the Permanent User Reports file.

Corrective Action: No action is required.

CTDGBXE ERROR ACCESSING CDAM FILE RC=`rc`Link copied to clipboard

Explanation: An error occurred during a read of a CDAM file. The return code (rc) indicates why the error occurred.

Valid values for rc, and their explanations, are:

Return Code	Explanation
4	End of data sets
8	Point error
12	Get error
16	Unrecognized request
20	Allocation error
24	Open error
28	Subsystem not operational
32	Wrong data read from the file
36	Unrecognized cache routine name
56	Invalid media specified for report

The file is not accessed.

Corrective Action: Ask your INCONTROL administrator for assistance.

CTDGBYE CDAM SUBSYSTEM IS NOT ACTIVELink copied to clipboard

Explanation: A CDAM request was not performed because the CDAM subsystem was not active.

The request is not performed.

Corrective Action: Run the IOASINIT procedure to start the CDAM subsystem.

CTDGBZE ERROR IN `noterecord` - RC = `rc`Link copied to clipboard

Explanation: An error occurred during access of a Note record noterecord in the Active User file. A return code (rc) of 32 indicates an error during access of the Active User file.

The note is not accessed.

Corrective Action: Run the CTDGIR utility to check the integrity of the Active User file.

CTDGD0I CONTROL-V JCL ARCHIVING STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTVJAR Job Archiving utility has started.

Corrective Action: No action is required.

CTDGD1I CONTROL-V JOB ARCHIVING ENDED O.K.Link copied to clipboard

Explanation: This information message indicates that the CTVJAR Job Archiving utility ended successfully.

Corrective Action: No action is required.

CTDGD2I CONTROL-V JOB ARCHIVING FAILEDLink copied to clipboard

Explanation: This information message indicates that the CTVJAR Job Archiving utility failed. Other messages generated in response to the failure describe the cause for the failure.

Job archiving ends.

Corrective Action: Examine all messages issued by the Job and correct the failure. If necessary, correct the input and rerun the CTVJAR Job Archiving utility.

CTDGD3I * PARM=TEST SPECIFIED - SIMULATION MODE *Link copied to clipboard

Explanation: This information message indicates that the CTVJAR Job Archiving utility was run in TEST mode. CTVJAR was activated using the TEST parameter in the PARM field of the executive statement. When CTVJAR is active in TEST mode, no updates are performed to the Active User file. Only a report is created.

If the user sets the SYNC parameter to YES in CTVJAR, active generic decollation will close the recently created CDAM file. The active generic decollation will wait for new decollations until the CTVJAR Job Archiving utility is terminated.

No updates are performed to the Active User file. A report is created.

Corrective Action: Do the following:

Check the results of the TEST mode run.
If results are acceptable, rerun the CTVJAR utility with PARM set to PROD.

CTDGD4E INVALID RETURN CODE FROM SORT, RC=`rc`Link copied to clipboard

Explanation: The CTVJAR Job Archiving utility received an invalid return code from the SORT utility. CTVJAR called the SORT utility to sort the entry being consolidated, but the sort failed.

In this message, rc is the invalid return code

The system terminates the CTVJAR utility.

Corrective Action: Examine the messages generated by the SORT utility for a description of the problem. Correct the problem and rerun the CTVJAR utility.

CTDGD5E OPEN OF SORT FILE FAILED. DDNAME "SORTIN"Link copied to clipboard

Explanation: The CTVJAR Job Archiving utility was unable to open the file referenced by the SORTIN DD statement. Either the SORTIN DD statement is missing from the JCL of CTVJAR, or the definition of the SORTIN DD statement is invalid.

The CTVJAR utility terminates.

Corrective Action: Correct the DD statement and rerun the CTVJAR utility.

CTDGDCE CTDRPUF FAILED. RC: `rc`Link copied to clipboard

Explanation: Control-V called the CTDRPUF routine to create a report entry in the Active User file of the newly archived report. However, CTDRPUF was unable to create the new report.

In this message, rc is the CTVJAR return code

CTVJAR processing continues with the next report.

Corrective Action: Check the IOA log for all messages generated for this failure. If the cause for the failure remains unclear, contact BMC Customer Support.

CTDGDEE INVALID PARAMETERS RECEIVED FROM USER. RC =`rc`Link copied to clipboard

Explanation: There are invalid parameters in the SYSIN file. This is a summary message. Preceding messages clarify the error. The CTVJAR Job Archiving utility issues the return code rc.

The system terminates job archiving.

Corrective Action: Check all messages generated for this error. Correct the input parameters, and rerun the CTVJAR Job Archiving utility.

CTDGDFE THE PARAMETER `parm` MUST BE SPECIFIED FOR JOBARC UTILITYLink copied to clipboard

Explanation: The user attempted to execute the CTVJAR Job Archiving utility without specifying the parm parameter. The parm parameter is mandatory for CTVJAR.

The CTVJAR Job Archiving utility terminates.

Corrective Action: Add the parm parameter and rerun the CTVJAR utility.

CTDGE0E INVALID PARAMETER: - `parm`Link copied to clipboard

Explanation: An invalid parameter was specified in the parameter statement for the CTVJAR Job Archiving utility.

In this message, parm is the invalid parameter that was specified.

The CTVJAR Job Archiving utility terminates.

Corrective Action: Correct the values in the PARM statement, and rerun the CTVJAR Job Archiving utility.

CTDGE1E REDUNDANT PARAMETER: - `parm`Link copied to clipboard

Explanation: The parm parameter was specified more than once in the input for the CCTVJAR Job Archiving utility. The parm parameter can be specified only once in the input for this utility.

In this message, parm is the redundant parameter specified by the user.

The CTVJAR Job Archiving utility terminates.

Corrective Action: Ensure that the parm parameter is specified only once, and rerun the CTVJAR Job Archiving utility.

CTDGE2E ERROR IN PARAMETERS: FODATE IS HIGHER THAN TODATELink copied to clipboard

Explanation: A later date value was specified in FODATE than in TODATE in the input for the CTVJAR Job Archiving utility. The FODATE and TODATE parameters indicate a date range for reports to be consolidated by CTVJAR. A date range is valid only if FODATE is earlier than, or the same as, TODATE.

The CTVJAR Job Archiving utility terminates.

Corrective Action: Ensure that the date value specified for FODATE is not later than the date value for TODATE. Rerun CTVJAR.

CTDGE3E INVALID DATE SPECIFIED:= `ddName`Link copied to clipboard

Explanation: An invalid date value was specified in the ddName DD statement in the input for the CTVJAR Job Archiving utility.

The CTVJAR Job Archiving utility terminates.

Corrective Action: Check and correct the date value and rerun the CTVJAR utility.

CTDGE4E NO USER RECORDS FOUND FOR -`fileName`Link copied to clipboard

Explanation: Control-V found a SYSDATA record for the fileName CDAM file. However, the fileName CDAM file contained no user records that corresponded to the SYSDATA record. In the input for the CTVJAR Job Archiving utility, the user specified a CDAM file that contained no user records in the input for the CTVJAR utility.

In this message, fileName is the name of the problematic CDAM file.

The CTVJAR utility ignores the SYSDATA record, and continues processing normally.

Corrective Action: Check why the user records are missing. If the user records were deleted using the U screen, restore user records from a backup.

CTDGE6E CTVXVAL FAILED FOR - `indexFile` - SEE OTHER ERROR MESSAGESLink copied to clipboard

Explanation: The CTVXVAL internal routine was unable to process the indexFile index file.

The system skips the index file, and continues processing.

Corrective Action: To determine the cause, check the other messages generated by the failure of CTVXVAL.

CTDGE8E CTDTRE FAILED RC: 08Link copied to clipboard

Explanation: An internal routine failed with a return code of 08. The CTVJAR Job Archiving utility uses the CTDTRE routine to determine the validity of each user name supplied by the user for the consolidated report.

The CTVJAR utility terminates.

Corrective Action: Determine the cause by checking preceding error messages generated by the failure. Verify that the user tree is properly defined and rerun the CTVJAR utility.

CTDGE9E USER NAME `userName` IS NOT FOUND IN TREE. JOB ARCHIVING WILL NOT BE PERFORMEDLink copied to clipboard

Explanation: The userName user name could not be found by the CDTRE utility. The CTVJAR Job Archiving utility uses the CTDTRE utility program to determine the validity of the user name supplied by the user for the consolidated report. The userName user name was specified by the USER parameter of the CTVJAR utility, but could not be found in the Control-D recipient tree.

CTVJAR terminates.

Corrective Action: Correct the user parameter and rerun CTVJAR.

CTDGEEE THERE ARE TOO MANY MATCHING CDAM DATASETS KEPT OPEN BY CONTROL-D MONITORS. UTILITY TERMINATES.Link copied to clipboard

Explanation: The CTVJAR Job Archiving utility terminated execution without creating consolidated reports. This occurred under option SYNC=NO, because too many CDAM datasets matching selection criteria are opened by the Control-D decollation monitor.

Corrective Action: Execute the utility with parameter SYNC=YES.

CTDGF0I PAGES `num1` TO `num2` ARE SELECTED FOR INCLUSIONLink copied to clipboard

Explanation: This information message indicates that the SPAGE command with the INCLUDE parameter was issued during online viewing of a report. The range of pages identified in the message is printed after exit from online viewing.

Corrective Action: No action is required.

CTDGF1I PAGES `num1` TO `num2` ARE SELECTED FOR EXCLUSIONLink copied to clipboard

Explanation: This information message indicates that the SPAGE command with the EXCLUDE parameter was issued during online viewing of a report. The range of pages identified in the message is not printed after exit from online viewing.

Corrective Action: No action is required.

CTDGF2I ALL PAGES HAVE BEEN UNSELECTEDLink copied to clipboard

Explanation: This information message indicates that the SPAGE RESET command was issued during online viewing of a report. No pages are printed after exit from online viewing.

Corrective Action: No action is required.

CTDGF3E `text`Link copied to clipboard

Explanation: The specified error occurred while a report was being viewed online, during processing of the SPAGE command.

Possible values of text are:

INTERNAL ERROR - SPGB PARAMETER ADDRESS IS ZERO
UNABLE TO OBTAIN STORAGE FOR INITIAL SPAGE BLOCK
UNABLE TO OBTAIN PROGRAM WORK AREA STORAGE
INTERNAL ERROR - REPORT RECORD PARAMETER ADDRESS IS ZERO
SECURITY EXIT DENIED ACCESS TO THE SPAGE COMMAND
UNABLE TO RELEASE EXCESS STORAGE OF EXISTING SPAGE BLOCK
UNABLE TO OBTAIN STORAGE FOR EXTENDED SIZE SPAGE BLOCK
UNABLE TO RELEASE STORAGE OF COPIED SPAGE BLOCK
INTERNAL ERROR - FUNCTION ID PARAMETER ADDRESS IS ZERO
INTERNAL ERROR - FUNCTION ID CODE IS INVALID
INTERNAL ERROR - WORD COUNT PARAMETER ADDRESS IS ZERO
INTERNAL ERROR - CURRENT PAGE PARAMETER ADDRESS IS ZERO
PARAMETER NOT RECOGNIZED - CORRECT THE COMMAND AND TRY AGAIN
INTERNAL ERROR - WORD LIST PARAMETER ADDRESS IS ZERO
INVALID PARAMETER LENGTH - CORRECT THE COMMAND AND TRY AGAIN
INVALID PAGE NUMBER - SPECIFY A NUMBER FROM 1 TO 99999999
START PAGE NUMBER MUST BE SPECIFIED BEFORE END PAGE NUMBER
START PAGE NUMBER MUST NOT BE GREATER THAN END PAGE NUMBER
INTERNAL ERROR - SECURITY EXIT CALL ROUTINE ADDRESS IS ZERO
INTERNAL ERROR - SECURITY EXIT FUNCTION ID ADDRESS IS ZERO
START PAGE NUMBER GREATER THAN NUMBER OF PAGES IN THE REPORT

The SPAGE command is not processed.

Corrective Action: If possible, fix the problem and try again.

Where space is a problem, try increasing the REGION size.

If these measures fail, do the following:

Record the following information:
- the text of the message
- the IOA products that are installed at the site
- all the messages from the IOA log that refer to the report in question
- where possible, the order of the user actions during viewing of the report
Contact BMC Customer Support.

CTDGF4E USER $SYSDATA DOES NOT EXIST IN PERMANENT USER FILELink copied to clipboard

Explanation: An attempt has been made to view a $SYSDATA record in the Permanent file, but it does not exist in that file.

Corrective Action: No action is required.

CTDGI0S GID INTERFACE ERROR RC=`rc` PGM `pgm_csect` ID=`xxx` FUNCTION `func`Link copied to clipboard

Explanation: An error occurred while accessing the Global Index Database above DB2.

The variables in this message are:

rc - the return code from the CTDGID interface routine
pgm_csect - the program CSECT, which received the error
xxx - an identifier for localizing the erroneous call
func - the operation that caused the error

Valid values for rc, and their explanations, are:

Return Code	Explanation
12	Invalid function
20	Not enough storage
48	SETPATH was not issued before value accessing
56	Error opening the CTDGIDB2 member
60	Invalid parameter found in the CTDGIDB2 member
64	Obligatory parameter missing from the CTDGIDB2 member
68	Duplicate parameter found in the CTDGIDB2 member
72	More than 10 fields found in a PATH description in the CTDGIDB2 member.
76	DB2 open error
80	Accessing path not present in the CTDGIDB2 member
84	SQL error
85	SQL error if time-out occurs
88	Error in loading the DB2 interface module

The system action depends on the identity of the component that was accessing the Global Index database. 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: Search the IOA Log file and the relevant job log for messages clarifying the source of the error. Correct the error and restart IOA application server. If the error persists, contact BMC Customer Support.

CTDGI1E INVALID FUNCTIONLink copied to clipboard

Explanation: The Global Index facility was invoked with an invalid function.

The request is not performed.

Corrective Action: Request a valid function for the Global Index facility.

CTDGI6E INDEX NAME PATH IS NOT SETLink copied to clipboard

Explanation: A request for an index value was performed before a SETPATH request. SETPATH must be performed before the index value is requested

The SETPATH request fails.

Corrective Action: Put the SETPATH request before the request for an index value, and try again.

CTDGIAE OPEN OF THE CTDGIDB2 MEMBER FAILEDLink copied to clipboard

Explanation: An error occurred while opening the CTDGIDB2 member.

The Global Index request is not performed.

Corrective Action: Search the relevant job log for messages clarifying the source of the error. Determine whether the CTDGIDB2 member exists in the library pointed to by the DADPARM DD statement. After resolving the problem, either restart the IOA application server or rerun the job, depending on which component was accessing the Global Index database.

CTDGIBE INVALID STATEMENT IN CTDGIDB2: `statement`Link copied to clipboard

Explanation: An invalid statement statement was detected in the CTDGIDB2 member.

The Global Index request is not performed.

Corrective Action: Correct the CTDGIDB2 member and either restart the IOA application server or rerun the job, depending on which component is accessing the Global Index database.

CTDGICE OBLIGATORY PARAMETER (DSN, PLAN, PATH OR TABLE) IS MISSING IN CTDGIDB2Link copied to clipboard

Explanation: An obligatory parameter is missing in the CTDGIDB2 member.

The obligatory parameters are:

DSN
PLAN
PATH
TABLE

The Global Index request is not performed.

Corrective Action: Correct the CTDGIDB2 member and either restart the IOA application server or rerun the job, depending on which component is accessing the Global Index database.

CTDGIDE DUPLICATE STATEMENT IN CTDGIDB2: `duplic_stmt`Link copied to clipboard

Explanation: A duplicate statement duplic_stmt was detected in the CTDGIDB2 member, although this statement can be specified only once.

The Global Index request is not performed.

Corrective Action: Correct the CTDGIDB2 member and either restart the IOA application server or rerun the job, depending on which component is accessing the Global Index database.

CTDGIEE NUMBER OF FIELDS IN THE PATH `num` MORE THEN 10Link copied to clipboard

Explanation: Too many fields are specified for path number num. A maximum of 10 fields can be specified.

The Global Index request is not performed.

Corrective Action: Correct the CTDGIDB2 member and either restart the IOA application server or rerun the job, depending on which component is accessing the Global Index database.

CTDGIFE DB2 OPEN ERROR RC=`rc` RS=`rsn`Link copied to clipboard

Explanation: An error occurred while opening the DB2 subsystem.

The variables in this message are:

rc - the return code from the DB2 CAF interface
rsn - the reason code returned from the DB2 CAF interface

The Global Index request is not performed.

Corrective Action: For the explanation of the return and reason codes, refer to your DB2 documentation. If necessary contact your DB2 administrator.

CTDGIGE {PATH | TABLE} NOT FOUND IN CTDGIDB2: `indexPath|tableName`Link copied to clipboard

Explanation: Either the requested index path or the DB2 table was not found in the CTDGIDB2 member.

The variables in this message are:

indexPath - the requested index path
tableName - the name of the requested DB2 table

The Global Index request is not performed.

Corrective Action: Do the following:

Check the indexPath index path name and the tableName DB2 table name.
Check CTDGIDB2 member and the job input statements, and correct them as necessary.
Rerun the job.

CTDGIHE SQL ERRORLink copied to clipboard

Explanation: DB2 issued a SQL error code.

This message (CTDGIHE) is followed by the DB2 messages, which provide the error code and a detailed explanation of the error.

The Global Index request is not performed.

Corrective Action: Do the following:

To establish the source of the error, examine the DB2 messages that followed this CTDGIHE message. For clarification of the DB2 messages, refer to your DB2 documentation.
Correct the error.
Restart the IOA application server or rerun the job, depending on which component is accessing the Global Index database.
If necessary contact your DB2 administrator.

CTDGIIE GETVAL WAS NOT ISSUED BEFORE GETVSALink copied to clipboard

Explanation: A GETVSA request was issued, but a GETVAL request had not been issued before it.

The possible cause is an internal error in the application that calls the CTDGID interface routine.

The Global Index request is not performed.

Corrective Action: Contact your INCONTROL administrator.

CTDGIJE SQL ERROR `code` DURING INSERTION LINE TO DB2 TABLE `table name`Link copied to clipboard

Explanation: An SQL error occurred during inserting line to DB2 table when decollation mission loads data to Global Index database. Control-D decollates the report without loading data to Global Index database. The decollation mission is set to status ENDED- NOT "OK" after it is completed.

Corrective Action: Do the following actions:

Examine the DB2 messages associated with this error to determine the reason for the error and correct the problem.
Use the CTDGBILD job to load index values from reports decollated by this mission to the Global Index database.

Messages CTDH00 through CTDHxxLink copied to clipboard

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

CTDH01I CREATION OF PRINT CONTROL-RECORDS STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTDBLXRP utility has begun processing.

The CTDBLXRP utility rebuilds Print Control Records in the Active User Report List file.

Corrective Action: No action is required.

CTDH02I CREATION OF PRINT CONTROL-RECORDS ENDED OKLink copied to clipboard

Explanation: This information message indicates that the CTDBLXRP utility has successfully completed execution.

The CTDBLXRP utility rebuilds Print Control Records in the Active User Report List file.

The CTDBLXRP utility terminates with a condition code of 0.

Corrective Action: No action is required.

CTDH03S CREATION OF PRINT CONTROL-RECORDS ENDED WITH ERRORSLink copied to clipboard

Explanation: The CTDBLXRP utility, which rebuilds Print Control Records in the Active User Report List file, encountered a critical error during execution.

The utility terminates with a condition code of 8 or higher.

Corrective Action: Check the IOA Log file and system log for previous messages associated with the error. Correct the problem and re-execute the utility.

CTDH07E "FE" PRINT SUPPORT ERROR. RETURN CODE `rc` FUNCTION `func`Link copied to clipboard

Explanation: The CTDBLXRP utility, which rebuilds Print Control Records in the Active User Report List file, encountered an error while performing the func function.

The error associated with each return code (rc) is identified below.

rc	Explanation
008	Memory shortage.
012	Memory shortage.
016	Invalid function.
020	Database I/O error.
024	Open error.

Processing terminates.

Corrective Action: Check the IOA Log file and system log for additional messages associated with the error. Determine the cause of the error, correct the problem, and re-execute the utility. If the problem persists, contact BMC Customer Support.

Messages CTDI00 through CTDIxxLink copied to clipboard

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

CTDI01E ERROR CONNECTING SESSION MANAGERLink copied to clipboard

Explanation: An error was encountered while attempting to connect to the session manager. Printing to the CTDS destination failed because the session manager interface could not establish a connection.

The printing job fails.

Corrective Action: Fix the problem and reprint the report.

CTDI02E INSUFFICIENT STORAGE. INCREASE THE REGION SIZELink copied to clipboard

Explanation: There is insufficient storage available for program processing.

The job is not run.

Corrective Action: Increase the value of the REGION parameter and rerun the job.

CTDI03E textLink copied to clipboard

Explanation: This message includes a message text (text) returned from the communication program. This message is issued together with other error messages and clarifies the cause of the problem.

Corrective Action: No action is required.

CTDI04E INTERNAL ERROR SENDING REPORTS TO SESSION MANAGERLink copied to clipboard

Explanation: The session manager interface program was invoked with an invalid argument. The error occurred in the application using the session manager interface.

The report is not sent to the session manager.

Corrective Action: Fix the application program.

CTDI05E ERROR IN DEFAULT PARAMETERS CTDSPARM RC=`rc`Link copied to clipboard

Explanation: An error was encountered while attempting to access the CTDSPARM member in the CTD PARM library. The program cannot read the CTDSPARM member.

The attempt to read the CTDSPARM member fails.

Corrective Action: Check if the CTDSPARM member exists in the CTD PARM library, and if the CTD PARM library is allocated.

CTDI06E ERROR IN LOADING TRANSLATION TABLE RC=`rc`Link copied to clipboard

Explanation: An error was encountered while loading a translation table, for example, from EBCDIC to ASCII.

The printing job fails.

Corrective Action: Correct the problem and rerun the printing job.

CTDI07E ERROR CLOSING CONNECTION WITH SESSION MANAGERLink copied to clipboard

Explanation: An error was encountered during session termination. The session manager interface was not able to terminate the session manager connection.

The printing job fails.

Corrective Action: Fix the connection problem and rerun the printing job.

CTDI08E CTDDS HOST AND/OR PORT ARE NOT SPECIFIED IN CTDSPARMLink copied to clipboard

Explanation: The interface program cannot connect with the session manager, because a default HOST and/or PORT is not defined in the CTDSPARM member.

The connection fails.

Corrective Action: Specify defaults for HOST and PORT.

CTDI09E DYNALLOC ERROR OF THE PAG FILE. RC=`rc rsn`Link copied to clipboard

Explanation: An error occurred during dynamic allocation of a PAG file in the printing process.

The dynamic allocation request fails.

Corrective Action: Analyze the return and reason code, fix the problem accordingly, and perform the print request again.

CTDI0AE THE SYSDATA RECORD IS NOT FOUNDLink copied to clipboard

Explanation: An attempt has been made to print a report to a Control-D/Delivery Server destination by means of a user entry, but no corresponding $SYSDATA entry was found.

The probable cause is that the relevant $SYSDATA record was deleted manually.

The report is not printed to the destination.

Corrective Action: No action is required.

CTDI0BE CLOSING INVERTED COMMA IS OMITTED IN THE CTDSPARMLink copied to clipboard

Explanation: The format of a parameter value in the CTDSPARM member is invalid. The value began with a single quotation mark (') or double quotation marks ("), but did not end with the same type of quotation marks.

The invalid parameter value is ignored. The report is not printed.

Corrective Action: Examine the CTDSPARM member and insert a valid value where necessary.

CTDI0CI REPORT NAME = `reportName`Link copied to clipboard

Explanation: This information message provides the report name for the accompanying message.

Corrective Action: Examine the accompanying message and its user response, and take the appropriate corrective action.

CTDI0EE CTDS EXTERNAL DESTINATION `dest` IS NOT FOUNDLink copied to clipboard

Explanation:This message is issued when a print mission tries to send a subscription for printing a report or for notification to the Control-D/Delivery Server but the External Destination dest specified in the subscription record does not exist in the External Destinations List.

The report or notification is not sent to the Control-D Delivery Server.

Corrective Action: Do the following:

Define the External Destination dest in the External Destinations List (for more details see Control-D and Control-V User Guide) or change the External Destination in the subscription record to one that exists in the External Destination List using CTVUPINV utility.
Rerun the problematic print mission.
If you changed the External Destination to an existing one, change it also in the CTDSPARM member so that this destination is used by the next subscriptions.

CTDI0FW BODY TEXT READ ERROR, MEMBER=`memname` RC=`rc`Link copied to clipboard

Explanation:The e-mail body text cannot be read from the memname member specified in the BODYTEXT parameter of CTDS DESTINATION ATTRIBUTES. The return code rc can have the following values:

04 - the memname member does not contain a section corresponding to the printed report name.
08 - the memname member is not found in the IOA BANNERS library

The attached to e-mail report is distributed without an e-mail body text. Print mission or Immediate print ends OK.

Corrective Action:Check the BODYTEXT parameter in CTDS DESTINATION ATTRIBUTES and the content of the specified member. Fix the problem and print the report again.

CTDI0GW RECIPIENTS LIST READ ERROR, MEMBER=`memname` RC=`rc`Link copied to clipboard

Explanation:The e-mail recipients list cannot be read from the memname member specified in the RECIPIENT parameter of CTDS DESTINATION ATTRIBUTES. The return code rc can have the following values:

04 - the memname member does not contain a section corresponding to the printed report name.
08 - the memname member is not found in the IOA BANNERS library

The report is not distributed to the e-mail addresses specified in the member.

If additional e-mail addresses are specified in the RECIPIENT parameter or in the CTD tree recipient entry, the report is distributed to these e-mail addresses and the Print mission or Immediate print ends with the status OK.

If additional e-mail addresses are not specified, the report is not distributed. The CTDI0HE message follows this message and the Print mission or Immediate print ends with the status NOT OK.

Corrective Action:Check the RECIPIENT parameter in CTDS DESTINATION ATTRIBUTES. Fix the problem and print the report again.

CTDI0HE EMPTY RECIPIENTS LIST FOR THE DESTINATION `destname`Link copied to clipboard

Explanation:No e-mail addresses are resolved to report distribution when report is printed to CTDS destination of email type.

The report is not distributed and the Print mission or Immediate print ends NOT OK.

Corrective Action:Check the IOA Log for additional messages associated with this printing. Check the RECIPIENT parameter specified in the CTDS destname Destination Attribute. Fix the problem and print the report again.

CTDI0IE Number of allowed consecutive delivery errors exceeded `xx`. WVN019 is set to NOLink copied to clipboard

Explanation: The number of consecutive errors encountered while attempting to connect to the Control-D/Delivery Server exceeded the value of the DATA parameter in optional wish WVN019.

Optional wish WVN019 is set to NO for the current Printing Mission.

Corrective Action: Look for additional messages on the System and IOA Logs. Fix the problem and restart the PRINT mission.

Messages CTDJ00 through CTDJxxLink copied to clipboard

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

CTDJ01I ACTIVATION OF ALTERNATIVE INDEXES STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTDUFANX utility has activated an alternative index component of a user file.

Corrective Action: No action is required.

CTDJ02I ACTIVATION OF ALTERNATIVE INDEXES ENDED COMPLETELYLink copied to clipboard

Explanation: This information message indicates that the alternative index component was successfully activated, deactivated, or printed. This message is issued by the CTDUFANX utility.

Corrective Action: No action is required.

CTDJ03S ACTIVATION OF ALTERNATIVE INDEXES ENDED WITH ERRORLink copied to clipboard

Explanation: An error was encountered during alternative index component activation. This message is issued by the CTDUFANX utility. Other error messages indicate the cause of the error.

The alternative index file is not usable.

Corrective Action: Correct the problem, and rerun the CTDUFANX utility to activate the alternative index component.

CTDJ04I ALTERNATIVE INDEXES DEFINITIONS LISTLink copied to clipboard

Explanation: This information message indicates the list of alternative index definition statements from the member specified in parameter M of the CTDUFANX utility.

Corrective Action: No action is required.

CTDJ05I ALTERNATIVE INDEX `letter` DELETEDLink copied to clipboard

Explanation: This information message indicates alternative index deactivation. This message is issued by the CTDUFANX utility.

In this message, letter is the letter that identifies the alternative index component.

Corrective Action: No action is required.

CTDJ06I ALTERNATIVE INDEX `letter` ADDEDLink copied to clipboard

Explanation: This information message indicates alternative index activation. This message is issued by the CTDUFANX utility.

In this message, letter is the letter that identifies the alternative index component.

Corrective Action: No action is required.

CTDJ07I ACTIVE ALTERNATIVE INDEXES LISTLink copied to clipboard

Explanation: This information message indicates the list of active alternative indexes for the user file specified in the FILE parameter of the CTDUFANX utility.

Corrective Action: No action is required.

CTDJ08S ILLEGAL DEFINITION: `field`Link copied to clipboard

Explanation: An error was detected in a field in the definition statement of the definition member specified in parameter M of the CTDUFANX utility.

In this message, field is the illegal field. If field = REC LENGTH, the total length of the index record exceeds the maximum value.

The CTDUFANX utility terminates with a condition code of 24.

Corrective Action: Rerun the CTDUFANX utility after setting the correct definition. For more information, refer to the section that describes the CTDUFANX utility in the INCONTROL for z/OS Utilities Guide.

CTDJ09S FORBIDDEN INPUT PARAMETER: `parm`Link copied to clipboard

Explanation: A forbidden parameter was detected for the CTDUFANX utility.

In this message, parm is the forbidden parameter.

The CTDUFANX utility terminates with a condition code of 20.

Corrective Action: Rerun the CTDUFANX utility after setting the correct parameter. For more information, refer to the section that describes the CTDUFANX utility in the INCONTROL for z/OS Utilities Guide.

CTDJ0AS OPEN ERROR FOR DDNAME `ddName`.Link copied to clipboard

Explanation: The file that the CTDUFANX utility requested cannot be opened. Possible causes are causes:

The DD statement that references the data file is missing.
The file referenced by the DD statement is not an IOA Access Method data file.
An internal error occurred while attempting to open the file referenced by the DD statement.

The CTDUFANX utility terminates with a condition code of 8.

Corrective Action: Correct the JCL and rerun the job. If the error persists, notify your INCONTROL administrator.

CTDJ0BI INPUT PARAMETERS: `parmList`.Link copied to clipboard

Explanation: This information message indicates the input parameters list for CTDUFANX utility.

Corrective Action: No action is required.

CTDJ0CI ALTERNATIVE INDEX `letter` IS NOT AVAILABLE FOR READLink copied to clipboard

Explanation: This information message indicates that an alternative index is active but not available for read. As a result, the alternative index cannot be used during a report list request. This message is issued by the CTDUFANX utility.

In this message, letter is the letter that identifies the alternative index.

Corrective Action: If the corresponding User Report List data component contains some reports, rebuild alternative indexes using the CTDDIB utility.

CTDJ0DI ALTERNATIVE INDEX `letter` IS FORMATTEDLink copied to clipboard

Explanation: This information message indicates that an alternative index is active, but contains no index values. This message is issued by the CTDUFANX utility.

In this message, letter is the letter that identifies the alternative index.

Corrective Action: If the corresponding User Report List data component contains some reports, rebuild alternative indexes using the CTDDIB utility.

CTDJ0EI ALTERNATIVE INDEX `letter` IS NOT FORMATTEDLink copied to clipboard

Explanation: This information message indicates that an alternative index component contains some records. This message is issued by the CTDUFANX utility.

In this message, letter is the letter that identifies the alternative index.

Corrective Action: No action is required.

CTDJ0HI ALTERNATIVE INDEX `letter` IS NOT ACCESSIBLELink copied to clipboard

Explanation: This information message indicates that an inaccessible alternative index component has been detected by the CTDUFANX utility. This is caused by an internal error.

In this message, letter is the letter that identifies the alternative index.

The CTDUFANX utility terminates with a condition code of 20.

Corrective Action: Check and repair the User Report List database using the CTDDIG utility. If the error persists, notify your INCONTROL administrator.

Messages CTDM00 through CTDMxxLink copied to clipboard

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

CTDM03S Control-V UNMIGRATE ENDED WITH ERRORSLink copied to clipboard

Explanation: The CTVUNMIG Control-V utility ended with errors.

CTVUNMIG terminates.

Corrective Action: Check the job log or the IOA log for the other messages generated by this error. Correct the problem, and rerun the CTVUNMIG utility.

CTDM04E LOADING OF Control-{D | V} INSTALLATION PARAMETERS FAILEDLink copied to clipboard

Explanation: Load of the CTDPARM or CTVPARM module failed.

The loading of Control-D or Control-V Installation Parameters failed. Possible causes are:

The IOA Load library is not in the load modules search list.
There is insufficient memory to load the IOA Installation Parameters.
A specified load module does not exist in the Load library.

The CTVUNMIG utility continues without sending messages to the IOA log.

Corrective Action: Do the following:

To produce messages to the IOA log, 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, increase the region size.
Rerun the CTVUNMIG utility.

CTDM06E INVALID PARAMETER:- `parm`Link copied to clipboard

Explanation: The user specified an invalid parameter for the CTVUNMIG utility.

The utility stops executing with an error.

Corrective Action: Correct the parm parameter and rerun the utility.

CTDM07E MISSING PARAMETERSLink copied to clipboard

Explanation: The user omitted mandatory parameters from the input to the CTVUNMIG utility.

The CTVUNMIG utility stops executing with an error.

Corrective Action: Specify the required parameters and rerun the utility.

CTDM08S UNABLE TO LOAD MODULE `modnam`Link copied to clipboard

Explanation: Control-V was unable to load the modnam module.

Possible causes are:

The IOA Load library is not in the load modules search list.
Insufficient storage was available to load the module.
The modnam module does not exist in the IOA Load library.

In this message, modnam is the name of the module that could not be loaded.

The system action is determined by the module (modnam):

If modnam is the IOASPRM module, the CTVUNMIG utility continues without IOA parameters.
If modnam is the LSMCALL module, the utility stops executing with an error.

Corrective Action: No action is required.

If the IOA Load library is not in the search list, add a STEPLIB DD statement to the library.
If the loading failed due to lack of memory, increase the REGION size.

Rerun CTVMIG.

CTDM10S OPEN OF DDNAME=`ddName` DSNAME=`dsn` FAILEDLink copied to clipboard

Explanation: The user specified a DD name that could not be opened.

The utility stops executing with a condition code of 16.

Corrective Action: Check the system log for messages generated in response to this failure. If you are unable to solve the problem, report the contents of the messages to BMC Customer Support.

CTDM12I FILE DSNAME=`dsn` UNMIGRATION ENDEDLink copied to clipboard

Explanation: This information message indicates that the specified file was successfully unmigrated.

dsn is the last extent of a CDAM file that was unmigrated. The unmigrated file can be found on DASD.

Corrective Action: No action is required.

CTDM13E MIGRATED FILE EOD REACHEDLink copied to clipboard

Explanation: This information message indicates that the size of the migrated file did not correspond to the information in the header of that file.

The job stops executing with a condition code of 08.

Corrective Action: Contact BMC Customer Support and send the complete log of the job.

CTDM20I CONTROL-D FOREIGN REPORT RESTORE ENDED O.K.Link copied to clipboard

Explanation: This information message indicates that a foreign report was successfully restored as a Control-D report.

Corrective Action: No action is required.

CTDM21E CONTROL-D FOREIGN REPORT RESTORE FAILEDLink copied to clipboard

Explanation: The CTDFOR utility failed to restore the foreign report file.

The CTDFOR utility terminates. The foreign report is not restored.

Corrective Action: Examine other messages to determine the cause of the failure. Fix the problem, and rerun the CTDFOR utility.

CTDM29E REDUNDANT PARAMETER:- `parm`Link copied to clipboard

Explanation: The same parameter was specified twice for the CTDFOR utility.

The CTDFOR utility terminates.

Corrective Action: Remove the redundant parameter, and rerun the CTDFOR utility.

CTDM2FS UNKNOWN PRODUCT NAME PROVIDED IN PRODUCT= PARAMETER: `parm`Link copied to clipboard

Explanation: A product name specified in the PRODUCT parameter is unknown to the CTDFOR utility. It is not the name of a product supported by the utility.

The CTDFOR utility terminates.

Corrective Action: Set the PRODUCT parameter to the name of a supported product.

CTDM30E CONVERSION ROUTINE FAILED. RC = `rc`Link copied to clipboard

Explanation: The conversion routine called by the CTDFOR utility failed to convert the report file to a CDAM file.

The CTDFOR utility terminates.

Corrective Action: Examine other messages to determine the cause for the conversion routine failure. Correct the problem and rerun the CTDFOR utility.

CTDMP0I CTDUFMDV STARTEDLink copied to clipboard

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

Corrective Action: No action is required.

CTDMP1E MIGRATED USER FILE IS NOT ALLOWED FOR UPDATINGLink copied to clipboard

Explanation: Another application (such as the CTDDELRP or CTVCLMIG utilities or a MIGRATION mission) is updating a migrated User Report List file. The CTDUFMDV utility cannot be submitted with the PART parameter at the same time.

The CTDUFMDV utility ends with an error.

Corrective Action: Resubmit the CTDUFMDV utility with the PART parameter again. If the Migrated User File (MUF) became unavailable as a result of the CTDUFMDV utility failure, submit the CTDUFMDV utility with the RESET parameter, to restore full accessibility to the old MUF.

CTDMP2E OPEN OF FILE `ddName` FAILEDLink copied to clipboard

Explanation: The data set referenced by the ddName DD statement could not be opened.

The CTDUFMDV utility ends with an error.

Corrective Action: Check other messages generated by the CTDUFMDV job to determine the cause for the failure. Correct the problem and rerun the utility.

CTDMP3E ORDER OF INPUT PARAMETERS IS INCORRECTLink copied to clipboard

Explanation: The sequence of dates defined in the SYSIN stream for the CTDUFMDV utility, which was submitted with the EXEC statement parameter PART, is not in ascending order.

The CTDUFMDV utility ends with an error.

Corrective Action: Correct the input parameters and rerun the utility.

CTDMP4E FIELD PARM `param` IS INCORRECTLink copied to clipboard

Explanation: The value of the CTDUFMDV EXEC statement parameter param is not valid.

The CTDUFMDV utility ends with an error.

Corrective Action: Correct the invalid parameter and rerun the utility.

CTDMP5I INPUT PARAMETERS:Link copied to clipboard

Explanation: This information message is issued to the JES log of the job for the CTDUFMDV utility as a header before the following CTDMP6I message or messages.

Corrective Action: No action is required.

CTDMP6I `InputStatement`Link copied to clipboard

Explanation: This information message displays the input parameters that were specified in the SYSIN stream and issued to JES log of the job for the CTDUFMDV utility.

Corrective Action: No action is required.

CTDMP7E INPUT PARAMETER IS INCORRECTLink copied to clipboard

Explanation: The value of parameter that was displayed in the last CTDMP6I message is not valid.

The CTDUFMDV utility ends with an error.

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

CTDMP8E INSUFFICIENT MEMORYLink copied to clipboard

Explanation: There is not enough memory available to run the CTDUFMDV utility.

The utility ends with an error.

Corrective Action: Do one of the following:

If the CTDUFMDV utility was submitted with the PART parameter, increase the REGION size and resubmit the utility.
If the CTDUFMDV utility was submitted with the ACT, HST, or MIG parameters, do one or both of the following:
Decrease the value of the maximum number of VSA records processed by one cycle using the SYSIN stream.
Increase the REGION size and resubmit the utility.

CTDMP9E INVALID RETURN CODE FROM SORT, RC=`rc`Link copied to clipboard

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

The CTDUFMDV utility ends with an error.

Corrective Action: For details about the reason for the failure, refer to the documentation for the sort program and to the job’s sort messages.

CTDMPAE NO $SYSDATA RECORDS FOUND IN THE `fileType` USER FILELink copied to clipboard

Explanation: The fileType User Reports List file does not contain any SYSDATA record.

In this message, fileType is the type of User Reports List file. Valid values are:

The CTDUFMDV utility ends with an error.

Corrective Action: No action is required.

CTDMPEI CTDUFMDV ENDED OK. `fileType` USER FILE IS UPDATED.Link copied to clipboard

Explanation: This information message indicates that the CTDUFMDV utility has successfully updated a User Report List file.

In this message, fileType is the type of User Reports List file. Valid values are:

Corrective Action: No action is required.

CTDMPFI CTDUFMDV ENDED OK. MIG PARTITIONS ARE CREATED OR UPDATED.Link copied to clipboard

Explanation: This information message indicates that the CTDUFMDV utility has successfully separated an old Migrated User Report List file to different partitions or updated a new Migration User Report List in secondary execution.

Corrective Action: No action is required.

CTDMPGW DUPLICATE RECORD IN NEW FILE. KEY=`VSARecordKey`Link copied to clipboard

Explanation: A duplicate record was found in the data file. The duplicate record might be the result of an updating target Migrated User Report List after a previous CTDUFMDV execution.

The CTDUFMDV utility continues processing. The duplicate record that was updated first is removed. The record that was updated later contains more current data, and remains in the data file.

Corrective Action: No action is required.

CTDMPHE MIGRATED USER FILE CANNOT BE SEPARATED REPEATEDLYLink copied to clipboard

Explanation:The CTDUFMDV is submitted for Migrated User Report List which was already separated (CTDUFMDV was submitted with parameter PART for the same MUF).

The CTDUFMDV utility ends with an error.

Corrective Action: If you need to separate the original MUF again, first submit CTDUFMDV with the RESET parameter.

CTDMPII NUMBER OF PROCESSED RECORDS:`XXXXXXXXX`Link copied to clipboard

Explanation: This information message displays the number of processed VSA records from Migrated User Report List.

Corrective Action: No action is required.

CTDMPJE SYSIN IS EMPTYLink copied to clipboard

Explanation:This message indicates that no input statements were specified in the SYSIN stream for the CTDUFMDV utility submitted with MODE=PART or (COPYOLD,DATE) or (COPYNEW,DATE).

The CTDUFMDV utility ends with an error.

Corrective Action: Add the required input statements under DD card SYSIN and rerun the utility.

CTDMR0I CTDUFMPR UTILITY STARTED/RESTARTED WITH `function` FUNCTION IN `mode` MODELink copied to clipboard

Explanation: This information message indicates that the CTDUFMPR utility started or restarted with the function specified in the input parameters (COPY or DELETE) in the specified mode (PROD or TEST).

The first time the utility is submitted for a specified function, the term STARTED is displayed in the message.

If the utility did not end with RC=0 in the previous run and now is starting again with the same function, the term RESTARTED is displayed in the message.

An example where the utility does not end with RC=0 is where the utility does not process all the required records in the previous run because the time limit, specified by the TIMELIM parameter, was exceeded.

Corrective Action: No action is required.

CTDMR1E MIGRATED USER FILE IS NOT DIVIDED TO PARTITIONSLink copied to clipboard

Explanation: This error message is issued when the CTDUFMPR utility did not find the MIGPART record in the file pointed to by the DAMIG DD statement.

The utility stops with RC=8.

Corrective Action: Check whether the DAMIG DD statement points to the correct Migrated User File. Do not submit the CTDUFMPR utility if the Migrated User file is not divided into partitions.

CTDMR3E INVALID EXEC PARAMETER: `parm`Link copied to clipboard

Explanation: The parm input parameter specified in the CTDUFMPR utility JCL EXEC statement is not valid.

The utility stops with RC=12.

Corrective Action: Correct the invalid input parameter (parm) in the JCL and resubmit the job.

CTDMR4E UTILITY WITH FUNCTION COPY IS COMPLETED. SUBMIT IT WITH FUNCTION DELETE.Link copied to clipboard

Explanation: This error message is issued when the user submits the CTDUFMPR utility with the COPY function after the COPY stage has aleady ended with return code 0, but the DELETE stage has not yet been submitted yet.

The utility stops with return code 8.

Corrective Action: Submit the CTDUFMPR utility with the DELETE function to complete the repartition process.

CTDMR5I INPUT SYSIN PARAMETERS:Link copied to clipboard

Explanation: This information message is issued as a header before printing the parameters specified in the SYSIN DD stream. The statements specified in the SYSIN DD stream are printed after this message.

Corrective Action: No action is required.

CTDMR6E INVALID INPUT PARAMETER: `parm`Link copied to clipboard

Explanation: The parm input parameter, specified in the SYSIN DD stream for CTDUFMPR, is not valid.

The utility stops with RC=12.

Corrective Action: Correct the invalid input parameter (parm) in the JCL and resubmit the job.

CTDMR7E INVALID NUMBER OF INPUT PARTITION DATESLink copied to clipboard

Explanation: The number of new partition last dates specified in the SYSIN DD stream for the CTDUFMPR utility is not equal to the number of existing partitions in the Migrated User file.

The utility stops with RC=12.

Corrective Action: Correct the invalid input parameters specified in the SYSIN DD stream and resubmit the job.

CTDMR8I THERE ARE `n` PARTITIONS IN THE MIGRATED USER FILELink copied to clipboard

Explanation: This information message indicates how many partitions exist in the Migrated User File.

Corrective Action: No action is required.

CTDMR9I --- COPY RECORDS TO APPROPRIATE PARTITIONSLink copied to clipboard

Explanation: This information message indicates that the CTDUFMPR utility has started the stage of copying records to other Migrated User File partitions. Records located in partitions that do not match the date ranges of the new partitions will be copied to appropriate partitions.

Corrective Action: No action is required.

CTDMRAI `nnnnnnnn` RECORDS ARE READ FROM PARTITION `x`Link copied to clipboard

Explanation: This information message indicates how many records have been read from partition x of the Migrated User File. Such a message is issued only for partitions which are candidates for moving records from them because their date ranges have been changed by the input parameters.

Corrective Action: No action is required.

CTDMRBI `nnnnnnnn` RECORDS ARE COPIED FROM PARTITION `x` TO PARTITION `y`Link copied to clipboard

Explanation: This information message indicates how many records have been copied from partition x to partition y by the CTDUFMPR utility.

Corrective Action: No action is required.

CTDMRCI --- COPY NEW RECORDS ADDED OR UPDATED DURING UTILITY RUNNINGLink copied to clipboard

Explanation: This information message indicates that the stage of copying the records, which were added or updated while the CTDUFMPR utility was running, has started. The Migrated User File records added or updated in partitions that do not match the date ranges of the new partitions will be copied to appropriate partitions.

Corrective Action: No action is required.

CTDMRDE COPY FUNCTION NOT COMPLETED, MUST COMPLETE COPY BEFORE SUBMITTING WITH DELETE FUNCTIONLink copied to clipboard

Explanation: This error message is issued when the user submits the CTDUFMPR utility with the DELETE function, before the COPY function is submitted and completed.

The utility stops with RC=8.

Corrective Action: Ensure that the CTDUFMPR utility with the COPY function has been submitted and completed, before re-submitting the CTDUFMPR utility with the DELETE function.

No action is required.

CTDMREI `nnnnnnnn` RECORDS ARE DELETED FROM PARTITION `x`Link copied to clipboard

Explanation: This information message indicates how many records have been deleted from partition x by the CTDUFMPR utility.

Corrective Action: No action is required.

CTDMRFW UTILITY STOPPED BECAUSE THE TIME LIMIT `hhmm` WAS EXCEEDEDLink copied to clipboard

Explanation: This warning message indicates that the CTDUFMPR utility ended because the time limit, specified in the input parameter, was exceeded. Not all the records, which were specified to be copied or deleted, were processed.

The utility stops with RC=4.

Corrective Action: Re-submit the utility with the same FUNCTION parameter as before.

CTDMRGI PARTITION `x` LAST DATE: OLD – `date1`, NEW – `date2`Link copied to clipboard

Explanation: This information message indicates the existing (OLD) last report date1 for partition x and the new last report date2 that will take its place for partition x after repartition process is completed. The dates are displayed in YYYYMMDD format. The CTDUFMPR utility issues this message for each existing partition of the Migrated User File.

Corrective Action: No action is required.

CTDMRHI CTDUFMPR UTILITY ENDED OK, RC=`rc`Link copied to clipboard

Explanation: This information message indicates that the CTDUFMPR utility ended without errors. The return code, rc,can be 00 or 04. RC=00 indicates that all the required records of the Migrated User File have been processed and the submitted utility function is completed. RC=04 indicates that the utility stopped because the time limit was exceeded.

Corrective Action: If RC=00, no action is required. If RC=04, re-submit the utility with the same FUNCTION parameter as before.

CTDMRII CTDUFMPR UTILITY ENDED WITH ERRORS, RC=`rc`Link copied to clipboard

Explanation: This information message indicates that the CTDUFMPR utility ended with errors. Additional error messages, describing the errors, precede this message.

Corrective Action: Perform the actions described in the additional error messages.

CTDMRJI --- DELETING RECORDS COPIED TO OTHER PARTITIONSLink copied to clipboard

Explanation: This information message indicates that the CTDUFMPR utility started the step of deleting the records that were copied to the other Migrated User File partitions.

Corrective Action: No action is required.

CTDMRKE MIGRATED USER FILE IS HELD BY CREATE PARTITIONS OR REPARTITION PROCESSLink copied to clipboard

Explanation: This error message is issued by a Control-D application (such as migration mission, CTDDELRP, or CTVCLMIG), which cannot work in parallel with the CTDUFMDV or CTDUFMP utilities when they are updating the Migrated User file partitions. For more information about synchronization of Control-D components with the CTDUFMDV and CTDUFMPR utilities, see the INCONTROL for z/OS Administrator Guide.

The Control-D application stops after issuing this message.

Corrective Action: Re-submit the stopped Control-D application after CTDUFMDV, with function PART, or CTDUFMPR, with function COPY, is completed.

CTDMRLE CTDUFMPR WITH FUNCTION=DELETE IS NOT STARTED SINCE A RESTORE MISSION IS IN PROCESSLink copied to clipboard

Explanation: The CTDUFMPR utility issues this error message, when it is started with the DELETE function while a restore operation from a migrated mission is in process. The DELETE function can only be started after the restore operation has been completed. For more information about synchronization of Control-D components with the CTDUFMPR utilities, see the INCONTROL for z/OS Administrator Guide.

The utility stops with RC=8.

Corrective Action: Re-submit the CTDUFMPR utility with the DELETE function after all restore missions are completed.

CTDMRMW PERFORM ACTIONS DESCRIBED IN ADMINISTRATOR GUIDE BEFORE STARTING CTDUFMPR WITH FUNCTION DELETELink copied to clipboard

Explanation: This warning message is issued at the completion of a run of CTDUFMPR utility with the COPY function. It is intended to remind the user that some additional actions must be performed before starting the CTDUFMPR utility with the DELETE function.

The utility ends with RC=0 after issuing this message.

Corrective Action: Perform the actions described in the INCONTROL for z/OS Administrator Guide and then submit the CTDUFMPR utility with the DELETE function.

CTDMS0I CTDUPMIS UTILITY STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTDUPMIS utility started.

Corrective Action: No action is required.

CTDMS1I CTDUPMIS UTILITY COMPLETED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the CTDUPMIS utility completed successfully.

Corrective Action: No action is required.

CTDMS2E CTDUPMIS UTILITY ENDED WITH ERRORSLink copied to clipboard

Explanation: This error message indicates that the CTDUPMIS utility discovered problems during processing. Additional information on the problems is available in the job log.

The utility stops.

Corrective Action:Examine the job log for error messages describing the problems. Make any necessary corrections and rerun the utility.

CTDMS3E UPDATE PARAMETER `parm` IS NOT AVAILIBLE SINCE SIMILAR SELECTION PARAMETER IS NOT SPECIFIEDLink copied to clipboard

Explanation: The parameter parm is specified in the CHANGE TO statement to be updated, but the similar parameter for selecting values to be updated is not specified.

The utility stops.

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

CTDMS4E INVALID PARAMETER:`parm`Link copied to clipboard

Explanation: The parm input parameter specified in the JCL for the CTDUPMIS utility is not valid.

The utility stops.

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

CTDMS5E THE PARAMETER `parm` MUST BE SPECIFIEDLink copied to clipboard

Explanation: The parm input parameter for the CTDUPMIS utility is required, but it is missing.

The utility stops.

Corrective Action: Add the missing parameter to the JCL and rerun the job.

CTDMS6E REDUNDANT PARAMETER:`parm`Link copied to clipboard

Explanation: The parm input parameter for the CTDUPMIS utility has already been specified.

The utility stops.

Corrective Action:Remove the extra input parameter from the input parameter stream in the JCL and rerun the job.

CTDMS7E NO SELECT STATEMENTS ARE SPECIFIED IN THE INPUT PARAMETER STREAMLink copied to clipboard

Explanation: At least one SELECT statement must be specified in the input parameters stream, but none are specified.

The utility stops.

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

CTDMS8E PARAMETER `parm` LENGTH EXCEEDEDLink copied to clipboard

Explanation: The parm input parameter for the CTDUPMIS utility exceeds the maximum allowable length.

The utility stops.

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

CTDMS9E EMPTY SELECT/CHANGE PARAMETER GROUPLink copied to clipboard

Explanation:There are no parameters specified in either the SELECT or the CHANGE TO statement. At least one parameter must be specified.

The utility stops.

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

CTDMSAI NUMBER OF SELECTED MEMBERS `nm`, CATEGORIES `nc`Link copied to clipboard

Explanation: This information message indicates the number of decollation mission definition members and categories selected during the CTDUPMIS utility run.

Corrective Action:No action is required.

CTDMSBI NUMBER OF UPDATED MEMBERS `nm`, CATEGORIES `nc`Link copied to clipboard

Explanation: This information message indicates the number of decollation mission definition members and categories updated during the CTDUPMIS utility run.

Corrective Action:No action is required.

CTDMSCI parm IS CHANGED FROM `old_value` TO `new_value`Link copied to clipboard

Explanation: This information message indicates that the value of the parm decollation mission parameter is changed from old_value to new_value.

Corrective Action:No action is required.

CTDMSDI parm `old_value` IS DELETEDLink copied to clipboard

Explanation: This information message indicates that the old_value of the parm decollation mission parameter is deleted.

Corrective Action:No action is required.

CTDMSEI parm `new_value` IS ADDEDLink copied to clipboard

Explanation: This information message indicates that the new_value of the parm decollation mission parameter is added.

Corrective Action:No action is required.

CTDMSGW parm `new_value` ALREADY EXISTSLink copied to clipboard

Explanation: This warning message issued by the CTDUPMIS utility when the CHANGE TO statement includes instructions to add a new decollation parameter value to the decollation mission definition, but that parameter value already exists in the selected decollation block.

The new value is not added and the decollation mission definition is not updated.

Corrective Action:Examine the input parameters. Change the parameters and rerun the utility if necessary.

CTDMSHW CLASS `x` IS NOT DELETED. AT LEAST ONE CLASS SHOULD REMAIN.Link copied to clipboard

Explanation: This warning message issued by the CTDUPMIS utility when the CHANGE TO statement includes instructions to delete class x from the ON-CLASS or ON-TRNCLASS decollation mission definition, but x is the only class in this statement. It cannot be deleted because this statement must contain at least one class value.

The x class value is not deleted and the decollation mission definition is not updated.

Corrective Action:Examine the input parameters. Change the parameters and rerun the utility if necessary.

CTDMSII MEMBER `member` CATEGORY `category`Link copied to clipboard

Explanation: This information message is issued before these messages: CTDMSGW, CTDMSHW, CTDMSOE, and CTDMSPE. It indicates which decollation member and category the following message is related to.

Corrective Action:No action is required.

CTDMSKE STORE=CAT CAN BE SPECIFIED ONLY IF OUTLIB DIFFERS FROM REPLIBLink copied to clipboard

Explanation:The STORE=CAT input parameter is specified for the CTDUPMIS utility, but the OUTLIB parameter is not specified. The STORE=CAT parameter can only be specified when the OUTPUT parameter is specified.

The utility stops.

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

CTDMSLE MEMBER NAME CAN BE UPDATED ONLY IF OUTLIB DIFFERS FROM REPLIBLink copied to clipboard

Explanation:The MEMBER parameter is specified in the CHANGE TO statement for the CTDUPMIS utility, but the OUTLIB parameter is not specified or the OUTLIB library is the same as the REPLIB library. The member name can only be changed when the OUTPUT parameter specifies a library different from the input REPLIB library.

The utility stops.

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

CTDMSME CTDUPMIS UTILITY TERMINATES DUE TO AN ERROR IN THE SORTLink copied to clipboard

Explanation:The CTDUPMIS utility issues this message when the invoked SORT utility ended with errors.

The utility stops.

Corrective Action:To identify the problem, examine the messages issued by the SORT utility to SYSOUT. Make the appropriate changes in the JCL and rerun the job.

CTDMSNI MEMBER NAME IS CHANGED FROM `old_member` TO `new_member`Link copied to clipboard

Explanation: This information message indicates that the decollation member is stored in the library specified in the OUTLIB parameter with the name: new_member.

Corrective Action:No action is required.

CTDMSOE CLASS `x` IS INVALID FOR GENERIC DECOLLATION MISSIONLink copied to clipboard

Explanation:The CTDUPMIS utility attempts to change the class value to x or add class x to a generic decollation mission definition, but the class x is not specified in the list of generic classes in the CTDPARM parameters member.

The decollation mission definition is not updated.

Corrective Action:Examine the input parameters. Change the parameters and rerun the utility if necessary.

CTDMSPE CLASS `x` IS DEDICATED FOR GENERIC DECOLLATION MISSIONS ONLYLink copied to clipboard

Explanation:The CTDUPMIS utility attempts to change the class value to x or add class x to a non-generic decollation mission definition, but the class x is specified in the list of generic classes in the CTDPARM parameters member.

The decollation mission definition is not updated.

Corrective Action:Examine the input parameters. Change the parameters and rerun the utility if necessary.

CTDMSRW NO DECOLLATION MISSIONS ARE SELECTEDLink copied to clipboard

Explanation:There are no decollation mission definitions found in the REPLIB library satisfying the selection parameters specified for the CTDUPMIS utility.

The decollation mission definition is not updated.

Corrective Action:Examine the input parameters. Change the parameters and rerun the utility if necessary.

CTDMSSE PARAMETER `parm` IS NOT AVAILIBLE IN ‘CHANGE TO’ STATEMENTLink copied to clipboard

Explanation:The parm parameter is specified in the CHANGE TO statement to be updated, but this parameter is only available as a selection parameter in the SELECT statement.

The utility stops.

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

Messages CTDO00 through CTDOxxLink copied to clipboard

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

CTDO01E OBJECT RECORD `recordKey` HAS NOT BEEN FOUND IN THE REPOSITORY ON THE `req` REQUEST.Link copied to clipboard

Explanation: In the course of the req request (issued either from Control-D program or from DO screen), the recordKey record was not found in the Control-D database and req was not successfully completed. Either recordKey does not exist or there is a consistency violation in the Control-D database.

Corrective Action: Search IOALOG for a message about recordKey deletion or for a message indicating an access error regarding recordKey.

Messages CTDP00 through CTDPxxLink copied to clipboard

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

CTDP01E INVALID DIRECTION PARAMETER SPECIFIED - VALUE SHOULD BE "T", "B", "D", OR "U"Link copied to clipboard

Explanation: An internal error caused an invalid parameter to be sent to the host when the Get-Report-List API was issued.

No report entries are returned by the host.

Corrective Action: Check the IOA Log file and the system log for additional error messages. Report the problem and any additional error messages to BMC Customer Support.

CTDP02E USER=$SYSDATA IS NOT SUPPORTEDLink copied to clipboard

Explanation: $SYSDATA was specified in the USER parameter of the Control-D/WebAccess Server Report List filter. The $SYSDATA user is not supported by Control-D/WebAccess Server in Page On Demand mode.

No reports are retrieved.

Corrective Action: Change the USER parameter in the Report List filter to a valid user name.

CTDP03E ODATE, DECOLLATION DATE, AND RUN DATE MUST ALL BE THE SAMELink copied to clipboard

Explanation: The ODATE, DECOLLATION DATE, and RUN DATE Report List filter fields contain different values. When retrieving reports according to all three date types, the same value must be entered for all three dates in the Report List filter.

No reports are retrieved.

Corrective Action: Correct the date values in the Report List filter or specify only one date type.

CTDP04E DECOLLATION TIME AND RUN TIME MUST BE THE SAMELink copied to clipboard

Explanation: The DECOLLATION TIME and RUN TIME fields of the Report List filter must have the same value. When using both time types to retrieve reports, the same value must be specified for each time field in the Report List filter.

No reports are retrieved.

Corrective Action: Correct the time values in the Report List filter or specify only one time type.

CTDP05E MISMATCH BETWEEN DATES AND TIMES SPECIFIEDLink copied to clipboard

Explanation: The DATE and TIME Report List filter fields are not the same type. When using DATE and TIME to retrieve reports, the DATE and TIME Report List filter fields must be the same type. For example, if retrieving according to Decollation date, only the DECOLLATION TIME field or no time field is valid.

No reports are retrieved.

Corrective Action: Specify a valid combination of DATE and TIME fields in the Report List filter.

CTDP06E INVALID VALUE - SPECIFY `val1, val2`, OR `val3`Link copied to clipboard

Explanation: Due to an internal error, an invalid value was specified in one of the Report List filter fields.

The invalid value was sent to the host in the Get-Report-List API.

No report entries are returned by the host.

Corrective Action: Check the IOA Log file and the system log for additional error messages. Report the problem and any additional error messages to BMC Customer Support.

CTDP07E RECIPIENTS LIST IS OVERFILLED. PLEASE INCREASE ITS SIZELink copied to clipboard

Explanation: The number of recipients that were encountered during the report list requests processing exceeded the estimate given in optional wish WDN004.

The request terminates with an error message.

Corrective Action: Correct the value in the DATA parameter in optional wish WDN004, then stop and restart the IOAGATE monitor.

CTDP08E INVALID SORT FIELD OR DIRECTION SPECIFICATIONLink copied to clipboard

Explanation: There is an invalid value in at least one sort key field or direction specified either in optional Wish WD3368 or in the Control-D/Web Access Report List request.

The Control-D/Web Access Report List request is rejected.

Corrective Action: Examine the values entered in sort key fields and directions, either in optional Wish WD3368 or the Report List request, and correct any invalid values.

CTDP09E ALLOWED SIZE OF SORTED REPORT LIST IS EXCEEDEDLink copied to clipboard

Explanation: The number of reports selected on the Control-D/Web Access Report List request exceeds the limit specified in optional Wish WD3368.

The Control-D/Web Access Report List request is rejected.

Corrective Action: Do one of the following:

Increase the limit specified in optional Wish WD3368.
Narrow the scope of the Report List request.

CTDP0AE INTERNAL ERROR RC=`rc` IN `pgmname`Link copied to clipboard

Explanation: An internal error occurred during the processing of a Control-D/Web Access Report List request.

In this message, rc is the internal error return code and pgmname is the program name, where the error occurred.

The Control-D/Web Access Report List request is rejected.

Corrective Action: Call your INCONTROL administrator.

CTDP10E INTERNAL ERROR - INVALID REQUEST SUB-TYPE RECEIVEDLink copied to clipboard

Explanation: An internal error occurred when the user attempted to view a report in Control-D/WebAccess Server Page On Demand mode.

The report is not made available for viewing.

Corrective Action: Check the IOA Log file and the system log for additional error messages. Report the problem and any additional error messages to BMC Customer Support.

CTDP11E INTERNAL ERROR - STORAGE NOT AVAILABLE FOR `element`Link copied to clipboard

Explanation: The host server has insufficient memory to perform the view report request.

The report is not made available for viewing.

Corrective Action: Increase the REGION size of the server task on the host and restart the server.

CTDP12E INTERNAL ERROR - ILLEGAL USER FILE TYPE SPECIFIED IN OPEN REQUEST - `fileType`Link copied to clipboard

Explanation: An internal error occurred when the user attempted to view a report in Control-D/WebAccess Server Page On Demand mode.

The report is not available for viewing.

Corrective Action: Check the IOA Log and the system log for additional error messages. Report the problem and any additional error messages to BMC Customer Support.

CTDP13E Page `page` longer than maximum output message lengthLink copied to clipboard

Explanation: Page page, which is requested to be viewed by an end user in Control-D/WebAccess, is longer than the IOGATE buffer size. This value is specified in the MAXMSGSZ parameter that is found in the corresponding application server definition in the ECAAPPL member of the IOAENV library.

The report is not made available for viewing.

Corrective Action: If the MAXMSGSZ parameter is set to the maximum allowed value (32723), review the text report page size and change the LINECT parameter so that the page size fits into the MAXMSGSZ specification.

Old reports with a big page size should be redecollated. Because page separators inside of CDAM cannot be changed, these reports should be issued to SPOOL using the CTDAMUTI utility with the RECOVER function and redecollated from SPOOL.

The optional wish WD3595 allows the viewing of incomplete pages instead of receiving the CTDP13E message.

CTDP14E You are not allowed to access report `reportName / jobName / username`Link copied to clipboard

Explanation: The CTDX004 Control-D user exit or the CTDSE04 security module on the host does not allow the current user to view this report entry. For more information, see the VIEWCONF function within the exit.

The report is not available for viewing.

Corrective Action: To authorize a user to view this report, notify your INCONTROL administrator.

CTDP16E INTERNAL ERROR IN CTDTFLL, RC= `rc`Link copied to clipboard

Explanation: An internal error occurred in one of the following cases:

during an attempt to view a report in Control-D/WebAccess Server Page On Demand mode
during an attempt to print a Control-V index report by a PRINT mission from the Control-D PRINT monitor

The error occurred in the CTDTFLL program in the host server during processing of a view report request. The report is not made available for viewing. The following are possible CTDTFLL rc (return code) values:

4--one or more continuation User records not found.
8--user file access error.
12--cannot read SYSDATA record.
16--GETMAIN failed because of insufficient memory.
20--too many GETMAIN calls.
32--FREEMAIN request error.

Corrective Action: Check the IOA Log and the system log for additional error messages. Report the problem and any additional error messages to BMC Customer Support.

CTDP17E INTERNAL ERROR IN IOABOX, FUNCTION - `function`, RC=`rc`, FEEDBACK=`feedbackCode`Link copied to clipboard

Explanation: An internal error occurred during an attempt to view a report in Control-D/WebAccess Server Page On Demand mode in the IOABOX program in the host server. The report is not available for viewing. The following are possible IOABOX rc (return code) values:

8--block point error
12--block get error
20--CDAM file allocation error
28--CDAM subsystem not operational
32--encoding error
36--unrecognized cache routine name
56--invalid media specified for report

When rc=8 or rc=12, there is a feedbackCode from the CDAM system.

Corrective Action: Check the IOA Log and the system log for additional error messages. Report the problem and any additional error messages to BMC Customer Support.

CTDP18E INTERNAL ERROR - ILLEGAL REPORT HANDLE SUPPLIED IN REQUESTLink copied to clipboard

Explanation: An internal error occurred during an attempt to view a report in Control-D/WebAccess Server Page On Demand mode.

The report is not available for viewing.

Corrective Action: Check the IOA Log and the system log for additional error messages. Report the problem and any additional error messages to BMC Customer Support.

CTDP19E INTERNAL ERROR - UNABLE TO FREE STORAGE OF `element`, RC=`rc`Link copied to clipboard

Explanation: An internal error occurred when the user attempted to exit from viewing a report in Control-D/WebAccess Server Page On Demand mode.

The host server cannot close the viewed report. Other problems may occur due to this error.

Corrective Action: Check the IOA Log and the system log for additional error messages. Report the problem, the return code in this message, and any additional error messages to BMC Customer Support.

CTDP1AE INTERNAL ERROR - ILLEGAL PAGE NUMBER REQUESTEDLink copied to clipboard

Explanation: An internal error occurred when the user attempted to view a report in Control-D/WebAccess Server Page On Demand mode.

The report is not made available for viewing.

Corrective Action: Check the IOA Log and the system log for additional error messages. Report the problem and any additional error messages to BMC Customer Support.

CTDP1BE INTERNAL ERROR IN CTVINXR, FUNCTION = `func`, RC=`rc`Link copied to clipboard

Explanation: An internal error occurred in the CTVINXR program during an attempt to view a report in Control-D/WebAccess Server Page On Demand mode. The Report List filter included index name or index value (or both) selection criteria to retrieve only report sections corresponding to the index criteria.

The report is not made available for viewing.

Corrective Action: Check the IOA Log and the system log for additional error messages. Report the problem and any additional error messages to BMC Customer Support.

CTDP1CE REPORT ENTRY DOES NOT EXISTLink copied to clipboard

Explanation: The report entry requested for viewing does not exist in the host database. It was probably deleted from the host database after the report list was retrieved and before the report view request was issued.

The report is not made available for viewing.

Corrective Action: Use the Refresh option to produce an updated report list that does not contain deleted report entries.

CTDP1DE INDEX ENTRY DOES NOT EXISTLink copied to clipboard

Explanation: An attempted to view a report based on an index value specified in the Hit List filter failed, because the specified value does not exist in the current index for the report.

The report is not viewed.

Corrective Action: In the Filter window, select reports without the Index Value parameter, and then use the Viewing With Indexes option to select the required index value in order to view the report.

CTDP1EE NON-UNIQUE INDEX OR VALUELink copied to clipboard

Explanation: An attempt to view a report based on an index value specified in the Hit List filter failed, because the specified index name and index value prefix are not unique for the report. More than one index satisfies the specified index mask, or more than one value satisfies the specified value prefix entered in the Hit List filter.

The report is not viewed.

CTDP1FI REPORT `reportName / jobName / JOBID / userName /category` VIEWED FROM ACTIVE | MIGRATED FILE [LT=hhmm]Link copied to clipboard

Explanation: This information message is generated when the specified report is viewed by means of Page On Demand from the active or migrated file. The text of the message specifies the report name, job name, JobID, user name, category, and file type.

Corrective Action: No action is required.

CTDP1GI INDEX NAME: `index_name`Link copied to clipboard

Explanation: This information message provides the index name for the accompanying message.

Corrective Action: Examine the accompanying message and its user response, and take the appropriate corrective action.

CTDP1HI INDEX VALUE: `index_value`Link copied to clipboard

Explanation: This information message provides the index value for the accompanying message.

Corrective Action: Examine the accompanying message and its user response, and take the appropriate corrective action.

CTDP1LI REPORT `reportName / jobName / JOBID / userName /category` SAVED FROM ACTIVE | MIGRATED FILE [LT=hhmm]Link copied to clipboard

Explanation: This information message is generated when the specified report is saved by means of Page On Demand from the active or migrated file. The text of the message specifies the report name, job name, JobID, user name, category, and file type.

Corrective Action: No action is required.

CTDP1MI REPORT `reportName / jobName / JOBID / userName /category` EMAILED FROM ACTIVE | MIGRATED FILE [LT=hhmm]Link copied to clipboard

Explanation: This information message is generated when the specified report is emailed by means of Page On Demand from the active or migrated file. The text of the message specifies the report name, job name, JobID, user name, category, and file type.

Corrective Action: No action is required.

CTDP1NI REPORT `reportName / jobName / JOBID / userName /category` PRINTED FROM ACTIVE | MIGRATED FILE [LT=hhmm]Link copied to clipboard

Explanation: This information message is generated when the specified report is printed by means of Page On Demand from the active or migrated file. The text of the message specifies the report name, job name, JobID, user name, category, and file type.

Corrective Action: No action is required.

CTDP20E You are not authorized to use this optionLink copied to clipboard

Explanation: There is no authorization to perform this action under Page On Demand. This message is generated by the CTDX04 Control-D user exit or the CTDSE24 security module.

The requested function is not performed.

Corrective Action: If the user should be authorized to perform this function, call your INCONTROL administrator.

CTDP21I Report `reportName / jobName / username` will be retrieved in batchLink copied to clipboard

Explanation: Some or all of the CDAM files of the report to be viewed or printed have migrated, and are not immediately available. At sites using DF/HSM with Control-D option WD2889 applied, a request for online viewing or immediate printing of a report causes the CTDTUSR program to check if the CDAM files of the report were migrated.

A batch job is submitted to recall these migrated CDAM files for later access.

Corrective Action: Wait until this batch job completed successfully. Then, try again to view the report.

CTDP22E INTERNAL ERROR - ILLEGAL INDEX HANDLE SUPPLIED IN REQUESTLink copied to clipboard

Explanation: An internal error occurred during an attempt to access an index in Control-D/WebAccess Server in Page On Demand mode. An invalid index token was received from the client.

The index is not accessed.

Corrective Action: Check the IOA Log and the system log for additional error messages. Report the problem and any additional error messages to BMC Customer Support.

CTDP23E ERROR - SECTION NUMBER REQUESTED IS NOT IN SEQUENCELink copied to clipboard

Explanation: An internal error occurred in the Page On Demand facility.

The requested report is not displayed.

Corrective Action: Notify your INCONTROL administrator, and do the following:

Activate debug levels 10, 11, 17, 18 and 19 in the Control-D Application Server.
Duplicate the operation that caused the error to occur.
Print the output from the DADUMP and DATRACE debug data sets.
Send the printed output to BMC Customer Support.

CTDP24E ERROR ACCESSING CDAM FILE, CTDPRSC FUNCTION=`func`, RC=`rc`Link copied to clipboard

Explanation: An internal error occurred while attempting to access a CDAM file. The CDAM file being accessed was created by a printing mission using the STORE parameter set to YES.

The report is not displayed.

Corrective Action: Notify your INCONTROL administrator and do the following:

Activate debug levels 10, 11, 17, 18 and 19 in the Control-D Application Server.
Duplicate the operation that caused the error to occur.
Print the output from the DADUMP and DATRACE debug data sets.
Send the printed output along with the message text and return code to BMC Customer Support.
Look for additional error messages in the IOALOG and the job log.

CTDP25E DYNAMIC ALLOCATION OF `fileName` FILE FAILED, RC=`rc`, REASON CODE=`rsn`Link copied to clipboard

Explanation: An internal error occurred during dynamic allocation of temporary file, while Control-D was retrieving a PDF or CCIF report using the Page On Demand interface.

The report is not displayed.

Corrective Action: Notify your INCONTROL administrator. Look for additional error messages in the job log generated in response to the problem. If the problem cannot be resolved, send a copy of the CTDPARM member and the error messages in the job log to BMC Customer Support.

CTDP26E You are not authorized to cancel restore request for report `reportName / jobName / username`Link copied to clipboard

Explanation: The user is not authorized to cancel restore request for the selected report.

The un-restore request is rejected by the security exit. The un-restore operation is not performed.

Corrective Action: To get access to this action, notify your INCONTROL administrator.

The variables in this message are:

reportName - the name of the report
jobName - the name of the job that created the report
username - the user for whom the report was created

CTDP27E DYNAMIC DEALLOCATION OF `fileName` FILE FAILED, RC=`rc`, REASON CODE=`rsn`Link copied to clipboard

Explanation: An internal error occurred during dynamic deallocation of temporary file, while Control-D was retrieving a PDF or CCIF report by means of the Page On Demand interface.

The report is not displayed.

CTDP28E ERROR CREATING `fileName` FILE FOR VIEWING, RC=`rc`Link copied to clipboard

Explanation: Control-D detected an internal error when the indexed section of a PDF or CCIF report was requested for viewing.

The report is not displayed.

Corrective Action: Notify your INCONTROL administrator and do the following:

Activate debug levels, 11, 17, 18 and 19 in the Control-D Application Server.
Duplicate the operation that caused the error to occur.
Look for additional error messages in the IOALOG, job log and SYSOUT data sets.
View the complete PDF or CCIF without Control-V indexes, to bypass the cause of the problem.

If you cannot solve the problem, record this error message, all other associated error messages, the results of viewing the PDF or CCIF without indexes, and the output of the DADUMP and DATRACE debug data sets. Contact BMC Customer Support.

CTDP29E ERROR OPENING `fileName` FILE, RC=`rc`Link copied to clipboard

Explanation: Control-D detected an internal error while preparing an indexed section of a subset PDF or CCIF file for viewing. Control-D generated the return code, which is reserved for internal use.

The report is not displayed.

Corrective Action: Notify your INCONTROL administrator and do the following:

Activate debug levels, 11, 17, 18 and 19 in the Control-D Application Server.
Duplicate the operation that caused the error.
Look for additional error messages in the IOALOG, job log, and SYSOUT data sets.
View the complete PDF or CCIF without Control-V indexes to bypass the cause of the problem.

If you cannot solve the problem, record all associated error messages, the results of viewing the PDF or CCIF without indexes, and the output of the DADUMP and DATRACE debug data sets. Contact BMC Customer Support.

CTDP2AE INTERNAL ERROR - REPORT TYPE REQUESTED IS NOT CORRECTLink copied to clipboard

Explanation: An internal error occurred in the Page On Demand facility.

The requested report is not displayed.

Corrective Action: Notify your INCONTROL administrator and do the following:

Activate debug levels 10, 11, 17, 18 and 19 in the Control-D Application Server.
Duplicate the operation that caused the error to occur.
Print the output of the DADUMP and DATRACE debug data sets.
Send the printed output to BMC Customer Support.

CTDP2BE AN IMAGE CAN BE VIEWED ONLY VIA AN INDEX VALUELink copied to clipboard

Explanation: The user tried to view an image report without specifying an index value. In order to view an image report, an index value must be specified.

The report is not displayed.

Corrective Action: Specify an index and an index value for the report.

CTDP2CE You are not authorized to restore report `reportName / jobName / username`Link copied to clipboard

Explanation: The user is not authorized to restore the selected report.

The restore request is rejected by the security exit. The report is not restored.

Corrective Action: To get access to this action, notify your INCONTROL administrator.

CTDP2DI Report `reportName / jobName / username` will be restored from long-term archiveLink copied to clipboard

Explanation: This information message indicates that the requested report is being restored from a long-term archive. The restoration process is underway. It may take some time.

The report will be restored.

Corrective Action: No action is required.

CTDP2EI Report `reportName / jobName / username` is already waiting for restoreLink copied to clipboard

Explanation: The report requested for restore is already waiting for restore based on a previous request. The previous restore request for the same report, perhaps from another user, is being processed. The current request is unnecessary.

The report will be restored.

Corrective Action: No action is required.

CTDP2FE INTERNAL ERROR. RC=`rc` REASON CODE=`rsn`Link copied to clipboard

Explanation: The IOATAE program encountered an internal error during report translation from ASCII to EBCDIC.

The request could not be performed.

Corrective Action: Have your INCONTROL administrator notify BMC Customer Support.

CTDP2GE Error during processing restore request for report `reportName / jobName / username`Link copied to clipboard

Explanation: This error message indicates that an error occurred during report restore processing. Details of the error can be found in other messages that accompany this message.

The restore request is not performed.

Corrective Action: Check the log for additional messages concerning the restore failure.

CTDP2HE ERROR FROM CTDPRPS RC= `rc`Link copied to clipboard

Explanation: An internal error occurred in the CTDPRPS program during a check on the requested report.

Possible error causes are:

rc	Explanation
4	End of report is exceeded
8	Storage request failed
12	Invalid function accessing the CTDPRPSP program
16	Supplied buffer is too small to create line
20	Invalid report was processed
28	Error retrieving a resource for a normalized report

The request is not performed.

Corrective Action: Check the IOA Log file for additional messages associated with the error and try to correct the problem. If the error persists, collect all related information and contact BMC Customer Support.

CTDP2IE PROGRAM `pgm` FAILED. RC=`rc`Link copied to clipboard

Explanation: An internal error occurred in the pgm program during report transformation.

The request is not performed

Corrective Action: Have your INCONTROL administrator notify BMC Customer Support.

CTDP2JE ERROR OPENING `fileName` FILELink copied to clipboard

Explanation: An error occurred while opening a temporary file for the report transformation process.

In this message, fileName is the name of the file that could not be opened.

The request is not performed.

Corrective Action: Notify your INCONTROL administrator or responsible system programmer.

CTDP2KE PUT TO `fileName` FILE FAILED, RC=`rc`Link copied to clipboard

Explanation: An internal I/O error occurred while attempting to write to file fileName during the transformation process of a report.

The request is not performed.

Corrective Action: Have your INCONTROL administrator notify BMC Customer Support.

CTDP2LE ERROR IN ATTACH OF `pgm` ,RC=`rc`Link copied to clipboard

Explanation: An internal error was encountered while attempting to attach the pgm transformation program.

In this message, rc is a macro ATTACH return code.

The request is not performed.

Corrective Action: Have your INCONTROL administrator notify BMC Customer Support.

CTDP2ME Program `pgm` not found in load library, Rc=`rc`Link copied to clipboard

Explanation: The pgm transformation program was not found in the load library.

rc is a macro BLDL return code, and is described in IBM documentation.

The request is not performed.

Corrective Action: Analyze the return code and correct the problem accordingly. If the problem persists or you cannot correct it, have your INCONTROL administrator notify BMC Customer Support.

CTDP2NE Report `reportName / jobName / username` is too big, you are not allowed to view itLink copied to clipboard

Explanation: An attempt has been made to view a report which exceeds the limit defined in optional wish WD3353.

Corrective Action: If you think that you should be authorized to perform this action, contact your INCONTROL administrator.

CTDP2OE DJDEPARM support is not availableLink copied to clipboard

Explanation: APPLY was set in optional Wish WD3408 to YES, but the level of CTDDJE was less than that required for this setting to operate.

The requested function is not performed.

Corrective Action: Enter ICE and recompile the appropriate version of CTDDJE, which is in the SAMPEXIT library.

CTDP2PI `jobname/recipient/report` ID=`recordId` SET TO RESTORE WITH MISSION `misName`Link copied to clipboard

Explanation: This information message indicates that the 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

Corrective Action: No action is required.

CTDP2RE Report `reportName / jobName / username` should be in "WAIT-RESTORE" stateLink copied to clipboard

Explanation: You cannot un-restore a record that is not scheduled to be restored. Only records in the WAIT-RESTORE state can be un-restored.

The un-restore operation is not performed.

The variables in this message are:

reportName - the name of the report
jobName - the name of the job that created the report
username - the user for whom the report was created

Corrective Action: No action is required.

CTDP2SI Restore request canceled for report: `jobName / username / reportName` ID=`recordId`Link copied to clipboard

Explanation: This information message indicates that the restore request to the backed up (migrated) report is canceled.

The variables in this message are:

reportName - the name of the report
jobName - the name of the job that created the report
username - the user for whom the report was created
recordId - the internal database identifier of the report

Corrective Action: No action is required.

CTDP2TI Restore request canceled for report: `reportName / jobName / username`Link copied to clipboard

Explanation: This information message indicates that the restore request to the backed up (migrated) report is canceled.

The variables in this message are:

reportName - the name of the report
jobName - the name of the job that created the report
username - the user for whom the report was created

Corrective Action: No action is required.

CTDP2UE Error during processing cancel restore request for report `reportName / jobName / username`Link copied to clipboard

Explanation: An error occurred during cancellation of report-restore processing. The unrestore operation is not performed.

Corrective Action: For details of this error, check the log for related messages.

CTDP2WE PASSWORD IS NOT DEFINED FOR THIS PDF REPORT. ACCESS DENIED.Link copied to clipboard

Explanation: This error message is issued when a user tries to open a PDF report. This report should be protected by a password, but no password has been defined by the administrator.

The request fails.

Corrective Action: Contact the IOA administrator.

CTDP2XE PASSWORD IS NOT DEFINED. ACCESS DENIED FOR PDF REPORT `report_name`Link copied to clipboard

Explanation: This error message in IOA LOG indicates that the end user has tried to open a PDF report. This report is set as protected using the %%$PDFPASS=Y option in the SET statement of the corresponding decollation mission, but the password is not defined by the administrator in the User Permanent file. The message is followed by message CTDP2YI or CTDP2ZI, which provides additional report parameters.

The request fails

Corrective Action: The administrator needs to define the password for this report using the CTVUPINV utility. See the CTDP2YI or CTDP2ZI messages for the report parameters.

For details, see Protecting access to PDF reports in the INCONTROL for z/OS Administrator Guide.

CTDP2YI JOBNAME `job_name` RECIPIENT `recipient_name` CATEGORY `category`Link copied to clipboard

Explanation:This information message in IOA LOG follows the CTDP2XE message to provide additional report parameters.

Corrective Action: No action is required.

CTDP2ZI JOBNAME `job_name` RECIPIENT `recipient_name` CATEGORY `category` INDEX `index_value`Link copied to clipboard

Explanation: This information message in IOA LOG follows the CTDP2XE message to provide additional report parameters.

Corrective Action: No action is required.

CTDP30E INTERNAL ERROR - ILLEGAL NOTES HANDLE SUPPLIED IN REQUESTLink copied to clipboard

Explanation: An internal error occurred during an attempt to access notes in Control-D/WebAccess Server in Page On Demand mode. An invalid note token was received from the client.

The notes are not accessed.

Corrective Action: Check the IOA Log and the system log for additional error messages. Report the problem and additional error messages to BMC Customer Support.

CTDP31E INTERNAL ERROR - CONTINUATION REQUEST WITHOUT AN INITIAL REQUEST FOR INDEX OF NOTESLink copied to clipboard

Explanation: An internal error occurred during an attempt to access notes in Control-D/WebAccess Server in Page On Demand mode. Only the continuation of a request was received. The initial request may have been lost due to a transmission error.

The notes are not accessed.

Corrective Action: Check the IOA Log and the system log for additional error messages. Report the problem and any additional error messages to BMC Customer Support.

CTDP32W NOTES ARE NOT SUPPORTED FOR THIS REPORT IN PAGE ON DEMAND MODELink copied to clipboard

Explanation: Notes are accessible in Page On Demand mode only for reports decollated under IOA Release 5.0.4 and above. The notes of reports decollated by a previous version of Control-D are not accessible in Page On Demand mode.

The requested action is not performed.

Corrective Action: Create or access the note by means of the Control-D Notepad facility.

CTDP33E INTERNAL ERROR IN CTDNPS - FUNCTION "`func` " RC=`rc`Link copied to clipboard

Explanation: The Control-D Application Server received a non-zero return code from the CTDNPS routine.

Notes cannot be accessed.

Corrective Action: Report this error message and any other relevant messages to BMC Customer Support.

CTDP34E INTERNAL ERROR - CANNOT TRANSLATE PAGE NUMBER OF NOTELink copied to clipboard

Explanation: An internal error occurred during an attempt to access a tag note for a report being viewed. A tag note cannot be accessed because the page number of the associated string is unknown.

The note is not accessed.

Corrective Action: Report this problem and any relevant error messages from the IOA Log and the Control-D Application Server to BMC Customer Support.

CTDP35E NOTE DATA IS TOO LONG - LIMITED TO 560 PER VERSIONLink copied to clipboard

Explanation: The note being created contains too many characters. Each note version is limited to 560 characters.

The note version is not created.

Corrective Action: Make the note shorter.

CTDP36E INTERNAL ERROR - REPORT NOTE DOES NOT EXIST - CANNOT ADD NEW VERSIONLink copied to clipboard

Explanation: An internal error occurred when trying to create a tag note for a report being viewed. A tag note cannot be created because of an internal error.

The note is not created.

Corrective Action: Report this problem and any relevant error messages from the IOA Log and the Control-D Application Server to BMC Customer Support.

CTDP37E CANNOT ADD VERSION - MAXIMUM NUMBER OF VERSIONS REACHEDLink copied to clipboard

Explanation: The user tried to add a new version of a note, but the maximum number of note versions already exists.

The new version is not added.

Corrective Action: Modify an existing note version or delete and replace the last version of the note.

CTDP38E INTERNAL ERROR - CANNOT CREATE REPORT NOTE - ALREADY EXISTSLink copied to clipboard

Explanation: The attempt to create a General note for a report failed due to an internal error.

The note is not created.

Corrective Action: Report this problem and any relevant error messages from the IOA Log and the Control-D Application Server to BMC Customer Support.

CTDP39E ERROR IN INPUT MESSAGE LENGTH - MESSAGE IS TOO SHORT - REQUEST TYPE = `type`Link copied to clipboard

Explanation: An internal communication error occurred between Control-D/WebAccess Server and the Control-D Application Server.

The message is ignored.

Corrective Action: Report this problem and any relevant error messages from the IOA Log and the Control-D Application Server to BMC Customer Support.

CTDP3AE INTERNAL ERROR - CANNOT DELETE REPORT NOTE - DOES NOT EXISTLink copied to clipboard

Explanation: The user attempted to delete a note attached to a report, but the note does not exist.

The note is not deleted.

Corrective Action: Report the entry for which you received this message and any relevant messages in the IOA Log and Control-D Application Server to BMC Customer Support.

CTDP3BE INTERNAL ERROR FREEING STORAGE - RC=`rc`Link copied to clipboard

Explanation: An internal error occurred when the user attempted to exit from the Note window in Control-D/WebAccess Server in Page On Demand mode.

The server on the host cannot free the associated note structure of the notes accessed. Other problems may occur because of this error.

Corrective Action: Check the IOA Log and the system log for additional error messages. Report the problem and additional error messages to BMC Customer Support.

CTDP3CE REPORT ENTRY DELETED - CANNOT ACCESS NOTESLink copied to clipboard

Explanation: The report entry corresponding to the notes being processed does not exist. It was probably deleted by another user or by the CTDDELRP utility.

The note is not saved or updated.

Corrective Action: Refresh the User Report list to get a current list of existing report entries.

CTDP3DE INTERNAL ERROR - INVALID REQUEST SUB-TYPE - MUST BE BETWEEN 1 AND `n`Link copied to clipboard

Explanation: An internal error occurred during an attempt to access a note of a report in Control-D/WebAccess Server in Page On Demand mode. An invalid request type was received from the client.

The note is not accessed.

Corrective Action: Check the IOA Log and the system log for additional error messages. Report the problem and any additional error messages to BMC Customer Support.

CTDP3EE INTERNAL ERROR - INVALID NOTE TOKEN SUPPLIED IN REQUESTLink copied to clipboard

Explanation: An internal error occurred during an attempt to access a note of a report in Control-D/WebAccess Server in Page On Demand mode. An invalid note handle was received from the client.

The note cannot be accessed.

Corrective Action: Check the IOA Log and the system log for additional error messages. Report the problem and any additional error messages to BMC Customer Support.

CTDP3FE ACTION NOT DONE - NOTE IS CURRENTLY IN USE - TRY AGAIN LATERLink copied to clipboard

Explanation: There was an attempt to delete an existing note or create a new version of a note that is currently accessed by another user. A note that is currently in use by one user can only be browsed by other users.

The requested action is not performed.

Corrective Action: No action is required.

CTDP3GE INTERNAL ERROR - PAGE NOT FOUND IN PAGE TABLE - CANNOT CREATE NOTELink copied to clipboard

Explanation: An internal error occurred when trying to create a tag note for a report being viewed. A tag note cannot be created because the page number of the associated string is unknown.

The note is not created.

Corrective Action: Exit from Page On Demand mode and try to create the note again. If you do not succeed, report this problem and any relevant messages from the IOA Log and the Control-D Application Server to BMC Customer Support.

CTDP3HS INSUFFICIENT STORAGE - INCREASE REGION SIZELink copied to clipboard

Explanation: There is insufficient memory in the host server to perform the notes access request.

The notes are not accessed.

Corrective Action: Increase the REGION size of the server task on the host, and restart the server.

CTDP3IE CANNOT CREATE NOTE - THIS NOTE ALREADY EXISTSLink copied to clipboard

Explanation: You cannot create a tag note for a string that is already associated with a tag note.

The note is not created.

Corrective Action: Tag the note to a different string or create a new version of the existing note.

CTDP3JE YOU ARE NOT AUTHORIZED TO USE THIS OPTIONLink copied to clipboard

Explanation: You are not authorized to view, create or delete a note under Page On Demand. This message is generated by the CTDX024 Control-D user exit or the CTDSE24 security module for the ‘shownote,’ ‘delnote,’ or ‘addnote’ function.

The requested function is not performed.

Corrective Action: If the user should be authorized to perform this function, contact your INCONTROL administrator.

CTDP3KE YOU ARE NOT AUTHORIZED TO ACCESS NOTESLink copied to clipboard

Explanation: You are not authorized to access notes under Page On Demand. This message is generated by the CTDX024 Control-D user exit or the CTDSE24 security module for the ‘viewnote’ function.

The notes are not retrieved.

Corrective Action: If the user should be authorized to perform this function, contact your INCONTROL administrator.

CTDP3LE YOU ARE NOT AUTHORIZED TO CREATE/EDIT/DELETE NOTESLink copied to clipboard

Explanation: You are not authorized to write or delete notes under Page On Demand. This message is generated by the CTDX024 Control-D user exit or the CTDSE24 security module for the ‘editnote’ function.

The note is not created or deleted.

Corrective Action: If the user should be authorized to perform this function, contact your INCONTROL administrator.

CTDP3MI Note created by user user_name in report report_nameLink copied to clipboard

Explanation: This information message notifies you that a note was created in the report through Control-D/WebAccess Server.

Corrective Action: No action is required.

CTDP3NI Note deleted by user user_name from report report_nameLink copied to clipboard

Explanation: This information message notifies you that a note was deleted in the report through Control-D/WebAccess Server.

Corrective Action: No action is required.

CTDP3OI Note version added by user user_name to report report_nameLink copied to clipboard

Explanation: This information message notifies you that a new note version was added in the report through Control-D/WebAccess Server.

Corrective Action: No action is required.

CTDP40E UNABLE TO ACCESS INDEXES - RC = `rc`Link copied to clipboard

Explanation: An internal error occurred when accessing the Index facility of Control-D/WebAccess Server Page On Demand or Control-D PRINT monitor.

The requested action is not performed.

Corrective Action: Report this problem and any relevant error messages from the IOA Log and the Control-D Application Server to BMC Customer Support.

CTDP41E NOT ENOUGH SPACE FOR INDEXES - SOME INDEXES ARE MISSINGLink copied to clipboard

Explanation: There are too many index paths for this report. Some index paths cannot be accessed by means of Page On Demand.

Only the displayed index paths are accessible by means of Page On Demand.

Corrective Action: You can access the rest of the index paths by means of the Control-D Index facility.

CTDP42E INTERNAL ERROR - INVALID REQUEST SUB-TYPE - MUST BE BETWEEN 1 AND `n`Link copied to clipboard

Explanation: An internal error occurred when the user attempted to access an Index facility of Control-D/WebAccess Server Page On Demand.

The function is not performed.

Corrective Action: Check the IOA Log and the system log for additional error messages. Report the problem and any additional error messages to BMC Customer Support.

CTDP43E INTERNAL ERROR FREEING STORAGE - RC = `rc`Link copied to clipboard

Explanation: An internal error occurred when the user attempted to exit from the Index facility of Control-D/WebAccess Server Page On Demand.

The server on the host cannot close the index used. Other problems may occur because of this error.

Corrective Action: Check the IOA Log and the system log for additional error messages. Report the problem and any additional error messages to BMC Customer Support.

CTDP44S INSUFFICIENT STORAGE - INCREASE REGION SIZELink copied to clipboard

Explanation: Insufficient memory in the host server to perform the index request.

The indexes cannot be accessed.

Corrective Action: Increase the REGION size of the server task on the host, and restart the server.

CTDP45E REPORT ENTRY DELETED - CANNOT ACCESS INDEXESLink copied to clipboard

Explanation: The report entry corresponding to the index being processed does not exist. The report entry was probably deleted by another user or by the CTDDELRP utility.

The report is not displayed.

Corrective Action: Refresh the User Report list to get a current list of existing report entries.

CTDP46S ERROR IN INPUT MESSAGE LENGTH - MESSAGE IS TOO SHORTLink copied to clipboard

Explanation: An internal communication error occurred between Control-D/WebAccess Server and the Control-D Application Server.

The requested action is not performed.

Corrective Action: Report this problem and any relevant error messages from the IOA Log and the Control-D Application Server to BMC Customer Support.

CTDP47S ERROR IN INPUT MESSAGE - INDEX PATH IS INCORRECTLink copied to clipboard

Explanation: Internal error in communication between Control-D/WebAccess Server and the Control-D Application Server.

The report section is not retrieved.

Corrective Action: Report this problem and any relevant error messages from the IOA Log and the Control-D Application Server to BMC Customer Support.

CTDP48S INTERNAL ERROR - LOAD OF MODULE `modName` FAILEDLink copied to clipboard

Explanation: The Control-D Application Server failed to load the modName module.

The requested function is not performed. Other problems may follow.

Corrective Action: Consult your INCONTROL administrator. If necessary, report this problem to BMC Customer Support.

CTDP49S INTERNAL ERROR - MISMATCH BETWEEN INDEX RECORD AND USER RECORDLink copied to clipboard

Explanation: Internal error in the Control-D Application Server or Control-D PRINT monitor.

The requested action is not performed.

Corrective Action: Report this problem, the report entry for which it occurred, and any relevant error messages from the IOA Log and the Control-D Application Server to BMC Customer Support.

CTDP4AS INTERNAL ERROR IN INPUT PARAMETERSLink copied to clipboard

Explanation: An internal error occurred when accessing the Index facility of Control-D/WebAccess Server Page On Demand.

The requested action is not performed.

Corrective Action: Record this problem and any relevant error messages from the IOA Log and the Control-D Application Server to BMC Customer Support.

CTDP4BS INTERNAL ERROR - CANNOT LOCATE THE PREVIOUS VALUE FROM WHICH TO STARTLink copied to clipboard

Explanation: An internal error occurred when accessing the Index facility of Control-D/WebAccess Server Page On Demand.

The requested action is not performed.

Corrective Action: Record this problem and any relevant error messages from the IOA Log and the Control-D Application Server to BMC Customer Support.

CTDP4CE CANNOT VIEW REPORT SECTION - INDEX PATH VALUES ARE NOT UNIQUELink copied to clipboard

Explanation: The index values in the selected path are not unique. The report cannot be viewed.

The report section is not viewed.

Corrective Action: Choose index values from the List of Index Values, and then attempt to View the report.

CTDP50I REPORT PRINTED FROM `fileName` FILE: `jobName / userName / reportName`Link copied to clipboard

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.

CTDP51E CTDDPR/CTDCNV/CTDUF MODULE NOT LOADED, RC=`rc`Link copied to clipboard

Explanation: The CTDDPR, CTDCNV, or CTDUF module cannot be loaded.

In this message, rc is a macro LOAD return code, and is described in IBM documentation.

The request is not performed.

Corrective Action: Analyze the return code and fix the problem.

CTDP52E ERROR IN CTDDPR: INVALID DESTINATIONLink copied to clipboard

Explanation: An invalid destination was detected in the CTDDPR program for the report that was requested for printing. The sysout can not be allocated with this destination.

The print request is not performed.

Corrective Action: Correct the destination, and perform the print request again.

CTDP53E SYSOUT ALLOCATION FAILED, RC=`rc`, ERROR=`rsn`Link copied to clipboard

Explanation: An error was encountered when the CTDDPR program tried to allocate a sysout.

In this message, rc and rsn are dynamic allocation return and reason codes, respectively. They are described in IBM documentation.

The request is not performed.

Corrective Action: Analyze the reason code, fix the problem, and issue the request again.

CTDP54E INCORRECT CONTINUATION RECORDLink copied to clipboard

Explanation: An incorrect continuation record was encountered when opening a requested report. This indicates that the Control-D database contains corrupted records, because of an internal error. The request is not performed.

Corrective Action: Check the IOA Log file and the system log for additional error messages. Report the problem and any additional error messages to BMC Customer Support.

CTDP55E ERROR IN CTDDPR: USER FILE ACCESS ERRORLink copied to clipboard

Explanation: An internal error was encountered during access of a User Active Report file.

The request fails.

Corrective Action: Have your INCONTROL administrator notify BMC Customer Support.

CTDP56E ERROR IN CTDDPR: CDAM ERRORLink copied to clipboard

Explanation: An I/O error was encountered during processing of an Immediate Print request from Control-D/Web Access. 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 request fails.

Corrective Action: Use the following suggestions to resolve the issue:

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

CTDP57E ERROR IN CTDDPR: INSUFFICIENT STORAGELink copied to clipboard

Explanation: There was insufficient storage to handle an immediate printing request

The print request fails.

Corrective Action: Increase the REGION parameter value for the Application Server.

CTDP58E INTERNAL ERROR - IN CTDDPR - RC=`rc`Link copied to clipboard

Explanation: An internal error occurred during processing of the immediate print request from Control-D/Web Access.

The following table lists and explains the possible values for the return code (rc):

rc	Explanation
28	An internal error occurred while processing an Immediate Print request.
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 print request is not performed.

Corrective Action: Use the following procedure to correct the error.

Check the IOA Log file and job log for additional messages associated with the error.
Correct the problem based on information found in the messages
Re-submit the print request.
If the error persists, contact BMC Customer Support.

CTDP59E MiSSING OUTPUT STATEMENT `stmt`Link copied to clipboard

Explanation: The stmt required OUTPUT statement is missing from the Application Server procedure.

The request fails.

Corrective Action: Add the missing OUTPUT statement to the Application Server procedure.

CTDP5AE ERROR IN READING PAGEDEF/FORMDEF MEMBERLink copied to clipboard

Explanation: The report requires a PAGEDEF/FORMDEF definition, but the corresponding member containing the definition was not found in the PAGEDEF/FORMDEF library.

The request is not performed.

Corrective Action: Notify your INCONTROL administrator.

CTDP5BE ABEND IN IMMEDIATE PRINT {`scode`|`ucode` }Link copied to clipboard

Explanation: An abend occurred during an immediate printing.

The variables in this message are:

scode - a system ABEND code
ucode - an user ABEND code

The report is not printed.

Corrective Action: Notify your responsible system programmer.

CTDP5CE INTERNAL ERROR - INVALID HANDLE TYPE IN INPUTLink copied to clipboard

Explanation: An internal error occurred during processing of an Immediate Print request from Control-D/WebAccess. An invalid type of handle was received. The request is not performed.

Corrective Action: Check the IOA Log and the system log for additional error messages. Report the problem and any additional error messages to BMC Customer Support.

CTDP5DE INTERNAL ERROR - ILLEGAL INDEX HANDLE SUPPLIED IN REQUESTLink copied to clipboard

Explanation: An internal error occurred during an attempt to access an index in Control-D/WebAccess. An invalid index token was received from the client. The index was not accessed.

Corrective Action: Check the IOA Log and the system log for additional error messages. Report the problem and any additional error messages to BMC Customer Support.

CTDP5EI REPORT REQUESTED FOR PRINT FROM `fileName` FILE: `jobName / userName / reportName`Link copied to clipboard

Explanation: This information message indicates that following a request by a Control-D/WebAccess user, the identified report was successfully submitted in a host for deferred printing.

The variables in this message are:

reportName - the name of the report that is to be printed
jobName -the name of the job that created the report
userName - the name of the recipient to whom the report belongs
fileName - the name of the file from which the reportName report is to be printed

The reportName report will be printed at the host machine with the corresponding Print Mission.

Corrective Action: No action is required.

CTDP5FE ERROR IN DEFERRED PRINT REQUEST RC=`rc`Link copied to clipboard

Explanation: An error was encountered during the deferred printing of a report.

Valid values for rc, and their explanations, are:

Return Code	Explanation
8	Insufficient memory
12	Invalid request
16	Error during the opening of a Control-D database file
36	USER record not found in the Control-D database
48	Invalid sub-request type.

The report is not printed.

Corrective Action: If the return code is 8, increase the amount of memory that is allowed for Control-D monitors. Otherwise, have your INCONTROL administrator notify BMC Customer Support.

CTDP5GE AT LEAST ONE PRINT MISSION NAME SHOULD BE ENTEREDLink copied to clipboard

Explanation: A print mission name was not specified in the deferred print request. A print mission name is mandatory.

The print request is not performed.

Corrective Action: Specify a print mission name, and enter the request again.

CTDP5HE REQUESTED NUMBER OF PRINT COPIES EXCEEDS THE MAXIMUM ALLOWEDLink copied to clipboard

Explanation: The requested number of report copies for printing exceeds the allowable maximum. The allowable maximum is defined in the MAXCOPIES field in the report decollating mission definition.

The print request is not performed.

Corrective Action: Correct the number of copies, and perform the print request again.

CTDP5IW Action `action` denied for object keyed by `objkey`Link copied to clipboard

Explanation: A Control-D/WebAccess user issued a request for the identified action to the Control-D/WebAccess ruler (Logical View) with a specific key in the Control-D Repository, but the 024 Control-D User Exit or Security Exit denied the request.

The variables in this message are:

action - the action requested by the user
objkey - the key of the Control-D/WebAccess ruler in the Control-D Repository

The request is rejected.

Corrective Action: Call your INCONTROL administrator.

CTDP5JI RULER `action: rulerName` KEYED BY <`rulerKey>` FOR REPORT <`reportName>`Link copied to clipboard

Explanation: A Control-D/WebAccess user requested an action on a Control-D/WebAccess ruler (Logical View) with a specific key in the Control-D Repository, and the request was fulfilled.

The variables in this message are:

rulerName - the name of the Control-D/WebAccess ruler
rulerKey - the key of the Control-D/WebAccess ruler in the Control-D Repository
reportName - the name of the report
action - the requested action

Corrective Action: No action is required.

CTDP62E CTDPCIN: CTDPRSC FUNCTION = `func`, RC = `rc`.Link copied to clipboard

Explanation: An internal error occurred in the CTDPRSC internal module.

The error occurred during either of the following:

preparation of a CCIF file for viewing
creation of a Control-V index during printing mission processing

The report is not displayed or the index is not created.

Corrective Action: Notify your INCONTROL administrator and do the following:

Look for additional error messages in the IOA Log file, job log and SYSOUT data sets.
If the error occurred in Page-On-Demand, activate debug levels 10, 11, 17, 18 and 19 in the Control-D Application Server.
Duplicate the operation that caused the error to occur.
Send the DADUMP and DATRACE output debug data sets to BMC Customer Support.

CTDPD1E INVALID USER FILE - SPECIFY A, M, OR HLink copied to clipboard

Explanation: The CTD/WA user's request to copy, move, or delete the report was rejected. This is an internal error message that normally does not appear.

Corrective Action: Call your INCONTROL administrator.

CTDPD2W THE `req` REQUEST FROM USER `useriD` IS REJECTED FOR REPORT <`reportName`>Link copied to clipboard

Explanation: The CTD/WA user's request to copy, move, or delete the report was rejected by the installation Exit program.

Corrective Action: Call your INCONTROL administrator.

CTDPD3I REPORT WITH KEY <`reportID`> IS `act` FROM USER `user1` TO USER `user2`Link copied to clipboard

Explanation: This information message indicates that the reportID report has been successfully copied or moved from user user1 to user user2, in accordance with the CTD/WA user's request.

In this message, reportID is the identity of the report.

The information about the report name is provided in message CTDI0CI, which follows this message.

Corrective Action: No action is required.

CTDPD4I REPORT WITH KEY <`reportID`> IS DELETEDLink copied to clipboard

Explanation: This informational message indicates that the reportID report has been successfully deleted from the repository , in accordance with the CTD/WA user's request.

In this message, reportID is the identity of the report.

The information about the report name is provided in message CTDI0CI, which follows this message.

Corrective Action: No action is required.

CTDPT1E RECIPIENT LIST IS EMPTY.Link copied to clipboard

Explanation: The Recipient Tree, or the requested subtree, is empty.

Corrective Action: Correct the request and retry.

CTDPT2E INSUFFICIENT MEMORY TO PERFORM THE RECIPIENT TREE REQUEST.Link copied to clipboard

Explanation: A shortage of storage occurred while processing the Recipient Tree.

The user’s request that led to the processing of the Recipient Tree is rejected.

Corrective Action: Wait for a time, then retry the request. If the problem persists, call your INCONTROL administrator.

CTDPT3E INTERNAL ERROR IN RECIPIENT TREE REQUEST.Link copied to clipboard

Explanation: An internal error occurred while processing a user’s request.

The request is rejected.

Corrective Action: Call your INCONTROL administrator.

CTDPU1E RECORD TO BE UPDATED NOT FOUNDLink copied to clipboard

Explanation: The record to be updated in the Control-D database was not found. The record was deleted, perhaps by another user, before it could be updated.

The record is not updated.

Corrective Action: Refresh the received data.

CTDPU2E RECORD IS CHANGED, UPDATE FAILEDLink copied to clipboard

Explanation: A record in the Control-D database was changed after the user has received it, that is, after it was read and before it was updated.

The request fails.

Corrective Action: Refresh received data, and issue the update request again.

CTDPU3E ERROR OPENING THE IOA AM FILELink copied to clipboard

Explanation: An internal error occurred during the opening of the IOA AM file.

The IOA AM file is not opened.

Corrective Action: Have your INCONTROL administrator notify BMC Customer Support.

CTDPU4E REQUEST IS NOT VALID FOR THIS TYPE OF REPORT (STORE=YES).Link copied to clipboard

Explanation: A Control-D/Web Access user attempted to approve or reject a report created for further STORE=YES print mission processing.

These actions are not valid for these types of reports.

Corrective Action:Either approve or reject the report created by the print mission with the STORED=YES setting.

CTDPU5W Request rejected because of report status change.Link copied to clipboard

Explanation: A record in the Control-D database was changed after the user has received it, that is, after it was read and before it was updated.

The request fails.

Corrective Action: Refresh received data, and issue the update request again.

CTDPU6E Request rejected because of incorrect authorization in the Approval Tree.Link copied to clipboard

Explanation: An Approval name element related to the request has no authorized users in the Approval tree. The request fails.

Corrective Action: Define authorized users in the element, and issue the update request again.

CTDPU9E Parallel approval is not supported by CTD/WALink copied to clipboard

Explanation: An Approval name element related to the request is defined for Parallel Approval but CTD/WA does not support this type of Approval processing. The request fails.

Corrective Action: Upgrade CTD/WA to a newer version or define an Approval name element for Multi-step Approval processing.

CTDPUAW REQUEST REJECTED BECAUSE OF DUPLICATE APPROVAL BY THE SAME USERLink copied to clipboard

Explanation: A user has attempted to approve a report that was already approved by the same user earlier in another Approval process. The message is issued if the WDN131 optional wish is applied to prevent duplicate approval by the same user.

The request fails.

Corrective Action: The report can be approved by another end user who is authorized for the same Approval name in the Approval Tree.

CTDPUBE INVALID RETURN CODE `rc` FROM `module` - NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: This error message indicates that an internal error occurred in a specific module during request processing and provides the RC.

The request fails.

Corrective Action:Ask your IOA administrator to contact BMC Software Customer Support.

Messages CTDQ00 through CTDQxxLink copied to clipboard

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

CTDQ01E SYNTAX ERROR `err_num` IN LINE `lineNum` OF MEMBER $$CLIQUELink copied to clipboard

Explanation: When entering parameters in the Control-D Objects Entry Panel (Screen DO), the parsing of the $$CLIQUE Report Cliques description member failed.

Corrective Action: Fix the $$CLIQUE member in the IOA MSG library.

CTDQ02E INVALID CLIQUE FORMATLink copied to clipboard

Explanation: While attempting to create a new Report Clique definition in the Control-D Report Cliques Entry Panel (Screen DO.1), the command NEW was typed with an invalid format.

The SELECT FORMAT window is displayed.

Corrective Action: No action is required.

CTDQ03E SYNTAX ERROR IN REPORT CLIQUE TEXT; KEYWORD=`keywd`Link copied to clipboard

Explanation: The requested entry contains invalid data in the keywd keyword.

Corrective Action: Correct the non-valid value using DO screen.

CTDQ04E MISSING VALUE FOR MANDATORY KEYWORDLink copied to clipboard

Explanation: No value was inserted in a mandatory keyword.

Corrective Action: Insert a value for the keyword.

CTDQ05E VALUE LENGTH IS NOT IN RIGHT BOUNDSLink copied to clipboard

Explanation: The value that has been inserted in a keyword is either too long or too short.

Corrective Action: Correct the keyword value.

CTDQ06E INVALID NUMBERLink copied to clipboard

Explanation: The value that has been inserted in a keyword that requires a numeric value is not a valid number.

Corrective Action: Correct the keyword value.

CTDQ07E NUMBER IS NOT IN RIGHT BOUNDSLink copied to clipboard

Explanation: The value that has been inserted in a keyword that requires a numeric value is either too small or too large.

Corrective Action: Correct the keyword value.

CTDQ08E COMBO VALUE DOES NOT MATCH ANY OPTIONLink copied to clipboard

Explanation: The value that has been inserted in a keyword does not correspond to one of the options on the screen.

Corrective Action: Correct the keyword value.

CTDQ09E REPORT CLIQUE `cliqName` ALREADY EXISTSLink copied to clipboard

Explanation: An attempt has been made to save a new Report Clique definition using a name that has already been used for an existing Report Clique definition.

Corrective Action: Save the new Report Clique definition under a different name.

CTDQ0AE OBJECT NOT FOUNDLink copied to clipboard

Explanation: A file entry has been selected for editing, deleting, or browsing, but the file entry does not exist. Perhaps the object was deleted by another user or CTD/WA working simultaneously.

Corrective Action: Check the parallel processing in LOG using the Log screen, which you access through the IOA Primary Option menu. Use the CTDDIG utility to check the integrity of the Permanent User file (for object types 1-4) or the Active User file (for object type 5).

CTDQ0CE THIS COMMAND IS ALLOWED IN EDIT MODE ONLYLink copied to clipboard

Explanation: The command "SAVE" was entered, but the user entered the Report Clique screen (Screen DO.Z) in Browse mode.

The SAVE command is rejected.

Corrective Action: No action is required.

CTDQ0DE TO BROWSE RESOURCES OF TYPE 'CLIQUE' USE OPTION 4 ON OBJECTS ENTRY PANELLink copied to clipboard

Explanation: Having opened the Control-D Resources Entry Panel (Screen DO.3) by entering "3" in the COMMAND field of the Control-D Objects Entry Panel (Screen DO), the user entered "CLQ" in the RESOURCE TYPE field.

The Control-D Resources Entry Panel (Screen DO.3) is designed to list resources of all types other than Clique Resources.

The selection of the CLQ option is rejected.

Corrective Action: Exit the Control-D Resources Entry Panel (Screen DO.3) and open the Control-D Clique Resources Entry Panel (Screen DO.4).

CTDQ0EW THE UNKNOWN KEYWORD(S) WILL BE DELETED FROM THE CLIQUE DURING SAVELink copied to clipboard

Explanation: A Control-D Report Clique contains keywords that are not defined in the Report Clique description member, because the member has been changed since the Report Clique was last saved. The user has edited and then tried to save the Report Clique. This message warns that the undefined keywords will be deleted when the Report Clique is saved.

Corrective Action: No action is required.

CTDQ0GE THE OPTION IS NOT ALLOWED ON THIS LINELink copied to clipboard

Explanation: In one of the following Control-D screens

the Resources List screen (Screen DO.R)
the Reports Cliques List screen (Screen DO.C)
the Resource Sets List screen (Screen DO.T)

The user typed D (delete) beside a line, but the line had already been deleted.

Corrective Action: No action is required.

CTDQ0HW ONLY THE FIRST 200000 BYTES OF THE HUGE RESOURCE CAN BE BROWSEDLink copied to clipboard

Explanation: An attempt has been made to browse a very large resource from the Control-D Resources List screen (Screen DO.R), but no more than 200,000 bytes of data can be browsed from this screen.

Only the first 200,000 bytes of data are displayed.

Corrective Action: No action is required.

Messages CTDR00 through CTDRxxLink copied to clipboard

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

CTDR01E INVALID PARAMETER, VALID PARAMETER: MODE=TEST OR MODE=PRODLink copied to clipboard

Explanation: A MODE parameter error was detected in the CTDRSD utility.

The CTDRSD utility terminates with a condition code of 8.

Corrective Action: Correct the JCL and rerun the job. The MODE parameter in the CTDRSD utility must be set to one of the following values:

TEST - The utility runs in simulation mode and performs an analysis. It issues error messages that indicate when there are orphan RESSET records and RESOURCEs.
PROD - The utility runs in production mode and deletes orphan RESSET, RESOURCE records from the permanent user file, and members from the Control-D RESLIB library.

CTDR02I UTILITY CTDRSD STARTED IN mode MODELink copied to clipboard

Explanation: This information message indicates that the CTDRSD -- Delete orphan resource records utility started in TEST or PROD mode.

Corrective Action: No action is required.

CTDR03E ORPHAN RESOURCE SET jobName/counter IS DETECTEDLink copied to clipboard

Explanation: The CTDRSD utility detected an orphan RESSET record. The variables in this message are:

jobName - The name of the job to which the orphan RESSET record belongs.
counter - The counter part of the orphan RESSET record key.

If the CTDRSD utility is running in PROD mode, the orphaned RESSET record will be removed.

Corrective Action: No action is required.

CTDR04E RESOURCE SET IS MISSING FOR SYSDATA jobName/counter FILE {ACT | HST | MIG}Link copied to clipboard

Explanation: This message indicates that the CTDRSD utility cannot find the RESSET record that was referred by the SYSDATA record jobName/counter. The variables in this message are:

jobName - The name of the job to which the SYSDATA record belongs.
counter - The counter part of the SYSDATA record key.

The CTDRSD utility continues processing.

Corrective Action: An end-user might experience problems when viewing a corresponding report. Investigate why the RESSET record was removed and try to restore the missing RESSET record to its original state.

CTDR05I SYSDATA RECORDS WITH RESOURCE SET IN THE {ACT | HST | MIG} FILE numLink copied to clipboard

Explanation: This information message indicates the number of found SYSDATA records which contain references to RESSET records in the specified user file.

Corrective Action: No action is required.

CTDR06I ORPHAN RESOURCE SET jobName/counter IS DELETEDLink copied to clipboard

Explanation: This information message is issued by the CTDRSD utility and indicates that the utility has deleted the orphaned RESSET record. The variables in this message are:

jobName - The name of the job to which the orphan RESSET record belongs.
counter - The counter part of the orphan RESSET record key.

Corrective Action: No action is required.

CTDR07I UTILITY CTDRSD ENDED.Link copied to clipboard

Explanation: This information message indicates that the CTDRSD -- Delete orphan resource records utility ended.

Corrective Action: No action is required.

CTDR08I NO ERRORS DETECTED.Link copied to clipboard

Explanation: This information message indicates that the CTDRSD utility ended with no errors detected.

Corrective Action: No action is required.

CTDR09I ORPHAN RESOURSE SET RECORDS `num`Link copied to clipboard

Explanation: This information message displays the number of found orphan RESSET records.

Corrective Action: No action is required.

CTDR0AE ERROR WHILE LOADING CTDAOBJ IS ENCOUNTEREDLink copied to clipboard

Explanation: An error occurred during an attempt to load the CTDAOBJ module. 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 CTDAOBJ module does not exist in the Load library.
The IOA Load library is in the Linklist, and someone has updated the library without performing a refresh for the LLA.
There is some other system-oriented reason which may be found in the syslog.

The CTDRSD utility ends with a condition code of 16.

Corrective Action: Try the following options to resolve the error:

Look on the system log for additional messages related to the problem. Then 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, increase the region size.
If the Load library has been modified and the IOA Load library is in the Linklist, refresh LLA.
Rerun the CTDRSD utility.

CTDR0BE OPEN FAILED FOR OBJECT FILE RC = `rc`Link copied to clipboard

Explanation: The CTDRSD utility failed to open the OBJECT database. In this message, rc is the return code generated by the error.

The CTDRSD utility ends with a condition code of 16.

Corrective Action: Check the IOALOG and the system log for messages which indicate the reason that the open failed. If you are unable to solve the problem, report the contents of the messages to BMC Customer Support.

CTDR0CI RESOURSE SET RECORDS IN THE PERMANENT USER FILE `num`Link copied to clipboard

Explanation: This information message displays the number of RESSET records found in the User file.

Corrective Action: No action is required.

CTDR0DE GET RESOURCE SET LIST ERRORLink copied to clipboard

Explanation: An error occurred while accessing a RESSET record list. This message accompanies additional messages, which provide detailed information.

The CTDRSD utility ends with a condition code of 16.

Corrective Action: Check the IOA Log and the system log for additional error messages. If you are unable to solve the problem, report the contents of the messages and any additional error messages to BMC Customer Support.

CTDR0EE SORT FAILED WITH RC = `rc`Link copied to clipboard

Explanation: The site SORT utility, which was invoked by the CTDRSD, has ended with errors. In this message, rc is the return code generated by the SORT utility.

The CTDRSD utility ends with a condition code of 16.

Corrective Action: Refer to the SORT messages of the job and to the user guide for the SORT facility used at your site. If necessary, call your system programmer for assistance.

CTDR0FE OPEN OF SORT FILE FAILED. DDNAME `ddname`Link copied to clipboard

Explanation: An OPEN failure for the ddname DD statement was detected for the CTDRSD utility. The main program of the CTDRSD utility could not open the ddname DD statement. The specified DD statement is missing from the JCL for the CTDRSD utility.

The CTDRSD utility ends with a condition code of 16.

Corrective Action: Add the missing DD statement and rerun the CTDRSD utility.

CTDR0GE GET RESOURCE LIST ERRORLink copied to clipboard

Explanation: An error occurred while accessing a RESOURCE list. This message accompanies additional messages, which provide detailed information.

The CTDRSD utility ends with a condition code of 16.

CTDR0HI RESOURCES IN THE PERMANENT USER FILE `num`Link copied to clipboard

Explanation: This information message displays the number of RESOURCE records found in the permanent user file.

Corrective Action: No action is required.

CTDR0IE RESOURCE `res_name/res_typ/rep_format/res_sum` IS MISSING FOR RESOURCE SET `jobName/counter`Link copied to clipboard

Explanation: This message indicates that the CTDRSD utility cannot find the RESOURCE record or the member of the Control-D RESLIB library that has been referred by the RESSET record jobName/counter. The variables in this message are:

res_name - The name of the requested resource.
res_typ - The code of the type of the requested resource.
rep_format - The code of the format of the decollated report.
res_sum - The checksum of the requested resource.
jobName - The name of the job to which the orphan RESSET record belongs.
counter - The counter part of the orphan RESSET record key.

The CTDRSD utility continues processing.

Corrective Action: An end-user might have problems with viewing the corresponding report. Investigate why the RESOURCE was removed and try to restore the missing resource to its original state.

CTDR0JE ORPHAN RESOURCE `res_name/res_typ/rep_format/res_sum` IS DETECTEDLink copied to clipboard

Explanation: The CTDRSD utility detected an orphan RESOURCE. The variables in this message are:

res_name - The name of the requested resource.
res_typ - The code of the type of requested resource.
rep_format - The code of the format of the decollated report.
res_sum - The checksum of the requested resource.

If the CTDRSD utility is running in PROD mode, the orphaned RESSET record will be removed.

Corrective Action: No action is required.

CTDR0KE ORPHAN CLIQUE RESOURCE `Rep_Clique_name/res_sum` IS DETECTEDLink copied to clipboard

Explanation: The CTDRSD utility detected an orphan CLIQUE RESOURCE. The variables in this message are:

Rep_Clique_name - The Report Clique Definition name.
res_sum - The checksum of the requested Report Clique resource.

If the CTDRSD utility is running in PROD mode, the orphaned CLIQUE RESOURCE will be removed.

Corrective Action: No action is required.

CTDR0LI ORPHAN RESOURCE `res_name/res_typ/rep_format/res_sum` IS DELETEDLink copied to clipboard

Explanation: This information message is issued by the CTDRSD utility and indicates that the utility has deleted the orphaned RESOURCE. The variables in this message are:

res_name - The name of the requested resource.
res_typ - The code of the type of the requested resource.
rep_format - The code of the format of the decollated report.
res_sum - The checksum of the requested resource.

Corrective Action: No action is required.

CTDR0MI ORPHAN CLIQUE RESOURCE `Rep_Clique_name/res_sum` IS DELETEDLink copied to clipboard

Explanation: This information message is issued by the CTDRSD utility and indicates that the utility has deleted the orphaned CLIQUE RESOURCE. The variables in this message are:

Rep_Clique_name - The Report Clique Definition name.
res_sum - The checksum of the requested Report Clique resource.

Corrective Action: No action is required.

CTDR0NI ORPHAN RESOURCES `num`Link copied to clipboard

Explanation: This information message displays the number of found orphan RESOURCE records from the permanent user file and/or members of the Control-D RESLIB library.

Corrective Action: No action is required.

CTDR0OE CLIQUE RESOURCE `Rep_Clique_name/res_sum` IS MISSING FOR RESOURCE SET `jobName/counter`Link copied to clipboard

Explanation: This message indicates that the CTDRSD utility cannot find the CLIQUE RESOURCE referred by the RESSET record jobName/counter. The variables in this message are:

Rep_Clique_name - The Report Clique Definition name.
res_sum - The checksum of the requested Report Clique resource.
jobName - The name of the job to which the RESSET record belongs.
counter - The counter part of the RESSET record key

The CTDRSD utility continues processing.

Corrective Action: An end-user might experience problems when attempting to view the corresponding report. Investigate why the CLIQUE RESOURCE was removed and try to restore the missing CLIQUE RESOURCE to its original state.

CTDR0PE ORPHAN RESOURCE `res_name/res_typ/rep_format/res_sum` IS NOT DELETEDLink copied to clipboard

Explanation: Either the orphaned RESOURCE record from the permanent user file or a member of the Control-D RESLIB library was not deleted by the CTDRSD utility. This message follows other messages that explain the nature of the error. The variables in this message are:

res_name - The name of the requested resource.
res_typ - The code of the type of the requested resource.
rep_format - The code of the format of the decollated report.
res_sum - The checksum of the requested resource.

The CTDRSD utility continues processing.

Corrective Action: Review the messages that precede this message for reasons for the deletion failure.

CTDR0QE ORPHAN CLIQUE RESOURCE `Rep_Clique_name/res_sum` IS NOT DELETEDLink copied to clipboard

Explanation: The orphaned CLIQUE RESOURCE was not deleted by the CTDRSD utility. This message follows other messages that explain the nature of the error. The variables in this message are:

Rep_Clique_name - The Report Clique Definition name.
res_sum - The checksum of the requested Report Clique resource.

The CTDRSD utility continues processing.

Corrective Action: Review the messages that precede this message for reasons for the deletion failure.

CTDR0RE RESOURCE SET `jobName/counter` IS NOT DELETEDLink copied to clipboard

Explanation: The orphaned RESSET record was not deleted by the CTDRSD utility. This message follows other messages that explain the nature of the error. The variables in this message are:

jobName - The name of the job to which the orphan RESSET record belongs.
counter - The counter part of the orphan RESSET record key.

The CTDRSD utility continues processing.

Corrective Action: Review the messages that precede this message for reasons for the deletion failure.

CTDR0SI DELETED RESOURCE SET RECORDS `num`Link copied to clipboard

Explanation: This information message displays the number of deleted RESSET records.

Corrective Action: No action is required.

CTDR0TI DELETED RESOURCES `num`Link copied to clipboard

Explanation: This information message displays the number of deleted RESOURCE records from the permanent user file and/or members of the Control-D RESLIB library.

Corrective Action: No action is required.

CTDRS0I CTDUFPRT STARTEDLink copied to clipboard

Explanation: This information message indicates that CTDRSTMS, the massive restore request utility, has started.

Corrective Action: No action is required.

CTDRS1E INVALID PARAMETER: `parm`Link copied to clipboard

Explanation: The parm input parameter specified for the CTDRSTMS utility is not valid.

The utility stops.

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

CTDRS2E REDUNDANT PARAMETER: `parm`Link copied to clipboard

Explanation: The parm input parameter for the CTDRSTMS utility has already been specified.

The utility stops.

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

CTDRS3E THE PARAMETER `parm` MUST BE SPECIFIEDLink copied to clipboard

Explanation: The required parm input parameter for the CTDRSTMS utility is missing.

The utility stops.

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

CTDRS6I NUMBER OF SELECTED RECORDS: `number`Link copied to clipboard

Explanation: This information message issue displays the total number of records selected by the CTDRSTMS utility.

Corrective Action: No action is required.

CTDRSEI CTDUFRST ENDED WITH ERRORSLink copied to clipboard

Explanation: This information message indicates that the CTDRSTMS utility finished with errors.

Corrective Action: Examine other messages relating to the CTDRSTMS utility to identify and fix the problem, and then rerun the utility.

CTDRSFI CTDRSTMS ENDED OKLink copied to clipboard

Explanation: This information message indicates that the CTDRSTMS utility finished successfully.

Corrective Action: No action is required.

CTDRSGI KEY=`'reportKey'`, ODATE=`date`Link copied to clipboard

Explanation: This information message identifies a report that was selected by the CTDRSTMS utility.

The variables in the message are:

reportKey - VSA key of the selected report.
date - decollation mission order date of the report. The date format is one of he following, depending on the site standard defined in the IOAPARM installation member.
dd/mm/yy
mm/dd/yy
yy/mm/dd

Corrective Action: No action is required.

CTDRSHI LIST OF SELECTED REPORTS:Link copied to clipboard

Explanation: This information message is the title for the list of selected reports (CTDRSGI messages) that are issued by the CTDRSTMS utility.

Corrective Action: No action is required.

Messages CTDS00 through CTDSxxLink copied to clipboard

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

CTDS20E ACCESS DENIED FOR USER `userName: rsn`Link copied to clipboard

Explanation: The IOASE16 security module or the IOAZ016 user exit rejected the request to log on to the Control-D Application Server. The message displays the reason provided by the security package for rejecting the user.

For an explanation of the reason code (rsn), see your security software documentation.

The variables in this message are:

userName - the name of the user
rsn - the reason for denying access

The login request is rejected.

Corrective Action: Check that the user name and password are spelled correctly and retry. If necessary, contact your security administrator.

CTDS21W `fileName` user file unlocked. Lock was done by `progName` rc=`rc`.Link copied to clipboard

Explanation: A post processing request routine revealed that one of the user files was held and not released during request processing. The routine releases the file.

The variables in this message are:

fileName - the name of the user file. Valid values are:
- ACT
- MIG
- HST
progName - the name of the program that held and did not release the file
rc - the return code of the release command. A return code of 04 means that the file was successfully released. A return code greater than 04 means that there was an error in the release command.

Corrective Action: No action is required.

Messages CTDT00 through CTDTxxLink copied to clipboard

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

CTDT01I TRANSFER START GROUP `groupId` REPORT `repId`Link copied to clipboard

Explanation: This information message indicates that the transfer of the repId report in the groupId group from the Control-D Session Agent started.

Corrective Action: No action is required.

CTDT02I TRANSFER ENDED OK GROUP `groupId`, BYTES `numBytes` (`trfr_rate` BYTES/SEC), REPORT `repId`Link copied to clipboard

Explanation: This information message indicates that the transfer of the repId report in the groupId group from the Control-D Session Agent ended successfully.

The variables in this message are:

groupId - the identity of the group that contains repId
repId - the identity of the report that was transferred
numBytes - the number of bytes transferred
trfr_rate - the transfer rate, in bytes per second

Corrective Action: No action is required.

CTDT04E FUNCTION `func` WAS SUPRESSED BY CTDSE27/CTDX027 EXIT GROUP `groupId` REPORT `repId`Link copied to clipboard

Explanation: A File Transfer option function has been suppressed, either by Control-D Security Exit 27, or by Control-D User Exit 27.

The variables in this message are:

func - the File Transfer option function that was suppressed
groupId - the identity of the group that contains repId
repId - the identity of the report that was to be transferred

The repId report is not transferred.

Corrective Action: If you use Control-D Security Exit 27 to perform some special function instead of or in addition to the standard function, no intervention is required.

Otherwise, correct Control-D Security Exit 27 or Control-D User Exit 27.

CTDT05E UNEXPECTED RETURN CODE `rc` FOR FUNCTION `func` FROM CTDSE27/CTDX027 EXIT GROUP `groupId` REPORT `repId`Link copied to clipboard

Explanation: An unexpected return code was returned by either Control-D User Exit 27 or Control-D Security Exit 27.

The variables in this message are:

rc - the return code
func - the function that was being performed when rc was returned
groupId - the identity of the group that contains repId
repId - the identity of the report on which func was being performed

The transfer of repId from the Control-D Session Agent is terminated.

Corrective Action: Correct Control-D Security Exit 27 or Control-D User Exit 27.

CTDT06E ERROR IN FTOPARM `errorText`Link copied to clipboard

Explanation: An error was found in the text of a member in the Control-D FTOPARM library.

The transfer of the current message from the Control-D Session Agent is terminated.

Corrective Action: Correct the problematic text in the Control-D FTOPARM library.

CTDT07E TRANSFER HAS BEEN TERMINATED GROUP `groupId`, BYTES `numBytes` (`trfr_rate` BYTES/SEC), REPORT `repId`Link copied to clipboard

Explanation: The transfer of a report has been terminated.

The variables in this message are:

groupId - the identity of the group that contains repId
numBytes - the number of bytes transferred
trfr_rate - the transfer rate, in bytes per second
repId - the identity of the report that was being transferred

The transfer of repId is terminated.

Corrective Action: Examine accompanying messages that explain the reason for the termination of this transfer.

CTDT08E TRANSFER ENDED NOT OK GROUP `groupId`, BYTES `numBytes` (`trfr_rate` BYTES/SEC), REPORT `repId`Link copied to clipboard

Explanation: The transfer of a report ended unsuccessfully (NOT OK).

The variables in this message are:

groupId - the identity of the group that contains repId
numBytes - the number of bytes transferred
trfr_rate - the transfer rate, in bytes per second
repId - the identity of the report that was being transferred

Corrective Action: Examine accompanying messages that explain the reason for the transfer ending NOT OK.

CTDT09E INVALID AFP FILE - repIdLink copied to clipboard

Explanation: You attempted to transfer an invalid AFP report through the FTO Application Server.

The repId variable in this message indicates the identity of the report that was being transferred.

Corrective Action: Examine the AFP file and check its validity.

CTDT0AE TRANSFER CANCELED - FILE IS EMPTY, GROUP groupId REPORT repIdLink copied to clipboard

Explanation: The transfer was canceled because the transferred file is empty.

The variables in this message are:

groupId - the identity of the group that contains the report
repId - the identity of the report that was being transferred

Corrective Action: Check the transferred file, and ensure that it is not empty.

CTDTR0I CTDUPTR UTILITY STARTEDLink copied to clipboard

Explanation: This information message indicates that CTDUPTR, the utility that updates the Control-D recipient tree, has begun.

Corrective Action: No action is required.

CTDTR1I CTDUPTR UTILITY COMPLETED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the CTDUPTR utility finished without errors.

Corrective Action: No action is required.

CTDTR2E CTDUPTR UTILITY ENDED WITH ERRORSLink copied to clipboard

Explanation: This information message indicates that the CTDUPTR utility discovered problems during processing. Additional information on the problems discovered is available in the job log.

The utility stops.

Corrective Action: Examine the job log for error messages describing the problem. Make any necessary corrections and rerun the utility.

CTDTR3I CONTROL-D RECIPIENT TREE MEMBER `memname` SAVEDLink copied to clipboard

Explanation: This information message indicates that the Control-D recipient tree member (memname) has been updated by the CTDUPTR utility and saved in the library.

Corrective Action: No action is required.

CTDTR4E INVALID PARAMETER: `parm`Link copied to clipboard

Explanation: The parm input parameter specified in the JCL for the CTDUPTR utility is not valid.

The utility stops.

Corrective Action: Correct the invalid input parameter (parm) in the JCL and rerun the utility.

CTDTR5E THE PARAMETER `parm` MUST BE SPECIFIEDLink copied to clipboard

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

The utility stops.

Corrective Action: Add the missing parameter to the JCL and rerun the utility.

CTDTR6E REDUNDANT PARAMETER: `parm`Link copied to clipboard

Explanation: The parm input parameter for the CTDUPTR utility has already been specified. The same parameter is specified twice.

The utility stops.

Corrective Action: Remove the extra input parameter from the JCL and rerun the utility.

CTDTR7E NO OPERATIONS SPECIFIED IN THE INPUT PARAMETERSLink copied to clipboard

Explanation: No operations have been found in the input parameters for the CTDUPTR utility. The input parameters should contain at least one of the following operations:

SELECT
DELETE
INSERT
COPY

The utility stops.

Corrective Action: Correct the input parameters and rerun the job.

CTDTR8E RECIPIENT LEVEL `lv` IS NOT DEFINED IN CTDPARMLink copied to clipboard

Explanation: The recipient level lv specified in the input parameter for the CTDUPTR utility is not found in the available levels list in CTDPARM.

The utility stops.

Corrective Action: Use the following procedure:

Examine the input parameters in the JCL.
Do one of the following actions:
Correct the value for the recipient level
Add the new level to CTDPARM
Rerun the utility.

CTDTR9I CTDUPTR UTILITY IS RUNNING IN SIMULATION MODELink copied to clipboard

Explanation: This information message indicates that the CTDUPTR utility is running in simulation mode because the MODE=TEST parameter has been specified.

The utility issues the updating report but does not save the updated Recipient tree member in the library.

Corrective Action: If all update actions in the issued report are correct, set the MODE parameter to PROD (MODE=PROD) and run the utility to update the Recipient Tree.

CTDTRAW RECIPIENT `recipient name` IS NOT DELETED BECAUSE IT HAS CHILD ELEMENTSLink copied to clipboard

Explanation: This warning message is issued when a DELETE operation is specified, without the WITHCHILD parameter, for a recipient that has child elements.

The utility skips the DELETE operation and continues processing.

Corrective Action: Use the following procedure:

Verify the specified recipient and all its child elements should be deleted.
If the recipient should be deleted, add the WITHCHILD parameter to the DELETE operation.
Rerun the utility.

CTDTRBI NUMBER OF RECIPIENTS IN THE TREE IS `nnnnnnn`.Link copied to clipboard

Explanation: This information message indicates that the Control-D Recipient tree contains nnnnnn recipient entries after updating by the CTDUPTR utility.

Corrective Action: No action is required.

CTDTRCI THE RECIPIENT TREE MEMBER `memname` IS NOT SAVEDLink copied to clipboard

Explanation: This information message indicates that the CTDUPTR utility did not save the updated Recipient tree member memname in the library.

The utility issues the updating report but the updated Recipient tree member is not saved in the library.

Corrective Action: This message is issued in the following cases:

The utility ran in TEST mode. For more information, see the explanation of message CTDTR9I.
The utility discovered problems during processing. Examine the job log for error messages describing the problem, correct the problem and rerun the utility.

CTDTRDE RECIPIENT=`recipient name`, STATEMENT=`statement`Link copied to clipboard

Explanation: This message follows the error message CTD003E and gives information on the Recipient tree member statement causing the error.

The utility stops.

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

Verify that the Recipient tree member name (recipient name) specified is correct.
If the member name is incorrect, set the MEMBER parameter to the correct value.
If the member name is correct, check the specified statement in this member and make the appropriate changes to fix the problem.
Rerun the utility.

CTDTREW RECIPIENT `recipient name` IS NOT FOUND TO BE COPIEDLink copied to clipboard

Explanation: This warning message is issued when the recipient entry, specified as the source for a COPY operation, is not found in the recipient tree.

The utility skips the COPY operation and continues processing.

Corrective Action: Correct the recipient name specified as the source to be copied and rerun the utility.

CTDTRFW NO RECIPIENTS SATISFY TO `operation` PARAMETERSLink copied to clipboard

Explanation: This warning message indicates that no recipient entries satisfied the selection parameters specified for the SELECT or DELETE operation.

The operation is skipped and the utility continues processing.

Corrective Action: Adjust the selection parameters and rerun the utility.

CTDTRGW CTDUPTR UTILITY COMPLETED WITH WARNINGSLink copied to clipboard

Explanation: This warning message indicates that the CTDUPTR utility finished processing and wrote warning messages to the job log.

The utility ends with the return code 4. If PROD mode has been specified, the updated Recipient tree member is saved in the library.

Corrective Action: Make the appropriate changes to the JCL based on the information contained in the warning messages in the job log and rerun the utility.

CTDTRHW RECIPIENT=`recipient name`, PARAMETER=`parameter`Link copied to clipboard

Explanation: This message indicates the parameter line that caused the warning message (either CTDTRIW or CTDTRJW) that follows this line.

The problematic parameter line is skipped and the utility continues processing.

Corrective Action: For information on how to correct the parameter line, see the User actions for the CTDTRIW or CTDTRJW message.

CTDTRIW ENTRY SPECIFIED FOR DELETION IS NOT FOUNDLink copied to clipboard

Explanation: This warning message indicates that a description line, address line, synonym or authorized TSO user specified to be deleted from a recipient entry is not found. The preceding CTDTRHW message indicates the parameter line that caused the warning.

The parameter line, indicated by the CTDTRHW message, is skipped and the utility continues processing.

Corrective Action: Correct the parameter line indicated by the CTDTRHW message and rerun the utility.

CTDTRJW DUPLICATE ENTRY IS NOT ADDEDLink copied to clipboard

Explanation: This warning message indicates that a description line, address line, synonym or authorized TSO user specified to be added to a recipient entry already exists. The preceding CTDTRHW message indicates the parameter line that caused the warning.

The parameter line, indicated by the CTDTRHW message, is skipped and the utility continues processing

Corrective Action: Correct the parameter line indicated by the CTDTRHW message and rerun the utility.

CTDTRLI `nnnnnnn` NEW RECIPIENTS WERE ADDEDLink copied to clipboard

Explanation: This information message indicates the number of recipients (nnnnnnn) added to the Control-D recipient tree during the CTDUPTR utility run.

Corrective Action: No action is required.

CTDTRMI `nnnnnnn` RECIPIENTS WERE DELETEDLink copied to clipboard

Explanation: This information message indicates the number of recipients (nnnnnnn) deleted from the Control-D recipient tree during the CTDUPTR utility run.

Corrective Action: No action is required.

CTDTRNI `nnnnnnn` RECIPIENTS WERE UPDATEDLink copied to clipboard

Explanation: This information message indicates the number of recipients (nnnnnnn) updated in the Control-D recipient tree during the CTDUPTR utility run.

Corrective Action: No action is required.

CTDTROI `nnnnnnn` RECIPIENTS WERE COPIEDLink copied to clipboard

Explanation: This information message indicates the number of recipients (nnnnnnn) copied to another recipient in the Control-D recipient tree during the CTDUPTR utility run.

Corrective Action: No action is required.

CTDTRPE PARAMETER LENGTH EXCEEDED: `parm`Link copied to clipboard

Explanation: The parm input parameter exceeds the maximum allowable length.

The utility stops.

Corrective Action: No action is required.

CTDTRRE RECIPIENT `recipient name` IS NOT VALID IN THE RECIPIENT TREE `recipient tree member`Link copied to clipboard

Explanation: During the CTDUPTR utility run, it was detected that the specified recipient in the Control-D recipient tree has an invalid structure.

Corrective Action: Remove this recipient from the recipient tree through the Recipient Tree facility (option T on the IOA Primary Option menu), and then create it again.

Messages CTDU00 through CTDUxxLink copied to clipboard

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

CTDU10E `fileType` USER FILE ERROR `error`Link copied to clipboard

Explanation: An error occurred while accessing a User Reports List file. This message is written to the IOA Log file by the user file interface routine.

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.

error - the error description

Control returns to the calling routine which usually issues the CTD908S message.

Corrective Action: Do one of the following, depending on the value of error:

If the value of error is INCORRECT FORMAT OF DATA / INDEX FILE, use the IOADBF utility to reformat the problematic file.
If the value of error is RECORD NOT FOUND IN THE DATA FILE or INDEX RECORD DOES NOT MATCH DATA RECORD, use the CTDDIB utility to rebuild the index file.
If the value of error is FILE IS NOT CONVERTED ACCORDING TO WD1164, use the CTDDIB utility to rebuild the index file.
If the value of err is DATA FILE OVERFLOW or INDEX FILE OVERFLOW, enlarge the problematic file by running the IOADBF utility with the EXTEND function.
You can prevent this problem in the future by defining a secondary space allocation and automatic extension in the corresponding Space Calculation Step. You can find this using ICE:
1. In the IOA Installation Menu, select Customization.
2. Select the environment to customize.
3. In the Customization screen, set Product ID to CTD and select Product Customization.
4. Select Major Step 5, Customize Control-D User Files.
If the value of error is ALTERNATIVE INDEX DEFINITION MISMATCHES LRECL, check and correct the alternative index definition in the DEF xxxi or DEFALTI members or both, and rerun the CTDUFDBF, CTDUFANX, and CTDDIB utilities to recreate the alternative index component.

CTDU11I `opn` OPERATION FOR `fileName` FILE FROM `pgm` PROGRAM IN `modeType` MODELink copied to clipboard

Explanation: This information message indicates that accesses to user files were traced as requested by optional wish WD2370.

Corrective Action: No action is required.

CTDU99E `fileType` FILE RC=`rc` FUNC `func` PGM `pgmCsect` ID=`xx /yyy` LAST KEY=`lastKey`Link copied to clipboard

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

This message accompanies the CTD908S message, and provides additional information.

The variables in this message are:

fileType - the type of User Report 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 by the data component values.

rc - return code
func - the operation that caused the error
pgmCsect - the program CSECT that received the error
xx/ yyy - an identifier for localizing the erroneous call
lastKey - the key in the data or index file

The following table lists and explains the possible values for the return code (rc):

rc	Explanation
004	Read operation: EOF. Add index operation: Duplicate Key. Update operation: Record was changed. 0i
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.
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.
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.

Corrective Action: Do the following:

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

CTDUF0I CTDUFPRT STARTEDLink copied to clipboard

Explanation: This information message indicates that CTDUFPRT, the user records printing utility, started.

Corrective Action: No action is required.

CTDUF1E INVALID PARAMETER: `parm`Link copied to clipboard

Explanation: The parm input parameter specified for the CTDUFPRT utility is not valid.

The utility stops.

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

CTDUF2E REDUNDANT PARAMETER: `parm`Link copied to clipboard

Explanation: The parm input parameter for the CTDUFPRT utility has already been specified. The same parameter is specified twice.

The utility stops.

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

CTDUF3E THE PARAMETER `parm` MUST BE SPECIFIEDLink copied to clipboard

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

The CTDUFPRT utility stops.

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

CTDUF4E THE PARAMETER `parm` CANNOT BE SPECIFIED FOR RECORD TYPE `x`Link copied to clipboard

Explanation: The parm input parameter for the CTDUFPRT utility cannot be specified for record type x which is specified in the RECORD parameter.

The CTDUFPRT utility stops.

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

CTDUF5I INPUT PARAMETER: `parm`Link copied to clipboard

Explanation: This information message identifies that the parm input parameter for the CTDUFPRT utility is specified.

Corrective Action: No action is required.

CTDUF6I NUMBER OF SELECTED RECORDS: `num`Link copied to clipboard

Explanation: This information message issues total number of records selected by the CTDUFPRT utility.

Corrective Action: No action is required.

CTDUF9I `recordType` RECORDS: `num`Link copied to clipboard

Explanation: This information message follows the CTDUF6I message if the RECORD parameter is not specified for the CTDUFPRT utility.

Each such message issues the number of selected records of the specified record type.

Corrective Action: No action is required.

CTDUFEI CTDUFPRT ENDED WITH ERRORSLink copied to clipboard

Explanation: This information message indicates that the CTDUFPRT utility finished with errors.

Corrective Action: Examine other messages relating to the CTDUFPRT utility to identify and fix the problem, then rerun the utility.

CTDUFFI CTDUFPRT ENDED OKLink copied to clipboard

Explanation: This information message indicates that the CTDUFPRT utility finished successfully.

Corrective Action: No action is required.

CTDUFGI CONTROL-V UTILITY CTVSCTT STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTVSCTT utility was started.

Corrective Action: No action is required.

CTDUFHI CONTROL-V UTILITY CTVSCTT STOPPED BECAUSE OF ERRORSLink copied to clipboard

Explanation: This information message indicates that the CTVSCTT utility stopped working because of severe errors detected during the utility run.

The CTVSCTT utility ends with a return code of 08.

Corrective Action: Examine the accompanying messages for the cause of the problem and take action accordingly.

CTDUFII CONTROL-V UTILITY CTVSCTT ENDEDLink copied to clipboard

Explanation: This information message indicates that the CTVSCTT utility ended and the output file was created that contains information about the data sets that were migrated to tape.

Corrective Action: No action is required.

CTDUFKE MEDIA NAME `media` NOT FOUND IN IOASPRMLink copied to clipboard

Explanation: The CTVSCTT utility read a SYSDATA or Index record from the Migrated User file with a media name that does not exist in the IOASPRM parameters member.

The problematic record is skipped and the CTVSCTT utility continues processing.

Corrective Action: Check the media name issued in the message. If there were reports that were migrated to this media, add this media to the IOASPRM member and rerun the utility.

CTDUFLE THE PARAMETER 'FIELD' CAN BE SPECIFIED AFTER PRINTFORM=REPORT ONLYLink copied to clipboard

Explanation: This error message is issued when the FIELD parameter was encountered, in the input stream for the CTDUFPRT utility, before the PRINTFORM=REPORT parameter was specified.

The utility stops.

Corrective Action: Correct the input parameters and rerun the job.

CTDUFME FIELD= `fieldName` CANNOT BE SPECIFIED FOR RECORD TYPE `type`Link copied to clipboard

Explanation: This error message is issued when the CTDUFPRT utility has been submitted and the following conditions are true:

PRINTFORM parameter is set to REPORT (PRINTFORM=REPORT)
FIELD parameter set to a field name that is not permitted for the record type (type) specified

The utility stops.

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

Check the list of field names allowed for the printed records type. For more information, see the INCONTROL for z/OS Utilities Guide.
Correct the input parameters
Rerun the job

Messages CTDV00 through CTDVxxLink copied to clipboard

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

CTDV00I CTVUPINV UTILITY STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTVUPINV utility started.

Corrective Action: No action is required.

CTDV01I CTVUPINV UTILITY COMPLETED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the CTVUPINV utility completed successfully.

Corrective Action: No action is required.

CTDV02E CTVUPINV UTILITY ENDED WITH ERRORSLink copied to clipboard

Explanation: This error message indicates that the CTVUPINV utility processing was interrupted because of problems. Additional information about the problems is available in the job log.

The utility stops.

Corrective Action: Examine the job log for error messages describing the problem. Make any necessary corrections and rerun the utility.

CTDV03I CTVUPINV UTILITY IS RUNNING IN SIMULATION MODELink copied to clipboard

Explanation: This information message indicates that the CTVUPINV utility is running in the simulation (TEST) mode. No data will be changed in the Permanent User File. Only an output report will be issued.

Corrective Action: No action is required.

CTDV04E INVALID PARAMETER: `parm`Link copied to clipboard

Explanation: The parm input parameter specified in the JCL for the CTVUPINV utility is not valid.

The utility stops.

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

CTDV05E INVALID PARAMETER IN CTDSPARM: `parm`Link copied to clipboard

Explanation: The parm input parameter in the CTDSPARM member that specifies a default destination value for printing subscribed reports is not valid.

The utility stops.

Corrective Action: Correct the invalid parm input parameter in the CTDSPARM member and rerun the job.

CTDV06E REDUNDANT PARAMETER: `parm`Link copied to clipboard

Explanation: The parm input parameter of the CTVUPINV utility has already been specified. The parameter can validly be specified only once in the current statement.

The utility stops.

Corrective Action: Remove the extra input parameter from the input parameter stream in JCL and rerun the job.

CTDV07E `parm` PARAMETER LENGTH EXCEEDEDLink copied to clipboard

Explanation: The parm input parameter of the CTVUPINV utility exceeds the maximum allowable length.

The utility stops.

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

CTDV08E EMPTY `stat` STATEMENTLink copied to clipboard

Explanation: The action stat statement is specified of the CTVUPINV utility without any parameters.

The utility stops.

Corrective Action: Add required parameters to the statement in the JCL and rerun the job.

CTDV09E OBLIGATORY PARAMETER `parm` FOR RECORD TYPE=`x` IS MISSINGLink copied to clipboard

Explanation: The parm parameter, which is obligatory for the record type x, is missing after the record is inserted or updated by the CTVUPINV utility. The utility does not process the input statement causing this error, but continues to process other input statements.

Corrective Action: Check the input parameters causing this error, specify valid parameters in JCL, and run the new job, if necessary.

CTDV0AE PARAMETER `parm` IS NOT AVAILIBLE FOR RECORD TYPE=`x`Link copied to clipboard

Explanation: The record type x, created by the CTVUPINV utility according to the specified input parameters, is missing the parm parameter, which is obligatory for this record type. The utility does not process the input statement causing this error, but continues to process other input statements.

Corrective Action: Check the input parameters causing this error, specify valid parameters in JCL, and run the new job, if necessary.

CTDV0BE EMPTY INDEX NAME OF INDEX LEVEL `x`Link copied to clipboard

Explanation: The CTVUPINV utility issues this error message in the following cases:

The name of the Index level x is not specified in the created subscription record, but the name of the next Index level is specified.
The name of the Index level x is not specified in the created subscription record, but the Index value of the corresponding Index level is specified.

The utility does not process the input statement causing this error, but continues to process other input statements.

Corrective Action: Check the input parameters causing this error, specify valid parameters in JCL, and run the new job, if necessary.

CTDV0CE EMPTY INDEX VALUE OF INDEX LEVEL `x`Link copied to clipboard

Explanation: The CTVUPINV utility issues this error message in the following cases:

The value of the Index level x is not specified in the created subscription record, but the value of the next Index level is specified.
The value of the Index level x is not specified in the created subscription record, but the Index name of the corresponding Index level is specified.

The utility does not process the input statement causing this error, but continues to process other input statements.

Corrective Action: Check the input parameters causing this error, specify valid parameters in JCL, and run the new job, if necessary.

CTDV0DE REPORT NAME SHOULD NOT HAVE MASK CHARACTERS FOR RECORD TYPE=G/RLink copied to clipboard

Explanation: The CTVUPINV utility issues this error message when the created subscription record of type G or R has mask characters in the first 12 bytes of the report name. It is not valid because the first 12 characters of the report name are included with the record ID.

The utility does not process the input statement causing this error, but continues to process other input statements.

Corrective Action: Check the input parameters causing this error, specify valid parameters in JCL, and run the new job, if necessary.

CTDV0EE LAST LEVEL INDEX VALUE SHOULD NOT HAVE MASK CHARACTERS FOR RECORD TYPE=I/SLink copied to clipboard

Explanation: The CTVUPINV utility issues this error message when the created subscription record of type I or S has mask characters in the first 12 bytes of the last level index value. It is not valid because the first 12 characters of the last level index value are included with the record ID.

The utility does not process the input statement causing this error, but continues to process other input statements.

Corrective Action: Check the input parameters causing this error, specify valid parameters in JCL, and run the new job, if necessary.

CTDV0GE THE SECOND DESTINATION SHOULD NOT BE SPECIFIED WHEN THE FIRST IS EMPTYLink copied to clipboard

Explanation: The CTVUPINV utility issues this error message when the created subscription record has the second specification for the printing destination, while the first specification is empty.

The utility does not process the input statement causing this error, but continues to process other input statements.

Corrective Action: Check the input parameters and the CTDSPARM default destination parameters causing this error, specify valid parameters in JCL, and run the new job, if necessary.

CTDV0HE DUPLICATE RECORD, OLD RECORD ID: `record_id`Link copied to clipboard

Explanation: The CTVUPINV utility issues this error message when the created subscription record has the same record key of an existing subscription record. For more information about the record key, see the description of the utility in the INCONTROL for z/OS Utilities Guide.

The utility does not process the input statement causing this error, but continues to process other input statements.

Corrective Action: Check the input parameters causing this error, specify valid parameters in JCL, and run the new job, if necessary.

CTDV0II OPERATION: `operation`, RECORD ID: `record_id`Link copied to clipboard

Explanation: The information message precedes the error messages CTDV09E, CTDV0AE, CTDV0BE, CTDV0CE, CTDV0DE, CTDV0EE, CTDV0FE, CTDV0GE, and CTDV0HE. It is issued when the error described in the following message is recognized in the subscription record updated by the CHANGE TO or REPLICATE operations. It indicates the performed operation and the created subscription record. You can see the contents of the updated INV record in the output report file referred to in the DAREPORT DD statement.

Corrective Action: No action is required.

CTDV0JE CTVUPINV UTILITY TERMINATES DUE TO AN ERROR IN THE SORTLink copied to clipboard

Explanation: The CTVUPINV utility issues this error message when the invoked SORT utility ended with errors.

The utility stops.

Corrective Action:Examine the messages issued by the SORT utility to SYSOUT to identify the problem. Make appropriate changes to the JCL and rerun the job.

CTDV0KI nnnnnnn NEW SUBSCRIPTION RECORDS WERE ADDEDLink copied to clipboard

Explanation: This information message indicates the number of subscription records added to the Permanent User File during the CTVUPINV utility run.

Corrective Action: No action is required.

CTDV0LI `nnnnnnn` SUBSCRIPTION RECORDS WERE READ FROM THE PERMANENT FILELink copied to clipboard

Explanation: This information message indicates the number of subscription records read from the Permanent User File during the CTVUPINV utility run.

Corrective Action: No action is required.

CTDV0MI `nnnnnnn` SUBSCRIPTION RECORDS WERE SELECTEDLink copied to clipboard

Explanation: This information message indicates the number of subscription records selected from the Permanent User File during the CTVUPINV utility run.

Corrective Action: No action is required.

CTDV0NI `nnnnnnn` SUBSCRIPTION RECORDS WERE DELETEDLink copied to clipboard

Explanation: This information message indicates the number of subscription records deleted from the Permanent User File during the CTVUPINV utility run.

Corrective Action: No action is required.

CTDV0OI `nnnnnnn` SUBSCRIPTION RECORDS WERE UPDATEDLink copied to clipboard

Explanation: This information message indicates the number of subscription records updated in the Permanent User File during the CTVUPINV utility run.

Corrective Action: No action is required.

CTDV0PW NO RECORDS WERE PROCCESSED BY THE UTILITYLink copied to clipboard

Explanation: This warning message indicates that no records were found that satisfy the selection parameters specified in the input statements. In this situation the CTVUPINV utility ends with return code 4.

Corrective Action: No action is required.

CTDV0QI `nnnnnnn` SUBSCRIPTION RECORDS WERE REPLICATEDLink copied to clipboard

Explanation: This information message indicates the number of subscription records replicated in the Permanent User File during the CTVUPINV utility run.

Corrective Action: No action is required.

CTDV0RE SUBSCRIBE=`X` IS NOT AVAILIBLE FOR RECORD TYPE=`Y`Link copied to clipboard

Explanation:The record type X, created by the CTVUPINV utility according to the specified input parameters, has the SUBSCRIBE type Y, which is not available this record type. The utility does not process the input statement causing this error, but continues to process other input statements.

Corrective Action: Check the input parameters causing this error, specify valid parameters in JCL and run the new job if necessary.

CTDV0SE INVALID DESTINATION FOR SUBSCRIBE=`X`Link copied to clipboard

Explanation:This error message can be issued by either the CTVUPINV utility or when an end-user tries to subscribe to a report using Control-D/WebAccess.

The message is issued by the CTVUPINV utility in the following cases:

for a record with SUBSCRIBE=I/E the first destination was not CTDS. Where SUBSCRIBE=I/E,only CTDS is valid.
for a record with the first printing destination is CTDS, but the second destination is empty
the DEST1 and DEST2 input parameters are not specified and the NOTIFICATION and/or E-MAIL parameters in the CTDSPARM member are incorrect or omitted.

The message is issued by the Application Server if the NOTIFICATION and/or E-MAIL parameters in the CTDSPARM member are incorrect or omitted.

Corrective Action: If the error message is issued under CTVUPINV, check the input parameters and the CTDSPARM default destination parameters. Specify valid parameters and run the new job if necessary. If the error message is issued by Application Server, define correct values in the CTDSPARM member and run the new job if necessary.

CTDV0TE YOU ARE NOT AUTHORIZED TO SUBSCRIBE FOR REPORT `jobName/username/reportName`Link copied to clipboard

Explanation:Either the CTDX024 Control-D user exit or the CTDSE24 security module on the host does not allow the current user to subscribe for report entry.

Corrective Action: Ask your INCONTROL administrator for authorization to subscribe for the report.

CTDV0UE SUBSCRIPTION TO THIS E-MAIL ADDRESS ALREADY EXISTS FOR REPORT`jobName/username/reportName`Link copied to clipboard

Explanation:The end-user tried to subscribe a report to an e-mail address, where the subscription to the address already exists.

Corrective Action:Subscribe the report with the correct e-mail address.

CTDV0VE SUBSCRIPTION CANNOT BE PERFORMED. DEFAULT SUBSCRIPTION PARAMETERS ARE NOT SET.Link copied to clipboard

Explanation:The end-user wants to receive notification or report by e-mail, but the default destination is not set in the CTDSPARM member. Subscription is not performed.

Corrective Action:Notify your INCONTROL administrator.

CTDV0WI SUBSCRIPTION PERFORMED FOR REPORT `jobName/username/reportName`Link copied to clipboard

Explanation: This information message indicates that the subscription for the report was successful.

Corrective Action:No action is required.

Messages CTDW00 through CTDWxxLink copied to clipboard

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

CTDWL0I APPLICATION SERVER CONNECTED TO WLM SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the Application server successfully connected to the WLM (Work Load Manager).

Corrective Action: No action is required.

CTDWL1I APPLICATION SERVER DISCONNECTED FROM WLM SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the Application server successfully disconnected from the WLM (Work Load Manager).

Corrective Action: No action is required.

CTDWL2E MEMBER CTDASWLM IN CTD PARM LIBRARY HAS INVALID STRUCTURELink copied to clipboard

Explanation: The structure of the CTDASWLM member in the CTD PARM library is invalid. Message CTDWL3I or CTDWL5I follows message CTDWL2E, displaying a text description of the error encountered.

The Control-D Application server continues normal processing, but does not involve the WLM to manage the response time.

Corrective Action: Fix the problem, and reload the CTDASWLM member.

CTDWL3E `inputControlStatement`Link copied to clipboard

Explanation: This message follows message CTDWL2E, and displays the control statement of the error encountered.

Corrective Action: No action is required.

CTDWL4E CONNECTION TO WLM SERVICE `service` FAILED,RC=`rc`,REASON CODE= `rsn`Link copied to clipboard

Explanation: Connection to the WLM service for the current request failed with return code of rc and a reason code of rsn.

The variables in this message are:

service - one of the following WLM services:
- IWMCONN- IWMDISC- IWMCLSFY- IWMRPT
rc - WLM return code
rsn - WLM reason code

The Control-D Application server continues normal processing, but does not involve the WLM to manage the response time for the current request.

Corrective Action: Do the following:

For an explanation of the return and reason codes, refer to IBM documentation about WLM for a description of the received return and reason codes.
Fix the problem, and reload the CTDASWLM member.

CTDWL5E GENERIC SUBSYSTEM TYPE OR SUBSYSTEM NAME IS NOT DEFINEDLink copied to clipboard

Explanation: The CTDASWLM member in the CTD PARM library does not contain the correct Generic Subsystem Type (parameter SYSNAME) or Subsystem Name (parameter SUBSYSNAME) as defined in WLM for the Application server. This message follows message CTDWL2E.

The Control-D Application server continues normal processing, but does not involve the WLM to manage the response time.

Corrective Action: Fix the problem, and reload the CTDASWLM member.

Messages CTDX00 through CTDXxxLink copied to clipboard

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

CTDX00I CTDUFEXP UTILITY STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTDUFEXP utility started.

Corrective Action: No action is required.

CTDX01E CTDX005 IS CALLED FOR AN INVALID FUNCTION `function`. REQUEST REJECTED.Link copied to clipboard

Explanation: Sample Exit Program CTDX005 was called for the function unintended function.

The request is ignored.

Corrective Action: Notify your INCONTROL administrator.

CTDX02E CONTROL CHARACTER TRANSLATION ERRORLink copied to clipboard

Explanation: An error occurred when sample Exit Program CTDX005 attempted to transfer ASA control characters to machine control characters, or vice versa.

Translation of the current record is terminated.

Corrective Action: Notify your INCONTROL administrator.

CTDX03E ABEND `abCode` OCCURED IN CONTROL-D EXIT 005Link copied to clipboard

Explanation: Abend abCode occurred during the execution of sample Exit Program CTDX005.

The current request is terminated. The Exit program returns with a return code of 12.

Corrective Action: Notify your INCONTROL administrator.

CTDX04E ABEND `abCode` OCCURED IN CONTROL-D EXIT 003Link copied to clipboard

Explanation: Abend abCode occurred during the execution of sample Exit Program CTDX003.

The current request is terminated. The Exit program returns with a return code of 12.

Corrective Action: Notify your INCONTROL administrator.

CTDX05E PRINT FILE `ddName` CANNOT BE OPENED. REPORTS WILL BE SENT TO A SPOOL.Link copied to clipboard

Explanation: Sample Exit Program CTDX005 was unable to open the ddName print file.

The print mission’s output is rerouted to a spool instead of a dataset.

Corrective Action: Notify your INCONTROL administrator.

CTDX06E FAILED TO ALLOCATE EXISTING PRINT FILE `dsName` RC= `rc` RSN= `rsn`Link copied to clipboard

Explanation: Sample Exit Program CTDX005 failed to use the existing dsName dataset for its print file.

The variables in this message are:

dsName - the dataset to be used for the print file
rc - the return code from the failed dynamic allocation request
rsn - the reason code from the failed dynamic allocation request

The Exit program tries to create a new dataset for its print file.

Corrective Action: Notify your INCONTROL administrator.

CTDX07E PRINT FILE ALLOCATION ERROR: DSNAME= `dsName` RC= `rc` RSN= `rsn`Link copied to clipboard

Explanation: Sample Exit Program CTDX005 failed to allocate the new dsName dataset for its print file.

The variables in this message are:

dsName - the dataset to be used for the print file
rc - the return code from the failed dynamic allocation request
rsn - the reason code from the failed dynamic allocation request

The print mission’s output is rerouted to a spool instead of a dataset, as described in message UXDX05E.

Corrective Action: Notify your INCONTROL administrator.

CTDX08I PRINT FILE `ddName dsName` ASSIGNED TO MISSION `misName`Link copied to clipboard

Explanation: This information message indicates that the dsName dataset was allocated for the print mission’s misName print file with ddName.

Corrective Action: Notify your INCONTROL administrator.

CTDX09W FAILED TO UNALLOCATE PRINT FILE `ddName` RC=`rc` RSN=`rsn`Link copied to clipboard

Explanation: Sample Exit Program CTDX005 failed to unallocate the ddName print file.

The variables in this message are:

ddName - the DD name to be used for the print file
rc - the return code from the failed dynamic allocation request
rsn - the reason code from the failed dynamic allocation request

The program continues with a new print file.

Corrective Action: Notify your INCONTROL administrator.

CTDX0AE CTDUFEXP UTILITY TERMINATES DUE TO AN ERROR IN THE SORTLink copied to clipboard

Explanation: The CTDUFEXP utility issues this error message when the invoked SORT utility ended with errors. The utility stops.

Corrective Action: Examine the messages issued by the SORT utility to SYSOUT to identify the problem. Make appropriate changes to the JCL and rerun the job.

CTDX0BE EXPORT RULERS IS NOT AVAILIBLE FOR `file` FILELink copied to clipboard

Explanation: The CTDUFEXP utility issues this error message when the object RULERS is specified for a file type, which is not an ACT file type. Export RULERS can be performed only from Active User file. The utility stops.

Corrective Action: Correct the input parameters according to the utility parameters description in the INCONTROL for z/OS Utilities Guide. Rerun the utility.

CTDX0CW LOCATE ERROR FOR `dsn`, RC = `rc`Link copied to clipboard

Explanation: This warning message notifies that the CTDUFEXP utility cannot locate the dsn dataset name in the MVS catalog. The utility continues to work, but the VOLSER of the volume where the problematic dataset resides is not included to the output report.

Corrective Action: Analyze the rc return code of the LOCATE macro. It is described in the IBM document: z/OS DFSMSdfp Advanced Services. Determine why the data set could not be located. Correct the problem, if possible, and rerun the CTDUFEXP utility, if necessary.

CTDX0DE PARAMETER `parm` IS NOT AVAILIBLE FOR THE REPORTS/RULERS SELECTIONLink copied to clipboard

Explanation: The CTDUFEXP utility issues this error message when the specified parm selection parameter is not available for the REPORTS or RULERS objects. The utility stops.

Corrective Action: Correct the input parameters according to the utility parameters description in the INCONTROL for z/OS Utilities Guide. Rerun the utility.

CTDX0EW LIST= `outrep` NOT AVAILIBLE FOR `file` FILELink copied to clipboard

Explanation: The CTDUFEXP utility issues this warning message when the output report specified in the LIST parameter is not available for the processed User file type. The utility continues to work, but the specified output report is not issued.

Corrective Action: No action is required.

CTDX0FW LIST= `outrep` NOT AVAILIBLE FOR `action` ACTIONLink copied to clipboard

Explanation: The CTDUFEXP utility issues this warning message when the output report specified in the LIST parameter is not available for the action performed by the utility. The utility continues to work, but the specified output report is not issued.

Corrective Action: No action is required.

CTDX0GI `number` RECORDS READ FROM `file` FILELink copied to clipboard

Explanation: This information message indicates total number of records that the CTDUFEXP utility has read from the file User file.

Corrective Action: No action is required.

CTDX0HI `number record-type` RECORDS SELECTED FOR `action`Link copied to clipboard

Explanation: This information message indicates the number of records of the record-type type that the CTDUFEXP utility has selected for the EXPORT or CLEANUP action.

Corrective Action: No action is required.

CTDX0II `number` REPORTS SELECTED FOR `action`Link copied to clipboard

Explanation: This information message indicates the number of Control-D reports that the CTDUFEXP utility has selected for the EXPORT or CLEANUP action.

Corrective Action: No action is required.

CTDX0JW THERE ARE NO REPORTS/RULERS SELECTED FOR `action`Link copied to clipboard

Explanation: This warning message indicates that the CTDUFEXP utility has selected neither reports nor rulers for the EXPORT or CLEANUP action.

Corrective Action: Examine the input selection parameters. Change them and rerun the utility if necessary.

CTDX0KE `dsn` ALREADY EXISTS. DELETE THE OLD DATASET OR CHANGE THE PACKAGE NAMELink copied to clipboard

Explanation: The CTDUFEXP utility issues this error message when it detects an output dataset in the MVS catalog with the same package name and file type as specified by the input parameters. The utility stops.

Corrective Action: Delete the old dataset outside of Control-D or change the package name in the input parameter if you want to keep the old dataset name. Rerun the utility.

CTDX0LI `number` DATASETS SELECTED FOR EXPORTLink copied to clipboard

Explanation: This information message indicates the number of datasets that the CTDUFEXP utility has selected for export.

Corrective Action: No action is required.

CTDX0MI `number` VOLUMES SELECTED FOR EXPORTLink copied to clipboard

Explanation: This information message indicates the number of volumes that the CTDUFEXP utility has selected for export.

Corrective Action: No action is required.

CTDX0NW `report-key` -REPORT IS NOT DELETED BECAUSE IT HAS NOT BEEN UNLOADED FOR EXPORT.Link copied to clipboard

Explanation: The CTDUFEXP utility performing the CLEANUP action issues this warning message if the specified report is selected for delete but it has not been previously unloaded by the utility in the EXPORT action. The utility continues to work, but the specified report is not deleted.

Corrective Action: Examine the input parameters for the utility. If it is necessary, run the utility with the EXPORT action and only then with the CLEANUP action.

CTDX0PE CLEANUP RULERS ACTION IS NOT AVAILIBLE FOR THE UTILITY.Link copied to clipboard

Explanation: The CTDUFEXP utility issues this error message when the CLEANUP RULERS action has been specified in the input parameters. This action is not available for the utility. Only reports can be cleaned-up. The utility stops.

Corrective Action: Correct the input parameters according the utility parameters description in the INCONTROL for z/OS Utilities Guide. If necessary, rerun the utility.

CTDX0QE INPUT PARAMETERS ERRORLink copied to clipboard

Explanation: This error message indicates that the CTDUFEXP utility discovered errors in the input parameters. Additional information about the errors is available in the job log. The utility stops.

Corrective Action: Examine job log for error messages describing the problem. Make any necessary corrections in the input parameters and rerun the utility.

CTDX0RE EMPTY `group-name` PARAMETERS GROUPLink copied to clipboard

Explanation: The CTDUFEXP utility issues this error message when the group-name (INCLUDE or EXCLUDE) statement is not followed with selection parameters. The utility stops.

Corrective Action: Correct the input parameters according to the utility parameters description in the INCONTROL for z/OS Utilities Guide. Rerun the utility.

CTDX0SE MEDIA NAME `mediaName` NOT FOUND IN IOASPRMLink copied to clipboard

Explanation: This message is issued by the CTDUFEXP utility when printing the ‘List of exported datasets’ report, if a media name is not found in the IOASPRM member.

The variable in this message, mediaName, contains the media name of the migrated report.

The corresponding entry in the ‘List of exported datasets’ report has an empty SIZE value.

The utility continues to work.

Corrective Action: Add the media name, mediaName, as specified in the message, to the IOASPRM member and rerun the CTDUFEXP utility.

CTDX0TE CENTERA INIT ERROR: RC= `rc`, REASON CODE= `rsn`Link copied to clipboard

Explanation: Connection to EMC Centera cannot be established. This message is followed by message MIG5E9I, which issues the Centera pool value used for connection.

The variables in this message are:

rc - return code from the EMC Centera API.
rsn - reason code from the EMC Centera API.

The ‘List of exported datasets’ report issued by the CTDUFEXP utility has empty SIZE column for all entries related to the CENTERA media.

The utility continues to work.

Corrective Action: Refer to EMC Centera documentation for a description of the received reason code. Check the pool value printed in the accompanying MIG5E9I message. If the IP addresses are not correct, update them in parameters POOL1-POOL4 in the IOASPRM member. Then rerun the CTDUFEXP utility.

CTDX0UI CLIP_ID= `clipId`Link copied to clipboard

Explanation: This information message follows message CTDX0VE. The clip ID related to the message CTDX0VE is issued, where clipId is the CENTERA clip ID.

Corrective Action: No action is required.

CTDX0VE CENTERA READ ERROR RC=`rc`, REASON CODE=`rsc`, BLN=`blk`, L=`len`Link copied to clipboard

Explanation: The CTDUFEXP utility issues this message when an error is detected while reading a block from the EMC Centera clip. This message is followed by message CTDX0UI, which issues the problematic Centera clip name.

The variables in this message are:

rc - return code from the EMC Centera API
rsn - reason code from the EMC Centera API
blk - error block number
len - returned block length

Corrective Action: Refer to the EMC Centera documentation for a description of the received reason code. Rerun the CTDUFEXP utility, if necessary.

CTDX10I CTDRETC UTILITY STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTDRETC utility started.

Corrective Action: No action is required.

CTDX11I CTDRETC UTILITY COMPLETED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the CTDRETC utility completed successfully.

Corrective Action: No action is required.

CTDX12E CTDRETC UTILITY ENDED WITH ERRORSLink copied to clipboard

Explanation: This error message indicates that the CTDRETC utility discovered problems during processing. Additional information about the problems is available in the job log. The utility stops.

Corrective Action: Examine the job log for error messages describing the problem. Make any necessary corrections and rerun the utility.

CTDX13E THE ACTION STATEMENT PRESERVE/FREE/CHANGE/DELREP/PRINT IS MISSINGLink copied to clipboard

Explanation: This error message indicates that the statement that defines the action of the CTDRETC utility is missing in the input parameters. The utility stops.

Corrective Action: Specify the one of following actions: PRESERVE, FREE, CHANGE, DELREP, or PRINT as the first statement in the SYSIN DD input parameters stream in JCL. Rerun the utility.

CTDX14E INVALID PARAMETER: `parm`Link copied to clipboard

Explanation: The parm input parameter specified in the JCL for the CTDRETC utility is not valid. The utility stops.

Corrective Action: Correct the invalid input parameter (parm) in the JCL and rerun the job.

CTDX15E THE PARAMETER `parm` MUST BE SPECIFIEDLink copied to clipboard

Explanation: The mandatory parm input parameter for the CTDRETC utility is missing. The utility stops.

Corrective Action: Add the missing parameter to the JCL and rerun the job.

CTDX16E REDUNDANT PARAMETER: `parm`Link copied to clipboard

Explanation: The parm input parameter for the CTDRETC utility has already been specified. The utility stops.

Corrective Action: Remove the extra input parameter from the input parameter stream in JCL and rerun the job.

CTDX17E SELECTION PARAMETER `parm` IS NOT AVAILIBLE FOR `action` ACTIONLink copied to clipboard

Explanation: The parm input selection parameter is not available for the action action specified as the first statement in the input stream for the CTDRETC utility. The utility stops.

Corrective Action: Remove the parm selection parameter from the input parameter stream in JCL and rerun the job.

CTDX18E PARAMETER `parm` LENGTH EXCEEDEDLink copied to clipboard

Explanation: The length of the parm input parameter exceeds the maximum available for this parameter length. The utility stops.

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

CTDX19E SELECTION PARAMETER `parm` IS NOT AVAILIBLE FOR `file` FILELink copied to clipboard

Explanation: The input parm selection parameter is not available for the file file type specified in the DBFILE input parameter for the CTDRETC utility. The utility stops.

Corrective Action: Remove the parm selection parameter from the input parameters stream in JCL and rerun the job.

CTDX1AE CTDRETC UTILITY TERMINATES DUE TO AN ERROR IN THE SORTLink copied to clipboard

Explanation: The CTDRETC utility issues this error message when the invoked SORT utility ended with errors. The utility stops.

Corrective Action: Examine the messages issued by the SORT utility to SYSOUT to identify the problem. Make appropriate changes to the JCL and rerun the job.

CTDX1CW LOCATE ERROR FOR `dsn`, RC = `rc`Link copied to clipboard

Explanation: This warning message notifies that the CTDRETC utility cannot locate the dsn dataset name in the MVS catalog. The utility continues to work, but the VOLSER of the volume where the problematic dataset resides is not included to the output report.

CTDX1FW LIST= `outrep` NOT AVAILIBLE FOR `action` ACTIONLink copied to clipboard

Explanation: The CTDRETC utility issues this warning message when the output report specified in the LIST parameter is not available for the action performed by the utility. The utility continues to work, but the specified output report is not issued.

Corrective Action: No action is required.

CTDX1GI `number` RECORDS READ FROM `file` FILELink copied to clipboard

Explanation: This information message indicates total number of records that the CTDRETC utility has read from the file User file.

Corrective Action: No action is required.

CTDX1HI `number record-type` RECORDS SELECTED FOR `action`Link copied to clipboard

Explanation: This information message indicates the number of records of the record-type type that the CTDRETC utility has selected for the performed action.

Corrective Action: No action is required.

CTDX1II `number` REPORTS SELECTED FOR `action`Link copied to clipboard

Explanation: This information message indicates the number of Control-D reports that the CTDRETC utility has selected for the performed action.

Corrective Action: No action is required.

CTDX1JW THERE ARE NO REPORTS SELECTED FOR `action`Link copied to clipboard

Explanation: This warning message indicates that the CTDRETC utility has selected no reports for the performed action.

Corrective Action: Examine the input selection parameters. If necessary, change them and rerun the utility.

CTDX1LI `number` DATASETS SELECTED FOR `action`Link copied to clipboard

Explanation: This information message indicates the number of datasets that the CTDRETC utility has selected for the performed action.

Corrective Action: No action is required.

CTDX1MI `number` VOLUMES SELECTED FOR EXPORTLink copied to clipboard

Explanation: This information message indicates the number of volumes that the CTDRETC utility has selected for the performed action.

Corrective Action: No action is required.

CTDX1PE SELECTION PARAMETER `parm` IS NOT AVAILABLE IN EXCLUDE STATEMENTLink copied to clipboard

Explanation: The parm input selection parameter is not available in the EXCLUDE statement of the input stream for the CTDRETC utility. This parameter is only available in the INCLUDE statement. The utility stops.

Corrective Action: Remove the parm selection parameter, which is unavailable, from the JCL input parameter stream and rerun the job.

CTDX1QE INPUT PARAMETERS ERRORLink copied to clipboard

Explanation: This error message indicates that the CTDRETC utility discovered errors in the input parameters. Additional information about the errors is available in the job log. The utility stops.

Corrective Action: Examine the job log for error messages describing the problem. Make any necessary corrections in the input parameters and rerun the utility.

CTDX1RE EMPTY `group-name` PARAMETERS GROUPLink copied to clipboard

Explanation: The CTDRETC utility issues this error message when the group-name (INCLUDE or EXCLUDE) statement is not followed with selection parameters. The utility stops.

Corrective Action: Correct the input parameters according to the utility parameters description in the INCONTROL for z/OS Utilities Guide. Rerun the utility.

CTDX21I CTDUFEXP UTILITY COMPLETED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the CTDUFEXP utility completed successfully

Corrective Action: No action is required.

CTDX22E CTDUFEXP UTILITY ENDED WITH ERRORSLink copied to clipboard

Explanation: This error message indicates that the CTDUFEXP utility discovered problems during processing. Additional information on the problems is available in the job log. The utility stops.

Corrective Action: Examine job log for error messages describing the problem. Make any necessary corrections and rerun the utility.

CTDX23E THE ACTION STATEMENT EXPORT OR CLEANUP IS MISSINGLink copied to clipboard

Explanation: This error message indicates that the statement that defines the action of the CTDUFEXP utility is missing in the input parameters. The utility stops.

Corrective Action: Specify the requested action (EXPORT or CLEANUP) as first statement in the SYSIN DD input parameters stream in JCL. Rerun the utility.

CTDX24E INVALID PARAMETER: `parm`Link copied to clipboard

Explanation: The parm input parameter specified in the JCL for the CTDUFEXP utility is not valid. The utility stops.

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

CTDX25E THE PARAMETER `parm` MUST BE SPECIFIEDLink copied to clipboard

Explanation: The mandatory parm input parameter for the CTDUFEXP utility is missing. The utility stops.

Corrective Action: Add the missing parameter to the JCL and rerun the job.

CTDX26E REDUNDANT PARAMETER: `parm`Link copied to clipboard

Explanation: The parm input parameter for the CTDUFEXP utility has already been specified. The utility stops.

Corrective Action: Remove the extra input parameter from the input parameters stream in JCL and rerun the job.

CTDX27E NEITHER REPORTS NOR RULERS ARE SPECIFIED BY INPUT PARAMETERSLink copied to clipboard

Explanation: The statement defining the objects to be processed by the CTDUFEXP utility (REPORTS or/and RULERS) is missing in the input parameters. The input parameters stream must contain at least one of these statements. The utility stops.

Corrective Action: Add the REPORTS or RULERS statement to the input parameters stream in JCL and rerun the job.

CTDX28E PARAMETER `parm` LENGTH EXCEEDEDLink copied to clipboard

Explanation: The length of the parm input parameter exceeds the maximum available length for this parameter. The utility stops.

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

CTDX29E SELECTION PARAMETER `parm` IS NOT AVAILIBLE FOR `file` FILELink copied to clipboard

Explanation: The input parm selection parameter is not available for the file file type specified by the DBFILE input parameter for the CTDUFEXP utility. The utility stops.

Corrective Action: Remove the selection parameter from the input parameter stream in JCL and rerun the job.

CTDX30I CTDREPUS UTILITY STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTDREPUS utility started.

Corrective Action:No action is required.

CTDX31I CTDREPUS UTILITY COMPLETED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the CTDREPUS utility completed successfully.

Corrective Action: No action is required.

CTDX32E CTDREPUS UTILITY ENDED WITH ERRORSLink copied to clipboard

Explanation: This error message indicates that the CTDREPUS utility discovered problems during processing. Additional information on the problems discovered is available in the job log. The utility stops.

Corrective Action: Examine the job log for error messages describing the problem. Make any necessary corrections and rerun the utility.

CTDX32I CTDDBSTB UTILITY STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTDDBSTB utility started.

Corrective Action: No action is required.

CTDX33I CTDDBSTB UTILITY COMPLETED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the CTDDBSTB utility completed successfully.

Corrective Action: No action is required.

CTDX34E INVALID PARAMETER:`parm`Link copied to clipboard

Explanation: The parm parameter specified in the JCL for the CTDREPUS utility is not valid. The utility stops.

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

CTDX36E INVALID PARAMETER:`parm`Link copied to clipboard

Explanation: The parm parameter for the CTDREPUS utility has already been specified. The parameter must only be specified once. The utility stops.

Corrective Action:Remove the extra input parameter from the input parameters stream in the JCL and rerun the job.

CTDX38E PARAMETER `parm` LENGTH EXCEEDEDLink copied to clipboard

Explanation: The length of the parm input parameter exceeds the maximum allowable length for this parameter. The utility stops.

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

CTDX3AE CTDREPUS UTILITY TERMINATES DUE TO AN ERROR IN THE SORTLink copied to clipboard

Explanation: The CTDREPUS utility issues this error message when the invoked SORT utility ended with errors. The utility stops.

Corrective Action: Examine the messages issued by the SORT utility to SYSOUT to identify the problem. Make appropriate changes to the JCL and rerun the job.

CTDX3CW LOCATE ERROR FOR `dsn`, RC = `rc`Link copied to clipboard

Explanation: This warning message notifies that the CTDREPUS utility cannot locate the dataset name dsn in the MVS catalog. The utility continues to work, but the VOLSER of the volume where the problematic dataset resides is not included to the output report.

Corrective Action: Analyze rc return code of the LOCATE macro. It is described in the IBM document: z/OS DFSMSdfp Advanced Services. Determine why the dataset could not be located. If possible, correct the problem and rerun the CTDREPUS utility if necessary.

CTDX3HI `number` REPORT ENTRIES SELECTED FOR PROCESSINGLink copied to clipboard

Explanation: This information message indicates the number of report entries that the CTDREPUS utility has selected for processing.

Corrective Action: No action is required.

CTDX3II `number` REPORTS HAVE BEEN PROCESSEDLink copied to clipboard

Explanation: This information message indicates the number of Control-D reports that have been processed.

Corrective Action: No action is required.

CTDX3JI `number` USER RECORDS HAVE BEEN PROCESSEDLink copied to clipboard

Explanation: This information message indicates how many user records were processed by the CTDDBSTB utility.

Corrective Action: No action is required.

CTDX3JW NO REPORT ENTRIES HAVE BEEN SELECTEDLink copied to clipboard

Explanation: This warning message indicates that the CTDREPUS utility has not selected any reports that satisfy the specified criteria.

Corrective Action: Examine the input criteria. If necessary, change them and rerun the utility.

CTDX3KI `number` RECORDS IN FILELink copied to clipboard

Explanation: This information message indicates how many records were found in file.

Corrective Action: No action is required.

CTDX3KW NO USER RECORDS HAVE BEEN SELECTEDLink copied to clipboard

Explanation: No user records were found that match the selection parameters submitted to the CTDDBSTB utility.

Corrective Action: Correct the selection criteria.

CTDX3LI `number` SYSDATA RECORDS HAVE BEEN PROCESSEDLink copied to clipboard

Explanation: This information message indicates how many SYSDATA records were processed by the CTDDBSTB utility.

Corrective Action: No action is required.

CTDX3MI `number` SRT2E35 USER RECORDS HAVE BEEN PROCESSEDLink copied to clipboard

Explanation: This information message indicates how many user records from SRT2E35 were processed by the CTDDBSTB utility.

Corrective Action: No action is required.

CTDX3MW THE VALUE OF THE PARAMETER LENGTH WAS CHANGED TO MAXIMUM FOR THE FIELD.Link copied to clipboard

Explanation: This warning message indicates that the LENGTH parameter has been changed to the maximum value for the FIELD parameter.

Corrective Action: No action is required.

CTDX3NI `number` SRT3E35 RECORDS HAVE BEEN PROCESSEDLink copied to clipboard

Explanation: This information message indicates how many records from SRT3E35 were processed by the CTDDBSTB utility.

Corrective Action: No action is required.

CTDX3OI `number` SUMMARY RECORDS HAVE BEEN PROCESSEDLink copied to clipboard

Explanation: This information message indicates how many summary records were processed by the CTDDBSTB utility.

Corrective Action: No action is required.

CTDX3PI `number` SUMMARY OF RECORDS LESS ONE PERCENTLink copied to clipboard

Explanation: This information message provides information about the number of processed records.

Corrective Action: No action is required.

CTDX3QE INPUT PARAMETERS ERRORLink copied to clipboard

Explanation: This error message indicates that the CTDREPUS utility discovered errors in the input parameters. Additional information about the errors is available in the job log. The utility stops.

Corrective Action: Examine the job log for error messages describing the problem. Make any necessary corrections and rerun the utility.

CTDX3RI USER RECORDS HAVE BEEN SELECTED FOR PROCESSINGLink copied to clipboard

Explanation: This information message indicates the number of user records that the CTDDBSTB utility has selected for processing.

Corrective Action: No action is required.

CTDX3SI USER TOTAL VALUES HAVE BEEN PROCESSEDLink copied to clipboard

Explanation: This information message indicates the number of records in the output report for the CTDDBSTB utility.

Corrective Action: No action is required.

CTDX40I CTDNREOR UTILITY STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTDNREOR utility started.

Corrective Action: No action is required.

CTDX41I CTDNREOR UTILITY COMPLETED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the CTDNREOR utility completed successfully.

Corrective Action: No action is required.

CTDX42E CTDNREOR UTILITY ENDED WITH ERRORSLink copied to clipboard

Explanation: This error message indicates that the CTDNREOR utility discovered problems during processing. Additional information on the problems discovered is available in the job log.

Corrective Action: Examine the job log for error messages describing the problem. If necessary, make any necessary corrections and rerun the utility.

CTDX44E INVALID PARAMETER: `parm`Link copied to clipboard

Explanation: The parm input parameter specified in the JCL for the CTDNREOR utility is not valid. The utility stops.

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

CTDX45E THE PARAMETER `parm` MUST BE SPECIFIEDLink copied to clipboard

Explanation: The mandatory parm input parameter for the CTDNREOR utility is missing. The utility stops.

Corrective Action: Add the missing parameter to the JCL and rerun the job.

CTDX46E REDUNDANT PARAMETER: `parm`Link copied to clipboard

Explanation: The parm input parameter for the CTDNREOR utility has already been specified. The utility stops.

Corrective Action: Remove the extra input parameter from the input parameter stream in the JCL and rerun the job.

CTDX48E PARAMETER `parm` LENGTH EXCEEDEDLink copied to clipboard

Explanation: The length of the parm input parameter exceeds the maximum allowable length for this parameter. The utility stops.

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

CTDX4AE CTDNREOR UTILITY TERMINATES DUE TO AN ERROR IN THE SORTLink copied to clipboard

Explanation: The CTDNREOR utility issues this error message when the invoked SORT utility ended with errors. The utility stops.

Corrective Action: Examine the messages issued by the SORT utility to SYSOUT to identify the problem. Make appropriate changes to the JCL and rerun the job.

CTDX4BI `number` REPORTS HAVE BEEN PROCESSEDLink copied to clipboard

Explanation: This information message indicates the number of Control-D report entries containing Notepad records with the old format that have been processed by the CTDNREOR utility.

Corrective Action: No action is required.

CTDX4CI `number` OLD NOTEPAD RECORDS HAVE BEEN PROCESSEDLink copied to clipboard

Explanation: This information message indicates the number of Notepad records with the old format that have been processed by the CTDNREOR utility.

Corrective Action: No action is required.

CTDX4DI `number` NEW NOTEPAD RECORDS HAVE BEEN CREATEDLink copied to clipboard

Explanation: This information message indicates the number of Notepad records with the new format that have been created by the CTDNREOR utility.

Corrective Action: No action is required.

CTDX4JW NO REPORTS WITH OLD NOTEPAD RECORDS HAVE BEEN FOUNDLink copied to clipboard

Explanation: This warning message indicates that the CTDNREOR utility has found no reports containing Notepad records with the old format requiring reorganization.

Corrective Action:Examine the input selection parameters. If necessary, change them and rerun the utility.

CTDX4LE CONTROL-D IS ACTIVE IN COMPATIBILITY MODE, UTILITY RUNNING IS NOT ALLOWEDLink copied to clipboard

Explanation: This error message indicates that the CTDNREOR utility has been submitted when Control-D is running in compatibility mode with a version less than 8.0.00. The utility is not allowed to run in this mode, since the Notes created by the utility are not accessible if the customer falls back to the old version.

The utility stops with return code 8.

Corrective Action:Submit the utility after Control-D is running in full (incompatibility) mode.

CTB–CTD

CTB MessagesLink copied to clipboard

Messages CTB0 through CTB0xxLink copied to clipboard

CTB001I CONTROL-M/ANALYZER RUNTIME ENVIRONMENT STARTED - MODE IS modeType SCOPE IS scopeLink copied to clipboard

CTB002I CONTROL-M/ANALYZER RUNTIME ENVIRONMENT ENDEDLink copied to clipboard

CTB003S INTERNAL ERROR IN COMMAND DO cmdLink copied to clipboard

CTB004E LEVEL SPECIFIED IN DO EXTRACT (lvl1) IS GREATER THAN HIGHEST EXISTING LEVEL (lvl2)Link copied to clipboard

CTB005E LINE FROM WHICH TO EXTRACT (lin) NOT WITHIN THE LINE RANGE (fromline-toline) CURRENTLY IN MEMORYLink copied to clipboard

CTB006E LENGTH TO EXTRACT (charas) EXCEEDS THE MAXIMUM ALLOWABLE LENGTH (max_charas)Link copied to clipboard

CTB007E LINE TO FIND (lin) NOT WITHIN THE LINE RANGE (fromline-toline) CURRENTLY IN MEMORYLink copied to clipboard

CTB008E FROM COL (fromcol) SHOULD BE GREATER THAN TO COL (tocol)Link copied to clipboard

CTB009I GROUP-MODE IS modeTypeLink copied to clipboard

CTB00BI CONTROL-M/ANALYZER IS RUNNING IN "DEFINE" MODE (NO ACTIONS PERFORMED)Link copied to clipboard

CTB010E COMPILATION ERROR FOR RULE ruleName RC= rcLink copied to clipboard

CTB011E MEMORY ALLOCATION ERROR WHILE LOADING RULE ruleNameLink copied to clipboard

CTB012I WHILE PROCESSING COMMAND DO cmdLink copied to clipboard

CTB013I ENDED result COMMITTED num VARIABLE(S) USER RC= rcLink copied to clipboard

CTB015E NO GROUP SPECIFIED FOR CONTROL-M/ANALYZER INVOCATIONLink copied to clipboard

CTB016E BLOCK blk DOES NOT EXISTLink copied to clipboard

CTB017E COLUMN RANGE TO EXTRACT col1-col2 IS BEYOND LINE LENGTH lenLink copied to clipboard

CTB020W NEGATIVE COLUMN VALUE (col_val) SPECIFIED WHEN SEARCHING FOR "string"Link copied to clipboard

CTB021E STRING IN WHEN DOES NOT FIT THE SPECIFIED COLUMN RANGELink copied to clipboard

CTB022E FROM LINE (fromline) GREATER THAN TO LINE (toline) IN WHEN, LEVEL= lvl, SEARCH STRING=" string"Link copied to clipboard

CTB023E FROM COL (fromcol) GREATER THAN TO COL (tocol) IN WHEN, LEVEL= lvl, SEARCH STRING="string"Link copied to clipboard

CTB024E FROM LINE (fromline) GREATER THAN TO LINE (toline) IN STOP, LEVEL= lvl, SEARCH STRING="string"Link copied to clipboard

CTB025E FROM COL (fromcol) GREATER THAN TO COL (tocol) IN STOP, LEVEL= lvl, SEARCH STRING="string"Link copied to clipboard

CTB026E NO DATA MATCHING WHEN CRITERIALink copied to clipboard

CTB030E DATABASE VARIABLE NOT FOUND: DB_ grp.var (GEN= generationNum DATE= date KEY= key)Link copied to clipboard

CTB031E VARIABLE NOT FOUND: varNameLink copied to clipboard

CTB032E DATABASE VARIABLES ALREADY COMMITTED. RUN ID " runId" CANNOT BE SETLink copied to clipboard

CTB033E CANNOT SET SYSTEM VARIABLE varNameLink copied to clipboard

CTB034E DATABASE VARIABLE DB_ grp.var DOES NOT EXISTLink copied to clipboard

CTB035E ERROR PARSING LINE " line". LINE SKIPPEDLink copied to clipboard

CTB036E ERROR PARSING VARIABLE: VAR= varName VAL=" value"Link copied to clipboard

CTB037E AUTOEDIT MEMBER lib (memName) ALREADY LOADEDLink copied to clipboard

CTB038E AUTOEDIT MEMBER lib (memName) NOT PREVIOUSLY LOADEDLink copied to clipboard

CTB03AI WHILE PROCESSING AUTOEDIT MEMBER lib (memName)Link copied to clipboard

CTB03BW AUTOEDIT VARIABLE varName ALREADY EXISTS IN MEMBER lib (memName)Link copied to clipboard

CTB03CE AUTOEDIT VARIABLE varName ALREADY EXISTS IN ANOTHER MEMBER: memNameLink copied to clipboard

CTB03DE VARIABLE varName IS NOT AN AUTOEDIT VARIABLE. CANNOT PERFORM ADDSYMLink copied to clipboard

CTB040E INVALID SEARCH CRITERIA FOR DATABASE VARIABLELink copied to clipboard

CTB041S INTERNAL ERROR IN modName: OPT= optn RC= rcLink copied to clipboard

CTB045E ERROR COMMITTING DB _grp.varLink copied to clipboard

CTB046E DATABASE VARIABLE NOT PREVIOUSLY SET: DB_ grp.varLink copied to clipboard

CTB047E ERROR CREATING DB_ grp.varLink copied to clipboard

CTB048E UNABLE TO COMMIT var. VARIABLE WAS PASSED AS AN ARGUMENT TO THE BLOCK/RULELink copied to clipboard

CTB050E MEMORY ALLOCATION ERROR IN AUTOEDITLink copied to clipboard

CTB051E UNRESOLVED AUTOEDIT SYMBOL: " string"Link copied to clipboard

CTB052E EMPTY AUTOEDIT SYMBOL: " string"Link copied to clipboard

CTB053E INVALID AUTOEDIT SYNTAX: " string"Link copied to clipboard

CTB054E RESOLVED AUTOEDIT STATEMENT EXCEEDS MAXIMUM LENGTH. ORIGINAL STATEMENT=" string"Link copied to clipboard

CTB055E TOO MANY BLANKS TO RESOLVE IN AUTOEDIT: " string"Link copied to clipboard

CTB056S INTERNAL ERROR IN CTBCAE: STRING= string RC= rcLink copied to clipboard

CTB057W VALUE val OF varName DOES NOT FIT ITS FORMATLink copied to clipboard

CTB058E LENGTH HAS TO BE GREATER THAN PRECISION IN FORMAT OF varNameLink copied to clipboard

CTB060E INVALID GROUP NAME IN: " dbRefStatement"Link copied to clipboard

CTB061E INVALID VARIABLE NAME IN: " dbRefStatement"Link copied to clipboard

CTB062E INVALID GENERATION ID IN: " dbRefStatement"Link copied to clipboard

CTB063E INVALID KEY VALUE IN: " dbRefStatement"Link copied to clipboard

CTB064E INVALID RUN ID IN: " dbRefStatement"Link copied to clipboard

CTB065E INVALID DATE IN: " dbRefStatement"Link copied to clipboard

CTB066E A CATEGORY APPEARS TWICE IN: " dbRefStatement"Link copied to clipboard

CTB067E INVALID PLACEMENT OF "." IN: " dbRefStatement"Link copied to clipboard

CTB068E SPECIFIED CATEGORY INVALID IN CURRENT CONTEXT. STRING= " dbRefStatement"Link copied to clipboard

CTB069E INVALID CATEGORY IDENTIFIER IN: " dbRefStatement"Link copied to clipboard

CTB06AS INTERNAL ERROR. INVALID PREFIX IN: " dbRefStatement"Link copied to clipboard

CTB06BS INTERNAL ERROR IN CTBCNMP: STRING= " dbRefStatement" RC= rc IS INVALIDLink copied to clipboard

CTB06CE USER MODULE modName NOT FOUNDLink copied to clipboard

CTB070E SYNTAX ERROR IN EVALUATION ROUTINE (POS n), INPUT=" expression"Link copied to clipboard

CTB071E UNBALANCED PARENTHESES IN EVALUATION ROUTINE (POS n), INPUT=" expression"Link copied to clipboard

CTB072E SYMBOL ERROR IN EVALUATION ROUTINE (POS n), INPUT=" expression"Link copied to clipboard

CTB073E TOO MANY COMMAS IN EVALUATION ROUTINE (POS n), INPUT=" expression"Link copied to clipboard

CTB074E INVALID NUMBER OF COMMAS IN EVALUATION ROUTINE (POS n), INPUT=" expression"Link copied to clipboard

CTB075E INTERNAL ERROR IN EVALUATION ROUTINE (ERR error), INPUT=" expression"Link copied to clipboard

CTB076E VARIABLE NOT FOUND IN EVALUATION ROUTINE (POS num), INPUT= exprLink copied to clipboard

CTB077E SCAN ERROR IN EVALUATION ROUTINE (POS n), INPUT=" expr"Link copied to clipboard

CTB078E INTERNAL ERROR IN CTBEVAL: INPUT=" expr" RC= rc IS INVALIDLink copied to clipboard

CTB079E MAXIMUM VARIABLE SIZE EXCEEDED (POS n), INPUT=" expr"Link copied to clipboard

CTB07AE UNABLE TO ALLOCATE MEMORY IN EVALUATION ROUTINE (POS n), INPUT=" expr"Link copied to clipboard

CTB07BE VARIABLE NOT FOUND IN EVALUATION ROUTINE (POS n), INPUT=" expr"Link copied to clipboard

CTB003S INTERNAL ERROR IN COMMAND DO `cmd`Link copied to clipboard

CTB004E LEVEL SPECIFIED IN DO EXTRACT (`lvl1`) IS GREATER THAN HIGHEST EXISTING LEVEL (`lvl2`)Link copied to clipboard

CTB005E LINE FROM WHICH TO EXTRACT (`lin`) NOT WITHIN THE LINE RANGE (`fromline-toline`) CURRENTLY IN MEMORYLink copied to clipboard

CTB006E LENGTH TO EXTRACT (`charas`) EXCEEDS THE MAXIMUM ALLOWABLE LENGTH (`max_charas`)Link copied to clipboard

CTB007E LINE TO FIND (`lin`) NOT WITHIN THE LINE RANGE (`fromline-toline`) CURRENTLY IN MEMORYLink copied to clipboard

CTB008E FROM COL (`fromcol`) SHOULD BE GREATER THAN TO COL (`tocol`)Link copied to clipboard

CTB009I GROUP-MODE IS `modeType`Link copied to clipboard

CTB010E COMPILATION ERROR FOR RULE `ruleName` RC= `rc`Link copied to clipboard

CTB011E MEMORY ALLOCATION ERROR WHILE LOADING RULE `ruleName`Link copied to clipboard

CTB012I WHILE PROCESSING COMMAND DO `cmd`Link copied to clipboard

CTB013I ENDED `result` COMMITTED `num` VARIABLE(S) USER RC= `rc`Link copied to clipboard

CTB016E BLOCK `blk` DOES NOT EXISTLink copied to clipboard

CTB017E COLUMN RANGE TO EXTRACT `col1-col2` IS BEYOND LINE LENGTH `len`Link copied to clipboard

CTB020W NEGATIVE COLUMN VALUE (`col_val`) SPECIFIED WHEN SEARCHING FOR "`string`"Link copied to clipboard

CTB022E FROM LINE (`fromline`) GREATER THAN TO LINE (`toline`) IN WHEN, LEVEL= `lvl`, SEARCH STRING=" `string`"Link copied to clipboard

CTB023E FROM COL (`fromcol`) GREATER THAN TO COL (`tocol`) IN WHEN, LEVEL= `lvl`, SEARCH STRING="`string`"Link copied to clipboard

CTB024E FROM LINE (`fromline`) GREATER THAN TO LINE (`toline`) IN STOP, LEVEL= `lvl`, SEARCH STRING="`string`"Link copied to clipboard

CTB025E FROM COL (`fromcol`) GREATER THAN TO COL (`tocol`) IN STOP, LEVEL= `lvl`, SEARCH STRING="`string`"Link copied to clipboard

CTB030E DATABASE VARIABLE NOT FOUND: DB_ `grp.var` (GEN= `generationNum` DATE= `date` KEY= `key`)Link copied to clipboard

CTB031E VARIABLE NOT FOUND: `varName`Link copied to clipboard

CTB032E DATABASE VARIABLES ALREADY COMMITTED. RUN ID " `runId`" CANNOT BE SETLink copied to clipboard

CTB033E CANNOT SET SYSTEM VARIABLE `varName`Link copied to clipboard

CTB034E DATABASE VARIABLE DB_ `grp`.var DOES NOT EXISTLink copied to clipboard

CTB035E ERROR PARSING LINE " `line`". LINE SKIPPEDLink copied to clipboard

CTB036E ERROR PARSING VARIABLE: VAR= `varName` VAL=" `value`"Link copied to clipboard

CTB037E AUTOEDIT MEMBER `lib` (`memName`) ALREADY LOADEDLink copied to clipboard

CTB038E AUTOEDIT MEMBER `lib` (`memName`) NOT PREVIOUSLY LOADEDLink copied to clipboard

CTB03AI WHILE PROCESSING AUTOEDIT MEMBER `lib` (`memName`)Link copied to clipboard

CTB03BW AUTOEDIT VARIABLE `varName` ALREADY EXISTS IN MEMBER `lib` (`memName`)Link copied to clipboard

CTB03CE AUTOEDIT VARIABLE `varName` ALREADY EXISTS IN ANOTHER MEMBER: `memName`Link copied to clipboard

CTB03DE VARIABLE `varName` IS NOT AN AUTOEDIT VARIABLE. CANNOT PERFORM ADDSYMLink copied to clipboard

CTB041S INTERNAL ERROR IN `modName`: OPT= `optn` RC= `rc`Link copied to clipboard

CTB045E ERROR COMMITTING DB `_grp.var`Link copied to clipboard

CTB046E DATABASE VARIABLE NOT PREVIOUSLY SET: DB_ `grp.var`Link copied to clipboard

CTB047E ERROR CREATING DB_ `grp.var`Link copied to clipboard

CTB048E UNABLE TO COMMIT `var`. VARIABLE WAS PASSED AS AN ARGUMENT TO THE BLOCK/RULELink copied to clipboard

CTB051E UNRESOLVED AUTOEDIT SYMBOL: " `string`"Link copied to clipboard

CTB052E EMPTY AUTOEDIT SYMBOL: " `string`"Link copied to clipboard

CTB053E INVALID AUTOEDIT SYNTAX: " `string`"Link copied to clipboard

CTB054E RESOLVED AUTOEDIT STATEMENT EXCEEDS MAXIMUM LENGTH. ORIGINAL STATEMENT=" `string`"Link copied to clipboard

CTB055E TOO MANY BLANKS TO RESOLVE IN AUTOEDIT: " `string`"Link copied to clipboard

CTB056S INTERNAL ERROR IN CTBCAE: STRING= `string` RC= `rc`Link copied to clipboard

CTB057W VALUE `val` OF `varName` DOES NOT FIT ITS FORMATLink copied to clipboard

CTB058E LENGTH HAS TO BE GREATER THAN PRECISION IN FORMAT OF `varName`Link copied to clipboard

CTB060E INVALID GROUP NAME IN: " `dbRefStatement`"Link copied to clipboard

CTB061E INVALID VARIABLE NAME IN: " `dbRefStatement`"Link copied to clipboard

CTB062E INVALID GENERATION ID IN: " `dbRefStatement`"Link copied to clipboard

CTB063E INVALID KEY VALUE IN: " `dbRefStatement`"Link copied to clipboard

CTB064E INVALID RUN ID IN: " `dbRefStatement`"Link copied to clipboard

CTB065E INVALID DATE IN: " `dbRefStatement`"Link copied to clipboard

CTB066E A CATEGORY APPEARS TWICE IN: " `dbRefStatement`"Link copied to clipboard

CTB067E INVALID PLACEMENT OF "." IN: " `dbRefStatement`"Link copied to clipboard

CTB068E SPECIFIED CATEGORY INVALID IN CURRENT CONTEXT. STRING= " `dbRefStatement`"Link copied to clipboard

CTB069E INVALID CATEGORY IDENTIFIER IN: " `dbRefStatement`"Link copied to clipboard

CTB06AS INTERNAL ERROR. INVALID PREFIX IN: " `dbRefStatement`"Link copied to clipboard

CTB06BS INTERNAL ERROR IN CTBCNMP: STRING= " `dbRefStatement`" RC= `rc` IS INVALIDLink copied to clipboard

CTB06CE USER MODULE `modName` NOT FOUNDLink copied to clipboard

CTB070E SYNTAX ERROR IN EVALUATION ROUTINE (POS `n`), INPUT=" `expression`"Link copied to clipboard

CTB071E UNBALANCED PARENTHESES IN EVALUATION ROUTINE (POS `n`), INPUT=" `expression`"Link copied to clipboard

CTB072E SYMBOL ERROR IN EVALUATION ROUTINE (POS `n`), INPUT=" `expression`"Link copied to clipboard

CTB073E TOO MANY COMMAS IN EVALUATION ROUTINE (POS `n`), INPUT=" `expression`"Link copied to clipboard

CTB074E INVALID NUMBER OF COMMAS IN EVALUATION ROUTINE (POS `n`), INPUT=" `expression`"Link copied to clipboard

CTB075E INTERNAL ERROR IN EVALUATION ROUTINE (ERR `error`), INPUT=" `expression`"Link copied to clipboard

CTB076E VARIABLE NOT FOUND IN EVALUATION ROUTINE (POS `num`), INPUT= `expr`Link copied to clipboard

CTB077E SCAN ERROR IN EVALUATION ROUTINE (POS `n`), INPUT=" `expr`"Link copied to clipboard

CTB078E INTERNAL ERROR IN CTBEVAL: INPUT=" `expr`" RC= `rc` IS INVALIDLink copied to clipboard

CTB079E MAXIMUM VARIABLE SIZE EXCEEDED (POS `n`), INPUT=" `expr`"Link copied to clipboard

CTB07AE UNABLE TO ALLOCATE MEMORY IN EVALUATION ROUTINE (POS `n`), INPUT=" `expr`"Link copied to clipboard

CTB07BE VARIABLE NOT FOUND IN EVALUATION ROUTINE (POS `n`), INPUT=" `expr`"Link copied to clipboard

CTB07CE VARIABLE NOT NUMERIC IN EVALUATION ROUTINE (POS `n`), INPUT=" `expr`"Link copied to clipboard

CTB07DE ERROR WHILE EVALUATING EXPRESSION (POS `n`), INPUT=" `expr`"Link copied to clipboard

CTB07EE DIVISION BY ZERO IDENTIFIED IN EVALUATION ROUTINE (POS `n`), INPUT=" `expr`"Link copied to clipboard

CTB07FS `req` IS AN INVALID REQUEST TO FUNCTION `func`Link copied to clipboard

CTB080S INTERNAL ERROR IN CTBXALC: RC= `rc`Link copied to clipboard

CTB081E ALLOCATION ERROR IN CTBXALC: `rcerrCode infoCode`Link copied to clipboard

CTB082S ALLOCATION ERROR IN CTBXALC: ABEND `abend`Link copied to clipboard

CTB083S INTERNAL ERROR IN CTBXALC: RC `rc` INVALIDLink copied to clipboard

CTB084I DURING PROCESSING OF DSN= `dsn` DD= `ddName`Link copied to clipboard

CTB085E INVALID MEMBER NAME: `string`Link copied to clipboard

CTB090S INTERNAL ERROR IN CTBXSIO: RC= `rc`Link copied to clipboard