Gary,
About a queue manager, or any process that runs on any computer, I
have always assumed, maybe incorrectly, that a CPU on a box can only do one
thing at a time. It may be incredibly fast, giving the illusion of many
things happening at once, but when you get right down to it,
Peter,
As far as I know, if a process is performing I/O, it should not be
locking up the CPU. The process will swap out (call it what you
will on your favorite OS) while performing I/O and other processes
that want to use the CPU are scheduled. I believe this is computing
101... but I took
This would be true for the smallest unit of execution (normally a thread,
not a process). Thus if a thread of execution was committing data to disk,
that thread would not continue until the commit was completed. However,
another thread within the same process would get CPU if it was able to
Hi,
I am trying to create a message set with an XML DTD in MQSI v2.1. When I import the DTD, the system (my PC) takes a long time to responce where I checked the Windows task manager having a 100% CPU usage. After a long time, MQSI returns a message said my newly created message
Neil, I am specifically thinking of the scenario where the message is
already on the destination QM. Regardless of whether the messages were in
syncpoint or not as they traveled across the channel, I am only concerned
about how messages are handled in a HUB queue manager once they are
committed to
Which MQ feature should I look for if my applications would like to share
messages. Would like to deliver
a message to a specific queue and allow multiple API's to consume that
message and not have a message gone
until each API has actually consumed a specific message.
Instructions for managing
We had
a similar requirement in our AS/400 applications to send any
changed/deleted/added records from certain files as an MQ message. We use
the DB2/400 database triggers as the mechanism to initiate the process.
Because of the issues involved with database triggers, wewrote a Generic
So here is my real question, which is what makes me wonder exactly how a QM
handles messages.
Our HUB server is using Veritas. The disk that is being written to (whenever
that may be) is actually on the Storage Area Network (SAN).
The HUB is also clustered with 2 queue managers dedicated to
Thanks David and Marty! The exit is a LOT more useful now. :-)
-- T.Rob
-Original Message-
From: David C. Partridge [mailto:[EMAIL PROTECTED]
Sent: Friday, May 30, 2003 5:05 AM
To: [EMAIL PROTECTED]
Subject: Re: Security exit MQCD fields
The first time you will see all the relevant
Hi All
I have been stuck on a syntax error for some time so I figured I would reach out for a
bit of help on this one:)
Environment: WMQI 2.1 CSD3WMQ 5.3 CSD 1
I am trying to code a CASE statement in a compute node but am getting a syntax error.
I have looked at it in the ESQL
It has been a while since I compiled on Linux, so you may want to check the
help. I assume you are using GNU C++ compiler so try doing gcc --help I
believe. If my guess it right it is '-G' or similar.
Hope this helps.
Roger, since you have a Linux system could you help this fellow ;-)
Chris
Hello there.
When an application puts a persistent msg on a queue and if the corresponding
qmgr fails before the messge is committed/backed out . can the message
still be recovered after the qmgr comes up ? I mean, is the message logged ?
Does a qmgr perform a commit/backout just before it
Can you send high priority messages down their own channels and the
persistent ones down their own.
These would run as separate processes and (possibly) not block each other.
Regards
John.
-Original Message-
From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED]
Sent: 30 May 2003
Try linking with the gcc -G option (gcc -G module1.o module2.o etc.) I think
that creates shared libraries on Linux.
Try gcc --help or search the web fore details on gcc.
Regards
John.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 30 May 2003 11:30
To:
The HUB has dozens of channels to and from each spoke. My question is if one
pair of spokes is exchanging Nonpersistent messages and another pair starts
sending persistent, will they hurt each other.
I don't think dedicating channels to be persistent or not between a spoke QM
and the HUB will
Peter,
Got a question. On my arcitectural diagrams I have specifications for 8-WAY
servers. I agree with you that a CPU can only do one thing at a time. While
that CPU is waiting what are the other 7 doing? If the are also waiting on
#1 what is the use of haveing a multi CPU machine except for IBM
That because Gary is very old! (tee hee hee)
From: Gary Ward [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: How a MQSeries Hub does its thing with persistent / non-persi
stent messages
Date: Fri, 30 May 2003 09:11:49 -0400
Peter,
Here are some examples.
set MailType = CASE
InputBody.WfMessage.ActivityImplInvoke.ProgramID.ProgramName
when 'WorkItemNotification' then 'is Ready for Your Approval'
when 'RejectionNotice' then 'Has Been Disapproved'
when 'ReWorkNotice ' then 'Requires Rework'
Wesley,
You are strattleing across application and MQ functionality.
MQ Functionality
MQGET with the browse option will let you get a message and not distroy it.
now.
Application Functionality
How do you tell when the last application on the list viewed the message
bobbee
From: Wesley
If you application didn't receive the RC=0 I believe it would be considered
an inflight transaction and would be backed out upon QMGR restart.
From: Diwakar S Yammanuru [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: MQ behaviour - persistent messages
Here is a makefile for Linux. This makefile compiles test1.c into a shared
library of test1.so
+ cut here ++
# Makefile
CC = cc
CFLAGS = -G -I. -DUNIX
CFLAGS_COMPILE_ONLY = -c -DUNIX
LIBS = -lmqm
#
.c.o:
${CC} ${CFLAGS_COMPILE_ONLY} ${CFLAGS} $
OBJ = test1.o
A possible candidate for publish/subscribe?
-Original Message-
From: Wesley Shaw [SMTP:[EMAIL PROTECTED]
Sent: Friday, May 30, 2003 7:02 AM
To: [EMAIL PROTECTED]
Subject: Sharing a MQ Message
Which MQ feature should I look for if my applications would like to share
The message might be logged, but it cannot be recovered. A qmgr crash effects a
backout, but I would say it happens more after the fact, rather than just before.
-Original Message-
From: Diwakar S Yammanuru [SMTP:[EMAIL PROTECTED]
Sent: Friday, May 30, 2003 7:59 AM
To: [EMAIL
Here is a situation:
An application is running, It reads a Q or 2 writes a Q or 2 all in a UOW
and the QMGR goes down now part of that UOW is a PUT to a queue prior to the
MQCOMIT to ICE the processing deal. Are the messages comitted when the QMGR
comes back up? Mr Diwakar never said he was in
Peter,
If you use NPMSPEED=normal, non-persistent and persistent messages in the same batch
all become available at the same time. You can infer from that, that performance of
non-persistent messages is dependent on I/O for persistent messages, though I believe
it is more likely to be the
Jeff,
Can't answer your question directly, but can at least point you to the Info
Center in case you haven't already found it:
http://www-3.ibm.com/software/webservers/appserv/infocenter.html
-- T.Rob
-Original Message-
From: Jeff A Tressler [mailto:[EMAIL PROTECTED]
Sent: Friday, May
For Ha-Has, I made a dedicated channel for this app from SPOKE1 to HUBQM.
The only messages going over this channel are non persistent. Thousands of
messages are zooming across this channel every hour. The XMIT queue never
got deeper than 2. The speed is normal. A bin change hits our SAN, which
Someone please correct me if I am wrong, but what I have seen is that the log files
are still written to with non-persistent messages because of the queue manager to
queue manager commit/syncpoint activity for messages traveling over the channel. I
know this because there is a bug in Windows
Here's my mindset. Assuming non-persistent messages do not require disk I/O, then they
should continue to flow even when your disk I/O sub-system is temporarily unavailable.
Since you experiencing something else, there must be conditions under which NP
messages are dependent on the disk. I was
In order to get the behaviour you want, the task processing NP messages must not use
or be dependent on SAN I/O whatsoever. Now you don't have absolute control of the I/O
that MQ uses. For example, NP messages can spill to disk if they are large or many,
and sometimes MQ will use disk
With NPMSPEED=fast, you should not lose persistent messages and you should not lose
non-persistent messages except when there is somekind of channel abend. Did you
experience otherwise?
Do you lose more messages with NPMSPEED=fast or from SAN-related timeouts?
-Original Message-
Howdy John et al,
Thanks to everyone who sent me an email, after playing all night, I came
up with the following two make files. The first builds my shared library,
the second links the MQ C++ shared libraries (and mine) into a test program.
I sugest you file this one away because it is bound to
I write multi threaded clients all the time. just make sure you link the
correct libraries in and all works fine.
Sid
-Original Message-
From: Stefan Sievert [mailto:[EMAIL PROTECTED]
Sent: Saturday, 31 May 2003 5:32 AM
To: [EMAIL PROTECTED]
Subject: MQClient thread-safe?
Happy
33 matches
Mail list logo
