RUNSTAT – Alter run cycle status
Modifies the unloaded values of the Valid From (ADRVALF
)
and Valid To (ADRVALT
) dates of each run cycle.
This affects the value in any generated Data or Batch Loader output.
It does not affect the database, unless you process the generated
Batch Loader output.
RUNSTAT
is designed to enable you to turn
off the planning capability of an application while still allowing
it to be submitted, so that the planning capability can be later reinstated.
Typically, this option is used for copying production schedules to
a test environment, or disaster recovery testing.
ACTIVATE
- Puts any run cycles that are Valid To
LOWDATE
back into effect withVALFROM
being the current Workload Automation Programming Language date andVALTO
beingHIGHDATE
(for example, 711231). RETAIN
- Do nothing with run cycle
VALFROM
andVALTO
values (default). SUSPEND
- Sets the
VALFROM
andVALTO
values toLOWDATE
(for example, 720101) for any run cycles for which the Valid To date is set to the current Workload Automation Programming Language date, or later.
- If you
SUSPEND
a run cycle with a Valid To date set to a future date other thanHIGHDATE
, this information is lost. When the application is later reinstated withACTIVATE
, it usesHIGHDATE
as the new Valid To date. - In the ISPF panels, the
VALTO
date is translated to an “Out of Effect” date. This means that the date listed in the “Out Of Effect” column is actually one day after the actualVALTO
date (with the exception ofHIGHDATE
, which is listed the same asVALTO
as opposed to the day after). It is important to understand this as a run cycle showing an “Out Of Effect” date in the panels of “today” will actually have aVALTO
date of “yesterday” and therefore not be affected byRUNSTAT(SUSPEND)
.