IBM Support

PQ80186: IMS V9 RUNUNDER SUPPORT FOR HP POINTER CHECKER V2

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible in next release.

Error description

  • IMS V9 RUNUNDER SUPPORT FOR HP POINTER CHECKER V2
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IMS High Performance Pointer    *
    *                 Checker for z/OS Version 2 Release 1         *
    *                 (FMID=HPC2210).                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: By the maintenance provided by this     *
    *                      APAR, IMS High Performance Pointer      *
    *                      Checker for z/OS Version 2 Release 1    *
    *                      is enabled to run on IMS Version 9      *
    *                      (Program Number 5655-J38).              *
    ****************************************************************
    * RECOMMENDATION: Apply the maintenance for this APAR.         *
    ****************************************************************
    IMS High Performance Pointer Checker for z/OS has been modified
    so that it can run on IMS Version 9.
    The main changes are to support the HALDB Online Reorganization.
     -HD Pointer Checker can process the active set of DBDS
      (A-J&X) or (M-V&Y). User can see the processed data sets
      by seeing the DBD name and data set name in the reports of
      HD Pointer Checker.
     -HD Tuning Aid can process the KEYSIN data set created from
      any side of DBDS, (A-J&X) or (M-V&Y).
     -Space Monitor and DB Historical Data Analyzer can process
      the HISTORY data set created from any side of DBDS,
      (A-J&X) or (M-V&Y).
     -DB Segment Restructure can process (A-J&X) or (M-V&Y) DBDS.
      FABRUNLD program unload the data base from the active
      set of DBDS. FABRRELD can reload the data base to (A-J&X) or
      update the segment data in the active set of DBDS.
    
       Note  HD Pointer Checker and DB segment Restructure
      cannot process the HALDB partition when the Online
      Reorganization is not completed.
    
    HD Pointer Checker can process the image copy data set created
    in large block interface by IMS Version 9 IC utility.
     Note  The image copy data set in large block interface created
    by IC2 utility cannot be processed.
    
    The layout of history record is changed. A new field is added
    and FABGHIR, DSECT macro of the history record, is changed.
    However, the preexistence history data set can be used as it is.
    
    The functional specification of PHIDAM primary index processing
    is changed. Before this APAR, when DATASET=IMAGECOPY is
    specified in the DATASET statement of primary index in the
    PROCCTL data set, the real data set was processed. After this
    APAR, FABP2047W is issued and primary index data set is not
    checked.
    

Problem conclusion

Temporary fix

