IBM Support

IT09433: MQ MANAGED FILE TRANSFER TRACE GENERATES UNWANTED TRACE POINTS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When WebSphere MQ Managed File Transfer trace has been
    enabled using, for example, the trace string:
    
     trace=com.ibm.wmqfte.bridge.session.
    
     then the trace file which is generated should only contain
    trace points from the package:
     "com.ibm.wmqfte.bridge.session", but the resultant trace
    output contain trace information generated by other packages
     as well, for example, com.ibm.mq.exits and
     com.ibm.mq.ese which are not specified in the trace
    specification.
    
    Additional Symptom(s) Search Keyword(s): MQMFT; Trace
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of:
    
    - The WebSphere MQ V7.5 Managed File Transfer component.
    - The IBM MQ V8 Managed File Transfer component.
    
    who are asked to collect a WebSphere MQ Managed File Transfer
    trace by IBM Support.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    This APAR addresses two issues:
    
    Issue 1:
    --------------
    The trace mechanism provided by the WebSphere MQ Managed File
    Transfer and IBM MQ Managed File Transfer components allows
    users to specify a trace specification containing the internal
    packages and/or classes that will be traced. For example, to
    trace the interactions between a Protocol Bridge Agent and an
    FTP Server, the trace specification:
    
    com.ibm.wmqfte.bridge.session.ftp=all
    
    can be used.
    
    However, a problem with the trace mechanism meant that trace
    files always contained trace points from the classes in the
    package:
    
    - com.ibm.mq.exits
    
    even if that package was not covered by the trace specification.
    
    Issue 2:
    --------------
    If the WebSphere MQ Managed File Transfer or IBM MQ Managed File
    Transfer components were being used on an installation that also
    had access to the Advanced Message Security (AMS) component,
    then the WebSphere MQ Managed File Transfer and IBM MQ Managed
    File Transfer trace mechanism would incorrectly trace entry and
    exit trace points from classes within the package:
    
    - com.ibm.mq.ese
    
    even if the trace specification did not include that package.
    
    Issue 3:
    --------------
    Enabling a trace a Protocol Bridge Agent using a trace
    specification that incorporates the either of the classes shown
    below:
    
    com.ibm.wmqfte.bridge.session.ftp.FTPSession
    com.ibm.wmqfte.bridge.session.ftp.FTPSSession
    
    ensures that the trace file contains details of all of the FTP
    commands sent to, and the replies received from, a FTP Server.
    Some examples of these trace points are shown below:
    
    c.i.w.b.session.ftp.FTPSession$EventTrace ----+----+---- d
    protocolReplyReceived data
    [[FILE]PB-FTP-RX : 220 ProFTPD 1.3.4c.15 Server (FTP Service) []
    c.i.w.b.session.ftp.FTPSession$EventTrace ----+----+---- d
    protocolCommandSent data
    [[FILE]PB-FTP-TX : USER user1
    c.i.w.b.session.ftp.FTPSession$EventTrace ----+----+---- d
    protocolReplyReceived data
    [[FILE]PB-FTP-RX : 331 Password required for user1
    c.i.w.b.session.ftp.FTPSession$EventTrace ----+----+---- d
    protocolCommandSent data
    [[FILE]PB-FTP-TX : PASS *****
    c.i.w.b.session.ftp.FTPSession$EventTrace ----+----+---- d
    protocolReplyReceived data
    [[FILE]PB-FTP-RX : 230 User user1 logged in
    
    It was not possible to trace the FTP commands sent to, and the
    FTP responses received from, an FTP Server without tracing the
    rest of the FTPSession or FTPSSession class.
    

Problem conclusion

  • The following changes have been made to the trace mechanism used
    by the WebSphere MQ V7.5 Managed File Transfer and IBM MQ V8.0
    Managed File Transfer components:
    
    Change 1:
    --------------
    Trace information from the classes in the package:
    
    - com.ibm.mq.exits
    
    is now only written to a trace file if the trace specification
    includes the entry:
    
    com.ibm.mq.
    
    
    Change 2:
    --------------
    Trace files will only contain entry and exit trace points from
    the classes in the package
    
    - com.ibm.mq.ese
    
    if the trace specification includes the entry:
    
    com.ibm.mq
    
    
    Change 3:
    --------------
    The ability to just trace the the FTP commands sent to, and the
    replies received from, a FTP Server has now been added. To do
    this, the following trace specification should be used:
    
    com.ibm.wmqfte.bridge.session.ftp.EventTrace=moderate
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.5       7.5.0.6
    v8.0       8.0.0.4
    
    The latest available FTE maintenance can be obtained from
    'Fix List for WebSphere MQ File Transfer Edition 7.0'
    http://www-01.ibm.com/support/docview.wss?uid=swg27015313
    
    The latest available MQ 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

    IT09433

  • Reported component name

    WMQ MFT

  • Reported component ID

    5724H7242

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-06-11

  • Closed date

    2015-09-24

  • Last modified date

    2015-09-24

  • 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 MFT

  • Fixed component ID

    5724H7242

Applicable component levels

  • R750 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSCUHLE","label":"WMQ Managed File Transfer"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
24 September 2015