Conversion Details

This section includes the following topics:

• Overview of Conversion Details

• Component Conversion Summary

• Component Conversion Detail

  • 1. EVENT NUMBR

  • 2. EVNT TYPE

  • 3. SCHED TIME, EARLY TIME

  • 4. LATE TIME

  • 5. CALID

  • 6. APP

  • 7. GRP ID

  • 8. USERID

  • 9. EVENT NAME

  • 10. JOB NAME

  • 11. MUST END

  • 12. NOT AFTER

  • 13. DSP PRI

  • 14. TPS

  • 15. DCAL, WCAL, CONFCAL

  • 16. WDAYS

  • 17. NOT

  • 18. REFEVENT

  • 19. NWDAY

  • 20. RETAIN

  • 21. RESOURCE

  • 22. WHEN

  • 23. NOTDURING

  • 24. COND CODE

  • 25. $ VARIABLES

  • 26. SPECIAL NAMES VARIABLES

  • 27. ZEKESET PROGRAM

  • 28. ZEKESET SET VAR

  • 29. ZEKE-CTL

  • 30. SCOM

  • 31. ZCOM

  • 32. COMM and WORK

  • 33. MSG

  • 34. JCL SOURCE

  • 35. CLASS

  • 36. AVGDUR

  • 37. OPR OK

  • 38. SYSTEM

  • 39. TIMES

  • 40. DSPCH FREQ

  • 41. REQUEST

  • 42. CDATE

  • 43. FREQCALC

  • 44. DATE

  • 45. EVERY

  • 46. CONTROL

  • 47. EXPIRE

  • 48. PLATFORM

  • 49. TARGET

  • 50. VAR and ?VAR in SET clauses

  • 51. Oasis Variables

  • 52. OR

  • 53. LATE END

• Unique Control-M Parameters

  • DO SYSOUT

  • RESOURCE

  • Control-M/Restart

Overview of Conversion Details

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

Component Conversion Summary

The conversion tables on the following pages list ZEKE components and the corresponding Control-M parameters to which they are converted.

Table 9 Components of ZEKE List Events Reports

Table 10 ZEKE OCCURS Clause Keywords

Table 11 ZEKE WHEN/SET Clause Keywords

Table 12 Components of the ZEKE JCL Variables and Steps

Table 13 ZEKE Command and Message Event Types

Component Conversion Detail

1. EVENT NUMBR

Every ZEKE event is assigned a unique event number. The conversion tool uses this event number to form a job name (MEMNAME) for COMM, WORK, MSG, SCOM, and ZCOM events that do not have job names associated with them.

The first two characters of the event type are concatenated to a zero-padded 6-character event number. For example, the job name created for an SCOM event with event number 100 is SC000100.

2. EVNT TYPE

ZEKE events define actions that occur within a computer installation. There are two categories of ZEKE events–System events and Work Center Events.

System events are divided into the following types:

Table 14 Types of ZEKE System Event

Work Center, or COMM or WORK, events describe actions over which ZEKE has no control. These tasks require manual intervention.

The conversion tool supports JOB, MSG, SCOM, ZCOM, COMM, and WORK type events.

For more information concerning how the conversion tool forms job names for COMM, WORK, MSG, SCOM and ZCOM type events, see the preceding item, 1. EVENT NUMBR.

3. SCHED TIME, EARLY TIME

The ZEKE SCHED TIME is the normal schedule time for the event. The ZEKE EARLY TIME is the earliest time that an event can be dispatched.

• If an EARLY TIME is defined for an event, the conversion tool uses that time in the TIME FROM Control-M scheduling definition parameter to specify the lower time limit for job submission.

• If there is no EARLY TIME, the SCHED TIME is used.

• If no EARLY TIME is specified and the SCHED TIME is 00:00, the TIME FROM Control-M parameter is left blank.

• When the ZEKE SCHED TIME or EARLY TIME is greater than 24:00, the conversion tool subtracts 24 hours from this time to ensure that the job is submitted on the proper day and at the proper time.

• The Control-M SAC and FROM TIME DAYS offset parameters are set, if necessary. For more information, see The 48-hour Clock and New Day Processing.

4. LATE TIME

The ZEKE LATE TIME is the time at which an event is considered late if it has not been dispatched. If the event is not dispatched by this time, a message is issued to the console.

The conversion tool uses the ZEKE LATE TIME to set a SHOUT WHEN LATESUB Control-M message to indicate that the job is late when this time has passed. For more information, see "SHOUTL" in Conversion Parameters.

The SHOUT TIME DAYS offset may also be set to +001, when necessary. For more information, see The 48-hour Clock and New Day Processing.

5. CALID

ZEKE events are associated with a ZEKE calendar. The conversion tool assigns the ZEKE calendar ID, when required by the scheduling logic, to one or more of the DCAL, WCAL, and CONFCAL Control-M scheduling parameters.

However, when the OCCURS clause of an event contains keywords that cause the conversion tool to create additional calendars, such as HOLIDAYS or WEEKENDS, the IOABLCAL utility creates a combined calendar, and this new calendar name is used in the appropriate Control-M parameter. For more information, see Calendars.

6. APP

The ZEKE APP field identifies the application of which the event is a part.

The conversion tool creates the APPL Control-M parameter from the ZEKE APP field. The APPL Control-M parameter is used to supply a common descriptive name to a set of related groups of jobs.

In addition, the APP field may be used to form the full Control-M Table name or first five characters of the Control-M Table name. For more information, see "GROUPBY" in Conversion Parameters.

The APP field may also be used to create the OWNER Control-M parameter. For more information, see "OWNER" in Conversion Parameters.

7. GRP ID

The ZEKE GRP ID field identifies the group of which the event is a part. The conversion tool creates the GROUP Control-M parameter from the ZEKE GRP ID field. In addition, the GRP ID field may be used to form the Control-M Table. For more information, see "GROUPBY" in Conversion Parameters.

The GRP ID field may also be used to create the OWNER Control-M parameter. For more information, see "OWNER" in Conversion Parameters.

