ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Volumes are scratched in CA1 with ROBSCR set to NO and CTSSYNC isn't being run. How are volumes still getting scratched in OAM?

book

Article ID: 226627

calendar_today

Updated On:

Products

CA 1 Tape Management

Issue/Introduction

Volumes are scratched in CA1 via TMSCLEAN, but the CA1 ROBSCR parameter is set to 'NO', and CTSSYNC is not being run.  How are volumes still getting scratched in OAM? 

Environment

Release : 14.0

Component : CA 1 Tape Management

Resolution

In this case the CA1 ROBSCR parameter was set to 'NO', thus TMSCLEAN was not calling OAM in the usual manner to scratch the volumes in OAM, and CTSSYNC was not being run to notify and synchronize OAM. Also, the target volumes did not have the ROBTY and ROBID fields set in the TMC volume records. 

The CA1 parameter settings showed that parameter SCRTCH was set to YES and parameter XITS was set to TMSXITS.  This will result in a call to the security user exit pointed to by the CA1 'XITS' parameter.  In very old releases of CA1, this 'security' exit actually had a dual function: 1) allow the deletion of RACF TAPEVOL and discrete data set profiles during TMSCLEAN scratch processing, 2) notify auto-mounting tape devices that CA-1 has changed the status of the volser to scratch.  For these pre-r12.0 releases, a usermod was provided for the scratch function, and was delivered in the *.PPOPTION(CL05228/CL05228S) members.  With release 12.0 and beyond, this TMSXITS exit was modified to only provide the security feature, but the scratch function was replaced with the CA1 ROBSCR parameter option.  The reason the volumes were getting scratched in OAM for this case was because of use of this older version of the XITS exit.