Restrictions and considerations

Edit online

The following restrictions and considerations apply when you use DB Historical Data Analyzer in the TSO/ISPF environment.

Restrictions

  • A database whose attribute has been changed by DBD regeneration cannot be treated in the same way as before DBD regeneration. In this situation, all HISTORY data set entries for the database must be deleted before the database is processed by HD Pointer Checker. Otherwise, the results are unpredictable. This also applies to the migration situation from non-HALDB to HALDB.
  • DB Historical Data Analyzer applies only to the following database organizations:
    • HDAM
    • HIDAM (primary and index)
    • HISAM (including SHISAM)
    • Secondary index
    • PHDAM (partitioned HDAM)
    • PHIDAM (partitioned HIDAM)
    • PSINDEX (partitioned secondary index)
    Indirect list data sets (ILDS) used for PHDAM and PHIDAM are not analyzed.
  • In order to produce graph charts, Interactive Chart Utility (ICU) of Graphical Data Display Manager Presentation Graphic Feature is a prerequisite, and this program must be run under TSO/ISPF.
  • The database administrator must be familiar with the functions and operations of TSO/ISPF and GDDM® Interactive Chart Utility (ICU) to produce the HD Analysis graph.
  • While running DB Historical Data Analyzer in the TSO/ISPF environment, you cannot invoke DB Historical Data Analyzer from the DB Historical Data Analyzer panel, or have two dialog sessions in the split screen mode.
  • The HISTORY data set must be periodically reorganized to avoid performance problems with DB Historical Data Analyzer and the shortage of the available space on the HISTORY data set.

Considerations for HALDB Online Reorganization (OLR)

  • For a HALDB partition that is OLR capable, the utility shows the DD names and database data set names of the active data set groups (either (A-J&X) or (M-V&Y)) at the time of HD Pointer Checker's run.
  • The utility can work while a HALDB partition is in cursor-active status.