We did not let the default.
As a rule of thumb start with 1/3 of your total Workfile. Do
calculation after you increase 32K Workfiles (Bufferpool and
Monitor the following if an agent hits MAXTEMPS.
SQLCODE = -904, ERROR: UNSUCCESSFUL EXECUTION CAUSED BY AN
REASON 00C90305, TYPE OF RESOURCE 100, AND RESOURCE NAME =
SQLSTATE = 57011
And Check your Statistics Report columns AGENT MAX STORAGE (KB) and
OF MAX EXCEEDED 0
*From:* IDUG DB2-L [mailto:[login to unmask email] *On Behalf Of *Mark
*Sent:* Monday, February 14, 2011 5:48 PM
*To:* [login to unmask email]
*Subject:* [DB2-L] MAXTEMPS in DB2 9 for z/OS
We are about to go to DB2 9 CM on z/OS this weekend in production.
the new settings we are having some internal discussions on is the
setting to control the maximum amount of temporary workspace a
can use. The default setting is 0, which works the same as in DB2
no limit on any job.
How have you used this in your shops? Have you let the default or
trying to pick a memory setting that stops one job from taking all
and pushing other jobs out?
Any comments about your experience with this will be
This message contains privileged and confidential information
the above addressees only. If you receive this message in error
delete or destroy this message and/or attachments. The sender of
message will fully cooperate in the civil and criminal prosecution
individual engaging in the unauthorized use of this message.
[image: Independent, not-for-profit, User Run - the IDUG
difference! ] < http://www.idug.org/
The IDUG DB2-L Listserv is only part of your membership in IDUG. If
not already an IDUG member, please register here. < http://www.idug.org/register
* IDUG EMEA * Prague, Czech Republic * 14-18 November 2011 *
* If you are going to attend only one conference this year, this is
Mentoring should be a rewarding experience for everyone...
IDUG is offering up to 80% off when you both come to the
If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L
is the home of IDUG's Listserv