IV74107: JAVA TDUMPS ON ZOS ARE NOT UNIQUELY NAMED

APAR status

• Closed as program error.

Error description

• Error Message: The default naming convention for zOS TDUMPS
  generated by the Java SDK is
  "%uid.JVM.TDUMP.%job.D%y%m%d.T%H%M%S" where %uid is the zOS user
  ID and %job the zOS job name. This default, and the additional
  options available to configure the TDUMP name, do not allow a
  unique name to be constructed in cases where multiple instances
  of Java are being run under the same zOS user ID and job name.
  .
  Stack Trace: N/A
  .
  Additional dump naming options such as the %pid (process ID) and
  %tick (millisecond counter) tokens are not suitable for use in
  TDUMP names because of the zOS dataset naming
  rules. Each dot-separated qualifier in the dataset name must
  start with a non-numeric A-Z or $, and must be no more than 8
  characters.
  

Local fix

Problem summary

• The problem is caused by the limitations in the Java SDK dump
  naming options.
  

Problem conclusion

• Additional dump filename tokens %asid (zOS address space ID) and
  %jobid (zOS job ID) have been added to allow unique naming of
  the TDUMPs.
  .
  This APAR will be fixed in the following Java Releases:
   6 SR16 FP7 (6.0.16.7)
   8 SR1 FP10 (8.0.1.10)
   7 R1 SR3 FP10 (7.1.3.10)
   7 SR9 FP 10 (7.0.9.10)
   6 R1 SR8 FP7 (6.1.8.7)
  .
  Contact your IBM Product's Service Team for these Service
  Refreshes and Fix Packs.
  For those running stand-alone, information about the available
  Service Refreshes and Fix Packs can be found at:
   https://www.ibm.com/developerworks/java/jdk/
  

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:

  PI45888

• Fixed component name

  J9 COMMON CODE

• Fixed component ID

  620700127

Applicable component levels

• R600 PSY

     UP

• R270 PSY

     UP

• R260 PSY

     UP