Previous Topic

Next Topic

Book Contents

Book Index

IN: Runtime Scheduling Parameter

Prerequisite conditions that must be satisfied before the job can run.

Figure 227 IN Parameter Format

Optional. A maximum of two prerequisite conditions can be specified in each standard IN line. One prerequisite condition can be specified in each long IN line. When you specify the second prerequisite condition in a standard IN line, or one prerequisite condition in a long IN line, and press Enter, a new IN line is opened for specifying additional prerequisite conditions. For more information, see Specifying Long IN Condition Names.

Each specified prerequisite condition consists of the mandatory subparameters described in Table 189.

Table 189 IN Subparameters

Subparameter

Description

cond_name

User-supplied descriptive name of 1 through 39 characters used to identify the condition. Mandatory.

Notes:

A condition name must not begin with the symbols "|", "¬", or "\", and must not contain parentheses ( ), because each of these characters has a special meaning. For more information, see Logical Relations between Multiple Conditions.

If you want to use the UFLOW (unique flow) feature, the condition name must not exceed 36 characters since the UFLOW feature concatenates a unique 3-character suffix to the name of any condition that connects jobs within the ordered table.

You can use an AutoEdit variable in a condition name, provided that the AutoEdit variable has a value that is known before the job is ordered.

dateref

4-character date reference. Mandatory.

Valid values are:

  • date – Specific date (in either mmdd or ddmm format, depending on the site standard).
  • ODAT – Resolves to the original scheduling date. Default.
  • +nnn – Resolves at job order time to ODATE+nnn calendar days. nnn is three digits (000-999).
  • -nnn – Resolves at job order time to ODATE-nnn calendar days. nnn is three digits (000-999).

Note: -001 is not necessarily the same as PREV, because PREV is based on job scheduling criteria, while -nnn is based on calendar days.
  • PREV – Resolves to the previous date on which the job ought to have been scheduled, according to its basic scheduling criteria, or ODATE–1 for a forced job.

Note: for SMART Table Scheduled Jobs: If the value of the SCHEDULE RBC parameter has been set to * (asterisk), PREV is resolved to the nearest previous date that satisfies one or more non-Exclude RBCs in the SMART Table Entity.
  • STAT – Static. Indicates that the condition, such as IMS-ACTIVE, is not date-dependent.

Note: Before STAT was introduced, date 0101 was recommended to be used in conditions that were not date-dependent. Unlike 0101, STAT is not a date, and it operates differently. Always use STAT when defining conditions that are not date-dependent.
  • **** – Any scheduling date
  • $$$$ – Any scheduling date

Note: If a date reference is not specified, value ODAT is automatically inserted when you press Enter.

Parent Topic

Job Production Parameters