Conversion Details

This appendix includes the following topics:

• Overview of Conversion Details

• Component Conversion Summaries

  • 1. Job Name

  • 2. Appl ID and Job Grouping

  • 3. Owner ID

  • 4. Data Dependencies

  • 5. Operation Dependencies

  • 6. Manual Workstations

  • 7. Workstation Resources, Workstation Servers

  • 8. Run Cycle (Offset-Based)

  • 9. Calendars, Periods (Offset-Based Run Cycles)

  • 10. Arrival-Time, Deadline

  • 11. Priority

  • 12. Operator Instructions

  • 13. SEARCH and TABLE Directives

  • 14. FETCH Directive

  • 15. BEGIN and END Directives

  • 16. &, %, and ? Variables (for OPC/ESA Only)

  • 17. SRSTAT

  • 18. Started Task Option (for OPC/ESA Only)

  • 19. DESCRIPTION

  • 20. Automatic Submission Option (for OPC/ESA Only)

  • 21. DEADLINE WTO Option (for OPC/ESA Only)

  • 22. ERROR TRACKING Option

  • 23. Catalog Management (for OPC/ESA Only)

  • 24. SCAN Directive

  • 25. OPSTAT

  • 26. Highest Return Code – HRC (for OPC/ESA Only)

  • 27. Rule/Period Name

  • 28. Suppress If Late

  • 29. Run Cycle Valid From and To

  • 30. //*%IJ, //*%1V, //*%1S (PSS only)

  • 31. //*%2V, //*%2S (PSS only)

  • 32. %Snnx (PSS Only)

  • 33. //*%IP (PSS Only)

  • 34. %-variables (PSS)

  • 35. Group Definition

  • 36. Workstation Destination

  • 37. SETFORM/SETVAR Directives

  • 39. EQQJCCT Macro

  • 40. RECOVER Directive

  • 41. ADRULE, REPEAT, and SHIFT (Rule-Based Run Cycle) (for OPC/ESA Release 3 and Later Only)

  • 42. Duration Time

  • 43. WAIT Workstation Option

  • 44. AUTOMATION Workstation Option

  • 45. Distributed Job Scripts/Parameters

  • 46. WTO Workstation Option

  • 47. WSSTAT

• Unique Control-M and Control-M/Restart Parameters

  • AUTO-ARCHIVE

  • DO SYSOUT

  • SHOUT

  • ADJUST CONDITIONS

Overview of Conversion Details

This section details the conversion of relevant OPC parameter definitions and JCL to corresponding Control-M job scheduling definition and AutoEdit parameters, and also describes unique Control-M and/or Control-M/Restart parameters that may be specified for the conversion.

Component Conversion Summaries

The tables below list OPC parameters and JCL directives and parameters that are found in application definitions, and the corresponding Control-M statements to which they are converted. Following the tables is a detailed explanation of how each field is converted.

Table 10 Job Schedule Definition Conversion

Table 11 JCL LIbrary Conversions

Table 12 PSS Special JCL Statements Conversion

Table 13 OPC Macros

1. Job Name

The conversion tool converts the OPC job name to the Control-M MEMNAME parameter.

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

For OPC manual operations, that is, for non-computer workstations, when an OPC job name does not exist, the MEMNAME is formed according to the following format:

workstation-name#operation-number

• %%OOPNO=job’s operation number.

• %%OWSID=job’s workstation id.

2. Appl ID and Job Grouping

The conversion tool converts each OPC application to one Control-M SMART Table. The Control-M table name is created from the OPC application ID, which may be changed manually during the conversion process. Tables are members of a partitioned data set (PDS) library. Therefore, all application names must be unique and valid PDS member names. For more information, see "DELCHAR" and "TBLUNIQ" in Conversion Parameters.

The OPC application ID (unchanged) is also used to determine the Control-M GROUP and APPL job scheduling parameters. For more information on Group Scheduling, see Application Definition and Control-M SMART Table Scheduling.

3. Owner ID

An owner ID is assigned to each application. This field may be used for security in Control-M. The Control-M OWNER is the OPC application owner ID. During the conversion process, you can change the owner ID, as described in JOB1: Extract Workstation and Application Info. For fault-tolerant jobs, the Control-M OWNER is determined by the JOBUSR parameter, if present in the job definition.

4. Data Dependencies

Resources in OPC are converted under Control-M to the following elements:

• Control resources in the format resource-name where resource-name is taken from the special resource name defined in OPC. The held status is the same as required in OPC: S (shared) or E (exclusive). If the OPC 'Keep on error' indicator is set (indicating the operation keeps the resource when it fails), then the Control-M OnFail Keep indicator (K) is set. Special resources with names containing more than20 characters are converted to unique 20-character Control resource names.

• IN conditions, when the SPECCND conversion parameter, described in "SPECCND" in Conversion Parameters, is set toY. The condition name is the same as the resource name. This condition is present in the IOA Conditions file whenever the resource is available. As in OPC, the first time you use Control-M after installation, you must inform the system that the resource is available. You can do this by running the JCL in the CONDITION LIST TO BE ADDED file (the IOACOND job).

  Whenever the resource becomes unavailable because a job ends NOTOK, Control-M automatically deletes the prerequisite IN condition that represents the special resource. This occurs only if the resource is exclusively held for the job. The SPECCND conversion parameter, described in "SPECCND" in Conversion Parameters, controls whether the conversion program creates the tables with this capability. You must determine the value of SPECCND by reference to the ONERROR parameter of the OPC JTOPTS initialization statement.

• Quantitative resources - For more information, see Data Dependencies.

5. Operation Dependencies

The format of Control-M IN and OUT condition names created from OPC operation dependencies is

predecessorapplname-jobname_successorapplname-jobname date-ref

where

• predecessorapplname is the new application name to which the OPC predecessor job belongs.

• successorapplname is the new application name to which the corresponding OPC successor job belongs (see Table 6).

As in OPC, Control-M can differentiate between internal and external dependencies. Internal dependencies are established for operations in the same application, which are ordered on the same day, by specifying IN or OUT conditions using the ODAT date-ref value, which is the date on which the job was ordered. For external dependencies between applications, since the applications can be ordered on different dates, their IN conditions are created using the date-ref **** (any date). However, an external predecessor of an operation, which specifies the operation itself or another operation within the same application, is converted to an IN condition with a date-ref of PREV, rather than being treated as an external condition with a date-ref of ****.

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

IN conditions of a job are deleted upon the successful completion of the job regardless of whether they originally represented internal or external prerequisites.

6. Manual Workstations

Manual operations (PRINT and GENERAL workstations) are converted to dummy job schedules that wait for manual IN conditions. For more information, see "MANLCND" in Conversion Parameters.

If the manual operation does not have a job name associated with it, the dummy job schedule name format is:

workstation#operation-number

The condition name format is:
wstype_workstation-name_application-name_operation-number
where wstype is either a P (PRINT) or G (GENERAL workstation).

7. Workstation Resources, Workstation Servers

The number of parallel servers (PS), R1, and R2 workstation resources required by an OPC operation are shown in the Operation Data section of the Application report. The conversion tool converts these resources to Control-M Quantitative resources using the respective quantities from the Application report.

The format of the server Quantitative resource is:
workstation-name_SERVER

The format of the R1 and R2 workstation Quantitative resources is:
workstation-name_resource-name
where workstation-name and resource-name are taken from the Workstation report.

The conversion forces every job in Control-M to require at least one server Quantitative resource, even if the OPC job did not require a server. This enables implementation of "closed" workstations in Control-M. To close the workstation, set the server resource quantity to 0 in the Control-M Resources file.

If the Control parameter in OPC for the server resource is NO, the conversion sets the quantity of this resource to 9999.

8. Run Cycle (Offset-Based)

The conversion tool will convert the Offset-based freeday rules and offsets to standard Control-M RBCs with scheduling criteria as follows:

Note that the above applies to both NORMAL and NEGATIVE run-cycles which are converted to regular and Exclude RBCs respectively.

OPC calendars, periods and free-day rules are translated to Control-M composite calendars only, when it is not possible to convert them to standard Control-M scheduling criteria.

The above OPC/Control-M parameter equivalencies do not apply when:

• A run cycle specifies an offset greater than +62 or less than -62.

• An application specifies multiple run cycles and with Freeday 4 (with offset not +001) and some other Freeday rule.

In such cases the run cycles are converted by creating an RBC with just a DCAL=composite-cal.

The different types of calendars created by the conversion (base, period, composite) are described below in item 9. Calendars, Periods (Offset-Based Run Cycles).

The conversion process creates a file that contains OPC RUN CYCLE information, such as the new calendar name, period, offsets, and free-day rule for each OPC calendar. The new calendar is used by Control-M. An OPC application can be defined with a number of different run cycles. Each run cycle defines different scheduling criteria. For details about how this is handled by the conversion tool, see 27. Rule/Period Name.

9. Calendars, Periods (Offset-Based Run Cycles)

OPC calendars and periods are translated into Control-M calendars.

The sequence of stages in the calendar conversion process is shown below.

1. OPC calendars are translated to Control-M work and free day calendars that contain a Y for each working day and are called base calendars. OPC periods are translated to Control-M calendars that contain a Y for each day that was specified in the period definition and are called period calendars. Scheduled days in the OPC Period Report are defined according to the Interval Origin date and the Interval End date. When an Interval End date is specified, then all the days in the range between the Origin and End date are considered scheduled days.

   For NONCYCLIC Periods, if no Interval End date is specified, then it is assumed as the next Interval Start Date minus one day. As a result, all the days in the range between the Interval Start date and the next Interval Start date minus 1 day are considered scheduled days. If no End Date is specified for the last Interval, only the Interval Start Date is considered as a scheduled day.

2. A calendar is created for each RUN-CYCLE. The run days in the calendar are calculated as follows:

   1. For each day that was specified in the period, the conversion tool adds the OFFSETS that were defined in OPC and marks them in the Control-M calendar with an appropriate sign. The appropriate sign is determined by the OPC free day rule, as shown in the following table.

      Table 14 Control-M Free Days Values

      Sign	Description
      + or -	Schedule the start day on the closest work day after or before the free day.
      Y	Schedule the start day on the specified free day. This is a final calendar.
      N	Do not schedule the start day if it occurs on the specified free day.

      When free days are excluded, only work days are taken into account in calculating where to place the appropriate sign.

      The calendar names that are created at this stage end with a non-numeric character (}, J-R).

   2. If a free day rule cannot be converted to standard Control-M scheduling criteria, the IOABLCAL utility is invoked to create a final calendar, called a composite calendar, by combining the Control-M working day calendar created in stage1 with the run cycle calendar created in stage 2.A. For details of the IOABLCAL utility, see the INCONTROL for z/OS Utilities Guide.

3. If the application has both NORMAL and NEGATIVE run cycles which cannot be converted to Control-M standard scheduling criteria, the conversion executes the IOABLCAL utility to create a final (composite) calendar, by logically subtracting all the NEGATIVE calendars created in stage 2 from the NORMAL calendars. For details of the IOABLCAL utility, see the INCONTROL for z/OS Utilities Guide.

4. Resultant calendars are placed into the Control-M DCAL and CONFCAL parameters. You can change this by editing the Calendar Names files, which are described in JOB1: Extract Workstation and Application Info. For an exception to this rule, see 29. Run Cycle Valid From and To.

