The ISO operand in the @INPUT statement (format 3) is ignored. Hexadecimal input is based on the coding of the current work file's character set.
The output format of the @STATUS statement has been modified since some of the items in the output are no longer relevant, some global properties are now work file-specific and there are other properties that need to be output.
In the @VTCSET=OFF statement, only those line mode control characters that do not belong to the EBCDIC-DF03 kernel are converted into smudge characters. This contributes to the purpose of the statement which is to prevent the fragmentation of the screen output due to control characters.
No line count is now specified for screen output in the @VDT statement. Screen output with the @PRINT V or @PRINT E statement now always uses the number of lines that can be displayed on the screen (in L mode this is always 23 lines).
When the @VDT F2 statement is issued, the position is no longer moved back to column 1. Instead, the screen remains at the specified start column.
The @VDT statement now also supports the additional formats F3 and F4.
The statements @COMPARE, @FSTAT, @SHIH, @SHOW, @STAJV and @STATUS output information to work file 9. If a file is already open there then the output is rejected. In the past, this was only the case for the @SHIH and @SHOW LIBRARY statements.
The characters defined as delimiter characters using the @QUOTE statement must not be the same as the wildcard characters (see the @SYMBOLS statement). Although, in the past, the @SYMBOLS statement was rejected if a delimiter character was to be defined as
a wildcard character, the @QUOTE statement was nevertheless accepted if a wildcard was to be defined as a delimiter character. In some cases, this could lead to problems during the analysis of statement syntax.
The special marks (marks 13, 14 and 15) are no longer deleted by the @DELETE MARK statement. Even though, in the past, the special marks could only be set via the subroutine interface they were not protected against deletion by ordinary EDT users. This is the behavior described in the V16.6B manual.
Column number specifications in the @SEPARATE statement now operate recursively, i.e. if separating a record creates a continuation record which exceeds the specified column number, then the continuation record itself is split. In the past, the continuation record was not separated, thus obviating the point of specifying a column number as a separation point.
Specifying a separator in @SEPARATE may result in the creation of records of length 0 if multiple separators occur in immediate succession in the record. This change is the result of the desire to make the handling of empty lines consistent.
It is now also possible in F mode to save the last defined current line number and current increment in the @SET statement (format 6) and to restore the saved settings. In the past, this function was only effective in L mode.
A new @RUN statement with modified syntax and a modified interface has been introduced.
The @SHOW statement (format 1) no longer uses the ISO4 operand. The layout of the information line has been adapted.
In batch mode, the @DIALOG statement is rejected with the message EDT5400. In compatibility mode and in EDT V16.6B it is ignored without any message if switch 5 is set. If switch 5 is not set, it is rejected with message EDT5400 in compatibility mode and with the (inappropriate) message EDT5409 in EDT V16.6B.
In the @SDFTEST statement, the explicit specification of either the name of the program whose statements are to be checked or of the name type applies only to the current call and does not implicitly modify the settings made for these values using @PAR SDF-PROGRAM or @PAR SDF-NAME-TYPE.
In the @SDFTEST statement, it is now possible to check commands and statements with more than 255 continuation lines (up to the maximum buffer length of 16379 bytes).
A record marked by means of the statement code S is always positioned in the second screen line. If necessary, the information line and tab line are temporarily hidden.
If a statement which is retrieved into the statement line using # contains characters which cannot be displayed in the current communications character set then ?s are output instead of these characters.