About This Version

In CA WA CA 7 Edition Version 12.0, the primary repository of scheduling data (workload definitions, active workload status records, and workload history) is a CA Datacom database. This document assumes that you use the CA Datacom/AD common component.

In earlier versions, scheduling data was stored in various formats in VSAM and direct-access files. These files were allocated to the programs needing access to the data such as CA7ONL, JFI, DBVR, and others.

CA WA CA 7 Edition programs no longer allocate the repository. Instead, they access data through a CA Datacom/AD address space known as a Multi-User Facility or MUF. The MUF allocates the database and handles requests for access using either cross-memory services or XCF depending on the location of the requesting program.

Each database that a MUF supports is assigned a number that is known as a DBID. DBID=770 identifies the database reserved for use with CA WA CA 7 Edition. A MUF contains only one such DBID 770 database; however it can be shared among multiple instances of CA WA CA 7 Edition.

Each instance is restricted to a subset of the database known as a logical database. The name of the logical database is a required parameter for programs that access scheduling data (this parameter is provided in the DBPARMS input). The key that the program constructs begins with this logical database name. This effectively partitions the physical database into subsets or logical databases.

Thus to access scheduling data in this version, a CA WA CA 7 Edition program (like UCC7) must:

Identify the MUF that allocates the physical database containing the scheduling data. This identification is accomplished by including selected MUF data sets in the load library concatenation of the program.
Target a subset of the physical database by providing the logical database name as an input parameter to the program (DBPARMS).

These issues are discussed in greater detail later in this document.