We are rolling out PDSE V2 member generation capability to our users and in initial testing of CA-Disk Archive and Restore the generations are not restored and the PDSE V2 maxgen value is lost which prevents new generations from being created.
Is there a configuration setting or something that we have to do to enable generations support?
Envoyé depuis mon smartphone Samsung Galaxy.
Yes this is a feature which will be delivered in R14. It is not yet available for the actual R12.5 release.
I will check with the labs if that feature can be also delivred for the actual release and if yes when.
I will let you know,
Update from Development:
PDSE V2 support capabilities will be included in the Base PAX file for the CA-DISK r14.0 incremental release. The CA Disk r14.0 release is still in the planning stages so we have no target GA Date at this time. We are currently re-factoring a target for the initial Base PAX file, which will be the base starting point for the CA Disk r14 incremental release.
We are currently back at the drawing board for planning the timing of the Disk r14 release.There is no new target at this time. At this point we do know the Disk r14 release will notstart until at least the second calendar quarter of 2017.
Robert - thank you for the update. The lack of support in both CA-Alloc and CA-Disk is an impediment to rolling out PDSE Member Generations. We had a key user testing it last week when disk management moved his pdse and when he opened it after the move all his generations were gone. We have given everyone testing the caveats but it still surprises them.
Looking forward to your support when r14.0 ships.
I worked from home the last two days. I have your do and will read it on the way in tomorrow.
Thank you for sending it.
Sent from my iPhone
Thank you - our storage admin just received an e-mail with this info:
CA PML Solution Notification - RI91078 that explains that 12.5 has zero support for PDSE V2 member generations and that there is no circumvention at this time.
btw. the notification is in error in that the restored PDSE is restored as a PDSE V2 but without MAXGEN. The notification says it is restored as a PDSE V1
Actually since the version number is not specified when allocated, the version number is going to be set by the value of the PDSE_VERSION keyword in IGDSMSxx. So it is possible to get a PDSE version 2 at restore time even without preallocating.
RI91078 has been updated to define this: