With the KDCOUT command, the user can request the output of asynchronous messages.
openUTM announces asynchronous messages with the following message:
K012 nnn asynchronous message(s) present
The UTM message appears in the system line together with a dialog output at this terminal. The number of asynchronous messages is specified with nnn. The user can retrieve these messages using the KDCOUT command. If there are no messages for the terminal when KDCOUT is entered, openUTM outputs the UTM message:
K020 No message(s) present
When an asynchronous message is retrieved with KDCOUT, it is deleted by the next input, except when KDCLAST is entered (see "KDCLAST - repeat the last output").
The result of the KDCDEF statement LTERM ..., RESTART= NO is that any pending asynchronous messages are deleted when the connection is set up or shut down to this LTERM partner.
The function variants of openUTM have the following effects on the handling of asynchronous messages:
With UTM-S applications, asynchronous messages are logged even if the application run is interrupted and are retained until retrieved with KDCOUT.
With UTM-F applications, asynchronous messages are only stored during the application run. They are lost when the application run terminates.