IBM Support

IT17558: CreateDate within a queue statistics PCF messages has wrong day of month and has two unwanted characters at the end

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

  • When using TEXT or BINARY file to message transfer, the
    destination agent is expected to put a zero byte message to the
    destination queue if the transfer fails for some reason. If
    BINARY transfer mode is used, a zero byte message gets put into
    the destination queue to indicate a failed transfer however this
    does not happen if TEXT transfer mode is used.
    
    Sequence of the event:
    	Start file to message transfer
    	Agent is stopped while transfer is in progress
    	Restart sending agent
    	Transfer fails unexpectedly (e.g missing source file).
    	If the transfer is a binary transfer then a blank message
    is written to the destination queue
    	If the transfer is a text transfer then no blank message is
    written to the destination queue
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of:
    
    - WebSphere MQ File Transfer Edition V7.0.4
    - The MQ v7.5.0 Managed File Transfer component.
    - The MQ v8.0.0 Managed File Transfer component.
    - The MQ v9.0.0 Managed File Transfer component.
    
    who perform file to message transfer with text mode.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When using File to Message conversion with transfer mode as
    either TEXT or BINARY, the destination agent was expected to put
    a zero byte message to the destination queue if the transfer
    failed for some reason. If BINARY transfer mode was used, a zero
    byte message was put to the destination queue to indicate a
    failed transfer - however this did not happen if TEXT transfer
    mode was used due to a missing checkpoint .
    

Problem conclusion

  • The WebSphere MQ File Transfer Edition product, and the MQ
    Managed File Transfer component, have been updated such that a
    checkpoint is always added for both text and binary file to
    message transfers. This means that that if the transfer fails
    unexpectedly, the destination agent puts a zero byte message to
    the destination queue to indicate a failed transfer.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.4.7
    v7.5       7.5.0.8
    v8.0       8.0.0.6
    v9.0 CD    9.0.2
    v9.0 LTS   9.0.0.1
    
    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

    IT17558

  • Reported component name

    WMQ FILE TRANSF

  • Reported component ID

    5724R1000

  • Reported release

    704

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-10-18

  • Closed date

    2016-11-26

  • Last modified date

    2017-06-01

  • 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:
01 June 2017