# MX\_IATIMEOUT

> [HTML Version](mx_iatimeout.htm)

_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](subroutine-print-pairs.htm.md).

**Parameters**

_opcode_  ([Num](num.htm.md))  \[in\]

0 (mxop\_get) to retrieve, 1 (mxop\_set) to set

_timesecs  _([Num](num.htm.md))  \[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](ag_iatimeout.htm.md)

•	[IATIMEOUT](iatimeout_sp.htm.md)[sp](keyword-types.htm.md) 

•	[Trapping Timeouts and Closed Windows](trappingtimeoutsand.htm.md)