With SAS 9.4M7, reading in a Teradata table might intermittently generate an error when either of the following scenarios is true:

Scenario 1

• You run SAS 9.4M7 with Hot Fix J8F003 or J8F004.
• Your first LIBNAME statement connecting to Teradata or your CONNECT TO statement includes the OVERRIDE_RESP_LEN=YES option.
• Your Teradata clispb.dat file includes setting resp_buf_len= to a value greater than 65,535.

Scenario 2

• You run SAS 9.4M7 with Hot Fix J8F003 or J8F004.
• You use TTU 15.10. 
• Your first LIBNAME statement connecting to Teradata or your CONNECT TO statement includes OVERRIDE_RESP_LEN=NO, or if you do not include the option because the default is no.

The error might look similar to the following:

This issue occurs because, starting with Hot Fix J8F003, the resp_buf_len setting in the clispb.dat file is ignored and is automatically set to 1,048,500 when OVERRIDE_RESP_LEN=YES or when the option is not included. 
 
The workaround is to set resp_buf_len=65535 in your Teradata clispb.dat file and to use OVERRIDE_RESP_LEN=YES.

The error might also occur with versions prior to SAS 9.4M7. For more information, see SAS Note 46785.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Post Hot Fix Installation Information

After you apply the hot fix, there are some differences:

• If you use TTU 16.20 or later, you should remove the TCP_BUF_SIZE environment variable from your SAS program or sasv9.cfg file, because it is automatically tuned by Teradata starting with TTU 16.00.
• Output generated as a result of specifying the SASTRACE= option reveals the response buffer and request buffer size for each connection. The output might look similar to the following:

• The RESP_BUF_LEN= setting in the clispb.dat file is honored if you specify the OVERRIDE_RESP_LEN=YES option in the first LIBNAME statement or in each CONNECT TO statement to Teradata. If you set the OVERRIDE_RESP_LEN= option to no, the default RESP_BUF_LEN is 1,048,500.

Currently, the OVERRIDE_RESP_LEN= option is not checked for different settings when determining whether multiple LIBNAME statements can share a connection to Teradata. If the connection is shared, the setting for the option in the first LIBNAME statement is honored for the shared connection even if the settings are different. This behavior does not change with the hot fix. 

For example, the following LIBNAME statements result in OVERRIDE_RESP_BUFF = NO:

While the following LIBNAME statements result in OVERRIDE_RESP_BUFF = YES:      

Operating System and Release Information

A fix for this issue for SAS/ACCESS Interface to Teradata 9.47 is available at: