Global Test Mode

This chapter includes the following topics:

• Overview

• Preparation

• New Day Procedure

• Operating in Test Mode

OverviewLink copied to clipboard

Global Test mode is used to observe Control-M/Tape functioning and to adjust Control-M/Tape rules and definitions to eliminate inconsistencies between the existing tape management system and Control-M/Tape. The object of this stage of implementation is to reach a situation in which Control-M/Tape makes the same media management decisions as your current tape management system.

In Global Test mode, Control-M/Tape records information in the Media Database, but does not intervene in any way with media processing (for example, expired data sets are not uncataloged, and volumes are not rejected). All media processing is managed by the existing tape management system.

Global mode of operation is determined by the MODET parameter in the CTTPARM member. Mode of operation can also be specified for specific Control-M/Tape rules. However, when Global Test mode is specified, all rules operate in Test mode regardless of the mode specified in each rule definition.

Before Control-M/Tape is activated in Global Test mode, verify that Control-M/Tape parameters have been set properly, modify user exits as necessary, and implement interfaces with relevant system components (for example, external data managers and automated tape libraries).

While Control-M/Tape is operating in Global Test mode, monitor the databases of Control-M/Tape and the other tape management system, and compare the reports from both systems. If inconsistencies are detected, it may be necessary to modify Control-M/Tape rules and/or regenerate the Media Database by reconverting the database of the other tape management system.

This chapter describes

• preparation for operating in Global Test mode

• Set installation parameters.

  • Establish initialization procedures and New Day procedures.

  • Prepare Control-M/Tape reports.

  • operation of Control-M/Tape in Global Test mode

• Start Control-M/Tape in Global Test mode.

  • Monitor synchronization of the Media Database and the existing tape management system database.

  • Review System and Job log messages.

PreparationLink copied to clipboard

Before Control-M/Tape is activated in Global Test mode, information in the existing tape management system’s database and definitions must be converted to Control-M/Tape format. For more information, see the Control-M/Tape Conversion Guide.

Installation Parameter ConsiderationsLink copied to clipboard

The CTTPARM member in the IOA PARM library contains Control-M/Tape installation parameters. These parameters are defined during installation of Control-M/Tape.

Before implementing Control-M/Tape in Global Test mode, make sure that Control-M/Tape installation parameter settings are compatible with the existing tape management system and with the environment in which Control-M/Tape is to be implemented.

Adjust the parameters in a way that does not affect your production environment.

Adjust the parameters in a way that is compatible with the existing tape management system. Do not implement features that do not exist in the other tape management system. Doing so may prevent synchronization of Control-M/Tape with the other tape management system.

Make sure that the following CTTPARM parameters are set appropriately before activating Control-M/Tape in Global Test mode. These parameters are grouped by function in the CTTPARM member, but are listed below in alphabetical order for easier reference.

Table 4 CTTPARM Parameters

DO RETENTION=DAYS       0030           And/Or  A               JCL EXPDT                         And/Or

New Day ProcedureLink copied to clipboard

The New Day procedure is the primary mechanism used to perform daily maintenance on the Control-M/Tape Media Database and related files. The New Day procedure (job CTTDAY), can be activated automatically by a scheduler (for example, Control-M) at a predefined time each day. It can also be activated manually.

When establishing the New Day procedure for Global Test mode:

• Ensure that the order in which various tasks are performed in the New Day procedure is compatible with the existing tape management system. For example, retention management precedes vault management in CA-1, while vault management precedes retention management in CA-TLMS.

• Two New Day procedure members (CTTDAY and CTTDAYT) are provided with Control-M/Tape, each with an alternate order of procedures. Ensure that the correct one is used at your site.

If the order of procedures in the Control-M/Tape New Day procedure is different from the order in the other tape management system, it could lead to inconsistencies in retention (reflected in the daily scratch and vaulting reports).

