Conversion Details

This appendix includes the following topics:

• Overview of JCL Conversion Details

• Component Conversion Summary

• Component Conversion Detail

  • 1. JOB and MEMBER

  • 2. JCLID

  • 3. SYSTEM

  • 4. JCL-OVRD and #JCL

  • 5. VERIFY

  • 6. MAINT and #MNT

  • 7. HOLD

  • 8. EXEC

  • 9. PRTY and #RES

  • 10. COND-CODE, RO and #SCC

  • 11. TYPE1 and TYPE2

  • 12. CLASS and #RES

  • 13. SCAL

  • 14. ROLL, INDEX

  • 15. SBTM

  • 16. DOTM and LDTM

  • 17. Scheduling Information

  • 18. Job Triggering and #NTR

  • 19. DEP-JOB

  • 20. DEP-JOB=/jobname

  • 21. DSN

  • 22. NWK

  • 23. USER REQUIREMENTS

  • 24. PROSE

  • 25. Virtual Resource Management

  • 26. #JI, #JO, and #JEND, #XI, #XO, and #XEND Statements

  • 27. JCL Job Class

  • 28. CA-7 Batch Terminal Commands

  • 29. CA-11 Non-Restartable Steps

  • 30. INSERT-RMS and //*CA-11 Comment Statements

  • 31. CA-11 U11RMS Step

  • 32. NXTCYC SET-OFF

  • 33. RESCHNG and #RES

  • 35. OWNER

  • 36. SCHID

  • 37. JCL Initialization Statement

  • 38. SHOUT

  • 39. CMEM Rule Table

  • 40. MAINID

  • 42. JES ROUTE PRINT

  • 43. JCLLIB

  • 44. DEP-JOB=?

  • 45. DONT SCHEDULE BEFORE/AFTER

  • 46. #HLD

  • 47. #NOX

  • 48. #MSG

  • 49. #VER

  • 50. ARFSET and #ARF

  • 51. #7UNI

  • 52. LAST-RUN DATE/TIME

  • 58. Global Parameters

  • The CA-7 LAST-RUN DATE/TIME value is converted into the Control-M SETVAR %%$LASTRUNDT auto-edit variable.

• Unique Control-M Parameters

  • CATEGORY

  • DO SYSOUT

  • ADJUST CONDITIONS

Overview of JCL Conversion Details

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

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

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

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

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

Component Conversion Summary

The following conversion tables list CA-7 and CA-11 components that are converted to corresponding Control-M parameters, with cross-references to the topics dealt with in this section.

Table 11 Components of the CA-7 Job Definition Screen (JOB)

Table 12 Components of the CA-7 Job Scheduling Screen (SCHD, JOB)

Table 13 Components of the CA-7 Job Triggering Screen (SCHD, JTRG)

Table 14 Components of the CA-7 Dataset Triggering Screen (SCHD, DTRG)

Table 15 Components of the CA-7 Job Predecessor/Successor Screens (JOBCONN)

Table 16 Components of the CA-7 Documentation Screens (PROSE)

Table 17 Components of the CA-7 Commands Screens

Table 18 Components of the CA-7 Virtual Resource Management Screen (RM/RSRC)

Table 19 Components of the CA-7 Modification to Resolved Schedule Dates Screen

Table 20 Components of the CA-7 or CA-11 JCL Parameter, Statement, or Step

Table 21 Components of the CA-7 or CA-11 Initialization File Statement

Table 22 Components of the CA-7 CALENDAR Macro

Table 23 Components of CA-7 Workload Balancing Macros

Table 24 CA-DRIVER Components

* See the chapter about conversion details in the Control-M for z/OS for CA-SCHEDULER Conversion Guide for details regarding CA-Driver components.

Table 24a Components of CA-7 Automated Recovery Facility (ARF)

Component Conversion Detail

The items in the following section describe the conversion of CA-7 components in more detail.

1. JOB and MEMBER

In CA-7, the job name is specified in the JOB parameter of the CA-7 CPU Job Definition screen and serves as the only job identifier. The JCL member name is specified in the MEMBER parameter of the CA-7 CPU Job Definition screen.

In Control-M, the job name is determined at time of submission and the JCL member name is specified in the MEMNAME job scheduling definition parameter.

In Control-M, job grouping is performed by defining all jobs related to one application in one table. The CA-7 head-of-tree job names are used by the conversion tool to name the Control-M tables.

The Control-M table name is also specified as part of the Control-M GROUP parameter. This table name supplies a common name to the set of related jobs in a SMART Table. The table name also acts as the SMART Table Entity name.

The conversion tool specifies the CA-7 job name in the Control-M MEMNAME parameter. If the CA-7 job name differs from the CA-7 MEMBER name, such as when several CA-7 job definitions use a single JCL member, the following Instream AutoEdit JCL statement is added to the job definition:

%%INCLIB library-name %%INCMEM member-name

This overrides the Control-M MEMNAME and MEMLIB values and copies the JCL from the member identified in the CA-7 MEMBER parameter. In addition, you can optionally install the Control-M job submission exit (Exit 2) to simulate CA-7 processing. For more information, see the description of Exit 2 in Post Step 1. Customize Control-M and Install User Exits.

The conversion tool also uses the CA-7 job name to convert CA-7 job triggers and connections into Control-M IN and OUT conditions, as detailed in 18. Job Triggering and #NTR.

2. JCLID

The CA-7 JCLID is a 3-digit number that identifies the JCL library for a particular job. The library names are contained in the user-modified CA-7 Initdeck in the DSN parameter of the JCL Initialization statements. For more information on CA-7 Initdeck, see the discussion of the input to JOB2 in JOB2 - Create Control-M Tables, CMEM Rules, and XML Definitions.

The conversion tool specifies the CA-7 JCL library name in the MEMLIB Control-M job scheduling definition parameter. If the JCLID of a job does not correspond to any JCL initialization statements, the MEMLIB parameter is set to GENERAL.

The JCLID parameter is not required for non-executable jobs, that is, when EXEC is set to N in the CA-7 JOB screen.

The CA-7 JCLID value 254 indicates use of the CA-7 Special Override library. For more information on how to obtain the equivalent functionality in Control-M, see Special Override Library.

The JCLID for a job is ignored if the JCLLIB field specifies a symbolic JCL variable. For details, see 43. JCLLIB.

3. SYSTEM

The SYSTEM parameter in the CA-7 JOB screen is an optional parameter that associates the job with an application system name.

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

4. JCL-OVRD and #JCL

The CA-7 JCL-OVRD job definition parameter indicates whether, before it can be submitted, the job requires manual JCL overrides, such as specifying a tape serial number in the JCL of the job. Similarly, the CA-7 #JCL override statement in the JCL member specifies that the job requires manual JCL overrides.

In Control-M, such modifications are easily performed by the AutoEdit facility. For more information on the AutoEdit facility, see the Control-M for z/OS User Guide.

The conversion tool adds a manual IN condition to the Control-M job scheduling definition to prevent the automatic submission of the job. The format of the condition is:

JCL_OVERIDE_jobname

where jobname is the Control-M MEMNAME.

5. VERIFY

The CA-7 VERIFY job definition parameter indicates whether the job requires manual verification before it can be submitted.

The conversion tool adds a manual IN condition to the Control-M job scheduling definition to prevent the automatic submission of the job. The format of the condition is:

VERIFY_JCL_jobname

where jobname is the Control-M MEMNAME.

6. MAINT and #MNT

The CA-7 MAINT job definition parameter indicates whether the job is a maintenance job that does not require production data sets, MVS and JES utilities, backups, and the like. For such jobs, CA-7 ignores input data sets requirements. Similarly, the CA-7 #MNT override statement in the JCL member specifies that the job is a maintenance job.

The conversion tool ignores the DSN connection for MAINT jobs.

7. HOLD

The CA-7 HOLD job definition parameter indicates whether the job is held when it enters the Request Queue.

The conversion tool adds a manual IN condition to the Control-M job scheduling definition to indicate that the job is held. The format of the condition is:

HELD_jobname

where jobname is the Control-M MEMNAME.

8. EXEC

The CA-7 EXEC job definition parameter indicates whether the job must be executed. If N is specified, the job does not execute, but CA-7 simulates a normal completion.

In Control-M, set the OVERLIB parameter to DUMMY to prevent the job being submitted.

If EXEC is set to N in the CA-7 job definition, the conversion tool sets the OVERLIB parameter of the Control-M job scheduling definition to DUMMY.

9. PRTY and #RES

The CA-7 PRTY job definition parameter specifies job submission priority. Job priority can be any value from 0 through 255. A value of 255 indicates an express job.

Similarly, job submission priority is determined by the values of the following parameters in the JCL member, which override the value in the CA-7 PRTY parameter:

• the PRT parameter in the CA-7 #RES override statement

The Control-M PRIORITY job scheduling definition parameter uses two alphanumeric characters to set job priority.

The conversion tool transforms the CA-7 numeric value to an alphanumeric value while maintaining priority order. This is achieved by converting the two high order digits of the CA-7 PRTY from 00-25 to A-Z, and not converting the low order digit.

