Creating and Maintaining Object Databases

Control-O/COSMOS Object databases contain information about the objects (started tasks, terminals, and so on) managed by Control-O/COSMOS.

Object databases are normally created in pairs. Each pair consists of the following:

• Source Object database

  Contains all object names and pertinent information as a permanent database.

• Working Object database

  Working copy of the Source Object database used to manage objects during Control-O/COSMOS operations. This copy is modified by Control-O/COSMOS at regular intervals to reflect changes in the production environment.

Working Object databases are required and are used by Control-O/COSMOS. Source Object databases can be used, but are not required.

Control-O/COSMOS determines what actions are performed, by scanning the Working Object databases. All information in the Working Object databases is copied from the Source Object database each time Control-O/COSMOS is activated. You can use other means to create the Working Object database. For example, the Working Object database can be created dynamically.

Creating rows with a rule can create a Working Object database. For example, an operator command can be issued to display objects and a command response can be used to add rows to the list of objects to be managed.

An Object database, describing started task (STC) objects at your site, can be created using the SYSIMAGE facility, and can be maintained through the Variable Database Definition facility. This Object database can be modified, and other Object databases can be created, using the Variable Database facility.

Maintaining separate Source and Working Object databases provides the following advantages:

• Saves disk space.

  The Working Object database contains much information that is meaningless after Control-O/COSMOS is brought down. The Source Object database contains only the information necessary for re-creation of Working Object databases.

• Enables management of objects using one Source Object database.

  The Source Object database is used to upload information for multiple Working Object databases (that is, one on each CPU) when Control-O/COSMOS is started. Using one Source Object database avoids duplicate definitions in multi-CPU and Sysplex environments.

Example

VTAM normally depends on JES2 no matter which CPU of the system is involved. Therefore, if an object named JES2 is appropriately defined in the Source Object database, the definition of JES2 is copied to the Working Object database of every CPU.