Conversion from CA-TLMS

Overview of CA-TLMS ConversionLink copied to clipboard

This chapter describes the CA-TLMS to Control-M/Tape conversion process. A brief description of the differences between CA-TLMS and Control-M/Tape is followed by detailed conversion steps.

Conversion to Control-M/Tape is currently supported for CA-TLMS versions 5.3, 5.4, 5.5, 12.6, and 14.0. CA-TLMS is comprised of the following primary components:

Table 8 CA-TLMS Primary Components

Component

Description

Volume Master File (VMF)

Volume and dataset information for each volume in the tape library.

Retention Master File (RMF)

User-defined policies for storage (i.e., vaulting) and retention management.

Tape Retention System (TRS)

Performs retention and storage procedures according to information in the VMF and RMF.

Online Recorder

Accesses and maintains the VMF according to tape activity at the site.

CA-TLMS Scratch Pool management can be used to restrict certain datasets to specific tape volumes.

Control-M/Tape volume and dataset information is stored in the Control-M/Tape Media Database (MDB). When a dataset is created, Control-M/Tape records dataset attributes in the relevant dataset record in the Media Database and updates the appropriate volume record. Dataset access is tracked in both records. As Control-M/Tape rules are processed, changes to media management attributes (e.g., vault patterns and retention periods) are updated in the Media Database.

The following diagram indicates how the major CA-TLMS components are converted to Control-M/Tape format.

Figure 7 Conversion of CA-TLMS Components to Control-M/Tape

VMF CleanupLink copied to clipboard

The CA-TLMS Volume Master file (VMF) contains sequential, fixed length records that contain volume and dataset information.

To avoid propagating errors to the Media Database, ensure that the VMF is free of errors and data discrepancies (e.g., chaining problems or dead volume entries) before conversion. The following CA-TLMS utilities can be used to help clean up the VMF:

Table 9 CA-TLMS Utilities Used to Clean Up the CA-TLMS Volume Master File (VMF)

Utility

Description

TLMSVCVS

Verifies the VMF.

TLMSTRS, and TLMSTRAN

Updates tape movement, retention criteria, and scratch status in VMF records.

For more information about VMF cleanup, see CA-TLMS Conversion Process, and your CA-TLMS documentation.

Volume RangesLink copied to clipboard

Control-M/Tape requires definition of a range of volume serial numbers (volsers) for each media type before it generates volume records. Volumes in the VMF database that are not within the ranges specified to Control-M/Tape are not converted to the Control-M/Tape Media Database. Make an inventory of all active volume ranges in your data center. This inventory must be used as a reference when specifying volume ranges to Control-M/Tape during conversion.

Retention, Pool, and Vault DefinitionsLink copied to clipboard

The conversion tool creates Control-M/Tape rules according to the retention and vault management definitions described in the RMF.

Rules describing pool information are defined manually according to a CA-TLMS report. For more information, see Step 11: Define Scratch Pools and Related Rules.

All Control-M/Tape rules have the same format and use the same set of parameters to define actions and other criteria. After Control-M/Tape implementation has been completed and Control-M/Tape is running in production mode, rules created during conversion can be combined so that retention, vaulting, and pool specifications for a dataset are described in the same rules.

Retention ManagementLink copied to clipboard

The CA-TLMS Tape Retention System (TRS) uses the information stored in the VMF and RMF to control volume retention. Retention for a dataset may be defined in

  • a specific RMF entry

  • a keyword specified by JCL parameter EXPDT

  • the RMF Default record

If retention for a dataset is specified in more than one of these locations, CA-TLMS applies the retention definition with the highest priority, as demonstrated in the following table.

Table 10 CA-TLMS Retention Definition Priorities

Retention Definition Type

Priority

RMF entry

Highest priority

Retention specified in JCL (e.g., using parameter EXPDT)

Medium priority

Retention specified in the RMF Default record

Lowest priority

The conversion programs determine the appropriate retention for each dataset and automatically convert CA-TLMS retention policies to Control-M/Tape rule definitions. The name of each Control-M/Tape rule definition generated from CA-TLMS retention policies begins with a prefix specified during conversion.

Control-M/Tape retention rules are created from information in the RMF. Therefore, they do not reflect the Tape Default Retention (DEF Statements) specified in member TLMSIPO of the CAI.PPOPTION library. Tape Default Retention can affect Keep Data Control (Type 2) datasets.

To ensure compatibility with CA-TLMS during implementation of Control-M/Tape, you must define Control-M/Tape rules that specify the information contained in the DEF statements in use at your site.

Storage Location (Vault) ManagementLink copied to clipboard

CA-TLMS manages the movement of tape volumes between different storage locations according to commands specified in the RMF. Storage type and tape capacity are defined for each location.

The conversion tool automatically converts RMF location information to Control-M/Tape rule definitions.

Locations with more than one type of storage, such as CABINET, BOX, and UNDEFINED, are described by multiple records in the RMF. A different Location ID is assigned to each type of storage in each storage location.

During conversion, a Control-M/Tape Vault definition must be defined for each CA-TLMS location ID (storage location). All relevant cabinet IDs and their starting slot numbers must also be defined for these vaults.

