Hello,

I'm trying to grasp DB2 SQL-replication.

In the example at http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/
topic/com.ibm.swg.im.iis.db.repl.asnclp.sql.doc/topics/
iiyrsclpbldscriptsql.html there is a section called "ASNCLP script 5
(subscription-set member)".

The code in the example contains this statement:

SET PROFILE TBSPROFILE FOR OBJECT TARGET TABLESPACE OPTIONS UW
USING FILE "c:\TSTRG.TS" SIZE 700 PAGES;

What's the purpose of the TSTRG.TS file? What should the permissions of
such a file be? Should it be backed up? Or is it temporary while setting
up replication? If not: Is is a performance bottleneck (i.e.: should it be
put on potent storage?). And if it's not temporary: placing it in the
root of the filesystem seems odd; would a better placement be something
like ~db2inst1/sqllib?

--
Troels

On Jan 12, 3:19*am, Troels Arvin <tro... (AT) arvin (DOT) dk> wrote:
If your target tables do not exist, asnclp will try to create them for
you. If you do not want the target tables to be created in the
default tablespace, then you need to give asnclp some information
about what the tablespaces you want it use. asnclp can also create
the target table spaces. You'll need to tell asnclp where to put it,
etc..

The Set Profile command tells asnclp about table spaces for those
situations where you're having asnclp create things for you. If your
target table already exists, the profile isn't necessary. If you're
good with all tables going into the default, no need for the profile
either.

The sample is just that and not a recommendation It's not likely
anyone would want to put table spaces in a root directory.

--
david

Hello Lennart,

In comp.databases.ibm-db2, you recently wrote:
Ah, it's to be interpreted as a tablespace container file, it seems.

[...]
I would very much appreciate that. Do you happen to also have init-scripts
for properly starting/stopping replication (capture and/or apply daemons)
on server boot/shutdown?

--
Troels