IBM Support

IC96979: VARIABLE EXPRESSIONS IN THE WMQ FTE MONITOR TRANSFER DOCUMENT ARE NOT EXPANDED CORRECTLY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The WebSphere MQ File Transfer Edition 'fteCreateMonitor'
    command has an optional parameter '-mt' which specifies the
    name of the XML document that contains the task definition
    when the trigger condition is met. Variable expressions in this
    task definition XML document do not translate correctly. This
    results in the following error "BFGRP0034I: The file transfer
    request has completed with no files being transferred."
    

Local fix

  • None,
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of WebSphere MQ File Transfer Edition
    and Managed File Transfer, who are using a Resource Monitor,
    with a task transfer XML document that contains variables
    which are to be substituted with their associated values once
    the trigger condition(s) of the Resource Monitor are satisfied.
    
    
    Platforms affected:
    AIX, HP-UX Itanium, HP-UX PA-RISC, IBM iSeries, Linux on
    Power, Linux on S390, Linux on x86, Linux on x86-64, Linux on
    zSeries, Solaris SPARC, Solaris x86-64, Windows, z/OS,
    MultiPlatform
    
    ****************************************************************
    PROBLEM SUMMARY:
    When creating a WebSphere MQ File Transfer Edition / Managed
    File Transfer 'Resource Monitor', a task document is supplied,
    which provides details of the intended task to execute when
    the resource monitor's trigger condition is met.
    
    For example, you might use the command line syntax:
    
    fteCreateMonitor -mt transferRequest.xml -ma AGENT1 -mn MONITOR1
    -md /home/userID/wmqfte/triggerdir -tr "match,*" -pi 10 -pu
    seconds
    
    which creates a monitor called "MONITOR1" for the agent
    "AGENT1", to be triggered whenever a file appears in the
    directory:
    
      /home/userID/wmqfte/triggerdir
    
    
    Within the monitor transfer document, "transferRequest.xml" in
    the above example, you can define values using variable names,
    such as:
    
      ${fileName} -- The name of the trigger file
      ${filePath} -- The full path name of the trigger file
    
    When the monitor is triggered and the defined task begins, the
    source agent substitutes these variables with values based on
    the trigger file.
    
    
    A defect in the variable substitution parser resulted in these
    variables not being correctly substituted, which would result in
    the variable names themselves being included in the task XML
    message produced and submitted to the agent. This situation
    would likely result in a failure to run the defined task,
    e.g., a file transfer, depending on the specific string which
    was used in the transfer document.
    
    APAR IC82765 (included in WebSphere MQ File Transfer Edition
    7.0.4.2 and WebSphere MQ Managed File Transfer 7.5.0.1)
    attempted to correct this problem, but in doing so introduced
    a new issue where the variable would be expanded, but may have
    had an extension of the XML element appended to the string.
    
    For example, if your monitor transfer document contained the
    elements:
    
    
    
    
    
              /a/dir/${FilePath{token=2}}/${fileName}
    
    
    
    
    
    and the trigger file had the filename:
    
      /some/location/filename.zip
    
    the following might be transmitted to the destination agent to
    process:
    
    
    
    
    
              /a/dir/location//${file${fileName}
    
    
    
    
    
    which would likely lead to a transfer failure, if a file could
    not be created on the destination filesystem with the literal
    name:
    
    "/a/dir/location//${file${fileName}"
    

Problem conclusion

  • The internal XML DOM object used to encapsulate the data in
    transfer document has been modified to prevent the problem
    from occurring.
    
    Note that while the above example referenced the ${fileName} and
    ${filePath} variables, the problem could affect any variable
    which is expanded in the monitor transfer document.
    
    
    | MDVPARTL 7.0.4-WS-MQFTE-JavaVM-FP002-Windows_x86 |
    | MDVPARTL 7.0.4-WS-MQFTE-JavaVM-FP002-Solaris_x86 |
    | MDVPARTL 7.0.4-WS-MQFTE-JavaVM-FP002-Solaris_SPARC |
    | MDVPARTL 7.0.4-WS-MQFTE-JavaVM-FP002-Linux64_SystemP |
    | MDVPARTL 7.0.4-WS-MQFTE-JavaVM-FP002-Linux_x86 |
    | MDVPARTL 7.0.4-WS-MQFTE-JavaVM-FP002-Linux_SystemZ |
    | MDVPARTL 7.0.4-WS-MQFTE-JavaVM-FP002-IBMi |
    | MDVPARTL 7.0.4-WS-MQFTE-JavaVM-FP002-HPUX_PARISC |
    | MDVPARTL 7.0.4-WS-MQFTE-JavaVM-FP002-HPUX_IA64 |
    | MDVPARTL 7.0.4-WS-MQFTE-JavaVM-FP002-AIX_ppc |
    
    | MDVPARTL 7.0.4-WS-MQFTE-JavaVM-FP003-Windows_x86 |
    | MDVPARTL 7.0.4-WS-MQFTE-JavaVM-FP003-Solaris_x86 |
    | MDVPARTL 7.0.4-WS-MQFTE-JavaVM-FP003-Solaris_SPARC |
    | MDVPARTL 7.0.4-WS-MQFTE-JavaVM-FP003-Linux64_SystemP |
    | MDVPARTL 7.0.4-WS-MQFTE-JavaVM-FP003-Linux_x86 |
    | MDVPARTL 7.0.4-WS-MQFTE-JavaVM-FP003-Linux_SystemZ |
    | MDVPARTL 7.0.4-WS-MQFTE-JavaVM-FP003-IBMi |
    | MDVPARTL 7.0.4-WS-MQFTE-JavaVM-FP003-HPUX_PARISC |
    | MDVPARTL 7.0.4-WS-MQFTE-JavaVM-FP003-HPUX_IA64 |
    | MDVPARTL 7.0.4-WS-MQFTE-JavaVM-FP003-AIX_ppc |
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.4.4
    v7.5       7.5.0.3
    
    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

    IC96979

  • Reported component name

    WMQ FILE TRANSF

  • Reported component ID

    5724R1000

  • Reported release

    704

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-10-17

  • Closed date

    2013-12-16

  • Last modified date

    2013-12-16

  • 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

    WMQ FILE TRANSF

  • Fixed component ID

    5724R1000

Applicable component levels

  • R704 PSY

       UP

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

Document Information

Modified date:
16 December 2013