CASESPECIFIC What is its purpose? - response (4) by dnoeth

You set the transaction mode in the connection string:
TMODE=ANSI/TERA/DEFAULT
 
Regarding "best mode" you should check your system's default. Most systems still use Teradata sessions and there are some important differences:
- Teradata defaults to SET tables, NOT CASESPECIFIC chars and silently truncates strings which exceed the target colunm's size.
Each request is by default an auto-commited transaction unless you use BEGIN/END TRANSACTION (BT/ET)
- ANSI defaults to MULTISET tables, CASEPECIFIC chars and returns an error when a string is trucated.
Transaction are handled like Oracle, the first request within a session opens a transaction which is explicitly commited using COMMIT.
 
Dieter