Kulbir,
are the messages persistent? mayby a log analysis could be an approach (just an idea, but i think
this well be hard to implement because log details are not known to the normal mq users).
i use a channel exit in a similiar situation, i wanted to be able to see what messages
(target
Hi,
We have an issue with one of our NT Boxes. We are running WMQ 5.3 in this
machine. Our Client is trying to connect to this machine through his sender
channel. Although the listener and queue mgrs at my end are up running,
the msg doesn't reach me. The MQ error log at sender end suggests
Stefan,
Thanks for the response. Unfortunately
because of the validated environment we work in (Pharmaceutical regulations)
we need to use persistent messages no matter what approach we take. We
will match the incoming messages with the outgoing messages by using the
ApplIdentityData field in
If everything is set up correctly, I would have someone put a scope on the line
and see what happens to the message. A bad firewall rule, a misconfigured router/switch, are a couple of
of reasons that can cause this error. Are you using the default port or did you assign a particular port? Is
Kulbir,
persistent messages are in the log, so log analysis may still be an approach, but (again) hard to implement.
using the applidentity data to match incoming and outgoing message will work, but you must be sure it is not used anywhere else in the application and
you must be sure the value
Hi,
Obviously, I don't know your system, but on ours whenever we get odd IP
errors, the word 'Firewall' springs to mind. Another point, can other
clients connect? IMHO, the first test for a client connection should be
(unless the server is z/OS) over localhost, using env vars and the simplest
Ray,
We use the default 1414 port.
We were getting the following error message when we tried accessing the
listen queue through MMF.(Nastel MQControl Explorer)
EXRC_MQNODE_UNREACHABLE: Local Manager running on the MQSeries Node is
either not running or not responding. It may also
Stefan,
We will be developing on Windows and using
this in production on Sun Solaris.
Also, would you share the same channel exit
across channels or have separate instances on each channel? We may
have up to 600 channels in total connected to 3 queue managers on the hub.
We're worried about
Additional comments:
Acquire the storage for you structure at MQXR_INIT time, and store the
pointer in MQCXP.ExitUserArea.
Make sure that you release the storage and clear the pointer at MQXR_TERM
time.
Do whatever processing you need at MQXR_MSG time (you'll probably want to
know whether the
Rao,
From the main Support Pac page
(http://www-306.ibm.com/software/integration/support/supportpacs/) pick the
link in the right-hand margin that says Submit Category 4 SupportPacs to
submit a new Support Pac. Alternatively, contact the author of a Support
Pac directly if you want to contribute
Run, don't walk to:
http://www-306.ibm.com/software/integration/support/supportpacs/individual/m
a86.html
and download the information about MQSeries and firewalls.
HTH
Dave
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at
Each instance of a channel exit can hang any structures (or control blocks)
that it needs to maintain state across invocations in MQCXP.ExitUserArea
(store a pointer in here). You can store in this structure any hconn (n.b.
you'll get MQRC_ALREADY_CONNECTED when you do the MQCONN, so just
Kulbir,
my exit is on os/390, its written in assembler and the number of channels it is used in is about 20, so i am afraid
i have to stop giving hints at this point because your environment differs too much (and i am not a unix guru).
Using an exit in 600 channels (or 200) could maybe be a
If the timings are captured on different boxes, and the machine clocks are
not synchronized, then you could have some interesting results.
David C.
Partridge To: [EMAIL PROTECTED]
[EMAIL PROTECTED]
Indeed so! :-)
Dave
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
Sounds like they're not hitting the right box, hence the message stating : EXRC_MQNODE_UNREACHABLE: Local Manager running on the MQSeries Node is either not running or not responding.
The firewall rules would appear to be the culprit, pointing them to a different box where there is no active
Is
this something that you will need always from this point forward, or is this a
one time deal just to get an idea?
If all
you want to know is how long name resolution takes place on the MQ Hub this one
time, I would do the following:
Do
this off hours.
Create
a new channel into the Hub, and
Has anyone ever implemented a process that would encrypt data as it is
written to a queue and decrypted as it is read from a queue.
Dave De Seve
Middleware Systems Support - 52/996.69
MQSeries Certified Specialist WebSphere Administrator
Marriott International - Information Resources
Direct
Dave,
Rather than trying to write your own encryption technique, I would
recommend that you look at a vendor product like Candle's PathWAI Secure.
PathWAI Secure uses standard RSA security to encrypt and authenticate
messages either in a queue or over a channel. By using a vendor supported
Rob - thanks very much for the help. I have submitted the request.
Cheers
Rao
-Original Message-
From: Wyatt, T. Rob [mailto:[EMAIL PROTECTED]
Sent: 24 March 2004 1:38 AM
To: [EMAIL PROTECTED]
Subject: Re: Managing linear logs with MQ5.3 on Windows
Rao,
From the main Support Pac page
There are even products out there that do that :-)
One of them is IBM WebSphere MQ ESO (Extended Security Option), which is a
'package' of
IBM WebSphere MQ and Tivoli Access Manager for Business Integration (TAMBI)
Michael
-Oorspronkelijk bericht-
Van: MQSeries List [mailto:[EMAIL
I have a queue manager that has been removed from a cluster using the correct
procedure (suspend, set channel attrs, stop channels...). I still have queues on other
cluster members (even after having refreshed the cluster) from this (now,
non-existant) queue manager showing up:
dis clusqmgr(*)
Use the RESET command to force a QM out of a cluster.
RESET CLUSTER(yourclustername) QMID(thebadQMID) ACTION(FORCEREMOVE)
QUEUES(YES)
Issue it once from one of your Full Repositories.
-Original Message-
From: Antony Boggis [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 23, 2004 6:26 PM
Title: RE: Re: Queues from non-cluster members...
Even though neither of the repositories show the old queue manager when I do a dis clusqmgr(*) ?
tonyB.
-Original Message-
From: MQSeries List on behalf of Potkay, Peter M (PLC, IT)
Sent: Tue 3/23/2004 3:45 PM
To: [EMAIL
The single biggest factor related to performance is whether or not you use
persistent messages. Make sure you only use persistent messages where you
absolutely must. For example almost all inquiry style transactions can use
non-persistent messages. And a surprising number of update messages can
Dave,
We use cleartext queues and encrypted data queue, when data is written to a
queue a trigger fires the encryption process for that queue and puts all the
data into the other queue in encrypted format... Works very well.
Sid Young
QML Pathology
-Original Message-
From: De Seve,
Bon,
Do you have a performance problem ? What kind of hardware are you using, do
you have network teaming?, is the disk / I/O sub-system a problem? Is the
applications that collect the data designed to collect all messages in one
hit or several hits at a time ?
More information please!
Sid
27 matches
Mail list logo
