• Subject: Re: Matching Record (Was Need Help)
  • From: "James W. Kilgore" <qappdsn@xxxxxxx>
  • Date: Tue, 05 Aug 1997 22:54:51 -0700
  • Organization: Progressive Data Systems, Inc.

John Carr wrote:
> 

> <SNIP SNIP>
> 
> 
> Without looking, What was Position 45 in the header Spec (HSpec) used for
> in RPGII? 
Peering through the cob webs I'm comming up with nohalt for unprintable
characters, but there 
as a little voice saying no, no, it's to allow for inquiry
interrupt.....but then again.....

 ok ok,  How about; How was CORE STORAGE INDEX defined in RPG
> and what was it's use?

The key value at the beginning of each track of the index portion of a
file.  The system could narrow down it's search to the nearest track. 
This index was retained in CORE STORAGE when you used to get your
processor from a CORE house.  It was originally used by the program
specifying the index (S/34 F spec) then graduated to a system level
resource automatically calculated and sharable by all programs (S/36
ocl).

I think the math went something like (key length + 3) * #of tracks =
storage index size

It's a curse to remember even only half the details of stuff like this. 
Sometimes I wake up in the middle of the night, in a cold sweat,
screaming "when will it stop!" =:-o
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].