HP3000-L Archives

April 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:
Tracy Pierce <[log in to unmask]>
Reply To:
Tracy Pierce <[log in to unmask]>
Date:
Fri, 11 Apr 2003 07:09:16 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (39 lines)
I'm not convinced that FSPACE(fn,-1) really does work reliably with CM KSAM:
How can it?  All the docs I've read (ie not all of them!) indicate that the
indices are single-threaded, leaving reliable backspace theoretically
impossible: there is no backward pointer like there is on Image paths.
Please tell me I'm wrong?

Tracy (expecting correction) Pierce

> -----Original Message-----
> From: Jeff Kell [mailto:[log in to unmask]]
> Sent: Thursday, April 10, 2003 7:10 PM
> To: [log in to unmask]
> Subject: Re: FSPACE and KSAM
>
>
> John Pitman wrote:
>  > Having found that FSPACE(fn ,-1) does a logical (key
> sequence) backup
>  > in CM KSAM, does anybody know if it will also work on NM
> KSAM please?
>
> It works in the positive direction at least.  We have a common routine
> (name search) that pulls a screenful (20 recs) of matches
> from a common
> starting point by ffindbykey/fspace(x) to the starting point
> of the next
> screen, read 20 recs, display, if they want more, x=+20, iterate.
>
> In this case, CM code works on KSAMXL :-)
>
> Jeff
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>

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

ATOM RSS1 RSS2