|
|
|
|
|
This group includes messages for the Control-M/Tape product.
Explanation: This information message indicates that the CTTRTM utility deleted all data sets and changed the status of the volume to SCRATCH.
The utility continues executing.
Corrective Action: No action is required.
Explanation: This information message indicates that the specified data set was marked SCRATCH by the CTTRTM utility according to the expiration criteria for the data set.
Corrective Action: No action is required.
Explanation: This information message indicates that although the expiration date of a data set has been reached, the data set has not been expired, because a grace period was defined. However, when the grace period is over, the data set will be expired.
The variables in this message are:
Grace periods are defined by the GRACECAT and GRACECYC parameters in CTTPARM. For more information on these parameters, see the Control-M/Tape chapter in the INCONTROL for z/OS Installation Guide.
The utility continues processing normally.
Corrective Action: No action is required.
Explanation: The CTTRTM utility could not uncatalog the data set. The data set could not be uncataloged because the MVS Catalog is not available or an I/O error occurred in catalog volume.
The CTTRTM utility skips the data set record and continues executing.
Corrective Action: Notify your system programmer of the value of rc.
Explanation: The CTTRTM utility successfully uncataloged the data set that was scratched just now.
The message is issued only when UNCATMSG=YES in the CTTRTM TYPERET statement.
Corrective Action: No action is required.
Explanation: The CTTRTM utility found that the dataset that was scratched just now is not cataloged. Therefore, CTTRTM does not attempt to uncatalog the dataset.
The message is issued only when UNCATMSG=YES and UNCTLG=YES (the default) are set in the CTTRTM TYPERET statement.
Corrective Action: No action is required.
Explanation: In the input parameters of the CTTRTM utility, there is an inconsistency between the values of the MODE parameter in the TYPERET statement, and the values of the REPORT NAME parameter. For example, MODE is set to REGULAR in the TYPERET statement for the RECALC report.
The utility stops executing.
Corrective Action: Correct the values of the TYPERET MODE parameter and the REPORT NAME, and rerun the utility.
Explanation: Volume vol is an active volume, but no data sets from the Media Database were found on the volume. This message indicates a logical error in the Media Database.
The CTTRTM utility continues processing.
Corrective Action: Notify your database administrator.
Explanation: More than the maximum number of volumes or data sets specified by the MAXVOLNO parameter or the MAXDSNO parameter, respectively, were marked for expiration during a run of the CTTRTM utility. Before scratching data sets or volumes, the CTTRTM utility checks how many volumes or data sets will be scratched in the current run of the utility.
In this message, num is the number of volumes or data sets that would have been marked for expiration by this run of the utility.
No volumes or data sets are scratched. The CTTRTM utility produces a Scratch report that describes the volumes and data sets that would have been scratched if the specified maximum were not exceeded.
Corrective Action: Determine why so many data sets were marked as expired and, if necessary, increase the limit for the maximum number of volumes or data sets that can be marked for expiration in the MAXVOLNO parameter or the MAXDSNO parameter.
Explanation: This information message indicates that a record was processed by the CTTMER or CTTSPL utilities.
The variables in this message are:
Corrective Action: No action is required.
Explanation: The CTTMER utility tried to merge a record that already exists in the Media Database. The records that CTTMER was merging into a target Media Database were split off from another Media Database by the CTTSPL utility. These records can only be merged into the target Media Database if they, that is, their volsers, do not already exist there. However, the volser of the record identified in the message already exists in the target Media Database.
CTTMER ignores this record, and does not merge it to the Media Database. The original record in the source Media Database remains unchanged. CTTMER continues to process the rest of the records.
Corrective Action: Check why the record to be merged already exists in the target Media Database.
Explanation: An invalid silo type was specified in the CTTPARM member.
Valid values of type are:
Corrective Action: Specify a valid silo type (if desired).
Explanation: The CTTRBM utility was invoked with an invalid silo function input parameter.
The following silo functions (func) are valid when invoking the CTTRBM utility:
Corrective Action: Correct the procedure used to invoke the CTTRBM utility.
Explanation: This information message indicates that the report file passed to the CTTRBM utility does not match the requested silo function.
Corrective Action: If desired, either request the CUASCR silo function for the SCRATCH or FULLSCR report of the Retention Management Utility (CTTRTM), or request the EJECT silo function for the DISTRIB report of the Vault Management Utility (CTTVTM).
Explanation: This information message indicates that a robot function requested for the specified volume failed because the volume cannot be found in the Automated Tape library.
In this message, mod_nam is one of the following Automated Tape library Interface module names:
Possible system actions:
Corrective Action: To suppress this message, see the description of user exit CTTX008 in the Control-M/Tape Implementation Guide.
Explanation: The silo function requested for a volume failed.
The software of the robotic tape library returns the operation code opc, the return code rc in decimal format, and the reason rsn in hexadecimal format.
In this message, modName is one of the following Automated Tape library Interface module names:
Possible system actions:
Corrective Action: Refer to the messages and codes documentation for your tape robot or silo for a description of the codes returned in this message.
Explanation: The report file passed to the CTTRBM utility is inappropriate for the requested silo function. The report passed to the CTTRBM utility was neither a SCRATCH report nor a DISTRIB report.
The CTTRBM utility is terminated.
Corrective Action: Do one of the following:
Explanation: The CTTRBM utility was unable to load the specified interface module.
In this message, modName is one of the following Automated Tape library Interface module names:
The specified interface is not used. The CTTRBM utility continues processing with the other interfaces (if any are loaded). If no other interfaces are loaded, the CTTRBM utility is terminated.
Corrective Action: If the specified interface is not needed, remove it from the specification for the RBTTYPE parameter in the CTTPARM member. If the specified interface is needed, add the appropriate module to one of the STEPLIB or LINKLIST libraries.
Explanation: Control-M/Tape initiated a SCRATCH or ACTIVATE operation on the specified volume (volser) in the database of the robot. However, the current status of this volume in the Media Database is incompatible with the attempted operation. The status of each volume in the Media Database and the robot database must be the same.
There was probably a delay between the issuance and execution of the robot request. During which the status of the specified volume was changed in the Media Database.
In this message, volser is the volume whose status update attempt is not compatible with its status in the Media Database.
The status of the volume is not changed in the robot database.
Corrective Action: Do one of the following:
Explanation: This information message indicates the current retry number for an action requested of a robotic tape library. This message is generated each time the action is retried.
Control-M/Tape requested an action from a robotic tape library. The action failed and is being retried. Each time the action is attempted, the retry number is incremented. The action is not retried if the action is successfully performed, or if the specified maximum number of retries is exceeded.
Message variables are:
Processing continues normally.
Corrective Action: Verify that the retry was completed successfully.
Explanation: The robotic library function func that was requested by means of the robot_int robotic interface module was successfully performed for the volser volume.
See message CTT333I for a list of interface modules and the robotic libraries with which they are associated.
Corrective Action: No action is required.
Explanation: Incorrect value specified for the optional parameter OKMSG. Only YES or NO are allowed. CTTRBM terminates.
Corrective Action: Specify a correct value and rerun CTTRBM.
Explanation: This information message indicates that the CTTVEXP utility successfully issued the EXPORT command to the Virtual Tape Server (VTS) and the export list volume is volser. The EXPORT command ejects physical tapes from the VTS so that logical VTS volumes can be put into external vaults. CTTVVM created volser earlier.
CTTVEXP waits for messages from OAM indicating that export processing is finished.
Corrective Action: No action is required.
Explanation: The CTTVEXP utility could not export tapes from the Virtual Tape Server (VTS).
Possible reasons are:
CTTVEXP stops.
Corrective Action: Do one of the following:
Explanation: This information message indicates that the CTTVVM or CTTVEXP utility is running in simulation mode. When CTTVTM runs in simulation mode (TYPERUN MODE is set to SIMULATION), CTTVTM notifies CTTVVM and CTTVEXP, so that they also run in simulation mode.
In simulation mode, CTTVVM does not create the Export List volume or the Import List volume and CTTVEXP does not perform any EXPORT command.
Corrective Action: To export tapes from the VTS, run CTTVTM with TYPERUN MODE set to NORMAL.
Explanation: This information message indicates that a volume with serial number volser was not exported because Control-M/Tape processed it in test mode. Test mode is set with the expression MODE=TEST in CTTPARM, or by a rule specifying MODE TEST. Control-M/Tape does not export a volume from the VTS (Virtual Tape Server) that it processed in test mode.
CTTVVM does not include the volser in the Export List File.
Corrective Action: If you intend to export a volume, make sure Control-M/Tape is not in test mode when it processes the volume.
Explanation: Volume with serial number volser was not exported because of an earlier error. Control-M/Tape does not export a volume serial number if an error occurred while Control-M/Tape was processing it.
CTTVVM does not include the volser in the Export List File.
Corrective Action: Check the error message before CTT344E, fix the problem and try again.
Explanation: The StorageTek ExLM level does not support vendor tape management systems. Control-M/Tape uses the StorageTek ExLM vendor tape management systems support to interface with ExLM.
ExLM processing terminates.
Corrective Action: See the section that describes the Robotic Tape Library Interface in the Control-M/Tape Implementation Guide for the minimum ExLM level required for the interface.
Explanation: The CTTVVM utility was invoked with the expression MODE=ALLVLT to export a volume with a vaulting pattern that has more than ten vaults, and the next requested vault is beyond the tenth.
When the CTTVVM utility exports volumes from the Virtual Tape Server (VTS) based on the complete vaulting pattern (MODE=ALLVLT), it supports a maximum of ten vaults in each vaulting pattern. Since the next vault of the volume specified in the CTT344E message that accompanies this message is beyond the tenth vault, CTTVVM cannot export this volume.
CTTVVM issues message CTT344E, which specifies the volser for the volume that caused this error. This volume is not included in the Export List file created by this run.
Corrective Action: Use the CTTVVM utility with MODE set to FIRSTVLT to export the volume based on the first vault only.
Explanation: This information message indicates that the CTTVVM utility successfully created an Import or Export List volume.
Message variables are:
If CTTVVM created an Export List volume, CTTVVM passes its volser to CTTVEXP by means of DD card VVMVOL and CTTVEXP issues the EXPORT command.
Corrective Action: If CTTVVM created an Import List volume, check that the physical volumes that contain the logical volumes to be imported are in the library. Then, issue the IMPORT command.
Explanation: The CTTVEXP utility could not read the Export Status File to produce a status report, because Control-M/Tape does not support the Export Status file identifier.
CTTVEXP stops without issuing a report.
Corrective Action: Check that Export processing finished successfully, and that OAM messages indicate that an Export Status file was created. If necessary, notify your INCONTROL administrator.
Explanation: This information message indicates the results of the CTTVEXP export operation. The information is based on the Export Status File records, where log_volser is the serial number of the logical volume, and stat_code is the export status code.
If the export operation succeeded, phys_volser specifies the serial number of the physical volume to which the logical volume was exported and dest specifies the destination.
If the export operation ended with an error, rsn describes the nature of the error.
Corrective Action: Refer to IBM documentation to resolve errors during processing of logical volumes.
Explanation: This information indicates that dynamic stacking was successfully performed on the specified volume. This message is followed by message CTT351I, which contains details about the stacked data set.
Corrective Action: No action is required.
Explanation: This information message follows message CTT350I. It provides details about the data set that will be added to the volume specified in CTT350I.
Corrective Action: No action is required.
Explanation: An error was encountered during the stacking process for job jobName.
This message is followed by another message that has details about the error.
Stacking stops for this job.
Corrective Action: Check the accompanying error message for details about the error.
Explanation: This message follows message CTT352S when there is insufficient storage for stacking processing.
Stacking processing stops for this job.
Corrective Action: Notify your INCONTROL administrator.
Explanation: This message follows message CTT352S when an internal error in encountered during stacking processing.
Stacking processing stops for this job.
Corrective Action: Notify your INCONTROL administrator.
Explanation: This message follows message CTT352S when an internal abend occurs in stacking processing.
The message contains details about the abend: abending module name, abending load module load point, and offset of the abending instruction in the module.
Stacking processing stops for this job and a system dump is produced.
Corrective Action: Format and save the dump, and notify your INCONTROL administrator.
Explanation: Control-M/Tape could not satisfy the stacking requirements for the dsn data set.
This message is followed by a message describing why the data set could not be stacked and why the stacking requirements could not be satisfied.
Stacking stops for the specified data set. The job continues without stacking for the dsn data set. The data set is written to a scratch volume.
Corrective Action: See later messages for details about the error and correct the problem.
Explanation: The search limit for a stackable volume has been reached. This message follows message CTT356W, which specifies the data set for which stacking has stopped.
Stacking stops for the data set. The job continues without stacking for this dsn. The search for the next stackable volume begins from the volume reached in this search.
Corrective Action: Check and, if necessary, adjust the search limit for stackable volumes, defined in the STKSRCHL parameter in the CTTPARM member.
Explanation: DO RETENTION=EDM is specified in the matching rule. Stacking cannot be performed for EDM-controlled data sets.
This message follows message CTT356W, which specifies the data set for which stacking stopped.
Stacking stops for the data set. The job continues without stacking for this dsn.
Corrective Action: Use the Rule Simulation Facility to find matching rules for the data set. Check matching rules for conflicts between stacking definitions and other definitions (for example, retention definitions).
Explanation: TEST mode is specified in the matching rule. Stacking is not performed for data sets matched by rules with mode TEST.
This message follows message CTT356W which specifies the data set for which stacking has stopped.
Stacking stops for the data set. The job continues without stacking for this dsn.
Corrective Action: Use the Rule Simulation Facility to find matching rules for the data set. Check matching rules for conflicts between stacking definitions and other definitions (for example, mode definitions).
Explanation: The matching rule contains vault entries, and the stacking algorithm specified by the STKMODE parameter in the CTTPARM member does not allow vault matching.
This message follows message CTT356W, which specifies the data set for which stacking stopped.
Stacking stops for the data set. The job continues without stacking for this DSN.
Corrective Action: Do the following:
To use vault matching in the stacking algorithm set STKMODE to R or A.
Explanation: The data set to be stacked is not in the Stacking Database, and a default size value is not specified. The search process must locate the data set record in the Stacking Database to determine its average size.
This message follows the CTT356W message, which specifies the data set for which stacking stopped.
Stacking stops for the data set. The job continues without stacking for this data set.
Corrective Action: Do one or more of the following:
Explanation: The specified data set record is marked NOT STACKABLE in the Stacking Database. Stacking cannot be performed for NOT STACKABLE data sets.
This message follows message CTT356W which specifies the data set for which stacking stopped.
The data set record was marked NOT STACKABLE for one of the following reasons:
Stacking stops for the data set. The job continues without stacking for this dsn.
Corrective Action: No action is required.
Explanation: The matching rule specifies a pool not defined to Control-M/Tape.
This message follows message CTT356W, which specifies the data set for which stacking stopped.
Stacking stops for the data set. The job continues without stacking for this dsn.
Corrective Action: Do the following:
Explanation: The pool name in the matching rule has an invalid pointer in memory. It points to an area in memory that cannot be identified as a pool block.
This message follows message CTT356W, which specifies the data set for which stacking stopped.
Stacking stops for the data set. The job continues without stacking for this dsn.
Corrective Action: Reload the pool table into memory with the following operator command: S CTTINIT,PARM=‘RELOAD,TBLT=POOL’
Explanation: All volumes in all ranges of the specified pool were searched, and none satisfied the search process requirements. The search process searches all volumes in the specified pool for a stackable volume. The search starts at the last found volser, and checks volsers one at a time until the first searched volser is encountered (that is, until a loop is detected).
This problem is probably due to one of the following reasons:
This message follows message CTT356W which specifies the data set for which stacking stopped.
Stacking stops for the data set. The job continues without stacking for this dsn.
Corrective Action: Determine the reason for this error and correct the problem.
Explanation: The search process found that no Media entries were defined in CTTPARM. The search process uses the values specified for the Media parameters in CTTPARM to calculate the remaining size on a volume.
This message follows message CTT356W which specifies the data set for which stacking stopped.
Stacking stops for the data set. The job continues without stacking for this dsn. No data set stacking can be performed until this problem is corrected.
Corrective Action: Define Media parameters in CTTPARM, as explained in the Control-M/Tape chapter of the INCONTROL for z/OS Installation Guide. Definition of these parameters only takes effect after Control-M/Tape is brought down and restarted.
Explanation: This information message indicates that the specified immediate request for a scratch tape was changed to a deferred request by Control-M/Tape.
Under JES3, dynamic data set stacking is performed only in deferred mode. When a job is interpreted by JES3, Control-M/Tape searches the job for created data sets that are candidates for stacking. If any of the scratch requests for tapes for these candidate data sets are in immediate mode, Control-M/Tape changes them to deferred mode so that stacking can be performed.
The variables in this message are:
The job continues. The DD allocation is deferred so that stacking can be performed.
Corrective Action: No action is required.
Explanation: User Exit CTTX010 requested that stacking search processing be stopped for the data set. The exit request causes a halt in the stacking process for the data set specified in message CTT356W which follows this message.
Stacking stops for the data set. The job continues and a scratch volume is requested for the data set.
Corrective Action: No action is required.
Explanation: The silo function requested for a volume ended with a warning.
The software of the robotic tape library returns the operation code opc, the return code rc in decimal format, and the reason rsn in hexadecimal format.
In this message, modName is one of the following Automated Tape library Interface module names:
If modName indicates the last library to be searched, the CTTRBM utility continues processing with the next volume. If modName indicates a library other than the last library to be searched, the CTTRBM utility searches for the same volume (volser) in the next tape library.
Corrective Action: Refer to the messages and codes documentation for your tape robot or silo for a description of the codes returned in this message.
Explanation: CTTVVM cannot process the volume whose serial number is volser, because it has no vaulting pattern. The CTTVVM utility groups logical volumes by their vaulting patterns. No vaulting pattern is an integrity error in the Media Database (MDB).
The CTTVEXP utility issues error message CTT344E and does not include the volser volume serial number in the Export List file.
Corrective Action: Use the CTTIDB utility to check the integrity of the MDB. Then, fix the errors.
Explanation: This information message specifies the serial numbers for a logical volume (log_volser) that should be imported, and the physical volume (phys_volser) from which it should be imported. The CTTVVM utility determines when a logical volume should be imported back to the Virtual Tape Server (VTS) .
The CTTVVM utility produces an Import List File for the volume with the specified serial number.
Corrective Action: Issue an IMPORT command. Refer to the previous CTT347I message for the serial number of the Import List volume.
Explanation: The CTTVVM or CTTVEXP utility could not run because Control-M/Tape is not active. Control-M/Tape intercepts OAM messages about completion of the export operation in a real-time environment. For this reason, Control-M/Tape must be active when the CTTVVM and CTTVEXP utilities run.
The specified utility stops.
Corrective Action: Start Control-M/Tape and rerun CTTVVM and CTTVEXP.
Explanation: Control-M/Tape tried to perform the func function on the volser volume in the robotic tape library, but the robotic tape library returned an error because the tape is currently being used by the robotic tape library.
The utility continues processing. The IOA Functional Monitor will later automatically retry the func function on the volser volume.
Corrective Action: No action is required.
Explanation: An error occurred during "volume cleanup" or "label cleanup."
Volume cleanup is the deletion from the Media database of all data set records of a volume.
Label cleanup is the deletion from the Media database of a database record.
Cleanup occurs when
The variables in this message are:
Possible values of rsn, and their explanations, are shown in the following table:
rsn |
Explanation |
|---|---|
0001 |
No data set record for L-Index |
0002 |
Attempt to remove an active data set |
0003 |
Active data set on a non-active volume |
0004 |
Record of the first volume of the data set not found |
0005 |
The first volume of the multi-volume chain differs from the first volume of the data set |
0006 |
Non-active volume in an active multi-volume chain |
0007 |
The volume update function failed for a volume |
0008 |
The update function failed for a volume |
0009 |
A data set that had already been found could not be read at deletion time |
0010 |
Data set deletion failed |
0011 |
Next volume expected but not found |
0012 |
A volume other than the first in a multi-volume chain could not be read |
0013 |
A volume other than the first in an active multi-volume chain is not active |
0014 |
The volume update function failed for a volume other than the first in a multi-volume chain |
0015 |
The first volume in a multi-volume chain differs from the first volume of a data set (other than the first) |
0016 |
The update function failed for a volume other than the first in a multi-volume chain |
0017 |
Database access error while reading the L-index |
0018 |
The expected L-index was not found |
0019 |
The L-index has a non-matching RBA |
0020 |
An attempt to delete the L-index failed |
0022 |
The update function failed for a data set (DDSVOLS#) |
The cleanup process is performed only for the current volume in the multi-volume chain of which it is part. Processing continues normally.
Corrective Action: Use the CTTIDB utility to check the logical integrity of the Media database, and correct all errors that are reported by the utility. For more information, see the description of verifying Media database integrity in the Control-M/Tape Implementation Guide.
Explanation: This information message is a column header for message CTT381I.
This message is followed by message CTT381I.
Corrective Action: No action is required.
Explanation: This information message contains summary information on each data set for which statistical calculations regarding average data set size have been performed.
This CTT381I message follows the CTT380I message, which provides column headers for the information in this CTT381I message.
The variables in this message are:
Corrective Action: No action is required.
Explanation: Open of the ddName DD statement failed.
Possible causes are:
Execution stops.
Corrective Action: Correct the JCL of the job and rerun.
Explanation: An invalid parameter was specified.
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.
Parent Topic |