IBM Support

PM31037: MAP FAILS TO LOAD FROM CORRECT LOCATION AFTER BAILING DUE TO XDS AMBIGUITY CONDITION IS ENCOUNTERED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A map fails to load with the error "Map does not exist (3)",
    return code 3, due to the map being loaded from an incorrect
    location with the after "Bailing due to XDS ambiguity / unknown
    type for map" condition is encountered.  The "Use map from
    project" subdirectory is incorrectly added before the map name
    when the "Use external map" is defined for the WTX Map node.
    
    
    An error similar to the folloiwng is observed:
    Jan 17 16:09:39 xxxx user:info WebSphere Broker v6105...
    [6449]BIP2176S: Could not find message
    1001 in catalogue txmsgv82.cat, inserts are Bailing due to XDS
    ambiguity / unknown type for map
    /path_to_map/mymap.mmc,
    instance 1 -- restarting without XDS {1} {2} {3} {4} {5} {6}:
    ESBBQ2.572d6c33-2d01-0000-0080-e0c430b62ee0: TXInterface.cpp:
    1020: RESTART: :
    
    Jan 17 16:09:39 xxx user:info WebSphere Broker v6105...
    [6449]BIP2176S: Could not find message
    1003 in catalogue txmsgv82.cat, inserts are Map status for
    /path_to_map/a_BE/mymap.mmc, Map
    does not exist (3).  Confirm map was deployed correctly. {1} {2}
    {3} {4} {5} {6}: ESBBQ2.572d6c33-2d01-0000-0080-e0c430b62ee0:
    TXInterface.cpp: 597: _LoadMapTX:
    
    In the above you will notice that the map path is correct, but
    once it restarts, a_BE was added to the path name.  In place of
    a_BE, you could also see a_LE or e_BE
    

Local fix

  • WTXCQ - WTX00036616
    TR / TR
    Circumvention: None
    

Problem summary

  • Users Affected:
    WebSphere Transformation Extender customers using WMB XMLNS
    domain (XDS4C parsing) with external map and the map fails in
    XDS4C causing it to restart
    
    
    Problem Description:
    When bailing in XDS4C, and doing a restart, the code to load the
    map was forcing the map to be a "memory" map, so it would append
    the platform directory to the path.
    
    Platforms Affected:
    All
    

Problem conclusion

  • Modified code to pass in to RunTX whether or not the map is a
    "memory" map (map in project).
    
    Delivered in:
    8.2.0.6, 8.3.0.4
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM31037

  • Reported component name

    WTX FOR INT SER

  • Reported component ID

    5724M4010

  • Reported release

    820

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2011-01-24

  • Closed date

    2011-02-22

  • Last modified date

    2011-04-22

  • 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

    WTX FOR INT SER

  • Fixed component ID

    5724M4010

Applicable component levels

  • R820 PSY

       UP

  • R830 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCKRDT","label":"WTX for Integration Servers"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
22 April 2011