A fix is available
APAR status
Closed as program error.
Error description
Various bugs discovered during internal testing with EzNoSql 1) -1 in max_space results in 0C9 when using znsq_create 2) dsname and storclas with only blank characters result in 0x7FFF for znsq_create 3) Missing double quotes on keyname when calling znsq_create_index results in 0x00000100 4) DocumentJNI_read allocation failure with Java eznosql workload 5) EXTATTR(PGM) NOT SET FOR LIBIGWZNSQJ.SO OBJECT IN USS IN 3.2 (discovered in field) Additional Keywords: SMSVSAM RLS VSAMRLS DF122 EZNOSQL/K AIFRAMEWORK/K
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * All EzNoSQL API and VSAMDB users * **************************************************************** * PROBLEM DESCRIPTION: * * Miscellaneous fixes and enhancements * * for EzNoSQL APIs * **************************************************************** * RECOMMENDATION: * **************************************************************** The C API znsq_create() function will issue an unknown (0x7FFF) return code if passed an invalid data set name and/or SMS construct (storage, data, management) class names containing whitespace characters. The C API znsq_create() function will cause an ABEND0C9 if the max_space argument is passed an invalid range of hexadecimal values. The Java API insert() function causes a memory leak in the case of auto-generated key insert calls. C, Java, and Python APIs exhibit incomplete Reason/Return code error information when invalid data set name arguments are detected in znsq_create_index(). C, Java, and Python read APIs may return corrupted JSON documents if the average document size parameter is smaller than the actual written document size. This presents as a spanned document that will also be missing its auto-generated key. Java and Python APIs may return garbage data at the end of a JSON document when re-driving a read request, resulting in an invalid JSON. RLS compressed documents contain an extra byte. JNI libigwznsqj.so file is missing the EXTATTR(PGM) attribute on z/OS 3.2 Keywords: SMSVSAM RLS VSAMRLS DF122 EZNOSQL/K AIFRAMEWORK/K RLSPSP/K
Problem conclusion
znsq_create() will issue a specific return code for invalid data set and SMS construct class names. znsq_create() will issue an invalid argument return code if the max_space argument is out of bounds. The memory leak in Java insert() is patched at the JNI layer. znsq_create_index() prints the full Reason/Return code in the event of invalid data set names. znsq_read() and Java readOne() fixes JSON document corruption with null-terminates and reallocates a new buffer on a re-drive attempt. VSAM RLS compressed records no longer contain an extra byte. libigwznsqj.so is set with the EXTATTR(PGM) bit enabled by default. libigwznsqj.so, libigwznsqd31.so and libigwznsqd64.so are set with the APF-authorized bit enabled by default.
Temporary fix
Comments
APAR Information
APAR number
OA68612
Reported component name
VSAM REC LEV SH
Reported component ID
5695DF122
Reported release
320
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2025-10-10
Closed date
2026-06-04
Last modified date
2026-07-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UJ99671 UJ99672 UJ99673
Modules/Macros
IDAVRRS1 IGWVRCIX IGWVRD31 IGWVRD64 IGWVR312 IGWVRJNI IDAVRCMS IGWVRJAR IGWVRCLU
Fix information
Fixed component name
VSAM REC LEV SH
Fixed component ID
5695DF122
Applicable component levels
R250 PSY UJ99673
UP26/06/16 P F606
R310 PSY UJ99672
UP26/06/16 P F606
R320 PSY UJ99671
UP26/06/16 P F606
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":"320"}]
Document Information
Modified date:
02 July 2026