Previous Topic

Next Topic

Book Contents

Book Index

OUT: Post–Processing Parameter (decollating mission)

Prerequisite conditions to be added and/or deleted when the report decollating mission ends OK.

Note: OUT and DO COND statements are similar, but not identical. The differences are outlined below in "OUT/DO COND Differences."

Figure 315 OUT Parameter Format

Optional. A maximum of two prerequisite conditions can be specified in each OUT line. Upon specifying the second prerequisite condition in a line and pressing Enter, a new line is opened for specifying additional prerequisite conditions.

Each specified prerequisite condition consists of the following mandatory subparameters:

Table 231 OUT Subparameters

Subparameter

Description

cond_name

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

dateref

4-character date reference. 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, TAPE-READY) is not date-dependent.
  • ODAT – Original scheduling date. Default.
  • PREV – Previous date on which the mission should have been scheduled, according to its basic scheduling criteria (or ODAT–1 for a forced mission).
  • NEXT – Next scheduling date (or ODAT+1 for a forced mission).
  • **** – Any scheduling date. Valid only with opt= – .
  • $$$$ – Any scheduling date. Valid only with opt= – .

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

opt

Indicates whether to add or delete the specified prerequisite condition. Valid values:

  • + – Add (create) the prerequisite condition.
  • - – Delete the prerequisite condition.

Parent Topic

Decollating Mission Parameters