Thanks Dave I know that the MQCONNX appears in the trace file but I don''t believe the MQCNO values appear but you may be able to help me there. I'll send the trace file to you if thats ok.
Regards Neil -----Original Message----- From: David C. Partridge [mailto:[EMAIL PROTECTED] Sent: 19 June 2003 15:50 To: [EMAIL PROTECTED] Subject: Re: New MQ API Exit to find MQCNO values The sample exit DOES dump the connect options on the CONNX. Is the problem one of interpreting them? As far as I remember, in the case of an MQI client the CONNX is issued by the MCA based on the MQCONN issued at the client. You should see the CONNX call in the trace for the exit if you enable tracing by setting the environment variables MQAPI_TRACE_LOGFILE and MQAPI_TRACE_OPTIONS at the SYSTEM level (using control panel) prior to starting the QM. I *strongly* suggest that you have NO other MQ activity on the box at the time, as you'll get quite enough trace files with just the MQ processes. It will help if you don't have MQ Explorer running as that will create voluminous quantities of trace (though in its own file). If you need help reading the trace for the client proxy, email it to me (offline) and we can discuss the detail content. Only send me the trace for the process acting as the client proxy. You can tell which file it is because you'll see entries in there for execution environment MQXE_MCA_SVRCONN (though IIRC the connect is issued with environment set to MQXE_MCA). David Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