Pool ManagementLink copied to clipboard

CA-TLMS Tape Pool management allows ranges of tape volumes in a tape library to be defined as a tape pool for a specific group of users or application. Scratch requests are restricted to a specific pool according to a specified DSN prefix, job name, EDM name and program name. On detection of a scratch mount request, CA-TLMS checks the mounted tape volume against the volume ranges that are valid for the dataset.

Control-M/Tape Pool definitions and relevant rule definitions are manually defined during conversion to ensure compatibility between Control-M/Tape and CA-TLMS pool management. For more information, see Step 11: Define Scratch Pools and Related Rules.

External Data ManagerLink copied to clipboard

Control-M/Tape can track tape volumes that are managed by an External Data Manager (EDM) such as DFSMShsm or CA-Disk. If CA-TLMS interfaces with an EDM at your site, appropriate Control-M/Tape rules must be defined to identify the relevant datasets as EDM-controlled.

For more information, see Step 9: Define and Edit Rules in Special Cases.

Tape Management UtilitiesLink copied to clipboard

Various utilities are used by CA-TLMS and Control-M/Tape to perform management functions for your tape library. CA-TLMS utilities and the equivalent utilities in Control-M/Tape are listed in Table 11.

Table 11 CA-TLMS Utilities and Equivalent Control-M/Tape Utilities

CA-TLMS

Description

Control-M/Tape

CTLMAIN

Initialization utility

CTTINIT

TLMSVCVS

Checks the integrity of the tape management database.

CTTIDB

TLMSTRS

TLMSTRAN

Retention and vault management.

CTTRTM

CTTVTM

TLMSRMUP

Updates retention and vaulting information in the tape management database.

Rule Definition facility

TLMSVMIN

Management of the tape database.

CTTDLD

IOADUL

IOADLD

CTTBIX

TLMSVMUT

Backup and restore of the tape management database.

Any backup utility

CA-EARL

Produces reports from the tape management database.

CTTRPT

For a detailed description of all Control-M/Tape utilities (including those mentioned above), see the Control-M/Tape chapter of the INCONTROL for z/OS Utilities Guide.

CA-TLMS Conversion ProcessLink copied to clipboard

The process of conversion from CA-TLMS to Control-M/Tape includes

  • executing CA-TLMS utilities

  • editing operations

  • running Control-M/Tape jobs

  • modifying vault and/or pool definitions through the Control-M/Tape Online facility

The steps required for CA-TLMS to Control-M/Tape conversion are described in detail in the remainder of this chapter. The conversion steps are accessed by the INCONTROL Installation and Customization Engine (ICE).

Use the following steps to begin conversion from CA-TLMS to Control-M/Tape.

  1. If you are converting from TLMS version 5.3, 5.4, or 5.5, rename the following items:

    • Conversion routines in the IOA SAMPEXIT library:

      Old Name

      New Name

      CTTCTR1

      CTTCTR16

      CTTCTR2

      CTTCTR26

      CTTCTR4

      CTTCTR46

      CTTCTR15

      CTTCTR1

      CTTCTR25

      CTTCTR2

      CTTCTR45

      CTTCTR4

    • Members in the IOA.INSTCTT library:

      Old Name

      New Name

      CONVTREP

      CONVTRE6

      CONVTRE5

      CONVTREP

  2. Enter ICE as described in the ICE chapter of the INCONTROL for z/OS Installation Guide.

  3. In the Major Step Selection screen, type CTT in the product field, select "INSTALL CTx" (ICE option3) from the IOA installation menu, and press Enter. The Control-M/Tape installation menu is displayed.

  4. Choose major step 14 "Conversion from CA-TLMS"

    Figure 8 ICE Screens for Converting CA-TLMS to Control-M/Tape

    CopyCopied to clipboard 
    ---------------------------- Minor Steps Selection ---------------------------
                                                                                 
     Environment: IOA610    Product: CTT                                         
     Major Step: 14  Conversion from CA-TLMS                                     
                                                                                 
     Sel values: S Select step     C Mark step as completed    R Reset status    
                 B Browse Step     X Mark step as excluded     ? Help            
     PF7/PF8  To scroll through all Steps                                        
     -----------------------------------------------------------------------------
     Sel  Step Status   Type    Opt Description                                  
     ===  ==== ======   ====    === ===========                                  
                                                                                 
      .     1  *        Edit     R  Set Conversion Parameters                    
      .     2           Job      R  Compile and Link Conversion Programs         
      .     3           Extrnl      Stop Tape Activity                           
      .     4           Job         Format Media Database                        
      .     5           Extrnl      Prepare CA-TLMS VMF for Conversion           
      .     6           Job         Create CA-TLMS Reports                       
      .     7           Job         Convert Reports into Media Database          
      .     8           Job         Convert the RMF into Rules                   
      .     9           Extrnl      Define EDM Rules and TLMSIPO Rules           
      .    10           Extrnl      Define Vaults                                
      .    11           Extrnl      Define Scratch Pools and Related Rules       
      .    12           Extrnl   R  Adjust Rule List                             
      .    13           Job         Apply Vault Rules                            
      .    14           Job         Apply Retention Rules                        
      .    15           Job         Verify Media Database Integrity              
      .    16           Extrnl      Resume Tape Activity                         
      .    17           Extrnl      Adjustments                                  
      .    18           Job      Y  Collect Statistics for Stacking              
     ------------------------------> End of Minor Steps <-------------------------

