IBM Support

PI46110: NEED NOT SPECIFY OVERFLOW= AND PRIMEDB= KEYWORDS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • The OVERFLOW= and PRIMEDB= keywords on DATABASE statements in
    HDPC stand-alone jobs are changed from required to optional.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: IBM IMS High Performance Pointer Checker for *
    *                 z/OS Version 3 Release 1 (FMID=HPC2310)      *
    *                 users who run HD Pointer Checker stand-alone *
    *                 jobs for HISAM databases with overflow data  *
    *                 sets or index databases.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: The OVERFLOW= and PRIMEDB= keywords on  *
    *                      DATABASE statements are changed from    *
    *                      required to optional.                   *
    ****************************************************************
    * RECOMMENDATION: Apply the maintenance for this APAR.         *
    ****************************************************************
    The OVERFLOW= and PRIMEDB= keywords on DATABASE statements
    are changed from required to optional.
    

Problem conclusion

Temporary fix

Comments

  • By this APAR, the OVERFLOW= and PRIMEDB= keywords on DATABASE
    statements in the PROCCTL data set are changed from required to
    optional. You can omit these keywords when you run HD Pointer
    Checker stand-alone jobs for HISAM databases with overflow data
    sets or index databases.
    If you omit these keywords, HD Pointer Checker sets the overflow
    ddnames of the HISAM and index databases, and the dbdnames of
    the primary databases that are indexed by the index databases.
    
    This enhancement is being implemented as a result of RFE ID
    44390.
    
    << Documentation Changes >>
    Note: The Part and Chapter numbers are those of the PDF file.
    The documentation is modified as follows:
    ==============================================================
    IMS High Performance Pointer Checker for z/OS, V3R1,
    User's Guide (SC19-2401-03)
    ==============================================================
    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
     Part 2. HD Pointer Checker utility
    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    --------------------------------------------------------------
    Chapter 4. Using the HD Pointer Checker processor
    --------------------------------------------------------------
    - Input
      - FABPMAIN PROCCTL data set
        - DATABASE statement
    --------------------------------------------------------------
    <The descriptions of the following keywords are changed: >
    :
    Keywords
    The following keywords can be specified on the DATABASE
    statement:
    DB=dbdname
      Specifies the dbdname (as coded in your DBD) of the HISAM,
      HIDAM index or the secondary index databases, the HDAM, the
      HIDAM, the PHDAM, PHIDAM, or the PSINDEX to be processed.
      This keyword is a required keyword.
    :
    OVERFLOW=ddname
      Specifies the ddname (as coded in your DBD) of the ESDS of
      the HISAM data set group, or the index database.
      You can omit this keyword when HD Pointer Checker is runs as
      a stand-alone job. In this case, HD Pointer Checker sets the
      ddname of the ESDS of the HISAM database or the index
      database.
      Abbreviations OFLOW and OVFLW can be used for OVERFLOW.
    PRIMEDB=dbdname
      Specifies the dbdname of the primary database indexed by the
      HIDAM index or the secondary index database to be processed.
      You can omit this keyword when HD Pointer Checker is runs as
      a stand-alone job. In this case, HD Pointer Checker sets the
      dbdname of the primary database indexed by the HIDAM index or
      the secondary index database.
    

APAR Information

  • APAR number

    PI46110

  • Reported component name

    IMS POINTER CHE

  • Reported component ID

    5655E0900

  • Reported release

    310

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Xsystem

  • Submitted date

    2015-08-02

  • Closed date

    2015-08-26

  • Last modified date

    2015-09-02

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

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

    UI30555

Modules/Macros

  • FABPADBS
    

Publications Referenced
SC19240103    

Fix information

  • Fixed component name

    IMS POINTER CHE

  • Fixed component ID

    5655E0900

Applicable component levels

  • R310 PSY UI30555

       UP15/08/28 P F508

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.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX89G","label":"IMS HP Pointer Checker"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 September 2015