Hi Denis, many thanks for your insight. After adding the entries in the registry, I got a single, much more reasonable error MQRC2012 - ENVIRONMENT_ERROR. Not sure what that mean. I do have MQSERVER defined correctly pointing to the working svrconn and port.
any idea? I'll do more research, when I come through with this, I'll report my result back. Bill, what's the SupportPac "Q" you mentioned? Nice to know someone did it successfully before. thanks a lot. Ben "Blondiaux Denis (DBB)" To: [EMAIL PROTECTED] <Denis.Blondiaux cc: @DEXIA.BE> Subject: Re: share MQ WindowsClient binary and library possible? Sent by: MQSeries List <[EMAIL PROTECTED] en.AC.AT> 06/11/2004 02:49 AM Please respond to MQSeries List Hi, I try to do the same thing but it's really not possible to run mqclient without adding minimal registry keys. You will find these three keys after my signature. A few month ago, I've open a change request to IBM to answer allowing client installation files on a LAN, without registry changes. The answer from IBM is in a few word : "it's a valid request since the licence for client is free. But it will not be treated with an absolute priority. so, MAY BE in another version." I think that if a lot of customer ask this request, they can choose to implement it in a CSD. Best Regards, Denis ps. Here is the three key that my tests show as required. [HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeries\CurrentVersion] "FilePath"="J:\\MQM\\TOOLS\\MQCLIENT" "WorkPath"="J:\\MQM\\TOOLS\\MQCLIENT" [HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeries\CurrentVersion\Configuration\AllQueueManagers] "DefaultPrefix"="J:\\MQM\\TOOLS\\MQCLIENT" -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Marty Fraiser Sent: jeudi 10 juin 2004 18:33 To: [EMAIL PROTECTED] Subject: Re: share MQ WindowsClient binary and library possible? I've seen that done successfully. It's been years since helping a customer set it up and don't remember the details but it worked for hundreds of clients pointing to a shared server drive. We may have added registry entries on each client to make it appear the client was installed but I don't remember, You should be able to figure out why you're getting a 2195 by tracing the client connect attempt. Maybe you don't have write access to the share or something along those lines; or maybe it's missing expected registry entries? You might try replicating the MQ registry entries from the server with client installed, with appropriate substitutions, to one of the client wannabes. HTH, Marty Benjamin F. Zhou wrote: >Hi, > >since quite many developers need to access MQ via WindowsClient. I tried >to install the client software once on a shared network drive, then just >add that location, say L:\ibm\mqseries\bin, to system path, and define >the MQSERVER environment variable. > >But this doesn't seem to work. and I got reason code 2195 - unexpected >error. I also checked the registry, don't really see any entry of >significance related to this problem. > >Has anyone tried this before with success? > >thanks a lot. > >Benjamin F. Zhou >Mercedes-Benz USA >x.2474 > >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 -------------------------------------- Dexia Bank disclaimer : http://www.dexia.be/maildisclaimer.htm -------------------------------------- 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