MVSFORUMS.com

[serobinson]

Our shop wants to convert 40 or so data sets. That means inccrease length and reformatt data. We intend to do this by running a job after CICS but before nightly processing. What is the best way to convert the data sets without causing GDG refrences problems? Considering the range of generations refrenced in nightly batch processing, the bases have low GDG limits, and the oldest generation is scratched.

We intend to use File Mananger for the conversion so that isn't an issue for this post.

[superk]

Create new datasets with the same generation, but a different version, i.e.:

for generation HLQ.SOME.THING.G0001V00

create the new re-formatted dataset HLQ.SOME.THING.G0001V01

[serobinson]

Thanks Superk. That is exactly what I'm looking for. Do I need to use an absolute generation number or is there a way to use a relative one? If you know of a good link, you can just post that. I have not been able to find one that answers all of my questions about GDG versions.
Therefore, I'm making some assumptions about versions. Correct me if I'm wrong.

1) GDGs with relative numbers access the newest version.
2) Creating a new version will not scratch other generations when the base is defined with the scratch attribute.

[dbzTHEdinosauer]

relative nunbers relate to a unique file. 0 is latest, -1 is 1 before the latest, etc...

A new version will scratch the oldest, when the newest causes the max number of versions to exceed the limit set during the gdg creation.
_________________
Dick Brenholtz
American living in Varel, Germany

[serobinson]

dbz I'm not sure that you understand what superk and I are talking about. You are talking about a generation(G0001). We are talking about a version(V01) of a generation. Also, the newest generation will only cause the oldest one to scratch if the base is defined with the scratch attribute. You can define the base with other attributes, for ex: NOSCRATCH.