Each message that openUTM generates while an application is running can be issued to one or more of the following destinations:
SYSLST | Output to SYSLST. |
SYSOUT | Output to SYSOUT. |
STATION | Output to clients connected via a PTERM or a TPOOL with PTYPE |
SYSLINE | Output to the system line of the terminal; user screen formats are maintained. If a message is to be output to the system line, both SYSLINE and STATION must be specified as destinations |
CONSOLE | Output to the console of the system operator; the application name is also output |
PARTNER | Output to clients connected via a PTERM or a TPOOL with PTYPE=APPLI or SOCKET (except HTTP clients). |
SYSLOG | Output to the system log file (see section "UTM log file SYSLOG"). |
MSGTAC | Output to the MSGTAC program unit (see section “MSGTAC event service” in the openUTM manual „Programming Applications with KDCS”). |
USER-DEST-1 to USER-DEST-4 | |
Output to user-specific message destinations to which you can assign a USER queue, a TAC queue, an asynchronous TAC or an LTERM partner as concrete message destinations at generation time. Either cyclically or when requested by the user, WinAdmin and WebAdmin can retrieve messages from these UTM queues, output these in lists and save them in the configuration database if required. For details, see online help for WinAdmin/WebAdmin, keyword „message collectors“. The assignment between USER-DEST-1..4 and the concrete destination is defined by means of the KDCDEF statement MSG-DEST. | |