IBM Support

IT36971: SYNTAX TOKEN IN .MXL MAP GETS CORRUPTED AFTER DISTINCT SET OF CLICKS IN MAP

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

  • Specific sequence of mouse-click actions corrupts syntax token
    Simulation Steps:
    Below are the steps to reproduce:
    Open map editor and the map in question.
    Open syntax tokens to validate it shows 0x01 and 0xFF for syntax
    token X.
    Open field properties of any field and just click on all tabs
    from
    right to left and click ok and close the field properties
    window.
    Then save the map and close the map tool fully.
    Restart the map tool and open the map again and open syntax
    token X you will see 0 in place of 0x01 .
    Supporting Documentation/Asset Location:
    Customer attached a map and recording of duplication to SF
    TS003700752
    Observations:
    Reproduced and it appears to only happen with .mxl
    They replaced rather than added to the range in X syntax token
    Expected Behavior:
    Syntax tokens should remain unchanged when not changing anything
    in syntax token editor
    Business Impact:
    Specific and probably unlikely series of steps will cause the
    map to fail if syntax tokens are no longer encompassing
    characters used.
    

Local fix

  • STRRTC - B2BISFG-53707
    OAQ/ OAQ
    Circumvention: Save the map in map format instead of mxl format.
    

Problem summary

  •   Problem Description:
    
    Specific sequence of mouse-click actions corrupts the syntax
    token.
    
    
    
    Simulation Steps:
    
    Below are the steps to reproduce:
    
    Open map editor and the map in question.
    
    Open syntax tokens to validate it shows 0x01 and 0xFF for syntax
    token X.
    
    Open field properties of any field and click on all tabs from
    right to left and click ok. Close the field properties window.
    
    Save the map and close the map tool fully.
    
    Restart the map tool and open the map again and open syntax
    token X and you will see 0 in place of 0x01.
    
    
    
    Observations:
    
    It happens with .mxl only.
    
    They replaced rather than added to the range in X syntax token.
    
    
    
    Expected Behavior:
    
    Syntax tokens should remain unchanged when not changing anything
    in the syntax token editor.
    
    
    
    Business Impact:
    
    Specific and unlikely series of steps will cause the map to fail
    if syntax tokens are no longer encompassing the characters used.
    
    
    
    Platforms Affected:
    
    All Platforms
    
    
    
    Users Affected:
    
    All customers using B2BI Map Editor.
    

Problem conclusion

  •   Resolution Summary:
    
    The behavior is now corrected. Syntax token for a non printable
    character will be saved and it will load correctly in the Map
    Editor.
    
    A code fix is provided.
    
    
    
    Delivered in:
    
    6000007
    

Temporary fix

  •    No workaround
    

Comments

APAR Information

  • APAR number

    IT36971

  • Reported component name

    STR B2B INTEGRA

  • Reported component ID

    5725D0600

  • Reported release

    600

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-05-20

  • Closed date

    2021-07-29

  • Last modified date

    2021-07-29

  • 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

    STR B2B INTEGRA

  • Fixed component ID

    5725D0600

Applicable component levels

[{"Line of Business":{"code":"LOB02","label":"AI Applications"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JSW","label":"Sterling B2B Integrator"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"600"}]

Document Information

Modified date:
30 July 2021