If you use Vesoft's Security 3000 product then you can disallow logons under
various conditions.  The following lines, taken from a Security 3000 help
screen, indicate one of the possibilities.


   $FORBID "JSCOUNT('PARTBACK,MANAGER.SYS&EXEC')>0"
             "Warning: system backup in progress - try again later"
             @[log in to unmask],MANAGER.SYS

Nicholas Saner
Gaiam, Inc.
(303) 222-3656

-----Original Message-----
From: Leonard S. Berkowitz [mailto:[log in to unmask]]
Sent: Thursday, June 22, 2000 5:53 AM
To: [log in to unmask]
Subject: [HP3000-L] Looking to bullet-proof a data base restore


Yesterday, in trying to restore a data base to a development machine, three
datasets could not be restored because they were being accessed. The restore
job
checks at the outset to make sure that the data base is quiet (MPEX: LISTF
db,ACCESS), but apparently some user or job opened the data base after
RoadRunner was already executing (this restore job takes 3 hours or so).

Can someone suggest a strategy to keep people out, other than waiting until
the
nightly window? If I change the file-access matrix for the group where the
data
base resides, will MANAGER.SYS (normal logon for the restore job) or a user
with
AM, OP still be able to restore the data base? I assume so, but I need
confirmation of this approach or the suggestion of an alternate strategy.

Thanks.
===================
Leonard S. Berkowitz
Perot Health Care Systems
(Harvard Pilgrim Health Care account)
voice: 617-509-1212
fax:   617-509-3737
pager: 781-226-2431