PK21494: ENHANCEMENT TO SORT CONTROL STATEMENT

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• This APAR provides a new function that makes it possible
  for HP Load to determine whether the physical sequential
  sort processing is needed before loading.
  

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    *
  *                      determine whether to run the physical   *
  *                      sequential sort processing.             *
  ****************************************************************
  * RECOMMENDATION: Apply the maintenance for this APAR.         *
  ****************************************************************
  This APAR provides a new function to determine whether to run
  the physical sequential sort processing by using the information
  stored in the particular records written to the unload data set.
  This function needs IMS High Performance Unload for OS/390
  Version 1 Release 1 with APAR PK21498. In order to use this
  function, unloaded data set have to be created by High
  Performance Unload with CHECKREC=YES option. And specify
  SORT=COND in the FRRIN.
  

Problem conclusion

Temporary fix

Comments

• HP Load provides a new function to determine whether to run the
  physical sequential sort processing.
  
  *
  ========================
  = 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.4 Processing environments
  1.1.4.1 Software requirements
  ---------------------------------------------------------------
     :
    IMS High Performance Load for z/OS supports only the exit
    routines for data conversion provided by this product.
    Physical Sequence Sort for Reload requires DFSORT(TM) (Data
    Facility Sort), which is a part of z/OS. It is the same as
  | when you specify YES or COND for the SORT= control statement.
  | - If you use SORT=COND option, HP Load determines whether to
  |   run the physical sequential sort processing by using the
  |   information stored in the particular records written to the
  |   unload data set. This function needs IMS High Performance
  |   Unload for OS/390 Version 1 Release 1 with APAR PK21498. In
  |   order to use this function, unload data set have to be
  |   created by High Performance Unload with CHECKREC=YES
  |   option.
     :
  
  ---------------------------------------------------------------
  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 1. DD statements and record format for High          |
   |          Performance Load                                  |
   +----------+-----------+-----------+-------------------------+
   | DDNAME   | Use       | Format    | Need                    |
   +----------+-----------+-----------+-------------------------+
                                 :
   |          |           |           |                         |
   +----------+-----------+-----------+-------------------------+
   | SEQERROR=| ABEND or  | ABEND     | Handles key sequence    |
   |          | SAVE      |           | errors                  |
   +----------+-----------+-----------+-------------------------+
   | SORT=    | YES       | NO        | Specifies whether to    |
  ||          | NO        |           | run physical sequential |
  ||          | COND      |           | sort before the load    |
   |          |           |           | process                 |
   +----------+-----------+-----------+-------------------------+
   | USEREXIT=| exitname  | (none)    | Specifies the name of   |
                                :
  
   2.2.3.22 SORT control statement
     :
     ___________________________________________________________
    |                                                           |
    |             _NO___                                        |
    | >>__SORT=__|_YES__|____________________________________>< |
  | |            |_COND_|                                       |
    |___________________________________________________________|
  
  
    YES
     Runs physical sequential sorting before the reload process.
     It sorts in the physical sequence of the block, then the RAP
     numbers.
  
    NO
     Does not run the sort process.
  
  | COND
  |  Runs physical sequential sorting if any of the following
  |  conditions is satisfied:
  |
  |  - When using Load API function
  |  - The input unloaded data set was created in *CS format
  |  - The input unloaded data set was not created by HP Unload
  |    with CHECKREC=YES option
  |  - The input unloaded data sets are concatenated
  |
  |  When the input unloaded data set was created by HP Unload
  |  with APAR PK21498 and CHECKREC=YES option, the following
  |  conditions are also used as the criteria:
  |
  |  - DB organization is changed from (P)HIDAM to (P)HDAM
  |  - The input unloaded data set was created via secondary
  |    index database
  |  - Any of the following is changed between unload and reload
  |    processes:
  |    - Randomizing module name
  |    - RAP number
  |    - The maximum BLK/CI number in RAA
  |    - The starting position of root key
  |    - The length of root key
  
    The HDAM/PHDAM data should be in the order for loading, so if
  | it is not in that order, SORT=YES or COND is required.
  | Instead of reloading with SORT=YES or COND, you can run PSSR
    before reloading.
    This statement is applicable for HDAM/PHDAM, and there are
    some restrictions as follows:
  
    - This statement is exclusive with the USERHDR= and the
      USERHDRX= control statements.
     :
  
  | If you specify SORT=COND, HP Load determines whether to run
  | the physical sequential sort processing according to the
  | criteria listed above. So, in some cases, it does not sort
  | input unloaded data sets even if the sort process is required
  | for the reload. In such a case, you have to run PSSR before
  | reloading or specify SORT=YES instead of SORT=COND.
  
  ---------------------------------------------------------------
  APPENDIX1.3 Appendix C. Message and Codes
  APPENDIX1.3.3.1 High Performance Load Messages
  ---------------------------------------------------------------
                                 :
  | HPSR0119I PHYSICAL SEQUENTIAL SORTING PROCESSED (rrrr)
  |
  | Explanation: SORT=COND is specified and physical sequential
  | sorting is processed by one of following reasons.
  |
  | Reason
  | - Description
  |
  | CHANGE DB ORGANIZATION
  | - DB organization is changed from (P)HIDAM to (P)HDAM
  | CHANGE RANDOMIZER
  | - The randomizing module name is changed between unload and
  |   reload processes.
  | CHANGE RAP#
  | - RAP number is changed  between unload and reload processes.
  | CHANGE RBN
  | - The maximum BLK/CI number in RAA is changed between unload
  |   and reload processes.
  | CHANGE ROOT KEY LENGTH
  | - The length of root key is changed between unload and reload
  |   processes.
  | CHANGE ROOT KEY POSITION
  | - The starting position of root key is changed between unload
  |   and reload processes.
  | CONCATENATED UNLOAD D/S
  | - The input unloaded data sets are concatenated
  | CS HEADER
  | - The input unloaded data set was created in *CS format
  | LOAD API
  | - Load API function is used
  | LOW LEVEL UNLOAD D/S
  | - The input unloaded data set was not created by HP Unload
  |   with CHECKREC=YES option or the APAR PK21498 was not
  |   applied for HP Unload.
  | UNLOADED VIA SECONDARY INDEX
  | - The input unloaded data set was created via secondary index
  |   database
  |
  | System Action: Processing continues.
  | Programmer Response: None
  | Problem Determination: None
  
  | HPSR0120I SORT PROCESS IS NOT APPLICABLE (rrrr)
  |
  | Explanation: SORT=COND is specified. However, physical
  | sequential sorting is not processed by one of following
  | reasons.
  |
  | Reason
  | - Description
  |
  | DB ORGANIZATION
  | - DB organization is not (P)HDAM.
  | USERHDR=
  | - Both SORT= and USERHDR= are specified.
  | USERHDRX=
  | - Both SORT= and USERHDRX= are specified.
  |
  | System Action: Processing continues.
  | Programmer Response: Please refer to the description of SORT=
  | control statement and verify the reason.
  | Problem Determination: None
  ======================= 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:

  UK13163

Modules/Macros

• FABSPE15 FABSPE35 FABSRT15 FABSRT35 HPSRDSCT
  HPSRFCA0 HPSRHDLD HPSRHDL7 HPSRHDL8 HPSRHDL9 HPSRHSLD HPSRHSL7
  HPSRHSL8 HPSRHSL9 HPSRMSGT HPSRRLDM HPSRRLD7 HPSRRLD8 HPSRRLD9
  HPSRRRIN HPSRRRI0 HPSRRRI9 HPSRSTMT
  

Fix information

• Fixed component name

  IMS HIGH PERF L

• Fixed component ID

  5655E0700

Applicable component levels

• R210 PSY UK13163

     UP06/04/04 P F604

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.