C4.1 DCM OVERVIEW
VANDCM, the Database Control Manager, processes user-application services, thus providing functions of OSI Layer 7,the Application Layer. The primary function of DCM is to manage application processes to facilitate an apparent directconnection between a user terminal and the application process that delivers a user-requested service. Applicationservices are the result of application processes intercommunicating according to protocols that govern specificapplication requests to provide distributed processing services appropriate to the application, its management, and DCMsystem management. The application level is the only level seen by the end user.DCM is responsible for storage and retrieval of all database software components including both logicalinformation images and application process images. Interaction and intercommunication between applicationentities is synchronized by NCM Session Administrator (C3.2b2) and memory mapped data sinks (or sockets)and pipeline communication links are used to pass data between application entities.DCM functions via three types of application processes. 1) Common Service Elements which set up anassociation between application entities; 2) General Purpose Applications which provide broad applicationssuch as file transfer, and 3) User Specific Applications which provide limited functions such as EFT orreservation collection and processing. Protocols for *1 & *2 are expected to be formalized by the ISO in early1984 with ISO/TC97/SC16/N1662 defining the Common Service Elements and protocol definitions alsoavailable in early 1984.C4.1 DCM SUBSYSTEMS & MODULESThe DCM System consists of six peer subsystems: 1) Batch Transaction Processor (BTP) which coordinates DCMoperations, 2) System Manager which provides user configuration and database con-figuration, 3) ModificationProcessor which performs database updates without disrupting retrieval service, 4) Retrieval Processor whichaccesses requested DCM information and process services from disk based storage locations via either a simpleretrieval module or a complex retrieval module, 5) Application Processor which provides an interface between an activeuser and an application process or DCM Retrieval Processor and provides routines to assist with programdevelopment, and 6) Audit Collector which collects all DCM statistical messages and queues them to NCM AuditCollector/Processor. DCM operates these six subsystems as message receivers to pro-vide pipelinecommunication links for interprocess-communications.C4.2a BATCH TRANSACTION PROCESSOR (BTP)DCM Batch Transaction Processor (BTP) coordinates all DCM operations. it manages inbound andoutbound messages, moving them between the buffer region (DCM BUFFER) and either the receivers orthe transmitters within an I/O processor; it analyzes session control information within messages todetermine the session number, and it calculates the most efficient scheduling for all DCM services,interacting with the DCM operating system to adjust dynamically priority and runburst of competitive sys-tem processes to prioritize system-wide and user-specific processing.The BTP operates via three modules. 1) DCM INPUT which manages all inbound messages, 2) DCMOUTPUT which manages all outbound messages, and 3) Process Schedule Manager (SCHED) which sche-dules all processing of DCM services. These three modules organize DCM messages into BUFFER, astructured buffer region with a directory that enables prioritized processing regardless of the order in whichmessages are placed in the buffer.DCM BUFFER contains input-full, output-full., and empty buffers. These buffers store messages pendingprocessing by a DCM sub-system or dispatch to GCM through the X.25 communications link that connectsthe two hardware systems. DCM BUFFER contents are catalogued in DCM BUFDIR: each input-full oroutput-full message is catalo
ued by message location, size, routing instructions, message priority, andmessage type.