8. USERID

The ZEKE USERID field identifies the person who is responsible for the event. The conversion tool can create the OWNER Control-M field from the ZEKE USERID field. For more information, see "OWNER" in Conversion Parameters.

The ZEKE USERID field may also be used in creating the Control-M Table name. For more information, see "GROUPBY" in Conversion Parameters.

9. EVENT NAME

The ZEKE EVENT NAME identifies the event. End of Event (EOE) and End of Group ((W)EOG) WHEN conditions use the EVENT NAME, as described in 22. WHEN.

The conversion tool uses the EVENT NAME as the first 12 characters of the DESC Control-M parameter so that the original event of each Control-M job is identifiable.

The EVENT NAME field can also be used to create the OWNER Control-M parameter. For more information, see "OWNER" in Conversion Parameters.

In addition, the EVENT NAME field can be used to form the Control-M Table name of the Control-M Table name. For more information, see "GROUPBY" in Conversion Parameters.

10. JOB NAME

The ZEKE JOB NAME is the same as the job name entered on the MVS job card for JOB type events and is used by ZEKE to track the event during the duration of its life.

The conversion tool creates the MEMNAME Control-M parameter from the ZEKE JOB NAME field.

For job-naming conventions in relation to non-JOB type events, see 1. EVENT NUMBR.

When the ZEKE JOBNAME is not the same as the JCL member name, see 34. JCL SOURCE.

The JOB NAME field may also be used to create the OWNER Control-M parameter. For more information, see "OWNER" in Conversion Parameters.

11. MUST END

The ZEKE MUST END field is the time by which the event must complete. Before an event is dispatched, ZEKE adds the average duration and the current system time, and compares the result to this field. If the MUST END time is less than the calculated time, the event is removed from the dispatch queue and an operator message is issued.

The conversion tool determines a value for the DUE OUT Control-M parameter according to the value of the MUST END field. The conversion tool also adds a SHOUT WHEN LATESUB message. The Control-M monitor uses the calculated DUE IN time of the job to determine if the job is submitted on time, that is, if it will finish by the DUE OUT time of the job.

The DUE OUT DAYS offset and SHOUT TIME DAYS offset may also be set to +001, when necessary. For more information, see The 48-hour Clock and New Day Processing.

12. NOT AFTER

The ZEKE NOT AFTER field is the time after which an event cannot be dispatched. If the NOT AFTER time is earlier than the system time, the event is removed from the dispatch queue and an operator message is issued.

The conversion tool creates the TIME UNTIL Control-M parameter from the NOT AFTER time to indicate that the job cannot be submitted after this time.

The TIME UNTIL offset and may also be set to +001, when necessary. For more information, The 48-hour Clock and New Day Processing.

13. DSP PRI

The ZEKE DSP PRI field is used to assign a dispatch priority number to the event. The highest priority is 1. The lowest is 99. The default is 50.

The conversion tool creates the PRIORITY Control-M parameter by subtracting the ZEKE DSP PRI field from 100, because the Control-M PRIORITY is in the reverse order: 1 is low, 99 is high.

When ZEKE resources must be held for a job until its full resource requirements have been allocated, the conversion tool sets the job's PRIORITY to '*' instead, making the job into a critical path job so that the job's resources are treated in a similar manner.

14. TPS

The ZEKE TPS field specifies the number of tape drives required by the job. The job is dispatched only when the specified number of drives is free.

Control-M handles tape drive resources as Quantitative resources. The RESOURCE Control-M job scheduling definition parameter specifies the resource name and the quantity used by a job.

The conversion tool uses the resource name TAPE to represent the ZEKE tape drives. The quantity is obtained from the TPS field.

Add the TAPE resource to the Control-M Resource file with a quantity corresponding to the maximum number of the installation's tapes drives.

You may want to implement the Dynamic Tape Drive Quantity Adjustment feature to automate tape drive handling, by setting the AUTOTAPE parameter in the CTMPARM member of the IOA PARM library to Y. For more information on the AUTOTAPE parameter, see the Control-M for z/OS User Guide.

15. DCAL, WCAL, CONFCAL

Several ZEKE OCCURS clause keywords cause the conversion to create and utilize calendars. Frequently these calendars must also be combined. The conversion tool combines them into one calendar, CALnnnnn, and places this calendar name in the DCAL Control-M parameter.

In cases where the ZEKE scheduling criteria is +/- nn [W]DAYS, the Control-M CONFCAL calendar is set as follows:

• When the DAYS option is in use, the CONFCAL calendar is set to ALLDAYS.

• When the WDAYS option is in use, the calendar specified in the ZEKE event is coded in the CONFCAL parameter.

• When the CALENDAR clause is specified in combination with a DATE clause, then the calendar is coded in the CONFCAL parameter.

For more information, see Calendars.

16. WDAYS

The setting of the WDAYS Control-M parameter depends on the setting of the SWEEK IOA Installation Parameter. The illustrations in Table 10 in Component Conversion Summary, all assume that the SWEEK parameter is set to MON. If the SWEEK parameter is set to SUN, add 1 (modulo 7) to all WDAYS or Dn specifications.

17. NOT

The NOT keyword is supported with the following OCCURS keywords:

• (W)SUNDAY-(W)SATURDAY

• JANUARY-DECEMBER

• WDAYW

• DAY

• WDAY

• (W)EOM

• DATE

• HOLIDAYS

• HOL/WEEK

• CALENDAR cal

• MONTH.n

• REFEVENT

• WORKDAYS

• WORKDAY EQ n

• WEEKENDS

• SUNDAY.n - SATURDAY.n

• SUNDAY.L - SATURDAY.L

When the OCCURS keyword is converted to a WDAYS Control-M parameter, NOT has the effect of placing a minus sign in front of the value. For example NOT DAY.2 is converted to DAYS=-2.

The "NOT (CALENDAR cal)" criteria, where cal is a SPECIAL Zeke calendar, is converted to the $HLWKnnn negative calendar, derived from cal.

