IBM Support

PI89490: SPMN DISPLAYS THE WRONG NUMBER OF AVAILABLE EXTENTS OF OSAM DATA SETS IN IMS V14 OR LATER.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The maximum number of extents per OSAM data set has increased to
    120 in IMS V14 or later.
    Space Monitor (SPMN) displays the wrong number of available
    extents of OSAM data sets in SPMN reports.
    

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 Space Monitor (SPMN).          *
    ****************************************************************
    * PROBLEM DESCRIPTION: SPMN displays the wrong number of       *
    *                      available extents of OSAM data sets     *
    *                      in IMS V14 or later.                    *
    ****************************************************************
    * RECOMMENDATION: Apply the maintenance for this APAR.         *
    ****************************************************************
    In IMS V14 or later, the maximum number of extents per OSAM data
    set has increased to 120. But, Space Monitor incorrectly treats
    it same as the maximum number of extents of IMS V13.
    As the result, the wrong number of available extents of OSAM
    data sets is shown in Space Monitor reports.
    

Problem conclusion

  • HPPC has been modifiled to fix the error.
    
    Documentation Changes:
    Note: The Part, Chapter, and Table 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 (SC19240103)
    ================================================================
    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Part 5. Space Monitor utility
    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    ----------------------------------------------------------------
    Chapter 27. Available data set extents and last space
    - Available data set extents
    ----------------------------------------------------------------
    
    << The row for Data set Type OSAM in Table 74 has been changed
       as follows: >>
    
    Table 74. Maximum number of extents that Space Monitor utility
    uses to calculate the number of available extents
      +----------+-----------------------+-----------------------+
      | Data set | Max number of extents | Max number of extents |
      |  type    |  per volume           |  per data set         |
      +----------+-----------------------+-----------------------+
      | OSAM     | 16
    | |          |                       |  for IMS V13          |
      |          |                       +-----------------------+
    | |          |                       | 120                   |
    | |          |                       |  for IMS V14 or later |
      +----------+-----------------------+-----------------------+
    | |Note: For IMS V13, the maximum number of extents per OSAM |
      |      data set is determined as follows:                  |
      |      1. ...                                              |
      |      2. ....                                             |
      |                                                          |
      +----------+-----------------------+-----------------------+
    
      :
    
     Examples
    
      The following examples show how to calculate the number of
      allocatable extents from the number of extents currently
      allocated. Allocatable extents means the space that can be
      allocated under the current status of allocation. In these
    | examples, IMS V14 and no rotational position sensing (RPS)
      device is assumed.
    
      :
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI89490

  • Reported component name

    IMS POINTER CHE

  • Reported component ID

    5655E0900

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-10-30

  • Closed date

    2017-11-09

  • Last modified date

    2017-12-02

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

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

    UI51800

Modules/Macros

  •    FABKCOLL
    

Publications Referenced
SC19240103    

Fix information

  • Fixed component name

    IMS POINTER CHE

  • Fixed component ID

    5655E0900

Applicable component levels

  • R310 PSY UI51800

       UP17/11/11 P F711

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 December 2017