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


Changes in ESA data spaces, efficient migration and a new success story: Learn more in our newsletter!


Migration Packages

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


» Migration Packages

Success Stories

GDIS and BOI: Carrying on the Success

With TABEX4 JTC, GDIS has introduced the world's fastest Java interface for table access on customer and control data. Learn the details in our new Success Story.


» read this Success Story

» read more Success Stories