HP3000-L Archives

March 2005, 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:
"Vance, Jeff H (Cupertino)" <[log in to unmask]>
Reply To:
Vance, Jeff H (Cupertino)
Date:
Wed, 23 Mar 2005 13:17:31 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (38 lines)
Hi all,

I've completed the external specs for the new DEVINFO CI function and
have available for your comments an early draft of the HELP text. Please
see:

http://jazz.external.hp.com/private/devinfoHelp.txt

Also we have similar specs for volinfo and spoolinfo, see:

http://jazz.external.hp.com/private/volinfoHelp.txt

http://jazz.external.hp.com/private/spoolinfoHelp.txt


We would very much appreciate your review of these external specs.  Are
we providing enough information to meet your needs?  Also, as important,
are we providing too much info, too many aliases, overlapping data,
unnecessary formatted results (where the integer form will suffice),
etc.

For instance, does spoolinfo really need to accept "Onnn" and "#Onnn" as
valid inputs for the target spoolfile?  Does devinfo need to distinguish
between "all printers" vs. "serial printers" vs. "ds printers" -- ditto
for terminals?  Do we need to distinguish between MB and sectors for all
of the disk size items returned by volinfo?  Etc...

If we are returning information or formats which you don't see value in
please let me know. If I can reduce the complexity of these functions
and still meet customer needs then we all win. 


Thanks,
 Jeff Vance, vCSY

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2