HP3000-L Archives

May 1999, 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:
Joseph Norris <[log in to unmask]>
Reply To:
Joseph Norris <[log in to unmask]>
Date:
Fri, 14 May 1999 06:51:02 -0700
Content-Type:
TEXT/PLAIN
Parts/Attachments:
TEXT/PLAIN (32 lines)
If you want to really get into producing reports from ksam files, I would
suggest looking at suprtool from Robelle. I worked for 3 years in a shop
that was an IBM isam conversion to KSAM and we used suprtool for
reporting. You can define the fields, do an extract and the list option
has basic reporting features. Or you can extract to a file and use another
language for reporting.


#Joseph Norris (Perl - what else is there?/Linux/CGI/Msql)
print @c=map chr $_+100,(6,17,15,16,-68,-3,10,11,16,4,1,14,-68,12,1,14,8,
-68,4,-3,-1,7,1,14,-68,6,11,15,1,12,4,-68,-22,11,14,14,5,15,-90);


On Fri, 14 May 1999, Don Seay wrote:

On Thu, 13 May 1999 14:22:40 -0400, Michael Berkowitz
<[log in to unmask]> wrote:

>I don't know of any free report writer for Ksam files, but if you want a
>dump of a file for a key value you can use FCOPY.
>
>:FCOPY FROM=ksamfile;TO=;SUBSET="char string",start key column
>

It's been a while since I've done extensive work with KSAM files, but
I seem to recall that with CM KSAM, if the records do not need to be
retrieved in key order, you can significantly speed up the FCOPY by
adding ;KEY=0. I think that forces FCOPY to ignore the key file and to
sequentially read the data file. Lots less I/O that running down a
key's path in the key file and picking up the corresponding data
records.

ATOM RSS1 RSS2