BOI Software Entwicklung und Vertrieb GmbH

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

Spazgasse 4

Email: office@boi.at

4040 Linz, Austria

www.boi.at

How to reorganize or enlarge protocol databases TABPRO and TABCMP?

Reorganize or enlarge protocol databases TABPRO or TABCMP

On the one hand, the databases TABPRO and TABCMP contain special entries (protocol entries), which are not processed by "normal" reorganization. On the other hand, the data of both databases belong to each other. Therefore the databases TABPRO and TABCMP may not be reorganized with the utility commands TABN03-SAVE and TABN01-LOADDB. This is also described in BOIDOC-209a and BOIDOC-206.

If the amout of data in TABPRO and/or TABCMP becomes too large or if the datbases are full, the following options are available:

Enlarge the databases TABPRO and TABCMP

To enlarge the databases TABPRO and/or TABCMP, the following steps have to be performed:

  1. Generate a Reo file with all entries and tables with the following TABN03 commands:

    DBOSELECT,**********,**,ALL
    DBOSAVE

  2. Create a database of the desired size (TABN01-INIT): This should be standard databases WITH compression for both TABPRO and TABCMP (Init type 'T3C', this is the default for TABN01-INIT).
  3. Load all data with the TABN01 command TABN01-DBOLOAD from the Reo file generated in step 1 into the database generated in step 2.

The amount of data expected in the protocol databases TABPRO and TABCMP is described in article What amount of data is to be expected in the protocol databases TABPRO and TABCMP?

Documentation

BOIDOC_206_utility_en.pdf

News

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

11.07.2018

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