Query the trkprj in the trkmaster db, make sure this project db name (prjDbName) is exactly same as in sysdatabases. In Control Panel | ODBC, check User DSN (and System DSN if running INET), make sure Tracker SQL Server ODBC driver configuration does not contain any entries for Server and Database. This should fix the error.
b) Verify the ChangeMan STC JCL has the parm 'XML=YES'. c) Verify XML job SER#PARM DSN references the same IP address and port# used by the ChangeMan STC. d) Verify client LPAR has IP connectivity to ChangeMan STC LPAR.
Open the ODBC datasource screen in Windows which is usually in the Administrative Tools area Go to the System DSN tab and just verify that your new ODBC connection is using the driver called "ODBC Driver 11 for SQL Server" If it's not using that driver you can manually create one on that screen and select the driver then open configurator and point to the new ODBC Connection.
Run the following SQL to create a UNIX/Linux shell script that confirms the existence of the appropriate file in the item library: sqlplus <basedb>/<password>@< dsn > SQL> set heading off
$ cat dm.sh dmcli -user dmsys -pass dmsys -host stal-al-sun3:671 -dbname intermediate - dsn ora9 -cmd exit The login information needs to be modified to reflect your system settings.
