One interesting anomaly with PDSE generations is if you delete a member using tso delete then the generations are not deleted. If you use LMMDEL to delete a member (you can't delete an individual generation) then the member and all generations are deleted.
BUT the anomaly is that if you then create a new member using the former member name then the absolute generation numbers will start where the deleted member generation numbers ended. Definitely not intuitive. -------------------------------------------------------------------------- Lionel B. Dyck (Contractor) Mainframe Systems Programmer Enterprise Infrastructure Support (Station 200) (005OP6.3.10) VA OI&T Service Delivery & Engineering -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Tom Marchant Sent: Tuesday, June 07, 2016 8:33 AM To: [email protected] Subject: [EXTERNAL] Re: Survery PDSE MAXGENS_LIMIT On Mon, 6 Jun 2016 20:08:32 -0500, TonyB-IBM-MAIN wrote: >Does the generation counter get incremented when a member is output of a batch >job? AFAIK, when a member is written, the normal (default) behavior is to create it as a new generation if that is the way the PDSE was created. An old generation will fall off the end if the limit had been reached. In ISPF you can override this behavior with SAVE NOGEN. I assume that there is a way for a batch job to do the same, but I don't know how. -- Tom Marchant ---------------------------------------------------------------------- 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
