Steve,

There are two situations where RoadRunner's syntax implies selection of an
entire database:

The qualifier 'ISIMAGE' and the parameter 'DBSTORE'.  The 'isimage' qualifier
works well and when used in a select statement, against a database, will include
the '-410' and '-411' coded files (Select [log in to unmask] where isimage).
(Actually the 'safer' syntax should be "/ACCOUNT/GROUP/DBNAME@ where isimage" in
order to also include any 'jumbo chunks' and/or any 'b-tree' index files).

The 'DBSTORE' parameter, however, does NOT recognize the above indicated
filecoded files as being part of the database and will NOT store the entire
database if they have been modified AND conversely it will NOT store them as
part of the database if they have NOT been modified (This is mainly while a
partial is being performed).

I brought the above deficiency to "Unison's" attention more than 2 years ago
with no results.  A few months ago an e-mail from a Tivoli programmer was
submitted to this list asking some questions about which files/filecodes should
be included when an Image database is being stored.  That action gave the
impression that someone was addressing these issues, but it has been over 6
months without any results.

Perhaps you could 'elaborate' on the nature of 'your backup problem'.  You're
about to get better suggestions from this list than Tivoli.

Regards
Paul H. Christidis

____________________Reply Separator____________________
Subject:    Subject: Unknown PRIV files
Author: [log in to unmask]
Date:       5/26/99 7:37 AM

We've found that we've got the same files as Tim, and can't back them up
with RoadRunner (Tivoli).  After reading the thread, I contacted DISC and
got this reply:

Our index files use file codes -410 and -411.
File code -410 is used to signify the Omnidex root file (the file containing
a note of what is indexed in your database) but this is named <DB>0A where
<DB> is the name of your database, e.g. SALES0A.
File code -411 is used to signify the Omnidex indexes, the naming convention
for these being <DB>0B ... <DB>0Z ... <DB>1A ... <DB>1Z, etc.
As you can appreciate there is nothing to stop anyone else using these file
codes so I suspect that the QR files may not be Omnidex related as it does
not match the naming convention of our Omnidex root file.

Although I still haven't found out what the files are, the Tivoli support
desk has a work around for the backup problem - EXCLUDE them from the
backup!!.

Steve McKee
Technical Specialist
Scottish Legal Aid Board