HP3000-L Archives

March 1998, 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:
John Zoltak <[log in to unmask]>
Reply To:
John Zoltak <[log in to unmask]>
Date:
Tue, 24 Mar 1998 09:14:53 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (71 lines)
Here's my 2 cents, which seems opposite of the opinions so far. By I
would like to see

        b) have LISTF,2 use the same output format for 1TB files as it
does for
           smaller files even if this breaks some existing applications
working on
           less than 4GB files.  That is, force applications to change
as soon as
           large files become supported even if there are no large files
on the
           system.

Any CI command file that I have use a LISTF,6 and then uses FINFO for
the details. Any of the programs that I have that need to process this
information, use the same LISTF,6 and calls to FLABELINFO. So I am ready
right now for the change!

John Zoltak
North American Mfg Co

> -----Original Message-----
> From: Jeff Vance [SMTP:[log in to unmask]]
> Sent: Monday, March 23, 1998 6:45 PM
> To:   [log in to unmask]
> Subject:      [HP3000-L] 1 Tbyte files and LISTF
>
        <snip>

>    What is more important to you and your customers (not mutually
> exclusive
>    choices):
>
> a) guarantee 100% that all existing programs and scripts that process
>    LISTF,2 output will work correctly on all files <= 4 Gbytes.
>    However, for files larger than 4GB, these programs and scripts may
>    require modification.
>
> b) have LISTF,2 use the same output format for 1TB files as it does
> for
>    smaller files even if this breaks some existing applications
> working on
>    less than 4GB files.  That is, force applications to change as soon
> as
>    large files become supported even if there are no large files on
> the
>    system.
>
> c) guarantee that any existing program/script that tries to process
> LISTF,2
>    output on files larger than 4GB will return accurate results.  For
>    instance if this "old" program is adding up the EOF field it will
> get an
>    addition error or abort or ??? when it encounters a large file.
> That is,
>    you don't want this program to silently "skip" (or add the wrong
> units of
>    measure for) this large file when computing the total EOF across
> the
>    fileset.
>
>
> Your input will help us make design trade-offs on the LISTF and
> LISTFILE
> command's support of Large Files.
>
> thanks,
> Jeff Vance, CSY
>
> --

ATOM RSS1 RSS2