ICE screens can be used to check and record your progress during conversion, and to run some of the jobs performed during certain conversion steps.

If you are not yet familiar with ICE, BMC recommends that you review Installation and Customization Engine chapter of the INCONTROL for z/OS Installation Guide.

Procedure TableLink copied to clipboard

The conversion process consists of the following operations and programs.

Table 12 Steps in the CA-TLMS Conversion Process

Step

Operation

Job/Screen/ External Event

Relevant Program

1

Set Conversion Parameters

Edit

N/A

2

Compile and Link Conversion Programs

CONVTASM

N/A

3

Stop Tape Activity

External Event

N/A

4

Format Media Database

CONVFMDB

IOADBF

5

Prepare CA-TLMS VMF for Conversion

 

CATVCVS (TLMSVCVS)

6

Generate Volume and Dataset Data From the VMF, And Retention, Location and Selection Data From RMF

CONVTREP

CATRPTS

7

 

 

Extract data from VMF Reports to the VWR File

CONVTMDB

CTTCTR1

Load MDBD Data Records From the VWR File

Same as above

CTTDLD5

Build MDBI Index Records

Same as above

CTTBIX

8

Convert RMF into Rules

CONVTRMF

CTTCTR2

9

Define External Data Manager (EDM) rules

Rule Definition screen (TR)

N/A

10

Define vaults

Vault Definition screen (TV)

N/A

11

Define Scratch Pools and Related Rules

Pool Definition screen and Rule Definition screen (TP and TR)

N/A

12

Adjust Rule List

Edit

N/A

13

Apply Vault Rules

CONVVTM

CTTVTM

14

Apply Retention Rules

CONVTRTM

CTTRTM

15

Verify Media Database Integrity

CONVIDB

CTTIDB

16

Resume Tape Activity

External Event

N/A

17

Final Adjustments

External Event

N/A

18

Collect Statistics for Stacking

CONVSTK

CTTSTK

Step 1: Set Conversion ParametersLink copied to clipboard

Before running the conversion jobs, several conversion parameters must be modified to match your site standards. The conversion parameters are listed in member CTTTLMDF in the IOA MAC library. These parameters specify default values in the rules created during the conversion. Change the default values of these parameters only if it is necessary for compatibility with your site’s rule naming conventions:

Table 13 Conversion Parameters in Member CTTTLMDF

Parameter

Description

TLMSVER

The version of CA-TLMS installed at your site.

Valid values are 5.3, 5.4, 5.5, 12.6, and 14.0.

Default: 5.3

If you are converting from TLMS version 5.3, 5.4, or 5.5 , ensure that modules were renamed as instructed in CA-TLMS Conversion Process.

RLDRMFN

The prefix for Control-M/Tape retention rules generated from the Retention Master file (RMF). The name of each Control-M/Tape retention rule is comprised of this prefix and a sequential number. Up to three characters can be specified for this field.

Default: RMF

RLDGROP

The group name for Control-M/Tape rules created by the conversion tool. A Group name is a descriptive name for a group of rules. Up to twenty characters can be specified for this field.

Default: TLMS-RULES

RLDGUID

The user ID (OWNER) for Control-M/Tape rules generated during conversion. The OWNER field is mandatory for all rules and can be useful during implementation of Control-M/Tape security. Up to eight characters can be specified for this field.

Default: CTTCONV

RLDPRTY

The rule sequence priority for rules created by the conversion tool. The order in which the rules are scanned is very important for rule processing. Sequence priority controls the order in which rules are scanned. When Control-M/Tape searches for a rule, the first rule that matches the selection criteria is activated. Priority is determined in ascending order where blank < A < Z < 0 < 9. For details about order of rule processing, see the organization and administration chapter of the Control-M/Tape User Guide. This field contains two characters.

Default: 00 (medium priority)

RLDCNSR

The value for the Control-M/Tape CONTINUE SEARCH field. This field determines whether or not Control-M/Tape searches for additional rules that match a dataset currently being processed. Specify N (No) for this parameter to ensure compatibility with CA-TLMS. Valid values are:

  • Y – Continue search.

  • N – Do not continue search. Default.

RLDPRFX

Indicates whether or not dataset names specified for datasets with CYCLE type retention must be used as prefixes that identify different generations (cycles) of the dataset. This parameter indicates the value for subparameter PREFIX in DO RETENTION statements of Control-M/Tape rules created by the conversion. The expression RLDPRFX=N is compatible with the cycle retention that is performed in the CA-TLMS working mode. For more information, see DO RETENTION in the rule parameters chapter of the Control-M/Tape User Guide. Valid values are:

  • Y – Consider datasets with the same prefix as different generations of the same dataset.

  • N – Ignore specified prefixes, and identify each dataset by its full name. Default. Compatible with CA-TLMS working mode.

RLDMODE

