Conversion Steps

This chapter discusses the steps before, during, and after OPC conversion.

Overview of the Conversion Tool Operation

The operation of the conversion tool consists of a series of steps divided in the following sections:

The following is a summary of the steps:

Pre-conversion Planning

  1. Review system or OPC exits required in the Control-M environment.

  2. Ensure that all personnel involved in the conversion process have the necessary security privileges and authorizations.

Automated ICE Operations

Post-conversion Operations

BMC Software recommends that you first review the contents of Planning the Conversion and then read through the remainder of this chapter before performing the steps. It is important to follow the outlined sequence of the steps to ensure a successful conversion.

Pre-conversion Planning

Before beginning the actual conversion process, the following list must be reviewed for tasks that may need to be performed in preparation for the conversion:

  1. Review any system or OPC exits that perform functions that must be implemented in the Control-M environment.

  2. Ensure that all personnel involved in the conversion process have security access to all required functions and that they have authorization to execute the necessary batch jobs.

Automated ICE Operations

Stage 0: Set Conversion Defaults

In the SET OPC CONVERSION DEFAULTS OPTIONS panel default values are provided for the conversion parameters. New values can be specified or the default values accepted. When this stage is completed the defaults member (OPCDEF) in the INSTWORK ICE library is updated with the new values. For more information about the conversion parameters, see Conversion Parameters.

Do not add any comment text in conversion default parameter statements. Comments can be specified only in separate records containing an asterisk in column 1.

Stage 1: Data Extraction

Overview of Data Extraction

Before beginning the data extract phase, to ensure that the OPC reports are in a format recognizable by the conversion tool, you must assure that the OPC PAGESIZE option in the BATCHOPT member of the EQQPARM library is set to its default value (55).

In this stage, the OPC scheduling reports, together with all the production data files and libraries that are required for the conversion, are extracted to a scheduling data package. A job is created that must be copied to and run in an environment where the production files are accessible, from where it extracts the data and generates a scheduling data package.

If you already have your own OPC data (such as, OPC Reports and JCL libraries) and want to use the OPC Conversion ICE Interface to process the conversion, follow the instructions in Using Your Own Data to Process the Conversion.

This stage consists of the following steps:

  • preparing the conversion environment for the data extraction process

  • extracting the OPC environment data and generating a scheduling data package

Using Your Own Data to Process the Conversion

  1. Access step 4 and enter your reports file prefix, (FP3 save and exit).

    Your OPC reports must have the following suffixes:

    • AD.REPORT - OPC APPLICATION DETAIL REPORT

    • WS - OPC WORKSTATION DESCRIPTION REPORT

    • OPERINST - OPC OPERATOR INSTRUCTION REPORT

    • OPCCAL - OPC CALENDAR REPORT

    • JCLVAR - OPC JCL VARIABLE TABLE REPORT

    • PERIOD.P01,P02,...,P10,P11,...,Pnn - OPC PERIOD REPORTS

  2. Access Step 5.

    1. Enter your JCC Message Table Members. Enter Y to continue.

    2. Enter the Calendars names (the calendars numbers must be the numbers of the PERIOD reports). Enter Y to continue.

    3. If you have JCL libraries enter the names. Enter Y to continue.

  3. Continue with the conversion steps. When you reach step 9, answer N to the question and then continue with step 10, described in Create Application List.

Set File Allocation for Data Extraction

In the SET FILE ALLOCATION DEFAULTS FOR DATA EXTRACTION panel default values are provided for SMS or non-SMS parameters and space allocation parameters. The values are used in the data extraction stage.

  1. Specify a valid file name prefix for the File Name Prefix that will be used for the prefix of the OPC reports that are created by JOB0 or used by the existing OPC reports. In either case, the prefix is required for the conversion process.

  2. Do one of the following:

    • For non-SMS, specify valid values for the UNIT and VOLSER.

    • For SMS, specify valid values for SMS DATA CLASS, SMS STORAGE CLASS, and SMS MANAGMENT CLASS.

  3. For the SPACE ALLOCATION PARAMETERS specify new values or accept the default values for the following:

    • APPLICATION REPORT

    • WORKSTATION REPORT

    • OPERINST REPORT

    • CALENDAR REPORT

    • PERIOD REPORT

    • JCL VARIABLES REPORT

