TMSCOPY RC=0 as AUDIT is NOT cleared

book

Article ID: 132090

calendar_today

Updated On:

Products

CA 1 Tape Management CA 1 Tape Management - Copycat Utility CA 1 Tape Management - Add-On Options

Issue/Introduction

Why CA1 was unable to provide an alert on the fact the AUDIT was not cleared and Lpars were locked after a while?
It would have been good to get such alert with an RC different from 0 and a warning message from TMSCOPY, so we could have reacted quicker and not lost a lot of money. 

Environment

Release: ONE...00200-14.0-One-TAPE MANAGEMENT
Component:

Resolution

Apar ST08332 needs to be applied and a new message is created as alert.
 
IEFTMS48 WARNING! WARNING! WARNING!                                       
    TMSCOPY WAS NOT ABLE TO RESET CONTROL RECORD                          
    VALUES TO RELEASE ALL BLOCKS THAT WERE BACKED                         
    UP IN THE AUDIT FILE.                                                 
    CONTACT CA 1 SUPPORT FOR ASSISTANCE IN                                
    DETERMINING WHETHER AN ORPHANED LPAR EXISTS                           
    IN YOUR BLOCKSET AUDIT DATA SET.                                      
                                                                          
Reason:                                                                   
This warning is issued when a BLOCKSET AUDIT dataset is used and one      
of the CPU entries in TMSCTL#5 may contain a CPU whose BLOCKID is         
is significantly less than the Audit's NEXTAVAIL value.                   
                                                                          
Action:                                                                   
Prior to contacting CA 1 Support regarding this warning, execute CA 1     
Utility TMSBINQ with a control statement of HEADERS.                      
If it is determined that one of the LPAR names in TMSCTL#5 is available   
but no activity has been recorded from that system for many hours,        
simply start TMSINIT on that LPAR, this will force a new BLOCK to be      
assigned. Then execute TMSCOPY BACKUP again and this message should       
not be issued.                                                            
If you determine that an orphaned CPU exists in TMSCTL#5 and that         
system is no longer available, then contact CA 1 Support for              
assistance in removing that CPU from TMSCTL#5.