IBM Support

PK76659: ILDSBLD=YES,DSPR SORTIN PROBLEMS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible in next release.

Error description

  • This APAR fixes the following problems of the ILDSBLD=YES,DSPR
    function
      - SORTIN data sets (HPSRILEA and HPSRILEB) allocated
    dynamically are not deleted until the job-step termination. Too
    much system dasd space is requested.
      - SORTIN data sets cannot be specified in JCL.
      - SORT error when no ILE record is built.
    

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 fixes the following problems  *
    *                      of the ILDSBLD=YES,DSPR function :      *
    *                      1. SORTIN data sets (HPSRILEA and       *
    *                         HPSRILEB) allocated dynamically      *
    *                         are not deleted until the job-step   *
    *                         termination. Too much system dasd    *
    *                         space is requested.                  *
    *                      2. SORTIN data sets cannot be specified *
    *                         in JCL.                              *
    *                      3. SORT error when no ILE record is     *
    *                         built for a logical relationship or  *
    *                         a PSINDEX database.                  *
    ****************************************************************
    * RECOMMENDATION: Apply the maintenance for this APAR.         *
    ****************************************************************
    This APAR fixes the following problems of the ILDSBLD=YES,DSPR
    function:
    1. SORTIN data sets (HPSRILEA and HPSRILEB) allocated
       dynamically are not deleted until the job-step termination.
    2. When a SORTIN data set (HPSRILEA or HPSRILEB) is specified
       in JCL, HP Load attempts to allocate it dynamically,
       and a HPSR3640E error occurs.
    3. When ILDSBLD=YES,DSPR is specified, and no ILE record is
       built for a logical relationship or a PSINDEX database
       for a partition, SORT task ended abnormally.
    And this APAR provides a minor enhancement: The number of
    ILDS records are added to "Segment count summary" report.
    

Problem conclusion

Temporary fix

