Browse Prior Art Database

SAP Job Scheduling with Dependencies on Jobs That Do not Yet Exist Disclosure Number: IPCOM000015486D
Original Publication Date: 2002-Jan-05
Included in the Prior Art Database: 2003-Jun-20

Publishing Venue



Disclosed is a program that performs job monitoring in SAP. SAP by itself has limited job scheduling (i.e. batch) functionality. Tivoli Workload Scheduler (also known as Maestro) is an add on tool that provides much more functionality for job scheduling. However, what the Tivoli Scheduler software lacks is the capability to build dependencies on jobs that do not exist at the time the schedule is established. This program used in conjunction with Tivoli Workload Scheduler provides that functionality in an SAP environment. This program has been created with the purpose of checking the status of other jobs in the system. This program is to be executed as an SAP job to search for the completion of jobs that other jobs are dependent on. This program is to be set up as one of the jobs in the Tivoli Workload Scheduler schedule. Also, in the same schedule, the job with a dependency on the job that does not exist at the time the schedule is initiated would be set to be dependent on completion of the disclosed program. The program would monitor for the creation of the necessary job and complete after it detected that the job on which there is the true dependency completes. Example of Problem: In Fig. 1 is the typical scenario that highlights the circumstances in which the disclosed program would be necessary. Job B creates Job C, and Job A is dependent on Job C. Job C does not exist at the time the schedule is initiated (because it does not exist until Job B completes). Therefore, there is no way in SAP to schedule Job A to run following Job C. Under these circumstances, the SAP system administrator would have to manually monitor the system to verify that Job C had been created and completed and then manually execute Job A. Figure 1