Unsubscribe
SIGN OFF MQSeries 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
Communication about cluster boundaries
Hello all, we want to know, how to communicate about MQSeries Cluster boundaries. Because of firewall restrictions we had to build two overlapping cluster and the need to communicate between two nodes in both cluster. We want to use workload balancing, the queues reside on several cloned machines in both cluster. A small and simple scenario: QM1 belongs to Cluster1 and share a local Queue Q.TEST.ORIG in his cluster QM2 belongs to Cluster2 want to put a message to Q.TEST.ORIG. QMR belongs to Cluster1,Cluster2 and should act as a MQ-Gateway We do some tests and no one work properly: a) Define QALIAS Q.TEST on QMR shared in Cluster1, Cluster2 and point to Q.TEST.ORIG in the Cluster1 Result: Reason 2082 on QMR b) Define QREMOTE Q.TEST.1 on QMR shared in Cluster2, point to Q.TEST.ORIG (without naming a remote QMGR) Result: Reason: 2087 on QMR Defining a QREMOTE on QMR shared in Cluster2 and point to Q.TEST.ORIG on QM1, QM2 can send messages to the Q, but this is a lost of the workload balancing feature of the cluster. Henry Springer MQSeries Familie K-DOI-23 Volkswagen AG Brieffach 1891 38436 Wolfsburg Telefon +49-53 61-92 97 74 Telefax +49-53 61-92 28 13 eFax +49-5361-95 72 97 74 http://www.volkswagen.de 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: Transmission Queue and Remote Queue
Karthikeyan, The Transmission queue (xmitq) is the physical storage for messages being transfered over a channel. The remote queue is only a definition that point to a xmitq and a remote qmgr that will receive the messages. It also point to the local queue on the remote qmgr that will receive the messages sent. Jonas Nyberg Electrolux IT Solutions - Sweden Karthikeyan Senthilnathan [EMAIL PROTECTED] wrote: All, What is different between Transmission Queue and Remote Queue.? Regards, Karthikeyan Senthilnathan Software Engineer WWRE Project IBM Global Services India PARVAAZ, Shankar Shet Road, Pune - 411 001 INDIA Tel: +91 (20) 6449724, Extn - 1551 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 __ Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of buying online with Shop@Netscape! http://shopnow.netscape.com/ Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/ 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: xinetd daemon - Red Hat Linux
On Linux, if xinetd service is enabled in place of inetd service, we must
configure /etc/xinetd.conf file.
Eg: xinetd.conf configuration for Qmgr PHK is
service PHK
{
flags = REUSE
socket_type = stream
wait = no
user = mqm
server = /opt/mqm/bin/amqcrsta
server_args = -m PHK
log_on_failure += USERID
disable = no
}
Karthik
- Minds are like parachutes, they function best when open
Graham French
Graham.French@MQSOLUTTo: [EMAIL PROTECTED]
IONS.CO.UK cc:
Sent by: MQSeries ListSubject: xinetd daemon - Red Hat
Linux
[EMAIL PROTECTED]
AT
05/28/2002 02:56 PM
Please respond to
MQSeries List
Anyone have a sample of the MQSeries configuration file for the xinetd
daemon in Red Hat Linux ?
Graham French
MQSolutions
+44 (0)7973 821288
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: V5.2 Shared Queues
Russell - thanks for the comments. You are correct that CMDSCOPE is not needed to clear a shared queue. I was just trying to give a list of 'possible' uses - and chose the wrong one ;-). Re the mixing of updates to local and shared queues, I was thinking about the cases where a task had completed successfully, and then subsequently the qmgr 'died'. If for some reason the batch of messages put to the local queue and shared queue were 'related' then this could cause a problem. I really like the Shared Queues feature. I distinctly remember being impressed when I used amqsgetc (client on Windows NT) to get messages out of the Coupling Facility. Wow! Regards ... Ruud -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of Russell Finn Sent: 28 May 2002 12:18 To: [EMAIL PROTECTED] Subject: Re: V5.2 Shared Queues Ruud, A very nice list, on which I have a couple of points: Along with the QSGDISP field, there is another new field called CMDSCOPE (Command Scope) which determines the scope of the command. e.g. you could 'clear' all shared queues, The CMDSCOPE parameter is not needed to clear a shared queue since there is only one (shared) instance of it. The CMDSCOPE parameter could usefully be used to clear all queues with QSGDISP(COPY) - ie ones created from a GROUP object. When a GROUP object is defined, a local COPY of it is pushed out to each queue manager in the QSG. Ensure you do not update both local queue and shares queues in one update 'unit'. If the queue manager that 'owns' the local queue crashes, then the local queue is unavailable, but the shared queue remains available. The unit of work paradigm is the same for transactions that update local and shared queues - the operations will either all commit or all backout. As you say, the shared queue will remain available for other queue managers to access. Any shared messages in the first UOW will get peer recovered (ie rolled forward or backward), but the messages put to the local queue will also have the same roll forward/backward decision applied to them. Of course, these messages won't be available until the failed queue manager is recovered. Russell Russell Finn MQSeries System Test [EMAIL PROTECTED] |-+ | | Ruud van Zundert | | | [EMAIL PROTECTED]| | | OM | | | Sent by: MQSeries| | | List | | | MQSERIES@AKH-WIE| | | N.AC.AT | | || | || | | 24/05/02 16:49 | | | Please respond to| | | MQSeries List| | || |-+ --- ---| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Re: V5.2 Shared Queues | | | | | --- ---| Norm, If you subscribe to the monthly MQ Update magazine by Xephon, then you could have a look at the Feb 2001 issue for an article entitled 'MQ V5.2 for OS/390 V5.2: CF and DB2 Issues'. Personally, it did not take me too long to get Shared Queues to run. The specific issues I recall are as follows : - ensure your coupling facility is at level 9 or above. Check correct level of OS/390 (V2.9 I believe). - when you go into production consider having a backup CF - DB2 V5.1 or higher in 'data sharing' mode - You can only use shared queues for non-persistent messages up to a maximum size of 63k - V5.3 will allow for persistent messages, but the 63K limit still applies. - You'll need to update the CSQ6SYSP macro to code the details of the QSG (Queue Sharing Group). - To make a queue 'shared', set a new field called QSGDISP to 'shared'. The default is not shared. Unfortunately, you'll also need to know the name of the specific CF structure. - Although you still need a queue manager to define a shared queue, it is no longer 'owned' by a queue manager. The queue definition is stored in DB2. You'll therefore need to run some batch jobs to define the database, table spaces and tables, as well as some jobs to set up some data (via new utility CSQ5PQSG). The amount of DB2 space is small, so talk to your DB2 sysprog about where to place the MQ/DB2 data, e.g. existing or new DB2 susbsys. - MQ connects to the DB2 'Group Attach' name instead of a specific DB2 subsystem - although this does result in MQ being connected to a DB2 subsys. If that subsys 'dies', MQ will connect to the next available DB2 subsys within that DB2 group. WARNING: the second DB2 subsys (and of course the
Re: Remote Queue problem
Hello, Thanks for all that answered my question. I didn't get any mail from the list server until Thursday afternoon... and I was on vacation by then. I assume a problem with our Mail Server here... Anyway the problem is fixed... I had changed the names of my transmission queue...but didn't point the channel to it... so messages never went. Thanks again. Have a Great day! Mike Michael S. LawrenceSystems ProgrammerAtlas Van Lines [EMAIL PROTECTED] [EMAIL PROTECTED] 05/22/02 09:16AM Hello Running MQSERIES V1R2 / OS390 2.10 My transmission queues are filling up and all looks ok except that we just can get it to send across. When I turn trigger off and turn it back on, channel goes from inactive to run. But nothing leaves my qmgr.I am not sure what is setup wrong or if something is broken. I have gone back over the setup and had the NTserver side check out what they check out and all looks ok... any direction would be helpful. I thought that if the channel could connect and even if the NT side didn't have a queue setup (they do) that it would go to the dead letter queue. I know I am missing something simple.
Re: Communication about cluster boundaries
All - just had loads of notifications from various company's socalled 'anti-virus' programs. My attached called overlap.cmd was rejected. I have, therefore, renamed it to overlap.txt. Regards ... Ruud -Original Message- From: Ruud van Zundert [mailto:[EMAIL PROTECTED]] Sent: 28 May 2002 14:17 To: MQSeries List Subject: RE: Communication about cluster boundaries Henry - it's a bit tricky to get this to work, and if you follow this procedure, you should be ok: I've attached an example script that you can run on a Win2000 machine. It is re-runnable. This is what it does (run via 'overlap.cmd') : 1. define 4 qmgrs QMT1, QMT2, QMT2B and QMGW. QMT1 holds the full repository for cluster CL001. QMT2 holds the full repository for cluster CL002. QMT2B holds a partial repository for cluster CL002. QMGW is the 'gateway' linking the 2 clusters together. 2. Cluster queue QMT2.CQ is defined on both QMT2 and QMT2B. 3. A 'bridge' queue called BRIDGE is defined on the gateway as a QALIAS - it resides in cluster CL001, but points to target queue QMT2.CQ in cluster CL002. 4. To test: amqsput BRIDGE QMT1 Result : messages 'should' ;-) arrive on QMT2.CQ spread across qmgrs QMT2 and QMT2B. Let us know how you get on. Regards ... Ruud -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of Springer, Henry Sent: 28 May 2002 11:22 To: [EMAIL PROTECTED] Subject: Communication about cluster boundaries Hello all, we want to know, how to communicate about MQSeries Cluster boundaries. Because of firewall restrictions we had to build two overlapping cluster and the need to communicate between two nodes in both cluster. We want to use workload balancing, the queues reside on several cloned machines in both cluster. A small and simple scenario: QM1 belongs to Cluster1 and share a local Queue Q.TEST.ORIG in his cluster QM2 belongs to Cluster2 want to put a message to Q.TEST.ORIG. QMR belongs to Cluster1,Cluster2 and should act as a MQ-Gateway We do some tests and no one work properly: a) Define QALIAS Q.TEST on QMR shared in Cluster1, Cluster2 and point to Q.TEST.ORIG in the Cluster1 Result: Reason 2082 on QMR b) Define QREMOTE Q.TEST.1 on QMR shared in Cluster2, point to Q.TEST.ORIG (without naming a remote QMGR) Result: Reason: 2087 on QMR Defining a QREMOTE on QMR shared in Cluster2 and point to Q.TEST.ORIG on QM1, QM2 can send messages to the Q, but this is a lost of the workload balancing feature of the cluster. Henry Springer MQSeries Familie K-DOI-23 Volkswagen AG Brieffach 1891 38436 Wolfsburg Telefon +49-53 61-92 97 74 Telefax +49-53 61-92 28 13 eFax +49-5361-95 72 97 74 http://www.volkswagen.de 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 endmqm -i QMT1 endmqm -i QMT2 endmqm -i QMT2B endmqm -i QMGW dltmqm QMT1 dltmqm QMT2 dltmqm QMT2B dltmqm QMGW crtmqm -u SYSTEM.DEAD.LETTER.QUEUE QMT1 amqmdain crtlsr QMT1 -t TCP -p 6001 amqmdain crtchi QMT1 SYSTEM.CHANNEL.INITQ amqmdain start QMT1 crtmqm -u SYSTEM.DEAD.LETTER.QUEUE QMT2 amqmdain crtlsr QMT2 -t TCP -p 6002 amqmdain crtchi QMT2 SYSTEM.CHANNEL.INITQ amqmdain start QMT2 crtmqm -u SYSTEM.DEAD.LETTER.QUEUE QMT2B amqmdain crtlsr QMT2B -t TCP -p 6012 amqmdain crtchi QMT2B SYSTEM.CHANNEL.INITQ amqmdain start QMT2B crtmqm -u SYSTEM.DEAD.LETTER.QUEUE QMGW amqmdain crtlsr QMGW -t TCP -p 6099 amqmdain crtchi QMGW SYSTEM.CHANNEL.INITQ amqmdain start QMGW runmqsc QMT1 qmt1.txt runmqsc QMT2 qmt2.txt runmqsc QMT2B qmt2b.txt runmqsc QMGW qmgw.txt
MQ V5.2 CSD4 New System Queue
All, When I create a queue manager I like the usual confirmation stating that 29 objects have been created. Then, having just applied CSD4 for MQ V5.2 on Windows, this number is now 30. There is a new system queue called SYSTEM.PENDING.DATA.QUEUE Also, if you run 'strmqm -c qmgr' this extra queue is added to an existing queue manager. There is no documentation in the readme for CSD4 and a trawl through the internet has not revealed anything. The comment on the queue itself states 'MQ deferred message q'. Any takers? Regards ... Ruud 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
AW: Communication about cluster boundaries
Hello Ruud, thank you for your answer, I will try it tomorrow. Please can you provide your four runmqsc cmdfiles, named qmt1.txt, qmt2.txt, qmt2b.txt, qmgw.txt I think, there is the tricky part. Henry Springer MQSeries Familie K-DOI-23 Volkswagen AG Brieffach 1891 38436 Wolfsburg Telefon +49-53 61-92 97 74 Telefax +49-53 61-92 28 13 eFax +49-5361-95 72 97 74 http://www.volkswagen.de -Ursprüngliche Nachricht- Von:Ruud van Zundert [mailto:[EMAIL PROTECTED]] Gesendet am:Dienstag, 28. Mai 2002 16:21 An: [EMAIL PROTECTED] Betreff:Re: Communication about cluster boundaries Datei: overlap.txt All - just had loads of notifications from various company's socalled 'anti-virus' programs. My attached called overlap.cmd was rejected. I have, therefore, renamed it to overlap.txt. Regards ... Ruud -Original Message- From: Ruud van Zundert [mailto:[EMAIL PROTECTED]] Sent: 28 May 2002 14:17 To: MQSeries List Subject: RE: Communication about cluster boundaries Henry - it's a bit tricky to get this to work, and if you follow this procedure, you should be ok: I've attached an example script that you can run on a Win2000 machine. It is re-runnable. This is what it does (run via 'overlap.cmd') : 1. define 4 qmgrs QMT1, QMT2, QMT2B and QMGW. QMT1 holds the full repository for cluster CL001. QMT2 holds the full repository for cluster CL002. QMT2B holds a partial repository for cluster CL002. QMGW is the 'gateway' linking the 2 clusters together. 2. Cluster queue QMT2.CQ is defined on both QMT2 and QMT2B. 3. A 'bridge' queue called BRIDGE is defined on the gateway as a QALIAS - it resides in cluster CL001, but points to target queue QMT2.CQ in cluster CL002. 4. To test: amqsput BRIDGE QMT1 Result : messages 'should' ;-) arrive on QMT2.CQ spread across qmgrs QMT2 and QMT2B. Let us know how you get on. Regards ... Ruud -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of Springer, Henry Sent: 28 May 2002 11:22 To: [EMAIL PROTECTED] Subject: Communication about cluster boundaries Hello all, we want to know, how to communicate about MQSeries Cluster boundaries. Because of firewall restrictions we had to build two overlapping cluster and the need to communicate between two nodes in both cluster. We want to use workload balancing, the queues reside on several cloned machines in both cluster. A small and simple scenario: QM1 belongs to Cluster1 and share a local Queue Q.TEST.ORIG in his cluster QM2 belongs to Cluster2 want to put a message to Q.TEST.ORIG. QMR belongs to Cluster1,Cluster2 and should act as a MQ-Gateway We do some tests and no one work properly: a) Define QALIAS Q.TEST on QMR shared in Cluster1, Cluster2 and point to Q.TEST.ORIG in the Cluster1 Result: Reason 2082 on QMR b) Define QREMOTE Q.TEST.1 on QMR shared in Cluster2, point to Q.TEST.ORIG (without naming a remote QMGR) Result: Reason: 2087 on QMR Defining a QREMOTE on QMR shared in Cluster2 and point to Q.TEST.ORIG on QM1, QM2 can send messages to the Q, but this is a lost of the workload balancing feature of the cluster. Henry Springer MQSeries Familie K-DOI-23 Volkswagen AG Brieffach 1891 38436 Wolfsburg Telefon +49-53 61-92 97 74 Telefax +49-53 61-92 28 13 eFax +49-5361-95 72 97 74 http://www.volkswagen.de 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: Put Message Date/Time
Do MQPMO-SET-CONTEXT and have your app set the time itself. Otherwise it's GMT From: Ryan Parmenter [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Put Message Date/Time Date: Tue, 28 May 2002 06:12:09 -0500 A fairly simple question for most of you, I hope. We are writing a single message to two queues, one the actual queue to transmit the message and the other an archiving queue. When I retrieve the messages from the archiving queue to write them to a SQL Server dbs, the Put date/time is GMT when the message has come from the Mainframe to NT, but current time (CST) when the message was sent from NT (the archive queue resides on the NT side). My question is this - how can I ensure that messages from the Mainframe are sent such that the Put date/time is current time and not GMT? We are planning an application for our PC support techs that will allow them to retrieve messages from the dbs based on date/time range and it would be nice for the date/time we store to be accurate/current time. Thanks. 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 _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp. 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: Howto save (and restore) the Queue manager configuration with IBM /MQ for Windows (PROTOm@il:20020527576 CENTROSIM)
Don't forget MS65 to automate it From: Emile Kearns [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Howto save (and restore) the Queue manager configuration with IBM /MQ for Windows(PROTOm@il:20020527576 CENTROSIM) Date: Tue, 28 May 2002 08:02:20 +0200 Download supportpac MS03, it saves the queue manager and its objects. This can be used to re-create your queue manager again Emile Kearns Software Futures -Original Message- From: Alessandro Caffarra [mailto:[EMAIL PROTECTED]] Sent: 27 May 2002 04:57 To: [EMAIL PROTECTED] Subject: Howto save (and restore) the Queue manager configuration with IBM /MQ for Windows (PROTOm@il:20020527576 CENTROSIM) Hi all, after some weeks of trial, I have just got a licensed IBM/MQ. Somebody told me that I must uninstall the trial version before to install the licensed one. Is it true? How can I save the current configuration and later restore it in the new version? Thanks for the help. Alessandro ***Internet Email Confidentiality Footer*** Qualsiasi utilizzo non autorizzato del presente messaggio nonche' dei suoi allegati e' vietato e potrebbe costituire reato. Se lei ha ricevuto erroneamente il presente messaggio, Le saremmo grati se, via e-mail, ce ne comunicasse la ricezione e provvedesse alla distruzione del messaggio stesso e dei suoi eventuali allegati. Le dichiarazioni contenute nel presente messaggio nonche' nei suoi eventuali allegati devono essere attribuite esclusivamente al mittente e non possono essere considerate come trasmesse o autorizzate da CENTROSIM S.p.A.; le medesime dichiarazioni non impegnano CENTROSIM S.p.A. nei confronti del destinatario o di terzi. CENTROSIM S.p.A. non si assume alcuna responsabilita' per eventuali intercettazioni, modifiche o danneggiamenti del presente messaggio e-mail. The information transmitted is intended only for the person or entity to wich it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. 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 _ Chat with friends online, try MSN Messenger: http://messenger.msn.com 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: Howto save (and restore) the Queue manager configuration with IBM /MQ for Windows (PROTOm@il:20020527576 CENTROSIM)
Assuming he's running under UNIX. -Original Message- From: Robert Broderick [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 28, 2002 11:16 AM To: [EMAIL PROTECTED] Subject: Re: Howto save (and restore) the Queue manager configuration with IBM /MQ for Windows (PROTOm@il:20020527576 CENTROSIM) Don't forget MS65 to automate it From: Emile Kearns [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Howto save (and restore) the Queue manager configuration with IBM /MQ for Windows(PROTOm@il:20020527576 CENTROSIM) Date: Tue, 28 May 2002 08:02:20 +0200 Download supportpac MS03, it saves the queue manager and its objects. This can be used to re-create your queue manager again Emile Kearns Software Futures -Original Message- From: Alessandro Caffarra [mailto:[EMAIL PROTECTED]] Sent: 27 May 2002 04:57 To: [EMAIL PROTECTED] Subject: Howto save (and restore) the Queue manager configuration with IBM /MQ for Windows (PROTOm@il:20020527576 CENTROSIM) Hi all, after some weeks of trial, I have just got a licensed IBM/MQ. Somebody told me that I must uninstall the trial version before to install the licensed one. Is it true? How can I save the current configuration and later restore it in the new version? Thanks for the help. Alessandro ***Internet Email Confidentiality Footer*** Qualsiasi utilizzo non autorizzato del presente messaggio nonche' dei suoi allegati e' vietato e potrebbe costituire reato. Se lei ha ricevuto erroneamente il presente messaggio, Le saremmo grati se, via e-mail, ce ne comunicasse la ricezione e provvedesse alla distruzione del messaggio stesso e dei suoi eventuali allegati. Le dichiarazioni contenute nel presente messaggio nonche' nei suoi eventuali allegati devono essere attribuite esclusivamente al mittente e non possono essere considerate come trasmesse o autorizzate da CENTROSIM S.p.A.; le medesime dichiarazioni non impegnano CENTROSIM S.p.A. nei confronti del destinatario o di terzi. CENTROSIM S.p.A. non si assume alcuna responsabilita' per eventuali intercettazioni, modifiche o danneggiamenti del presente messaggio e-mail. The information transmitted is intended only for the person or entity to wich it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. 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 _ Chat with friends online, try MSN Messenger: http://messenger.msn.com 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
Problem receiving messages from a restarted client application.
I've got an application developer with an MQ Client situation I cannot fully explain. I'm hoping someone can shed some light on this. The application is a long running MQ Client that services a low volume queue. It was written with unlimited waits and has syncpoint logic to prevent the loss of messages if/when the client application abnormally stops. The problem happens if the application terminates (not clean, they just kill it), and they restart a new instance of the application with no messages on the queue. Once a message is arrives on the queue the new service never returns the message. We do see that as expected the IPPROCS show the original instance of the client's agent does not go away until the new message arrives. Furthermore we can see that with the syncpointing the agent rolls the message back to the queue when it determines that the client channel is gone. At this point the message is available for retrieval and be have been able to browse it or retrieve it by staring another instance of the application after the message already exists on the queue. However it the second instance of the application is already waiting for the message before it arrives, then it just waits indefinitely. I was not able to replicate this until I forced a truncation error. The application is written in JAVA and the messages are greater than the default 4096 buffer so we know his agent should be running into a truncation error situation. The application has been changed on our advice. It now is a triggered application with a more reasonable wait interval and a controlled method of stopping the application. However I'd still like to understand why the second service failed to receive the message. I've found nothing in the manuals to support this, and frankly I could see other Java or JMS applications running into this if they abnormally terminate and are restarted before a message arrives. Rick 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 V5.2 CSD4 New System Queue
Ruud, I have to say upfront that I don't know the documented truth, but it 'smells' like it has something to do with what is described in this recent post: http://www.messageq.com/forums/vienna/msg_body.php3?ID=31105 Obviously CSD04 introduces support for deferred messages that will only be made availble to other applications at the time the producing application disconnects. Hopr that helps, Stefan From: Ruud van Zundert [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: MQ V5.2 CSD4 New System Queue Date: Tue, 28 May 2002 15:35:13 +0100 All, When I create a queue manager I like the usual confirmation stating that 29 objects have been created. Then, having just applied CSD4 for MQ V5.2 on Windows, this number is now 30. There is a new system queue called SYSTEM.PENDING.DATA.QUEUE Also, if you run 'strmqm -c qmgr' this extra queue is added to an existing queue manager. There is no documentation in the readme for CSD4 and a trawl through the internet has not revealed anything. The comment on the queue itself states 'MQ deferred message q'. Any takers? Regards ... Ruud 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 _ Send and receive Hotmail on your mobile device: http://mobile.msn.com 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
MQSeries PUB/SUB
All, We are trying to setup an MQSeries PUB/SUB environment on HP-UX v.11 running MQ 5.2 with CSD04. We've installed SupportPacs - MA0C (MQSeries - Publish/Subscribe) and MA0F (MQSeries Application Messaging Interface). We seem to have a problem after we've created and started a QMGR and we attempt to start the broker (strmqbrk -m QMgrName). We receive the message - 'MQSeries message broker for queue manager PUBSUB not active.' The QMGR error logs contains the following error - An attempt has been made to run the MQSeries message broker (PUBSUB) but the broker has ended for reason '5800: (Unexpected Error)'. Thanks for any help that can be provided. begin:vcard n:Cook;Stephen tel;cell:(336)926-2134 tel;fax:(336)744-6509 tel;home:(336)764-3818 tel;work:(336)744-6650 x-mozilla-html:FALSE org:IMG SRC=http://fedesk.sabre.com/images/logo.gif; ;EDS Connectivity Middleware Solutions adr:;;;Winston-Salem;NC;27105;USA version:2.1 email;internet:[EMAIL PROTECTED] title:Infrastructure Specialist fn:Stephen Cook end:vcard
Read Receipt for a Message
If I have a client putting messages on a queue, can I get some sort of indication that the message was read without building this into the application layer? What I think I mean is can MQ be configured to send a read receipt automatically or do I have to create something on the application layer? Wayne 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: Read Receipt for a Message
Have your sending application set the MQRO-COD option in the MQMD-REPORT field. In the Reply-to-Queue field, place the name of the queue you want this report to go to. The receiving QM on the other side will automatically send you a report when somebody GETS this message on the other side. Peter Potkay IBM MQSeries Certified Specialist, Developer [EMAIL PROTECTED] X 77906 -Original Message- From: Wayne Happ [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 28, 2002 2:03 PM To: [EMAIL PROTECTED] Subject: Read Receipt for a Message If I have a client putting messages on a queue, can I get some sort of indication that the message was read without building this into the application layer? What I think I mean is can MQ be configured to send a read receipt automatically or do I have to create something on the application layer? Wayne 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
Re: MQ V5.2 CSD4 New System Queue
Stefan - thanks. I've read the post, and you're right, it could have something to do with a 'pub/sub deferred deregister message' (try and say that quickly ;-) ). Any IBMers wish to comment as well? Regards ... Ruud -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of Stefan Sievert Sent: 28 May 2002 18:12 To: [EMAIL PROTECTED] Subject: Re: MQ V5.2 CSD4 New System Queue Ruud, I have to say upfront that I don't know the documented truth, but it 'smells' like it has something to do with what is described in this recent post: http://www.messageq.com/forums/vienna/msg_body.php3?ID=31105 Obviously CSD04 introduces support for deferred messages that will only be made availble to other applications at the time the producing application disconnects. Hopr that helps, Stefan From: Ruud van Zundert [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: MQ V5.2 CSD4 New System Queue Date: Tue, 28 May 2002 15:35:13 +0100 All, When I create a queue manager I like the usual confirmation stating that 29 objects have been created. Then, having just applied CSD4 for MQ V5.2 on Windows, this number is now 30. There is a new system queue called SYSTEM.PENDING.DATA.QUEUE Also, if you run 'strmqm -c qmgr' this extra queue is added to an existing queue manager. There is no documentation in the readme for CSD4 and a trawl through the internet has not revealed anything. The comment on the queue itself states 'MQ deferred message q'. Any takers? Regards ... Ruud 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 _ Send and receive Hotmail on your mobile device: http://mobile.msn.com 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
Distribution Queues on 5.2/390
Quick question, Does OS/390 MQSeries V5.2 support Distribution Queues? I see from the Application Programming guide that it doesn't as far as I can tell...but is there an APAR or something to allow it to? Will future release 5.3? support them? Thanks in advance, Mike Michael S. LawrenceSystems ProgrammerAtlas Van Lines [EMAIL PROTECTED]wk# (812) 424-4326 x2652fax# (812) 421-7153
Re: MQ V5.2 CSD4 New System Queue
Yes, This is the internal queue that the queue manager uses to guarantee that non durable JMS subscriptions are deregistered in the event of an unexpected termination of either the queue manager or the subscriber. There's also a new queue manager process (amqzdma) which manages the queue. Andy. Ruud van Zundert [EMAIL PROTECTED]@AKH-WIEN.AC.AT on 28/05/2002 19:25:23 Please respond to MQSeries List [EMAIL PROTECTED] Sent by:MQSeries List [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Re: MQ V5.2 CSD4 New System Queue Stefan - thanks. I've read the post, and you're right, it could have something to do with a 'pub/sub deferred deregister message' (try and say that quickly ;-) ). Any IBMers wish to comment as well? Regards ... Ruud -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of Stefan Sievert Sent: 28 May 2002 18:12 To: [EMAIL PROTECTED] Subject: Re: MQ V5.2 CSD4 New System Queue Ruud, I have to say upfront that I don't know the documented truth, but it 'smells' like it has something to do with what is described in this recent post: http://www.messageq.com/forums/vienna/msg_body.php3?ID=31105 Obviously CSD04 introduces support for deferred messages that will only be made availble to other applications at the time the producing application disconnects. Hopr that helps, Stefan From: Ruud van Zundert [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: MQ V5.2 CSD4 New System Queue Date: Tue, 28 May 2002 15:35:13 +0100 All, When I create a queue manager I like the usual confirmation stating that 29 objects have been created. Then, having just applied CSD4 for MQ V5.2 on Windows, this number is now 30. There is a new system queue called SYSTEM.PENDING.DATA.QUEUE Also, if you run 'strmqm -c qmgr' this extra queue is added to an existing queue manager. There is no documentation in the readme for CSD4 and a trawl through the internet has not revealed anything. The comment on the queue itself states 'MQ deferred message q'. Any takers? Regards ... Ruud 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 _ Send and receive Hotmail on your mobile device: http://mobile.msn.com 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 PUB/SUB
Are you running draft 4 or draft 11 threads, does your broker match your queue manager in this respect ? (e.g does strmqbrk link to strmqbrk_d, does endmqm link to endmqm_d). Note that HP performance is MUCH improved when running draft 11 threads. Were any FDC's produced ? If not then it is likely that a trace will be required to understand what's going on. If you'd like to send me a trace then I'll have a look, but I probably won't get to it until Thursday at the earliest. Andy. Stephen Cook [EMAIL PROTECTED]@AKH-WIEN.AC.AT on 28/05/2002 18:17:26 Please respond to MQSeries List [EMAIL PROTECTED] Sent by:MQSeries List [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:MQSeries PUB/SUB All, We are trying to setup an MQSeries PUB/SUB environment on HP-UX v.11 running MQ 5.2 with CSD04. We've installed SupportPacs - MA0C (MQSeries - Publish/Subscribe) and MA0F (MQSeries Application Messaging Interface). We seem to have a problem after we've created and started a QMGR and we attempt to start the broker (strmqbrk -m QMgrName). We receive the message - 'MQSeries message broker for queue manager PUBSUB not active.' The QMGR error logs contains the following error - An attempt has been made to run the MQSeries message broker (PUBSUB) but the broker has ended for reason '5800: (Unexpected Error)'. Thanks for any help that can be provided. 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 PUB/SUB
Cleaning up the shared memory segments and semaphores didn't seem to help. There are not any SYSTEM.BROKER.* queues defined but it's my understanding those queues are defined when the broker is started (strmqbrk). The userid that is trying to start the broker is a member of the MQM group and root as been added to the MQM group as well. Any other thoughts? Thanks. Ed Murphy wrote: The broker should automatically create the queues (SYSTEM.BROKER.*) that are needed for it to work. Steve: Please look in the MQ Explorer with the system objects displayed. Do you see a set of SYSTEM.BROKER queues? Is the user that is running the broker a member of the MQM group? Regards, Ed -Original Message- From: Ramnath Cidambi [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 28, 2002 1:56 PM To: [EMAIL PROTECTED] Subject: Re: MQSeries PUB/SUB Steve We have it running in production without any problems. Do you have the SYSTEM queues required for running the broker? End the queue manager, see if any ipc's are hanging (using ipcs command). If they are remove them. Then start the queue manager and then start the broker. Thanks -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 28, 2002 12:17 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: MQSeries PUB/SUB All, We are trying to setup an MQSeries PUB/SUB environment on HP-UX v.11 running MQ 5.2 with CSD04. We've installed SupportPacs - MA0C (MQSeries - Publish/Subscribe) and MA0F (MQSeries Application Messaging Interface). We seem to have a problem after we've created and started a QMGR and we attempt to start the broker (strmqbrk -m QMgrName). We receive the message - 'MQSeries message broker for queue manager PUBSUB not active.' The QMGR error logs contains the following error - An attempt has been made to run the MQSeries message broker (PUBSUB) but the broker has ended for reason '5800: (Unexpected Error)'. Thanks for any help that can be provided. 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 begin:vcard n:Cook;Stephen tel;cell:(336)926-2134 tel;fax:(336)744-6509 tel;home:(336)764-3818 tel;work:(336)744-6650 x-mozilla-html:FALSE org:IMG SRC=http://fedesk.sabre.com/images/logo.gif; ;EDS Connectivity Middleware Solutions adr:;;;Winston-Salem;NC;27105;USA version:2.1 email;internet:[EMAIL PROTECTED] title:Infrastructure Specialist fn:Stephen Cook end:vcard
Re: MQSeries PUB/SUB
strmqbrk does not match the queue manager in this respect - strmqbrk does not link to strmqbrk_d but endmqm does link to endmqm_d. Each attempt to start the broker does produce an FDC. Should I send the FDC? Thanks. Andrew Hickson wrote: Are you running draft 4 or draft 11 threads, does your broker match your queue manager in this respect ? (e.g does strmqbrk link to strmqbrk_d, does endmqm link to endmqm_d). Note that HP performance is MUCH improved when running draft 11 threads. Were any FDC's produced ? If not then it is likely that a trace will be required to understand what's going on. If you'd like to send me a trace then I'll have a look, but I probably won't get to it until Thursday at the earliest. Andy. Stephen Cook [EMAIL PROTECTED]@AKH-WIEN.AC.AT on 28/05/2002 18:17:26 Please respond to MQSeries List [EMAIL PROTECTED] Sent by:MQSeries List [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:MQSeries PUB/SUB All, We are trying to setup an MQSeries PUB/SUB environment on HP-UX v.11 running MQ 5.2 with CSD04. We've installed SupportPacs - MA0C (MQSeries - Publish/Subscribe) and MA0F (MQSeries Application Messaging Interface). We seem to have a problem after we've created and started a QMGR and we attempt to start the broker (strmqbrk -m QMgrName). We receive the message - 'MQSeries message broker for queue manager PUBSUB not active.' The QMGR error logs contains the following error - An attempt has been made to run the MQSeries message broker (PUBSUB) but the broker has ended for reason '5800: (Unexpected Error)'. Thanks for any help that can be provided. 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 begin:vcard n:Cook;Stephen tel;cell:(336)926-2134 tel;fax:(336)744-6509 tel;home:(336)764-3818 tel;work:(336)744-6650 x-mozilla-html:FALSE org:IMG SRC=http://fedesk.sabre.com/images/logo.gif; ;EDS Connectivity Middleware Solutions adr:;;;Winston-Salem;NC;27105;USA version:2.1 email;internet:[EMAIL PROTECTED] title:Infrastructure Specialist fn:Stephen Cook end:vcard
