IBM Support

PH32886: INCORRECT VARIABLE DEFINITION LEADS TO FAILURE IN TRANSFORMER SCRIPT

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

  • When a variable is defined that points to itself (ie. recursive
    variable), it results in the transformer script failure -
    wc2n.sh (z/OS only). Any subsequent synchronization attempts
    will show synchronization was successful, but in fact
    transformer script continues to fail without updating was.env
    and *jvm.options files for all the servers in node, even if the
    bad definition was at a server level.
    
    Example of the recursive variable:
    DB2UNIVERSAL_JDBC_DRIVER_NATIVEPATH=${DB2UNIVERSAL_JDBC
    _DRIVER_NATIVEPATH}
    Once the variable was set to a different
    value (not to point to itself), the issue was resolved and all
    was.env files were updated.
    
    The only error issued is StackOverFlowError shown below. There
    is no message to say what caused it or which file had an issue
    during transformation. A message saying synchronization was
    successful is still issued. On subsequent restarts, there is
    just an FFDC log issued making it hard to notice the exception.
    
    The goal of this APAR is to improve the error reporting. End
    user will still need to fix the variable definition in order to
    resolve the problem.
    
    With the APAR on, WAS will catch the StackOverFlowError and
    issue an new error to end user during sync and fail the sync
    operation with error showing the file being processed.
    
    BOJ0060E: Transformer Exception: java.lang.StackOverflowError
    .management.util.zos.gate.RepositoryImpl.fullTransform(Repositor
    yImpl.java:975)
    .management.util.zos.Config2Native.transform(Config2Native.java:
    207)
    .management.util.zos.Config2Native.transform(Config2Native.java:
    182)
    .management.util.zos.ZOSConfigRepositoryListener.handleNotificat
    ion(ZOSConfigRep
    ...
    

Local fix

  • Remove or update the variable that is pointing to itself. Save
    and Synchronize the node.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of Z/OS IBM WebSphere Application *
    *                  Server V8.5 and V9.                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: When a variable is defined that         *
    *                      points to itself it will lead to        *
    *                      StackOverflowError being logged to      *
    *                      FFDC. Synchronization was               *
    *                      successful but nodeagent will not       *
    *                      start.                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a variable is defined that points to itself it will lead
    to StackOverflowError being logged to FFDC. Synchronization was
    successful but nodeagent will not start.
    FFDC log show: BOJ0060E: Transformer Exception:
    java.lang.StackOverflowError
    .management.util.zos.gate.RepositoryImpl.fullTransform(Repositor
    yImpl.java:975)
    .management.util.zos.Config2Native.transform(Config2Native.java:
    207)
    .management.util.zos.Config2Native.transform(Config2Native.java:
    182)
    .management.util.zos.ZOSConfigRepositoryListener.handleNotificat
    ion(ZOSConfigRep....
    

Problem conclusion

  • The code is modified to throw exception during syncNode and
    also to show the problem file being transformed.
    The fix for this APAR is targeted for inclusion in fix pack
    8.5.5.20 and 9.0.5.8.
    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

    PH32886

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-12-21

  • Closed date

    2021-02-12

  • Last modified date

    2021-02-12

  • 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

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850"}]

Document Information

Modified date:
14 February 2021