Resolved Issues
Resolved issues are corrections and updates to Teradata Tools and Utilities software and to documentation affected by the updates.
|
Issue |
Description |
|
CLAC-28974 |
BTEQ now imports from a Vartext data file properly in cases where the Vartext data contains multi-byte characters such that one of those bytes corresponds to the delimiter being used. |
|
CLAC-29742 |
BTEQ supports an unlimited value for PAGELENGTH. |
|
CLAC-30413 |
BTEQ now strips trailing comments embedded in a LOGON string for all LOGON elements, provided that the comments are separated from the elements by at least one white space. |
|
CLAC-30819 |
Interactive mode Windows BTEQ now behaves as usual to SIGINT (Ctrl+C) on all supported Windows OSs. |
|
CLAC-30930 |
Windows BTEQ now properly handles input scripts containing LF new lines in combination with the OS command. |
|
CLAC-30978 |
Mainframe BTEQ uses default values when DCB attributes are missing for new output data sets. |
|
CLAC-30999 |
Mainframe BTEQ no longer abends when opening non-DLL COBOL NOTIFY exits. |
|
CLAC-31058 |
BTEQ gracefully handles all memory allocation failures. |
|
CLAC-31214 |
BTEQ, when running in UTF-16 mode (where I/O is UTF-16 and session charset is also UTF-16), parses and executes the THEN clause from the IF-THEN command properly, just like when running in non-UTF-16 mode. |
|
CLAC-31315 |
BTEQ handles long lines in input properly. |
|
CLAC-31427 |
z/OS BTEQ no longer abends when doing an export to a PDS member where the associated DD definition contains DISP=NEW within the BTEQ JOB STEP. |
|
CLAC-28781 |
Documentation Only - Character set information has been revised. |
|
CLAC-30774 |
Documentation Only - Clarification made for the encoding of external source files. |