Re: MQ53 - PF4 prompt
Hi, We have the same problem but it seems that this bypass (adding &THLQUAL.SCSQTBLE) in the SYSPROC concatenation doesn't works for us. After investigation, we've seen that the problem seems to be due to a pfkeys profile mismatch. Anyone have the solution to solve this ? We have not found anything about this problem on IBM site. Wat is the status of your PMR 16704, now ? thanks a lot for help. Best Regards, Denis Denis Blondiaux Dexia Banque Belgium +32 2 222 6703 -Original Message- From: Andrew Miller [mailto:[EMAIL PROTECTED] Sent: jeudi 19 décembre 2002 14:54 To: [EMAIL PROTECTED] Subject: Re: MQ53 - PF4 prompt I raised PMR 16704 raised with IBM due to problems with new panels. The solution to this in short was to add SYS1.SCSQTBLE to the ISPF SYSPROC concatenation. I have asked that a DOC APAR be raised at very least as this came out of the blue. HTH Windy On 16/12/2002 16:42:21 MQSeries List wrote: >A couple of months ago we installed 5.3 (MQ OS/390), but just recently noticed >that PF4 (used to give a full list of objects from the CSQ0REXX menu) is >presenting only the first seven object types?. The screen indicates that a PF8 >would give you "More", yet it just takes you back to the main menu ? Has anyone >else seen this, or perhaps it's something we had to do w/the rexx exec? Any >ideas? > > > >Dave [EMAIL PROTECTED] For more information on Standard Life, visit our website http://www.standardlife.com/ The Standard Life Assurance Company, Standard Life House, 30 Lothian Road, Edinburgh EH1 2DH, is registered in Scotland (No. SZ4) and regulated by the Financial Services Authority. Tel: 0131 225 2552 - calls may be recorded or monitored. This confidential e-mail is for the addressee only. If received in error, do not retain/copy/disclose it without our consent and please return it to us. We virus scan and monitor all e-mails but are not responsible for any damage caused by a virus or alteration by a third party after it is sent. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive -- Visit our websites http://www.dexia.be - http://www.axionweb.be "The information contained in this message is intended for the addressee only and may contain confidential and/or privileged information and/or information protected by intellectual property rights. If you are not the addressee, please delete this message and notify the sender; you should not use, alter, copy or distribute this message or disclose its contents to anyone. Email transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. No responsibility is accepted by Dexia Bank for any loss or damage arising in any way from its use. Any views or opinions expressed in this message are those of the author and do not necessarily represent those of Dexia Bank or any of its affiliates. Therefore this email does not constitute a commitment by Dexia bank unless it contains an express statement to the contrary from an authorised representative." Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Channel State - Retrying
Hi, Stop and reset the channel then start it again. When the sequence number stuffs up the channel goes into retry. Sid -Original Message- From: Sony Varghese [mailto:[EMAIL PROTECTED] Sent: Wednesday, 28 May 2003 6:48 PM To: [EMAIL PROTECTED] Subject: Channel State - Retrying Hi everyone, When does a channel go into the retry state? I have a scenario where 2 qmgrs QM1 and QM2 communicate with each other. I've defined sender channel QM1.QM2 on QM1 and a corresponding receiver channel on QM2 QM2 is on a clustered node consisting of 2 members M1 and M2. As a part of my test, I initially put 200 messages on a remote definition queue on QM1 and all the 200 messages are transferred to the corresponding queue on QM2. No problems here !! Both the sender and receiver channel are in the running state at this point. While the channels are in the running state i switch/relocate QM2 from member M1 to M2. During relocation, QM2 is ended in the following way: - endmqm -i : If this takes more than a specified time, - endmqm -p If this takes more than a specified time, - manually stopping the queue manager Once QM2 comes back up again, the receiver channel is inactive but the sender is still running .. I thought that at this point the sender channel would go to retrying state but it still remains in the running state? I put another 200 messages but the messages are not delivered to the queue on QM2. However, the transmission queue on QM1 is empty and the sender channel status shows me a message count of 400. Has anyone faced this before? Do reply, Thanks, VJ Instructions for managing your mailing list 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: opening multiple connections from C program on solaris
Hi, The reason for requiring multiple connections - is the application is designed as a gateway to two other applicatins. Hence there is a possiblity of getting messages from either interfaces asynchronously. further the async. processing is based on a dialog. Unless the dialog is complete, messages that are retreived or put cannot be commited. If there is an error in completing the dialog, then it should be rolled-back for the particular message in question, rather than for all messges that have been handled on that connection (within a given time-interval), but the status of other messages in other queues would be different ( because the dialog may not be complete ..because the application is waiting for a response to arrive, while it is currently someother message on a different queue). Then we have a problem of data consistency. rgds lakshmi > -Original Message- > From: Paul Clarke [SMTP:[EMAIL PROTECTED] > Sent: Wednesday, May 28, 2003 11:21 AM > To: [EMAIL PROTECTED] > Subject: Re: opening multiple connections from C program on solaris > > >Hi, > > >Is it possible to set-up multiple MQ connections from a program in Solaris > env. I tired to set-up multiple connections, but the >connection handle is > the same for all of them. Is it possible to get unique connection-handles > for each connection. > > >The reason for this requirement is that the program has to handle multiple > queues, and the application has to issue MQCMIT based >on the data received > in the queues. The program is designed for a real-time asynchronous > communication. The application is >up-running all the time and keeps > polling it other interfaces to check if data has arrived. Based n the data > received from other >interfaces, it has to PUT the message into an MQ Queue > and commit it. It is also a single -threaded application. > > > >mfg > >lakshmi > > Prior to 5.3 you could only have one connection to one Queue Manager in > each thread. Since your application is single threaded then you can only > have one connection. I would expect you to get back reason code > MQRC_ALREADY_CONNECTED on your subsequent attempts to connect. In 5.3 you > can ask for 'shared' connection when you issue MQCONNX. This connection can > be used across threads and you can issue MQCONN multiple times on the same > thread. > > What I don't quite understand is why, in a single threaded application that > seems to be issuing one MQPUT, you need to have multiple connections to the > Queue Manager anyway. > > Cheers, > P. > > Paul G Clarke > WebSphere MQ Development > IBM Hursley > > Instructions for managing your mailing list subscription are provided in > the Listserv General Users Guide available at http://www.lsoft.com > Archive: http://vm.akh-wien.ac.at/MQSeries.archive The content of this e-mail is intended only for the confidential use of the person addressed. If you have received this message in error, please notify us immediately by electronic mail, by telephone or by fax at the above num- bers. E-mail communications are not secure and therefore we do not accept any res- ponsibility for the confidentiality or altered contents of this message. Please be aware that SIS Group and its subsidiary companies cannot accept any orders or other legally binding correspondence with a participant as part of an E-mail. The views expressed above are not necessarily those held by SIS Group and its subsidiary companies and not binding for them. exfe Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Channel State - Retrying
Hi Hubert, Here is my present test scenario: I'm presently using TruCluster V5.1 (Cluster software for Compaq Tru64 Unix) During relocation, I am not taking over the filesystem /var/mqm . Will this cause a problem? My test messages presently are not persistent . Channel attribute NPMSPEED is set to Fast. Awaiting your reply, Warm Regards, VJ. -Original Message- From: Kleinmanns, Hubert [mailto:[EMAIL PROTECTED] Sent: 28 May 2003 10:23 To: [EMAIL PROTECTED] Subject: AW: Channel State - Retrying Hi Sony, some questions: What cluster do you use (HACMP, SunHA, Veritas ...) ? Do you take over the file system /var/mqm ? Are your messages persistent ? What is the value of the channel attribut NPMSPEED ? Regards Hubert Kleinmanns -Ursprüngliche Nachricht- Von: Sony Varghese [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 28. Mai 2003 10:48 An: [EMAIL PROTECTED] Betreff: Channel State - Retrying Hi everyone, When does a channel go into the retry state? I have a scenario where 2 qmgrs QM1 and QM2 communicate with each other. I've defined sender channel QM1.QM2 on QM1 and a corresponding receiver channel on QM2 QM2 is on a clustered node consisting of 2 members M1 and M2. As a part of my test, I initially put 200 messages on a remote definition queue on QM1 and all the 200 messages are transferred to the corresponding queue on QM2. No problems here !! Both the sender and receiver channel are in the running state at this point. While the channels are in the running state i switch/relocate QM2 from member M1 to M2. During relocation, QM2 is ended in the following way: - endmqm -i : If this takes more than a specified time, - endmqm -p If this takes more than a specified time, - manually stopping the queue manager Once QM2 comes back up again, the receiver channel is inactive but the sender is still running .. I thought that at this point the sender channel would go to retrying state but it still remains in the running state? I put another 200 messages but the messages are not delivered to the queue on QM2. However, the transmission queue on QM1 is empty and the sender channel status shows me a message count of 400. Has anyone faced this before? Do reply, Thanks, VJ Instructions for managing your mailing list 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: opening multiple connections from C program on solaris
>Hi, >Is it possible to set-up multiple MQ connections from a program in Solaris env. I tired to set-up multiple connections, but the >connection handle is the same for all of them. Is it possible to get unique connection-handles for each connection. >The reason for this requirement is that the program has to handle multiple queues, and the application has to issue MQCMIT based >on the data received in the queues. The program is designed for a real-time asynchronous communication. The application is >up-running all the time and keeps polling it other interfaces to check if data has arrived. Based n the data received from other >interfaces, it has to PUT the message into an MQ Queue and commit it. It is also a single -threaded application. >mfg >lakshmi Prior to 5.3 you could only have one connection to one Queue Manager in each thread. Since your application is single threaded then you can only have one connection. I would expect you to get back reason code MQRC_ALREADY_CONNECTED on your subsequent attempts to connect. In 5.3 you can ask for 'shared' connection when you issue MQCONNX. This connection can be used across threads and you can issue MQCONN multiple times on the same thread. What I don't quite understand is why, in a single threaded application that seems to be issuing one MQPUT, you need to have multiple connections to the Queue Manager anyway. Cheers, P. Paul G Clarke WebSphere MQ Development IBM Hursley Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
AW: Channel State - Retrying
Hi Sony, some questions: What cluster do you use (HACMP, SunHA, Veritas ...) ? Do you take over the file system /var/mqm ? Are your messages persistent ? What is the value of the channel attribut NPMSPEED ? Regards Hubert Kleinmanns -Ursprüngliche Nachricht- Von: Sony Varghese [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 28. Mai 2003 10:48 An: [EMAIL PROTECTED] Betreff: Channel State - Retrying Hi everyone, When does a channel go into the retry state? I have a scenario where 2 qmgrs QM1 and QM2 communicate with each other. I've defined sender channel QM1.QM2 on QM1 and a corresponding receiver channel on QM2 QM2 is on a clustered node consisting of 2 members M1 and M2. As a part of my test, I initially put 200 messages on a remote definition queue on QM1 and all the 200 messages are transferred to the corresponding queue on QM2. No problems here !! Both the sender and receiver channel are in the running state at this point. While the channels are in the running state i switch/relocate QM2 from member M1 to M2. During relocation, QM2 is ended in the following way: - endmqm -i : If this takes more than a specified time, - endmqm -p If this takes more than a specified time, - manually stopping the queue manager Once QM2 comes back up again, the receiver channel is inactive but the sender is still running .. I thought that at this point the sender channel would go to retrying state but it still remains in the running state? I put another 200 messages but the messages are not delivered to the queue on QM2. However, the transmission queue on QM1 is empty and the sender channel status shows me a message count of 400. Has anyone faced this before? Do reply, Thanks, VJ Instructions for managing your mailing list 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: Channel State - Retrying
This looks like a message sequencing problem. Try resetting the sequence # -Original Message- From: Sony Varghese [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2003 2:18 PM To: [EMAIL PROTECTED] Subject: Channel State - Retrying Hi everyone, When does a channel go into the retry state? I have a scenario where 2 qmgrs QM1 and QM2 communicate with each other. I've defined sender channel QM1.QM2 on QM1 and a corresponding receiver channel on QM2 QM2 is on a clustered node consisting of 2 members M1 and M2. As a part of my test, I initially put 200 messages on a remote definition queue on QM1 and all the 200 messages are transferred to the corresponding queue on QM2. No problems here !! Both the sender and receiver channel are in the running state at this point. While the channels are in the running state i switch/relocate QM2 from member M1 to M2. During relocation, QM2 is ended in the following way: - endmqm -i : If this takes more than a specified time, - endmqm -p If this takes more than a specified time, - manually stopping the queue manager Once QM2 comes back up again, the receiver channel is inactive but the sender is still running .. I thought that at this point the sender channel would go to retrying state but it still remains in the running state? I put another 200 messages but the messages are not delivered to the queue on QM2. However, the transmission queue on QM1 is empty and the sender channel status shows me a message count of 400. Has anyone faced this before? Do reply, Thanks, VJ Instructions for managing your mailing list 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
Channel State - Retrying
Hi everyone, When does a channel go into the retry state? I have a scenario where 2 qmgrs QM1 and QM2 communicate with each other. I've defined sender channel QM1.QM2 on QM1 and a corresponding receiver channel on QM2 QM2 is on a clustered node consisting of 2 members M1 and M2. As a part of my test, I initially put 200 messages on a remote definition queue on QM1 and all the 200 messages are transferred to the corresponding queue on QM2. No problems here !! Both the sender and receiver channel are in the running state at this point. While the channels are in the running state i switch/relocate QM2 from member M1 to M2. During relocation, QM2 is ended in the following way: - endmqm -i : If this takes more than a specified time, - endmqm -p If this takes more than a specified time, - manually stopping the queue manager Once QM2 comes back up again, the receiver channel is inactive but the sender is still running .. I thought that at this point the sender channel would go to retrying state but it still remains in the running state? I put another 200 messages but the messages are not delivered to the queue on QM2. However, the transmission queue on QM1 is empty and the sender channel status shows me a message count of 400. Has anyone faced this before? Do reply, Thanks, VJ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
opening multiple connections from C program on solaris
Hi, Is it possible to set-up multiple MQ connections from a program in Solaris env. I tired to set-up multiple connections, but the connection handle is the same for all of them. Is it possible to get unique connection-handles for each connection. The reason for this requirement is that the program has to handle multiple queues, and the application has to issue MQCMIT based on the data received in the queues. The program is designed for a real-time asynchronous communication. The application is up-running all the time and keeps polling it other interfaces to check if data has arrived. Based n the data received from other interfaces, it has to PUT the message into an MQ Queue and commit it. It is also a single -threaded application. mfg lakshmi The content of this e-mail is intended only for the confidential use of the person addressed. If you have received this message in error, please notify us immediately by electronic mail, by telephone or by fax at the above num- bers. E-mail communications are not secure and therefore we do not accept any res- ponsibility for the confidentiality or altered contents of this message. Please be aware that SIS Group and its subsidiary companies cannot accept any orders or other legally binding correspondence with a participant as part of an E-mail. The views expressed above are not necessarily those held by SIS Group and its subsidiary companies and not binding for them. exfe Instructions for managing your mailing list 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 Client
Dankie Francois. The ideal solution for my client would be to have MQServers at all the remote locations, but unfortunately the client is VERY price sensitive and will not be able to afford it. He does however still want assured one time message delivery and that is where the concern about assured message delivery using clients came from. Thanks for everyone's comments. Regards Andre van Zyl -Original Message- From: Francois Van der Merwe1 [mailto:[EMAIL PROTECTED] Sent: 27 May 2003 12:53 To: [EMAIL PROTECTED] Subject: Re: MQ Client Andre, I think one of the concerns in the "server concentrator" setup is that the "window of opportunity for something to go wrong" is bigger when the clients connect to a server that is a long way from it or when the client connections are slow. Yes, you must use syncpoint, and yes, you must use COA or COD or both, but you need to think about what must you do when something goes wrong. For instance, say you receive a COA but no COD and then the connection brake? Is that good enough reason to resend the message or not? Maybe it will be best if the "server" side application know how to handle duplicates, so that if the client does not know what to do, then it can just resend. Also, if the volume is high, then server to server connections is usually faster. Some pros for client connection: Client can connect to more than one QM at a time. Client can automatically use alternate channels when primary is down Client is really cheap Simpler admin Cons Performance suffers No DB XA stuff No local Q's Expose to network outages memory overhead on server for every client connection no clustering no UOW coordination Client is synchronous less control over channels, no keepalive, No batching of high volume messages Francois van der Merwe Senior IT Specialist: IBM MQSeries Certified Specialist, Solutions Expert & Developer IBM, Cape Town, South Africa +27 (0)82 556 9467 / +27 (0)21 402 5597 [EMAIL PROTECTED] "van Zyl, Andre" <[EMAIL PROTECTED]To: [EMAIL PROTECTED] .SAPPI.COM> cc: Sent by: MQSeriesSubject: Re: MQ Client List <[EMAIL PROTECTED] N.AC.AT> 05/27/2003 03:46 PM Please respond to MQSeries List Thanks -Original Message- From: Paul Clarke [mailto:[EMAIL PROTECTED] Sent: 27 May 2003 02:30 To: [EMAIL PROTECTED] Subject: Re: MQ Client >The question / concern I have has to do with assured message delivery when >using MQClients. >We are starting a new project which involves one central MQServer with >several distributed MQClients (all connected via a secure WAN). >We know that with MQServer, message delivery is assured. It is however >expensive to have many queue managers all over the show if the same >objective can be obtained by means of MQClients. >The only issue which now arises is how do I ensure assured message delivery? Andre, The semantics of messaging is exactly the same for a client as for a locally connected application. In other words, in order to do reliable messaging in a local application you must follow a certain set of rules like issuing MQPUTs and MQGETs under transactions etc. These rules are exactly the same for a client. One area which often concerns programmers is the MQCMIT call. What happens if you lose your network half way through an MQCMIT verb and get a MQRC_CONNECTION_BROKEN reason code. Did the transaction commit or didn't it ? Well, this is the same for a local application, you are not guaranteed to get a definitive answer on your transaction commit even for the local application. If you really care, you must do some 'known' action (like put a message to a queue) that you can subsequently check the next time you connect. The principle difference between a client and a local application is that clients (at least the free ones) can not have other resource managers involved in the transaction. So if you want a client application to update a database in the same transaction as an MQPUT call then you should either have a real Queue Manager or use the new Transactional Client product (which costs money). So, on the face of it, you can now do pretty much everything as a client that you can do locally. This does not mean however that regardless of the size of your organisation or the location of your applications that you should just have one server in the middle and everyone else connect as clients. There are many reasons why you might want queues more localised to your applications quite apart from the limiting factor of how many applications is it reasonable to have a single server serve. Hope this helps, P. Paul G Clarke WebSphere MQ Development IBM Hursley Instructions for managing your mailing list subscription are provided in the Listserv Ge
