Subject: | |
From: | |
Reply To: | |
Date: | Thu, 11 Jun 1998 14:19:17 -0600 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
DBSTORE does more than ensure the availability of all sets of a database.
It also includes them in the store even if they are not explicitly specified.
In other words, you can store a database simply by selecting its root file
and spcifying DBSTORE. Using DBSTORE also sets the store date and
resets the 'dirty" flag in the database. Many of us have relied on this
funtionality in the past, and can no longer do so when we implement
jumbo datasets or TPI.
>>> Joseph Rosenblatt <[log in to unmask]> 06/11/98
01:32pm >>>
RoadRunner does store Jumbo Dataset files. The DBSTORE function only
ensures that if all the DB is not stored that none of it is available to
be restored , i.e. all or nothing. By using the HFS naming convention in
your store/restore select statement all files will be stored/restored,
those in the HFS name space and those in the MPE name space.
e.g. /@/@/@/ (which is the same as /) stores everything
/account/data/dbfile@/ will store all jumbo sets files
It requires a bit of observation on the part of systems and operations
but I have yet to lose a backup due to this DBSTORE problem.
The cause for concern is the lack of response from the vendor. This may
have been addressed. See * RoadRunner (FWD) * in this weeks listings. It
wouldn't hurt to call your sales rep and or tech services dept at
TIVOLI. HP occasionally forgets that the 3000 user is important so how
much can we expect from TIVOLI (IBM)?
|
|
|