openUTM enables you to request specific screen functions together with the message output when using +formats and *formats. To do this, you enter one of the predefined values for your programming language in the KCDF (device function) field in the KDCS parameter area. For C/C++ these values are in the kcdf.h include file and for COBOL in the COPY element KCDFC.
With "#" formats, KDCF must be set to binary zero. The screen functions are controlled using global attributes.
You can use the following functions in +formats and *formats:
KCREPL | (replace) |
Clear and rewrite screen | |
KCERAS | (erase) |
If KCLM = 0, all variable fields are erased, the format is retained. If KCLM > 0, new field contents are output in the same format, other variable fields are erased | |
KCALARM | (alarm) |
An audible alarm sounds at output | |
KCREPR | (reproduce) |
Screen output to printer | |
KCRESTRT | (restart) |
screen restart after PEND RS | |
KCNODF | (no device feature) |
No screen function, KCDF is set to binary zero |
If you are working with message segments, only the entry for the first message segment applies. All subsequent message segments must have binary zero in the KCDF field.
You can combine two or more screen output functions, for example with the statement:
COBOL: | KCDF = KCREPL + KCREPR + KCALARM |
C/C++: | kcdf = KCREPL | KCREPR | KCALARM |
For performance reasons, however, you should use the KCREPL function sparingly.
The effect of KCERAS and KCREPL depends on the selection of the FHS start parameters, see the "FHS User Guide".
For information on error processing when formatting errors occur, refer to the openUTM manual ”Messages, Debugging and Diagnostics”.