CA 1 - Different state between TMC and Tape Volume Catalog for manually scratched volsers
search cancel

CA 1 - Different state between TMC and Tape Volume Catalog for manually scratched volsers

book

Article ID: 376954

calendar_today

Updated On:

Products

CA 1 Flexible Storage

Issue/Introduction

Volumes were updated manually to scratch them by changing the following flags:

e.g.:

 VOL  SCRATCH VVVVVV,NODSN            

 REP EXPDT=2024/214                   

 REP OUTCODE=HEXZEROS                 

 REP OUTDATE=ZEROS                    

 REP ROBTY=HEXZEROS                   

 REP ROBID=000                        

 Unfortunately the sample used removed the ROBTY and ROBID values. So, the volumes got scratch in the TMC but not in the Tape volume catalog.

ROBTY and ROBID were updated using below cards to the former values:

VOL VVVVVV,NODSN                                                                                            
REP ROBTY=81                                                                                                
REP ROBID=001                                                                                               
    VVVVVV UPDATED.                                                              * VOLUME IN SCRATCH STATUS 
        01 TMC RECORDS UPDATED    

But still the volume still remains private in the tape volume catalog

LINE       VOLUME USE      VOLUME              CHECKPT  LIBRARY   STORAGE   MEDIA     RECORDING             
OPERATOR   SERIAL ATTR     ERROR STATUS        VOLUME   NAME      GRP NAME  TYPE      TECHNOLOGY  COMPACTION
--(1)----  -(2)-- --(3)--  -------(4)--------  --(5)--  --(6)---  --(7)---  --(8)---  ---(9)----  ---(10)---
           VVVVVV PRIVATE  NO ERROR            NO       RITC001   VTTS01    MEDIA2    36TRACK     YES       
---------  ------ --------  ---------  -------------  BOTTOM  OF  DATA  -------------  ---------  --------  

 

Environment

Release : All

Component : CA 1

Resolution

Once the ROBTY and ROBID have been correctly updated, a CTSSYNC must be run. Example of the CTSSYNC for your reference below: 

//STEP1 EXEC PGM=CTSSYNC
//SYSIN DD  *
SYNC,VVVVVV-VVVVVV

https://techdocs.broadcom.com/us/en/ca-mainframe-software/performance-and-storage/ca-1-tape-management-system/15-0/utilities-and-reports/ctssync-utility-support-3495-3494-devices.html