1. ZEUS

2. zVDB
What is ZEUS?
CICS
PROGRAM PRODUCT
IMS/DC
TSO
BATCH APPLICATION MQ
APPLICATION DBMS
VSAM,
FLAT FILES
ADABAS,
SQL DBMS
IMS/DB
DB2
OTHER
zOS DATA
A subsystem for the componentization and integration of mainframe applications, processes, transactions and data from all sources and of all types.

3. What is zVDB? ZEUS himself pulls a VDB table out of a hat! zVDB
zVDB is an AI-based program product that instantiates and manages VDB virtual relational tables and VDB databases in response to client SQL requests.
zVDB is a magic-based program product wherein
ZEUS himself pulls a VDB table out of a hat!

4. VIRTUAL RELATIONAL TABLE?
zVDB
WHAT IS A zVDB
VIRTUAL RELATIONAL TABLE?
COLUMN 2
COLUMN 1
COLUMN 3
COLUMN 4
COLUMN 5
COLUMN 6
COLUMN n
CICS
PROGRAM PRODUCT
IMS/DC MQ
IMS/DB
DB2
VSAM
In a zVDB dynamic virtual table any column can come from
any data source across the enterprise of zOS systems.

5. HOW DOES zVDB INSTANTIATE A VIRTUAL TABLE?
DATASTREAM
CLIENT-SERVER
DIALOG
DATA
SOURCE
APPLICATION
||VARIABLE 2 | VARIABLE 1| VARIABLE 3 ||
zVDB Virtual Table
Interact and with the data source application, database or file while tracing the dialog.
Parse the interaction datastreams from the data source for data variables.
Define the VDB virtual table by assigning parsed variables as column names in the virtual table
VARIABLE 1 2 3

6. zVDB RUNTIME LOGIC Assign Client request a dedicated subtask
Receive client SQL request (TCP/IP or SNA LU2 or LU6.2).
Assign Client request a dedicated subtask
From dialog recording metadata, build and orchestrate a navigation plan, based
on the input column values specified in the client SQL request, which will derive
the variables, which are columns in the VDB virtual table.
Execute the navigation plan.
Instantiate the VDB virtual table.
(a) Insert the new table into zVDB Virtual Database in DB2.
and/or
(b) Interact with Client ODBC to select table.
(c) Transmit datastream with VDB table rows.

7. zVDB INTERNAL PROCESSING
ZEUS maintask initializes the zVBD environment by attaching its dedicated subtasks: TCP/IP, VTAM, Console, SRM, Project
Request processing executes through a zero wait state thread dispatcher.
ZEUS handles all memory allocation/deallocation, control block requests and deletions.
Both ZEUS and zVDB have been developed based on a highly abstracted hierarchical API architecture. All zVDB API’s are included in the ZEUS API set.
(continued)

8. zVDB INTERNAL PROCESSING (continued)
zVDB metadata is organized in a set of related tables. This metadata defines everything about the applications, the data, the orchestration plans, the data variables, the virtual tables, the dialogs, the screen and buffer formats for the dialogs (3270 screens for LU2), stored SQL procedures.
zVDB has a complete emulation of both SNA LU2 protocol and protocol.
TCP/IP and VTAM subtasks have their own listeners to detect requests.
When a request is received a dedicated subtask is assigned to the request until it has completed processing.
(continued)

9. zVDB INTERNAL PROCESSING (continued)
249 subtasks out of the zOS max of 255 are available for parallel processing in ZEUS. zVDB allocates one subtask per user.
Since client interaction with applications and data sources executes at machine speeds, response times are solely a factor of the end server processing time.
Both ZEUS and zVDB have been tuned down to the instruction level and all activities within the systems have been optimized for minimum resource consumption and maximum throughput.
zVDB to zVDB communications enable transfer of all metadata between ZEUS subsystems, i.e. sending test system metadata to production system.

10. ZEUS™
zVDB™