See these recent APAR closures to resolve the PDSE scroll max issue and one other:
APAR or PTF Updated Status CC Component Abstract and comments OA55431 6/7/18 CLOSED PER ISPF Z/OS PDF&S AN ABEND 002-A8 OCCURS DOING A SCROLL MAX DOWN ON A PDSE MEMBER OA54890 6/6/18 CLOSED PER EXTENDED DATA S IEBPDSE DETECTED PDSE DIRECTORY CORRUPTION FOLLOWING AN ISPF IEBPDSE I prefer to use member generations rather than a full blown source control system for my personal JCL, REXX, ISPF Panel, and a few other libraries. I keep up to 20 generations while working on updates and will then prune down to 1-3 after things are looking solid and then prune down to 0 generations when I'm truly happy with the updates. Prune is a feature of PDSEGEN that deletes generations while leaving the requested number of generations alive. -------------------------------------------------------------------------- Lionel B. Dyck (Contractor) <sdg>< Mainframe Systems Programmer – RavenTek Solution Partners -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Steve Smith Sent: Monday, June 11, 2018 9:00 AM To: [email protected] 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 PDSE V2 seem to cause problems when trying to scroll max down through large members. This is almost certainly a bug, and it may have been fixed already, or at least will be. But unless I need generations, I usually stick with V1. sas On Mon, Jun 11, 2018 at 9:48 AM, Jerry Callen <[email protected]> wrote: > 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 > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- sas ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
