A fix is available
APAR status
Closed as program error.
Error description
PNTLSTRL and hence PDALSTRL, should have maximum/largest key length of the all the defined partitions defined in a HALDB. In this customers environment, PNTLSTRL and PDALSTRL is set to 2 not 19 that is the true max size of the key length. DFSPSM10 code will be modified correct this base code error.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All IMS V13 HALDB (High Availability Large * * Database) users who have defined different * * KEYSTRNG lengths for the partitions. * **************************************************************** * PROBLEM DESCRIPTION: Records, that belong to a set of * * partitions with a certain KEYSTRNG, are * * inserted into the wrong partitions. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** User has a HALDB that has 222 partitions and a partition selection exit (PSE). The partitions are selected by account number or part of the account number. 16 of the 222 partitions are dedicated to a single account and are defined to DBRC with a KEYSTRNG of 19. The rest of the partitions are defined with a KEYSTRNG of 2. Two key tables are constructed and the length of each table entry is a user defined entry length plus the largest string length (PDALSTRL). PDALSTRL is 1 (length-1) and not 18 as expected so the 16 dedicated partitions are not selected and their records are inserted in other partitions. A batch unload/reload puts the records back in their proper partitions. The problem is PDALSTRL (DFSPDA) and PNTLSTRL (DFSPNT) both contain a length of 2 and not the longest defined key string (KEYSTRNG). During system initialization of all partitioned database DDIRs DBRC is called to obtain partition definition data. The length of the longest KEYSTRNG is returned in the field XDL_MAXPSLEN. This first call to DBRC is only for the first 12 partitions and DBRC will need to be called again and again until all partition definition data has been retrieved for all partitions in the HALDB. XDL_MAXPSLEN will not have the longest KEYSTRNG until all partition definition data has been retrieved. The problem is DFSPSM10 does not get the value from XDL_MAXPSLEN on the subsequent DBRC calls and PDALSTRL and PNTLSTRL are updated to contain the longest KEYSTRNG of the first 12 partitions.
Problem conclusion
GEN: KEYWORDS: *** END IMS KEYWORDS *** DFSPSM10 has been changed to get the value from XDL_MAXPSLEN after each call to DBRC which will cause PDALSTRL and PNTLSTRL to be updated to contain the longest KEYSTRNG.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PM78787
Reported component name
IMS V13
Reported component ID
5635A0400
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2012-12-08
Closed date
2013-02-22
Last modified date
2013-10-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
010PC2 UK91949
Modules/Macros
DFSPSM10
Fix information
Fixed component name
IMS V13
Fixed component ID
5635A0400
Applicable component levels
R300 PSY UK91949
UP13/02/27 P F302
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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"300","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
14 December 2020