Thanks for the info. I tried several different ways - include changing the
manual/automatic. Nothing worked. Luckily I saved all qmgrs. I went to the
command prompt to dltmqm and crtmqm.
The newly created qmgr worked fine without cluster definitions. After I
restored the old definitions, it
Rebecca,
If your app is getting by MessageID or CorrelId and is doing a
destructive get, MQ starts at the top of the queue and works its way down
till it finds yours. As it goes top to bottom, it touches each message to
see if it matches your selection criteria. If it does, you get it. If
Rebecca,
For MQ v5.2 on OS/390 browse will remove expired messages.At that
release it is no longer necessary to do a destructive get. So, if you
are running 5.2 or newer, the same process can be used on OS/390 as on
other platforms.
-Tom
Tim, thanks for the input. I like your naming
convention but how would it address the issue of
deleting these PD queues that were not deleted by the
client apps due to sys failure etc? If these queues
were not deleted before the qmgr is recycled, then
they and their persistent msgs will be
Sounds like duplicate messages in the SYSTEM.CHANNEL.SYNCQ. IBM can tell you how to find them and which is the proper one to be deleted.
Glen Shubert
Mountazar Abou Chrouche [EMAIL PROTECTED]
Sent by: MQSeries List [EMAIL PROTECTED]
08/27/2002 07:55 AM
Please respond to MQSeries List
We are running MQSeries V5.2 CSD04, MA88 V5.2.1 and Pub/Sub 1.06 on
a SunOS 8 environment. Our Pub/Sub applications consist of durable
and non-durable clients. We are running up to 500+ subscribers on the
non-durable clients and 200+ of the durable.
I am using the NasTel product to monitor the
We are running MQSeries V5.2 CSD04, MA88 V5.2.1 and Pub/Sub 1.06 on
a SunOS 8 environment. Our Pub/Sub applications consist of durable
and non-durable clients. We are running up to 500+ subscribers on the
non-durable clients and 200+ of the durable.Oftentimes, a durable
client (3 threads)
I suppose one could use the same queue for requests and replies if
everything runs under the same qmgr. I wouldn't advise it though as it
severly restricts the flexibility of your design. At a minimum, use
different qnames in your application and resolve them to a single queue with
aliases. One
Hi! All,
A simple question, Does an IMS checkpoint ensures an
MQ message is commited. I have a BMP in which I am
taking IMS checkpoint after inserting a record into
DB2 database and putting the message into the queue.
The checkpoint frequency is around 1 second and we
have utility which after
Steve,
Since I may have planted the seed against using permanent dynamic queues,
let me clarify a bit. A permanent dynamic queue is unique in that it can be
easily created on the fly by an application. That can simplify one aspect of
administration--on-demand creation of permanent queues. If you
Shailesh,
the short answer is yes, if you specify MQxMO_SYNCPOINT on your GET/PUT.
From chapter 17 of the MQ Appl.Prog.Guide:
Syncpoints in IMS applications
In an IMS application, you establish a syncpoint by using IMS calls such as
GU(get unique) to the IOPCB and CHKP (checkpoint). To back out
We are trying to route messages in a message flow to one of about 60 output
queues. The deciding factor of which queue to send the message to is a
message type piece of data within the message payload. For example, the
payload of a message might contain a message identifier of I010 or O150
or
thank Andre, But is there any limitation on the MQSI side , any limitaation on the size of the messagethat can be transformed?
Andre van Zyl <[EMAIL PROTECTED]>wrote:
Hi,
Here is an extract from our R3Link Documentation which might be helpful:
"
Restrictions
The amount of R/3 IDoc data that
Hi All,
Is there a limiation on the size of the messages that MQSI can handle for performing any kind of transformation or is itsame aswhat MQ itself can handle.
Thanks in Advance
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
14 matches
Mail list logo
