J***@ibm-main.lst
2006-08-03 23:16:23 UTC
Nested JCL procs can be quite useful, but RESTART= seems to only allow
JOBSTEP.PROCSTEP and when you are doing nested procs, this is just not
enough. You would need something like JOBSTEP.NESTPROC.PROCSTEP or
JOBSTEP.NESTPROC1.NESTPROC2.NESTPROC3.PROCSTEP and so on. Looking at the
JCL manual, it appears that there is just no way to do such a restart for
nested procs if the step you want is WITHIN a nested proc. Anyone have
any way of getting around this? My scheduling program seems to deal with
it properly, but using the scheduler for my testing is a bit cumbersome.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
JOBSTEP.PROCSTEP and when you are doing nested procs, this is just not
enough. You would need something like JOBSTEP.NESTPROC.PROCSTEP or
JOBSTEP.NESTPROC1.NESTPROC2.NESTPROC3.PROCSTEP and so on. Looking at the
JCL manual, it appears that there is just no way to do such a restart for
nested procs if the step you want is WITHIN a nested proc. Anyone have
any way of getting around this? My scheduling program seems to deal with
it properly, but using the scheduler for my testing is a bit cumbersome.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html