Output From IMBS Macro

Transparency Programs and Macros › Output From IMBS Macro— IMBSTAB

Output From IMBS Macro— IMBSTAB

IMBSTAB is an Assembler program module generated by the IMBS macro. It consists of storage (DS) and storage constants (DC), in the form of tables and buffers. IMBSTAB:

Supplies IMBSPROC with information needed to move pointers for current records from the CA IDMS/DB subschema table into the dummy CA IDMS/DB record
Provides IMBSBRDG with information needed to build DBOMP records from retrieved CA IDMS/DB records
Supplies IMBSBRDG with the information needed to return updated records from the user work area to the CA IDMS/DB database

The IMBSTAB module contains the following four tables:

Table	Contains:
Control table	Control information
Set table	An entry for each set described to the IMBS macro
Pointer table	Pointers for each set described to the IMBS macro; the groups of pointers are in the same order as the corresponding sets in the set table.
File table	A group of entries for each file described to the IMBS macro

The control table, set table, pointer table, and file table layouts are shown in the figures on the following pages.

Control Table

Set Table

The set table contains one entry for each set described to the IMBS macro.

Set Table

Pointer Table

The pointer table contains one group of pointers (owner, prior, current, and next) for each set described to the IMBS macro, in the same order as the sets to which they correspond are named in the set table.

Pointer Table

File Table

The file table contains one group of entries for each DBOMP file and corresponding CA IDMS/DB record type described to the IMBS macro.

File Table

The IMBS macro generates a CA IDMS/DB logical record buffer from which the bridge program constructs the DBOMP logical record. The size of this buffer is equivalent to the size of the largest CA IDMS/DB record described in the file table.

Assembling and Linking IMBSTAB

You can reassemble IMBSTAB as often as you like. This allows you to change control information and accommodate the requirements of multiple DBOMP applications. The information most likely to vary is the program name, the usage mode, the name of the record for which RACN is to be maintained, and the CATALR option (Z/VSE only).

Each time you change any input statements, do the following:

Submit all of the IMBS input statements.
Link edit IMBSTAB to the library containing IMBSBRDG.

For the JCL you use to assemble and link edit the IMBSTAB module, see Using the Transparency as a Bridge to CA IDMS/DB.

The following flowchart illustrates IMBSTAB assembly and linkage.