Rene and Alfredo jump in with some excellent thoughts.

Actually, I can see where someone, having just copied an attached TURBODB,
would also want to have it attached to an SQLDBE, maybe for test purposes.
But in reality, you do not want to copy the TC file since the corresponding
ATC file will not have the information back to the copied TURBODB.  As you
have stated, a copy of the TC file is irrelevant and indeed must not be
copied.

However, might I be so bold as to suggest that when copying an attached
TURBODB, you might possibly consider doing two things:  1- Inform the user
that the TURBODB is attached to one or more DBEs (and perhaps even list them
by the simple expedient of reading the TC file.)  2- Detach the copied
database and tell the user you did that. I believe it is only a simple
matter of flipping a bit in the newly copied root file.  (If you are already
doing that, please excuse my ignorance.)

As for the utility to which you refer, indeed it was made freeware a few
years back and is freely downloadable at www.hicomp.com/dbtune.htm.  Please
read the page and download away.  It has been updated for the latest release
of IMAGE/SQL.


Kind regards,

Denys. . .

Denys Beauchemin
HICOMP
(800) 323-8863  (281) 288-7438         Fax: (281) 288-7438
denys at hicomp.com                             www.hicomp.com

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On Behalf Of
F. Alfredo Rego
Sent: Monday, July 22, 2002 9:29 PM
To: [log in to unmask]
Subject: Re: IMAGE filetype

At 7:13 PM -0600 7/22/02, Rene Woc wrote:

>Hello Denys,
>
>At 7:42 PM -0500 7/22/02, you wrote:
>
>>Leaving my argument about tape subsystem technology with Stan aside for a
>>minute, the TC file is filecode -430.  I am rather surprised that Adager
did
>>not copy it.  If it did not, it probably had a reason not to.  For the
newly
>>copied database, what does a DBUTIL SHOW MYDB ALL reveal about the
>>attachment?  If it does not complain, perhaps it was not attached at the
>>time of the copy and therefore the TC was left behind as an extraneous
file.
>
>Adager database copies are not attached to SQL DBEs even though the
>source database may be. This is a design decision, since users most
>likely do not want to attach the database copy to the same DBE the
>source database is. Therefore, it does not copy the TC file because
>it's not relevant.

I should have said all of this, explicitly (even though some people
have complained about Adager's verbosity :-)

Sorry about the confusion caused by my lack of an explicit message
during Adager's "copy database" function.  I made a note to correct
this oversight.


>If the user wishes to attach the database copy to some SQL DBE, I
>recommend using your IMAGE/SQL utility to extract all relevant
>"attach" information from the source database.

Just to be explicit, I want to make sure that everybody is on
the same page as Rene:  When Rene says "your IMAGE/SQL utility",
he refers to the utility that Denys wrote.

Denys: If I remember correctly, you kindly made your IMAGE/SQL
utility available for download.  Could you please refresh our
collective memory with the URL?

Thanks,

   _______________
  |               |
  |               |
  |            r  |  Alfredo                     [log in to unmask]
  |          e    |                           http://www.adager.com
  |        g      |  F. Alfredo Rego
  |      a        |  Manager, R & D Labs
  |    d          |  Adager Corporation
  |  A            |  Sun Valley, Idaho 83353-3000            U.S.A.
  |               |
  |_______________|

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *