Doubt about EVENT trigger behavior x Command timmings

[Thaina Muntoreanu]

Hi,

I would like to know if, within an application, when an event is triggered, there is any execution priority order.

For example: if I have jobs that do not have a submission time set, they will automatically run as soon as the event is triggered. In the same application, I also have a task (without a runtime) that executes a command to put all jobs in the application on HOLD. Will this task take priority? Or could it happen that some jobs start running before the HOLD command is executed?

What I’m trying to achieve is that on a specific day only, the application is triggered in HOLD, so I thought of adding a task issuing a commando to HOLD all jobs within that appl, and I'm just trying to mitigate the risk of jobs starting to execute before the command is issued.

I am opened for suggestion on how to achieve it.

[Chris_Elvin]

Hi,

You are quite correct to worry about the execution priority/order of jobs that do not have predecessors within an application.  There is no guarantee what order the jobs might run.

You could create a TASK that is a predecessor to the jobs and this TASK is only scheduled on the days when you wish to hold the work.  On these days, the TASK would start and require completing before the other jobs can run.  Of course the TASK would need to have all the required jobs explicit;y defined as successors.

A slightly simpler approach would be to use the APPLSTART workload object.  This is like a self-completing task and it is implicitly the predecessor to all jobs within the application.  Therefore if an APPLSTART job is held, no jobs in the application will run.  The code snippet below will cause the APPLSTART job to be generated only on Saturdays meaning that on Saturday, all job in the applications will be held waiting the release of the APPLSTART job

APPLSTART job_zero HOLD
  RUN SATURDAY
ENDJOB

[Thaina Muntoreanu]

Thanks @Chris_Elvin

Appstart will work perfectly! =)