IBM Support

IC63609: WINDOWS V7 CLIENT SEEMS TO CONNECTS TO V3 VSE SERVER THEN DISCONNECTS BUT THE SERVER SEE THE CLIENT AS CONNECTED.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When connecting a V7 Windows client to a z/VSE v3.0 queue
    manager the channel connection seems complete but soon it drops
    the connection at client end but at queue manager end the
    channel connection is shown as active and running when in fact
    it has no connection any longer to the client.
    .
    Analysis shows that the z/VSE queue manager rejects the
    connection because the .NET client sends in an MQOPEN request
    and provides a version 3 MQOD structure, which is unsupported.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All .NET users connecting to versions of WebSphere MQ that do
    not understand version 3 MQOD structures.
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM SUMMARY:
    When an MQOD object is constructed it initializes all its fields
    to default values, including setting the version field to 1.
    The act of clearing the version 2 and version 3 fields results
    in .NET believing that they are in use, and hence sets the
    version of the MQOD to 3. This problem was introduced in
    WebSphere MQ v7.0.1.0.
    

Problem conclusion

  • The MQObjectDescriptor .NET class has been modified to
    initialize the version to 1 after all the fields are
    initialized to their default values.
    
    | MDVREGR 7.0-WS-MQ-Windows-RP0001 |
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.1
    --------           --------------------
    Windows            U200310
    
    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

    IC63609

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-10-07

  • Closed date

    2009-10-29

  • Last modified date

    2010-04-08

  • APAR is sysrouted FROM one or more of the following:

    PK97765

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WMQ WINDOWS V7

  • Fixed component ID

    5724H7220

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCPQ63","label":"APAR \/ Maintenance"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
08 April 2010