Conversion Steps

This chapter includes the following topics:

Overview of Conversion Tool OperationLink copied to clipboard

If you have not yet downloaded and installed the Control-M conversion tools, do so now according to the instructions in Downloading and Installing the Control-M Conversion Tools.

Installation and Operation of the Conversion Tool Consists of a Series of StepsLink copied to clipboard

BMC Software recommends that you first review the contents of Appendix E, "Planning the Conversion," 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.

The following is a summary checklist of the steps:

  1. Create the conversion source and load libraries.

  2. Copy CA-JOBTRAC JCL Libraries and JMF Members.

  3. Check and modify parameters in the DEFAULTS member.

  4. Modify and run the ASMLINK member.

  5. Modify and run the JOB0 member.

  6. Modify and run the JOB1 member.

  7. Modify and run the JOB2 member.

  8. Modify and run the JOB3 member.

  9. Final adjustments.

  10. Check the conversion results.

  11. Add new tables to the New Day Procedure.

  12. Create Control-M Calendars.

  13. Add resources to the Control-M Resources File.

Step 1. Create the Conversion Source and Load LibrariesLink copied to clipboard

  1. Run the $$INIT job in the IOA CONV library to create the JOBTRAC conversion Source library and allocate the conversion Load library.

  2. Tailor the following parameters in the member in accordance with your local site conventions.

    Table 6 Parameters To Be Adjusted

    Parameter

    Description

    Job statement

     

    INLIB

    IOA CONV library name

    OUTLIB

    JOBTRAC conversion source library name

    LOADLIB

    JOBTRAC conversion load library name

    UNIT

    Unit name of DASD device

    VOLSER

    Volser of DASD device

    PRODUCT

    JOBTRAC

  3. Submit the job for execution. The job must finish with a completion codeof0.

Step 2. Copy CA-JOBTRAC JCL Libraries and JMF MembersLink copied to clipboard

To prevent changes to the current production JCL environment, you should create a copy of the CA-JOBTRAC JCL libraries and JMF members. JMF members include the JMFSYM01 member in the DATELIB library, and any alternate JMF members.

A sample job for copying these production JCL libraries is provided in the COPYLIBS member in the conversion source library.

For CA-LIBRARIAN or CA-PANVALET libraries, use the utilities supplied by Computer Associates International, Inc. to create and copy the production JCL libraries into partitioned data sets for use by the conversion tool.

New libraries must be allocated with enough space and directory blocks to enable update of all their members.

Step 3. Check and Modify the Parameters in the DEFAULTS MemberLink copied to clipboard

Edit the DEFAULTS member in the conversion source library. Adjust the Control-M parameters according to your site requirements. In addition, to set a MAXWAIT default value, set optional wish WM2367 (in member IOADFLT of the IOA IOAENV library) at this point.

For a detailed description of these conversion parameters, see Downloading and Installing the Control-M Conversion Tools.

Step 4. Modify and Run the ASMLINK MemberLink copied to clipboard

The ASMLINK member in the conversion source library assembles and link-edits all conversion programs using the DEFAULTS parameter member, which was tailored in the previous step.

Edit the ASMLINK member to adjust the following specifications in accordance with your local conventions, in both the ASMMCL and LKED procedures:

  • Job statement.

  • Conversion Source library name (the SRCLIB parameter) created in Step1.

  • Conversion Load library name (the LOADLIB parameter) allocated in Step1.

  • IOA LOAD library name (the IOALOAD parameter).

  • IOA MAC library name (the IOAMAC parameter).

  • IOA SMP/E Distribution LOAD library name, set in the ALOAD parameter.

Submit the job and check the sysout for completion code and error messages. A condition code of 4 in the link-edit steps is acceptable, if caused by unresolved external references. All other steps must complete with a condition code of 0.

This step must be re-executed whenever changes are made to the parameters in the DEFAULTS member or a source fix is applied to any module. If necessary, also perform an LLA REFRESH after changes are made.

Step 5. Modify and Run the JOB0 MemberLink copied to clipboard

