Re: Change Timeout for MQCONN
Paul, The description for the registry entries can be found here: http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/ en-us/regentry/58804.asp?frame=true http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit /en-us/regentry/58804.asp?frame=true Try setting TcpMaxConnectRetransmissions to zero it should noticably reduce the connect timeout. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Meekin, Paul Sent: Wednesday, October 13, 2004 01:45 To: [EMAIL PROTECTED] Subject: Re: Change Timeout for MQCONN Thanks for the responses Ken and Rick. Ken, yes you are correct about what I am trying to achieve and thanks for the pointers to the registry values. I have tried the TcpMaxConnectRetransmissions one but so far it doesn't seem to make any difference. It certainly looks like the right parameter though so I'm assuming I'm doing something silly! The TcpInitialRTT parameter also looked relevant but unfortunately it says you can only increase it from the default of 3 seconds - not decrease it! Cheers, Paul -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Ken Woloschuk Sent: 08 October 2004 20:05 To: [EMAIL PROTECTED] Subject: Re: Change Timeout for MQCONN Rick, You probably are setting MQSERVER to point to an node which has TCP active but the qmgr is down. Then the response will be immediate because the target node TCPIP address is reachable but the qmgr is not. Try and set MQSERVER to a node with a TCPIP address that is not reachable and see what happens. I believe Paul wants to minimize the connect time so in the cas where the node is reachable but the qmgr is down his connect timeout will be immediate which should be a good thing. Otherwise, by tweaking the registry parameters, the connect time for the non-reachable case can be reduced. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Rick Tsujimoto Sent: Friday, October 08, 2004 12:07 To: [EMAIL PROTECTED] Subject: Fw: Change Timeout for MQCONN ooops. sent original reply to Ken instead of the list. - Forwarded by Richard Tsujimoto/Consultant-NewYork/CanonUSA on 10/08/2004 02:05 PM - Richard Tsujimoto/Consultant-NewYork/CanonUSA 10/08/2004 01:58 PM To [EMAIL PROTECTED] cc Subject Re: Change Timeout for MQCONN Link Notes:///8525684A007B83F3/DABA975B9FB113EB852564B5001283EA/39013E4BD0DD930B 85256F270061E75E If you take the sample program amqsget and specify a non-existent QMGR name, the program ends immediately with a 2058 reason code. I don't think that TCP/IP setting has any effect on Paul's problem. Ken Woloschuk [EMAIL PROTECTED] Sent by: MQSeries List [EMAIL PROTECTED] 10/08/2004 01:47 PM Please respond to [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject Re: Change Timeout for MQCONN For WXP or W2K look at the following registry entries: HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters TcpMaxConnectRetransmissions and HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\interface -name TcpInitialRTT For example, by setting TcpMaxConnectRetransmissions to 1 the connect should time out in about 10 seconds. Setting it to zero, the connect should time out in about 5 seconds. You'll need to reboot the windows box when you change these parameters. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Meekin, Paul Sent: Friday, October 08, 2004 07:39 To: [EMAIL PROTECTED] Subject: Change Timeout for MQCONN Hi all, I've got a Perl program which is trying to connect to a queue manager. If the QMgr is not active (or doesn't exist) the MQCONN seems to wait about 20 seconds before timing out - or maybe under the covers it's retrying. I'd like to reduce this timeout if possible. I thought about using the setsockopt() function as one of the options is SO_RCVTIMEO but unfortunately I need access to the actual socket structure which of course is buried in the MQ code. Anyone know of how I might achieve this? It's on Windows if that matters although I could probably run it on Unix if it makes a difference. Cheers, Paul 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: Change Timeout for MQCONN
For WXP or W2K look at the following registry entries: HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters TcpMaxConnectRetransmissions and HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\interface -name TcpInitialRTT For example, by setting TcpMaxConnectRetransmissions to 1 the connect should time out in about 10 seconds. Setting it to zero, the connect should time out in about 5 seconds. You'll need to reboot the windows box when you change these parameters. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Meekin, Paul Sent: Friday, October 08, 2004 07:39 To: [EMAIL PROTECTED] Subject: Change Timeout for MQCONN Hi all, I've got a Perl program which is trying to connect to a queue manager. If the QMgr is not active (or doesn't exist) the MQCONN seems to wait about 20 seconds before timing out - or maybe under the covers it's retrying. I'd like to reduce this timeout if possible. I thought about using the setsockopt() function as one of the options is SO_RCVTIMEO but unfortunately I need access to the actual socket structure which of course is buried in the MQ code. Anyone know of how I might achieve this? It's on Windows if that matters although I could probably run it on Unix if it makes a difference. Cheers, Paul 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: VMS MQClient Channel tab location and name configuration
When I did work with VMS using a V2 QMGR the environment variable MQCHLLIB didn't work as documented - I simply put the AMQCLCHL.TAB into the MQSeries top level directory with the correct permissions and clients were able to function. Can't remember if the MQCHLTAB had any effect - if it is effective then multiple channel tables could reside in mqs_root:[mqm] if that is where your top level directory is. Haven't used the v5.1 flavour of MQ on VMS so can't comment. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Gurney, Matthew Sent: Tuesday, October 05, 2004 11:53 To: [EMAIL PROTECTED] Subject: VMS MQClient Channel tab location and name configuration When resolving the location of the mq client channel tab file on a VMS host, which environment variables are relevant? The Clients manual states: MQCHLTAB - This specifies the name of the file containing the client channel definition table. On VM/ESA: GLOBALV SELECT CENV SETLP MQCHLTAB filename But what about MQCHLLIB, is this relevant on the VMS platform? How, as in what format, do I specify the security exit location in the channel definition? eg if it was a unix mq client I might specify the exit location as /opt/mqm/myexits/secexit.so(Verify), what notation would I use to explicitly locate a security exit for a VMS client? These questions relate to a VMS host making a mq client connection to a Solaris host running MQServer. Thanks, Matt. == This message is for the sole use of the intended recipient. If you received this message in error please delete it and notify us. If this message was misdirected, CSFB does not waive any confidentiality or privilege. CSFB retains and monitors electronic communications sent through its network. Instructions transmitted over this system are not binding on CSFB until they are confirmed by us. Message transmission is not guaranteed to be secure. == 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: Change Timeout for MQCONN
I tried the sample using the following: set MQSERVER=SYSTEM.ADMIN.SVRCONN/TCP/targetnode amqsgetc KEN.QL targetqmgr and the timeouts are as shown below. -Original Message-From: MQSeries List [mailto:[EMAIL PROTECTED]On Behalf Of Rick TsujimotoSent: Friday, October 08, 2004 12:07To: [EMAIL PROTECTED]Subject: Fw: Change Timeout for MQCONNooops. sent original reply to Ken instead of the list. - Forwarded by Richard Tsujimoto/Consultant-NewYork/CanonUSA on 10/08/2004 02:05 PM - Richard Tsujimoto/Consultant-NewYork/CanonUSA 10/08/2004 01:58 PM To [EMAIL PROTECTED] cc Subject Re: Change Timeout for MQCONNLink If you take the sample program amqsget and specify a non-existent QMGR name, the program ends immediately with a 2058 reason code. I don't think that TCP/IP setting has any effect on Paul's problem. Ken Woloschuk [EMAIL PROTECTED] Sent by: MQSeries List [EMAIL PROTECTED] 10/08/2004 01:47 PM Please respond to[EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject Re: Change Timeout for MQCONN For WXP or W2K look at the following registry entries:HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\ParametersTcpMaxConnectRetransmissionsandHKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\interface-nameTcpInitialRTTFor example, by setting TcpMaxConnectRetransmissions to 1 the connect shouldtimeout in about 10 seconds. Setting it to zero, the connect should time out inabout5 seconds. You'll need to reboot the windows box when you change theseparameters.-Original Message-From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Meekin,PaulSent: Friday, October 08, 2004 07:39To: [EMAIL PROTECTED]Subject: Change Timeout for MQCONNHi all,I've got a Perl program which is trying to connect to a queue manager. Ifthe QMgr is not active (or doesn't exist) the MQCONN seems to wait about 20seconds before timing out - or maybe under the covers it's retrying. I'dlike to reduce this timeout if possible.I thought about using the setsockopt() function as one of the options isSO_RCVTIMEO but unfortunately I need access to the actual socket structurewhich of course is buried in the MQ code.Anyone know of how I might achieve this? It's on Windows if that mattersalthough I could probably run it on Unix if it makes a difference.Cheers,PaulInstructions for managing your mailing list subscription are provided inthe Listserv General Users Guide available at http://www.lsoft.comArchive: http://vm.akh-wien.ac.at/MQSeries.archiveInstructions for managing your mailing list subscription are provided inthe Listserv General Users Guide available at http://www.lsoft.comArchive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Change Timeout for MQCONN
Rick, You probably are setting MQSERVER to point to an node which has TCP activebut the qmgr is down. Then the response will be immediate because the target nodeTCPIP address is reachable but the qmgr is not. Try and set MQSERVER to a nodewith a TCPIP address that is not reachable and see what happens. I believe Paul wantsto minimize the connect time so in the cas where the node is reachable but the qmgr is downhis connect timeout will be immediate which should be a good thing. Otherwise, by tweakingthe registry parameters, the connect time for the non-reachable case can be reduced. -Original Message-From: MQSeries List [mailto:[EMAIL PROTECTED]On Behalf Of Rick TsujimotoSent: Friday, October 08, 2004 12:07To: [EMAIL PROTECTED]Subject: Fw: Change Timeout for MQCONNooops. sent original reply to Ken instead of the list. - Forwarded by Richard Tsujimoto/Consultant-NewYork/CanonUSA on 10/08/2004 02:05 PM - Richard Tsujimoto/Consultant-NewYork/CanonUSA 10/08/2004 01:58 PM To [EMAIL PROTECTED] cc Subject Re: Change Timeout for MQCONNLink If you take the sample program amqsget and specify a non-existent QMGR name, the program ends immediately with a 2058 reason code. I don't think that TCP/IP setting has any effect on Paul's problem. Ken Woloschuk [EMAIL PROTECTED] Sent by: MQSeries List [EMAIL PROTECTED] 10/08/2004 01:47 PM Please respond to[EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject Re: Change Timeout for MQCONN For WXP or W2K look at the following registry entries:HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\ParametersTcpMaxConnectRetransmissionsandHKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\interface-nameTcpInitialRTTFor example, by setting TcpMaxConnectRetransmissions to 1 the connect shouldtimeout in about 10 seconds. Setting it to zero, the connect should time out inabout5 seconds. You'll need to reboot the windows box when you change theseparameters.-Original Message-From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Meekin,PaulSent: Friday, October 08, 2004 07:39To: [EMAIL PROTECTED]Subject: Change Timeout for MQCONNHi all,I've got a Perl program which is trying to connect to a queue manager. Ifthe QMgr is not active (or doesn't exist) the MQCONN seems to wait about 20seconds before timing out - or maybe under the covers it's retrying. I'dlike to reduce this timeout if possible.I thought about using the setsockopt() function as one of the options isSO_RCVTIMEO but unfortunately I need access to the actual socket structurewhich of course is buried in the MQ code.Anyone know of how I might achieve this? It's on Windows if that mattersalthough I could probably run it on Unix if it makes a difference.Cheers,PaulInstructions for managing your mailing list subscription are provided inthe Listserv General Users Guide available at http://www.lsoft.comArchive: http://vm.akh-wien.ac.at/MQSeries.archiveInstructions for managing your mailing list subscription are provided inthe Listserv General Users Guide available at http://www.lsoft.comArchive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Windows 2000 Server and CSD07 problem
See if a process has any of the MQSeries DLL's open. http://www.sysinternals.com has a utility called process explorer which can help. If you run it up choose the find option then find dll - enter mq and it should find all the processes with MQSeries dll's open. You can also try the find handle option and enter say ibm(if you installed MQ into \program files\ibm\websphere mq otherwise enter some other directory name in the MQSeries path) and all processes having any MQ related files open should be listed. Hope this is of some assistance. +++ -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Roger Lacroix Sent: Tuesday, June 22, 2004 13:58 To: [EMAIL PROTECTED] Subject: Windows 2000 Server and CSD07 problem Help please, Box: Windows 2000 Server SP4 (dual CPU) Today I installed WMQ v5.3 with CSD01 using Terminal Services (to D: drive of server) and the install went fine (I copied the CD to a local drive then did the install from it). As I said, everything went fine and I reboot the server. After the reboot, I downloaded CSD07. First I stopped the MQ Services and clicked 'Hide the icon'. Check Task Manager for any AMQ*** or RUNMQ*** tasks and there were none. Under Terminal Services launched the CSD07 (U200212A.exe) and goes fine until it gets to'Checking files; please wait' (the 2nd time). Then I get the following error: 'IBM WebSphere MQ files are in use. Stop activity and retry. (AMQ4757)' I have rebooted the server 2 twice now, stopped services, checked the Task Manager and I don't see anything MQ related running. I have NOT even defined a queue manager yet on this server!! Could it be a problem with Terminal Services?? Or is CSD07 like CSD06 where it wasn't fully baked by IBM? Anyone have an idea or comment? Regards, Roger lacroix Capitalware Inc. 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
FW: Is SUN's JMS messaging superior to MQSeries?
This didn't appear on the list so Iam forwarding it on ... -Original Message- From: mqteam [mailto:[EMAIL PROTECTED] Sent: Sunday, May 30, 2004 02:32 To: [EMAIL PROTECTED] Subject: Re: Is SUN's JMS messaging superior to MQSeries? Hello All, I have found at least a few flaws in the design of the experiment: 1) The use of a single connection to a queue manager (something that never happens in real life) 2) The use of only a single message size, when comparing products one should play with message sizes. 3) I failed to see tuning performed on the queue manager, when installing and creating a queue manager on a machine as the one described, one should tune the WMQ properly Last but not least, when you read the support pack JMS performance with WMQ 5.3 on Windows 2K (mp7d) you can see WMQ out performing itself in a different benchmark design. Now I am not saying that Sun Java System Message queue is not a good product, or that the benchmark is neither interesting nor insightful, I just find it a little out of touch with the how messaging applications work. Cheers Didi - Original Message - From: Ken Woloschuk [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, May 28, 2004 3:22 PM Subject: Is SUN's JMS messaging superior to MQSeries? I came across a report which claims that Sun's Java Message Queue software out-performs IBM's MQSeries. The report can be found at: http://wwws.sun.com/software/products/message_queue/wp_JMSperformance.pdf Can anyone comment on the validity of this report and are there any reports to the contrary - ie: showing that MQSeries performs better than Sun's product? 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
Is SUN's JMS messaging superior to MQSeries?
I came across a report which claims that Sun's Java Message Queue software out-performs IBM's MQSeries. The report can be found at: http://wwws.sun.com/software/products/message_queue/wp_JMSperformance.pdf Can anyone comment on the validity of this report and are there any reports to the contrary - ie: showing that MQSeries performs better than Sun's product? 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 with clearing a queue
How about using 'rsvmqtrn' to either commit or back out the UoW?? -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Tuesday, May 25, 2004 05:26 To: [EMAIL PROTECTED] Subject: Re: Problem with clearing a queue Gina, Sounds like the channel is Indoubt. Resolve the channel with the BACKOUT option. Then see if you can clear the queue. If this works i think you will need to reset the sequence number before starting the channel back up. Gina McCarthy [EMAIL PROTECTED]To: [EMAIL PROTECTED] .COMcc: Sent by: MQSeriesSubject: Re: Problem with clearing a queue List [EMAIL PROTECTED] n.AC.AT 05/25/2004 07:13 AM Please respond to gimccarthy Bill, Thanks for your response. The reason why I didn't get the 'in use' message is because the channel is down. There are no ipprocs/opprocs. The get/put are both enabled. I even went as far as to change the usage to normal...nothing is working. Regards, Gina -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, May 24, 2004 5:36 PM To: [EMAIL PROTECTED] Subject: Re: Problem with clearing a queue Well, for one thing, if the channel is still running, it has the transmit queue open for exclusive use. That means no other application can open the queue for input (to get messages). If the channel is stopped, It would have disabled gets on the queue when it went down, which has the same effect. You would have to re-enable gets on the queue before you can clear it. That said about xmit queues, I am surprised at the error, I would expect something different, like queue in use or something similar. Anyway, you may want to try ensuring the channel is down (stopped) and then use MQSC commands to re-enable the get attribute on the queue and see if that helps. Bill Anderson SITA Atlanta, GA Standard Messaging Engineering WebSphere MQ Service Owner 770-303-3503 (office) 404-915-3190 (cell) [EMAIL PROTECTED] http://www.mconnect.aero/ Gina McCarthy [EMAIL PROTECTED]To: [EMAIL PROTECTED] .comcc: Sent by: MQSeriesSubject: Problem with clearing a queue List [EMAIL PROTECTED] N.AC.AT 05/24/2004 04:43 PM Please respond to gimccarthy I have a queue on AIX 5.3 that has 25000 msgs in it. It is a transmit queue. One of the messages is 2.5M...too big. I cannot delete that message nor can I clear the queue. I get the following error: clear qlocal(OS4MQSP1) AMQ8143: WebSphere MQ queue not empty. Has any seen this? Any recommendations? Regards, Gina McCarthy 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 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 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 with clearing a queue
See the note on transmission queues at the following link: http://publibfp.boulder.ibm.com/epubs/html/csqzaj09/csqzaj090w.htm#HDRCLRQL -Original Message-From: MQSeries List [mailto:[EMAIL PROTECTED]On Behalf Of Gina McCarthySent: Monday, May 24, 2004 14:44To: [EMAIL PROTECTED]Subject: Problem with clearing a queue I have a queue on AIX 5.3 that has 25000 msgs in it. It is a transmit queue. One of the messages is 2.5M...too big. I cannot delete that message nor can I clear the queue. I get the following error: clear qlocal(OS4MQSP1) AMQ8143: WebSphere MQ queue not empty. Has any seen this? Any recommendations? Regards, Gina McCarthy
Re: CSD06 problems onWin2K server
The following link describes a situation similar to yours on a non-windows platform. It may still provide some insight into your problem: http://www-1.ibm.com/support/docview.wss?rs=0q1=AMQ5525uid=swg21165631loc =en_UScs=utf-8cc=uslang=en -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Monday, May 10, 2004 17:26 To: [EMAIL PROTECTED] Subject: Re: CSD06 problems onWin2K server Thanks for the advice... Will v5.3 install recognize the existing v5.1 data directory structure and convert correctly if I uninstall v5.1 first ??? Sid -Original Message- From: Adiraju, Rao [mailto:[EMAIL PROTECTED] Sent: Tuesday, 11 May 2004 7:28 AM To: [EMAIL PROTECTED] Subject: Re: CSD06 problems onWin2K server Hi Sid Recently I have upgraded two of our production WIN2K servers to V5.3 - CSD06 along with few development queue managers. And I haven't come across any such problems. However, I always adopt the approach of uninstalling previous versions (we had 5.2 then) and reinstalling V5.3. Only problem we have encountered is, which is a known bug, that MQ console was not saving the settings in the registry. For example, if you change port number on the listener, it will use the new port temporarily and once the box is rebooted it reverts back to old port number. Because the changes weren't saved in the registries. IBM has provided a fix for this - one dll has to be replaced with the latest version. No installs or upgrades are necessary - just replacing the DLL will the do the job. If I remember correctly, in V5.1 the security profiles are maintained in a flat file structure and where as in V5.3 they are part of SYSTEM.AUTH.DATA.QUEUE under control of OAM. May be something gone wrong in your conversion process of this data. Just food for thought. If it is possible try to remove the MQ software (clean uninstall) and then reinstall it and see if the problem disappears. If you want, you can start with empty authorisation rules and later on you can covert old rules/data in to the new world. Cheers Rao Adiraju WebSphere MQ Specialist The National Bank of NZ Ltd. Wellington - New Zealand Tel: +64-4-494 4299 Fax: +64-4-802 8509 Mbl: +64-211-216-116 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 9 May 2004 12:38 PM To: [EMAIL PROTECTED] Subject: CSD06 problems onWin2K server Howdy all, I am reposting this as I didn;t get a response to my last attempt and in light of the recent interest in CSD06. I have built a fresh Win2K server and installed v5.3 (upgrade over v5.1 installation) and everything worked fine untill I put csd06 on and the APAR fix IC39916 patch and after that the queue manager falls over while trying to start with an The Object Authority Manager has failed. error message is AMQ5525 Has anyone encountered this ? Sid Young Brisbane Australia 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 is confidential and may contain privileged material. If you are not the intended recipient you must not use, disclose, copy or retain it. If you have received it in error please immediately notify me by return email and delete the emails. Thank you. 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: CSD 6
Have a look at the following link: http://www-1.ibm.com/support/docview.wss?rs=0q1=amq4757uid=swg21157389loc =en_UScs=utf-8cc=uslang=en -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Ward, Mike S Sent: Friday, May 07, 2004 06: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: TCP error
Since you have a lot of clients having the save problem it may be that you have a network related problem?? The operating system is identifying that it has rejected the TCP operation because it was unable to perform the TCP action on the physical network. This results from conditions such as high traffic on the network, poorly configured network settings in the Windows machine NIC, improperly configured routers or gateways, and other types of network related issues(eg: router refreshes). Network troubleshooting should be done to determine why the client/server traffic resulted in the error, with investigation focusing on traffic volume, routing, and hardware configuration. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Thomas, Don Sent: Wednesday, April 28, 2004 06:54 To: [EMAIL PROTECTED] Subject: Re: TCP error My first question would be: are all of the clients running the same code? If so try and recreate the situation with a single client. At first blush it would seem to me that the clients aren't ending in a 'controlled' manner. Just a thought... Don Thomas EDS - PASC * Phone: +01-412-893-1659 Fax: 412-893-1844 * mailto:[EMAIL PROTECTED] -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Ruzi R Sent: Wednesday, April 28, 2004 7:47 AM To: [EMAIL PROTECTED] Subject: Re: TCP error We are at MQ 5.3 CSd06 on NT and have been getting this error quite frequently. I would be very much interested in any suggestions. Best regards, Ruzi --- Emile Kearns [EMAIL PROTECTED] wrote: 10054 WSAECONNRESET -- Connection reset by peer. This occurs when an established connection is shut down for some reason by the remote computer From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: 28 April 2004 10:30 AM To: [EMAIL PROTECTED] Subject: TCP error Howdy all, I have an NT4 server running MQ v5.1 that constantly generates recv call errors in the event log error number 10054. Errors are occuring every 3 seconds on average. Does anyone know how to fix this with the version I currently have ? Sid Young 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 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 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 not connect to queue manager
The permissions on authorization files, created by the OAM, are: S:RWD, O:RWD, G:RWD, W:R (ID=MQM, ACCESS=R+W+E+D+C) see the following for more info: http://www-306.ibm.com/software/integration/mqfamily/library/manualsb/amqqag 00/amqqag001q.htm#HDRUAF -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of David Awerbuch Sent: Monday, April 26, 2004 15:45 To: [EMAIL PROTECTED] Subject: Fwd: Re: can not connect to queue manager An update. I disabled the OAM as Ken suggested, and that has solved the problem, so I now know it is security related. So this still begs the question: how on VMS do I find out what the security violation is? Thanks, Dave A. --- David Awerbuch [EMAIL PROTECTED] wrote: Date: Mon, 26 Apr 2004 07:56:43 -0700 (PDT) From: David Awerbuch [EMAIL PROTECTED] Subject: Re: can not connect to queue manager To: Mqseries Messages [EMAIL PROTECTED] Roger Lacroix wrote: Did you issue the 'refresh security' from runmqsc (or whatever it is called for OpenVMS). Note: For earlier releases of MQ for Unix, you had to bounce to queue manager to pick up new security setting. (Strange but true.) Roger, there were no security setting changes made to this user. The user was created with the MQM rights, but as a habit I restarted the qm anyway, to no avail. Ken Woloschuk wrote: You could try and disable the OAM and see if there are other authorization issues like file/directory permissions. There's only one problem - on VMS you define a logical PRIOR to creating the queue manager which disables the OAM for the life of the queue manager. This may be beneficial if you can create a test queue manager which has the 2035 return for the given userID. The following link discusses the OAM and VMS: http://www-306.ibm.com/software/integration/mqfamily/library/manualsb/amqqag 00/amqqag001m.htm#HDRUTOAM Ken, that sounds like sound advise - I'll disable the OAM and see what happens. Gunther Jeschawitz wrote: On UNIX systems, you have to be a member of the group mqm to start runmqsc. You don't need any other authority. Maybe it's the same on OpenVMS. The userid has the MQM rights (this is what is required under OpenVMS). I was trying to find out where to get more details on the security violation itself. This is the first MQ install I've done on this release of OVMS, so I need to get more info to find out what's missing. Thank you all for your input; more details to follow. Dave A. = David A. Awerbuch, IBM Certified MQSeries Specialist APC Consulting Services, Inc. Providing Automated Solutions to Business Challenges West Hempstead, NY(516) 481-6440 [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25 http://photos.yahoo.com/ph/print_splash = David A. Awerbuch, IBM Certified MQSeries Specialist APC Consulting Services, Inc. Providing Automated Solutions to Business Challenges West Hempstead, NY(516) 481-6440 [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25 http://photos.yahoo.com/ph/print_splash 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: Webshpere MQ 5.3 and queue size
See the following links for pertinent info: http://www.mail-archive.com/[EMAIL PROTECTED]/msg13265.html http://www-306.ibm.com/software/integration/support/supportpacs/individual/mp01.html -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of mqteam Sent: Sunday, April 25, 2004 00:46 To: [EMAIL PROTECTED] Subject: Webshpere MQ 5.3 and queue size Hello all, Can anybody send me the registry key needed to expand queue sizes and any other steps required to expand queue sizes beyond the 2GB limit? The relevant operating systems are: Windows 2K Solaris 9 TIA Didi 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 clients
Is this what your looking for? http://publibfp.boulder.ibm.com/epubs/html/csqzaf07/csqzaf070z.htm#HDRSUPPAC -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Usha Suryadevara Sent: Thursday, April 22, 2004 12:22 To: [EMAIL PROTECTED] Subject: Re: WebSphere MQ clients Thanks Hossam, that was my assumption too, but at this point my company needs a proof, a written statement or something. Is anybody aware of something like that ? Thanks Usha At 02:03 PM 4/22/2004 -0400, you wrote: I remember back during my IBM MQ training, the IBM instructor said, you can use as much clients as you want. If I'm wrong , Then I'm in big trouble :-) regards, Hossam -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Usha Suryadevara Sent: Thursday, April 22, 2004 1:44 PM To: [EMAIL PROTECTED] Subject: WebSphere MQ clients Hello all, Do we need a special license for WebSphere MQ Clients ? Isn't WebSphere MQ client by itself available for free download ? In other words is it legal for me to buy one license for WebSphere and then bundle the MQ client installation in my product client application installation. I do not think so, but i couldn't find any information online, maybe i didn't search enough. It would be great if somebody can help me through this question. Thanks in advance. Usha 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: can not connect to queue manager
You could try and disable the OAM and see if there are other authorization issues like file/directory permissions. There's only one problem - on VMS you define a logical PRIOR to creating the queue manager which disables the OAM for the life of the queue manager. This may be beneficial if you can create a test queue manager which has the 2035 return for the given userID. The following link discusses the OAM and VMS: http://www-306.ibm.com/software/integration/mqfamily/library/manualsb/amqqag 00/amqqag001m.htm#HDRUTOAM -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of David Awerbuch Sent: Thursday, April 22, 2004 13:56 To: [EMAIL PROTECTED] Subject: can not connect to queue manager Hello all, I am running MQS 5.10 (ECO02) on OpenVMS V7.3-2 for Alpha. I have a userid that should be able to connect to the queue manager: 1. userid (UAF) is granted privelege MQM 2. the command 'dspmqaut -m qm -p userid -t qmgr' returns: inq set connect altusr crt dlt chg dsp setid setall Does anyone have any idea why this user would be getting a 2035 - not authorized - when trying to runmqsc for qm? I enabled my operator status (reply /enable) but I am not receiving any security messages (or any messages) regarding this user. There are no new records being added to any of the AMQEERR01.LOG files in [.errors], [.qmgrs.$system.errors], or [.qmgrs.qm.errore]. How can I figure out what the problem is? For those who are not familiar with OpenVMS, 5.1 is still the current supported version of MQ for this platform. Thanks, Dave A. = David A. Awerbuch, IBM Certified MQSeries Specialist APC Consulting Services, Inc. Providing Automated Solutions to Business Challenges West Hempstead, NY(516) 481-6440 [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25 http://photos.yahoo.com/ph/print_splash 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: Problem channel initiator
Does this link shed any light on your problem? http://www-1.ibm.com/support/docview.wss?rs=0q1=amq9509+channel+initiatoruid=swg2024loc=en_UScs=utf-8cc=uslang=en -Original Message-From: MQSeries List [mailto:[EMAIL PROTECTED]On Behalf Of Alex A. L. Sousa - BMSSent: Thursday, April 15, 2004 12:27To: [EMAIL PROTECTED]Subject: Problem channel initiator Hi, I have installed MQ version 5.3, Fix Pack CSD06, on operating system AIX V52. I have two queue managers installed. I have a script to start MQ: strmqm QMx runmqtrm -m QMx runmqchi -m QMx When the channel initiatior starts, I receive the message "AMQ9509: Program cannot open queue manager object", but the channel initiatior starts and works fine. For information, I had MQ version 5.0 installed, and I removed it (not migration), and install version 5.3. Thanks in advance Alex Augusto Lopes Sousa Gerência de Suporte- Basis SAP BMS - Belgo Mineira Sistemas S/A Tel: (31) 3217-4212 - Belo Horizonet - Brasil[EMAIL PROTECTED] Esta mensagem, incluindo seus anexos, tem caráter confidencial e seu conteúdo é restrito aos destinatários. Caso você tenha recebido esta mensagem por engano, queira por favor retorná-la e apagá-la de seus arquivos. Qualquer uso não autorizado, replicação ou disseminação desta mensagem ou parte dela é expressamente proibido, e passível de ações e indenizações judiciais cabíveis. A BMS não se responsabiliza pelo conteúdo da mensagem acima, sendo esta responsabilidade exclusiva de seu autor.
What is rmm.jar used for?
rmm.jar is distributed with MQ v5.3. Iam unable to find any doc on this java file - does anyone know what it's used for? Thx 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 clients with CSD06 integrated?
The support paks for MQ clients seems to have been updated to include CSD06 but when downloaded the README indicates CSD04 is integrated? Anyone have any idea whats going on here? For the windows client the download is at http://www-1.ibm.com/support/docview.wss?rs=203uid=swg24006105loc=en_UScs =utf-8lang=en 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: Managing linear logs with MQ5.3 on Windows
The MS62 support pack found on Hursley applies to both UNIX and Windows (W2K/WNT/WXP). For Windows, there is no mqs.ini file therefore you MUST specify the -n option to prevent the parsing of .ini files. Assuming you've installed perl on windows and have gzip on the system with its location specified in the %PATH% environment variable then the cleanmqlogs.pl script should work as documented. (see the support pak documentation for instructions on installing perl and associating the .PL suffix with perl). Note that if there are spaces in the directories you'll need to put double quotes around the directory specification or use the 8.3 representation. Here is an example, on windows, of an actual run of the MS62 support pak: (The queue manager is named test) C:\PROGRA~1\IBM\WEBSPH~1\binrcdmqimg -l -m test -t ALL * Media image for object test, type catalogue recorded. Media image for object test, type qmgr recorded. Media image for object SYSTEM.DEFAULT.PROCESS, type process recorded. Media image for object SYSTEM.DEFAULT.NAMELIST, type namelist recorded. Media image for object SYSTEM.DEFAULT.AUTHINFO.CRLLDAP, type authinfo recorded. Media image for object KEN.QL, type queue recorded. Media image for object MQMON, type queue recorded. Media image for object SYSTEM.ADMIN.CHANNEL.EVENT, type queue recorded. Media image for object SYSTEM.ADMIN.COMMAND.QUEUE, type queue recorded. Media image for object SYSTEM.ADMIN.PERFM.EVENT, type queue recorded. Media image for object SYSTEM.ADMIN.QMGR.EVENT, type queue recorded. Media image for object SYSTEM.AUTH.DATA.QUEUE, type queue recorded. Media image for object SYSTEM.CHANNEL.INITQ, type queue recorded. Media image for object SYSTEM.CHANNEL.SYNCQ, type queue recorded. Media image for object SYSTEM.CICS.INITIATION.QUEUE, type queue recorded. Media image for object SYSTEM.CLUSTER.COMMAND.QUEUE, type queue recorded. Media image for object SYSTEM.CLUSTER.REPOSITORY.QUEUE, type queue recorded. Media image for object SYSTEM.CLUSTER.TRANSMIT.QUEUE, type queue recorded. Media image for object SYSTEM.DEAD.LETTER.QUEUE, type queue recorded. Media image for object SYSTEM.DEFAULT.ALIAS.QUEUE, type queue recorded. Media image for object SYSTEM.DEFAULT.INITIATION.QUEUE, type queue recorded. Media image for object SYSTEM.DEFAULT.LOCAL.QUEUE, type queue recorded. Media image for object SYSTEM.DEFAULT.MODEL.QUEUE, type queue recorded. Media image for object SYSTEM.DEFAULT.REMOTE.QUEUE, type queue recorded. Media image for object SYSTEM.MQSC.REPLY.QUEUE, type queue recorded. Media image for object SYSTEM.PENDING.DATA.QUEUE, type queue recorded. AMQ7467: The oldest log file required to start queue manager test is S022.LO G. AMQ7468: The oldest log file required to perform media recovery of queue manager test is S015.LOG. C:\PROGRA~1\IBM\WEBSPH~1\bin Z:\mqseries_related\support_pacs\ms62_lin_log_maint_perlcleanmqlogs.pl ^ More? -t C:\Program Files\IBM\WebSphere MQ -l C:\PROGRA~1\IBM\WEBSPH~1\log -n test Z:\mqseries_related\support_pacs\ms62_lin_log_maint_perl\cleanmqlogs.pl: test: N eeded for Media Recovery: S015.LOG Z:\mqseries_related\support_pacs\ms62_lin_log_maint_perl\cleanmqlogs.pl: test: N eeded for Qmgr Restart: S022.LOG About to gzip test's S004.LOG About to gzip test's S005.LOG About to gzip test's S006.LOG About to gzip test's S007.LOG About to gzip test's S008.LOG About to gzip test's S009.LOG About to gzip test's S010.LOG About to gzip test's S011.LOG About to gzip test's S012.LOG About to gzip test's S013.LOG About to gzip test's S014.LOG Z:\mqseries_related\support_pacs\ms62_lin_log_maint_perl C:\PROGRA~1\IBM\WEBSPH~1\log\test\activedir Volume in drive C has no label. Volume Serial Number is C002-5176 Directory of C:\PROGRA~1\IBM\WEBSPH~1\log\test\active 03/21/2004 18:04DIR . 03/21/2004 18:04DIR .. 03/21/2004 17:59 510,099 S0~1.GZ S000.LOG.gz 03/21/2004 18:02 704,207 S0~2.GZ S001.LOG.gz 03/21/2004 18:02 783,652 S0~3.GZ S002.LOG.gz 03/21/2004 18:02 658,033 S0~4.GZ S003.LOG.gz 03/21/2004 18:02 739,633 S0AB05~1.GZ S004.LOG.gz 03/21/2004 18:02 656,740 S0AB02~1.GZ S005.LOG.gz 03/21/2004 18:02 786,927 S0AB07~1.GZ S006.LOG.gz 03/21/2004 18:02 651,246 S0AB00~1.GZ S007.LOG.gz 03/21/2004 18:02 800,641 S0AB01~1.GZ S008.LOG.gz 03/21/2004 18:02 671,522 S0AB06~1.GZ S009.LOG.gz 03/21/2004 18:03 729,910 S0AC09~1.GZ S010.LOG.gz 03/21/2004 18:03 717,544 S0AC0E~1.GZ S011.LOG.gz 03/21/2004 18:04 674,490 S0AC03~1.GZ S012.LOG.gz 03/21/2004 18:04 724,322 S0AC04~1.GZ S013.LOG.gz 03/21/2004 18:04 712,174 S0AC05~1.GZ S014.LOG.gz 03/21/2004 18:04 1,049,600 S015.LOG 03/21/2004 18:04
Re: Managing linear logs with MQ5.3 on Windows
Rao, On the web page you've listed download the ms62.tar.gz file listed towards the bottom of the page. You can open it with WINZIP. You then will have access to the cleanmqlogs perl script which will work on windows and unix. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Adiraju, Rao Sent: Monday, March 22, 2004 14:45 To: [EMAIL PROTECTED] Subject: Re: Managing linear logs with MQ5.3 on Windows Ken With due to respect, I am not sure what is this Hursley you are talking and how to get there. I usually logon to IBM WMQ Support pack homepage to download any support pack and here is the address: http://www-306.ibm.com/software/integration/support/supportpacs/individual/m s62.html On this page MS62 talks about how to install and run on windows, BUT NO ZIP FILE CAN BE SEEN. In I fact asked this question a month back, and haven't heard anything since then. Are you talking of another home page for Hursley where we can download this service pack. Believe me, it was damn frustrating to download something which doesn't exist. Hence I said bugger all, and built my own VB script for it. Cheers Rao -Original Message- From: Ken Woloschuk [mailto:[EMAIL PROTECTED] Sent: 11 January 2001 1:52 AM To: [EMAIL PROTECTED] Subject: Re: Managing linear logs with MQ5.3 on Windows The MS62 support pack found on Hursley applies to both UNIX and Windows (W2K/WNT/WXP). For Windows, there is no mqs.ini file therefore you MUST specify the -n option to prevent the parsing of .ini files. Assuming you've installed perl on windows and have gzip on the system with its location specified in the %PATH% environment variable then the cleanmqlogs.pl script should work as documented. (see the support pak documentation for instructions on installing perl and associating the .PL suffix with perl). Note that if there are spaces in the directories you'll need to put double quotes around the directory specification or use the 8.3 representation. Here is an example, on windows, of an actual run of the MS62 support pak: (The queue manager is named test) C:\PROGRA~1\IBM\WEBSPH~1\binrcdmqimg -l -m test -t ALL * Media image for object test, type catalogue recorded. Media image for object test, type qmgr recorded. Media image for object SYSTEM.DEFAULT.PROCESS, type process recorded. Media image for object SYSTEM.DEFAULT.NAMELIST, type namelist recorded. Media image for object SYSTEM.DEFAULT.AUTHINFO.CRLLDAP, type authinfo recorded. Media image for object KEN.QL, type queue recorded. Media image for object MQMON, type queue recorded. Media image for object SYSTEM.ADMIN.CHANNEL.EVENT, type queue recorded. Media image for object SYSTEM.ADMIN.COMMAND.QUEUE, type queue recorded. Media image for object SYSTEM.ADMIN.PERFM.EVENT, type queue recorded. Media image for object SYSTEM.ADMIN.QMGR.EVENT, type queue recorded. Media image for object SYSTEM.AUTH.DATA.QUEUE, type queue recorded. Media image for object SYSTEM.CHANNEL.INITQ, type queue recorded. Media image for object SYSTEM.CHANNEL.SYNCQ, type queue recorded. Media image for object SYSTEM.CICS.INITIATION.QUEUE, type queue recorded. Media image for object SYSTEM.CLUSTER.COMMAND.QUEUE, type queue recorded. Media image for object SYSTEM.CLUSTER.REPOSITORY.QUEUE, type queue recorded. Media image for object SYSTEM.CLUSTER.TRANSMIT.QUEUE, type queue recorded. Media image for object SYSTEM.DEAD.LETTER.QUEUE, type queue recorded. Media image for object SYSTEM.DEFAULT.ALIAS.QUEUE, type queue recorded. Media image for object SYSTEM.DEFAULT.INITIATION.QUEUE, type queue recorded. Media image for object SYSTEM.DEFAULT.LOCAL.QUEUE, type queue recorded. Media image for object SYSTEM.DEFAULT.MODEL.QUEUE, type queue recorded. Media image for object SYSTEM.DEFAULT.REMOTE.QUEUE, type queue recorded. Media image for object SYSTEM.MQSC.REPLY.QUEUE, type queue recorded. Media image for object SYSTEM.PENDING.DATA.QUEUE, type queue recorded. AMQ7467: The oldest log file required to start queue manager test is S022.LO G. AMQ7468: The oldest log file required to perform media recovery of queue manager test is S015.LOG. C:\PROGRA~1\IBM\WEBSPH~1\bin Z:\mqseries_related\support_pacs\ms62_lin_log_maint_perlcleanmqlogs.pl ^ More? -t C:\Program Files\IBM\WebSphere MQ -l C:\PROGRA~1\IBM\WEBSPH~1\log -n test Z:\mqseries_related\support_pacs\ms62_lin_log_maint_perl\cleanmqlogs.pl: test: N eeded for Media Recovery: S015.LOG Z:\mqseries_related\support_pacs\ms62_lin_log_maint_perl\cleanmqlogs.pl: test: N eeded for Qmgr Restart: S022.LOG About to gzip test's S004.LOG About to gzip test's S005.LOG About to gzip test's S006.LOG About to gzip test's S007.LOG About to gzip test's S008.LOG About to gzip test's S009.LOG About to gzip test's S010.LOG About to gzip test's S011.LOG About to gzip test's S012.LOG About to gzip test's S013.LOG About to gzip test's S014.LOG Z:\mqseries_related\support_pacs
Re: Managing linear logs with MQ5.3 on Windows
We currently use the MS62 support pack to clean up linear logs. It was mentioned that the MS0L support pack offers a JAVA solution for cleaning up linear logs for windows. I downloaded MS0L and found the following procedure to work on windows: For windows usage, first create a qm.ini in MQ top dir\qmgrs\queue mgr name eg: C:\PROGRA~1\IBM\WEBSPH~1\Qmgrs\test The contents of qm.ini should consist of one line: LogType=LINEAR Include the mqllm.jar file in the classpath: c:\set classpath=%classpath%;dir path to mqllm.jar\mqllm.jar eg: c:\ set classpath=%classpath%;c:\java_stuff\mqllm.jar For a queue manager named test execute the following: c:\ java com.ibm.aim.logfile.AimMqLinearLogfileMaint -q test -d C:\PROGRA~1\IBM\WEBSPH~1 -a C:\archive -v Here, C:\PROGRA~1\IBM\WEBSPH~1 is the mqseries top level directory and c:\archive is where the zipped logs are to be stored. I found the placement and contents of the qm.ini file by trial and error. The documentation doesn't seem to mention anything about qm.ini on windows. If anyone else has had experience with the JAVA version of MS0L on windows it would interesting to here from you. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Luc-Michel Demey Sent: Friday, March 19, 2004 16:54 To: [EMAIL PROTECTED] Subject: Managing linear logs with MQ5.3 on Windows Hi all, I am trying to find if any of the available support packs are suitable for managing linear logs on a MQ 5.3 Windows NT box. I have done a little testing, most of them rely on the qm.ini file not more present above 5.0. Even with a fake ini file on the right place, I was not able to use : - MS0L : Java exception - MS62 : Perl problems In both cases (Java Perl), I suspect NT 4 related problems. Any ideas / experiences to share ? TIA, LMD. -- Luc-Michel Demey - Freelance EAI Consultant Paris / France Tel. : +33 6 08 755 655 http://consulting.demey.org/ - lmd at demey dot org 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: WMQ 5.1 on Alpha VMS
You mentioned VMS V7.1 - I thought the minimum level for VMS is V7.2-1 for MQ V5.1? See: http://www-306.ibm.com/software/integration/wmq/openvmsv51/factsheet.html -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of David Awerbuch Sent: Friday, February 20, 2004 10:10 To: [EMAIL PROTECTED] Subject: WMQ 5.1 on Alpha VMS Hello, I have a client who installed MQ 2.2.1 on an HP Alpha running OpenVMS 7.1, then deleted it and installed WebSphereMQ 5.1 CSD05 after-wards. The delete-cleanup/install cycle had to be repeated 2 times for the install to finally complete the IVP successfully. There is an open issue with IBM regarding RUNMQSC spinning on an apparent RMS error. This same customer has also failed numerous times trying to install 5.1 on a OVMS system on which no other version of MQ has been previously installed. The questions here are: 1) Is your installation currently running WebSphere 5.1 on HP Alpha OpenVMS 7.1? 2) Have you tried to run 5.1 only to give up and fall back to 2.2.1? 3) Are you running 2.2.1 and have considered upgrading to 5.1 but decided not to? If you, or someone you know of, fits these circumstances, I would appreciate hearing from you or your forwarding me a contact; we have a few questions we would like to ask the VMS administrators at these locations. Thank you all in advance. Dave Awerbuch = David A. Awerbuch, IBM Certified MQSeries Specialist APC Consulting Services, Inc. Providing Automated Solutions to Business Challenges West Hempstead, NY(516) 481-6440 [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Mail SpamGuard - Read only the mail you want. http://antispam.yahoo.com/tools 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: Process /sys$system/runmqchl terminated with status 20
I believe the default number of channel initiators is 3. The maxinitiators setting may not be the source of your problem - I mentioned it solely since it had an error return of 20. If you are attempting to run more than the default 3 channel initiators then perhaps this setting may be of assistance. Do the error logs contain any information regarding lack of resources? -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of David Awerbuch Sent: Thursday, February 05, 2004 09:16 To: [EMAIL PROTECTED] Subject: Re: Process /sys$system/runmqchl terminated with status 20 Ken, There is no 'maxinitiators' clause in the [channels] stanza. Does anyone know what the default value is? I have other systems (2.2.1) with more channels running than this 5.1.0 system has, so I don't properly understand why this would be a problem now. Thanks, Dave A. -Original Message- From: Ken Woloschuk [mailto:[EMAIL PROTECTED] Sent: Sunday, February 04, 2001 5:57 PM To: [EMAIL PROTECTED] Subject: Re: Process /sys$system/runmqchl terminated with status 20 I've seen error status 20 occur on a queue manager when the maxinitiators was set too low to accomodate all requested channel initiators. This would be set in the channels stanza in the file qm.ini. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Williams, Arlen Sent: Wednesday, February 04, 2004 12:00 To: [EMAIL PROTECTED] Subject: Re: Process /sys$system/runmqchl terminated with status 20 Error 20 on a VMS system is BADPARM, bad parameter value. -Original Message- From: David Awerbuch [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 04, 2004 9:18 AM To: [EMAIL PROTECTED] Subject: Process /sys$system/runmqchl terminated with status 20 Hello, I am logged on as user MQADMIN, with MQM rights, on an Alpha/OpenVMS 7.3 system running WMQ 5.1.0, ECO02. I am receiving the following operator message about every minute, with occasionally gaps of from 5 to 25 minutes. Reply received on ATP023 from user MQADMIN at ATP023 Batch 11:53:18 Process /sys$system/runmqchl terminated with status 20 Does anyone have any ideas what this is all about? I can not find a reference to this message or the status 20. Thanks, Dave A. = David A. Awerbuch, IBM Certified MQSeries Specialist APC Consulting Services, Inc. Providing Automated Solutions to Business Challenges West Hempstead, NY(516) 481-6440 [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.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: Process /sys$system/runmqchl terminated with status 20
I've seen error status 20 occur on a queue manager when the maxinitiators was set too low to accomodate all requested channel initiators. This would be set in the channels stanza in the file qm.ini. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Williams, Arlen Sent: Wednesday, February 04, 2004 12:00 To: [EMAIL PROTECTED] Subject: Re: Process /sys$system/runmqchl terminated with status 20 Error 20 on a VMS system is BADPARM, bad parameter value. -Original Message- From: David Awerbuch [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 04, 2004 9:18 AM To: [EMAIL PROTECTED] Subject: Process /sys$system/runmqchl terminated with status 20 Hello, I am logged on as user MQADMIN, with MQM rights, on an Alpha/OpenVMS 7.3 system running WMQ 5.1.0, ECO02. I am receiving the following operator message about every minute, with occasionally gaps of from 5 to 25 minutes. Reply received on ATP023 from user MQADMIN at ATP023 Batch 11:53:18 Process /sys$system/runmqchl terminated with status 20 Does anyone have any ideas what this is all about? I can not find a reference to this message or the status 20. Thanks, Dave A. = David A. Awerbuch, IBM Certified MQSeries Specialist APC Consulting Services, Inc. Providing Automated Solutions to Business Challenges West Hempstead, NY(516) 481-6440 [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it! http://webhosting.yahoo.com/ps/sb/ 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
Different behavior for clussdr and sdr channels?
Have the following scenario: Using MQ v5.3 csd5. I disconnect a machine from the network hosting a queue manager which supports a clustered queue. I then put a message to that clustered queue from elsewhere in the cluster. I monitor the status of the active channels on the queue manager that will transmit the message to the disconnected node. The cluster sender channel goes to binding and stays in that state for a long period of time before going into a retrying state. I reconnect the machine and leave the queue manager stopped. I resend the message and the cluster sender goes binding and then in short order goes into retrying. I then do the same thing using a sender channel. With the target machine disconnected I send a message and the status of the sender channel goes to binding followed in short order by retrying. It seems that with cluster sender channels the presence of the target queue manager tcpip address makes a difference to how long it stays in a binding state. A sender channel seems to be uneffected by the presence or absence of the target tcpip address. This would be of interest if the program doing the put specifies MQC.MQOO_BIND_NOT_FIXED. The message is placed on the cluster transmit queue and sits there until the cluster sender channel goes into a retrying state at which time it will be sent to another instance of the cluster queue. In my case I've set up a cluster exit (one of sample programs distributed with MQ) which first sends messages to a specific queue manager and then fails over to any remaining queue managers hosting an instance of the clustered queue. While the binding state is in effect the queue depth of the transmit queue grows and the messages will not be forwarded on to other active queue managers hosting an instance of queue. This is why the time needed to get to a retrying state is important. Does anyone have any insight into this? 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: setting up MQ environment on windows for Perl
Give this a try. The nmake test may skip some tests but the the software still seems to work. C:\MQ_PER~1\MQSERI~1.20ls C:\MQ_PER~1\MQSERI~1.20\*.* .exists [t.in] [.options] [util] [blib] Changes.html [examples] Changes.src [include] CONFIG [MQClient] COPYRIGHT [MQSeries-Message-DeadLetter] LICENSE [MQSeries-Message-PCF] Makefile [MQSeries-Message-RulesFormat] Makefile.PL [MQSeries-OAM] MANIFEST [MQSeries-PubSub] MQSeries.pm [MQSeries] pm_to_blib [MQServer] README [pre.in]README.html 253952 (228917) bytes in 13 files C:\MQ_PER~1\MQSERI~1.20 C:\MQ_PER~1\MQSERI~1.20echo %path% . . . C:\Perl\bin\; C:\Program Files\Microsoft Visual Studio\Common\Tools\WinNT; C:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin; C:\Program Files\Microsoft Visual Studio\Common\Tools; C:\Program Files\Microsoft Visual Studio\VC98\bin C:\MQ_PER~1\MQSERI~1.20echo %lib% C:\Program Files\IBM\WebSphere MQ\tools\lib; C:\Program Files\Microsoft Visual Studio\VC98\mfc\lib; C:\Program Files\Microsoft Visual Studio\VC98\lib C:\MQ_PER~1\MQSERI~1.20echo %include% C:\Program Files\IBM\WebSphere MQ\tools\c\include; C:\Program Files\IBM\WebSphere MQ\tools\cplus\include; C:\Program Files\Microsoft Visual Studio\VC98\atl\include; C:\Program Files\Microsoft Visual Studio\VC98\mfc\include; C:\Program Files\Microsoft Visual Studio\VC98\include edit the CONFIG file according to your configuration C:\MQ_PER~1\MQSERI~1.20perl Makefile.PL C:\MQ_PER~1\MQSERI~1.20nmake test C:\MQ_PER~1\MQSERI~1.20nmake install Good luck! -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Daniel Graper Sent: Friday, December 05, 2003 10:11 To: [EMAIL PROTECTED] Subject: setting up MQ environment on windows for Perl I need to write a Perl script to run on my windows workstation that will access MQ message queues. I has dowloaded the Perl interpreter and installed the MQ client but am having some challenges installing the MQ perl libraries. Has anyone out there installed the MA89 MQ modules for windows before? thanks, Dan 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: Windows Log Rotation
A java version is available at: http://www-306.ibm.com/software/integration/support/supportpacs/individual/m s0l.html -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Beinert, William Sent: Monday, December 01, 2003 10:46 To: [EMAIL PROTECTED] Subject: Re: Windows Log Rotation I hacked MS62 to just delete unneeded logs on NT. (I do a record image first) You are welcome to it, if you want it. You have to install Active State Perl to use it. Bill Beinert Systems Programming Con Edison When they took the fourth amendment, I was quiet because I didn't deal drugs! When they took the sixth amendment, I was quiet because, I was innocent. When they took the second amendment, I was quiet because I didn't own a gun! Now they've taken the first amendment, and I can say (or do) nothing about it. The Second Amendment is in place in case they ignore the others. MODWN DAbE -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Monday, December 01, 2003 9:04 AM To: [EMAIL PROTECTED] Subject: Windows Log Rotation Has anybody written a script for MQ log file rotation and archive in a Windows environment? I am looking to set one up, but do not want to reinvent the wheel. Thank you. Michael 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: dmpmqaut
try dmpmqaut -m QM1 2 out.txt -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Ruzi R Sent: Tuesday, November 25, 2003 14:12 To: [EMAIL PROTECTED] Subject: dmpmqaut on MQ 5.3/2WK. If I issue: dmpmqaut -m QM1 out.txt to see all the authorities on QM1, out.txt gets created but it is empty. Is there a free utility out there that will dump all the authorities in a file on a given qmgr? Thanks in advance, Ruzi 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
