How can I understand some of the common terminology for CA Datacom/DB and CA Datacom/AD?

Document ID : KB000020806
Last Modified Date : 14/02/2018
Show Technical Document Details


CA Datacom/AD and CA Datacom/DB have some specific terms to describe the components and the processing of the software. How can I understand the meaning and usage of some of the more common terms?


Are you new to CA Datacom, or are you confused by some of the terminology you read in the manuals or in your contact with the CA Datacom support team? Here are some terms that have a close similarity to commonly understood z/OS terms:


The MUF (Multi-User) is the manager of the system. It receives a request from the application and determines how it should be processed. It coordinates the activities that must take place to service the request.

The MUF runs in a separate region in the z/OS and z/VSE environments. The required space for the MUF region varies according to the MUF startup options.


Is similar to the OS CATALOG, and holds information about all the databases in the Multi-User Facility (MUF)


Is like an OS DATASET and is the smallest unit of data that is accessed by physical open, read and write functions


Contain logging and recovery information, like SMF records file update information


Is like SYS1.DUMP in that it holds dump and control block information for failed tasks


Is a work area in the MUF to process a logical unit of work, like the z/OS INITIATOR


Manages which database tables are accessed and how, just as JCL manages files, for a particular program


Asks the MUF to tell what is happening "right now," just as D A shows all the jobs running in the system


Is a command to stop the MUF, similar to the P jobname command


Is similar to the DUMP jobname command, but specific to the MUF


Identifies a particular unit of work, just as the JES # identifies the job or task