Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
PDSE Member Generations z/OS DFSMS Using Data Sets SC23-6855-00 |
|
Version 2 PDSEs support multiple levels, or generations, of members. This allows you to reverse or access recent changes to a member. It also allows you to retain multiple generations of a member for archival reasons. Member generations is similar to generations for data sets, which is described in Processing Generation Data Groups. Users can control member generation with these DD keywords in JCL:
System programmers can set the upper limit for MAXGENS with MAXGENS_LIMIT in the IGDSMSxx member of PARMLIB. For more information about PARMLIB, refer to IGDSMSxx in z/OS MVS Initialization and Tuning Reference. Programs can use macros to exploit member generations.
The member rename function retains generations. Old generations are retained under the original names. Any new generations are retained under the new names. If you create a member which has the same name as a series of previously created generations, the new member is associated with the existing generations. When a specific generation, or the current generation, is deleted, the other generations remain. Deleting a specific generation can create a gap between two generation numbers. You can fill in this gap by replacing one or more generations. A generation is retained until enough newer generations have been created to cause it to be deleted, based on the number of generations defined with MAXGENS. |
Copyright IBM Corporation 1990, 2014
|