Bad SMF14 and SMF15 records are produced when the IBM APAR OA51325 is not applied - TLMS.

Products

• TLMS Tape Management

Issue/Introduction

When clients run the TMSCSMF Utility, they receive 0 records for TYPE 14 and TYPE 15 records:
FIRST SMF RECORD READ: 00:00 2017/018 
LAST SMF RECORD READ: 08:00 2017/018 
TOTAL SMF RECORDS READ: 2,822,877 
TOTAL TYPE 14 RECORDS SELECTED: 0 
TOTAL TYPE 15 RECORDS SELECTED: 0 
TOTAL SMF RECORDS NOT SELECTED: 2,822,877 

Environment

CA TLMS Tape Management R14.0
CA TLMS Tape Management R12.6

Cause

What prevents TYPE 14 and TYPE 15 records from being selected by TLMSCSMF is because IBM PTF OA51325 has not been applied. The reason the job didn't run correctly was due to the fix not being on in the first place so the SMF data that was being captured wasn’t tracking all the information CA TLMS needed.

Resolution

The client will need to apply IBM PTF OA51325 in order for the SMF data to be in good condition and to be captured correctly when TLMSCSMF is run. T

 

Additional Information

Please Note: The IBM PTF OA51325 will only apply to new SMF data that is being produced and will not work retroactively for old SMF data.