AIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: PDSEGEN - 2 years old
That's it for me. I like JCL and working source libraries to have 2-5
generations just so I can go back if the need arises (or I just
accidentally save when I didn't really want to).
As a side note, the other "improvements" with
That's it for me. I like JCL and working source libraries to have 2-5
generations just so I can go back if the need arises (or I just
accidentally save when I didn't really want to).
As a side note, the other "improvements" with PDSE V2 seem to cause
problems when trying to scroll max down
So, I'm curious: What are people actually USING member generations for?
For source code, it seems like a decent source control system is a better bet.
Are member generations primarily a form of "oops recovery?"
-- Jerry
--
Lionel,
Congratulations and happy anniversary to PDSEGEN.
I wanted to let you, and the rest of mainframe world, know that File-AID/MVS
from Compuware introduced support for PDSE V2 Member Generations in July, 2015
in release 16.3. Our current GA release, 17.2, has continued to provide
I wanted to let y'all know that PDSEGEN turns 2 years old tomorrow - 5/26. That
is the day that I created the very first alpha version of PDSEGEN using
information from Thomas Reed's SHARE presentation on how to access PDSE V2
Member Generations.
Since then it has grown thanks to the input,