The conversion tool supports CA-7 express priority (when PRTY is set to 255), which is used to bypass Workload Balancing priority scheduling criteria, by defining the job as a critical path, that is, by specifying *5 in the Control-M PRIORITY parameter. For more information, see the Control-M for z/OS User Guide.

10. COND-CODE, RO and #SCC

The CA-7 COND-CODE and RO job definition parameters can be used to define job-level condition code checks to determine whether a job is considered successful or not. The COND-CODE parameter indicates the value for the comparison, and the RO parameter specifies the relational operator. The default setting of RO is 0, when no condition code checking occurs. Similarly, the CA-7 #SCC override statement in the JCL member specifies step-level condition code checking.

The Control-M job scheduling definition enables the user to set condition code checking at step level as well as job level, using the ON PGMST CODES post-processing parameters. By default, Control-M considers a job as ENDED OK if no step condition code is higher than 4.

The conversion tool converts the COND-CODE and RO values to ON PGMST post-processing parameters in the Control-M job scheduling definition. These parameters reflect the same condition code checking as that performed by CA-7. If the RO value is #S, the condition code checks specified in the #SCC statements are used and incorporated as ON PGMST post-processing parameters in the Control-M job scheduling definition.

The following list details the exact #SCC conversion logic:

Table 25 CA-7 #SCC Conversion Logic

In addition to permitting a step name operand following the Relational Operator, such as GE or LE, the conversion tool also allows specification of the procedure step name as follows:

#SCC COND=(nn,ro,stepname.procstepname)

where

• nn is the return code of the step

• ro is the Relational Operator value

• stepname is the name of the step which returned nn

• procstepname is the name of the procedure in the step which caused the step to return nn

This statement is converted to Control-M as

ON PGMST stepname PROCST procstepname CODES xxxx

as shown in the above table.

For processing step names in the form *-stepname, (step exclusion) the conversion makes use of Control-M step range statements as follows:

STEP RANGE -RNGnnn FR (PGM.PROC) stepname . TO stepname
ON PGMST *-RNGnnn PROCST +EVERY CODES code
DO OK

-RNGnnn indicates a Control-M exclusionary step-range name. For this feature to function properly, optional parameter EXSTPRNG in the CTMPARM member of the IOA PARM library must be set to Y.

When the CA-7 job definition indicates default checking, unless you set the value of the MAXCCOK parameter in CTMPARM to 4095, the conversion tool sets the following Control-M specification (for Mainframe jobs only):

ON PGMST ANYSTEP PROCST CODES C****
DO OK

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

When the CA-7 RO field is set to IG(nore), the conversion tool sets the following Control-M specification:

ON PGMST ANYSTEP PROCST CODES *****  ****
DO OK

11. TYPE1 and TYPE2

The CA-7 TYPE1 and TYPE2 job definition parameters specify the number of tape drives used by a job. CA-7 manages only two tape drive types by referencing a CA-7 logical device type, not the MVS device types.

Control-M handles tape drive resources, and any other critical computer resources, as quantitative resources. The Control-M job scheduling definition RESOURCE parameter specifies the resource name and the quantity used by a job.

The resource names specified in the TAPE1 and TAPE2 conversion parameters in the DEFAULTS member are used by the conversion tool to represent the two CA-7 tape drive types. The CA-7 TYPE1 and TYPE2 C (calculated) amounts are converted to Control-M job scheduling definition RESOURCE specifications. When a non-zero tape resource manual override (M) amount is specified, this amount is used instead of the calculated (C) tape resource amount.

The resources above must be added to the Control-M Resources file with a quantity corresponding to the MXTAL parameter of the CA-7 workload balancing TAPE1 and TAPE2 macros.

12. CLASS and #RES

In CA-7, class barriers are workload balancing parameters that establish the maximum number of jobs that can be submitted concurrently in the associated job class.

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

If the CLASBAR conversion parameter, which is described in "CLASBAR" in Conversion Parameters, is set to Y, the conversion tool converts the CA-7 CLASS by specifying a RESOURCE parameter with a quantity of 1, in the format

CLASS_BAR_jobclass

where jobclass is the CA-7 workload balancing job class.

The CA-7 workload balancing job class can also be specified using the value in the CLASS parameter in the #RES JCL override statement. This value overrides the value in the CA-7 CLASS parameter.

The above resources must be added to the Control-M Resources file with a quantity corresponding to the CA-7 class barrier specification, which is defined in the BARx parameter of the workload balancing CLBARR macro.

13. SCAL

CA-7 calendars are defined for one year only. A CA-7 Base calendar ID has the format SCALyyxx

where:

• yy is the target year

• xx are two unique characters used during initial creation of the calendar

A Control-M calendar definition can contain multiple years, and its name can be from 1 through 8 characters in length.

The Control-M job scheduling definition has several optional calendar parameters, namely DCAL, WCAL and CONFCAL. For more information on these parameters, see the Control-M for z/OS User Guide.

Calendars are automatically created as described in the following situations.

When the User Specifies CA-7 Base Calendars in JOB1

The CA-7 schedule definition must contain a Base calendar. It may also contain additional optional calendars for each schedule-ID. These are used to verify, or resolve, the requested schedule days against the days specified as working days in the calendar. When a specific day is not a working day, for example, because it is a holiday or weekend, the ROLL parameter determines the schedule. The conversion tool uses the CA-7 SCAL Base calendar ID as the Control-M CONFCAL calendar based on the ROLL specification. For more information on the ROLL parameter, see the next item, 14. ROLL, INDEX.

The following naming convention is used by the conversion tool when converting CA-7 Base calendars to Control-M calendars:

• Up to the first five characters are a constant value, as specified in the CALPREF conversion parameter. For more information, see "CALPREF" in Conversion Parameters.

• The next two characters are the last two characters of the CA-7 calendar name, that is, the SCAL=xx that was specified by the PRINT command of JOB1.

