BOI Software Entwicklung und Vertrieb GmbH

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

Spazgasse 4


4040 Linz, Austria

Steps needed before using SHS data spaces in TABEX/4 Windows

How are SHS data spaces implemented in TABEX/4 Windows?

SHS data spaces are implemented as shared memory segments using Windows file mapping objects.

The following configurations must be set so that the TABEX/4 services and programs can process these global system objects in newer Windows versions.

Windows permissions

The user IDs under which the TABEX/4 services, batch and console programs run, must have the Windows permission "create global objects".


fig. generation of global objects

TABEX/4 system parameters

In the TABEX/4 system parameters (file boiparam.txt in the TABEX/4 subdirectory "sys") the entry WINOBJ must have the prefix "Global\", so that objects are addressed in the global namespace and not objects in the own session.

The required entry may already be listed within comment brackets in the parameter file.

In this case, the desired entry shall be activated by removing the comment brackets. The previous entry shall be deactivated by adding the comment brackets, so that it becomes inactive.

Otherwise, the entry must be changed (if it already exists) or added, if it does not yet exist.

fig. boiparam.txt


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