Rule specific operation mode for rules created during conversion. When a rule is executed in TEST mode, information is recorded in the Media Database, but Control-M/Tape does not perform any actions.

If TEST is specified for Control-M/Tape installation parameter MODE, all rules are run in test mode (that is, Global Test mode overrides any rule-specific production mode). It is recommended that you not modify the default value for this parameter. Valid values are:

  • P – Production mode. Default.

  • T – Test mode.

RLDDESC

A free-text rule description to be inserted in the DESCRIPTION field of each rule created by the conversion tool. This field can contain a maximum of 61 characters.

Default: CONVERTED FROM CA-TLMS RMF.

DCCODES

Data Center location IDs. Specifies location IDs that refer to the data center (i.e., the main library). If necessary, two location IDs (separated by commas) can be specified for this parameter (e.g., DC,LB). Default: DC.

The locations IDs specified in parameter DCCODES are converted to location MAINLIB in Control-M/Tape.

Location IDs that refer to other storage locations must not be specified in parameter DCCODES.

DATEFRM

Date format used in CA-TLMS reports produced in Step 6. Valid values are:

  • A – mm/dd/yy

  • J – yy/mm/dd

  • W – dd/mm/yy. Default.

CABINET

Whether or not to use CA-TLMS cabinet and slot numbers (CCSS values). Valid values are:

  • Y – The conversion program translates cabinet and slot numbers (CCSS values) to slot numbers in Control-M/Tape.

  • N – Cabinet and slot numbers are ignored. A slot number of 0 is assigned to all volumes. Default.

If Y is specified for this parameter, you have to define the appropriate cabinets in conversion program CTTCTR1 (described in Step 2 below).

MAINVLT

How the conversion program handles volumes that are being placed in MAINLIB. Valid values are:

  • Y – The volumes are marked as "vaulted".

  • N – The volumes are marked as "not vaulted". Default.

BMC recommends that you use this default setting.

Step 2: Compile and Link Conversion ProgramsLink copied to clipboard

The CONVTASM job compiles and links all conversion programs.

Defining Cabinets to Control-M/TapeLink copied to clipboard

The CTTCTR1 conversion program, which is compiled by the CONVTASM job, builds the database work file from CA-TLMS reports 4 and 10. If you specified Y for the CABINET parameter in Step 1, you must define the appropriate cabinets in this program before running the CONVTASM job.

  1. Edit the CTTCTR1 member in the IOA SAMPEXIT library.

  2. Look for the CABINET symbol to locate the CABINET table. This is the table that is used to convert the CA-TLMS cabinets to Control-M/Tape slot numbers (see Figure9).

    Figure 9 CABINET table format in CTTCTR1 member

    CopyCopied to clipboard 
    CABINET  EQU
    *LOC_ID   DC  C'LO'                 <=== CHANGE
    CAB_ID   DC  C'ID'                  <=== CHANGE
    CABSTART DC  FL4'1000'              <=== CHANGE
    CABENTRY EQU *-CABINET
             DC  C'V1',C'AA',FL4'1100'  <=== CHANGE
             DC  C'V1',C'AB',FL4'1200'  <=== CHANGE
             DC  C'V2',C'AA',FL4'1300'  <=== CHANGE
             DC  C'V2',C'AB',FL4'1400'  <=== CHANGE
             DC  C'V3',C'AA',FL4'1500'  <=== CHANGE
             DC  C'V3',C'AC',FL4'1600'  <=== CHANGE
    CABEND   DC  C'00',C'00',FL4'0'     END OF LIST

    The CABINET table contains the following columns:

    • First field – 2-character vault identifier. This vault identifier is common to CA-TLMS and Control-M/Tape.

    • Second field – 2-character CA-TLMS cabinet identifier.

    • Third field – Control-M/Tape starting slot number of a range of slot numbers for a given cabinet.

  3. Specify a Control-M/Tape starting slot number for each CA-TLMS cabinet identifier within each vault. The range of slot numbers must be unique in each vault.

    Example

    • An installation with 800 volumes is contained within 4 vaults: V1, V2, V3, V4.

    • Each vault has 2 cabinet identifiers: AA and AB.

    • Each CA-TLMS cabinet identifier has 100 slots (0-99).

    The following table shows one way to specify the Control-M/Tape starting slot numbers for each cabinet, with the resulting slot range:

    Table 14 Example specification of Control-M/Tape starting slot number

    Vault

    CA-TLMS cabinet and slot number

    Control-M/Tape starting slot number

    Resulting Control-M/Tape slot range

    V1

     

    AA (0-99)

    1100

    1100-1199

    AB (0-99)

    1200

    1200-1299

    V2

     

    AA (0-99)

    1300

    1300-1399

    AB (0-99)

    1400

    1400-1499

    V3

    AA (0-99)

    1500

    1500-1599

    AB (0-99)

    1600

    1600-1699

    V4

    AA (0-99)

    1700

    1700-1799

    AB (0-99)

    1800

    1800-1899

    The following figure shows how to edit the CABINET table to produce this result:

    Figure 10 Example format to convert CA-TLMS cabinet to Control-M/Tape cabinet

    CopyCopied to clipboard 
    CABINET  EQU *LOC_ID   DC  C'V1'                  VAULT V1
    CAB_ID   DC  C'AA'                  CABINET AA
    CABSTART DC  FL4'1100'              STARTING SLOT NUMBER 1100
    CABENTRY EQU *-CABINET
             DC  C'V1',C'AB',FL4'1200'  V1 AB STARTING SLOT NUMBER 1200
             DC  C'V2',C'AA',FL4'1300'  V2 AA STARTING SLOT NUMBER 1300
             DC  C'V2',C'AB',FL4'1400'  V2 AB STARTING SLOT NUMBER 1400
             DC  C'V3',C'AA',FL4'1500'  V3 AA STARTING SLOT NUMBER 1500
             DC  C'V3',C'AB',FL4'1600'  V3 AB STARTING SLOT NUMBER 1600
             DC  C'V4',C'AA',FL4'1700'  V4 AA STARTING SLOT NUMBER 1700
             DC  C'V4',C'AB',FL4'1800'  V4 AB STARTING SLOT NUMBER 1800
    CABEND   DC  C'00',C'00',FL4'0'     END OF LIST

    In this example CABINET table

    • CA-TLMS vault V2, cabinet AA, slot 34 is referred by Control-M/Tape as slot number 1334.

    • CA-TLMS vault V3, cabinet AB, slot 66 is referred by Control-M/Tape as slot number 1666.

  4. After you have edited the CTTCRT1 member, submit job CONVTASM. All job steps must end with a condition code of0.

