IBM Support

PI27563: SUPPORT FOR IMS V14

A fix is available

Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as new function.

Error description

  • Support for IMS V14
KEYWORDS: IMSV14TGT/K IMSV13TGT/K

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 use IMS Version 14.                *
****************************************************************
* PROBLEM DESCRIPTION: This APAR enables IMS High Performance  *
*                      Pointer Checker (HPPC) to run under IMS *
*                      V14 and support IMS V14 and V13 HALDB   *
*                      OSAM 8GB data sets.                     *
****************************************************************
* RECOMMENDATION: Apply the maintenance for this APAR.         *
****************************************************************
IMS High Performance Pointer Checker for z/OS V3R1 has been
modified to run under IMS Version 14 and support HALDB OSAM 8GB
data sets.

*** Notes ***
- When you use the Integrated DB Sensor function in HD Pointer
  Checker on IMS Version 14 environment, you need to apply APAR
  PI27634 to IMS Database Reorganization Expert V4.1.
- When you use IMS Library Integrity Utilities' DBD map function
  or DBD reversal function in HD Pointer Checker on IMS Version
  14 environment, you need to apply APAR PI27566 to IMS Library
  Integrity Utilities V2.2.
- When you monitor IMS full-function database VSAM data sets by
  Space Monitor or the Integrated DB Sensor function on IMS
  Version 14 environment, you need to apply APAR PI26352 to
  Tools Base V1.5.


Additionally, this APAR fixes the problem that when HDPC is run
with HASH=YES and correctly detects more than 100 pointer errors
that indicate MSGFABP1082E or MSGFABP1084E, the number of the
error messages MSGFABP1082E or MSGFABP1084E is not limited even
when OPTION ERRLIMIT=YES is specified.

Problem conclusion

  •

Temporary fix

  •

Comments

  • 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 (SC19240102)
==============================================================
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Part1. Introduction and product setup
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
--------------------------------------------------------------
Chapter 1. Overview of IMS HP Pointer Checker
--------------------------------------------------------------
- IMS HP Pointer Checker terminology
--------------------------------------------------------------
<<The following description is added:>>
 To make this information easier to read, the version and
 release levels of IMS are abbreviated, as follows:
 - IMS Version 11 refers to IMS Version 11 Release 1.
 - IMS Version 12 refers to IMS Version 12 Release 1.
 - IMS Version 13 refers to IMS Version 13 Release 1.
|- IMS Version 14 refers to IMS Version 14 Release 1.

--------------------------------------------------------------
- IMS HP Pointer Checker documentation and updates
  - Related publications
--------------------------------------------------------------
<<The following IMS publications have been added to the table:>>
 Short title                    Title
 -----------------------------  ---------------------------
 IMS Database Administration
|                               IBM IMS Version 14 Database
|                               Administration
 -----------------------------  ---------------------------
 IMS Operations and Automation
|                               IBM IMS Version 14 Operations
|                               and Automation
 -----------------------------  ---------------------------
 IMS System Definition
|                               IBM IMS Version 14 System
|                               Definition
 -----------------------------  ---------------------------

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Part 2. HD Pointer Checker utility
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
--------------------------------------------------------------
Chapter 4. Using the HD Pointer Checker processor
--------------------------------------------------------------
- Restrictions and considerations
  - Restrictions and considerations by database organization
    types
--------------------------------------------------------------
<<The following description is changed:>>
|HDAM, HIDAM, PHDAM, and PHIDAM databases whose size is greater
 than 4 GB

 For an HDAM or an HIDAM database that uses OSAM access method,
 a database data set with an even-numbered block size might
|exceed 4 GB. For a PHDAM or a PHIDAM database that uses OSAM
|access method, a data set size of the database that is
|registered as DSORG=OSAM8G in RECON data sets might also exceed
|4 GB.
 :

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Part 5. Space Monitor utility
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
--------------------------------------------------------------
Chapter 25. Using Space Monitor
- Input
  - Control member data set (SPMNMBR)
    - Data set control statement
--------------------------------------------------------------
Second statement
<<The following description is changed:>>
 Position Description
 33-35    Specify the warning threshold value for the percentage
          of the data set used space within the maximum size.
          :
          The maximum size is as follows:
|         - For OSAM data set of non-HALDB HD database of which
|           block size is an even number, or for OSAM data sets
|           of HALDB that is registered as DSORG=OSAM8G in RECON
|           data sets, the maximum size is 8 GB.
          - For other database data set than above, the maximum
            size is 4 GB. (1 GB is 1,024 MB)

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Part 8. Troubleshooting
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
--------------------------------------------------------------
Chapter 36. Messages and codes
- HD Pointer Checker messages and codes
  - HD Pointer Checker messages
--------------------------------------------------------------
<<The following messages are changed:>>
FABP0412E SEGMENT BEYOND THE SIZE LIMIT
Explanation: The database is probably damaged. A segment data is
located in the block or CI that exceeds the data set size limit.
The maximum size of a database data set is:
 - 8 GB when it is an OSAM data set of non-HALDB with an even
