IBM Support

IT23459: MQ Explorer incorrectly saves property value for MFT ant script invocation when value ends in a backslash

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

  • Through the MQ Explorer GUI, the user sets up a Managed File
    Transfer transfer and adds a Program Invocation in the
    additional options of the transfer. If the user selects 'Ant
    Script' from the drop-down menu and attempts to supply a value
    for a property within the ant script that ends in a backslash,
    then the value is incorrectly interpreted. The ending backslash
    is removed, and if there is a following property/value entry in
    the properties table, this row is appended to the value that had
    the trailing backslash.
    
    For example, if the following property/value entries were added:
    
    	property1 = value1\
    	property2 = value2
    
    then the backslash would be removed and the next property/value
    entry in the properties table would be appended to the end of
    the value, so the properties table would change to the
    following:
    
    	property1 = value1, property2 = value2
    	property2 = value2
    
    
    Additionally, the presence of successive backslashes in a value
    would result in some of the backslashes being removed when
    interpreted by the MQ Explorer.
    
    If a value contains more than 1 backslash in succession, then
    backslashes are removed in the following way:
    
    	\		becomes		\
    	\\		becomes		\
    	\\\	becomes		\\
    	\\\\	becomes		\\
    	\\\\\	becomes		\\\  etc.
    
    following the pattern: y = floor ( ( x + 1 ) / 2 ), where x is
    the actual number of backslashes entered and y is the
    interpreted number of backslashes. This change also happens each
    time the user opens the configuration window after setting the
    properties.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This APAR affects users of the:
    
      - IBM MQ v8 Explorer Managed File Transfer plug-in
      - IBM MQ v9 Explorer Managed File Transfer plug-in
    
    who specify Ant Script program invocations when configuring a
    transfer, where any of the supplied property values either
    contain successive backslashes or end in a backslash.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The WebSphere MQ Explorer Managed File Transfer plug-in did not
    properly escape backslashes that were specified as a value for
    properties supplied to an Ant Script, which is set as a Program
    Invocation when creating a transfer. Therefore, if a value ended
    in a backslash, then the value would be interpreted incorrectly.
    For example, if the following values were entered:
    
    	property1 = value1\
    	property2 = value2
    		
    then the backslash would be removed and the next property/value
    entry in the properties table would be appended to the end of
    the value
    		
    	property1 = value1, property2 = value2
    	property2 = value2
    		
    If there was no following property in the properties table then
    the configuration for the program invocation is deleted.
    		
    The presence of successive backslashes in a value would result
    in some of the backslashes being removed when interpreted by the
    MQ Explorer.
    
    This change also happens each time the user opens the
    configuration window after setting the properties.
    

Problem conclusion

  • The WebSphere MQ Explorer Managed File Transfer plug-in has been
    updated so that backslashes are properly escaped within the
    program invocation configuration for Ant Scripts.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.9
    v9.0 LTS   9.0.0.4
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT23459

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-12-12

  • Closed date

    2018-01-29

  • Last modified date

    2018-01-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

    IBM MQ BASE MP

  • Fixed component ID

    5724H7251

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.0.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
29 January 2018