IBM Support

PH54585: WEBSPHERE APPLICATION SERVER FOR Z/OS 9.0.5.15 GENERIC JVM ARGUMENTS NOT EXPANDED IN JVM.OPTIONS FILES

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • In WebSphere z/OS 9.0.5.15, WebSphere variables and JVM
    generic argument are not expanded.  When a variable isn't
    expanded correctly, the argument might not work as expected.
    
    For example, the string ${JVM_CACHE} might be used in
    -Xshareclasses instead of the WebSphere home directory
    (WAS_HOME).
    
    WebSphere uses a variable called -Xshareclasses to modify JVM
    class sharing behavior.  The variable controlDir=${JVM_CACHE}
    is within the setting for -Xshareclasses to control the shared
    class cache directory.  When the ${JVM_CACHE} string isn't
    expanded in -Xshareclasses, the Java shared class directory is
    created in the user.dir/user.home directory instead of the
    WAS_HOME directory.
    
    If the -Xshareclasses variable is set incorrectly, many
    problems can happen.  For example, all your application
    servers might shut down randomly.
    

Local fix

  • LOCAL FIX FOR JVM ARGUMENTS:
    ============================
    1. Find your list of generic JVM arguments by using the steps
    in
    Setting generic JVM arguments in WebSphere Application Server,
    https://www.ibm.com/support/pages/node/397841.
    2. Search through the list of arguments to find any values that
    contain variables.
    - Variables start with ${ and $(.  For example, ${WAS_HOME} is
    a variable.
    3. Replace the variable with the value that would be replaced
    at
    run time.
    - For example, ${WAS_HOME} might be replaced with
    /WebSphere/ND/DeploymentManager
    4. Save your changes.
    5. Restart the server.
    
    LOCAL FIX FOR -Xshareclasses:
    ============================
    Although -Xshareclasses is technically a JVM argument, by
    default, it does not show up as a JVM argument in the
    administrative console.  To work around the variable
    replacement
    issue for -Xshareclasses, you can override its value by setting
    a new value as a generic JVM argument in the administrative
    console for the control and servant regions:
    For the control and servant regions, perform the following
    actions:
    1. Find your list of generic JVM arguments by using the steps
    in
    Setting generic JVM arguments in WebSphere Application Server,
    https://www.ibm.com/support/pages/node/397841.
    2. Set a new generic JVM agument as follows, replacing WAS_HOME
    with the path for your WebSphere home directory.
    - Control region:
    -
    Xshareclasses:name=webspherev80_%g_control,controlDir=WAS_HOME,g
    roupAccess,nonFatal
    - Servant region:
    -
    Xshareclasses:name=webspherev80_%g_servant,controlDir=WAS_HOME,g
    roupAccess,nonFatal
    Example:
    -
    Xshareclasses:name=webspherev80_%g_control,controlDir=/WebSphere
    /ND/DeploymentManager,groupAccess,nonFatal
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All z/OS users of IBM WebSphere             *
    *                  Application Server 9.0.5.15                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: In WebSphere Application Server for     *
    *                      z/OS 9.0.5.15, variables set as part of *
    *                      a                                       *
    *                      JVM generic argument are not expanded   *
    *                      in                                      *
    *                      the jvm.options files.                  *
    ****************************************************************
    * RECOMMENDATION:  Install a fix pack or interim fix that      *
    *                  contains this APAR.                         *
    ****************************************************************
    Because the risk to your systems is significant, IBM support
    strongly recommends that you install the interim fix.  However,
    you can perform the local fix steps in this section as a short-
    term solution:
    LOCAL FIX FOR JVM ARGUMENTS:
    ============================
    1. Find your list of generic JVM arguments by using the steps
    in
    Setting generic JVM arguments in WebSphere Application Server,
    https://www.ibm.com/support/pages/node/397841.
    2. Search through the list of arguments to find any values that
    contain variables.
    - Variables start with ${ and $(.  For example, ${WAS_HOME} is
    a variable.
    3. Replace the variable with the value that would be replaced
    at
    run time.
    - For example, ${WAS_HOME} might be replaced with
    /WebSphere/ND/DeploymentManager
    4. Save your changes.
    5. Restart the server.
    LOCAL FIX FOR -Xshareclasses:
    ============================
    Although -Xshareclasses is technically a JVM argument, by
    default, it does not show up as a JVM argument in the
    administrative console.  To work around the variable
    replacement
    issue for -Xshareclasses, you can override its value by setting
    a new value as a generic JVM argument in the administrative
    console for the control and servant regions:
    For the control and servant regions, perform the following
    actions:
    1. Find your list of generic JVM arguments by using the steps
    in
    Setting generic JVM arguments in WebSphere Application Server,
    https://www.ibm.com/support/pages/node/397841.
    2. Set a new generic JVM agument as follows, replacing WAS_HOME
    with the path for your WebSphere home directory.
    - Control region:
    -
    Xshareclasses:name=webspherev80_%g_control,controlDir=WAS_HOME,g
    roupAccess,nonFatal
    - Servant region:
    -
    Xshareclasses:name=webspherev80_%g_servant,controlDir=WAS_HOME,g
    roupAccess,nonFatal
    Example:
    -
    Xshareclasses:name=webspherev80_%g_control,controlDir=/WebSphere
    /ND/DeploymentManager,groupAccess,nonFatal
    

Problem conclusion

  • The WebSphere code is corrected to properly expand the ${ and $(
    values for the -X parameter in the options files.
    
    The fix for this APAR is targeted for inclusion in fix pack
    9.0.5.16. For more information, see 'Recommended
    Updates for WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH54585

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-05-17

  • Closed date

    2023-05-25

  • Last modified date

    2023-06-16

  • 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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

[{"Business Unit":{"code":"BU011","label":"Systems - zSystems software"},"Product":{"code":"SG19O","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"900"}]

Document Information

Modified date:
16 June 2023