5. Additional periodic calendars are created for use (if required) in rule-based run cycle conversions. The names of these additional calendars end with a non-numeric character ({, A-I).

   For more information, see 41. ADRULE, REPEAT, and SHIFT (Rule-Based Run Cycle) (for OPC/ESA Release 3 and Later Only).

Examples

The following examples are based on an OPC base calendar (CAJALEON) (see Table 15) that is converted to a Control-M calendar (CAJA000) and three periods (SEMANAL, DIARIO and MENSUAL) all of which are defined below. Three OPC applications (AA, BB and CC) are shown below with their relevant offset-based run cycles. The Control-M calendars that are created for the SCHEDULE RBC in the Control-M job scheduling definition for these application are shown and explained below.

Table 15 OPC Base Calendar - CAJALEON

The free days shown in Table 16 are used to determine the scheduling of days according to the free-day rule.

Table 16 Free Days

The Control-M base calendar created for CAJALEON is shown in Figure 2. It is based on the Default Status for Monday to Sunday, shown in Table 15, and the free days, shown in Table 16. Note that the days marked 'N' are free days.

Figure 2 Control-M Base Calendar - CAJA000

Y2007
M01NYYYY  YYYYY  YYYYY  YYYYY  YYY
M02YY  YYYYY  YYYYY  YYYYY  YYY  
M03YY  YYYYY  YYYYY  YYYYY  YYYYY
M04 YYYYY  YYYNN  YYYYY  YYYYY  Y
M05NYYY  YYYYY  YYYYY  YYYYY  YYYY
M06Y  YYYYY  YYYYY  YYYYY  YYYYY 
M07 YYYYY  YYYYY  YYYYY  YYYYY  YY
M08YYY  YYYYY  YYNYY  YYYYY  YYYYY
M09  YYYYY  YYYYY  YYYYY  YYYYY  
M10YYYYY  YYYYN  YYYYY  YYYYY  YYY
M11NY  YYYYY  YYYYY  YYYYY  YYYYY
M12  YYYNY  YYYYY  YYYYY  YNYYY  Y

The SEMANAL period described in Table 17 is converted to the Control-M period calendar shown in Figure 3.

Table 17 SEMANAL Period

Figure 3 SEMA258 (Every 7th Day)

Y2007            SEMANAL ORIGEN LUNES
M01      Y      Y      Y      Y      
M02   Y      Y      Y      Y         
M03   Y      Y      Y      Y         
M04Y      Y      Y      Y      Y     
M05     Y      Y      Y      Y       
M06  Y      Y      Y      Y          
M07Y      Y      Y      Y      Y     
M08    Y      Y      Y      Y        
M09 Y      Y      Y      Y      Y    
M10      Y      Y      Y      Y      
M11   Y      Y      Y      Y         
M12 Y      Y      Y      Y      Y

The DIARIO period described in Table 18 is converted to the Control-M period calendar shown in Figure 4.

Table 18 DIARIO Period

Figure 4 DIAR048 (All Days)

Y2007            TODOS LOS DIAS LABORABLES
M01YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
M02YYYYYYYYYYYYYYYYYYYYYYYYYYYY
M03YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
M04YYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
M05YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
M06YYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
M07YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
M08YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
M09YYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
M10YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
M11YYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
M12YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY

The MENSUAL period described in Table 19 is converted to the Control-M period calendar shown in Figure 5.

Table 19 MENSUAL Period (MENS179 - See Below)

Figure 5 MENS179 (First Day of Month)

Y2007            MENSUAL ORIGEN DIAS UNO
M01Y
M02Y
M03Y
M04Y
M05Y
M06Y
M07Y
M08Y
M09Y
M10Y
M11Y
M12Y

Figure 10 SEM260 (SEMANAL NORMAL 001, MENSUAL NEGATIVE 001 002 003 -003 -002 -001 AFTER)

Y2007  SEMA259   - $NEG1     = SEMA260
M01       Y      Y      Y
M02           Y      Y
M03           Y      Y      Y
M04        Y      Y      Y
M05      Y      Y      Y      Y
M06          Y      Y      Y
M07        Y      Y      Y
M08     Y      Y      Y      Y
M09         Y      Y      Y
M10       Y      Y      Y
M11           Y      Y      Y
M12         Y      Y      Y

The $NEG1 calendar is built from the MENSUAL period (1st day of month) and hence excludes the 1st, 2nd, 3rd, last, next to last, and 2nd next to last days of the month from the SEMA259 calendar shown in Figure 11.

Figure 11 SEMA259

Y2007  CAJA000   * $SEMA259  = SEMA259
M01       Y      Y      Y      Y
M02    Y      Y      Y      Y
M03    Y      Y      Y      Y
M04 Y      Y      Y      Y      Y
M05      Y      Y      Y      Y
M06   Y      Y      Y      Y
M07 Y      Y      Y      Y      Y
M08     Y      Y      Y      Y
M09  Y      Y      Y      Y
M10Y      Y      Y      Y      Y
M11    Y      Y      Y      Y
M12  Y      Y      Y      Y      Y

Figure 12 is the SEMANAL calendar (SEM258) converted into a relative calendar for free day AFTER processing.

Figure 12 $SEM259

Y2007            SEMANAL ORIGEN LUNES
M01      +      +      +      +
M02   +      +      +      +
M03   +      +      +      +
M04+      +      +      +      +
M05     +      +      +      +
M06  +      +      +      +
M07+      +      +      +      +
M08    +      +      +      +
M09 +      +      +      +      +
M10      +      +      +      +
M11   +      +      +      +
M12 +      +      +      +      +

10. Arrival-Time, Deadline

The conversion tool handles OPC time definitions in the following manner:

• The Control-M FROM and DUE-OUT time definitions are set according to the OPC arrival time and deadline time of the operation or application. Similarly, the Control-M FROM and DUE-OUT days’ offset definitions are set according to the OPC arrival day and deadline day of the operation or application. See the note below that describes the case when an operation’s arrival and/or deadline time are blank.

  The OPC deadline is also used to create the Control-M SHOUT WHEN LATESUB parameter, when the Suppress If Late option is set toY. The SHOUT WHEN LATESUB parameter is described in "SHOUTL" in Conversion Parameters, and the Suppress If Late option is described in 28. Suppress If Late.

  If the OPC Time Dependent MVS Job Option is set toN (No), the Control-M FROM time is not set.

• If the OPC arrival/deadline time is between midnight and the Control-M New Day time and

  • The OPC arrival day is blank (0), the Control-M SAC parameter is set toP. The New Day time is set by the Control-M DAYTIME installation parameter in the CTMPARM member. For more details, see Post Step 2: Perform Final Adjustments.

  • The OPC arrival day is greater than 0, the SAC parameter is not set, but the Control-M FROM days offset is set to the OPC arrival day minus 1.

  • The OPC deadline day is greater than 0, the Control-M DUE-OUT days offset is set to the OPC deadline day minus 1.

• The Control-M UNTIL time is always set to ‘>’.

• The SAC parameter is set in a SMART table entity in the following circumstances:

  • If no jobs in the table specify the SAC parameter, then SAC is set to blank.

  • If all jobs in the table specify SAC=P, then SAC is set to ‘-’.

  • If at least one job, but not all, specify SAC=P, then SAC is set to ‘P’.

11. Priority

The OPC priority is copied unchanged to the Control-M PRIORITY parameter.

The conversion tool supports OPC urgent priority, that is, operations defined with priority 9, by defining the job as a critical path, which is accomplished by specifying *9 in the Control-M PRIORITY parameter. For more information, see the PRIORITY parameter in the Control-M for z/OS User Guide.

12. Operator Instructions

The conversion tool converts an operation's OPC operator instructions to a multi-line DESC parameter in the corresponding Control-M job definition. Documentation for jobs with more than 57 lines of operator instructions is placed in the DOCMEM member of the DOCLIB. When an OPC operation has no associated job name the DESC parameters (DOCMEM) are placed in the ws#oper job definition, where:

• ws is the job's Workstation id.

• oper is the operation number.

13. SEARCH and TABLE Directives

The OPC JCL SEARCH directive is converted to the Control-M %%INCLIB AutoEdit statement. The member names in the NAME parameter are converted to member names in the %%INCMEM parameter The NOAPPL, NOGLOBAL, and APPL subparameters are not supported. The GLOBAL variable table is always included in the JCL member through the Control-M %%GLOBAL AutoEdit statement.

The OPC TABLE directive is converted in the same manner as the SEARCH directive.

The OPC JCL variables contained in the SEARCH and TABLE variable tables are automatically converted to a Control-M AutoEdit variables library based on the OPC JCL Variable Tables report. The OPC TABLE ID is used as the Control-M AutoEdit member name, and the AutoEdit variable is simply the OPC variable name with %% prefixed to it. The description of the variable is also placed in the AutoEdit member as a comment preceding its variable definition.

14. FETCH Directive

The OPC JCL FETCH directive is converted to a Control-M %%INCLIB and %INCMEM AutoEdit statement. The member name in the MEMBER parameter is converted to a member name in the %%INCMEM part of the statement. The COMP parameter is also supported; this parameter is discussed in the following item.

15. BEGIN and END Directives

The OPC JCL BEGIN and END directives are converted to Control-M AutoEdit statements. These directives are used to either conditionally or unconditionally include or exclude JCL and data statements within the JCL run-stream. For example, the OPC directives

//*%OPC BEGIN COMP=(&var..EQ.(express-1, express-2)),
//*%OPC ACTION-INCLUDE

generate the following AutoEdit statements:

//*%%IF %%var EQ express-1
//*%%GOTO LABELmmnn
//*%%ELSE
//*%%IF %%var EQ express-2
//*   %%GOTO LABELmmnn
//*   %%ELSE
//*    ...
//*   %%ELSE
//*     %% GOTO LABELmmXX
//*   %%ENDIF
//*    ...
//*   %%ENDIF
//*%%LABEL LABELmmnn

When the COMP parameter uses an NE comparison operator, the logic is changed to nested IF statements as follows:

//*%%IF %%var NE express-1
//*%%IF %%var NE express-2
//*   %%GOTO LABELmmnn
//*   %%ELSE
//*     %%GOTO LABELmmXX
//*     %%ENDIF
//*     %%ELSE
//*     %%GOTO LABELmmXX
//*     %%ENDIF
//*%%LABEL LABELmmnn

Operators GT, GE, LT and LE in the COMP parameter are also supported.

If ACTION=EXCLUDE is specified, rather than INCLUDE, the LABELs on the GOTO AutoEdit statements are reversed (that is, LABELmmnn is switched with LABELmmXX).

The OPC/ESA END directive is converted to the following Control-M AutoEdit statement with all the INCLUDEd and EXCLUDEd JCL preceding this statement:
//*%%LABEL LABELmmXX

The ACTION=NOSCAN subparameter is supported by adding the following Control-M auto-edit statement:
//*%%RESOLVE OFF

This causes auto-edit variables in subsequent JCL lines not to be resolved and to be submitted as-is, without causing an error. Auto-edit JCL resolution is resumed at the end of the BEGIN block by adding the following statement:
//*%%RESOLVE YES

16. &, %, and ? Variables (for OPC/ESA Only)

When the AUTSCAN conversion parameter is set to Y (Yes), all OPC/ESA &, %, and ? symbols in the OPC/ESA directives and embedded in the JCL stream (whether in JCL statements or in the data stream, that is, following DD *) are converted to AutoEdit variables.

//DD1 DD DSN=&ABC&QRS%XYZ

//DD1 DD DSN=%%ABC.%%QRS%%XYZ

When AUTSCAN is set to N (No), the translation of the OPC/ESA variables to AutoEdit variables depends on the presence or absence of the OPC/ESA SCAN directive in the JCL member. For more details, see 24. SCAN Directive.

The following are ignored by the conversion:

• CLIST/REXX names prefixed by '%'.

• A JCL variable, &var-name, defined in the JCL ‘// SET var-name=xxx’ statements.

• JCL variables defined in in-stream JCL procedures.

• System symbolic &SYSUID.

?-variables are supported when they are the first (or only) variable on the line.

JCL variables defined in OPC Variable tables are supported. The OPC JCL Variable report is processed and a Control-M LIBSYM library is created containing members, one for each JCL VARIABLE TABLE ID defined in the OPC JCL Variable report. Each member contains an auto-edit variable definition, with the default value specified, for each OPC Variable name defined in the report.for that Variable table.

The conversion also supports the case a variable is dependent upon another (independent) variable. For example, suppose that the variable CJCLASS (in table VAR1), with a default value of:3 is dependent on the independent variable OJOBNAME and when OJOBNAME has value A, CJCLASS has value 1 and when OJOBNAME has value B, CJCLASS has value 2. Then the following auto-edit statements are created in the LIBSYM member VAR1:

* CJCLASS
%%CJCLASS  = 3
%%IF  %%OJOBNAME EQ A
%%SET %%CJCLASS = 1
%%ENDIF
%%IF  %%OJOBNAME EQ B
%%SET %%CJCLASS = 2
%%ENDIF

and when the variable &CJCLASS is encountered in a JCL member which specifies the OPC TABLE directive

//*%OPC TABLE NAME=(VAR1)

it is converted according to the above auto-edit logic.

// PARM=('S=&ALMIP.U=&ALMUSR PW=&ALMPW PORTA=&ALMP AMB=&AMB MORE=&MOR')

%%SET %%0=%%ALMIP
%%SET %%1=%%ALMPW
// PARM=('S=%%0%%.U=%%ALMUSR PW=%%1 PORTA=%%ALMP AMB=%%AMB MORE=%%MOR')

17. SRSTAT

The OPC SRSTAT command allows changes to the availability status of special resources. OPC SRSTAT commands in JCL steps are converted to ADD/DELETE COND statements or to CHANGE RESOURCE statements in a JCL step that executes IOACND commands via the CTMUTIL utility. The special resource name in the SRSTAT command is converted to a Control-M condition name, as described in 4. Data Dependencies, or to a Control-M quantitative resource name. When the special resource names are longer than 20 characters, the name specified in the RESNAME file created in JOB1 is used. For more information, see JOB1: Extract Workstation and Application Info.

The OPC AVAIL subparameter of the SRSTAT command determines the ADD/DELETE form of the CTMUTIL command, as follows:

• AVAIL(YES) is converted to an ADD COND command.

• AVAIL(NO) is converted to a DELETE COND command.

The condition date reference is always set to STAT.

When the DEV and/or Q sub-parameters are specified on the SRSTAT command, the res-name is treated as a Control-M quantitative resource and SRSTAT is converted as follows:

• SRSTAT res-name Q(quantity)

  is converted to a RESET QUANTITY statement, which is the equivalent of the IOACND command:
  CHANGE RESOURCE res-namequantity

• SRSTAT res-name DEV([+|-]quantity)

  is similarly converted to a RESET QUANTITY statement, which is the equivalent of the IOACND command:
  CHANGE RESOURCE res-name [+|-]quantity

If the OPC quantity appears without a sign, then the conversion appends a '+' before it.

The AVAIL, DEV and Q subparameters are ignored by the conversion if they specify either a KEEP or RESET value and hence may result in the SRSTAT command being ignored.

The same limitations that apply to OPSTAT also apply to SRSTAT, as described in the note under 25. OPSTAT.

18. Started Task Option (for OPC/ESA Only)

The OPC/ESA Started Task option in the Workstation report determines the setting of the Control-M TASKTYPE parameter. When the Started Task Option is NO, TASKTYPE is set to JOB. When the Started Task Option is YES, TASKTYPE is set to STC, the PREVENT-NCT2 parameter is set to N (for non-DUMMY type jobs only), and the OVERLIB parameter is set to blanks.

Cyclic Started task operations (see 27. Rule/Period Name) are converted with the TASKTYPE set to CST.

19. DESCRIPTION

The Application text or the Operation text in the OPC Application report is placed in the (first line of the) Control-M DESC parameter. If the OPC job is a DUMMY job, that is, if the operation number is 0, only the Application text is used. Otherwise, the Operation text is used and, in addition, the workstation name and operation number are placed in the DESC parameter, starting at position 42.

20. Automatic Submission Option (for OPC/ESA Only)

The Automatic Submission MVS Job option in the OPC/ESA Application report specifies whether jobs and started tasks automatically start when all predecessor jobs have been satisfied and all required resources are available. However, If the JCL for the job is not under TWS control, for example, when the job arrives via a RJE link, this option is set to N.

When the Automatic Submission option is set to N (No), the conversion tool creates a Control-M CMEM On Spool JOBARRIVAL ... DO FORCEJOB rule for the (non-dummy) externally submitted job to bring it under the control of the Control-M monitor. For more information, see the Control-M for z/OS User Guide, Chapter 4, for details about On Spool jobs.

21. DEADLINE WTO Option (for OPC/ESA Only)

The Deadline WTO MVS Job option in the OPC/ESA Application report specifies whether an operator message is issued when the operation passes its deadline and the operation is in started status, that is, the operation has been started, but has not been marked as completed within the deadline time. A Control-M SHOUT WHEN LATE time post-processing parameter is placed into the job scheduling definition when the Deadline WTO option is set to Y (Yes) using the deadline time.

22. ERROR TRACKING Option

The Error Tracking (Control) MVS Job option in the OPC Application report determines whether an error in a job or started task is to cause the operation representing the job or started task to be marked as E (ended-in-error). If N (No) is specified, the operation is marked as C (complete) when it ends, regardless of the outcome, except for certain errors occurring during job submission. For more information, see the OPC/ESA User Guide.

When Error Tracking is set to N (No), the following Control-M post-processing statement is added to the job scheduling definition:

ON PGMST ANYSTEP          CODES EXERR
  DO OK

When error tracking is set to Y (Yes) and the RETCODE conversion parameter is set to LAST, the following post-processing statements are added to the Control-M job scheduling definition:

ON PGMST ANYSTEP PROCST           CODES C*** S*** U****
  DO OK
ON PGMST $LAST   PROCST           CODES >C[hrc] S*** U****
  DO NOTOK

In the second statement, hrc is the Highest Return Code (HRC) value. If no HRC is specified for the OPC operation that is being converted, the value specified for the Control-M HIGHRC conversion parameter is used.

For more information on the RETCODE conversion parameter, see "RETCODE" in Conversion Parameters.

For more information on the HRC, see 26. Highest Return Code – HRC (for OPC/ESA Only).

For more information on the HIGHRC conversion parameter, see "HIGHRC" in Conversion Parameters.

23. Catalog Management (for OPC/ESA Only)

The Catalog Management MVS Job Option can be used to automatically delete, uncatalog, or catalog data sets that have been created or modified in a job or started task that has ended in error or requires a rerun. This facility is available on a job-by-job basis and is converted to the Control-M/Restart PREVENT-NCT2 parameter. For more details, see Catalog Management and "NCT2" in Conversion Parameters.

24. SCAN Directive

When the AUTSCAN conversion parameter is set to N (No), the conversion tool only translates OPC variables to Control-M AutoEdit variables in a JCL member if it encounters an OPC SCAN directive (//*%OPC SCAN) in the member. Translation of the OPC variables to AutoEdit variables only takes place in lines of the member after the SCAN directive is encountered.

When AUTSCAN is set to Y (Yes), the SCAN directive is ignored and all OPC variables are translated to Control-M AutoEdit variables.

25. OPSTAT

The OPC OPSTAT command provides a method of using the OPC automatic event reporting (AER) facility to set operation statuses and coordinate tasks. For example, it can be used to trigger the start of an operation when a particular step in a job is complete.

The OPC OPSTAT commands in JCL steps are converted to AJF FORCEOK MEM=jobname statements in Control-M JCL steps (CTMUTIL utility invoking CTMAPI). This conversion changes the job status to ended OK and thus enables post-processing of the job as if it had successfully ended.

The conversion tool only converts OPSTAT commands that specify the following subparameters to identify the operation whose status is to be changed:

Table 23 Conversion of OPC OPSTAT Commands

The conversion tool only converts Batch commands in SYSIN and SYSTSIN DD statements. The Batch commands can appear in-stream, that is, following //SYSIN DD *, in a PDS member, or in a sequential data set. For more information, see "PNIBTSD" in Conversion Parameters. Non-supported Batch commands in SYSIN and extraneous DD statements in the converted steps are deleted. OPCSTAT commands that are continued on multiple lines, with or without a continuation character, are supported. Parameters in the OPCSTAT command that contain OPC variable values are not supported.

26. Highest Return Code – HRC (for OPC/ESA Only)

The Highest Return Code field in the OPC/ESA Application report specifies the highest acceptable return code from any step in the operation. If a return code for a step in the job exceeds this value, the operation is set to ended-in-error status.

The Control-M default is that the job is considered as having ENDED OK status if no step has a condition code higher than the value set by the MAXCCOK parameter in the CTMPARM member in the IOA PARM library. The value of MAXCCOK should be set to the same value as the HIGHRC conversion parameter. For more information, see "HIGHRC" in Conversion Parameters.

The conversion tool converts the OPC/ESA HRC value to the following Control-M parameters:

ON PGMST ANYSTEP CODES=<C(hrc+1)
  DO OK

If the HRC is less than the value set by the HIGHRC conversion parameter, the Control-M parameters created are:

ON PGMST ANYSTEP CODES=>C(hrc)
  DO NOTOK

27. Rule/Period Name

An OPC application can be defined with a number of different run cycles defining different scheduling dates. Each run cycle is given a Rule/Period Name. The conversion tool assigns the Rule/Period Name to a Rule-Based Calendar in the SMART Table Entity that defines the basic scheduling criteria of the run cycle. For an overview of Control-M SMART Table scheduling, see Application Definition and Control-M SMART Table Scheduling.

If there are multiple Rule-Based Calendars assigned in a SMART Table, the Rule-Based Calendar has a suffix of _n, where n is an alphanumeric character, either 2 through 9, or A through W.

When an OPC application contains multiple offset-based normal run cycles (and no negative run cycles) or multiple rule-based regular run cycles (and no exception run cycles), all with different Input Arrival times and the same Run Days/Rule definition, the conversion tool converts the Application to a Control-M cyclic table as follows: The TASKTYPE is set to TBC (table cyclic), the CYCLIC TYPE is set to 'S' (specific run times), and the SPECIFIC RUN TIMES are set to contain the Input Arrival times from each of the run cycles. The MAXRERUN field is set at the number of run cycles and the TOLERANCE parameter is set to be the difference, in minutes, between the last run cycle's Deadline and Input Arrival.

When the above criteria are not met for multiple run cycles or when an Application contains a mix of Offset-based and Rule-based run cycles, the conversion tool uses the arrival and deadline time of the last run cycle for the Control-M FROM and DUE-OUT times. The last arrival and deadline times/days are also inherited for operations that do not specify their own arrival and deadline time.

28. Suppress If Late

The Suppress If Late MVS Job option from the OPC Application report is used when OPC may not be able to submit or release a job at the appropriate time, such as when predecessors have not completed, or when there is a system outage. This option is used to determine whether the job is to be submitted or released when it becomes possible, or whether it is not to be submitted or released at all.

Set the DUEINCHK parameter in the CTMPARM member in the IOA PARM library to N to bypass the global suppression of job submission after the due-in time of a job has passed. When an operation's OPC Suppress If Late option is set to Y, the conversion sets a message to be issued via the SHOUT WHEN LATESUB * to indicate that the job is being submitted late (according to its DUE-IN time).

29. Run Cycle Valid From and To

OPC Run Cycle Valid From and To dates are converted to the Control-M SCHEDULE RBC ACTIVE FROM and UNTIL parameters in the Rule-Based Calendars of the SMART Table Entity which correspond to the respective run cycle.

30. //*%IJ, //*%1V, //*%1S (PSS only)

The PSS special JCL comment statements //*%IJ, //*%1V, and //*%1S are ignored by the conversion tool. The ' % ' in column 4 is simply replaced by an ' * ' to prevent confusion when the conversion tool converts OPC &-variables to Control-M AutoEdit variables.

31. //*%2V, //*%2S (PSS only)

The //*%2Vnn and //*%2Snn PSS special JCL comment statements that define JCL and SYSIN variables are converted to %%SET Control-M AutoEdit statements.

The %%SET statements are formed as follows:

1. When a default value of dd...d is specified in columns35 through36 of the PSS comment statement, the %%SET statement formed is:
   %%SET %%Vnn = dd...d

2. When a variable, %Vmm, is specified in the variable format code field (columns60 through64) of the PSS comment statement, the %%SET formed is:
   %%SET %%Vnn = %%Vmm

3. When a logical run date is specified in the variable format code field (columns60 through64) of the PSS comment statement, the %%SET formed is:
   %%SET %%Vnn = autoedit date variable

   The PSS logical date formats are converted to AutoEdit formats as follows:

   Table 24 Conversion of PSS Logical Date Formats

   PSS Format	Control-M Format
   TDDMY	%%ODAY.%%OMONTH.%%OYEAR
   TDDM	%%ODAY.%%OMONTH
   TDMD	%%OMONTH.%%ODAY
   TDND	%%OJULDAY
   TDYND	%%OYEAR.%%OJULDAY
   TDSYS	%%OYEAR.%%OJULDAY
   TDMDY	%%OMONTH.%%ODAY.%%OYEAR
   TDYMD	%%ODATE
   TDMY	%%OMONTH.%%OYEAR
   TDYM	%%OYEAR.%%OMONTH
   TDD	%%ODAY
   TDM	%%OMONTH
   TDY	%%OYEAR
   TDNDY	%%OJULDAY.%%OYEAR
   TDC	%%$CENT
   TDCY	%%$CENT.%%OYEAR
   TDCT	%%SUBSTR %%$CENT 1 1
   TDDC	%%OWDAY

4. For SYSIN variable definitions, the //*%2S special JCL comment statement is converted only if columns68 and69 specify %x. In this case, the %SET formed is:
   %%SET %%x = yyy
   where yyy is of the form described in paragraphs 1, 2 and 3 in this Item.

For any variable defined with B (blank) in its validation mask, you must ensure that the variable value is converted to AutoEdit format using the %%BLANKn AutoEdit variable.

32. %Snnx (PSS Only)

A %%Snn statement identifies a SYSIN job instream file for which preparation (variable insertion and/or substitution) is necessary. The conversion tool deletes this statement from the input stream.

33. //*%IP (PSS Only)

The //*%IP PSS special JCL comment statement allows for the insertion of one or several statements from a member of the PSS Parameter library. The conversion tool converts this statement to the following Control-M AutoEdit statement:

%%INCLIB parmlib %%INCMEM member-name

where:

• parmlib is set from the PARMLIB conversion parameter.

• member-name is taken from column8 of the IP comment statement.
  A member-name beginning with the characterP indicates a user exit, and is not supported.

34. %-variables (PSS)

All PSS %-variables embedded in the JCL stream, whether in JCL statements or in the data stream, that is, following DD *, are converted to %%AutoEdit variables.

The AutoEdit concatenation symbol, %%., is used to convert PSS variables that are concatenated with constant data. For example, %V99xxx is converted to %%V99%%.xxx.

Implicitly defined variables on //*%2S comment statements, that is, where the variable relative position is defined in columns 68–69, are not supported by the conversion tool.

35. Group Definition

OPC also allows you to group applications by assigning each application a Group Definition Application ID. These Group Definition Application IDs point to a common Group Definition, with the result that the applications inherit the run cycle definitions specified in the Group Definition. When the conversion tool converts OPC applications that point to Group Definitions, the Control-M Rule-Based Calendars corresponding to the run cycles in the OPC Group Definition Application ID replace the Rule-Based Calendars in the Control-M SMART Table Entity.

For more information on SMART Table Scheduling, see Application Definition and Control-M SMART Table Scheduling.

36. Workstation Destination

The OPC Workstation Destination (for computer systems) is the OPC tracker that can communicate with the OPC controller, and corresponds to a destination specified on an OPC ROUTOPTS initialization statement. During the conversion, a blank destination is associated with mainframe jobs, while for distributed jobs a NOD_wsnm default value is assigned in the WS.EXT file. It is recommended to edit and change the file to specify the actual Control-M NODEID for the distributed job definitions.

37. SETFORM/SETVAR Directives

The OPC SETFORM/SETVAR directives define the format of dynamic-format supplied variables. After OPC processes the SETFORM/SETVAR directives, the variable can be referred to and used.

//*%OPC SETFORM/SETVAR dynamic-variable-name=[SUBSTR](format-expression)

The format-expression might contain any of the following OPC date/time-related keywords together with an optional arithmetic expression of the form +nxx, where n is numeric and xx is a function, such as CD (calendar days), MO (months), YR (years), WK (weeks), or WD (work days), which operates upon the date/time keywords:

Table 25 Date-Related Keywords

The format-expression might contain any of the following time-related keywords:

Table 26 Time-Related Keywords

Any other characters in the format expression are regarded as delimiters.

For the time-related dynamic variables (see below), only HH and MM (minutes) are recognized. For date-related dynamic variables, only CCYY, YY, MM (month), DD, and DDD are recognized.

Table 27 Date-Related Dynamic Variables

Format expressions can also contain combinations of constants and OPC variables. Expressions can optionally be operated upon with the SUBSTR function.

Control-M converts the SETFORM/SETVAR directives to the following AutoEdit statement:

//* %%SET %%dynamic-variable-name=[SUBSTR]converted-format-expression [pos] [len]

The elements in the format expressions are converted as displayed in the following table:

Table 28 Format Expressions Elements

Table 29 Time-Related Keywords

Blanks are converted to %%BLANK.

Delimiters in the format expression are converted by placing the AutoEdit concatenation symbol '%%.' before the delimiters.

39. EQQJCCT Macro

The OPC EQQJCCT macro is used for setting an error code after scanning the sysout data set of a job and for recording error conditions in an incident log file.

Control-M performs the equivalent functionality via the ON SYSOUT job scheduling definition statement. The following table details how the OPC EQQJCCT macro is converted Control-M ON SYSOUT job scheduling parameters:

Table 30 Conversion of EQQJCCT Macro Parameters

Values not listed in the EQQJCCT CA and T parameter are not supported by the conversion tool.

The ON SYSOUT statements are added to all job definitions (in all scheduling tables) whose jobname (MEMNAME) matches the member name of the message table member in the EQQJCLIB library.

40. RECOVER Directive

The OPC JCL RECOVER directive specifies job rerun and restart actions for various situations.

In OPC, when a RECOVER statement is matched against an error condition, the statement is changed to a JCL comment. If the job is rerun, it no longer functions as a RECOVER statement (other RECOVER statements in the JCL remain active). To support this functionality, the conversion tool creates all converted RECOVER directives as compound ON PGMST statements, as follows:

ON PGMST ANYSTEP     PROCST        CODES FC001                          A/O A
ON PGMST xxx         PROCST        CODES yyyy                            A/O
  DO do-statements

The above construct causes the ON statement to be deactivated after the first job failure occurs. If afterwards there are additional failures, the DO action will not be performed again.

Hence, there is no need to specify the global CTMPARM parameter FORCONCE as Y, so that DO FORCEJOB statements are not executed during the RESTART of a job if they were already executed during the original run of the job or during a previous RESTART of the job.

The OPC JCL RECOVER directive contains many parameters and subparameters. The table shown below summarizes how the conversion tool converts each parameter to Control-M job scheduling parameters.

The entry in the "Note" column in Table 31 refers to the number of the corresponding note immediately after the table.

Table 31 Conversion of RECOVER Directive Parameters

Notes

1. The ERRSTEP parameter restricts the RECOVER directive so that it is active only for certain specified steps.

   Values for the ERRSTEP parameter can be specified in several different formats. They are converted according to the following table:

   Table 32 Conversion of ERRSTEP Values

   ERRSTEP Value	Control-M Parameter	Maximum Values Converted
   Stepname	ON PGMST stepname	5
   *	ON PGMST ANYSTEP
   stepname.procstep	ON PGMST stepname PROCST procstep	1
   stepx – stepy	STEP RANGE RNGEnnn FR stepx TO stepy ON PGMST *RNGEnnn	1

   If the ERRSTEP parameter is not specified in the RECOVER directive, the following statement is generated by the conversion:
   ON PGMST xxxx

   The value of xxxx in this statement is determined according to the circumstances, as shown in Table 33.

   Table 33 ON PGMST Statement Variable Values

   Circumstances	Variable Value
   OPC STEPCODE parameters are coded.	+EVERY
   Both the following conditions are satisfied: The RETCODE conversion parameter is set to HIGHEST. No OPC STEPCODE parameters are coded. For more information on the RETCODE conversion parameter, see Conversion Parameters.	ANYSTEP
   Both the following conditions are satisfied: The RETCODE conversion parameter is set to LAST. No OPC STEPCODE parameters are coded. For more information on the RETCODE conversion parameter, see Conversion Parameters.	$LAST

   The ON PGMST statement built using the ERRSTEP value serves as the basis for all other parameters in the RECOVER directive, which is described in the following note

2. The JOBCODE and STEPCODE parameters restrict the RECOVER directive so that it is active only for certain specified job completion codes and return codes.

   Values for the JOBCODE and STEPCODE parameters can be specified in several different formats and are converted according to the following table:

   Table 34 Conversion of JOBCODE and STEPCODE Values

   JOBCODE Value	Control-M Codes
   Sxxx	Sxxx
   Uxxx	Unnnn
   xxxx	Case Codes
   N	Cnnnn
   *	S***,U****
   x – y	>C(x-1) AND <C(y+1)
   FLSH	FLUSH
   CCUN	*UKNW
   JCL	JFAIL
   JCLI	JNRUN
   OSUB	JNSUB
   PCAN	JLOST
   CLNx	*UKNW
   JCCE	*UKNW
   CAN	JNSUB
   OJCV	JNSUB
   OSUF	JFAIL

   • Generic abend codes, which specify an asterisk to represent any character, are supported.

   • The OPC user abend code, Uxxx, is specified with a 3-digit hexadecimal number. Control-M coverts this number into a 4-digit decimal number.

   • A Case Code used as a value for the JOBCODE and STEPCODE parameters must be defined in the Case Code parameter file created in JOB2, as discussed in JOB2: Convert JCL Members.

   If neither JOBCODE nor STEPCODE parameters are specified, the conversion uses the following defaults:

   Copy

   CODES   S*** U**** >C0004      AND
   CODES   S*** U**** <C4096

   The OPC NOERR initialization statement lists error codes that should not cause an operation to be marked as ended in error. This initialization statement is not supported.

3. The DELSTEP parameter specifies a step or range of steps to be deleted from the inline JCL before rerunning a failed operation.

   The conversion tool modifies both the JCL of the job and the relevant scheduling definition. This is illustrated by the following example:

   If the JCL of a job consists of

   Copy

   //jobname    JOB
   //STEP1      EXEC  ...
   //STEP2      EXEC  ...
   //STEPX      EXEC  ...
   //STEPY      EXEC  ...

   and the following is specified for the DELSTEP parameter

   Copy

   //DELSTEP=(STEP1,STEP2,STEPX-STEPY)

   the conversion tool modifies the JCL, by adding AutoEdit statements, in the following way:

   Copy

   //jobname    JOB
   //*  %%IF    %%STEP1  NE  1
   //STEP1      EXEC  ...
   //*  %%ENDIF
   //*  %%IF    %%STEP2  NE  1
   //STEP2      EXEC  ...
   //*  %%ENDIF
   //*  %%IF    %%STEPX  NE  1
   //STEPX      EXEC  ...
   //STEPY      EXEC  ...
   //*  %%ENDIF

   In addition, the conversion tool adds the following parameters to the job scheduling definition:

   Copy

   SET VAR  %%STEP1=0
   SET VAR  %%STEP2=0
   SET VAR  %%STEPX=0

   and in the ONPGMST statement the following is added:

   Copy

   DO SET VAR = %%STEP1=1
   DO SET VAR = %%STEP2=1
   DO SET VAR = %%STEPX=1

4. The ADDPROC parameter specifies a name, or list of names, of JCL procedure library members to be added to the inline JCL before a failed operation is rerun.

   The conversion tool modifies both the JCL of the job and the relevant scheduling definition, as illustrated by the following example.

   If ADDPROC=(PROC1) is specified, the following AutoEdit statements are added to the JCL following the job statement:

   Copy

   //*  %%IF      %%PROC1  EQ 1
   //*  %%INCLIB  DDNAME=EQQPRLIB  %%INCMEM  PROC1
   //*  %%ENDIF

   In addition, the conversion tool adds the following parameters to the job scheduling definition:

   Copy

   SET VAR  %%PROC1=0

   and in the ONPGMST statement the following is added:

   Copy

   DO SET VAR = %%PROC1=1

5. The RESSTEP parameter specifies the name of the job step at which point the operation must be restarted. RESSTEP is ignored when specified in an STC (Started task).

   Values for the RESSTEP parameter can be specified in several different formats and are converted to DO IFRERUN statements according to the following table:

   Table 35 Conversion of RESSTEP Values

   RESSTEP Value	Control-M DO IFRERUN Statement
   stepname	FROM stepname
   stepname.procstep	FROM stepname.procstep
   *	FROM $FIRST (default)
   %	FROM $EXERR

6. The RESTART parameter specifies whether a job must be restarted. When RESTART is set to YES, the conversion tool adds a DORERUN parameter to the end of the ONPGMST block.

7. The ADDAPPL parameter specifies an application, or list of applications, to be added to the OPC current plan.

   The conversion tool translates the applicationIDs in the ADDAPPL parameter to Control-M table names using the Application and Owner ID Name list file (created in JOB1). Table names are then used in DO FORCEJOB statements that are added to the ONPGMST statement.

   If an applicationID in the ADDAPPL parameter is not found in the Application and OwnerID Name list file, an error message is produced.

8. The RELSUCC parameter specifies the applicationID of a successor occurrence (or a list of IDs). The application ID is used to form condition names with the following format:

   appl-id_jobname

   DOCOND statements with these condition names and specifying a date of STAT+ are added to the ONPGMST statements.

9. The TIME parameter restricts the RECOVER directive so that it is only valid during a specified time range.

   If TIME=0000-2400 is specified, the DO IFRERUN parameter (the product of conversion of the RESSTEP OPC parameter, as described in Note 5 in this Item) is created with CONFIRM=N specified. If any other range is specified, CONFIRM=Y is specified in the DO IFRERUN parameter.

10. The ALTJOB parameter specifies an alternate job or started-task name to use when the job is restarted. The conversion tool converts this to the Control-M RERUNMEM parameter. Note that if there are multiple RECOVER directives in a job, which specify different ALTJOB parameters, only the first is used and the others are ignored.

41. ADRULE, REPEAT, and SHIFT (Rule-Based Run Cycle) (for OPC/ESA Release 3 and Later Only)

Rule-based run cycle allow specifying scheduling criteria through rule-based run cycle parameters. Unlike Offset-based run cycle criteria, these are converted directly to Control-M basic scheduling parameters that minimize the number of Control-M calendars required, which is discussed in JOB1: Extract Workstation and Application Info. The rule-based parameters, in conjunction with the OPC Free-day rule, are converted according to the general principles outlined in the following tables.

Table 36 Conversion of Free-Day Rule Parameters

Table 37 Conversion of Rule-Based Parameters

Notes

1. The OPC ONLY and YEAR Rule parameter combination is converted to Control-M DATES parameters ddmm or mmdd depending on the value of the DATETYP IOA installation parameter.

   The YEAR parameter is not supported in combination with the LAST, MONTH, WEEK, DAY(WORKDAY) or DAY(specific-days) parameters, except with the EVERY parameter.

2. When the SWEEK IOA installation parameter is set to MON, the days Monday, Tuesday, ..., Saturday, Sunday are converted to WDAYS=1, 2, ...,6, 0 respectively. When SWEEK=SUN, these days are converted to 2, 3, ..., 6, 0, 1 respectively.

3. When the OPC LAST parameter is specified with ONLY and a non-specific day (DAY or WORKDAY), the conversion tool converts it to DAYS=Ln. When a specific day is specified in the OPC DAY parameter (Sunday, Monday, ...) the conversion tool converts it as follows:

   Copy

   DAYS=L1,L2,L3,L4,L5,L6,L7    And/Or A
   WDAYS=n

   where n is set as described in Note 2 in this Item.

   The OPC LAST parameter is ignored when it is coded in combination with the EVERY parameter.

4. When the OPC ONLY parameter is specified with a specific DAY, the conversion tool converts it by inserting the value DmWn in the WDAYS parameter, where:

   • m is chosen as in Note 3 in this Item.

   • n is the number specified in ONLY.

5. When the OPC DAY(WORKDAY) parameter is specified, the Control-M DAYS are specified as workdays (Dn or Ln) and a DCAL calendar, taken from the OPC calendar-id, is also specified.

6. Specific weeks, for example, WEEK (1, 4), are not supported, nor is the WEEK parameter supported in combination with YEAR or MONTH, except in certain situations, such as when used with OPC parameter EVERY (referred to in Table37 on page129).

7. The OPC PERIOD parameter is supported only when no more than one period name is specified in the rule.

8. You must create the HOLIDAY calendar, based on the applications base calendar.

9. Calendars created by the conversion tool which end with the following characters ({, A-I) are periodic calendars.

   You may have to modify these calendars to produce the desired scheduling.

   For more information, see the discussion of special year-end handling of periodic calendars in the IOA chapter of the Control-M for z/OS User Guide.

10. OPC criteria that specify a series of days (EVERY(nn)) on a monthly basis are converted to Control-M cyclic tables when nn is greater than 1. The following parameters are specified in the SMART Table Entity's Rule-Based Calendar:

    • MONTHS=xxx (depending on the months requested).

    • MAXWAIT=30 (to ensure that the table remains on the AJF for the entire month).

    • DAYS=1+mm (mm=0 if ORIGINSHIFT is not specified).

    In the table entity, the following are specified:

    • TASKTYPE=TBC

    • INTERVAL=nn*1440 (interval time in minutes)

    • FROM=STRT (interval begin time between cycles based on actual activation of the table)

    • MAXWAIT=30

    • MAXRERUN=30/nn

    For the OPC REPEAT control statement which defines cyclic run cycles with a given interval, from and until time, the conversion creates a Control-M cyclic table definition as follows:

    • TASKTYPE=TBC

    • FROM TIME=hhmm

    • UNTIL TIME=hhmm

    • INTERVAL=hh*60+mm (interval time in minutes)

    • FROM=STRT

    • MAXRERUN=(UNTIL TIME – FROM TIME)/INTERVAL

    • MAXWAIT=1

11. OPC criteria that specify a SHIFT are converted to the Control-M Extended Shift +|-nnn when the specified OPC SHIFT TYPE is W (workdays).

    Support for SHIFT TYPE D (days) is provided by setting the CONFCAL to the ALLDAYS calendar only when the job definition does not otherwise require a CONFCAL.

    An error message is produced when nnn exceeds 62.

42. Duration Time

The OPC duration time (hh.mm) of an operation is its estimated processing time. OPC uses the estimated processing time when creating the current plan, to work out a timetable for the operations (Planned start time, Latest start time and Planned end time). The OPC Duration time is not necessary accurate because OPC can adjust this figure dynamically from its experience of the actual durations.

The conversion tool converts the duration time to a 4-digit number in minutes and, when the conversion option ELAPSED is set Y, creates the following Control-M SETVAR parameter in the job scheduling definition:
%%CONV-ELAPSED=nnnn

43. WAIT Workstation Option

An OPC/ESA WAIT workstation is a general non reporting workstation with the WAIT option set to Y. A WAIT workstation is used to create a dummy operation that runs for a specified period of time. This time period is defined as the duration of the operation. When the WAIT operation is in an OPC application of mainframe operations, the following Control-M auto-edit variable is created in a corresponding dummy job, and it provides the equivalent functionality:

%%CTM_PRE_SUB_WAIT=nnnM

When the WAIT operation is in an OPC application of distributed operations, the conversion tool converts it to a distributed Command task with a command line of ‘sleep nnnn’ where nnnn is the operation’s duration.

44. AUTOMATION Workstation Option

An OPC/ESA Automation workstation enables sending commands to System Automation when the workstation type is general and the reporting attribute is automatic. The conversion tool converts automation operations to Started tasks that execute the IOAOPR utility with a parameter of CMDMEM=jobname.

45. Distributed Job Scripts/Parameters

Support for OPC distributed job definitions and fault tolerant workstations. For more information, see Jobs on Distributed Platforms.

46. WTO Workstation Option

An OPC WTO workstation enables the issuance of a write-to-operator (WTO) message at an operator console. When an operation at a WTO workstation is started, TWS builds a WTO message containing the text for the operation allowing console automation software to intercept it and take necessary action. TWS automatically dispatches a WTO operation, subject to its scheduling criteria being satisfied.

The conversion tool converts WTO operations to SHOUT WHEN OK statements in the job scheduling definition and specifies a message text consisting of EQQW776I + the operation text and a destination of OPER.

47. WSSTAT

The OPC WSSTAT command allows changes to the status of a workstation in the current plan. Since the OPC workstation concept plays no role in Control-M, the WSSTAT functionality is converted as a quantitative resource, either available or unavailable. Hence, OPC WSSTAT commands in JCL steps are converted to RESET QUANTITY (CHANGE RESOURCE) statements in a JCL step that executes IOACND commands via the CTMUTIL utility. Only the WSNAME and STATUS subparameters are supported. The workstation name in the WSNAME parameter is converted to a Control-M quantitative resource name of the form workstation-name_SERVER. For more information, see Conversion Parameters., option RESOURC.

The STATUS parameter determines the quantity for the SERVER resource as follows:

• A (Active): 9999 (available).

• O (Offline): 0 (not available).

• CHANGE RESOURCE workstation-name_SERVER 0|9999

The same limitations that apply to OPSTAT also apply to WSSTAT, as described in the note under 25. OPSTAT.

Unique Control-M and Control-M/Restart Parameters

Several unique Control-M and Control-M/Restart job scheduling definition parameters that do not have corresponding OPC capabilities 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 parameters, and must be reviewed and modified to specify your local Control-M and Control-M/Restart preferences. For additional information regarding these parameters, see Conversion Parameters the Control-M for z/OS User Guide, and the Control-M/Restart User Guide.

The parameters are set out in the following paragraphs.

AUTO-ARCHIVE

This Control-M/Restart parameter archives the three SYSDATA files of the job for Control-M/Restart use and online viewing. The archive parameters, such as retention period or archive data set type, are determined by Control-M/Restart installation parameters.

This parameter has a subparameter, SYSDB, which is set to Y (Yes). Each job scheduling definition archives the three SYSDATA files to a common data set, instead of a unique data set.

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 the time of submission to the automatically held output class. After analyzing the sysout, Control-M may be ordered to requeue the sysout. For more information regarding DO SYSOUT options, see the Control-M for z/OS User Guide.

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

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

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

SHOUT

This Control-M parameter specifies messages to be sent, "shouted," to different destinations on different occasions.

The conversion tool supports the following SHOUT situations:

Table 38 SHOUT Situations

For the various occasions where these SHOUT option are utilized by the conversion tool, see Component Conversion Summaries and the SHOUTxx parameters in Conversion Parameters.

ADJUST CONDITIONS

The ADJUST CONDS parameter indicates whether to ignore prerequisite conditions normally set by predecessor jobs if the relevant predecessor jobs are not scheduled.

Ignoring prerequisite conditions normally set by predecessor jobs can cause dependent jobs to run out of order.

The conversion tool maintains the Job order by setting the ADJUST CONDS parameter to D(ummy), which is the equivalent of inserting dummy jobs in place of the prerequisite jobs that are not run.

For jobs running on Control-M distributed platforms, the AJUST CONDS parameter is set to Y and the Control-M/Server CTM_GROUP_ADJUST_DUMMY configuration parameter controls the creation of dummy jobs that run in place of unscheduled prerequisite jobs.

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

• If CTM_GROUP_ADJUST_DUMMY is set to N, OUT conditions of the jobs that were not ordered are ignored by the ordered jobs in the SMART Table. (Default)