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:
Michael Berkowitz <[log in to unmask]>
Reply To:
Michael Berkowitz <[log in to unmask]>
Date:
Thu, 10 Aug 2000 13:51:11 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (54 lines)
Barry Lake writes:

-----Original Message-----
From: Barry Lake [mailto:[log in to unmask]]
Sent: Thursday, August 10, 2000 1:23 PM
To: [log in to unmask]
Subject: Re: - DBexpansion: Addendum...


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...
----------------------------------------------------------
Actually, that wan't what I was thinking of.  If you do DDX write, you
should put your max capacity at the 4GB limit.  In other words some
unobtainable size like 10,000,000 on a data set that normally has 50,000
records.  This is what I was referring to.

Pre-DDX enable:
Operations checks weekly capacities and expands as necessary.  Intelligent
user program that does a mode 202 DBINFO almost never reports a potential
full condition.

DDX enabled:
DDX enabled as follows on new or existing sets.
Capacity: 10000000,10000,1000
Say you have a data set with 8500 entries and a limit of 10000.  You DDX it
with max capacity 10,000,000 increment of 1000, keep initial capacity of
10000.  You tell operations, "don't need to check this set no more, we're on
cruise control".  1500 entries added to set, no problemo.  User on last day
of month trying to ship end of month merchandise out tries to add entry
10001.  Intelligent program doing mode 202 DBINFO complains.  Warehouse
manager says, "What do you mean everybody logoff!".  You look for work at
Dairy Queen.

Mike Berkowitz
Guess? Inc.

ATOM RSS1 RSS2