In message 
<[log in to unmask]
 >, "[log in to unmask]" 
<[log in to unmask]> writing at 12:55:50 in his/her 
local time opines:-
>I've been using:
>
>RUN MV.HPBIN.SYS;INFO="/from_filename /to_filename"
>
>for years now.   (note use of posix filenaming convention.  Not sure if 
>it's required - but it works just fine)
>
>This is a handy way of doing a 'hot install' of a program or library 
>that's in production - w/o taking the application down.
>
>Users that have loaded the program/library BEFORE the 'mv' command 
>continue using the old program/library, until they exit.  (you can see 
>who's still using the old program/library by doing a 'listf filename,9')
>
>Users loading the program/library AFTER the 'mv' command will start 
>using the 'new' program/library.
>
>MUCH easier on your users than forcing everyone to quit/restart.  Only 
>the users that NEED the fix need exit/re-enter the app.
>
>Of course, YMMV - but it's worked well for me.
>
>-Brian Edminster
>Applied Technologies, Inc.
>"Robust Solutions and Integration For Today and Tomorrow"
>
>See www.MPE-OpenSource.org for this, and more tips on keeping your 3000 
>alive and thriving.

You can do something very similar in straight MPE with:-
PURGELINK targetfile
COPY sourcefile, targetfile

I used to do this a lot, generally with both commands within a user 
command, to minimise the window for failed access to targetfile during 
the process.

I guess the 'mv' approach might be completely atomic, and so close this 
window completely, though?

Roy
-- 
Roy Brown        'Have nothing in your houses that you do not know to be
Kelmscott Ltd     useful, or believe to be beautiful'  William Morris

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