The Status-RTM message is sent to the application by the local node to indicate the Response Time Monitor (RTM) parameters being used by the host. The host can specify the following parameters:
Until the first character of a response is written to the screen.
Until the keyboard is unlocked.
Until the application is allowed to send data (CD or EB received).
The local node is responsible for interpreting the response times reported to it by the application, and for sending RTM statistics to the host when required; the application is responsible for measuring the response times and reporting them to the local node. (The application reports response times to the local node using the Status-Acknowledge message—see Response Time Monitor Data for more information on measuring and reporting response times).
If the application does not wish to provide a local display of RTM data, it only needs to determine whether RTM measurement is active and, if so, the definition by which response times are measured; it can ignore the other parameters. If RTM measurement is not active, the application need not measure and report response times.
If the application wishes to provide a local display of RTM data, it should use the information from the Status-RTM message to ensure that the local interpretation of response times matches the interpretation used by the host. In particular, it should not display RTM data at all if the Status-RTM message indicates that local display is not permitted (or if the "permission to view RTM data" field in the 3270 user configuration record indicates that it is not permitted). The application is responsible for maintaining its own RTM statistics for local display; that is, for classifying the response times according to the boundaries specified by the host and maintaining counts of responses in each category. Although the local node maintains these statistics for sending to the host when required, it does not report them to the application.
Note RTM statistics are maintained for a specific LU, not for a specific application's use of that LU. This means that when the Status-RTM message is received at start of day the counters can be nonzero to include a previous use of the LU. The counters are only reset when the host requests the local node to reset them or when the local node sends unsolicited RTM data to the host.