HP3000-L Archives

February 1996, 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:
Ken Sletten b894 c332 x62525 <[log in to unmask]>
Reply To:
Ken Sletten b894 c332 x62525 <[log in to unmask]>
Date:
Tue, 6 Feb 1996 21:19:00 P
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
Steve wrote after James:
 
>>      CAPACITY: 1015         ENTRIES: 14           MAXIMUM CAPACITY: 1015
>>
>>as an example.  As you can see, if a dataset is not enabled for DDX the
>>two capacities are the same.  So sometime soon there should be a patch for
>>Query that will at least show users both values.
>>
>>Is that OK??
 
>I would rather see non-DDX sets left alone, with just the CAPACITY
>column.  For DDX sets, show both CAPACITY and MAX CAP.  That way, if
>the two values are equal, you can tell at a glance that this is a DDX
>set that has grown to max, and not a set with DDX disabled.  Also, for
>those that choose not to enable DDX, Query's output won't change
>providing better backward compatibility.
 
I think Steve is exactly right.  With a small increment, having
a DDX-enabled dataset be right at the max will happen
once in a while.  And if it is, there would be no way to tell
from this display whether it is DDX-enabled or not.  Need to
be able to do that.
 
Ken Sletten

ATOM RSS1 RSS2