Multiple Source and Working Object Databases

Multiple Source Object databases can be defined for Control-O/COSMOS objects. The number of Source Object databases appropriate for your site depends on the nature of the objects to be managed and the way in which Control-O/COSMOS is to be implemented. Definition of multiple Source Object databases enables you to:

• Separate objects of different types (for example, started tasks and VTAM LUs).
• Specify different UP/DOWN status names. For example, for objects of a certain type ONLINE/OFFLINE or ACTIVE/INACTIVE may be appropriate.
• Define different columns in the Object databases. For example, a column for started task objects containing the open reply ID of the started task (if any). A reply ID is meaningful only for a started task but is meaningless for a VTAM LU.

Objects defined in each Source Object database are copied to Working Object databases when Control-O/COSMOS is initialized.

In a multi-CPU environment, a single Source Object database (stored on disk) can be used to generate a Working Object database (in memory only) in each CPU. This simplifies object management by enabling management of Object databases in multiple CPUs using a single central file (meaning, a Source Object database).