Conversion Details

This section details the conversion of relevant CA-JOBTRAC components into Control-M job scheduling definition parameters, and also describes the unique Control-M conversion parameters that can be specified. It includes the following topics:

Component Conversion Summary

The conversion tables on the following pages list CA-JOBTRAC components that are converted to corresponding Control-M parameters.

Item number (Item No.) in the following tables refers to the topic number in this chapter.

Table 7 Components of CA-JOBTRAC SCL Members

CA-JOBTRAC Parameter

Control-M Job Scheduling Definition Parameter

Item  No.

EVENT TYPE

OVERLIB=DUMMY

1

TIME and THRESHOLD

TIME FROM, UNTIL SHOUT WHEN LATESUB

2

DATE

MONTHS, DAYS IN conditionrelativedatereference

3

@BUSGRP/@SCHDID

GROUP, OWNER, table name

4

@DATEFORM

MONTHS, DAYS

5

EVENT NAME

MEMNAME, OWNER

6

DEPS

CONFIRM=Y, IN conditions (manual), ON PGMST statements

7

REFERBACK I=

TASKTYP=CYC, INTERVAL

8

REFERBACK R=

CONTROL, RESOURCE, CMEM, IN and/or OUT conditions

9

REFERBACK A=

In-stream JCL

14

EFERBACK IP=

CMDLINE

32

REFERBACK NODE=

NODEID

33

REFERBACK ED=

SETVAR

34

@WORKD

DCAL, WCAL, CONFCAL

35

@WDnnn

DCAL, WCAL, CONFCAL

35

RELEASEn (SUCCESSOR/
PREDECESSOR)

IN and/or OUT conditions

10

SCL member name

APPL, OWNER, GROUP

24

MAXIMUM CONDITION CODE

ON PGMST ANYSTEP CODES Cnnnn

DO OK

11

LOCATION ID

DCAL

12

VERSION NUMBER

IN and/or OUT conditions

13

@HOL, @CYC, UDEFx

DCAL

15

HOLIDAY ACTION

CONFCAL, SHIFT

25

Table 8 CA-JOBTRAC Process Period (PROCESSP) Keywords

Process Period

Control-M Basic Scheduling Criteria

Item  No.

DAILY

DAYS=ALL

 

=MTWTFSS or
MONDAY-SUNDAY

WDAYS=1–0

16, 17

day#n

WDAYS=DmWn, m=1–0

16

day#LAST

WDAYS= 1–0 AND DAYS=L1, ..., L7

16

day#Mn

WDAYS=1-0 AND DAYS=(L(7*n)-6, ...., L(7*n))

16

Xday#n

WDAYS=DdayW1,DdayW2,DdayW3,DdayW4,DdayW5 excluding the entry for week n (DdayWn)

16

Xday#LAST

WDAYS=1-0 AND DAYS=(-L1,-L2,-L3,-L4,-L5,-L6,-L7)

16

EOY

DAYS=L1, MONTHS=12

 

EOM, XEOM

DAYS=L1, -L1

17

FOM

DAYS=D1

15,17

LASTDAY

DAYS=L1

17

WORKDAYS

WORKDAYMnn

WORKDAY#nn

WORKDAYXnn

WORKDAY>nn

WORKDAY<nn

 

DAYS=Lnn

DAYS=Dnn

DAYS=-Dnn

DAYS=n+1, n+2, ..., 31

DAYS=1,2, ..., n-1

15,17

CYCDAYMnnn

CYCDAY#nnn

CYCDAYXnnn

DAYS=LnnnP*

DAYS=DnnnP*

DAYS=-DnnnP*

15,17

QTRn

DAYS=D1, MONTHS=m (m=1,4,7,10)

 

QTRnA

MONTHS=(m,m+1,m+2) (m=1,4,7,10)

 

**/dd/**

DAYS=dd

17

mm/**/**

MONTHS=mm

DCAL=ALLDAYS

17

