HP3000-L Archives

January 1996, Week 3

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:
Alfredo Rego <[log in to unmask]>
Reply To:
Alfredo Rego <[log in to unmask]>
Date:
Sat, 20 Jan 1996 10:25:39 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (52 lines)
I got a message from Jeff Kell:
 
> Speaking of DDX/DMX, let me bring up an old thread that never was resolved.
> The standard DBINFO call for capacity returns the "current" capacity of the
> dataset and number of entries.  Applications intelligent enough to check
> this before doing dbputs *STILL* fail even if DDX is enabled since it looks
> like there is no capacity left (example - OpenDesk).  It could be argued
> that if the "put" is critical enough to bother to check, then dbinfo
> shouldn't assume DDX expansion will succeed (adequate disc space).  This
> sounds more like an excuse; but I suppose the overhead of determining if
> DDX "would succeed" might be worse.  I still want this behavior changed.
 
 
Then, I got a message from Rene Woc, Adager's Senior Vice-President and
General Manager:
 
> A side effect on Adager's support is the support calls we get when somebody
> enables DDX on a detail dataset using default (!) for InitCap (which sets it
> to CurrentCap) and then runs query's 'fo sets' on this database.  Query
> appears as if no capacity change has taken place, and one has to point the
> user to dbutil's 'show ... capacity' command for the user to believe
> something did take place.  The user many times has already used Adager's
> 'report capacity' but believes that the information is coming from the same
> tool that made the change and is not certain that everything is ok. These
> phone calls usually take a long time because of the complexity of the
> explanation.
 
 
Birket Foster is a firm believer that everyone should be in the
"call-avoidance" business.  DBINFO's behavior, according to Jeff and Rene,
generates unnecessary calls.  For everyone's benefit, I agree with Jeff
that we should bring this old thread up again.  Let's hear the comments and
please let HP know what you think.  I'm sure they'll appreciate hearing
from the trenches.  This is the only way they can know what's important for
the users.
 
As a member of the SigIMAGE Executive Committee (SIEC), I'll be delighted
to convey those messages that shy people send directly to me, rather than
to the list.
 
 
+---------------+
|               |
|            r  |  Alfredo                     [log in to unmask]
|          e    |                           http://www.adager.com
|        g      |  F. Alfredo Rego               Tel 208 726-9100
|      a        |  Manager, Theoretical Group    Fax 208 726-2822
|    d          |  Adager Corporation
|  A            |  Sun Valley, Idaho 83353-3000            U.S.A.
|               |
+---------------+

ATOM RSS1 RSS2