Rob,
Good points, and it was not until I started
work here that I saw this technique. My first
response was wt?
After eight years, I believe the "unlimited"
PF approach is valid, assuming the implications
are understood and managed.
As you said, probably a non-starter for his customer
and probably a nice enhancement for his app.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, September 18, 2013 8:45 AM
To: Midrange Systems Technical Discussion
Subject: RE: File size warning
Gary,
However, he has a customer who asked for this feature. It's up to him to determine if he can, and is willing to, and how to pass on the cost of, this feature. Telling his customer he's micromanaging probably won't go well.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: rob@xxxxxxxxx
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 09/18/2013 10:41 AM
Subject: RE: File size warning
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Gary has a point here. I guess I would only put a maximum extents on
files that have been known to be affected by runaway jobs.
There are several ways to query the system catalog for files(tables) whose
members(partitions) whose size is huge, have a lot of deleted rows and so
on.
Rob Berendt
midrange.com
