Conversion Steps

Overview of the Conversion Tool Operation

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

Pre-conversion Planning and Activities
- Review system exits required in the Control-M environment.
- Ensure that all personnel involved in the conversion process have the necessary security privileges and authorizations.
Automated ICE Operations
Post-conversion Operations

BMC 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 and Activities

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

Review any system or ASG ZEKE exits that perform functions that must be implemented in the Control-M environment.
Verify 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.
Verify that the DATE parameter of the ZEKE SSSIOPT macro is set to match the equivalent value of the Control-M DATETYP parameter (in the IOAPARM member of the IOA PARM library) as follows:
- DATE=MMDD <==> DATETYP=A
- DATE=DDMM <==> DATETYP=W
Set optional wishes WM2367 and WM2548 in the IOADFLTL member of the IOA PARM library for the MAXWAIT and RETRO default parameter values to be used by the CTMBLT utility when creating scheduling definitions.

Automated ICE Operations

Stage 0. Set Conversion Defaults

In the SET ZEKE CONVERSION DEFAULTS OPTIONS panel default values are provided for the conversion parameters. In the panel, the parameters are arranged in groups as indicated in Table 3 below. New values can be specified or the default values accepted. When this stage is completed, the ZEKDEF defaults member in the INSTWORK ICE library is updated with the new values. Short descriptions of the options are provided in this panel. 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.

Table 3 ZEKDEF Conversion Parameters

Parameter Group	Parameter
ZEKE FUNCTIONALITY SETTINGS	REL
	UCMDPRC
	ZEKESET
CONTROL-M FUNCTIONALITY SETTINGS	DSDOC
	FRMCLS
	JOBCARD
	INIT
	RELEASE
	TOCLS
SHOUT PARAMETERS SETTINGS	DEST
	SHOUTL
	SHOUTN
	SHOUTT
	SHOUTX
CONVERSION FUNCTIONALITY SETTINGS	COMMENT
	JOBSLSH
	MAYBEPF
	OWNER
	OWNLEN
	VARLIB
CONVERSION SIZES SETTINGS	LINMAX
CONVERSION SIZES SETTINGS	MAXEOG
PARAMETER DESCRIPTION	LINMAX

Stage 1. Data Extraction

Overview of Data Extraction

In this stage, the ASG ZEKE definitions, reports, and libraries, which 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 ASG ZEKE data and want to use the ASG ZEKE 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 ASG ZEKE environment data and generating a scheduling data package.

Using Your Own Data to Process the Conversion

Choose step 4 and enter your reports file name prefix, (PF3 save and exit).
Choose step 5.
1. Accept the default value of the Zeke Sub-System name. Press Y to continue.
2. If you have JCL libraries enter the names. Press Y to continue.
  The following ASG ZEKE reports must be sequential files with the following suffixes:
  - EVENTS: the ASG ZEKE Main EVENTS report containing scheduling and job dependency information.
  - EVENTS.PART2: the ASG ZEKE Main EVENTS report containing scheduling and job dependency information (Part 2).
  - CALENDAR: the ASG ZEKE Calendar report.
  - CMDS: the ASG ZEKE commands and message report.
  - DOC: the ASG ZEKE event documentation report.
  - VARIABLE: the ASG ZEKE JCL Variable report.
  - LISTJCL: the ASG ZEKE report listing the JCL members in the ZEKE Catalog.
  - DEAC: the ASG ZEKE event deactivation report.
Continue with the conversion steps. When you reach step 9, answer N to the question and then continue with step 10, described in Create CTM Scheduling & Calendars.

Set File Allocation for Data Extraction

In the SET FILE ALLOCATION DEFAULTS FOR DATA EXTRACTION panel, specify values that will be used in the data extraction stage.

Specify a valid file name prefix that will be used for the ASG ZEKE reports that are created by JOB0 or used by the existing ASG ZEKE reports. In either case, the prefix is required for the conversion process.
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 MANAGEMENT CLASS.
For the SPACE ALLOCATION PARAMETERS specify a new value or accept the default value for the ZEKE Proc LIB sequential FILE.

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

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

Table 4 Fixing SB37 Problems in the Conversion

