Creating time-dependent operations

Usually, the input arrival time of an operation is not the time when HCL Workload Automation for Z starts an operation. HCL Workload Automation for Z tries to maximize the throughput of work in your system by starting as many operations as quickly as possible in any one day. Some operations might not be started because the resources they require are not available, a predecessor has not completed, or the workstation on which they run is closed. If an operation can run (that is, if all its predecessors have completed and resources are available), HCL Workload Automation for Z usually starts the operation regardless of its input arrival time or the time of day.

For example, when you run jobs on distributed agents, the JTOPTS SUPPRESSPOLICY parameter affects the actual start time. If you specify the suppress if late option, the value of SUPPRESSPOLICY also impacts the start of late operations.

For most operations, this is exactly what you want. However, you often need to run jobs or started tasks at a particular time of day or at regular intervals throughout the day. To do this, make the job operation time-dependent on the MVS™ JOB OPTIONS panel (EQQAMJBP - Job, WTO, and print options ). The following steps describe what happens when HCL Workload Automation for Z starts a time-dependent operation, and what happens if it is late:

  1. Is the operation time-dependent?
    1. Yes: continue with step 2.
    2. No: HCL Workload Automation for Z starts the operation as soon as it is added to the current plan or as soon as its dependencies are met.
  2. Is it the input arrival time?
    1. Yes: continue with step 3.
    2. No: wait for the input arrival time. Continue at step 2.
  3. Is the operation ready?
    1. Yes: continue with step 4.
    2. No: wait until the operation is ready. Continue at step 3.
  4. Does the operation have the suppress-if-late attribute (see Options that apply to all operations)?
    1. Yes: continue with step 5.
    2. No: HCL Workload Automation for Z starts the operation.
  5. Does the SUPPRESSPOLICY allow more time for this operation?
    1. Yes: HCL Workload Automation for Z starts the operation.
    2. No: give the operation a status according to the SUPPRESSACTION option (C, E, or RL).

An operation with the status RL can be started only after manual intervention. For details about the SUPPRESSPOLICY and SUPPRESSACTION parameters see the JTOPTS statement.

Only for trackers using JES2 for z/OS V3.1, or later: When a time-dependent operation scheduled on a tracker is ready to be run and you have set the JESSYMBOL HOLDUNTL parameter in OPCOPTS, the operation will be sent to the tracker at the time resulting from the IA time minus the seconds set in JESSYMBOL HOLDUNTL. On the tracker, JES2 holds the operation until the time dependency is resolved and optimizes the resources required for execution, then the operation is run. This applies only to jobs that run on computer automatic workstations, except for virtual and started-task workstations.

If the operation allocates special resources, consider that they might be remain allocated for a longer time.