At 10:16 AM -0700 8/9/00, [log in to unmask] wrote:
>Before DDX, the operational staff would probably check if data sets were
>getting full, possibly with MPEX
>%LISTF @(DBSETFULLNESS > .9),DB
>
>They would dutifully check and expand the sets necessary during scheduled
>downtime, probably weekends.  Now comes DDX and the system manager tells
>operations, "You don't need to check DDX sets, they autoexpand".  So MPEX is
>changed to read
>%LISTF @(DBSETFULLNESS > .9 AND DBSETDYNAMIC=FALSE),DB
>
>Because operations isn't watching the sets, thinking DDX is doing the work,
>disaster will happen when you can't afford it.  Lots of data sets fill in
>the middle of the day, most likely at a time you can't afford to down.


Good point.

As useful and well written as we all know MPEX is, I'm quite surprised to
find that this has not yet been addressed in the software.

What we need is a new file attribute "DBSETMAXFULLNESS" which would
correspond to the currently available "DBSETFULLNESS", except that rather
than calculating entries/capacity it would calculate entries/maxcapacity.

Notice, however, that since there is now a "DBSETMAXCAPACITY" file
attribute that corresponds to the older "DBSETCAPACITY", one could probably
write a customized listf mode or script that calculated the *true*
fullness, taking into account whether or not DDX has been enabled.

Also, I notice that although my version of MPEX (27N81128) has
DBSETMAXCAPACITY and DBSETDYNAMIC, neither is mentioned in the online help.
Hmmm...that makes me wonder what other neat new features are hidden in the
software unbeknownst to me.



Barry Lake                                 [log in to unmask]
Allegro Consultants, Inc.                  www.allegro.com
(408)252-2330