John Dunlop wrote (after my direct e-mail reply):

> Jeff, thanks for your speedy reply. You replied :
>
> >Use VSUSER [volsetname]
>
> Granted the VSUSER command will tell me if any users are logged onto a
> particular volumeset, but that does not tell me if anyone is accessing a file
> in that volumeset from a logon outside that volumeset (e.g. with SM
> capability). Or am I misunderstanding logons and volumesets ?

I opened a database on our workspace set, hit break, and tried:

> (MANAGER.SYS): vsuser workspace
>    VOLUME SET NAME                  JOBNUM   JOB NAME
>  ---------------------------        ------   --------
>  WORKSPACE                           S5345   MANAGER.SYS
> (MANAGER.SYS): resume

And after exiting query:

> (MANAGER.SYS): vsuser workspace
> No volume sets currently reserved. (CIERR 10625)

I also noticed a background job running in our production account was
accessing the development volumeset.  After some fishing around, I
found that my userID in production has :setcatalog udcform.form.tym
(Formation UDCs) which is indeed on the development volumeset.

Depending on your application, you might try :VSCLOSE volset;NOW
(requires that you be operator or allowed the command) which will
abort any jobs/sessions accessing 'volset'.  You will have to VSOPEN
it before backing it up, of course.

Jeff Kell <[log in to unmask]>