Szerkesztés

Megosztás a következőn keresztül:

Response Time Monitor Data

  • Cikk

For a 3270 display application, the local node maintains statistics on host response times—the time it takes the host to respond after the 3270 user presses ENTER or an AID key to send data to the host. These statistics can then be sent to the host for analysis.

The Status-RTM message, sent by the local node to the application, informs the application of the Response Time Monitor (RTM) parameters specified by the host. (For more information, see RTM Parameters.) These parameters specify whether RTM data is to be collected, whether the application is permitted to display RTM statistics locally, the time boundaries by which response times are to be grouped, and the definition of response time. The time can be measured until the first character of the host response reaches the screen, until the keyboard is unlocked, or until the user can send further data (change direction (CD) or end bracket (EB) received by the application).

If the host specifies that response times are to be measured for this session, the application is responsible for measuring response times and for reporting them to the local node. This involves:

  • Starting a timer when the user presses the ENTER key or an AID key to send data to the host.

  • Stopping the timer when the host's response to the inbound data is received, as defined by the RTM definition specified on the Status-RTM message.

  • Reporting the response time to the host on the Status-Acknowledge(Ack) message, which acknowledges the host's response. One of the fields on this message specifies the last response time measured by the application, or specifies that no response time is to be reported.

  • Optionally displaying the most recent response time as a last transaction time indicator (LTTI) on the 3270 emulation status line.

    If the application wants to provide a local display of RTM data, it is responsible for maintaining its own response time statistics. It should use the same definition and boundaries as those specified on the Status-RTM message to ensure that the local data matches the data sent to the host by the local node. Note that the Status-RTM message can indicate that a local display of response times is not permitted. In this case, the application should not display either the response times or the LTTI.

See Also

Opening the PLU Connection
Closing the PLU Connection
PLU Session
Outbound Chaining
Inbound Chaining
Segment Delivery
Brackets
Direction
Pacing and Chunking
Confirmation and Rejection of Data]
Shutdown and Quiesce
Recovery
Application-Initiated Termination
LUSTATs]