JOB0 packs all the CA-JOBTRAC files into a single DFDSS DUMP file, and uses FTP to upload the TERSED file to the BMC support site.

Edit the JOB0 member in the conversion source library. Adjust the following specifications according to your local conventions:

  • The job statement.

  • The name of the CA-JOBTRAC EXCLPARM member in the TRACPARM library, specified in the DAEXCL DD statement in STEP0.

  • The name of the CA-JOBTRAC RESOURCE member in the TRACPARM library, specified in the DARESIN DD statement in STEP0.

  • The name of the CA-JOBTRAC JMFSYM01 member in the DATELIB library, specified in the DATELIB1 DD statement in STEP0.

  • The name of the CA-JOBTRAC PRODDATE member in the DATELIB library, specified in the DATELIB2 DD statement in STEP0.

  • The name of the CA-JOBTRAC EXCLPARM library, specified in the EXCLPARM DD statement in STEP0. The library name must be the same as for DD statement DAEXCL.

  • The name of the CA-JOBTRAC RESOURCE library, specified in the RESOURCE DD statement in STEP0.

  • The name of the CA-JOBTRAC DATELIB library, specified in the JMFSYM01 DD statement in STEP0. The library name must be the same as for DD statement DATELIB1.

  • The name of the CA-JOBTRAC DATELIB library, specified in the PRODDATE DD statement in STEP0. The library name must be the same as for DD statement DATELIB1.

  • The name of the CA-JOBTRAC SCLLIB library in STEP6.

  • The name of the CA-JOBTRAC EXCLPARM library in STEP6. The library name must be the same as for DD statement DAEXCL in STEP0.

  • The name of the CA-JOBTRAC RESOURCE library in STEP6. The library name must be the same as for DD statement RESOURCE in STEP0.

  • The name of the CA-JOBTRAC CCPF report in STEP6.

  • The name CTM.JBT.JMFSYM01 in STEP6 to be the same as in DD statement JMFSYM01 in STEP0.

  • The name CTM.JBT.PRODDATE in STEP6 to be the same as in DD statement PRODDATE in STEP0.

  • The name of the CA-JOBTRAC ADR report in STEP6.

  • The name of the CA-JOBTRAC AMR report in STEP6.

  • The name of the CA-JOBTRAC SCS report in STEP6.

  • The name of the tersed file in step TERSE.

  • The email address in step FTP1.

  • The opened issue number (2 places) in step FTP1.

  • The email address in step FTP1.

  • The name of the tersed file in step FTP1. This name must be the same as in step TERSE.

Submit the job and check the sysout for completion code and error messages. For message explanations, see Messages.

Step 6. Modify and Run the JOB1 MemberLink copied to clipboard

JOB1 creates the Control-M table and Calendar library.