If you already entered a value, but wish to reset any of the space allocation parameters to its default value, enter a slash, "/", in the appropriate field.

If there is an SB37 abend due to insufficient disk space, see Table 1, and increase the appropriate space allocation.

Table 1 Fixing SB37 Problems in the Conversion

JOB

STEP

DD

Fields on the screen with the space information

JOB0

 

 

 

 

 

ADPRT

OUT

APPLICATION REPORT

WSPRT

OUT

WORKSTATION REPORT

OIPRT

OUT

OPERINST REPORT

CALPRT

OUT

CALENDAR REPORT

PRTPER

OUT

PERIOD REPORT

JCLVAR

OUT

JCL VARIABLES REPORT

JOB1

 

 

 

 

 

 

 

 

 

 

 

STEP2

 

DAWS

LIST OF OPC WORKSTATIONS

DAOUT

LIST OF QUANTATATIVE RESOURCES

STEP3

 

 

DAAPPL

APPLICATION EXTRACT INFORMATION

DACHANGE

LIST OF APPLICATION NEW NAMES

RESNAME

SPECIAL-RESOURCES FOR NAMES EXCEEDING

STEP4

DAXRF

APPLICATION VS JOBNAME XREF REPORT

STEP5

 

SORTIN

APPLICATION EXTRACT INFORMATION

CALNAME

LIST OF CALENDAR NEW NAMES

STEP6

 

 

 

DACOND

CONDITION LIST TO BE ADDED

SORTWK01

APPLICATION EXTRACT INFORMATION

SORTWK02

APPLICATION EXTRACT INFORMATION

SORTWK03

APPLICATION EXTRACT INFORMATION

JOB2

 

STEP3

 

LIBSYM

CTM AUTO-EDIT STATEMENTS LIBRARY

RECVEXT

JCL RECOVER DIRECTIVES EXTRACT FILE

JOB3

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

STEP2

DACAL

CTM CALENDARS LIBRARY

STEP3

 

DABLT

CTMBLT UTILITY INPUT STATEMENTS

DADAILY

DAILY JOB

STEP4A

 

 

 

SORTWK01

CTMBLT UTILITY INPUT STATEMENTS

SORTWK02

CTMBLT UTILITY INPUT STATEMENTS

SORTWK03

CTMBLT UTILITY INPUT STATEMENTS

SORTOUT

CTMBLT UTILITY INPUT STATEMENTS

STEP4B

DASCHD

CTM SCHEDULE TABLE LIBRARY

STEP5

DATBUPD

CTMBLT UTILITY INPUT STATEMENTS

STEP8

 

 

 

SORTOUT

APPLICATION VS JOBNAME XREF REPORT

SORTWK01

APPLICATION VS JOBNAME XREF REPORT

SORTWK02

APPLICATION VS JOBNAME XREF REPORT

SORTWK03

APPLICATION VS JOBNAME XREF REPORT

STEP8A

 

 

 

SORTOUT

JCL RECOVER DIRECTIVES EXTRACT FILE

SORTWK01

JCL RECOVER DIRECTIVES EXTRACT FILE

SORTWK02

JCL RECOVER DIRECTIVES EXTRACT FILE

SORTWK03

JCL RECOVER DIRECTIVES EXTRACT FILE

JOB4

 

 

 

 

 

STEP2

CALXML

XML FILE CONTAINING MAINFRAME CALENDARS

STEP3

CALXML

XML FILE CONTAINING DISTRIBUTED CALENDARS

STEP4

DALXML

XML FILE CONTAINING MAINFRAME JOB DEFS

