Formats can also be output at printers. Refer to the manual for your formatting system for information about the supported printer functions.
In the KCMF/kcfn field of the KDCS parameter area, you enter for the FPUT/DPUT call:
*format_name | +format_name | #format_name
where:
* | Formatting without the option of changing the attribute |
+ | Formatting with the option of changing the attributes of individual format fields |
# | Formatting with the option of both changing the characteristics of individual format fields and changing the global characteristics of the format fields |
The formatting system must support the printer models as they are known in the VTSU-B or as they were generated for RSO (for PTYPE=*RSO).
If you use the FORMAT event exit for printouts, you have to consider the following:
you do not have to set the restart area
you have to request the print out confirmation in the message header
you have to enter the confirmation bytes transferred by openUTM in the message header
you ascertain the formatting specifications, such as format name, device type, etc. from the KB header and the parameter area of the FORMAT event service.
For the structure of the message header, refer to your printer manual.
Form feed
Whenever FPUT/DPUT is called, including in the case of message segments with FPUT/DPUT NT, the form feed depends on the contents of the KCDF field in the KDCS parameter area (exception: when #Formats are used):
KCREPL | Form feed before printing, i.e. the format is printed starting at the basic form setting specified at the printer. |
other | No form feed, i.e. the format is printed starting at the next line (also for the first FPUT/DPUT). |
This allows you to concatenate formats in order to print large forms, independent of any length limitations. However, the physical message segment must be shorter than:
the BCAM letter length (see TRANSDATA manual "Generating a Data Communication System"), and
the device-specific length that is supplied by VTSU-B when a connection is established.