ms0i (mqauth52) *should* work on WMQ 5.3 but you're probably better off using
amqoamd -s.
The likely reason you got an empty list is because all your authority entries
are for 'mqm', which ms0i won't output by default. Use the -a(ll) switch to
have it include 'mqm' entries in it's output.
Reg
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 Frid
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 t
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-
> Fr
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 scratchpa
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
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 MQ
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 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 3
I don't think that support pack has been upgraded to 5.3 because the amqoamd
command now writes setmqaut commands as an option. I'm not sure the MS0I
script would have correctly handled the generic authorizations anyway.
-- T.Rob
-Original Message-
From: Terrence J Serena [mailto:[EMAIL
Hi
Thanks Raul, perfect examples of exactly the type of thing I am trying to accomplish.
Hours of struggling put to rest 2 minutes after getting your samples!
Dan
-Original Message-
From: Raul Acevedo [mailto:[EMAIL PROTECTED]
Sent: Friday, May 30, 2003 9:21 AM
To: [EMAIL PROT
I would say that all 8 WILL work at the same time, but each can only do one
thing at a time. If the QM is in fact multi-threaded/processed under the
covers, then at least you could have 8 "things" going on at the same time.
BUT, if all 8 CPUs need to share a resource, like the disk, then are we bac
Hi Dennis.
I agree that non-persistent and persistent messages in a batch will be
available at the same time. But my batches are of 1 or 2 messages. Since my
BATCHINT is zero, and the channel can keep the XMIT queue at zero, I doubt I
am incurring any performance hit. 1 or 2 messages are sent acro
Hi Jeff,
>>>How do you verify the installation and configuration of the
>>>JMS in WebSphere Application Server? I hope it is as simple
>>>as using an equivalent to amqsput. It would be nice to run
>>>something like a jmsput and jmsget program to verify the
>>>connectivity exists.
Have you run the
Hi
Normal programming tasks use the MQI (MQSeries API) to access
MQSeries. Our company is beginning to experiment with WebSphere
Application Server and its use of the JMS to access MQSeries.
Our Infrastructure Group has set up and configured the system but
this group has little or no actual knowl
Happy Friday everybody,
can anybody (from IBM?) comment on the following statement:
"The MQ Client interface is not thread-safe. You cannot safely use MQ Client
connections to the same queue manager from multiple threads within the same
process (for example, a Workflow Web Client Servlet) ..."
I
I have just upgraded to WebSphere MQ 5.3 with CSD 03 on AIX. I am having a
problem with support pac ms0i, when attempting to back up WMQ object
authorizations. The command I enter, and the message I get, is:
mqauth52 -m QMSTEST -f QMSTEST.oam1 -s
processed 31 objects.
wrote authorities script to
Does anyone have the classpath fix for the IC01 supportpack. What JAR is
missing from the PATH in the BAT files?
bobbee
_
Add photos to your messages
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 (synch
Not bad Dennis!!
From: "Miller, Dennis" <[EMAIL PROTECTED]>
Reply-To: MQSeries List <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Sharing a MQ Message
Date: Fri, 30 May 2003 09:21:12 -0700
A possible candidate for publish/subscribe?
> -Original Me
Sorry I didn't answer all the question before as Dennis did. You wouls
expect that your input to the transaction is recoverable also. So when the
process starts again you can restart that transaction as if nothing happened
(sometimes almost). This is one of the benifits of running under a LUW. If
y
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 the
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: [EMAI
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 sha
I think that's still not quite right.
On open, you supply a prefix for the intended queue name followed by an asterisk in
the dynamicqname, like "XYZ*". The qmgr creates a dynamic queue with a unique name
starting with your prefix and ending with some timestamp/jibberish. The qmgr puts that
nam
I think there's a subtle "middlepoint" here.
You may not have received an RC=0 on the commit, but the messages may have
been committed anyway. There would be a small window of opportunity where MQ
has completed the commit, but before it could return RC=0 to the app, it all
goes pear shaped.
I thi
I think I joined the thread part way through. Now I'm playing catchup. I've
read you original message which I'll add my 2p (English money) in
revers(ish) order:
Q3. I then defined a local queue on QMHUB and used one of the spoke QMs to
send non-persistent message to it. 1 GIG worth actually. Now t
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
al
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
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 S
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'
whe
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,
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
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 make
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: [EMAIL
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 14:2
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 cra
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
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 refe
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 fi
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 MQSI.
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, we wrote a Generic
D
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 y
43 matches
Mail list logo