STEP5

DALXML

XML FILE CONTAINING DISTRIBUTED JOB DEFS

STEP6

 

XMLOUT1

XML FILE CONTAINING DISTRIBUTED JOB DEFS

XMLOUT2

XML FILE CONTAINING MAINFRAME JOB DEFS

Extract the Data from OPC Environment

  1. In the EXTRACT CONVERSION INPUT DATA panel, specify values for the following:

    • OPC messages file

    • OPC initialization parameters file

    • OPC library name containing the JCC Message Table Members

    In addition, if you want to upload the compressed package to the BMC FTP support site specify values for the following:

    • email address

    • issue number

    Enter YES to save and continue.

  2. In the SPECIFY OPC CALENDARS panel, specify the names of the OPC Calendars that will be converted. Initially the calendar list is empty. Enter YES to save and continue.

  3. In the SPECIFY JCL LIBRARIES panel, specify the JCL libraries that need to be converted. Initially the library list is empty, but you can enter as many JCL libraries that you need to be converted. For each library, specify a unique name to be used as a suffix. The conversion renames each library, in the restore job, to prefix.suffix, and accesses it using this name. Enter YES to save and continue.

  4. If you specified Y for the PNIBTSD default parameter (for more information, see Conversion Parameters), in the SPECIFY ADDITIONAL LIBRARIES FOR PNIBTSD panel, you will be prompted for non-instream batch SYSIN file names. For each batch SYSIN file, specify a unique name to be used as a suffix. The conversion renames each file, in the restore job, to prefix.suffix, and accesses it using this name. Enter YES to save and continue.

  5. If an existing copy of the data extraction job already exists, you are prompted whether you want to replace it or not. The resultant job is then displayed in the ISPF editor for editing, if necessary.

  6. Run the job in the environment where OPC is installed.

  7. Verify that the job ran successfully.

For more information, see JOB0: Produce OPC Reports.

Closure of Data Extraction

In this stage, the OPC scheduling reports, with all the required production data files and libraries were extracted and compressed into a scheduling data package (prefix.TRS). Copy the scheduling data package, to the conversion environment.

Stage 2: Conversion

Overview of Conversion Process

The scheduling data package, created in the previous stage, is copied to the conversion environment. The OPC job scheduling reports and calendars, and the OPC JCL libraries and members are all converted to Control-M format. Finally, XML draft files are created that contain the job definitions and calendars in Control-M format. The XML draft files can later be opened directly by Control-M/Desktop for loading to Control-M/Enterprise Manager.

This stage consists of the following steps:

  • preparing the environment for the conversion process files

  • running a job to extract the files from the compressed file taken from the production environment

  • running a job that creates an application list (and if necessary, adjusting the results)

  • converting the JCL libraries

  • running a job that creates Control-M Calendar and table libraries (and if necessary, adjusting the results)

  • running a job that creates Control-M XML draft files (and if necessary, adjusting the results)

Set File Allocation for Conversion

  1. In the SET FILE ALLOCATION DEFAULTS FOR CONVERSION STAGES panel values are provided for SMS or non-SMS parameters and space allocation parameters. Specify new values or accept the default values. The values are used in the following conversion stages.

  2. Enter YES to save and continue.

Extract the Package File

  1. Select the Extract the Package File step.

    • In the TRS File to be Extracted field, type the new name of the TRS file brought from the production environment.

    • Press Enter.

  2. The jobs for extracting the package file run automatically in the conversion environment.

  3. Confirm to continue, when prompted after the metadata extraction job, before the job that extracts the other files.

  4. Verify that the jobs ran successfully.

Create Application List

  1. Select the Create application list step.

  2. The job for creating the application list is displayed in the ISPF editor. If necessary, edit the job.

  3. Run JOB1 in the conversion environment.

  4. Verify that the job ran successfully.

For more information, see JOB1: Extract Workstation and Application Info.

Review and Modify Application List

