RE: qsyslibl entries and qmqm

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 make the programmers add and remove QMQM when they make MQ Series calls.
It's also a good idea to code an "MQ Down" flag to sidestep the MQ Series
code.  MQ Series may run well 99% of the time but it can wreak havoc if you
need to restart it and all of your users have to wait for their calls to
time out.

Just my 2¢,

Scott Ingvaldson
AS/400 System Administrator
GuideOne Insurance Group

-----Original Message-----
date: Fri,  7 Nov 2003 12:03:05 -0800
from: Jerry <jdraper@xxxxxxxxxxxxx>
subject: qsyslibl entries and qmqm

Raging debate:

What belongs in qsyslibl?  I believe just IBM system stuff.

What belongs in qusrlibl?  I believe utilities, global app stuff, etc.

What belongs in jobd libl?  Jobd specific.

What belongs in app specific libl?  App specific.

This came up when trying to decide where to place the qmqm library Websphere
MQ
for iSeries V5R3).


Jerry

   
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.