openUTM operates in line mode whenever the name specified in KCMF/kcfn starts with a blank. In line mode, openUTM also enables you to use the following options to control the screen output:
use logical control codes to structure the output
In addition to the screen output functions KCALARM, KCREPR and KCRESTRT that can be used in format mode (see "Screen output functions in format mode (BS2000 systems)"), in line mode it is also possible to use the screen output functions KCCARD and KCEXTEND (extended line mode).
use of edit profiles
For a description of how to prepare messages for printing, refer to section "Output to printers".
Using logical control codes for structuring
In line mode you can use logical control codes to structure the output. The VTSU (Virtual Terminal Support) terminal support facility then converts the control codes into the physical control codes necessary for the addressed device. You can use all logical control codes permitted by the TIAM access method, see the "TIAM User Guide". In some programming languages data structures are available which you can copy into the program (see the "TIAM User Guide).
KCCARD screen function
You can use the KCCARD screen function to input data via magnetic strip cards:
If you use the KCCARD screen function to output a dialog message, the keyboard is locked and the terminal user is requested to insert a magnetic strip card into the ID card reader.
KCEXTEND screen function
If you use this screen function the output fields are set to a particular, predefined value which is equivalent to the macro WRTRD, ... EXTEND=YES. All output fields are displayed in half video and protected by default, see the "TIAM User Guide" for further information.
Edit profiles
An edit profile is a set of attributes used for output in line mode. Using edit profiles you can, for example, specify that characters entered at the terminal are not to be displayed (password entry) or request lower case to upper case conversion. Alongside the KCCARD screen function edit profiles are another way of requesting input from ID card readers. You can also perform other screen functions such as, for example, KCREPR.
You use the KDCDEF statement EDIT to specify the name and attributes of edit profiles at generation (see the openUTM manual “Generating Applications”). The length of the name can be up to 7 characters. You can use the MPUT/FPUT/DPUT calls to address an edit profile in a program unit. To do this, enter a blank in the first byte of the KCMF/kcfn field and the name of the edit profile in the remaining seven bytes.
Edit profiles are handled like format names, i.e. the name of the edit profile of the last output message is returned in the KCRMF/kcrfn field after INIT (as with format identifiers). If you use MGET/FGET calls the name is entered in the KCMF/kcfn field.
Note the following points when edit profiles:
When using MPUT, FPUT or DPUT calls with edit profiles, no screen function may be specified (KCDF must be set to binary zero) as otherwise openUTM responds to MPUT with 70Z or to FPUT/DPUT with 40Z.
As soon as edit profiles are generated for an application, you must use 8 blanks in KCMF/kcfn to identify messages in line mode (without edit profile); it is not sufficient to fill set the first byte with blanks, since openUTM interprets this as an incorrect format identifier and sets the corresponding error code in KCRCCC.
If you use MPUT NT, FPUT NT or DPUT NT to issue multiple message segments to a terminal, the name of the edit profile must not change, otherwise openUTM responds to MPUT with 75Z and to FPUT/DPUT with 45Z. When issuing partial messages to printers edit profile names may change.
If the screen was overwritten by the output of an asynchronous message, openUTM performs an automatic KDCDISP on the next input when using edit profiles.
For messages to UPIC clients the names of the edit profiles are treated like format identifiers, i.e. they are also passed (therefore they also appear in the UTM program unit in KCRMF/kcrfn), although they do not have any effect.
For messages via distributed processing the names of the edit profiles are processed like format identifiers:
In distributed processing via LU6.1 the names of the edit profiles are transferred (i.e. they appear in KCRMF/kcfn). However, they have no effect.
In distributed processing using OSI TP, no edit profile must be specified in KCMF/kcfn, since openUTM uses field of the the format identifier to transfer the abstract syntax.