Clarification of the scope of error resolved by SO09116

Products

• Disk Backup and Restore - MVS
• DISK BACKUP AND RESTORE- ADD-ON OPTIO
• DISK BACKUP AND RESTORE

Issue/Introduction

Regarding solution document SO09116, please help to clarify the scope of the error that is resolved in this solution document. SO09116 appears to reference messages generated by Top Secret. 

Does this mean that this error only impacts users of Top Secret or are users of other security managers, such as RACF and ACF2, also affected?

Environment

Release : 12.5

Component : CA Disk Backup and Restore

Resolution

This problem is link only with a security authorization failure.

It can occurs with whatever the security product used. 

The VSAM data set that must be released is not authorized to the customer which try to do the release. The consequence is than the rename which the Release perform fails and the return back to the previous state for the data set not bring the DSORG to its original state. This is a code failure that can be easily reproduced by giving read access only to the person who submit the release of this data set.

The VSAM release failed and the INDEX component returns as PS Dsorg which is bad. 

So as the description state into the PTF the security failure (S913) provokes an abend S0C4 into the Release job.

Additional Information

After applying PTF SO09116 to CA Disk r12.5, can users bypass S913-38 abnormal end?

No, this is a security tool message that can't be bypassed and are not managed by CA Disk.

 

After applying PTF SO09116, if the user executes IDLE-SPACE-RELEASE job with a User-ID lower than RACF READ authority for the VSAM data set, does CA Disk r12.5 printing warning message and bypass IDLE-SPACE-RELEASE process?

Not exactly, let me explain what we have done and what the result will be with the PTF applied.

We do have corrected the return code from our program. We add a new print flag for data set which does not release idle space. We add ESTAE logic and add a new return code if open abend.

If we get no zero-return code, then we don't update the catalog and VTOC.

If you have a list of data sets to be released and one of them is not authorized as UPDATE for you, then we let the security tool send the S913-38 message and set a return code 8 associated with messages 2132 and 9999 into the MSGPRINT.

 

Please show us the effect of SO09116 more concretely.

Before the PTF is applied, you run RELEASE and got S913-38 with S0C4. The DSORG for the INDEX component is changed to PS.

With the PTF applied, you run RELEASE and got S913-38 with RC8. The DSORG for the INDEX component is not changed and stay as VS.

Additional messages are now written into the RELEASE output job to point you on the S913 data set name in cause.

 ADSDM425 2132 S913-38 ABEND OCCURRED PROCESSING VOLUME=vvv,DSNAME=..

 ADSDM465 9999 SYSTEM ERROR PROCESSING DSN = dataset.name

 ADSDM465 9999 ABEND OCCURRED DURING PROCESSING