CTMBLT Parameters

The CTMBLT utility receives parameters from an input file referenced by the DAINPRM DD statement. The syntax of the input statements is:

Figure 21 CTMBLT Input Syntax

Note the following points about this syntax:

• Parameters enclosed in braces { } are optional.
• Parameters not enclosed in braces { } are mandatory.

Note: It is not necessary to define mandatory parameters locally if their corresponding global definitions have been provided.

• The set of parameters enclosed in a matching pair of brackets [ ] can be specified more than once.
• Parameters may begin in any column of the 80-byte input record. No spaces are included between keywords and parameters.
• One parameter is permitted per line. Subparameters can follow a main parameter on the same line, separated from the main parameter by a comma. Comments can be placed on the same line, separated from the parameter by a space.
• To use a double-byte character set (DBCS) in free text fields, enclose the free-text parameter values (for example, DESC, SHOUT MSG) between shift-out (x’OE’) and shift-in (x’OF’) delimiter bytes to indicate the beginning and end of DBCS text.
• Lines beginning with an asterisk (*) are treated as comments.
• Any parameters whose values contain special characters (for example, DESC='this description, contains blanks and commas') should be enclosed in either single or double quotes, or parentheses.

The parameters specified in the input file are divided into the following groups:

• General Parameters

  These parameters specify scheduling library names (LIBRARY), table names (TABLE), job or SMART Table Entity scheduling definition names, (MEMNAME and TABLE-ENTITY) and rule-based calendars (SCHEDULE-RBC).

  This set of parameters also contains the following control parameters: MEM-OVERWRITE, ADD-GLOBAL, and OPTION. These control parameters can be specified any number of times, in any order, anywhere in the input stream. Each control parameter applies to the table definition in which it is embedded, taking effect from the point where it is encountered, and all subsequent table definitions, until a new value for the parameter is specified.

• Job Scheduling Definition Parameters

  These parameters correspond to the parameters of the job scheduling definition screen. They can be defined in the ways shown in the following table:

  Table 94 CTMBLT Job Scheduling Definition Parameters

  Parameter	Description
  Global	Apply to all job scheduling definitions in the table in which they are specified. When multiple occurrences of a parameter are not permitted, and there are no Local definitions specified, the Global definition of the parameter is applied. Global definitions are specified by placing such parameters between the TABLE parameter and the first MEMNAME or TABLE-ENTITY (SMART Table Entity) parameter in the table.
  Local	Apply only to the job scheduling definition for which they are specified.
  Super Global	Super Global parameters, if specified, must be specified before the first TABLE parameter and after any control parameters in the input stream. Alternatively, they can be specified after parameter TABLE=*END that is used to delimit the scope of the Super Global parameters (rather than to define a new table). Any job scheduling definition parameter defined as a Super Global parameter remains in effect as a Global parameter across all the tables in the input run stream until a TABLE=*END parameter is encountered or until the end of the run stream.

  The sequence in which the parameters appear in the input file is important as it determines

  • which job and SMART Table Entity scheduling definitions belong in which table, and which tables belong in which library
  • whether job scheduling definition parameters are interpreted as Super Global, Global or Local

  When duplicate parameters are specified as Global or Super Global parameters, only the last takes effect.

• Special Parameters
  • Model – By using this parameter when creating a new job scheduling definition, you can significantly reduce the number of job scheduling parameters you need to code. You achieve this by specifying an existing job scheduling definition to serve as a model or skeleton. When you do, the effect is as if you had effectively specified every possible CTMBLT job scheduling parameter, with values corresponding to those contained in the job scheduling definition of the model.

    MODEL must be the first parameter specified in the job scheduling definition; it must be specified immediately after the MEMNAME or TABLE-ENTITY (SMART Table Entity) parameters.

    You cannot specify MODEL as a global or super-global parameter.

    MODEL fields supplied for multiple value fields (for example, IN and OUT) are always retained in the output job definition – the values provided by input parameters (LOCALs, and GLOBALs/SUPER GLOBALs if ADD-GLOBAL=Y) are added to the output job definition.

    After specifying MODEL, you can specify any number of job scheduling parameters to modify or add to the model definition, subject to the following restrictions:

    • Job scheduling parameters specified after MODEL must be consistent with the model. If, for example, the model definition contains DAYS values and you wish to specify DATES parameters, then precede the DATES parameters with the OPTION=/DATES statement. For more information, see "OPTION" in CTMBLT General Parameters.
    • If the model you specify contains an RBC which is not defined in the SMART Table Entity to which the current job belongs, CTMBLT will accept the model, but will produce an error message after displaying the job scheduling definition.
    • If the model you specify contains an RBC, but the current job does not belong to a SMART Table, the RBC is ignored.
    • You can only specify a model SMART Table Entity following a TABLE-ENTITY (SMART Table Entity) general parameter.
  • JCL – This parameter is used to build in-line JCL statements to replace the JCL member specified in the MEMLIB parameter.
  • APPL-FORM, APPL-TYPE, APPL-VER, CM-VER – These parameters are used when defining jobs as distributed (non-mainframe) job definitions. For information about the proper usage of these parameters, consult the relevant Control-M User Guide.
  • DEFTYPE – This parameter is used to specify that a job definition is to be built for use on a distributed platform only.

The parameters of the input file are described below, according to SMART Table.