IBM Support

PI90210: Change of JVMPROFILE file needs to be done each time a new fix pack is released.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer is looking for a solution to allow him to have a
    version of the MQ files in USS which do not have the VRM
    number as part of the files names, so he does not need to
    change his JVMProfile files each time a new MQ fix pack
    is released.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IBM MQ for z/OS Version 9       *
    *                 Release 0 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: When a fixpack is applied to the MQ for *
    *                      z/OS java component, an OSGi system     *
    *                      (for example CICS OSGi) configured to   *
    *                      reference the OSGi jar files may lose   *
    *                      access to the MQ jars and fail the next *
    *                      time they are needed.                   *
    ****************************************************************
    The jar files for OSGi are named with the current fixpack level
    as part of the filename. When applying maintenance to the Java
    component of MQ, the SMP/E install replaces the previous OSGi
    files with new ones which thus have new names. The JVM profile
    for an OSGi JVM server needs to be edited to refer to the new
    jar names otherwise it will fail to access them.
    

Problem conclusion

  • Symlinks have been added to the file system so that the JVM
    profile configuration only has to be performed once, persisting
    future fixpack installations.
    
    The following page in the IBM MQ 9.0.0 Knowledge Center is
    updated:
    IBM MQ
     Developing Applications
      Developing JMS and Java applications
       Using IBM classes for JMS
        Using IBM classes for JMS in a CICS OSGi JVM server
    
    https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm
    .mq.dev.doc/q121750_.htm
    
    The pathnames to be set for com.ibm.mq.osgi.allclientprereqs.jar
    and com.ibm.mq.osgi.allclient.jar have changed from:
    <MQ_ROOT>/OSGi/com.ibm.mq.osgi.allclientprereqs_<VERSION>.jar
    <MQ_ROOT>/OSGi/com.ibm.mq.osgi.allclient_<VERSION>.jar
    to
    <MQ_ROOT>/OSGiCurrent/com.ibm.mq.osgi.allclientprereqs.jar
    <MQ_ROOT>/OSGiCurrent/com.ibm.mq.osgi.allclient.jar
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI90210

  • Reported component name

    IBM MQ Z/OS V9

  • Reported component ID

    5655MQ900

  • Reported release

    008

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-11-14

  • Closed date

    2018-01-17

  • Last modified date

    2018-02-01

  • APAR is sysrouted FROM one or more of the following:

    PI86853

  • APAR is sysrouted TO one or more of the following:

    UI53262

Modules/Macros

  • CSQ8JTR1
    

Fix information

  • Fixed component name

    IBM MQ Z/OS V9

  • Fixed component ID

    5655MQ900

Applicable component levels

  • R008 PSY UI53262

       UP18/01/31 P F801

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":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
01 February 2018