IOACLCND Parameters

Unless the utility is instructed otherwise using parameters, it deletes all prerequisite conditions (except those whose date reference is STAT) in the IOA Conditions file.

The utility outputs a list of all the deleted prerequisite conditions.

Prerequisite conditions that must not be deleted (for example, prerequisite conditions needed throughout the year) are specified by means of control statements, that are specified using DD statement DACRSIN or SYSIN. The formats of these statements are displayed below, followed by explanations:

equation1

equation2s

equation4s

IGNORE statements instruct the utility not to delete the indicated prerequisite conditions, as follows:

An IGNORE COND statement instructs the utility not to delete the indicated prerequisite condition under any circumstances.
An IGNORE CONDIN statement instructs the utility not to delete the indicated prerequisite conditions if the utility determines that the prerequisite conditions are referenced conditions. A referenced condition is a prerequisite condition appearing in the IOA Conditions file at the same time that it appears as an IN condition in an active job, mission or rule (for example, one that is currently present in the Active Jobs file or Active Missions file).

Conversely, SELECT {COND|CONDIN} statements instruct the utility to delete the prerequisite conditions specified. A customer who wants to delete only those statements specified in the SELECT COND statement should specify IGNORE COND * as the last statement.

IGNORE and SELECT statements can contain the following values:

cond-prefix specifies the prefix of prerequisite conditions. An asterisk indicates all prerequisite conditions.
If a FROM or TO combination is supplied, the specified condition is processed by the SELECT/IGNORE statement only if its date is in the date range.
date can be either a specific date in the site defined standard (mmddyy, ddmmyy or yymmdd) or a relative date. A relative date is specified in the format -n, where n is the number of days before the current date (for example, -5 means five days before the current date). Relative and specific dates can be mixed (for example, a specific FROM date and a relative TO date).

When a FROM and/or TO date is not specified, the current date is the default for the unspecified date. The TO date (regardless of whether specific, relative or assumed) cannot precede the FROM date.

Note: Prerequisite conditions whose date reference is STAT are ignored by this utility.

CONTROLM and CONTROLD statements indicate whether the utility checks prerequisite conditions in the Active Jobs file and/or the Active Missions file, respectively, if a CONDIN-type condition statement is specified. By default, each of these files is checked if its respective product is installed (according to IOA installation options). These statements can be used to override the default. You can specify either, both or neither of these statements.

These statements can impact the result of a CONDIN-type condition statement because the utility cannot determine that a prerequisite condition is referenced unless it can check the Active Jobs or Missions file for the job or mission containing the IN prerequisite condition.

Valid values for these statements are described below:

Table 27 Control-M and Control-D Statements

Statement	Description
CONTROLM	Determines whether the Control-M Active Jobs file is checked during the cleanup process of the IOA Conditions file. Optional. Valid values are: YES – Check the Active Jobs file. Default (if Control-M is installed). NO – Do not check the Active Jobs file. Default (if Control-M is not installed).
CONTROLD	Determines whether the Control-D Active Missions file is checked during the cleanup process of the IOA Conditions file. Optional. Valid values are: YES – Check the Active Jobs file. Default (if Control-D is installed). NO – Do not check the Active Jobs file. Default (if Control-D is not installed).

Statement

Description

CONTROLM

Determines whether the Control-M Active Jobs file is checked during the cleanup process of the IOA Conditions file. Optional. Valid values are:

YES – Check the Active Jobs file. Default (if Control-M is installed).
NO – Do not check the Active Jobs file. Default (if Control-M is not installed).

CONTROLD

Determines whether the Control-D Active Missions file is checked during the cleanup process of the IOA Conditions file. Optional. Valid values are:

YES – Check the Active Jobs file. Default (if Control-D is installed).
NO – Do not check the Active Jobs file. Default (if Control-D is not installed).

The utility can be run simultaneously with the Control-M and the Control-D monitors.

If the job is submitted under Control-M, AutoEdit variables are supported.

Parent Topic

IOACLCND – Clean the IOA Conditions File