We used Platinum products-Analyzer, Detector and Loganalyzer to discover all matters of DB/2 anomalies. It maybe that a Recover to RBA is order.They're now CA products. There's Redbooks on DB/2 recovery and restoration. One of the toughest was a table that had been backed up and dropped. Then on restoration the DBA had done a recreate of the table and then extended it and tried to reload. I forget the reason code but the Level-2 guy picked it up right away. Have to recreate the table reload it and then do the extend. Anyway with a log Analysis and SMF records should be able to converge on the solution.
In a message dated 3/30/2019 2:59:53 PM Central Standard Time, [email protected] writes: Bill A general note: The SMF records are described in z/OS Version 2 Release 3 MVS System Management Facilities (SMF) Find the version appropriate to your z/OS Operating system level. Note: Not all IBM collected records are described in there For example, in DFSMShsm Storage Administration is where the SMF records are discussed for DFHSM. Unless your shop changed the numbers, they are typically 240/241 So long as your z/OS System programmer or Stg Admin has set HSM to capture SMF, then you will need to determine how the SMF data is offloaded and stored at your shop. If you can issue the command F dfhsm-stc-name,Q SETSYS - that will show you what SMF Records are used. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
