Re: Compiling MQ applications in 64 bit mode.
Title: Compiling MQ applications in 64 bit mode. THE ONLY way you can support 64 bit applications on AIX connecting to MQ is to use the 64 bit MQ CLIENT support pack (MACS). This includes new 64-bit headers and libraries. There is no "binding mode" for 64 bit applications. David
Incorrect conname in CLUSRCVR
If the conname in a cluster receiver is incorrect, then it won't be possible to start the channel TO that clusrcvr after the information about that cluster receiver is flowed to the other QMs in the cluster. In this case (assume the clusrcvr is on a full repos QM called QM1), then what is the correct recovery procedure (without completely deleting and redefining the cluster). Is it: At QM1: 0. Change the channel defn for the clusrcvr so it has the correct conname 1. Alter the QM so it isn't a full repos for the cluster 2. resolve in doubt clussdrs 3. Wait for clussdr channels to go inactive 4. Stop the clusrcvrs 5. Refresh cluster REPOS(YES) 6. Alter the QM so it is again a full repos 7. Restart cluscvrs. Regards, David C. Partridge Technical Products Director Primeur Security Services Tel: +44 (0)1926 511058 Mobile: +44 (0)7713 880197 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: C++ Connection pool
Hi there Didi - long time no speak. I don't know - the question was asked on behalf of a development company working for one of our customers, and I don't know the platform they are using. Most likely is Unix or Windows 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
Re: C++ Connection pool
Didi, You said that the COM+ interface gives session pooling. I accept that it provides an MQSession object that's shared between threads, and that you can create MQQueueManager objects or use the AccessQueueManager() method to get a QM object. However I can't see anything in the docs that suggest that it does session pooling whereby when an MQQueueManager object is destroyed ( or a .Disconnect() is issued) that an MQDISC is NOT actually issued (at least for a while - say 30 mins) and if a new MQQueueManager object is created for that thread the connection is re-used. To me the docs just suggest a light wrapping of the MQI. Or does the MQSession.AccessQueueManager() method behave differently from explicitly constructing an MQQueueManager, setting the Name Property and issuing a Connect(). Please could you clarify this for me? Thanks Dave 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
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
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
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
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
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
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
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
Re: AS/400: MQ clients
IIRC there is no MQ client on AS/400 (though memory is faulty these days) The second sign of getting old is loosing your memory. I can't remember what the first one was. D. 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: Channel conversion from Mainframe
Why use in channel conversion? Why not use get with convert? This way you can change your mq topology, adding channels if necessary w/o incurring the cost of conversion as the message crosses very channel. Dave -Original Message-From: MQSeries List [mailto:[EMAIL PROTECTED]On Behalf Of Kulbir S. ThindSent: 12 November 2004 10:44To: [EMAIL PROTECTED]Subject: Channel conversion from MainframeHi, We may need to enable channel conversion on a channel from the Mainframe to Sun Solaris. Does anyone know if this is an issue? Are there any gotchas? Is there any documentation specifically for channel conversion from the Mainframe? Thanks in advance, Kulbir.
Re: Use of nCipher hardware with MQ on AIX - resend without signature
FWIW, DSMQ *does* support nCipher nFast h/w - but while what is does for MQ channels is v. similar to SSL, it isn't compatible on the wire, so you can't have SSL on one end of the channel, and DSMQ on the other. Dave -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of B.A.H. van der Leeuw Sent: 27 October 2004 19:23 To: [EMAIL PROTECTED] Subject: Use of nCipher hardware with MQ on AIX - resend without signature Hi, In the MQSeries documentation, it is mentioned that PKCS #11 hardware is supported as cryptographic hardware. However, in the appendix of the Security guide, only the IBM FC 4963 is mentioned as supported hardware under AIX. We want to use nCipher nFast hardware in combination with AIX5.2 and MQ 5.3.0.6, but this is not tested by IBM. Is there anyone around that uses this combination of hardware and software? Any issues? Regards, Ard van der Leeuw BAHLEO http://www.bahleo.nl/ +31 55 3603994 +31 6 28846008 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: Message length?
If you are using MQCONNX, you can pass an MQCD to the MQCONNX (pointed to by the MQCNO), and in the MQCD, you can specify the MaxMsgLength. If the srvrconn at the other end of the channel agrees, you should be OK to use large messages up to the lower of the two sizes (the one you supply and the one on the srvrconn channel definition). Dave 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 Series IMS Bridge EBCDIC to ASCII Conversion
IIRC the conversion for the IMS bridge is done at the receiving MCA and all is converted to the QM codepage. Dave
Re: need help finding MQCHT_SENDER
cmqxc.h Dave
Unexpected channel terminations on Solaris when channel exits are used.
If you see this, it could be caused by the patch level of the Solaris linker. We had a crit. sit. at a customer which after much tracing (truss as well as MQ traces) we narrowed down a segv in dlclose().This was happening on Solaris 8, and the customer had patch level 109147-24 for the linker. Applying 109147-27 resolved the problem even though the docs for the patch didn't show any fixes for dlclose(). So if you have channel exits and you get FDCs for Probe Id :- RM487001 Component :- rriChannelTerminate Major Errorcode :- rrcE_CHANNEL_TERMINATED then you should check that you have at least this patch level applied to the Solaris linker (there's almost certainly an equivalent patch level for Solaris 9, but I don't know the number). Regards, David C. Partridge Technical Products Director Primeur Security Services Tel: +44 (0)1926 511058 Mobile: +44 (0)7713 880197 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 maintenance
Title: RE: MQ maintenance Yes (it won't be this year). Dave
Re: Where to find Character Conversion Tables?
Philip Where did you get those pdf files from please, can they be pulled of the web? Dave 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: Where to find Character Conversion Tables?
Hmmm The table for CP 037 appears incomplete is it doesn't cover any of the characters 00-3f, while that for 437 covers the full 00-ff range. Also some of the character assignments in CP 437 seem strange. For example x09 is normally a tab character, and in the 437 table it is shown as an small circle (glyph name SM75). Dave -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: 28 September 2004 19:30 To: [EMAIL PROTECTED] Subject: Re: Where to find Character Conversion Tables? (See attached file: cp00037z.pdf) DeBlassio, Joe [EMAIL PROTECTED]To: [EMAIL PROTECTED] -MINOR.COM cc: Sent by: MQSeries Subject: Where to find Character Conversion Tables? List [EMAIL PROTECTED] c.at 09/28/2004 01:54 PM Please respond to MQSeries List Hi Where can I find out how a character from windows (CCSID 437) is being converted to a character on z/OS (37)? It's been some time since I've had to do this so I'm having trouble remembering. Thanks for your help, Joe This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of J.P. Morgan Chase Co., its subsidiaries and affiliates. 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: setmqaut on unix
Think of it as a documented feature: System Administration Guide, Chapter 4, Section: Authority to work with WebSphere MQ objects, Sub-Section: Identifying the user ID Principals and groups Principals can belong to groups. You can grant access to a particular resource to groups rather than to individuals, to reduce the amount of administration required. For example, you might define a group consisting of users who want to run a particular application. Other users can be given access to all the resources they require simply by adding their user ID to the appropriate group. This is described in Creating and managing groups. A principal can belong to more than one group (its group set) and has the aggregate of all the authorities granted to each group in its group set. These authorities are cached, so any changes you make to the principal's group membership are not recognized until the queue manager is restarted, unless you issue the MQSC command REFRESH SECURITY (or the PCF equivalent). UNIX systems All ACLs are based on groups. When a user is granted access to a particular resource, the user ID's primary group is included in the ACL, not the individual user ID, and authority is granted to all members of that group. Because of this, be aware that you could inadvertently change the authority of a principal by changing the authority of another principal in the same group. All users are nominally assigned to the default user group nobody and by default, no authorizations are given to this group. You can change the authorization in the nobody group to grant access to WebSphere MQ resources to users without specific authorizations. Dave -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Wright, Tim (AFM) Sent: 29 September 2004 15:15 To: [EMAIL PROTECTED] Subject: setmqaut on unix Does anyone know if IBM recognise the fact that setmqaut on unix doesn't work for principals ( if you apply an authority setting to a principal, the auth actually applies to the principal's primary group ) as a bug? If not has anyone ever raised a PMR about this? thanks tim * Emails aren't always secure, and they may be intercepted or changed after they've been sent. Abbey doesn't accept liability if this happens. If you think someone may have interfered with this email, please get in touch with the sender another way. This message doesn't create or change any contract. Abbey doesn't accept responsibility for damage caused by any viruses contained in this email or its attachments. Emails may be monitored. If you've received this email by mistake, please let the sender know at once that it's gone to the wrong person and then destroy it without copying, using, or telling anyone about its contents. Abbey National Treasury Services plc Reg. No. 2338548, Cater Allen International Ltd Reg. No. 2572704, and Inscape Investments Limited Reg. No. 3839455 are registered in England and have their Registered Offices at: Abbey National House, 2 Triton Square, Regent's Place, London, NW1 3AN. Cater Allen International Ltd is a subsidiary of Abbey National Treasury Services plc. Abbey National Treasury Services plc and Cater Allen International Ltd are Members of The London Stock Exchange. Abbey National Asset Managers Ltd. Reg. No. 106669. Registered Office: Abbey National House, 301 St Vincent Street, Glasgow, G2 5HN. Registered in Scotland. Abbey National Asset Managers Ltd and Inscape Investments Limited are members of the Abbey Marketing Group and provide OEICS, PEPS, and ISAs. Abbey National Treasury Services plc, Cater Allen International Ltd, Inscape Investments Limited, and Abbey National Asset Managers Ltd are authorised and regulated by the Financial Services Authority. Abbey Financial Markets is the brand name for Abbey National Treasury Services plc. 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: Websphere MQ on AIX Dead Letter Queue Messages
Look at the messages using amqsbcg or use one of the DLQ support packs Dave 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: TCP/IP Errors
What's your keepalive time? 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
Re: libstdc++.so.3
LD_ASSUME_KERNEL=2.4.1? Dave 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: Audit of configuration changes
On OS/390, there is an audit record cut for configuration changes. They are written to SYSTEM.ADMIN.CONFIG.EVENT if you alter the qmgr to enable CONFIGEV. Dave 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: Audit of configuration changes
Unfortunately, configuration event support only seems to be present on OS/390. Why this is so I don't know as it should be simple to implement. I don't think that this is in the new release when it drops (at least I saw nothing about this in the presentation that Mark Taylor gave at the ISV conference and was I believe also shown in USA at a public event). Dave 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: Creating report messages ends with reason 2035
When the report is generated, the ReplyToQ queue is opened and the report message put using the authority of the UserIdentifier in the MQMD of the message causing the report, except in the following cases: Exception reports generated by a receiving MCA are put with whatever authority the MCA used when it tried to put the message causing the report. The PutAuthority channel attribute determines the user identifier used. COA reports generated by the queue manager are put with whatever authority was used when the message causing the report was put on the queue manager generating the report. For example, if the message was put by a receiving MCA using the MCA's user identifier, the queue manager puts the COA report using the MCA's user identifier. Applications generating reports should normally use the same authority as they would have used to generate a reply; this should normally be the authority of the user identifier in the original message. So, if this is a remote QM to the originator, then this should be being PUT with the authority of the MCA the originally put it onto the input Q. Whether this authority is enough to write to the TQ to go back depends on the platform and what user was running the MCA. For distributed platforms the user running the MCA will almost always be mqm or equivalent so it should work, but for the 390 system, the authority is defined by the RACF permissions and the value of the setting of PUTAUT on the receiver channel. This is discussed in chapter 15 and 17 of the z/OS System Setup Guide. So my guess is that the receiving system is 390 and that you are running your receiver channels with ALTMCA and that the CHIN is writing OK to the output Q, but when the getter gets the message the only authority left is the ALT part of ALTMCA. Perhaps someone with more experience of 390 access control for MQ can comment it this is a 390 system. Dave -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Kleinmanns, Hubert Sent: 22 September 2004 08:14 To: [EMAIL PROTECTED] Subject: Creating report messages ends with reason 2035 MQ-Guys, I have the following situation: 1. An application APP1 on qmgr MQ1, running as a user mqusr1, creates a message and sends it to a qmgr MQ2. APP1 sets the report options to MQRO_COD + MQRO_EXCEPTION + MQRO_PASS_MSG_ID + MQRO_PASS_CORREL_ID (I think, relevant in my case is only MQRO_COD ). 2. Application APP2 on qmgr MQ2, running as a user mqusr2, reads the message successfully. But when APP2 tries to put the report message, it fails with the reason code 2035 and the message is put to the local DLQ. 3. The user mqusr1 does not exist on system 2, but the MD contains the user mqusr1 in the field UserIdentifier. 4. When I create the user mqusr1 on system 2 with appropriate permissions, the report message is delivered successfully. Now the question: How can I enable the user mqusr1 to write to a queue on system 2 without creating this account. Nevertheless the field UserIdentifier has to contain this user, so that the system 1accepts the message? In fact, it is not only one user on system 1, which may send a message and I do not want at all create a dozen or more users, just to enable the report messages. Thanks in advance. Mit freundlichen Grüßen / With kind regards Hubert Kleinmanns (N-Tuition Business Solutions AG) im Auftrag von / on behalf of AGIS Allianz Dresdner Informationssysteme GmbH GB2 Engineering AG2HDB02 - Host-DC-Systeme und Middleware (Bank) Windmühlstraße 14 / F 2.417 D-60627 Frankfurt / Main Telefon: +49-69-263-53262 Telefax: +49-69-263-11375 E-Mail: [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: Creating report messages ends with reason 2035
I'm afraid to say that as far as I know, there's no other way to make this work. I bow to greater expertise if someone can provide the scoop on how it can work without defining the sending user on the receiving system. Dave 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: AW: Creating report messages ends with reason 2035
Perhaps someone from MQ Dev could comment on the reasoning behind the decision to send the COD with the authority of the userid in the MQMD (even though the user probably won't exist on the receiving system in a DQM environment). From my naive view of the world it would seem more logical to use either a) The userid under which the receiving app is running, or b) Send the COD with the authority of the QM. However it's my experience that (in general) IBM don't make this sort of decision without thought, and if we understood the logic we could at least understand where they were coming from. Dave 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: Disappearing cluster queues
Mike, You said: out of the box MQ will only publish and subscribe cluster object information to 2 Full Repositories can you point to where this is documented please. Thanks Dave 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: Disappearing cluster queues
My experience is that you *need* to have explicitly defined cluster sender and receiver channels between all the FULL repositories, and that if you don't you will run into this sort of problem. You shouldn't need to explicitly define clussdr channels from the full repositories to the other cluster members. Dave 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: MMC/Any GUI for administering MQ on AIX
And in answer to your question, you can use MQExplorer to admin a remote QM. Open explorer, right click on Queue Managers and select Show Queue Manager and use the Show a Remote queue manager option. Dave 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: Large message size support on MQSeries
Yes, but MQ on 390 doesn't support segmentation (though MQ 5.3 390 does support message grouping which can just about achieve a similar function) Also consider the impact on the system that very large messages may have especially when going between QMs over channels (may need to have separate xmit queues and channels just for large messages so you don't block the small ones). Also what will the storage use be for the MCA (CHIN) when handling messages this size. Dave -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Zhang, Yan Sent: 03 September 2004 15:31 To: [EMAIL PROTECTED] Subject: Large message size support on MQSeries Hi All, From what I read, that MQ supports upto 100mb for single message. It seems there is option for segmentation, Does that mean it supports over 100mb if using the segmatation option? Thank you very much!! Yan The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. 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: Connecting to more than one queue managers on solaris, linux
Using MQ Client you can do this - each thread can own a connection to different QM. Dave 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: DataCapture Exit and MQ API
Are you talking about a channel message exit here or an API exit? If a message exit, then you can connect at MQXR_INIT time (and cache the HCONN somewhere). You won't ever need to disconnect as the reason from the MQCONN should be already connected. If an API exit, all invocations of the API exit have a useable HCONN for all normal MQI verbs. Dave P. 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: Channel status / restarting channels.
Tom, I'd go further than that. The values from the cluster receiver *will* eventually override whatever you set on the cluster sender. What is more, in most cases, there won't be a cluster sender definition to dink with as you would normally only ever manually define one cluster sender channel - to one of the repos QMs. The exception to this case is that you would always manually define all cluster channels between all the full repository QMs. Dave 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: transactional client with Oracle
As far as I know it is the same price as a full server license. Dave 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: PMQCD MsgExitPtr value is coming as Null
If MQCD.Version =4 then the first thing to check for a given exit is HOW MANY exits of a given type there are. For example check MQCD.MsgExitsDefined. If 0 then there aren't any. If non-zero then follow MsgExitPtr (worth checking for null pointer - just in case). If you want to apply an exit in the case where there aren't any, you need to allocate the memory (at MQXR_INIT time), fill in the MQCD fields at MQXR_AUTO. time, and release the memory at MQXR_TERM time. If you want to ADD an addnl exit then life is of course more complex ... Dave 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: PMQCD MsgExitPtr value is coming as Null
Is this a SDR chl or a CLUSSDR? If latter, AND the CLUSRCVR channel has an exit coded, AND the channel has connected at least once, then you have an MQ BUG. If the channel has never been connected, this is to be expected, as you need to have connected to the repository at least ONCE for your QM to know what the CLUSRCVR channel definition is. Dave -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Shuba P.K. Sent: 25 August 2004 10:58 To: [EMAIL PROTECTED] Subject: Re: PMQCD MsgExitPtr value is coming as Null MQCD.Version value is 7. But when I try to get the value of MQCD.MsgExitsDefined it is 0. Whether in the receiver channel there is an exit name or not. What do I do?? -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of David C. Partridge Sent: Wednesday, August 25, 2004 3:00 PM To: [EMAIL PROTECTED] Subject: Re: PMQCD MsgExitPtr value is coming as Null If MQCD.Version =4 then the first thing to check for a given exit is HOW MANY exits of a given type there are. For example check MQCD.MsgExitsDefined. If 0 then there aren't any. If non-zero then follow MsgExitPtr (worth checking for null pointer - just in case). If you want to apply an exit in the case where there aren't any, you need to allocate the memory (at MQXR_INIT time), fill in the MQCD fields at MQXR_AUTO. time, and release the memory at MQXR_TERM time. If you want to ADD an addnl exit then life is of course more complex ... Dave 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: PMQCD MsgExitPtr value is coming as Null
You would only define manually define a clussdr channel to a repos QM. You can't be connected to the repository if the sender to the repos has never been started. Alternatively you were connected to the repos, and then changed the definition of the clusrcvr at the repos while the other QM was down (in which case it will try to use an out of date defn of the clussdr from its local cache). -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Shuba P.K. Sent: 25 August 2004 12:58 To: [EMAIL PROTECTED] Subject: Re: PMQCD MsgExitPtr value is coming as Null Yes, it is a CLUSSDR, This is second scenario. The channel has never been connected. And QM is connected to repository. Inspite of this, the NumberofMessageExitsDefined is coming as 0. In the receiver channel there is ExitName and ExitData Present. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of David C. Partridge Sent: Wednesday, August 25, 2004 4:22 PM To: [EMAIL PROTECTED] Subject: Re: PMQCD MsgExitPtr value is coming as Null Is this a SDR chl or a CLUSSDR? If latter, AND the CLUSRCVR channel has an exit coded, AND the channel has connected at least once, then you have an MQ BUG. If the channel has never been connected, this is to be expected, as you need to have connected to the repository at least ONCE for your QM to know what the CLUSRCVR channel definition is. Dave -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Shuba P.K. Sent: 25 August 2004 10:58 To: [EMAIL PROTECTED] Subject: Re: PMQCD MsgExitPtr value is coming as Null MQCD.Version value is 7. But when I try to get the value of MQCD.MsgExitsDefined it is 0. Whether in the receiver channel there is an exit name or not. What do I do?? -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of David C. Partridge Sent: Wednesday, August 25, 2004 3:00 PM To: [EMAIL PROTECTED] Subject: Re: PMQCD MsgExitPtr value is coming as Null If MQCD.Version =4 then the first thing to check for a given exit is HOW MANY exits of a given type there are. For example check MQCD.MsgExitsDefined. If 0 then there aren't any. If non-zero then follow MsgExitPtr (worth checking for null pointer - just in case). If you want to apply an exit in the case where there aren't any, you need to allocate the memory (at MQXR_INIT time), fill in the MQCD fields at MQXR_AUTO. time, and release the memory at MQXR_TERM time. If you want to ADD an addnl exit then life is of course more complex ... Dave 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
Re: Queue Indexing on Distributed Platforms
IIRCthe queues are always indexed on distributed. Dave
Re: Queue Indexing on Distributed Platforms
Rob As far as I know, based on my (possibly faulty) memory of some discussions with the Hursley folks a couple or three years back, the way the queue file on disk is constructed on distributed means that it is always indexed to some degree, however I defer to any MQ mavens who may know better. On 390, the way queues are stored on the page sets is such that indexing doesn't come free, and so it's configurable (with a cost as the QM starts up). Dave 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: Queue Indexing on Distributed Platforms
In this context, distributed probably only means Windows and mainstream Unix. Dave -Original Message- From: David C. Partridge [mailto:[EMAIL PROTECTED] Sent: 18 August 2004 15:42 To: MQSeries List Subject: RE: Queue Indexing on Distributed Platforms Rob As far as I know, based on my (possibly faulty) memory of some discussions with the Hursley folks a couple or three years back, the way the queue file on disk is constructed on distributed means that it is always indexed to some degree, however I defer to any MQ mavens who may know better. On 390, the way queues are stored on the page sets is such that indexing doesn't come free, and so it's configurable (with a cost as the QM starts up). Dave 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: Shared Library Problem
This sounds like an obscure problem with the MQ data conversion code. Remember that when MQ is looking to do data conversion, if the data format isn't a built-in one, then MQ looks for a shared library with the same name as the data format to be converted (or that name with _r appended for re-entrant threaded code). The fact that MQSTR happens to be the name of the standard MQFMT_STRING built-in format strikes me as no coincidence. Dunno what's wrong though. HTH Dave 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: MACZ SupportPack 64bit HPUX Client Libs
We were very successfully running the AIX version of the 64-bit client support pack on an AIX 5.2 system with the QM on the same system - what's more I can't see any reason whatsoever that this shouldn't work for HP! After all the client is running in its own 64-bit process and communicating to the QM using TCP - why on earth shouldn't it work? What's more one of our major banking clients is now running this in production. Cheers, David C. Partridge Technical Products Director Primeur Security Services Tel: +44 (0)1926 511058 Mobile: +44 (0)7713 880197 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
No posts since Wednesday at 21:03?
I've not received anything from the list since 21:03 on Wednesday This seems odd - or has everyone really gone to sleep!? Regards, David C. Partridge Technical Products Director Primeur Security Services Tel: +44 (0)1926 511058 Mobile: +44 (0)7713 880197 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: DLQ message - RC2119 from UNIX MCA
If this was an AIX qmgr, then if you hadn't installed the bos iconv tables (I can't remember the smit component name), then you wouldn't have the relevant xlate tables as MQ on AIX doesn't install them - you have to. Dave 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: WBIMB SQLCODE
Bob, I can only suggest that you open a PMR, and be prepared to fight a battle royal to try to get IBM to change their mind, or at least to suggest the new right way to code this stuff. Dave 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: ^_^ meay-meay!
Dennis - looks like you caught a virus on your PC Dave 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: MACZ SupportPack 64bit HPUX Client Libs
Strange - I can't comment for sure on the HP version, but the AIX version of the 64 bit client will co-reside on the same machine as the MQ 5.3 server. So I'd suggest that it's PMR time. Dave -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Potkay, Peter M (ISD, IT) Sent: 04 August 2004 15:45 To: [EMAIL PROTECTED] Subject: MACZ SupportPack 64bit HPUX Client Libs http://www-1.ibm.com/support/docview.wss?rs=203uid=swg24005901loc=en_UScs =utf-8lang=en I have an HP-UX server running a queue manager at 5.3 CSD07 at 32bit. The app needs to run at 64bit. They are OK running as an MQClient even though thet are local to the QM. The server will allow both 32bit and 64bit apps to run. But MQ will not allow 5.3 (the QM) to run on the same machine as 5.2 (the client if I compile it with the MACZ libs). Why in the world would the support pack, released after 5.2 was no longer supported, be based on 5.2? Any rumors as to when the server version of MQ for HPUX will allow 64bit? Or if this support pack will be rereleased based on 5.3? Short of uninstalling 5.3 MQ server and reinstalling 5.2 client only, which isn't officially supported, and having the QM installed on a separate server (more $$$), am I S.O.L? Peter Potkay MQSeries Specialist The Hartford Financial Services [EMAIL PROTECTED] x77906 IBM MQSeries Certified 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: MACZ SupportPack 64bit HPUX Client Libs
Are you sure that you're compiling and linking the client app correctly for 64 bit? I think for a regular app (not a shared lib) you need to use: c89 +DD64 -c -D_HPUX_SOURCE -o appl.o appl.c -I/opt/mqm/inc64 You also need to link with options: for non-threaded: +noenvvar appl.o -o appl -L/opt/mqm/lib64 -L/usr/lib/pa20_64 -lmqic for threaded: +noenvvar appl.o -o appl -L/opt/mqm/lib64 -L/usr/lib/pa20_64 -lmqic_r -lpthread (NOTE: Not sure about the +noenvvar option - probably only relevant for suid appls.) This is derived from the instructions on how to link MCA exits for 64bit clients which can be found at: http://www-1.ibm.com/support/docview.wss?rs=171context=SSFKSJq1=1172220ui d=swg21172220loc=en_UScs=utf-8lang=en+en I just modified this for linking an application - so if I got it wrong I apologise Note also that the above instructions are in error as they say to use: -I/opt/mqm/inc rather than -I/opt/mqm/inc64 on the compile options. Dave 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: problem in reading messages
Check the options you've specified on your call to accessQueue(). It says you've supplied conflicting options. PS can those of you who post in html please strongly consider posting in plain text. Dave 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: Client Channel Definition Tables Files
Do you have either of MQCHLLIB or MQCHLTAB environment variables set? These will impact where the table is created, and what it is called respectively. Dave 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: Moving the list server ?
I use both - but mostly the list server. I prefer to keep the email subscription format. Dave 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 on Windows with shared disks
Paul, What is the block on using MSCS - that looks to be the exact tool you need! Dave 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: Very Basic VMS questions
MQ 2.2 is almost anantique - perhaps you should try to auction it off :-) Dave
Re: MO71 SupportPac Source Code
Paul, If the powers that be do allow the source out without charge, why not make it open source and put it on one of the open source CVS repositories? Cheers Dave -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Paul Clarke Sent: 13 July 2004 11:07 To: [EMAIL PROTECTED] Subject: MO71 SupportPac Source Code Hi, Over the years I've received a number of requests for the source code for my MO71 SupportPac and I've always had to say no. However, I am now investigating the possibility (depending on demand etc) of making the source code available either for free or for a small fee. If you're interested in obtaining the source code I would appreciate it if you could send me a note directly rather than via the listserver. Why would you want the source ?, well... 1/ Since there's no support agreement it's the only way you could run it in production. 2/ You'd like to add a feature which I've been too slow adding myself 3/ You want to remove features to stop those pesky users doing something they shouldn't 4/ You're just curious about how something has been done. 5/ You're convinced you can make a better job of it than I have. Cheers, Paul. Paul G Clarke WebSphere MQ Development IBM Hursley 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: encryption messages
You have a number of options depending of the level of MQ you are running, and whether you need to have the messages encrypted on the queues as well as while traversing the channels. If you're only concerned to protect data flowing over the channel: a) If running MQ 5.3, and the free SSL implementation of channel security is adequate to meet your needs, then you can go this route. Your choice of algorithms may be constrained depending on the platform, and it doesn't e.g. compress data b4 doing crypto - which may pay off in throughput on the channel. Not as function rich as option b) nor as flexible, but it is free. b) If not running MQ 5.3 or you want additional capabilities look at something like our Data Secure for WebSphere MQ (DSMQ) product which uses MQ channel exits to provide the following services: 1) Peer Entity Authentication according to X.509 standard as channel starts, setting of MCA User of srvrconn channel instance based on credentials of the client for all platforms (not just 390), session keys set up for message or send/receive exits. 2) Data Authentication (none, MD5 or SHA-1 HMAC) 3) Data Encryption (none, RC4, DES, 3DES) 4) Data Compression (before data auth and encryption if chosen) which we refer to as the Peer to Peer (P2P) component of the DSMQ product. This option has been chosen by many financial organisations around the world.Other vendors are also active in this space. If you also require that data in the MQ queues (and logs) be protected without requiring modifications to your applications, then you will need to purchase a product that does this. The End to End (E2E) component of our DSMQ product provides this capability without requiring you to modify applications. Messages may be compressed (or not), digitally signed or signed and encrypted for specific recipient(s).This is available for MQ 2.1, 5.2 and 5.3 on 390, and for 5.3 on distributed platforms. Tivoli also has a product in this area (AMBI). FWIW, in my opinion, it is far too complex and has far too much in the way of pre-requisites and administrative overhead by comparison with DSMQ, but as I was the product architect and designer for DSMQ E2E, I would be biased I guess! Oh yes, TAMBI costs more too unless you've got some huge corporate discount :-). Regards, David C. Partridge Technical Products Director Primeur Security Services Tel: +44 (0)1926 511058 Mobile: +44 (0)7713 880197 -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of LEONARDO VALENTINO CRUZ Sent: 12 July 2004 12:49 To: [EMAIL PROTECTED] Subject: encryption messages --- Recebido de POINFOR.UX90825 351.21.3117492 04-07-12 - [EMAIL PROTECTED] Hi all, An auditors want to do encryption of messages that across channel of MQseries. Scenario: Aix encrypt messages, and send by channel to MQSeries of the OS/390 MqSeries in OS/390 with CICS decrypt messages, and process and encrypt the response and send by sender channel to AIX Aix decrypt messages and receive a message. Anyone help ? thanks Leonardo Cruz Sistemas CICS/MQSeries [EMAIL PROTECTED] Av. da Liberdade, 222 - 9º Piso 1250-148 Lisboa 351 21 311 7492 BBVA Portugal DISCLAIMER This message is intended exclusively for the named person. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of 'BBVA'. Please note that internet e-mail neither guarantees the confidentiality nor the proper receipt of the message sent. If the addressee of this message does not consent to the use of internet e-mail, please communicate it to us immediately. 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: File transfer
Take a look at support pack MA0M which points to: http://www.primeur.com/products/xsp/xsp.html which is a freeware open source FT tool for MQ. Cheers Dave -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Kerry Swemmer Sent: 12 July 2004 08:41 To: [EMAIL PROTECTED] Subject: File transfer Hi All, Does anyone have some sample code, suggestions or recommended techniques that they are willing to share to do file transfer of large (120MB) drawing files over MQ? Thanx, Kerry Swemmer T-Systems South Africa (Pty) Ltd Database Administrator Computing and Desktop Services Address: c/o DaimlerChrysler, 7 Settlers Way, East London, South Africa Postal Address: PO Box 671, East London, 5200 Phone: +27 (43) 706 2549 Fax:+27 (43) 706 2085 Mobile: +27 (83) 657 4151 E-mail: [EMAIL PROTECTED] Internet: www.t-systems.co.za Any views expressed in this message are those of the individual sender, and T-Systems South Africa (Pty) Ltd accepts no liability therefore, except where the sender specifically states them to be those of T-Systems South Africa (Pty) Ltd. Although this message has been scanned for the possible presence of computer viruses prior to despatch, T-Systems South Africa (Pty) Ltd cannot be held responsible for any viruses or other material transmitted with, or as part of, this message. 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: Message Exit Syncpoint
You should probably change your code so that you use the same persistence for your message as the message you're tracking (or whatever), and set the put message option for syncpoint to either: MQPMO_SYNCPOINT or MQPMO_NO_SYNCPOINT depending on whether or not the message is persistent. Cheers Dave -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Narasimhareddy_V Sent: 05 July 2004 10:43 To: [EMAIL PROTECTED] Subject: Re: Message Exit Syncpoint Hi Paul Thank you for the below information, I have corrected the NPMSPEED properties,after this it worked for me.. Regards Narasimha Reddy -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Paul Clarke Sent: Monday, July 05, 2004 2:22 PM To: [EMAIL PROTECTED] Subject: Re: Message Exit Syncpoint Narasimha, Are you certain that the original message is being put under syncpoint ?. Note that for a NPMSPEED(FAST) channel only persistent messages will be put under syncpoint. Does your exit decide whether to use syncpoint or not based on the persistence of the original message ? Cheers, P. Paul G Clarke WebSphere MQ Development IBM Hursley MQSeries List [EMAIL PROTECTED] wrote on 04/07/2004 14:25:46: Dear All, In our system,we have written Channel Message Exit which takes a copy of message coming on requestor channel putting it into Alias Queue with sync point (i.e, keeping this transaction into MCA's Unit Of Work). we are not committing inside the Channel message exit. In this case the message is deleverd to the destination queue by MCA properly, but the copy we have put to our queue is not getting comitted. But this should not happen according to the following information specified in the WebSphere MQ Intercommunication Manual(page 630). An exit runs in the same thread as the MCA itself. It also runs inside the same unit of work (UOW) as the MCA because it uses the same connection handle. Therefore, any calls made under syncpoint are committed or backed out by the channel at the end of the batch. For example, one channel message exit program can send notification messages to another and these messages will only be committed to the queue when the batch containing the original message is committed. Therefore, it is possible to issue syncpoint MQI calls from a channel message exit program. Anybody experienced with these this kind of issues. Any comments on this are highly appreaciated.. Thanks Regards Narasimha Reddy ** This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated. ** 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 ** This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated. ** 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 issues with dead letter queue
It's clear you know Murphy's law :-) Now how about O'Reilly's law which states very simply: Murphy was an optimist. Dave 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: MQSeries on Mainframes OS/390
On 390 you don't use a DLL. You use a normal load module, and only specify
the (up to 8 character) name of the load module in the channel definition.
The DD CSQXLIB will be where MQ looks for this load module.
As regards specifying the message data you do it just the same way you do on
the other platforms using the TSO panels or CSQUTIL (I think):
ALTER CHANNEL(channelname) CHLTYPE(chltype) MSGDATA('whatever')
or if multiple exits are in use:
ALTER CHANNEL(channelname) CHLTYPE(chltype) MSGDATA('data for exit1','data
for exit2')
Dave
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: Fw: Red Hat Linux 9
Paul, Thanks again Dave 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: Command Server Working Mechanisms
The only tricky part is to edit the amqpcsea binary to make it look at some queue *other than* the command queue. Now that's a nasty hacker's trick GRIN ... Dave 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: Fw: Red Hat Linux 9
Thanks Paul, I found a Technote that mentioned another environment variable that could be used instead: export AMQ_THREADMODEL_RESET=1 Is it preferable to use this e.v. rather then LD_ASSUME_KERNEL, and if so what values are available for it and what is their impact? Thanks again Dave -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Paul Clarke Sent: 29 June 2004 15:54 To: [EMAIL PROTECTED] Subject: Re: Fw: Red Hat Linux 9 David, I spoke to one of our Linux guys and this was his response there are 2 possible values you can set in LD_ASSUME_KERNEL. Both are supported by MQ. 2.4.19 Linuxthreads with floating stacks 2.2.5 Linuxthreads without floating stacks In order to use MQ on Red Hat 9 (or any NPTL based distribution) you must use one of these settings and have at least MQ CSD 5 installed. The LD_ASSUME_KERNEL variable must be set in the enviornment when executing any of the mq administration commands (crtmqm, strmqm, runmqsc etc). (Note: Also if you have trouble installing MQ then try setting LD_ASSUME_KERNEL before executing the 'rpm' installation commands) MQ applications (linked with libmqm.so or libmqm_r.so) must also set LD_ASSUME_KERNEL to one of the values, however client applications (libmqic.so or libmqic_r.so) can run without setting LD_ASSUME_KERNEL. I hope this helps. So do I, Cheers, P. Paul G Clarke WebSphere MQ Development IBM Hursley - Forwarded by Paul Clarke/UK/IBM on 29/06/2004 12:24 - David C. Partridge [EMAIL PROTECTED] Sent by: MQSeries List [EMAIL PROTECTED] 29/06/2004 12:10 Please respond to MQSeries List To [EMAIL PROTECTED] cc Subject Red Hat Linux 9 I know there was a discussion about this while back, and IIRC the consensus was that you should set LD_ASSUME_KERNEL=2.2.5 to run MQ 5.3 on RHL 9.0. Is this really the right value - or should I be using LD_ASSUME_KERNEL=2.4.1? The reason I ask this is that MQ 5.3 is running fine on my RHL 8 system with kernel level 2.4.20 with no specific LD_ASSUME_KERNEL settings and should therefore be using the floating stacks version of LinuxThreads by default (rather than the original LinuxThreads version which a 2.2.5 value would force). Has this changed with recent CSDs (i.e. does MQ 5.3 plus CSD?? now have the fixes to work correctly with both LinuxThreads and NPTL?)? Do user applications using the QM need this setting or is it just the queue manager processes? What about the IBM JDK/JRE? Does that need this as well? Thanks, 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 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: MQSeries Channel Exits on AS400
What made you think you can use AS/400 CL for a msgexit? The Intercommunication
manual is very specific:
The exit is a program object written in the C/400(R), Integrated Language
Environment(R) (ILE) COBOL/400(R) or ILE RPG/400(R) language. The exit program names
and their libraries are named in the channel definition.
Observe the following conditions when creating and compiling an exit program:
The program must be made thread safe and created with the C/400, ILE RPG/400, or ILE
COBOL/400 compiler. For ILE RPG you must specify the THREAD(*SERIALIZE) control
specification, and for ILE COBOL you must specify SERIALIZE for the THREAD option of
the PROCESS statement. The programs must also be bound to the threaded WebSphere MQ
libraries: QMQM/LIBMQM_R in the case of C/400 and ILE RPG/400, and AMQ0STUB_R in the
case of ILE COBOL/400. For additional information about making RPG or COBOL
applications thread safe, refer to the appropriate Programmer's Guide for the
language.
WebSphere MQ for iSeries requires that the exit programs are enabled for teraspace
support. (Teraspace is a form of shared memory introduced in OS/400 V4R4.) In the case
of the ILE RPG and COBOL compilers, any programs compiled on OS/400 V4R4 or later are
so enabled. In the case of C, the programs must be compiled with the TERASPACE(*YES
*TSIFC) options specified on CRTCMOD or CRTBNDC commands.
An exit returning a pointer to its own buffer space must ensure that the object
pointed to exists beyond the timespan of the channel-exit program. In other words, the
pointer cannot be the address of a variable on the program stack, nor of a variable in
the program heap. Instead, the pointer must be obtained from the system. An example of
this is a user space created in the user exit. To ensure that any data area allocated
by the channel-exit program is still available for the MCA when the program ends, the
channel exit must run in the caller's activation group or a named activation group. Do
this by setting the ACTGRP parameter on CRTPGM to a user-defined value or *CALLER. If
the program is created in this way, the channel-exit program can allocate dynamic
memory and pass a pointer to this memory back to the MCA.
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Shuba
P.K.
Sent: 24 June 2004 13:06
To: [EMAIL PROTECTED]
Subject: MQSeries Channel Exits on AS400
Hi All,
Requirement:
I have a setup that has one RemoteQueue Definition, Transmission Queue, Sender,
Reciever channel pair. When the message moves across a channel, I want this Message
Channel Exit program to get activated and do the processing. In the current setup my
original message goes to the destined queue on the other Queue Manager using
Channels.
This one can be accomplished in Windows and in AIX by using a dll(functionname) in the
message exit parameter of the channel defination.
As one of the MQ series manual for AS/400, it says we have to put the
Library/Programname.
Problem we are facing:
1. We created a simple CL program as
PGM
SNDBRKMSG MSG('It is working') TOMSGQ(JAGANNATH)
ENDPGM
We added this program name in the MSGEXIT parameter of the CRTMQMCHL command.
But when we are sending a message to this Q Manager from our Q Manager on NT then this
program is not executed (We confirmed this because we could not see any Break message).
2. We have the C codes which we had developed for the NT environment. Now we put the
same code in AS/400 and created a service program out of that. But we dont know what
all parameters it should get. Can any of you please help on this?
Regards,
Shuba.
{--?~ jvx2 j)b b.n +bvz'^v) ? ??K n?i^jm? 0[(~ ?`+r{m jH ' j A' j!
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: runmqlsr - 5 instances running ?
Depending on the platform what you may be seeing is all the active threads in the one listener process (with I think three active connections in this case). Do the PPID values all go back to the same runmqlsr process? If so then that would suggest that this is the case. What release of MQ is this and how are you starting the listener? If its 5.3 I'd expect one runmqlsr per QM, and on (or more) amqrmppa processes with multiple threads. David -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Benjamin F. Zhou Sent: 22 June 2004 12:49 To: [EMAIL PROTECTED] Subject: runmqlsr - 5 instances running ? Hi, I'm replacing amqcrsta with runmqlsr. According to the insight I got from the Vegas conference, and a FAQ from IBM: ..., a SINGLE listener can now handle an unbounded number of connections... However, whenever I start runmqlsr, a ps -aef | grep runmqlsr shows five instances of it running. Is this the default behavior? Can anyone explain why? thanks, Benjamin F. Zhou Technical Specialist MessagingIntegration Supp. 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
Re: amqcrsta processes
Clients that aren't issuing an MQDISC perhaps? Dave 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: Channel exits on HP11 and HP 11.11
Good call - we suggested that DCE be removed, and after IBM made the *same* suggestion, they removed MQ 5.3 with DCE (luckily they weren't using DCE) and reinstalled 5.3 without DCE. The exits now load fine. Thanks David -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Egner, Dan Sent: 15 June 2004 18:33 To: [EMAIL PROTECTED] Subject: Re: Channel exits on HP11 and HP 11.11 David, SUMMARY: It might be DCE. DETAILS: I went to the BMC support web site www.bmc.com/support.html and I went to the Resolution Knowledge Database. and entered Exec format error as search criteria. It found resolution 141357, which says: Symptom/Question Not getting any qstats. All qstats show up as zero. Exec format error message on bmcmqx.sl appears on AMQERR01.LOG. The BMC MQSeries Extensions service does not start. BMC MQSeries Extensions are not enabled or started. Additional Problem or Contact Information Here is what you see in /var/mqm/errors: --- 11/20/02 09:36:13 AMQ6188: The system could not dynamically load the shared library '/opt/BMCS/mq/bin/bmcmqx.sl' due to a problem with the library. The errno was 8 and the error message was 'Exec format error'. The queue manager will continue without this library. EXPLANATION: This message applies to AIX, HP-UX and Linux systems. The shared library '/opt/BMCS/mq/bin/bmcmqx.sl' failed to load correctly due to a problem with the library. ACTION: Check that the library exists and is in the correct place with the correct file permissions etc. and has not been corrupted. --- Here is what you see if you run a tusc trace (HP-UX only) $ ./tusc amqzxma0 -m MYQMGR tusctrace4.txt /usr/lib/dld.sl: Can't shl_load() a library containing Thread Local Storage: /usr/lib/libpthread.1 /usr/lib/dld.sl: Exec format error AMQ6188: The system could not dynamically load the shared library '/opt/BMCS/mq/bin/bmcmqx.sl' due to a problem with the library. The errno was 8 and the error message was 'Exec format error'. The queue manager will continue without this library. The system could not load the module '/opt/BMCS/mq/bin/bmcmqx.sl' for the installable service 'NameService' component 'BMC.MQSeries.Extensions'. The system return code was 536895880. The Queue Manager is continuing without this component. WARNING! If you run the tusc trace as above, DO NOT USE CONTROL C to stop the queue manager. Use endmqm -i per normal. Resolution The problem happened on HP-UX 11.11. When DCE (Distributed Computing Environment) was removed from the computer the problem went away and qstats were collected just fine. == Regards, Dan Egner IBM WebSphere MQ V5.3 System Administration Certified Product Support BMC Software, Inc -Original Message- From: David C. Partridge [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 15, 2004 11:25 AM To: [EMAIL PROTECTED] Subject: Channel exits on HP11 and HP 11.11 Don't know if anyone has seen this before or not. One of our customers is getting Exec format error messages reported in the MQ error logs for our channel exits on his HP_UX 11 system after upgrading from MQ 5.2 to MQ 5.3. The exits were working prior to the upgrade. The code works just fine on our HP_UX 11 system with MQ 5.3, the only substantive difference might be the our current test systems are HP 11.11 and the customer is running HP 11.00. When the problem occurs, stderr contains: /usr/lib/dld.sl: Can't shl_load() a library containing Thread Local Storage: /usr/lib/libpthread.1 /usr/lib/dld.sl: Exec format error AMQ6188: The system could not dynamically load the shared library '/var/mqm/exits/mqppsx.sl' due to a problem with the library. The errno was 8 and the error message was 'Exec format error'. The queue manager will continue without this library. I think this is (probably) an HP 11 problem with the loader or some such, but strangely this *only* started happening when the customer upgraded from MQ 5.2 to MQ 5.3. Cheers, David C. Partridge Technical Products Director Primeur Security Services Tel: +44 (0)1926 511058 Mobile: +44 (0)7713 880197 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 and Windows 2003 security
Is this one of those things where you need to use DCOMCNFG to set the domain password for MUSR_MQADMIN, now that the local MUSR_MQADMIN has been deleted (I assume it has been)? Dave 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
Channel exits on HP11 and HP 11.11
Don't know if anyone has seen this before or not. One of our customers is getting Exec format error messages reported in the MQ error logs for our channel exits on his HP_UX 11 system after upgrading from MQ 5.2 to MQ 5.3. The exits were working prior to the upgrade. The code works just fine on our HP_UX 11 system with MQ 5.3, the only substantive difference might be the our current test systems are HP 11.11 and the customer is running HP 11.00. When the problem occurs, stderr contains: /usr/lib/dld.sl: Can't shl_load() a library containing Thread Local Storage: /usr/lib/libpthread.1 /usr/lib/dld.sl: Exec format error AMQ6188: The system could not dynamically load the shared library '/var/mqm/exits/mqppsx.sl' due to a problem with the library. The errno was 8 and the error message was 'Exec format error'. The queue manager will continue without this library. I think this is (probably) an HP 11 problem with the loader or some such, but strangely this *only* started happening when the customer upgraded from MQ 5.2 to MQ 5.3. Cheers, David C. Partridge Technical Products Director Primeur Security Services Tel: +44 (0)1926 511058 Mobile: +44 (0)7713 880197 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: Channel exits on HP11 and HP 11.11
It was built on HP 11, so no. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Wyatt, T. Rob Sent: 15 June 2004 18:00 To: [EMAIL PROTECTED] Subject: Re: Channel exits on HP11 and HP 11.11 David, Long shot here, but does the exit need to be relinked after the upgrade? Check out: http://publibfp.boulder.ibm.com/epubs/html/amqcac05/amqcac050m.htm#Header_47 -- T.Rob -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of David C. Partridge Sent: Tuesday, June 15, 2004 12:25 PM To: [EMAIL PROTECTED] Subject: Channel exits on HP11 and HP 11.11 Don't know if anyone has seen this before or not. One of our customers is getting Exec format error messages reported in the MQ error logs for our channel exits on his HP_UX 11 system after upgrading from MQ 5.2 to MQ 5.3. The exits were working prior to the upgrade. The code works just fine on our HP_UX 11 system with MQ 5.3, the only substantive difference might be the our current test systems are HP 11.11 and the customer is running HP 11.00. When the problem occurs, stderr contains: /usr/lib/dld.sl: Can't shl_load() a library containing Thread Local Storage: /usr/lib/libpthread.1 /usr/lib/dld.sl: Exec format error AMQ6188: The system could not dynamically load the shared library '/var/mqm/exits/mqppsx.sl' due to a problem with the library. The errno was 8 and the error message was 'Exec format error'. The queue manager will continue without this library. I think this is (probably) an HP 11 problem with the loader or some such, but strangely this *only* started happening when the customer upgraded from MQ 5.2 to MQ 5.3. Cheers, David C. Partridge Technical Products Director Primeur Security Services Tel: +44 (0)1926 511058 Mobile: +44 (0)7713 880197 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: MQINQ in a clustered environment
You can only issue an MQINQ against an object that exists on the local QM (or is the local QM). Dave
Re: SVRCONN channel question
Each connection will run in its own thread in an amqrmppa process, so they won't get in each other's way unless there's contention for exclusive access to a queue. There's no any specific benefit in having some clients connect on one channel name, and some on another unless they have different access requirements. Dave 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: Data Conversion
As a general rule do not use in channel conversion - make the application that MQGETs the message use conversion - avoids redundant conversion at the least. Also remember that only MQSTR format messages would be converted. Dave -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Ward, Mike S Sent: 11 May 2004 23:51 To: [EMAIL PROTECTED] Subject: Data Conversion Hi all, I have a question about MQ data conversion and I am hoping someone out there has an answer for me. I have a Q mgr set up on Z/OS and one set up on Windows. I have verified that both sender channels on either side are set to data conversion yes. If I send a message from Z/OS(Via PQEDIT) to the windows side and use the rfhutil to read it from the q. It's still in EBCDIC format. If I send a message from the windows side(Via mqput2) and read it from the queue using PQEDIT the data looks like it's in ASCII format. I have been scratching my head over this all day. I made sure the sender channels are set to convert yes and I have stopped and restarted them to make sure they took. Does anyone have any idea's as to why this is occurring? I am at the 5.3 level csd 6 on windows and on z/os I am also at the 5.3 level and I thing equivalent to csd 3. Thanks in advance for any reply's 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: Remote Event Queues and Active Channels
Set the DISCINT on these channels to zero? Dave 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: Remote Event Queues and Active Channels
I guess the only way round this is to use a local agent to collect events and use an out of band (i.e. non MQ) transport to centralise the event data. I think this is what some of the commercial monitoring products do. Dave 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: Remote Event Queues and Active Channels
No this won't work - the channel exit you could use to suppress the event message would be in the message exit (MQCXP.ExitResponse=MQXCC_SUPPRESS_FUNCTION), and this exit will only be invoked once the channel is running - catch 22! Dave 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: Reason Code 2033.
Are you resetting the messageid and correlid when you move to browse next? If you don't, you'll be specifically looking for another message with the same message and correlation ids as the first one and the likely result will be a 2033. Also why do you INQ and then close, reopen and then browse? Why not just do a browse first and if you get a 2033, give up? Dave 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: Remote Event Queues and Active Channels
That would work - I think. D. 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: Application seeing 2009 (MQRC_CONNECTION_BROKEN) errors...
...on Solaris 8, MQ 5.3 CSD6 we found that 109147-24 was *not* ok (MQ abends within Solaris dlclose() code) , while 109147-27 was ok (even if the delta between the two versions did not include documented bug fixes that looked dlclose-related). Don't know if this is relevant to what you're seeing or not. Dave -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Vaic, Miroslav (GE Consumer Finance, consultant) Sent: 07 May 2004 13:16 To: [EMAIL PROTECTED] Subject: Re: Application seeing 2009 (MQRC_CONNECTION_BROKEN) errors... Thank you for the ideas. I would like to point out that there are no errors and no FDCs reported - neither at system or qmgr level. This is quite strange. MQ are running well, but the applications get error 2009. Miroslav. - Miroslav Vaic Project UFO - Universal Front-End Interfaces Team Telefon +420 224 442 080 GSM: +420 602 215 470 E-mail: [EMAIL PROTECTED] -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of David C. Partridge Sent: Friday, May 07, 2004 1:15 PM To: [EMAIL PROTECTED] Subject: Re: Application seeing 2009 (MQRC_CONNECTION_BROKEN) errors... Another point here. By any chance are you seeing Internal Error FDCs (e.g. too many open files)? If so you should probably review your kernel settings - see the MQ Quick Beginnings manual for Solaris. Dave 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: Application seeing 2009 (MQRC_CONNECTION_BROKEN) errors...
If you are referring to a problem with a conflict between MQ 5.3 and patches to the Solaris loader resulting in unexpected process terminations, then I believe that latest Solaris loader patch will work fine with MQ 5.3 and CSD05 or CSD06. There were problems with earlier Solaris loader patch levels. If this is not the problem you are referring to, then I think we'll need a chapter and verse description of the incompatibility you refer to, and probably you'll need to involve IBM support. Dave -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Vaic, Miroslav (GE Consumer Finance, consultant) Sent: 07 May 2004 10:24 To: [EMAIL PROTECTED] Subject: Re: Application seeing 2009 (MQRC_CONNECTION_BROKEN) errors... Dear MQ Specialists, Would anyone be able to comment the problem described below ? We have a very similar problem: We use WebSphere MQ 5.3 for Solaris (Solaris 5.8). There are about 100 applications connecting to MQ using the binding mode (ie server, ie local connections, NOT client connections through a channel). After we reach a certain load on the machine where the applications and MQ run, MQ starts returning error code 2009 to any MQI call. Due to the documentation this could happen if the QMGR goes down, nevertheless, we checked the QMGR, IP listener and logs and we cannot find any problem there. QMGR is running and in the log, there are no messages at all. What may be important, we do not have installed any higher CSD as there was a registered problem with a Solaris Patch (MQ patches and Solaris patches cannot coexist on the machine). We will try to remove the Solaris patch and install current CSD on MQ, if it helps. But, any comments would be welcome - has anyone seen this problem ? Does anyone have any advice ? Thanks in advance, Miroslav - Miroslav Vaic Project UFO - Universal Front-End Interfaces Team Telefon +420 224 442 080 GSM: +420 602 215 470 E-mail: [EMAIL PROTECTED] -Original Message- From: Antony Boggis [mailto:[EMAIL PROTECTED] Sent: Friday, October 24, 2003 8:47 PM To: [EMAIL PROTECTED] Subject: Application seeing 2009 (MQRC_CONNECTION_BROKEN) errors... I seeing (with intermittent regularity) a bunch of 2009 reson codes in server applications on site here. The applications concerned are server apps (C++, no Java), running on the same box as the queue manager and are using server bindings (linking with libmqm.so), and connect using MQCONN, supplying the queue manager name (there is no default queue manager defined). Additional info: * Solaris 5.8 * MQ 5.2 CSD06 (I know CSD07 is availbale) * Applications linked with libmqm.so * There are no MQ environment variables defined (no MQSERVER). * This host has only two queue managers defined. * The queue manager is a member of a cluster (six qmgrs total). I'm not getting anything obvious in the error logs (neither the global or the queue manager local). Nothing that would indicate a server error prior to the application getting a reason code of 2009. -- tonyB. 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: Application seeing 2009 (MQRC_CONNECTION_BROKEN) errors...
Another point here. By any chance are you seeing Internal Error FDCs (e.g. too many open files)? If so you should probably review your kernel settings - see the MQ Quick Beginnings manual for Solaris. Dave 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: CSD 6
Did you stop (hide) the button bar applet after using it to stop the MQSeries service? Dave -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Ward, Mike S Sent: 07 May 2004 13:39 To: [EMAIL PROTECTED] Subject: CSD 6 Hi all, I am trying to apply csd 6 to a 5.3 install on windows 2000. The install waits for all MQ applications and processes to complete. Then it says checking files please wait. Then it stalls and says Websphere MQ files are in use. Stop activity and retry. The message is AMQ4757. Can anyone help? I can't find any MQ running except the csd. Thanks. Mike S. Ward Jr. A.V.P. Information Technology Security Service Federal Credit Union (210)476-4600 [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: SYSTEM.DEFAULT.INITIATION.QUEUE Question
Trigger first or trigger every? If the latter, I suggest that youchange your app design to use trigger first and suck all messages from the triggeredqueues. Dave -Original Message-From: MQSeries List [mailto:[EMAIL PROTECTED]On Behalf Of R. Dirk TolsonSent: 06 May 2004 01:39To: [EMAIL PROTECTED]Subject: SYSTEM.DEFAULT.INITIATION.QUEUE QuestionI have a new message flow that is confusing me. The source is MQ 2.1 on MVS. Persistent messages are routed to MQ 5.3 on Solaris. Occaisonally an event occurs that throws a monkey wrench in things. Today MVS went down and the system had to be IPLed. For some reason a larger than normal number of messages were sitting in the XMIT queue, 24000. On the Unix side the messages were handled until the SYSTEM.DEFAULT.INITIATION.QUEUE reached its maximum depth of 1000, then everything stopped. By starting and stopping the qmgr I could force another 1000 or so messages to be processed until the SYSTEM.DEFAULT.INITIATION.QUEUE reached its max depth again. My main question is what is happening? When the init queue is full some kind of events seem to stop. I guess I could just bump the maximum depth of the init queue up to some ridiculous number, but that doesn't feel right. I seem to be missing a key principle here. Can anybody clue me in?
Re: Max no. of qmgrs
There probably is such a limit, and this will primarily be determined by disk space, and shared resources such as semaphores and open file limits and the like. However the return question I have is how many are you contemplating, and why do you want to host many QMs on the same box? Far better to have a few QMs with '000s of queues than many QMs with a few queues each. Dave -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of W Samuel Sent: 04 May 2004 14:52 To: [EMAIL PROTECTED] Subject: Max no. of qmgrs Hello, Is there a limit on the max number of queue managers that can run on a single host ? Regards WS Yahoo! Messenger - Communicate instantly...Ping your friends today! Download Messenger Now http://uk.messenger.yahoo.com/download/index.html 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: Message Tracking
Actually I mis-spoke myself. The API exit can be called *three times* for an MQGET, depending on exactly which entry point(s) you activate. 1) Before MQGET - typically use to log things like options pointer values and MQMD (did the developer remember to reset message id, correl id, ccsid etc.). The MQGET hasn't been issued at this point. 2) Before data conversion (but after the MQGET). IIRC this is always called if set up even if data conv not specified. 3) After data conversion. Dave -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Roger Lacroix Sent: 29 April 2004 19:02 To: [EMAIL PROTECTED] Subject: Re: Message Tracking Hi, So the difference in the data between calls 'before get' and 'after get' would be the data conversion (if the app did a get with convert) ? Or would the be just for timestamping how long the get call took? i.e. because 'before get' call would not have the message data yet. Regards, Roger Lacroix Quoting David C. Partridge [EMAIL PROTECTED]: Yes, that's *exactly* what I mean, so if you do 100 gets followed by a backout, the exit is called 200 times (for before get and after get entries) and then once before the backout and once afterwards. Dave -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Roger Lacroix Sent: 29 April 2004 16:03 To: [EMAIL PROTECTED] Subject: Re: Message Tracking Hi, Hummm, so are you suggesting that under SyncPoint the Api Exit is called twice: once for the get and then again for commit (or back). Hummm, most interesting. Regards, Roger Lacroix Capitalware Inc. http://www.capitalware.biz Quoting David C. Partridge [EMAIL PROTECTED]: The API Exit is invoked at MQCMIT and MQBACK time, but you'll have royal fun keeping track of what was committed and backed out it you are logging messages to see what happened. Dave 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
Re: Setmqaut on v5.1
And while you are at it - go straight to CSD06 or higher. Dave 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: Backout of failed a C++ Application
IIRC on MVS the default is COMMIT, not BACKOUT when the application fails Dave
Re: Message Tracking
The API Exit is invoked at MQCMIT and MQBACK time, but you'll have royal fun keeping track of what was committed and backed out it you are logging messages to see what happened. Dave 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: Message Tracking
Yes, that's *exactly* what I mean, so if you do 100 gets followed by a backout, the exit is called 200 times (for before get and after get entries) and then once before the backout and once afterwards. Dave -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Roger Lacroix Sent: 29 April 2004 16:03 To: [EMAIL PROTECTED] Subject: Re: Message Tracking Hi, Hummm, so are you suggesting that under SyncPoint the Api Exit is called twice: once for the get and then again for commit (or back). Hummm, most interesting. Regards, Roger Lacroix Capitalware Inc. http://www.capitalware.biz Quoting David C. Partridge [EMAIL PROTECTED]: The API Exit is invoked at MQCMIT and MQBACK time, but you'll have royal fun keeping track of what was committed and backed out it you are logging messages to see what happened. Dave 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: Can a MQ server act as MQClient?
Its not clear at all what you are trying to do and why you think that you need QM to act as a client. Can you explain why you think that you want QM1 to connect as a client, rather than having the QMs connected using (e.g.) sender and receiver channels. Perhaps if you described (in outline) the business problem you are trying to solve that would allow us to understand your thought processes. Dave 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: MsgId and CorrelId Conversion
Message Id and Correlation Id are defined to be BINARY data, not character data. MQ will never convert these, and IMHO, neither should you. If the application developer is assuming that they will be converted they are mistaken. Dave 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: Java and remote Dynamic reply q routing
IIRC the replytoqmgr is set to the putting QM if you leave it blank so if you create a dynamic reply queue and put a message with the reply queue name set, but not the reply to QM, then reply messages will go to the right place. Not intuitive I admit, as my first thoughts on this were that you needed to specify the reply to QM even if itwere the one you are running on. However, the documentation is quite specific: If the ReplyToQMgr field is blank, the local queue manager looks up the ReplyToQ name in its queue definitions. If a local definition of a remote queue exists with this name, the ReplyToQMgr value in the transmitted message is replaced by the value of the RemoteQMgrName attribute from the definition of the remote queue, and this value will be returned in the message descriptor when the receiving application issues an MQGET call for the message. If a local definition of a remote queue does not exist, the ReplyToQMgr that is transmitted with the message is the name of the local queue manager. Dave
More rebranding nonsense
You remember that the suits re-branded good 'ole MQSeries and WMQI (WBIMB or unofficially BIMBO). Well, they've now re-branded WAS Enterprise as WBISF (WebSphere Business Integration Server Foundation). At this rate no-one will know what anything is called anymore (perhaps that's the idea). Dave 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: Use channel exits or not?
Additional comments: Acquire the storage for you structure at MQXR_INIT time, and store the pointer in MQCXP.ExitUserArea. Make sure that you release the storage and clear the pointer at MQXR_TERM time. Do whatever processing you need at MQXR_MSG time (you'll probably want to know whether the message is inbound or outbound on the channel - look at MQCD.ChannelType to determine what type of channel this is. Dave 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: TCP/IP errors
Run, don't walk to: http://www-306.ibm.com/software/integration/support/supportpacs/individual/m a86.html and download the information about MQSeries and firewalls. HTH Dave 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: Use channel exits or not?
Each instance of a channel exit can hang any structures (or control blocks) that it needs to maintain state across invocations in MQCXP.ExitUserArea (store a pointer in here). You can store in this structure any hconn (n.b. you'll get MQRC_ALREADY_CONNECTED when you do the MQCONN, so just remember that you DO NOT do an MQDISC in this case) and any hobj's that you need (for writing to your audit queue e.g.). Therefore each instance of a channel exit is isolated from other instances even in a threaded channel model as in MQ 5.3 using the shared channel agent - just make sure your code is naturally re-entrant and don't store stuff between invocations anywhere but in the control block you store the pointer to in MQCXP.ExitUserArea (put another way don't use static variables or expect stack variables to hang around). Cheers Dave 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: Use channel exits or not?
Indeed so! :-) Dave 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
