Conversion Steps

This chapter includes the following topics:

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. Verify the integrity and accuracy of the CA-7 database.

  2. Simplify the JCL conversion process by running the CA-7 SASSJCLU utility.

  3. Ensure that all calendar-oriented schedules are RESOLVEd against the proper Base Calendar.

  4. Review system exits required in the Control-M environment.

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

Automated ICE Operations

  1. Stage 0. Set Conversion Defaults

  2. Stage 1. Data Extraction

  3. Stage 2. Schedule Definition Conversion

  4. Stage 3. JCL Conversion

Post-conversion Operations

  1. Post Step 1. Customize Control-M and Install User Exits

  2. Post Step 2. Perform Final Adjustments

  3. Post Step 3. Check Conversion Results

  4. Post Step 4. Customize the New Day Procedure

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. Verify the CA-7 database to ensure its integrity and accuracy.

    1. Run the UCC7DBVR program to verify that all logical pointers in the CA-7 database are properly set.

    2. Run the following Analyze commands to correct, if necessary, various database index entries and cross references.

      • RQMT

      • TRIG

      • XREF

      • RESANL

  2. Simplify the JCL conversion process by running the CA-7 SASSJCLU utility against the CA-7 JCL Scheduled Override control statements and the scheduled JCL itself.

  3. Ensure that all calendar-oriented schedules are RESOLVEd against the proper Base Calendar. Without schedule resolution, job schedules cannot be correctly defined in the LSCHD report. For more information, see JOB1.

  4. Review any system, CA-7, or CA-11 exits that perform functions that must be implemented in the Control-M environment.

  5. Ensure that all personnel involved in the conversion process have security access to all required functions, such asauthorized CA-7 LOGON IDs, and that they have authorization to execute the necessary batch jobs.

Automated ICE Operations

Stage 0. Set Conversion Defaults

In the SET CA-7 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 default member (CA7DEF) in the IOA INSTWORK (ICE) library is updated with the new values. A short description accompanies each parameter. For full 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

In this stage, the CA-7 scheduling definitions, 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.

This stage consists of the following steps:

  • preparing the conversion environment for the data extraction process

  • extracting the CA-7 environment data and generating a scheduling data package

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. New values can be specified or the default values accepted. The values are used in the data extraction stage.

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

Table 2 Fixing SB37 Problems in the Conversion

JOB

STEP

DD

Fields on the Screen with the Space Information

JOB0

 

 

 

 

 

STEP1

SYSPRINT

LJOB REPORT

S1P*

SYSPRINT

LJOB REPORT

STEP2

SYSPRINT

LSCH REPORT

STEP3

 

BASE CALENDARS REPORT

STEP4

 

(for CA-7 R3.2 or earlier only) RESOURCE REPORT

STEP5

 

LARF REPORT

JOB1

 

 

 

 

 

 

 

 

 

 

STEP3

DALJOBO

REFORMATED LJOB

STEP5

DAJOBSCH

JOB/SCHID LIST FILE

STEP7

DALJOBO

REFORMATED LJOB

STEP8

DALJOBO

REFORMATED LJOB

STEP9

DAOUT1

APPLICATION REPORT FILE

STEP10

 

DACAL

CONTROL-M CALENDAR LIBRARY

DACALS

SCHDYONLY/PERIODIC CAL NAMES FILE

STEP11

SORTOUT

CALENDAR NAMES LIST FILE

STEP12

DABLT

LARF REPORT

STEP13

DASCHD

LARF REPORT

STEP1B

LJOBSORT

SORTED LJOB

JOB2

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

STEP2

 

 

 

 

DACMEM

CONTROL-M CMEM RULES TABLE

DATAG

ADDITIONAL SCHEDULING RBC FOR 'DATES'

DABLT

CTMBLT CONTROL STATMENTS

DABLTF

LARF REPORT

DD PJCLCNV

LJOB JOBNAME FILE FOR JCL CONVERSION

STEP2A

 

 

 

SORTWK01

CTMBLT CONTROL STATMENTS

SORTWK02

CTMBLT CONTROL STATMENTS

SORTWK03

CTMBLT CONTROL STATMENTS

SORTOUT

CTMBLT CONTROL STATMENTS

STEP2B

DASCHD

CONTROL-M SCHEDULING TABLE LIB

STEP5

CTMSV5

CONTROL-M SCHEDULING TABLE LIB

STEP6

DADAILY

