HP3000-L Archives

August 1995, Week 4

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 Dirickson b894 westwins <[log in to unmask]>
Reply To:
Steve Dirickson b894 westwins <[log in to unmask]>
Date:
Thu, 24 Aug 1995 18:00:00 P
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
<<The current scorecard looks like this:
 
        For changing the behavior of DBInfo mode 202:
 
                John Sullivan (?)
                Jeff Kell
                Chris Bartram
                Ken Paul
 
        For not changing DBInfo mode 202:
 
                Steve Cooper (?)
                Guy Smith (?)
 
Let's now use the list to have a constructive debate on pros and cons for
making this change and register your vote and then we'll see if we need
to go to SIG IMAGE to ask for a change.>>
 
If DDX is turned on, "current capacity" is, from an operational
viewpoint, a purely fictitious number; it's only the capacity until it
isn't. So what good is the information? If I check just before the set is
auto-expanded, and then check again later, I'm going to use the most
current information anyway, so why not have Mode 202 report the "real"
limit? Mode 202 is a "tell me about the set" query, and part of the
information returned is "and how much can I put into it?" Since the true
answer to that "how much" question is the maximum capacity for a DDX set,
that's what Mode 202 should return. If someone wants all the gory
details, they're going to use Mode 205.

ATOM RSS1 RSS2