IBM Support

PM47404: FIX INTERNAL FATAL ERROR (IXJXE0678E [ERR 0614]

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Under certain circustances stylesheet compilation could fail
    with the message
    
    FATAL ERROR: IXJXE0678E: [ERR 0614] The processor has
    encountered an internal error condition. Please report the
    problem and provide the following information: We shouldn't
    leave more than one item on the FCG codegen stack.
    
    This was due to an unexpected interaction of two optimizers.
    The compiler has been corrected, which should eliminate this
    error case and may produce slightly faster execution.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of the XML Feature Pack           *
    ****************************************************************
    * PROBLEM DESCRIPTION: Under certain circustances stylesheet   *
    *                      compilation could fail                  *
    *                      with the message                        *
    *                      FATAL ERROR: IXJXE0678E: [ERR 0614]     *
    *                      The processor has                       *
    *                      encountered an internal error           *
    *                      condition. Please report the            *
    *                      problem and provide the following       *
    *                      information: We shouldn't               *
    *                      leave more than one item on the FCG     *
    *                      codegen stack                           *
    ****************************************************************
    * RECOMMENDATION:  Install a fix pack that contains this       *
    *                  APAR.                                       *
    ****************************************************************
    This was due to an unexpected interaction of two optimizers --
    essentially, one failed to allow for the loop refactoring
    performed by the other. Since the number of arguments
    passed/returned was different in the two cases, this oversight
    resulted in a call being incompatible with the function it
    called, which we detected and reported when we started to
    convert the IL representation into executable code.
    

Problem conclusion

  • Repairing the optimizer resolved this problem.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM47404

  • Reported component name

    XML FEATUREPACK

  • Reported component ID

    5655N0256

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-09-08

  • Closed date

    2011-10-20

  • Last modified date

    2012-08-09

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

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

    PM47409

Fix information

  • Fixed component name

    XML FEATUREPACK

  • Fixed component ID

    5655N0256

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
09 August 2012