Step 3: Stop Tape ActivityLink copied to clipboard

Stop all tape activity. If Control-M/Tape is active, bring it down with the following command:

CopyCopied to clipboard 
S CTTINIT,PARM=‘MODE=TERM’

BMC recommends that you also bring down CA-TLMS at this time.

If CA-TLMS is not brought down at this time, information about datasets processed after production of the CA-TLMS reports (in Step 6) are not incorporated into the Control-M/Tape Media Database that is produced by the conversion tool.

Step 4: Format Media DatabaseLink copied to clipboard

Run the CONVFMDB job to format the Control-M/Tape Media Database. If the Media Database already exists, for example, due to previous conversions, reformat it to remove all old data.

All job steps must end with a condition code of 0.

Step 5: Prepare CA-TLMS Volume Master File (VMF) for ConversionLink copied to clipboard

Control-M/Tape builds the Media Database from the volume and dataset information in the VMF. Before executing the conversion process, the VMF must be free from errors and data discrepancies (for example, chaining problems and dead volume entries). It is also necessary to ensure that all VMF records contain the most current retention and location information before conversion.

Errors that remain in the VMF are carried over to the Control-M/Tape Media Database during conversion.

Use the following CA-TLMS utilities to check the integrity of the CA-TLMS VMF and if necessary correct errors.

Table 15 CA-TLMS Utilities Used to Check the Integrity of the CA-TLMS VMF

Utility

Description

TLMSVCVS

Detects invalid internal multivolume and multidataset chains, or errors that exist in the free chain of unused AUX records. Invalid or broken chains may be due to invalid updates, abnormal terminations, system crashes, or incomplete restoration during disaster recovery procedures.

You must correct all errors that are detected by this utility.

TLMSRMUP

Manually updates the RMF. If you need to add or change location or retention criteria in the RMF before the conversion process, run this utility before executing procedure CATTRS (described below).

This utility produces CA-TLMS Report 40.

CATTRS

Runs the CA-TLMS Tape Retention System. The following utilities are executed by this procedure.

TLMSTRS

Reads the VMF and RMF, generates a transaction file for processing by utility TLMSTRAN (below), and produces CA-TLMS reports 41 and 44.

TLMSTRAN

Applies transactions to the VMF according to the file produced by utility TLMSTRS. The CA-TLMS Online Recorder must be active while utility TLMSTRAN is running.

Step 6: Create CA-TLMS ReportsLink copied to clipboard

Before running this job, run the daily retention and vaulting processing for CA-1. This is necessary to convert to PHASED or PROD modes. This is also recommended when you convert to TEST mode.

Users of TLMS version 5.4 who have set the default data format in reports to a non-standard format (for example, 12-Jan-2000) must insert the following statement as the first statement in the SYSIN file that is used in job CONVTREP:

SDT date

where date is mm/dd/yyyy, dd/mm/yyyy or yyyy/mm/dd based on the date format specified for parameter DATEFRM in Step 1 of the conversion process.

All job steps must end with a condition code of 0.

This job is used to generate CA-TLMS reports from the VMF and the RMF. These reports are used in a later step to create Control-M/Tape rule definitions, and to build the Control-M/Tape Media Database.

This job uses the CATRPTS CA-TLMS procedure to produce the following reports:

Table 16 CA-TLMS Reports Created by Job CONVTREP

Report

Description

TLMS004

Active Data Set Report. Lists all datasets in the VMF that are not in scratch status.

TLMS010

Volume Master Report. Lists all volumes (according to volume serial number) in the VMF regardless of their status.

TLMS015

Tape Retention Location Report. Lists all locations (local and remote) defined in the RMF.

