RE: qsyslibl entries and qmqm -- MIDRANGE-L

Forgive me, I am generally an unfailing iSeries fan, but we have had MQ
Series V5.2 (on OS/400 V5R1) lock up as described three times this year.  I
have supplied Hursley (MQ Series Development) with complete joblogs and
traces and no explanation or resolution was ever found.  Last month we
migrated the system to a new 810 and this month we had MQ (now V5.2 on
OS/400 V5R2 and all new hardware) lock up again, only this time we got the
same msg MCH3601 in the same place (Spin_Lock_Request) but the job did not
go to MSGW status.  It locked up and quit working but gave no indication
that anything abnormal had even happened.

I can forgive the occasional situation required a restart, but this can
require such things as having all users with QMQM in their library list to
logoff, deleting and recreating MQ journals and receivers, using ENDJOBABN
on the offending job(always requires this), clear "ghost queues" by clearing
IFS directories and once we had to uninstall and reinstall the entire
product.

We have never had to "IPL the machine to quiesce the product,"  but I would
find that completely uacceptable in an iSeries environment.  

Strangely enough, we never had any of these problems on MQ V4.x, they have
all occurred on MQ V5.2.  We are current on all PTF's and even(now) stop and
restart MQ Series while the daily backup runs (Developer said that MQ Series
could not run during a SWA backup, even though idle.)

I will say that 99% of the time it works great, but that 1% of the time that
it doesn't it will cause you pain.

Regards,

Scott Ingvaldson
AS/400 System Administrator
GuideOne Insurance Group

-----Original Message-----
date: Mon, 10 Nov 2003 10:06:28 -0000
from: "McCallion, Martin" <martin.mccallion@xxxxxxxxx>
subject: RE: qsyslibl entries and qmqm

Scott Ingvaldson wrote:

> I highly recommend that you do not put MQ Series libraries in 
> any library
> list. (including JOBD's)  MQ Series has a nasty habit of 
> locking up, (in our
> environment anyway) leaving all the users with requests 
> stacked up waiting
> for timeouts.  Then when IBM suggest a "cold start" you have 
> to make all of
> the users sign off so you can get the MQ libraries out of 
> their library
> lists.

I think this is slightly unfair to MQSeries.  It _used_ to be so, up to
and including MQSeries V4R2M1 -- and we had some times when we had put
QMQM in our SYSLIBL, and had to IPL the machine to quiesce the product.
So I would agree with the recommendation.  But I haven't seen anything
like the number of problems since MQSeries went to 5.1 and above.  Your
mileage may vary, of course.

And as to the version numbering, I think the original poster was
referring to MQSeries 5.3 (which is the current version) when he said
V5R3.  The AS/400 version of the product used to used the VRM numbering
convention like (but independent from) OS/400.  But after V4R2M1 (of
MQSeries) the version numbering (and codebase) was standardised across
the platforms (the OS/400 version came in line with all the others, in
other words).  So the correct way to refer to the release is "MQSeries
version 5.3".

Cheers,

Martin.

-- 
Martin McCallion
Senior Technical Consultant
Misys Wholesale Banking Systems
1 St George's Road, London, SW19 4DR, UK
T +44 (0)20 8486 1951
F +44 (0) 20 8947 3373
martin.mccallion@xxxxxxxxx
www.misys.com

   
This message and accompanying documents are covered by the Electronic
Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contains information
intended for the specified individual(s) only. This information is
confidential. If you are not the intended recipient or an agent responsible
for delivering it to the intended recipient, you are hereby notified that
you have received this document in error and that any review, dissemination,
copying, or the taking of any action based on the contents of this
information is strictly prohibited. If you have received this communication
in error, please notify us immediately by e-mail, and delete the original
message.