Re: MQ .NET and channel exits

2004-11-23 Thread David C. Partridge
Does the code also allow specification of securityData?

Thanks
Dave

-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Jason
Edmeades
Sent: 22 November 2004 16:01
To: [EMAIL PROTECTED]
Subject: Re: MQ .NET and channel exits


Support for these was added under APAR IC39879
(http://www-1.ibm.com/support/docview.wss?uid=swg1IC39879), which shipped
in fixpack 8, although I do agree the documentation wasnt updated. Looking
at the code I have suspicions you might need a fix on top of that as well
(defect 80465) which you would have to get through service and is scheduled
for fixpack 09.

This should enable the message and send / receive exits from a .net
environment to be supplied

Regards,
Jason Edmeades
[EMAIL PROTECTED]
Websphere MQ Service Architect
Internet email: [EMAIL PROTECTED]

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


Re: MQ .NET and channel exits

2004-11-23 Thread Meekin, Paul
Ahh, I see... in that case I agree it would be a surprising limitation!

Thanks Sid.

-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of
[EMAIL PROTECTED]
Sent: 23 November 2004 01:34
To: [EMAIL PROTECTED]
Subject: Re: MQ .NET and channel exits


It's not an actual VM, it's a runtime that just in time compiles code to
native executable format... quite different from Java.



-Original Message-
From: Meekin, Paul [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 23 November 2004 01:52
To: [EMAIL PROTECTED]
Subject: Re: MQ .NET and channel exits

Forgive the butting in but, isn't .NET Microsoft's latest attempt at
creating a proprietary Java-like platform? (Java-like in the sense of
being a complete VM, language, interpreter etc rather than an actual JVM
environment).

In that case, isn't it reasonable to have similar limitations to Java apps?

-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of David
C. Partridge
Sent: 22 November 2004 15:05
To: [EMAIL PROTECTED]
Subject: Re: MQ .NET and channel exits


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


H   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

Re: MQ .NET and channel exits

2004-11-22 Thread David C. Partridge
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


Re: MQ .NET and channel exits

2004-11-22 Thread Potkay, Peter M (ISD, IT)
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


Re: MQ .NET and channel exits

2004-11-22 Thread David C. Partridge
H   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


Re: MQ .NET and channel exits

2004-11-22 Thread Potkay, Peter M (ISD, IT)
.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


H   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

Re: MQ .NET and channel exits

2004-11-22 Thread David C. Partridge
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


H   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

Re: MQ .NET and channel exits

2004-11-22 Thread Jason Edmeades
Support for these was added under APAR IC39879
(http://www-1.ibm.com/support/docview.wss?uid=swg1IC39879), which shipped
in fixpack 8, although I do agree the documentation wasnt updated. Looking
at the code I have suspicions you might need a fix on top of that as well
(defect 80465) which you would have to get through service and is scheduled
for fixpack 09.

This should enable the message and send / receive exits from a .net
environment to be supplied

Regards,
Jason Edmeades
[EMAIL PROTECTED]
Websphere MQ Service Architect
Internet email: [EMAIL PROTECTED]

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


Re: MQ .NET and channel exits

2004-11-22 Thread Meekin, Paul
Forgive the butting in but, isn't .NET Microsoft's latest attempt at creating a 
proprietary Java-like platform? (Java-like in the sense of being a complete 
VM, language, interpreter etc rather than an actual JVM environment).

In that case, isn't it reasonable to have similar limitations to Java apps?

-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of David
C. Partridge
Sent: 22 November 2004 15:05
To: [EMAIL PROTECTED]
Subject: Re: MQ .NET and channel exits


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


H   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

Re: MQ .NET and channel exits

2004-11-22 Thread David C. Partridge
Thanks very much for that info.

I'm confused though - I looked the apar text, and it said that the fix would
support specification of the message exit.   Surely msgexit isn't valid for
client ...

David

-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Jason
Edmeades
Sent: 22 November 2004 16:01
To: [EMAIL PROTECTED]
Subject: Re: MQ .NET and channel exits


Support for these was added under APAR IC39879
(http://www-1.ibm.com/support/docview.wss?uid=swg1IC39879), which shipped
in fixpack 8, although I do agree the documentation wasnt updated. Looking
at the code I have suspicions you might need a fix on top of that as well
(defect 80465) which you would have to get through service and is scheduled
for fixpack 09.

This should enable the message and send / receive exits from a .net
environment to be supplied

Regards,
Jason Edmeades
[EMAIL PROTECTED]
Websphere MQ Service Architect
Internet email: [EMAIL PROTECTED]

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


Re: MQ .NET and channel exits

2004-11-22 Thread David C. Partridge
There doesn't appear to be anything in the readme for CSD8 about this :-(

Dave

-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Jason
Edmeades
Sent: 22 November 2004 16:01
To: [EMAIL PROTECTED]
Subject: Re: MQ .NET and channel exits


Support for these was added under APAR IC39879
(http://www-1.ibm.com/support/docview.wss?uid=swg1IC39879), which shipped
in fixpack 8, although I do agree the documentation wasnt updated. Looking
at the code I have suspicions you might need a fix on top of that as well
(defect 80465) which you would have to get through service and is scheduled
for fixpack 09.

This should enable the message and send / receive exits from a .net
environment to be supplied

Regards,
Jason Edmeades
[EMAIL PROTECTED]
Websphere MQ Service Architect
Internet email: [EMAIL PROTECTED]

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


Re: MQ .NET and channel exits

2004-11-22 Thread Sid . Young
It's not an actual VM, it's a runtime that just in time compiles code to
native executable format... quite different from Java.



-Original Message-
From: Meekin, Paul [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 23 November 2004 01:52
To: [EMAIL PROTECTED]
Subject: Re: MQ .NET and channel exits

Forgive the butting in but, isn't .NET Microsoft's latest attempt at
creating a proprietary Java-like platform? (Java-like in the sense of
being a complete VM, language, interpreter etc rather than an actual JVM
environment).

In that case, isn't it reasonable to have similar limitations to Java apps?

-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of David
C. Partridge
Sent: 22 November 2004 15:05
To: [EMAIL PROTECTED]
Subject: Re: MQ .NET and channel exits


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


H   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

MQ .NET and channel exits

2004-11-19 Thread David C. Partridge
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


Re: MQ .NET and channel exits

2004-11-19 Thread Potkay, Peter M (ISD, IT)
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