Setting Up a Job Dependency

In many cases, a job should run only after some external requirements are satisfied. For example, a job may need data generated by another job, or it can run only after another job has completed successfully.

Tidal Automation has the flexibility to encompass the different scheduling needs encountered in a business environment. You use job dependencies to prevent a job from running until the preceding job completes or enters a predefined status. You can also set jobs to run only when manually released.

In this chapter, we are going to define (add) a job called Inv21. We will assign a calendar to this job, but we will also make it Require operator release. Even if according to its calendar, the job is due to run, it does not run until it is released from Waiting on Operator status. We will define a second job, Inv22, which depends on Inv21. Inv22 does not run until Inv21 completes normally. Finally, we release Inv21, and the jobs end with a Completed Normally status.

Interdependence of Inv21, Inv22, and the Operator

The chapter describes how to:

• Define a job that waits for an operator to release it

• Define a job that depends on the completion of another job

• Monitor jobs and job dependencies

• Release a job that requires operator intervention

To complete the exercises in this tutorial, you need to:

• Install Tidal Automation in the TA default directory (or the examples in this tutorial will not work properly).

• Select the Super User option in your User definition.

• Configure a default agent.

• Create and have available the work day calendar.