Edit the JOB1 member in the conversion source library. Adjust the following specifications according to your local conventions:

  • Job statement.

  • Conversion load library name (specified in the CTMLOAD DDstatement in STEP0).

  • IOA LOAD library name (specified in the IOALOAD DDstatement in STEP0).

  • IOA PARM library name (specified in the IOAPARM DDstatement in STEP0).

  • IOA LOG library name (specified in the IOALOG DDstatement in STEP0).

  • IOA IOAENV library name (specified in the IOAENV DD statement in STEP0).

  • Name of the CA-JOBTRAC schedule library containing the Schedule Control Language (SCL) members (specified in the DASCL DDstatement in STEP0).

    If you want to concatenate multiple SCL libraries in a single execution, change JOB1 as follows:

    In STEP0 add the following DD statements:

    CopyCopied to clipboard 
    //DASCL2  DD  DISP=SHR,DSN=second-SCL-lib
    //DASCL3  DD  DISP=SHR,DSN=third-SCL-lib
    //DASCL4  DD  DISP=SHR,DSN=fourth-SCL-lib
    //DASCLn  DD  DISP=SHR,DSN=nth-SCL-lib

    And in both STEP2 and STEP6 change the DASCHD DD as follows:

    CopyCopied to clipboard 
    //DASCHD DD  DSN=*.STEP0.DASCL,DISP=SHR
    //       DD  DSN=*.STEP0.DASCL2,DISP=SHR
    //       DD  DSN=*.STEP0.DASCL3,DISP=SHR
    //       DD  DSN=*.STEP0.DASCL4,DISP=SHR
    //       DD  DSN=*.STEP0.DASCLn,DISP=SHR

  • Name of the CA-JOBTRAC TRACPARM library containing the EXCLPARM member (specified in the DAEXCL DDstatement in STEP0,).

  • Name of the CA-JOBTRAC TRACPARM library containing the RESOURCE member (specified in the DACND DDstatement in STEP0).

  • Name and location of the Control-M CMEM Rule table (specified in the DACMEM DDstatement in STEP0).

  • Name and location of the table definition file (specified in the DABLT DDstatement in STEP0).
    This file is the input to the CTMBLT utility.

  • Name and location of the CONTROL-M scheduling table library (specified in the DASCHD DD statement in STEP0).

  • Name and location of the Control-M IOACND JCL utility that adds resources to the Control-M Resources file (specified in the DAPRM DDstatement in STEP0).

  • Name of the CA-JOBTRAC CCPF table print image file (specified in the DAREPORT DDstatement in STEP0).

  • The name and location of the output distributed job definition XML (DAXML DDstatement in STEP0). Several CTMTLB parameters must be manually set (DATACENTER, SCHEDULE-LIB). For details, see the INCONTROL for z/OS Utilities Guide.

  • The name and location of the output mainframe job definition XML (DAXML2 DDstatement in STEP0). Several CTMTLB parameters must be manually set (DATACENTER, SCHEDULE-LIB). For details, see the INCONTROL for z/OS Utilities Guide.

Submit the job and check the sysout for completion code and error messages. For message explanations, see Messages.

The message following message may be ignored for the first (or only) run of JOB1:

CopyCopied to clipboard 
IEF283I NOT DELETED 8

If you are allocating files on SMS-managed volumes, you must, prior to executing JOB1 the first time, pre-allocate all files referred to by DD statements DACMEM, DABLT, DASCHD, and INCLIB.

If the JOBTRAC SCLs do not contain any distributed jobs definitions, delete the following from JOB1:

  • In STEP0 and STEP1, the DAXML DD statement

  • STEP10

Step 7. Modify and Run the JOB2 MemberLink copied to clipboard

JOB2 converts the CA-JOBTRAC JCL libraries and JMFSYM01 members to Control-M AutoEdit format.

Edit the JOB2 member in the conversion source library. Adjust the following specifications according to your local conventions:

  • Job statement.

  • Conversion Load library name (specified in the CTMLOAD DDstatement in STEP0).

  • IOA LOAD library name (specified in the IOALOAD DDstatement in STEP0).

  • Name of the CA-JOBTRAC DATELIB library containing the JMFSYM01 member (specified in the DAJMF DDstatement in STEP0).

    Ensure that this name, and any alternate JMF members, are not the actual JMFSYM01 production members, but only copies; for instructions, see Step 2. Copy CA-JOBTRAC JCL Libraries and JMF Members.

  • Name of the CA-JOBTRAC DATELIB library containing the PRODDATE member (specified in the DAPDATE DDstatement in STEP0).

  • Name and location of the partitioned data set into which the members containing Control-M AutoEdit %%INCLIB statements (for CA-JOBTRAC JCL ADI statements) are to be placed (specified in the DAINCLIB DDstatement in STEP0).

  • Name of the CA-JOBTRAC JCL library (specified in the JBTJCL DDstatement in STEP0).

  • Name of the CA-JOBTRAC SCS table print image file (specified in the DASCS DD statement in STEP0).

  • Name and location of the Control-O Rule table for ON EVENT rules (specified in the DARULE3 DD statement in STEP0).

    Ensure that this name is not the actual production JCL library name, but only a copy; for instructions, see Step 2. Copy CA-JOBTRAC JCL Libraries and JMF Members. STEP3 in JOB2 must be executed as many times as there are CA-JOBTRAC JCL libraries.