LIST OF SCHEDULING TABLES TO ORDER

STEP6C

DASCHD

CTMBLT CONTROL STATMENTS

STEP6D

 

DAINPRM

CTMBLT CONTROL STATMENTS

DASCHD

CONTROL-M SCHEDULING TABLE LIB

STEP6E

CALXML

CONTROL-M CALENDAR LIBRARY

STEP6F

CALXML

CONTROL-M CALENDAR LIBRARY

STEP7

DAXML

XML JOB DEFINITION FOR NON-MAINFRAME JOBS

STEP8

CALXML

CONTROL-M CALENDAR LIBRARY

STEP9

DAXML

XML JOB DEFINITION FOR MAINFRAME JOBS

STEP10

CALXML

 

START

 

XMLOUT1

XML JOB DEFINITION FOR NON-MAINFRAME JOBS

XMLOUT2

XML JOB DEFINITION FOR MAINFRAME JOBS

JOB3

 

 

STEP2

WORK

WORK LIBRARY

STEP3

DD IEBUPDTE

IEBUPDTE FORMATTED FILE OF ALL PROCESSED JCL MEMBERS

STEP4

DD SYSUT2

UPDATED JCL LIBRARY (PJCLCNV=Y only)

JOB4

 

STEP2

 

DADATA

DATA INPUT STATMENT LIBRARY

DALIBSYM

DNEST PROCEDURE OVERRIDE LIBRARY

Extract the Data from CA-7 Environment

Begin

  1. In the EXTRACT CONVERSION INPUT DATA panel, specify

    • a valid CA-7 LOGON Userid

    • the location of the CA-7 Initialization File statements and the CACCENV profile member

      If the CA-7 Cross-Platform Tracker (XTRK) for notification of file create/update actions is used at the site (for DSN requirement connections and/or DSN triggered by events), then do the following:

      1. If member CACCENV exists in the CA-7 PROFILE library, copy it to any test PDS. Otherwise, create an empty CACCENV member in the test PDS.

      2. Copy the file pointed to by the XEVENTS DD statement from the CA-7 XTRK procedure to the end of the newly created CACCENV member.

      3. Specify the above test PDS in the parameter 'CA-7 PROFILE LIBRARY CONTAINING MEMBER CACCENV' in the ICE EXTRACT CONVERSION INPUT DATA panel.

      If XTRK is not used and the CACCENV member is not in use at this site, then specify NULLFILE for the above ICE parameter

    Enter YES to save and continue. You will be prompted by a series of pop-up panels described below.

  2. In the SPECIFY CA-7 BASE CALENDARS panel, specify the names and years of CA-7 Base Calendars that will be converted. Specify the calendar names and years in the format which is acceptable by the CA-7 SASSBTRM PRINT,YEAR=yy,SCAL=xx statement. Initially the calendar list is empty, but you can enter as many calendars/years that you need to be converted. If the calendar is a multiyear calendar, then the calendar name must be repeated for each year that is required. Enter YES to save and continue.

  3. If CA-DRIVER is in use at the site, then in the SPECIFY CA-DRIVER PROCEDURE LIBRARIES panel, specify the CA-DRIVER Procedure libraries that need to be converted. Initially the library list is empty, but you can enter as many CA-DRIVER Procedure 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. In the next SPECIFY JCL LIBRARIES panel, specify the CA-7 JCL and, if you specified Y for the PNIBTSD default parameter (for more information, see Conversion Parameters), parameter-libraries (members containing Batch Terminal Input (BTI) statements) that need to be converted. Initially the library list is empty, but you can enter as many JCL and parameter 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.

  5. The SPECIFY JOB PREFIXES panel provides the option of creating multiple partial LJOB reports. This panel can be ignored if all the jobs in the CA-7 database can be included in a single LJOB report. However, if one LJOB report, which includes all the jobs, is too large (the CA-7 Batch Terminal Interface issues an Out of Space error message), then this panel can be used to create several smaller, partial reports. On each line of the LJOB PREFIXES field, the user enters a set of prefix elements separated by commas. Each element can be either a single prefix or a range of prefixes (separated by hyphens). Each line, which can contain as many elements as required, creates a single LJOB report. The user must ensure that the supplied prefixes or range of prefixes includes all the jobs in the CA-7 database. In addition, the user must ensure that the special characters are not left out.

    This step ensures that when multiple partial LJOB reports are produced, in subsequent conversion stages the resultant consolidated LJOB will be in sorted order by CA-7 jobname and will not contain duplicate job definitions, as required by the conversion tool.

  6. If a data extraction job already exists, you will be prompted as to whether you want to replace the existing copy. The data extraction job (CA7JOB0) is then displayed in the ISPF editor. If necessary, edit the job.

  7. Run the job in the environment where CA-7 is installed. This job utilizes the CA-7 Batch Terminal mechanism and might require several hours for processing, due to the manner in which CA-7 communicates with Batch Terminals.

  8. Verify that the job ran successfully.

