IBM Support

PH19287: EXCESSIVE TRACING WITH POSTUPGRADETRACE=0 AND PREUPGRADETRACE=0

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

  • Setting postUpGradeTrace=0 and preUpGradeTrace=0 should disable
    tracing, but it does not. The resulting WASPreUpgradeTrace and
    WASPostUpgradeTrace files are created as if full tracing was
    enabled.
    

Local fix

  • 1. Run BBOWMPRO job first. It copies the bbomigrt2.sh from the
    read-only filesystem to the migration temp directory. This
    should be a copy of the file, not a symlink to the read-only
    filesystem.
    2. Edit the lines in the bbomigrt2.sh script and
    replace
    traceparms=" -traceString *=all=off -traceFile
    ${postTraceFileName} "
    with
    traceparms=" -traceString *=all=disabled -tracefile
    ${postTraceFileName} "
    
    3. Run BBOWMPRE and BBOWMPOS
    
    
    Replacing "off" with "disabled" will turn off tracing.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V9.0 Migration Tools for z/OS        *
    ****************************************************************
    * PROBLEM DESCRIPTION: Migration jobs generate trace despite   *
    *                      trace being set to 'Off' or '0' in      *
    *                      response file                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The trace string provided to WASPreUpgrade and WASPostUpgrade
    when a value of 0 is specified for the 'preUpgradeTrace' or
    'postUpgradeTrace' values of the EV dataset is incorrect. It
    specifies *=all=off when it should specify *=all=disabled.
    

Problem conclusion

Temporary fix

  • Manually patch bbomigrt2.sh to adjust the value of traceString
    to include '*=all=disabled' instead of '*=all=off'
    

Comments

APAR Information

  • APAR number

    PH19287

  • 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

    2019-11-15

  • Closed date

    2020-01-07

  • Last modified date

    2020-01-07

  • 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":"BU048","label":"IBM Software"},"Product":{"code":"SSCWL8S","label":"General"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
07 January 2020