What's the difference between using "catalog node" and catalog admin node"?
--
Chuck
Remove "_nospam" to reply by email

Catalog node allows to identify (catalog) any instance that is "remote"
from the one you are using.
catalog local node ...for another instance in the same OS
catalog tcpip node ... for anothe instance on another system which uses
tcpip

Catalog admin node is to catalog the DAS (Database Administration
Server) on the local or remote system.
catalog admin local node ....

Do: db2 ? catalog node .... on a command line to get the actual format
of the command for node
or
db2 catalog admin node ....

HTH, Pierre.

Chuck wrote:[color=blue]
> What's the difference between using "catalog node" and catalog admin node"?[/color]

--
Pierre Saint-Jacques - Reply to: sesconsjunk at attglobaljunk dot com
Reconstruct address: Remove the two junk and replace at and dot by
their symbols.
IBM DB2 Cerified Solutions Expert - Administration
SES Consultants Inc.

I don't know if it will help, but the links I use for
db2 q&a are:

1) The manuals (from
http://www.software.ibm.com/data/db2/library)

2) The Certification Guides

I've found other books on UDB to be very basic or
lacking in administration help.

I'd also suggest you subscribe to DB2EUG mailing list
(db2eug@herethey.com) where you'll get additional help.
More info is at
http://www2.herethey.com:8888/mailman/listinfo/db2eug

Finally you'll find more useful information on the IDUG
website (http://www.idug.org). Consider attending an
IDUG Conference to learn a lot and to build up a network
of contacts.

-----------------------------------------
Posted with NewsLeecher v1.0 beta 18
* State of the art usenet client
* http://www.newsleecher.com/
-----------------------------------------

So if I want to use the Control Center to be able to both look at
database objects, and make parameter changes to both an instance and a
database within that instance on a remote server, do I need to catalog
the node both ways?

I find that if I just catalog the node, and a database, I can look at
objects but not make parameter changes. If I catalog it as an "admin"
node I can make parameter changes but not look at db objects (or connect
to the db for that matter). Do I need to catalog a separate tcpip node
for each instance on the admin node?

Coming from an Oracle background and being used to the Oracle Enterprise
Manager, I'm finding configuring the Control Center a bit clunky.
--
Chuck Hamilton


Pierre Saint-Jacques <sescons@attglobal.net> wrote in
news:2U7qc.56038$1f2.431288@weber.videotron.net:
[color=blue]
> Catalog node allows to identify (catalog) any instance that is
> "remote" from the one you are using.
> catalog local node ...for another instance in the same OS
> catalog tcpip node ... for anothe instance on another system which
> uses tcpip
>
> Catalog admin node is to catalog the DAS (Database Administration
> Server) on the local or remote system.
> catalog admin local node ....
>
> Do: db2 ? catalog node .... on a command line to get the actual format
> of the command for node
> or
> db2 catalog admin node ....
>
> HTH, Pierre.
>
> Chuck wrote:[color=green]
>> What's the difference between using "catalog node" and catalog admin
>> node"?[/color]
>[/color]



--
Chuck
Remove "_nospam" to reply by email

The proper way, using the control center, is to catalog the admin node
and then to catalog each instance node and then each db within each
instance.

This way, you'll be able to make changes to admin cfg, dbm cfg od each
instance as well as db cfg for each db.

the process is:
1) db2 catalog admin tcpip node ....
2) db2 catalog tcpip node ..... repeat for each instance at that
admin node
3) db2 catalog db FOO at node ..... repeat for each db within each
instance at that node

Repeat for each independent server system you have in the network.

This work needs to be done from the workstation you use to access and
maintain each of those system. Typically that would be your
administration client wkstn.

HTH, Pierre.

Chuck wrote:
[color=blue]
> So if I want to use the Control Center to be able to both look at
> database objects, and make parameter changes to both an instance and a
> database within that instance on a remote server, do I need to catalog
> the node both ways?
>
> I find that if I just catalog the node, and a database, I can look at
> objects but not make parameter changes. If I catalog it as an "admin"
> node I can make parameter changes but not look at db objects (or connect
> to the db for that matter). Do I need to catalog a separate tcpip node
> for each instance on the admin node?
>
> Coming from an Oracle background and being used to the Oracle Enterprise
> Manager, I'm finding configuring the Control Center a bit clunky.
> --
> Chuck Hamilton
>
>
> Pierre Saint-Jacques <sescons@attglobal.net> wrote in
> news:2U7qc.56038$1f2.431288@weber.videotron.net:
>
>[color=green]
>>Catalog node allows to identify (catalog) any instance that is
>>"remote" from the one you are using.
>>catalog local node ...for another instance in the same OS
>>catalog tcpip node ... for anothe instance on another system which
>>uses tcpip
>>
>>Catalog admin node is to catalog the DAS (Database Administration
>>Server) on the local or remote system.
>>catalog admin local node ....
>>
>>Do: db2 ? catalog node .... on a command line to get the actual format
>>of the command for node
>>or
>>db2 catalog admin node ....
>>
>>HTH, Pierre.
>>
>>Chuck wrote:
>>[color=darkred]
>>>What's the difference between using "catalog node" and catalog admin
>>>node"?[/color]
>>[/color]
>
>
>[/color]

--
Pierre Saint-Jacques - Reply to: sesconsjunk at attglobaljunk dot com
Reconstruct address: Remove the two junk and replace at and dot by
their symbols.
IBM DB2 Cerified Solutions Expert - Administration
SES Consultants Inc.

Chuck wrote:
[color=blue]
> So if I want to use the Control Center to be able to both look at
> database objects, and make parameter changes to both an instance and a
> database within that instance on a remote server, do I need to catalog
> the node both ways?
>
> I find that if I just catalog the node, and a database, I can look at
> objects but not make parameter changes. If I catalog it as an "admin"
> node I can make parameter changes but not look at db objects (or connect
> to the db for that matter). Do I need to catalog a separate tcpip node
> for each instance on the admin node?[/color]

You need to do both. Cataloging something an admin node defines the
connection to port 523 (where the DB2 admin server listens). You'll
notice with the admin node that you can't specify the port number,
unlike a DB2 instance (catalog tcpip node).
[color=blue]
> Coming from an Oracle background and being used to the Oracle Enterprise
> Manager, I'm finding configuring the Control Center a bit clunky.[/color]

It's also possible to add everything through Control Center. It will take
care of cataloging everything for you, just right click to add new systems,
instances, databases.


Good luck,





-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----

Ian <ianbjor@mobileaudio.com> wrote in
news:40a96481$1_1@corp.newsgroups.com:
[color=blue]
>
> It's also possible to add everything through Control Center. It will
> take care of cataloging everything for you, just right click to add
> new systems, instances, databases.
>
>
> Good luck,[/color]

I think my initial problem was in figuring out that you need to catalog
the node multiple times. Once for the admin server and once for each
instance. Once I realized that (and I didn't find it spelled out anywhere
in the docs) things started moving a lot smoother. Maybe I need to search
for a db2 client or command center concepts guide and go through it.
--
Chuck
Remove "_nospam" to reply by email