TMS Audit file size when running TMSOSCAT RESYNC and SYNC

Products

• CA 1 Flexible Storage

Issue/Introduction

How much extra space is needed for the CA1 TMS Audit file when running the TMSOSCAT RESYNC & SYNC utilities?

 

Resolution

Run a TMSCOPY BACKUP to reset the audit file.  If the audit file reaches it's threshold then run another backup . You can also have the MPF exit installed to automatically backup the TMC and Audit file.

When running TMSOSCAT PARM=SYNC/RESYNC:

1.  First run the RESYNC on whichever system has access to the most DSNs (this would normally be the system with shared access to the most catalogs, but this is not necessarily always the case).
2.  The RESYNC count of updates which would be for both entries in the catalog, but not listed as cataloged in the TMC, and vice versa, would be the first value to sum.  This job can both turn ‘on’ and ‘off’ the various catalog bits in the TMC.
3. The SYNC run on each of the other systems will have an upper bound on the number of possible updates, limited only by the count of records found in the RESYNC job which have "DSN - NOT- ON CATALOG=".  Since the SYNC job can only affect turning ‘on’ the various catalog bits, the only records it could possibly change are for those which are identified with "DSN - NOT- ON CATALOG=" in the RESYNC job.
4. Each SYNC job could have ‘overlapping’ records returned (i.e., records indicating that no catalog entry exists for the same data set).  Filtering out the unique records returned among all of the SYNC jobs as a whole would give an exact count of the remaining Audit updates to be added to the results from the RESYNC job (but this might not be necessary or practical – using the upper bound value determined from the RESYNC job is probably good enough, this value would be added to the full RESYNC count).
5. The formulas in the Utilities manual along with this sum value can then be used to determine the amount of extra space needed in the Audit file. TMSOSCAT

Allocate the TMC and Audit Datasets

 

 

 

Additional Information

Caveats that needs to be considered when running TMSOSCAT RESYNC and SYNC process :  

• TMSCOPY needs to be run before and after running the RESYNC and SYNC on all the LPARs.
• RESYNC should be run first and alone (specify PARM='RESYNC,TEST' to collect information without modifying the TMC).  
• The rest of the SYNC jobs can be run concurrently after the RESYNC job (specify PARM='SYNC,TEST' to collect information without modifying the TMC).  
• All of the above should be completed before the next run of TMSCLEAN.