JOB	STEP	DD	Fields on the Screen with the Space Information
JOB0	Z1	SYSPRINT	ZEKE EVENTS file
	Z2	SYSPRINT	ZEKE EVENTS Part 2 file
	Z3	SYSPRINT	ZEKE DOC file
	Z4	SYSPRINT	ZEKE CALENDAR file
	Z5	SYSPRINT	ZEKE VARIABLE file
	Z6	SYSPRINT	ZEKE CMDS file
	Z7	SYSPRINT	ZEKE LISTJCL file
	Z8	SYSPRINT	ZEKE EVENTS DEAC file
JOB1	STEP2	EOGTBL	END OF GROUP FILE
JOB2	STEP2	DAZJCLO	JCL LIBRARY CREATED FROM LISTJCL
	STEP3	DACAL	IOA CALENDAR LIBRARY
		DABCLIN	CTMBCL UTILITY STATEMENTS
		DAHOLID	CALENDAR/HOLIDAY NAME FILE
	STEP4	DADOC	CTM DOCUMENTATION LIBRARY
		DAJCL	CTM JCL LIBRARY FOR SCOM, ZCOM, MSG
		SORTIN	CTMBLT SCHEDULE TABLES DEFINITIONS
		DABLTPRM	SORTED CTMBLT SCHEDULE DEFINITIONS
		DADAILY	CTM DAILY PROCESS LIST
		DAZINFO	ZEKE EVENT INFORMATION FILE
	STEP4A	SYSUT2	CONTROL-O RULES MEMBER (CMEM)
	STEP5	DASCHD	CTM SCHEDULING TABLES LIBRARY
JOB3	STEP2	DAXML	XML FILE for DISTRIBUTED JOBS DEFINITIONS
	STEP3	DAXML	XML FILE for MAINFRAME JOBS DEFINITIONS
	STEP4	XMLOUT1	XML FILE for DISTRIBUTED JOBS DEFINITIONS
	STEP4	XMLOUT2	XML FILE for MAINFRAME JOBS DEFINITIONS
	STEP5	CALXML	XML FILE for DISTRIBUTED CALENDARS
	STEP5	CALXML	XML FILE for DISTRIBUTED CALENDARS
	STEP6	CALXML	XML FILE CONTAINING MAINFRAME CALENDARS

Extract the Data from ASG ZEKE Environment

In the EXTRACT CONVERSION INPUT DATA panel, specify file names or values for the following:
- Set the value of the Zeke Sub-System name (default SSSI). Press Y to continue.
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.
In the SPECIFY JCL LIBRARIES panel, specify the JCL and SCRIPT libraries that need to be converted. If the Universal command product is in use at your site or the PNIBTSD conversion option (see Conversion Parameters) is set to Y, then all libraries that contain Universal command scripts and non-instream Zeke utility commands must be included in this list. 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.

For CA-LIBRARIAN or CA-PANVALET libraries, the utilities supplied by CA-LIBRARIAN or CA-PANVALET must be used to create and copy the production JCL libraries into PDS libraries, which can then be specified above.
If the data extraction job already exists, you will be prompted if you want to replace the existing copy. The job is then displayed in the ISPF editor. If necessary, edit the job.
Run the job in the environment where ASG ZEKE is installed.
Verify that the job ran successfully.

For more information, see JOB0: Produce the ZEKE Reports.

Closure for Stage 1

In this stage, the ASG ZEKE scheduling definitions, 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 test environment.

Stage 2. Conversion

Overview of the Conversion Stage

The scheduling data package, created in the previous stage, is copied to the conversion environment. The ASG ZEKE job scheduling reports and calendars, and the ASG ZEKE 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 by Control-M and loaded into a workspace.

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 Control-M Calendar and schedule definition libraries (and if necessary, adjusting the results).
Running a job that creates Control-M XML draft files (and if necessary, adjusting the results).
Converting the JCL libraries.

Set File Allocation for Conversion

In the SET FILE ALLOCATION FOR CONVERSION panel, specify values that will be used in the conversion stages that follow.

