LISTSERV - HP3000-L Archives

HP3000-L Archives

July 2002, Week 4

HP3000-L@RAVEN.UTC.EDU

	LISTSERV Archives
	HP3000-L Home
	HP3000-L July 2002, Week 4

	Log In
	Register

	Subscribe or Unsubscribe

	Search Archives

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 >>]

Subject:	Re: IMAGE filetype
From:	Rene Woc <[log in to unmask]>
Reply To:	Rene Woc <[log in to unmask]>
Date:	Mon, 22 Jul 2002 19:13:26 -0600
Content-Type:	text/plain
Parts/Attachments:	text/plain (30 lines)

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.

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.

Cordially,

Rene

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

ATOM RSS1 RSS2

RAVEN.UTC.EDU