============================================================================== Tivoli Storage Manager (TSM) for Windows ODBC Driver README.ODBC.TXT Version 5 Release 2, Level 2.0 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2003. All rights reserved. ============================================================================== This Readme is divided into the following sections: What's New Software Requirements Installing the ODBC Driver Uninstalling the ODBC Driver Supported ODBC Applications Supported ODBC Functions Defining Data Sources Known Problems and Limitations Troubleshooting/Diagnostics ODBC Driver Configuration Details TSM ODBC Driver Tracing APARs Fixed in this Release Other Defects Fixed in this Release Trademarks ---------- What's New ---------- - See the following sections in this README file for information on additional changes: - APARs Fixed in this Release - Other Defects Fixed in this Release --------------------- Software Requirements --------------------- The TSM ODBC driver is supported on the following Microsoft operating systems: - Windows 2000 - Windows XP - Windows 2003 -------------------------- Installing the ODBC Driver -------------------------- The TSM ODBC driver package on the FTP site is an executable file. When this file is executed, the install image will be extracted, then the setup program will start. If you are installing the TSM ODBC driver from the CD-ROM, setup.exe is in directory x:\deskCD\tsmcli\win32\odbc\disk1 where x: drive letter that corresponds to your CD-ROM drive. To start the install, run setup.exe. To run a silent install, run setup.exe as follows: setup /s /v/qn ---------------------------- Uninstalling the ODBC Driver ---------------------------- 1. Stop any running applications that are using the TSM ODBC Driver. 2. From the Administrative Tools folder, start the ODBC Data Sources Administrator. Alternatively, you can run program odbcad32.exe. 3. From the "User DSN" tab, remove all DSNs associated with the TSM ODBC Driver. Repeat from the "System DSN" and "File DSN" tabs. 4. From the Control Panel, double-click on "Add/Remove Programs". 5. On the left side of the "Add/Remove Programs" dialog, click on "Change or Remove Programs" (if it is not already selected). 6. Locate "Tivoli Storage Manager ODBC Driver" in the list of currently installed programs. Select "Tivoli Storage Manager ODBC Driver", then click on "Remove". Follow the prompts to remove the ODBC Driver. 7. The Microsoft Software Installer will not remove any files that it did not install. Therefore you may manually need to delete any remaining files in the ..\tsm\odbc directory, and then remove the ..\tsm\odbc directory itself. The TSM ODBC Driver is now removed from your system. --------------------------- Supported ODBC Applications --------------------------- The TSM ODBC driver is supported with any ODBC application, within the constraints specified in the "Supported ODBC Functions" and "Known Problems and Limitations" sections of this README file. It should be noted that resolution of problems occurring due to limitations or defects in the ODBC application is the responsibility of that application's vendor. ------------------------ Supported ODBC Functions ------------------------ The following ODBC 3.x functions are implemented in the TSM ODBC driver: - SQLAllocHandle - SQLBindCol - SQLBindParameter - SQLCancel - SQLCloseCursor - SQLColAttribute - SQLColumns - SQLConnect - SQLDescribeCol - SQLDisconnect - SQLDriverConnect - SQLExecDirect - SQLExecute - SQLFetch - SQLFreeHandle - SQLFreeStmt - SQLGetConnectAttr - SQLGetCursorName - SQLGetData - SQLGetDiagRec - SQLGetEnvAttr - SQLGetFunctions - SQLGetInfo - SQLGetStmtAttr - SQLGetTypeInfo - SQLNumParams - SQLNumResultCols - SQLPrepare - SQLPrimaryKeys - SQLRowCount - SQLSetConnectAttr - SQLSetCursorName - SQLSetEnvAttr - SQLSetStmtAttr - SQLSpecialColumns - SQLStatistics - SQLTables The ODBC 3.x specification can be found in the Microsoft Developer Network (MSDN) library. At the time of this writing, the URL is: http://msdn.microsoft.com/library/default.asp From there, navigate to the ODBC specification via these links (in order): - Data Access - Reference - Microsoft Open Database Connectivity (ODBC) - ODBC Programmer's Reference --------------------- Defining Data Sources --------------------- The ODBC Data Source Administrator in the Control Panel can be used to add, remove, and configure data source entries. ODBC applications can then be used to connect to the TSM server. Note for 64-bit Windows XP and 2003 users: The TSM ODBC driver is only available in a 32-bit version. Therefore you must use the 32-bit version of the ODBC Data Source Administrator (odbcad32.exe) to configure TSM ODBC driver DSNs. This executable is located in directory x:\WINDOWS\SysWOW64, where x: is the drive letter where Windows is installed (usually C:). The TSM ODBC setup program will create a default user data source name (DSN) called "TSM ODBC Sample User DSN". You can either update this entry, or remove it and create one or more new DSNs to connect to your TSM Server(s). When creating new DSNs, the driver name to use is "TSM ODBC Driver". The ODBC data source setup panel for TSM has the following controls: - Data source name: (REQUIRED) Specify the name you wish to use for the DSN. This is the name that will appear in the "Name" column when you run the ODBC Data Source Administrator. The maximum allowed length is 255 characters. - Description: (OPTIONAL) This is a free-form text field where you may enter a comment or description about this DSN. The maximum allowed length is 255 characters. - Language: (REQUIRED) Select the language in which ANSxxxxx messages should be displayed. The available languages are those that were selected at the time the ODBC driver was installed. Note: Only the ANSxxxxx messages are available in other languages. The ODBC driver dialogs and other non-ANSxxxxx text strings are currently displayed in English only. - Administrator name: (OPTIONAL) Specify the the TSM Administrator ID to use with this DSN. - Fetch size: (REQUIRED) Specify the number of records that the ODBC driver requests from the TSM server per fetch request. Larger values may improve performance, especially when fetching a large number of records. This value must be between 1 and 1000000 (inclusive). The default value is 50. - TCP/IP address: (REQUIRED) Specify the TCP/IP address of the TSM server you are connecting to. If you do not know which address to use, see your TSM administrator. - TCP/IP port: (REQUIRED) Specify the TCP/IP port number of the TSM server you are connecting to. If you do not know which port number to use, see your TSM administrator. - Enable trace: (OPTIONAL) Checking this box activates TSM ODBC driver tracing. Unchecking this box deactivates tracing. Normally this box should remain unchecked. Tracing should only be performed at the request of TSM Service or Development. - Trace file name: (OPTIONAL) This field is available only when "Enable trace" has been checked. Here you can specify a fully-qualified file name to which trace data is written. Tracing should only be performed at the request of TSM Service or Development. When creating file DSNs, you can use the following keywords: DRIVER= must be "TSM ODBC Driver" (without the quotes) UID= is a valid TSM Administrator ID. TCPADDR= is the TCP/IP address for your TSM server. TCPPORT= is the TCP/IP port number used to connect to your TSM server. FETCHSIZE= is the number of records that the ODBC driver requests from the TSM server per fetch request. This value must be between 1 and 1000000 (inclusive). The default value is 50. For example, if your administrator ID is "storman",your TSM server address is "storman.tucson.ibm.com", and your TSM TCP/IP port number is "1500", then the file DSN should look like this: [ODBC] DRIVER=TSM ODBC Driver UID=storman TCPADDR=storman.tucson.ibm.com TCPPORT=1500 Note that UID, TCPADDR, and TCPPORT are not required; if they are not specified, then you will be prompted for their values. The [ODBC] line is added for you automatically when you use the ODBC Data Soure Administrator to create the file DSN. To create a file DSN using the ODBC Data Source Administrator: 1) Start the ODBC Data Source Administrator from the Control Panel. Alternatively you can run odbcad32.exe. 2) Click on the "File DSN" tab, then click "Add...". 3) Select "TSM ODBC Driver" (located in the "Name" column). Then click "Next". 4) Enter the name you want to use for this DSN. For example, "TSM File DSN". Click "Next". 5) The dialog now shows you a summary of the options chosen thus far. Click "Finish". 6) You should now be presented with the "Connect to TSM Server" dialog. Fill in the TCP/IP address, TCP/IP port, administrator ID, and password, then click "Connect". An attempt will be made to connect to the TSM server using the information you supplied above. If the connection is successful, you will be returned to the ODBC Data Source Administrator dialog. If there was a problem connecting to the TSM server, then you will be prompted again to enter the correct information. Note: For security purposes, the password is NOT saved. It is used in this step for the purpose of validating the connection information. ------------------------------ Known Problems and Limitations ------------------------------ - SELECT statements containing the AS keyword in the column specification will not work. For example, the following will not work: select node_name as "Node Name" from nodes - For 64-bit Windows XP and 2003 users: The ODBC driver is available in a 32-bit version only, and thus is not compatible with 64-bit applications. The ODBC driver can be installed on 64-bit Windows XP and 2003 systems, but must be used with 32-bit applications. Also, the 32-bit version of the ODBC Data Source Administrator must be used to create and configure DSNs (see the "Defining Data Sources" section above). - If the ODBC application is running in a different locale from that of the server, data containing characters that do not map into the ODBC application machine's locale may appear unintelliglble ("garbled"). - When opening TSM database tables in Lotus Approach, the "Open" dialog includes a field labeled "Files of type". Select "ODBC Data Sources (*)" for this field. Do not select "TSM ODBC Driver (*)", because Approach will not open the tables. - If you use a file DSN to link TSM database tables into Microsoft Access, you will not be able to open the linked table after Access has been shut down and restarted. This problem is discussed in Microsoft support article Q327268. - The ANSxxxxx messages can now be displayed in languages other than English. Available languages include German, English, Spanich, French, Italian, Japanese, Korean, Portuguese (Brazilian), and Chinese (Simplified and Traditional). However, the TSM ODBC configuration dialogs and other non-ANSxxxxx text strings are currently displayed in English only. - In order to maintain the database integrity, only SELECT statements are supported by TSM ODBC Driver. You will not be able to manipulate the database with any other statements. - If there are more than two tables specified in the FROM clause of a SELECT statement, the query results will not be optimized by the TSM server. You may see duplicate records in the results. Example: The following SQL statement will get duplicate records: SELECT * FROM NODES, FILESPACES, CONTENTS [Note] The SQL statement execution time may be much longer due to preparing large amount of query results. - The columns in the ORDER BY clause must be in the select list. The TSM ODBC driver provides the information for the application. Some applications do not retrieve the information before generating the SQL query. Example: The following SQL statement will fail because PWSET_TIME is not in the select list. SELECT ADMIN_NAME FROM ADMINS ORDER BY PWSET_TIME - Not all TSM database tables have a primary key. When selecting "Link Tables" using MS Access, MS Access will prompt the users for primary key fields in the following situations: - the table does not have a primary key, or - the table has a primary key, but the primary key is comprised of multiple index fields. You may select primary key fields or select "Cancel" to ignore the prompt. --------------------------- Troubleshooting/Diagnostics --------------------------- Before proceeding with the items described below, be sure to check the "Known Problems and Limitations" section (above) to see if your problem is already known. If your problem is not described in that section, then continue with this section. * INSTALLATION PROBLEMS The Microsoft Software Installer (MSI) is used to install the TSM ODBC driver. If you are having trouble installing the TSM ODBC driver, you should contact IBM/Tivoli support and provide the following information: - Operating system version and service pack number (i.e. Windows 2000 SP 3, Windows XP SP 1a, etc.) - Exact version/release/level/patch of the TSM ODBC driver you are trying to install (i.e. 5.2.0.0). The version information can be found at the top of this README file. - Step-by-step recreate scenario, including the last dialog box you see before the failure occurs, and the exact text of any error messages you see. - Examine the system Event Log and report any event log errors that coincide with the time the install failure occurred. - An MSI setup.log file. To create this file, run setup.exe again as follows: setup /v"/l*v setup.log" Follow the prompts as usual to recreate the failure. After the setup program ends, you will have a file called setup.log which contains detailed diagnostic information about the setup. * DATA SOURCE CONFIGURATION PROBLEMS If you are having trouble creating or configuring a data source for the TSM ODBC driver, then read the "TSM ODBC Driver Configuration Details" section (below) and compare your system settings with those described in that section. If you do find any differences, and if you do not know how to repair them, or are uncomfortable doing so, then contact IBM/Tivoli support and provide the information described below the next paragraph (you do not need to provide trace data at this point). If the configuration looks okay, then try obtaining a trace of the TSM ODBC driver. See section "TSM ODBC Driver Tracing" (below) for instructions on tracing. Once you have the trace data, contact IBM/ Tivoli support and provide the following information: - Operating system version and service pack number (i.e. Windows Windows 2000 Server SP 3, Windows XP SP 1, etc.) - Exact version/release/level/patch of the TSM ODBC driver you are trying to install (i.e. 5.2.0.0). The version information can be found at the top of this README file. - Step-by-step recreate scenario, including the last dialog box you see before the failure occurs, and the exact text of any error messages you see. - Your ODBC configuration information. Include the following items: > X:\WINNT\ODBC.INI > X:\WINNT\ODBCINST.INI > The odbchkcu.reg and odbchklm.reg files created by the following commands: regedit -e odbchkcu.reg hkey_current_user\software\odbc regedit -e odbchklm.reg hkey_local_machine\software\odbc > A directory listing of the files in the directory where the TSM ODBC driver is installed. For example, if the driver is installed to directory C:\Program Files\Tivoli\TSM\odbc, then open up an OS command prompt, change into that directory, and issue the following command: dir > odbcdir.out Then you can send in the odbcdir.out file. > Trace data. * APPLICATION PROBLEMS If you have been able to install the TSM ODBC driver and configure a data source, but you are having trouble getting your application to work, then please do the following: - Verify that the application you are using is supported. See section "Supported ODBC Applications" (above) for a list of supported applications. If the application is unsupported, then be aware that assistance from IBM/Tivoli will be on a "best effort" basis only; it is recommended that you contact your Tivoli marketing representative and ask to open a requirement for supporting your application. NOTE: customer requirements are an integral part of future product planning, but this does not guarantee that support for your application will be implemented. - Obtain a trace as described in section "TSM ODBC Driver Tracing" (below). Contact IBM/Tivoli support and provide the following information: - Operating system version and service pack number (i.e. Windows Windows 2000 Server SP 3, Windows XP SP 1, etc.) - Exact version/release/level/patch of the TSM ODBC driver you are trying to install (i.e. 5.2.0.0). The version information can be found at the top of this README file. - Name and exact version/service pack of the ODBC application you are using. - Step-by-step recreate scenario, including the last dialog box you see before the failure occurs, and the exact text of any error messages you see. - Your ODBC configuration information. Include the following items: > X:\WINNT\ODBC.INI > X:\WINNT\ODBCINST.INI > The odbchkcu.reg and odbchklm.reg files created by the following commands: regedit -e odbchkcu.reg hkey_current_user\software\odbc regedit -e odbchklm.reg hkey_local_machine\software\odbc > A directory listing of the files in the directory where the TSM ODBC driver is installed. For example, if the driver is installed to directory C:\Program Files\Tivoli\TSM\odbc, then open up an OS command prompt, change into that directory, and issue the following command: dir > odbcdir.out Then you can send in the odbcdir.out file. > Trace data. --------------------------------- ODBC Driver Configuration Details --------------------------------- NOTE: The following implementation details are subject to change in future product releases. This information is being provided primarily for diagnostic purposes. * INSTALLED FILES The following files are always installed with the TSM ODBC driver into the directory specified during installation. The default TSM installation directory is: (32-bit Windows) x:\Program Files\Tivoli\TSM\odbc (64-bit Windows) x:\Program Files (x86)\Tivoli\TSM\odbc where 'x:' is the drive letter where the operating system is installed (usually C:). - dscenu.txt - dsmntapi.dll - odbcadsm.dll - tsmutil1.dll One or more of the following files may also be installed, depending on the language version of Windows you are running and/or which additional language support you specified during installation. - dscchs.txt Chinese (Simplified) - dsccht.txt Chinese (Traditional) - dsccsy.txt Czech - dscdeu.txt German - dscesp.txt Spanish - dscfra.txt French - dschun.txt Hungarian - dscita.txt Italian - dscjpn.txt Japanese - dsckor.txt Korean - dscplk.txt Polish - dscptb.txt Portuguese (Brazilian) - dscrus.txt Russian Example 1: If your machine is running the German version of Windows, then the dscdeu.txt file will be installed by default. Example 2: If your machine is running the German version of Windows and you also select French and Italian language support, then dscdeu.txt, dscfra.txt, and dscita.txt will be installed. Example 3: If you machine is running the English verison of Windows and you also select Spanish and Japanese support, then dscesp.txt and dscjpn.txt will be installed. NOTE: Prior versions of the TSM ODBC driver placed its files in the winnt\system32 directory. The following files may be deleted from that directory if they still exist: - dsgameng.txt - odbcadsm.dll - odbcadsm.txt * ENVIRONMENT VARIABLES The TSM ODBC driver uses the DSMODBC_DIR system environment variable to locate the driver's message repository (dsc*.txt). DSMODBC_DIR is set to the directory in which the ODBC driver is installed, i.e. C:\Program Files\Tivoli\TSM\odbc. Prior versions of the TSM ODBC driver used the DSMODBC_DIR or DSMG_DIR environment variables, which have been deprecated. However, they will still be honored if set. Specifically, if DSMODBC_DIR is set, then its value will be honored. If DSMODBC_DIR is not set, but DSMG_DIR is set, then the DSMG_DIR value will be honored. If neither DSMODBC_DIR nor DSMG_DIR are set, then the ODBC driver will look for the message repository in the "Path" value of the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Odbc The TSM ODBC driver installation program will attempt to remove DSMG_DIR and DSMODBC_DIR if they exist on your system. However, if they still exist after the install, then they should be removed manually. NOTE: While DSMG_DIR and DSMODBC_DIR are still honored as stated above, this is subject to change in the future. Therefore it is recommended that you not rely on these values. * REGISTRY SETTINGS IMPORTANT: Do NOT change any of these values unless it is at the direction of IBM/Tivoli Development or Service. The TSM ODBC driver installation settings are located in subkeys of the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion The following subkeys and associated values are pertinent to the TSM ODBC driver installation: ComponentsMsi NAME EXPLANATION ------------------------------------------------------------------ ODBC Driver A REG_SZ value that must be "Odbc" (without the quotes). Odbc NAME EXPLANATION ------------------------------------------------------------------ Path The directory in which you installed the TSM ODBC driver. This is the parent directory for the "odbc" subdirectory which contains the odbcadsm.dll file. For example, if odbcadsm.dll is in directory "C:\Program Files\Tivoli\TSM\odbc", then Path should be set to "C:\Program Files\Tivoli\TSM". This is a REG_SZ value. PtfLevel A REG_SZ value indicating the 4-node version number of the TSM ODBC driver. For example, if the TSM 5.1.5.0 ODBC driver is installed, then this value should be "5.1.5.0" (without the quotes). Odbc\nls\xx_XX xx_XX is a language abbreviation as follows (with the language name shown to the right for your reference): cs_CZ Czech de_DE German en_US U.S. English es_ES Spanish fr_FR French hu_HU Hungarian it_IT Italian ja_JP Japanese ko_KR Korean pl_PL Polish pt_BR Portuguese (Brazilian) ru_RU Russian zh_CN Chinese (Simplified) zh_TW Chinese (Traditional) Notes: You must always have the "Odbc\nls\en_US" subkey. If you installed the TSM ODBC driver on a non-English Windows system, then you may also have a subkey that corresponds to the language version of Windows you are running. For example, if you are running the German language version of Windows, then you may also have the "Odbc\nls\de_DE" subkey. You may have other subkeys as well if, during the install, you selected multiple language support. NAME EXPLANATION ------------------------------------------------------------------ FileName A REG_SZ value indicating the name of the TSM message repository that corresponds to the subkey's language setting. For example, in subkey "Odbc\nls\de_DE", the FileName value should be "dscdeu.txt" (without the quotes. Language A REG_SZ value indicating the language of the message repository specified in the "FileName" value. For example, if the FileName setting is "dscdeu.txt", then the Language setting must be "German". The following summarizes the subkey/FileName/Language settings: SUBKEY FILENAME LANGUAGE ------------------------------------------------------ Odbc\nls\cs_CZ dsccsy.txt Czech Odbc\nls\de_DE dscdeu.txt German Odbc\nls\en_US dscenu.txt English (US) Odbc\nls\es_ES dscesp.txt Spanish Odbc\nls\fr_FR dscfra.txt French Odbc\nls\hu_HU dschun.txt Hungarian Odbc\nls\it_IT dscita.txt Italian Odbc\nls\ja_JP dscjpn.txt Japanese Odbc\nls\ko_KR dsckor.txt Korean Odbc\nls\pl_PL dscplk.txt Polish Odbc\nls\pt_BR dscptb.txt Portuguese (Brazilian) Odbc\nls\ru_RU dscrus.txt Russian Odbc\nls\zh_CN dscchs.txt Chinese (Simplified) Odbc\nls\zh_TW dsccht.txt Chinese (Traditional) The TSM ODBC driver settings are located in subkeys of the following registry key: (32-bit Windows) HKEY_LOCAL_MACHINE\SOFTWARE\ODBC (64-bit Windows) HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC The following subkeys and associated values are pertinent to the TSM ODBC driver (these are all located under HKEY_LOCAL_MACHINE\SOFTWARE\ODBC): ODBC.INI\ODBCADSM NAME EXPLANATION ------------------------------------------------------------------ ADSMTrace A REG_SZ value that indicates whether TSM ODBC driver tracing is enabled. Values may be one of: - No - Yes If tracing is enabled (ADSMTrace is set to Yes), then trace output will be written to the file specified by the TraceFileName value (see below). Language A REG_SZ value that indicates which language version of the TSM message repository is in use. Values may be one of the following: - Czech - German - English (US) - Spanish - French - Hungarian - Italian - Japanese - Korean - Polish - Portuguese (Brazilian) - Russian - Chinese (Simplified) - Chinese (Traditional) TraceFileName A REG_SZ value that indicates the name of the TSM ODBC driver trace file. ODBCINST.INI\ODBC Drivers NAME EXPLANATION ------------------------------------------------------------------ TSM ODBC Driver A REG_sZ value indicating that the TSM ODBC driver is installed. This value is always set to "Installed". ODBCINST.INI\TSM ODBC Driver NAME EXPLANATION ------------------------------------------------------------------ APILevel A REG_SZ value that is always set to "0". This indicates that the TSM ODBC driver implements ODBC Core level functions only. ConnectFunctions A REG_SZ value that is always set to "YYN". This string indicates whether the driver implements the SQLConnect(), SQLDriverConnect(), and SQLBrowseConnect() functions, respectively. A 'Y' ("Yes") means that the function is implemented in the driver; a 'N' ("No") means that the function is not implemented in the driver. Thus the TSM ODBC driver currently implements SQLConnect() and SQLDriverConnect(); the driver does not implement SQLBrowseConnect(). Driver A REG_SZ value that specifies the full path to the TSM ODBC driver. Thus if the driver is installed to C:\Program Files\Tivoli\TSM\odbc, the value will be: C:\Program Files\Tivoli\TSM\odbc\odbcadsm.dll DriverODBCVer A REG_SZ value that indicates which version of the ODBC specification the driver supports. supports. This value is set to "03.51". FileUsage A REG_SZ value indicating how the driver treats files in a data source. Since the TSM ODBC driver is not a file-based driver, this value is always "0". Setup A REG_SZ value that specifies the full path to the driver's Data Source configuration program. The TSM ODBC driver's configuration program is in the TSM ODBC driver itself, so this value should always match that of the Driver setting (see above). SQLLevel A REG_SZ value that indicates the SQL-92 grammar supported by the driver. Since TSM supports a subset of the SQL-92 entry-level grammar, this value is always "0". UsageCount A REG_DWORD value that indicates how many components use this driver. Since the driver is used by only one component (the TSM ODBC driver itself), this value should be "1". The TSM ODBC driver data source settings are located in subkeys of the following registry key: HKEY_CURRENT_USER\Software\ODBC\ODBC.INI The following subkeys and associated values are pertinent to the TSM ODBC driver data sources (these are all located under HKEY_CURRENT_USER\Software\ODBC\ODBC.INI): - A user-specified data source name. Note that the TSM ODBC driver install program configures a sample data source called "TSM ODBC Sample User DSN". NAME EXPLANATION ------------------------------------------------------------------ CommMethod A REG_SZ value indicating the communications method that the TSM ODBC driver uses to communicate with the TSM server. since the only supported communications protocol is TCP/IP, this value is always set to "TCP/IP". Driver A REG_SZ value that specifies the full path to the TSM ODBC driver. Thus if the driver is installed to C:\Program Files\Tivoli\TSM\odbc, the value will be: C:\Program Files\Tivoli\TSM\odbc\odbcadsm.dll NOTE: This value always matches that of the Driver value specified in registry subkey HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ TSM ODBC Driver (see above). DsnDescription A REG_SZ value containing a user-specified free- form comment (or description) for the data source definition. FetchSize A REG_SZ value indicating the maximum number of rows that the ODBC driver requests (buffers) from the TSM server at a time. Note that this is not the same as the SQL_ATTR_ROW_ARRAY_SIZE ODBC statement attribute. The former governs the number of records that the ODBC driver will buffer from the server, while the latter governs the number of records that the application will request from the ODBC driver. The default setting is "50" (50 records). Larger settings may improve performance. TcpPort A REG_SZ value indicating the TCP/IP communications port that the TSM ODBC driver uses to connect to the TSM server. TcpSrvAddr A REG_SZ value indicating the TCP/IP address that the TSM ODBC driver uses to connect to the TSM server. UID A REG_SZ value indicating the name of the TSM Administrator ID used to connect to the TSM server. * ODBC .INI FILES The operating system records information from ODBC registry keys in two files located in the x:\winnt directory (x:\windows for Windows XP users): - ODBC.INI - ODBCINST.INI IMPORTANT: Do NOT rename, delete, or otherwise modify these files or their contents unless it is at the direction of IBM/Tivoli Development or Service. ----------------------- TSM ODBC Driver Tracing ----------------------- There are two parts to collecting TSM ODBC driver trace data. When collecting trace data, you need to collect both parts: - Tracing the ODBC Driver Manager - Tracing the TSM ODBC driver The following are the steps involved in collecting trace data: 1) Activate TSM ODBC driver tracing. To do this, start the ODBC Data Source Administrator (odbcad32.exe), select the data source, and click the "Configure..." button. This will bring up the "Configure a TSM Data Source" dialog. Check the "Enable trace" check-box, and enter a fully-qualified trace file name; for example, C:\TSMODBC.TRC. Then click the "OK" button. Leave the ODBC Data Source Administrator running since you will need it in the next step. 2) Activate ODBC Driver Manager tracing. To do this, select the "Tracing" tab in the ODBC Data Source Administrator. In the "Log file Path" text box, enter a fully-qualified trace file name; for example, C:\ODBCMGR.TRC. Do *not* use the same name as in step 1 above. Click the "Apply" button. Next, click the "Start Tracing Now" button. The button's name will change to, "Stop Tracing Now". If the button already was labeled "Stop Tracing Now", then click the button to change it to "Start Tracing Now", then click it again to restart the trace (the button will once again read "Stop Tracing Now"). Click the "OK" button. 3) Delete (or rename) any existing TSM ODBC driver trace. Using the same name as in step 1 above, delete or rename C:\TSMODBC.TRC (if it exists.) 4) Delete (or rename) any existing ODBC Driver Manager trace. Using the same name as in step 2 above, delete or rename C:\ODBCMGR.TRC (if it exists.) 5) Recreate the problem. 6) After the problem has been recreated, rename the two trace files to different names. Using the sample names above, you could rename them as follows: C:\TSMODBC.TRC --> C:\TSMODBC.KEEP.TRC C:\ODBCMGR.TRC --> C:\ODBCMGR.KEEP.TRC 7) Zip up the renamed trace files (they may grow rather large) and be prepared to send them in to IBM/Tivoli support for analysis. 8) Deactivate ODBC Driver Manager tracing. Using the ODBC Data Source Administrator, select the "Tracing" tab and click the "Stop Tracing Now" button. Then click "OK". 9) Deactivate TSM ODBC driver tracing. Using the ODBC Data Source Administrator, select the data source and click the "Configure..." button. Uncheck the "Enable trace" check-box, then click "OK". --------------------------- APARs Fixed in this Release --------------------------- APARs fixed in version 5.2.2: IC37761 - TSM ODBC driver applications may hang APARs fixed in version 5.2.0: IC33846 - Incorrect format of enumerated fields when using the version 4.2 or 5.1 ODBC driver. IC33963 - ODBC driver displays connection information when connecting to the TSM server. ----------------------------------- Other Defects Fixed in this Release ----------------------------------- Defects fixed in version 5.2.2: None Defects fixed in version 5.2.0: - Fixed a problem with setting SQL_ATTR_ROW_ARRAY_SIZE to a value higher than 1. Calling SQLSetStmtAttr() to set SQL_ATTR_ROW_STATUS_PTR, SQL_ATTR_ROWS_FETCHED_PTR, and SQL_ATTR_ROW_ARRAY_SIZE now all work correctly. ---------- Trademarks ---------- IBM is a trademark or registered trademark of the International Business Machines Corporation or its subsidiary corporations in the United States or other countries or both: Tivoli and The Power to Manage. Anything. Anywhere. are trademarks or registered trademarks of Tivoli Systems Inc. in the United States, other countries, or both. In Denmark, Tivoli is a trademark licensed from Kjobenhavns Sommer - Tivoli A/S. Microsoft, Windows, Windows NT, Windows 2000, Windows XP, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Microsoft Data Access Components (MDAC), and Microsoft Software Installer are the copyrighted work of Microsoft and/or its suppliers.