Re: Flood of AMQ7467/AMQ6378 messages
Heinz, As I am sure you are aware, AMQ7467 is telling you to clean up your logs. Your client should have procedures in place to maintain the log files, which would prevent this message from being repeated. -Original Message- From: Heinz Klein [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 02, 2003 3:10 PM To: [EMAIL PROTECTED] Subject: Flood of AMQ7467/AMQ6378 messages Hello. I appended a similar question some time ago but at that time the customer did not pursue the subject and I never got a complete picture. What is happening: every 3:25 minutes (approximately 200 seconds) the messages above are written to the AMQERRnn logs. In the logs I am serching right now this went on for about 18 hours, without a single change in the log numbers. I saw in an IBM document that for Unix (actually Sun, but I am allowing myself to extrapolate it to AIX, HP/UX and Linux) there is a stanza in the qm.ini file called 'CheckPointWaitLen' which could explain this behavior. However, I am on Windows 2K. Does a similar parameter exist there? And if yes, where can I find it (a quick search through the registry did not show anything similar). Thanks in advance for any help. Heinz Klein OLTP Tecnologia Solucoes Sao Paulo/SP - Brasil 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
Channels not starting up - What am I missing here?
Maybe I've been looking at this too long, and am just not seeing the problem. I'm hoping a fresh set of eyes can shed some light on this problem. Very simply, I need my channels to start up when a message lands on an xmit queue. On the xmit queue I have triggering on, type first, depth 1, trigger data equals the channel name (uppercase), init queue name is SYSTEM.CHANNEL.INITQ Bridgette Beardsley 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: Channels not starting up - What am I missing here?
No, I am bypassing using a process by specifying the channel name in the trigger data, so that when the trigger msg goes to the init queue, it contains the info needed for the initiator to start the right channel. BTW, I have this working in production, it's the development environment that's giving me heck - isn't that usually the way? lol -BB -Original Message- From: Hinds, Bernard [mailto:[EMAIL PROTECTED] Sent: Friday, March 28, 2003 1:40 PM To: [EMAIL PROTECTED] Subject: Re: Channels not starting up - What am I missing here? Do you have a process to start the channel? -Original Message- From: Beardsley, Bridgette [mailto:[EMAIL PROTECTED] Sent: Friday, March 28, 2003 2:36 PM To: [EMAIL PROTECTED] Subject: Channels not starting up - What am I missing here? Maybe I've been looking at this too long, and am just not seeing the problem. I'm hoping a fresh set of eyes can shed some light on this problem. Very simply, I need my channels to start up when a message lands on an xmit queue. On the xmit queue I have triggering on, type first, depth 1, trigger data equals the channel name (uppercase), init queue name is SYSTEM.CHANNEL.INITQ Bridgette Beardsley 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: Increase size of error logs
Aatush, You can increase the logs to a total of 63 primary and secondary, but to change the log size or type (linear vs circular), you will need to redefine your qmgr. On WinNT go to MQSeries Services, right click on the queue manager, go to Properties, and then the Log tab. -Bridgette Beardsley -Original Message-From: Aatush Desai(PIPEX) [mailto:[EMAIL PROTECTED]Sent: Wednesday, March 12, 2003 6:12 PMTo: [EMAIL PROTECTED]Subject: Increase size of error logs Hi...MQ error logs (amqerr01.log..etc) are cut when they go over 256KB. MQ also keeps 3 logs. Does anyone know either how to increase the size of the logs or the number of logs. Platform if NT, v5.2 and above.Thanks Aatush
Re: mqver command for 5.3 CSD01
Peter, The CSD doesn't necessarily show up with mqver. Who knows why?! I applied the CSD separately and get the same message as you posted. So here's how I identify it - 1. I emailed my boss that the CSD install was successful (so it's gotta be true!) lol 2. Check the memo.ptf file - seriously - this should be accurate 3. An option to remove the latest CSD will be in the MQ Programs File 4. A directory named CSD01 will be added following IBM\WebSphere MQ\ -Bridgette -Original Message- From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED] Sent: Thursday, March 13, 2003 8:33 AM To: [EMAIL PROTECTED] Subject: mqver command for 5.3 CSD01 I just upgrade to what I thought was 5.3 CSD01, but I get this message when I do mqver: Name: WebSphere MQ Version: 530 CMVC level: p000-L021011 BuildType: IKAP - (Production) The read me file says: This readme file applies to Websphere MQ books dated October 2002 and CSD01 level of the V5.3 product shipped on or after October 2002. So what do I trust, the mqver command, which indicates I have no CSD01, or the readme, which indicates I do? Does the CSD only show up in the mqver command if you applied a CSD separatly? If you got a version with the CSD included, the only way you would know is knowing that the product shipped on or after the date 021011 had the CSD functionality included? Peter Potkay IBM MQSeries Certified [EMAIL PROTECTED] X 77906 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
AMQ7880
Does anyone know what reason 545284625 could mean? --- 03/07/2003 09:16:21 AMQ7880: Error code 71 starting SITEST/Queue Manager WebSphere MQ service. EXPLANATION: The service was unable to start SITEST/Queue Manager. The error message reported was as follows: There are 89 days left in the trial period for this copy of WebSphere MQ. The Queue Manager ended for reason 545284625 '' ACTION: Use WebSphere MQ Services to investigate why the service could not begin. If recovery for this service is active, MQ will attempt to recover. --- Bridgette Beardsley 713-546-6167 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: Backing Up Services in NT
David, Are you looking for something to export the definitions of your objects? Try supportpac ms03 at http://www-3.ibm.com/software/integration/support/supportpacs/individual/ms03.html -Bridgette Beardsley -Original Message-From: De Seve, David [mailto:[EMAIL PROTECTED]Sent: Monday, March 03, 2003 3:14 PMTo: [EMAIL PROTECTED]Subject: Re: Backing Up Services in NT I guess I am looking for a way to export the current configuration first. -Original Message-From: Gorse, Darry [mailto:[EMAIL PROTECTED]Sent: Monday, March 03, 2003 11:47 AMTo: [EMAIL PROTECTED]Subject: Re: Backing Up Services in NT I don't know if there isa formal support pac or utility but I have used the amqmdain command in a bat file to recreate MQ services. Here is a sample, you just need to modify it to your needs. Cheers, Darry -Original Message-From: De Seve, David [mailto:[EMAIL PROTECTED]Sent: Monday, March 03, 2003 9:41 AMTo: [EMAIL PROTECTED]Subject: Backing Up Services in NT Does anybody know a utility for backing-up/restoring MQ Services in NT so that I don't have to recreate them from scratch after I delete/recreate a queue manager? Thanks
Re: Hopping messages across clusters
Randy, Why not use a remote queue definition on QM9 that points to QC.LOCAL? -Bridgette Beardsley -Original Message- From: Crowder, Randall [mailto:[EMAIL PROTECTED] Sent: Monday, February 24, 2003 2:56 PM To: [EMAIL PROTECTED] Subject: Hopping messages across clusters Intercommunication Gurus!!! I have the following setup - two overlapping clusters A and B. --- Cluster A | QM1 | QC.LOCAL - Local to QM1, shared in Cluster A | QM2 | QC.LOCAL - Local to QM2, shared in Cluster A |-| | | QM3 | | QC.LOCAL.ALIAS - Alias on QM3, shared in Cluster B |-|- | QM8 | | QM9 | |-- Cluster B In this example. QM3 is the only queue manager that is a part of both clusters. What I'm trying to figure out is how a program connected to QM9 can put messages to QC.LOCAL on QM1/QM2. So far, the only thing I've been able to get working is to create an alias for QC.LOCAL on QM3 and make the alias a part of Cluster B. Is there another way? I'd like to be able to do it programmatically - where I wouldn't have to create the alias definition on QM3... Thanks for any assistance. Randy C. 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: PCF Commands on OS/390
The following table lists each WebSphere MQ platform that supports PCFs. Platform WebSphere MQ for Short name Compaq OpenVMS Alpha Compaq OpenVMS Alpha Compaq NonStop Kernel Compaq NSK iSeries OS/400(R) OS/2 OS/2 UNIX(R)(R) systems see Note below UNIX systems Windows NT(R) Windows -Original Message-From: Long, Matthew Jr. (Inland) [mailto:[EMAIL PROTECTED]]Sent: Tuesday, February 18, 2003 4:38 PMTo: [EMAIL PROTECTED]Subject: PCF Commands on OS/390 I'm successful at making a connection from Win2K to a OS/390 Mainframe using MQCONNX, but I can't run any PCF commands. These PCF Commands work fine on UNIX, VMS, NT, and Win2K, but not the Mainframe. Any ideas why this is? Thanks!
MQSeries GENTRAN
Has anyone on the list ever set up Gentran:Server on NT with Gentran's MQSeries Gateway (adapter) and MQSeries? How about Gentran's Sterling Integrator and MQSeries? Thanks, Bridgette Beardsley 713-546-6167 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
