openUTM generates messages while an application is active. K messages and P messages are sent to one or more of the following destinations:
STDOUT | Output to stdout. |
STDERR | Output to stderr. |
STATION | Output to clients connected by means of a PTERM or a TPOOL with PTYPE=TTY. |
SYSLINE | Output to the system line of the data display terminal. If a message is to be output to the system line, both SYSLINE and STATION must be specified as destinations. System line messages are attached to the output from the dialog program, i.e. output in the following line. |
CONSOLE | Output to the console of the system operator; the application name is also output. |
PARTNER | Output to clients connected by means of a PTERM or a TPOOL with PTYPE=APPLI or SOCKET (except HTTP clients). |
SYSLOG | Output to the system log file SYSLOG (see "UTM log file SYSLOG"). |
MSGTAC | Output to the MSGTAC service (see section "MSGTAC event service" of 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 UTM 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 specified by means of the KDCDEF statement MSG-DEST. | |
U messages are only sent to STDOUT, STDERR and SYSLOG.