HP3000-L Archives

December 2003, 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:
Michael Berkowitz <[log in to unmask]>
Reply To:
Michael Berkowitz <[log in to unmask]>
Date:
Tue, 9 Dec 2003 13:45:05 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (39 lines)
Tracy Pierce writes

-----Original Message-----
From: Tracy Pierce [mailto:[log in to unmask]] 
Sent: Tuesday, December 09, 2003 1:39 PM
To: [log in to unmask]
Subject: Re: KSAMXL File problem


just my .03...

1) it would seem perfectly adequate to simply post hpvariable results
for
the last file examined; if the user really wants results for a number of
files, that could be easily engineered.

2) KSAM64?  is that the same as KSAM or KSAMXL, or is it a 3rd entity?

Tracy (stuck on 6.0) Pierce
----------------------------------------------------------------------
From the 6.5 communicator:

Large File support of KSAM files requires the addition of yet another
KSAM file type. Due to the internal structure of CM KSAM and KSAM XL
files, these file types cannot support file sizes beyond 4GB. The
implication of this was that in order to meet our customer demand of
Large File KSAM support, a new KSAM file type needed to be defined. This
new KSAM file type is the KSAM64 file, or file type 7. KSAM64 files have
an improved, generalized internal structure that allows them to support
file sizes from one record to the maximum object size of 128GB. KSAM64
files are externally identical to KSAMXL files (and support all CM KSAM
intrinsic calls as well).

Mike Berkowitz
Guess? Inc.

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

ATOM RSS1 RSS2