[Info-vax] Proper dismounting of disks at shutdown
John Wallace
johnwallace4 at yahoo.co.uk
Mon Jul 11 14:02:12 EDT 2011
On Jul 11, 4:50 pm, Albrecht Schlosser <ajs856S... at go4more.de> wrote:
> On 11.07.2011 17:41, JF Mezei wrote:
>
> > What is the incantation that allows a process to run down properly
> > instead of STOP/ID= ?
>
> Maybe STOP/IMAGE/ID=
> in more recent VMS versions (I don't know exactly when it appeared,
> but it is present in V7.3-2).
>
> > Allin1 leaves a few processes lying around, and I have been using
> > STOP/ID to rid of them, but I guess that isn't enough to cause the
> > global sections to be vaporized.
>
> If STOP/IMAGE works, then the process can run its exit handlers, and
> depending on how it has been designed, this may enable the process
> to delete the global section(s).
>
> Albrecht
You might want to look at the VMS documentation or online help for the
system service $FORCEX. I can't comment on whether it will help in
JF's particular case, but it clearly exists, does pretty much what you
describe (forces the exit of an image in another process, without
terminating the process), and is even potentially relevant on VMS
versions prior to V7.3 (a long way prior, in fact).
At least one example of $FORCEX documentation can be found (for now)
in the System Services Reference at
http://h71000.www7.hp.com/doc/73final/4527/4527pro_041.html
and there will doubtless be similar ones elsewhere for different
versions of VMS.
There's also discussion of $FORCEX in the relevant sections of the VMS
Programming Concepts manual, e.g. the section on Performing Image
Exit. There's one currently at:
http://h71000.www7.hp.com/doc/82final/5841/5841pro_016.html
There were some example $FORCEX programs in the ITRC, but although the
index entries are still Googlecached, the recent HP improvements to
the ITRC mean the content is lost (at least for those I tried).
Have a lot of fun,
John
More information about the Info-vax
mailing list