HP3000-L Archives

March 2001, Week 3

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:
"Johnson, Tracy" <[log in to unmask]>
Reply To:
Johnson, Tracy
Date:
Mon, 19 Mar 2001 14:05:53 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (74 lines)
Oh yeah, what am I thinkin'.  Brain fart.

Although I think the concept still applies to
itty bitty files.  Rack a bunch of them up
and treat them as a byte stream.  Most of my
command files are less than 12 fixed record lines.

Tracy Johnson
MSI Schaevitz Sensors


-----Original Message-----
From: Simonsen, Larry [mailto:[log in to unmask]]
Sent: Monday, March 19, 2001 1:56 PM
To: 'Johnson, Tracy'
Cc: Hp3000-L (E-mail)
Subject: RE: Maybe ALLOCATE Should be Brought Back? [was: I don't
underst and ...]


16 sectors is 4096 bytes.  The file allocation is in pages.
The allocate only resolved the links in the shared libraries it did not
create a stack or force the program to stay resident in memory.


-------------------------------------------------
Larry Simonsen                Phone: 801-489-2450
Flowserve Corporation     Fax: 801-491-1750
PO Box 2200                    http://www.Flowserve.com
Springville, UT 84663      e-mail: [log in to unmask]
-------------------------------------------------
All opinions expressed herein are my own and reflect, in no way, those of my
employer.

 -----Original Message-----
From:   Johnson, Tracy [mailto:[log in to unmask]]
Sent:   Monday, March 19, 2001 10:45 AM
To:     [log in to unmask]
Subject:        Maybe ALLOCATE Should be Brought Back?  [was: I don't
understand ...]

The prior statements on flat file blocking factor got me to
thinking...

There used to be a thing in MPE/V where you could ALLOCATE
programs in (virtual?) memory so that the system didn't have
to go out and do a "step-and-fetch-it" to disk every time
you ran a program.

Let's say I have a bunch of rinky-dink little command files,
yet at the same time, I do not want to be troubled with
turning them into a UDC.  Each file uses 16 sectors (thanks
to the invention of MPE/XL, now MPE/iX.)

What if one were to "read-in" a bunch of those command files
in to a 4096 byte page of memory.  I could cram 256 of those
little 16-sector command files into this so-called page.

Anytime I wanted to use one of those command files, via
some reiteration of the old ALLOCATE command.  It would go
read the appropriate section of this page instead of looking
up the command file.

Tell me if this sounds too much like a UDC, do UDCs utilize
memory in this way or is this a different concept?  It
sound more like the old ALLOCATE idea than UDCs to me.

Tracy Johnson
MSI Schaevitz Sensors


(P.S. I do use the full width in my 128-byte-wide files,
thanks.)

ATOM RSS1 RSS2