IBM Support

IC90658: WMQ MFT: 7.5 AGENTSTATUSJITTERTOLERANCE PROPERTY INCORRECTLY DEFINED AS AGENT PROPERTY INSTEAD OF COORDINATION QMGR PROPERTY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In WebSphere MQ V7.5, the property:
    "agentStatusJitterTolerance"
    has been changed from a Coordination Queue Manager property to
    an Agent property, which means it needs to be set in an
    agent.properties file rather than coordination.properties.
    
    This change is incorrect. The property needs to be a
    Coordination Queue Manager property.
    
    One of the installation options for the WebSphere MQ V7.5
    Managed File Transfer component is a Tools only installation.
    
    In this type of installation, users will have access to all of
    the Managed File Transfer commands (such as fteListAgents) as
    well as a coordination.properties file.
    
    However, this type of installation will not install any Agents.
    This means that there will be no agent.properties file, and so
    no mechanism to set the "agentStatusJitterTolerance" property
    used by fteListAgents.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of WebSphere MQ Managed File Transfer
    who either:
    
    - Set the agentStatusJitterTolerance property in an
    agent.properties file, as documented in the "The
    agent.properties file" topic of the WebSphere MQ V7.5
    Information Center.
    - Set the agentStatusJitterTolerance property in a
    coordination.properties file, as documented in IBM technote
    1616381.
    
    and then run the fteListAgents command.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM SUMMARY:
    The property agentStatusJitterTolerance defines the maximum
    amount of time an agent status message publication can be
    delayed by before the message is considered as overdue. This
    property is used by the fteListAgents command to determine if an
    agent status publication is still current, or if it is out of
    date.
    
    In WebSphere MQ File Transfer Edition V7.0.4,
    agentStatusJitterProperty was defined as a coordination queue
    manager property. When the fteListAgents command was run, it
    looked for this property in the coordination.properties file for
    the coordination queue manager that it was connecting to, and
    then used this value when determining agent status.
    
    In WebSphere MQ V7.5 Managed File Transfer, the property was
    moved to be an agent property. However, the fteListAgents
    command was not changed and still expected
    agentStatusJitterTolerance to be in a coordination.properties
    file. This resulted in the following behaviour:
    
    - If agentStatusJitterTolerance was set in agent.properties, the
    value was ignored by the fteListAgents command.
    - If agentStatusJitterTolerance was specified in the
    coordination.properties file for the coordination queue
    manager used by fteListAgents, the warning 'BFGUB0060W: The
    MQMFT property name "agentStatusJitterTolerance" is not valid in
    file "coordination.properties" and will be ignored.' was written
    for to the console when the fteListAgents command was run.
    

Problem conclusion

  • WebSphere MQ V7.5 Managed File Transfer has been updated to
    allow the agentStatusJitterTolerance property to be set in the
    coordination.properties file. If the property is specified in
    the coordination.properties file for the coordination queue
    manager used by the fteListAgents command, the value of the
    property will be used when the command determines agent status.
    
    If the agentStatusJitterTolerance property has been defined in
    an agent.properties file, the value of the property in the
    file will not be used by the fteListAgents command.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following:
    
    Version            v7.5
    --------           --------------------
    Fix available in:  7.5.0.2
    
    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

    IC90658

  • Reported component name

    WMQ FTE

  • Reported component ID

    5724H7242

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-03-06

  • Closed date

    2013-05-07

  • Last modified date

    2013-07-08

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

  • 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:
08 July 2013