CICS domains
At the top level, CICS® is organized into domains. With the exception of the application domain, which contains several components, each domain is a single major component of CICS.
Domains never communicate directly with each other. Calls between
domains are routed through kernel linkage routines. Calls can be made
only to official interfaces to the domains, and they must use the
correct protocols. This structure is shown in Figure 1.
Figure 1. CICS organization—domains
Each domain manages its own data. No domain accesses another
domain's data directly. If a domain needs data belonging to
another domain, it must call that domain, and that domain then passes
the data back in the caller's parameter area. 
The CICS domains are shipped as object code only (OCO); no source code is available for the domains.
The following table lists the CICS domains alphabetically by domain identifier. For each domain, the table also shows whether or not the domain is OCO, and gives a reference to the section describing the interfaces to the domain.
Note: The
application domain is mainly non-OCO, but it contains these OCO components:
- CICS data table services
- RDO for VSAM files and LSR pools
- Some EXEC CICS system programming functions
- Autoinstall terminal model manager
- Partner resource manager
- SAA Communications and Resource Recovery
- Some of the file control functions
- Recovery manager connectors interfaces.
The offline statistics utility program (DFHSTUP) and the system dump formatting routines are also treated as OCO.
AS