|
|
|
|
|
This group includes messages for the Control-M/Tape product.
Explanation: This information message indicates that the real-time environment was successfully established.
In this message, rel is the specific release of Control-M/Tape.
Corrective Action: No action is required.
Explanation: The initialization of Control-M/Tape activated by the CTTINIT procedure failed due to an error. This message is preceded by a message that identifies the error that caused the initialization failure.
Initialization terminates and the already-created environment is removed from the system.
Corrective Action: Notify your INCONTROL administrator.
Explanation: Dynamic stacking cannot be activated if Control-M/Tape was initialized without dynamic stacking, meaning that the DYNSTK parameter was set to N in CTTPARM.
STARTSTK is not performed. Control-M/Tape continues to work in NOSTACK mode.
Corrective Action: If you want to utilize dynamic stacking, do the following:
If you later want to stop dynamic stacking temporarily, use the CTTINIT setting MODE=STOPSTK. To stop it for a longer period, set DYNSTK to N.
Explanation: This information message indicates that the real-time environment was successfully removed from the system. The CTTINIT procedure was activated with MODE set to TERM to delete the previously established environment.
In this message, rel is the specific release of Control-M/Tape.
The system operates now without Control-M/Tape.
Corrective Action: No action is required.
Explanation: The specified MVS function (LOCATE or OBTAIN) failed for a Control-M/Tape file. All the Control-M/Tape files are accessed by the CTTINIT procedure, and should exist on the CPU where each is activated. The LOCATE function could fail if the data set is not cataloged. The OBTAIN function could fail if it is cataloged on a wrong volume.
The return code in the message is a SVC99 MVS return code.
Initialization terminates.
Corrective Action: Check that the data set in the message matches the name specified in installation the DBPREF parameter in the CTTPARM member. Make sure that the data set exists and is cataloged on the correct volume.
Explanation: The specified volume could not be located in the system.
Initialization terminates.
Corrective Action: Check that the volume is accessible from the CPU where the CTTINIT procedure was activated.
Explanation: The CTTINIT procedure was started with MODE set to either
while the INIT/VERIFY process reveals that the Control-M/Tape real-time environment was already active in this CPU.
The INIT/VERIFY process is not started.
Corrective Action: Either use the existing Control-M/Tape environment or delete the existing one before trying to INIT/VERIFY a new one.
Explanation: The Control-M/Tape operation mode is set to one of the following modes: TEST, ACTIVE, SUSPEND, DORMANT, STACKING, or NO-STACK.
Control-M/Tape operates according to the mode, as follows:
Corrective Action: No action is required.
Explanation: This information message indicates that the Control-M/Tape initialization or termination process was started by the CTTINIT procedure.
Corrective Action: No action is required.
Explanation: This information message indicates that the reload function for a module (for example, user exit) or tables (rules, pools or vaults) was performed. When Control-M/Tape is activated in the system, certain components can be reloaded (refreshed with a new copy). Reload can be performed for the following:
Upon successful completion, the system operates with the new modules or tables.
Corrective Action: No action is required.
Explanation: This information message indicates that the specified dynamic installation component function was successfully performed (for example, applied, removed).
The dynamic installation function can be optionally performed according to installation parameters for each of the following components:
Corrective Action: No action is required.
Explanation: The dynamic installation function (for example, APPLY, REMOVE) failed with the specified return code (rc). This function can also be performed according to installation parameters on operating system interfaces, the SVC, and the WTO intercept. This message follows a message about a failure to a component.
Processing terminates immediately.
Corrective Action: Check preceding error messages for details about the error and notify your INCONTROL administrator.
Explanation: SVC number svc_num is already defined for another purpose not related to Control-M/Tape. The SVC number that was specified for Control-M/Tape during installation time in the CTTPARM member is already defined in the system. Control-M/Tape does not replace it with its own SVC.
Dynamic installation of the SVC fails, and the currently executing function is terminated.
Corrective Action: Either change the SVC number in the CTTPARM member to an unused number, or remove the older definition from the system.
Explanation: SVC svc_num is not installed in the system. The SVC is used by all Control-M/Tape real-time functions. Therefore, as part of the initialization process, the existence of the SVC is checked. This message indicates that although the dynamic SVC installation was not required (DYNSVC was set to N in the CTTPARM member), the SVC is not properly defined.
The currently executing function continues without defining the SVC since dynamic definition was not requested.
Corrective Action: Check why the SVC was not properly defined, or change the installation parameters to perform dynamic SVC installation (set DYNSVC to Y).
Explanation: The APPLY option of Control-M/Tape could not install SVC svc_num, because it was already in the system. Before installing the specified SVC, the CTTINIT procedure of Control-M/Tape checks to see if it already exists in the system.
The SVC may be already in the system for one of the following reasons:
The attempt to install the SVC stops, and the initialization process stops.
Corrective Action: Check earlier errors, or do one of the following:
For more information, refer to the INCONTROL for z/OS Upgrade Guide.
Explanation: SVC svc_num could not be dynamically installed or removed from the system.
The SVC is not installed or removed. The currently executing function stops.
Corrective Action: Check preceding error messages for details. Notify your INCONTROL administrator.
Explanation: Although dynamic installation was not required, the specified intercept is not installed or properly defined in the system. As part of the initialization process, the existence of the intercept is checked.
Valid values for interceptName are WTO or VOLSTAT.
The currently executing function continues without installing the intercept.
Corrective Action: Check why the intercept was not properly installed, or change the installation parameters to perform dynamic installation.
Explanation: The APPLY option of Control-M/Tape could not install the specified intercept because it was already in the system. Before installing the specified intercept, the CTTINIT procedure of Control-M/Tape checks to see if it already exists in the system.
The intercept may be already in the system for one of the following reasons:
Valid values for interceptName are WTO or VOLSTAT.
The attempt to install the intercept stops.
Corrective Action: Check earlier errors or do one of the following:
Consult the INCONTROL for z/OS Upgrade Guide.
Explanation: The specified intercept could not be dynamically installed or removed from the system. Possible values of interceptName are WTO or VOLSTAT.
The specified intercept is not reinstalled or removed. The currently executing function is terminated.
Corrective Action: Check preceding error messages for details about the error. Notify your INCONTROL administrator.
Explanation: The real-time value of the parameter CTVINTR has been changed to 'NONE'.
Control-M/Tape changes the real-time value of CTVINTR to 'NONE' and continues to run.
Corrective Action: No response required.
Explanation: The real-time value of the parameter CTVINTR is other than 'NONE'.
Control-M/Tape continues to use the current value of the CTVINTR parameter.
Corrective Action: Change the Control-M/Tape CTVINTR parameter in the member CTTPARM to 'NONE'. Then issue the following command, which updates the system with the new value:
S CTTINIT,PARM='MODE=RELOAD,TBLT=PARM'
Explanation: One of the following situations occurs:
The currently executing function continues without installation of the specified component
Corrective Action: No action is required.
Explanation: The APPLY option of Control-M/Tape could not install the specified component because it is already in the system. Before installing the specified component, the CTTINIT procedure of Control-M/Tape checks to see if it already exists in the correct place in the system.
The component may be already in the system for one of the following reasons:
The attempt to install the interfaces stops, and the initialization process stops.
Corrective Action: Check earlier errors or do one of the following:
Consult the INCONTROL for z/OS Upgrade Guide.
Explanation: The component could not be dynamically installed or removed from the system.
The component is not installed or removed. The currently executing function is terminated.
Corrective Action: Check preceding error messages for details about the error.
Explanation: Due to internal error, activation of a Control-M/Tape subsystem failed.
The initialization process stops and the already created environment is removed from the system.
Corrective Action: Notify your INCONTROL administrator.
Explanation: Termination of Control-M/Tape cannot continue because Control-M/Tape detected active jobs that use removable media in the system. When active jobs that use removable media are still active, Control-M/Tape cannot stop. This message is followed by one or more CTT825I messages that identify the active jobs.
Control-M/Tape does not terminate.
Corrective Action: No action is required.
Explanation: This information message identifies the name and ID of an active job in the system that uses removable media.
This messages accompanies message CTT824E. There is one CTT825I message for each active job that uses removable media. The last CTT825I message is followed by message CTT826A.
Corrective Action: No action is required.
Explanation: There was an attempt to terminate Control-M/Tape while there are still active jobs in the system that use removable media.
This message asks what to do next, as follows.
This message follows message CTT825I.
The CTTINIT procedure waits for the operator reply.
Corrective Action: Reply to the message.
Note:
Using the FORCE option is not recommended. If you use this option, the removable media used by the active jobs will not be updated in the Control-M/Tape repository, and jobs might abend. Also, other unpredictable situations could occur, that sometimes might be resolved only by IPL.
Explanation: Termination of Control-M/Tape failed because Control-M/Tape was unable to remove the specified component. Since termination cannot continue, Control-M/Tape enters DORMANT mode.
This message follows a specific error message, which identifies the error.
Termination of Control-M/Tape stops. Control-M/Tape enters DORMANT mode.
Corrective Action: Look for previous Control-M/Tape messages and check why Control-M/Tape failed to remove the specified component. Then proceed accordingly.
Explanation: This information message indicates that the operator instructed Control-M/Tape to abort termination, probably because termination of Control-M/Tape was in progress when Control-M/Tape informed the operator about active jobs in the system.
This message follows message CTT826A.
Normal processing continues.
Corrective Action: No action is required.
Explanation: A CTTINIT operation was attempted while another was already operating. The current run of the CTTINIT utility cannot proceed until the old one ends.
The new CTTINIT is ended.
Corrective Action: Restart the CTTINIT utility after the conclusion of the current run of the CTTINIT utility.
Explanation: The CTTINIT utility discovered an error in the Control-M/Tape password.
This messages follows other messages that detail the error and password.
The CTTINIT procedure stops.
Corrective Action: Check the job log of CTTINIT for previous messages that refer to this failure, and proceed accordingly.
Explanation: The Media Database (MDB) and the Trace (TRC) file are on the specified volume.
This message is issued during initialization of Control-M/Tape, when both the data component of the MDB (MDBD) and the TRC file are on the same volume. If the MDB is damaged, the CTTRCV utility can recover it using the TRC file as input. If the TRC file is also damaged, recovery fails. Keeping the TRC file on the same volume as the MDBD increases the danger of both being damaged simultaneously, with a resulting inability to recover.
Control-M/Tape initialization continues.
Corrective Action: As soon as possible, move the TRC file to a different volume from the one holding the MDB. Control-M/Tape must be inactive when the file is moved.
Explanation: A Control-M/Tape subsystem was not statically defined. Because the TSSALLOC parameter in the CTTPARM member was set to N, Control-M/Tape does not dynamically define its subsystem during initialization.
The Control-M/Tape real time environment is not initialized.
Corrective Action: Either change the value of the TSSALLOC parameter in the CTTPARM member to Y, or define the Control-M/Tape subsystem statically.
For more information, see the description of the TSSALLOC parameter in the Control-M/Tape chapter of the INCONTROL for z/OS Installation Guide.
Explanation: When Control-M/Tape reloads rules following operator request RELOAD,TBLT=RULE, it first loads the new set of rules into memory and makes them active. Then, after several seconds, it releases the old set of rules, unless there are active processes using these old rules. This message indicates that there is at least one active process still using the old set of rules.
This message is followed by message CTT834A.
Corrective Action: Implement one of the options specified in message CTT834A.
Explanation: In the situation described by message CTT833I, the user has the following response options:
Corrective Action: Implement the appropriate option.
Explanation: During Control-M/Tape real time environment initialization, the dynamic installation for the exitName exit failed.
Control-M/Tape real-time environment initialization is terminated.
Corrective Action: Refer to IBM documentation along with the return code and reason code displayed in the message to understand why Control-M/Tape could not dynamically install the exit.
Explanation: When updating a record using function RECUPD, an attempt was made to change the record key, (for example, the VOLSER in the volume record).
Execution of the RECUPD function is terminated, and the record is not updated.
Corrective Action: The record key cannot be updated directly. Instead, first delete the record, and then add a new one with the required key. If you inadvertently try to change the key by specifying an invalid offset in the REP statement, correct the control REP statement accordingly.
Explanation: When trying to add a data set to the Media Database (MDB) using the DSNADD function, the selected pool specified in the corresponding Control-M/Tape rule did not contain the volser in which the data set resides.
The variables in this message are:
Execution of the DSNADD function is terminated. The data set is not added.
Corrective Action: Synchronize the DSVOLSER parameter with the pool definition.
Explanation: The CTTMUP utility issues this message when volume record fields that are related to vaulting are modified. When vaulting related fields are modified in a volume record, the corresponding vault, slot and box records need to be modified to reflect the changes made in the volume record. The CTTVTM utility performs the necessary synchronization in the indicated mode.
The CTTMUP utility continues.
Corrective Action: Run the CTTVTM utility in SLOTBLD or BOXBLD mode as indicated by the message.
Explanation: Open of a rule list data set failed (the DARULLST DD statement).
Possible causes are:
The CTTINIT procedure stops.
Corrective Action: Correct the JCL and restart the CTTINIT procedure.
Explanation: Invalid data has been found in the rule order list.
The CTTINIT procedure stops.
Corrective Action: Check the format of the rule order list in the PARM library; correct and restart the CTTINIT procedure.
Explanation: The order of rule ruleName from table tableName failed. This message is preceded by messages which explain why the rule table could not be ordered.
The rule is not ordered.
Corrective Action: Check earlier messages for reasons the rule order failed. Correct as necessary and reorder the rule table.
Explanation: A stmt_type statement is either missing or in the wrong order in a rule definition member. The rule definition data may have manually been changed incorrectly. The data does not conform to a valid Control-M/Tape format.
The rule is not ordered.
Corrective Action: Restore the table to its original state (from a backup copy) and reorder the rule table.
Explanation: An invalid scheduling date format was used in the rule list or in an order or force request.
Valid date formats are:
The requested table order fails.
Corrective Action: Correct the date; reorder the rule table.
Explanation: The rule definition has been corrupted and the data does not conform to a valid Control-M/Tape format.
This message is followed by one or more CTT856S messages describing all statements belonging to the damaged rule. An asterisk (*) appears in the line under the erroneous data.
The rule is not ordered.
Corrective Action: Restore the table to its original state by means of the Online Viewing Facility, or by editing the member, then reorder the rule table.
Explanation: The rule definition is corrupt.
This message follows message CTT855S, and displays each statement in the damaged rule. An asterisk * appears in the line under a damaged statement.
The CTTMRLL program terminates with a condition code of 08.
Corrective Action: Restore the table to its original state.
Explanation: This is the normal message when a rule order is successfully loaded by the CTTINIT procedure. The rule is now active and will be used by the Control-M/Tape real-time process.
Corrective Action: No action is required.
Explanation: A severe error was found in the rule definition data statements. This message is followed by additional messages regarding the error.
The rule table is not ordered.
Corrective Action: Check for additional messages concerning the errors. Correct the error and reorder the table.
Explanation: The specified rule order failed as a result of a user exit check.
The rule order is not ordered or loaded.
Corrective Action: Check for prior messages concerning the reason for failure and the Control-M/Tape EXIT 1.
Explanation: The operation was canceled because Control-M/Tape User Exit CTTSE01 ended with a return code higher than 0.
The operation is canceled.
Corrective Action: Check why the exit ended with a return code higher than 0, and proceed accordingly.
Explanation: The rule loading program of the CTTINIT utility tried to allocate a block for rules in ECSA. Due to lack of memory, it received an area in CSA. Control-M/Tape does not allocate CSA areas for rule blocks when working in TEST mode.
Rule loading is stopped. The CTTINIT procedure terminates after freeing all memory blocks allocated thus far.
Corrective Action: Either increase the ECSA size defined in your system, or reduce the number of rules defined to Control-M/Tape. Restart the CTTINIT utility.
Explanation: Control-M/Tape was unable to free rule blocks from memory. The rule loading program ended unsuccessfully. An error occurred during the process of freeing all rule blocks allocated thus far.
If the allocated blocks are in ECSA or CSA, they are not freed by Control-M/Tape. If the allocated blocks are in a private region, they will be freed at job end.
Corrective Action: If allocated blocks remained in ECSA or CSA, use a tool (for example, OMEGAMON, RESOLVE) to free these blocks. Blocks not freed by a tool will be freed automatically by the next IPL.
Note:
Use extreme caution when freeing blocks from ECSA or CSA manually.
Explanation: Control-M/Tape was unable to load any rules because no rules were scheduled for today.
Control-M/Tape does not load any rule, and execution stops.
Corrective Action: Use the TR screen to check your rule definitions and update the rule scheduling criteria so as to ensure that at least one rule will be scheduled for today.
Explanation: The Slot Management Facility could not find an empty slot for a volume being moved to the vault specified in the message. If a capacity is defined for a vault, Control-M/Tape tries to assign a slot to each volume that comes to the vault.
The appropriate Slot Definition record is not updated.
Corrective Action: Increase the capacity of the vault using the Vault Definition screen (screen TV), or define the vault with no capacity. Then run the CTTVTM utility in SLOTBLD mode.
Explanation: The Slot Management Facility tried to assign a slot to a volume according to the slot number specified in the volume record, but the slot is already occupied by another volume.
Control-M/Tape does not reassign the slot number, but continues with the next volume.
Corrective Action: Correct the slot number in the volume record using the Volume Update screen.
Explanation: The util utility cannot run in the mode requested if Control-M/Tape is active. Some Control-M/Tape utilities cannot be run while the Control-M/Tape real-time environment is active.
The utility terminates.
Corrective Action: See the description of this utility in the INCONTROL for z/OS Utilities Guide.
Explanation: An input statement was continued to the next line, but no continuation line was supplied. A comma at the end of a line indicates a continuation line, but the input was exhausted before the continuation line was received.
The program stops executing.
Corrective Action: Either remove the comma or supply the missing line.
Explanation: The current control statement is in error.
Possible values for err are:
err |
Explanation |
|---|---|
INVALID DATE - date |
The date specified (date) is in an invalid date format or contains invalid values. Valid formats for the date are yyyymmdd or yymmdd. |
INVALID EQUATE SPECIFIED - equ |
The equate equ was used incorrectly. For the correct usage of equate, see the appendix that describes logical field names for the Control-M/Tape repository in the INCONTROL for z/OS Administrator Guide. |
INVALID FUNCTION ISSUED |
An invalid function was used. For a list of supported functions, see the documentation for the CTTMUP utility. |
INVALID HEX VALUE SPECIFIED - hex |
hex is an invalid hexadecimal value. |
INVALID KEYWORD SPECIFIED - kwd |
The keyword kwd was used incorrectly, perhaps on the wrong side of the relation symbol. For the correct keyword format, see the appendix that describes logical field names for the Control-M/Tape repository in the INCONTROL for z/OS Administrator Guide. |
INVALID NUMERIC VALUE SPECIFIED |
A non-numeric value was specified. |
INVALID PARAMETER VALUE - parm= val |
The value assigned to parameter parm is invalid. For a list of correct values, see the appendix that describes logical field names for the Control-M/Tape repository in the INCONTROL for z/OS Administrator Guide. |
INVALID 'parm=' SPECIFICATION |
The value specified for the parm parameter is invalid. |
INVALID RBA PARAMETER |
An invalid value was given to an RBA field. The RBA format is X hhhhhhhh, where X is a constant and hhhhhhhh is a valid RBA found in the MDB. |
INVALID RELATION IN KEYWORD - keywd |
An invalid relation symbol was used. Only the “=” symbol can be specified. |
INVALID RETENTION DATA - rtn |
Incorrect retention data was specified. For the correct format of retention data, see the documentation for the CTTMUP utility. |
INVALID STATEMENT CODE |
The statement contained an invalid code, or was not correctly placed. |
INVALID ZERO VALUE SPECIFIED |
The value of zero is invalid. |
KEYWORD NOT FOUND IN DICTIONARY - keywd |
The keyword keywd is invalid. Check the spelling. |
MANDATORY FIELDS NOT FOUND |
At least one mandatory field is missing. For mandatory fields, see the documentation for the CTTMUP utility. |
TYPERUN STATEMENT MISSING |
The TYPERUN statement is mandatory. It was not specified. |
VOLSER TOO LONG - volser |
VOLSER should contain one through six characters only. |
VALUE EXCEED MAXIMUM parm= val |
The parm parameter has been set to a value (val) that exceeds the maximum. |
Corrective Action: Correct the error and rerun the utility.
Explanation: Rule search is not performed for the dsn data set that is being added. The CTTMUP utility was activated with RULEINFO set to YES (the default). The DSNADD function was requested, but the volume specified as dsvolser was not in the Media Database. A rule search cannot be performed without valid volume information.
The dsn record is added without application of rule information for this data set.
Corrective Action: Ensure that the correct volume keyword dsvolser was specified in command DSNADD. When adding a data set (DSNADD) and a volume (VOLADD) to contain the data set, it is recommended that commands be issued in the following order: VOLADD, DSNADD.
Explanation: This information message indicates that the specified function was performed successfully. The record key or the record type is indicated.
The CTTMUP utility continues to the next function.
Corrective Action: No action is required.
Explanation: The scratch action requested for the vol volume could not be performed because vol is a member of a multivolume chain, and expiration of a single volume of a multivolume chain is not allowed.
The CTTMUP utility continues to next function.
Corrective Action: Use function GRPSCR if you wish to expire the entire multivolume chain.
Explanation: The data set label number does not match the number of the highest label specified on one of its volumes. All the volumes connected by a multivolume data set must have the same label number as the data set itself, except for the last volume, which can have a higher label number.
In this message, volser is the identity of the problematic volume.
The execution of the current function continues.
Corrective Action: Correct the data set label number using the DSNUPD function, or the highest label number of the volume using the VOLUPD function.
Explanation: The RECUPD function discovered that the data specified in the VER statement does not correspond to the data in the selected record.
Execution of the RECUPD function is terminated.
Corrective Action: Correct the data in the VER statement according to that in the selected record.
Explanation: The load of the pool or vault failed. This message is preceded by messages that explain why the pool or vault could not be loaded.
The pool or vault is not loaded.
Corrective Action: Check earlier messages for reasons the pool or vault load failed. Correct as necessary.
Explanation: Open of the pool or vault data sets failed (the DAPOOLS or DAVLTS DD statement).
Possible causes are:
Processing continues. Control-M/Tape will not have a pool or vault defined to it.
Corrective Action: No action is required.
Explanation: A statement of the type type is either missing or in the wrong order in a pool or vault definition member. The pool or vault definition data may have been manually changed incorrectly. The data does not conform to a valid Control-M/Tape format.
The pool or vault is not ordered.
Corrective Action: Restore the table to its original state from a backup copy. Reorder the pool or vault table.
Explanation: This information message indicates a pool or vault order was successfully loaded by the Control-M/Tape monitor.
The pool or vault is now in a Control-M/Tape WAIT SCHEDULE state.
Corrective Action: No action is required.
Explanation: The pool or vault definition is corrupt, and the data does not conform to a valid Control-M/Tape format.
This message is followed by one or more CTT885S messages describing all statements belonging to the corrupted pool or vault order. An asterisk (*) appears in the line under the erroneous data.
The pool or vault is not ordered.
Corrective Action: Restore the table to its original state by means of the Online Viewing facility; then reorder the pool or vault table.
Explanation: The pool or vault definition is corrupt.
This message follows message CTT884S. It appears once for each statement in the corrupted pool or vault in the scheduling table, each occurrence displaying a different statement. An asterisk * appears in the line under an erroneous statement.
The CTTMPVL program terminates with a condition code of 08.
Corrective Action: Try to restore the table to its original state.
Explanation: A severe error was found in the pool or vault definition data statements. It is followed by additional messages regarding the error.
The pool or vault table is not ordered.
Corrective Action: Check for additional messages concerning the errors in the systems and IOA Log. Correct the error and reorder the table.
Explanation: Two pools (pool1 and pool2) were defined with a range overlap. Therefore, some volumes may belong to both pools. Control-M/Tape requires that volume ranges be unique for all pools.
The initialization process terminates.
Corrective Action: Correct the pool definitions so that no volume is defined in more than one pool.
Parent Topic |