Fixes are available
APAR status
Closed as program error.
Error description
XMS Client for .NET ignores Connection Factory properties set by the user when connecting to WebSphere MQ. MQSERVER/MQCHLLIB Environment variable(s) is given higher precedence if defined.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: XMS Client applications which connecto to WebSphere MQ using the Connection Factory properties and have MQSERVER/MQCHLLIB defined for other application(s) on the same machine. Platforms affected: Windows **************************************************************** PROBLEM SUMMARY: If MQSERVER/MQCHLLIB is set, XMS Cliend ignores the Connection Factory properties set by the user. XMS Client attempted to use MQSERVER/MQCHLLIB and this caused CreateConnection() API to fail.The Connection Factory properties were ignored even when they are set.
Problem conclusion
Current order of precedence followed by XMS Client to connect to a WebSphere MQ Queue Manager: 1. Connection Factory properties set by the user. 2. MQSERVER Environment variable. 3. MQCHLLIB Environment variable.
Temporary fix
Comments
APAR Information
APAR number
IZ60721
Reported component name
MSG SRVCS CL .N
Reported component ID
5724M2100
Reported release
200
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-09-16
Closed date
2009-10-23
Last modified date
2009-10-26
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
MSG SRVCS CL .N
Fixed component ID
5724M2100
Applicable component levels
R200 PSY
UP
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCRTPP","label":"SupportPac"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
26 October 2009