In a recent note, John Mattson said:
> Date: Thu, 3 Aug 2006 16:15:56 -0700
>
> 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.
>
Likewise, from:
# 4.4 "z/OS V1R5.0 MVS JCL Reference"
4.4 Backward References
The following statements cannot be referenced:
[ ... ]
* Nested procedure statements
Why? Seems like another case if IBM's missing the point when
implementing a Requirement. Surely, the objective of the Requirement
for nested JCL PROCs was not that nested PROCs should provide all
the capabilities of first-level procs _except_ backward references,
RESTART, (others ... ?).
Should I browse V1R7.0 to see if there's any improvement?
-- gil
--
StorageTek
INFORMATION made POWERFUL
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