• If the CA-7 base calendar is periodic (see Conversion Steps and 12. CLASS and #RES, in the INPUT section see the details about periodic calendars), a periodic Control-M calendar is created with the above naming convention. This periodic calendar has all of its days marked as scheduled working days with the appropriate period indicator. An additional corresponding non-periodic calendar is also created. Its name is the same as the periodic calendar with the addition of the suffix "0". It has only the actual scheduled days marked with a "Y". It is used as a CONFCAL Calendar, as necessary, in the job scheduling definitions, which are governed by a periodic base calendar to determine when a relative periodic day is actually to be scheduled or not.

• A second periodic calendar is also created with the above naming convention using a suffix of 'W'. This calendar is used as a weekdays calendar for periodic WDAYS scheduling criteria which requires a WCAL calendar. This calendar has all its days marked with period indicators '1' through '6' indicating the week of the (non-standard) month in which the scheduled day occurs.

Base calendars created with the CA-7 OPTION=SCHDYONLY are marked as SCHDYONLY. For more information, Post-conversion Operations.

When a CA-7 Job Has the SCHDMOD CURRENT Indicator Set in its Scheduling Information

The CA-7 Modification to Resolved Schedule Dates screen (D.B.2.7) enables a user to permanently modify a resolved schedule for a job input network or on a specific schedule-id without having to redefine the schedule. This modification is indicated by a status of CURRENT.

A list of all CA-7 job schedule members that have been modified using the SCHDMOD screen is available in CA7ER789, the CA-EARL CURRENT SCHDMOD report. For more information, see the CA-7 Management Reporting Guide.

The user can, globally or on an individual application basis, determine whether SCHDMOD CURRENT processing is to be performed on jobs whose schedules are so marked. For more information, see "SCHDMOD" in Conversion Parameters, and the description of the Application Report file in 12. CLASS and #RES. SCHDMOD CURRENT processing is the same as the processing described below.

When CA-7 Job Schedule Parameters Cannot Be Consistently Converted to Control-M Basic Scheduling Parameters

The CA-7 job schedule parameters cannot be consistently converted to Control-M Basic Scheduling parameters when

• the conversion tool encounters a CA-7 SYMETRIC parameter, and the calendar used for the schedule was created with OPTION set to SCHDYONLY, or the CA-7 SPAN parameter is greater than 45

• it is determined by the conversion tool that the CA-7 scheduling definition for a particular ScheduleID cannot automatically be converted to Control-M Basic Scheduling parameters

• a CA-7 job schedule utilizes a nonstandard (periodic) calendar

• SCHDMOD CURRENT processing is requested (as described in the preceding section)

When one of these cases is encountered, the following occurs:

• JOB1 builds an auxiliary calendar in the Control-M Calendar library that is based on the CA-7 scheduling definition of the job in the LSCHD report. For more information on auxiliary calendar naming conventions, see the description of the Control-M Calendars library among the Output Files under JOB1.

• The auxiliary calendar is marked as SCHDMOD-CURRENT if the CA-7 schedule in the LSCHD report of the corresponding job indicates that at least one modification made to its schedule ID is still in effect, that is,the modification has a status of CURRENT. Otherwise, the calendar is marked as AUXILIARY CAL.

• For all jobs associated with the ScheduleID, the Control-M job scheduling definitions in the table are modified as follows:

  • the auxiliary calendar name is placed into the DCAL parameter

  • the DAYS and MONTHS parameters are set to ALL

  • the WDAYS, AND/OR, CONFCAL, WCAL, and SHIFT parameters are cleared

  Auxiliary calendars placed into the Control-M Calendar library are 1-year calendars only, spanning January through December or July through June, depending on when the CA-7 schedules were RESOLVEd. You must extend these calendars to multiple years as soon as possible.

  You can use Control-M utilities to

  • utilize user-defined calendars rather than the auxiliary calendars

  • reduce the number of calendars defined to Control-M by defining your own Control-M Basic Scheduling parameters, such as DAYS or WDAYS.

  • For more information, see the discussion of the creation of auxiliary calendars in the description of the use of the CTMXRF Control-M utility in Post Step 2. Perform Final Adjustments.

14. ROLL, INDEX

The Control-M SHIFT job scheduling definition parameter encompasses both the CA-7 ROLL parameter and the CA-7 INDEX parameter. The SHIFT parameter has the format xyyy

where

• the value of x corresponds to the ROLL parameter value

• the value of yyy corresponds to the INDEX parameter value

Each of these conversions is described below.

The CA-7 ROLL schedule definition parameter indicates the action CA-7 is to take when verifying (resolving) schedule parameters against the CA-7 Base calendar.

CA-7 ROLL action values are converted to Control-M as follows:

1. When ROLL is set to D, no action is to be performed and the requested schedule day is to be skipped. In such a case, the Control-M SHIFT parameter in the Control-M job scheduling definition is left blank.

2. When ROLL is set to B, the requested schedule day is to be rolled backward to the previous calendar working day. In such a case, SHIFT is set to < in the Control-M job scheduling definition.

3. When ROLL is set to F, the requested schedule day is to be rolled forward to the next calendar working day. In such a case, SHIFT is set to > in the Control-M job scheduling definition.

4. When ROLL is set to N, the requested schedule day must be kept regardless of the calendar definition (except for DAILY scheduling). In such a case, SHIFT is set to @ in the Control-M job scheduling definition.

When the CA-7 Base calendar is a non-standard (periodic) calendar, the Control-M CONFCAL and SHIFT parameters are omitted, regardless of the CA-7 ROLL value.

The CA-7 INDEX schedule definition parameter is used to specify an adjustment to schedule days. After exercising the ROLL option, the schedule is adjusted forward or backward by the number of working days specified in INDEX. This value (not exceeding 62), including sign, is copied to the Control-M SHIFT parameter in the yyy portion of the value, as described earlier in this item.

15. SBTM

The CA-7 SBTM schedule definition parameter specifies a submission time prerequisite. CA-7 does not submit the job before this time.

The Control-M FROM job scheduling definition parameter specifies the earliest time the job can be submitted.

The conversion tool assigns the value of the CA-7 SBTM parameter to the Control-M FROM parameter. If no value is set in the CA-7 SBTM parameter, the conversion tool can optionally use the deadline start time, the STARTM parameter on the LJOB report. For more information, see "STARTM" in Conversion Parameters.

16. DOTM and LDTM

The CA-7 DOTM and LDTM schedule definition parameters specify the due-out time and lead time used by CA-7 for scheduling. DOTM (due-out time) specifies the time that the job must end. LDTM (lead time) specifies the execution time of the job plus any additional setup time. CA-7 uses the value of these parameters to calculate the start time, that is, the time at which the job must be placed on the Request Queue.

The Control-M DUE OUT job scheduling definition parameter, or the DOTM parameter of a demanded job, specifies a time by which a job must finish execution. The conversion tool assigns the value of the CA-7 DOTM parameter to the Control-M DUE OUT parameter that is used in calculating the time at which a job must be submitted.

For information about how the conversion handles the CA-7 LDTM, see 19. DEP-JOB and the descriptions of parameters LDTTHRSH and LEADTM0 in Conversion Parameters.

17. Scheduling Information

Many of the differences between Control-M and CA-7 schedule definitions are a matter of terminology only. The conversion tool handles such differences automatically. For example, CA-7 WEEKLY is WDAYS in Control-M, MONTHLY is DAYS, and ANNUAL is DATES (computed on a non-leap year basis).

Although the following CA-7 scheduling specifications are converted automatically, they require additional clarification.

1. MONTHLY, NDAY=ddd, WEEK=xx

   This CA-7 schedule specification means "do not run on DAY ddd WEEKxx." The conversion tool converts this schedule combination by specifying the weeks to schedule the job instead of specifying the weeks not to schedule the job, as shown in the following example:

   Table 26 Scheduling Information Conversion Example

   CA-7	WEEKLY	DAY=THU
   	MONTHLY	NDAY=THU	WEEK=02
   		NDAY=THU	WEEK=03
   	translates to
   Control-M	WDAYS	D4W1,D4W4,D4W5,D4W6

   If xx is -00, the Control-M DAYS parameter is set to L1, L2, ..., L7 or -L1, -L2, ..., -L7, depending on whether the week is to be included or excluded; the Control-M WDAYS parameter is set to the value of the CA-7 DAY.

   If xx is 01, the Control-M DAYS parameter is set to 1, 2, ..., 7 or -1, -2, ..., -7, depending on whether the week is to be included or excluded; the Control-M WDAYS parameter is set to the value of the CA-7 DAY.

   When WEEK=04 and WEEK=05 are specified, the conversion treats it as if WEEK=-00 was coded.

2. A CA-7 calendar definition can specify OPTION=SCHDYONLY. This calendar definition parameter changes the representation of the CA-7 MONTHLY RDAY schedule definition parameter from processing days to calendar (working)days. This is converted by specifying the calendar in the Control-M DCAL parameter and the days of the month as working days, in Dn format.

   Every CA-7 schedule is associated with a calendar that—by default—applies to all its schedule-ids. However, you can specify a base calendar (SCAL=xx) for each schedule-id . In such cases, the conversion uses this calendar (for the Control-M DCAL, CONFCAL) rather than the schedule's default calendar.

3. SYMETRIC START=ddd SPAN=nnn

   A SYMETRIC definition schedules a job beginning on the date specified in the START parameter, and recursively schedules it every nnn days as specified in the SPAN parameter.

   SYMETRIC schedules are converted to job definitions with the following attributes:

   • the SCHEDULE RBC corresponding to the CA-7 SCHEDULE-ID contains

     • a DATES value of ddmm (or mmdd) derived from the Julian date ddd specified in the CA-7 START parameter

     • a MAXWAIT value of 99, so the job is never removed from the Active Jobs File

     • the TASKTYPE is CYClic

   • the INTERVAL parameter in the job definition is set to nnnDFROMTRGT, meaning the job must be recycled every nnn days from the date scheduled for the current job run

   SYMETRIC schedules are only converted in this way if

   • the calendar corresponding to the schedule-ID was not created with OPTION set to SCHDYONLY

     and

   • the value in the CA-7 SPAN parameter does not exceed 45

   When an online P (Plan) command in Screen 2 is issued for a converted SYMETRIC job, the calendar plan shows the job as being scheduled on only one date, that specified in the DATES parameter. In most cases, this does not match the CA-7 schedule (LSCHD) for the job. This is because the conversion tool converts the job as a cyclic job. Reruns of cyclic jobs are not displayed in response to the Plan command if the INTERVAL parameter is set to span more than one day.

4. REPEAT INTERVAL=hhmm TYPE=type COUNT=cccc STOP=hhmm

   A REPEAT definition schedules a job to execute recursively every hhmm hours and minutes based on the INTERVAL parameter until either the STOP time (TIME UNTIL) is reached or the COUNT maximum number of reruns (MAXRERUN) is reached. The cyclic jobs begin running based on a type (INTERVAL FROM) of either Start, End, or Clock (Target).

   However, when a cyclic job's window of eligibility (FROM time – UNTIL time) crosses the site's Newday time, the job definition is converted as follows: The UNTIL time is set to ‘>’, the MAXWAIT is set to 1, and the MAXRERUN is calculated based on the difference of the original CA-7 Start and Stop times divided by its Interval.

   Scheduling criteria of negative Annual days in combination with REPEAT are ignored.

5. When a CA-7 job contains multiple schedule-ids which differ only in their time parameters (due-out, submit, start) then the job definition is converted to a Control-M (enhanced) cyclic SMART table. If the differences in the time intervals are fixed, then the job is converted to a regular cyclic SMART table using the INTERVAL parameter and the MAXRERUN parameter is set to the number of schedule-ids. Otherwise, the job is converted to an enhanced cyclic SMART table with a list of specific times. However, if the resultant SMART table contains only a single job and that job is cyclic, then the SMART table is not changed to cyclic.

6. Periodic scheduling: When the CA-7 job's schedule criteria specifies a non-standard base calendar, the conversion will convert all DAYS and WDAY criteria into periodic scheduling format, namely [-][D|L]nP[m|*] and the corresponding DCAL or WCAL calendar will be periodic. Multiple Control-M SCHEDULE RBCs might be necessary to fully convert such CA-7 schedule-ids (see 36. SCHID).

7. If conversion of CA-7 scheduling criteria require any of the following, see 36. SCHID.

   • both Control-M DAYS and DATES parameters

   • both Control-M periodic and non-periodic parameters

   • more than 12 Control-M DATES parameters

8. If CA-7 job schedule parameters cannot be consistently converted to Control-M Basic Scheduling parameters, or if the SCHDMOD CURRENT scheduling indicator is set, see 13. SCAL and parameter SCHDMOD in Conversion Parameters.

9. Schedules that contain only negative ANNUAL days are converted to empty RBCs. When ANNUAL DAY=nnn is the same as ANNUAL NDAY=nnn, they cancel each other out.

10. ANNUAL days 366 is converted to DATES 3112.

18. Job Triggering and #NTR

In CA-7, the execution sequence of jobs within an application is specified by job triggering. Job completion with acceptable condition codes triggers the next job or jobs until the entire application is completed.

In Control-M, job sequence is specified using prerequisite conditions. Each job that finishes OK according to its specification in the Control-M job scheduling definition can add a prerequisite condition to the IOA Conditions file. The condition is specified as an OUT condition in the job scheduling definition.

The conversion tool builds condition names in the format

schedule-table_jobname_sfx ODAT

where:

• schedule-table is the Control-M table name

• jobname is the MEMNAME

• sfx is taken from conversion option SFXCND (see Conversion Parameters)

If there are duplicate job names within the same table, then a numeric occurrence number of the job is appended to the condition name preceding the suffix.

Every converted job contains an OUT condition of this type, and all triggered jobs contain this condition as an IN condition. This mechanism ensures that the Control-M execution flow is the same as in the CA-7 job triggering definitions.

The CA-7 #NTR override statement in the JCL member causes suppression of the job triggering that is otherwise initiated by successful job completion.

The conversion tool converts #NTR override statements in JCL members by suppressing the creation of OUT conditions in the relevant job scheduling definitions.

The conversion tool builds Control-M tables containing all the application jobs. This means that an entire job tree, based on the CA-7 triggering information, is contained in one Control-M table.

For more information, see Control-M Table Creation.

19. DEP-JOB

The CA-7 DEP-JOB job connection parameter specifies a predecessor job on which the job specified in the JOB parameter is dependent. This causes the dependent job to wait until the job specified in the DEP-JOB parameter has completed OK.

For job type connection dependencies, the conversion tool builds IN and OUT conditions in the form

jobname_dep-jobname_sfx ODAT

where

• jobname (the predecessor job name, on which dep-jobname is dependent) is the Control-M MEMNAME of the predecessor job

• dep-jobname (the successor job name) is the Control-M MEMNAME of the successor job.

• sfx is taken from conversion option SFXCND (See Conversion Parameters)

A separate OUT condition is created for each job for which a job or DSN connection exists. This provides a considerable degree of granular control for manipulating OUT conditions. For example, if job A has three dependent jobs (B, C, and D as specified in DEP-JOB), three IN/OUT conditions are created, B_A_OK, C_A_OK, and D_A_OK, each in the respective job scheduling definition. If job A abends, you can selectively trigger job B without affecting jobs C and D by adding the condition B_A_OK to the IOA Conditions file.

For details on how the IN/OUT conditions are affected by the CA-7 job connection LEADTM (the satisfaction lead time in hours), see Conversion Parameters, conversion options LDTTHRSH and LEADTM0. The conversion ignores a LEADTM value 99, but the customer should consider implementing sample user exit CTMX001Z to simulate the functionality of LEADTM=99. A Control-M SETVAR parameter %%LEADTM=leadtm_schid_jobname is added to the job definition for each job connection specifying a lead time.

Job connection conditions are deleted from the IOA Conditions file when the job ends successfully via an OUT statement (specifying an option of '-'). When many jobs run more than once each day, this allows cleaning used conditions from the IOA Conditions file, so that a condition that triggered a successful job run does not trigger subsequent job runs.

20. DEP-JOB=/jobname

The CA-7 DEP-JOB job connection parameter can specify a job name preceded by "/" (slash). This type of job connection is referred to as a negative job dependence, in that CA-7 prevents the connected job and the job specified in the DEP-JOB parameter from executing concurrently. The job specified in the DEP-JOB parameter runs only when the connected job ends (or abends), but it is not triggered by the connected job.

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

The conversion tool converts this CA-7 job connection by specifying the CONTROL parameter in the format

EXCLUSIVE_jobname

where jobname is the connected CA-7 job name.

This CONTROL resource is specified for the connected job with the Exclusive option, and for the DEP-JOB job with the Shared option.

Generic negative job dependencies (a jobname prefix followed by an asterisk) are supported by specifying the jobname prefix in the Control-M CONTROL parameter and by adding this CONTROL parameter, with the Share option, to all jobs whose jobname matches the prefix. The CONTROL parameter, with the Exclusive option, is added to the job definition in which the generic negative dependency is defined.

21. DSN

The CA-7 DSN job connection parameter specifies an input data set name as a prerequisite for a job. This type of job connection instructs CA-7 to suspend the execution of a job until the input data set is created.

For example, if the CA-7 job connection definition states that JOBB has an input data set connection to DSN.OUTFILE, the job is dependent upon the creation of that data set.

For CA-7 DSN requirements in Mainframe jobs, the conversion creates two Control-O rules:

• The first rule is triggered when the DSN is cataloged. It adds an OUT condition that specifies the dsname, up to 39 bytes long, along with a date reference of STAT. If the dsname is longer than 39 characters, the rule removes all periods, and issues a warning message.

• The second rule is triggered when the DSN is deleted. It deletes the condition added by the first rule. The job that specifies the DSN as a requirement will have this condition as a prerequisite IN condition.

The conversion tool ignores a DSN connection when a CA-7 job definition specifies any of the following:

• Job is a MAINT job (maintenance job)

• DSN is marked as "*PERM DSN*"

• DSN is marked as "PERM FOR JOB"

A job’s DSN REQUIREMENT is processed as described above when the DSN is marked as 'CREATED BY [**NONE**|nnn JOBS]' in the DSN connection requirement in the LJOB report, unless the CA-7 Cross-Platform Tracker (XTRK) feature is in use at the site. In such a case, or when a distributed job is TRIGGERED BY a dataset, a Filewatcher job (FWJnnnnn) is created. The filename in the Filewatcher job is the matching remote (distributed) filename found in an EVENT rule in the CA-7 XEVENTS file. If no match is found, the MVS DSN specified in the LJOB REQUIREMENT is used. For further details, see Stage 1. Data Extraction.

22. NWK

The CA-7 NWK job connection parameter is used to specify the network prerequisites of a job.

The conversion tool converts this CA-7 job connection to a manual IN condition of the form

NW_jobname

where jobname is the Control-M MEMNAME.

23. USER REQUIREMENTS

The CA-7 USER REQUIREMENTS job connection parameter specifies user-defined prerequisites for a job. It contains up to 36 characters of text. CA-7 suspends the execution of a specific job until this user-defined prerequisite is manually posted.

In Control-M, a manual prerequisite condition prevents the submission of a job until the condition is added manually to the IOA Conditions file.

The conversion tool converts this CA-7 connection by specifying a long IN condition in the Control-M job scheduling definition of the connected job. The format of the string is

jobname_usertext

The variable jobname is the Control-M MEMNAME of the CA-7 connected job. The variable usertext is at least the first 30 characters of the USER REQUIREMENTS parameter.

24. PROSE

In CA-7, job documentation (PROSE) optionally describes each job. The PROSE data is stored in the CA-7 database, and is maintained by means of the PROSE on-line screens.

In Control-M, documentation can be specified for each job. The documentation data of each job is specified in the DESC field of the Job Scheduling definition or may be contained in one library member of a Documentation Library. See Prose Information for the method chosen by the conversion tool to convert CA-7 PROSE data.

25. Virtual Resource Management

The Virtual Resource Management facility enables the definition of job-to-resource dependencies that control execution of the job according to resource availability at job submission time. For more information on this facility, see Virtual Resource Management (VRM).

The types of resources managed by this facility, and the way the conversion tool converts them to Control-M, are as follows:

• Shared and Exclusive resources

  A Shared resource connection enables multiple jobs to execute at the same time, even though they may all use the same resource. An Exclusive resource is used to indicate that the job requires exclusive use of a resource, so that no other job requiring the resource can execute until the end of the exclusive use job.

  In Control-M, a CONTROL parameter is used to control resource sharing, and is defined with Exclusive or Shared options. For more information on the CONTROL parameter and its subparameters, see the Control-M for z/OS User Guide.

  When the resource Free attribute is specified as Y, Control-M adds the K onFail subparameter to the resource.

• Corequisite resources

  In the case of a Corequisite resource connection, whether a job executes depends on whether the status of the specified resource is active or inactive.

  In Control-M, these resources are converted into manual IN conditions in the format

  [\]resName STAT

  where resName is the name of the resource.

  When the CA-7 Free attribute specifies A (Active), the condition name does not contain a prefix. When the Free attribute specifies I (Inactive), the condition name is prefixed with a '\' to indicate an inverted (negative) condition.

• Resource Count resources

  The availability to a job of a Resource Count resource depends on the count or number specified for this resource and job. When a job-to-resource connection is made to a Resource Count resource, the specified number identifies the total number of occurrences of this resource that are used by this job.

  In Control-M, a RESOURCE parameter is used to specify Quantitative resources and the actual quantity of the resource that the job requires. For more information on the RESOURCE parameter, see the Control-M for z/OS User Guide.

  The resource Free attributes are converted to Control-M onOk and onFail subparameters, as follows:

  Resource Free attributes	Control-M onOk and onFail subparameters
  N	D
  F	blank
  Y	K
  A	D

• Address Space resources

  An Address Space resource controls the submission of the job based on the status of an address space, depending on whether the status of the resource (a job or started task name) is active or inactive.

  In Control-M, these resources are converted into manual IN conditions in the format

  [\]resName STAT

  where resName is the name of the resource.

  When the CA-7 Free attribute specifies A (Active), the condition name does not contain a prefix. When the Free attribute specifies I (Inactive), the condition name is prefixed with a '\' to indicate an inverted (negative) condition.

  You must add or delete these manual conditions from the Control-M Resource file when the resource becomes active or inactive.

• A Variable definition

  This is not a required job resource, but rather defines the name of a WLM Scheduling Environment. This is converted to the Control-M SCHENV scheduling parameter.

26. #JI, #JO, and #JEND, #XI, #XO, and #XEND Statements

The CA-7 override statements #JI, #JO, and #JEND, and similarly, #XI, #XO, and #XEND, indicate JCL statements that are to be included, or omitted, based on scheduling criteria.

The Control-M AutoEdit %%IF, %%ELSE, %%ENDIF, %%GOTO and %%LABEL control statements provide a Boolean "IF" logic capability.

The conversion tool converts the #JI, #JO, #JEND, #XI, #XO, and #XEND) statements to corresponding Control-M AutoEdit statements. Only the CA-7 RPT parameter is ignored. The CA-7 ID parameter is converted to the AutoEdit variable %%SCHID which, for scheduled jobs, is derived from the first 3 characters of the Control-M system variable %%$RBC.

The %%$RBC system variable is the Rule-Based Calendar name of the Rule-Based Calendar that causes the job to be submitted. All Rule-Based Calendar names are of the form

sched-ID_head-of-tree-jobname

For non-scheduled, independent (single-purpose) jobs, sched-ID is set to 000.

The CA-7 BD, ED, OA, OB, BT, and ET parameters are converted to the system-defined date and time AutoEdit variables %%[O]YEAR, %%[O]JULDAY, and %%TIME, based on the setting of the CA-7 CV subparameter. %%OYEAR and %%OJULDAY are the conversion results when CV is set to DO or DL. %%YEAR and %%JULDAY are the conversion results when CV is set to CU.

The following examples illustrate how the #JI and #JO override statements are converted.

#JI,ID=(1,5,10,15),BD=97010,ED=97250,OA=0100,OB=1530,
BT=1010,ET=1212

%%IF X%%$RBC NE X
%%SET %%SCHID = %%SUBSTR %%$RBC 1 3
%%ENDIF
%%IF %%SCHID EQ 001
 %%GOTO LABEL0001
 %%ELSE
%%IF %%SCHID EQ 005
 %%GOTO LABEL0001
 %%ELSE
%%IF %%SCHID EQ 010
 %%GOTO LABEL0001
 %%ELSE
%%IF %%SCHID EQ 015
 %%GOTO LABEL0001
 %%ELSE
 %%GOTO LABEL00XX
%%ENDIF
%%ENDIF
%%ENDIF
%%ENDIF
%%LABEL0001
%%IF %%OYEAR.%%OJULDAY GE 97010
%%IF %%OYEAR.%%OJULDAY LE 97250
%%SET %%HHMM = %%SUBSTR %%TIME 1 4
%%IF %%HHMM GE 0100
%%IF %%HHMM LE 1530
 %%GOTO LABEL0002
 %%ELSE
 %%GOTO LABEL00XX
%%ENDIF
 %%ELSE
 %%GOTO LABEL00XX
%%ENDIF
 %%ELSE
 %%GOTO LABEL00XX
%%ENDIF
 %%ELSE
 %%GOTO LABEL00XX
%%ENDIF

%%LABEL LABEL0002
%%IF %%OYEAR.%%OJULDAY EQ 97010
%%SET %%HHMM = %%SUBSTR %%TIME 1 4
%%IF %%HHMM GE 1010
 %%GOTO LABEL0003
 %%ELSE
 %%GOTO LABEL00XX
%%ENDIF
%%LABEL LABEL0003
%%IF %%OYEAR.%%OJULDAY EQ 97250
%%SET %%HHMM = %%SUBSTR %%TIME 1 4
%%IF %%HHMM LE 1212
 %%GOTO LABEL0004
 %%ELSE
 %%GOTO LABEL00XX
%%ENDIF
%%LABEL LABEL0004
 .
 .
 <JCL STATEMENTS>
 .
 .
%%LABEL LABEL00XX

#JO,ID=205-250,BD=97010,ED=98010,CV=CU

%%IF X%%$RBC NE X
%%SET %%SCHID = %%SUBSTR %%$RBC 1 3
%%ENDIF
%%IF %%SCHID GE 205
%%IF %%SCHID LE 250
 %%GOTO LABEL01XX
 %%ELSE
 %%GOTO LABEL0101
%%ENDIF
 %%ELSE
 %%GOTO LABEL0101
%%ENDIF
%%LABEL0101
%%IF %%YEAR.%%JULDAY GE 98010
 %%GOTO LABEL01XX
 %%ELSE
 %%GOTO LABEL0102
%%ENDIF
%%LABEL0102
 .
 .
 .
 <JCL STATEMENTS>
 .
 .
 .
%%LABEL LABEL01XX

27. JCL Job Class

Control-M Quantitative resources based on the JCL job class can optionally be added to job scheduling definitions. This may be required at sites where the CA-7 CLASS parameter is used for job grouping purposes, for example, to limit the number of CICS jobs running concurrently.

If you specified a value other than '  ' (Blank) for the JOBCLAS conversion parameter, which is described in "JOBCLAS" in Conversion Parameters, the conversion tool builds quantitative resource parameters with a quantity of one in the format

JOBCLASS_resource-name[_$]

where

• resource-name is either the user text specified in the JCL Job Class Translation Table or the JCL job class

• $ is a mask character

The exact format of the quantitative resource depends on specifications in the Job Class Translation Table. For details, see Post-conversion Operations.

28. CA-7 Batch Terminal Commands

The following CA-7 Batch Terminal commands are supported:

• The CA-7 DEMAND[H] Batch Terminal command is used to submit special purpose jobs.

• The POST command is used to satisfy the prerequisite conditions of jobs.

• The HOLD and RELEASE commands are used to hold and free the normal scheduling activities of jobs.

• The RESTART command restarts jobs awaiting restart in the request queue.

• The PRSQA command activates a corequisite resource and the PRSQD command deactivates a corequisite resource activated by a PRSQA command.

• In the U7SVC utility, the D=dsn command is used to indicate that the creation of a data set has completed.

The above commands are converted as follows:

• The conversion tool converts CA-7 DEMAND[H] commands to Control-M CTMAPI ORDER commands, to force a job into the Active Jobs file.

• The CA-7 POST commands are converted to IOA IOAAPI ADD COND commands that add conditions to the IOA Conditions file (for the format of the converted conditions, see 19. DEP-JOB).

• The CA-7 HOLD, RELEASE and RESTART commands are converted to Control-M CTMAPI AJF commands HOLD, FREE and RERUN.

• The CA-7 PRSQA commands are converted to IOA IOAAPI ADD COND commands that add conditions to the IOA Conditions file and the CA-7 PRSQD commands are converted to IOA IOAAPI DELETE COND commands that delete conditions from the IOA Conditions file (for the format of the converted conditions, see 25. Virtual Resource Management).

• The U7SVC D=dsn is converted by issuing simulated messages IGD101I/IGD104I (via IOA utility IOATEST), which trigger a predefined CMEM/CTO rule ON-DSNEVENT, as follows:

  Copy

  WTO=IGD101I SMS ALLOCATED TO DDNAME (WORK    )
  WTO=        DSN (' dsn’)
  WTO=IGD104I dsn RETAINED

• Comment statements ('/*') in PDS members or sequential files are also supported.

The only Batch Terminal commands converted are those specified as input to programs and procedures listed in the Batch Terminal input file. For more information, see JOB3 - Convert JCL Members.

The only Batch Terminal commands converted are those in non-concatenated SYSIN, CA7DATA, and UCC7DATA DD statements, with or without a stepname.

Only one Batch Terminal command is recognized in each line, and the command must begin in column 1. It can appear in any one of the following positions:

• in a PDS member

• in a sequential data set

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

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

If Batch Terminal commands appear in the CA-7 PARM parameter on the EXEC statement, only one command is converted, and the whole of that command must be contained in one JCL line.

Unsupported Batch Terminal commands in SYSIN and extraneous DD statements are deleted. PARM parameters that contain unsupported commands are nullified, and EXEC statement parameters that follow the PARM parameter are ignored.

The CTMUTIL utility is the Control-M equivalent of the CA-7 Batch Terminal procedure. CTMUTIL serves as the umbrella procedure for invoking the IOA IOAAPI, and the Control-M CTMAPI and CTMRELRS utilities whenever their functionality is required. For more information on the CTMUTIL utility, see Conversion Parameters.

29. CA-11 Non-Restartable Steps

If Control-M/Restart is installed, the UCC11NR and CA11NR DD statements in CA-11 non-restartable steps are converted to Control-M/Restart CTRNORST DD statements.

30. INSERT-RMS and //*CA-11 Comment Statements

The CA-7 INSERT-RMS job definition parameter indicates whether the CA-11 U11RMS JCL step is to be automatically inserted at execution time by CA-7.

The CA-11 comment statement //*CA-11 is used to override the setting specified by the INSERT-RMS parameter. When the Control-M/Restart is installed, and

• the CA-7 job definition indicates INSERT-RMS=Y

  or

• a CA-11 comment statement in the JCL of a job, before the first EXEC statement, specifies

  Copy

  //*CA-11 INSERTRMS=YES

the AUTO-ARCHIVE, SYSDB, and PREVENT-NCT2 parameters are set to Y, and a DO IFRERUN statement is inserted into the Control-M job scheduling definition.

Specifying //*CA-11 PARM=value causes the conversion tool to process the statement exactly as if a U11RMS step had been encountered. For more information, see the following item.

31. CA-11 U11RMS Step

The CA-11 U11RMS JCL step (RUN HANDLER) uses PARM (or TYPRUN) values in the EXEC statement to control the CA-11 processing mode. When Control-M/Restart is installed, the conversion tool analyzes these PARM values and converts them to the appropriate Control-M/Restart parameters, as detailed in the following paragraphs.

When the value of PARM is set to P(production processing), R(rerun or restart processing), or F(format processing), the following occurs:

• The following Control-M/Restart parameters are set to Y (Yes)

  • AUTO-ARCHIVE

  • SYSDB

  • PREVENT-NCT2

• A DO IFRERUN statement is inserted into an ON PGMST scheduling definition

• When the value of PARM is set to P or F, the DO IFRERUN restart step defaults to $EXERR.

• When the value of PARM is set to R, if startprocstep.startstep and endprocstep.endstep are included in the PARM parameter setting, these are used in the FROM and TO subparameters of DO IFRERUN. The CC=nnnn statement in the PARM parameter is ignored.

• The procedure name to identify the U11RMS step is determined from the PROCRMS parameter of the RESTART statement in the CA-7 Initialization file. Ifthis parameter is not set, a default value of UCC11RMS is used. Ifthis does not agree with the actual CA-11 usage, which is set out in Table21 in the Component Conversion Summary, you must insert the correct PROCRMS value in the RESTART statement before running the conversion.

• When the value of PARM is set to N(null processing), DO IFRERUN is not inserted into the job scheduling definition and the PREVENT-NCT2 parameter is set to N (No) even if the job definition contains the statement INSERT-RMS=Y or a //*CA-11 comment statement is specified earlier in the JCL of the job. For more information, see 30. INSERT-RMS and //*CA-11 Comment Statements.

When the U11RMS step contains the statement PARM=‘R, PSEUDO=YES’, you must set up a Control-M/Restart simulation run. For more information, see the Control-M/Restart User Guide.

In CA-11, the user option module is generated by the U11OPTBL macro, which codes the default return code value issued by CA-11 during rerun (R) processing. If this value is not 0, you must specify the ADDPROC, PROCRC, and NCT2RC parameters in the CTRPARM member of the IOA PARM library. These parameters simulate the action of CA-11 in passing the desired return code to subsequent job steps, and are described in the INCONTROL for z/OS Installation Guide: Customizing. Specify these parameters as follows:

• Set the ADDPROC parameter to the step name specified in the STEPRMS parameter of the RESTART statement in the CA-7 Initialization file, or the default value of CA07RMS.

• Take PROCRC from the U11OPTBL CA-11 macro.

• If you want the Control-M/Restart step to simulate a nonzero return code during the original run of the job for NCT2 processing, specify NCT2RC.

If you use the CA-11 U11VOLCX macro (Volume INCLUDE/EXCLUDE list) or the U11UCSEX exit (Uncatalog/Scratch exit), you must either specify corresponding Control-M/Restart EXCLUDE DSN statements, or Exit 1 (CTRX001) to perform the equivalent function.

If your JCL contains any referbacks to a U11RMS step in the COND parameter of the type COND=(1,NE,UCC7RMS.U11STEP), do the following:

1. Set the ADDPROC, PROCRC, and NCT2RC parameters (as described above).

2. Change the U11STEP step name to IOATEST. This can be done by one of the following methods:

   • change the step name directly in the JCL members, by means of a utility that can make multiple updates

   • use Control-M User Exit 2 (CTMX002) to search the JCL member for EXEC statements containing the string COND=(1,NE,UCC7RMS.U11STEP), and, without physically changing the actual JCL member, change that string on submission to COND=(1,NE,UCC7RMS.IOATEST).

32. NXTCYC SET-OFF

The CA-7 NXTCYC SET=OFF command causes all regularly scheduled processing cycles to be indefinitely suspended until the scheduling indicator is manually reset to SET=ON. Locked jobs are also prevented from processing.

The conversion tool adds a manual IN condition to the Control-M job scheduling definition to prevent the automatic submission of the job. The format of the condition is:

SUSPEND_jobname

where jobname is the Control-M MEMNAME.

33. RESCHNG and #RES

The CA-7 RESCHNG Batch Terminal command is used to change tape drive resources allocated to a job. Similarly, the CA-7 #RES override statement (TP1 and TP2 values) in the JCL member can be used to change the high-water tape drive requirements of the job. The Control-M CTMRELRS procedure can be used to change the quantity of resources allocated to a job.

The conversion tool converts CA-7 RESCHNG JCL Batch Terminal Step operations and #RES override statements to Control-M JCL steps that change quantitative resources allocated to a job. For more information, see 11. TYPE1 and TYPE2, and Workload Balancing.

RESOURCE quantities for a job, previously determined by the TYPE1 and TYPE2 parameters in the CA-7 job definition, are overridden by the CTMRELRS step.

The same conversion restrictions that apply to the DEMAND and POST commands, which are described in 28. CA-7 Batch Terminal Commands, also apply to the RESCHNG command.

35. OWNER

Identifies the Control-M user ID in the table.

The USEROPT conversion parameter specifies the source from which the OWNER parameter is to be taken. For more information, see "USEROPT" in Conversion Parameters.

The USERLEN conversion parameter specifies the number of characters to be used in the OWNER parameter. For more information, see "USERLEN" in Conversion Parameters.

subuser\domain

36. SCHID

The CA-7 SCHID parameter provides a method of varying scheduling requirements, job triggers, JCL overrides, and so on, for the same job.

Within Control-M, a job in a SMART Table can be assigned different sets of basic scheduling criteria by means of Rule-Based Calendars. For each CA-7 SCHID assigned to a job, the conversion tool creates a Rule-Based Calendar in the SMART Table Entity of the SMART Table. The name of the Rule-Based Calendar is in the format

schedule-ID_head-of-tree-jobname[_n]

where n is an integer and indicates that a supplemental Rule-Based Calendar had to be created for the same CA-7 scheduling criteria.

This occurs when the CA-7 scheduling criteria are so complex that a single Control-M Rule-Based Calendar is insufficient, for example, where the conversion of CA-7 scheduling criteria requires

• both Control-M DAYS and DATES parameters

• both Control-M periodic and non-periodic parameters

• more than 12 Control-M DATES parameters

Each Rule-Based Calendar is then placed into the appropriate job scheduling definition.

The Control-M %%$RBC AutoEdit system variable contains the name of the RBC that causes the job to be scheduled. When the CA-7 JCL of a job contains CA-7 JCL override statements in the format

#JI,ID=...

the conversion tool converts these statements to Control-M AutoEdit statements, transforming the ID subparameter into the %%SCHID AutoEdit variable as follows:

%%SET %%SCHID = %%SUBSTR %%$RBC 1 3

This extracts the first three characters of the CA-7 SCHID RBC. For an example, see 26. #JI, #JO, and #JEND, #XI, #XO, and #XEND Statements.

In the following instance, the %%$RBC variable is not used to derive a value for %%SCHID in the converted JCL:

• When the CA-7 SCHID of a job is changed from nnn to mmm by means of the statement SCHID=nnn/mmm in the TRIGGERED JOBS section of the LJOB report, the Control-M SET VAR AutoEdit variable %%CHG_SCHID is set to the changed SCHID (mmm). In the JCL conversion of the corresponding JCL members, ensure the proper resolution of %%SCHID by using the following code:

  Copy

  %%RESOLVE NO
  %%IF %%CHG_SCHID GE 0
       %%SET  %%SCHID = %%CHG_SCHID

37. JCL Initialization Statement

The ALT parameter of the CA-7 JCL Initialization Statement enables you to define alternate libraries to be searched prior to searching the primary JCL library specified in the DSN parameter. ALT is a number from 000 through 253 that specifies the index value from another initialization file JCL statement.

The conversion tool specifies the CA-7 Alternate JCL library name using the Control-M OVERLIB job scheduling definition parameter.

A value of DUMMY overrides the alternate JCL library name specified in the OVERLIB parameter when EXEC is set to N. For more information, see 8. EXEC.

The ALT on the JCL Initialization statement is ignored if the JCLLIB field specifies a symbolic JCL variable. For details, see 43. JCLLIB.

38. SHOUT

Causes specific messages to be sent by Control-M ("shouted") to predetermined destinations on predefined occasions.

The conversion tool supports the following situations:

Table 27 Occasions for SHOUT Messages

The SHOUTT conversion parameter specifies the SHOUT message text for failed jobs. The default is

%%JOBNAME J%%JOBID ENDED NOTOK!

The SHOUTL conversion parameter specifies the SHOUT message text for jobs submitted late. The default is

MEMBER %%JOBNAME IS LATE!

The SHOUTE conversion parameter specifies the SHOUT message text for jobs that are still executing after their DUE OUT time. The default is

%%JOBNAME J%%JOBID STILL EXECUTING AFTER DUE OUT!

In these SHOUT messages, %%JOBNAME and %%JOBID are the AutoEdit variables in which the name of the submitted job and the JES job number are placed. If a job name cannot determined then the JCL member name of the job to be submitted is used instead.

When SHOUTT or SHOUTL or SHOUTE are left blank, the corresponding SHOUT messages are suppressed. Various computer personnel can be specified as the Control-M SHOUT destination. For more information, see the Control-M for z/OS User Guide.

The SHOUTDT and SHOUTDL conversion parameters specify the destination of the SHOUT message texts for failed and late jobs respectively. The conversion tool accesses the user ID from the USEROPT conversion parameter, which is discussed in "USEROPT" in Conversion Parameters.

39. CMEM Rule Table

For details on how the conversion tool converts CA-7 data set triggering, see Control-M Event Manager.

40. MAINID

The CA-7 MAINID parameter specifies on which mainframe CPU a job may or may not be scheduled or the distributed platform on which the job should run.

For mainframe jobs, the following guidelines apply:

To display a list of all the CA-7 MAINID specifications that are assigned to the CA-7 SUBMIT data sets or internal reader, use the following CA-7 command:

/DISPLAY,CPU=ALL

The user must supply an AutoEdit translation table that associates a system ID with each MAINID as described in Post Step 1. Customize Control-M and Install User Exits.

The conversion tool converts MAINID in the format SYn or /SYn by creating a %%n AutoEdit variable in the Control-M SYSTEM ID parameter in the job scheduling definition.

The JCL of jobs that require system affinity is then modified by Control-M by inserting one of the following JES statements before the first step:

/*JOBPARM SYSAFF=%%n (for JES2)

//*MAIN SYSTEM=%%n (for JES3)

The %%n AutoEdit variable is resolved from the AutoEdit cache member created in Post Step 1. Customize Control-M and Install User Exits.

MAINID specifications of the form /SYn, meaning do not schedule on system n, are only supported for JES3 systems. The %%n AutoEdit variable then takes the form /%%n.

For additional information, see Network Communications Facility.

For distributed jobs:

The following MAINID distributed platforms are supported by the conversion: WIN, FTP, SAP, UNIX, PS (PeopleSoft), OS40 (AS400), FTRG (file-triggering), and BWPC (SAP Business Warehouse). The following are passively supported only: OMDK (On-line Disk Monitor), NSTP (Non-stop jobs), OMEL (Eventlog Monitor), and OMPM (Process Monitor).

For these platforms, the JCL member that corresponds to the job definition may contain a leading #7UNI statement and it is processed as described in 51. #7UNI.

If the JCL member does not contain a #7UNI statement and the PNIBTSD conversion has been set to 'X', the conversion will search the member for certain keywords and convert them as follows:

• CMDNAME, COMMAND, and SCRIPTNAME — converted same as SUBFILE, as described in 51. #7UNI.

• ARGS — converted same as PARMnn statements, as described in 51. #7UNI. Multiple argument values and arguments continued on multiple lines are supported.

• AGENT — converted same as NODE, as described in 51. #7UNI.

• USER — converted same as SUBUSER, as described in 51. #7UNI.

• ENVAR — converted same as PARMnn, as described in 51. #7UNI, except that the ENVAR parameter name (ENVAR parameter-name=parameter-value) replaces the PARMnn. Any delimiters (quotes or apostrophes) surrounding the parameter value are removed.

  When the ENVAR parameter name is STDOUT, the conversion creates the following additional Control-M statement. This statement causes the STDOUT output to be copied to the filename specified as the ENVAR parameter value.

  Copy

  ONPGM,STEP=ANYSTEP,CODES=OK
  DO=SYSOUT,SYSOUT-OP=F,SYSOUT-PRM=%%STDOUT

  When the ENVAR parameter name is STDERR, the conversion creates the following additional Control-M statement. This statement causes the STDERR output to be copied to the filename specified as the ENVAR parameter value.

  Copy

  ONPGM,STEP=ANYSTEP,CODES=NOTOK
  DO=SYSOUT,SYSOUT-OP=F,SYSOUT-PRM=%%STDERR

• FILENAME — a File Watch er job is created with the specified file name. All other sub-parameters are ignored.

• EXITCODE statements are ignored.

For PS, SAP, FTP, or BWPC jobs, the PNIBTSD conversion must be set to 'X', and the conversion scans the JCL member for platform-specific parameters and converts them to the corresponding Control-M SETVAR parameters, as follows:

Table 27a Conversion of Statements in PS Jobs

All the Control-M parameters are created as SETVARs with the prefix %%PS8-.

Table 27b Conversion of Statements in FTP Jobs

For SAP and BWPC supported parameters see 51. #7UNI.

42. JES ROUTE PRINT

When the JESRPRT conversion parameter is set to Y, as discussed in "JESRPRT" in Conversion Parameters, the conversion tool searches the JCL member of each job for JES ROUTE PRINT new-dest statements and converts them to Control-M SYSOUT post-processing parameters in the format:

SYSOUT   OP   N   new-dest

where

• N specifies that the held output destination of the job is to be changed to new-dest

• new-dest is the first eight characters of the destination parameter specified on the JES ROUTE PRINT statement

The JES ROUTE PRINT statement is deleted from the JCL run stream.

43. JCLLIB

The CA-7 JCLLIB is a symbolic variable that identifies the JCL library for a particular job. The JCL variables and corresponding library names are contained in the CA-7 JCL Library Variables report.

When a job’s LJOB definition does not contain a JCLLIB field or the JCLLIB specifies '*NUMERIC JCLID*', the JCL library name is determined by the JCL ID and the Initdeck (see 2. JCLID). The conversion tool specifies the CA-7 JCL library name in the MEMLIB Control-M job scheduling definition parameter and searches in that library for the member when the job’s JCL must be processed. If the JCLLIB of a job does not correspond to any JCL variable in the report, the MEMLIB parameter is set to 'NON-EXIST-JCLLIB'. If the member is not found in the indicated JCL library, then the Alternate Library, if one is specified, is searched.

The JCLLIB parameter is not used for non-executable jobs, that is, when EXEC is set to N in the CA-7 JOB screen.

44. DEP-JOB=?

The CA-7 DEP-JOB job connection parameter can be used to specify a job name preceded by ? (question mark). This type of job name indicates a conditional job dependency. Conditional job dependencies work as follows.

If Job A is conditionally dependent on Job B, the execution of Job A depends on Job B only if Job B is in the Request, Ready or Active queue when Job A enters the Request queue.

The Control-M ADJUST CONDITIONS parameter determines how Control-M processes a requirement for a prerequisite condition by successor jobs in a SMART Table. To handle conditional job dependency, the conversion tool sets this parameter to Y which instructs Control-M to ignore, for each job in the group, any IN prerequisite condition that is added by a predecessor job that will not be ordered during the current day. For more information, see ADJUST CONDITIONS.

In addition to the ADJUST CONDITIONS feature, the Control-M Maybe Jobs feature can also be used to simulate this "conditional handling" of predecessor prerequisites. For more information, see the discussion of Maybe Jobs in the Control-M for z/OS User Guide.

The conversion tool facilitates use of the Maybe Jobs feature by creating IN conditions in the following format:

?jobname_dep-jobname_OK ODAT

where

• jobname (the predecessor job name, on which dep-jobname is dependent) is the Control-M MEMNAME of the predecessor job

• dep-jobname (the successor job name) is the Control-M MEMNAME of the successor job.

This format enables the ADDMNCND KSL utility script to use the special character "?" (hexadecimal 6F) to recognize conditions of this type. For more information on the ADDMNCND utility script, see the Keystroke Language chapter of the Control-M for z/OS User Guide.

For more information on job connection dependencies, see 19. DEP-JOB.

45. DONT SCHEDULE BEFORE/AFTER

CA-7 DONT SCHEDULE BEFORE and DONT SCHEDULE AFTER parameters are used to set dates and times before and after which a job must not be scheduled.

The conversion tool converts DONT SCHEDULE BEFORE and DONT SCHEDULE AFTER parameters to Control-M DEFINITION ACTIVE FROM and DEFINITION ACTIVE UNTIL values in the relevant job scheduling definitions.

Dates are converted into the Gregorian format using a 2-digit year. The precise date format that is applied depends on the value specified for the IOA DATETYP installation parameter.

Upon conversion, the values in CA-7 DONT SCHEDULE BEFORE and DONT SCHEDULE AFTER parameters are inserted into the DEFINITION ACTIVE FROM or DEFINITION ACTIVE UNTIL parameters respectively of both the job being converted and any of its dependent jobs which do not already have any values specified in those parameters.

46. #HLD

The CA-7 JCL #HLD override statement specifies that the job must be held.

The conversion tool converts the #HLD override statement to the following IOA IOATEST utility step:

// EXEC IOATEST,PARM=‘WTOR=JOB %%JOBNAME IS HELD’

This step causes the job to wait for an operator reply until the HOLD can be removed.

47. #NOX

The CA-7 #NOX override statement in the JCL member indicates that the job must not be executed.

The conversion tool converts the #NOX override statement to the following JCL and Control-M AutoEdit statements:

//#NOX EXEC PGM=IEFBR14
//*   %%GOTO END999

and at the end of the member adds the following AutoEdit statement:

//* %%LABEL END999

This has the effect of turning the job into a dummy job.

48. #MSG

The CA-7 #MSG override statement in the JCL member is used to send messages to the CA-7 Master Station at job submission time.

The conversion tool converts the #MSG override statement to the following IOA IOANOTE utility step:

// EXEC IOANOTE,PARM=‘message-text’

The first 48 bytes of the message text are placed into the PARM parameter.

49. #VER

The JCL CA-7 #VER override statement specifies that the job requires manual verification.

The conversion tool converts the #VER override statement to the following IOA IOATEST utility step:

// EXEC IOATEST,
// PARM=’WTOR=JOB %%JOBNAME REQUIRES MANUAL VERIFICATION’

This causes the job to wait for any operator reply after the manual verification has been satisfied.

50. ARFSET and #ARF

The ARFSET parameter in the CA-7 JOB screen is an optional parameter that names an ARFSET, which specifies a set of automated recovery criteria that should be activated for the job. This can be overridden using the #ARFSET statement in the JCL. Both of these designations can be overridden using the ARFSET keyword on the DEMAND[H] command.

The conversion tool converts the ARFSET and #ARF override statement by incorporating the ARFSET's automated recovery actions into the job's scheduling definition. Refer to Conceptual Overview for full details.

If a CA-7 job definition specifies a set of automated recovery criteria via an ARFSET parameter, the MAXRERUN and DO IFRERUN parameters which would normally be created in the job scheduling definition if Control-M/Restart is installed, are suppressed to prevent the possible conflicts.

51. #7UNI

The #7UNI JCL Override statement flags JCL to be used to send work to Unicenter TNG. When the Conversion tool encounters the #7UNI statement in a JCL member, the corresponding job definition is treated as a distributed job and the parameters listed in this section, which are extracted from the JCL member (in a SYSIN in-stream file, a PDS member, or a sequential file) or from the CA-7 Profile library, member CACCENV, are processed.

SUBUSER, DOMAIN

See 35. OWNER for details.

NODE

The NODE statement 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 NODE name.

SUBFILE

The SUBFILE statement identifies the Agent-platform command to run when defining jobs for the Agents running on non-z/OS platforms. The SUBFILE statement may span multiple 80-byte input lines, which are concatenated to form the full directory/path name. The conversion tool converts the SUBFILE as follows:

• If the Subfile contains both a directory path and a program name, then the conversion will set the Control-M MEMNAME to the program name and the MEMLIB to the directory path.

• If the Subfile (CMDLINE) contains only a program name without any directory path, then the Control-M TASKTYP is set to 'command' and the conversion builds a Control-M CMDLINE parameter consisting of the progam name followed by %%PARMn (n=1-9) for as many PARMs as necessary.

• If the command string is very long, the conversion will break the string into multiple SETVAR AutoEdit variables, %%0, %%1, %%2, %%3, and %%4 and the CMDLINE parameter is then set to %%0.%%1.%%2.%%3.%%4.

PARMnn

The PARMnn (nn ranging from 1-64, values 1-256 characters) optional parameters supply values to be used on the distributed platform. If a PARMnn statement spans multiple 80-byte input lines, the conversion tool converts them to Control-M AutoEdit job submission variables, %%PARMnn. If the PARM value is very long the conversion will break the string into multiple SETVAR auto-edit variables, %%5, %%6, %%7, %%8, and %%9 and the PARMnn parameter is then set to %%5.%%6.%%7.%%8.%%9.

For SAP jobs, the values specified in the PARMnn statements are scanned for SAP-specific switches or parameters and are converted to the corresponding Control-M SAP SETVAR parameters, as follows:

Table 27c Conversion of PARMnn Statements in SAP Jobs

All the Control-M parameters are created as SETVARs with the prefix %%SAPR3-STEP-S01-

52. LAST-RUN DATE/TIME

The CA-7 LAST-RUN DATE/TIME value is converted into the Control-M SETVAR %%$LASTRUNDT auto-edit variable.

58. Global Parameters

CA-7 global variables that are identified by the special prefix designation specified in the LGVAR report are automatically converted to Control-M auto-edit format (%%variable-name).

For mainframe jobs, this conversion is performed when converting the CA-7 JCL libraries.

For distributed (non-mainframe) jobs, see step 12 in Post Step 3. Check Conversion Results for details.

59. CA-DRIVER Variable Parameters

CA-DRIVER variable parameters are converted to Control-M %% AutoEdit variables. When a CA-DRIVER variable contains a substring reference, it is converted to an AutoEdit %%SUBSTR function when referenced in DSET CA-DRIVER commands.

Array type CA-DRIVER variables are also supported.

The CA-DRIVER Reserved-Name Variable parameters in the following table are supported when referenced in CA-DRIVER DIF and DSET commands. Entries in the Note No. column refer to the notes that follow the table.

All these variables are translated in the DAYMONTH AutoEdit Global Definition member. For more information, see Post Step 2. Perform Final Adjustments.

Table 28 Supported CA-DRIVER Reserved-name Variables

Unique Control-M Parameters

Several unique Control-M job scheduling definition parameters that do not have corresponding CA-7 features can be set by the conversion tool during the creation of the Control-M tables.

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

CATEGORY

This Control-M parameter specifies the Control-D report decollating mission category that must be scheduled under Control-D when the job is scheduled under Control-M. This option is only available if Control-D is installed at your site. For more information, see the description of the D-CAT parameter in the Control-M for z/OS User Guide.

If you use the DCTGRY conversion parameter, which is described in "DCTGRY" in Conversion Parameters, the conversion tool specifies the CATEGORY parameter in the job scheduling definition of relevant jobs. This specifies the unique character string in the CA-7 JCL that precedes, and so identifies the existence of, the Mission Category. When the conversion tool finds this character string in the JCL, the characters following the string (up to 20) are entered in a CATEGORY basic scheduling parameter.

For example, if the character string is //*CTDMC=, the following statements in the CA-7 JCL

//*CTDMC=XYZ
//*CTDMC=DAILY

respectively specify mission categories ‘XYZ’ and ‘DAILY’.

The conversion tool can optionally define an OUT condition, to be used in Control-D processing, in the job scheduling definition of any job for which a CATEGORY scheduling parameter is specified. For more information, see "CTDCOND" in Conversion Parameters.

The format of the condition is

jobname-usertext     ODAT+

The variable jobname is the Control-M MEMNAME of the job, and the variable usertext is specified in the CTDCOND conversion parameter.

For example, if the value specified in CTDCOND is '-ENDED-OK' and the job scheduling definition of the ABC job has a CATEGORY parameter, then the OUT condition

ABC-ENDED-OK   ODAT+

is placed in the job scheduling definition of the ABC job.

DO SYSOUT

This Control-M parameter specifies how the job output is to be 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 MSGCLASS JCL parameter of the job at time of submission to the automatically held output class defined during installation, the Control-M HLDCLAS parameter. After analyzing the sysout, Control-M can 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 TOCLASS conversion parameter specifies the output class to which Control-M requeues the job output. For more information on this parameter, see "TOCLASS" in Conversion Parameters.

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 this parameter, see "RELEASE" in Conversion Parameters.

The FROMC conversion parameter specifies which of the held sysout classes must be requeued. For more information on this parameter, see "FROMC" in Conversion Parameters.

ADJUST CONDITIONS

For jobs running on Control-M distributed platforms, the Control-M/Server CTM_GROUP_ADJUST_DUMMY configuration parameter controls the creation of dummy jobs that run in place of unscheduled prerequisite jobs, as follows:

• Y: a dummy job waits for the prerequisite conditions expected by the job it is replacing, and performs the post-processing of the job.

• N: Out conditions of the jobs that were not ordered are ignored by the ordered jobs in the SMART Table. Default.