IBM Support

PK48420: ENHANCEMENT OF PARTINIT FUNCTION.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • A new option is provided for the PARTINIT control statement.
    This option enables initializing empty HALDB partitions which
    were unloaded regardless of the PINIT flag in the RECON.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IBM IMS High Performance Load   *
    *                 for z/OS Version 2 Release 1 (FMID=H1IM210)  *
    ****************************************************************
    * PROBLEM DESCRIPTION: This APAR provides a new function to    *
    *                      initialize HALDB partitions after       *
    *                      reload.                                 *
    ****************************************************************
    * RECOMMENDATION: Apply the maintenance for this APAR.         *
    ****************************************************************
    This APAR provides a new function to initialize a HALDB
    partition which remains empty after the reload and the partition
    information is included in the unloaded data set.
    The initialization is to be performed regardless of the
    PARTITION INIT NEEDED flag in the DBRC RECON record.
    To use this function, the unloaded data set have to be created
    by High Performance Unload with APAR PK48499 and with
    CHECKREC=YES option. And specify PARTINIT=YES,UNLOAD in the
    FRRIN.
    

Problem conclusion

Temporary fix

Comments

  • ========================
    = Documentation Change =
    ========================
    IMS High Performance Load for z/OS Version 2 Release 1 User's
    Guide SC18-9222-02 ( SC18922202 ) should be changed as follows:
    
    2.0      High Performance Load
    2.2      Operating instructions
    2.2.3    Control statements
    2.2.3.2  Overview of High Performance Load control statements
    
       :
    Table 5. High Performance Load control statements for a HALDB
    Reload
    
      +-----------+---------------+-------+-----------------------+
      | KEYWORD   |ACCEPTED VALUES|DEFAULT| DESCRIPTION           |
      +-----------+---------------+-------+-----------------------+
      |PARTINFO=  | YES OR NO     | YES   |  SPECIFIES            |
      |           |               |       |  WHETHER TO           |
      |           |               |       |  BUILD ILDS AND       |
      |           |               |       |  HOW TO BUILD IT      |
      |           |               |       |  DURING               |
      |           |               |       |  REORGANIZATION       |
      +-----------+---------------+-------+-----------------------+
      |PARTINIT=  ||NO            | NO    |  INITIALIZES          |
      |           ||YES           |       |  PARTITIONS NOT       |
      |           ||YES,PINITON   |       |  POPULATED BY         |
      |           ||YES,UNLOAD    |       |  ANY SEGMENT          |
      |           |               |       |  DURING RELOAD        |
      +-----------+---------------+-------+-----------------------+
         :
    
    2.2.3.16      PARTINIT control statement
    
    | Specifies whether to initialize HALDB partitions after reload.
    | High Performance Load initializes a HALDB partition when a
    | HALDB partition does not contain any segment during reload.
         :
    
       _________________________________________________________
      |                                                         |
    | |                     _NO_______________                  |
    | |                    |      _,PINITON_  |                 |
    | | >>____PARTINIT=____|_YES_|__________|_|______________>< |
    | |                          |_,UNLOAD__|                   |
      |                                                         |
      |_________________________________________________________|
    
    NO
      Specifies that any initialization of a HALDB partition is not
      to be performed after reload.
    
    YES
      Specifies that initialization of a HALDB partition is to be
      performed for partitions not populated by any segment during
    | reload.
    |
    |    PINITON
    |       Specifies that initialization of a HALDB partition is to
    |       be done when the flag in the DBRC RECON record for the
    |       partition shows that the partition needs to be
    |       initialized (PINIT). If you only specify PARTINIT=YES,
    |       PARTINIT=YES,PINITON is assumed.
    |
    |    UNLOAD
    |       Specifies that initialization of a HALDB partition is to
    |       be done when the partition information is included in
    |       the input unloaded data set.  To use this option, the
    |       following conditions must be satisfied:
    |
    |         - The input unloaded data set has been created by HP
    |           Unload with APAR PK48499 and with the CHECKREC=YES
    |           option.
    |
    |         - The input unloaded data sets are not concatenated.
    
    APPENDIX1       Appendixes
    APPENDIX1.3     Appendix C.  Messages and codes
    APPENDIX1.3.3   Messages
    APPENDIX1.3.3.1 High Performance Load messages
    
    | HPSR0121W PARTINIT=YES,UNLOAD IS IGNORED (reason)
    |
    | Explanation: PARTINIT=YES,UNLOAD was ignored because HP Load
    | could not determine which partition should be initialized.
    | reason gives description why the process was ignored. The
    | reason is one of the following:
    |
    |   CONCATENATED UNLOAD D/S
    |    - The input unloaded data sets are concatenated.
    |
    |   LOW LEVEL UNLOAD D/S
    |   - The input unloaded data set was not created by HP Unload
    |     with the CHECKREC=YES
    |     option, or the release level or the maintenance level of
    |     HP Unload is lower than the level that is required for HP
    |     Load to work correctly.
    |
    | System Action: Processing continues.
    | Programmer Response: Check the HALDB Process Summary Report to
    | determine if the all deleted/defined partitions are processed.
    | If there are partitions that are not processed, you must
    | initialize them by DFSUPNT0 before using it.
    | Problem Determination: None
    
    ======================= End of Doc-Change ======================
    

APAR Information

  • APAR number

    PK48420

  • Reported component name

    IMS HIGH PERF L

  • Reported component ID

    5655E0700

  • Reported release

    210

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-07-05

  • Closed date

    2007-07-26

  • Last modified date

    2007-08-03

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

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

    UK27474

Modules/Macros

  •    HPSCOPTD HPSRDSCT HPSRFCA0 HPSRMSGT HPSRRLDA
    HPSRRLDM HPSRRLD7 HPSRRLD8 HPSRRLD9 HPSRRRIN HPSRRRI0 HPSRRRI9
    HPSRSTMT
    

Publications Referenced
SC18922202    

Fix information

  • Fixed component name

    IMS HIGH PERF L

  • Fixed component ID

    5655E0700

Applicable component levels

  • R210 PSY UK27474

       UP07/07/27 P F707

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":"BU048","label":"IBM Software"},"Product":{"code":"SSCX89F","label":"IMS HP Load"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.1.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 August 2007