BOI Software Entwicklung und Vertrieb GmbH

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

Spazgasse 4

Email: office@boi.at

4040 Linz, Austria

www.boi.at

Which allocation levels are available for TABEX databases?

General

When a user logs in, a new TABEX/4 monitor session is started where a step-wise allocation of databases is carried out.

The levels of the allocation are:

  1. monitor allocation script (z/OS) or JCL file (Unix, Linux, Windows)
  2. dynamic allocation table of the session (sysparm settings)
  3. dynamic allocation table of the user (user profile settings)
  4. dynamic allocation table of the instance (instance configuration settings)

By implementing exits, further levels of the allocation can be defined by the customer.

Level 1: monitor allocation script (z/OS) or JCL file (Unix, Linux, Windows)

After the monitor has started a new session, the session reads a script/JCL file and executes the commands defined in this file.

See BOIDOC_226_tcpip-monitor_en (for z/OS) and BOIDOC_224_cs_admin_en (for Windows, Unix, Linux) and the example for level 1 (see below).

Level 2: dynamic allocation table of the session (sysparm settings)

If the keyword SESALCID for a dynamic allocation table of the session is fond in sysparm, additional session allocations are read from a TABEX table and executed.

See BOIDOC_209a_config_en, chapter Configuration of the TABEX/4 Web Application, subsection Settings of the TABEX monitor,  sysparm entry SESALCID and the example for level 2 (see below).

Level 3: dynamic allocation table of the user (user profile settings)

If the keyword DYNALC is found in the user profile (or in a copybook, which is included in the user's profile), additional user-specific allocations are read from a TABEX table and executed.

See BOIDOC_209a_config_en, chapter Overview of the control parameters, subsection User profile parameters (only in user profiles), enty DYNALC and the example for level 3 (see below).

Level 4: dynamic allocation table of the instance (instance configuration settings)

If the keyword DYNALC is found in the instance configuration table, additional instance-specific allocations are read from a TABEX table and executed.

See BOIDOC_209a_config_en, chapter Overview of the control parameters, subsection Instance parameters (only in instance configuration), entry DYNALC and the example for level 4 (see below).

Further levels of the allocation defined by the customer (exit implementation)

Additional allocations can be implemented as customer exits, for example by an instance initialization exit between the levels 3 and 4.

See BOIDOC_209a_config_en, chapter Overview of the control parameters, subsection System parameters, entry EXITIINIT.

Allocations of the TABEX/4 databases delivered by BOI

The followin TABEX databases and the associated chain databases must be allocated in level 1:

INTSRC

INTMOD

OPSMSG

TABLGG, TABLGE

The following TABEX databases and the associated chain databases must be allocated at the latest in level 3:

TABCTL

APPLGG, APPLGE

TABTMP

Allocation example level 1

Monitor allocation script for z/OS

ALLOC FI(INTSRC) DA(TABEX4.CUST.INTSRC) SHR
ALLOC FI(INTMOD) DA(TABEX4.CUST.INTMOD) SHR
ALLOC FI(OPSMSG) DA(TABEX4.CUST.OPSMSG) SHR
ALLOC FI(TABLGG) DA(TABEX4.CUST.TABLGG) SHR
ALLOC FI(TABLGE) DA(TABEX4.CUST.APPLGG) SHR
ALLOC FI(TABCTL) DA(TABEX4.CUST.TABCTL) SHR
ALLOC FI(APPLGG) DA(TABEX4.CUST.APPLGG) SHR
ALLOC FI(APPLGE) DA(TABEX4.CUST.APPLGE) SHR
ALLOC FI(INTSRC1) DA(TABEX4.BOI.INTSRC) SHR
ALLOC FI(INTMOD1) DA(TABEX4.BOI.INTMOD) SHR
ALLOC FI(OPSMSG1) DA(TABEX4.BOI.OPSMSG) SHR
ALLOC FI(TABLGG1) DA(TABEX4.BOI.TABLGG) SHR
ALLOC FI(TABLGE1) DA(TABEX4.BOI.APPLGG) SHR
ALLOC FI(TABCTL1) DA(TABEX4.BOI.TABCTL) SHR
ALLOC FI(APPLGG1) DA(TABEX4.BOI.APPLGG) SHR
ALLOC FI(APPLGE1) DA(TABEX4.BOI.APPLGE) SHR

JCL file for Unix, Linux, Windows

FILE = INTSRC '<tabexcus>/.tdb'<tdb>
FILE = INTMOD '<tabexcus>/.tdb' <tdb>
FILE = OPSMSG '<tabexcus>/.tdb' <tdb>
FILE = TABLGG '<tabexcln>/.tdb' <tdb>
FILE = TABLGE '<tabexcln>/.tdb' <tdb>
FILE = TABCTL '<tabexcus>/.tdb' <tdb>
FILE = APPLGG '<tabexcln>/.tdb' <tdb>
FILE = APPLGE '<tabexcln>/.tdb' <tdb>
FILE = INTSRC1 '<tabextdb>/INTSRC.tdb' <tdb>
FILE = INTMOD1 '<tabextdb>/INTMOD.tdb' <tdb>
FILE = OPSMSG1 '<tabextdb>/OPSMSG.tdb' <tdb>
FILE = TABLGG1 '<tabexlng>/TABLGG.tdb' <tdb>
FILE = TABLGE1 '<tabexlng>/TABLGE.tdb' <tdb>
FILE = TABCTL1 '<tabextdb>/TABCTL.tdb' <tdb>
FILE = APPLGG1 '<tabexlng>/APPLGG.tdb' <tdb>
FILE = APPLGE1 '<tabexlng>/APPLGE.tdb' <tdb>

Allocation example level 2

Eintrag in boiadmin.properties

sysparm = SESALCID=XY

By using this entry in the boiadmin.properties the single version table $TABI4ATXY is searched in the OPSMSG database and the allocations in the table are performed.

The contents of the single version table $TABI4ATXY for z/OS looks like the monitor allocation script for z/OS, and for Unix, Linux, Windows it looks like the JCL file for Unix, Linux, Windows, but not the same databases as in level 1 may be allocated.

Allocation example level 3

Entry in user profile of user BOI

The entry DYNALC = DYNALC_BOI-99999999(OPSMSG) in the user profile of user BOI has the following effect: the single version table DYNALC_BOI is searched in the database OPSMSG die and the allocations defined in this table are executed.

The contents of the single version table DYNALC_BOI for z/OS looks like the monitor allocation script for z/OS, and for Unix, Linux, Windows it looks like the JCL file for Unix, Linux, Windows, but not the same databases as in level 1 and level 2 may be allocated.

Allocation example level 4

Entry in the instance configuration table

By entering DYNALC = DYN_INST05-99999999(OPSMSG) in the instance configuration of the instance $ICFG_005 the single version table DYN_INST05 is searched in the database OPSMSG and the allocations defined in this table are executed.

The contents of the single version table DYN_INST05 for z/OS looks like the monitor allocation script for z/OS, and for Unix, Linux, Windows it looks like the JCL file for Unix, Linux, Windows, but notthe same databases as in level 1 to 3 may be allocated.

Documentation

BOIDOC_209a_config_en.pdf, chapter  Stages of file allocation

Valid from

TABEX/4 Version 4.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