mm/dd/**

DATES=mmdd

16

UDEFx

XUDEFx

DATES=mmdd

15, 16

CYCLAST

DAYS=L1P*

15

dddCYC#nnn

 

15

CYCLEnn

DAYS=D*Px (x=1,2,...D,E)

15

Conditional operators: +,X

RELATION=A, 'not' logic

17

WEEKDAY#n

WEEKDAY#L

WEEKDAYXn

WDAYS=Dn

WDAYS=L1

WDAYS=-Dn

17

--/--/yy

ACTIVE-FROM=0101yy, ACTIVE-UNTIL=3112yy

 

dddCYC#nn

 

15

EVnday(x)

Cyclic scheduling criteria

27

Table 9 Components of the CA-JOBTRAC JCL Conversion

CA-JOBTRAC Component

Control-M AutoEdit Parameter

Item No.

AJO x=mmddyy

%%IF, %%ENDIF

18

JMF Variables and dates

%% AutoEdit variables

19

Current Day Dynamic Variables

%% AutoEdit variables

20

ADI //: control stmt

%%INCLIB, %%INCMEM

21

ADI date variable

%%AutoEdit variables

22

AUTO-SCHD ($A) program

IOACND ADD COND

23

Table 10 Condition Code Program Filter (CCPF) Table Components

CA-JOBTRAC CCPF TABLE Component

Control-M Parameter

Item No.

Event Name

 

26

Step Name

ON PGMST

26

Procstep Name

ON PGMST º PROCST

26

Condcode Operator/Value

ON PGMST º CODES

26

Table 11 Automatic Data Set Recognition (ADR) Table Components

CA-JOBTRAC ADR TABLE Component

Control-O Rule Parameter

Item No.

DSN

DSN

30

CPU

SMFID

30

ACT

RUN

 

DO FORCEJOB … JOB

30

TOD Threshold

TIME FROM and/or UNTIL

30

Trigger Event

See ACT RUN

30

Create Event

ON DSNEVENT

30

Trigger Process Pe

 

30

Table 12 Automatic Message Recognition (AMR) Table Components

CA-JOBTRAC ADR TABLE Component

Control-O Rule Parameter

Item No.

Msg Text

ON MESSAGE/STRING

31

Offset (first occurrence)

COL

31

Command/Reply

command/wtor

31

Altered Text

newtext

31

Offset (second occurrence)

 

31

Process Pe

Basic scheduling criteria

31

Create Event

JNAME

31

Trigger Event

See Trg Act RUN

31

TOD Range

TIME FROM and/or UNTIL

31

SYS

SMFID

31

Trg Act

ALTR

CMD

NOND

RPLY

RUN

SUPP

 

DO DISPLAY … NEWTEXT

DO COMMAND

DESC=2

DO ASKOPER

DO FORCEJOB … JOB

DO DISPLAY … SUPPRESS Y

31

Extended Text

 

31

Table 13 System Command Scheduling (SCS) Table Components

CA-JOBTRAC SCS TABLE Component

Control-O Rule Parameter

Item No.

Table

ON EVENT

28

CMD

DO COMMAND

28

Intv

INTERVAL

28

Range

TIME FROM and/or UNTIL

28

Process Pe

Basic scheduling criteria

28

SYSID

SYSTEM

28

Component Conversion Detail

1. EVENT TYPE

The EVENT TYPE CA-JOBTRAC parameter identifies the type of event being defined. The EVENT TYPE parameter can contain E (REXX IMOD), D (dummy job) or blank (any other type of event).

Only EVENT TYPEs D and blank are supported by the conversion tool.

In Control-M, an OVERLIB parameter specified as DUMMY indicates that the job must not be submitted. When the EVENT TYPE is D, the conversion tool sets the OVERLIB parameter of the Control-M job scheduling definition to DUMMY.

2. TIME and THRESHOLD

The CA-JOBTRAC TIME parameter defines the time of day when the action specified by the THRESHOLD parameter is performed.

The CA-JOBTRAC THRESHOLD value of blank or S (start time) uses TIME to indicate the earliest time that an event can be submitted. The conversion tool uses the CA-JOBTRAC TIME in the Control-M TIME FROM scheduling definition parameter to specify the lower time limit for job submission. If a start time is not defined, the default start time, that is, the Control-M FROM time, is the same as the target time (described below).

A value of ASAP in the CA-JOBTRAC TIME parameter is translated as blanks in the Control-M TIME FROM parameter.

When the threshold value is blank, a Control-M SHOUT WHEN LATESUB message is set. This message is sent when the specified TIME has passed.

The CA-JOBTRAC threshold value T (target time) indicates that an event can be submitted after being loaded to the schedule, but the event is considered late if it has not been submitted by the specified time. The conversion tool uses the CA-JOBTRAC TIME to set a Control-M SHOUT WHEN LATESUB message to indicate that the job is late when this time has passed. If the TIME value specifies ASAP, the T threshold value is ignored.

The CA-JOBTRAC threshold value A indicates that the event must be purged from the schedule if the job has not been submitted by a specific time. The conversion tool creates the Control-M TIME UNTIL subparameter from the CA-JOBTRAC TIME to indicate the job cannot be submitted after this time.

CA-JOBTRAC historical start time (*) is ignored by the conversion tool.

For additional information regarding when the days offset is specified in the TIME parameter, see 3. DATE.

3. DATE

The CA-JOBTRAC DATE parameter can be a fixed, generic, or relative date. This parameter determines the date for which an event is scheduled. The date and process period for each event have a Boolean AND relationship that determines when the event is scheduled. Fixed and generic dates are converted to Control-M DAYS and MONTHS job scheduling parameters as follows:

Table 14 Conversion of Date Parameters

Format

Converted Format

mmdd

MONTHS=mm, DAYS=dd

mm**

MONTHS=mm

**dd

DAYS=dd

Relative dates cause an event to be scheduled if the process period of an event matches the calendar resolution of the current date. Depending on the relative date entry, the event is scheduled for the current date or some date relative to the current date. The conversion tool supports relative dates with the following formats:

Table 15 Relative Date Formats

Format

Description

*

Current date. The event is scheduled if the process period is matched. The conversion tool converts the processing period. No additional action is necessary.

*-n

Used with predecessor scheduling to indicate that a predecessor event is scheduled to run n days before the successor event.

The conversion tool converts all predecessor events with negative relative dates to IN conditions with a relative date reference of -nnn.

*+n

Indicates that the event is to be scheduled in n days from the current day. Relative dates in this format are used together with the TIME parameter to schedule events that are to run on some future day.

The conversion tool sets the Control-M TIME FROM + DAYS offset parameter to n. Similarly, when a Control-M SHOUT WHEN LATESUB parameter is generated, the same + DAYS offset is set in the SHOUT TIME parameter. For more information on these TIME parameters, see 2. TIME and THRESHOLD.

The DATE parameter is placed in the Control-M DESC job scheduling parameter.

4. @BUSGRP/@SCHDID

The CA-JOBTRAC @BUSGRP/@SCHDID parameter identifies the business group of which the event is a part. The conversion tool optionally creates the Control-M GROUP parameter from the 8-character CA-JOBTRAC @BUSGRP/@SCHDID parameter.

The @BUSGRP/@SCHDID parameter may also be used to create the Control-M OWNER parameter. For more details, see "OWNER" in Conversion Parameters.

Control-M automatically supports CA-JOBTRAC multi-tier business group scheduling by grouping CA-JOBTRAC events into Control-M tables that correspond to CA-JOBTRAC Business Groups. The CA-JOBTRAC @BUSGRP/@SCHDID parameter is used as the table name.

The default table name for jobs not belonging to a Business Group is the CA-JOBTRAC SCL member name.

5. @dateform

The CA-JOBTRAC @DATEFROM control record specifies the format of the dates used in the SCL members. @DATEFORM=A specifies mm/dd format, and @DATEFORM=I specifies dd/mm format. The conversion tool uses the @DATEFORM control record to determine the format of CA-JOBTRAC date parameters when converting them to Control-M MONTHS and DAYS job scheduling parameters.

6. EVENT NAME (EVENTNM)

The CA-JOBTRAC EVENT NAME identifies the event being scheduled, or indicates that the SCL record is a continuation of a previous SCL record. The EVENT NAME can be a job name, a REXX IMOD, a schedule name (prefixed with a 0), or a CA-JOBTRAC task, such as 0ARCHIVE, 0SYSARCH, or 0JOBARCH.

The conversion tool supports both EVENT NAME jobname and schedule name types. The jobname is the name of any job to be scheduled and must match both

  • The jobname entered in the MVS JCL job statement.

  • The member name of the job in the JCL library.

except when the REFERBACK A CA-JOBTRAC parameter is specified, as described in The conversion tool creates the MEMNAME Control-M parameter from the EVENT NAME CA-JOBTRAC parameter.

When a schedule name type is specified, you must ensure that a @BUSGRP parameter is not specified in the SCL member for that schedule as this would cause the conversion tool to change the name of the resultant Control-M table. Jobtrac schedules are converted to Control-M Started task definitions which invoke the STC CTMJOBPR that resides in the IOA PROCLIB library. You must copy CTMJOBPR to an MVS library from which Started tasks can be executed (see the INCONTROL for z/OS Installation Guide: Installing, Chapter 4 Installing IOA, Step 5.3 for details).

In addition, the following Control-M parameters are set in the job scheduling definition:

  • MEMNAME=CTMJOBPR

  • MEMLIB=*,LIB=%%SCHLIB,TABLE=schname (extracted from the Jobtrac SCL event name 0schname)

  • TASKTYPE=STC

  • SET VAR=%%SCHLIB=schedule-lib-name (taken from the &SCHLIB parameter in the DEFAULTS conversion member)

  • CTMJOBPR invokes the Control-M batch utility CTMJOB which orders jobs and tables.

When the EVENT NAME is a Jobtrac Archive task, a CTMJT003-10E error message is issued.

It may also be used to create the Control-M OWNER parameter; for details, see "OWNER" in Conversion Parameters.

JOBTRAC jobs on distributed platforms are identified as event type C. For such jobs, the Control-M MEMNAME parameter is omitted. In addition, a Control-M JOBNAME XML parameter is created from the Event name.

7. DEPS

The CA-JOBTRAC DEPS parameter specifies execution dependencies that must be satisfied before an event can be submitted.

The entries set out in the following table are supported by the conversion tool:

Table 16 Execution Dependencies

CA-JOBTRAC Dependency

Control-M Job Scheduling Parameter

M (Manual release dependency)

CONFIRM=Y

J (JCL required dependency)

IN=JCL-REQU–eventnm (manual condition)

E (Edit JCL dependency)

IN=EDIT-JCL–eventnm (manual condition)

? (View documentation dependency)

IN=VIEW-DOC–eventnm (manual condition)

Q (Queued release dependency)

IN=Q-RELEAS–eventnm (manual condition)

A (Abend bypass)

ONPGM STEP=ANYSTEP CODES=(U****,S***) DO=OK

8. REFERBACK I

The CA-JOBTRAC REFERBACK I parameter specifies a time interval at which an event must be submitted. At each interval the event is resubmitted. A stopping time may optionally be defined to specify when the event must cease to be resubmitted. In addition, a third subparameter may optionally be specified, to indicate the point from which the interval is to be calculated.

When the REFERBACK I parameter is specified, the conversion tool creates the event as a cyclic job using the Control-M TASKTYPE=CYC job scheduling parameter. The time interval specified in I=hhmm is converted to the Control-M INTERVAL parameter. If an optional stop time is also specified as a secondary parameter (that is, I=hhmm/hhmm) the stop time is placed into the Control-M TIME UNTIL parameter, to prevent infinite recycling. If an optional third subparameter (that is, I=hhmm/.../r) is specified, it is converted to the Control-M INTERVAL FROM parameter, as follows:

  • r=E ===> FROM END

  • r=A ===> FROM STRT

  • r=S ===> FROM TRGT

9. REFERBACK R

The CA-JOBTRAC REFERBACK R parameter specifies resource conditions that must be satisfied before an event can be submitted.

The conversion tool converts the RESOURCE REFERBACK parameter depending on how the resource code ID is defined in the RESOURCE member of the CA-JOBTRAC TRACPARM library. For more information, see Resource Management.

When the CA-JOBTRAC resource code ID definition specifies NOJOB=eventname, the conversion tool creates Control-M CONTROL parameters in the format:
x_eventname
where x is the Resource ID code

The resource mode of the CONTROL resource in the job identified by eventname is Exclusive (E), while the resource mode of the CONTROL resource in the jobs that contain a REFERBACK to the resource code ID is Shared (S).

When the CA-JOBTRAC resource code ID definition specifies JOB=eventname, the conversion tool creates a CMEM rule defining a JOBARRIVAL event. The CMEM rule specifies that upon arrival of job eventname, a condition in the format:
x_eventname ODAT
is to be added to the Control-M Resources file, where x is the resource code ID

In addition, the conversion tool creates Control-M IN conditions of the same format as above for jobs that contain a REFERBACK to the resource code ID. For the job whose jobname is eventname a post processing OUT condition in the format:
x_eventname ODAT –
is placed in the job scheduling definition that deletes the condition added by the CMEM JOBARRIVAL event just described

When the CA-JOBTRAC resource code ID definition specifies GENERIC(nn), the conversion tool creates, for all jobs that contain a REFERBACK to the resource code ID, Control-M RESOURCE statements in the following format:
x_GENERIC nnnn
where nnnn is the total quantity of all Quantitative resources with a prefix of x

The conversion tool also creates a JCL job to run utility IOACND to add resources to the Control-M Resources file, with control statements in the form:
ADD RESOURCE x_GENERIC nn

10. RELEASEn (SUCCESSOR and/or PREDECESSOR)

The CA-JOBTRAC RELEASEn parameter specifies various types of successor and predecessor conditions that correspond to Control-M IN and OUT condition parameter definitions.

A REFERBACK parameter value of blank or + indicates that the event names in the RELEASEn parameters are successors. A REFERBACK parameter value of - indicates that the event names in the RELEASEn parameters are predecessors.

The conversion tool converts both predecessors and successors jobs to IN or OUT condition names in the form:
[prefix]fromtablename-fromeventname[+vv]_[totablename-]toeventname[+vv] dateref
where:

  • fromtablename is the name of the SCL or business group in which the predecessor event resides

  • fromeventname is the name of the predecessor event

  • totablename is the name of the SCL or business group in which the successor event resides

  • toeventname is the name of the successor event

  • vv is the version number and is present only if the from/to event is associated with a non-blank version number; for more information, see 13. VERSION NUMBER (VV).

  • dateref is ODAT unless a negative relative DATE (*–n) is specified for a predecessor event, in which case dateref is set to -nnn. For more information, see 3. DATE.

The totablename is omitted when it is the same as the fromtablename.

The above condition is created as an OUT condition in the Control-M predecessor job scheduling definition and as an IN condition in the successor job definition. All of these IN conditions are deleted via an OUT condition which specifies a dateref of:
'**** -'.

The REFERBACK parameter value of "=" indicates a conditional predecessor dependency, which allows you to create conditions referring to jobs that may or may not be in the schedule. Conditional dependencies become predecessors only if they are already on the current schedule when the primary event is added.

Control-M has a Maybe Jobs feature that can simulate this conditional handling of predecessor prerequisite; for instructions on utilizing this feature, see the Control-M for z/OS User Guide. The conversion tool facilitates use of the Maybe Jobs feature by creating IN and OUT condition names with a special character prefix of '¢' (hexadecimal '4A') which allows the Control-M ADDMNCND KSL to specify the condition name prefix '¢' as a Maybe job indicator.

Conditions using this special prefix are also created when predecessor and successor jobs have different processing periods. For more information, see Successor and Predecessor Dependencies.

Predecessor and successor schedule types (event names starting with 0) are not supported. If a schedule of this type is detected, the CTMJT001-10E message, which is described in Messages, is issued. These schedules must be manually converted as follows:

  • When an SCL schedule awaits the completion of a job, convert the corresponding Control-M table to a SMART Table, using, for example, the CTMBTBL utility, and add an IN condition that forces the table to wait for the indicated job to the SMART Table Entity.

  • When a job awaits the completion of an SCL schedule, convert the corresponding Control-M table to a SMART Table and add an OUT condition to the SMART Table Entity. This same condition must be added as an IN condition to the successor job.

11. MAXIMUM CONDITION CODE (CCDE)

The CA-JOBTRAC Maximum Condition Code provides a means to test condition codes at the event level. If the defined condition code is violated CA-JOBTRAC imposes a dependency requiring that the output of the event be checked before successor events can be submitted.

In Control-M, the ON PGMST post-processing parameter specifies the codes-event (a combination of job steps and status codes) on which DO actions are performed.

The CA-JOBTRAC Maximum Condition Code, nnnn, is converted to:

Copy
ON PGMST ANYSTEP CODES <C(nnnn+1)
DO OK

If the CA-JOBTRAC Maximum Condition Code is 4 or less and the MAXCCOK parameter in the CTMPARM member in the IOA PARM library is set to 0, the Maximum Condition Code is converted to:

Copy
ON PGMST ANYSTEP CODES >Cnnnn
DO NOTOK

CA-JOBTRAC step level condition codes are not supported.

12. LOCATION ID (LOC)

The CA-JOBTRAC Location ID provides distributed control over production. For example, the location ID is used for determining the holiday and cyclic calendars and workdays. The conversion tool uses the location ID to form calendar names for the Control-M DCAL parameter. For more information, see Calendars.

13. VERSION NUMBER (VV)

The CA-JOBTRAC Version Number assigns a version number to an event. The same event can be on the current schedule more than once only if each occurrence has a unique Version Number. The Version Number allows the same event to be scheduled multiple times under different scheduling criteria, such as different starting times.

The conversion tool supports the CA-JOBTRAC Version Number by creating multiple Control-M job scheduling definitions for the same CA-JOBTRAC event. In addition, the IN and OUT conditions associated with events having non-blank Version Numbers are modified so that the Version Number is added to the condition name to ensure the proper triggering of like-named events. For more information, see 10. RELEASEn (SUCCESSOR and/or PREDECESSOR).

The Version Number is also placed in the Control-M DESC job scheduling parameter.

14. REFERBACK A

The CA-JOBTRAC REFERBACK A parameter specifies an alternative production JCL member name that does not match the event name. This is the member that contains the JCL to be submitted for the event.

The conversion tool uses the name specified in this parameter to create the following in-stream JCL in the converted job scheduling definition:

Copy
//* %%INCLIB &JCLLIB %%INCMEM memname

where memname is the alternate member name specified in the REFERBACK A parameter. The JCLLIB conversion parameter is described in "JCLLIB" in Conversion Parameters.

15. @HOL, @CYC, UDEFx, XUDEFx, Parameters Requiring Calendars

For full details, see Calendars.

16. WDAYS, DATES

The setting of the Control-M WDAYS and DATES parameters depends on the setting of the SWEEK and DATETYP IOA Installation Parameters. Table 4.2 illustrations all assume SWEEK=MON and DATETYP=A (mmddyy). If SWEEK=SUN, add 1 (modulo 7) to all WDAYS or Dn specifications.

17. X (not)

The X conditional operator, and the X prefix used in the Process Period Keywords, are supported preceding the following keywords:

  • =MTWTFSS

  • SUNDAY–SAT

  • WORKDAYxnn

  • EOM, date

  • CYCxnnn

  • WEEKDAY#n

When the Process Period Keyword is converted to a Control-M DAYS or WDAYS parameter, X has the effect of placing a minus sign in front of the value. For example, X TUESDAY is converted to WDAYS=-2.

18. AJO (Automatic JCL Override)

The CA-JOBTRAC AJO facility is used to automatically delete or insert specified JCL statements based on specific dates. AJO is defined by placing codes in the JCL statement to be affected by the override action. The code must begin in column 73, and is in the form:

Copy
x={mm|**}{dd|**}{yy|**}

where x=D, I, R, or A

The conversion tool converts this by "sandwiching" the affected JCL statements between the following Control-M AutoEdit statements:
%%IF {%%YEAR.}{%%MONTH.}{%%DAY} oper {yy}{mm}{dd}
<JCL statements>
%%ENDIF

where oper depends on the value of x as follows:

x=D, I, R, A; oper=NE, EQ, GE, LT

Only the parts of the date that are not generic, that is, are not **, cause the conversion tool to generate the corresponding Control-M AutoEdit date system variable.

If the CA-JOBTRAC AJO statement specifies I=01**01, the conversion tool generates

Copy
%%IF  %%YEAR.%%MONTH  EQ  0001

A specification of process period in column 60 and {D|I}=SCHD in column 73 in a JCL statement is supported for some column 60 values similar to the above (the <JCL statement> and %%ENDIF are not shown in the converted AutoEdit statements below). The supported column 60 values are:

  • Column 60 = {mm|**}{dd|**}{yy|**} creates:
    %%IF {%%YEAR.}{%%MONTH.}{%%DAY} oper {yy}{mm}{dd}

  • Column 60 = MONDAY|TUESDAY|WEDNESDAY... creates:
    %%IF %%WDAY EQ n

  • Column 60 = =MTWT.. creates:
    %%IF %%WDAY EQ n (for each 'day' specification in the =MTW...)

  • Column 60 = WORKDAY>nn creates:
    %%SET %%0=%%$WCALC %%$ODATE > MTWTF

    %%IF %%0 EQ %%$ODATE

    %%SET %%0=%%$CALCDTE %%$OYEAR.%%OMONTH%%.01 - 1

    %%SET %%0=%%$WCALC %%0 + nn MTWTF

    %%IF %%$ODATE GT %%0

  • Column 60 = WORKDAY<nn creates:
    %%SET %%0=%%$WCALC %%$ODATE > MTWTF

    %%IF %%0 EQ %%$ODATE

    %%SET %%0=%%$CALCDTE %%$OYEAR.%%OMONTH%%.01 - 1

    %%SET %%0=%%$WCALC %%0 + nn MTWTF

    %%IF %%$ODATE LT %%0

  • Column 60 = WORKDAY#nn creates:
    %%SET %%0=%%$WCALC %%$ODATE > MTWTF

    %%IF %%0 EQ %%$ODATE

    %%SET %%0=%%$CALCDTE %%$OYEAR.%%OMONTH%%.01 - 1

    %%SET %%0=%%$WCALC %%0 + nn MTWTF

    %%IF %%$ODATE EQ %%0

  • Column 60 = LASTDAY creates:
    %%SET %%0=%%$CALCDTE %%$OYEAR.%%OMONTH%%.01 + M1

    %%SET %%0=%%$CALCDTE %%0 - 1

    %%IF %%$ODATE EQ %%0

  • Column 60 = EOM creates:
    %%SET %%0=%%$CALCDTE %%$OYEAR.%%OMONTH%%.01 + M1

    %%SET %%0=%%$WCALC %%0 - 1

    %%IF %%$ODATE EQ %%0

  • Column 60 = FOM creates:
    %%SET %%0=%%$WCALC %%$OYEAR.%%OMONTH%%.01 > MTWTF

    %%IF %%$ODATE EQ %%0

19. JMF (JCL Management Facility)

CA-JOBTRAC JMF facility enables the following:

  • Global variable changes to JCL submitted through CA-JOBTRAC and parameters in cataloged procedures.

  • Insertion of parameter statements or values into JCL.

  • Input definitions from multiple partitioned database libraries.

  • Assignment of Current Day Dynamic Variables, as explained in the following item.

The JMF variables specified in the JMFSYM01 member of the DATELIB library, and in any alternate location JCL libraries, are converted to Control-M AutoEdit variables.

JMF alternate library definitions are converted to the following AutoEdit statement:

Copy
%%INCLIB libname %%INCMEM membname

All JMF variable definitions are converted to AutoEdit %%SET statements with variables of the type JMF &: converted to %% variables, both in the JMF member and wherever they appear in JCL members. Embedded blanks in JMF variables are converted to the AutoEdit system variable %%BLANKn.

JMF date specifications allow JMF variables to contain different values depending on the date appended to the variable value. The JMF date specification enables a variable to take on a specific value either before, after, on, or within a range of dates. The conversion tool handles these situations by using the %%SET statement to set the variable value within AutoEdit %%IF and %%ENDIF statements. For example, the following JMF statement:

Copy
VAR=&:GMMDDYY,(01026,01055)

is converted to

Copy
%%IF  %%YEAR.%%JULDAY  GE 01026
%%IF  %%YEAR.%%JULDAY  LE 01055
%%SET  %%VAR  = %%GMMDDYY
%%ENDIF
%%ENDIF

The Control-M JOBTRAC conversion tool does not support JOBTRAC JMF TODDATE and OSDDATE control statements that specify calendar or working day offsets. For example, TODDATE:+2 and OSDDATE:-10W are not supported.

Control-M %%INCLIB xxxx %%INCMEM xxxx statements are inserted into the JCL members to aid in resolving user-defined JMF variables to their assigned values.

Standard Jobtrac variables &:var are normally converted to Control-M AutoEdit variables (%%var). The exceptions are shown in Table 17.

Table 17 CA-JOBTRAC variable conversion

CA-JOBTRAC variables

Control-M AutoEdit variables

&:VAR..constant

%%VAR.constant (One of the periods is deleted.)

&:VAR..&:VAR2

%%VAR..%%VAR2 (The double period is retained.)

&:VAR.&:VAR2

%%VAR.%%VAR2 (The single period is retained.)

&:VAR.constant

%%VAR%%.constant (The period is replaced by the '%%.' operator. The constant does not begin with one of the delimiters listed below.)

&:VAR.#xxx

%%VAR#xxx (The period is deleted. # is any of the delimiters listed below.)

LIST of delimiters:

  • ' (Apostrophe)

  • & (Ampersand)

  • ( ) (Open and Close Parentheses)

  • , (Comma)

  • / (Forward Slash)

  • * (Asterisk)

  • % (Percent)

  • - (Dash)

  • + (Plus)

  • = (Equal Sign)

  • ? (Question Mark)

  • Blank Space

20. Current Day Dynamic Variables

The DYNAMIC member in the conversion Source library contains the translation of all CA-JOBTRAC Current Day Dynamic Variables to Control-M AutoEdit format.

This member is inserted in all converted CA-JOBTRAC JCL members, as an AutoEdit %%INCLIB statement, to provide default values for any converted JMF variables that may reside in the JCL run-stream.

21. ADI //: CONTROL STATEMENT

The Automatic Date Insertion (ADI) feature enables automatic insertion of JCL records in JCL run-streams. A CA-JOBTRAC JCL statement in the form //:(cntlname) indicates that the record identified by the tag cntlname (in the PRODDATE member of the CA-JOBTRAC DATELIB library) must replace the //: statement.

The conversion tool supports this feature by creating a member in an INCLIB partitioned data set for each record in the PRODDATE member. The member name used is the cntlname tag in the PRODDATE record. In addition, the //: statement in the JCL is converted to the following AutoEdit statement:

Copy
%%INCLIB inclib–name %%INCMEM cntlname

22. ADI DATE VARIABLES

The ADI feature described in the preceding item enables replacement lines to contain date code variables. CA-JOBTRAC automatically determines the date on which an event was added to the schedule and converts the date to the specified format.

The conversion tool converts the date code variables as shown in Table 18:

Table 18 Conversion of Date Code Variables

Variable

Output

\M

%%OMONTH.

\D

%%ODAY.

\Y

%%OYEAR

\YDDD

%%OYEAR.%%OJULDAY

\M3

%%OSM3
see the DYNAMIC member in the conversion Source library)

\M9

%%OSM9
(see the DYNAMIC member in the conversion Source library

23. AUTO-SCHD Feature ($A Program)

The CA-JOBTRAC AUTO-SCHD feature (the $A program) provides JCL batch services to

  • Add a previously unscheduled event, such as an on-request event, to the current schedule and track event execution.

  • Manually submit JCL to remove a dependency of an event already on the current schedule.

The conversion tool supports use of the AUTO-SCHD feature using a CA-JOBTRAC JCL step in the following form:

Copy
//$AUTO EXEC PGM=$A,COND=(0,op),PARM='x,...'

where x is the control character specifying the AUTO-SCHD function

The conversion tool supports control characters T and Q that are used to remove a dependency of an event already on the schedule. The conversion tool converts the $AUTO step to the IOA IOACND utility step, which adds conditions to the IOA Conditions File, in the following format:
//$AUTO EXEC IOACND,COND=(0,op),
// PARM='ADD COND cond–prefix–eventname %%OMONTH.%%ODAY'
where cond-prefix is either JCL-REQU (for control character T) or Q-RELEAS (for control character Q)

24. SCL Member Name

CA-JOBTRAC SCL (Schedule Control Language) PDS members specify the events contained in a CA-JOBTRAC schedule.

The conversion tool uses the SCL member name as the value for the Control-M APPL parameter in each job scheduling definition generated from a CA-JOBTRAC event in the SCL member.

The SCL member name is also used as the Control-M scheduling table name and as the value for the GROUP (when the SCL member does not specify @BUSGRP/@SCHDID parameters) and optionally OWNER Control-M parameters. For more information, see "OWNER" in Conversion Parameters.

25. HOLIDAY ACTION

The CA-JOBTRAC HOLIDAY ACTION parameter provides a number of ways for you to handle events that occur on holidays. For example, if the date on which an event is to be scheduled is a holiday, the event can be coded so that it is scheduled on the first working day before or after the holiday.

In Control-M, CONFCAL calendars and the SHIFT parameter are used for handling holidays and other scheduling exceptions, by checking scheduling dates and shifting jobs if they cannot be scheduled on the originally specified day.

The following values for the HOLIDAY ACTION parameter are supported by the conversion tool:

Table 19 Holiday Action Parameters

CA-JOBTRAC HOLIDAY ACTION

Control-M Job Scheduling Parameter

blank

CONFCAL=WORKD

P

CONFCAL=WORKD, SHIFT=<

W

CONFCAL=WORKD, SHIFT=>

S

CONFCAL=WORKD, SHIFT=@

H

CONFCAL=WORKD, SHIFT=@
IN=HOLIDAYH-eventname (manual condit)

N

CONFCAL=WORKD, SHIFT=@+1

O

CONFCAL=HOLID

You must build the HOLID calendar manually. This calendar identifies holidays, and must specify only holidays as scheduling days.

26. CCPF Table

Event names in the CCPF table are used to determine which Control-M job scheduling definitions include a corresponding ON PGMST statement. When a mask (a prefix followed by an asterisk) is specified for the event name in the CCPF table, the corresponding ON PGMST statement is inserted into all job scheduling definitions in which the job name matched the generic event name (that is, the mask). For more information on the CCPF table, see CCPF (Condition Code Program Filter) Tables.

CCPF Step Name and Procstep Name are normally copied as they are to the Control-M ON PGMST ... PROCST statement.

  • If an * (asterisk) is specified for the Step Name, a value of ANYSTEP is specified for the Control-M ON PGMST parameter.

  • If an * (asterisk) is specified for the Procstep Name, blanks are inserted in the Control-M ON PROCST parameter.

  • All other masks for the CA-JOBTRAC Step Name and Procstep Name parameters are not supported by the conversion tool.

CCPF Condcode Operators and Values are converted as described in the following table:

Table 20 Conversion of CCPF Condcode Operators and Values

CCPF Condcode Operator/Value

Control-M CODES

EQ nnnn

Cnnnn

LT nnnn

<Cnnnn

LE nnnn

<C(nnnn+1)

GT nnnn

>Cnnnn

GE nnnn

>C(nnnn-1)

If the MAXCCOK parameter in the CTMPARM member of the IOA PARM library is greater than the CCPF Condcode, then for operators LT and LE only, the above table is modified as follows:

Table 21 Conversion of CCPF Condcode Operators and Values (when the MAXCCOK parameter is greater than the CCPF Condcode)

CCPF Condcode Operator/Value

Control-M CODES

LT nnnn

>C(nnnn-1) DO NOTOK

LE nnnn

>Cnnnn DO NOTOK

All ON PGMST statements converted from the CCPF table specify DO OK to set the status of the relevant job step to OK.

Numbers 27 through 29 are not currently in use.

27. EVnday(x)

The Jobtrac processing period EVnday(x) schedules a job every nth weekday (day) of the year, starting with the xth occurrence of the weekday. The conversion tool supports this process period for the following values: n < 7 and x < 5 and converts it as follows:
TASKTYPE=CYC
INTERVAL=n*7 Days
WDAYS=DdayWx
MONTHS=1
MAXWAIT=99

28. SCS Table

The CA-JOBTRAC SCS table is used to create a CONTROL-O ON EVENT rules table. For more information on the SCS table, see Table 13 in Component Conversion Summary.

The conversion of the SCS table is a fairly straightforward one-to-one correspondence as illustrated in Table 13. However, the following must be noted:

  • A time range of 0000 through 2359 is converted to blanks in both the TIME FROM and UNTIL parameters.

  • Commands F T,cmdmbr which cause the commands in member cmdmbr to be executed are not supported.

  • Command SCHD#nnn to schedule a message reply is not supported.

  • Process Periods that are supported are SUNDAY-SATURDAY and DAILY.

29 ADR Table

The CA-JOBTRAC ADR table is used to create a Control-O ON DSNEVENT rules table. For more information on ADR tables, see ADR (Automatic Data Set Recognition) Tables.

The conversion of the ADR table is a fairly straightforward one-to-one correspondence, as illustrated in Table 11 in Component Conversion Summary. However, the following must be noted:

  • A TOD threshold of 0000 through 2359 is converted to blanks in both the TIME FROM and UNTIL parameters.

  • A Trigger Event name in the form 0sclname causes the jobname in the DO FORCEJOB … JOB parameter to remain blank and the sclname to be used in the TABLE subparameter. Otherwise the trigger event is copied as the jobname and the TABLE name is extracted from the CTMXRF XRF=JOB cross-reference report. This report lists every job (event) and all the tables in which it appears.

  • If the Create Event parameter is left blank, then an '*' is placed in the ON DSNEVENT parameter.

  • Non-blank Process Periods (in both Create and Trigger) are not supported by the conversion tool.

  • Only the RUN action is supported.

30. AMR Table

The CA-JOBTRAC AMR table is used to create a Control-O ON MESSAGE or ON STRING rules table. For more information on the AMR table, see AMR (Automatic Message Recognition) Tables.

The conversion of the AMR table is a fairly straightforward one-to-one correspondence as illustrated in Table 12 in Component Conversion Summary. However, the following must be noted:

  • A TOD threshold of 0000 through 2359 is converted to blanks in both the TIME FROM and UNTIL parameters.

  • Any message texts that contain just a message identifier are converted to ON MESSAGE rules. All others are converted to ON STRING rules.

  • Any message texts containing a double slash (//) are converted to multiple ON STRING rules connected with an AND relationship.

  • When Trg Act=RUN, a Trigger Event name in the form 0sclname causes the jobname in the DO FORCEJOB … JOB parameter to remain blank and the sclname to be used in the TABLE subparameter name. Otherwise the trigger event is copied as the jobname and the TABLE subparameter name is extracted from the CTMXRF XRF=JOB cross-reference report. This report lists every job (event) and all the tables in which it appears.

  • Process Periods that are supported are SUNDAY–SATURDAY and DAILY

  • Extended lines are not supported

  • Trg Actions blank, EXIT, and PURG are not supported

31. REFERBACK IP=

Depending on the Event type (see 1. EVENT TYPE), the CA-JOBTRAC REFERBACK IP parameter may specify an argument to pass to a REXX IMOD (event type E) or a path name/directory name and arguments for distributed job execution (event type C). Event type E is not supported.

For event type C, the conversion tool sets the Control-M TASKTYPE parameter to 'Command' and the Control-M CMDLINE parameter is set to the command string in the IP parameter. Any arguments specified in the IP parameter are converted to Control-M AutoEdit job submission variables %%PARMn (n=1-9).

When a CMDLINE parameter is created in the job definition XML, neither a MEMLIB nor a MEMNAME parameter are created.

32. REFERBACK NODE=

The CA-JOBTRAC REFERBACK NODE parameter identifies the specific distributed platform where the job runs. The conversion sets the Control-M NODEID parameter (host name of an agent computer) to the agent name.

33. REFERBACK ED=

The CA-JOBTRAC ED statement defines an environmental dependency to a REXX IMOD, batch file, script, command, or program for distributed job definitions. These variables are converted to Control-M AutoEdit variables of the form:
AUTOEDIT EXP="%%environmental-dependency-name=environmental-dependency-argument"

Embedded blanks in the argument are converted using the AutoEdit %%BLANKn variable.

34. @WORKD and @WDnnn

The Jobtrac @WORKD global control record resets the workdays parameter for location 000 to include Saturday (SAT), Sunday (SUN), or Saturday and Sunday (SATSUN), or returns the workdays parameter to Monday through Friday (MTWTF).

The Jobtrac @WDnnn global control record overrides the location zero workday calculations. It is used to add Saturday or Sunday or both to locations other than zero. nnn is the location ID of the location affected.

The conversion supports the above global (SCL-wide) parameters by specifying calendar names MTWTF, SAT, SUN or SATSUN in the Control-M DCAL, WCAL and/or CONFCAL scheduling criteria parameters whenever a workdays calendar is required in any of these parameters. For jobs whose location is 000 (or blank), the current setting of the @WORKD parameter is used. If @WORKD has not been set, then a default value of MTWTF is used. For jobs whose location ID is nnn (other than 000), the current setting of @WDnnn parameter is used. If @WDnnn has not been set, then the current setting of @WORKD is used.

It is the user’s responsibility to actually create IOA Calendars with the names MTWTF, SAT, SUN, and SATSUN.

Unique Control-M Parameters

Several unique Control-M job scheduling definition parameters can be set by the conversion tool during creation of the Control-M tables.

The DEFAULTS parameters member in the conversion Source library contains the default settings for these unique parameters, and must be reviewed and modified to specify your local Control-M preferences. For more information regarding these parameters, see Conversion Parameters and the Control-M for z/OS User Guide.

DO SYSOUT

This Control-M parameter specifies how the job output is handled.

At job completion, Control-M analyzes the job output. To enable Control-M to locate the job output 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, namely the Control-M HLDCLAS parameter. After analyzing the sysout, Control-M may be ordered to requeue the sysout. For more information on 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, which is described in "TOCLS" in Conversion Parameters, specifies the output class to which Control-M requeues the job output.

The RELEASE conversion parameter controls whether Control-M releases the job output for printing on the system spool. The default is Y (Yes). For more information on RELEASE, see "RELEASE" in Conversion Parameters.

If the JOBTRAC SCLs contain distributed job definitions (that is, for platforms such as UNIX, AIX, and so on), then the TOCLS parameter is set to blank by the conversion tool. If you nevertheless require the TOCLS SYSOUT requeuing feature for the mainframe jobs defined in the JOBTRAC SCLs, you should customize and install sample user exit CTMX001D provided in the IOA SAMPEXIT library, which provides the same functionality.

RESOURCE

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

Control-M/Restart Facility

If the site has Control-M/Restart installed along with Control-M, the Control-M/Restart PREVENT-NCT2 parameter is set to Y and the following statements are inserted into the job scheduling definitions:

  • ON PGMST ANYSTEP CODES EXERR

  • DO IFRERUN FROM $EXERR

  • DO RERUN