RE: Limiting QUSER DASD

And see: http://archive.midrange.com/mi400/200602/msg00037.html

Bruce Vining




"Ingvaldson, Scott" <SIngvaldson@xxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
03/30/2007 11:00 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: Limiting QUSER DASD






See Accessing any job's QTEMP @:

http://search400.techtarget.com/tip/0,289483,sid3_gci816185,00.html 

Regards,
 
Scott Ingvaldson
System i Administrator
GuideOne Mutual Insurance Company


-----Original Message-----
From: Elvis Budimlic [mailto:ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx] 
Sent: Friday, March 30, 2007 10:49 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Limiting QUSER DASD

I don't think objects in QTEMP count as temporary storage in IBM
terminology so if Crystal reports are actually creating objects there
(how???), then you have a serious challenge on your hands, especially
without tools that can peek into QTEMP (PEX can, but I don't wish that
pain upon anyone).

Celebrating 10-Years of SQL Performance Excellence

-----Original Message-----
Subject: RE: Limiting QUSER DASD

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.





-----------------------------------------
DISCLAIMER:
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.