IBM Support

JR49074: UCA DEFINITION WITH DUPLICATED PARAMETER MAPPING FAILS TO UPDATE VARIABLES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • During creation and modification of a UCA the XML definition of
    the parameters may become duplicated. For variables to be
    properly transported by the UCA, there must be a unique name
    for each mapped variable.
    
    Scenario from Developer/User's perspective.
    When a start message event (SME) or intermediate message event
    (IME) is processed, one of the variables in the receiving BPD
    is empty or is not updated to a new value.
    
    Confirming problem:
    Unzipping the application export (TWX) locate the UCA
    definition by searching (grep) through the files for the name
    of the UCA. Find the file with the UCA definition. The file
    will not have a formal extension, it will be in this format
    
    4. <UUID>  where <UUID> is the uniquely generated ID for this
    object.  This file is an XML document
    
    To confirm this is the correct file, the name of the UCA will
    appear in the 3rd line of the file. See this example.
    
    <underCoverAgent id="4.7ee3408c-ce80-4ea9-b8cf-a9416661f4c4"
    name="UCA - reset data 2">
    
    Every mapped variable in the UCA will start with be in this XML
    block.
    
    <parameterMapping name="instanceID">
    
    
    If there are two occurences of the same <parameterMapping> for
    the same variable, the UCA cannot carry the variable data to the
    IME or SME.
    

Local fix

  • none, iFix is required
    

Problem summary

  • Sometimes (in specific applications on some systems) not all
    data transported by a message via a message UCA are delivered
    to the target BPD.
    
    PROBLEM DETAILED DESCRIPTION:
    In the trace, the following string can be seen: "Not assigning
    value of output parameter name = <mappingName> as no target
    variable has been specified" In addition, in the associated twx
    multiple mapping definitions exist for name '<mappingName>'.
    The reason for this problem is that resolution of mapping based
    on names fails if multiple mappings with the same name exist.
    

Problem conclusion

  • Perform the output mapping of an inbound message event based on
    parameter Ids.
    
    FIX AVAILABILITY:
    iFix for 8.0.0.0 is/will be available on Fix Central; search
    for APAR JR49074 at http://www.ibm.com/support/fixcentral/
    iFix for 8.0.1.1 is/will be available on Fix Central; search for
    APAR JR49074 at http://www.ibm.com/support/fixcentral/
    iFix for 8.0.1.2 is/will be available on Fix Central; search for
    APAR JR49074 at http://www.ibm.com/support/fixcentral/
    iFix for 8.5.0.1 is/will be available on Fix Central; search for
    APAR JR49074 at http://www.ibm.com/support/fixcentral/
    Fix is also targetted for inclusion in next fixpack for
    BPM 8.0.1
    
    When obtaining any of the above fixes, be sure to download the
    accompanying readme, for itself, and any prerequisite fixes, and
    review them thoroughly.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR49074

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-01-16

  • Closed date

    2014-03-13

  • Last modified date

    2014-03-13

  • 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

    BPM STANDARD

  • Fixed component ID

    5725C9500

Applicable component levels

  • R800 PSY

       UP

  • R801 PSY

       UP

  • R850 PSY

       UP

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

Document Information

Modified date:
13 March 2014