Modifed June 2017 (added second paragraph to Comments)
xcall MIAMEX, MX_IATIMEOUT, opcode, timesecs
MX_IATIMEOUT (MIAMEX 180) allows querying / setting the inactivity timeout.
This function has both a subroutine and a print tab implementation.
Parameters
opcode (Num) [in]
0 (mxop_get) to retrieve, 1 (mxop_set) to set
timesecs (Num) [in, out]
Timeout value in seconds. If opcode=0, the current timeout setting (or zero if disabled) is returned here. Otherwise the value passed in timesecs is used to reconfigure the current inactivity timer.
Comments
Note that unlike the case in miame.ini IATIMEOUT property, which uses units of minutes, the MX_IATIMEOUT function uses units of seconds.
In ATE GUI environments, chances are that an inactivity timeout will occur while the ATE client is waiting on input within a local client context, in which case it will not detect that the server-side process received a timeout signal, or even that the connection has been terminated from the server side. To avoid that, set the inactivity timeout on the client (using AG_IATIMEOUT) rather than on the server side. Such a timeout will cause ATE to initiate a disconnect, which will generate a SIGHUP signal sent to the application process on the server, resulting in error 250.
See Also
| • | AG_IATIMEOUT to set the inactivity timeout on the ATE client |