Comments

  • Documentation Changes:
    The documentation is modified as follows:
    ==============================================================
      IMS High Performance Pointer Checker for z/OS, V2R1,
      User's Guide Vol.1 (SC18725700)
    ==============================================================
    PREFACE.3 Terms Used in This Book
    The following term is add to the list of IMS versions:
    | IMS Version 9       refers to IMS Version 9 Release 1
    --------------------------------------------------------------
    2.1.1.4   Restrictions
    Add the following restrictions:
    | If an HALDB is in two active sets of data sets (both A-J&X
    | and M-V&Y) because an Online Reorganization is not completed,
    | HD Pointer Checker is not able to run against them.
    --------------------------------------------------------------
    2.1.5.1.1 EXEC Statement
    Add the following statement to the list of the IMS documentation
    |      IMS Version 9 Installation Volume 3: System Definition
    |      and Tailoring
    2.1.5.1.2 DD Statements
      ddname  DD
    Add the following sentences at the end of ddname DD:
    | It is recommended to omit the DD statement of database data
    | set or image copy data set that the appropriate data base
    | data set or the latest image copy data set is selected and
    | allocated dynamically by HD Pointer Checker.
    | Consideration for an Online Reorganization (OLR) of HALDB:
    | If the data base is Online Reorganization capable and
    | you need to process the data set other than the data set
    | allocated dynamically, specify as the following instructions:
    |     For the real database data set, specify the DD name
    |     of the active DBDS.
    |     For the image copy data set, specify the DD name
    |     in according with DD= parameter in the DATABASE statement
    |     in the PROCCTL data set. If DD=*ALL is specified or
    |     DD= parameter is omitted, it is assumed that DD=A to J or
    |     X.
    --------------------------------------------------------------
    2.1.5.3.2 Database Data Set of HALDB
    Add the following sentence at the end of the chapter:
    | When it is an Online Reorganization capable data base, the
    | active set of DBDS registered in the RECON is allocated
    | dynamically with the active DD name.
    2.1.5.3.3 Image Copy Data Set
    Add the following sentence at the end of the chapter:
    | When it is an Online Reorganization capable data base, the
    | latest image copy data set registered in the RECON is
    | allocated dynamically with the same DD name as at the time
    | of the image copy was taken.
    --------------------------------------------------------------
    2.1.6.1.5 DATABASE Statement
      DD
        dsg-id or (dsg-id1, dsg-id2,...)
    Modify as follows:
           Specifies data set group to be processed. This option is
    |      valid for HALDB only. Letters A through J, M through V, X
    |      and Y can be specified for dsg-id. The letter L cannot be
           specified. If EPSCHK=YES is effective, ILDS can be
           evaluated automatically.
    |      Consideration for the Online Reorganization capable HALDB
    |        When DATASET=REAL is specified, the DD= parameter is
    |        ignored and always assumed as the DD of active DBDS.
    |        When DATASET=IMAGECOPY is specified, refer
    |        "Consideration for an Online Reorganization (OLR) of
    |        HALDB:" in
             "ddname DD" in "2.1.5.1.2 DD Statements".
    --------------------------------------------------------------
    2.1.7.2   PRIMAPRT Data Set
      The following report is changed:
        PROCCTL STATEMENTS REPORT
    2.1.7.3   STATIPRT Data Set
      The following reports are changed:
        SEPARATOR PAGE FOR DB/DSG (RUN TIME OPTION FOR DB/DSG)
        INTERVAL STATISTICS REPORT
        BIT MAP DISPLAY REPORT
        FREE SPACE MAP REPORT
        MAXIMUM FREE SPACE DISTRIBUTION REPORT
        INTERVAL FREE SPACE SUMMARY REPORT
        HD DATA SET STATISTICS REPORT
        DB RECORD DISTRIBUTION STATISTICS REPORT
    2.1.7.4   VALIDPRT Data Set
      The following reports are changed:
        VALIDATION OF A POINTER TO A TARGET AT SCAN REPORT
        SCAN OF INDEX DATABASE REPORT
        DESCRIPTION OF ALL SCANNED DATABASE REPORT
        VALIDATION OF A POINTER TO A TARGET AT CHECK REPORT
    2.1.7.5   EVALUPRT Data Set
      The following reports are changed:
        EVALUATION OF INDEX POINTERS AND KEYS REPORT
        EVALUATION OF ALL POINTERS TO THE SAME TARGET REPORT
        POINTER CHAIN RECONSTRUCTION
    2.1.7.6   EVALIPRT Data Set
      The following reports are changed:
        EPS HEALING REPORT
        EVALUATION OF ILKS REPORT
    2.1.7.7   SNAPPIT  Data Set
      The following report is changed:
        BLOCK MAP / BLOCK DUMP REPORT
    2.1.7.8   SUMMARY  Data Set
      The following report is changed:
        HD POINTER CHECKER SUMMARY (HALDB)
    --------------------------------------------------------------
    3.1.1.4   Restrictions
      To use HALDB, users will need to keep to following points in
      mind:
    Add the following consideration for an Online Reorganization of
    HALDB:
    |- HD Tuning Aid can process the KEYSIN data set
    |  even if some of the partitions are incomplete
    |  for the Online Reorganization.
    |  Regardless of the active set of DBDS,
    |  the DBD parameters and overrides report always shows
    |  the ddname for (A-J&X) data set representatively.
    --------------------------------------------------------------
    3.1.6 Output
     The following report is changed:
        DBD PARAMETERS AND OVERRIDES REPORT (PHDAM)
    --------------------------------------------------------------
    APPENDIX1.13.1.3 Messages
      The following messages are added:
    |  FABP1082E DG x POINTS TO DG y BY ODD RBA
    |    Explanation:
    |      The pointer contains an odd value RBA, although the
    |      active DBDS of the target partition is A to J or X. The
    |      pointer should contain an even value.
    |    System Action: Processing continues.
    |    Programmer Response:
    |      The database is probably damaged. Repair the database.
    |    Problem Determination: See Appendix B.
    |  FABP1084E DG x POINTS TO DG y BY EVEN RBA
    |    Explanation:
    |      The pointer contains an even value RBA, although the
    |      active DBDS of the target partition is M to V or Y. The
    |      pointer should contain an odd value.
    |    System Action: Processing continues.
    |    Programmer Response:
    |      The database is probably damaged. Repair the database.
    |    Problem Determination: See Appendix B.
    |  FABP1086E POINTER CONTAINS AN ODD VALUE
    |    Explanation:
    |      The pointer contains an odd value RBA, although the data
    |      base is not capable of an Online Reorganization. The
    |      pointer should contain an even value.
    |    System Action: Processing continues.
    |    Programmer Response:
    |      The database is probably damaged. Repair the database.
    |    Problem Determination: See Appendix B.
    |  FABP2047W PHIDAM PRIMARY INDEX OF DB: dbdname PART: partname
    |  IS NOT SCANNED BECAUSE OF AN IMAGE COPY
    |    Explanation:
    |      DATASET=IMAGECOPY is specified in the DATABASE statement
    |      of a primary index of PHIDAM data base.
    |      The primary index is not checked.
    |    System Action: Processing continues.
    |    Programmer Response:
    |      The image copy of the PHIDAM primary index cannot be take
    |      by IBM image copy products, so DATASET=IMAGECOPY is
    |      insignificant. Specify DATASET=REAL for checking the
    |      primary index of PHIDAM data base.
    |    Problem Determination: None.
    |  FABP2095E ONLINE REORG IS ACTIVE FOR DB: dbname PART:
    |  partname
    |    Explanation:
    |      The partition (partname) of HALDB (dbname) cannot be
    |      processed because an Online Reorganization had not been
    |      completed.
    |    System Action: Processing stops.
    |    Programmer Response:
    |      Correct the error, and rerun the HD Pointer Checker job.
    |    Problem Determination: None.
    ==============================================================
      IMS High Performance Pointer Checker for z/OS, V2R1,
      User's Guide Vol.2 (SC18725800)
    ==============================================================
    PREFACE.3 Terms Used in This Book
    The following term is add to the list of IMS versions:
    | IMS Version 9       refers to IMS Version 9 Release 1
    --------------------------------------------------------------
    2.0       DB Historical Data Analyzer
    2.1       Overview
    2.1.5     Restrictions
    Add the following consideration for HALDB OLR:
    | DB Historical Data Analyzer can process the HISTORY data set
    | even if some of the partitions are incomplete
    | for the Online Reorganization.
    | For the HALDB partition which is Online Reorganization
    | (OLR) capable, the ddnames in the reports show
    | the active DBDS at the time of HD Pointer Checker's run,
    | either (A-J&X) or (M-V&Y).
    2.2       Operating Instructions (MVS Batch Environment)
    2.2.3     Input
    2.2.3.2   HISTIN Data Set
    2.2.3.2.6 DATABASE Control Statement
    Add the following paragraph regarding HALDB OLR:
      DDname
        For HALDB, specify each ddname created by the concatenation
        of the partition name and the data set suffix character,
    |   A through J or X. .
    |   For the HALDB which is Online Reorganization (OLR) capable,
    |   you can specify the data set suffix character M through V or
    |   Y, as well as A through J or X.
    |   Even if which suffix is specified, DB Historical Data
    |   Analyzer processes the history records for both (A-J&X) and
    |   (M-V&Y) sets.
    --------------------------------------------------------------
    2.2.4     Output
    2.2.4.1   HISTPRT Data Set
    The following reports are changed to distinguish between
    (A-J&X) and (M-V&Y) data sets for HALDB partition:
        HISTORY DATA SET BY KEY DATE REPORT
        HISTORY DATA SET BY DB-DS REPORT
        HD POINTER CHECKER SUMMARY REPORT
        HD ANALYSIS REPORT
    --------------------------------------------------------------
    3.0       Space Monitor
    3.1       Overview
    3.1.5     Restrictions
    Add the following consideration for HALDB OLR:
    | For the HALDB partition which is Online Reorganization
    | (OLR) capable, the ddname shown in the reports presents
    | the active DBDS at the time of HD Pointer
    | Checker's run, either (A-J&X) or (M-V&Y).
    3.2       Operating Instructions
    3.2.3     Input
    3.2.3.1   Control Member Data Set (SPMNMBR)
    3.2.3.1.4 Format of the First Statement
    Add the paragraphs about HALDB OLR:
         10 - 17        Specify, left-justified, the ddname to be
                        processed. It is required only for
                        an IMS full-function database data set.
                        For HALDB, specify the ddname created
                        with the concatenation of the partition
                        name and the DSG suffix character,
    |                   A through J or X.
                        You cannot specify the ddname of
                        the Indirect List Data Set (ILDS).
    |                   For the HALDB which is Online Reorganization
    |                   (OLR) capable, you can specify the DSG
    |                   suffix character M through V or Y, as well
    |                   as A through J or X. Even if which side is
    |                   specified, Space Monitor processes the
    |                   history records for both (A-J&X) and (M-V&Y)
    |                   sets.
         19 - 62        Specify, left-justified, the data set name.
                        For an IMS full-function database data set,
                        this name must correspond to the ddname to
                        be processed.
    |                   For the HALDB which is Online Reorganization
    |                   (OLR) capable, if the specified database
    |                   data set does not exist, Space Monitor
    |                   searches for the other of database data set,
    |                   (A-J&X) or (M-V&Y) .
    --------------------------------------------------------------
    3.2.4     Output
    3.2.4.1   Space Monitor Graph Record Data Set (SPMNSPDT)
    3.2.4.1.1 Function
     This is an OS sequential data set that contains Space Monitor
     graph records. One record is created for each data set,
     and each record consists of a prefix, multiple entries of
     data (called buckets), and a suffix.
    | For HALDB partitions, the data for any (M-V&Y) data set is
    | merged into the record for the corresponding (A-J&X) data set.
    3.2.4.2   SPMNPRT Data Set
    The following reports are changed to distinguish between
    (A-J&X) and (M-V&Y) data sets for HALDB partitions:
        SPACE ANALYSIS BY DATA SET REPORT
        SUMMARY OF DATA SETS BY VOLUME REPORT
    3.2.4.3   SPMNPRTW Data Set
    The following report is changed to distinguish between
    (A-J&X) and (M-V&Y) data sets for HALDB partitions:
        SPACE MONITOR EXCEPTION REPORT
    --------------------------------------------------------------
    4.0       DB Segment Restructure
    4.1       Overview
    4.1.6     Restrictions
    Add the following two restrictions for HALDB OLR:
    |  11. While HALDB Online Reorganization (OLR) is not completed
    |  for the specified partition, DB Segment Restructure
    |  abnormally terminates due to the IMS batch region user abend
    |  3303.
    |  12. For the HALDB partition which is OLR capable, when
    |  FABRRELD runs as an initial load program (using the PSB
    |  which contains PROCOPT=L or PROCOPT=LS on the PCB statement),
    |  it always loads the (A-J&X) side.
    |  When FABRRELD runs as an update program (using the PSB
    |  which contains PROCOPT=A on the PCB statement), the update
    |  is on the active data sets, either (A-J&X) or (M-V&Y).
    