"NOT month" is converted by specifying every month except the month in the NOT clause. For example, NOT JUNE or NOT MONTH.6 is converted to MONTHS=1-5, 7-12.

"NOT REFEVENT nnnnn" is supported only when the REFEVT conversion parameter is set to CAL.

"NOT WORKDAYS" scheduling criteria is supported by creating a DCAL or WCAL holiday calendar ($HLWKnnn).

"NOT day-name.x" is converted to an Exclude RBC whose name is day-name.x. In such a case, the RBC RELATIONSHIP parameter is set to A (and).

"DAILY AND NOT day-name" is converted the same as NOT day-name with the addition of the calendar WCAL=ALLDAYS.

The NOT keyword is also supported in simple compound NOT expressions, such as NOT (xxx OR yyy OR zzz), but not in complex compound expressions, such as NOT ((xxx OR yyy) AND zzz).

18. REFEVENT

When a REFEVENT {nnnnn|event-name} is specified in the OCCURS clause of an event and the REFEVT conversion parameter is set to BASIC, the conversion tool searches through the ZEKE database for event {nnnnn|event-name} and converts its OCCURS clause keywords as if they were the keywords found on the event in question. When the REFEVT conversion parameter is set to CAL, the conversion tool creates a calendar name of the form RFxnnnnn and places it into the Control-M DCAL parameter. In such a situation, x=N or 0, depending on whether the REFEVENT field is preceded by the NOT operator; and nnnnn is the event number. It is your responsibility to actually create the calendar, using the IOA Calendar facility (Screen 8). Only one REFEVENT for each OCCURS clause is supported when the REFEVT conversion parameter is set to BASIC. Nested REFEVENT statements are supported.

19. NWDAY

The ZEKE NWDAY field specifies how to schedule an event on non-workdays.

The meaning of the ZEKE codes is explained in the following table.

Table 15 Codes in ZEKE NWDAY Field

When a job fails confirmation for scheduling on a given day, because the day is not a working day in the CONFCAL calendar, the SHIFT Control-M parameter determines if and when the job will be alternatively scheduled.

The conversion tool translates the ZEKE NWDAY codes to a SHIFT Control-M value as follows:

Table 16 Conversion of ZEKE NWDAY Codes

20. RETAIN

The ZEKE RETAIN field indicates whether ZEKE must retain an event if it is not dispatched on the scheduled date.

The MAXWAIT Control-M parameter specifies the number of extra days a job must wait to be executed in the Active Jobs file, after which the job is disregarded. When the value in the ZEKE RETAIN field is N, MAXWAIT is set to 0. When the value in the RETAIN field is Y, the MAXWAIT value is taken from WM2367 (see member IOADFLT in the IOA IOAENV library).

21. RESOURCE

The ZEKE Resource Control screen is used to define resource usage by event and to serialize the use of critical resources.

The CONTROL Control-M job scheduling definition parameter is used to control all job resource sharing. The conversion tool converts ZEKE Resource Controls by specifying the first 20 bytes of the ZEKE Resource Name in the CONTROL Control-M parameter, using the Shared/Exclusive ZEKE resource mode.

When ZEKE resources must be held for a job until its full resource requirements have been allocated, and the resource count is more than 1, then the conversion tool converts the resource to a Control-M Quantitative RESOURCE rather than a CONTROL resource, and uses the ZEKE resource count as the Control-M quantity for the RESOURCE. For further instructions and information when this occurs, see Post-step 3. Configure Control-M/EM and Check Conversion Results and 13. DSP PRI.

In either case, whether the resource is converted to a Quantitative RESOURCE or a CONTROL resource, if the ZEKE resource AT FAIL attribute specifies that the resource should be kept (rather than released) if the job fails, the conversion adds the K (keep) onFail attribute to the resource.

22. WHEN

The ZEKE WHEN clause can specify various types of prerequisite conditions. Each type causes the conversion tool to create corresponding IN or OUT or ON PGMST ... DO COND Control-M parameter definitions, as described below. The IN conditions are placed in the corresponding successor (to) jobs and the OUT and ON PGMST … DO COND statements are placed in the corresponding predecessor (from) jobs or SMART table entities. In addition, some WHEN clauses require Control-O rules to complement these statements.

The general format of the IN, OUT and DO COND condition names for all WHEN type criteria (EOJ, AEOJ, WEOJ, XEOJ, EOE, AEOE, WEOE, XEOE, EOS, AEOS, BOJ, EOG, WEOG, DSN, VAR-$) is:

[boolean-oper][prefix-]fromtablename-jobname_[totablename-]jobname[suffix] date-ref [option]

where

• fromtablename is the Control-M table name in which the predecessor job has been placed

• totablename is the Control-M table name in which the corresponding successor job has been placed. In the case where the predecessor and successor jobs belong to the same table, totablename is omitted.

• suffix – for WHEN criteria which specify abnormal end-of-job (AEOJ, AEOE, AEOS) a suffix of ‘¬’ is appended to the end of the condition name.

• prefix – WHEN clauses indicating WEAK conditions (WEOJ, WEOE, WEOG) allow you to create conditions referring to jobs that may or may not be in the schedule. WEAK conditions enable you to specify that the condition must be respected if the event is in the schedule; otherwise, ignore the condition. Control-M has a Maybe jobs feature that can simulate this conditional handling of predecessor prerequisites. For more information on utilizing this feature, see the discussion of the Manual Conditions File and Maybe jobs in the Control-M for z/OS User Guide.

  The conversion tool facilitates use of the Maybe jobs feature by creating a standard condition name with a prefix of ‘?’. This allows the Control-M ADDMNCND KSL to key on the '?' special character. Alternative prefixes may also be specified, see "MAYBEPF" in Conversion Parameters.

  For additional options regarding Maybe jobs, see the discussion of the CTMX001Z sample exit in Post-step 1. Customize Control-M and Install User Exitss.

  Condition names beginning with the prefix ‘+’ can be created. See the parameter "JOBMANL" in Conversion Parameters for the circumstances under which this may happen.

  Condition names associated with (W)EOG End-of-Group events are created with a prefix of ‘EOG-‘ and without any jobname and totablename. For more details, see Job Dependencies.

  For criteria EOJ, AEOJ, WEOJ, and BOJ, the jobname may be followed by an ‘AT remote-system-id’ clause.

  In such a case, condition names created will have a prefix appended as specified in the REMOTEID source conversion member. Because remote job names might exceed 8 characters, the format of the condition name is modified to:

  [boolean-oper]prefixfromjobname-tojobname[suffix] date-ref [option]