TLMS016

Tape Retention Selection Report. Lists all retention commands in the RMF. Retention type, location ID, and count value are listed for each dataset or dataset group.

Step 7: Convert Reports into Media DatabaseLink copied to clipboard

This step performs job CONVTMDB that converts reports created by job CONVTREP (in Step 6) into volume and dataset records in the Control-M/Tape Media Database. The names of reports 4 and 10 that were created by job CONVTREP are passed to job CONVTMDB.

The following programs are executed by job CONVTMDB.

Table 17 Programs Executed by Job CONVTMDB

Program

Description

CTTCTR1

Extracts data from reports generated by job CONVTREP (Step 6), to a general work file called the VWR file. The VWR file contains all the volume and dataset information necessary for building the volume and dataset records in the
Control-M/Tape Media Database. This program must end with condition code 0. If it ends with a condition code other than 0, resolve the errors indicated by the messages, and rerun job CONVTMDB.

CTTDLD5

Runs utility CTTDLD in CONVERT mode to load the volume and dataset records from the VWR file into the data component of the Media Database. This program must end with a condition code of 0.

CTTBIX

Runs utility CTTBIX in CONVERT mode to build the index records for the Control-M/Tape Media Database. This program must end with a condition code of 0. Condition code 8 indicates that errors were detected but the utility continued and the Media Database Index file was built successfully. The inconsistencies indicated by issued messages must be investigated and manually corrected.

Before submitting this job, edit it as described below.

Two parameters (REP04 and REP10) are passed to procedure CONVTMDB. Change these parameters in the //EXEC statement following the //PEND statement so that they specify the names of the reports created by job CONVTREP in Step 6.

Specify the ranges of volumes used at your site in the LOAD.SYSIN DD statement. Volumes in the CA-TLMS VMF that are not within the ranges specified to Control-M/Tape are not added to the Media Database. Specify the following parameters for each RANGE statement:

Table 18 Parameters for Ranges of Volumes

Parameter

Description

FIRST

First volume serial number in the range.

LAST

Last volume serial number in the range.

MEDIA

Volume media type.

VENDOR

Vendor of the media (Optional).

Submit Job CONVTMDBLink copied to clipboard

If any of the steps of this job end abnormally, it is necessary to reformat the Control-M/Tape Media Database before rerunning job CONVTMDB. For details on how to format the Media Database, see Step 4: Format Media Database.

For more information about utilities CTTDLD and CTTBIX, see the Control-M/Tape chapter of the INCONTROL for z/OS Utilities Guide.

Step 8: Convert the Retention Master File (RMF) Into RulesLink copied to clipboard

This step consists of running job CONVTRMF. This jobcreates Control-M/Tape rule definitions from retention and location data in report TLMS016, generated in Step 6.

Verify that the relevant CA-TLMS files have been cleaned up and that all integrity errors in CA-TLMS tape library information have been resolved. For more information about ensuring CA-TLMS information integrity, seeStep 5: Prepare CA-TLMS Volume Master File, and your CA-TLMS documentation.

Before running this job, specify the following parameters in the CONV step of this job:

Table 19 Parameters for Job CONVTRMF

Parameter

Description

REP

Name of the report file (generated using job CONVTREP) containing report TLMS016.

RULEMEM

Rule member name to be created in the Control-M/Tape Rule Definition library. This library is allocated during Control-M/Tape installation. For the full name of the library, refer to your installation procedures.

Run job CONVTRMFLink copied to clipboard

All steps of this job must end with a condition code of 0. Do not change the rule definitions created by this job until after you run job CONVVTM in Step 13: Apply Vault Rules and job CONVTRTM in Step 14: Apply Retention Rules. This ensures compatibility between information in the Control-M/Tape Media Database and the CA-TLMS VMF and RMF.

Step 9: Define and Edit Rules in Special CasesLink copied to clipboard

This step consists of manual definition of rules to support certain functions that are not handled automatically by the conversion job.

EDM RulesLink copied to clipboard

If an External Data Manager, such as DFSMShsm, or CA-Disk, is defined in your CA-TLMS system, rules must be defined in Control-M/Tape to identify its datasets as EDM-controlled before continuing with the conversion process.

Use the following steps to convert EDM information at your site:

  1. Analyze the EDM information in CA-TLMS.

    • For CA-TLMS version 5.3, check CA-TLMS user Exit TLMSXUPD in the CAISRC library to determine what EDM support has been implemented, and check member TLMSIPO or Exit TLMSXUP for existing EDM definitions.

    • For CA-TLMS version 5.4 or later, check parameter EDM in member TLMSIPO in your CA-TLMS PARM library.

  2. Identify EDM datasets to Control-M/Tape. In the Control-M/Tape Rule Definition screen (Screen TR), create a rule with a DO RETENTION=EDM statement for each EDM dataset or group.

Other rules may have been created in earlier conversion steps for certain EDM-controlled datasets (that is, specifying the DO RETENTION=PERMANENT statement) if other retention definitions for these datasets were included in the CA-TLMS RMF.

Default RuleLink copied to clipboard