Comments

  • ========================
    = Documentation Change =
    ========================
    IMS High Performance Load for z/OS Version 2 Release 1 User's
    Guide SC18-9222-03 ( SC18922203 ) should be changed as follows:
    ================================================================
    2.0 IMS High Performance Load
    2.2.2 JCL requirements
    
    HPSRILEA, HPSRILEB, and HPSRWKnn data sets are added.
    
     +-----------------------------------------------------------+
     |Table 1. DD statements and record format                   |
     |         for IMS High Performance Load                     |
     +-----------+---------------+------------+------------------+
     | DDNAME    |  Use          |  Format    | Need             |
     +-----------+---------------+------------+------------------+
     :           :               :            :                  :
    |+-----------+---------------+------------+------------------+
    || HPSRILEA  | Input/Output  |            | Optional         |
    |+-----------+---------------+------------+------------------+
    || HPSRILEB  | Input/Output  |            | Optional         |
    |+-----------+---------------+------------+------------------+
    || HPSRWKnn  | Input/Output  |            | Optional         |
     +-----------+---------------+------------+------------------+
    
    | HPSRILEA/HPSRILEB DD
    |   These data sets are used by DFSORT, substituting for SORTIN
    |   data sets, when ILDSBLD=YES,DSPR is specified.
    |   If you do not specify the statement, the data sets are
    |   allocated dynamically with sizes estimated on the basis of
    |   the allocation size of ILDS.
    |   A dummy data set or DISP=MOD parameter can not be specified
    |   on the HPSRILEA/HPSRILEB DD statement.
    |   For more information of SORTIN data sets, see DFSORT
    |   Application Programming Guide.
    |
    | HPSRWKnn DD
    |   These data sets are used by DFSORT, substituting for
    |   SORTWK data sets, when ILDSBLD=YES,DSPR is specified.
    |   nn shows its serial number.
    |   If you do not specify the statement, the data sets are
    |   allocated dynamically by DFSORT.
    |
    |   For more information, see DFSORT Application Programming
    |   Guide.
    ---------------------------------------------------------------
     2.2.3 Control statements
     2.2.3.13 ILDSBLD control statement
    
      Specifies whether to build ILDS and how to build the ILDS.
      This control statement is optional. If you do not explicitly
      specify this control statement, ILDSBLD=C will be used.
        __________________________________________________________
       |                                                          |
       |                _C______________                          |
       | >>__ILDSBLD=__|_YES__ _______ _|______________________>< |
       |               |      |_,DSPR_| |                         |
       |               |_NO_____________|                         |
       |__________________________________________________________|
    
    C
     ILDS is rebuilt in the same manner of IMS HD Reorganization
     Reload.
    
       YES
         ILDS is rebuilt. In the process of rebuilding, the records
         of ILDS are arranged in sequence of the key value.
         To improve the performance of rebuilding ILDS by making
         the VSAM load mode in effect, you need to specify the
    |    REUSE and SPEED parameter in your ILDS CLUSTER definition,
         and specify the ILDSBLD=YES control statement.
    
        DSPR
    |     ILDS is rebuilt using DFSORT to sort ILE records,
    |     instead of using data space heap sort.
    |     HPSRILEA,HPSRILEB and HPSRWKnn work data sets, which are
    |     used as SORTIN and SORTWK data sets, are allocated
    |     dynamically if you do not specify those DD statements.
    
    ---------------------------------------------------------------
    2.2.4 Reports and statistics
    2.2.4.1.2 Segment Count Summary report
    :
    Figure 3 shows an example of the Segment Count Summary report
      for an HDAM database. ...
    :
      IMS HIGH PERFORMANCE LOAD
      5655-M26                                                    12
    
                                 "SEGMENT COUNT SUMMARY"
    
      DBNAME = PHIO0100  PARTNAME = PHIO01A    PART ID = 00001   DS
    
      *** SEGMENT COUNT IN THIS PARTITION ***
                                                           DELETED B
         SEGNAME  LVL DSG PARENT   READ        RELOADED    RANDOMIZE
         -------- --- --- -------- ----------- ----------- ---------
         ROOT1LV1  01  01                   21          21
         DEP11LV2  02  02 ROOT1LV1          21          21
         DEP21LV2  02  02 ROOT1LV1          21          21
         DEP31LV3  03  02 DEP21LV2          21          21
         DEP41LV2  02  03 ROOT1LV1          21          21
         DEP51LV3  03  03 DEP41LV2          21          21
         DEP61LV3  03  03 DEP41LV2          21          21
         -------- --- --- -------- ----------- ----------- ---------
         TOTAL                             147         147
    
    | ILDS RECORDS = 21
    
      *** SEGMENT COUNT IN HDAM OVERFLOW AREA ***
    
         SEGNAME  OCCURRENCES PERCENTAGE
         -------- ----------- ----------
         ROOT1LV1           0        0.0
         DEP11LV2           0        0.0
         DEP21LV2           0        0.0
         DEP31LV3           0        0.0
         DEP41LV2           0        0.0
         DEP51LV3           0        0.0
         DEP61LV3           0        0.0
         -------- -----------
         TOTAL              0
    
      This report consists of two parts: a segment count in the
      entire database, and a segment count in the HDAM, PHDAM, or
      HISAM overflow area.
      :
      DELETED BY USER EXIT
      The number of deleted segment occurrences due to a return code
      8 or 12 from the user exit routine.
    
    | ILDS RECORDS
    |  The number of ILE records in ILDS for this partition.
    ---------------------------------------------------------------
      APPENDIX1.3.3.1 High Performance Load messages
    
      HPSR3735E NONZERO RETURN CODE FROM DFSURIT0; aa, PID=bbbb,
               RC=cccccccc, RSN=dddddddd|CC=cccc
      Explanation: An error was found when DFSURIT0 was called
      to end the process for ILDS of Partition ID: bbbb.
      The DFSURIT0 either ended with a return code of cccccccc
      and a reason code of dddddddd or ended abnormally with
      a completion code of cccc.
        Error Type (aa) Description
        01              GETMAIN error.
        02              FREEMAIN error.
        03              VSAM error.
        04              Load error.
        05              Sort error.
        06              Data space error.
        07              DFSURIT0 ended abnormally.
      System action: The Reload task issues a user 3735 abend.
    | Programmer response: For the data space error (aa=06),
    | the return code and the reason code shown in the message
    | are from DSPSERV macro. See MVS Assembler Services Reference
    | and check the meaning.
    | Otherwise, this is likely to be an internal system
      error. Record the message and contact IBM Software Support.
      Problem determination: None.
    ---------------------------------------------------------------
    | HPSR3621E INCORRECT DATA SET FOR dddddddd DD -
    | rrrrrrrr
    |
    | Explanation:  Incorrect parameter is specified in dddddddd
    | DD, error reason is rrrrrrrr
    |
    | Reason (rrrrrrrr) Description
    |
    | DUMMY
    |   A dummy data set is specified for ddddddd
    | DISP=MOD
    |   DISP=MOD is spesified for ddddddd
    |
    | 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 number

    PK76659

  • 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

    2008-12-01

  • Closed date

    2008-12-11

  • Last modified date

    2009-01-02

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

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

    UK42426

Modules/Macros

  • HPSCRR05 HPSCZRIO HPSCZRPA HPSRCILA HPSRCILE
    HPSRCIL7 HPSRCIL8 HPSRCIL9 HPSRDSCT HPSRHRPA HPSRHRPT HPSRHRP7
    HPSRHRP8 HPSRHRP9 HPSRHTBL HPSRMSGT HPSRRCBM HPSRRIO0 HPSRRLDA
    HPSRRLDM HPSRRLD7 HPSRRLD8 HPSRRLD9 HPSRRR05
    

Publications Referenced
SC18922203    

Fix information

  • Fixed component name

    IMS HIGH PERF L

  • Fixed component ID

    5655E0700

Applicable component levels

  • R210 PSY UK42426

       UP08/12/15 P F812

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:
02 January 2009