Preventing ESP from posting EXTERNAL and MANUAL JOBs as soon as the APPL is created

Products

• ESP Workload Automation

Issue/Introduction

When using scheduled instead of Scope, the SCHEDULED statement prevents the EXTERNAL from being satisfied causing an event to be triggered early.

 

 

 

 

Environment

Component: ESP Workload Automation
Release:   12.0

Resolution

Use the SCHEDULED statement instead of SCOPE. The SCHEDULED statement prevents the EXTERNAL from being satisfied when an event is triggered early.  When an APPL that uses scope is triggered early, the external may be satisfied since the external job is completed within the SCOPE time. 

Example 1: ESP will only look for the application scheduled to build at 6 AM today. The scheduled time is found in the event.  
JOB MYJOB EXTERNAL APPLID(myappl) SCHEDULED('06:00 today')

Example 2: No matter when this application is created, ESP will only look for the application that is scheduled between 6 AM today to 6 AM tomorrow:
JOB MYJOB EXTERNAL APPLID(myappl) SCHEDULED('06:00 today until 06:00 tomorrow')

NOTE: The SCHEDULED statement will work correctly when schedules are running behind.
             The SCOPE statement may not look back far enough. This will cause some schedules to hang. It's best to use SCHEDULED in every case.