IBM Support

IT19996: IBM MQ MFT: UPDATE INTERNAL VALUES FOR VRMF TO ALLOW FOR DOUBLE DIGIT FIX PACKS

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

  • IBM MQ Managed File Transfer stores an internal representation
    of its version using single digit for each of the version,
    release, modification and fix pack (VRMF) fields.
    
    If fix pack ten is reached, a single digit will be insufficient
    to hold the two digit fix pack value.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of IBM MQ Managed File Transfer.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    IBM MQ Managed File Transfer holds an internal representation of
    its version number.  This is stored using a single digit for
    each of the version, release, modification and fix pack (VRMF)
    fields.  For example IBM MQ version 9.0.0.1 is represented as
    the integer 9001.
    
    If fix pack number 10 is reached, a single digit would be
    insufficient to hold the two digit fix pack version number.
    
    In earlier releases, such as IBM MQ v8, both the modification
    and fix pack fields can be used to cater for fix packs 10 and
    later.  There is no IBM MQ 8.0.1 for example, so 8010 could be
    used to represent Fix Pack 8.0.0.10. as this value is greater
    than 8009 which would represent 8.0.0.9.
    
    Since the release of IBM MQ 9.0 CDR, which has version numbers
    similar to 9.0.1 and 9.0.2, the third digit is no longer
    available for use for the Fix Pack version.  There is no way to
    differentiate in the internal VRMF representation between IBM MQ
    MFT 9.0.0.10 and IBM MQ CDR 9.0.1.0 as both would be 9010.
    

Problem conclusion

  • The code has been updated to use two digits per version field.
    
    For example, 9.0.0.1 is represented as 09000001, and a 9.0.0.10
    fix pack would be represented as 09000010.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    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

    IT19996

  • Reported component name

    IBM MQ MFT V9.0

  • Reported component ID

    5724H7262

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-03-31

  • Closed date

    2017-05-12

  • Last modified date

    2017-05-12

  • 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 MFT V9.0

  • Fixed component ID

    5724H7262

Applicable component levels

  • R900 PSY

       UP

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

Document Information

Modified date:
12 May 2017