IBM Support

PM64433: RUNTIME TAB FOR LOGS IN CONSOLE SHOW INCORRECT INFORMATION WHEN USING CLUSTER LEVEL VARIABLES.

Fixes are available

7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When using cluster level variables to create the path for
    systemout and systemerror logs, the Runtime tab/panel of the ISC
    shows an incorrect status of the servers and disables the
    option to "View" the logs.
    
    Example: $(ROOT)/$(CLUSTER)/SystemOut.log
    
    This is due to the underlying utility used by some console
    panels to do variable translation not taking into account
    cluster level variables.
    

Local fix

  • No workaround exists
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0, V8.0 and V8.5 administrative   *
    *                  console panels for retrieving and viewing   *
    *                  logs.                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: Retrieval/viewing of server log files   *
    *                      from the administrative console fails   *
    *                      when the file path contains cluster     *
    *                      level websphere variables               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The administrative console panel for displaying logs use a
    workspace utility to expand path variables. The utility did not
    correctly handle variables defined at the cluster level.
    

Problem conclusion

  • WebSphere Application Server code was changed so that cluster
    variables used in log file paths in the administrative console
    are handled correctly.
    
    To avoid an unexpected change in behavior, the change must be
    enabled with a system property. To enable the new behavior the
    system property
    
    com.ibm.websphere.workspace.decodeclustervariable=true
    
    must be set in the deployment manager, and the deployment
    manager restarted.
    
    The property can be set in the dmgr console at the
    following panel:
    
    System Administration > Deployment manager > Java and Process
    Management > Process definition > Java virtual machine > Custom
    properties
    
    APAR PM64433 requires a change to documentation.
    
    NOTE: Periodically, we refresh the documentation on our Web
    site, so the changes might have been made before you read this
    text. To access the latest on-line documentation, go to the
    product library page at:
    
    http://www.ibm.com/software/webservers/appserv/library
    
    The following changes to the WebSphere Application Server
    Version 7.0 Information Center will be made available in
    September, 2012.
    
    The following description of the
    com.ibm.websphere.workspace.decodeclustervariable custom
    property, that is included in the topic "Java virtual machine
    custom properties":
    
    com.ibm.websphere.workspace.decodeclustervariable
    
    Use this property to ensure that  variables defined at a
    cluster scope are  expanded when they occur in log file paths
    defined in the administrative console. If the  property is not
    set, and cluster scoped variables are used to define log file
    paths, then the deployment manager may fail to retrieve the
    requested log file. Therefore, you should add this property to
    your deployment manager JVM settings if you include cluster
    scoped variables in your log file paths.
    The default value for this custom property is false.
    If you decide to use this custom property, you must specify it
    as a deployment manager JVM custom property. After you set
    this property to true, you must restart the deployment manager
    before this configuration change goes into effect.
    
    APAR PM64433 is currently targeted for inclusion in WebSphere
    Application Server Fix Packs 7.0.0.25, 8.0.0.5, and 8.5.0.1.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

  • Define path in the console without reference to cluster
    scoped varaibels.
    

Comments

APAR Information

  • APAR number

    PM64433

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-05-11

  • Closed date

    2012-07-10

  • Last modified date

    2012-11-02

  • 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

  • R700 PSY UK81738

       UP12/10/04 P F210

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.



Document information

More support for: WebSphere Application Server for z/OS
General

Software version: 7.0

Reference #: PM64433

Modified date: 02 November 2012