Restarts with GDGs is one thing z/VSE is much better at. Once a GDG is
created in a step, it becomes the current GDG for all following steps.
So, following steps don't need to reference +1, then require a change
during a restart.
It part of the difference that z/OS reads the whole job in then
allocates everything where as z/VSE only reads the following JCL after
the previous step has completed.
Tony Thigpen
John McKown wrote on 07/11/2018 01:30 PM:
On Wed, Jul 11, 2018 at 12:01 PM Jesse 1 Robinson <jesse1.robin...@sce.com>
wrote:
I, like many here, am old enough to remember how much of a PITA
it was to restart a job when a step failed for some reason. Mainly deleting
datasets, but also changing GDG relative generation numbers if the restart
is after the step which created the new GDG which is used in subsequent
steps. {shudder}
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
