HP3000-L Archives

August 2000, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Barry Lake <[log in to unmask]>
Reply To:
Barry Lake <[log in to unmask]>
Date:
Thu, 10 Aug 2000 13:22:54 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (27 lines)
At 8:42 PM +0200 8/10/00, [log in to unmask] wrote:
>Michael wrote...
>
>>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. However, a potential quick solution in this case (in the
>middle of the day) could be to run QUERY, add a couple of entries to
>the "seemingly full" datasets (just enough to trigger a DDX expansion)
>and then delete them again. Not ideal, but probably doable.


I think what Michael was trying to express was a situation in which you
have DDX enabled, and therefore are lulled into believing you don't need to
worry about capacity management anymore. Over time, the data set
automatically expands until it reaches the MAX capacity. At that point,
even your query trick wouldn't help...


Barry Lake                              [log in to unmask]
Allegro Consultants, Inc.               www.allegro.bogus.com
(408)252-2330
--------
Attempting to use anti-spam technique.
Remove ".bogus" to create valid address.

ATOM RSS1 RSS2