ABAP Archives

Use

File – Applies to direct input only.

The telnet server does not intercept any input from the client, but rather lets it pass on to the running program.

In this mode, the SAPVtio usually receives the data through a named or an anonymous pipe. Therefore, all the rules for specifying the output file name can be applied to the input file name, that is:

When "STDIN$" is specified as the file name, it is treated as an anonymous pipe

Every identifier between the %…% signs is expanded to the value of the corresponding environment variable, except for two cases:

%pid% is expanded to the running process number

%tid% is expanded to the running thread number

Terminal configuration – In this field, you can specify the file that will contain the escape sequences recognized by SAPVtio.

When the SAPVtio receives the input in a raw mode (through a pipe), the special keys (arrows, function keys etc.) are passed on in the form of escape sequences. These sequences can slightly differ for different terminal emulations, and can therefore be configured externally. The sequences can be specified in the terminal configuration file using a special format. Refer to the Specifying escape sequences section in the appendix.

Use the "…" button to browse through your file system to find the adequate file.

Echo input characters– When checked, the SAPVtio will automatically transfer any character read from the input stream to the output stream. Although useful in some telnet applications, this option must be unchecked when using SAPVtio with SAPConsole.

Standard console events input– If you have an application (such as SAPConsole) that runs on a telnet server which does all the escape sequence interpreting work internally, use this option. This will leave the terminal emulation work to the telnet server and expect the input from the Windows Console.