HP3000-L Archives

June 2000, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Joseph Rosenblatt <[log in to unmask]>
Reply To:
Joseph Rosenblatt <[log in to unmask]>
Date:
Thu, 22 Jun 2000 08:03:16 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (37 lines)
Leonard,
If I am not mistaken RR has a DBSTORE function that will not allow you to
STORE a partial DB. I think it has an equivalent function for restoring
databases. If that doesn't work you can always change the group password.
Joseph Rosenblatt
-----Original Message-----
From:   HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf
Of Leonard S. Berkowitz
Sent:   Thursday, June 22, 2000 7: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

ATOM RSS1 RSS2