PK18989: ENABLE REDUCTION OF DATASPACE USAGE WHEN HPIO=N IS SPECIFIED.

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• A new method is provided to reduce dataspace usage when
  processing (P)HDAM OA and HPIO=N is specified.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IBM IMS High Performance        *
  *                 Load for OS/390 Version 2 Release 1          *
  *                 (FMID=H1IM210)                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: This APAR provides a new function to    *
  *                      reduce the usage of dataspace when      *
  *                      HPIO=NO is specified.                   *
  ****************************************************************
  * RECOMMENDATION: Apply the maintenance for this APAR.         *
  ****************************************************************
  This APAR provides a new function to reduce the usage of
  dataspace when HPIO=NO is specified.
  When you specify both OADSPR=YES and HPIO=NO, HP Load attempts
  to reduce the usage of dataspace in processing (P)HDAM overflow
  area by using an OVERFLOW DD as a temporary data set. If the DD
  statement is not specified in the JCL, High Performance Load
  attempts to allocate it on a direct access device dynamically.
  

Problem conclusion

Temporary fix

Comments

• HP Load provides a function to reduce the usage of dataspace in
  processing (P)HDAM overflow area by using an OVERFLOW DD as a
  temporary data set.
  
  ========================
  = DOCUMENTATION CHANGE =
  ========================
  IMS High Performance Load for z/OS Version 2 Release 1 User's
  Guide SC18-9222-01 ( SC18922201 ) should be changed as follows:
  
  ----------------------------------------------------------------
  1.0 General information
   1.1 Introduction
    1.1.5 Compatibility
     1.1.5.2 Compatibility with High Performance Load for OS/390
          Version 1
  ----------------------------------------------------------------
     :
    JCL and control statements used in Version 1 can be used in
    Version 2 except for:
  | The POINTERS DD ; it is not used in Version 2. If it is
  | specified, it will be ignored.
  
    The DATASPACE control statement; High Performance Load Version
    2 uses the data space only as a temporary area to keep pointer
    and database blocks; therefore, the specification of DATASPACE
    is not necessary. If specified, it will be ignored.
  
  ----------------------------------------------------------------
  1.0 General information
   1.1 Introduction
    1.1.6 Changes from Version 1
  ----------------------------------------------------------------
   :
    IMS High Performance Load for z/OS includes the following
    enhancements:
     :
  | Eliminating POINTERS DD statement.
  | This DD statements is not necessary in Version 2. High
    Performance Load uses the data space as a temporary space for
    database blocks and pointer information instead of using the D
    statements. If any is coded in a JCL stream for Version 2,
    it will be ignored. For details, see "Compatibility"
    in topic 1.1.5.
  
  ----------------------------------------------------------------
  2.0 High Performance Load
   2.2 Operating instructions
    2.2.2 JCL requirements
  ----------------------------------------------------------------
    +------------------------------------------------------------+
    | Table 1. DD statements and record format for High          |
    |          Performance Load                                  |
    +----------+-----------+-----------+-------------------------+
    | DDNAME   | Use       | Format    | Need                    |
    +----------+-----------+-----------+-------------------------+
                                 :
    +----------+-----------+-----------+-------------------------+
    | HPSRSIDX | Output    | RECFM=VB  | Optional                |
    |          |           | LRECL=900 |                         |
    +----------+-----------+-----------+-------------------------+
   || OVERFLOW | Input/    | RECFM=VB  | Optional                |
   ||          | Output    |           |                         |
    +----------+-----------+-----------+-------------------------+
    | IMSDALIB | Input     |  :        | Optional                |
  
   :
  
  (The following section should be added.)
  
  | OVERFLOW DD
  |
  | Defines an optional sequential data set used as a temporary
  | storage to keep database blocks that are directed to the
  | overflow area during HDAM RAA reloading. Such blocks are
  | written into the overflow area after RAA reloading completes.
  | This data set is used only if both OADSPR=Y and HPIO=N are
  | specified. The SPACE parameter for the DD statement must be
  | large enough to hold all CIs or blocks in the overflow area.
  | The DCB parameters must include RECFM=VB. High Performance
  | Load uses optimized BLKSIZE for this data set with which two
  | blocks reside in a track of a direct-access device or an
  | allowed maximum size for a tape.
  
  | This data set must reside on either a tape or a direct-access
  | device.
  
  | If this DD statement is not specified, High Performance Load
  | attempts to allocate dynamically the value calculated
  | internally according to the following method on a direct
  | access device.
  
  | Method of dynamic allocation size calculation: The number of
  | database blocks directed to the overflow area during HDAM RAA
  | reloading cannot be estimated in advance. For optimization,
  | High Performance Load calculates the cylinders in OVERFLOW DD,
  |  which can contain database blocks in 25% of RAA. High
  | Performance Load uses the same value in calculating both
  | primary and secondary values. The value is either the
  | calculated value of 10 cylinders, whichever is greater.
  
  | Because the blocks in OVERFLOW DD are maintained by a
  | different method from that in an actual database data set, the
  |  number of cylinders for the OVERFLOW DD cannot be directly
  | comparable with the 25% of RAA cylinders.
  
  | For the calculation, High Performance Load uses the geometry
  | of the 3390 device regardless of the actual device type of
  | OVERFLOW DD, because the device type cannot be known before
  | the allocation. If a 3380 or 9345 DASD is used, for example,
  | the effective percentage of RAA of the amount allocated is a
  | little smaller, around 20%.
  
  | Unfortunately, there is no formula for estimating the space
  | requirement for OVERFLOW DD beforehand. The size of OVERFLOW
  | DD depends on the number of segments to be directed to the
  | overflow part of the database. But a size equal to the
  | overflow part of the original database is enough, until you
  | change the DBD definition or the randomizer.
  
  ----------------------------------------------------------------
  2.0 High Performance Load
   2.2 Operating instructions
    2.2.3 Control Statements
     2.2.3.xx OADSPR control statement
  ----------------------------------------------------------------
    Specifies whether High Performance Load reduces the usage of
  | dataspace (DSP) when processing the overflow area by using the
  | High Performance I/O driver or by using an OVERFLOW DD.
    This specification is valid only for HDAM or PHDAM databases.
    This control statement is optional. If you do not explicitly
    specify this control statement, OADSPR=NO will be used.
  
      _________________________________________________________
     |                                                         |
     |               _NO__                                     |
     | >>__OADSPR=__|_YES_|_________________________________>< |
     |                                                         |
     |_________________________________________________________|
  
  
    YES
    Reduces the usage of DSP when processing the overflow area.
  
    No
    Does not reduce the usage of DSP when processing the overflow
    area.
  
    Notes:
  | If you specify both OADSPR=YES and HPIO=YES, High Performance
  | Load attempts to reduce the usage of dataspace by using the
  | High Performance I/O driver. It can also reduce the time for
  | reloading.
  | If you specify both OADSPR=YES and HPIO=NO, High Performance
  | Load attempts to reduce the usage of dataspace by using an
  | OVERFLOW DD as a temporary data set. If the DD statement is
  | not specified in the JCL, High Performance Load attempts to
  | allocate it on a direct access device dynamically. For
  | details, see "JCL Requirements" in topic 2.2.2.
    This function does not support IPR Type-A Image Copy
    processing.
    This function might not be able to reduce the usage of
  | dataspace depending on the DB. Because HP Load keeps the
  | data in a dataspace until the information for pointers
    in the block are resolved.
  
  ----------------------------------------------------------------
  APPENDIX1.3 Appendix C. Message and Codes
  APPENDIX1.3.3.1 High Performance Load Messages
  ----------------------------------------------------------------
                                 :
   HPSR0110W "keyword" IS IGNORED UNDER IMS REGION CONTROLLER
  
                HPIO=
   DELETE:
   |            OADSPR=
   DELETE:
  
    Explanation: The keyword cannot be used under IMS region
    controller (PGM=DFSRRC00). The parameter was ignored.
                                 :
  DELETE:
  | HPSR0117W OADSPR= IS IGNORED BECAUSE OF THE SPECIFICATION OF
  | HPIO=NO
  | Explanation: If HPIO=NO is specified in FRRIN DD or HPSIN DD,
  | The keyword OADSPR= cannot be used. The parameter is ignored.
  | System Action: Processing continues; the parameter was
  | ignored.
  | Programmer Response: Correct the control statement that is
  | causing the error, and if necessary, rerun the job.
  | Problem Determination: Check the control statement and the
  | database organization of the database to be reloaded.
  DELETE:
  
  | HPSR3710E DUMMY SPECIFIED FOR OVERFLOW DD
  |
  | Explanation:  The DUMMY parameter is specified in OVERFLOW DD.
  | The DUMMY parameter is not allowed for OVERFLOW DD.
  |
  | System Action:  High Performance Load issues a user 3710
  | abend and a dump.
  | Programmer Response:  Correct the error and rerun the job.
  |
  | Problem Determination:  Make sure that a DD statement is
  | present for the ddname indicated, and that it properly
  | identifies the correct data set.
  ======================= End of Doc-Change ======================
  

APAR Information

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

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

  UK12165

Modules/Macros

• FABFLINK HPSCCPYR HPSCOPTD HPSRBFRM HPSRDSCT
  HPSRHDLD HPSRHDL7 HPSRHDL8 HPSRHDL9 HPSROVIO HPSRRLDM HPSRRLD7
  HPSRRLD8 HPSRRLD9 HPSRRRIN HPSRRRI0 HPSRRRI9 H1IM210J
  

Fix information

• Fixed component name

  IMS HIGH PERF L

• Fixed component ID

  5655E0700

Applicable component levels

• R210 PSY UK12165

     UP06/03/02 P F603

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.