|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
General knowledge |
« View previous topic :: View next topic » |
Author |
Message
|
ktg |
Posted: Wed May 31, 2006 10:55 pm Post subject: General knowledge |
|
|
Centurion
Joined: 09 Jan 2006 Posts: 138 Location: India
|
Hi People,
Why don't we have MQGET1 similar to MQPUT1?
Regards, |
|
Back to top |
|
 |
Mr Butcher |
Posted: Wed May 31, 2006 11:13 pm Post subject: |
|
|
 Padawan
Joined: 23 May 2005 Posts: 1716
|
you know before the put if you want to put only one message.
but when you get you never know how many messages are there for get. so mqget1 does not really makes sense (in most cases). the recommendation is to loop on the queue until queue is empty.
my 2 cents, your mileage may vary. _________________ Regards, Butcher |
|
Back to top |
|
 |
jefflowrey |
Posted: Thu Jun 01, 2006 5:10 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Mr Butcher wrote: |
the recommendation is to loop on the queue until queue is empty. |
More particularly, to loop on the queue until the GET returns a 2033 return code. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
tleichen |
Posted: Thu Jun 01, 2006 6:18 am Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005 Posts: 663 Location: Center of the USA
|
Also, not to mention the overhead difference involved in MQPUT1 vs. MQPUT. I don't think you want some lackey coding an MQGET sequence that would essentially do:
MQCONN, MQOPEN, MQGET, MQCLOSE, MQDISC... over and over again.
 _________________ IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
Back to top |
|
 |
ktg |
Posted: Fri Jun 02, 2006 4:35 am Post subject: |
|
|
Centurion
Joined: 09 Jan 2006 Posts: 138 Location: India
|
"Thanks a lot" people, for ur answers...
Have a nice week end
Regards, |
|
Back to top |
|
 |
wschutz |
Posted: Fri Jun 02, 2006 4:58 am Post subject: |
|
|
 Jedi Knight
Joined: 02 Jun 2005 Posts: 3316 Location: IBM (retired)
|
tleichen wrote: |
Also, not to mention the overhead difference involved in MQPUT1 vs. MQPUT. I don't think you want some lackey coding an MQGET sequence that would essentially do:
MQCONN, MQOPEN, MQGET, MQCLOSE, MQDISC... over and over again.
 |
I'm sure you didn't mean to imply that the MQPUT1 does a MQCONN/MQDISC. The MQPUT1 is the equivalent of MQOPEN,MQPUT,MQCLOSE. _________________ -wayne |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|