Conversion Steps

This chapter includes the following topics:

Overview

The conversion process consists of the following steps, which can be implemented separately according to the needs of the report distribution environment.

  1. Tailor and Run Member INPJASML.

  2. Create the INFOPAC dump file that is used as input for the conversion programs.

  3. Create Control-D decollation mission definitions from INFOPAC information, as follows:

    1. Check and Modify Options Specified in Member INPDEFDM

    2. Check and Modify the Table of Migration Mission Names

    3. Tailor and Run Job INPJDECM

  4. Create the Control-D Recipient Tree, using INFOPAC recipient reports. The Control-D Recipient Tree is a very important element of Control-D that is used by almost all Control-D processes. Therefore, the Recipient Tree should include all Control-D recipients before you begin testing Control-D functions.

  5. Create the Control-D History User file from INFOPAC information, to enable access to reports archived by INFOPAC.

    1. Tailor and Run Job INPJARCH

    2. Tailor and Recompile User Exit CTDX004

    3. Tailor Skeleton INPSKL in the Control-D SKL Library

  6. Test the Conversion

Step 1. Tailor and Run Member INPJASML

  1. Use member ASMLINK to assemble and link-edit the conversion programs.

    • Tailor the JCL of this member according to your naming conventions.

  2. Submit the job for execution and check the sysout for error messages. Condition code 0 indicates proper completion of the job.

Step 2. Create the INFOPAC Dump File

  1. Use sample job INPJDUMP in the IOA SAMPLE library to create the INFOPAC dump file.

    • The following table describes the input and output for this step:

      Table 1 Job INPJDUMP Input and Output

      Data

      Description

      Input

      Input the INFOPAC database in this step.

      Output

      Output is a sequential file containing the dump.

      Name the output file CTD.INPC.REPORT. Otherwise, you must change the name in the job that extracts the data.

      Make sure the output file has the following characteristics: physical sequential, record format FBA, logical record length 133.

  2. Submit the job for execution and check the sysout for error messages. Condition code 0 indicates proper completion of the job.

Step 3. Convert Report Definitions

Step 3.A. Check and Modify Options Specified in Member INPDEFDM

Tailor the Control-D options specified in member INPDEFDM in the IOA SAMPLE library. Adjust the options according to your needs. The default values of the options are listed in Default Conversion Parameters.

Step 3.B Check and Modify the Table of Migration Mission Names

  1. Check and modify the migration mission table in the sequential file as needed.

  2. Ensure that this file has the following characteristics: physical sequential, record format FB, logical record length 80.

    • The name of the INFOPAC migration class begins in column 1. The name of the corresponding migration mission begins in column 15.

Step 3.C Tailor and Run Job INPJDECM

Use job INPJDECM to build the Control-D decollation mission definitions.

The following table describes the input and output for this step:

Table 2 Job INPJDECM Input and Output

Data

Description

Input

Input to this step includes the following entities:

  • CTD.INPC.REPORT file, extracted from the INFOPAC database.

  • CTD.INPC.MIGCLASS file, including the table of migration mission names.

  • Member INPDEFDM in the IOA SAMPLE library. This member contains external parameters for the conversion. These parameters are used as defaults for the report decollation definitions. Make any necessary changes before you run job INPJDECM.

Output

This step outputs a PDS library containing Control-D report decollation mission definitions.

The default file name is CTD.REPORTS. The characteristics of this file are: partitioned dataset, logical record length 80, blocksize 3120.

  1. Tailor member INPJDECM in the IOA SAMPLE library.

  2. Submit the jobs for execution and check the sysout for error messages. Condition code 0 indicates proper completion of the job.

Make sure the SPACE parameter specified for file DAREPMIS contains enough directory blocks, and that the primary allocation value is large enough.

Step 4. Create the Control-D Recipient Tree

  1. Use job INPJTREE from the IOA SAMPLE library to create the Control-D Recipient Tree.

  2. Submit the job for execution and check the sysout for error messages. Condition code 0 indicates proper completion of the job.

    For more information about building a Control-D Recipient Tree, see Building a Control-D Recipient Tree.

Step 5. Archive the Conversion

Step 5.A Tailor and Run Job INPJARCH

Job INPJARCH adds records to an existing History User file. If this job is rerun, reformat the History User file to prevent the addition of duplicate records. Use job CTDUFDBF from the Control-D JCL library to reformat the History User file.

  1. Submit the job for execution and check the sysout for error messages. Condition code 0 indicates proper completion of the job.

  2. Run the CTDUFSR utility to resort the data portion of the History User file. A sample job can be found in member CTDUFSR in the CTD JCL library.

Step 5.B Tailor and Recompile User Exit CTDX004

Adjust User Exit CTDX004 using Sample Exit CTDX004L supplied in the IOA SAMPEXIT library.

Step 5.C Tailor Skeleton INPSKL in the Control-D SKL Library

Tailor skeleton INPSKL in the Control-D SKL library.

Step 6. Test the Conversion

Test the conversion.