Closure for Stage 1

Copy the compressed output file, prefix.TRS, which is generated by the job, to the conversion environment.

Stage 2. Schedule Definition Conversion

Overview of Definition Conversion Details

This section details the conversion of relevant CA-7 and CA-11 components into corresponding Control-M job scheduling definition parameters and AutoEdit parameters, and describes the unique Control-M conversion parameters that can be specified.

Set File Allocation for Conversion

Begin

  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. At this point you can choose to back up the current values or restore the most recently saved values of parameters, settings, and options for the set of files associated with the specified prefix. In the Backup/Restore field, enter one of the following values:

    • B: back up the current values for the extracted environment

    • R: restore to the most recently saved values

    • blank: continue with file allocations without performing a backup or a restore

    This backup/restore mechanism enables you to run multiple conversion sets in a single IOA environment. After backing up one conversion set and exiting this panel, you can re-enter the panel and work on a different set. At a later time, you can return to this panel, specify the appropriate file name prefix and restore values for the conversion set, and proceed from the last step performed.

    The following information is included in the backup/restore process:

    • Conversion options

    • Allocation attributes

    • Space allocations (from the Extraction and Conversion panels)

    • PARM values (from all panels)

    • Tables built (including BTERM, periodic base calendars, and the edited APPL list)

    • List of JCL and CA-DRIVER libs

  3. To complete the backup/restore process and/or file allocations, enter PF3 or END to save and Exit.

Extract the Package File

Begin

  1. Select the Extract the Package File step.

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

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

If the INITDECK file contains JCL statements that span more than one line, the REPJCL step will not be able to correctly modify the INITDECK JCL entries to the new names of the JCL files. You must manually edit the INITDECK file in the conversion environment.

Create Application List and Calendars

Begin

  1. In the CREATE APPLICATIONS LIST, CALENDARS LIBS AND ARFSET SCHED LIB panel, enter the maximum number of jobs in the CA-7 LJOB report. Enter YES to save and continue.

  2. In the NON-STANDARD (PERIODIC) BASE CALENDAR LIST panel specify the beginning/ending day of the month pairs and the calendar name/year data for all the CA-7 non-standard calendars. Enter YES to save and continue.

  3. If the job for creating the Application list and Calendars already exists, you will be prompted as to whether you want to replace the existing copy. The job (CA7JOB1) is then displayed in the ISPF editor. If necessary, edit the job.

  4. Run the job in the conversion environment.

  5. Verify that the job ran successfully.

Review and Modify Application List

An editor can be used to modify only the table names (columns 41 through 48), and the SCHDMOD CURRENT indicator. When editing, it is important to ensure that the table names remain unique, valid PDS member names.

For more information, see JOB2 - Create Control-M Tables, CMEM Rules, and XML Definitions.

Create CTM Scheduling Definition & XML

