RGRUN

Purpose

Use the RGRUN control statement to add a run cycle specification within a run cycle group. RGRUN statements follow the RGSTART statement that defines a run cycle group and are followed each by the ADRULE statement that defines the run cycle rule.

Format


1  RGRUN?  ACTION (
2.1! ADD
2.1 SETDEFAULT
2.1  NAME (
2.2.1 rule name
2.1 )
1 )?  DESCR ('
2.1 run cycle description
1 ')?  CALENDAR (
2.1 calendar name
1 )?  DLDAY (
2.1! 0
2.1 number of days
1 )?  DLTIME (
2.1 hhmm
1 )?  IATIME (
2.1 hhmm
1 )?  JVTAB (
2.1 variable table name
1 )?  RPTEVRY (
2.1 hhmm
1 )?  RPTENDT (
2.1 hhmm
1 )?  RULE (
2.1! E
2.1 1
2.1 2
2.1 3
2.1 4
1 )?  TYPE (
2.1! R
2.1 E
2.1 A
2.1 D
1 )?  SUBSETID (
2.1 subset name
1 )?  VALFROM (
2.1! current date
2.1 yymmdd
1 )?  VALTO (
2.1! current date
2.1 yymmdd
1 )

Parameters

ACTION (SETDEFAULT | ADD)
If you specify SETDEFAULT, the remaining keyword values that you specify on the RGRUN statement become default values for all RGRUN statements that follow. No application description 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.

CALENDAR (variable table name)
The name of the calendar used by this run cycle. The name can be of up to 16 characters. If it is not specified, the run cycle uses the calendar specified for the run cycle group.
JVTAB (variable table name)
The name of the JCL variable table to be used for the occurrences generated. The name can be of up to 16 characters. If it is not specified, the run cycle uses the variable table specified for the run cycle group.
DESCR ('run cycle description')
A free-format description of the run cycle, up to 50 characters and enclosed in single quotation marks.
DLDAY (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.

A value specified here overrules for this run cycle any value defined with RGDLDAY for the entire group.

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

A value specified here overrules for this run cycle any value defined with RGDLTIME for the entire group.

IATIME (hhmm)
The time, in the format hhmm, that the application is to arrive at the first workstation. If it is not specified here, the run cycle uses the input arrival time specified for the run cycle group.
NAME (rule name)
The run cycle name. It can be of up to 8 characters.
RPTENDT (hhmm)
The repeat end time for the EVERY options, in the format hhmm. It must be a time between the IA time of the run cycle and the calendar work day end time of the application.
RPTEVRY (hhmm)
The repeating frequency for the EVERY options, in the format hhmm. It specifies that the application has an occurrence in the long-term plan every hhmm, starting from the IA time to the repeat end time (RPTENDT keyword). If this keyword is not set, only the occurrence related to the IA time is added to the long-term plan.
RULE (1 | 2 | 3 | 4 | E)
Defines which free-day rule is in effect. See Selecting a free-day rule.
SUBSETID (subset name)
The run cycle subset identifier. If the run cycle is part of a subset in the run cycle group (this is useful to match more run cycles against negative rules or to use the logical AND condition), enter the name of the subset. It must be from 1 to 8 alphanumeric characters long and must start with a letter or national character.
TYPE (A | D | E | R)
Specify the type of rule-based run cycle. R (regular) means that the ADRULE statement specifies days when the application should be scheduled. E (exclusion) means that the ADRULE statement specifies days when the application should not be scheduled. A (regular for subsets) means that the ADRULE statement specifies days when the application should be scheduled if they match all A types of the set of run cycles belonging to SUBSETID. D (exclusion for subsets) means that the ADRULE statement specifies days when the application should not be scheduled if they match all D types of the set of run cycles belonging to SUBSETID.
VALFROM (yymmdd | current date)
The start date of the validity of this run cycle, in the format yymmdd.
VALTO (yymmdd | current date)
The end date of the validity of this run cycle, in the format yymmdd.

Example

In the following sample, the run cycle is type A, a regular run cycle that is part of the run cycle group subset named FIRSTH13, and is valid for the month of JANUARY 2013. The ADRULE statement immediately following this statement specifies that the application must run on every other work day of the ones specified in the CAL2013 calendar. The deadline for the application is 15.00 on the same day. The input arrival time is 10.30, but this is not necessarily the time that the application will start.

RGRUN NAME(RC1PP13) IATIME(1030) DLTIME(1500) TYPE(A) RULE(1) VALFROM(130102) 
VALTO(130201)CALENDAR(CAL2013) SUBSETID('FIRSTH13')
ADRULE EVERY(2) DAY(WORKDAY) MONTH(JANUARY)