IBM Support

IV51770: THE MQ_LCLADDR ENVIRONMENT VARIABLE BEHAVES INCONSISTENTLY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The MQ_LCLADDR environment variable has inconsistent behaviour.
    
    The first time a channel is started, the input is parsed and
    if LoclAddr is not set then the environment variable
    MQ_LCLADDR is used. The next time when parsing is done,
    WebSphere MQ uses the cached values for channel. This does not
    include the LoclAddr and so the MQ_LCLADDR environment
    variable is not checked. This results in channels not using
    the MQ_LCLADDR variable.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users who use MQ_LCLADDR environment variable to make use of a
    particular local address while establishing channel connections
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM SUMMARY:
    The environment variable MQ_LCLADDR helps set the local
    communication address on a channel that has the transport type
    as TCP/IP. It is used as an alternative to the channel attribute
    LoclAddr and is used only when LoclAddr is not specified on
    the channel.
    
    When a channel is started in first attempt, it checks the
    presence of LoclAddr value and only if the LoclAddr value is not
    set, the channel uses the value set in MQ_LCLADDR variable.
    The next time when the channel is started, it uses the cached
    values. Since the LoclAddr was not cached during the first
    attempt, the channel will start without using MQ_LCLADDR
    variable as it will only be used when a check on LoclAddr is
    made during channel start and it is not found to be set.
    So MQ_LCLADDR variable will only be used on the first attempt
    and will be left unused on the successive attempts of channel
    start.
    

Problem conclusion

  • The LoclAddr attribute of channel is now cached so that when the
    channel retries, it uses the cached values and finds that
    LoclAddr is not set which makes the channel to use the
    MQ_LCLADDR variable's value. This ensures that the usage of
    MQ_LCLADDR environment variable has a consistent behaviour.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.1       7.1.0.5
    v7.5       7.5.0.4
    v7.0       7.0.1.12
    
    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

    IV51770

  • Reported component name

    WMQ AIX V7

  • Reported component ID

    5724H7221

  • Reported release

    701

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-11-07

  • Closed date

    2013-12-13

  • Last modified date

    2013-12-13

  • 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 AIX V7

  • Fixed component ID

    5724H7221

Applicable component levels

  • R701 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDEZSF","label":"IBM WebSphere MQ Managed File Transfer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
31 March 2023