| Issue/Enhancement | Description |
|---|---|
| BTEQ-970 | BTEQ's behavior for handling breaks has changed for Workstation platforms.
|
| BTEQ-6971 BTEQ-6845 |
BTEQ now allows Large Data Objects (LDOs) to be imported via non-deferred transfers. This allows for smaller LDOs to be loaded with fewer parcels along with the initial SQL request, which may improve performance over deferred transfers. Non-deferred LDO imports can be accomplished by using the new DEFERLIMITS option for the IMPORT command. |
| BTEQ-6262 BTEQ-10265 |
BTEQ now allows Large Data Objects (LDOs) to be exported via non-deferred transfers. This allows for smaller LDOs to be unloaded with fewer parcels, which may improve performance over deferred transfers. Non-deferred LDO exports can be accomplished by using the existing DEFERTRANS option or the new DEFERLIMITS option for the EXPORT command. |
| BTEQ-6221 | BTEQ now has a TRIMTRAILINGSPACES command, which when set to OFF, inhibits the trimming of trailing spaces from field-mode response lines. By default, TRIMTRAILINGSPACES is ON, which means BTEQ will trim all trailing spaces from field-mode response lines.Use the OFF setting to inhibit BTEQ from trimming the trailing spaces. The TRIMTRAILINGSPACES setting only affects the output for Field Mode, not Record Mode, Indicator Mode, or Multipart Indicator Mode. In other words, TRIMTRAILINGSPACES setting affects only those response lines that go to stdout or EXPORT REPORT files, and not those that go to EXPORT DATA, EXPORT INDICDATA or EXPORT DIF files. Note that this setting affects only the columnar response lines. For example, it affects the SELECT or HELP query output but does not affect the SHOW or COMMENT query output. Trimming the trailing spaces from field-mode response lines could be beneficial for stdout files as it minimizes the number of bytes used for tabular report output. However, for exported reports, trimming of trailing spaces can cause issues for post-processing that expects fixed-size records. |
| BTEQ-6757 | BTEQ 15.10 was enhanced to add a timeout feature via a new BTEQ command EXITONDELAY. This command can be used to establish the maximum time duration within which to allow a submitted SQL request to be processed before CLI will time out the request. When a time out occurs, the BTEQ process will terminate. The time out is triggered when either the database goes down or the duration is exceeded. There is a usage scenario that is currently limited by a CLI restriction. To effect an EXITONDELAY timeout, BTEQ must disable CLI's Automatic Redrive capability. This means that when a database goes down, CLI will not be able to re-establish lost connections for the purpose of re-driving their requests. So it may be the case that an SQL request, which could have succeeded within the specified timeout duration, will not succeed because CLI must immediately return control to BTEQ for a down database and BTEQ must then immediately exit.
|
| BTEQ-6994 | BTEQ has changed the message that is displayed when the end of a RUN file is reached without executing an EXIT or QUIT command. In the past, BTEQ displayed the following:*** Warning: EOF on INPUT stream. To be more specific, BTEQ now displays: *** Encountered EOF on RUN file. Returning to stdin. Similarly, BTEQ has changed the messages that are displayed when the end of the stdin file is reached in batch mode. In the past, workstation BTEQ displayed the following: *** Warning: EOF on INPUT stream. *** BTEQ exiting due to EOF on stdin. And in the past, z/OS BTEQ displayed the following: *** Warning: EOF on INPUT stream. Now, both workstation and z/OS BTEQ display this one message: *** BTEQ exiting due to EOF on stdin. |