Submit the job and check the sysout for completion code and error messages. For message explanations, see Messages. The job must finish with a condition code of 0.

Step 8. Modify and Run the JOB3 MemberLink copied to clipboard

JOB2 converts the CA-JOBTRAC ADR and AMR tables to Control-O Rules tables.

Edit the JOB3 member in the conversion Source library. Adjust the following specifications according to your local conventions:

  • Job statement.

  • Conversion Load library name (specified in the CTMLOAD DDstatement in STEP0).

  • IOA LOAD library name (specified in the IOALOAD DDstatement in STEP0).

  • IOA PARM library name (specified in the IOAARM DDstatement in STEP0).

  • IOA LOG library name (specified in the IOALOG DDstatement in STEP0).

  • IOA IOAENV library name (specified in the IOAENV DDstatement in STEP0).

  • Name of the Control-M Job Scheduling library created in JOB1 (specified in the DASCHD DDstatement in STEP0).

  • Name of the CA-JOBTRAC ADR table print image file (specified in the DAADR DDstatement in STEP0).

  • Name of the CA-JOBTRAC AMR table print image file (specified in the DAAMR DDstatement in STEP0).

  • Name and location of the Control-O Rule table for ON DSNEVENT rules (specified in the DARULE1 DDstatement in STEP0).

  • Name and location of the Control-O Rule table for ON MESSAGE and ON STRING rules (specified in the DARULE2 DDstatement in STEP0).

Submit the job and check the sysout for completion code and error messages. For message explanations, see Messages. The job must finish with a condition code of 0.

Step 9. Final AdjustmentsLink copied to clipboard

  1. If a CMEM rule table was built in the CMEM file created in JOB1, follow the instructions on managing the CMEM facility in the INCONTROL for z/OS Administrator Guide.

  2. Ensure that the JCL libraries specified by the DAINCLIB and JBTJCL DD statements in Step 6 are are concatenated in member IOADSN in the IOA IOAENV library (or member IOADSNL in the IOA PARM library) via the KEY parameter for a DALIB DD statement. For further information about the IOADSN member, see the section about Allocation Members in the INCONTROL for z/OS Administrator Guide.

  3. Copy the DYNAMIC member from the conversion Source library and the JMFSYM01 member specified by the DAJMF DDstatement, which is referred to in Step6, to the library named in the INCLIB conversion parameter, which is described in "INCLIB" in B Conversion Parameters.

  4. Set the MAXCCOK parameter to the maximum acceptable condition code for any job step. For further information on this parameter, see the CTMPARM member in the IOA PARM library.

  5. If conversion option TOCLS was set to blank due to distributed job definitions in your JOBTRAC SCLs, but you nevertheless require the SYSOUT requeuing feature for the JOBTRAC mainframe jobs (described in Unique Control-M Parameters), you should customize and install sample user exit CTMX001D, which is provided in the IOA SAMPEXIT library.

    This exit may be tailored to local requirements. Carefully read the comments in the CTMX001D members of the IOA SAMPEXIT library to determine the desired method of implementation. If Exits 1 is currently being used, the supplied exit must be incorporated into the current exit.

  6. If the JOBTRAC SCLs contain distributed job definitions, follow the instructions in Step 5 (JOB1, DD statement DAXML) for processing the XML scripts produced by the CTMTLB utility for uploading to the proper distributed platform.

