APAR status
Closed as program error.
Error description
When a GDG data exists, the java RecordFile.getInstance method opens the GDG dataset instead of just establishing a reference to it. As a result, a call to FileOutputRecordStream.getInstance using the RecordFile object results in the creation of another GDG dataset. RecordFile should not issue the open call that causes the initial GDG dataset creation. RecordFile should only be used to navigate the dataset hierarchy. It should not be opening any datasets. The problem was reported for, Java(TM) SE Runtime Environment (build pmz3160sr7-20091215_02(SR7)) IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 z/OS s390-31 jvmmz3160sr7-20091214_49398 (JIT enabled, AOT enabled) J9VM - 20091214_049398 JIT - r9_20091123_13891 GC - 20091111_AA) JCL - 20091202_01 However, the problem is present in earlier versions of java. The comments in the RecordFile.java file have the following: /** * Constructs a RecordFile. If the record file exists then it is opened * with the original record length and record format, otherwise * <code>JRIO_DEFAULT_RECORD_LENGTH</code> and * <code>JRIO_DEFAULT_RECORD_FORMAT</code> are used. * @param absoluteFileName the full path name of the file. */
Local fix
Problem summary
When FileOutputRecordStream opens a GDG dataset using a +1 relative index, 2 new GDG datasets are created. For example, if a GDG dataset has 2 generations, by opening the GDG dataset with a +1 relative index, 2 additional generations will be created, resulting in a total of 4 generations.
Problem conclusion
This will be fixed in: 6.0.0 SR9 FP1 The solution is to use absolute path name instead of GDG relative index in FileOutputRecordStream as soon as the file is created. To obtain the fix: Install build 20110211 or later
Temporary fix
Comments
APAR Information
APAR number
PM23826
Reported component name
JAVA 6 Z/OS 31
Reported component ID
620700105
Reported release
600
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-10-04
Closed date
2010-12-17
Last modified date
2011-11-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
JAVA 6 Z/OS 31
Fixed component ID
620700105
Applicable component levels
R600 PSY
UP
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
09 August 2022