Only *remote* nodes need to be cataloged using CATALOG TCPIP NODE. Your
local system automatically qualifies as a node. When you create a database,
it will be created on the local node. Do a "db2 list db directory" with a
local and a remote database cataloged and you'll see it looks like:
System Database Directory
Number of entries in the directory = 2
Database 1 entry:
Database alias = RMTSAMP
Database name = SAMPLE
Node name = RMTNODE
Database release level = a.00
Comment =
Directory entry type = Remote
Catalog database partition number = -1
Alternate server hostname =
Alternate server port number =
Database 2 entry:
Database alias = SAMPLE
Database name = SAMPLE
Database drive = D:\DB2
Database release level = a.00
Comment =
Directory entry type = Indirect
Catalog database partition number = 0
Alternate server hostname =
Alternate server port number =
Note the different "Directory entry type".
Since you could (if you wanted to) use a T4 driver to connect to a local
database, the doc is saying that in that case you'd get better performance
from a T2 driver.
--
Larry Menard
IBM Workstation Database (DB2) Information Development, Samples Coordinator
Defender of Geese and of All Things Natural
"Raquel" <ra****************@yahoo.com> wrote in message
news:9a**************************@posting.google.c om...
Read this about the Universal JDBC Driver....
"In a Type 2 mode, the Universal JDBC driver provides local
application performance gains (because it avoids using TCP/IP protocol
to communicate to the DB2 server). "
Wht does it mean by "local" application performance? In type 2 mode,
it is a pre-requisite that all the databases that the application
running at the client need to be cataloged (through CCA or otherwise)
on the client; Most of the installations I have seen using TCPIP
'nodes' for cataloging (with CATALOG TCPIP NODE... command); so how
does the driver avoid using TCP/IP protocol?
TIA
Raquel.