Conversion from ASG-Zara

• Overview of ASG-Zara Conversion

  • Reconversion

• ASG-Zara Conversion Process

  • Step 1: Compile and Link the Conversion Program

  • Step 2: Stop Tape Activity

  • Step 3: Format Media Database

  • Step 4: Prepare ASG-Zara Database Conversion

  • Step 5: Produce an ASG-Zara Inventory report

  • Step 6: Convert ASG-Zara Inventory Report into Media Database

  • Step 7: Define Vaults

  • Step 8: Define Scratch Pools and Corresponding Rules

  • Step 9: Define External Data Manager Rules

  • Step 10: Create Control-M/Tape Rules

  • Step 11: Adjust Rule List

  • Step 12: Verify Media Database Integrity

  • Step 13: Resume Tape Activity

Overview of ASG-Zara Conversion

This chapter provides a detailed description of the steps that you perform to convert ASG-Zara to Control-M/Tape.

Reconversion

Conversion is normally performed several times during implementation of Control-M/Tape at a new site. If the current conversion is not the first conversion at your site, some of the conversion steps described in this chapter can be skipped.

ASG-Zara Conversion Process

The process of conversion from ASG-Zara to Control-M/Tape includes:

• Executing ASG-Zara utilities

• Defining vault, pool, and rule definitions in Control-M/Tape

• Running Control-M/Tape jobs

The steps required for ASG-Zara 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 ASG-Zara to Control-M/Tape.

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

2. In the Major Step Selection screen, type CTT in the product field, select "INSTALL CTx" (ICE option 3) from the IOA installation menu, and press Enter.

   The Control-M/Tape installation menu is displayed.

3. Choose major step 18, Conversion from ASG-Zara.

Step 1: Compile and Link the Conversion Program

This step consists of running job CONZEASM, which compiles and links the CTTCZAR conversion program.

The CTTCZAR program converts records in the ASG-Zara report (produced in Step 5) to Control-M/Tape Media Database records.

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

Step 2: Stop Tape Activity

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

S CTTINIT,PARM=‘MODE=TERM’

BMC Software recommends that you also bring down ASG-Zara at this time.

Step 3: Format Media Database

Run the CONVFMDB job to format the Control-M/Tape Media Database and prepare it for conversion.

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

Step 4: Prepare ASG-Zara Database Conversion

Control-M/Tape builds the Media Database from the ASG-Zara report to reflect the actual state of the ASG-Zara Database. Before conversion, the ASG-Zara Database must be free of errors and data discrepancies such as chaining problems and dead volume entries.

If errors remain in the ASG-Zara Database, they are carried over to the Control-M/Tape Media Database during conversion.

Use the Zara Database Verify System to detect and verify the integrity of the ASG-Zara Database.

Step 5: Produce an ASG-Zara Inventory report

This step consists of running the CONVZREP job, which extracts information from the ASG-Zara Database, so that other conversion steps can use the extracted information.

Run the CONVZREP job to generate a sequential file that the CONVZMDB job uses (in Step 6) to create Control-M/Tape Media Database records.

All steps must end with a condition code of 0.

Step 6: Convert ASG-Zara Inventory Report into Media Database

This step performs job CONVZMDB, which converts the ASG-Zara report created by job CONVZREP (in Step 5) into volume and dataset records in the Control-M/Tape Media Database.

CONVZMDB job includes 3 steps:

• Step CREVWR executes the CTTCZAR program, which extracts data from the ASG-Zara report 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 CONVZMDB.

• Step LOAD 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.

• Step BLDIDX 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.

Step 7: Define Vaults

Verify that the Vault Definition Table member is specified in DD statement DAVLTS in procedure CTTINIT.

This member is defined to CTTINIT during Control-M/Tape installation.

The default name for the Vault Definition Table member is $$VAULT, and it is stored in the Control-M/Tape PARM library.