APAR Information

  • APAR number

    PQ80186

  • Reported component name

    IMS POINTER CHE

  • Reported component ID

    5655E0900

  • Reported release

    210

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2003-10-29

  • Closed date

    2003-12-25

  • Last modified date

    2004-01-02

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UQ83626

Modules/Macros

  •    FABGANAL FABGDELT FABGHIR  FABGLIST FABGRHT
    FABGSUMM FABKCOLL FABKGRAF FABKGRUP FABKLIST FABKRHT  FABKSPMD
    FABPACKE FABPACTL FABPADBS FABPALLC FABPANAL FABPARCK FABPARCN
    FABPBCTL FABPCV01 FABPDATE FABPDCT  FABPDUMP FABPECTL FABPGET1
    FABPHCTL FABPHDTS FABPHEVL FABPHEXT FABPHINI FABPHPSD FABPHPT
    FABPHPUT FABPHSDA FABPHSHI FABPHSIX FABPHTRM FABPHXR  FABPIBLK
    FABPLBLD FABPLBLX FABPLINK FABPMAIN FABPMSGS FABPOIB  FABPOPEX
    FABPPDT  FABPPILE FABPPMAP FABPPSDA FABPPSIX FABPPSL9 FABPPSM9
    FABPPTRT FABPPUT0 FABPRCHK FABPRORG FABPSDA0 FABPSHI0 FABPSIT
    FABPSIX0 FABPSNAP FABPSTE0 FABPSUMM FABPTRC  FABPUCB  FABPUDBR
    FABPUDCT FABPUDRT FABPUDSR FABPUHTC FABPULDB FABPUMAP FABPUPHR
    FABPURND FABPURTO FABPXCTL FABPXRCK FABRRELD FABRRLD9 FABRULD9
    FABRUNLD FABTDPOR FABTHCHG FABTHCRE FABTHOUT FABTROOT FABUARCN
    HPC2210J
    

Publications Referenced
SC18725700SC18725800   

Fix information

  • Fixed component name

    IMS POINTER CHE

  • Fixed component ID

    5655E0900

Applicable component levels

  • R210 PSY UQ83626

       UP03/12/27 P F312

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Line of Business":{"code":null,"label":null},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX89G","label":"IMS HP Pointer Checker"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"210"}]

Document Information

Modified date:
03 October 2020