The Applications list file is a sequential file (with record length of 150) which contains a list of OPC applications (and owners) with the corresponding Control-M table names (and owners) that are to be assigned.

An editor can be used to optionally modify the following:

  • New Table Name (columns 18 through 25)

  • New Owner ID (columns 45 through 52)

When editing, it is important to ensure that the table names remain unique, valid PDS member names.

Convert JCL Libraries

To run the converted jobs on Control-M for z/OS, the OPC JCL libraries are converted to Control-M format.

  1. Select the Convert JCL Libraries step.

  2. In the BATCH TERMINAL DEFINITIONS panel, enter the OPC batch utility program and procedure names.

  3. Enter YES to save and continue.

  4. If an existing copy of the JCL conversion job already exists, you are prompted whether you want to replace it or not. The resultant job is then displayed in the ISPF editor for editing, if necessary, for example, to adjust the OPC Case Codes. For more information about OPC Case Codes see JOB2 Input.

  5. Run the job in the conversion environment.

  6. Verify that the job ran successfully.

For more information, see JOB2: Convert JCL Members.

Create CTM Scheduling & Calendars

  1. Select the Create CTM scheduling & calendars step.

  2. The job for creating the Control-M Calendar and table libraries is displayed in the ISPF editor. If necessary, edit the job.

  3. Run the job in the conversion environment.

  4. Verify that the job ran successfully.

For more information, seeJOB3: Construct Control-M Calendars, Table and CMEM Libraries.

Create CTM XML

  1. Select the Create CTM XML step.

  2. In the CREATE CTM XML DEFINITIONS FOR JOBS AND CALENDARS panel, enter the following information:

    • name of Control-M datacenter for distributed jobs

    • name of Control-M datacenter for mainframe jobs

    • the prefix to use for distributed-to-mainframe condition names

    • the prefix to use for mainframe-to-distributed condition names

    • the prefix to use for global condition names

  3. Enter YES to save and continue.

  4. If an existing copy of the XML creation job already exists, you are prompted whether you want to replace it or not. The resultant job is then displayed in the ISPF editor for editing, if necessary.

  5. Run the job in the conversion environment.

  6. Verify that the job ran successfully.

Closure of Conversion Process

At this stage, the scheduling data package (created from the production environment) has been copied to the conversion environment, and then uncompressed. In addition, the OPC job scheduling reports and calendars, and the OPC JCL libraries and members have been converted to Control-M format. Finally, XML draft files have been created that contain the job definitions and calendars in Control-M format.

Load the XML files to Control-M/Enterprise Manager to validate the conversion. For more details, see step 7 in the procedure described in Post Step 3: Check Conversion Results.

Post-conversion Operations

Post Step 1: Customize Control-M

  1. Make the following changes to the CTMPARM member in the IOA.PARM library:

    • Set the SCHPREVD parameter to Y. This parameter operates on jobs scheduled between midnight and the Control-M New Day time. It shifts these jobs to the previous day to avoid date discrepancies. This parameter is only operative when the SAC Control-M job scheduling parameter is set. For more information, see Control-M New Day Processing.

    • Set the FORCETAG parameter to Y.

    • Set the MAXACTIV parameter to a relevant maximum limit for the number of active jobs in Control-M.

  2. Copy the CNVOPCIN member from the IOA SAMPLE library into one of the libraries specified in the EQQJBLIB DD statement. For more information, see step 5. This member contains the translation of OPC system variables to Control-M AutoEdit format.

  3. Place the GLOBAL table member into the library specified in the DAGLOBAL DD statement of the Control-M procedure. The GLOBAL table member was named by means of the GTABLE conversion parameter, which is described in "GTABLE" in Conversion Parameters.

    Ignore this item if the value of the GTABLE parameter was specified as blank.

    To utilize the full potential of Control-M, users converting the OPC JCL variable tables might want to implement the Control-M Parameter Prompting Facility, described in the Control-M for z/OS User Guide, as an alternative to utilizing the AutoEdit variable library created in the conversion.

  4. Additional DD statements might be required in the Control-M monitor procedure and in the online logon procedure, as follows:

    • If OPC variables or OPC FETCH directives are used in your OPC JCL, an EQQJBLIB DD statement must refer to the library or library concatenation where FETCHed members reside.

    • If OPC RECOVER directives are used in your OPC JCL to set a value for the ADDPROC parameter, an EQQPRLIB DD statement must refer to the library or library concatenation where the ADDPROC RECOVER procedures reside.

  5. If the OPC database contains applications with no operations, then both the Control-M profile variable PGRPEMPT and the CTMPARM parameter EMPTYGRP must be set to Y.