Specify a valid file name prefix that will be used for the Control-M conversion results. The prefix is required for the conversion process.
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 MANAGEMENT CLASS.
Under the Create CTM Scheduling Definition And Calendars section, specify new values for the space allocation parameters or accept the default values for the following:
- CTMBCL utility statements.
- CALENDAR/HOLIDAY name file.
- Control-M DOCUMENTATION library.
- IOA CALENDAR library.
- Control-M DAILY process list.
- Control-O rules file.
- CTMBLT SCHEDULE tables definitions.
- SORTED CTMBLT schedule definitions.
- Control-M SCHEDULING tables library.
- ZEKE EVENT info file.
- Control-M JCL Library for SCOM,ZCOM,MSG.
- END OF GROUP file.
- JCL LIB created from ZEKE LISTJCL.
Under the Create CTM XML section, specify new values for the space allocation parameters or accept the default values for the XML files containing the following:
- Distributed jobs definitions.
- Mainframe job definitions.
- Distributed calendars.
- Mainframe calendars.
Press PF3 to save and continue.

Extract the Package File

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.
The jobs for extracting the package file run automatically in the conversion environment.
Confirm to continue, when prompted after the metadata extraction job, before the job that extracts the other files.
Verify that the jobs ran successfully.

Create CTM Scheduling & Calendars

Select the Create CTM scheduling & calendars step.
Fill the table of REMOTEIDs and the corresponding condition name prefix.

The REMOTEIDs are the distributed remote system ids which are specified in ZEKE 'WHEN' clauses EOJ, AEOJ or BOJ as objects of the 'AT' parameter. These names must be 1-8 characters long.

For each REMOTEID, the associated condition name prefix will used as the 'IN' condition prefix for all successor jobs triggered by the distributed remote job. The prefix must be 1-2 characters long, and must not contain the character '+' (which is used for manual conditions) or the default prefix specified for the MAYBEPF in the Conversion Functionality Settings section of the 'SET ZEKE CONVERSION DEFAULT OPTIONS' step.

If your site does not use any remote system ids, leave the table empty.

Enter YES to save and continue.
Fill the table of ZEKE SYSTEM ID to IOA/Control-M corresponding CPU IDS.

The SYSTEM IDs are the 1−8 character ZEKE system IDs.

The CPU ID is the CPU ID corresponding to the specified ZEKE system.

Enter YES to save and continue.
If the job for creating the Control-M Calendar and table libraries already exists, you will be prompted if you want to replace the existing copy. The job is then displayed in the ISPF editor. If necessary, edit the job. When editing, it is important to ensure that the table names remain unique, valid PDS member names.
Run the job in the conversion environment.
Verify that the job ran successfully.

For more information, see JOB2: Create Libraries, Including the Control-O Rules Library.

Create CTM XML

