Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword
Like this
3Activity
0 of .
Results for:
No results containing your search query
P. 1
C4 VANDCM- 1982

C4 VANDCM- 1982

Ratings: (0)|Views: 11|Likes:
Published by Vincent J. Cataldi
C4 VANDCM - DATABASE CONTROL MANAGER

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 direct connec¬tion between a user terminal and the application process that delivers a user-requested service. Application services are the result of application processes intercommunicating accord¬ing to protocols that govern specific application requests to provide distributed processing services appropriate to the ap¬plication, its management, and DCM system 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 logical information images and application process images. Interaction and intercommuni¬cation between application entities 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) Com¬mon Service Elements which set up an association between application entities; 2) General Purpose Applications which provide broad applications such as file transfer, and 3) User Specific Applications which provide limited functions such as EFT or reservation collection and processing. Protocols for *1 & *2 are expected to be formalized by the ISO in early 1984 with ISO/TC97/SC16/N1662 defining the Common Service Elements and protocol definitions also available in early 1984.
C4 VANDCM - DATABASE CONTROL MANAGER

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 direct connec¬tion between a user terminal and the application process that delivers a user-requested service. Application services are the result of application processes intercommunicating accord¬ing to protocols that govern specific application requests to provide distributed processing services appropriate to the ap¬plication, its management, and DCM system 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 logical information images and application process images. Interaction and intercommuni¬cation between application entities 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) Com¬mon Service Elements which set up an association between application entities; 2) General Purpose Applications which provide broad applications such as file transfer, and 3) User Specific Applications which provide limited functions such as EFT or reservation collection and processing. Protocols for *1 & *2 are expected to be formalized by the ISO in early 1984 with ISO/TC97/SC16/N1662 defining the Common Service Elements and protocol definitions also available in early 1984.

More info:

Published by: Vincent J. Cataldi on Nov 12, 2010
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

10/15/2012

pdf

text

original

 
C4 VA NDCM. DAT ABA SE CONT ROL MA NA GEDCM OVE RVIEW C4.1
C 3 9 D C M S U B S Y S T E M S & M O D U L E S C 4 . 2C 4 0 D C M B A T C H T R A N S A C T I O N P R O C E S S O R ( B P T ) C4.2aI N P U T : I n b o u n d M e s s a g e M a n a g e rC 4 . 2 a 1O U T P U T . O u t b o u n d M e s s a g e M a n a g e rC 4 . 2 a 2S C H E D P r o c e s s i n g S c h e d u l e rC 4 . 2 a 3C 4 1 D C M S Y S T E M M A N A G E R C 4 . 2 bU s e r C o n f i g u r a t o r C 4 . 2 b 1D a t a b a s e C o n f i g u r a t o r C 4 . 2 b 2C 4 2 D C M M O D I F I C A T I O N P R O C E S S O R C 4 . 4 cB a c k u p - R e s t o r a t i o n P r o c e s s o r C 4 . 2 c 1S t o r a g e C 4 . 2 c 2D a t a b a s e E d i t o r C 4 . 2 c 3S t r u c t u r e M o d i f i e r C 4 . 2c 3 . 1C o n t e n t M o d i f i e r C 4 . 2c 3 . 2S e r v i c e T e s t & V a l i d a t o r C 4 . 2c 3 . 3C 4 4 D C M R E T R I E V A L P R O C E S S O R C 4 . 2 dA c c e s s V a l i d a t e rC 4 . 2 d 1S i m p l e R e t r i e v e rC 4 . 2 d 2C o m p l e x R e t r i e v e rC 4 . 2 d 3C 4 5 D C M A P P L I C A T I O N P R O C E S S O R C 4 . 2 eA p p l i c a t i o n D e v e l o p e r ............................................................. C 4 . 2 e 1A p p l i c a t i o n I n t e r f a c e ................................................................ C 4 . 2 e 2C 4 7 D C M A U D I T C O L L E C T O R C 4 . 2 fP r o d u c t i o n R e p o r t e r .................................................................. C 4 . 2 f 1T r a f f i c R e p o r t e r ........................................................................... C 4 . 2 f 2B i l l i n g R e p o r t e r ........................................................................... C 4 . 2 f 3
 
