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 enlarge TABEX databases which are no protocol databases?

Enlarging protocol databases

Fpr TABEX databases which are used as protocol databases (TABPRO, TABCMP, TABPCA) there is a separate method (see How to reorganize or enlarge protocol databases TABPRO or TABCMP?) The method described below MUST NOT be used for protocol data or otherwise data are lost.

Enlarging TABEX databases

The procedure described below relates to 'normal' TABEX databases with or without compressing and random databases with or without compressing.

Since TABEX mass databases automatically expand, an enlargement by using TABEX is not possible. Should it be necessary to construct another base file for a TABEX mass database (for eample VSAM cluster), this approach can also be applied to this type of database.

For TABEX databases which are used as protocol databases (TABPRO, TABCMP, TABPCA) there is a special procedure (see "How to reorganize or enlarge protocol databases TABPRO or TABCMP?"). The method described below MUST NOT be used for protocol databases or otherwise data are lost.

Method 1

Step 1

Backup data in a TABEX SAVE file using utility TABN03:

  • Option 1 - only active data is saved:

    SAVE

  • Option 2 - overwritten versions are also saved:

    SAVE,,ALL

Attention: Deleted versions are not backed up with either of the two options

Step 2

If necessary, crate an appropriate file (for example VSAM cluster) in the file system.

Step 3

Initialize the TABEX database of desired type and suitable size with TABN01-INIT.

Step 4

Import the SAVE file created in step 1 with TABN01-LOADDB.

Method 2

This method can be used from TABEX version 3.2.0.

In this method, saving is performed as general database objects. In contrast to method 1 above:

  • table status entries text tables and AI tables are written into the SAVE file even if there is no correspondingdata table.
  • status entries of all types (not only table status entries but also protocol entries) are written into the SAVE file.

Step 1

Backupu data in a TABEX SAVE file with utility TABN03:

  • Option1 - only active data is saved:

      DBOSELECT,**********,**,VAL
      DBOSAVE

  • Variante 2 - overwritten versions are also saved:

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

Attention: Deleted versions are not backed up with either of the two options.

Step 2

If necessary, create an appropriate file (for example VSAM cluster) in the file system.

Step 3

Initialize the TABEX database with desired type and suitable size with TABN01-INIT.

Schritt 4

Import the SAVE file created in step 1 with TABN01-DBOLOAD.

Documentation

BOIDOC_206_utility_en.pdf

Valid from

TABEX/4 Version 3.2.0

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