The UseEncryption setting determines whether the login user ID and/or password is sent to the host encrypted or in clear text. When a user logs into the host or changes their host password using a StarSQL connection, StarSQL sends the user ID in clear text and the password encrypted unless the UseEncryption parameter is explicitly set to No or Yes (Any is the default value). To send the user ID and password encrypted, you must set the UseEncryption parameter to Yes and the host must support encryption.
DB2 for z/OS successfully negotiates password encryption. DB2 for i supports password encryption but does not support encrypted user IDs, therefore the UseEncryption setting must be Any or No. DB2 for Linux, UNIX, and Windows supports encrypted passwords if you enable the database for encryption as described in the "Host Preparation" chapter of the StarSQL for Windows User's Guide. If the host does not support encrypted passwords you can set UseEncryption to No to send both the user ID and password in clear text.
Specify Any, Yes, and No for the UseEncryption setting, as described in the following table.
UseEncryption Setting |
Description |
No |
StarSQL always sends the user ID and password to the host in clear text. |
Yes |
StarSQL always sends the user ID and password to the host encrypted. If the host does not support encryption, StarSQL returns an error. |
Any (default) |
StarSQL sends the user ID in clear text and the password encrypted. If the log fails, StarSQL then sends both the user ID and password in clear text. |