DataStage and IBM's Universe Database

ewartpm · Post by **ewartpm** » Sat May 24, 2003 9:29 am

This message is related to the one Hendrik Kotze posted earlier. When one makes an entry in the uvodbc.config file (when there are co-resident universe databases on the server running under Windows 2000), how does DataStage/Universe know which database to access.For example:

[ODBC DATA SOURCES]

DBMSTYPE = UNIVERSE
network = LAN
service = uvserver
host = localhost

DBMSTYPE = UNIVERSE
network = TCP/IP
service = uvserver
host = cfs-mark

The only difference is the host name. However, in this case, they are the same server. In DataStage, when one tries to import a Universe account using 'Universe Tables' instead of ODBC, DataStage defaults to the accounts in localuv and seems to ignore the 'account' entry one is prompted for.

Accessing a remote Universe database (10.0.4) with DataStage 6.0
If one uses the uvodbc.config route, is it necessary to create any other entries in DataStage or Universe e.g Does one have to make an entry in the UV.ACCOUNTS file in DataStage UV? Does some entry have to exist in UVNET II? Also, what role does the HOSTS file play in all this?

Any help would be much appreciated. IBM have acknowledged they have connection problems in Universe ver 10.0.4, but have not been specific enough for us to discount the problem and force a Universe upgrade to the next version.

Thanks

ray.wurlod · Post by **ray.wurlod** » Sun May 25, 2003 1:13 am

DataStage does not need to differentiate. The DBMSTYPE field in uvodbc.config is either UNIVERSE or ODBC, meaning "UniVerse-style" or "ODBC-style". A UniVerse-style connection uses the BASIC SQL client interface (BCI) to send SQL functions to the UniVerse Call Interface on the UniVerse/DataStage server, bypassing the need to use an ODBC driver. An ODBC-style connection uses the BCI to send SQL functions to an ODBC driver through the ODBC driver manager on the DataStage machine.
UV/Net recognizes entries of the form host!pathname in UV.ACCOUNT (or in F pointers in VOC files); no other configuration of UV/Net is needed. However, if a name is used for the remote host, that name has to be able to be resolved successfully on the local UniVerse machine (for example, an entry must exist in the %WINNT_ROOT%System32driversetchosts file).
I vaguely recall that there is something in the DS 6.0 readme file about this issue, but I don't have access to one as I'm typing this.

Ray Wurlod
Education and Consulting Services
ABN 57 092 448 518