That's right Gina. As an admin you provide them with the connection details: hostname, port number, channel name, QM Name(optional) plus any SSL or Exit info they may need if you have the channel locked down. They then code that in prep for the MQCONNX call.
If you give them a secondary QM it is up to their coding to decide when to stop trying to connect to QM #1, change the parameters to point at QM #2 and then retry the connection attempt. Note that if they do code the MQCONNX call with all these parms filled in it will override the MQSERVER variable or MQCHLLIB / MQCHLTAB if set. Peter -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of GINA MCCARTHY Sent: Monday, September 24, 2007 5:40 PM To: [email protected] Subject: Re: MQ Client Connections Thanks for your reply! They want to use the MQCONNX. Sooo...they need to use the same info (channel, protocol and conname) as the MQSERVER provided them....right? The channel would be a svrconn and they do not need access to a client channel table....right? Gi ________________________________ From: MQSeries List on behalf of Glen Larson Sent: Mon 9/24/2007 4:29 PM To: [email protected] Subject: Re: MQ Client Connections Hi Gina, When using the channel table method. You the admin generated the table by defining the QMGRs (with address) on a QMGR then placing the amqclchl.tab on a shared drive where it is available to the applications. This method allows you to move QMGRs to new servers, as needed. This method does require the application to specify the QMGR name vs * for the default. Also, the serverconn variable needs to be removed and the channel tab, and channel lib variables to be used. The MQCONNX method requires the application to be aware of the location of the QMGR(s) it wishes to use. Glen Larson Lead System Engineer Middleware Support Progressive Insurance 719-660-4717 cell 719-432-3102 work and 762-3102 network GINA MCCARTHY <[EMAIL PROTECTED]> Sent by: MQSeries List <[email protected]> 09/24/2007 01:11 PM Please respond to MQSeries List <[email protected]> To [email protected] cc Subject Re: MQ Client Connections "The easy approach is to use Client Channel tables unless the app wants to change and use MQCONNX rather than MQCONN." Is this saying I DO NOT need the client channel table? ;-) We're leaning toward this solution....would SVRCONN channels be enough? Regards, Gina McCarthy Arrow Electronics, Inc. 50 Marcus Drive Melville, NY 11747 (631) 847-5440 AIM: gigibeans1 -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of T-Rob Sent: Monday, September 24, 2007 2:55 PM To: [email protected] Subject: Re: MQ Client Connections The only catch here is if you need SSL in the channel table, which hopefully you do! Last I heard, M072 did not build a valid table when the SSL parameters were used. Paul, if you are listening on this thread, did that ever get fixed and released? -- T.Rob MQSeries List <[email protected]> wrote on 09/24/2007 02:20:30 PM: > Hi, > > Since you mentioned MQSERVER environment variable then I take it that > the client app on Solaris is not a Java app. Right? > > The easy approach is to use Client Channel tables unless the app wants > to change and use MQCONNX rather than MQCONN. > > With SupportPac MO72, this is a snap (even easier if you put these > commands in a Windows batch file). > > - Open a command prompt and CD to where you installed MO72 > > - Create a directory called: tables > mkdir tables > > - Set the MQCHLLIB environment variable > set MQCHLLIB={MO72_install_Path}\tables > > - Create a mqsc file (temp.mqsc) with your CLNTCONN definitions - 2 > items: z/Linux and Windows > > - Run MO72 against the file > mqsc.exe -n -t appABC.TAB < temp.mqsc > > - Now you will have a Client Channel Table file 'tables\appABC.TAB' > that you can ftp (as binary) to Solaris > > - In the app's profile set MQCHLLIB and MQCHLTAB environment variables > (make sure you remove MQ Server varaible) and you are done. > > > Hope that helps. > > > Regards, > Roger Lacroix > Capitalware Inc. > http://www.capitalware.biz > > > On Mon, 24 Sep 2007 13:40:20 -0400, GINA MCCARTHY <[EMAIL PROTECTED] > COM> wrote: > > I have never had the need to set up anything other than SVRCONN channels > > and MQSERVER for our MQ Clients. There was not a need to access more > > than one queue manager from each client. Well....now there is. > > > > I need some advice. The client is on Solaris and the Server(s) are > > on z/Linux and on Windows. > > > > Regards, > > Gina McCarthy > > Arrow Electronics, Inc. > > 50 Marcus Drive > > Melville, NY 11747 > > (631) 847-5440 > > AIM: gigibeans1 To unsubscribe, write to [EMAIL PROTECTED] and, in the message body (not the subject), write: SIGNOFF MQSERIES Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html To unsubscribe, write to [EMAIL PROTECTED] and, in the message body (not the subject), write: SIGNOFF MQSERIES Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html ________________________________ List Archive <http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings <http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe <mailto:[EMAIL PROTECTED]&BODY=sign off%20mqseries> Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com <http://www.lsoft.com/resources/manuals.asp> To unsubscribe, write to [EMAIL PROTECTED] and, in the message body (not the subject), write: SIGNOFF MQSERIES Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html ************************************************************************* This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. ************************************************************************* To unsubscribe, write to [EMAIL PROTECTED] and, in the message body (not the subject), write: SIGNOFF MQSERIES Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
