I have two jobs: JOB_A & JOB_B. JOB_B is a successor to JOB_A. When JOB_A is bypassed, JOB_B still runs. How can this be setup so that if JOB_A is bypassed then JOB_B will also be bypassed?
The NOEXEC is not an ESP option.
I would recommend something like Jonathan's suggestion. Using this solution it is possible to bypass large blocks of jobs
The reverse is also possible.
Have the second job as a request job. If the first job is not bypassed it will issue the request command to request the next(s) job to run.
Let us know if you need an example..
That is the point of bypass is to let that happen.
Then don’t set to NOEXEC. Set to onhold or something.
Batch System Engineer
Batch Innovation Team
T (313)553-1727| C (770)502-5519
I do this by putting both jobs in a subappl and then bypassing the subappl with an AJ command in a task like this:
JOB CLEANUP_TASKS LINK PROCESS
ESP AJ BYPASS_DSNP270 COMPLETE APPL(%ESPAPPL..%ESPAPGEN)
ESP AJ COMPLETE_DSNP271 COMPLETE APPL(%ESPAPPL..%ESPAPGEN)
ESP AJ COMPLETE_EDIFECS COMPLETE APPL(%ESPAPPL..%ESPAPGEN)
To actually answer your question set both jobs to NOEXEC
Thanks Steve. Where would I place the NOEXEC option? In the case below, FINS_BUYSC4095_%ENVIR is the JOB_B I was referring to in my original post. Does the NOEXEC go on the AFTER ADD(FINS_BUYSC4520_%ENVIR) line?
RUN WORKDAYS LESS 1 DAY
RUN NWCLOSE_NYSEOPEN LESS 1 DAY
NORUN NWOPEN_NYSECLOSE LESS 1 DAY
NORUN MON TUE WED THU
ABANDON SUBMISSION 06:15 PLUS 1 DAY
ARGS %BUYSPATH./buys/bin/BUYS4955.sh -adminarea VLS1
ARGS %BUYSPATH./buys/bin/BUYS4095.pl -interface VLS1
"NOEXEC", thats a cool option, tho' Client's seem to have a hard time grasping the difference between "NE" and "OI"
Thanks - yes I would like to see an example of using a request job.
How is the first job getting bypassed?
The example works for both manual process or something during processing.
If it is bypassed manually do a "BYS" instead by the job in CSF to bypass all the jobs in the subappl COMPSUB.
If the job is bypassed automatically it would be important to know what goes in the "IF" statement.
Here is a simple example of a job that bypasses the next two if it is later than 17.00
IF %ESPATIME > 17.00 THEN DO
ESPNOMSG AJ COMPSUB BYPASS APPL(%ESPAPPL..%ESPAPGEN)
It is important if there are more jobs in the application to code another SUBAPPL statement so the remainder of the jobs in the application are not BYPASSED.
Let me know if you have any questions.
The bypassed is done individually by the job MONITOR perspective. I understand that if you turn on automatic trigger for jobs successors you can have a high impact on your workflow, quite different from when u do premeditatedly in DEFINE perspective.
What I do is put on HOLD processes that want to give bypassed and then give bypassed, soon after I give RELEASE.
Now I understand that, to meet your needs, the CA could create a BYPASSED option with jobs successors.
Retrieving data ...