IBM send out a Red Alert Notification on November 4th.
- TITLE: Update to 2016.11.02 z/OS V2R2 VTOC Alert
Potential for loss of access to data on a volume due to erroneous 'End of File' written to the VTOC on z/OS V2R2 DFSMS (HDZ2220)
Are there any CA-Allocate implications ?
We took the local fix option of setting SSR Disabled. Are there any CA-Allocate implications in doing this ?
CA Allocate, when correctly configured, will eliminate any x37 abend.
If a specific E37 abend does occur due to an environmental event out of the control of CA Allocate, then the VTOC error condition described by the IBM RED ALERT could occur.
CA Allocate does not directly update the VTOC on a volume.
As usual if you have any further question, please contact CA Allocate support