IN: Runtime Scheduling Parameter (decollating mission)

Prerequisite conditions for report decollating mission execution.

Figure 274 IN Parameter Format

Optional, but recommended. A maximum of two prerequisite conditions can be specified in each IN line. When you specify the second prerequisite condition in a line and press Enter, a new line is opened for specifying additional prerequisite conditions.

Each specified prerequisite condition consists of the following subparameters:

Table 220 In Subparameters

Subparameter	Description
cond_name	User-supplied, descriptive name of 1 through 20 characters used to identify the condition. Mandatory.
dateref	4-character date reference. Mandatory. Valid values are: date—Specific date (in either mmdd or ddmm format, depending on the site standard). STAT—Static. Indicates that the condition (for example, PRINTER-SET) is not date-dependent. ODAT—Original schedule date. Default. PREV—Previous date on which the mission should have been scheduled, according to its basic scheduling criteria (or ODAT–1 if the mission is being forced). $$$$—Any scheduling date. If a date reference is not specified, value ODAT is automatically inserted when you press Enter.

Subparameter

Description

cond_name

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

dateref

4-character date reference. Mandatory. Valid values are:

date—Specific date (in either mmdd or ddmm format, depending on the site standard).
STAT—Static. Indicates that the condition (for example, PRINTER-SET) is not date-dependent.
ODAT—Original schedule date. Default.
PREV—Previous date on which the mission should have been scheduled, according to its basic scheduling criteria (or ODAT–1 if the mission is being forced).
$$$$—Any scheduling date.

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

Parent Topic

Decollating Mission Parameters