Changing the Value for Data Encryption - Call-Level Interface Version 2

Teradata® Call-Level Interface Version 2 Reference for Workstation-Attached Systems - 20.00

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Call-Level Interface Version 2
Release Number
20.00
Published
January 2024
Language
English (United States)
Last Update
2024-05-14
dita:mapPath
bmn1691484839905.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
fvz1470444150352
Product Category
Teradata Tools and Utilities
If the value provided is not appropriate for the application, before calling DBCHCL for the Connect, Run Startup, or Initiate Request function, the application program may set:
  1. Change Options to 'Y'.
  2. Set Data Encryption to:
    • Y, if messages to and from the database are to be encoded, starting with this message.
    • N, if messages to and from the database are not to be encoded, starting with this message.

    Users have no control over encryption of the connect (logon) messages. If the GSS or the SSO flags are turned on at the database/Gateway, connect messages are automatically encrypted. Encryption of all other messages is controlled through the Data Encryption field. For more information on database/Gateway flags, refer to the Gateway Control Utility documentation.

    If Data Encryption is set to 'Y', messages to the database computer are encrypted before they are placed on the network, and decrypted when they reach the database computer. Messages from the database computer are encrypted before they are placed on the network, and decrypted when they reach the workstation-attached system.

    Encryption and decryption take time. It is the application programmer’s responsibility to determine whether any particular request requires encryption. Some applications and sites may not require anything to be encrypted, some may require everything to be encrypted, and some may require selective encryption, for instance, encryption when text contains a password.