PH20304: LAST JAR FILE FROM CLASSPATH NOT IMPORTED INTO JMP REGION'S JVM

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• JMP regions changed to run with STDENV scripting (support added
  V14) to provide more flexibility. In contrast to the Java
  classpath configuration with the DFSJMMS PROCLIB member the
  STDENV scripting doesn't seem to correctly import the last jar
  file into the JMP region's JVM.
  message java.lang.NoClassDefFoundError
  

Local fix

• Append a colon ':' to the end of the export statement.
  For example:
  export CLASSPATH="$CLASSPATH":
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All IMS V15 users of Java enabled dependent regions that     *
  * make use of the STDENV DD card.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * There are a couple of problems with the modules DFSJVM00 and *
  * DFSJVM64:                                                    *
  * 1-                                                           *
  * When a Java enabled IMS dependent region is started with the *
  * STDENV DD card specified, the last item that appears on an   *
  * export statement is not recognized unless the export         *
  * statement is ended with a colon ':'.                         *
  *                                                              *
  * 2-                                                           *
  * The modules DFSJVM00 and DFSJVM64 are setting two            *
  * environment variables that are not needed and as a result we *
  * get the following unwanted messages: 'DFSJVMxx: Option # =   *
  * TEST_ENV=YES' and 'DFSJVMxx: Option # = BPX_SHAREAS=NO'.     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * INSTALL CORRECTIVE SERVICE FOR APAR/PTF                      *
  ****************************************************************
  Here are more details about the problems in DFSJVM00 and
  DFSJVM64:
  1-
  When the dependent region is processing the contents of the
  STDENV DD card, it gets back strings of characters that contain
  a New Line character at the end. This New Line character is not
  being removed from the strings before their contents get used or
  passed along to the JVM. The result is that the name of last
  item in the export statement is being interpreted as the name
  with the New Line character included, which is an item that does
  not exist in the file system. For example, if the last item in
  the exported CLASSPATH is 'imsudb.jar' it is interpreted as
  'imsudb.jar\n', where '\n' is the New Line character.
  
  2-
  The following two messages are a result of leftover unit-testing
  code and should not be printed.
  'DFSJVMxx: Option # = TEST_ENV=YES'
  'DFSJVMxx: Option # = BPX_SHAREAS=NO'
  

Problem conclusion

• The solutions to the problems in DFSJVM00 and DFSJVM64 are as
  follows:
  1-
  The modules DFSJVM00 and DFSJVM64 will remove the trailing New
  Line character from all the statements processed from the STDENV
  DD card.
  
  2-
  Remove the leftover unit-testing code that causes DFSJVM00 or
  DFSJVM64 to print the two unwanted messages.
  

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:

  UI69295

Modules/Macros

• DFSJVM00 DFSJVM64
  

Fix information

• Fixed component name

  IMS V15

• Fixed component ID

  5635A0600

Applicable component levels

• R500 PSY UI69295

     UP20/05/07 P F005

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.