Introduction

• Overview

  • How is this Book Organized?

  • What is Conversion?

  • When Should I Perform Conversion?

  • Reconversion of Tape Management Data

• Cross-Reference of Tape Management Terms

Overview

Conversion is the process by which information stored in your existing tape management system is translated into a format usable by
Control-M/Tape. The conversion process is normally performed several times during Control-M/Tape implementation.

Programs supplied with Control-M/Tape enable you to perform many of the necessary conversion steps automatically.

How is this Book Organized?

This book contains all the information that you need to convert your tape management information to Control-M/Tape format.

This chapter contains an introduction to various aspects of conversion to Control-M/Tape.

The conversion process can vary, depending on the tape management system that creates the data that is being converted. Chapters 2 through 6 of this book each describe conversion of data from a specific tape management system.

Conversion to Control-M/Tape is described for:

• CA-1

• CA-TLMS

• DFSMSrmm

• CA-EPIC/MVS

• Sites with no tape management system (MVS Catalog)

• ASG-ZARA

This chapter describes general issues relevant to all Control-M/Tape conversions. Read this chapter before proceeding with the conversion steps for your current tape management system.

Conversion from specific tape management systems is described in the remaining chapters of this guide.

What is Conversion?

The conversion process consists primarily of the following tasks:

• Convert Database – Convert the existing tape management system’s database to the Control-M/Tape Media Database. This process must be performed before testing begins, and is also necessary when changing the Control-M/Tape mode of operation, or if large discrepancies between the two databases have been detected.

• Convert and/or Adapt Definitions – Convert rules and definitions and policies (depending on the tape management system at your site) from the existing tape management system to Control-M/Tape definitions. Converted definitions can be revised in Control-M/Tape as necessary.

  The term "definitions" as used in this book refers to rule, vault and pool definitions.

Basic Conversion Steps

The following steps are normally performed as part of the conversion process:

1. Modify the parameters of the conversion programs.

2. Compile and link the conversion programs with the modified parameters.

3. Stop tape processing.

4. Format the Control-M/Tape Media Database.

   Formatting the Media Database overwrites all information previously stored in it.

5. Run the database analysis utilities of your existing tape management system to find and correct database errors and discrepancies (for example, broken chains, dead volumes). All errors must be corrected before conversion to Control-M/Tape. Errors that remain in the original database are propagated into the Control-M/Tape Media Database.

6. Produce reports from the existing tape management system. These reports are used as input for creation of the Media Database and rule, vault, and pool definitions for Control-M/Tape.

7. Run the conversion programs compiled in Step 2. These programs:

   • Convert information in the existing tape management system’s reports into data for the Control-M/Tape Media Database.

   • Load the data into the Control-M/Tape Media Database.

   • Create the Control-M/Tape Media Database index.

8. Create retention rules by converting the existing tape management system definitions and policies into Control-M/Tape rules.

9. Convert the existing tape management system vault patterns into Control-M/Tape rules.

10. Define Control-M/Tape rules that identify which datasets are controlled by an External Data Manager.

11. Adjust the Control-M/Tape rule list member so that it points to the new rules created in the above steps.

12. Define scratch pools to Control-M/Tape by using the Pool Definition screen (TP). If the existing tape management system uses scratch pools, those pools must be defined as Control-M/Tape scratch pools in this step.

13. Define vaults to Control-M/Tape by using the Vault Definition screen (TV).

14. Run Control-M/Tape vault management utility CTTVTM in a special conversion mode that adjusts the Media Database to the current vault status of your tapes.

15. Run Control-M/Tape retention management utility CTTRTM in a special conversion mode that adjusts the retention of tapes in the Media Database to match those of the existing tape management system.

16. Check the integrity of the Media Database. This step may reveal erroneous data converted from the existing tape management system. Erroneous data in the Media Database interferes with Control-M/Tape testing. The integrity of the Media Database must be assured before you start using
    Control-M/Tape.

17. Resume tape activity.

18. Run Control-M/Tape Stacking Statistics utility (CTTSTK). If you do not plan to activate Dynamic Dataset Stacking at this time, you may choose to delay execution of this utility until a later stage of the implementation process.

19. Adjust the Control-M/Tape New Day procedure (CTTDAY) to the requirements of your environment.

Automatic Conversion