• boolean-oper - Multiple WHEN clauses may be connected by the logical Boolean operators AND and OR in any combination.

  In CONTROL-M, the default relationship between multiple IN conditions is logical AND. To indicate logical OR relationships, the IN condition name must be modified to include special Boolean expression characters. These characters are '(' and ')', to indicate logical grouping of conditions, and '|' (hex 4F) to indicate logical OR.

  • The following WHEN clause

    (EOJ JOB1 OR EOJ JOB2) AND (EOJ JOB3 OR EOJ JOB4)

    is converted to the following IN conditions:

    Copy

    (|JOB1 |JOB2) (|JOB3 |JOB4)

  • The following WHEN clause

    Copy

    (EOJ JOB1 AND EOJ JOB2) OR (EOJ JOB3 AND EOJ JOB4)

    is converted to the following:

    Copy

    |(JOB1 JOB2) |(JOB3 JOB4)

  Warning: Some complex ZEKE Boolean expressions might not be properly converted, since nested Boolean expressions are not supported by Control-M

• date-ref - ODAT is used in all cases except

  • for Zeke VAR $-variables where STAT is used instead (see below)

  • for XEOJ and XEOE extended WHEN criteria where '****' is used instead (supports triggering jobs across multiple schedules - for example, jobs that have run in the past but are no longer in the schedule)

For event-type WHEN criteria (EOE, AEOE, WEOE) the event-name is converted to a jobname. For events which do not have a Zeke jobnames associated with them, the jobname assigned by the conversion tool is used. For example, for SCOM type events, the name SCnnnnnn where nnnnnn is the event number, is used.

For abnormal end-of-job type WHEN criteria (AEOJ, AEOE) the conversion tool also creates an ON PGMST parameter in the job scheduling definition of jobname, or in each job associated with the eventname event, using the above condition name as follows:

• ON PGMST ANYSTEP CODES NOTOK

• DO COND condition-name ODAT +

For end-of-step type WHEN clauses (EOS, AEOS stepname.procstepname.jobname) the conversion tool omits the totablename-jobname portion of the condition name and appends the stepname to the condition name.

The conversion tool also creates a Control-O rule that defines an ON STEP event. When a step in the WHEN (A)EOS ends with a STEPRC of OK, for EOS events, or S*** and U****, for AEOS events, this rule will add the condition described above to the IOA Conditions file.

For BOJ jobname WHEN clauses, which indicate a dependency on the beginning of a job, the conversion tool creates an IN condition with a prefix of BO and omits the totablename-jobname. The conversion tool also creates a Control-O rule that defines a JOBARRIVAL event.

When a jobname in a WHEN clause does not exist in the Zeke Event report, and the JOBMANL option is set to Y, then the conversion tool assumes that this job will be externally submitted (not through Zeke) and therefore creates an ON JOBEND rule in Control-O to trigger the job with this external dependency.

The rule indicates that upon the arrival of job jobname on the JES spool, the condition is added to the IOA Conditions file.

The standard condition name format ensures that a one-to-one correspondence is established between conditions and every pair of job dependencies, that is, all possible job dependencies are represented by unique condition names.

IN conditions of a job are deleted upon the successful completion of the job by specifying an OUT parameter with the condition name and a date reference and option of ODAT-.

The following WHEN clauses (DSN, VAR-$) are not converted to the standard condition naming convention described above, but have their own unique format.

For DSN dsn WHEN clauses, which indicate a dependency on the close of a sequential, non-VSAM output MVS data set, the conversion tool creates an IN condition of the form:

DS-dsnsfx

where dsnsfx is the last 36 characters of the data set name.

The conversion tool also creates a Control-O rule that defines a DSNEVENT event. The rule specifies that upon closing of a specific data set name or generation data group, in any job, the following condition is added to the IOA Conditions file:

DS-dsnsfx ODAT

where dsnsfx is the last 36 characters of the data set name.

ZEKE VAR $-variables may be used in OCCURS and WHEN clauses by specifying the variable name, a relational operator, and a specified value to which it can be compared.

The conversion tool supports ZEKE variables used in OCCURS and WHEN clauses by converting them to manual IN conditions of the form:

variable-name=variable-value STAT

VAR $VAR1 EQ ‘THIS IS A VAR’

VAR1=THIS_IS_A_VAR

These conditions can either be satisfied manually or automatically by conditions created from ZEKE SET commands, as discussed in 27. ZEKESET PROGRAM.

When variable values are enclosed in quotes, all embedded blanks are converted to underscore characters ‘_’.

A job that has a VAR type condition prerequisites will delete those conditions at successful end-of-job, thereby preventing these conditions from improperly triggering jobs later when the value of the variable changes.

23. NOTDURING

The ZEKE NOTDURING condition stipulates that the event cannot be dispatched while a specified program or job is running.

The CONTROL Control-M job scheduling definition parameter is used to control all job resource sharing, as well as to prevent concurrent runs of jobs.

The conversion tool converts the ZEKE NOTDURING JOB jobname by specifying the CONTROL Control-M parameter in the format

NOTDURING-jobname

This Control resource is specified for the job named in the NOTDURING clause with the Exclusive option, and for the job that contains the NOTDURING keyword, with the Shared option in its OCCURS clause.

The conversion tool provides support for generic NOTDURING job names, which are job name prefixes preceded by an asterisk, as follows:

• A CONTROL parameter with the Shared option set that is written in the above format, using the job name prefix instead of a full job name, is placed into all the job scheduling definitions with job names that match the specified prefix.

• A CONTROL parameter with the Exclusive option set is placed into the job scheduling definition of the ZEKE job that contains the NOTDURING keyword in its WHEN clause.

This method is used to minimize the number of exclusive CONTROL resources generated.

24. COND CODE

ZEKE COND CODE validation fields can be used to define job level and step level code analysis to determine if a job was successful.

The conversion tool converts ZEKE COND CODE values to the ON PGMST Control-M post-processing job scheduling parameters. This enables Control-M to check job and step condition codes in the same way as described above for ZEKE.

• ZEKE STEPNAME and PROCNAME are specified in the Control-M subparameters. IfMAXCOND AT EOJ is specified instead of a ZEKE STEPNAME and PROCNAME, or the STEPNAME is specified as ‘********’, a value of ANYSTEP is specified for the PGMST Control-M parameter. If the PROCNAME is specified as ‘********’ (any number of asterisks followed by a blank), the PROCST Control-M parameter is left blank.

• ZEKE ACTION codeA is converted to a DONOTOK Control-M statement, and ZEKE ACTION codeO is converted to a DOOK Control-M statement.

• ZEKE ACTION codeC (cancel) is converted to an ONSTEP rule in Control-O, which contains a DO STOPJOB statement that effectively terminates the job.

• ZEKE OPERATOR codes LOW and HI are converted as described in the following table:

  Table 17 Conversion of LOW and HI ZEKE OPERATOR Codes

  ZEKE Operator Codes	LOW	HI	Control-M Codes
  GE	nn		>C(nn-1)
  GT	nn		>Cnn
  LE	nn		<C(nn+1)
  LT	nn		<Cnn
  EQ	nn		Cnn
  NE	nn		NCnn
  RG	nn	mm	>C(nn-1), <C(mm+1)

The ZEKE MAXCC generation option can be supported by setting MAXCCOK in the CTMPARM member in the IOA PARM library to 4.

Generic ZEKE step names and proc names are not supported.

25. $ VARIABLES

ZEKE $ variables

• trigger events and establish relationships between events

• prevent events from being dispatched

• control job stream flows

• simplify recovery and restart

• substitute values within JCL statements at submission time

• pass information from job step to job step and from job to job

The conversion tool converts all ZEKE $ variables to IOA %%AutoEdit Global variables wherever they appear in the JCL stream.

(ZEKE line) $VAR1   $VAR2

%%SET %%0=%%\M\NO_APPL\NO_GROUP\NO_MEM\VAR1
%%SET %%1=%%\M\NO_APPL\NO_GROUP\NO_MEM\VAR2
%%0   %%1

System dependent variables that use $$$ are not supported.

26. SPECIAL NAMES VARIABLES

ZEKE Special Names Variables are converted as follows:

Table 18 Conversion of ZEKE Special Names Variables

27. ZEKESET PROGRAM

The ZEKE ZEKESET program provides batch services to perform the following functions:

• control job stream flows

• assist in abend recovery

• interact with user programs through ZEKE variables

• control event triggering

• execute MVS and JES commands

• execute Zeke commands

The CTMZSET Control-M utility provides similar functionality. This utility is described in detail in CTMZSET: Invoke IOATEST, IOAAPI, IOACND, CTMRELRS, and CTMAPI Services.

Batch commands converted are those in non-concatenated SYSIN statements (with or without a stepname qualification). Only one Batch command is recognized in each line. It can appear in any one of the following contexts:

• a PDS member

• a sequential data set

• instream, for example, following the statements //SYSIN DD * or //SYSIN DD DATA, or no SYSIN statement at all

• Temporary data sets are NOT supported

For more information, see "PNIBTSD" in Conversion Parameters.

Unsupported Batch commands in SYSIN and extraneous DD statements are deleted.

Non-DD JCL statements in the ZEKESET step, such as IF, SET, or INCLUDE, are not deleted.

28. ZEKESET SET VAR

ZEKE variables can be set to satisfy event prerequisites, and to control job stream flow and job restart. The SET VAR statement defines ZEKE variables and changes existing variable values.

The SET VAR statement

SET VAR $variable EQ operand

generates the following AutoEdit and CTMZSET statements:

1. Copy

   %%SET %%0=%%\M\NO_APPL\NO_GROUP\NO_MEM\variable
   %%SET %%1=%%\M\NO_APPL\NO_GROUP\NO_MEM\operand
   or %%SET %%1=operand-expression (if the operand is a character/numeric string or special variable)

2. Copy

   %%SET %%0 = %%1
   %%SET %%\M\NO_APPL\NO_GROUP\NO_MEM\variable        =%%0

3. Copy

   ADD COND variable = %%0 %%OMONTH.%%ODAY

where:

• variable is the variable name

• operand can be any of the following:

  • another ZEKE variable

  • a numeric value (up to 8 bytes)

  • a character string (up to 64 bytes)

  • ZEKE numeric variable names connected by the+ or- operator

  • a ZEKE special names variable, or variables, as described in 26. SPECIAL NAMES VARIABLES

ZEKE operand character strings that contain embedded blanks are supported. When the operand is a series of numeric variables connected by + or -, such as $A + $B, the operand is converted as %%A %%PLUS %%B. $A - $B is converted as %%A %%MINUS %%B.

Statement C is used by the IOACND IOA utility, which is also invoked by the CTMZSET utility, to add conditions to the IOA Conditions file. This causes prerequisite conditions to be satisfied.

In statement C, the underscore ( _ ) character replaces all embedded blanks in character string values, and the total length of the condition name is truncated to 39 bytes.

$VAR1 = "THIS IS A VERY LONG VAR"

ADD COND VAR1=THIS_IS_A_VERY_ mmdd

29. ZEKE-CTL

The ZEKE-CTL NOSUB JCL statement is used to deactivate ZEKE variable substitution. The ZEKE-CTL SUB JCL statement is used to activate, or reactivate, ZEKE variable substitution.

