I have already posted this question on mqseries.net, but I wondered if I
would get some more responses on the list server...
I am not looking for ideas on general MQSeries naming standards, I already
have those and there are enough examples in the archives to keep anybody
happy.
Our queue naming
Hi,
I'm replacing amqcrsta with runmqlsr. According to the insight I got from
the Vegas conference, and a FAQ from IBM: ..., a SINGLE listener can now
handle an unbounded number of connections... However, whenever I start
runmqlsr, a ps -aef | grep runmqlsr shows five instances of it running.
Is
Depending on the platform what you may be seeing is all the active threads
in the one listener process (with I think three active connections in this
case). Do the PPID values all go back to the same runmqlsr process? If so
then that would suggest that this is the case.
What release of MQ is
Title: Message
Hi
again
Either my mail from
yesterday got lost or notbody could help me on ma ssl problems... As a -18
doesnt provide much information, I would be interested on what ressources where
touched on the failing call (cert name, label name ?) Therefor I tried to use
the
I will be out of the office starting June 22, 2004 and will not return
until July 4, 2004.
I'm on the business trip. I'm reading mail on request only. In case of
urgency, please call me on my mobile: +386 40 456 639. If you cannot reach
me, please leave a voice mail or try to call me later.
Hi,
We recently upgraded from WebSphere MQ 5.2 to 5.3.1 on an OS/390 2.10 system.
We run a homegrown trigger monitor which does a GET WAIT on the batch initiation
queue, it runs as a batch job...not a started task. The JWT on this system is set at
15 minutes. For some reason, it seems
have TIME=1440 on the EXEC card?
Bill
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of
Sproull, George
Sent: Tuesday, June 22, 2004 11:16 AM
To: [EMAIL PROTECTED]
Subject: OS/390 GET WAIT Troubles
Hi,
We recently upgraded from WebSphere MQ 5.2 to 5.3.1
Aside from the JWT parameter in SYS1.PARMLIB(SMFPRMxx), I believe you can
have an SMF exit that gains control when jobs/users fail due to a wait
timeout. It's possible that the exit in your shop doesn't recognize the
STC names used for MQ 5.3.1. Or, you could simply code TIME=1440 as
someone
George,
I had opened a service request with MQ support a while back over the
changed behaviour of CSQOREXX at 5.3.The change is that CSQOREXX now
reacts to JWT where prior to 5.3 is seemed to not be affected by JWT. Here
is part of the reply I got:
The different behaviour of CSQOREXX is due
Our queues are named after what it is - we describe the contents of the
queue... because a queue does not do anything.
John Scott
[EMAIL PROTECTED]To: [EMAIL PROTECTED]
.CO.UK cc:
I always preferred SendingApp.ReceivingApp.BusinessReason where the third
parameter looks like your transaction portion of the name. Business name
could be defined as the business process_Interface so a message going from
SAP to ARIBA for warehousing of the GL arbitrage accounts would look like
Help please,
Box:
Windows 2000 Server SP4 (dual CPU)
Today I installed WMQ v5.3 with CSD01 using Terminal Services (to D: drive of
server) and the install went fine (I copied the CD to a local drive then did
the install from it). As I said, everything went fine and I reboot the server.
After
Roger, I am gonna guess this is just more typical MQ locked files, and
nothing specific to CSD07. Try the following, I wrote this up for my team
because we constantly deal with this:
When applying a CSD, no MQSeries dlls can be held by any programs. This step
will insure that all MQSeries dlls
Please ignore last posting, It seems to be specific to this platform(
Linux/zOS). On AIX, it shows only one.
Benjamin F.
ZhouTo: [EMAIL PROTECTED]
[EMAIL PROTECTED] cc:
We had a problem just like that and we even were using the MQPINUSEOK=1
flag. We tried stopping most of the services, but still got the error.
Eventually we just rebooted. Now mqver say it is at 530.7 CSD07, but I
wonder how good the install is. The queue manager is running and seems to be
Check the listserv archive (date around May 7,2004). There were some
excellent responses to a similar problem, not with W2K and Terminal
Services, but with applying CSDs in general.
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available
From the IBM docs:
- All MQ activity must be stopped before CSD install
- Check for processes with prefixes - amq,runmq, strmq
- Stop tools used to monitor MQ or any performance monitor tasks
- http://www.sysinternals.com (Process Explorer, etc.)
- CSD install log %TEMP%amqicsdn.txt shows the
Roger,
I had a similar problem with Win/2000 SP3 and CSD5. I rebooted several
times and it finally worked. I never did pin-down the cause of the
problem, you might want to look at the install log (see Quick Beginnings).
It should name the files it's choking on.
Roger Lacroix
In WBIMB when you are using a mapping node and configure the node to accept
the input from a RDB (database) source and have the output to a message set.
It look as if the mapping is going to generate a seperate SELECT call for
each mapping. In the database node you can combine mapping statements
Hi,
Of your list of files, besides IBM MQSeries, we have Windows Management
Instrumentation and stopping it did not help.
Regards,
Roger Lacroix
Quoting Potkay, Peter M (PLC, IT) [EMAIL PROTECTED]:
Roger, I am gonna guess this is just more typical MQ locked files, and
nothing specific to
Yes, that was Peter's checklist email plus some other comments.
Regards,
Roger Lacroix
416-566-7307
Capitalware Inc.
http://www.capitalware.biz
Quoting Lawrence Coombs [EMAIL PROTECTED]:
Check the listserv archive (date around May 7,2004). There were some
excellent responses to a similar
Fun is, huh?
Go to sysinternal.com, and download listdlls.exe. It is a lifesaver. Then
follow the below steps. Process Explorer is also found at sysinternals.
This has always worked, and I have dealt with CSD upgrades on 5.3 about 50
times. Ya know, this was never such an issue at 5.2.1.why
Yes, did that but it not help - the files remained locked.
Regards,
Roger Lacroix
416-566-7307
Capitalware Inc.
http://www.capitalware.biz
Quoting Kumar, Sudheer [EMAIL PROTECTED]:
From the IBM docs:
- All MQ activity must be stopped before CSD install
- Check for processes with prefixes -
What do people out there use for syncing up all their clocks on all their
servers?
We are using Transaction Vision to correlate our transactions. TV reports
the time from its sensors down to the millisecond (microsecond on z/OS and
UNIX). But if the servers are off in time by tenths or even
All,
Thanks for your comments.
No matter how many things I stopped and how many times I rebooted the server, I
had the problem with locked files.
Besides what mentioned below, here is what I did to resolve the problem:
- Removed the MQ Taskbar icon from the Startup folder
- Set the IBM MQ
Did you hide the MQSeries task bar icon? On the task bar, right click on
the Websphere MQ icon and select Hide from the menu. That stops
amqmtbrn.exe, and that has been enough to get me over the hump.
Roger Lacroix
[EMAIL PROTECTED]To:
See if a process has any of the MQSeries DLL's open.
http://www.sysinternals.com has a utility called process
explorer which can help. If you run it up choose the find
option then find dll - enter mq and it should find all
the processes with MQSeries dll's open. You can also try
the find handle
Roger,
And do you see patrolpsf.exe running? I had experience that this locked
amqmperf and amqxcs2 dll. Listdll is able to display that.
Cheers,
Ian
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Potkay,
Peter M (PLC, IT)
Sent: Wednesday, 23 June 2004 7:12
Hi,
I am working on MQSeries with AS400.
I have 2 queue managers speaking to each other using Remote queue
definition and transmission queue, sender channel and receiver channel.
What I want to do is track the message where all it flows through. For
this we need a channel exit program. I have
29 matches
Mail list logo
