BOI Software Entwicklung und Vertrieb GmbH

Phone: +43 (0) 732 / 736423 - 0

Spazgasse 4


4040 Linz, Austria

What to do if the TABEX/4 browser application is timed out and all open databases are locked by the monitor after cancellation?


If a time-out occurs, the monitor can only cancel the session. Normally database locks remain during crashes (for example, at abends, or when a TSO user is automatically logged out).

For operations with multiple databases it cannot be trusted, that all of the update processes have already been carried out. Therefore, a check and manual unlock(s) are necessary.

You can define the maximum time that the monitor waits until a session is canceled in the parameter monitor MON-TIMEOUT-RUNAWAY-SEC (in seconds).

Client-side the timeout is defined in in parameter montimeout. It might make sense to configure a larger value for the timeout.

The relationships between the different timeout parameters are described in the documentation.

Otherwise, there is theoretically the possibility to carry out the complex check asynchronously, and e.g. check every few seconds if there is already a result.


BOIDOC_209a_config_en.pdf, chapter Timeout configuration

Migration Packages

BOI GmbH offers migration packages for the table management systems SPITAB, TABSYS and VTAS.


» Migrations Packages

Success Stories

AirPlus has been using TABEX for 20 years.

Now TABEX/4 JAVA APPLICATION ENGINE has additionally been launched for audit-proof logging of the business processes by Java applications.


» read this success story

» more success stories