The conversion tool replaces ZEKE-CTL statements with Control-M AutoEdit statements that perform the same functions, as follows:

• Copy

  %%RESOLVE OFF Control-M AutoEdit statements replace ZEKE-CTL NOSUB statements

• Copy

  %%RESOLVE YES Control-M AutoEdit statements replace ZEKE-CTL SUB statements

30. SCOM

ZEKE SCOM events may specify MVS or JES system commands, or ZEKE commands. The conversion tool converts SCOM events into in-stream JCL statements in the corresponding Control-M job definitions. The type of in-stream JCL created depends on the type of ZEKE command issued.

For native MVS and JES system commands, (such as D J,L) a JCL member consisting of the IOA IOATEST procedure is created specifying the Control statement

CMD=MVS|JES command

The ZEKE commands supported by the conversion tool are ZSET, ZADD, ZDEL, ZDISABLE, ZENABLE, ZHOLD, ZRELEASE, ZOK, and ZALTER DONE|CONT(rol)|TIMEOK. The ZEKE command may be prefixed with ZEKx or Zx.

• The ZSET command creates a CTMZSET procedure with control statements similar to those created for the ZEKESET SETVAR statement, as described in 28. ZEKESET SET VAR.

  The ZSET SYSTEM command is not supported.

• The ZADD command is used to add an event to the schedule. The command may specify events either as event numbers, (generic) event names, (generic) job names, or combinations of event names and job names. All of these are converted to corresponding job names in Control-M tables. For the ZADD command, the conversion tool creates JCL to invoke a CTMAPI procedure using theORDER control statement as follows:

  Copy

  //S1 EXEC CTMAPI
  ORDER DD=SCHD MEM=sched_tbl JOB=jobname [ODATEOPT=RUN DATE=yymmdd]

  For more information, see the discussion of the CTMAPI utility in the Control-M for z/OS User Guide.

• The ZDEL command deletes variables or schedule records.

  The conversion tool supports only the schedule record delete function.

• The ZDISABLE command disables selected events.

• The ZENABLE command enables previously disabled events.

• The ZHOLD command places a HOLD on events.

• The ZRELEASE command releases a HOLD on events.

• The ZOK command notifies ZEKE that an event has been OKed (confirmed) by the operator for dispatch.

• The ZRESOURCE command maintains resources defined to the Zeke database.

• The ZALTER … DONE command forces an event to F/S (Forced Success) status.

• The ZALTER … CONT(rol) NO command marks the event as SUCC upon dispatch.

• The ZALTER … CONT(rol) NX command makes the event a non-executable event.

• The ZALTER … TIMEOK command satisfies the event's time requirement, regardless of the actual time.

For commands ZALTER … DONE|CONT|TIMEOK, ZDEL, ZDISABLE, ZENABLE, ZHOLD, ZRELEASE, and ZOK the conversion creates JCL to invoke a CTMAPI procedure using the following command:

AJF func MEM=memberName

where func is determined as follows:

Table 19 Conversion of ZEKE Commands to Control-M CTMAPI Functions

The conversion tool supports any combinations of the above command types contained within a single SCOM event.

• the DONE, TIMEOK, and CONT(rol) subparameters of the ZALTER command (see above)

• the RD[ate] yy[yy]ddd subparameter of the ZADD command is converted to ODATEOPT=RUN DATE=yymmdd on the CTMAPI ORDER statement (see above)

• the DA[te] yy[yy]ddd subparameter of the ZADD command is converted to DATE=yymmdd on the CTMAPI ORDER statement (see above)

Dates (RDATE and DATE) which specify 99999 (earliest date) are not supported.

For ZRESOURCE commands, the conversion creates JCL to invoke either the IOACND or CTMRELRS utility, as follows:

• The "ZRESOURCE ALTER resource-name SHR nn" command is converted to the IOACND command: "CHANGE RESOURCE resource-name nn"

• The "ZRESOURCE RELEASE resource-name EVTNUM nnn DATE yyyyddd" command is converted to the CTMRELRS command: "RELEASE RESOURCE resource-name 9999" (which effectively releases the entire quantity of the resource from the job.)

  Note that this form of the command is supported only if the EVTNUM number refers to the job itself.

All other forms of the ZRESOURCE command are not supported.

31. ZCOM

• ZEKE ZCOM events specify ZEKE commands. For more information, see the preceding item, 30. SCOM, for the type of ZEKE commands supported.

32. COMM and WORK

ZEKE COMM and WORK events describe actions over which ZEKE has no control. These events are known as work center or comment events. The comments specified on the COMM or WORK event screen are placed into the COnnnnnn DOCMEM members.

For additional information on COMM and WORK events, see 50. VAR and ?VAR in SET clauses.

33. MSG

ZEKE MSG events cause a message to be sent to the system console operator.

The conversion tool converts MSG events by adding a SHOUT WHEN OK parameter with a destination of OPER to a dummy job scheduling definition named MSnnnnnn. For information on how this name is formed, see 1. EVENT NUMBR.

Multiple message lines in MSG event are supported by creating multiple SHOUT parameters.

34. JCL SOURCE

The conversion tool places the value GENERAL, and not the actual JCL library name, in the MEMLIB Control-M parameter. The effect of this is

• all the ZEKE JCL libraries must be concatenated in member IOADSN in the IOA IOAENV library as specified in Step 10 - Adjustments.

• users who want to utilize the JCL edit facilities (Screens 2.J, 3.J) must

  • remove the DALIB definition from the ALCCTM and ALCCTW members in the IOA IOAENV library

  • define the DALIB DDconcatenation directly in the on line (TSO logon) procedure.

For users who utilize the ZEKE CATALOG facility to store JCL source members (by setting the ZEKE JCL to Y in the Event Master Record screen) these JCL source members are placed into a standard PDS (suffix name ZJCLIB) by JOB2. This PDS name must then be added to the DALIB concatenations mentioned in the preceding paragraph.

