Version 5.3.4 of my Administrator SupportPac is now available on the
SupportPac WebSite.
http://www-1.ibm.com/support/docview.wss?rs=203uid=swg24000142loc=en_UScs=utf-8lang=en
My thanks to many of you who have helped with suggestions and/or bug
reports.
Cheers,
P.
Paul G Clarke
WebSphere
A new version of the MO72 SupportPac has made it to the web.
http://www-1.ibm.com/support/docview.wss?rs=203uid=swg24007769loc=en_UScs=utf-8lang=en
This SupportPac allows RUNMQSC functionality over a client link to a remote
Queue Manager.
Support has been added for :-
Platforms :AIX,
Alan,
I'm not sure it answers your question but you seem to indicate that the
mesage is retried regardless of the failure. This isn't true, there are
only a small number of errors which are considered transitory (and
therefore retryable). From memory these are
MQRC_PUT_INHIBITED
A long shot but is it possible you haven't built your Unix exits threaded.
A common mistake is to forget to build it threaded or link with the right
threaded libraries. This can cause somewhat random failures and strange
behaviour like you're describing.
P.
Paul G Clarke
WebSphere Messaging
The key thing to check is that you're definitely spawning off the MQ
applications asynchronously. On Windows this means issuing the command
start App (or similar) rather than just App. If you run it syncronously
then the trigger monitor won't get control back, and therefore won't see
the next
If you set the cluster queue to PUT(INHIBIT) then that information is fed
back to the originating systems and the default WLM will no longer choose
you as a target (unless it has to if I recall).
Cheers,
P.
Paul G Clarke
WebSphere MQ Development
IBM Hursley
MQSeries List [EMAIL PROTECTED]
WebSphere MQ Development
IBM Hursley
MQSeries List [EMAIL PROTECTED] wrote on 15/10/2004 18:00:10:
Thanks for answers to my prior question, especially Paul Clarke from IBM.
I
will definitely test out your suggestion
Background
In a cluster I can have cluster queues with the same name
Have you checked that both the CLNTCONN and SVRCONN defintions have a
maximum message length as big as you need ?
Cheers,
P.
Paul G Clarke
WebSphere MQ Development
IBM Hursley
MQSeries List [EMAIL PROTECTED] wrote on 15/10/2004 13:42:20:
Hi list members,
I've a problem with MQ 5.3 CSD 4
Yes, of course.
In your QM.INI file have the lines
QueueManagerStartup:
Chinit=No
Cheers,
P.
Paul G Clarke
WebSphere MQ Development
IBM Hursley
MQSeries List [EMAIL PROTECTED] wrote on 15/10/2004 13:37:29:
Is there a way to start a 5.3 queue manager without starting the channel
not documented it is ?
Also, then what would be the effect of setting MAXINITIATORS=0 ?
Paul Clarke
[EMAIL PROTECTED]To:
[EMAIL PROTECTED]
IBM.COM cc:
Sent by: MQSeriesSubject
Tony,
It is not true that that the maximum message length across a channel is
4MB. The maximum message length is given by the lesser of the two maximum
message length value of the two channel defintiions at either side of the
channel.
Having said that what you suggest is usually a better
Tony,
Would I be right in thinking that you have configured your channels to use
a 5 second heartbeat (although there are other ways) ? If so, are you sure
you need it this frequent ?
Essentially the default timeout used to receive data on a socket is based
off the heartbeat interval. For
Oops, yes, I forgot about 'via' queue managers. Sorry about that. Via
Queue Managers is a bit more complicated.
I'll look into it but I can't promise when I'll get around to it. Too busy
with my day job.
Cheers,
P.
Paul G Clarke
WebSphere MQ Development
IBM Hursley
email : [EMAIL PROTECTED]
Yes, you can leave library blank on Windows. You could leave it blank most
of the time on OS/2 too.
As for backlog it's a question of how often you clients connect not just
how many of them you have. The backlog dictates how many connections are
allowed in to the listener while MQ is trying to
a different
value than we ask for and we're none the wiser.
If the QM is on Windows, and the ListenerBacklog is 100, and the incoming
requests are MQClients, what is the limit? 100, or 5?
-Original Message-
From: Paul Clarke [mailto:[EMAIL PROTECTED]
Sent: Friday, October 01, 2004 1
Due to popular demand I have put up a version of my MO72 SupportPac for
AIX, Solaris, Linux as well as Windows.
The zip file is available :-
ftp testcase.boulder.ibm.com
do an anonymous sign-in
cd ts/fromibm/mqseries
bin
get paul_mqsc.zip
It should work exactly the same although I haven't had a
vftp logged in.
ftp cd ts\fromibm\mqseries
550 ts\fromibm\mqseries: No such file or directory.
ftp
-Original Message-
From: Paul Clarke [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 15, 2004 8:27 AM
To: [EMAIL PROTECTED]
Subject: MO71 Version 5.3.4 Beta
Rather than have
the new date: (mm-dd-yy)
X:\time
The current time is: 11:02:02.59
Enter the new time:
-Original Message-
From: Paul Clarke [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 28, 2004 9:15 AM
To: [EMAIL PROTECTED]
Subject: Re: MO71 Version 5.3.4 Beta
Files on the testcase.boulder
Tony,
A transaction (or Unit of work) will be used by a channel if you send
persistent messages OR you have NPMSPEED set to NORMAL.
Bear in mind also that just because the applications you know about don't
send persistent messages doesn't necessarily mean no one else is. For
example the
Hubert,
With regard to second bit.
By default MO71 uses SET_ALL_CONTEXT. In other words it tries to maintain
the origin and identity context of the source message. Obviously you need
greater authority to use SET_ALL_CONTEXT. There are options in the
copy/move message screens to allow you to
I didn't think there was a client for iSeries, or for z/OS for that matter.
Am I out of date ?
Paul G Clarke
WebSphere MQ Development
IBM Hursley
email : [EMAIL PROTECTED]
Tel : External +44 (1962) 818201
MQSeries List [EMAIL PROTECTED] wrote on 21/09/2004 21:12:19:
As promised, here's a notification that my new SupportPac which allows you
to effectively run an MQSC program but as a client into a remote server is
live.
The SupportPac number is MO72 which is kinda odd cos MO71 is another one of
mine I wrote 7 years ago.
Here's the link,
: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Paul
Clarke
Sent: Tuesday, September 21, 2004 9:01 AM
To: [EMAIL PROTECTED]
Subject: MQSC client - MO72
As promised, here's a notification that my new SupportPac which allows
you
to effectively run an MQSC program but as a client into a remote
) 818201
MQSeries List [EMAIL PROTECTED] wrote on 21/09/2004 17:16:35:
Thanks for the offer! Solaris would be key for us.
-- T.Rob
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Paul
Clarke
Sent: Tuesday, September 21, 2004 11:05 AM
To: [EMAIL
Rather than have a formal beta program I thought I'd have a much more open
beta for the latest version of MO71.
Anyone who is interested in testing it for me is more than welcome.
The zip file is available via :-
ftp testcase.boulder.ibm.com
do an anonymous sign-in
cd ts\fromibm\mqseries
bin
get
I've never heard of this and it's difficult to imagine how this could
happen with a bug in the product. Are you certain the application isn't
doing something silly like getting the message under syncpoint and then
forgetting to issue MQCMIT.
From your description It sounds like this is
Subject
Re: MO71 Version 5.3.4 Beta
15/09/2004 13:48
Please respond to
MQSeries List
Paul, Yes. Please send the beta to me. Thanks ! Phil
Paul Clarke
Development
IBM Hursley
MQSeries List [EMAIL PROTECTED] wrote on 12/09/2004 23:45:26:
All,
Just hold your breath a little longer.
I have been working with Paul Clarke, author of MO71 to
Get a runmqsc 'client' that uses MO71 config files.
I already have a beta version and it should come out
T.Rob,
Ok, well first the good news.
AdoptMCA is equally applicable to runmqlsr and amqcrsta (and amqrmppa) for
that matter. Essentially, it doesn't make any difference where the channel
is running. We'll route it out and kill it.
Neutral news
AdoptMCA doesn't apply to SVRCONN channels. The
Tony,
Well it all depends on where the channels are running. If the channels are
running as threads of the listener which was the case prior to 5.3 then the
channels themselves will terminate (and probably not in a nice way if
you're talking KILL -9 or task manager here). 5.3 and after, killing
Far be it for me to defend the IBM web site, there are a number of things I
don't like about it either but I think calling it the worst on the net is
perhaps being a little harsh. I've been to some pretty bad sites.
Anyway, just to see how bad it was I thought I'd try it.
So I went to
I wouldn't be at all surprised if you find SSL supported by the
Administrator in future releases. However, if you want a GUI administrator
that supports SSL why not use my MO71 support pac. It does most of what
MQExplorer can do and a lot more besides.
Cheers,
P.
Paul G Clarke
WebSphere MQ
Tony,
I don't think it worth getting too worried about these FDCs. If anything it
looks like the product is being a little over zealous in reporting
something odd. From the function stack you can see that we're in AdoptMCA.
(Presumably you have Adopt MCA set on). Essentially a channel has
Dan,
Is it possible you're using the old webpage. The SupportPacs have been
re-arranged recently.
I've just tried it from
http://www-1.ibm.com/support/docview.wss?rs=203uid=swg24000142loc=en_UScs=utf-8lang=en
and it seems to work fine for me.
Cheers,
P.
Paul G Clarke
WebSphere MQ
You could daisy chain the event handlers. ie. have that part of the
processing of the event message is to put a copy of it to another queue.
Cheers,
P.
Paul G Clarke
WebSphere MQ Development
IBM Hursley
Agarwal, Krishan
[IT]
krishan.agarwal@
Hi,
Over the years I've received a number of requests for the source code for
my MO71 SupportPac and I've always had to say no. However, I am now
investigating the possibility (depending on demand etc) of making the
source code available either for free or for a small fee. If you're
interested
:[EMAIL PROTECTED] Behalf Of Paul
Clarke
Sent: 13 July 2004 11:07
To: [EMAIL PROTECTED]
Subject: MO71 SupportPac Source Code
Hi,
Over the years I've received a number of requests for the source code for
my MO71 SupportPac and I've always had to say no. However, I am now
investigating
Narasimha,
Are you certain that the original message is being put under syncpoint ?.
Note that for a NPMSPEED(FAST) channel only persistent messages will be put
under syncpoint. Does your exit decide whether to use syncpoint or not
based on the persistence of the original message ?
Cheers,
P.
Shanu,
The response I got from our JMS guys (actually it was a lady) was :-
Hi Paul,
Ill try to clarify this, well hope this helps anyway,
The listener port is an administered object that contains 2 jms
provider resource references : a Connection Factory and a Destination.
It has a pool
?
Thanks again
Dave
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Paul
Clarke
Sent: 29 June 2004 15:54
To: [EMAIL PROTECTED]
Subject: Re: Fw: Red Hat Linux 9
David,
I spoke to one of our Linux guys and this was his response
there are 2 possible values
the amount of log replay necessary for
restart recovery, it has almost nothing to do with media recovery.
I hope that helps,
Cheers,
P.
Paul G Clarke
WebSphere MQ Development
IBM Hursley
- Forwarded by Paul Clarke/UK/IBM on 29/06/2004 09:15 -
John Elgie [EMAIL PROTECTED]
Sent by: MQSeries
Richard,
I have spoken to development and they were not aware of this problem. They
suggest you raise a PMR so that it can be properly looked at rather than
just guess work.
Sorry I can't be of any more help,
P.
Paul G Clarke
WebSphere MQ Development
IBM Hursley
- Forwarded by Paul
-1844
* mailto:[EMAIL PROTECTED]
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Paul
Clarke
Sent: Tuesday, June 29, 2004 5:20 AM
To: [EMAIL PROTECTED]
Subject: Re: Fw: Why running rcdmqimg would free up linear log?
John,
I passed your question
.
So do I,
Cheers,
P.
Paul G Clarke
WebSphere MQ Development
IBM Hursley
- Forwarded by Paul Clarke/UK/IBM on 29/06/2004 12:24 -
David C. Partridge [EMAIL PROTECTED]
Sent by: MQSeries List [EMAIL PROTECTED]
29/06/2004 12:10
Please respond to
MQSeries List
To
[EMAIL PROTECTED
with channel status info as described
below?
Thanks -- T.Rob
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Paul
Clarke
Sent: Friday, June 25, 2004 7:38 AM
To: [EMAIL PROTECTED]
Subject: Re: FW: MQ Administration query
Yvette,
I'm afraid my answers
Yvette,
I'm afraid my answers to Bharath questions would have been somewhat
different.
Scenario 1 : When you repoint your sender chl connectivity to a different
machine. Currently, the remote Q Mgr is not running. Would a reset on my
sender chl make an impact in the receiver chl, if do a
Scenario 1: Resets on a channel only impact the local definition and are
not propagated to the remote side. So a reset on the sender only changes
the sender not the receiver.
A channel RESET *IS* propagated to the remote side. Issue a RESET on a
sender channel, send a persistent message then
Steve,
In general I would always suggest that applications explicitly issue MQBACK
or MQCMIT call since there are slight differences in behaviour on different
platforms. However, what you say is true. An MQDISC will implicitly commit
the transaction if possible. It is described in the Usage Notes
Yes for windows at least.
However you can only do one at a time. You do it by building a dll hook,
basically you put your own library between the application and MQ with
your
library loading the client or server dll as required.
HOWEVER you will be building something with custom code you are may
Does anyone have a channel send/receive exit that does compression that
they
might want to share? I'd rather not re-invent the wheel if possible.
Thanks,
Mark Bond
Mark,
You could take a look at SupportPac MO02
Hi All,
I using a JMS program to send a request and wait for the response on a
replyToQueue. When I created the replyToQueue using runmqsc and DEFINE
command, I end up getting the response with no problem. When I tried to
dynamically create a Temporary replyToQueue using the JMS
Hello Bill,
Thanks for the important gotcha. I just looked into command line syntax
and it does look promising. I am sure I will find a good use of it. One
thing that my Java sample does and Q doesn't though is using SSL connection
when asked. So, I think, the two will compliment each other.
I see.. This probably will not work in this case. My problem is: messages
are already on the transmission queue and only later we are notified that
the destination is not and will not be available and what the new
destination will be.
Pavel
Pavel,
MQ does not have an 'MQUPDATE' verb or whatever
Also, I have another (purely theoretical) question about the case. I
thought I understood how MQ worked: sender channel agent is a regular
application (or a thread) that is triggered by XMIT queue, takes messages
from there and communicates with the agent on the other end; now I am in
doubt: how
Hello, anyone using support pack mo71 for event monitoring?
I am trying to breakout event CHANNEL_STOPPED into the different flavors (
OK, ERROR, RETRY, ...) using the FILTER field.
for example using this filter REASONQUAL=7
however event always get's handled by the DEFAULT event rule.
I tried
Hello folks,
Many thanks to Paul, Kumar, Herbert, Bobbee and Peter. I've managed to
isolate the error. The developer while defining his process had not
followed the usual naming convention. The Process has been named 'Spain'.
While MQ Explorer lists the object details, runmqsc session odes
Thanks Paul for your inputs.
But I still believe I was logged into the correct machine and no case
sesitivity issues.
Is it possible that someone opens a session to modify a process in MQ
Explorer and at the same time someone tries to access that object through
the cmd prompt in Solaris - in
InterScan_Disclaimer.txt has been removed from this note on May 25
2004 by Paul Clarke
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
By far the best way to find out what an MQ process is doing is just to
switch on MQ trace. If you are really seeing 100% CPU then I suggest you
switch it on only for a short time. If the 100% is fairly constant then it
sounds like a bug, either in MQ or in an application. From the trace it
should
Howdy all,
I have a really odd problem with the MQMONNTP tool.
It has been working fine for years and all of a sudden it won't show any
queues!
It show processes and channels but not queues (there is no + symbol in
tree view so you cannot expand it out?
Does anyone have any idea where the
Hi,
Can we create queues remotely in MQSeries 5.3 on windows
client-server
environment ? In other words i want to be able to create a queue by
sending
a message/command to the Queue Manager from a different machine.
I can see there is an option of creating dynamic queues, but these are
Can someone settle an argument? The question is
whether to use one or more svrconn channels with a big
number of MQClients. Both the Queue manager and and
MQClients run on Win 2000 (MQ 5.3). Here is the
scenario: I have 1000 Mqclients all using the same
svrconn channel with the same
Gunilla,
If I understand you correctly what you're saying is that when your channel
has a network problem the sender channel tries to reconnect but the
receiver channel hasn't yet realised that there is a network problem since
it is still sitting in a TCP/IP recv().
The solution to this problem
Usha,
The reason we don't spend a lot of time describing the differences in the
client environment is because there aren't many. The more and more you
think about it you'll realise that from a programming model point of view
the client environment is almost identical to the local application case
Brian,
I'm afraid I don't agree with your comments Brian. If you're doing just
messaging (no databases involved) then the way you would code the
application for a client would be exactly the same as for a local
application. You do not have to write any special code just because you're
running as
Hi Jim
To my horror I can't find a command to stop/terminate/end the channel
initiator (may be it's due to my Monday syndrome or there is no such
facility) for non-z/OS platforms. I can kill the process, if that is what
is
called recycling. There one MQSC command called STOP CHINIT but that say
And then you are forced to run all your instances with the same security
settings and other settings like DISINT and what not. If thats what you
want, cool. But if you need different levels from different senders, you
will be stuck.
This is not strictly true; it depends on the parameter. A number
A new version of MO71 has been put to the WebSphere MQ Support Pac website
(note that the address has changed - don't ask me why).
http://www-1.ibm.com/support/docview.wss?rs=203uid=swg24000142loc=en_UScs=utf-8lang=en
Many thanks to all my beta testers for their help and suggestions.
My
Hi everyone,
I'm pretty sure the below will not work but would like
to confirm if anyone's tried this ?
3 Qmgrs : QMA, QMB and QMC
QMA communicates with QMC and
QMB communicates with QMC
Only one receiver channel exists on QMC.
Corresponding sender channels exist on QMA and QMB
Awaiting
The RESET CHL command cannot be done to a specific rcvr channel (OTOH,
one could interpret this as a positive thing, one command does them all!)
This is not strictly true. RESET CHL of a receiver is a race. First one to
start up gets RESET.
Actually you normally shouldn't issue RESET CHL on a
Paul,
Thanks for you explanation. Does it mean that, as a good practice, we
should not normally stop the listener from MQ services? I presume that's
the
same as endmqlsr (with -f?).
Anyway, at least we learn the -f this time and it works.
Thanks,
Ian
Ian,
It depends on whether you run your
Rick,
Sorry to hear IBM has 'missed the mark'. I'm slightly nervous that I too
will miss; believe me it's not intentional.
1/ IBM does not publish the format of the data it flows either between
Queue Managers or Queue Managers and a client. This is not because we're
trying to be awkward but
is the server queue field.
What else could I be missing?
many thanks for your help,
Ben
(Embedded image moved to file: pic08902.jpg)
(See attached file: mqmon_infra.vsd)
Paul Clarke
[EMAIL PROTECTED] To:
[EMAIL
) Not
authorized. I tried defining the userid of the NT box that has mqmon
running
on it and then modifying that user so that it has mqm as a group but I
still
get the same message. Any thoughts?
-Original Message-
From: Paul Clarke [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 17, 2004 3:50 AM
to
MQSeries List
I'm not sure I understand. If my NT userid is db2admin why would it work if
I change the MCAUSER on the SVRCONN to mqm? How can I secure it so that
only
users I designate can use it?
-Original Message-
From: Paul Clarke [mailto:[EMAIL PROTECTED]
Sent: Monday, March 22, 2004 4
double-click it, when all the qmgr info is shown
and the icon turns green, only for a few seconds.
thanks,
Ben
Paul Clarke
[EMAIL PROTECTED] To:
[EMAIL PROTECTED]
.IBM.COMcc:
Sent
Brian,
I think the first thing to do is find out exactly what the client is
waiting for for 4 minutes (who would have thought there was a valid
sentence with 'for' being used 3 times consecutively ?). I suggest you
switch on MQ trace and try the connect again. Look at the tracefile and
look at
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Paul
Clarke
Sent: Friday, March 19, 2004 11:53 AM
To: [EMAIL PROTECTED]
Subject: Re: MQ Client Connections
Brian,
I think the first thing to do is find out exactly what the client is
waiting for for 4 minutes
.
Ernest Roberts
- Forwarded by Ernest Roberts/171/DCAG/DCX on 03/19/2004 01:42 PM -
Paul Clarke
[EMAIL PROTECTED] To:
[EMAIL PROTECTED]
.IBM.COMcc:
Sent by: Subject
Sid,
For a channel to end 'indoubt' it must have had some form of failure either
at the local or remote end. You should examine the queue manager logs at
boths ends for messages about this channel.
Cheers,
P.
Paul G Clarke
WebSphere MQ Development
IBM Hursley
Mike,
MO71 supports two types of monitoring.
1/ Normal monitoring relies on a program at the remote Queue Manager to
receive the messages and send them back to the reply fields
This does therefore require a client (program) running on the remote
system
2/ Loopback monitoring allows yoiu to
of the firewall that we don't control) has allowed us
to avoid user impact in a number of cases.
-- T.Rob
-Original Message-
From: Paul Clarke [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 11, 2004 5:58 AM
To: [EMAIL PROTECTED]
Subject: Re: RCVR versus RQSTR channels
Rao,
Changing to use RQSTR
Capitalware Inc.
http://www.capitalware.biz
Quoting Paul Clarke [EMAIL PROTECTED]:
Ben,
I think this needs some investigation. I've just had a little play on my
XP
machine and it appears that
cmd /c c:\testbat.bat
doesn't work but
cmd /c cmd /c c:\testbat.bat
does !
I don't understand
Rao,
Changing to use RQSTR channels seem perfectly reasonable to me. If you do
this, you might want to consider changing your sender channels to servers.
A requester channel connecting to a sender will cause the sender end to
break the communications and re-connect back to the requester (ie.
Ben,
I think this needs some investigation. I've just had a little play on my XP
machine and it appears that
cmd /c c:\testbat.bat
doesn't work but
cmd /c cmd /c c:\testbat.bat
does !
I don't understand this at all; I would have thought the first version
should be fine. In the MO71 code I
the MO71 location for the MF qmgr
is still not active. I anticipate the viaQM simply took over the msg before
the MF entry gets a chance to get it. Do you see it that way?
best regards,
Ben
Paul Clarke
[EMAIL PROTECTED] To:
[EMAIL PROTECTED
Ben,
Nick has described it perfectly. The whole point of the 'via' location is
that messages are routed to/from your target Queue Manager *via* this other
location.
As far as where did your message go ? Well, check the normal places. If
you're certain the message got to the mainframe then it
Jan,
By q.exe are you referring to my supportpac MA01 ?. If you are, I'm afraid
that MA01 isn't really much use as a general Q unload/reload utility. For
small text messages where each message becomes a line of a file you can get
it to work but this is really for testing. I seem to remember
Thanks Jim. Do you know anyway to tell if the parameter is actually
taking effect? Should there be a message in the error logs or something?
We have changed it on several servers (sender and receiver sides), but I
can't yet tell if it is actually doing anything.
Thanks again,
B
Brian,
Not
If you're not interested in the MO71 support pac please delete.
It's about time I shipped another version of MO71 and again I'm looking for
people to beta test. Rather than be deluged with notes, as last time, let
me try a more pragmatic approach. I still have the list of people who were
kind
Depends what you mean by 'impact'. I assume you're talking about persistent
messages here. Generally speaking the addition of syncpoint to persistent
message operations will increase the performance since we only need to
force the log at commit time rather than for every message.
Download my MA01
DISTL represents whether distribution list are supported by the partner
queue manager. DISTL(YES) means the distribution list are supported by the
partner queue manager and specify DISTL(NO) if not.
Regards
Radha
It is true that DISTL specified whether the partner Queue Manager supports
David,
The pool processes are started by whoever needs it, ie the listeneer,
channel initiator etc. In general it best not to write an exit which
'assumes' certain characteristics. If I were writing an exit which wanted
to communicate (or share storage) with another exit I would use shared
memory
.
The channel tries to use each of the port values in
the range specified. When the
connection is successful, the port value is the port
that the channel then uses.
Best regards,
Ruzi
--- Paul Clarke [EMAIL PROTECTED] wrote:
MaxChannels and MaxActiveChannels are global
parameters. They specify
MaxChannels and MaxActiveChannels are global parameters. They specify the
maximum values regardless of how many listeners you have running or indeed
use inetd. There is no MQ parameter which limits the number that can
connect to a single listener. In 5.3 you can have a single listener to
handle
T.Rob,
This is good advice and I agree whole heartedly that the application
programmer must deal with 2009 reason codes correctly and perform message
operations in syncpoint if you need to ensure 100% reliability. However, I
do not agree that this is a client thing. Exactly the same decisions
??
Is there something I am missing. I / we do some progmatical tricks (?) when
it comes to no-coordinated processing. That is a given. BUT.?
bobbee
From: Paul Clarke [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: A program the uses MQSeries
)
If I click start, I get 'ABC.SVRCONN':Channel in use.
-Original Message-
From: Paul Clarke [mailto:[EMAIL PROTECTED]
Sent: Friday, September 12, 2003 11:48 AM
To: [EMAIL PROTECTED]
Subject: Re: Strange behavior with a Temp. Dynamic queue
MO71
If you select Channel Status from the QM
MO71
If you select Channel Status from the QM menu, you are provided with a
list
of all the instances. I right clicked on one of the 10 instances I had for
my SVRCONN channel, and saw it had a STOP option (MQExplorer does not).
So I selected STOP. Oops! The SVRCONN channel went into a Status of
I am at a loss to explain the following... (Solaris 5.8, WMQ 5.2 CSD06):
$ dspmq
QMNAME(CLUSTER2B.AR1.MANAGER) STATUS(Running)
.
.
$ export MQSERVER=SYSTEM.ADMIN.SVRCONN/tcp/127.0.0.1\(1414\)
$ /opt/mqm/samp/bin/amqsputc SYSTEM.DEFAULT.LOCAL.QUEUE
CLUSTER2B.AR1.MANAGER
Sample AMQSPUT0 start
1 - 100 of 201 matches
Mail list logo