GETDATES – Generate a list of run dates from a run cycle rule

Use the GETDATES command to generate the run dates for an entire set of run cycles within an application, or a particular input arrival subset. To produce the list of run dates, the command uses the LIST GENDAYS and MERGE commands internally.

GETDATES    ADID(<application>) [TYPE(A|G)]
            [STATUS(A|P)] 
            [VALID(<valid-on>)] [IAT(hhmm] 
            [FROMDATE(<from>)] [TODATE(<to>)] [SAVELIST(<pfx>)]
            [OUTPUT(ALL|COMBINED|INDIVIDUAL)]

where:

<application>: The name of the application for which to generate the run dates. By default, the command assumes the ACTIVE version of this, as an APPLICATION definition only, that is valid on the day the command runs. TYPE can be used to look for GROUP definitions and STATUS can be used to calculate dates for PENDING versions.
<valid-on>: The date used to find the version of the application. By default, it uses the current date.
hhmm: The input arrival time to select matching run cycles to calculate the run dates from. For applications that might have multiple runs within one day, this allows a specific single run to be calculated. If omitted, the run dates for all run cycles are calculated.
<from>: The date from which the run dates are calculated, in the format YYMMDD. The default is the current date.
<to>: The date until which the run dates are calculated, in the format YYMMDD. The default is the FROMDATE value plus 90 days.
<pfx>: The name of the SAVELIST to be produced, containing the combined run dates for all run cycles. This is also used as a prefix of internally generated SAVELIST for run cycle. It is required that SAVELIST entries are generated to enable internal use of the MERGE command to calculate the composite effect of all run cycles.

Output can be in the form of a SAVELIST and optionally output files if an OUTPUT GNDAY statement has been coded ahead of the command. The SAVELIST output can be used to generate interval dates within Periods using the PRSTART DATELIST keyword.

The amount of output can be influenced by the OUTPUT keyword, which can have the following values:

ALL: Generates SAVELIST and optionally file output for each individual run cycles and the combined result for all of the run cycles.
COMBINED: Only generate SAVELIST and optional file output for the combined result for all of the run cycles.
INDIVIDUAL: Only generate SAVLIST and optional file output for each individual run cycle. Do not generate any combined output.

Note:

For run cycles using the EVERY or UNTIL, only the initial Input Arrival time is used to select the run cycle with the IAT keyword.
Run cycle level SAVELIST output is named using the SAVELIST prefix followed by _cccc, where cccc is the run cycle sequence number.
For run cycles of type N and X, a rule definition is automatically generated internally, therefore the LIST GENDAYS command can calculate offsets of a period, for example ONLY(1) DAY(DAY) PERIOD(MYDATES). Period based run cycles can generate more offsets than a rule definition can support (11 positive and 11 negative). In these instances, multiple rules are generated until all of the period offsets have been accounted for. The run cycle SAVELIST name will be suffixed with _cccc_iiii, where cccc is the run cycle sequence number and iiii is the instance number of the multiple rules generated for the single run cycle.
For the limitations related to FROMDATE and TODATE, see LIST GENDAYS – Generate dates from a rule.
The LIST GENDAYS PIF call uses the same internal HCL Workload Automation for Z code that is used to generate the dates for GENDAYS in ISPF.
The GETDATES command is available only starting from HCL Workload Automation for Z V8.6 SPE, or later.