RE: Limiting QUSER DASD

["Jones, John \(US\)" <John.Jones@xxxxxxxxxx>]

Elvis, thanks for the detailed reply.

1. I'm checking this out.  I've changed the QPWFSERVER class to top out
at 1GB.  Odd, that.  DSPCLS displays max temp in MB; CHGCLS lets you
change it in KB.  Anyway, this says it still doesn't enforce a cap on
QTEMP storage.  I'm not sure off-hand if that'll prove to be an issue or
not.

2. I've already tried restricting the user's max storage; didn't do
anything.  That's why I asked about limiting QUSER.  I dislike changing
IBM objects and am a little torn between changing the QUSER USRPRF and
the QPWFSERVER CLS.  QPWFSERVER is more localized to our issue but we
work with classes so rarely (and user profiles so frequently) that I'm
afraid changes to QPWFSERVER will be forgotten even if documented.

3. No budget for extra tools right now.  Believe me I wish I had some $
to spend..  Anyway, while we're not at V5R4 yet, we are now current on
V5R3 cume & Group PTFs.

4. We went down that road last summer.  Had IBM DB2 gurus help our
Crystal folks figure out the best way to access the dbs.  Also led to a
number of indexes being created for their most common queries.  Did
wonders for performance & response time.

Thanks,