RGSTART

Purpose

Use the RGSTART control statement to signal the start of a run cycle group definition. When this statement is found in the input data set, it signals the batch loader to complete the preceding AD, OI, or RG being built and write it to the database.

After a RGSTART control statement there are one or more RGRUN control statements, one for every run cycle of the run cycle group.

The ADRULE control statement must immediately follow the RGRUN statement.

Format


1  RGSTART?  ACTION (
2.1! ADD
2.1 SETDEFAULT
1 )  RGNAME (
2.1 run cycle group name
1 )?  RGDESCR ('
2.1 descriptive text
1 ')?  RGCALEND (
2.1 calendar name
1 )?  RGDLDAY (
2.1! 0
2.1 number of days
1 )?  RGDLTIME (
2.1 hhmm
1 )?  RGIATIME (
2.1 hhmm
1 )?  RGJVTAB (
2.1 JCL variable table name
1 )?  RGOWNER (
2.1 owner ID
1 )

Parameters

ACTION (SETDEFAULT | ADD)
If you specify SETDEFAULT, the remaining keyword values that you specify on the RGSTART statement become default values for all RGSTART statements that follow. No run cycle group definition is updated. Keywords that you do not specify are assigned their standard defaults.

If you specify ADD or use it by default, the statement can result in an update of the database.

RGCALEND (calendar name)
The name of a calendar used by the entire group (of up to 16 characters). This field is optional. The run cycle group calendar is superseded by the calendar name specified for each run cycle, if any. If none is specified, the DEFAULT calendar is used.
RGDESCR ('descriptive text')
A description of up to 50 characters. This field is optional.
RGDLDAY (number of days | 0)
The number of days (from 1 to 99) from the input arrival day that the application should be completed in: 0 means that the deadline is on the same day as the input arrival day. This must be an integer.

This value becomes the default deadline day for the entire group. It is overruled at run cycle level by a value in the DLDAY keyword of RGRUN.

RGDLTIME (hhmm)
The deadline time that the application should be completed by, in the format hhmm.

This value becomes the default deadline time for the entire group. It is overruled at run cycle level by a value in the DLTIME keyword of RGRUN.

RGIATIME (hhmm)
The default input arrival time that will be generated by this run cycle group in the hhmm format. This field is optional, but if you do not specify here a value for the whole group, you must specify input arrival times for each run cycle of the group in the RGRUN control statement.
RGJVTAB (JCL variable table name)
The name of the JCL variable table associated with the run cycle group (up to 16 characters). This field is optional. The run cycle group variable table is superseded by the variable table specified for each run cycle, if any.
RGNAME (run cycle group name)
The name of the run cycle group. The name must be from 1 to 8 alphanumeric characters long and must start with a letter or national character. This field is required.
RGOWNER (owner ID)
The run cycle group owner's name (from 1 to 16 characters). This field is optional.

Examples

This example sets defaults for all following RGSTART statements:

RGSTART  ACTION(SETDEFAULT) RGOWNER(PAYGRP) RGCALEND(PRPCAL)
     RGJVTAB(PRPTABLE)

In this example, the batch loader will create the PERPAY13 run cycle group. This statement must then be followed by a number of RGRUN statements (one for each run cycle that will be in the PERPAY13 run cycle group) which in turn must be followed by their own ADRULE statement.

RGSTART  RGNAME(PERPAY13) RGDESCR('Run cycles for periodic payments of 2013')
         RGCALEND(PERCAL13) RGJVTAB(PRPTABLE) RGOWNER(PAYGRP) RGDLDAY(1)
         RGDLTIME(12.00)
 RGRUN NAME(RC1PP13) DESCR('Run cycle 1 of rcgroup PERPAY13')...<other keywords>
 ADRULE <keywords>
    RGRUN NAME(RC2PP13) DESCR('Run cycle 2 of rcgroup PERPAY13')...<other keywords>
    ADRULE <keywords>
 ...
 RGRUN NAME(RCnPP13) DESCR('Run cycle n of rcgroup PERPAY13')...<other keywords>
  ADRULE <keywords>