Continue rule definition processing (CONTINUE)

The CONTINUE function directs Advanced Allocation Management to perform applicable actions for a matched rule definition and then continue to look for additional matching rule definitions.

CONTINUE=ENABLE doesn’t have any significance when given along with EXCLUDE.

Syntax

CONTINUE=ENABLE|DISABLE

Operands

ENABLE: Enable CONTINUE processing.
Note: If CONTINUE=ENABLE, more than one rule definition can match an allocation. When this situation occurs, only the final match is reported.
DISABLE: Disable CONTINUE processing.

Default

DISABLE

Environments

ACS, ALLOCATE, CATCHECK, EXTEND, STOW, and UNALLOCATE.

Example

In the following example, CONTINUE=ENABLE directs Advanced Allocation Management to change the unit name when UNIT_NAME=VIO is specified, and then continue checking and acting on other matching rule definitions:

RULE DEFINITIONS

DEFAULTS
*
INCLUDE
  UNIT_NAME=VIO
  SET_UNIT_NAME=SYSDA
INCLUDE
  UNIT_NAME=VIO
  SET_UNIT_NAME=SYSDA
  CONTINUE=ENABLE
INCLUDE
  PROGRAM=ADRDSSU
  PRIM_REDUCE=(DISABLE,DISABLE)

Note the following items:

If the first rule definition occurs near the top of the RULEDEFS member when a request for VIO is encountered, it matches the rule definition, changes the unit name to SYSDA, and stops processing subsequent rule definitions. In this case, you might not want to stop processing at this point because the change is a global change and more specific changes might follow the definition.
If you specify a DFDSS step (ADRDSSU) and SYSPRINT is directed to VIO, Advanced Allocation Management changes the specification to SYSDA and disables PRIM_REDUCE for all allocations within this job step.

Example

The following is an example of accumulating rule definition information:

INCLUDE DDNAME=SYSUT1
               PRIM_REDUCE=ENABLE
               MSG_LEVEL=RULEDEF
               CONTINUE=ENABLE
 
INCLUDE JOBNAME=JJHTEST1
               SEC_ALLOC=ENABLE
               MSG_LEVEL=EXCEPTIONS

The following behavior occurs using the rule definition:

For a data set with a DDNAME of SYSUT1 in a job with a job name of JJHTEST2, the PRIM_REDUCE=ENABLE and MSG_LEVEL=RULEDEF options are set because only the first rule definition matches.
For a data set with a DDNAME of SYSUT2 in a job with a job name of JJHTEST1, the SEC_ALLOC=ENABLE and MSG_LEVEL=EXCEPTIONS options are set because only the second rule definition matches.
For a data set with a DDNAME of SYSUT1 in a job with a job name of JJHTEST1, the PRIM_REDUCE=ENABLE, SEC_ALLOC=ENABLE, and MSG_LEVEL=EXCEPTIONS options are set because both rule definitions match. Because MSG_LEVEL is specified on both rule definitions, the last MSG_LEVEL specification overrides the first MSG_LEVEL specification.

For an overview of CONTINUE=ENABLE processing, see Processing order.