ADRUN

Purpose

Use the ADRUN control statement to add a run cycle specification to an application description. To specify a rule-based run cycle, follow the ADRUN statement with an ADRULE statement. For a description of run cycles, see Creating run cycles. If you are specifying an offset-based run cycle, you supply all the information on the ADRUN statement.

Note: The ADRUN statement cannot be used to add run cycles to an application that is a member of a group; specify ADRUN when you create the group.

Format


1  ADRUN?  ACTION (
2.1! ADD
2.1 SETDEFAULT
1 )?  ADRJTAB (
2.1 var table name
1 )?  DESCR ('
2.1 run cycle description
1 ')?  DLDAY (
2.1! 0
2.1 deadline day
1 )?  DLTIME (
2.1 hhmm
1 )?  EIADAYS (
2.1! 0
2.2.1+ .,
2.2.1 start day from end of per
1 )?  IADAYS (
2.1! 1
2.2.1+ .,
2.2.1 start day from start of per
1 )?  IATIME (
2.1 hhmm
1 )
1  NAME (
2.1 rule name
1 )
1  PERIOD (
2.1 period name
1 )
2?  RPTENDT (
3.1 hhmm
2 )
2?  RPTEVRY (
3.1 hhmm
2 )
2?  RULE (
3.1! E
3.1 1
3.1 2
3.1 3
3.1 4
2 )
2?  SHIFT (
3.1! 0
3.1 number of days
2 )
2?  SHSIGN (
3.1! F
3.1 B
2 )
2?  SHTYPE (
3.1 W
3.1 D
2 )
2?  TYPE (
3.1! N
3.1 X
3.1 R
3.1 E
2 )
2?  VALFROM (
3.1! current date
3.1 yymmdd
2 )
2?  VALTO (
3.1! 711231
3.1 yymmdd
2 )

Restrictions

You cannot use ACTION(SETDEFAULT) to set default values for the NAME and PERIOD parameters.

Parameters

ACTION (SETDEFAULT | ADD)
If you specify SETDEFAULT, the remaining parameter values that you specify in the ADRUN statement become default values for all the ADRUN statements that follow. No application description is updated. Parameters 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.

ADRJTAB (variable table name)
A 16-character field that identifies the JCL variable table to be used for the occurrences generated. For offset-based run cycles, this JCL variable table overrides the one specified for the period. For rule-based run cycles, specify the JCL variable table here, because IBM Z Workload Scheduler ignores any JCL variable table associated with the period. The first character must be alphabetic.
DESCR ('run cycle description')
A free-format description of the run cycle, up to 50 characters and contained in single quotation marks.
DLDAY (deadline day | 0)
The number of days 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.
DLTIME (hhmm)
The time on the deadline day that the application should be completed by, in the format hhmm. For this parameter, there is no default value.

DLTIME is not required if you are specifying a period, rule, or run cycle group.

EIADAYS (start day from end of period | 0)
Depending on the value set for TYPE, this parameter defines one or more days relative to the start of the period when the application should be scheduled (TYPE N) or when it should not be scheduled (TYPE X). The numbers count from the end of the period; 1 is the last day.
IADAYS (start day from start of period | 1)
Depending on the value set for TYPE, this parameter defines one or more days relative to the start of the period when the application should be scheduled (TYPE N) or when it should not be scheduled (TYPE X). The numbers count from the start of the period; 1 is the first day.
IATIME (hhmm)
The time, in the format hhmm, that the application is to arrive at the first workstation. This parameter is required if you are specifying a period or rule.
NAME (rule name)
For rule-based run cycles, this is the name of the rule—up to 8 characters and unique for this application. Specify NAME, and type R or E, if you are creating a rule-based run cycle.
PERIOD (period name)
For offset-based run cycles, this is the name of a cyclic or noncyclic period defined in the calendar database. Specify PERIOD, and type N or X, if you are creating an offset-based run cycle.
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 parameter). If this parameter 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.
SHIFT (number of days | 0)
The number of days to shift the rule dates. This parameter is optional. It provides the means to define a run cycle relative to another, where the run cycle without the shifting offset is used to schedule an application in relation to which - using the same rule with a negative or positive shift of days - another application is scheduled.
SHSIGN (B | F)
Determines the negative or positive sense of the number defined in SHIFT. B (back) specifies that the shift is of a number of days before the dates generated by the rule. F (forth) specifies that the shift is of a number of days after the dates generated by the rule.
SHTYPE (W | D)
Defines the type of days that are to be counted for the shift. W implies work days, while D implies any day in the calendar. This parameter is required if you used SHIFT.
TYPE (X | E | R | N)
Specify R or E without IADAYS or EIADAYS when you create a rule-based run cycle. You must specify the NAME parameter, and an ADRULE statement must follow this ADRUN statement. 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.

Specify N or X together with IADAYS or EIADAYS when you create an offset-based run cycle. You must specify the PERIOD parameter. N (normal) means that the IADAYS and EIADAYS parameters define days when the application should be scheduled. X (negative) means that the IADAYS and EIADAYS parameters define days when the application should not be scheduled.

VALFROM (yymmdd | current date)
The start date of validity of this run cycle, in the format yymmdd. See the note under VALTO.
VALTO (yymmdd | 711231)
The end date of validity of this run cycle, in the format yymmdd.
Note: IBM Z Workload Scheduler interprets the yy part in the VALTO and VALFROM parameters as follows:
YY
Year
72 - 99
1972 - 1999
00 - 71
2000 - 2071

Examples

In the following sample, the first ADRUN statement is type R, which is a regular rule-based run cycle. The ADRULE statement immediately following this statement specifies the last work day of each month. The deadline for the application is 21.00 on the same day. The input arrival time is 9.00, but this is not necessarily the time that the application will start.

The second ADRUN statement is type N, which is a normal offset-based run cycle, so you must have defined a period called WEEK. The AD that is being built will be scheduled for the first day in each week. If the first day is a free day, the application is not scheduled for that week.

ADRUN NAME(LASTWD) IATIME(0900) DLTIME(2100) TYPE(R) RULE(1)
ADRULE ONLY LAST(1) DAY(WORKDAY) MONTH
⋮
ADRUN PERIOD(WEEK) IATIME(0900) DLTIME(2100) IADAYS(1) RULE(4)
In the following example, the statement is used to specify a shift of 2 work days before the last work day of the year.
ADRUN NAME(LSTWDYE) IATIME(0900) TYPE(R) RULE(1) SHIFT(2) SHSIGN(B) SHTYPE(W)
ADRULE ONLY LAST(1) DAY(WORKDAY) YEAR