Conversion of data from certain tape management systems is now performed by a series of online screens. During automatic conversion, you are prompted for information (for example, input dataset names) and given the option to perform or not to perform certain steps (for example, reformatting the Media Database). Many steps that were performed manually in previous versions are performed automatically by the conversion tool.

Automatic conversion is currently supported for CA-1 only.

When Should I Perform Conversion?

Conversion of tape management information is performed when implementing Control-M/Tape at a site that was previously managed by a different tape management system or when converting information from the MVS catalog.

The actual conversion process is performed at the following stages of Control-M/Tape implementation:

• At the very beginning of Control-M/Tape implementation.

• Before Control-M/Tape is activated in Global Phased mode.

• Before Control-M/Tape is activated in Global Production mode.

Reconversion of Tape Management Data

When Control-M/Tape is running in Global Test mode or Global Phased mode parallel to another tape management system, the databases of Control-M/Tape and the other tape management system must be synchronized. To ensure that the databases are synchronized, run Control-M/Tape’s New Day procedure whenever the retention and vaulting utilities of the existing tape management system are run.

If discrepancies are found, analyze them and correct Control-M/Tape definitions and/or parameters as necessary. If many discrepancies are detected it may be necessary to reconvert the data from the other tape management system.

A reconversion of tape management data is also recommended whenever the Control-M/Tape global operation mode is changed.

Control-M/Tape does not require any modifications to the existing tape management system at your site. Normally, definitions in the existing tape management system should not be changed during the changeover period to Control-M/Tape. However, if any definitions for the existing tape management system are changed, ensure that all modifications are also incorporated into the Control-M/Tape rule, vault, and pool definitions.

Cross-Reference of Tape Management Terms

For your convenience, the table below lists primary components of tape management systems that can be converted to Control-M/Tape, and the parallel features in Control-M/Tape.

Table 1 Cross-Reference of Tape Management Terms

Term	Control-M/Tape	CA-1	CA-TLMS	DF/SMSrmm	EPICMVS	ASG-ZARA
Database	MDB – Media Database	TMC – Tape Management Catalog	VMF – Volume Master File	Storage Management Library CDS	Dataset Name (DSN) Catalog	ASG-Zara Database
Dataset Record	Dataset Record (DDS)	DSNB (Dataset Name Block)	Dataset Name Record	D-record O-Record	Detail Record
Volume Record	Volume Record (DVL)	Volume Record	Volume Record	L-record E-record
Retention File	Rule Definitions – RULES Library (DO RETENTION)	RDS Retention Data Set	RMF Retention Master File	VRS	Master Record (EDD) EPICOPTS (OPTION SELECT)	Expiration Date Tables
Vault Pattern	Rule Definitions (DO VAULT)	VPD Vault Pattern Definitions	RMF	VRS	Master Record (EDD) EPICOPTS (OPTION SELECT)
Vault Definition	Member $$VAULT in the Control-M/Tape PARM library Updated through the Vault Definition screen (TV)	VPD	RMF	VRS	Vault Management System (VMS) Catalog	Off-site Management Rules
Storage Location (Vault)	Vault	Vault	Location	Storage Location	Vault
Vault (Location) Management Utility	CTTVTM	Vault Management – Batch Processing	TRS Tape Retention System	Storage Location Management (EDGHSKP)	Vault Movement Programs
Retention Management Utility	CTTRTM	Retention Management – Batch Processing	TRS – Tape Retention System	Retention Management (EDGHSKP)	SCRATCH Process Utility
Pool Management	N/A	N/A	N/A	Tape Pool Management	Tape Pool Management
Pool Type	N/A	N/A	N/A	Rack Pool	N/A
Pool Assignment	Rule Definitions (DO POOL)	SCRATCH assignment rules Member U01NSMxx in CA1.PARMLIB Or TMONSMxx	TRS		EPICOPTS (OPTION SELECT) EDD
Pool Definition	Member $$POOL in the Control-M/Tape PARM library Updated through the Pool Definition screen (TP)	Member U01SCRxx in TMUSCRxx in CA1.PARMLIB TMUSCRxx TMUSCRxx	Parameter TLMSIPD in member POOLID	Scratch Pool	EPICOPTS (TAPEPOOL)
Rules	Rules	Policies	Policies	Policies	N/A	Expiration Date Tables
Rule Location	Rule Definitions-RULES Library	RDS	RMF	Vital Record Specifications	EPICOPTS (OPTION SELECT)