The issue of how to deal with PDSE member generations is one that I struggled with when developing PDSEGEN. The solution that I came up with was to allow individual generations to be deleted, which required writing a routine to do so as the native TSO DELETE and ISPF Delete options would only delete the base member without the generations at the time.
With PDSEGEN you always see a member list with the base member and all generations. With PDSEGEN you can delete the base member with a prompt informing you that you are deleting the base and all generations, or you can delete base member and have the -1 promoted to be the new base. Note that once a generation is deleted that you may not recover it due to the way the PDSE data store is architected. That is both good (never having to compress) and bad (inability to recover a deleted element). However, I believe this was the right decision by the developers. Now if only the standard ISPF application had these capabilities. Lionel B. Dyck <>< Website: https://www.lbdsoftware.com Github: https://github.com/lbdyck Worry more about your character than your reputation. Character is what you are, reputation merely what others think you are. - - - John Wooden ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
