HP3000-L Archives

February 1996, Week 1

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:
Steve Cooper <[log in to unmask]>
Reply To:
Steve Cooper <[log in to unmask]>
Date:
Wed, 31 Jan 1996 18:01:51 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
[log in to unmask] (James Overman) wrote:
 
>I've already updated Query (for a future to-be-released version) to use
>DBINFO 205 (and revert to DBINFO 202 if not available) for the FO command.
>Rather than add another line I squished the capacity line a bit to give
>
>      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??
 
Hi James-
 
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.
 
/Steve Cooper

ATOM RSS1 RSS2