PH42347: INCORRECT NUMBERS OF EXTENTS IN DBHDA REPORTS AND AVAILABLE EXTENTS IN SPMN REPORTS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The number of extents in DBHDA reports and the number of
  available extents in SPMN reports are incorrect when the actual
  number of extents exceeds 255.
  

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 VSAM database data sets    *
  *                 with Extent Constraint Removal specified and *
  *                 run DB Historical Data Analyzer (DBHDA) as a *
  *                 batch job, Export Utility of DBHDA, or Space *
  *                 Monitor (SPMN).                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: When VSAM Extent Constraint Removal is  *
  *                      specified for an IMS database data set, *
  *                      the following problems might occur:     *
  *                      - The incorrect number of extents is    *
  *                        shown in the DBHDA report             *
  *                      - Export Utility writes an incorrect    *
  *                        number of extents to the flat records *
  *                      - The incorrect number of available     *
  *                        extents is shown in SPMN reports      *
  ****************************************************************
  * RECOMMENDATION: Apply the maintenance for this APAR.         *
  ****************************************************************
  In DB Historical Data Analyzer (DBHDA) utilities, the following
  problems might occur when VSAM Extent Constraint Removal is
  specified and the number of the IMS database data set extents
  exceeds 255:
  - The incorrect number of extents is shown in the HD Analysis
    report
  - Export Utility of DBHDA writes an incorrect number of extents
    to the NO_OF_EXTENT or NO_OF_OVEXTNT field of the flat records
    in the FABGEXPF data set
  
  In Space Monitor (SPMN), the following problem might occur when
  VSAM Extent Constraint Removal is specified:
  - The incorrect number of available extents is shown in the
    Space Analysis by Data Set report and the Space Monitor
    Exception report
  

Problem conclusion

• HPPC has been modified to fix the errors.
  
  *************************
  * Documentation Changes *
  *************************
  IMS High Performance Pointer Checker for z/OS 3.1 User's Guide
  (SC19240106) is modified as follows:
  ===================================================
  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
  Part 4. DB Historical Data Analyzer utility
  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
  ----------------------------------------------------------------
  Chapter 21. Using the Export Utility
  - Input
   - FABGRECI data set
    - FIELD definition statement
  ----------------------------------------------------------------
  <The maximum length and the description for NO_OF_EXTENT in
   Table 59 are modified as follows>
  Maximum length (in bytes):
  - Hexadecimal 2
  Description:
  - The number of data set extents
    Note: If VSAM extent constraint removal is specified, the
    number of extents can exceed 255. If the length of this field
    is 1 byte, it could cause overflow and data might be
    truncated. Consider specifying 2-byte length for this field.
  
  <The maximum length and the description for NO_OF_OVEXTNT in
   Table 61 are modified as follows>
  Maximum length (in bytes):
  - Hexadecimal 2
  Description:
  - The number of overflow data set extents
    Note: If VSAM extent constraint removal is specified, the
    number of extents can exceed 255. If the length of this field
    is 1 byte, it could cause overflow and data might be
    truncated. Consider specifying 2-byte length for this field.
  
  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
  Part 5. Space Monitor utility
  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
  ----------------------------------------------------------------
  Chapter 25. Using Space Monitor
  ----------------------------------------------------------------
  - Restrictions and considerations
   - Restrictions
  ----------------------------------------------------------------
  <The following restriction is added>
  If VSAM extent constraint removal is specified, Space Monitor
  calculates the number of available extents as follows:
  - If the number of extents is equal to or less than 255, Space
    Monitor calculates the number of available extents without
    considering VSAM extent constraint removal.  Therefore, the
    calculated value might be smaller than the actual number of
    available extents.
  - If the number of extents is equal to or more than 256, Space
    Monitor calculates the number of available extents considering
    VSAM extent constraint removal.
  
  ----------------------------------------------------------------
  - Output
   - SPMNPRT data set
    - Space Analysis by Data Set report
  ----------------------------------------------------------------
  <The following report filed description is modified as follows>
  EXT
   Total number of extents on the data set (S)
   If 999* is shown, it indicates that the number of VSAM data
   set extents exceeded the maximum value (999) that can be
   printed.
  
  ----------------------------------------------------------------
  Chapter 27. Available data set extents and last space
  ----------------------------------------------------------------
  - Available data set extents
  ----------------------------------------------------------------
  <The row for VSAM in Table 74 is modified as follows>
  +----+--------------+------------------------------------------+
  |Data|Maximum number|Maximum number of extents per data set    |
  |set |of extents per|                                          |
  |type|volume        |                                          |
  +----+--------------+------------------------------------------+
  |VSAM|123           |-251                                      |
  |    |              |-7257 when extent constraint removal is   |
  |    |              | specified. For restriction about VSAM    |
  |    |              | data set that has extent constraint      |
  |    |              | removal specified, see Restrictions.     |
  +----+--------------+------------------------------------------+
  
  <Add the condition "extent constraint removal is not specified"
    to the Example 1 and 2>
  Example 1
   Assume that the data set type is VSAM, extent constraint
   removal is not specified, and the number of usable volumes is
   2.
   ...
  Example 2
   Assume that the data set type is VSAM, extent constraint
   removal is not specified, and the number of usable volumes is
   3.
   ...
  

Temporary fix

Comments

APAR Information

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

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

  UI78485

Modules/Macros

• FABGANAL FABGXCB0 FABGXFLD FABGXXPE FABKCOLL FABKLIST FABKRHT
  FABPUPHR
  

Fix information

• Fixed component name

  IMS POINTER CHE

• Fixed component ID

  5655E0900

Applicable component levels

• R310 PSY UI78485

     UP21/12/14 P F112

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.