PM63004: ZFILE.EXISTS THROWS ZFILEEXCEPTION FOR A NONEXISTENT PDS DATASET NAME AND MEMBER INSTEAD OF RETURNING FALSE

APAR status

• Closed as program error.

Error description

• Using JzOS build version 2.4.0 or later (shipped with Java 6.0.1
  and Java 7) ,  class ZFile method exists throws ZFileException
  For example:
  Exception in thread "main" com.ibm.jzos.ZFileException:
  //'A.B.C': fopen() failed;
  EDC5049I The specified file name could not be located.
  ; errno=49 errno2=0xc00b0641 last_op=50 errorCode=0x21708
  at com.ibm.jzos.ZFile.fopen(Native Method)
  at com.ibm.jzos.ZFile.doZFileOpen(ZFile.java:601)
  at com.ibm.jzos.ZFile.<init>(ZFile.java:464)
  at com.ibm.jzos.PdsDirectory.<init>(PdsDirectory.java:72)
  at com.ibm.jzos.ZFile.dsExists(ZFile.java:214)
  at com.ibm.jzos.ZFile.exists(ZFile.java:276)
  at JzOSTest.main(JzOSTest.java:7)
     Using Java5 or Java6, which includes the JzOS
  version 2.3.0, ZFile.exists will return FALSE for
  a nonexistant PDS dataset.
  

Local fix

• Use either Java 5 or Java 6, which include the JzOS version
  2.3.0
  

Problem summary

• The problem is caused when calling ZFile.exists() on a PDS
  member with a nonexistent PDS and member name.
  

Problem conclusion

• This defect will be fixed in:
  6.0.1 SR4 (z/OS 31-bit)
  .
  JZOS is updated such that calling ZFile.exists() on a PDS member
  with a nonexistent PDS and member name will return false,
  instead of throwing a ZFileException.
  

Temporary fix

Comments

APAR Information

• 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 Z/OS 31

• Fixed component ID

  620700105

Applicable component levels

• R601 PSY

     UP