Step 10. Check the Conversion ResultsLink copied to clipboard

  1. Export the job schedule definitions of both Control-M for z/OS jobs and Control-M for Distributed Systems jobs.

    In the conversion jobs, specify unique names of all the required Control-Ms for the DATACENTER parameter values used as input to the CTMTLB utility.

    The specified names of the Control-Ms must the same names that will be used in Step 4, where the Control-Ms are defined using the Control-M Configuration Manager.

    If required, Control-M for Distributed Systems jobs can be divided among more than one Control-M. (Tip: use a table name prefix, or a list of table names.) To achieve this, the export to XML step must be repeated, and in each run, a different Control-M and different table names must be specified. This process must be performed on the job created in the conversion job library.

  2. Export the calendars created in the conversion process.

    Create a calendar XML for each Control-M (either Control-M for z/OS jobs or Control-M for Distributed Systems jobs), so it is possible to load them to all Control-Ms. If there are manual adjustments to calendars, or entire calendars that have to be created, either create them before the export process, or do it from Control-M/EM after loading the exported ones.

  3. 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.

  4. Define all Control-Ms (Control-M for z/OS jobs and Control-M for Distributed Systems) in the Control-M/Enterprise Manager environment.

    Define all required Control-Ms using the Control-M Configuration Manager. It is preferable to use the automatic discovery method. If the manual definition method must be used, verify that all settings and parameters are according to the attributes of the Control-M. The Platform attribute (Distributed or z/OS) is the most important setting that cannot be changed later.

    In any case, you must use the same names of the Control-Ms that were specified for the DATACENTER parameter values in Step 1.

  5. Import the exported Calendars to all Control-Ms on Control-M/EM.

    Use the Control-M/EM defcal utility. If there are manual modifications or whole calendars to be created, verify that all are available.

  6. Define the GCS distribution list.

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

  7. Load each XML file to Control-M/Desktop and write it to the Control-M/EM database, by doing the following:

    1. Save the XML draft files in a folder accessible to Control-M/Desktop.

    2. Open Control-M/Desktop.

    3. Select File => Open. Navigate to the folder where you saved the XML draft files. Set the Files of type to (ExportDefTable Format) (*.xml).

    4. Select the XML draft file and click Open.

    5. The jobs are displayed in a Workspace.

    6. After performing any necessary adjustments to the job definitions, write the job definitions to the Control-M/EM database, by selecting Action => Write.

    For more information, see the Control-M User Guide.

    Review any error messages, and resolve them. Some errors are detected and reported during the loading of the XML to Control-M/Desktop, and some errors are reported only when the draft is written to Control-M/EM. You might be required to re-run several conversion steps in Control-M for z/OS and then continue with step 1 of the testing.

  8. Set the New Day mechanism. For both Control-M for z/OS and Control-M for Distributed Systems, define the User-Daily jobs to be scheduled from the system daily and run at suitable times. Verify that every table is covered by at least one User-Daily. On the Control-M for z/OS, the User Daily can be either based on jobs that reference the various tables, or by job that uses the value of the table User-Daily field. Use the conversion created report as the basis for this process.

  9. Set 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.

  10. Run Control-M/Forecast for the Control-M or table, and create a full year plan of all jobs. This plan can be exported to text and compared with the reports that are produced from your current scheduling tool.

  11. Load Forecast from Control-M/Desktop on a specific date (as many times and various days as required), and compare the predicted flow with the current scheduling tool reports.

Step 11. Add New Tables to the New Day ProcedureLink copied to clipboard

Specify the new tables (created in JOB1) in the DAJOB DD statement of the Control-M New Day procedure.

Step 12. Create Control-M CalendarsLink copied to clipboard

The conversion tool places calendar names in the DCAL Control-M job scheduling parameter. The names used are WORKDnnn, HOLID, CYCLEnnn, and CYCnnn. In each of these names, nnn is the CA-JOBTRAC Location ID. In addition, the conversion tool may place other calendar names in the DCAL parameter in either of the following cases:

  • The Control-M Basic Scheduling parameters require a non-standard (periodic) calendar name.
    Calendar names such as xxxCYCyy may be created.

  • User-defined scheduling criteria (UDEFx) cannot be completely or consistently converted to values for the DATES Control-M parameter, or C is specified for the UDEF conversion parameter.

For further information, see Calendars.

The CTMXRF Control-M utility aids in the identification of calendar names used in the Control-M tables. All calendar names specified in the CTMXRF Calendar Cross Reference report (XRF=CAL) must be manually created using the Control-M IOA Calendar facility.

Step 13. Add Resources to the Control-M Resources FileLink copied to clipboard

Examine the DAPRM file created in JOB1 (see Step 5. Modify and Run the JOB0 Member). If there are any ADD RESOURCE control statements present, run the job in this file; otherwise skip this step.