Bypassing a job in dSeries

Document ID : KB000096821
Last Modified Date : 11/06/2018
Show Technical Document Details
Question:
Use Case: An interface file arriving on our UNIX server is extremely large. So large that it is causing delays in processing ranging anywhere from 3-7 hours behind schedule. There is a need to force complete the PeopleSoft job so it doesn't try to consume this large file.

Question: How can we bypass the PeopleSoft job so that it doesn't process this large file and cause unnecessary delays in processing?
Answer:
In order to be able to bypass the successor job, one should create an intermediate Link job between the job which is issuing the BYPASS and the job which is to be bypassed. This link is necessary because events process so quickly behind the scenes that the successor job may still trigger and begin processing. Adding the link creates a very short pause in the cycle and will allow the BYPASS to take place on the real job in the cycle.

Another solution would be to set a timed wait condition on the job to be bypassed to not submit before 1 minute. 

Best Recommended Solution: Create a link job dependency between the two jobs.