I will be out of the office starting 03/17/2003 and will not return until
03/22/2003.
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
I will be out of the office starting March 17, 2003 and will not return
until March 24, 2003.
I will out of the office until 03/24/03 and will return your email and
voice messages then. If you have a issue that you need immediate support
please as follows:
WebSphere F&T - Scott Stokes 972-280-562
Thanks,
Someone else suggested suppressing messages, I did a quick bit of research
on our output and if we suppress CSQX500I, CSQX501I, and CSQX545I it should
reduce the total output by about 90-95% which makes things manageable. This
is discussed in the z/OS System Setup Guide as follows.
Task 2
Probably not, can't be certain with java as I just dont know. However given
the underlying call is likely to be MQCONN or MQCONNX then you get one
connection per queue manager per thread, any additional connections just
get given the same handle. So yes maybe you could do it by coordinating
mutli-t
Title: MQ connection(s) from distributed side to Mainframe show Pending after server is dropped without dropping Bridge first
We
have tried ADOPTMCA to solve our problem and it didn't do any
good.
We
haven't tried ADOPTNEWMCA though.
Keith
-Original Message-From: Crupi, Margherita
[m
Title: MQ connection(s) from distributed side to Mainframe show Pending after server is dropped without dropping Bridge first
Could
the MQ channel ADOPTMCA* & ADOPTNEWMCA parms help you in respect
to automatically retry channel operations
-Original Message-From: Bullock, Rebecca (C
It's always been the same ID for me but I've been on NT and not 2000. You
might try setting the ID from the services dialog. I sure hope the other
listers chime in here because that was the only suggestion I had.
-- T.Rob
-Original Message-
From: Deiter Scott [mailto:[EMAIL PROTECTED]
S
Hello,
try the command 'dcomcnfg'.
Select the 'IBM MQSeries Services' entry, and request 'Properties'.
Then go to the 'identity' tab.
Regards... Neil Casey.
Deiter Scott
<[EMAIL PROTECTED]To: [EMAIL PROTECTED]
R
Oddly enough after setting the user with the amqmsrvn command the userid
does not show up in the security tab in the services properties window.
Is this window bending the truth or is this a different userid than the
amqmsrvn command sets?
>FromScott Deiter
Hanover Direct, Inc.
Folks,
I running Win2K server on a dell box.
MQSeries 5.2.1 with CSD 06
With the server up and running normal
Queue manager running and set to Automatic startup
Command Server running and set to Automatic startup
Channel Initiator running and set to Automatic startup
Listener running and set to A
If anyone is interested.
I deleted the broker and the config mgr. I then removed MQSeries 5.3. I then
installed MQSeries 5.2.1 and recreated the broker and the configuration mgr.
The control center now works with NO TCP/IP errors and I can import anything
my little heart desires!!
I am next going
Edward, all I did for the immediate problem was increase the maxdepth for
the DLQ and restart the channel. Then had the programmer fix the original
problem (app had a typo in the REplyToQ name). But likely you've done that
kind of thing already; I'd look at the suggestions from others...
-Orig
This behavior is no doubt caused by the MRRTY and MRTMR parameters on
the receiver channel's definition. The channel will pause MRTMR
milliseconds, and then retry. This repeats MRRTY times, or until the
put is successful. I'm not sure what the defaults are for the
parameters, but they are sufficien
I think your answer fits the scenario. The instances in which the problem occurred
were during a high message arrival rate. I looked at the MRRTY and MRTMR values of the
receiver channel. They are with their default values of 10(retries) and 1000
(milliseconds). So, I guess I would rather reduce
Edward,
Review your channel options for Retry count and Retry Interval.
Retry count - The number of times a send will be retried if the return code
gives a temporary error. Retry is attempted under the following conditions:
Queue full, Queue disabled for put, Queue in use. ( You indicated that on
Title: MQ5.2 Bug
We are getting some inconsitent results in our MQ application running on Websphere4.0. Threads were hanging ...
"There seems to be a bug in MQ5.2 related to double posting a semaphore operation. There is an MQ Agent that polls for messages, and when a message was incoming a
Have you checked the settings for your MRRTY and/or MRTMR channel
parameters? If the MCA can't put a message to its destination queue because
it is full, it will keep retrying for the number of times specified by MRRTY
at intervals of MRTMR. After this is exhausted, it will then put it to the
DLQ
Scott,
I've not actually done this but doesn't the service show up in the Control
Panel Services applet? If so, the UserID should be listed in the dialog.
Of course, the password will be starred out. I don't have a lab box to try
this on but other services I've configured this way show up proper
Edward
My 2 cents:
Do you have DLQ DEFINED on the Receiving side and is PUT ENABLED and has sufficient
MAXDEPTH
as in that case your channels will shut down and Xmit Queue will be filled up
you mentioned
"Hence, the queue filled up. "
which queue are you talking about, one on the recv side or
Yes, the messages get to the DLQ. But my question is why is it building up in the
transmit queue... As far as I know the DLQ did not get full.. What if any did you do
to alleviate the situation?
Edward.
-Original Message-
From: Bullock, Rebecca (CSC) [mailto:[EMAIL PROTECTED]
Sent: Mond
Also make sure that the receiving QM does in fact know that it has a DLQ.
Just because a DLQ is defined in not enough. The QM DLQ attribute needs to
be set.
Peter Potkay
IBM MQSeries Certified
[EMAIL PROTECTED]
X 77906
-Original Message-
From: Bullock, Rebecca (CSC) [mailto:[EMAIL PROT
We recently have fixed our mq authentication errors following these
instructions.
==
Configuring MQSeries Services to run under a domain user
You can change the user account under which MQSeries Services runs to be
other than the default MUSR_MQADMIN. To do this, first create the new domain
Edward, are you sure that some of the messages didn't go to the DLQ on the
other end of your channel? I've seen this happen when the DLQ over there
gets full; the channel stops and the messages start to build up in the
transmission queue until it, too, is full. At least, I think that's what I
remem
Hello,
I have a very interesting situation. One of the applications using MQ forgot
to service the queue (meaning "GET" ing messages from the queue). Hence, the queue
filled up. But instead of trying to put the excess messages in the DLQ on the
receiving side, it started filling up the
No.
> -Original Message-
> From: Rainer Nonk [SMTP:[EMAIL PROTECTED]
> Sent: Monday, March 17, 2003 1:05 AM
> To: [EMAIL PROTECTED]
> Subject: Backout/Commit on queue-level
>
> Hi all,
>
> if i want to use MQs backout/commit feature on queue level: Can i
> achieve this by cr
Tim,
A simple REXX exec that writes a JES msg to the job log of the CHIN, initiated by your AO product will do the trick. (I'm pretty sure there is also be a JES parm/exit that could accomplish the same thing). I wrote an EXEC that simply writes the date at 00:00 every day - that way, you hav
Presently, we have three active logs for a QMRG (using Dual logging
mode). We're planning to 1) add a 4th log and 2) increase the size of
our current logs so they'll all be the same allocation.
Do we have to REPRO the contents of all the logs when we do the add
(during an upcoming weekend IPL) o
I will be out of the office from 03/17/2003 until 03/18/2003.
I will respond to your message when I return.
My emergency out-of-office contacts are listed below.
Pager: 917-218-8938 - Numeric
Pager: 800-800-7759 - Text
Phone: 201-251-3892
E-mail: [EMAIL PROTECTED]
Regards,
Vlad.
Instr
Another way around this with INETD is to disable execution permissions on
amqcrsta_nd. We experienced this because SeeBeyond connection factory was
hammering the connection when it was lost due to the QMGR coming down.
bobbee
From: John Scott <[EMAIL PRO
I've experienced a couple of problems with inetd on AIX. As a result we've
switched over to using runmqlsr. It did have some memory leaks but since
CSD04/05 it works fine.
I particularly found problems if you attempted to stop a queue manager when
using inetd. Inetd would still accept incoming con
Darren, sounds like it's time for something drastic. How about adding some
kind a dump/snap just before your call. Or my personal favorite -- simply
zap the preceding instruction to x'00' and force an S0C1 (or whatever it's
called in CICS). Not pretty, but generally pretty effective. Or you can try
I have heard that the RUNMQLSR has been much improved for 5.3 so it is
SUPPOSEDLY as good asd INETD over 500 connections. This statement is not
from experience or anyone else who has experience with it.
bobbee
From: Tim Armstrong <[EMAIL PROTECTED]>
Reply-To
You can try this. The output is readable with a 5250
emulator, but if you map the IFS folder in the windows
explorer and open the file it's not readable. When
browsing it with the dspf command it's not formatted in
a user friendly way, but it's at least readable.
/qsys.lib/mqm_elux.lib/saveqmgr.pgm
SIGN-OFF
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
This suggests to me that perhaps CSQZPARM was enqueued by something, and the
started task idled out waiting for the enqueue to be released?
Try a 'd grs,c' perhaps?
Stabbing wildly in the dark,
Ian
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of P
Karthikeyan
S
Karthik
I think this will help:
522
Explanation: All of the tasks in a job step were in an SVC wait state
for
the time specified in the JWT parameter in the SMFPRMxx parmlib member.
The event control block (ECB) specified in the wait request was never
posted. This could be the result of waiting
Hi !
What TIME have you in your STC or Job ? Try once with TIME=1440.
Regards
Guido
-Original Message-
From: P Karthikeyan [mailto:[EMAIL PROTECTED]
Sent: Montag, 17. März 2003 11:08
To: [EMAIL PROTECTED]
Subject: MQSeries OS/390 QMGR Abend - CSQV086E - Reason 00E80100 - Urgent
Hi,
Well, a S522 means the task has been in a SVC wait state for longer than
that allowed by your systems definitions.
I think that is set in SYS1.PARMLIB(SMFPRMxx) & JWT parm if that is still
the way its done.
I'm not sure what you had set up to prevent tasks like MQSeries getting
timed out like thi
Rainer,
Could you elaborate a little here. I would tend to think you would want
to use the backout/commit at a message level. So, when you commit a message
it is recognized in the target queue as visible and committed. You would
use the backout if an error of some sort you designated occurred
Hi,
Today we face the problem of queue managers getting abended with the following error
messages:
IEA995I SYMPTOM DUMP OUTPUT
SYSTEM COMPLETION CODE=522
TIME=15.21.01 SEQ=50409 CPU= ASID=0045
PSW AT TIME OF ERROR 077C1000 8DE01B1A ILC 2 INTC 01
ACTIVE LOAD MODULE
Rick, I have a rather unsophisticated environment - CEDF is the limit of my
online debugging facilities and this doesn't step into the MQXCNVC call.
The handle is fine for calls that follow the MQXCNVC call... wonder if it is
a problem passing the parameters...
Cheers
Darren
From: Rick Tsujimoto <[
Hi all,
if i want to use MQs backout/commit feature on queue level: Can i
achieve this by creating an own MQQueueManager instance for each queue:
...
qMgr1 = new MQQueueManager("qm", env);
qMgr2 = new MQQueueManager("qm", env);
qMgr2 = new MQQueueManager("qm", env);
...
queue1 = qMgr1.accessQueue
Title: RE: Maximum size of defined message
-Original Message-From: Stephan C. Moen
[mailto:[EMAIL PROTECTED]Sent: Saturday, February 22, 2003 9:21
PMTo: [EMAIL PROTECTED]Subject: Re: Maximum size
of defined message
The
simple answer Linda is there is no overhead or
43 matches
Mail list logo