IBM Support

PQ63285: IMS V8 RUNUNDER SUPPORT FOR IPR V2

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • IMS V8 rununder support for IPR V2.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IMS Parallel Reorganization for *
    *                 z/OS Version 2 Release 1 (FMID=H25N210).     *
    ****************************************************************
    * PROBLEM DESCRIPTION: By the maintenance provided by this     *
    *                      APAR, IMS Parallel Reorganization for   *
    *                      z/OS Version 2 Release 1 is enabled     *
    *                      to run on IMS Version 8 (Program Number *
    *                      5655-C56).                              *
    ****************************************************************
    * RECOMMENDATION: Apply the maintenance for this APAR.         *
    ****************************************************************
    IMS Parallel Reorganization for z/OS has been modified so that
    it can run on IMS Version 8 (including PQ59157).
    

Problem conclusion

Temporary fix

Comments

  • ========================
    = DOCUMENTATION CHANGE =
    ========================
    IMS Parallel Reorganization for z/OS Version 2 Release 1 User's
    Guide (Document Number: SC27-1180-00) should be changed as
    follows.
    
    ================================================================
    PREFACE About This Guide
     PREFACE.4 Abbreviations of Product Names
    
     In this book,the following abbreviations are used for product
     names:
     +----------------------+------------------------------------+
     |Short Name            | Product Name                       |
     +----------------------+------------------------------------+
     |                         :                                 |
     +----------------------+------------------------------------+
     | IMS                  | The generic name for the following |
     |                      | products:                          |
     |                      | - IMS/ESA Version 6 Release 1      |
     |                      |   Database Manager                 |
     |                      |   (Program number: 5655-158)       |
     |                      | - IMS Version 7 Release 1 Database |
     |                      |   Manager                          |
     |                      |   (Program number: 5655-B01)       |
    ||                      | - IMS Version 8 Release 1 Database |
    ||                      |   Manager                          |
    ||                      |   (Program number: 5655-C56)       |
     +----------------------+------------------------------------+
     |                         :                                 |
     +----------------------+------------------------------------+
    
     PREFACE.5 References to IMS Products and Releases
      To make the text in this book easier to read, the version and
      release level of IMS have been abbreviated. The following
      abbreviation are used:
    
        - IMS Version 6 refers to IMS/ESA Version 6 Release 1
        - IMS Version 7 refers to IMS Version 7 Release 1
    |   - IMS Version 8 refers to IMS Version 8 Release 1
                               :
    ================================================================
    Chapter 1. Introduction
     1.2 Processing Environments
      1.2.1 Software Requirements
    
     IPR V2 operates in either z/OS or OS/390.  Its operating system
     requirements are the same as those for IMS supported by IPR V2.
    
     IPR V2 requires one of the following products:
    
     - IMS/ESA Version 6 Release 1 Database Manager (5655-158)
     - IMS Version 7 Release 1 Database Manager (5655-B01)
    |- IMS Version 8 Release 1 Database Manager (5655-C56)
                              :
     IPR V2 requires the following products and maintenance:
     1. For basic functions of IPR Driver, IPR Unload, and IPR
        Reload, the following are required:
                              :
     6. If you are to reorganize HISAM or SHISAM by using IPR
        Driver, the following maintenance must be applied:
      - IMS High Performance Load for OS/390 Release 1
        - APAR PQ61448
    |7. If you are to reorganize DATABASE by using IPR Driver,
    |   IPR Unload, and IPR Reload under IMS Version 8, the
    |   following maintenance must be applied:
    | - IMS High Performance Unload for OS/390 Release 1 (5655-E06)
    |   - APAR PQ63286
    | - IMS High Performance Load for OS/390 Release 1 (5655-E07)
    |   - APAR PQ63287
    | - If INDEXBLD=YES is specified for IPR Driver, IMS Index
    |   Builder for OS/390 Version 2 Release 1 (5655-E24)
    |   - APAR PQ57541
    ================================================================
    Chapter 2. IMS Parallel Reorganization Driver
     2.1 Overview
      2.1.2 Reorganization Manager
      Reorganization Manager provides IPR Driver with full DBRC
    | support. If you are using IMS Version 8, see "Restrictions" in
    | topic 2.5.
    
    
     2.5 Restrictions
     IPR Driver has the following restrictions:
                              :
    |The following restrictions,in addition to those previously
    |mentioned, apply if you are using IMS Version 8.
    | - The IMSPLEX= parameter that you can specify for the EXEC
    |   statements for IPR Unload, IPR Reload, and IPR DB Scan
    |   utilities cannot be specified for IPR Driver.
    |   If you want to specify the sysplex name, use the DBRC SCI
    |   Registration exit.
    |   If you are using RECON data set with IMSplex name
    |   registered, you need to specify the IMSplex name by using
    |   the DBRC SCI Registration exit.
    | - In the IMS Version 8 R/U environment,if a user is defined in
    |   the DBRC Command Authorization as without the authority
    |   for the following DBRC Command issues reorganization by
    |   using IPR V2, the process might abort.
    |+-------------------------------------------------------------+
    ||DBRC Command|Process of IPR |Status of the  |User's Response |
    ||            |Driver When the|Database after |                |
    ||            |User Has No    |Error          |                |
    ||            |Authority      |               |                |
    |+------------+---------------+---------------+----------------+
    ||LIST.RECON  |HPSG0333E and  |The status of  |Change the      |
    ||            |HPSG0011E (*1) |the database is|authority so    |
    ||            |are issued, and|the same as    |that the user   |
    ||            |the process    |before running |can issue the   |
    ||            |ends.          |IPR Driver Step|LIST.RECON      |
    ||            |For details,   | (not changed).|command.        |
    ||            |check the      |               |Or, issue the   |
    ||            |report (*3).   |               |LIST.RECON      |
    ||            |               |               |command by a    |
    ||            |               |               |user that has   |
    ||            |               |               |the authority.  |
    |+------------+---------------+---------------+----------------+
    ||LIST.DB     |HPSG0333E and  |The status of  |Change the      |
    ||            |HPSG0011E (*1) |the database is|authority so    |
    ||            |are issued, and|the same as    |that the user   |
    ||            |the process    |before running |can issue the   |
    ||            |ends.          |IPR Driver Step|LIST.DB command.|
    ||            |For details,   | (not changed).|Or, issue the   |
    ||            |check the      |               |LIST.DB command |
    ||            |report (*3).   |               |by a user that  |
    ||            |               |               |has the         |
    ||            |               |               |authority.      |
    ||            |               |               |                |
    |+------------+---------------+---------------+----------------+
    ||NOTIFY.REORG|HPSG0314E and  |Name swapping  |Issue the       |
    ||(If NAMESWAP|HPSG0011E (*2) |is completed,  |NOTIFY.REORG,   |
    || =YES)      |are issued, and|but DBRC       |NOTIFY.UIC, and |
    ||            |the process    |notification   |CHANGE.DB       |
    ||            |ends.          |process is not |command         |
    ||            |For details,   |completed.     |according to the|
    ||            |check the      |               |status of the   |
    ||            |report (*4).   |               |database. (*5)  |
    |+------------+---------------+---------------+----------------+
    ||NOTIFY.UIC  |HPSG0315E and  |Name swapping  |Issue the       |
    ||(If NAMESWAP|HPSG0011E (*2) |is completed,  |NOTIFY.UIC and  |
    || =YES)      |are issued, and|but DBRC       |CHANGE.DB       |
    ||            |the process    |notification   |command         |
    ||            |ends.          |process is not |according to the|
    ||            |For details,   |completed.     |status of the   |
    ||            |check the      |               |database. (*5)  |
    ||            |report (*4).   |               |                |
    |+------------+---------------+---------------+----------------+
    ||CHANGE.DB   |HPSG0316E and  |Name swapping  |Issue the       |
    ||(If NAMESWAP|HPSG0011E (*2) |is completed,  |CHANGE.DB       |
    || =YES)      |are issued, and|but DBRC       |command         |
    ||            |the process    |notification   |according to the|
    ||            |ends.          |process is not |status of the   |
    ||            |For details,   |completed.     |database. (*5)  |
    ||            |check the      |               |                |
    ||            |report (*4).   |               |                |
    |+-------------------------------------------------------------+
    |*1 HPSG0011E  REORGANIZATION ABORTED FOR DATABASE dbdname
    |              (RC=08, RSN=40010001)
    |*2 HPSG0011E  REORGANIZATION ABORTED FOR DATABASE dbdname
    |              (RC=08, RSN=40100004)
    |*3 For details, check the "DATA BASE RECOVERY CONTROL" report
    |   in HPSOUT2.
    |*4 For details, check the "DBRC NOTIFICATION PROCESSING" report
    |   in HPSOUT2.
    |*5 See "Automated DBRC Notification Processing" in topic
    |   2.1.2.5. and "Manual DBRC Notification Processing" in topic
    |   2.9.3.
    
     2.6 JCL Requirements
      2.6.1 EXEC Statement
                        :
    | Note: The IMSPLEX= parameter that you can specify for the EXEC
    |       statements for IPR Unload, IPR Reload, and IPR DB Scan
    |       utilities under IMS Version 8, cannot be specified for
    |       IPR Driver.
    |       If you want to specify the sysplex name, use the DBRC
    |       SCI Registration exit.
    
     2.9 Post-Reorganization Processing
      2.9.3 Manual DBRC Notification Processing
      The DBRC notification processing must be done after the data
      set name swapping.
    | If you are using IMS Version 8, see "Restrictions" in topic
    | 2.5.
                          :
    ================================================================
    3.0 Chapter 3. IPR Unload Utility
     3.7 JCL Requirements
      3.7.1 EXEC Statement
      The EXEC statement for the IPR Unload utility must be in the
      following format:
              //name  EXEC  PGM=HPSCMAIN,
              //            PARM='FUNC=UL,DBD=dbdname'
    
      Specify HPSCMAIN as the program name. The PARM= parameter
      keywords include the following:
      FUNC=UL
          Invokes the IPR Unload function to unload the database.
          This parameter is required.
      DBD=dbdname
          Specifies the name of the DBD that includes the database
          to be unloaded. This parameter is required.
    
      Optionally, you can use the DBRC=, SWAP=, IRLM=, IRLMNM=,
    | GSGNAME=, and IMSPLEX= parameters to specify the job step
      environment:
                          :
      GSGNAME=name
           Specifies the name of the global service group (GSG).
    
    | IMSPLEX=sysplex
    |      Specify the IMSplex name to be used for a RECON.
    |      This parameter is 1 to 5 characters.
    ================================================================
     4.0 Chapter 4. IPR Reload Utility
      4.1 Program Functions
       4.1.5 Supporting Partitioned Databases
    
       The IPR Reload utility supports reloading of PHDAM or PHIDAM
       databases introduced by High Availability Large Database
    |  (HALDB) of IMS Version 7 or later.
       You can either reload an entire database or reload only a
       single partition of a HALDB.
    
      4.6 JCL Requirements
                           :
       EXEC
           Must be in this form:
                  //name  EXEC  PGM=HPSCMAIN,
                  //            PARM='FUNC=RL,DBD=dbdname'
           Specify HPSCMAIN as the program name.
           The PARM= parameter keywords include the following:
    
           FUNC=RL
             Invokes the IPR Reload function to reload the database.
             This parameter is required.
           DBD=dbdname
             dbdname is the name of the DBD that includes the
             database to be reloaded. This parameter is required.
    
             Optionally, you can use the DBRC=, SWAP=, IRLM=,
    |        IRLMNM=, GSGNAME=, and IMSPLEX= parameters to specify
             the job step environment:
                            :
           GSGNAME=gsgname
             Specifies the name of the global service group (GSG).
             This parameter is optional.
    
    |      IMSPLEX=sysplex
    |        Specify the IMSplex name to be used for a RECON.
    |        This parameter is 1 to 5 characters.
                          :
    ================================================================
     5.0 Chapter 5. IPR DB Scan Utility
      5.5 JCL Requirements
       5.5.1 EXEC Statement
    
       The EXEC statement for the IPR DB Scan must be in the
       following format:
    
         //stepname EXEC PGM=HPSCMAIN,PARM='FUNC=SN'
    
       Specify HPSCMAIN as the program name.
       The PARM= parameter must include the following:
    
       FUNC=SN
         Invokes the IPR DB Scan utility to scan the database.
         This parameter is required.
    
       Optionally, you can use the DBRC=, SWAP=, IRLM=, IRLMNM=,
    |  GSGNAME=, and IMSPLEX= parameters to specify the job step
       environment:
                          :
       GSGNAME=name
         Specifies the name of the global service group (GSG).
    
    |  IMSPLEX=sysplex
    |    Specify the IMSplex name to be used for a RECON.
    |    This parameter is 1 to 5 characters.
    

APAR Information

  • APAR number

    PQ63285

  • Reported component name

    IMS PARALLEL RE

  • Reported component ID

    5655F7400

  • Reported release

    210

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2002-07-17

  • Closed date

    2002-08-07

  • Last modified date

    2002-09-04

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

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

    UQ68770

Modules/Macros

  • HPSGBBL0 HPSGBBL8 HPSGCM10 HPSGGIOB HPSGGIO0
    HPSGGRGB HPSGGRG0 HPSGLINK HPSGMPA0 HPSGRM10 HPSGRS00 HPSGTM00
    HPSGUBBL H25N210J
    

Publications Referenced
SC27118000    

Fix information

  • Fixed component name

    IMS PARALLEL RE

  • Fixed component ID

    5655F7400

Applicable component levels

  • R210 PSY UQ68770

       UP02/08/09 P F208

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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSVL5Q","label":"IMS Database Reorganization Expert for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"210","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
06 January 2023