IBM Support

JR46823: IF YOU HAVE A VARIABLE MARKED AS TRACKED VARIABLE AND YOU USE THIS VARIABLE IN MAPPING IN LINKED PROCESS YOU WILL GET AN ERR

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Prerequisites for the issue reported here is:
    - process A has a variable Z
    - variable Z is marked to be tracked
    - process A calls process B as 'linked process'
    - auto-tracking is enabled
    For each activity in process B, all variables that should be
    tracked are evaluated. In the current implementation, all
    tracked variables from process B and process A are found and
    are evaluated for tracking. Activities in process B cannot
    access the variables from process A, therefore the exception
    happens. The current code already tries to suppress any errors
    thrown during evaluation, but this does not work in all cases.
    The correct fix for this issue is to not try to evaluate
    process A's tracked variables at all - they are not accessible
    from process B.
    000000ea wle           E   CWLLG2015E:  An unexpected runtime
    exception  occurred. See exception for more details.  Error:
    Undeclared local variable, input or output parameter
    variableTracked found in service
    "Sub BPD" item "UNKNOWN" location "UNKNOWN". You must declare
    it in order to use it..
    com.lombardisoftware.server.core.UndeclaredVariableRuntimeExcept
    ion:
    Undeclared local variable, input or output parameter
    variableTracked found in service "Sub BPD" item "UNKNOWN"
    location "UNKNOWN". You must declare it in order to use it.
     at
    com.lombardisoftware.bpd.runtime.engine.st.AbstractBPDSymbolTabl
    e.get(Ab
    stractBPDSymbolTable.java:128)
     at
    com.lombardisoftware.bpd.runtime.engine.js.AbstractBPDSymbolTabl
    eScripta
    ble.get(AbstractBPDSymbolTableScriptable.java:55)
    The exception the customer sees is polluting the system log
    file, but does not harm BPM processing.
    

Local fix

  • N/A
    

Problem summary

  • Problem Summary:
    For each activity in the linked process, all variables
    marked for tracking of the linked process and the calling
    process
    are evaluated. From a linked process, variables of the calling
    process are not available. Therefore, the evaluation fails.
    

Problem conclusion

  • Problem Conclusion:
    The interim fix will only search for tracked variables within
    the boundary of the current linked process. This avoids error
    messages written out to the system out log file.
    
    iFix available on top of V8011
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR46823

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-06-03

  • Closed date

    2013-08-12

  • Last modified date

    2013-08-12

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

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

    JR46830

Fix information

  • Fixed component name

    BPM ADVANCED

  • Fixed component ID

    5725C9400

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
12 August 2013