bteq .logon error - response (1) by dnoeth

The default system name is "dbc".
The old way for name resolution was to add COPx to the system name (e.g. localhost -> localhostCOP1).
ODBC/.NET/JDBC additionally try to resolve the system name without expansion, i can't remember when this was added to CLI.
You probably use different versions of BTEQ/CLI, 13 vs. 13.10.
 
There are some articles on similar topics:
http://developer.teradata.com/connectivity/articles/logging-on-teradata-database-sessions-via-bteq
http://developer.teradata.com/connectivity/articles/laddered-concurrent-connect-lcc-client-performance-improvements
 
Dieter