• Determine which functions should be performed during Global Test mode (for example,retention and vault management processing) and which should not be performed (for example, automated tape library management procedures).

• Comment out (//*) the JCL steps that you do not want to run while in Global Test mode (for example, stacking statistics collection). Do not delete these steps. They are used when Control-M/Tape is activated in Global Phased mode and Global Production mode.

• Make sure that utilities called by the New Day procedure are compatible with the existing tape management system (for example, retention is processed in the same way).

• Make sure that compatible report formats are used. Customize Control-M/Tape report formats to match the existing system.

Control-M/Tape maintenance functions should run in parallel with (at the same time as) the maintenance utilities of the existing tape management system at your site. New Day procedure CTTDAY is compatible with most tape management systems. If you are converting from CA-TLMS, run CTTDAYT in the JCL library instead of CTTDAY. In CTTDAYT, the vaulting step precedes the retention step in order to maintain compatibility with CA-TLMS.

The following tasks are performed by the New Day procedure:

• Rule Refresh.

• Retention Management (CTTRTM).

• Vault Management (CTTVTM).

• Gathering Data Set Size Statistics for Stacking (CTTSTK).

• Media Database and Trace File Backup (CTTTRB).

Each of these tasks is described below, with special attention given to issues relevant for Control-M/Tape operations in Global Test mode.

New Day Procedure JCLLink copied to clipboard

Below is a sample JCL for the Control-M/Tape New Day procedure. Note the order in which the various tasks are performed. Also note that the CTTTRB job is run both before and after backup of the Media Database to indicate the start and end of the backup procedure.

Figure 4 Sample JCL for New Day Procedure

//I610INDY JOB  ,IOA610,MSGCLASS=X,CLASS=A
//*
//*
//*--------------------------------------------------------------
//*
//*               CONTROL-M/TAPE DAILY JOB
//*--------------------------------------------------------------
//*  THE BACKUP OF THE MEDIA DATABASE IS PERFORMED BY DFDSS.
//*  THIS BACKUP INCLUDES ALL THE MEDIA DATABASE EXTENTS.
//*  PLEASE CHANGE THE MEDIA DATABASE PREFIX IN SYSIN DD STATEMENT
//*  OF THE CTTBKPM STEP.
//*
//*  IN CASE YOU NEED TO RESTORE THE MEDIA DATABASE YOU HAVE
//*  TO USE DFDSS WITH RESTORE STATEMENT.
//*--------------------------------------------------------------
//*
//       JCLLIB  ORDER=%ILPREFA%.PROCLIB
//       INCLUDE MEMBER=IOASET%INSTID%
//*
//*--------------------------------------------------------------
//*  CHECK CONTROL-M/TAPE OPERATION MODE
//*--------------------------------------------------------------
//*
//CTTCHK   EXEC CTTINIT,
//       PARM='MODE=CHECK'
//*
//*--------------------------------------------------------------
//*  RELOAD CONTROL-M/TAPE RULES - THIS STEP IS OPTIONAL
//*--------------------------------------------------------------
//*
//CTTINIT EXEC CTTINIT,
//       PARM='MODE=RELOAD,TBLT=RULE'
//*
//*--------------------------------------------------------------
//*  CONTROL-M/TAPE RETENTION MANAGEMENT
//*--------------------------------------------------------------
//*
//CTTRTM  EXEC CTTRTM,REGION=32M
//CTTRTM.SYSIN  DD *
 TYPERUN   MODE=NORMAL
 TYPERET   MODE=REGULAR
 REPORT    NAME=SCRATCH,SUMMARY=YES
 FIELDS    ROWID,VOLSER,SLNAME,MEDIA,EXPDT,LACCDT,LOCATION,POOL,
  DSNAME,EXPDS
 SORTBY    POOL/B,VOLSER
/*
//*
//*--------------------------------------------------------------
//*  CONTROL-M/TAPE VAULTING MANAGEMENT
//*--------------------------------------------------------------
//*
//CTTVTM  EXEC CTTVTM,REGION=32M
//CTTVTM.SYSIN  DD *
 TYPERUN   MODE=NORMAL
 TYPEVLT   MODE=REGULAR
 REPORT    NAME=DISTRIB,SUMMARY=YES
 FIELDS    ROWID,VOLSER,DSNAME,TOSLOT,VOLSEQ,EXPDT,LBLTYP,CREJBN,CREDT
 SORTBY    FROMLOC/B,TOLOC/B,VOLSER
 REPORT    NAME=DISTRIB,SUMMARY=YES
 FIELDS    ROWID,TOLOC,VOLSER,FROMSLOT,TOSLOT,NEXTLOC
 SORTBY    FROMLOC/B,TOLOC,VOLSER
 REPORT    NAME=DISTRIB,SUMMARY=YES
 FIELDS    ROWID,FROMLOC,VOLSER,FROMSLOT,TOSLOT,NEXTLOC
 SORTBY    TOLOC/B,FROMLOC,VOLSER
/*
//*
//*--------------------------------------------------------------
//*  UPDATE CONTROL-M/TAPE STACKING DATABASE FROM THE TRACE FILE
//*--------------------------------------------------------------
//*
//CTTSTK  EXEC CTTSTK,SMFIN=NULLFILE,REGION=5M
//CTTSTK.SYSIN  DD *
 TYPERUN MODE=TRC
/*
//*
//*--------------------------------------------------------------
//*  BACKUP CONTROL-M/TAPE MEDIA DATABASE AND TRACE FILE
//*--------------------------------------------------------------
//*
//CTTTRB1 EXEC CTTTRB,PARM='BKP=START'
//*
//CTTBKPM EXEC PGM=ADRDSSU
//SYSPRINT DD SYSOUT=*
//TAPE     DD DISP=(,KEEP),UNIT=TAPE,
//            DSN=&DBPREFT..MDBBKP
//SYSIN    DD *            <<== CHANGE CONTROL-M/TAPE MEDIA PREFIX
 DUMP DATASET(                 -
    INCLUDE(CTT.V610.MDBD.E*)) -
    OUTDDNAM(TAPE)             -
    TOL(ENQF)
//*
//CTTBKPT EXEC PGM=IEBGENER
//SYSPRINT DD SYSOUT=*
//SYSUT1   DD DISP=SHR,DSN=&DBPREFT..TRC
//SYSUT2   DD DISP=(,KEEP),UNIT=TAPE,
//            DSN=&DBPREFT..TRCBKP
//SYSIN    DD DUMMY
//*
//CTTTRB2 EXEC CTTTRB,PARM='BKP=END'
//*
//*--------------------------------------------------------------
//*  ANALYZE THE MEDIA DATABASE
//*--------------------------------------------------------------
//*
//CTTIDB  EXEC CTTIDB
//SYSIN    DD *
 TYPERUN MODE=UPDATE,USEDAYS=7
//*
//*--------------------------------------------------------------
//*  ISSUE WARNING IF CTTDAY DID NOT FINISH SUCCESSFULLY
//*--------------------------------------------------------------
//*
//   IF (CTTVTM.CTTVTM.RC >= 8                         OR
//       CTTRTM.CTTRTM.RC >= 8                         OR
//       CTTSTK.CTTSTK.RC >= 8                         OR
//       CTTIDB.CTTIDB.RC >= 8                         OR
//       CTTINIT.CTTINIT.RC >= 8                       OR
//       CTTBKPM.RC >= 8                               OR
//       CTTBKPT.RC >= 8                               OR
//       ABEND)  THEN
//WARNING  EXEC PGM=CTM35F
//         INCLUDE MEMBER=&IOAENV
//SYSPRINT DD SYSOUT=*
//DA35F    DD DISP=SHR,
//     DSN=&OLPREFT..PARM(WARNDAY)
//   ENDIF
//*---------------------------------------------------------------
//*
//

External Data ManagersLink copied to clipboard

Control-M/Tape supports various External Data Managers (EDMs) such as DFSMShsm. These managers each have their own method of naming and tracking their data sets and volumes. Control-M/Tape allows the EDM to manage and expire EDM-controlled volumes, while Control-M/Tape tracks activity and supervises access of these volumes. EDM volumes are identified to Control-M/Tape through DO RETENTION=EDM statements in Control-M/Tape rule definitions.

BMC recommends that you implement the Control-M/Tape interface to the EDM in use at your site while operating Control-M/Tape in Global Test mode. The EDM interface enables Control-M/Tape to detect when the EDM scratches a tape, so that Control-M/Tape can update the Media Database accordingly. For more information on EDM interface implementation, see External Data Managers.

Restart Management InterfaceLink copied to clipboard

If the other tape management system at your site has an interface to a restart management product (for example, Control-M/Restart,) the Control-M/Tape interface to this product should be implemented as well. For more information, see the INCONTROL for z/OS Administrator Guide.

DFSMS ImplementationLink copied to clipboard

If the DFSMS System Managed Tape feature is used to manage tape data sets at your site, the Control-M/Tape interface to DFSMS should be implemented before Control-M/Tape is activated in Global Test mode. For information on how to implement this interface, see Control-M/Tape DFSMS Interface.

Control-M/Tape ReportsLink copied to clipboard

Control-M/Tape reports are produced through the CTTRTM, CTTVTM and CTTRPT utilities. Customize Control-M/Tape reports in a format similar to the reports of the other tape management system at your site. This makes it easier for you to compare reports and make necessary adjustments to tape management definitions. For information on how to customize the format of Control-M/Tape reports, see the descriptions of these utilities in the INCONTROL for z/OS Utilities Guide.

The CTTRTM utility produces a Scratch report listing all volumes that were expired (meaning, became scratch) as a result of the run of the utility. Figure 5 shows a sample of the default format for this report.

Figure 5 Sample Scratch Report

BMC SOFTWARE, INC. CONTROL-M/TAPE REPORT (VER 6.1.00)    DATE 08/08/2000 TIME 15.13    PAGE 1
List of Scratched Volumes
-------------------------
Pool Name:  $$NOPOOL
ROWID  VOLSER  SL-Name Media     Expiration  Last      Location  Dataset           Dataset
                                 Date        Access              Name              Expiration
-----  ------  ------  --------  ----------  --------  --------  ----------------- ----------
1      MOMO01  MOMO01  CART      08/08/00    10/11/99  MAINLIB   N60.TEST.DS       Catalog
2      MOMO02  MOMO02  CART      08/08/00    10/11/99  MAINLIB   N60.TEST.DS       Catalog
3      CC0001  CC0001  CART      08/08/00    11/11/99  MAINLIB   N60.CYCLDS        Cycl+001
4      CC0002  CC0002  CART      08/08/00    11/11/99  MAINLIB   N60.CYCLDS        Cycl+001
5      NLTAP1  NLTAP1  CART      08/08/00    11/11/99  MAINLIB   N60.TEST.DS1      08/08/00
6      NLTAP2  NLTAP2  CART      08/08/00    11/11/99  MAINLIB   N60.TEST.DS2      08/08/00
7      NL0001  NL0001  CART      08/08/00    11/11/99  MAINLIB   N60.TEST.DSX      08/08/00
Total In $$NOPOOL       :      7

The CTTVTM utility produces a Distribution report.

It lists all volumes that should be moved to a new location or assigned a new slot number. Figure 6 shows a sample of the default format for this report.

Figure 6 Sample Distribution Report

BMC SOFTWARE INC. CONTROL-M/TAPE REPORT (VER 6.1.00)    DATE 08/08/2000 TIME 15.59    PAGE 1
Distribution Report
-------------------
From Location:  MAINLIB    To Location:  VTLA
ROWID VOLSER  Data Set Name            To     Volume    Expiration  Label  Create    Create
Slot   Seq. No.  Date        Type   Job       Date
----- ------  ------------------------ ------ --------  ----------  -----  --------  --------
1     D00001  N60.D01.ARCHIVE.G0194V00 2       1        Catalog     SL     PRARC015  07/07/00
2     X00001  N60.D01.ARCHIVE.G0213V00 1       1        Catalog     SL     PRARC017  07/07/00
3     V00001  N60.V01.ARCHIVE.G0210V00 3       1        Catalog     SL     PRARC022  07/07/00
4     V00002  N60.V02.ARCHIVE.G0211V00 4       1        Catalog     SL     PRARC023  07/07/00
5     V00003  N60.V03.ARCHIVE.G0198V00 5       1        Catalog     SL     PRARC019  07/07/00
Total In VTLA    :
Total In MAINLIB :      5

The CTTRPT utility is a general reporting utility that produces reports based on information in the Media Database. A wide variety of sample reports is provided with this utility. Additional report formats can be generated by manipulating the parameters of this utility.

Use this utility to produce reports that are similar to the reports produced by your existing tape management system (in addition to the Scratch and Distribution reports described in the preceding samples).

Operating in Test ModeLink copied to clipboard

After the preparations described above, convert tape management data at your site and activate Control-M/Tape in Global Test mode. (Conversion of tape management data is described in detail in the Control-M/Tape Conversion Guide.)

Both Control-M/Tape and the other tape management system should be started at the same time after the conversion process. The objective of Global Test mode is to ensure that Control-M/Tape operates in the same way as your existing tape management system and that the Control-M/Tape Media Database and the database of the other tape management system are synchronized.

Start Control-M/Tape in Global Test ModeLink copied to clipboard

Make sure that the MODET parameter is set to TEST in the CTTPARM member in the IOA PARM library.

Start Control-M/Tape using the following command:

S CTTINIT,PARM=INIT

Monitor Tape Management ReportsLink copied to clipboard

Monitor tape management database synchronization in the following ways:

Compare the reports generated by the retention and vault management facilities of Control-M/Tape and the other tape management system.

Scan the system log and job log for messages that indicate that Control-M/Tape did not agree with an action performed by the existing tape management system.

Synchronization of the Control-M/Tape Media Database with the existing tape management system’s database is monitored primarily through the Scratch and Distribution reports. These reports are produced by the daily maintenance procedures of Control-M/Tape and the other tape management system. The reports should be produced by both tape management systems at the same time and have identical information. Below is a description of each report and sample problems that can be detected through inconsistencies in these reports.

Scratch ReportLink copied to clipboard

The Scratch report lists all volumes that were expired (meaning, became scratch) during the most recent run of the CTTRTM utility. There should be the same number of scratch volumes on the Scratch report as on the equivalent report produced by the existing tape management system.

An inconsistency in a global definition (for example, default retention) can cause a large number of inconsistencies. Therefore, appropriate settings for global parameters should be given a high priority.

You can determine if a problem is due to a global definition by comparing retention definitions of a data set or volume that was treated differently by Control-M/Tape and the other tape management system.

If the retention definitions are the same, the problem may be due to a global definition. In this case verify that the following Control-M/Tape installation parameters were assigned the appropriate values:

• CTLGWAIT

• EXPDTDDN

• RTNTYPE

• CYCLECNT

• EXPDTYPE

• RTNUPD

• DEFEXPDT

• OVERJCL

• GRACECAT

• GRACECYC

• EXPCAT

Resolving Retention DiscrepanciesLink copied to clipboard

The following table describes sample discrepancies that may be discovered when comparing Scratch reports of Control-M/Tape and the other tape management system:

Table 5 Retention Discrepancies and Resolutions

Distribution ReportLink copied to clipboard

The Distribution report is produced by the Vault Management facility (the CTTVTM utility). This report describes all volume movements between the active library (MAINLIB) and an external library, and between different external libraries.

The Distribution report lists all volumes that should be moved to a new location or assigned a new slot number. The CTTVTM utility checks each volume record’s vault specifications in the Media Database and determines which volumes should be moved to a new location according to their vault patterns. The current vault location in the volume record is updated and the new location for the volume is listed in the Distribution report. The information in the Control-M/Tape distribution report should contain the same information as the equivalent report produced by the existing tape management system.

An inconsistency in a global definition (for example, default retention) may be responsible for a large number of inconsistencies. Therefore, fixing global parameter settings should be given a high priority.

You can determine if a problem is due to a global definition by comparing vaulting patterns of a volume that was treated differently by Control-M/Tape and the other tape management system.

If the vaulting patterns are the same, the problem could be due to a global definition. In this case, verify that the following installation parameters have been properly defined:

• CYCLECNT

• VLTBYDS1

Resolving Vaulting DiscrepanciesLink copied to clipboard

The following table describes sample discrepancies that may be discovered when comparing the distribution reports of Control-M/Tape and the other tape management system:

Table 6 Vaulting Discrepancies and Resolutions

Monitor System and Job Log MessagesLink copied to clipboard

During Global Test mode, Control-M/Tape sends messages to the System log, Job log, or operator console if there is a contradiction between the existing tape management system’s actions and the actions Control-M/Tape would take if it were operating in Global Production mode. These messages can help you resolve inconsistencies found during comparison of scratch and distribution reports, and provide useful information on data integrity problems detected by the CTTIDB utility. For more information about this utility, see Chapter 5, "Verifying Media Database Integrity."

Most of these System and Job log messages are followed by message CTT146I.

CTT146I  JOB CONTINUES DUE TO TEST MODE

If Control-M/Tape were operating in Global Production mode, the job executing when the message was issued would be abended or the scratch tape would be rejected by Control-M/Tape. In Global Test mode, the job continues processing under the control of the existing tape management system. When the CTT146I message is sent to the log, Control-M/Tape bypasses the rest of the job and ignores all subsequent information produced by the job. This may result in additional inconsistencies between the existing tape management system and Control-M/Tape.

The following pages contain sample Control-M/Tape messages that may be sent to the System log or Job log as a result of an inconsistency with the existing tape management system. For each of these messages, it is important to investigate why the Control-M/Tape Media Database does not have the same information as the existing tape management system’s database. Be sure to check relevant earlier messages for a possible cause for the problem.

Potential ConflictsLink copied to clipboard

Problem 1 – File Sequence ErrorLink copied to clipboard

CTT107E 0123, FILES WITH HIGHER SEQUENCE NUMBERS EXIST ON VOLUME V00001 (OUTFILE,002)

A file was written on volume V00001, mounted on tape drive 0123, with sequence number 002 and a data set with a higher sequence number exists on that volume according to the information in the Control-M/Tape Media Database.

According to Control-M/Tape at least two data sets are already stored on this volume (V00001).

Since the other tape management system allowed this action, it apparently has no record of two or more data sets on this volume.

Problem 2 – Missing Previous FileLink copied to clipboard

CTT108E   0123, PREVIOUS FILE DOES NOT EXIST ON VOLUME VV0002 (OUTFILE,003)

A file with a specified sequence number (003) was written on volume VV0002, which is mounted on tape drive 0123, but no file with the preceding sequence number exists on the volume according to the Control-M/Tape Media Database.

Control-M/Tape requires file sequence numbers on a volume to be consecutive.

A data set with sequence number 002 would need to exist on this volume for Control-M/Tape to allow writing of a file with sequence number 003. According to Control-M/Tape, either one or no files exist on this volume.

Problem 3 – Data Set Name ConflictLink copied to clipboard

CTT109E   0123, DSNAME CONFLICTS WITH MDB DSNAME: DSN.VVV03 (INFILE,002)

An attempt was made to read a data set (specified in the JCL) with label 002 on a specific volume, and Control-M/Tape has no record of this data set on the specified volume. The specified volume contains data set DSN.VVV003 (meaning, not the requested data set) with the specified label number.

Problem 4 – Data Set Not FoundLink copied to clipboard

CTT110E   0123, DATA SET NOT FOUND IN MDB:  DSN.D0004 (INFILE)

A data set that is not found in the Control-M/Tape Media Database was read.

This message is issued only if the dynamic data set definition is not allowed (that is, DYNDS is set to N in the CTTPARM member).

The data set was either not converted from the existing tape management system, or it was added manually to the existing tape management system’s database and not to the Control-M/Tape Media Database.

During Global Test mode, make sure data sets are added consistently to the databases of both Control-M/Tape and the other tape management system. In Global Production mode, this error should not occur if DYNDS is set to Y in the CTTPARM member (that is, if the dynamic data set definition is activated).

Problem 5 – File Already ExistsLink copied to clipboard

CTT118E 0123, FILE ALREADY EXISTS: DSN.D0005 (OUTFILE)

An existing data set may have been overwritten.

The other tape management system allowed a data set to be written on the tape but, according to Control-M/Tape, the specified data set already existed on this tape and was overwritten.

Problem 6 – Non-Scratch Volume MountLink copied to clipboard

CTT125E 0123, V00006, NOT A SCRATCH VOLUME

A scratch tape was requested on the specified drive (0123). The tape supplied in response to this request (volume V00006) is not marked as scratch in the Control-M/Tape Media Database.

After a volume is mounted in response to a scratch request, Control-M/Tape verifies that the mounted volume is a scratch volume.

Problem 7 – EDM-Controlled VolumeLink copied to clipboard

CTT133E   0123, NON-EDM TRYING TO WRITE ON AN EDM VOLUME V00008

A job that is not an EDM (External Data Manager) wrote to a volume (V00008) that is marked as an EDM volume according to Control-M/Tape. The new information on this volume and the data sets it contains are not recorded in the Control-M/Tape Media Database. This results in discrepancies on the output reports.

If Control-M/Tape were operating in Global Production mode, the job would be abended. In Control-M/Tape, volumes marked as EDM-controlled can only be accessed by the EDM.

Problem 8 – Recreated Data Set on the Wrong VolumeLink copied to clipboard

CTT141E   0123, RECREATE ON WRONG VOLUME  VV0009

A data set was recreated on the specified volume (VV0009).

According to Control-M/Tape, this data set already existed on the volume, but the data set does not start on that volume. Control-M/Tape allows an existing data set to be overwritten only if the data set begins on the same volumes. Use the Control-M/Tape Inquire/Update screen to view the volume and data set information. For more information on conditions necessary for data set recreation, see the organization and administration chapter of the Control-M/Tape User Guide.

Assume, for this example, that volume VV0009 is the second volume of a multi-volume chain containing data set DSN.D0009. Control-M/Tape can only recreate data set DSN.D0009 starting from the first volume of the multi-volume chain. In Global Production mode, the job would abend.

Since the existing tape management system recreated this file starting on volume VV0009, the two databases are apparently not synchronized for either the data set or the volumes in the multi-volume chain.

Conflict ResolutionLink copied to clipboard

All of the above problems could be the result of one of the following:

The previous TMS expired tapes faster than Control-M/Tape.

The previous TMS allowed a job to proceed. However, the allowed job did not conform to Control-M/Tape rules.

A different retention was assigned to data sets by the two TMSs.

To resolve these problems:

1. Examine the relevant volume record in the Control-M/Tape Media Database, and in the parallel information in the other Tape Management System’s database. Examine previous messages in the system or job log to determine what problem may have caused this error.

2. Use the Online facility or the CTTMUP utility to make necessary correction in the Control-M/Tape Media Database.