Begin

  1. In the CREATE CTM SCHEDULING TBLES, CMEM RULES, XML DEFS panel, enter the following information:

    • name of a Control-M table for standalone (adhoc) jobs

    • name of a Control-M datacenter for distributed jobs

    • name of a Control-M datacenter for mainframe jobs

    • Job class translation definitions

    • expected maximum number of lines in any SMART Table (A value that is too small will result in error message CTM689E during the conversion.)

    • maximum number of scheduling tables in the SMART Table library

    • whether the converted scheduling library will be created in SMART table format or not

    • the source for the User daily table names (SYSTEM/#APPL#/#GRP#/xxx)

    • 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

    Enter YES to save and continue.

  2. If the job for creating the Control-M tables, CMEM Rules, and XML definitions already exists, you will be prompted whether you want to replace the existing copy. The CA7JOB2 job is then displayed in the ISPF editor. If necessary, edit the job.

  3. Run the job in the conversion environment. Since approximately 1.5 KB of virtual storage above-the-line is required for each CA-7 job, you must ensure that this job is not limited by the amount of above-the-line storage available to it (such as when using the IEFUSI SMF exit).

  4. Verify that the job ran successfully.

Closure for Stage 2

Load the XML files to Control-M/EM to validate the conversion.

For more details, see step 6 in the procedure described in Post Step 3. Check Conversion Results.

Stage 3. JCL Conversion

Overview of JCL Conversion Details

This section details the conversion of relevant CA-7 and CA-11 components into corresponding Control-M job scheduling definition parameters and AutoEdit parameters, and describes the unique Control-M conversion parameters that can be specified.

The JCL conversion process is controlled by the PJCLCNV conversion option. When PJCLCNV is set to N, all the members in all JCL libraries specified in ICE are processed, whether or not they are referenced by jobs specified in the CA-7 LJOB report. In such a case, all the members are updated in-place (in the library in which they reside) and a message is issued only for those members that are modified.

When PJCLCNV is set to Y, only JCL members that correspond to jobs specified in the LJOB report are processed. An IEBUPDTE-formatted file that contains all the modified/copied members is created, and it is then used to create a single output JCL library. The original JCL libraries remain unchanged. For further details, see Conversion Parameters and Messages for descriptions of parameter PJCLCNV and message CTMCA707-09I (respectively).

In both cases, any members that reside in PDSs on SYSIN DD statements of JCL steps and execute a CA-7 utility are processed and converted in-place, depending on the setting of the PNIBTSD Conversion option.

For CA-Driver conversion (JOB4), when PJCLCNV=Y, the CA-Driver conversion in STEP4 will process (in-place) only the new JCL library produced in JOB3. All CA-Driver Procedure libraries are processed in STEP3 regardless of the setting of PJCLCNV.

Convert JCL Libraries

Begin

  1. In the BATCH TERMINAL DEFINITIONS panel, enter the batch terminal input (BTI) parameter definitions. For more information, see JOB3 - Convert JCL Members. Enter YES to save and continue.

  2. If the job for converting the JCL and BTI parameter libraries already exists, you will be prompted whether you want to replace the existing copy. The CA7JOB3 job is then 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.

Convert CA-DRIVER Procedures

Begin

  1. In the CONVERT CA-DRIVER PROCEDURES AND JCL LIBS panel, enter the following information:

    • the starting number for NSTnnnn members

    • the starting number for DATnnnn members

  2. Enter YES to save and continue.

  3. If the job for converting the CA-Driver PROCs and JCL libraries already exists, you will be prompted whether you want to replace the existing copy. The CA7JOB4 job is then displayed in the ISPF editor. If necessary, edit the job.

  4. Run the job in the conversion environment.

  5. Verify that the job ran successfully.

Closure for Stage 3

The CA-7 JCL and CA-Driver libraries are converted now to Control-M format. For the actual Control-M production operation, these libraries must be copied into the production environment.

Post-conversion Operations

Post Step 1. Customize Control-M and Install User Exits

Begin

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

    • Set the SCHPREVD parameter to Y to activate SAC parameters in Control-M job scheduling definitions.

      For jobs scheduled between midnight and the Control-M New Day time, SAC shifts these job’s scheduling criteria to the previous day to avoid date discrepancies. For more information, see New Day Processing and Schedule Scan.

    • Set the FORCERBC parameter to Y.

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

    • If the CA-7 NCF feature was in use or NJE jobs will later be added to the Control-M environment, set the ENHNJE parameter to Y.

    • If CA-7 #SCC special override statements were used in JCL, set the EXSTPRNG parameter to Y.

    • If you want to implement the Dynamic Tape Drive Quantity Adjustment feature, set the AUTOTAPE parameter to Y.

    • Set the ABNDTYP parameter in the CTRPARM member of the IOA PARM library to UABEND to prevent anomalous situations when Control-M/Restart fails with RC=8 (for example, when it detects a non-existing SHR dataset). Although the job might not restart at all, it will, by default, end OK (and show as green in Control-M/EM). The UABEND value prevents this when restart fails by issuing a U0008 return code instead, so that the jobs ends NOTOK.

    • Set the DUEINCHK parameter to Y.

  2. If you wish Control-M to imitate CA-7 submission processing (forcing the jobname to be identical to the JCL member name), you can optionally activate Control-M User Exit 2 (the job submission exit). This exit is supplied in the CTMX002Q member in the IOA SAMPEXIT library. For details regarding this user exit, see the CTMX002 member in the same library. If Exit 2 is currently in use, use the Roof exit 2, CTMX002@, to serialize the new functionality.

  3. For information about customizing Control-M/Restart, see 31. CA-11 U11RMS Step.

  4. Create a member in the CTM PARM library (pointed to by the DAGLOBAL DD statement) containing AutoEdit definitions corresponding to all valid CA-7 MAINID parameters values as specified in the CA-7 MAINIDS Initdeck Initialization File statement. For example, if the MAINID SY1 corresponds to the CPU whose System ID is MVSA, and SY6 corresponds to MVSB, then the following lines should be coded in this member:

    Copy 
    %%1=MVSA
    %%6=MVSB

    This member should then be specified in the AutoEdit Global Cache definition member (by default, this is member CACHLST in the CTM PARM library). For example, if the member you created is named AEVARS, the member CACHLST should contain (at minimum):

    Copy 
    %%RESOLVE ALLCACHE
    %%GLOBAL AEVARS

    To activate this new member, issue the following Control-M command:

    Copy 
    F controlm,AECACHE=RELOAD

    For more information on the CA-7 MAINID parameter, see 40. MAINID. For more information on the Control-M AutoEdit Cache facility, see the Control-M chapter in the INCONTROL for z/OS Administrator Guide.

  5. Create a member in the CTM PARM library (pointed to by the DAGLOBAL DD statement) containing the following AutoEdit definition:

    %%JOBCARD=jobcard-parameters

    This AutoEdit variable is used in forming JCL job statements (when invoking the CTMAPI utility as in-stream JCL) as follows:

    //jobname JOB %%JOBCARD

    Follow the instructions in step 4. above to make this member part of the AutoEdit Global Cache facility.

  6. To simulate LEADTM=99 functionality (see Appendix F, item #19 for details), you can optionally activate Control-M User Exit 1 (the job submission exit).

    This exit is supplied in the CTMX001Z member in the IOA SAMPEXIT library. For details regarding this user exit, see the CTMX001 member in the same library. If Exit 1 is currently in use, use the Roof exit 1, CTMX001R, to serialize the new functionality.

  7. To support certain CA-7 ARF functionality (as described in Automated Recovery Facility (ARF)), you must activate IOA User Exit 34 (the job submission exit). This exit is supplied in the IOAX034A member in the IOA SAMPEXIT library. For details regarding this user exit, see the IOAX034A member in the same library.

Post Step 2. Perform Final Adjustments

The following final adjustments must be performed.

Begin

  1. If a CMEM Rule table was built in the CMEM file created in JOB3, follow the instructions in the Control-M for z/OS User Guide.

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

  3. The CTMXRF Control-M utility may be run with the cross reference statement XRF=CAL, to produce a Calendar Name-Jobname cross reference report. This report can be used to determine whether the conversion has created any auxiliary calendars, and if so, the identity of any auxiliary calendars that have been created.

    You can replace any of the existing auxiliary calendars with basic scheduling criteria by means of the CTMTBUPD utility, which is described in the INCONTROL for z/OS Utilities Guide.

    For more information on the creation of auxiliary calendars, see

    In order to minimize the work of maintaining auxiliary calendars, BMC Software recommends that, wherever possible, you replace them with basic scheduling parameters and base calendars. To do this, use the Control-M CTMTBUPD utility. For more information on this utility, see the Control-M chapter of the INCONTROL for z/OS Utilities Guide.

    Suppose the following:

    • The SJ123456 calendar is defined in the DCAL parameter of the TAG1 Rule-Based Calendar in the XYZ SMART Table.

    • The SJ123456 calendar schedules the job every third working day of the month, which in the CA-7 Q1 base calendar is a Monday.

    • The CALPREF conversion parameter was set to CTMCAL. The CALPREF conversion parameter is described in Conversion Parameters.

    • The SWEEK Control-M installation parameter is set to MON.

    Replace the auxiliary calendar by means of the following CTMTBUPD utility control statements:

    Copy 
    SEL TBL XYZ,TAG=TAG1
    DCAL=CTMCALQ1
    DAYS=D3
    RELATION=A
    WDAYS=1
    ENDSEL

    Any auxiliary calendars that are not replaced must be extended to multi-year calendars as soon as possible.

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

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

  6. Copy the AutoEdit member.

    If you use the CA-DRIVER, copy the DAYMONTH member, which contains AutoEdit Global Variable definitions, from the conversion source library to the library specified in the DAGLOBAL DDstatement, which is defined in the Control-M monitor procedure. Carefully read the customization instructions in this source member, which instruct you to delete or uncomment certain lines.

    If you have set the SWEEK IOA Installation parameter to SUN, change the DAYMONTH member as follows:

    Copy 
    %%OUTDAY1=SUNDAY
    %%OUTDAY2=MONDAY
    %%OUTDAY3=TUESDAY
    %%OUTDAY4=WEDNESDAY
    %%OUTDAY5=THURSDAY
    %%OUTDAY6=FRIDAY
    %%OUTDAY0=SATURDAY

  7. The CTMXRF Control-M utility must be run with the cross reference statement XRF=LIB, to complete any Control-M DO FORCEJOB actions that may have been created by a CA-7 ARF issuance of a DEMAND command. The user should scan the CTMXRF report for libraries that are identified as FRC types. Each job within the tables of such libraries should be examined for an ON PFMST …. DOFORCEJOB. The table names within these DO FORCEJOB statements are all specified as '????????'. These question marks should be replaced with the actual table name in which the job appears. The table names can easily be determined from the CTMXRF utility using cross reference statement XRF=JOB.

Post Step 3. Check Conversion Results

Begin

  1. Export the XML files for the job schedule definitions and the calendars of both Control-M for z/OS jobs and calendars and Control-M for Distributed Systems jobs and calendars created by the conversion tool.

    The names of the required Control-Ms for distributed jobs and mainframe jobs that are specified in (ICE) Minor Step 12 (Create CTM scheduling definition & XML) of Stage 2 (Schedule Definition Conversion) must be the same names that will be used in Step 3, where the Control-Ms are defined using the Control-M Configuration Manager.

    The values entered in the CONTROL-M NAME FOR DISTRIBUTED JOBS and the CONTROL-M NAME FOR MAINFRAME JOBS fields are used for the DATACENTER parameter values used as input to the CTMTLB utility.

    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. Start up the Control-M Monitor and IOAGATE on the mainframe for Control-M for z/OS jobs. Start up the Control-M Server and its corresponding Gateway for Control-M for Distributed Systems jobs.

    Verify that all are connected and working properly before continuing.

  3. Define all the 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.

  4. Import the exported Calendars to all the 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.

  5. Define the Global Conditions Server (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.

  6. Run the cleanup-at-job-level-only.py script to clean job conditions in cases where you have multiple jobs that await a single condition.

    Skip this step if parameter FLCLEAN is set to Y. For more information about the FLCLEAN parameter, see Conversion Parameters.

    The cleanup-at-job-level-only.py script is provided in the tools/CA7 directory of the Control-M Conversion Tool for distributed systems.

    Use the following command line:

    Copy 
    cleanup-at-job-level-only.py -m <mf_inputfile> -d <ds_inputfile> -o <outputdir>

    In this command, specify the following input parameters:

    • mf_inputfile — XML file of schedule definitions for mainframe jobs

    • ds_inputfile — XML file of schedule definitions for Distributed System jobs

    • outputdir — path to a directory in which to save the output files

    The script takes the 2 job schedule definition XML files that were copied from the mainframe, and creates a new, modified copy of each XML file in the specified directory. Ensure that you use the modified (output) XML files in the next step.

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

    1. Save the XML draft files in a folder accessible to the Planning domain.

    2. Open the Planning domain.

    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 checking in your changes to the database.

    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 the Planning domain, 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 the Planning domain in Control-M on a specific date (as many times and various days as required), and compare the predicted flow with the current scheduling tool reports.

  12. Make user and global auto-edit variables accessible to Distributed jobs.

    To activate support for user CA-7 Global variables and limited support for system CA-7 Global variables in ARGS of distributed jobs definitions:

    1. Copy member CNVCA7IN from the IOA SAMPLE library together with file prefix.MEMSIM (created in JOB4) into a text file in the Control-M Server file system.

      Before doing so, read carefully the instructions contained within member CNVCA7IN.

    2. Issue the following Control-M command:

      Copy 
      ctmvar -POOL load -POOLNAME ctm_ca7_globalvar_pool -FROM <filename>

      where <filename> is the copied file above.

      This command loads all the CA-7 variables into the named variable pool, which become accessible to the job via the %%POOLSYM=ctm_ca7_globalvar_pool SETVAR auto-edit variable in the job definition.

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 file pointed to by the DADAILY DD statement.

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.