Post Step 2: Perform Final Adjustments

The following final adjustments must be performed:

  1. The CTMXRF Control-M utility must be run with the cross reference statement XRF=RES, to determine if any Quantitative resources were placed in the newly created job scheduling definitions. Ifthis is the case, these resources must be added to the Control-M Resources file using the IOACND utility. For more information on the IOACND utility, see the INCONTROL for z/OS Utilities Guide.

  2. If CA-LIBRARIAN or CA-PANVALET libraries were converted to partitioned data sets in Step2 above, they may be reconverted back to CA-LIBRARIAN or CA-PANVALET format at this point.

  3. Review all OPC system exits (if any), for example, the OPC JES2 or JES3 interfaces, such asthe JES2 Exit6, the JES3 IATUX03, and the OPC SMF IEFUJV exits. Remove or modify such exits as appropriate.

Post Step 3: Check Conversion Results

  1. Transfer the Job schedule definition XML files (MF.XML and DS.XML) and the Calendar definition files (CALMF.XML and CALDS.XML) from the mainframe to the conversion environment.

    If wrong server names were provided during the conversion, you can use any text editor to replace the incorrect names with the correct names.

  2. Load the calendars to Control-M/EM through Control-M Web or using the EMDEF DEFCAL utility.

  3. Load the Job Schedule definition XML files to a Control-M/EM planning workspace, either one at a time or both together. You can do this either through the Control-M client or, for a small number of jobs, through Control-M Web.

  4. Review the list of warning messages produced during the conversion and perform all required manual adjustments.

  5. Use the View Schedule option to verify that the scheduling criteria of the converted jobs are the same as in OPC. If required, modify either the calendars or the job scheduling criteria to achieve the correct scheduling.

  6. Use the Verification Tool to compare jobs from specific dates (for example: a specific weekday, weekend, beginning of month, end of quarter, or holidays) based on reports produced by OPC.

  7. Verify the scheduling of specific folders by comparing the OPC long-term plan to the Control-M forecast.

  8. Start up Control-M Monitor and IOAGATE on the mainframe for Control-M for z/OS jobs. Start up Control-M Server and its corresponding Gateway for Control-M for Distributed Systems jobs.

    Verify that all are connected and working properly before continuing.

  9. Copy the CMEM sequential file to a member within a Control-M CMEM rules table library.

  10. Run the CalendarsDuplicatesRemoval utility to remove duplicate calendars. (Optional.)

  11. Define the GCS distribution list.

    It must be the same file used by the Control-M for z/OS conversion process to add the correct prefix to the various combinations of conditions based on their source and destination.

  12. Set the Forecast User-Daily setting for the Control-M for z/OS tables. For more details, see the Control-M Business Service Management Solution User Guide.

Post Step 4: Customize the New Day Procedure

Specify the new tables in the DAJOB DD statement of the Control-M New Day procedure. Use the list of tables created by JOB3 in the DADAILY file.

Order the IOALDNRS utility as part of the New Day procedure (and periodically during the day, if necessary) to produce the IOA Manual Conditions file. This file lists manual conditions for which jobs are waiting and can be used to add (or delete) these conditions to the IOA Conditions file, when necessary.