Jeff after Doug after Donna after me:

> > I think that if you VSCLOSE the mirrored volume set prior
> > to the =SHUTDOWN then it may not matter whether or
> > not the system reaches SHUT 6 because the volume set
> > is not mounted at the time of shutdown. If my
> > speculation is true the VSCLOSE will perform all
> > synchronization steps and flag the volume set as 'good'
> > just as the shutdown process would.
> >
> > </speculation>

ooh.....  good thought....

> Well, a VSCLOSE;NOW might do it but abort a lot of
> people using the volume set.

If power has been out for 50 minutes and no one has run up
to the computer room to initiate a graceful shutdown yet,
even if we still have users accessing files I would rather blow
them away 10 minutes early (since power out for 50 min
likely means odds are not real great it will come back on in
the next 10 (at least around here) ).

> .....  And that's a console command that you would have to
> finagle a way to execute.  But agreed, it would flush XM
> and shut the volume set cleanly.

Right about the "VSCLOSE; NOW"....   hmmm..... MPE help
for VSCLOSE appears to have a bug under the OPERATION
section...  It sez:
=========================================

This command may be issued from a session, job, program,
or in BREAK.  Pressing [BREAK] has no effect on this
command. This command may be issued only from the
system console.
=========================================

?? "may be issued from session, job, program";  but also
"may be issued only from console" ??....   I believe Jeff is
correct:  ONLY if including the "; NOW" suffix qualifier do
you need to have the CONSOLE (admit I don't recall actually
trying it from anything OTHER than the CONSOLE).

If that is correct and "non-NOW" VSCLOSE can be issued
from other than CONSOLE, then at least for our site most of
the time this would do the trick;  since a combination of our
"orderly shutdown" jobs and wild-card MPEX ABORTJOB
usually gets rid of all users of all volume sets....   but I would
certainly <plug> for an enhancement to allow  VSCLOSE;
NOW  from a job;  IF we cannot get the full   SHUTDOWN
from a job capability.....  but since as Donna mentioned it
came up # 2 on the SIB last time, let's <plug> hard for the
"SHUTDOWN from JOB or SESSION" enhancement first:
That will take care of everything including VSCLOSE....

We still have a few swing shift users working out in the shop;
otherwise I would have gone up and tried the VSCLOSE first;
then "<CTRL>-B RESET prior to SHUT 6" thing...

Ken Sletten