Previous Topic: How Persistent Data WorksNext Topic: DATALIB Members


Persistent Data Store Components

The persistent data store contains the following components:

DATALIB

Stores and maintains all information about the data objects. You can have one or multiple DATALIB data sets. Any one instance of SYSVIEW can use only one DATALIB.

The administrator can determine whether to have a unique DATALIB for each instance of SYSVIEW or share one of the DATALIBs.

One CA SYSVIEW can use only one DATALIB. You can share a DATALIB within a sysplex but not across multiple sysplexes. Multiple releases of CA SYSVIEW can share the DATALIB, making migration to a new release easier.

Data Store

Serves as the repository for data objects. The data store is a standard PDSE data set allocated during installation. At completion of the installation process, the data set is empty. No initial data is required nor is any data shipped with the product.

Data Object

Contains any logical piece of data.

DataId

Specifies the internal data identifier of the data object maintained by the data store.

DataKey

Specifies the data object key that the data store maintains. The DataKey includes the DataId plus additional information to help ensure a unique key across multiple instances of CA SYSVIEW.

Logical Components

Lets CA SYSVIEW components read and write to and from the data store through programs or callable subroutines.