NO, currently TEPS does not support MSSQL Server 2017.
APAR IJ31828 opened to address this issue.
From the Operating System and driver point of view all is fine: see item 1)+2). The problem appears to be the in "CNPSDataSource.exe". If there is a 32 Bit System DNS named "teps" already it is deleted by the TEPS data source executable. And a new one is created but with default MS SQL Driver. Thats why it is failing: Default SQL driver does not support TLS 1.2 (it is not updated by MS anymore). Hence, to solve the issue:
- We need somehow force the TEPS configuration tool to use the correct new "ODBC Driver 17 for SQL Server" driver.
- Tell Windows to use the new driver as default (perhaps by A "changing the driver name here: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\SQL Server > Driver"; or B "Copy the new driver to the path and name found in the registry ODBC\ODBCINST.INI\SQL Server > Driver string".
At this time we do not support the newer msodbcsql17.dll driver. We only support the sqlsrv32.dll driver.#Support#SupportMigration#Tivoli