If necessary, define Control-M/Tape rule that implement Tape Default Retention policies (DEF statements) specified in the CA-TLMS System Options (TLMSIPO) member. This ensures compatibility between Control-M/Tape and CA-TLMS operations. For example, define rule to handle datasets that are managed in CA-TLMS with Keep Date retention type (Type 2).

The conversion process converts the TLMS RMF Default record into a Control-M/Tape rule named $DEFAULT. This enables Control-M/Tape to use the same default retention period that was used by TLMS. If there is no $DEFAULT rule, Control-M/Tape uses the retention period set in the DEFEXPDT parameter in the CTTPARM member that was created when Control-M/Tape was installed. Compare the retention period specified in the $DEFAULT rule with that in the DEFEXPDT parameter, and consider whether to delete the $DEFAULT rule and allow the setting in the DEFEXPDT parameter to take effect.

For more information on the DEFEXPDT parameter, see the Control-M/Tape installation parameters section in the INCONTROL for z/OS Installation Guide.

The Retention Period in JCLLink copied to clipboard

You can set the retention period of the dataset in the DD statement of each job by means of the EXPDT parameter.

If the OVERJCL parameter is set to YES, the retention period in a Control-M/Tape rule statement overrides the retention period set by the JCL EXPDT parameter. If the OVERJCL parameter is set to NO, the retention period set in the rule is ignored, and the JCL EXPDT retention period takes effect.

Control-M/Tape does not automatically go through the process of comparing the expiration date setting in an individual rule with the expiration date in the JCL EXPDT parameter and using the later of the two dates to define the retention period.

Regardless of whether the expiration date in the rule setting or that in the JCL EXPDT produces the longer retention period, if you want Control-M/Tape to ensure that the dataset will be retained for the longer of the two retention periods, you must edit the rule accordingly, as shown in the following example:

  • The existing rule sets the expiration period to 10 days, by the DORETENTION = DAYS 10 statement.

  • The period set in the JCL EXPDT parameter is 20 days.

  • To ensure that the expiration period is the longer period, in this case the full 20 days defined by the JCL parameter, edit the definition in the rule as follows:
    DORETENTION=DAYS 10 AND JCL EXPDT.

For more information about retention periods, see the organization and administration chapter in the Control-M/Tape User Guide.

For more information about the OVERJCL parameter, see the organization and administration chapter in the Control-M/Tape User Guide and the Control-M/Tape chapter in the INCONTROL for z/OS Installation Guide.

Step 10: Define VaultsLink copied to clipboard

Before the converted vault (location) rules created in job CONVTRMF can be applied to the Media Database during Vault Management, the vaults must be defined to Control-M/Tape. All CA-TLMS locations defined in the RMF are listed in report TLMS015, generated in Step 6.

Define vaults to Control-M/Tape by using the Vault Definition screen (TV). Select the member that was allocated during installation for vault definitions. The default member is $$VAULT in the Control-M/Tape PARM library. Define all the vaults the same way that they are defined in CA-TLMS.

Be sure to define sufficient capacity to accommodate the maximum number of volumes that can reside simultaneously in each vault. This capacity must be defined for each media type that is to be kept in this vault.

Step 11: Define Scratch Pools and Related RulesLink copied to clipboard

If scratch pools are defined in your CA-TLMS system, rules must be created in Control-M/Tape to identify them and the datasets that are assigned to those pools.

Use the following steps to convert scratch pool information at your site:

  1. Analyze the pool information that has been defined for CA-TLMS.

    • For CA-TLMS version 5.3, check the pool information tables in members TLMSRTAB and TLMSVTAB in the CAISRC library.

    • For CA-TLMS version 5.4 or later, use system option POOLID in member TLMSIPO of the CAI.PPOPTION library to dynamically build user table TLMSPTAB. This table contains the definitions of the tape pools managed by CA-TLMS.

  2. Define Control-M/Tape pools that are identical to those defined in CA-TLMS, by the Pool Definition screen (screen TP). Select the member that was allocated for pool definitions during Control-M/Tape installation (Default: member $$POOL in the Control-M/Tape PARM library).

  3. Define Control-M/Tape rules that identify the datasets to be restricted to each pool. Use the DOPOOL statement in these rules to specify dataset names, groups, job names, or program names that must be used to determine the datasets for each pool.

During this step, you may create pool assignment rules that reference datasets for which other rule definitions were already created (by previous conversion steps). The recommended default value for parameter CONTINUE SEARCH in Control-M/Tape rule definitions created during conversion is N. Therefore, only one rule would normally be triggered for each dataset being processed.

To ensure that each pool assignment rule is triggered for all relevant datasets, specify a higher priority than the default in RLDPRTY (in Step 1) and specify Y in the CONTINUE SEARCH field for these rules.

Step 12: Adjust Rule ListLink copied to clipboard

After the Control-M/Tape rule definition tables have been created in job CONVTRMF and Step 11, they must be specified to Control-M/Tape by member RULLIST in the Control-M/Tape PARM library. This member contains the list of tables to be loaded into memory when Control-M/Tape is activated. In member RULLIST, enter a new line for each Rule Definition table (e.g., VMFRULE, POOLRULE) created. Copy the format of the rule tables already listed in this member.

