All who responded,
I thank you very much for your input. I have been able to work around my
situation now.
Thanks,
David Corbett
Certified Wbsphere MQ Solutions expert, developer & administrator
Quoting Dave Corbett <[EMAIL PROTECTED]>:
> Listers,
>
> I know someone has
Listers,
I know someone has dealt with this out there, and I would just like an
explanation of how I can accomplish this...
When I have installed MQ 5.3 on w2k, I have always said that I don't care
about any domain servers. However, when someone logs into the server where
MQ is installed, they m
ou run into on 5.3 if you don't have
the proper domain accounts set up. Look at Chapter 11 of the 5.3 Quick
Beginnings manual. Also have you looked at the Windows security event log
to
see if there are any more clues there?
-Original Message-
From: MQSeries List [mailto:[EMAIL PRO
These messages just mean that a client is issuing MQCONN / MQDISC calls on
a very frequent basis. When you have client connections direct to your
mainframe, you must be very particular in how those client applications are
written. They should keep persistent connections and handle MQ connection
b
I have an MQ v5.2.1 qmgr running on a w2k box. When I try to connect to
the qmgr from an app server (different physical box) I receive a 2063
error. This will happen with either a 5.2 client or a 5.3 client. A
strange thing about this box is that when I bring up MQ explorer, I can see
the QMGR,
I had this same question regarding triggering. Apparently once a process
has been triggered, the input use count is incremented and as long as it
remains greater than zero, another process will not be triggered.
Thanks,
David Corbett
IBM MQSeries Certified Specialist, Developer & Solutions Expert
Absolutely, you can mix shared and non-shared queues on a single qmgr in an
OS/390 or z/OS sysplex environment. I think 63k messages are fairly large
and you should consider breaking them into smaller pieces if possible. You
can easily flood the network if you are going to be sending a large numb
Has anyone out there used COM+ Object pooling to handle connections to a
QMGR? We are trying to use this to handle connection pooling. The gist of
our requirement is to open up MQ connections as needed, mark them as busy
while they are being used, and then clear the busy flag when the connection
You are probably running into a situation where you have many stale/broken
connections, but you haven't purged them because you don't know they are
stale or broken. If you are talking about TCP client connections, you need
to be aware of your TCPKEEPALIVE settings. By setting this value to a
mean
channels. You
may want to check those and possibly set them to zero.
Glen Shubert
Dave Corbett
<[EMAIL PROTECTED]> To:
Sent by: MQSeries List [EMAIL PROTECTED]
<[EMAIL PROTECTED]> cc:
in one end of the
channel not controlled by the qmgr. In my mind, the tougher question is
whether to forgo the NT concentrators and put qmgrs directily on the
webshere servers, which in effect are already acting as concentrators. I'm
skeptical about the advantage gained by having 4 inound
Since nobody has replied to this, I am assuming that we are the only ones
making extensive use of client connections direct to an OS/390 platform.
So, in the hopes that someone else besides us has some experience with this
architectural model, I am resending it to entice anyone with thoughts on
thi
To anyone with experience,
We originally had three NT MQ servers that would handle MQ connections from
11 websphere app servers and then had SNA channels defined to our OS/390
environment. The 11 app servers are spread across three mainframe LPARS in
4x4x3 configuration. The NT boxes served for
the first
instance will retrieve the message since it is already waiting on it."
One of the conditions necessary for a trigger message to be generated
is that no process has the main queue open for input. Since your app
is running, IPPROCS will equal 1, and a second proc
I have a couple of applications that desire to use triggering in order to
start processes. Both of these applications will be putting messages on an
OS/390 box via a direct client connection to the OS/390. I am planning on
setting the trigger mechanism to: TRIGGER FIRST.
Once the application get
t system? Is the different userid that you used, defined on the box
the
calls were made to?
Cheers,
Darry
-Original Message-
From: Dave Corbett [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 08, 2003 1:13 PM
To: [EMAIL PROTECTED]
Subject: MQ Client 5.2 - only works whn=en executed
en executed by NT id who install
ed it |
>---|
David,
Security was tightened on V52. Have you reviewed the MQ error logs on the
target system? Is the different userid that you used, defined on the box
the
calls were made to?
Cheers,
Darry
-----Original Mess
I have installed MQ client 5.2 on an NT 4.0 box with a userid that has
administrative rights to it. That user can start an application that makes
use of the mqclient calls and everything works fine. However, if I log
onto the NT box with a different userid (even if this id has admin rights),
the
I remember this was discussed some time ago on the list.
Cheers,
Darry Gorse
IBM Certified Specialist - WebSphere MQ
Systems Infrastructure & Operations
-Original Message-
From: Dave Corbett [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 27, 2002 8:47 AM
To: [EMAIL PROTECTE
r this was discussed some time ago on the list.
Cheers,
Darry Gorse
IBM Certified Specialist - WebSphere MQ
Systems Infrastructure & Operations
-Original Message-
From: Dave Corbett [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 27, 2002 8:47 AM
To: [EMAIL PROTECTED]
Subje
I have an application that has two W2k boxes talking to each other. One is
a QM and the other runs a websphere application that uses JMS to do MQ
calls. The websphere app makes client connections across a wan to the QM.
We are having network issues and the client channel connections end up
"orph
21 matches
Mail list logo
