CA1 remove a system from a sysplex system

Products

• CA 1 Flexible Storage

Issue/Introduction

What are the tasks to complete for CA1 when a system is removed from a sysplex ?

Resolution

If a shared BLOCKSET AUDIT is no longer going to be used by a system (such as when it is being shut down, decommissioned, quiesced, or reconfigured to use a different TMC/Audit combination), CA 1 must be made inactive before shutting down, quiescing, or reconfiguring.
By making CA 1 inactive, the CPU identification maintained in CTL#5 is removed for this LPAR. If CA 1 is not made inactive, an obsolete CPU entry is left in CTL#5, which makes TMSCOPY unable to clear the entire AUDIT file, and eventually results in 7yy-104 abends.

Advise that the following ptfs be applied :
  _ SO14858 TMSUDSNB - ADD NEW CONTROL STATEMENTS TO TMSUDSNB.
  _ SO09456 TMSCOPY INCREASE WINDOW WHEN DETERMINING INACTIVE LPARS
   _ SO08332 TMSCOPY DETECT A POSSIBLE ORPHANED BLOCK IN A BLOCKSET AUDIT
   _ SO05090 TMSAUDIT REPORT WITH TIME= DOES NOT SHOW SECONDARY FILES
   _ SO01864 TMSCOPY - RARE U1005 RC24 WITH A BLOCKSET AUDIT
   _ RO97172 TMSXT56E WITH BLOCKSET AUDIT AND EXCLUDED CPU
   _ LU12678 RARE CORRUPTION OF THE CA 1 AUDIT CONTROL RECORD
   _ LU05507 TMSCMD THRESHOLD VALUES INVALID FOR UNBLOCKED AUDIT DATASET
   _ LU03157 TMSCOPY U1005-24 ABEND IF INVALID BLOCKID FOUND IN TMSCTL#5

Before removing a system from a sysplex, the following tasks should be completed for CA1: 
- stop any tape activity on this system 
- stop  CA 1 batch utilities 
- disable the Vantage™ Storage Resource Management script for CA 1 
- Stop  CTS
- shutdown CA1 by answering with the SHUTDOWN value to the IEFTMS0 message.