Select the Create CTM XML step.
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 source for table user daily name (SYSTEM/#APPL#/#GRP#/XXX/blank).
- 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.
If the job for creating the XML definitions for jobs and calendars already exists, you will be prompted if you want to replace the existing copy. The job is then displayed in the ISPF editor. If necessary, edit the job.
Run the job in the conversion environment.
Verify that the job ran successfully.

Convert JCL Libraries

To run the converted jobs on Control-M for z/OS, the ASG ZEKE JCL libraries and scripts are made compatible to Control-M.

Select the Convert JCL Libraries step.
If the job for converting the JCL members to Control-M format already exists, you will be prompted if you want to replace the existing copy. The job is then displayed in the ISPF editor. If necessary, edit the job.
Run the job in the conversion environment.
Verify that the job ran successfully.

For more information, see JOB4: Convert JCL Members.

Post-conversion Operations

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

If a Control-O Rules member was created in JOB2 (output library CMEM), use this library as a Control-O Rules library or copy the member to a site-defined Control-O Rules library and follow the instructions for managing the Control-O Rule Definition facility, as discussed in the Control-O User Guide.
Create or copy the CTZMSET procedure, as described in CTMZSET: Invoke IOATEST, IOAAPI, IOACND, CTMRELRS, and CTMAPI Services.
Verify that all the JCL libraries specified in JOB4: Convert JCL Members are concatenated in member IOADSN in the IOA IOAENV library (or member IOADSNL in the IOA PARM library) using 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. In addition, the Control-M monitor procedure should also include DD statements for JCL libraries containing jobs whose job names do not match the JCL member name of the job it executes. For more information, see 34. JCL SOURCE.
The Table Definition file and the Sorted Table Definition file are no longer necessary and can be deleted.
In the CTMPARM member in the IOA PARM library, set the following parameters:
- SCHPREVD to Y
- EMPTYTBL to Y
- TBLDELJB to O
- TBLRECHK (see below)
The SCHPREVD parameter causes jobs to shift to the previous day to avoid date discrepancies. This parameter is only operative when the SAC Control-M job scheduling parameter is specified. For more information, see The 48-hour Clock and New Day Processing.

The TBLDELJB parameter determines whether deletion of a job inside a SMART Table before it ran (that is, in Wait Schedule status) causes the SMART Table Entity itself to end NOTOK. Its value should be set to O so that Control-M does not take into consideration jobs that were deleted before execution when it marks how the SMART Table Entity has ended.

Before selecting for submission a job belonging to a SMART table, a decision must be made whether to re-check the SMART table parameters, such as IN conditions. The decision is based on the TBLRECHK parameter. TBLRECHK should be set depending on how the ZEKE system generation parameter REMOVDQ is set. If REMOVDQ is set to YES, then TBLRECHK should be set to Y which causes the SMART table parameters to be checked before checking the job parameters, even if the SMART table is already Active. If something prevents the job from running (for example, if an IN condition of the SMART table is not met), even if the SMART table is already Active, the job is not selected.
Install User Exit 1, the ordering exit, to mimic the behavior of ZEKE in respect to Control-M Maybe jobs. This exit is supplied in member CTMX001Z in the IOA SAMPEXIT library. The exit provides the functionality of the ZEKE WEOJ parameter, which enables Control-M to dynamically process Maybe jobs.

This exit can be tailored to local requirements. Read the comments in the CTMX001Z member carefully to determine whether this functionality is desired. For additional details regarding this exit, see the CTMX001 member in the IOA SAMPEXIT library.

If Exit 1 is currently being used, use the roof exit, CTMX001R, which allows multiple exits to be invoked serially.

Post-step 2. Perform Final Adjustments

The following final adjustments must be performed:

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 IOA IOACND utility. For more information on the IOACND utility, see the INCONTROL for z/OS Utilities Guide.
If CA-LIBRARIAN or CA-PANVALET libraries were converted to partitioned data sets in Stage1 above, they can be reconverted back to CA-LIBRARIAN or CA-PANVALET format at this point.
Review all ASG ZEKE system exits (if any). Remove or modify such exits as appropriate.
Copy and rename member CNVZEKIN from the IOA SAMPLE to the library specified by the VARLIB conversion option, as described in Conversion Parameters. This member contains the translation of ZEKE system variables to Control-M AutoEdit format and should be renamed as DAYMONTH.

Post-step 3. Configure Control-M/EM and Check Conversion Results

Export the XML scripts for the job schedule definitions of both Control-M for z/OS jobs and Control-M for Distributed Systems jobs created in the conversion process using the deftable utility described in the Control-M Utility Guide.

The names of the required Control-Ms for distributed jobs and mainframe jobs that are specified in Create CTM XML of Stage 2. Conversion must be the same names that will be used below, in Step 4 of this procedure, 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.
Export the XML scripts for the calendars of both Control-M for z/OS and Control-M for Distributed Systems calendars created in the conversion process using the defcal utility described in the Control-M Utility Guide.

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.
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.
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.
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.
Define the GCS distribution list.

In Control-M, in the Tools domain choose Global Condition Prefixes. The Global Conditions Prefixes tab opens. Add the prefixes that were specified in the input file for JOB2 STEP6. Set the "From" and the "To" according to the names that were specified in ICE and placed in the generated JOB2.

This procedure must be performed after the Control-M servers are already defined.
Load each XML file to Control-M.

For more information, see the subtopics under the Using Workload Automation->Planning->Workspaces->Import/Export topic in the Control-M User Guide.

Review any error messages, and resolve them. 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.
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.
Define the Forecast User-Daily settings for the Control-M for z/OS folders in the Forecast domain. For more details, see the Control-M User Guide.
Run Control-M/Forecast for the Control-M or folder, 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. Alternately, the Plan (P) option of the Job List screen can be used to show a calendar of the days a job is scheduled or use the batch utility CTMRPLN to create a multi-year plan report for all jobs.
Load Forecast from the Control-M Planning Domain on a specific date (as many times and various days as required), and compare the predicted flow with the current scheduling tool reports. Alternatively you can use the Graphic Job Flow option, as displayed in Screen 2.G, to view the job flow of any of the ZEKE applications as they appear in Control-M or use the batch utility CTMRFLW to display a job flow report of jobs in scheduling tables or in the AJF.

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 JOB2 in the DAILY file.

Order the IOA 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.