Exporting Client Configuration Assistant definitions from one computer to another

[byrocat]

I've been building up a collection of DB2 database connections through
the Client Configuration Assistant.

What I've put together has become the "official list" of what we have,
and I need to export these so that the other people in the area can
pick up the list without having to go through the long manual process.

The Export feature does not export the whole set of information
(server, local name, comemnts, etc.) and selecting all the whole list
results in an empty file.

Has anyone had to do something similar and how did they get the
definitions out of the system and copied to other machines?

Thanks!

[Gert van der Kooij]

In article <11************ *********@z14g2 000cwz.googlegr oups.com>,
bd******@sympat ico.ca says...

I've been building up a collection of DB2 database connections through
the Client Configuration Assistant.

What I've put together has become the "official list" of what we have,
and I need to export these so that the other people in the area can
pick up the list without having to go through the long manual process.

The Export feature does not export the whole set of information
(server, local name, comemnts, etc.) and selecting all the whole list
results in an empty file.

Has anyone had to do something similar and how did they get the
definitions out of the system and copied to other machines?

Thanks!

I've used 'db2cfexp' and 'db2cfimp' from the command line without a
problem. I'm not sure it's available on every client.

[byrocat]

This is the same output as with Clinet Configuration Assistant export.

What I need is the mapping from the DBAlias (eg, BARNEY01) to the
actual database
mybarney.db2ins t.testdatabase (db2inst = 50791) to the acutal machine
information.

I can pull out the ODBC.INI and DB2CLI.INI files along with the
registry entries for LOCAL_MACHINE/..../ODBC.

What I can't find is the information that you see on the Properties
panel or when you go through the process of defining a new connection.

Thanks for the info so far...

[Gert van der Kooij]

In article <11************ **********@g44g 2000cwa.googleg roups.com>,
bd******@sympat ico.ca says...

This is the same output as with Clinet Configuration Assistant export.

What I need is the mapping from the DBAlias (eg, BARNEY01) to the
actual database
mybarney.db2ins t.testdatabase (db2inst = 50791) to the acutal machine
information.

I can pull out the ODBC.INI and DB2CLI.INI files along with the
registry entries for LOCAL_MACHINE/..../ODBC.

What I can't find is the information that you see on the Properties
panel or when you go through the process of defining a new connection.

Thanks for the info so far...

When using 'db2cfexp <your file> m' this info is exported to your file.
Did you try the 'm(aintain)' option?

[byrocat]

I figured out how to get the DB2 connection detail information.

Under the C:\Program Files\SQLLIB\DB 2 directoy are two subdirectories
SQLDBDIR and SQLNODIR. Copy them and all underlying files/directories
into a zip file.

Using regedit, export HKEY_LOCAL_MACH INE\SOFTWARE\OD BC into a file
and make copies of
ODBC.INI C:\Windows
DB2CLI.INI C:\Program Files\SQLLIB
If you copy them back into the appropriate directories on other system,
you're golden!

Considering that this is the thrid time that I've had to do this, I
have now created a document to cover everything.