HP3000-L Archives

August 1998, 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:
"Paul H. Christidis" <[log in to unmask]>
Reply To:
Date:
Mon, 10 Aug 1998 16:52:00 -0700
Content-Type:
TEXT/PLAIN
Parts/Attachments:
TEXT/PLAIN (26 lines)
Fellow Listers,

A few minutes ago I finished reading the PowerPatch 5 communicator.  Partly
based on what I read about 'MDX'/'DDX' and partly based on the excellent
discussion on this list of the intent of this new functionality and how it
should be used I thought of the following:

It sure would be nice if one could configure, using DBUTIL perhaps, some
method of notifying someone that an expansion had occurred.  It could be as
simple as a ':tellop' command or, for more flexibility, the name of a
command file with a predefined list of parameters (i.e. basename, setname,
increment, etc..).

The recent discussion about 'MDX' and 'DDX' highlighted the fact that they
are NOT intended to 'do away' with capacity management, their primary intent
is to prolong the availability of the database, even at less than optimum
performance, until a capacity change 'event' can 'safely' be scheduled.  The
'command file' option would be of great use for 'operator less' sites where
the system manager or the DBA/programmer in charge on a specific database
could 'configure' such a 'notification' command file and perhaps e-mail to
themselves or a central control point the 'expansion' event and the need of
scheduling a capacity change job.

Regards
Paul H. Christidis

ATOM RSS1 RSS2