Verify that the Vault Definition table and Pool Definition table (members $$VAULT and $$POOL in the Control-M/Tape PARM library) are specified in DD statements DAVLTS and DAPOOLS, respectively, in procedure CTTINIT.

Step 13: Apply Vault RulesLink copied to clipboard

This step consists of job CONVVTM that applies the Vault Rule definitions created in Step 8. Job CONVVTM runs utility CTTVTM with the MODE=CONVERT expression included in the TYPEVLT statement. During this run of utility CTTVTM:

  • rule definitions are loaded

  • vault patterns for each volume are recalculated

  • slot and box records are built

For more information about utility CTTVTM, see the Control-M/Tape chapter of the INCONTROL for z/OS Utilities Guide.

Check the results of job CONVVTM. The distribution report generated by utility CTTVTM lists all volumes that need to be moved as a result of this run of the utility. This report should be empty, indicating that no volumes need to be moved. If it is not empty, check the vaulting rules for the volumes listed in the report.

The report may indicate volume movement within a vault (for example, a volume moving from one slot in a specific vault to another slot in the same vault). This situation is normal and may only reflect differences in slot management between CA-TLMS and Control-M/Tape.

Step 14: Apply Retention RulesLink copied to clipboard

This step consists of job CONVTRTM that runs utility CTTRTM with the MODE=CONVERT expression included in the TYPERET statement. In this mode, no retention action is performed. This mode is used to update retention information in the Media Database. For more information about utility CTTRTM, see the Control-M/Tape chapter of the INCONTROL for z/OS Utilities Guide.

Submit the job and check the results of the run. The job must end with a condition code of 0.

No expiration should be performed during this run of utility CTTRTM. If the Scratch report produced by the utility lists volumes that were expired as a result of the run, determine why this occurred, and correct any detected errors.

Step 15: Verify Media Database IntegrityLink copied to clipboard

This step consists of job CONVIDB that runs utility CTTIDB after the conversion to verify the integrity of the Media Database. For more information about utility CTTIDB, see the Control-M/Tape chapter of the INCONTROL for z/OS Utilities Guide. CTTIDB issues messages if database inconsistencies are detected. Examples of such inconsistencies are:

  • Errors in chain links that connect volumes in a multi-volume chain

  • Active volumes that do not contain datasets

  • Scratch volumes that contain active datasets

  • Discrepancies between Media Database records

If utility CTTIDB reports errors, it might indicate problems that were overlooked or missed while cleaning up the CA-TLMS VMF. If this is the case, correct the original data and repeat the conversion process from Step 4 (Format Media Database). You can also correct problems directly in the Control-M/Tape Media Database. For more information about utility CTTIDB, see verifying media database integrity chapter of the Control-M/Tape Implementation Guide, and the Control-M/Tape chapter of the INCONTROL for z/OS Utilities Guide.

Utility CTTIDB also generates Media Database statistics that can be used for comparison with the CA-TLMS VMF. The statistics provided include:

  • Number of used data records

  • Number of used index records

  • Number of free data records

  • Number of free index records

  • Total number of records according to type, that is, volume, dataset, or scratch)

For information about the structure of the Media Database, such as data records and index records, see the Control-M/Tape chapter of the INCONTROL for z/OS Administrator Guide.

Step 16: Resume Tape ActivityLink copied to clipboard

Tape activity can now be resumed.

Start Control-M/Tape with the following command:

CopyCopied to clipboard 
S CTTINIT,PARM=‘MODE=INIT’

If CA-TLMS was stopped, it must also be started at this time.

Step 17: Final AdjustmentsLink copied to clipboard

The Control-M/Tape New Day procedure (CTTDAY) performs daily maintenance on the Control-M/Tape Media Database and related files. To ensure compatibility with CA-TLMS, replace member CTTDAY in the JCL library with member CTTDAYT. Job CTTDAYT performs vault processing (CTTVTM) before retention processing (CTTRTM).

CA-TLMS allows specification of JCL parameter SPACE=(1,(1,1)), in place of EXPDT=98000, to bypass tape management. If your are using this parameter, implement sample Exit CTTX003J (located in the IOA SAMPEXIT library) to support JCL parameter SPACE=(1,(1,1)) and to ensure compatibility between Control-M/Tape and CA-TLMS tape management.

Step 18: Collect Statistics for StackingLink copied to clipboard

This step consists of job CONVSTK that runs utility CTTSTK to collect dataset statistics from the Control-M/Tape Media Database. This statistical information is used by the Control-M/Tape Dynamic Dataset Stacking facility. This job must run with MODE set to MDB.

This step is relevant only if you are converting from CA-TLMS version 5.3. Statistical information is not available for dataset records converted from CA-TLMS version 5.4 or later.

Submit job CONVSTK. Check the results. All steps must end with a condition code of 0. Depending on the size of your Media Database, this utility may run for a long time.

For more information about collection of dataset statistics, see utility CTTSTK in the INCONTROL for z/OS Utilities Guide.

For more information about dataset stacking, see the dataset stacking chapter of the Control-M/Tape Implementation Guide.