To define vaults to Control-M/Tape to match the vaults that are defined to ASG-Zara

1. Enter the Control-M/Tape Vault Definition screen (TV).

2. Select the member that was allocated for vault definitions during Control-M/Tape installation.

   The default name is $$VAULT, stored in the Control-M/Tape PARM library.

3. Define all the vaults the same way that they are defined to ASG-Zara.

   If capacity is not specified for a vault, Control-M/Tape Slot Management will not be active for that vault.

Step 8: Define Scratch Pools and Corresponding Rules

If scratch pools are defined in your ASG-Zara system, define Control-M/Tape pools that are identical to those defined in ASG-Zara, through the Pool Definition screen (screen TP).

1. Select the member that was allocated for pool definitions during Control-M/Tape installation.

   The default member name is $$POOL, in the Control-M/Tape PARM library.

2. Verify that the Pool Definition Table member (by default, the $$ POOL member in the Control-M/Tape PARM library) is specified in DD statement DAPOOLS in procedure CTTINIT.

3. Create rules in Control-M/Tape to identify scratch pools and the datasets that are assigned to those pools.

   Use the DO POOL 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.

   To ensure that each pool assignment rule is triggered for all relevant datasets, specify Y in the CONTINUE SEARCH field for these rules.

Step 9: Define External Data Manager Rules

If an External Data Manager, such as DFSMShsm or CA-Disk, is defined in your ASG-Zara system, rules must be created in Control-M/Tape to identify as EDM-controlled datasets.

Use the Control-M/Tape Rule Definition screen (Screen TR) to identify EDM-controlled datasets.

For each EDM dataset or group of datasets:

• Enter the relevant job name and dataset name as selection criteria.

• Enter the DO RETENTION=EDM statement.

• Set CONTINUE SEARCH to Y to ensure that retention definitions in other relevant rules are applied.

Step 10: Create Control-M/Tape Rules

Use this step to create rules identical to those used in ASG-Zara to identify all aspects of removable media management (for example, retention or vaulting).

For more information about Control-M/Tape rules, see the chapters about online facilities, rule parameters, and organization and administration in the Control-M/Tape User Guide.

Step 11: Adjust Rule List

Verify that all Control-M/Tape rule tables are listed in the RULLIST member of the Control-M/Tape PARM library.

This member indicates the names of the rule tables that must be loaded when Control-M/Tape is activated.

Edit the RULLIST sample member, entering a new line in the table for each new rule table.

Use the format of the existing rule tables. The asterisk (*) in column one of each line is part of the required syntax of rule member names.

For more information about the rule list member, see the Organization and Administration chapter of the Control-M/Tape User Guide.

Step 12: Verify Media Database Integrity

1. Run the CONVIDB job.

   This utility runs the CTTIDB utility to verify the integrity of the Media Database.

2. If the CTTIDB utility reports errors, this may indicate logical problems in the input data of the conversion program. In this case, find and correct the source of the problem and repeat the conversion process.

   For more information about the CTTIDB utility, see the chapter that discusses media database integrity verification in the Control-M/Tape Implementation Guide, and the Control-M/Tape chapter of the INCONTROL for z/OS Utilities Guide.

   The job should complete with a condition code of 0. If it ends with a non-zero condition code, check the messages in the job sysout to determine whether the job was performed satisfactorily.

   You can also correct any problems directly in the Control-M/Tape Media Database using the CTTMUP utility. However, since such manual corrections are lost if tape management data is reconverted, this method is advised only for the final conversion run. For more information, see the description of the CTTMUP utility in the Control-M/Tape chapter of the INCONTROL for z/OS Utilities Guide.

Step 13: Resume Tape Activity

If ASG-Zara was stopped, and Control-M/Tape will be operating in Global Test mode or in Global Phased mode, start ASG-Zara now.

Start Control-M/Tape with the following command:

S CTTINIT,PARM=‘MODE=INIT’