MQSeries.net :: View topic

Mallik · Posted: Tue Jul 06, 2004 4:23 am Post subject:

One of our developers has a weird problem connecting to the MQ server. The MQ client with 5.3.0, he is able to connect to the queue manager where as with client 5.3.0.5 it gives 2012 error, "MQRC_ENVIRONMENT_ERROR".

Clients(5.3.0, 5.3.05) on Linux with C++ application issuing MQCONNX call.

Server on Solaris (5.3.0)

Our developer says he is using the lib 'libmqic_r.so', and I can see that lib is available on both 5.3 & 5.3.05. Not sure if we are missing anything. Has any one come across this prblem before?
This is the complete error.

***
MQRC_ENVIRONMENT_ERROR:
The call is not valid for the current environment
On z/OS, one of the following applies
An MQCONN or MQCONNX call was issued, but the application has been linked with an adapter that is not supported in the environment in which the application is running. For example, this can arise when the application is linked with the WebSphere MQ RRS adapter, but the application is running in a DB2 Stored Procedure address space. RRS is not supported in this environment. Stored Procedures wishing to use the WebSphere MQ RRS adapter must run in a DB2 WLM-managed Stored Procedure address space
An MQCMIT or MQBACK call was issued, but the application has been linked with the RRS batch adapter CSQBRSTB. This adapter does not support the MQCMIT and MQBACK calls
An MQCMIT or MQBACK call was issued in the CICS or IMS environment
The RRS subsystem is not up and running on the z/OS system that ran the application
On Compaq OpenVMS Alpha, OS/2, OS/400, Compaq NonStop Kernel, UNIX systems, and Windows, one of the following applies
The application is linked to the wrong libraries (threaded or nonthreaded)
An MQBEGIN , MQCMIT , or MQBACK call was issued, but an external unit-of-work manager is in use. For example, this reason code occurs on Windows when an MTS object is running as a DTC transaction. This reason code also occurs if the queue manager does not support units of work
The MQBEGIN call was issued in a WebSphere MQ client environment
An MQXCLWLN call was issued, but the call did not originate from a cluster workload exit
Corrective action: Do one of the following (as appropriate)
On z/OS
Link the application with the correct adapter
Modify the application to use the SRRCMIT and SRRBACK calls in place of the MQCMIT and MQBACK calls. Alternatively, link the application with the RRS batch adapter CSQBRRSI. This adapter supports MQCMIT and MQBACK in addition to SRRCMIT and SRRBACK
Modify the application to use the SRRCMIT and SRRBACK calls in place of the MQCMIT and MQBACK calls. Alternatively, link the application with the RRS batch adapter CSQBRRSI. This adapter supports MQCMIT and MQBACK in addition to SRRCMIT and SRRBACK
For a CICS or IMS application, issue the appropriate CICS or IMS call to commit or backout the unit of work
Start the RRS subsystem on the z/OS system that is running the application
In the other environments
Link the application with the correct libraries (threaded or nonthreaded)
Remove from the application the call that is not supported.

******