Just remember that in a multi-system MAS, the default is for
converter/interpreter processing can occur on any member of the
MAS. So there is always the possibility that jobs submitted at the
same time could have a C/I processing delay such that a later job
actually get accepted for execution before the desired job.
At 01:17 PM 3/3/2022, Frank Swarbrick wrote:
I've long (ever since we started our migration from VSE to z/OS in
2008) disliked the default of DUPL_JOB=DELAY, but I was overridden
in setting NODELAY because of the "it's always been this way"
attitude, and lack of desire to determine if there were any
dependencies on the behavior.
I am curious (but not hopeful) if there is anything available to log
or otherwise note when a job is delayed because it has the same name
as a job that is already running. Specifically, I am looking to
find processes that depend on the DELAY behavior.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
