|
|
|
|
|
This group includes messages for the Control-M/Tape product.
Explanation: A sort program that has been activated internally ended with an unexpected return code (rc).
The program stops executing with a condition code higher than 08.
Corrective Action: Refer to documentation for the sort program and to the sort messages of the job to clarify the reason.
Explanation: Control-M/Tape failed during the dynamic installation process for MVS Tape Label Processing Exits.
The started task of Control-M/Tape real-time environment is stopped.
Corrective Action: Contact BMC technical support.
Explanation: Control-M/Tape failed during the dynamic installation process for MVS Tape Label Processing Exits. Control-M/Tape found an inconsistency between the modules in the LPA and in the SYS1.LPALIB library.
The started task in the Control-M/Tape real-time environment is stopped.
Corrective Action: Make sure the module in error is match between the LPA and SYS1.LPALIB. If you have recently applied the IBM PTF to the SYS1.LPALIB library, then perform an IPL or add the LPALIB DD statement to the CTTINIT procedure that points to the SYS1.LPALIB library before applying the IBM PTF.
Explanation: The Add/Delete action for Control-M/Tape exit routine CTTHCKE of the HZSADDCHECK exit ended with an unexpected return code and reason code.
Control-M/Tape continues to initialize/terminate normally.
The Control-M/Tape check is not added to or deleted from IBM Health Checker.
Corrective Action: To clarify the reason for this issue, refer to the IBM documentation for IBM Health Checker and the CSVDYNEX macro.
Explanation: The specified requested action (either ADDNEW or DELETE) for a Control-M/Tape check by IBM Health Checker ended with an unexpected return code and reason code.
Control-M/Tape continues to initialize/terminate normally.
The Control-M/Tape check is not added to or deleted from IBM Health Checker.
Corrective Action: To clarify the reason for this issue, refer to the IBM documentation for IBM Health Checker and the HZSCHECK macro.
Explanation: Control-M/Tape was unable to add its check to IBM Health Checker.
Possible RC values are:
Corrective Action: For more information, refer to the IBM documentation for IBM Health Checker and for the CSVDYNEX and HZSCHECK macros.
Explanation: This information message follows other messages concerning the dynamic intercept process and identifies the module and CSECT in error.
Corrective Action: No action is required.
Explanation: One of the dynamic intercepts failed verification. Verification of an MVS module failed. The verification is done against the module in memory (LPA). The module or CSECT names are identified by CTT420I.
The dynamic intercept process is terminated. The failing CSECT is dumped into the data set pointed to by the DADUMP DD statement.
Corrective Action: Make sure that the intercepts are not already applied. Keep the dump of the failing CSECT. Contact BMC Customer Support.
Explanation: One of the dynamic intercept modules was not found in the Active LPA Queue (FLPA or MLPA) or in PLPA. The module is searched in the LPA, MLPA, or FLPA of the current active system.
The dynamic intercept process is terminated.
Corrective Action: Contact BMC Customer Support.
Explanation: One of the dynamic intercept CSECTs was not found in the modName module. The CSECT is searched in the specified module that resides in your STEPLIB libraries or in the cataloged SYS1.LPALIB library.
The dynamic intercept process is terminated.
Corrective Action: Contact BMC Customer Support.
Explanation: An internal error occurred in the dynamic intercept process.
The dynamic intercept process is terminated. All the intercepts already processed are rejected. The module or CSECT names are identified by CTT420I.
Corrective Action: Contact BMC Customer Support.
Explanation: The specified action failed for the specified DD statement.
The dynamic intercept process is terminated.
Corrective Action: Contact BMC Customer Support.
Explanation: There is a difference in length between the memory copy (in LPA) and the disk copy (in SYS1.LPALIB) of a specified module. This situation indicates a problem in the environment.
The dynamic intercept process continues.
Corrective Action: No action is required.
Explanation: The SVCUPDTE function failed with the specified return code. The Control-M/Tape SVC could not be installed.
The dynamic intercept process is terminated.
Corrective Action: Contact BMC Customer Support.
Explanation: This information message indicates that the dynamic intercept process is reversed and the MVS intercepts are being removed.
This message is the result of one of the following:
If the reason for this message is failure of the dynamic intercept process, after the intercepts are removed, the currently executing utility (CTTINIT or CTTHSMP) terminates.
Corrective Action: No action is required.
Explanation: Removal of Control-M/Tape intercepts failed. The expected intercept code was not found.
The Dynamic Intercepts Removal Process stops.
Corrective Action: Notify BMC Customer Support.
Explanation: The input to the CTTHSMP utility contains information on MVS MOD entries that belong to more than one FMID. The CTTHSMP utility cannot operate on input that contains several FMIDs.
The program terminates with a return code of 12.
Corrective Action: Provide input to the CTTHSMP utility in a single FMID MOD group.
Explanation: Too many UMID or RMID entries were added to the work area in the CTTHSMP utility. The utility cannot process more than 20,000 entries.
The program terminates with a return code of 16.
Corrective Action: Call BMC Customer Support.
Explanation: The CTTHSMP utility detected a UMID in an IBM MOD entry. IBM MODs do not normally have UMIDs. The detected UMID can indicate the existence of an IBM APAR fix or a hook applied for another product.
The program continues processing but ends with a return code of 4.
Corrective Action: Check which modifications apply to the relevant module and change accordingly.
Explanation: Control-M/Tape could not locate the elements necessary to install optional component opt_cpnt. Possible causes are:
Control-M/Tape continues operation without optional component opt-cpnt.
Corrective Action: Contact BMC Customer Support.
Explanation: An error occurred while trying to install or remove the Control-M/Tape WTO Intercept.
The dynamic intercept process is terminated.
Corrective Action: Call BMC Customer Support.
Explanation: The CTTWTOI module in the Control-M/Tape Load library does not contain the expected header.
The dynamic intercept process is terminated.
Corrective Action: Call BMC Customer Support.
Explanation: As part of the Control-M/Tape termination process, when trying to remove the Control-M/Tape WTO Intercept, the current WTO module (SVC 35) was not identified as the Control-M/Tape Intercept.
The dynamic intercept process is terminated. A snap of the current WTO SVC is provided under the DADUMP DD name.
Corrective Action: Check if some other program product at your site is interfering with MVS WTO and installing its own WTO Intercept. If not, call BMC Customer Support.
Explanation: The CTTVTM utility initiated the movement of the vol volume to a new location, but the status of the volume was changed by another job before the volume record was updated in the Media database.
The volume is not moved to a new location, although the movement appears in the utility output report.
Corrective Action: Do not move the volume. Ignore the vol entry in the CTTVTM utility output report.
Explanation: During a run of the CTTVTM utility with MODE set to CONVERT, the specified volume was marked vaulted but its current location was not found in the vault pattern of the matching rule of the volume data set.
The CTTVTM utility moves the volume to MAINLIB in the Distribution Report and marks it as a potential vault.
Corrective Action: Check the vault pattern of the rule that matches the volume’s data set and change it to include the current location name. Then rerun the CTTVTM utility.
Explanation: No rule was found for the data set used to determine the vaulting pattern for volume volser. Possible causes are:
This message is accompanied by message CTT202, which supplies the name of the data set used to determine the vaulting pattern for this volume.
If MODE was set to CONVERT, the volume is marked as MANUALY VAULTED.
In both CONVERT and RECALC modes, the volume is assigned the current location, and the expiration date of the data set that is used to determine the vaulting pattern of the volume.
Corrective Action: If a rule should have existed for the data set, define this rule and rerun CTTVTM with MODE set to RECALC.
Explanation: The RESLOT parameter and SLOTBLD or BOXBLD mode were specified for the CTTVTM utility. The RESLOT=YES and MODE=SLOTBLD or MODE=BOXBLD expressions cannot be both specified for the same run of the CTTVTM utility.
CTTVTM stops execution.
Corrective Action: If you want to run the CTTVTM utility with RESLOT=YES, change the mode of the utility to REGULAR or RECALC; otherwise, remove the RESLOT=YES option.
Explanation: The CTTVTM utility detected a logical error while processing the Media Database (MDB). CTTVTM accesses the volumes in a box by locating all its associated records. In this case, the box record number identified in the message cannot be located in the MDB. As a result, the data accessed for this box might be incomplete.
CTTVTM continues processing.
Corrective Action: If it is important to obtain precise data for the box in question, run CTTVTM in the BOXBLD mode.
Explanation: The CTTVTM utility detected that the number of volumes in the box found in the box record differs from the number of volumes actually in the box (count), based on information from the volume records (num). The two values should match.
The utility continues processing.
Corrective Action: Contact your IOA database administrator.
Explanation: The CTTVTM utility detected that the list of volumes in the box detailed in the box record, does not match the volumes that are actually found in the box, based on the information in the volume records. The two lists should match.
The utility continues processing.
Corrective Action: Contact your IOA database administrator.
Explanation: The CTTVTM utility detected that the location of the volume (vol_loc) is different than the location of the box in which the volume is contained. The two locations should match.
The utility continues processing.
Corrective Action: Contact your IOA database administrator.
Explanation: The CTTVTM utility did not find any box definition records in the Media Database (MDB), but found volumes that should be vaulted by box. Box records must be defined so vaulting by boxes can take place. To build box records, first the box must be defined and then the CTTVTM utility must be executed with the BOXBLD parameter.
The utility continues processing.
Corrective Action: If vault by boxes is required, define the box records and rerun CTTVTM. If the volumes need not be vaulted by box, change the Vault By Box parameter in the Rule Definition screen (screen TR) to ‘N.’
Explanation: The CTTVTM utility found that the record of box (boxId), does not exist in the Media Database (MDB), although at least one volume in the MDB is marked as being in the box.
The utility continues processing.
Corrective Action: Contact your IOA database administrator.
Explanation: The CTTVTM utility cannot find an empty box for the media specified to be used for vaulting by boxes. Volumes in the media specified in the message are marked to be vaulted by boxes. This cannot be carried out, since no more empty boxes are available for this media.
The utility continues processing.
Corrective Action: Check that all the boxes that are supposed to be available for this media are in fact available. If no problem can be found in the availability of the boxes, then define more boxes for this media.
Explanation: The CTTVTM utility was unable to move all volumes belonging to the box. The volumes that cannot be moved are listed in CTT202I messages that follow this message.
The utility continues processing without updating the new location of the volumes listed in CTT202I. Therefore, these volumes should be ignored even though they are listed in the CTTVTM report.
Corrective Action: See the previous error message.
Explanation: The CTTVTM utility was invoked with the BOXBLD parameter, but the box ranges defined in the MAINLIB library with prefix box_pref and media media_type overlap each other, causing duplicate box IDs. Each box ID must be unique.
The utility terminates with no action taken. No box is defined.
Corrective Action: Check and correct the box definitions. Rerun the CTTVTM utility with the BOXBLD parameter.
Explanation: MODE was set to BOXBLD in a simulation run of the CTTVTM utility. MODE cannot be set to BOXBLD in a simulation run of the CTTVTM utility.
The utility does not start processing.
Corrective Action: If you would like to define new boxes or to change existing box definitions, remove the SIMULATION option and rerun CTTVTM.
Explanation: The CTTVTM utility was invoked with the BOXBLD parameter, but the specified box ID is in use and was not defined. All boxes presently in use must be included in the box definitions in the MAINLIB library.
The utility terminates with no action taken (no box is defined).
Corrective Action: Check the box definitions. Verify that all boxes in use have correct definitions. Rerun the CTTVTM utility with the BOXBLD parameter.
Explanation: The CTTVTM utility was invoked with the BOXBLD parameter, but a box already in use was defined with a media type different from the one specified in its previous definition. Attributes of a used box cannot be changed.
CTTVTM terminates with no action taken. No box is defined.
Corrective Action: Specify the correct media type for this box, or range of boxes. Rerun the CTTVTM utility with the BOXBLD parameter.
Explanation: The CTTVTM utility was invoked with the BOXBLD parameter, but a box already in use was defined with a new box size. Attributes of a box in use cannot be changed.
The utility terminates with no action (no box is defined).
Corrective Action: Specify the correct size for this box or range of boxes. Rerun the CTTVTM utility with the BOXBLD parameter.
Explanation: The volume (volser) has been marked for vault by box, but MAINLIB is one of the locations specified in its vault pattern. A volume cannot be vaulted by a box if it has MAINLIB as one of the locations in its vault pattern.
The utility continues processing.
Corrective Action: Remove the mark from the volume so that it is not vaulted by box, or remove MAINLIB from the volume vault pattern.
Explanation: Exit CTTX006 rejected a Media Database (MDB) update of the specified volser that was requested by the utility. The utility tried to update the specified volume information in the MDB. Database. However, the update operation was rejected by Exit CTTX006. This may cause an integrity error in the MDB.
The utility continues. The specified volume information is not updated.
Corrective Action: Make sure an integrity error was not created due to the rejected update. Consider modifying Exit CTTX006 in case of unexpected rejections. Ignore this message if the rejection is expected.
Explanation: An attempt has been made to run the CTTVTM utility in SLOTBLD or BOXBLD mode, but with at least one INCLUDE or EXCLUDE statement in the input statements of the utility.
The utility stops processing.
Corrective Action: Remove all INCLUDE and EXCLUDE statements from the input statements of the utility and rerun the utility.
Explanation: The automated tape library residence status of the specified volume was set by the CTTSYNC utility in the Media Database (MDB). The CTTSYNC utility synchronizes the automated tape library residence status of MDB volumes according to the actual residence in the automated tape library.
The status of the volume in the MDB was changed to represent its actual status. The utility continues processing.
Corrective Action: No action is required.
Explanation: The automated tape library name of the specified volume was set by the CTTSYNC utility in the Media Database (MDB). The CTTSYNC utility synchronizes the automated tape library name of the MDB volumes from the name that was previously recorded in the MDB (oldLib) to the library name where the volumes actually reside (newLib).
The status of the volume in the MDB was changed to represent its actual status. The utility continues processing.
Corrective Action: No action is required.
Explanation: The status of the indicated volume in the automated tape library was set by the CTTSYNC utility according to its status in the Media Database (MDB). The CTTSYNC utility synchronizes the status of volumes in the automated tape library with the equivalent status in the MDB.
The status of the volume in the automated tape library was changed to agree with its status in the MDB. The utility continues processing.
Corrective Action: No action is required.
Explanation: This information message indicates that the CTTSYNC utility synchronized the automated tape library with the Media Database (MDB) and found that the volume resides in the automated tape library. The CTTSYC utility then updated the MDB.
The utility continues processing.
Corrective Action: No action is required.
Explanation: This information message indicates that the CTTSYNC utility synchronized the automated tape library type with the Media Database (MDB), determined the volume type, and updated the MDB accordingly.
The utility continues processing.
Corrective Action: No action is required.
Explanation: This information message indicates that the CTTSYNC utility retrieved the DFSMS Storage Group of the volume from the automated tape library database, and updated the Media database accordingly.
The utility continues processing.
Corrective Action: No action is required.
Explanation: The volser is controlled by DFSMShsm or Control-V, but it is not defined in the Control-M/Tape Media database.
Normal processing continues.
Corrective Action: Check why the volume is not defined in the Media database. If the volume should be defined in Control-M/Tape Media database, then use the CTTMUP utility to add the volume and its datasets to the Media database.
Explanation: The volser is controlled by DFSMShsm or Control-V, but its status in the Media database is not active or not it is not under EDM control.
Normal processing continues.
Corrective Action: Use the CTTMUP utility to update the volume record in the Media database to its correct status.
Explanation: The volser is not controlled by DFSMShsm or Control-V, but it is marked as active and under EDM control in Control-M/Tape Media database.
Normal processing continues.
Corrective Action: Verify that the volume is really not controlled by any of the External Data Managers (for example DFSMShsm, CA-Disk, or ExHPDM) used at your site, and scratch the volume in the Media database using the CTTMUP utility.
Explanation: The RBTTYPE parameter is set to NONE in the CTTPARM. The CTTSYNC utility cannot perform synchronization with any automated tape library.
The Utility ends.
Corrective Action: Specify the necessary ATL in the RBTTYPE parameter and rerun the utility.
Explanation: Control-M/Tape did not detect a valid statement at the beginning of the SYSIN file. The SYSIN file for the utility must begin with a valid statement. The SYSIN file is empty or the first control statement is invalid.
The utility stops executing.
Corrective Action: Correct the statements in the SYSIN file, and rerun the utility.
Explanation: The CTTIDB utility detected that the previous run of the specified Control-M/Tape utility abended.
In this message, dd/ mm/ yyyy is the date of the abending execution of the utility, and hh: mm: ss is the abending execution time.
The CTTIDB utility continues processing.
Corrective Action: Locate and correct the cause of the error. Rerun the utility.
Explanation: This information message indicates that phase n out of m phases of the specified utility started or ended. This message can help in estimating the execution time of the specified utility.
If this message does not indicate the end of the last phase of the utility, the specified utility continues processing.
Corrective Action: No action is required.
Explanation: This information message indicates that a Control-M/Tape utility has processed n percent of the records of the specified record type. This message can help in estimating the execution time of the utility.
The utility continues processing.
Corrective Action: No action is required.
Explanation: This information message indicates that a Control-M/Tape utility has processed n records of the specified record type. This message can help in estimating the execution time of the utility.
The utility continues processing.
Corrective Action: No action is required.
Explanation: Control-M/Tape discovered that the volser belongs to an invalid multivolume group in the Media Database (MDB). The first_vol variable indicates the first volume in the volume group.
Possible values of rc are:
Control-M/Tape stops processing the invalid multivolume group.
Corrective Action: Use the CTTMUP utility to correct invalid fields in volume records within the multivolume group.
Explanation: This information message indicates that a Control-M/Tape task was about to update a Media Database (MDB) record but discovered that the record was changed by another task.
The record is not updated in the current task.
Corrective Action: If the update was requested from the Online Facility, check the record, and if the update is still required, repeat the request.
Explanation: This information message indicates that the CTTRTM utility updated retention information in volume and data set records when running in either CONVERT or RECALC mode.
This message is followed by message CTT202I, which shows the Media Database (MDB) record being handled.
Corrective Action: No action is required.
Explanation: This information message indicates that the user was running the CTTRTM utility, and specified INCLUDE or EXCLUDE statements to select Media Database (MDB) records.
This message is followed by message CTT202I which shows the Media Database (MDB) record being handled.
Corrective Action: No action is required.
Explanation: A previous run of the CTTRTM utility or the CTTVTM utility abended. The current utility run includes the Automatic Restart mode. However, the user set RESTART to NO in the TYPERUN statement to prevent restarting the utility.
The utility continues running without restarting.
Corrective Action: No action is required.
Explanation: When applying retention criteria to a Media Database (MDB) data set record, Control-M/Tape discovered that more than three retention factors were specified for a data set. Data set retention information is stored in data set records by either the real-time environment when creating a data set, or by the CTTRTM utility in either RECALC or CONVERT mode.
Extraneous retention factors are ignored. Message CTT202I showing the Media Database (MDB) record being handled, is issued after this message.
Corrective Action: Check the matching Control-M/Tape rule, using the Rule Definition screen (Screen TR), and the JCL EXPDT parameter for the data set, and remove any extra retention factors.
Explanation: After modifying the Media Database (MDB) records, Control-M/Tape tried to make the equivalent changes in databases of the robot systems (automated tape libraries). To be able to update databases of the robot systems such as StorageTek or IBM 3495, the Control-M/Tape task must be APF-authorized, since this is required by interfaces to the robot systems.
The robot system databases are not updated.
Corrective Action: Contact your system programmer to make the Control-M/Tape task APF-authorized.
Explanation: According to the matching rule, Control-M/Tape requires that retention criteria for a data set be provided by the JCL EXPDT parameter when creating the data set. However, the JCL EXPDT parameter was not supplied in the JCL. The message is issued by one of the following:
If the message is issued by the Control-M/Tape real-time environment, the ddName parameter will be displayed. In other cases, the message will be followed by message CTT202I, which shows the Media Database (MDB) record being handled.
Installation default retention criteria are applied to the data set record.
Corrective Action: Supply the JCL EXPDT parameter in the DD statement when creating a data set. To change the retention criteria of the data set record that was created using the default retention criteria, use the CTTMUP utility.
Explanation: Control-M/Tape has updated a vaulted volume, and has unsuccessfully tried to update the appropriate Slot Definition record, to synchronize its data with the newly updated Volume record.
The Slot Definition records are created by the CTTVTM utility, according to the vault definitions that the user specifies in the Control-M/Tape Vault Definition screen (Screen TV).
The Slot Definition record is not updated.
Corrective Action: Check vault definitions using the Vault Definition screen (Screen TV), and then run the CTTVTM utility in mode SLOTBLD to synchronize the Slot Definition records with the Volume records.
Parent Topic |