First, here's 2 methods of doing what Dan asked for:
 
 
1) free
 
   :debug
   map myprog.pub.fum
      (assume it returns the virtual address $123.0 and a size of $10000 byes)
 
   fva $123.0, $10000
   unmap 1
   c
 
 
  NOTE: the above assumes that the program is *IN USE* at the time that
  you do the FVA command!  This is important, because if it isn't in use,
  then you've just mapped it in as *DATA* pages ... and when MPE gets around
  to loading it for the first person who wants to run it, the existing pages
  will be tossed out of memory, with no gain whatsoever!
 
  One workaround to the above is:
 
      :run myprog.pub.fum;debug
      map myprog.pub.fum
        (assume it returns the virtual address $123.0 and a size of $10000 byes)
      fva $123.0, $10000
      unmap 1
      c (or abort, as desired)
 
2) <PLUG> KLONDIKE, one of the tools from Lund Performance Solutions toolbox
   </PLUG>
   With KLONDIKE, assuming you've installed the UDCs, you can do:
 
      :freeze myprog.pub.fum
 
   NOTE: subject to precisely the same limitations as above.
 
   One workaround is:
 
        :run myprog.pub.fum;debug
        :freeze myprog.pub.fum
        c (or abort, as desired)
 
The Kelly RAMDISC is not a solution, as it will refuse to load NMPRG
files (because of the above described limitations)
 
 
 
> Dan's original message suggested that there was a POSIX interface on unix that
> could be used to lock a file into memory.  Is this true?  I'd be kind of
> surprised if the POSIX.1 standard included such an interface (and shouldn't we
> then have it on MPE/iX too?).
 
No, Dan contended that there is, but the closest I could find is a procedure
that says "lock *MY* program into memory" ... which is not the same ability
as "lock *THAT* program into memory".
 
 
--
Stan Sieler                                          [log in to unmask]
                                     http://www.allegro.com/sieler.html