Paul,
For a variety of reasons we need to try and
implement the conversions before the message arrives on our messaging broker
and yes we are using the IBM product you are thinking about :). We
need to know if it is possible to do conversion from all platforms to Sun
Solaris. If there are restri
I will be out of the office starting 03/26/2004 and will not return until
04/05/2004.
I will respond to your message when I return.
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-w
If you don't mind waiting... you can run the trigger monitor from a DOS
prompt on the Windows server instead of using MQServices to automate it.
It will keep running there and display all output to the window.
Peter Heggie
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] O
Hi There,
I'm running MQSeries 5.3 CSD03, and my trigger monitor program stops
occasionally with no error, is there a way to trace the operation of the
trigger monitor so I can try and get more detail information on why this is
happening? The date of my trigger monitor is 03/17/2003 09:59a 41,424
The October 2002 online version does not have it. Maybe they took it out
between June and October of 2002.
-Original Message-
From: Dawson, John [mailto:[EMAIL PROTECTED]
Sent: Friday, March 26, 2004 3:30 PM
To: [EMAIL PROTECTED]
Subject: Re: endmqlsr after endmqm
Peter,
It's the SC34
Peter,
It's the SC34-6068-00, System Administration Guide manual, dated June
2002.
John
-Original Message-
From: Peter Uranyi [mailto:[EMAIL PROTECTED]
Sent: Friday, March 26, 2004 2:30 PM
To: [EMAIL PROTECTED]
Subject:Re: endmqlsr after endmqm
John,
Do you have a
John,
Do you have a newer version of the System Admin Guide? Mine only lists the -m
and -w flags.
Peter
--- "Dawson, John" <[EMAIL PROTECTED]> wrote:
> Rebecca,
>
> After reading Paul's response, I looked in the WMQ Version 5.3 System
> Administration Guide and it is documented. So at least P
Title: Managing remote queue managers with RUNMQSC
Good suggestion (normally)... but I don't have access from
my windows client to the cluster members in question.
To access the queue manager(s) I have to SSH to a SSH
server, then telnet from there (since once I get to the SSH server, I am o
Title: Managing remote queue managers with RUNMQSC
Use
the MO71 support pac.
It
allows you to open up a runmqsc window into any QM from your desktop. Very
Cool.
-Original Message-From: Antony Boggis
[mailto:[EMAIL PROTECTED]Sent: Friday, March 26, 2004 3:00
PMTo: [EMAIL PROT
Title: Managing remote queue managers with RUNMQSC
I know it's possible to manage queue managers remotely using the "runmqsc" command processor. However, this (according to the docs) requires that transmission queues and queue manager aliases to the remote qmgrs be defined.
What I can't fin
Rebecca,
After reading Paul's response, I looked in the WMQ Version 5.3 System
Administration Guide and it is documented. So at least Paul will not
received the 'ruler on the hand' treatment.
John
-Original Message-
From: Bullock, Rebecca (CSC) [mailto:[EMAIL PROTECTED]
Sent: Fr
If you just want to keep users out, you can always stop the svrconn
channels that they use, and possibly other qmgr channels.
You would of course need to leave the SYSTEM.ADMIN.SVRCONN available if you
were to use the Windows explorer (and assuming that the developers do not
know about it, or hav
No, it's not a big deal, Pavel. And that's what I've done in the past, using
the ever popular kill -9. I'd hesitate to touch the setmqaut's since then
you have to put them back. Hadn't thought of the MCAUSER -- That's a nice
easy approach. But Paul's oh-so-secret flag is even easier.
-Origina
Sorry, one more question:
System Administration Book says that manual stopping QMs can leave some system
resources, like semaphores and shared memory, behind. But it says reboot would cure
the problem, anyway. Now, we are investigating if we need to have K* scripts for
Solaris, to stop QMs on s
Just STOP the channels.
-Original Message-
From: Pavel Tolkachev [mailto:[EMAIL PROTECTED]
Sent: Friday, March 26, 2004 1:52 PM
To: [EMAIL PROTECTED]
Subject: Re: endmqlsr after endmqm
Just gave it some thought..
One way to achieve that (meaning -- the maintenance mode, without bringin
Thanks Paul!
While you are still there, may be you take this question: should changing
authorizations or MCAUSER on channel disconnect currently connected users immediately;
or is this behavior different for FASTPATH and normally bound channels? I just
remember that the only way to externally a
Just gave it some thought..
One way to achieve that (meaning -- the maintenance mode, without bringing down
listener) must be to prohibit anyone to connect to QM, with setmqaut.. Another should
be to set MCAUSER in all channels to someone who cannot connect (like nobody). Also,
is it so bad jus
Sorry, I should have mentioned that this can only be done in 5.3, I do not
believe it was back-ported to 5.2
Cheers,
P.
Paul G Clarke
WebSphere MQ Development
IBM Hursley
- Forwarded by Paul Clarke/UK/IBM on 26/03/2004 18:18 -
|-+>
| |
The reason why we're not keen on people ending listeners while the Queue
Manager is active is because quite a number of customers run their channels
fastpath. Ending a program when there are fastpath applications which may
be issuing MQ calls when the process ends is potentially hazardous. Not too
Hi,
Ian. No, I don't have the answer, but I wanted to interject another reason one
might want to end the listener but not the queue manager. In some circumstances,
one might wish to perform some maintenance-type work on the queue manager but
not have users connecting, only allowing access throug
Title: Formatting production logs
Rao,
the
only commercial product that comes close to what you want in 1) is Cressida's
re-Quest.
(no I
have no connection to them, just answering a question :-)
)
There
is a way to format these logs yourself, but it takes a lot of guessing as the
format of the
>All,
>We need to do the conversion before transmission across the channel, we
have a channel exit on the other end that will need to manipulate the data.
>Regards,
>Kulbir.
Kulbir,
If this channel exit needs to actually look at the application data and
change it then are you sure it is not l
All,
We need to do the conversion before transmission
across the channel, we have a channel exit on the other end that will need
to manipulate the data.
Regards,
Kulbir.
"Glen Larson" <[EMAIL PROTECTED]>
Sent by: "MQSeries List" <[EMAIL PROTECTED]>
26-Mar-2004 15:59
Please respond to "MQ
Convert on channel is a leftover from the days one it was quite common for a
QM that does support conversion to be sending to a QM that did not. In that
case the receiving app could not convert, and the message had to arrive
already converted.
If both QMs support conversion, force the apps to issu
Kulbir,
We use MSG conversion in the applications only.(MQGET w/Convert option
specified)
1) If you use channel conversion and you cross multiple channels you open
yourself up for multiple conversions of a MSG, if it traverses multiple
qmgrs with multiple CCSIDs The sender does not know wher
Hi all,
Is there way to set RRS Private Context in a MQ application program or
exit? There is RRS Callable Context Service "Switch_Context" but it
requires key 0-7 or or supervisor state.
Onni Kukkonen
Vegasoft
Instructions for managing your mailing list subscription are provided in
the Listserv
All,
Hopefully this should be a pretty straight
forward query. We are going to have various applications connected
to our messaging broker. The Messaging Broker will be based on Sun
Solaris and have WMQ v5.3 CSD6 installed. The applications will be
hosted on various operating systems ranging i
z/OS
only though for Configuration Events.
I hope
the next version of MQ gives us this for Distributed.
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]Sent: Friday, March 26, 2004
9:36 AMTo: [EMAIL PROTECTED]Subject: Re: Formatting
production logs [Deutsche Boer
The configuration event may help,... ?!? SYSTEM.ADMIN.CONFIG.EVENT
Regards, Stefan
Ruzi R <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>
26.03.2004 13:46
Please respond to MQSeries List
To: [EMAIL PROTECTED]
cc: (bcc: Stefan Raabe/
Sorry, I am wrong about Events helping you Rao.
It will only fire off an event when an app tries to get from on Inhibited
queue, And then it only tells you what that app was.
It has no info for who inhibited the queue. :-(
-Original Message-
From: Potkay, Peter M (PLC, IT)
Sent: Friday
in this case, what SYSTEM.ADMIN.QMGR.EVENT will record
is the incident of an MQGET call from a queue that is
GET-Inhibited. It will not record who inhibited it.
So, I don't think it is going to be much of a help to
Rao.
Regards,
Ruzi
--- "Potkay, Peter M (PLC, IT)"
<[EMAIL PROTECTED]> wrote:
> T
Frankly I don't care about the numbers, as long as they differ from version
to version :-)
I have worked with Jxrgen, to test BlockIP2 on AIX and Solaris and that way
we did find some
other small but annoying things that weren't the same.
What I liked most about it was the shared effort to make so
32 matches
Mail list logo