C4 VANDCM-DATABASECONTROLMANAGER
C4.1 DCM OVERVIE
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
g
ued by message location, size, routing instructions, message priority, andmessage type.
 
The message type field specifies if the message is user-generated or system-generated and is set byeither DCM INPUT or OUTPUT. When DCM INPUT sets the variable, DCM OUTPUT uses it todetermine output processing procedures: conversely, when DCM OUTPUT sets the variable, DCM INPUTuses it to determine input processing procedures. Messages with improper addressing are spilled to a port-specific spill queue, messages addressed to a nonexistent user are spilled to a queue for such purpose ona port-specific basis.DCM INPUT moduleDCM INPUT processes user or system-generated messages, placing them into DCM BUFFER andreferencing them in DCM BUFDIR. User-generated messages are accepted from an X.25 driver whichman-ages the X.25 link interconnecting DCM and GCM processors. System-generated messages areaccepted through the communications facilities provided by the message receiver status of DCM INPUT.C4.2a2 DCM OUTPUT ModuleDCM OUTPUT processes user or system-generated messages, extract- ing them from DCM BUFFER in the orderspecified by the message priority and updating DCM BUFDIR to reflect the use of buffer resources. System-generatedmessages are transferred to an X.25 driver which manages the X.25 link interconnecting DCM and GCM processors.User-generated messages are transferred to the appropriate DCM process through communications facilities providedby the message receiver status of DCM OUTPUT.C4.2a3 Processing Scheduler (SCHED) ModuleDCM Processing Scheduler dynamically analyzes the state of the DCM system and calculates optimum permutations ofprocess scheduling to provide smooth resource allocation. It then composes a command for DCM OUTPUT specifyingrouting of the message and places this command into the DCM BUFDIR record associated with the message.SCHED also interacts with the DCM operating system to adjust dynamically the priority and runburst of competitive DCMprocesses to adjust the load on the DCM on a prioritized basis. During idle periods application processes (subsystemcomponents) automatically assume a SLEEP state until awakened by an interrupt message from the operating system.C4.2b DCM SYSTEM MANAGER SUBSYSTEMDCM System Manager directly controls both DCM user and database configuration and is responsible for initiating,maintaining, recording, and terminating connections for data transfer between application processes. In order toprovide central control of the sensitive area of configuration, although direct control of configuration functions is theresponsibility of DCM System Manager; its functions can be accessed only via NCM System Manager(C3.2a).DCM System Manager operates via two modules: 1) User Configurator which handles user configurations and 2)Database Configurator which handles database configurations.C4.2b1 User Configurator ModuleDCM User Configurator maintains user configuration information in a DCM User Directory. Immediately after useridentification, logon, and service selection NCM System Manager (C3.2a) for wards the user's configuration inreconfiguration packets to DCM User Configurator which updates its User Directory to include the entering user. ThisDCM User Directory is referenced by all DCM processes for user authorization character, user class, CUG associations,terminal-specific parameters, password, and any specialized information to enable access to foreign databases.C4.2b2 Database Configurator ModuleDCM Database Configurator defines database components as live or test bases, lists SAN addresses and titles in aSAN Directory to specify database parameters, and lists application ad-dresses and titles in an Application Directory.BTP and other DCM subsystems reference these tables to permit access of user-requested services. NCM SystemManager composes information packets and dispatches this i n f o r m a t i o n t o t h i s D C M m o d u l e whichupdates its tables accordingly.

Activity (3)

You've already reviewed this. Edit your review.
1 hundred reads
Dan liked this
Dan liked this

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->