A fix is available
APAR status
Closed as program error.
Error description
1) ABEND0F4 RSN614DEBC6 during ENDREQ, when attempting to free a block which was already freed. 2) For VSAMDB, SEQ requests and PUT noupdate do not support ARA31. 3) No ACB flags to determine if DB is keyless or is ordered index. 4) Possible to attempt to create two common block pools 5) ABEND0F4 RSN82010027 when racing EzNoSQL Connects creating IGWVRCT Btree. Additional Keywords: SMSVSAM RLS VSAMRLS DF122 RLSPSP/K VSAMDB RSNCODE 614DEBC6 82100022 COB0605T/K
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All EzNoSQL and VSAMDB users * **************************************************************** * PROBLEM DESCRIPTION: 1) ABEND0F4 RSN614DEBC6 is caused by * * orphaned AIX keys after canceling * * update AIXs for both RLS and VSAMDB * * 2) For VSAMDB, SEQ requests and PUT * * noupdate did not support ARA31. * * 3) No ACB flags to determine if DB is * * keyless or is ordered index. * * 4) Possible to create two common block * * pools because there is a missing * * check for an existing common block * * pool. * * 5) ABEND0F4 RSN82010027 when racing * * EzNoSQL Connects creating IGWVRCT * * Btree. * **************************************************************** 1) While canceling updating alternate indexes, the keys could be orphaned. The ABEND0F4 RSN614DEBC6 would occur during later requests because of these orphaned keys. 2) ARA31 is not supported. 3) ACB flags are needed in order for users to determine if a DB is keyless or ordered index. 4) When getting AIX record areas, it is possible to create two common block pools because it does not check if there is one existing already. 5) Racing causes the ABEND0F4 because a Connect request may access a control block created by another Connect
Problem conclusion
1. Fix ABEND0F4 RSN614DEB6C by doing external backout upon a failed AIX update request 2. For VSAMDB, now supports both ARA31 and ARA64 for RPLARG when returning key_value for SEQ requests and PUT noupdate. 3. Add two new ACB flags to indicate if the VSAMDB opened is a keyless or ORDEREDINDEX. 4. Add checks to prevent attempt to create two common block pools 5. Fix ABEND0F4 RSN82010027 by adding a check for a successful znsq_open before accessing the control block KEYWORDS: RLSPSP/K COB0605T/K EZNOSQL/K AIFRAMEWORK/K
Temporary fix
Comments
APAR Information
APAR number
OA66674
Reported component name
VSAM REC LEV SH
Reported component ID
5695DF122
Reported release
310
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2024-06-26
Closed date
2025-05-06
Last modified date
2025-05-23
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UJ97097 UJ97099 UJ97100 OA67962
Modules/Macros
IDAV192A IDAV192B IDAV192C IDAV193A IDAV557X IDAVRAIX IDAVRBF4 IDAVRCL0 IDAVRCLN IDAVRCOM IDAVRDMP IDAVRED1 IDAVRLCK IDAVRPCP IDAVRR10 IDAVRR40 IDAVRRA0 IDAVRRU0 IDAVRRX0 IDAVSEOX IDAVSIN2 IFGACB IGW8FLAI IGW8FLPA IGW8FRLG IGWVR312 IGWVRBKO IGWVRCLR IGWVRCLS IGWVRCMT IGWVRCRE IGWVRDEL IGWVRERJ IGWVRERR IGWVRIV2 IGWVRIVJ IGWVRJAR IGWVRJNI IGWVRNXR IGWVROPN IGWVRPSJ IGWVRRDJ IGWVRREP IGWVRUPJ IGWVRUPR IGWVRWRR IGWVRWRT
Fix information
Fixed component name
VSAM REC LEV SH
Fixed component ID
5695DF122
Applicable component levels
R250 PSY UJ97100
UP25/05/20 I 1000
R310 PSY UJ97099
UP25/05/20 I 1000
R320 PSY UJ97097
UP25/05/20 I 1000
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":"BU011","label":"Systems - zSystems software"},"Product":{"code":"SG19M"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"310"}]
Document Information
Modified date:
24 May 2025