BOI Software Entwicklung und Vertrieb GmbH

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

Spazgasse 4


4040 Linz, Austria

How to program user exits?

What are Exits?

Exits are SSL programs, which can be integrated into TABEX/4 by the customer to execute checks, postprocessing, and other functions of their own.

SSL (Single Source Language), theTABEX/4 internal programming language, also offers the possibility to call external programs(PL/I, Cobol etc.).

Besides the exit features such as protocol exits, security exits and menu exits,TABEX/4 offers a wide spectrum of extensibilities.

Spectrum of user exits

The following enumeration gives you an overview of the various possibilities where customer exit
programs can be integrated into the TABEX/4 Table Manager:

  1. at instance initialization (after loading the instance configuration table)
  2. setting a value of a system parameter
  3. after selection of a menu item
  4. creation of a TABEX view statement for dynamic view display
  5. security checks
  6. specification of an SSL program as handler for a customer specific icon
  7. after selection of a TABEX table from the TABEX database index
  8. specification a new table version date
  9. after committing an update of a TABEX table
  10. after online transfer from the modification database to the production database
  11. definition of views for the loading of data from relational databases (with technical fields when versioning of table rows)
  12. after loading data from relational databases
  13. before updating date into relational databases
  14. assignment of job parameter values
  15. protocol exits, if logging is enabled inside the web application, and for the commands of utilities TBVW01 and TBVW02. Protocol exits can be called using any menu item which changes tables. (The names of the customer specific MOD-IDs must begin with 'MY'.)
  16. evaluation of the tableID for the next step of a table sequence

TABEX/4 offers interface functions for exit programming:

  1. query of the active instance
  2. query of the active database
  3. deletion of the active TABEX table index, so that the system must reconstruct this index
  4. query of the table status
  5. writing customer data (10 bytes) into the table status
  6. methods for output of text and messages
  7. starting of jobs
  8. query of values of system parameters
  9. query of module parameters
  10. establishing a connection to a relational database
  11. loading an RDB table as TABEX DB into memory
  12. query of the MOD-ID
  13. query of table authorizations
  14. query of release policy

BOIDOC_209a_config_en.pdf, chapter User exits

Valid from

TABEX/4 Version 4.1.1


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