|
|
|
|
|
This group includes messages for the Control-M/Tape product.
Explanation: A rule name was specified without a table name. A rule name cannot be specified without a table name.
Corrective Action: Either specify the table name, or omit the rule name, in order to receive a list of tables in the library.
Explanation: An invalid option was specified in the ON field.
The ON field is used to specify criteria which must be met before Control-M/Tape performs actions. The option specified identifies certain criteria from the active environment.
Valid options in the ON field are:
Corrective Action: Correct the entry by specifying a valid ON option.
Explanation: An invalid volser range was specified in ON VOLSER fields. The ON VOLSER field enables specifying a range of volsers. For a volser range to be valid, the first value in the specified range must be less than or equal to the second value.
Corrective Action: Correct the entry by specifying a valid range.
Explanation: An invalid retention type was specified in a DO RETENTION statement. The DO RETENTION statement is used to specify a duration for which a data set or volser is kept. The retention type specified identifies how the duration is calculated. There may be a single retention type specified, or a combination of up to three different retention types using the AND/OR field.
Valid retention types are:
Corrective Action: Correct the entry by specifying a valid retention type.
Explanation: An attempt was made to open a DO RETENTION statement in a rule that already contains a DO RETENTION statement. The DO RETENTION statement specifies a duration for which a data set or volser is kept.
To avoid conflicting duration periods for the criteria defined in the ON block, there may be only one DO RETENTION statement per ON block.
Corrective Action: Instead of opening a second DO RETENTION statement, specify a combination of retention periods in one DO RETENTION statement using the AND/OR parameter.
Explanation: An attempt was made to specify a retention period that does not correspond to previous retention periods in the DO RETENTION statement. The DO RETENTION statement has up to three different retention periods to specify a duration for which a data set or volser is kept.
To avoid conflicting duration periods, the combination of retention periods specified in one DO RETENTION statement must be logical. For example, a retention period of PERMANENT may not be combined with any other retention periods.
Corrective Action: Specify a valid retention combination.
Explanation: An attempt was made to specify an additional vault or an additional retention period in a DO VAULT statement that already contains a retention period of PERMANENT. If a volume is to be kept permanently, it cannot be transferred to an additional vault, and no more retention periods can be specified.
Corrective Action: Clear the additional VAULT parameter or AND/OR parameter, if the volume is to be kept permanently, or change the retention period from PERMANENT to another retention period.
Explanation: A retention line was opened, but no retention type was specified. The retention period in a DO RETENTION, ABENDRET, or VAULT statement specifies a duration for which a data set or volser is kept. The retention type determines how the duration is calculated. There may be a single retention type, or a combination of up to three different retention types using the AND/OR field.
Valid retention types are: CA (MVS Catalog), CY (Cycles), DAT (Date), DAY (Days), ED (EDM), EX (EXPIRE), J (JCL EXPDT), L (Last access), P (Permanent), R (Return from vault), and V (VAULT DAYS). Some retention types are not valid for all retention periods in the different statements.
Corrective Action: Specify a valid retention type, or clear the preceding AND/OR field (or DO field in the case of a single retention) if no further retention criteria are required.
Explanation: The WHEN type was specified in the WHEN field of a DO statement was invalid or absent. The WHEN parameter determines when the DO statement that contains the WHEN parameter is performed.
Valid WHEN types are:
Corrective Action: Correct the entry by specifying a valid WHEN type.
Explanation: An attempt was made to open a DO POOL statement in an ON block that already contains a DO POOL statement. The DO POOL statement specifies the pool from which a scratch volume is taken.
To avoid conflicting data when mounting a scratch tape, there may be only one DO POOL statement per ON block.
Corrective Action: Delete the second DO POOL statement by clearing the DO field.
Explanation: An attempt was made to open a DO LABEL statement in an ON block that already contains a DO LABEL statement. The DO LABEL statement specifies whether or not a label is to be printed when a data set is written on a volume.
To avoid conflicting data when deciding whether or not to print a label, there may be only one DO LABEL statement per ON block.
Corrective Action: Delete the second DO LABEL statement by clearing the DO field.
Explanation: An attempt was made to open a DO STACK statement in an ON block that already contains a DO STACK statement. The DO STACK statement specifies whether or not stacking of data sets is performed on a certain volume.
To avoid conflicting data when deciding whether or not to stack data sets on a volume, there may be only one DO STACK statement per ON block.
Corrective Action: Delete the second DO STACK statement by clearing the DO field.
Explanation: An attempt was made to open a DO VAULT statement in a rule that already contains a DO VAULT statement. The DO VAULT statement determines in which vaults, if any, a volume is to be kept.
To ensure that a volume is specified in the correct sequence of vaults, there may be only one DO VAULT statement per ON block. However, a sequence of vaults may be specified in a DO VAULT statement. An empty VAULT entry is opened whenever a new vault is specified in a DO VAULT statement.
Corrective Action: Instead of opening a second DO VAULT statement, specify a sequence of vaults in the DO VAULT statement using the empty VAULT entry at the end of the statement.
Explanation: The rule does not contain any ON statements. Every rule must have at least one ON statement that identifies under what conditions to perform the DO statements.
The rule is not saved.
Corrective Action: Add an ON statement to the rule.
Explanation: In a DO RETENTION, ABENDRET, or VAULT statement, a value of zero was specified in the CYCLES field of a retention period. The CYCLES retention type determines the number of cycles that a volume or data set is to be kept. A cycle of a data set relates to the creation of a copy of the specified data set. A retention period of zero is invalid since it means there is no duration.
Corrective Action: Specify a valid number of CYCLES or change the retention type.
Explanation: An attempt was made to open a DO OWNER statement in an ON block that already contains a DO OWNER statement. The DO OWNER statement determines the owner of a volume data set. There may be only one owner for a volume or data set. Therefore, there may be only one DO OWNER statement per ON block.
Corrective Action: Delete the second DO OWNER statement by clearing the DO field.
Explanation: A retention type of DATE was specified for a vault. However, the date specified overlaps the duration of the same volume in a previous vault.
The DO VAULT statement enables a volume to be kept in a sequence of vaults. Each vault may have its own retention period. A volume is transferred from one vault to the next vault in the sequence at the end of its duration field. Overlapping of dates is invalid. The calculated duration for the retention of a volume or data set in a vault must only begin at the end of the retention period of the previous vault.
Corrective Action: Modify the retention date to a date after the retention period of the previous vault.
Explanation: An attempt was made to add an ON DATASET statement in a rule that already contains an ON DATASET statement. The ON DATASET statement specifies the data set or data set prefix that must be matched for Control-M/Tape to perform actions defined in the rule. This is the basic search criterion. Therefore, only one ON DATASET statement is allowed.
Corrective Action: Delete one of the ON DATASET statements. A mask containing * and ? may be used instead of a data set name.
Explanation: An invalid retention type was specified in a retention period of a DO VAULT statement. The DO VAULT retention period specifies a duration for which a data set or volser is kept in a vault. The retention type specified identifies how the duration is calculated. There may be a single retention type, or a combination of up to three types using the AND/OR field.
Valid retention types are:
Corrective Action: Correct the entry by specifying a valid retention type.
Explanation: An invalid retention type was specified in a retention period of a DO ABENDRET statement. The DO ABENDRET retention period specifies a duration for which a data set or volser is kept in case of an abend. The retention type specified identifies how the duration is calculated. There may be a single retention type, or a combination of up to three types using the AND/OR field).
Valid retention types are:
Corrective Action: Correct the entry by specifying a valid retention type.
Explanation: An invalid DO statement was specified in a Control-M/Tape rule (screen TR). DO statements specify actions to be performed by Control-M/Tape when scheduling and selection criteria for a rule are satisfied. For more information about DO statements, see the description of ON and DO statements in the rule parameters chapter of the Control-M/Tape User Guide.
The rule definition cannot be saved.
Corrective Action: Either delete the invalid DO statement or replace it with a valid DO statement.
Explanation: A POOL assignment was requested by means of a DO field in a rule that previously contains ON VOLUME or ON MEDIA statements. The POOL assignment is only meaningful when scratch tapes may be requested. If a volume or media appears as criteria for executing the rule, scratch tapes cannot be requested.
Corrective Action: Correct the entry by deleting the POOL assignment.
Explanation: An attempt was made to define a cycle retention type with a prefix that does not match the prefix of another cycle retention type. The prefix of the cycle retention types for the DO RETENTION and DO ABENDRET statements must be the same. The prefix of the cycle retention types within the DO VAULT statement must also be the same.
Corrective Action: Correct the entry.
Explanation: A STACK=Y statement was specified in a rule that previously contained an ON VOLUME, ON MEDIA, or ON UCB statement. STACK=Y processing takes place before media, volume or UCB information is available. Therefore, rules that are triggered by volume, media or UCB information cannot request dynamic stacking.
Correct the rule by deleting the STACK=Y statement or use a different ON statement.
Corrective Action: No action is required.
Explanation: The UCB range specified in the TR screen is invalid. The FROM or TO value is not a valid UCB address (hexadecimal value) or the FROM value is larger than the TO value.
The rule cannot be saved until the range is specified correctly.
Corrective Action: Specify a valid UCB range and save the rule.
Explanation: The specified DO statement (do_stmt) was included more than once in a Control-M/Tape rule. Only one DO statement of the specified type can be included in each Control-M/Tape rule.
The rule definition cannot be saved.
Corrective Action: Delete the duplicate DO statement, leaving only one DO statement of the specified type. See the section on ON and DO blocks in the chapter on rule parameters of the Control-M/Tape User Guide for more information about the specified DO statement.
Explanation: An invalid value was specified for the SCOPE subparameter in a DO STACK statement in the Rule Definition screen (screen TR).
Valid SCOPE values:
The rule definition cannot be saved.
Corrective Action: Specify a valid SCOPE value.
Explanation: A DO STKRULE statement was specified in a Control-M/Tape rule that does not include a DO STACK=Y statement. A DO STKRULE statement can only be specified if a STACK=Y statement is specified earlier in the rule.
The rule definition cannot be saved.
Corrective Action: Either specify a DO STACK=Y statement earlier in the rule or remove the DO STKRULE statement.
Explanation: No value was specified for subparameters JOB and DSN in a DO STKRULE statement of a Control-M/Tape rule. The DO STKRULE statement describes data sets or jobs that create data sets, which should not be stacked with the data set whose access triggered the rule. Therefore, a value must be specified for at least one of these subparameters.
The rule definition is not saved.
Corrective Action: Specify the required jobname, data set name, or both, in DO STKRULE and save the rule.
Explanation: An invalid value was specified for the current field in a Control-M/Tape rule. This field must have a value of either YES or NO.
The rule definition cannot be saved.
Corrective Action: Specify either YES or NO and save the rule.
Explanation: An invalid value was specified in a DO DYNVOL statement of a Control-M/Tape rule.
Valid values for a DO DYNVOL statement are:
The rule definition cannot be saved.
Corrective Action: Either specify a valid value for the DO DYNVOL statement, or delete the statement.
Explanation: An invalid value was specified in a DO RECREATE statement of a Control-M/Tape rule.
Valid values for a DO RECREATE statement are:
The rule definition cannot be saved.
Corrective Action: Either specify a valid value for the DO RECREATE statement or delete the statement.
Explanation: An invalid value was specified in a DO STKMODE statement of a Control-M/Tape rule. A DO STKMODE statement determines the algorithm used to search for a volume on which to stack the current data set. These searches are performed on the same pool as the eligible candidate volumes for stacking.
Valid values for a DO STKMODE statement are:
The rule definition cannot be saved.
Corrective Action: Specify a valid value for the DO STKMODE statement, or delete the statement.
Explanation: A DO statement at KEEP event was specified in a rule that previously contained an ON PGM statement. KEEP processing takes place when the PGM name is no longer available. Therefore, rules that are triggered by a PGM name cannot request an IOA service at a KEEP event.
Control-M/Tape does not save the rule definition.
Corrective Action: Correct the entry by deleting the KEEP event, or use a different ON statement.
Explanation: An invalid fast positioning option was specified in a DO FASTPOS rule statement. The DO FASTPOS statement specifies the mode of operation for fast positioning.
Valid fast positioning options are:
Control-M/Tape does not save the rule definition.
Corrective Action: Correct the entry by specifying a valid fast positioning option.
Explanation: A value was specified in a RETENTION field but the AND/OR relationship to the value in a previous RETENTION field was left blank.
If values are specified in more than one RETENTION field, a value must be inserted into the AND/OR field relating to each of the RETENTION fields, except the last, to avoid inconsistency.
The definition is rejected.
Corrective Action: Correct the definition, either by deleting the current RETENTION value, or by inserting an AND/OR relationship between the current RETENTION and the previous RETENTION.
Explanation: A Control-M/Tape rule definition is invalid. The definition included both of the following:
Dynamic stacking cannot be performed for data sets with an unpredictable return date from the vault. All stacked data sets on the volume must have the same return date from the vault.
The rule definition cannot be saved.
Corrective Action: Do one of the following:
Explanation: Either the year is not defined in the calendar, or the calendar was incorrectly modified.
The rule is not ordered.
Corrective Action: Check the contents of the rule order and the calendar. Correct accordingly, and reorder the rule.
Explanation: An invalid capacity type was specified. Valid capacity types are slots and boxes.
Corrective Action: Specify a valid capacity type.
Explanation: A vault name was specified without a table name. A vault name cannot be specified without a table name.
Corrective Action: Either specify the table name or omit the vault name.
Explanation: The field contains the value 0. It must hold a numeric value greater than 0.
Corrective Action: Correct the value in the field.
Explanation: The combination of the box ID and Capacity parameters creates a calculated box ID that exceeds six characters.
Corrective Action: Change either the box ID or Capacity parameters, or both, so that their combination does not exceed six characters.
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.
Explanation: The vault name has been changed by the user from MAINLIB to a different name, and therefore all box definitions are automatically changed to box capacity definitions. Be aware that box definitions are allowed only under the definition of vault name MAINLIB.
Corrective Action: No action is required.
Explanation: The same media capacity is already defined under the same vault, or the same box ID with the same media is already defined under the vault name MAINLIB.
Corrective Action: Do one of the following:
Explanation: The function requested is not authorized for the user. The message is issued by the IOA security mechanism.
Corrective Action: Check with your system security administrator.
Explanation: This information message indicates that the ADD, DELETE, or CHECK option completed successfully and the cond condition with the odate original scheduling date was added to or deleted from, or found in the IOA Conditions file.
In this message, odate is the date on which the message is issued. If the ADD, DELETE, or CHECK option is run by the IOACND utility in batch mode, the user ID (userId), job name (jobName), and job ID (jobId) of the batch file are also displayed.
Corrective Action: No action is required.
Explanation: No volume range is defined.
Corrective Action: Specify the volume range.
Explanation: Volume range is invalid. The first value in a valid volume range must be less than or equal to the second.
Corrective Action: Specify a valid range.
Explanation: A pool name was specified without a table name. A pool name must have a table name.
Corrective Action: Either specify the table name or omit the pool name.
Explanation: During the conversion of EPIC vaulting rules into Control-M/Tape rules, an EDM rule was found. EDM rules cannot be converted automatically. They must be defined manually.
The rule is not converted.
Corrective Action: Define the EDM rule manually by means of screen TR.
Parent Topic |