By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,836 Members | 1,735 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,836 IT Pros & Developers. It's quick & easy.

URGENT: Problème avec CREATE SERVER

P: n/a
jab
Je veux lier (join) une table qui se trouve dans une database avec une
qui se trouve dans une autre database. Les 2 databases sont sur le
même serveur en l'occurence DB2/NT 7.2.9. J'ai créé un wrapper avec le
control center (j'ai utilisé DRDA) et ensuite j'ai voulu créé le
serveur mais avec le wizard, il ne me présente pas mes tables !

J'ai donc essayé en ligne de commande. J'ai essayé la commande
suivante:

CREATE SERVER TEST TYPE DB2/NT VERSION 7.2.9 WRAPPER DRDA OPTIONS
(NODE 'DB2DEV1', DBNAME 'DCMI')

et je reçois:

DB21034E The command was processed as an SQL statement because it was
not a valid Command Line Processor command. During SQL processing it
returned: SQL0901N The SQL statement failed because of a non-severe
system error. Subsequent SQL statements can be processed. (Reason
"Invalid Request type for DB2 Admin Server".)

si j'essaie ce qui me semble être la bonne solution:

CREATE SERVER TEST TYPE DB2/NT VERSION 7.2.9 WRAPPER DRDA OPTIONS
(NODE 'DEVGC', DBNAME 'DCMI')

je reçois:

DB21034E The command was processed as an SQL statement because it was
not a valid Command Line Processor command. During SQL processing it
returned: SQL1019N The node name "DEVGC" specified in the command is
not valid.

En somme je ne sais pas quoi mettre comme NODE. Si je ne met pas de
NODE, je reçois un message m'indiquant que pour ce type de serveur, il
est requis.

L'arboressence sur mon serveur est (vu depuis le controle center):

Systems
|
--DB2DEV1
| |
| -- Instances
| |
| +--DEVXX
| |
| --DEVGC
| |
| --Databases
| |
| -- DPER
| |
| -- DCMI
| |
| -- DXXX
|
+-- DEVPROD1

Je veux lier table1 qui est dans dper avec table2 qui est dans dcmi.

Comment faire ?

pour infos:

La commande

LIST ADMIN NODE DIRECTORY SHOW DETAIL

retourne (extrait)

Node 2 entry:

Node name = DB2DEV1

Comment =

Protocol = TCPIP

Hostname = db2dev1

Service name = 523

Remote instance name = DB2DAS00

System = DB2DEV1

Operating system type = NT
La commande

LIST NODE DIRECTORY

retourne (extrait)

Node 13 entry:

Node name = DEVGC

Comment =

Protocol = TCPIP

Hostname = db2dev1

Service name = 50014

Merci pour votre aide car je suis bloqué par ce problème et le projet
est urgent. J'ai déjà posté ce message sur un autre forum mais sans
résultat.
Nov 12 '05 #1
Share this Question
Share on Google+
9 Replies


P: n/a
Bonjour la Belgique je crois!! (teledisnet.be)les réponses vous
viendront plus vite en expliquant le problème en anglais, mais je
comprends aussi venant de Montréal.
Enfin. Il semble que vous tentiez de d'identifier le NODE en utilisant
le nom (DEVGC) de l'instance. Il faudrait d'abord créer un LOACL NODE
pour cetee instance et ultiliser celui-ci dans la commande CREATE SERVER.

db2 catalog local node DEVGCNOD instance DEVGC

Ensuite votre commande:
CREATE SERVER TEST TYPE DB2/NT VERSION 7.2.9 WRAPPER DRDA OPTIONS
(NODE 'DEVGC', DBNAME 'DCMI')
devrait fonctionner.

Bonne chance et laissez-moi savoir!! Pierre

jab wrote:
Je veux lier (join) une table qui se trouve dans une database avec une
qui se trouve dans une autre database. Les 2 databases sont sur le
même serveur en l'occurence DB2/NT 7.2.9. J'ai créé un wrapper avec le
control center (j'ai utilisé DRDA) et ensuite j'ai voulu créé le
serveur mais avec le wizard, il ne me présente pas mes tables !

J'ai donc essayé en ligne de commande. J'ai essayé la commande
suivante:

CREATE SERVER TEST TYPE DB2/NT VERSION 7.2.9 WRAPPER DRDA OPTIONS
(NODE 'DB2DEV1', DBNAME 'DCMI')

et je reçois:

DB21034E The command was processed as an SQL statement because it was
not a valid Command Line Processor command. During SQL processing it
returned: SQL0901N The SQL statement failed because of a non-severe
system error. Subsequent SQL statements can be processed. (Reason
"Invalid Request type for DB2 Admin Server".)

si j'essaie ce qui me semble être la bonne solution:

CREATE SERVER TEST TYPE DB2/NT VERSION 7.2.9 WRAPPER DRDA OPTIONS
(NODE 'DEVGC', DBNAME 'DCMI')

je reçois:

DB21034E The command was processed as an SQL statement because it was
not a valid Command Line Processor command. During SQL processing it
returned: SQL1019N The node name "DEVGC" specified in the command is
not valid.

En somme je ne sais pas quoi mettre comme NODE. Si je ne met pas de
NODE, je reçois un message m'indiquant que pour ce type de serveur, il
est requis.

L'arboressence sur mon serveur est (vu depuis le controle center):

Systems
|
--DB2DEV1
| |
| -- Instances
| |
| +--DEVXX
| |
| --DEVGC
| |
| --Databases
| |
| -- DPER
| |
| -- DCMI
| |
| -- DXXX
|
+-- DEVPROD1

Je veux lier table1 qui est dans dper avec table2 qui est dans dcmi.

Comment faire ?

pour infos:

La commande

LIST ADMIN NODE DIRECTORY SHOW DETAIL

retourne (extrait)

Node 2 entry:

Node name = DB2DEV1

Comment =

Protocol = TCPIP

Hostname = db2dev1

Service name = 523

Remote instance name = DB2DAS00

System = DB2DEV1

Operating system type = NT
La commande

LIST NODE DIRECTORY

retourne (extrait)

Node 13 entry:

Node name = DEVGC

Comment =

Protocol = TCPIP

Hostname = db2dev1

Service name = 50014

Merci pour votre aide car je suis bloqué par ce problème et le projet
est urgent. J'ai déjà posté ce message sur un autre forum mais sans
résultat.


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

Nov 12 '05 #2

P: n/a
jab
This is the same message but in english.

I want to link (join) a table with another who is in an other
database. The two databases are on the same server (a DB2/NT 7.2.9
server). I've create a wrapper (DRDA) with the control center and
after, I would create a server but with the wizard, I cannot see my
databases. I try it also with command center:
CREATE SERVER TEST TYPE DB2/NT VERSION 7.2.9 WRAPPER DRDA OPTIONS
(NODE 'DB2DEV1', DBNAME 'DCMI')
and I receive:
DB21034E The command was processed as an SQL statement because it was
not a valid Command Line Processor command. During SQL processing it
returned: SQL0901N The SQL statement failed because of a non-severe
system error. Subsequent SQL statements can be processed. (Reason
"Invalid Request type for DB2 Admin Server".) If I try: CREATE SERVER TEST TYPE DB2/NT VERSION 7.2.9 WRAPPER DRDA OPTIONS
(NODE 'DEVGC', DBNAME 'DCMI') I receive: DB21034E The command was processed as an SQL statement because it was
not a valid Command Line Processor command. During SQL processing it
returned: SQL1019N The node name "DEVGC" specified in the command is
not valid.
What is the problem ?

Directory on my server is (view from controle center):
Systems
|
--DB2DEV1
| |
| -- Instances
| |
| +--DEVXX
| |
| --DEVGC
| |
| --Databases
| |
| -- DPER
| |
| -- DCMI
| |
| -- DXXX
|
+-- DEVPROD1

I want to join table1 on DPER database with table2 on DCMI database.

How can I do this ?

for informations:

The sentence:
LIST ADMIN NODE DIRECTORY SHOW DETAIL
return (partial listing) :
Node 2 entry:

Node name = DB2DEV1

Comment =

Protocol = TCPIP

Hostname = db2dev1

Service name = 523

Remote instance name = DB2DAS00

System = DB2DEV1

Operating system type = NT
The sentence
LIST NODE DIRECTORY
return (partial listing)
Node 13 entry:

Node name = DEVGC

Comment =

Protocol = TCPIP

Hostname = db2dev1

Service name = 50014


Thanks for your help.
Nov 12 '05 #3

P: n/a
jab
I try to catalogue node devgc2 as tcpip node and catalog database on
it but it's de same.
Nov 12 '05 #4

P: n/a
jab
I try this but it's always the same. No problem to catalog DEVGCNOD
but after I receive always the same message. I try with DEVGC and
DEVGCNOD as Node. Sorry for delay but at work I have no access
directly to news, I must do it via Google or at home.

PS: J'ai reformulé en Anglais et je vais continuer ainsi. J'étais un
peu distrait car je venais d'un forum en français.
Nov 12 '05 #5

P: n/a
Interesting! Can you copy the output of:
db2 list node directory
and
db2 list db directory

Could be DB2 is playing games (heaven forbid!) in cataloguing the
node(s) and/or db's.
Bonjour, Pierre.

jab wrote:
I try this but it's always the same. No problem to catalog DEVGCNOD
but after I receive always the same message. I try with DEVGC and
DEVGCNOD as Node. Sorry for delay but at work I have no access
directly to news, I must do it via Google or at home.

PS: J'ai reformulé en Anglais et je vais continuer ainsi. J'étais un
peu distrait car je venais d'un forum en français.


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

Nov 12 '05 #6

P: n/a
Bonjour,

Il faut créer un autre nom pour l'instance DEVGC, i.e DEVGCNOD et référencer
la base DCMI dans ce node:
CATALOG DB DCMI AS DCMI2 AT NODE DEVGCNOD

Puis faire un:
CREATE SERVER TEST TYPE DB2/NT VERSION 7.2.9 WRAPPER DRDA OPTIONS
(NODE 'DEVGCNOD', DBNAME 'DCMI2')

Cela devrait fonctionner. Le Federated impose 2 nodes en V7, ce qui n'est
plus le cas en V8.

Cordialement,

JM Blaise

"Pierre Saint-Jacques" <se*****@attglobal.net> a écrit dans le message de
news:40**************@attglobal.net...
Bonjour la Belgique je crois!! (teledisnet.be)les réponses vous
viendront plus vite en expliquant le problème en anglais, mais je
comprends aussi venant de Montréal.
Enfin. Il semble que vous tentiez de d'identifier le NODE en utilisant
le nom (DEVGC) de l'instance. Il faudrait d'abord créer un LOACL NODE
pour cetee instance et ultiliser celui-ci dans la commande CREATE SERVER.

db2 catalog local node DEVGCNOD instance DEVGC

Ensuite votre commande:
CREATE SERVER TEST TYPE DB2/NT VERSION 7.2.9 WRAPPER DRDA OPTIONS
> (NODE 'DEVGC', DBNAME 'DCMI')


devrait fonctionner.

Bonne chance et laissez-moi savoir!! Pierre

jab wrote:
Je veux lier (join) une table qui se trouve dans une database avec une
qui se trouve dans une autre database. Les 2 databases sont sur le
même serveur en l'occurence DB2/NT 7.2.9. J'ai créé un wrapper avec le
control center (j'ai utilisé DRDA) et ensuite j'ai voulu créé le
serveur mais avec le wizard, il ne me présente pas mes tables !

J'ai donc essayé en ligne de commande. J'ai essayé la commande
suivante:

CREATE SERVER TEST TYPE DB2/NT VERSION 7.2.9 WRAPPER DRDA OPTIONS
(NODE 'DB2DEV1', DBNAME 'DCMI')

et je reçois:

DB21034E The command was processed as an SQL statement because it was
not a valid Command Line Processor command. During SQL processing it
returned: SQL0901N The SQL statement failed because of a non-severe
system error. Subsequent SQL statements can be processed. (Reason
"Invalid Request type for DB2 Admin Server".)

si j'essaie ce qui me semble être la bonne solution:

CREATE SERVER TEST TYPE DB2/NT VERSION 7.2.9 WRAPPER DRDA OPTIONS
(NODE 'DEVGC', DBNAME 'DCMI')

je reçois:

DB21034E The command was processed as an SQL statement because it was
not a valid Command Line Processor command. During SQL processing it
returned: SQL1019N The node name "DEVGC" specified in the command is
not valid.

En somme je ne sais pas quoi mettre comme NODE. Si je ne met pas de
NODE, je reçois un message m'indiquant que pour ce type de serveur, il
est requis.

L'arboressence sur mon serveur est (vu depuis le controle center):

Systems
|
--DB2DEV1
| |
| -- Instances
| |
| +--DEVXX
| |
| --DEVGC
| |
| --Databases
| |
| -- DPER
| |
| -- DCMI
| |
| -- DXXX
|
+-- DEVPROD1

Je veux lier table1 qui est dans dper avec table2 qui est dans dcmi.

Comment faire ?

pour infos:

La commande

LIST ADMIN NODE DIRECTORY SHOW DETAIL

retourne (extrait)

Node 2 entry:

Node name = DB2DEV1

Comment =

Protocol = TCPIP

Hostname = db2dev1

Service name = 523

Remote instance name = DB2DAS00

System = DB2DEV1

Operating system type = NT
La commande

LIST NODE DIRECTORY

retourne (extrait)

Node 13 entry:

Node name = DEVGC

Comment =

Protocol = TCPIP

Hostname = db2dev1

Service name = 50014

Merci pour votre aide car je suis bloqué par ce problème et le projet
est urgent. J'ai déjà posté ce message sur un autre forum mais sans
résultat.


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

Nov 12 '05 #7

P: n/a
Merci pour cet "éclairement". J'avais toujours mal compris cette
mécanique dans V7.x
Salut, Pierre.

Jean-Marc Blaise wrote:
Bonjour,

Il faut créer un autre nom pour l'instance DEVGC, i.e DEVGCNOD et référencer
la base DCMI dans ce node:
CATALOG DB DCMI AS DCMI2 AT NODE DEVGCNOD

Puis faire un:
CREATE SERVER TEST TYPE DB2/NT VERSION 7.2.9 WRAPPER DRDA OPTIONS
(NODE 'DEVGCNOD', DBNAME 'DCMI2')

Cela devrait fonctionner. Le Federated impose 2 nodes en V7, ce qui n'est
plus le cas en V8.

Cordialement,

JM Blaise

"Pierre Saint-Jacques" <se*****@attglobal.net> a écrit dans le message de
news:40**************@attglobal.net...
Bonjour la Belgique je crois!! (teledisnet.be)les réponses vous
viendront plus vite en expliquant le problème en anglais, mais je
comprends aussi venant de Montréal.
Enfin. Il semble que vous tentiez de d'identifier le NODE en utilisant
le nom (DEVGC) de l'instance. Il faudrait d'abord créer un LOACL NODE
pour cetee instance et ultiliser celui-ci dans la commande CREATE SERVER.

db2 catalog local node DEVGCNOD instance DEVGC

Ensuite votre commande:
CREATE SERVER TEST TYPE DB2/NT VERSION 7.2.9 WRAPPER DRDA OPTIONS
> (NODE 'DEVGC', DBNAME 'DCMI')


devrait fonctionner.

Bonne chance et laissez-moi savoir!! Pierre

jab wrote:

Je veux lier (join) une table qui se trouve dans une database avec une
qui se trouve dans une autre database. Les 2 databases sont sur le
même serveur en l'occurence DB2/NT 7.2.9. J'ai créé un wrapper avec le
control center (j'ai utilisé DRDA) et ensuite j'ai voulu créé le
serveur mais avec le wizard, il ne me présente pas mes tables !

J'ai donc essayé en ligne de commande. J'ai essayé la commande
suivante:

CREATE SERVER TEST TYPE DB2/NT VERSION 7.2.9 WRAPPER DRDA OPTIONS
(NODE 'DB2DEV1', DBNAME 'DCMI')

et je reçois:

DB21034E The command was processed as an SQL statement because it was
not a valid Command Line Processor command. During SQL processing it
returned: SQL0901N The SQL statement failed because of a non-severe
system error. Subsequent SQL statements can be processed. (Reason
"Invalid Request type for DB2 Admin Server".)

si j'essaie ce qui me semble être la bonne solution:

CREATE SERVER TEST TYPE DB2/NT VERSION 7.2.9 WRAPPER DRDA OPTIONS
(NODE 'DEVGC', DBNAME 'DCMI')

je reçois:

DB21034E The command was processed as an SQL statement because it was
not a valid Command Line Processor command. During SQL processing it
returned: SQL1019N The node name "DEVGC" specified in the command is
not valid.

En somme je ne sais pas quoi mettre comme NODE. Si je ne met pas de
NODE, je reçois un message m'indiquant que pour ce type de serveur, il
est requis.

L'arboressence sur mon serveur est (vu depuis le controle center):

Systems
|
--DB2DEV1
| |
| -- Instances
| |
| +--DEVXX
| |
| --DEVGC
| |
| --Databases
| |
| -- DPER
| |
| -- DCMI
| |
| -- DXXX
|
+-- DEVPROD1

Je veux lier table1 qui est dans dper avec table2 qui est dans dcmi.

Comment faire ?

pour infos:

La commande

LIST ADMIN NODE DIRECTORY SHOW DETAIL

retourne (extrait)

Node 2 entry:

Node name = DB2DEV1

Comment =

Protocol = TCPIP

Hostname = db2dev1

Service name = 523

Remote instance name = DB2DAS00

System = DB2DEV1

Operating system type = NT
La commande

LIST NODE DIRECTORY

retourne (extrait)

Node 13 entry:

Node name = DEVGC

Comment =

Protocol = TCPIP

Hostname = db2dev1

Service name = 50014

Merci pour votre aide car je suis bloqué par ce problème et le projet
est urgent. J'ai déjà posté ce message sur un autre forum mais sans
résultat.


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



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

Nov 12 '05 #8

P: n/a
jab
Rien n'y fait, pas moyen de créer cet objet.
J' ai donc fait:

catalog local node devgcnod instance devgc
catalog db dcmi as dcmi2 at node devgcnod
create server test type db2/nt version 7.2.9 wrapper drda options
(node 'devgcnod', dbname 'dcmi2')

la réponse de db2 est:
DB21034E The command was processed as an SQL statement because it was
not a valid Command Line Processor command. During SQL processing it
returned: SQL1019N The node name "devgcnod" specified in the command
is not valid.

------------------------------------------------------------------------------
list node directory

(je ne suis concerné que par devgc sur db2dev1.)

Node Directory
Number of entries in the directory = 15
Node 1 entry:
Node name = DB2DEV01
Comment =
Protocol = TCPIP
Hostname = db2dev1
Service name = 50010
Node 2 entry:
Node name = DB2PRD02
Comment =
Protocol = TCPIP
Hostname = db2prd1
Service name = 50016
Node 3 entry:
Node name = DB2PRD03
Comment =
Protocol = TCPIP
Hostname = db2prd1
Service name = 50006
Node 4 entry:
Node name = DB2PRD05
Comment =
Protocol = TCPIP
Hostname = db2prd1
Service name = 50018
Node 5 entry:
Node name = DB2PRD06
Comment =
Protocol = TCPIP
Hostname = db2prd1
Service name = 50020
Node 6 entry:
Node name = DB2PRD07
Comment =
Protocol = TCPIP
Hostname = db2prd1
Service name = 50022
Node 7 entry:
Node name = DB2PRD08
Comment =
Protocol = TCPIP
Hostname = db2prd1
Service name = 50012
Node 8 entry:
Node name = DB2PRD09
Comment =
Protocol = TCPIP
Hostname = db2prd1
Service name = 50014
Node 9 entry:
Node name = DB2VAL01
Comment =
Protocol = TCPIP
Hostname = db2val1
Service name = 50018
Node 10 entry:
Node name = DB2VAL02
Comment =
Protocol = TCPIP
Hostname = db2val1
Service name = 50012
Node 11 entry:
Node name = DB2VAL03
Comment =
Protocol = TCPIP
Hostname = db2val1
Service name = 50020
Node 12 entry:
Node name = DB2VAL04
Comment =
Protocol = TCPIP
Hostname = db2val1
Service name = 50016
Node 13 entry:
Node name = DEVGC
Comment =
Protocol = TCPIP
Hostname = db2dev1
Service name = 50014
Node 14 entry:
Node name = DEVGCNOD
Comment =
Protocol = LOCAL
Instance name = DEVGC
Node 15 entry:
Node name = LOCAL
Comment =
Protocol = LOCAL
Instance name = oltp
----------------------------------------------------------------------
list db directory

System Database Directory
Number of entries in the directory = 49
Database 1 entry:
Database alias = VSZV
Database name = VSZV
Node name = DB2VAL01
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 2 entry:
Database alias = PNOVIS2
Database name = PNOVIS2
Node name = DB2PRD08
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 3 entry:
Database alias = VSPECREF
Database name = VSPECREF
Node name = DB2VAL01
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 4 entry:
Database alias = PREFUND
Database name = PREFUND
Node name = DB2PRD05
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 5 entry:
Database alias = IJU
Database name = PIJU
Node name = DB2PRD07
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 6 entry:
Database alias = DSIT
Database name = DSIT
Node name = DEVGC
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 7 entry:
Database alias = VNOVIS2
Database name = VNOVIS2
Node name = DB2VAL02
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 8 entry:
Database alias = PNIP
Database name = PNIP
Node name = DB2PRD09
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 9 entry:
Database alias = PCORDOS
Database name = PCORDOS
Node name = DB2PRD08
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 10 entry:
Database alias = VREFUND
Database name = VREFUND
Node name = DB2VAL01
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 11 entry:
Database alias = CTX
Database name = PCTX
Node name = DB2PRD02
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 12 entry:
Database alias = POZB
Database name = POZB
Node name = DB2PRD02
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 13 entry:
Database alias = DSNV
Database name = DSNV
Node name = DB2DEV01
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 14 entry:
Database alias = DPER2
Database name = DPER
Node name = DEVGCNOD
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 15 entry:
Database alias = DCDH
Database name = DCDH
Node name = DEVGC
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 16 entry:
Database alias = VCORDOS
Database name = VCORDOS
Node name = DB2VAL02
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 17 entry:
Database alias = VOZB
Database name = VOZB
Node name = DB2VAL04
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 18 entry:
Database alias = PDEMAND
Database name = PDEMAND
Node name = DB2PRD05
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 19 entry:
Database alias = PATTEST
Database name = PATTEST
Node name = DB2PRD08
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 20 entry:
Database alias = FFD
Database name = PFFD
Node name = DB2PRD02
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 21 entry:
Database alias = SRV
Database name = PSRV
Node name = DB2PRD06
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 22 entry:
Database alias = PSNV
Database name = PSNV
Node name = DB2PRD05
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 23 entry:
Database alias = SQLLIVES
Database name = SQLLIVES
Node name = DB2PRD03
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 24 entry:
Database alias = PBSFV2
Database name = PBSFV2
Node name = DB2PRD05
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 25 entry:
Database alias = VDEMAND
Database name = VDEMAND
Node name = DB2VAL01
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 26 entry:
Database alias = DBPROD22
Database name = DBPROD22
Node name = DB2PRD03
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 27 entry:
Database alias = PELFC
Database name = PELFC
Node name = DB2PRD05
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 28 entry:
Database alias = VATTEST
Database name = VATTEST
Node name = DB2VAL02
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 29 entry:
Database alias = IEG
Database name = PIEG
Node name = DB2PRD07
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 30 entry:
Database alias = PSRV
Database name = PSRV
Node name = DB2PRD06
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 31 entry:
Database alias = IBK
Database name = PIBK
Node name = DB2PRD07
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 32 entry:
Database alias = VSNV
Database name = VSNV
Node name = DB2VAL01
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 33 entry:
Database alias = IJD
Database name = PIJD
Node name = DB2PRD07
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 34 entry:
Database alias = VBSFV2
Database name = VBSFV2
Node name = DB2VAL01
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 35 entry:
Database alias = DMCO
Database name = DMCO
Node name = DEVGC
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 36 entry:
Database alias = CMI
Database name = DCMI
Node name = DEVGC
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 37 entry:
Database alias = SQLTEST
Database name = SQLTEST
Node name = DB2PRD03
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 38 entry:
Database alias = VELFC
Database name = VELFC
Node name = DB2VAL01
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 39 entry:
Database alias = LCMI
Database name = DCMI
Node name = DEVGC2
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 40 entry:
Database alias = VSRV
Database name = VSRV
Node name = DB2VAL03
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 41 entry:
Database alias = BSF
Database name = PBSF
Node name = DB2PRD05
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 42 entry:
Database alias = VEFF
Database name = VEFF
Node name = DB2VAL02
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 43 entry:
Database alias = PSZV
Database name = PSZV
Node name = DB2PRD05
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 44 entry:
Database alias = SQLDOCC
Database name = SQLDOCC
Node name = DB2PRD03
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 45 entry:
Database alias = DNIP
Database name = DNIP
Node name = DEVGC
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 46 entry:
Database alias = FJP
Database name = PFJP
Node name = DB2PRD02
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 47 entry:
Database alias = DPER
Database name = DPER
Node name = DEVGC
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 48 entry:
Database alias = PSPECREF
Database name = PSPECREF
Node name = DB2PRD05
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Database 49 entry:
Database alias = HVD
Database name = PHVD
Node name = DB2PRD07
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1
Merci de votre aide.
Nov 12 '05 #9

P: n/a
jab
En fait, à la fin, j'ai légèrement changé, je fais le lien de DCMI vers
DPER et non plus comme précédemment de DPER vers DCMI. J'ai donc fait
catalog local node devgcnod instance devgc
catalog db DPER as DPER2 at node devgcnod
create server test type db2/nt version 7.2.9 wrapper drda options
(node 'devgcnod', dbname 'DPER2')


Ce qui explique la présence de DPER2 dans la liste précédente et non de
DCMI2 comme annoncé au début.
Nov 12 '05 #10

This discussion thread is closed

Replies have been disabled for this discussion.