A fix is available
APAR status
Closed as program error.
Error description
When running the BLGUT1 index build utility against one of our da after upgrading to z/OS V2.5, the utility failed with the following message: BLX03113I BLXABEND: CODE=243, REASON=8, CHAIN=BLGUT135+0932.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the BLGUT1 (rebuild SDIDS from * * corresponding SDDS) utility in Tivoli * * Information Management for z/OS * **************************************************************** * PROBLEM DESCRIPTION: When the BLGUT1 utility processes a * * a logical SDDS record with more than * * 8191 (8K-1) unique structure words, it * * may lead to the utility taking a user * * abend 243 (x'F3') with reason code 8, * * indicating a VSAM PUT error for a * * record out of key sequence for an * * SDIDS. The issue seems to be more * * prevalent on a newer z/OS release, * * such as z/OS 2.5, versus older ones. * * * * Additional search keyword(s): * * ABENDU0243 ABENDU0F3 ABEND243 ABEND0F3 * **************************************************************** * RECOMMENDATION: * **************************************************************** As a part of the BLGUT1 utility's processing of SDDS records, the sort program it has been configured to invoke calls the E15 exit, BLGUT115, to read SDDS records, process them, and return to the sort program records that will be ordered and later passed to the E35 exit, BLGUT135, for writing to SDIDS. For a logical record (which may span multiple physical records) in SDDS, BLGUT115 collects the structure words, weeds out duplicates, and sorts them in ascending order before returning the structure words as individual records to the sort program. In sorting the structure words, BLGUT115 creates a reference array, initially with 8191 elements, with pointers to the buffered structured words. When an 8192nd structure word is encountered in a logical record, the reference array is expanded, the original array is copied into it, and the pointer to the latest structure word is inserted where it supposedly belongs in the array to maintain ascending order. Because the copy of the smaller array to the new array is 4 bytes off, the addition of an entry for the newly encountered, unique structure word is done incorrectly, basically wiping out one entry and leaving a zero address in the reference array where one should not be. When the reference array is used in creating the records to be passed to the sort program, the zero pointer is used to make a record that has trash data. Particularly on a release like z/OS 2.5, what corresponds to the key portion of the trash record happens to fall outside the key range of data already written into an SDIDS cluster, so the VSAM PUT fails and leads to the user 243 abend.
Problem conclusion
Part BLGUT115 is being changed to copy (non-zero) array entries from an old reference array to the correct place in the new, larger reference array.
Temporary fix
Comments
APAR Information
APAR number
OA65578
Reported component name
INFO MAN Z/OS 7
Reported component ID
5697SD900
Reported release
100
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2023-09-21
Closed date
2024-02-15
Last modified date
2024-03-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UJ94651
Modules/Macros
BLGUT115
Fix information
Fixed component name
INFO MAN Z/OS 7
Fixed component ID
5697SD900
Applicable component levels
R100 PSY UJ94651
UP24/02/16 P F402
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":"SSDHZ5","label":"Tivoli Information Management for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"100","Line of Business":{"code":"LOB70","label":"Z TPS"}}]
Document Information
Modified date:
04 April 2024