ORDER

Indicates a specific table member (or job) to be ordered

DSN=schedlib

Specifies the name of the scheduling library. You must specify either this parameter or parameter DDNAME, but not both.

DDNAME=dd | DD=dd

Specifies a pre-allocated DD name that points to the scheduling library. You must specify either this parameter or parameter DSN, but not both.

{MEMBER | MEM}=tableName

Specifies the name of the table that contains the job scheduling definitions. Full masking of the tableName table is supported. Mandatory.

TABLE={table | *}

Equivalent to the MEMBER parameter.

JOB{jobname | *}

Specifies the name of a job scheduling definition in the table. Optional. If a job name is not specified, or if an asterisk (*) is specified, the entire table is processed.

ODATE={date | ODATE | DATE} | DATE={date |ODATE | DATE}

Specifies the order date of the jobs in the table, in mmddyy, ddmmyy, or yymmdd format, depending on the site standard. This parameter overrides the checkpoint date specified in DD statement DACHK. Optional.

The default is the date from the checkpoint record. However, if it is run with PARM or from an application program, the DATEREC (DACHK) is ignored and the default is the current Control-M working date. Valid values:

• date – specific order date in mmddyy, ddmmyy, or yymmdd format, depending on the site standard
• ODATE – V-M working date
• DATE – system date

ODATEOPT

or ODOPT

Whether to wait for a specific date, or process the Order or Force request immediately.

Valid values are:

• VALUE or VAL – The Order or Force request is processed immediately. Default.
• RUN – The Order or Force request is not executed before the date set in the ODATE field, even if all required conditions and resources are available.

INTOTBL=table_rba

Dynamically inserts a job into a table, where table_rba is the RBA of a table which was already ordered and exists in the Active Jobs File.

You must also use the JOB parameter of the ORDER statement to identify the job you wish to insert into the Table.

Before performing the insertion, CTMJOB checks that the job specified in the ORDER statement belongs to the SMART Table Entity specified in the RBA.

The insertion is done as a FORCE, that is, the scheduling criteria of the job are not checked before it is inserted.

Even though a job may already have been ordered, it can be inserted again, as a duplicate, by means of the DUP parameter.

Note: This parameter is available only when used with CTMAPI.

DUP | NODUP

DUP allows, and NODUP prohibits, the dynamic insertion of duplicate jobs, that is of jobs that already exist in the table.

Note: This parameter is available only when used with CTMAPI.

NEWT

Orders a new SMART Table Entity together with the job that was specified in the JOB parameter.

FORCE

Places the job order in the Active Jobs file regardless of the job's Basic Scheduling parameters. Optional.

UFLOW

Specifies that a unique job flow is ordered or forced (only available when ordering or forcing a table).

A unique job flow feature is used to ensure that, when an entire table is ordered or forced, the new jobs are not effected by conditions that might already exist as relationships between jobs in the AJF. This is accomplished by automatically adding a unique 3-character suffix to the names of any condition that connects jobs within the ordered table. The unique suffix is only added to the names of conditions that consist of 1) an OUT condition of a job in the ordered table and 2) an IN condition to another job in the ordered table.

A typical use case for the unique job flow feature is where the same table is ordered multiple time a day, and there is a need for an independent job flow for each invocation.

SELECT RBC rbcname

and

IGNORE RBC rbcname

Specify RBCs whose associated jobs are either ordered or not ordered. A RBC is a set of Basic Scheduling criteria specified in a SMART Table Entity that is used to schedule specific jobs in the SMART Table. For more information, see the Control-M for z/OS User Guide.

• SELECT RBC or IGNORE RBC statements may be used for ordering SMART Tables and regular tables.
• SELECT RBC statements indicate RBCs to be used to select jobs to be ordered.
• IGNORE RBC statements indicate RBCs to be used to prevent jobs from being ordered.
• Each SELECT RBC statement or IGNORE RBC statement must appear on a separate line.
• Each block of SELECT RBC or IGNORE RBC statements must be preceded by an ORDER statement.
• An asterisk (*) can be included as a masking character for the suffix of the rule-based calendar name, or for the entire RBC name. For more information about character masking, see the Control-M for z/OS User Guide.
• Any number of SELECT RBC and IGNORE RBC statements can be specified
• Processing SELECT RBC and IGNORE RBC should include CTM and Table Level RBCs.