If necessary, you can make formats available before service start in order to simplify the entry of the data required by the service.
These formats are called basis formats. You can use basic formats in the following ways:
Define start formats
In the configuration of the UTM application you can define a specific start format for each LTERM partner. In applications with the SIGNON event exit (see "The SIGNON service") the exit can read this start format if no user is logged on to this LTERM. In applications without the SIGNON event exit and without user IDs, this start format is output after the terminal connection is established through this LTERM partner.In the configuration of the UTM application, you can define a user-specific start format for each user ID. After the user has signed on to UTM under this user ID, UTM outputs this format on screen. In applications without a SIGNON event exit, openUTM outputs this format after the user has signed on to openUTM under this user ID. In applications with a SIGNON event exit, the exit can read this start format if a user has signed on under this user ID. *formats, +formats and #formats can be used as start formats. #formats can only be used as start formats, however, when the SIGNON event service is used.
Format output at end of service
At the end of a dialog service you can output a format from a program unit This format can be used by the terminal user at the start of the next service.Format request using KDCFOR
The user at the terminal can use the KDCFOR user command to request a basic format. openUTM will then output the desired format. You cannot use KDCFOR for #formats.
In order to start a service by entering a format you have to transfer the desired transaction code together with the message. You can do this in the following ways:
In the format, the first input field is an 8-character field into which the user enters the desired transaction code.
Note that this field (in +formats including attributes) is not transferred to the message area. (Exceptions: #formats, BADTACS event service or if the INPUT exit was used to make other specifications). If the transaction code field contains blanks, the string up to the first blank is interpreted as the transaction code. If you use addressing aids to structure the input area, you must take account of this truncation of the transaction code.The format permits the transaction code to be entered at any other specified location. The input is evaluated using the input exit and the transaction code is extracted.
The transaction code is assigned to a function key at generation, see KDCDEF statement SFUNC in the openUTM manual “Generating Applications”, and the user presses this function key.
The function key must be an F-key because messages are not passed when the K-keys are used (see also the KDCDEF statement SFUNC).
The format contains one or more UTM control fields. In a control field, the transaction code is either entered by the user or is already preset. The "UTM control field" attribute is assigned when the format is created.