Today, if my shop has an IEFUSI that limits jobs and started tasks to 64M of virtual, except for those DB2 subsystems that are know of, and I add a new test pre V8 DB2 subsystem with a name that doesn't provide for the IEFUSI exception, and the DB2 Sysprog tries to define large bufferpools, the system will cause the subsystem to fail, due to the limit. Now with V8, this doesn't happen, and the system goes into a wait state, because of a poorly implemented TEST subsystem? This is my complaint. Wayne Driscoll Product Developer Western Metal Supply NOTE: All opinions are strictly my own.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Ted MacNEIL Sent: Saturday, October 29, 2005 7:00 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: (fwd) Re: MEMLIMIT and IEFUSI >And if management has not purchased the 4 terabytes of disk space per DB2 region for backing store, who takes the heat when DB2 tries to get the space. ... DB2 is using 2GB, today. Tomorrow, I put in V8. And, it's suddenly using 4TB (or, 128)? C'mon! These things don't happen overnight. A DB2 sub-system can't use 4GB for bufferspace, unless it gets defined that way. If a DBA defines it without communicating it, then that DBA should be working elsewhere. -teD In God we Trust! All others bring data! -- W. Edwards Deming ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
