A fix is available
APAR status
Closed as new function.
Error description
The IPR Driver supports the SORT control statement. This enables the user to specify whether to run the physical sequential sort processing between unload and reload.
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: HP Load provides new function to use * * the SORT control statement under the * * IPR Driver. * **************************************************************** * RECOMMENDATION: Apply the maintenance for this APAR. * **************************************************************** HP Load provides new function to use the SORT control statement for the IPR Driver. This enables the user to specify whether to run the physical sequential sort processing before the IPR Reload task. The sort process may be required when you change the randomizing parameters of HDAM database during reorganization by using the NEWDBD control statement for the IPR Driver. If you specify SORT=YES, the sort is processed unconditionally. If you specify SORT=COND, the sort is processed depending on conditions. The following APARs are also needed to use this new function: - PK33846 IMS Parallel Reorganization (FMID: H25N320) - PK33847 IMS High Performance Unload (FMID: H1IN110)
Problem conclusion
Temporary fix
Comments
======================== = 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 PK33847. 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.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 PK33847 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 | - Whether the root segment has key field 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. - The data updated by the DATXEXIT= control statement is not supported. - The root key updated by USEREXIT is not supported. - The compressed root key data created by specifying the DECN option is not supported for the reload process. D - The statement is ignored when the program is run under the D IPR Driver. 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. | CHANGE SEQ KEY FIELD OF ROOT | - The definition of the root key field 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 PK33847 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 : | HPSR3764E KEY FIELD IS NOT DEFINED FOR THE ROOT SEGMENT OF | HALDB | | Explanation: A key sequence field needs to be defined for the | root segment of HALDB. | | System Action: High Performance Load issues a user 3764 abend. | Programmer Response: Correct the error and rerun the job. | Problem Determination: None
APAR Information
APAR number
PK34472
Reported component name
IMS HIGH PERF L
Reported component ID
5655E0700
Reported release
210
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2006-11-10
Closed date
2006-12-14
Last modified date
2007-01-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK20625
Modules/Macros
HPSRDSCT HPSRE15A HPSRFCA0 HPSRHDBD HPSRHDB7 HPSRHDB8 HPSRHDB9 HPSRHDLD HPSRHDL7 HPSRHDL8 HPSRHDL9 HPSRMSGT HPSRRLDM HPSRRLD7 HPSRRLD8 HPSRRLD9 HPSRRRIN HPSRRRI0 HPSRRRI9
| SC18922201 |
Fix information
Fixed component name
IMS HIGH PERF L
Fixed component ID
5655E0700
Applicable component levels
R210 PSY UK20625
UP06/12/16 P F612
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.
[{"Line of Business":{"code":null,"label":null},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX89F","label":"IMS HP Load"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.1.0"}]
Document Information
Modified date:
14 December 2020