@INPUT (format 3) - Define EDT input mode

This format of the @INPUT statement allows users to define how EDT is to interpret text input in L mode.

Operation	Operands	L mode
@INPUT	[ { [ CHAR ]     | HEX | X [ISO]     | BINARY } ]

CHAR	Causes EDT to interpret record input in L mode as a sequence of characters in the character set applicable to the input source (terminal, SYSDTA, file, library element, work file) (see section “L mode” which also discusses the handling of character sets during input in L mode).
HEX, X	Causes EDT to interpret record input in L mode as a sequence of hexadecimal characters (see section “L mode” which also discusses the handling of character sets during hexadecimal input).
ISO	This operand is no longer supported in EDT V17.0 Unicode mode. For reasons of compatibility, it is ignored and no error message is issued if it is input. In EDT V17.0 Unicode mode, ISO character sets are not subject to any special processing. If an ISO character set is defined for the current work file then hexadecimal input for this work file is automatically interpreted in the correct code and there is no implicit conversion into EBCDIC.
BINARY	Causes EDT to interpret record input in L mode as a sequence of binary characters (see section “L mode”).

The default setting when EDT is called is @INPUT CHAR.

The maximum permitted abbreviation of the statement can only be used if operands are specified. If called without operands, the maximum permitted abbreviation is @INP as EDT otherwise recognizes the @INDEX statement.

Note

Even if @INPUT HEX or @INPUT BINARY has been specified, statements may not be entered in hexadecimal or binary coding.