The conversion tool normally specifies the ZEKE job name in the MEMNAME Control-M parameter. For more information, see 10. JOB NAME. If the ZEKE job name differs from the ZEKE JCL member name, a single line of In-Stream JCL is created in the job definition containing a %%INCLIB Control-M AutoEdit command that copies the JCL from the member name specified in the ZEKE JCL SOURCE parameter. In such cases, the user must add those libraries pointed to by the DD names in the ZEKE JCL SOURCE parameter to the Control-M monitor procedure under the same DD names.

35. CLASS

The ZEKE CLASS identifies an initiator class on which an event can run.

The conversion tool uses the ZEKE CLASS

• to create a SETVAR AutoEdit variable, %%CLASS, in the job scheduling definition

  The value of %%CLASS is set to the ZEKE CLASS, or, when the ZEKE CLASS is blank, to the value extracted from CLASS parameter of the JOB statement of the JCL member (when present). If the CLASS parameter in the JCL is also blank (or not specified) then the default CLASS setting, as specified in the CLASS conversion parameter is used.

• to replace the value of the CLASS field with the AutoEdit variable %%CLASS on all JCL JOB statements

  This enables you to dynamically modify the initiator class of a job using the job scheduling definition.

36. AVGDUR

The ZEKE AVGDUR field gives the estimated duration time for the initial run of a job. ZEKE then calculates the average duration based on the last 10 dispatches.

The conversion tool uses the AVGDUR time to set a SHOUT WHEN EXECTIME Control-M message to indicate that a job is still executing after its average run time duration has been exceeded.

When the AVGDUR is specified (non-blank), the Control-M SETVAR parameter %%CONV-ELAPSED is created with the value, in minutes, of the average duration.

37. OPR OK

The ZEKE OPR OK field indicates whether ZEKE is to wait for an operator OK before dispatching the event.

When OPR OK is YES, the conversion tool sets the CONFIRM Control-M parameter to Y.

38. SYSTEM

The ZEKE SYSTEM field is used to identify the system, pool, or work center that owns an event.

All the ZEKE System-IDs must be translated to MVS CPU-IDs that will be specified in JES2 or JES3 control statements to specify system affinity when jobs are run. See section Create CTM Scheduling & Calendars.

39. TIMES

The ZEKE TIMES field indicates the number of times an event is to be dispatched.

If the event is not a recurring event, that is, a DSPCH FREQ is not specified (see 40. DSPCH FREQ), then the TIMES field is converted to the Control-M MAXRERUN parameter.

For details of recurring events, see Recurring events and cyclic jobs.

40. DSPCH FREQ

The ZEKE DSPCH FREQ field is used for recurring events only, and indicates the amount of time the event is to wait before dispatching again.

The conversion tool converts the DSPCH FREQ to minutes and sets the wait time between cyclic runs, called the INTERVAL Control-M parameter, to this figure.

For details of recurring events, see Recurring events and cyclic jobs.

41. REQUEST

When the option REQOPT is set to Y, all ZEKE REQUEST jobs are converted with the CONFIRM Control-M parameter set to Y and the IOA ALLDAYS calendar is specified for the Control-M DCAL parameter in these jobs. When REQOPT is set to N neither the CONFIRM nor the DCAL parameters are set. For more information, see "REQOPT" in Conversion Parameters.

42. CDATE

The ZEKE ZEKESET CDATE control statements are converted to Control-M AutoEdit format. The following form of the CDATE statement is supported:

CDATE varName(alt-date-format) = DATE [ +|- nn DAYS|MONTHS|YEARS ]

where alt-date-format is a combination of MM, DD, YY, YYYY, DDD, MON, and so on; and nn is the number of days or months or years.

The CDATE statement is converted to

%%SET %%0 = %%\M\NO_APPL\NO_GROUP\NO_MEM\varName

%%SET %%1 = autoEditDateExpressions

or calculations using one or more of the following functions:

%%$CALCDTE, %%SUBSTR, %%$JULIAN
%%SET %%0 = %%1
%%SET %%\M\NO_APPL\NO_GROUP\NO_MEM\varName = %%0

43. FREQCALC

The ZEKE FREQCALC field is used for recurring events only as discussed in 39. TIMES. It is used to specify the next dispatch time after a recurring event has run. C designates clock time; S designates schedule time.

When C is specified in the FREQCALC field, the conversion tool sets the Control-M INTERVAL FROM parameter to END. When S is specified in the FREQCALC field, the conversion tool sets the Control-M INTERVAL FROM parameter to TRGT. For more information, see the description of the END and TRGT values in the Control-M for z/OS User Guide.

44. DATE

The ZEKE parameter DATE oper mm/dd/yyyy schedules jobs on the date specified if the operator relationship (oper) is TRUE.

The manner in which the conversion program converts DATE depends on the operator (oper). The following table provides details:

Table 20 Conversion of ZEKE DATE Operators

When the operator is EQ or NE or ‘NOT DATE’ is specified, DATEs which are earlier than the current system date are ignored by the conversion.

45. EVERY

The ZEKE parameter EVERY nn DAYS BEGINNING mm/dd/yyyy schedules the event every nn days, beginning on the date specified (mm/dd/yyyy). The event is not scheduled prior to the specified date.

Control-M converts this to a cyclic job with the following characteristics:

• INTERVAL is set to nn D, where the INTERVAL is measured in days; the maximum number of days is 45

• INTERVAL FROM is set to TRGT

• MAXWAIT is set to 99

• DEFINITION ACTIVE FROM is set to 0101yy

• DEFINITION ACTIVE UNTIL is set to 3112yy

• DATES is set to mmdd

When you are using the Job Scheduling Definition Plan screen (Screen 2.P) or the CTMRPLN utility to plan, such cyclic jobs appear to be scheduled only once, on the specified date. This is because the plan process does not take account of reruns of cyclic jobs.

When nn=1 in the EVERY statement, the job is not converted as cyclic but as follows:

• DAYS=ALL

• ACTIVE-FROM=yymmdd

46. CONTROL

