Indeed so, That's what started this whole thread :-( D.
-----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Potkay, Peter M (ISD, IT) Sent: 22 November 2004 14:01 To: [EMAIL PROTECTED] Subject: Re: MQ .NET and channel exits .NET clients do not support client channel tables. See the 1st page of chapter 5 in the .NET manual. -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of David C. Partridge Sent: Monday, November 22, 2004 8:31 AM To: [EMAIL PROTECTED] Subject: Re: MQ .NET and channel exits Hmmmm Anyone from Hursley able to comment? This seems to be a major omission from the manual. Support for channel tables in client mode also seems a pretty major omission, as this allows the use of exits with NO code modification at all. Dave -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Potkay, Peter M (ISD, IT) Sent: 22 November 2004 13:12 To: [EMAIL PROTECTED] Subject: Re: MQ .NET and channel exits Yes, the manual is incomplete in this area. The Hash Table definitely works, I just haven't used the Security Exit parameter yet. You could also directly code MQEnvironment.SecurityExit if you don't want to use the hash table. -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of David C. Partridge Sent: Monday, November 22, 2004 5:08 AM To: [EMAIL PROTECTED] Subject: Re: MQ .NET and channel exits Strange, my version of the documentation doesn't mention that at all. The only attributes mentioned for the MQEnvironment class are: Channel Hostname Port SSLCipherSpec SSLKeyRepository SSLPeerName The Java MQEnvironment class DOES have attributes for channel exits. Are you saying that the use of a HashTable and setting the exit names will actually work as expected? Unfortunately changing the code isn't an option in this particular case, so even if you can set the HashTable values prior to the connect, and there are (undocumented) attributes of the MQEnvironment class for: securityExit sendExit receiveExit just like the Java implementation, this wouldn't solve the problem for the particular situation. Cheers Dave -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Potkay, Peter M (ISD, IT) Sent: 19 November 2004 18:01 To: [EMAIL PROTECTED] Subject: Re: MQ .NET and channel exits David, I haven't actually used it yet, but there is something for specifying a channel exit on the MQEnvironment class. 'build the hash table with the connection info myHashTable.Add(IBM.WMQ.MQC.CHANNEL_PROPERTY, "ClientChannelName") myHashTable.Add(IBM.WMQ.MQC.HOST_NAME_PROPERTY, "HostName") myHashTable.Add(IBM.WMQ.MQC.PORT_PROPERTY, 1414) myHashTable.Add(IBM.WMQ.MQC.SECURITY_EXIT_PROPERTY, "SecurityExitPath") 'connect to the QM using tha HashTable for connection paramters myQM = New MQQueueManager(QMName, myHashTable) -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of David C. Partridge Sent: Friday, November 19, 2004 12:55 PM To: [EMAIL PROTECTED] Subject: MQ .NET and channel exits It would appear to be impossible to use MQ channel exits with MQ .NET, as it doesn't support the use of channel connection tables, and does not allow specification of channel exits in the MQEnvironment class, and there doesn't appear to be any other way to configure their use. This seems to be rather a problem if you have a need to do channel exit stuff with a .net client :-( Is there some (possibly undocumented) way round this? There is one line in the manual which suggests there is an MQChannelDefinition class, but this isn't mentioned anywhere else, and the MQQueueManager doesn't appear to have a ctor that uses one (but this may just be because it isn't documented). Is the code owner of the .net classes listening, or is someone who is able to catch his or her attention? Thanks, David C. Partridge 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 This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential 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 email and delete this communication and destroy all copies. 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 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 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