|  number of block size, or when it is an OSAM data set of a
|  HALDB that is registered as DSORG=OSAM8G in RECON data sets
|- 4 GB for a VSAM data set, an OSAM data set of non-HALDB with
|  an odd number of block size, or an OSAM data set of a HALDB
|  that is registered as DSORG=OSAM in RECON data sets
System action: Processing continues.
User response: The pointers pointing to those segments are
incorrect. Repair the database and rerun the HD Pointer Checker
job.
Problem determination: See Chapter 11, "Database repair
guidelines," on page 363.

 FABP0413W BYPASS SPACE BEYOND THE nGB SIZE LIMIT
 Explanation: The database data set is allocated beyond the n GB
|size limit. For an OSAM data set of non-HALDB with an even-
|numbered block size or an OSAM data set of a HALDB that is
|registered as DSORG=OSAM8G in RECON data sets, n is 8; othwise
 n is 4. The HD Pointer Checker bypasses checking of the blocks
 that exist over n GB. If other messages appear with FABP0413W,
 check the description of the messages. If no message other than
 FABP0413W appears, the database is not damaged. Then, this
 message means that the number of blocks allocated to this
 database exceeds the limit, and no valid segment data exists
 beyond that limit. This status occurs when some segments were
 attempted to be inserted beyond the limit.
 System action: Processing continues.
 User response: None.

<<The following messages are added:>>
|FABP0414E THE HALDB IS REGISTERED AS DSORG=OSAM IN RECON BUT
|SEGMENTS RESIDE BEYOND THE 4 GB BOUNDARY
|Explanation: This HALDB supports up to 4 gigabytes of data
|because the HALDB is registered as DSORG=OSAM in RECON data
|sets. However, segment occurrences are located in the block
|that exceeds 4 GB boundary.
|System Action: Processing continues.
|User Response: Check if the correct RECON data sets were used,
|and if not, correct the error and rerun the HD Pointer Checker
|job. Otherwise, the database is damaged. Repair the database
|and rerun the HD Pointer Checker job.

|FABP0416E THE HALDB IS REGISTERED AS DSORG=OSAM8G IN RECON BUT
|THE INPUT ICDS IS AN M-SIDE DATA SET
|Explanation: This HALDB supports up to 8 gigabytes of data
|because the HALDB is registered as DSORG=OSAM8G in RECON data
|sets. However, the input image copy data sets of the HALDB are
|M-side data sets. A-side data sets are valid data sets if
|HALDBs support up to 8 gigabytes of data.
|System Action: HD Pointer Checker treats the HALDB as the
|database that supports up to 4 gigabytes of data, and input
|data sets are treated as M-side data sets. Then processing
|continues.
|User Response: If error messages other than this message
|appear, the database is damaged. Repair the database,
|and rerun the HD Pointer Checker job.
|If no message other than this message appears, the database is
|not damaged but the incorrect RECON data sets were used. If you
|are trying to recover the HALDB by using the image copy data
|sets, recover the RECON data sets to the time when the image
|copy were taken and recover the HALDB.

|FABP0417E THE HALDB IS DEFINED AS VSAM IN THE DBD BUT IS
|REGISTERED AS DSORG=OSAM8G IN RECON
|Explanation: This HALDB is registered in the RECON data sets as
|a database that uses OSAM access method. However, in the DBD,
|the database is defined as VSAM access method. There is an
|inconsistency between the RECON data sets and the DBD.
|System Action: HD Pointer Checker treats the database data sets
|as VSAM data sets and processing continues.
|User Response: Specify the correct RECON data sets and the
|correct DBD library, and rerun the HD Pointer Checker job.

|FABP1087E HALDB dbdname IS REGISTERED AS DSORG=OSAM8G IN RECON
|BUT THE INPUT DBDS IS AN M-SIDE DATA SET
|Explanation: This HALDB supports up to 8 gigabytes of data
|because the HALDB is registered as DSORG=OSAM8G in RECON data
|sets. However, the input database data sets of the HALDB are
|M-side data sets. A-side data sets are valid database data sets
|if HALDBs support up to 8 gigabytes of data.
|System Action: Processing stops.
|User Response: Specify the correct RECON data sets and database
|data sets and rerun the HD Pointer Checker job.
×**** PE16/03/22 FIX IN ERROR. SEE APAR PI58614  FOR DESCRIPTION

APAR Information

  • APAR number

    PI27563

  • 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

    2014-10-14

  • Closed date

    2014-12-18

  • Last modified date

    2016-03-31

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

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

    UI24016

Modules/Macros

  •    FABGHIR  FABKCOLL FABPADBS FABPALLC FABPDATE
FABPDBS0 FABPDILK FABPE35G FABPGET1 FABPGVT0 FABPHDTS FABPHEXS
FABPHINI FABPHPSD FABPIBLK FABPLBLX FABPLINK FABPMSGS FABPMSGT
FABPPILE FABPPSDA FABPPSIX FABPPSLE FABPPSME FABPPUT0 FABPSENR
FABPSTAP FABPSTE0 FABPUCB0 FABPUDSR FABPUPHR FABRIMSV FABRRLDE
FABRULDE FABTHCHG FABTHCRE FABTHOUT FABTROOT HPC2310J

Publications Referenced
SC19240102

Fix information

  • Fixed component name

    IMS POINTER CHE

  • Fixed component ID

    5655E0900

Applicable component levels

  • R310 PSY UI24016

       UP14/12/20 P F412

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":"3.1.0"}]

Document Information

Modified date:
03 April 2021

Page Feedback