The ZEKE CONTROL field is a tracking indicator for Zeke-controlled jobs. When Zeke recognizes the event as a non-executable Zeke-controlled event, CONTROL is set to NX. The conversion tool converts this value by setting the MEMLIB Control-M parameter to DUMMY.

47. EXPIRE

The ZEKE EXPIRE field indicates a date on which the event expires. The conversion tool converts this value by setting the DEFINITION ACTIVE UNTIL CONTROL-M parameter to the specified date.

Zeke events which appear on the Events Deactivation report are converted to Control-M job scheduling definitions with the DEFINITION ACTIVE UNTIL CONTROL-M parameter set to the date on which the report was produced.

48. PLATFORM

The ZEKE PLATFORM field indicates the operating system platform upon which the Zeke job is defined. When a non-MVS platform is specified the conversion tool creates an embedded script from the contents of the job's JCL member. In addition, the Control-M OWNER parameter is extracted from the Zeke USERID regardless of the setting of the OWNER conversion option. For more information, see Jobs on Distributed Platforms.

49. TARGET

The Zeke TARGET allows a job to be routed to another system or platform. When the Zeke PLATFORM specifies MVS, then the TARGET is converted to the Control-M NJE-NODE parameter. When a non-MVS PLATFORM is specified, the TARGET is converted to a distributed NODEID.

50. VAR and ?VAR in SET clauses

ZEKE variable values may be set when a Comment event (COMM or WORK) is completed by utilizing the SET clause instead of the WHEN clause for these events.

The conversion tool supports variables in the SET clause by converting them to SET VAR and IN/OUT Control-M parameters in the format:

SETVAR:

%%0=varValue
%%\M\NO_APPL\NO_GROUP\NO_MEM\varName=%%0

IN/OUT:

varName=%%0

For more information, see

• 22. WHEN

• 27. ZEKESET PROGRAM

• 28. ZEKESET SET VAR

In ZEKE, the VAR SET clause automatically sets the variable to the specified value when the work center is flagged as complete, while the ?VAR requires that the operator enter the variable value before the work center is considered complete. The conversion tool supports this difference by setting the CONFIRM Control-M parameter to Y whenever a ?VAR variable is converted. This forces a manual confirmation to be entered from the Control-M Status screen (Screen 3), prior to which the Zoom screen (Option Z) may be entered, which provides the opportunity to modify the SET VAR Control-M parameter corresponding to the ?VAR variable.

51. Oasis Variables

The conversion tool provides limited support for Zeke Oasis variables, as follows:

• Partial support for Oasis variables in JCL members.

  Oasis variables of the form $(xxx) are converted to Control-M auto-edit variables '%%xxx.'.

  The variables are not converted to IOA Global variables (due to the lack of a Zeke report similar to the 'LIST VARIABLES' report for Oasis variables).

• Passive support for Oasis variables in Zeke WHEN clauses.

  The Oasis variable $(xxx) is converted to a pseudo auto-edit variable %%xxx? and a warning message is issued, notifying you that an Oasis variable was encountered when creating an IN condition or an ON DSNEVENT rule.

  The IN condition is created in the following format:

  +eventname_jobname

  where any Oasis variables $(xxx) within the jobname are replaced by '%%xxx?'.

  The user auto-edit variables %%xxx? are NOT resolved in condition names at job order time. It is the user's responsibility to manually handle these conditions.

52. OR

The Zeke OR OCCURS clause indicates combinations of alternate scheduling criteria for an event.

Simple occurrences, such as WORKDAYS OR SATURDAY, are accurately converted as DCAL=calendar-id, A/O=O, WDAYS=6.

However, more complex OR constructs may only be incompletely converted (or not fully accurately), in which case warning message CTMZEK02-05W is issued, alerting the user to examine the converted scheduling criteria to determine if any manual modifications are necessary.

53. LATE END

The ZEKE LATE END TIME is the time at which an event is considered late if it has not completed execution. If the event has not finished execution by this time, a message is issued to the console.

The conversion tool uses the ZEKE LATE END TIME to set a SHOUT WHEN LATE Control-M message to indicate that the job is late when this time has passed. For more information, see the description of the SHOUTLT parameter in Conversion Parameters.

The SHOUT TIME DAYS offset may also be set to +001, when necessary. For more information, see The 48-hour Clock and New Day Processing.

Unique Control-M Parameters

Several unique Control-M job scheduling definition parameters that do not have corresponding ZEKE features can be set using the ICE conversion parameters.

For additional information regarding these parameters, see Conversion Parameters and the Control-M for z/OS User Guide.

DO SYSOUT

Specifies how the job output must be handled.

At job completion, Control-M analyzes the job output. To enable Control-M to locate the output of the job on the system spool, Control-M modifies the JCL MSGCLASS parameter of the job at time of submission to the automatically held output class defined during installation, through the HLDCLAS Control-M parameter. After analyzing the sysout, Control-M may be ordered to requeue the sysout.

For more information regarding DO SYSOUT options, see the Control-M for z/OS User Guide.

The conversion tool can be instructed to specify various actions using the Control-M DO SYSOUT facility.

The TOCLS conversion parameter specifies the output class to which Control-M requeues the job output. For more information on this parameter, see "TOCLS" in Conversion Parameters.

RESOURCE

A Control-M Quantitative resource that may be added to all job scheduling definitions. For example, the INIT resource may be used for controlling initiators. For more information, see "INIT" in Conversion Parameters.

Control-M/Restart

When the Control-M/Restart is installed (CTR parameter in member IOAPARM of the IOA PARM library is set to Y (Yes) the following occurs to the job scheduling definitions created by the conversion tool:

• The PREVENT-NCT2 parameter is set from the NCAT2 parameter in the CTRPARM member in the IOA PARM library.

• (For non-distributed jobs only) The following ON PGMST statement is inserted into the job scheduling definition:

  Copy

  ON PGMST ANYSTEP CODES EXERR
  DO IFRERUN FROM $EXERR
  DO RERUN

  The DO RERUN statement is suppressed for cyclic type jobs.