Matrix © Concepts
The OS/390 and z/OS based enterprise technologies were conceived to provide applications programs with almost unlimited storage and computing capacity, as well as security and reliability. Much of the power of the system is hidden from applications programmers. The applications programmer does not have access to many of the systems functions that make such things as data spaces and sysplex inter-systems communications possible. Through a simple API applications programmers can use Matrix © to provide up to half a terabyte of data spaces with in their own address space and up to half a terabyte of shared dataspaces, per system in a sysplex. The dataspaces can be used to hold database items and indeces for high performance data delivery and lookup.
An application can simultaneaously work with dataspaces that are privately held in the address space of the application, shared among all applications and shared among all systems.
Tables
Matrix © enables you to format Vitual Work Areas into tables and arrays. The components of tables may potentially reside in any address space in any CPU in a sysplex. Tables may be Private, or Shared. Private tables may use Private or Shared data repositories. Shared data repositories may reside anywhere in a sysplex and may also be mirrored in all systems.
Example A: An application program on SYSB creates a shared Virtual Work Area called DATA and loads it with data from a file. When it has finished loading the data, it POSTs a cross systems event to indicate the data is ready. On SYSA an applications program creates a private work area, called INDX to use as a high performance index. It WAITs until the cross systems event has been POSTed. When it has, the application on SYSA creates a table from the private INDX and shared DATA work areas. When the application needs to access the table it reads the index from the private VWA in its own address space and it reads the data from SYSB.
Example B: An application program on SYSB creates two shared Virtual Work Areas called IND2 and DAT2 and loads them with data from a file. When it has finished loading the data, it creates a shared table then POSTs a cross systems event to indicate the table is ready. On SYSA an applications program waits until the cross systems event has been POSTed. When it has, the application on SYSA connects to the table. When the application needs to access the table it reads the index and data from SYSB.
