60485200
CONTRPL DATA
DMS-170
CYBER DATABASE CONTROL SYSTEM VERSION 2
DATA ADMINISTRATION REFERENCE MANUAL
CDC® OPERATING SYSTEMS:
NOS 2
NOS/BE 1
REVISION RECORD
Revision A (05/14/82)
B (08/26/83) C (09/22/83) D (02/20/84) E (05/13/86)
De sc ri ption
Initial release under NOS 2 and NOS/BE 1; PSR level 564. This manual represents a complete reorganization according to audience of documentation for CDCS, DDL, and FDBF (with FDBF separated into components of DDL and DML). This manual contains documentation intended for a data administrator, and supersedes the following manuals for users of the NOS 2 and NOS/BE operating systems: the CDCS 2 reference manual (Pub. No. 60491800); the DDL Version 3 reference manuals, volumes 1 and 2 (Pub. No. 60481900 and 60482000); and the FDBF 1 reference manual (Pub. No. 60482200). New features of CDCS 2.3 are also documented in this revision; the features include automatic recovery, data base transaction processing, data base versions, the basic recovery utility (DBREC), and extensions to the master directory and to the operator interface.
Released at PSR level 587. This revision documents improved duration loading capabilities of CDCS and miscellaneous technical corrections.
Released at PSR level 596. This revision documents a change to the procedure that initializes CDCS under NOS 2.2.
Released at PSR level 599. This revision documents support of concatenated keys for the FORTRAN Interface and includes miscellaneous technical corrections.
Released at PSR level 647. This revision removes references to FORTRAN 4 and incorporates miscellaneous technical and editorial changes.
REVISION LETTERS I, 0, Q, AND X ARE NOT USED
©COPYRIGHT CONTROL DATA CORPORATION 1982, 1983, 1984, 1986
All Rights Reserved
Printed in the United States of America
Address comments concerning this manual to:
CONTROL DATA CORPORATION
Publications and Graphics Division P.O. Box 3492
SUNNYVALE, CALIFORNIA 94088-3492
or use Comment Sheet in the back of this manual
LIST OF EFFECTIVE PAGES
New features, as well as changes, deletions, and additions to information in this manual are indicated by bars in the margins or by a dot near the page number if the entire page is affected. A bar by the page number indicates pagination rather than content has changed.
J ^ N
Page Front Cover Title Page
i i i i i / i v v v i v i i
v i i i t h r u x i i x i i i
1-1 thru 1-3 1-4
1-5 thru 1-12 2-1 thru 2-21 2-22
2-23
2-24 thru 2-30 2-31
2-32 2-33 2-34 2-35 2-36 2-37
3-1 thru 3-8 3-9 thru 3-11 3-12 thru 3-33 3-34
3-35 thru 3-37 3-38
3-39
4-1 thru 4-20 5-1
5-2 thru 5-4 6-1
6-2 6-3 6-4
6 - 4 . 1 / 6 - 4 . 2 6-5 thru 6-18 7-1 thru 7-9 8-1
8-2 8-3 8-4
8 - 4 . 1 / 8 - 4 . 2 8-5
8-6
8-7 thru 8-21 9-1 thru 9-3
9-4
9 - 4 . 1 / 9 - 4 . 2 9-6
9-7 9-8
9 - 8 . 1 / 9 - 8 . 2 9-9
9-10 9-11
Revision
E E D A B E A A E A A B D A B B A A B B A A B A E A B A E A E A A D D D A A A D E E E E D A A E E A A E E A A E
9-12 9-13 9-14 9-15 9-16 9-17 9-18
9-19 thru 9-27 10-1 thru 10-3 10-4 thru 10-8 10-8.1
10-8.2 10-9
10-10 thru 10-17 11-1
11-2 thru 11-5 11-6 thru 11-11 A-l thru A-4 B - l
B-2 B-3 B-4
B - 4 . 1 / B - 4 . 2 B-5
B-6 B-7 B-8 B-9
B-10 thru B-16 B-16.1
B-16.2
B-17 thru B-22 B-23
B-24
B-24.1/B-24.2 B-25 thru B-54 B-55
B-56 thru B-60 B-61
B-62 thru B-97 B-98
B-99 B-l 00 C - l C-2
C-3 thru C-5 C-6 thru C-9 D-l thru D-3 E - l
E-2 E-3 E-4 E-5 E-6
E-7 thru E-9 E-10 thru E-13
F - l F-2
Revision A A E A A E B A A E E E C A E A E A A A E E E A B A E B E E E A B C C A C A C A D A A A A B A A A A B B A A E A A A
Page Revision
G-lG-2 G-3
H-l thru H-4 H-5
H-61-1 1-2J - l J-2J-3
Index-1 thru Index-■10 Comment Sheet/Mailer Back Cover
60485200 E i i i / i v
( ^ %
PREFACE
This manual describes both the definition phase of a DMS-170 data base and the execution phase of CONTROL DATA® CYBER Database Control System (CDCS) Ve r s i o n 2 . A d a t a b a s e i s d e fi n e d b y t h e u s e o f the Data Description Language (DDL) and is control led by CDCS, which monitors all access by applica t i o n p r o g r a m s . S e v e r a l p r o d u c t s a r e i n v o l v e d i n the definition and execution phases; these products are CDCS Version 2.3, DDL Version 3.2, and the DDL portion of the FORTRAN Data Base Facility (FDBF) V e r s i o n 1 . 3 . A s d e s c r i b e d i n t h i s p u b l i c a t i o n , these products operate under control of the follow ing operating systems:
NOS/2 for the CONTROL DATA CYBER 180 Computer Systems; CYBER 170 Computer Systems; CYBER 70 Computer System Models 71, 72, 73, and 74; and 6000 Computer Systems
NOS/BE 1 for the CDC® CYBER 180 Computer Sys tems; CYBER 170 Computer Systems; CYBER 70 Computer System Models 71, 72, 73, and 74; and 6000 Computer Systems
This manual is designed for the data administrator.
The data administrator is the programming or man a g e r i a l p e r s o n o r g r o u p r e s p o n s i b l e f o r d e fi n i n g , c r e a t i n g , c o n t r o l l i n g , a n d m o n i t o r i n g d a t a b a s e s . It is assumed that the data administrator is knowl
edgeable in both systems and application program m i n g , h a s s o m e f a m i l i a r i t y w i t h d a t a m a n a g e m e n t concepts and terminology, and has used previously Control Data computers and software.
D e t a i l e d i n f o r m a t i o n f o r a p p l i c a t i o n p r o g r a m m e r s using CDCS is contained in the CDCS 2 Application Programming reference manual. Related material is contained in the publications listed below.
The NOS Manual Abstracts and the NOS/BE Manual A b s t r a c t s a r e i n s t a n t - s i z e d m a n u a l s c o n t a i n i n g b r i e f d e s c r i p t i o n s o f t h e c o n t e n t s a n d i n t e n d e d audience of all NOS and NOS product set manuals, and NOS/BE and NOS/BE product set manuals, respec t i v e l y. T h e a b s t r a c t s m a n u a l s c a n b e u s e f u l i n determining which manuals are of greatest interest t o a p a r t i c u l a r u s e r . T h e S o f t w a r e P u b l i c a t i o n s R e l e a s e H i s t o r y s e r v e s a s a g u i d e i n d e t e r m i n i n g w h i c h r e v i s i o n l e v e l o f s o f t w a r e d o c u m e n t a t i o n corresponds to the Programming System Report (PSR) l e v e l o f i n s t a l l e d s i t e s o f t w a r e . T h e a b s t r a c t s manuals are included in the list of publications of
secondary interest.
M a n u a l s a r e l i s t e d a l p h a b e t i c a l l y w i t h i n g r o u p i n g s t h a t i n d i c a t e r e l a t i v e i m p o r t a n c e t o r e a d e r s o f this manual.
The following manuals are of primary interest:
P u b l i c a t i o n P u b l i c a t i o n
Number CYBER Record Manager
Advanced Access Methods Version 2
Reference Manual 60499300
DMS-170
CYBER Database Control System Version 2
Application Programming Reference Manual 60485300
The following manuals are of secondary interest:
P u b l i c a t i o n
P u b l i c a t i o n Number CYBER Loader Version 1
Reference Manual 60429800
CYBER Record Manager
Basic Access Methods Version 1.5 Reference Manual
FORM Version 1 Reference Manual
60495700 60496200 Networks Products
Transaction Facility Version 1 Reference Manual
NOS Version 2 Manual Abstracts
60459500 60485500
60485200 D
NOS Version 2 Reference Set, Volume 3
S y s t e m C o m m a n d s 6 0 4 5 9 6 8 0 N O S / B E V e r s i o n 1 M a n u a l A b s t r a c t s 8 4 0 0 0 4 7 0 N O S / B E V e r s i o n 1 R e f e r e n c e M a n u a l 6 0 4 9 3 8 0 0 S o f t w a r e P u b l i c a t i o n s R e l e a s e H i s t o r y 6 0 4 8 1 0 0 0
CDC manuals can be ordered from Control Data Corporation, Litera ture and Distribution Servicesj 308 North Dale Street, St. Paul, Minnesota 55103.
This product is intended for use only as described in this document. Control Data can- riot be responsible for the proper functioning of undescribed features or parameters.
CONTENTS
NOTATIONS
1. INTRODUCTION TO DATA BASE PROCESSING WITH DMS-170
0 ^ \
Data Base Definition Schema Definition Subschema Definitions
COBOL Subschemas FORTRAN Subschemas Query Update Subschemas M a s t e r D i r e c t o r y D e fi n i t i o n Data Base Processing
Application Languages COBOL Processing FORTRAN Processing Query Update Processing Concurrency
Data Validation Record Mapping F i l e P r i v a c y Relations Constraints Data Base Versions Data Base Procedures Input/Output Processing
Fi le Org a n i zati on
Multiple-Index Processing Data Base Recovery
Automatic Recovery Data Base Transaction Manual Recovery Utilities Logging
Other Data Base Utilities Processing Through TAF CDCS Processing Flow CDCS Loading and Execution CDCS Batch Testing
2. SCHEMA DEFINITION
Schema Structuring Conventions Data Description
Data Organization Areas
Records
Repeating Data Items Data Size and Class Schema/Subschema Compatibility
Data Conversion
Coded Arithmetic to Numeric Picture Numeric Picture to Coded Arithmetic Coded Arithmetic to Coded Arithmetic Numeric Picture to Numeric Picture Record Mapping
Schema Programming Conventions Language Elements
Reserved Words User-Defined Names L i t e r a l s
Data Reference I d e n t i fi e r DDL Character Set Punctuation
x i i i
1-1 1-1 1-1 1-2 1-3 1-3 1-3 1-4 1-4 1-4 1-4 1-4 1-6 1-6 1-6 1-6 1-6 1-6 1-7 1-7 1-7 1-7 1-7 1-9 1-9 1-9 1-9 1-9 1-9 1-10 1-10 1-11 1-11 1-11 2-1 2-1 2-1 2-1 2-1 2-2 2-3 2-3 2-4 2-4 2-5 2-5 2-5 2-5 2-5 2-5 2-5 2-5 2-6 2-6 2-6 2-7 2-7 2-7
DDL Coding
DDL Statements Sequence Numbers Comment Lines Schema Syntax
Schema Identification Entry SCHEMA NAME Clause Other Clauses Area Description Entry
AREA NAME Clause
CALL Clause (Area Description Entry) ACCESS-CONTROL Clause
Record Description Entry RECORD NAME Clause WITHIN Clause
CALL Clause (Record Description Entry) Data Description Entry (Record Description
Entry)
PICTURE Clause TYPE Clause OCCURS Clause RESULT Clause CHECK Clause
ENCODING/DECODING Clause
CALL Clause (Data Description Entry) Data Control Entry
Area Control Entry (Data Control Entry) AREA NAME Clause
COMPRESSION/DECOMPRESSION Clause KEY Clause
SEQUENCE Clause RECORD CODE Clause Constraint Entry
CONSTRAINT NAME Clause DEPENDS ON Clause Relation Entry
RELATION NAME Clause JOIN Clause
Schema Compilation and Maintenance Facilities DDL3 Control Statement
Schema Compilation
DDL3 Control Statement for Compilation FILE Control Statement
Schema Compilation Example Schema Compilation Output Recompilation Guidelines E x h i b i t F a c i l i t y
Control Statement Format EXHIBIT Directive Format 3 . COBOL AND QUERY UPDATE SUBSCHEMA
DEFINITION
Subschema Structuring Conventions Data Description
Data Organization Group Items Elementary Items Schema/Subschema Compatibility
Omission of Data Items Ordering of Data Items Definition of Data Items
Data Size and Class Repeating Data Items Subschema Programming Conventions
2-8 2-8 2-8 2-8 2-8 2-9 2-9 2-9 2-9 2-9 2-9 2-10 2-10 2-11 2 - U 2-11 2-12 2-12 2-14 2-16 2-16 2-18 2-19 2-19 2-21 2-21 2-21 2-22 2-22 2-23 2-24 2-24 2-26 2-27 2-27 2-28 2-28 2-29 2-29 2-30 2-31 2-31 2-32 2-32 2-35 2-36 2-36 2-36
3-1 3-1 3-1 3-2 J-2 J-2 3-2 3-2 3-2 J-2 J-3 J-4 J-8
60485200 B
Language Elements Reserved Words User-Defined Names L i t e r a l s
Data Reference DDL Character Set Punctuation DDL Coding
Coding DDL Statements Sequence Numbers Continuation Lines Comment Lines
COBOL and Query Update Subschema Syntax T i t l e D i v i s i o n
SS Clause Other Clauses A l i a s D i v i s i o n
AD Clause Other Clauses Realm Division
RD Clause Other Clauses
Record Division, COBOL Subschema JUSTIFIED Clause
OCCURS Clause PICTURE Clause REDEFINES Clause
SYNCHRONIZED Clause USAGE Clause
RENAMES Clause VALUE Clause
Record Division, Query Update Subschema JUSTIFIED Clause
OCCURS Clause PICTURE Clause REDEFINES Clause SYNCHRONIZED Clause USAGE Clause RENAMES Clause R e l a t i o n D i v i s i o n
RN Clause RESTRICT Clause
Subschema Compilation and Subschema Library Maintenance
Subschema Library DDL3 Control Statement
Subschema Compilation and Library Maintenance Operations
Compiling a Subschema Creating a Subschema Library Compiling Multiple Subschemas
Compiling a Subschema and Adding to a Subschema Library
Replacing a Subschema Deleting a Subschema
Auditing a Subschema Library Compacting a Subschema Library Compilation Output
Recompilation Guidelines
4. FORTRAN SUBSCHEMA DEFINITION Subschema Structuring Requirements
Data Description Variables Arrays
Schema/Subschema Correspondence Omission of Data Items Ordering of Data Items Definition of Data Items
Data Size and Type Array Declaration
3-9 3-9 3-9 3-9 3-9 3-10 3-10 3-10 3-10 3-11 3-11 3-11 3-11 3-11 3-11 3-11 3-11 3-12 3-12 3-12 3-12 3-13 3-13 3-13 3-14 3-15 3-17 3-18 3-18 3-19 3-20 3-22 3-23 3-23 3-24 3-28 3-28 3-28 3-30 3-30 3-30 3-30 3-32 3-32 3-32 3-34 3-34 3-34 3-35 3-35 3-35 3-36 3-36 3-37 3-38 3-38
4-1 4-1 4-1 4-2 4-2 4-2 4-2 4-2 4-2 4-3 4-5
Concatenated Key
Subschema Programming Conventions Language Elements
Keywords
User-Defined Names Constants
FORTRAN DDL Statement Format Character Set
Blanks Continuation Statement Labels Comment Lines Blank Lines FORTRAN Subschema Syntax
SUBSCHEMA Statement ALIAS Statement
REALM Statement Record Definition
RECORD Statement Type Statements R e l a t i o n D e fi n i t i o n
RELATION Statement RESTRICT Statement END Statement
Subschema Compilation and Subschema Library Maintenance
Subschema Library DDLF Control Statement
Subschema Compilation and Library Maintenance Operations
Compiling a Subschema Creating a Subschema Library Compiling Multiple Subschemas Compiling a Subschema and Adding to
a Subschema Library Replacing a Subschema Deleting a Subschema
Auditing a Subschema Library Compacting a Subschema Library Compilation Output
Recompilation Guidelines 5. SCHEMA AND SUBSCHEMA MAPPING S t r u c t u r i n g R e s t r i c t i o n s
Data Conversion Data Class
Omission of Data Items 6. DATA STRUCTURES Data Base Files
CDCS and CRM Communication Data Base File Definition
CRM Record Types F i l e C o n t r o l
M u l t i p l e - I n d e x F i l e s
Multiple Record Descriptions Key Definitions
Data Base Versions
Defining Data Base Versions Access Control Locks
Examples of Environments for Data Base Versions
Te s t i n g S i t u a t i o n Branch Situation Relations
J o i n i n g F i l e s
Hierarchical Tree Structure Ranks of a Relation
Parent/Child Relationship Record Qualification
4-o 4-6 4-6 4-6 4-7 4-7 4-7 4-8 4-8 4-8 4-8 4-8 4-8 4-8 4-9 4-9 4-10 4-1U 4-10 4-11 4-12 4-12 4-12 4-1J 4-13 4-14 4-14 4-15 4-16 4-16 4 - l b 4-17 4-17 4-17 4-18 4-18 4 - i y 4-19 D - l 3-1 5-1 5-1 5-2 b-1 6-1 6-1 b-1 6-1 b-2 6-2 6-2 6-2 6-4 b-4.1 6-4.1 6-4.1 6-4.1 b-5
6-5 6-6 b-6 b-7 6-8 b-8
/p^sy
C D C S R e l a t i o n P r o c e s s i n g 6 - 9 S o u r c e a n d T a r g e t I d e n t i fi e r s 6 - 9 R e l a t i o n P o s i t i o n i n g 6 - 9
R e l a t i o n R e a d 6 - 9
O r d e r o f R e c o r d R e t r i e v a l 6 - 1 0 I n f o r m a t i v e C o n d i t i o n s 6 - 1 0 Effect of Versions on Relation
R e t r i e v a l 6 - 1 2
C o l l a t i n g S e q u e n c e s 6 - 1 3
C o n s t r a i n t s 6 - 1 3
D e fi n i n g C o n s t r a i n t s 6 - 1 3 T w o - F i l e C o n s t r a i n t s 6 - 1 3 S i n g l e - F i l e C o n s t r a i n t s 6 - 1 5 C D C S T w o - F i l e C o n s t r a i n t P r o c e s s i n g 6 - 1 5 G u i d e l i n e s f o r F i l e C r e a t i o n 6 - 1 6 C o n t r o l l i n g I n s e r t i o n O p e r a t i o n s 6 - 1 6 C o n t r o l l i n g D e l e t i o n O p e r a t i o n s 6 - 1 6 C o n t r o l l i n g M o d i fi c a t i o n O p e r a t i o n s 6 - 1 6 C D C S S i n g l e - F i l e C o n s t r a i n t P r o c e s s i n g 6 - 1 7 G u i d e l i n e s f o r F i l e C r e a t i o n 6 - 1 7 C o n t r o l l i n g I n s e r t i o n O p e r a t i o n s 6 - 1 7 C o n t r o l l i n g D e l e t i o n O p e r a t i o n s 6 - 1 7 C o n t r o l l i n g M o d i fi c a t i o n O p e r a t i o n s 6 - 1 7 R e s t r i c t i o n s f o r D a t a B a s e V e r s i o n s 6 - 1 8 7 . D A T A B A S E P R O C E D U R E S 7 - 1 D e s c r i b i n g D a t a B a s e P r o c e d u r e U s e 7 - 1 L o a d i n g o f D a t a B a s e P r o c e d u r e s 7 - 2 W r i t i n g D a t a B a s e P r o c e d u r e s 7 - 2 L i n k a g e a n d C o m m u n i c a t i o n 7 - 2
P a r a m e t e r L i s t 7 - 2
E n t r y C o d e s a n d R e t u r n C o d e s 7 - 3 I n t e r p r e t a t i o n o f P a r a m e t e r s 7 - 5 Data Base Procedures for Input/Output
F u n c t i o n s 7 - 5
R E A D S t a t e m e n t 7 - 5
W R I T E a n d R E W R I T E S t a t e m e n t s 7 - 5 D E L E T E a n d S T A R T S t a t e m e n t s 7 - 6 R e l a t i o n R E A D S t a t e m e n t 7 - 6
E r r o r P r o c e s s i n g 7 - 6
N o n f a t a l E r r o r s 7 - 6
F a t a l E r r o r s 7 - 6
R e t u r n C o d e s 7 - 7
P r o c e d u r e L i b r a r y P r e p a r a t i o n 7 - 7 S a m p l e D a t a B a s e P r o c e d u r e s 7 - 8 C O B O L D a t a B a s e P r o c e d u r e s 7 - 8 F O R T R A N D a t a B a s e P r o c e d u r e s 7 - 8 C O M P A S S D a t a B a s e P r o c e d u r e s 7 - 8
8 . M A S T E R D I R E C T O R Y 8 - 1
M a s t e r D i r e c t o r y S y n t a x 8 - 1 P e r m a n e n t F i l e I n f o r m a t i o n S u b e n t r y 8 - 1
P F N C l a u s e 8 - 2
U N / I D C l a u s e 8 - 2
P W C l a u s e 8 - 2
F A M I L Y N A M E C l a u s e 8 - 2
P A C K N A M E C l a u s e 8 - 2
S E T N A M E C l a u s e 8 - 2
V S N C l a u s e 8 - 2
D E V I C E T Y P E C l a u s e 8 - 2 S y n t a x f o r t h e C r e a t i o n R u n 8 - 3
S c h e m a S u b e n t r y 8 - 3
S C H E M A N A M E C l a u s e 8 - 3 FILE NAME Clause (Schema Subentry) 8-4 P R O C E D U R E L I B R A R Y C l a u s e 8 - 4 TRANSACTION RECOVERY FILE Clause 8-4 R E S TA R T I D E N T I F I E R F I L E C l a u s e 8 - 4 J O U R N A L L O G F I L E C l a u s e 8 - 4 Q U I C K R E C O V E R Y F I L E C l a u s e 8 - 4 . 1 JOB C ON T R OL IN F OR MAT ION C l aus e 8- 4.1
M a s t e r V e r s i o n S u b e n t r y 8 - 5 A r e a S u b e n t r y ( M a s t e r Ve r s i o n S u b e n t r y ) 8 - 6 A R E A N A M E C l a u s e ( A r e a S u b e n t r y ) 8 - 6 Permanent File Information Subentry
( A r e a S u b e n t r y ) 8 - 6
L O G C l a u s e ( A r e a S u b e n t r y ) 8 - 7 I N D E X F I L E C l a u s e ( A r e a S u b e n t r y ) 8 - 7 A l t e r n a t e V e r s i o n S u b e n t r y 8 - 7
VERSION NAME Clause (Alternate
V e r s i o n S u b e n t r y ) 8 - 7 AREA NAME SAME AS MASTER Clause
( A l t e r n a t e V e r s i o n S u b e n t r y ) 8 - 7 Area Subentry (Alternate Version
S u b e n t r y ) 8 - 8
S u b s c h e m a S u b e n t r y 8 - 8 SUBSCHEMA NAME Clause (Subschema
S u b e n t r y ) 8 - 8
FILE NAME Clause (Subschema Subentry) 8-8 S y n t a x F o r M o d i fi c a t i o n R u n 8 - 8
A d d S c h e m a E n t r y 8 - 9
D e l e t e S c h e m a E n t r y 8 - 9 M o d i f y S c h e m a E n t r y 8 - 9 M O D I F Y S C H E M A N A M E C l a u s e 8 - 9 FILE NAME Clause (Modify Schema
S u b e n t r y ) 8 - 9
E N D C l a u s e 8 - 1 0
C h a n g e P r o c e d u r e L i b r a r y S u b e n t r y 8 - 1 0 Change Transaction Recovery File
S u b e n t r y 8 - 1 0
C h a n g e R e s t a r t I d e n t i fi e r F i l e
S u b e n t r y 8 - 1 1
C h a n g e J o u r n a l L o g F i l e S u b e n t r y 8 - 1 2 Change Quick Recovery File Subentry 8-12 Change Job Control Information
S u b e n t r y 8 - 1 2
C h a n g e A r e a S u b e n t r y 8 - 1 3 D e l e t e V e r s i o n S u b e n t r y 8 - 1 5 A d d V e r s i o n S u b e n t r y 8 - 1 5 D e l e t e S u b s c h e m a S u b e n t r y 8 - 1 5 A d d S u b s c h e m a S u b e n t r y 8 - 1 5 M a s t e r D i r e c t o r y G e n e r a t i o n 8 - 1 6 D B M S T R D C o n t r o l S t a t e m e n t 8 - 1 6
C r e a t i o n R u n 8 - 1 7
M o d i fi c a t i o n R u n 8 - 1 7
D B M S T R D O u t p u t 8 - 1 7
9 . D A T A B A S E R E C O V E R Y 9 - 1
A u t o m a t i c R e c o v e r y 9 - 2
D a t a B a s e T r a n s a c t i o n 9 - 3 Data Base Recovery From Application
P r o g r a m F a i l u r e 9 - 3
R e c o v e r y F r o m S y s t e m F a i l u r e 9 - 4 R e c o v e r y o f a S i n g l e D a t a B a s e F i l e 9 - 4 | A u t o m a t i c J o u r n a l L o g M a i n t e n a n c e 9 - 4 Data Administrator's Role in Automatic
R e c o v e r y 9 - 4
D a t a B a s e U t i l i t i e s 9 - 4 . 1 |
D B R E C U t i l i t y 9 - 6
S c h e m a E n t r y 9 - 6
S C H E M A N A M E C l a u s e 9 - 6
D U M P C l a u s e 9 - b
A L L O C A T E C l a u s e 9 - 6
D B R E C C o n t r o l S t a t e m e n t 9 - 7 E x e c u t i o n o f D B R E C f o r A l l o c a t i o n 9 - 8 DBREC Execution to Dump the Journal
L o g F i l e 9 - 8
D B Q R F A U t i l i t y 9 - 9
D B Q R F I U t i l i t y 9 - 1 0
D B R C N U t i l i t y 9 - 1 1
F o r m a t o f I n p u t f o r D B R C N U t i l i t y 9 - 1 1 D B R C N C o n t r o l S t a t e m e n t 9 - 1 2 E x e c u t i o n o f t h e D B R C N U t i l i t y 9 - 1 3
60485200 E i x
D B R S T U t i l i t y 9 - 1 4 F o r m a t o f I n p u t f o r D B R S T U t i l i t y 9 - 1 4 D B R S T C o n t r o l S t a t e m e n t 9 - 1 4 E x e c u t i o n o f t h e D B R S T U t i l i t y 9 - 1 4 Recovery Example Using DBRST Utility 9-15
L o g g i n g 9 - 1 5
J o u r n a l L o g F i l e 9 - 1 5
J o u r n a l L o g F i l e L o g g i n g O p t i o n s 9 - 1 5 M a i n t e n a n c e o f t h e J o u r n a l L o g F i l e 9 - 1 7 J o u r n a l L o g F i l e S t r u c t u r e 9 - 1 7 J o u r n a l L o g R e c o r d S t r u c t u r e 9 - 1 7 Q u i c k R e c o v e r y F i l e 9 - 2 2 R e s t a r t I d e n t i fi e r F i l e 9 - 2 3 T r a n s a c t i o n R e c o v e r y F i l e 9 - 2 4 J o u r n a l L o g F i l e R e p o r t G e n e r a t i o n 9 - 2 4 R e c o v e r y C o n s i d e r a t i o n s 9 - 2 4
R e c o v e r y P o i n t s 9 - 2 5
Q u i c k R e c o v e r y F i l e R e c o v e r y P o i n t s 9 - 2 5 J o u r n a l L o g F i l e R e c o v e r y P o i n t 9 - 2 5 Recovery Point Processing With No Log
F i l e s 9 - 2 5
L o g g i n g O p t i o n s 9 - 2 5
Logging to the Transaction Recovery
F i l e 9 - 2 5
L o g g i n g t o t h e R e s t a r t I d e n t i fi e r F i l e 9 - 2 5 L o g g i n g t o t h e Q u i c k R e c o v e r y F i l e 9 - 2 5 Logging After-image Records to a
J o u r n a l L o g F i l e 9 - 2 6 Logging Before-Image Records to a
J o u r n a l L o g F i l e 9 - 2 6 M a n u a l D a t a B a s e R e c o v e r y 9 - 2 6 R e c o v e r y C o n d i t i o n s 9 - 2 7 P h y s i c a l S t o r a g e o r S o f t w a r e F a i l u r e 9 - 2 7
C a s c a d e E f f e c t 9 - 2 7
P r o g r a m L o g i c E r r o r 9 - 2 7
S y s t e m F a i l u r e 9 - 2 7
R e c o v e r y F r o m R e c o v e r y F a i l u r e s 9 - 2 7 10. DATA ADMINISTRATOR AND OPERATING SYSTEM
P R O C E D U R E S 1 0 - 1
D a t a A d m i n i s t r a t o r ' s R e s p o n s i b i l i t i e s 1 0 - 1 S y s t e m L i m i t a t i o n s 1 0 - 1
D a t a P r i v a c y 1 0 - 1
P r i v a c y ( A c c e s s C o n t r o l ) C h e c k i n g 1 0 - 1 O p e r a t i n g S y s t e m F i l e S e c u r i t y 1 0 - 3 A p p l i c a t i o n P r o g r a m m i n g I n t e r f a c e 1 0 - 3 C D C S C o n t r o l S t a t e m e n t 1 0 - 4
D i r e c t i v e F i l e 1 0 - 4
P a r a m e t e r s 1 0 - 4
A c c o u n t i n g S t a t i s t i c s 1 0 - 8
| D u r a t i o n L o a d i n g 1 0 - 8 . 1
C D C S L o a d i n g o f O v e r l a y C a p s u l e s 1 0 - 8 . 1 C D C S L o a d i n g o f C R M C a p s u l e s 1 0 - 8 . 1 C l a s s i fi c a t i o n a n d E f f e c t o f C R M E r r o r s 1 0 - 8 . 1 I C D C S C R M E r r o r L i s t i n g F i l e U s e 1 0 - 8 . 21 0 - 8 . 2 S y s t e m O p e r a t o r G u i d e l i n e s 1 0 - 8 . 2 C D C S I n i t i a l i z a t i o n 1 0 - 8 . 2
N O S S y s t e m P r o c e d u r e F i l e 1 0 - 9 N O S / B E S y s t e m P r o c e d u r e F i l e 1 0 - 9 O p e r a t o r I n t e r f a c e 1 0 - 1 0
P r o g r a m m a b l e D i s p l a y U s a g e 1 0 - 1 0 O p e r a t o r C o m m a n d s 1 0 - 1 1 S a m p l e O p e r a t o r I n t e r f a c e 1 0 - 1 6
C D C S T e r m i n a t i o n 1 0 - 1 6
1 1 . E X A M P L E S 1 1 - 1
S a m p l e S c h e m a 1 1 - 1
S a m p l e S u b s c h e m a s 1 1 - 1
C O B O L S u b s c h e m a 1 1 - 1
FORTRAN 5 Subschema Query Update Subschema
Sample Master Directory Creation Run Sample Master Directory Modification Run Sample DBREC Utility Run
APPENDIXES
Standard Character Sets Diagnostics
Glossary
Reserved Words and FORTRAN DDL Keywords Summary Syntax for the Schema, Subschemas,
Master Directory, and Data Base U t i l i t i e s
Future System Migration Guidelines Field Length Requirements
Data Conversion Rules
Collating Sequences for Data Base Files Summary of Data Definition in DMS-170 INDEX
FIGURES
1 - 1 D a t a B a s e D e fi n i t i o n
1-2 Subschema Describing a Portion of the Data Base
1-3 Data Base Processing With CDCS 1-4 Processing Using Data Base Versions 1-5 CDCS/TAF interface
1-6 Data Base Environment Under Operating System
2 - 1 I d e n t i fi e r F o r m a t 2-2 General Format, Schema 2-3 SCHEMA NAME Clause Format 2-4 Area Description Entry Format
2-5 AREA NAME Clause Format
2-6 CALL Clause Format (Area Description Entry)
2-7 ACCESS-CONTROL Clause Format 2-8 Record Description Entry Format 2-9 RECORD NAME Clause Format 2-10 WITHIN Clause Format
2-11 CALL Clause Format (Record Description E n t r y )
2-12 Data Description Entry Format 2-13 PICTURE Clause Format
2-14 PICTURE Clause Character Data Items 2-15 Sign Representation in Rightmost Digit 2-16 PICTURE Clause Numeric Data Items 2-17 TYPE Clause Format
2-18 TYPE Clause Numeric Data Items 2-19 TYPE Clause Character Data Items 2-20 OCCURS Clause Format
2-21 OCCURS Clause Examples 2-22 RESULT Clause Format
2-23 Virtual Data Item Processing 2-24 CHECK Clause Format
2-25 Examples of Valid Literals in the CHECK VALUE Clause
2-26 ENCODING/DECODING Clause Format 2-27 CALL Clause Format (Data Description
E n t r y )
2-28 Data Control Entry Format 2-29 Area Control Entry Format 2-30 AREA NAME Clause Format
2-31 COMPRESSION/DECOMPRESSION Clause Format 2-32 Examples of the COMPRESSION/
DECOMPRESSION Clause 2-33 KEY Clause Format
11-b 11-8 11-9 11-10 11-10
A - l B - l C - l D - l E - l F - l G - l H - l 1-1 J - l
1-2 1-3 1-5 1-8 1-10 1-12 2-7 2-8 2-9 2-9 2-9 2-10 2-10 2-11 2-11 2-11 2-11 2-12 2-12 2-13 2-14 2-14 2-14 2-15 2-15 2-16 2-17 2-17 2-18 2-18 2-20 2-20 2-20 2-21 2-21 2-21 2-22 2-22 2-23
2-34 SEQUENCE Clause Format 2-35 RECORD CODE Clause Format
2-36 Examples of the RECORD CODE Clause 2-37 Dependency Conditions Established by
C o n s t r a i n t s
2-38 Constraint Entry Format
2-39 Constraint Entry Within a Schema 2-40 Relation Direction Example 2-41 Relation Entry Format 2-42 Alignment Example 2-43 Data Name Example
2-44 DDL Control Statement Format for Schema Compilation and Maintenance
2-45 FILE Control Statement Format 2-46 Schema Compilation Example
2-47 Sample Schema Compilation Output Listing 2-48 Recompilation List Example
2-49 EXHIBIT Directive Format 2-50 EXHIBIT Examples
2-51 Executing the EXHIBIT Utility, Example 1 2-52 Sample EXHIBIT Utility Output, Example 1 2-53 Executing the EXHIBIT Utility, Example 2 2-54 Sample EXHIBIT Utility Output, Example 2 3-1 Omitting Schema Items From the Subschema 3-2 Reordering Data Items
3-3 Size Discrepancies of Data Items 3-4 Examples of Repeating Data Items 3-5 Insertion of Nonrepeating Group Items 3-6 Concatenated Key Declaration
3 - 7 I d e n t i fi e r F o r m a t
3-8 COBOL Subschema Qualification and Subscripting Example
3-9 General Format, COBOL and Query Update Subs chema
3-10 SS Clause Format 3-11 AD Clause Format 3-12 Assigning Aliases 3-13 RD Clause Format
3-14 Formats of Data Description Entries, COBOL Subschema
3-15 JUSTIFIED Clause Format, COBOL Subschema 3 - 1 6 C h a r a c t e r P o s i t i o n i n g
3-17 OCCURS Clause Format, COBOL Subschema 3-18 PICTURE Clause Format, COBOL Subschema 3-19 Alphabetic Data Items
3-20 Minus Sign Representation 3-21 Numeric Data Items 3-22 Alphanumeric Data Items
3-23 REDEFINES Clause Format, COBOL Subschema 3-24 Redefining Data Items
3-25 SYNCHRONIZED Clause Format, COBOL Subschema
3-26 USAGE Clause Format, COBOL Subschema 3-27 RENAMES Clause Format, COBOL Subschema 3-28 Renaming Data Items
3-29 VALUE Clause Format, COBOL Subschema 3-30 Examples of Valid Level 88 Literals 3-31 Examples of Valid Level 88 Figurative
Constants
3-32 Formats of Data Description Entries, Query Update Subschema
3-33 JUSTIFIED Clause Format, Query Update Subschema
3-34 OCCURS Clause Format, Query Update Subs chema
3-35 PICTURE Clause Format, Query Update Subschema
3-36 Examples of Insertion Characters 3-37 Examples of Replacement Characters 3-38 Examples of Picture Editing
3-39 REDEFINES Clause Format, Query Update Subschema
3-40 SYNCHRONIZED Clause Format, Query Update Subschema
2-23 3-41
2-24
2-25 3-42
2-26 3-43
2-26 3-44
2-27 3-45
2-28
2-28 3-46
2-29 3-47
2-29 3-48
2-29 3-49
2-31 3-50
2-33 3-51
2-33 3-52
2-35 3-53
2-36 3-54
2-36
2-37 4-1
2-37 4-2
2-37
2-37 4-3
3-3 4-4
3-3 4-5
3-4 4-6
3-7 4-7
3-8 4-8
3-8 4-9
3-10 4-10
4-11
3-10 4-12
4-13
3-11 4-14
3-11 4-15
3-12 4-16
3-12 4-17
3-13
4-18
3-13 4-19
3-13 4-20
3-14
3-14 4-21
3-15 4-22
3-16 4-23
3-16 4-24
3-17 4-25
3-17 4-26
3-17
3-18 6-1
6-2 3-18
3-19 6-3
3-19
3-20 6-4
3-20 6-5
3-21 6-6
3-22 6-7
3-23 6-8
3-23 6-9
3-23 6-10
6-11 3-24
3-26 6-12
3-27
3-27 6-13
6-14
3-28 6-15
6-16 3-28
USAGE Clause Format, Query Update
S u b s c h e m a 3 - 2 9
RENAMES Clause Format, Query Update
S u b s c h e m a 3 - 3 0
R N C l a u s e F o r m a t 3 - 3 0
R E S T R I C T C l a u s e F o r m a t 3 - 3 1 DDL3 Control Statement Format for
COBOL and Query Update Subschemas 3-32 C o m p i l i n g a S u b s c h e m a 3 - 3 4 C r e a t i n g a S u b s c h e m a L i b r a r y 3 - 3 5 Compiling a Subschema and Adding to a
S u b s c h e m a L i b r a r y J - 3 5 R e p l a c i n g a S u b s c h e m a L i b r a r y 3 - 3 6 D e l e t i n g S u b s c h e m a s F r o m t h e L i b r a r y 3 - 3 6 A u d i t i n g a S u b s c h e m a L i b r a r y 3 - 3 7 A u d i t L i s t i n g o f t h e S u b s c h e m a L i b r a r y 3 - 3 7 C o m p a c t i n g a S u b s c h e m a L i b r a r y 3 - 3 7 Sample COBOL Subschema Compilation
O u t p u t L i s t i n g 3 - 3 8
F i x e d O c c u r r e n c e E l e m e n t a r y I t e m s 4 - 5 Schema/Subschema Differences in Array
S i z e a n d D i m e n s i o n 4 - 5 Variable Arrays in Schema and Subschema 4-5 D e c l a r i n g a C o n c a t e n a t e d K e y 4 - 6 G e n e r a l F o r m a t , F O R T R A N S u b s c h e m a 4 - 9 S U B S C H E M A S t a t e m e n t F o r m a t 4 - 9 A L I A S S t a t e m e n t F o r m a t 4 - 9 A s s i g n i n g A l i a s e s 4 - 1 0 R E A L M S t a t e m e n t F o r m a t 4 - 1 0 R E C O R D S t a t e m e n t F o r m a t 4 - 1 0 T y p e S t a t e m e n t F o r m a t s 4 - 1 1
D e fi n i n g R e c o r d s 4 - 1 2
R E L A T I O N S t a t e m e n t F o r m a t 4 - 1 2 R E S T R I C T S t a t e m e n t F o r m a t 4 - 1 3 E x a m p l e s o f L o g i c a l E x p r e s s i o n s 4 - 1 3 E N D S t a t e m e n t F o r m a t 4 - 1 3 DDLF Control Statement Format for
F O R T R A N S u b s c h e m a s 4 - 1 4 C o m p i l i n g a S u b s c h e m a 4 - 1 6 C r e a t i n g a S u b s c h e m a L i b r a r y 4 - 1 6 Compiling a Subschema and Adding to a
S u b s c h e m a L i b r a r y 4 - 1 7 R e p l a c i n g a S u b s c h e m a L i b r a r y 4 - 1 7 D e l e t i n g S u b s c h e m a s F r o m t h e L i b r a r y 4 - 1 8 A u d i t i n g a S u b s c h e m a L i b r a r y 4 - 1 8 A u d i t L i s t i n g o f t h e S u b s c h e m a L i b r a r y 4 - 1 9 C o m p a c t i n g a S u b s c h e m a L i b r a r y 4 - 1 9 Sample FORTRAN Subschema Compilation
O u t p u t L i s t i n g 4 - 2 0
C o n c a t e n a t e d K e y D e fi n i t i o n 6 - 4 Key Definitions for Areas With Multiple
R e c o r d T y p e s 6 - 4
Example of Version Definitions in
M a s t e r D i r e c t o r y I n p u t b - 5 T w o - F i l e R e l a t i o n s h i p E x a m p l e 6 - 6 T h r e e - F i l e R e l a t i o n s h i p E x a m p l e 6 - 7 Tree Structure of CONTRACTS-PRODUCTS-
E M P L O Y E E S R e l a t i o n s h i p 6 - 7 Complex Tree Structure for CONTRACTS-
P R O D U C T S - E M P L O Y E E S R e l a t i o n s h i p b - 8 Record Occurrences for Three Related
F i l e s 6 - 1 0
Record Occurrences in User's Work Areas
A f t e r R e a d i n g 6 - 1 0
N u l l R e c o r d O c c u r r e n c e E x a m p l e s b - 1 1 Example of Null Occurrence and Control
B r e a k C o n d i t i o n s b - 1 2 Example of Files Joined by a Relation
a n d G r o u p e d b y V e r s i o n b - 1 2 T w o - F i l e C o n s t r a i n t E x a m p l e 6 - 1 3 T h r e e - F i l e C o n s t r a i n t E x a m p l e 6 - 1 4 S i n g l e - F i l e C o n s t r a i n t E x a m p l e 6 - 1 5 Example of Constraint Restrictions on
D a t a B a s e V e r s i o n s 6 - 1 8
60485200 E x i
7-1 Procedure Library Generation
7-2 ENCODING/DECODING Description for COBOL Data Base Procedure
7-3 Sample COBOL Data Base Procedure 8-1 Permanent File Information Subentry
Format
8-2 General Format, Creation Run 8-3 General Format, Creation Entry 8-4 Schema Subentry Format
8-5 Master Version Subentry Format 8-6 Area Subentry Format
8-7 Alternate Version Subentry Format 8-8 Subschema Subentry Format
8-9 General Format, Modification Run 8-10 Add Schema Entry Format
8-11 Delete Schema Entry Format 8-12 Modify Schema Entry Format
8-13 Change Procedure Library Subentry Format 8-14 Change Transaction Recovery File
Subentry Format
8-15 Change Restart Identifier File Subentry Format
8-16 Change Journal Log File Subentry Format 8-17 Change Quick Recovery File Subentry
Format
8-18 Change Job Control Information Subentry Format
8-19 Change Area Subentry Format 8-20 Delete Version Subentry Format 8-21 Add Version Subentry Format 8-22 Delete Subschema Subentry Format 8-23 Add Subschema Subentry Format 8-24 DBMSTRD Utility Control Statement 8-25 Sample First Section of DBMSTRD Output 8-26 Sample Second Section of DBMSTRD Output
(Master Directory Contents) 9-1 Automatic Recovery Environment 9-2 Manual Recovery Environment
9-3 Schema Entry Format (DBREC Utility) 9-4 DBREC Control Statement
9-5 Sample Off-line Execution of DBREC Utility to Dump the Journal Log File 9-6 DBQRFA Utility Control Statement 9-7 DBQRFI Utility Control Statement 9-8 Format of Input for DBRCN and DBRST
U t i l i t i e s
9-9 DBRCN Utility Control Statement 9-10 DBRST Utility Control Statement 9-11 DBRST Example
9-12 Log Record Header 9-13 Transaction Log Record
9-14 Invoke and Version Change Log Record 9-15 Open Log Record
9-16 Privacy Breach Log Record
9-17 Before Image and After Image Log Records 9-18 Close Log Record
9-19 Terminate Log Record 9-20 Recovery Point Log Record
9-21 Restart Identifier File Record Format 10-1 Sequence of Operations to Establish
an Active Data Base Environment 10-2 CDCS Control Statement
10-3 Sample NOS System Procedure File 10-4 Sample NOS/BE System Procedure File 10-5 DOWN Command
7-7 10-6
10-7
7-8 10-8
7-9 10-9
10-10
8-1 10-11
8-3 11-1
8-3 11-2
8-3 8-6
8-6 11-3
8-7 8-8
8-8 11-4
8-9 8-9
8-9 11-5
8-10 11-6
8-10 11-7
8-11
8-12
TAB
8-12 2-1
2-2 8-13
8-13 2-3
8-15 3-1
8-15
8-15 3-2
8-15 3-3
8-16
8-18 3-4
8-21 3-5
9-1
9-2 4-1
9-6 4-2
9-7 4-3
4-4 9-10
9-10 4-5
9-10 5-1
5-2
9-11 5-3
9-12 5-4
9-14
9-16 5-5
9-17 7-1
9-19 7-2
9-19 7-3
9-20 7-4
9-20 9-1
9-21 9-21
9-22 9-2
9-22 9-23
10-1 10-2
10-4 10-2
10-9
10-9 10-3
10-11
I D L E C o m m a n d 1 0 - 1 2
R E T A I N C o m m a n d 1 0 - 1 3
R E T U R N C o m m a n d 1 0 - 1 3
S T A T U S C o m m a n d 1 0 - 1 4
U P C o m m a n d 1 0 - 1 5
S a m p l e S e r i e s o f O p e r a t o r C o m m a n d s 1 0 - 1 6 Sample Schema Named MANUFACTURING-DB 11-2 Sample COBOL Subschema Named C5SS-
PR0DUCT-PERS0NNEL and Subschema
L i b r a r y C r e a t i o n 1 1 - 5 Sample FORTRAN 5 Subschema Named
F5SS-PR0DUCT-EVALUATI0N and
S u b s c h e m a L i b r a r y C r e a t i o n 1 1 - 7 Adding Sample Query Update Subschema
Named QUPRODMGT to the Subschema
L i b r a r y I 1 - 8
Sample Master Directory Creation Run 11-9 Sample Master Directory Modification
R u n 1 1 - 1 0
S a m p l e D B R E C U t i l i t y R u n 1 1 - 1 1
V a l i d C l a u s e C o m b i n a t i o n s 2 - 2 Valid Schema/Subschema Class
C o n v e r s i o n s 2 - 4
F i l e C o n t r o l S t a t e m e n t P a r a m e t e r s 2 - J 2 Valid Schema to Subschema Class
C o n v e r s i o n s 3 - 4
Data Class Representation in the Schema J-5 Data Class Representation in the COBOL
S u b s c h e m a 3 - 5
Data Class Representation in the Query U p d a t e S u b s c h e m a J - b Va l i d I d e n t i fi e r a n d L i t e r a l
C o m b i n a t i o n s J - 3 1
O r d e r i n g o f S u b s c h e m a S t a t e m e n t s 4 - 1 S c h e m a / S u b s c h e m a M a p p i n g 4 - 4 D a t a T y p e s f o r C o n c a t e n a t e d K e y s 4 - 5 Names of Variables and Common Blocks
G e n e r a t e d b y t h e D M L P r e p r o c e s s o r 4 - 7 Column Usage in FORTRAN DDL Statements 4-8
D a t a C l a s s e s 5 - 2
V a l i d D a t a C o n v e r s i o n s 5 - 2 Data Class Representation in the Schema 5-3 Data Class Representation in the
S u b s c h e m a 5 - 3
N u l l V a l u e s f o r D a t a C l a s s e s 5 - 4 P a r a m e t e r L i s t F o r m a t s 7 - 3 Applicable Parameters for Type of Call 7-3 E n t r y C o d e s a n d Va l i d R e t u r n C o d e s 7 - 4 Data Base Procedure Time of Execution 7-6 Summary of Requirements of Data Base
Definition for Features of Automatic
R e c o v e r y 9 - 5
Summary of Permanent File Name S p e c i fi c a t i o n s f o r A l l o c a t i o n o f
F i l e s b y D B R E C U t i l i t y 9 - 9 Options Used With Parameters of the
O p e r a t o r C o m m a n d s 1 0 - 1 2 Information Returned by the STATUS
C o m m a n d 1 0 - 1 5
P a g i n g a n d R e c y c l i n g C o m m a n d s 1 0 - 1 6
NOTATIONS
R e f e r e n c e f o r m a t s a r e p r e s e n t e d t h r o u g h o u t t h e m a n u a l t o i l l u s t r a t e e s s e n t i a l e l e m e n t s o f s y n t a x . The notations used in the reference formats follow t w o c o n v e n t i o n s : t h e C O B O L c o n v e n t i o n a n d t h e FORTRAN convention. The COBOL convention is used i n f o r m a t s t h a t d e s c r i b e s y n t a x f o r t h e s c h e m a , COBOL and Query Update subschemas, master directory, a n d d a t a b a s e r e c o v e r y u t i l i t i e s . T h e F O R T R A N convention is used in formats that describe syntax f o r t h e F O R T R A N s u b s c h e m a a n d f o r a l l c o n t r o l statements. The differences in the conventions are i n t h e i n t e r p r e t a t i o n o f u p p e r c a s e w o r d s , t h e o m i s s i o n o f u n d e r l i n e d u p p e r c a s e w o r d s f r o m t h e FORTRAN convention, and the use of punctuation.
NOTATION USED IN REFERENCE FORMATS
UPPERCASE COBOL convention. Uppercase words are reserved words and must appear e x a c t l y a s s h o w n . R e s e r v e d w o r d s c a n b e u s e d o n l y a s s p e c i fi e d i n t h e r e f e r e n c e f o r m a t s . I f n o t underlined, they are optional.
F O R T R A N c o n v e n t i o n . U p p e r c a s e words are keywords and must appear exactly as shown. Keywords can be u s e d o n l y a s s p e c i fi e d i n t h e reference formats.
{ } B r a c e s e n c l o s e o n e i t e m o r s e v e r a l v e r t i c a l l y s t a c k e d i t e m s i n a reference format. When one item is enclosed in braces and followed by e l l i p s i s , t h e i t e m c a n b e r e p e a t e d a t t h e u s e r ' s o p t i o n . W h e n s e v e r a l i t e m s a r e e n c l o s e d i n b r a c e s , o n e of the enclosed items must be used.
| | | | V e r t i c a l b a r s e n c l o s e t w o o r m o r e v e r t i c a l l y s t a c k e d i t e m s i n a reference format when at least one o f t h e e n c l o s e d i t e m s m u s t b e u s e d . E a c h o f t h e v e r t i c a l l y stacked items can be used once.
• • • E l l i p s e s i m m e d i a t e l y f o l l o w a p a i r o f b r a c k e t s o r b r a c e s t o i n d i c a t e t h a t t h e e n c l o s e d m a t e r i a l c a n b e repeated at the user's option.
P u n c t u a t i o n u s e d i f f e r s f o r t h e c o n v e n t i o n s a s f o l l o w s :
COBOL convention
P u n c t u a t i o n s y m b o l s s h o w n w i t h i n t h e f o r mats are required unless enclosed in brac k e t s a n d s p e c i fi c a l l y n o t e d a s o p t i o n a l . I n g e n e r a l , c o m m a s a n d s e m i c o l o n s a r e optional. One or more spaces separate the elements in a reference format.
UNDERLINED COBOL convention. Underlined upper- UPPERCASE case words are required when the format in which they appear is used.
F O R T R A N c o n v e n t i o n . U n d e r l i n e d uppercase words are not used.
Lowercase
[ 1
Lowercase words are generic terms that represent the words or symbols supplied by the user. When generic t e r m s a r e r e p e a t e d i n a f o r m a t , a number is appended to the term for i d e n t i fi c a t i o n .
B r a c k e t s e n c l o s e o p t i o n a l p o r t i o n s o f a r e f e r e n c e f o r m a t . A l l o f t h e f o r m a t w i t h i n t h e b r a c k e t s c a n b e o m i t t e d o r i n c l u d e d a t t h e u s e r ' s o p t i o n . I f i t e m s a r e s t a c k e d v e r t i c a l l y w i t h i n b r a c k e t s , o n l y o n e o f t h e s t a c k e d i t e m s c a n b e used.
FORTRAN convention
P u n c t u a t i o n s y m b o l s s h o w n w i t h i n f o r m a t s a r e r e q u i r e d u n l e s s e n c l o s e d i n b r a c k e t s and specifically noted as optional.
N u m b e r s s h o w n w i t h i n f o r m a t s a r e d e c i m a l u n l e s s o t h e r w i s e s p e c i fi e d .
NOTATION USED IN EXAMPLES
T i n d i c a t e s t h e p o s i t i o n o f a n a s s u m e d d e c i m a l point in an item.
A plus or minus sign above a numeric character (n) indicates an operational sign is stored in combina tion with the numeric character.
Character positions in storage are shown by boxes.
A B C D
A indicates a space (blank)
60485200 A x i i i
INTRODUCTION TO DATA BASE PROCESSING WITH DMS-170 1
The DMS-170 software package functions as a data management system for Control Data computer systems.
Through this data management system, a data base c a n b e d e fi n e d , m a i n t a i n e d , a n d c o n t r o l l e d i n a n e n v i r o n m e n t i n d e p e n d e n t o f t h e a p p l i c a t i o n s t h a t a r e a c c e s s i n g i t . C o n v e n t i o n a l fi l e s o t h e r w i s e owned and processed by a number of distinct appli cations can be described through the data descrip tion language facilities of DMS-170. Consequently, t h e r e s p o n s i b i l i t y f o r t a s k s s u c h a s d a t a d e s c r i p t i o n , d a t a c o n v e r s i o n , a n d v a l i d i t y c h e c k i n g i s transferred from the application programmer to the d a t a a d m i n i s t r a t o r.
The DMS-170 data management system is composed of the following elements:
Data Description Language (DDL), which creates the schema definition, as well as the COBOL, FORTRAN and Query Update subschema definitions.
CDC CYBER Database Control System (CDCS), which c o n t r o l s , m o n i t o r s , a n d i n t e r p r e t s d a t a b a s e requests from COBOL, FORTRAN, and Query Update application programs.
CDC CYBER Record Manager (CRM), which handles a l l i n p u t / o u t p u t p r o c e s s i n g r e q u e s t s o n a d a t a base from an application program.
Data Manipulation Languages (DML), which pro vide for data base access through the COBOL and FORTRAN programming languages. The COBOL DML consists of features within the COBOL language.
The FORTRAN DML consists of DML statements that are used within a FORTRAN-coded program and processed by a DML preprocessor before FORTRAN c o m p i l a t i o n .
Query Update language, which provides for data b a s e a c c e s s i n b o t h i n t e r a c t i v e a n d b a t c h modes. Query Update is a language that enables i n d i v i d u a l s w i t h v a r y i n g l e v e l s o f t e c h n i c a l e x p e r t i s e t o a c c e s s a n d m a n i p u l a t e t h e d a t a base and to produce special-purpose reports.
Each element of the DMS-170 system is used either i n t h e d e fi n i t i o n o r i n t h e p r o c e s s i n g o f a d a t a b a s e . T h e d e fi n i t i o n o f t h e d a t a b a s e i s a c c o m p l i s h e d t h r o u g h t h e c a p a b i l i t i e s o f D D L a n d t h e m a s t e r d i r e c t o r y u t i l i t y. P r o c e s s i n g o f t h e d a t a base involves retrieval and updating of the data by application programs through the facilities of CDCS.
T h e D M S - 1 7 0 e n v i r o n m e n t d e fi n e s t w o r o l e s : t h e data administrator and the application programmer.
T h e d a t a a d m i n i s t r a t o r i s r e s p o n s i b l e f o r t h e d e fi n i t i o n o f a d a t a b a s e . T h e d a t a a d m i n i s t r a t o r is a person or group of persons who develop and define the data base as well as monitor and control t h e d a y - t o - d a y p r o c e s s i n g o f t h a t d a t a b a s e . T h e a p p l i c a t i o n p r o g r a m m e r u s e s i n t e r f a c e c a p a b i l i t i e s of COBOL, FORTRAN, and Query Update in developing applications for data base processing.
C D C offers gui del i nes for the use of the software described in this manual. These guidelines appear in appendix F. Before using the software described i n t h i s m a n u a l , t h e r e a d e r i s s t r o n g l y u r g e d t o review this appendix. The guidelines recommend use o f t h i s s o f t w a r e i n a m a n n e r t h a t r e d u c e s t h e e ff o r t r e q u i r e d t o m i g r a t e a p p l i c a t i o n p r o g r a m s t o future hardware or software systems.
DATA BASE DEFINITION
To define a data base, the data administrator uses the Data Description Language (DDL). Through this l a n g u a g e , f o u r t y p e s o f d a t a d e s c r i p t i o n s c a n b e c r e a t e d : t h e s c h e m a , t h e C O B O L s u b s c h e m a , t h e FORTRAN subschema, and the Query Update subschema.
E a c h o f t h e s e d a t a d e s c r i p t i o n s f o l l o w s s p e c i fi c s t r u c t u r i n g c o n v e n t i o n s , i n c l u d e s u n i q u e c l a u s e s and s ta te me nts , an d c on for m s to an individual s et of rules. Once the schema and COBOL, FORTRAN, and Q u e r y U p d a t e s u b s c h e m a d e s c r i p t i o n s h a v e b e e n c r e a t e d a n d c o m p i l e d , t h e d a t a a d m i n i s t r a t o r c r e a t e s t h e m a s t e r d i r e c t o r y t h r o u g h o n e o f t h e d a t a b a s e u t i l i t y r o u t i n e s p r o v i d e d a s a p a r t o f
CDCS.
The relationship of the elements involved in defin ing a data base is shown in figure 1-1. The figure Indicates that the schema directory must be avail a b l e t o t h e D D L c o m p i l e r t o g e n e r a t e s u b s c h e m a d i r e c t o r i e s . B o t h t h e s c h e m a d i r e c t o r y a n d s u b s c h e m a d i r e c t o r i e s m u s t b e a v a i l a b l e t o g e n e r a t e t h e m a s t e r d i r e c to r y.
The data descriptions In the schema and subschema a r e o r g a n i z e d i n t o fi l e - l i k e s t r u c t u r e s . B y c o n v e n t i o n , t h e f o l l o w i n g t e r m s a r e u s e d w h e n r e f e r r i n g t o t h e s e s t r u c t u r e s :
Area in the schema Realm in the subschema
T h e s c h e m a d e s c r i p t i o n o f a n a r e a a p p l i e s t o a l l data within the structure. The subschema definition o f a r e a l m u s u a l l y a p p l i e s t o a p o r t i o n o f d a t a within the structure but can apply to all the data.
T h e a r e a p r o v i d e s t h e a c t u a l d e s c r i p t i o n o f t h e d a t a . T h e r e a l m p r o v i d e s t h e d e s c r i p t i o n o f d a t a from the viewpoint of the application programmer.
The term file is used in this manual to refer to an area or realm.
SCHEMA DEFINITION
T h e s c h e m a i s a d e t a i l e d E n g l i s h - l i k e d e s c r i p t i o n o f t h e d a t a i n a d a t a b a s e . A u s e r s i t e c a n h a v e many data bases, but only one schema is allowed for each data base.
60485200 A 1-1
Master Directory I n p u t
D D L Schema
Input
D D L Compiler
Schema Directory
Master
Directory U t i l i t y
Master Directory
j L z.
DDL Subschema I n p u t (COBOL, FORTRAN,
Query Update)
D D L Compiler
Subschema ( D i r e c t o r i e s I (COBOL. FORTRAN,
\ Query Update)
^s"^!\
Figure 1-1. Data Base Definition
The schema provides the logical description of the data base. A schema can be associated and used w i t h s e v e r a l p h y s i c a l d a t a b a s e s . A p h y s i c a l d a t a base is a set of files associated with the areas of the schema. This association Is described later in t h e M a s t e r D i r e c t o r y D e fi n i t i o n s u b s e c t i o n a n d i n the Data Base Versions subsection.
The schema description is created by DDL statements t h a t n a m e t h e s c h e m a , o r g a n i z e t h e s c h e m a i n t o areas, describe each record type with characteris
t i c s o f t h e d a t a , a n d d e s c r i b e r e l a t i o n s h i p s a n d constraints among areas. The schema also includes a c c e s s c o n t r o l l o c k s t h a t p r o v i d e a r e a p r i v a c y.
The DDL source statements describing the data are used as input to the DDL compiler and are compiled i n t o a n o b j e c t s c h e m a , o r s c h e m a d i r e c t o r y. T h e data administrator then uses the schema to define
any number of subschemas.
SUBSCHEMA DEFINITIONS
A s u b s c h e m a i s a d e t a i l e d d e s c r i p t i o n o f s e l e c t e d portions of data described by a schema. The sub schema defines the portion of the data base avail a b l e t o t h e a p p l i c a t i o n p r o g r a m ; t h e a p p l i c a t i o n program uses the subschema descriptions to access t h e d a t a b a s e . T h e s u b s c h e m a i s b a s e d o n t h e schema.
The data descriptions in the subschema are orga n i z e d i n t o r e a l m s t h a t c o r r e s p o n d t o a r e a s i n t h e schema. The realms included in a subschema can be a s u b s e t o f t h e a r e a s i n t h e s c h e m a . T h e d a t a i t e m s w i t h i n t h e r e a l m i n a s u b s c h e m a c a n b e a s u b s e t o f t h e d a t a i t e m s d e s c r i b e d f o r t h e c o r r e sponding area in the schema. Figure 1-2 illustrates t h e s i t u a t i o n i n w h i c h a s u b s c h e m a d e s c r i b e s a portion of a data base.
Physical Data Base (Data Base Files)
Shows schema d e s c r i p t i o n .
Logical Data Base ( D e s c r i p t i o n )
Schema Areas A, B, C, D
Shows schema and
subschema descriptions. Subschema
Realms A, C, D
A schema describes all data base files with
area descriptions.
A subschema describes portions of data base fi l e s w i t h r e a l m d e s c r i p t i o n s . Figure 1-2. Subschema Describing a Portion of the Data Base
/S^*V
Although only one schema is allowed for each data base, any number of subschemas can be defined to m e e t t h e n e e d s o f d i ff e r e n t t y p e s o f a p p l i c a t i o n s . S u b s c h e m a s a r e d e fi n e d b y t h e d a t a a d m i n i s t r a t o r f o r u s e b y a p p l i c a t i o n p r o g r a m s w r i t t e n i n t h e COBOL, FORTRAN, and Query Update languages.
COBOL Subschemas
A COBOL subschema is defined through the capabili ties of the DDL language. COBOL subschemas describe in COBOL-like syntax the parts of a data base that can be accessed by a COBOL program. Data descrip t i o n s i n C O B O L s u b s c h e m a s o u r c e s t a t e m e n t s a r e w r i t t e n t o c o r r e s p o n d t o d a t a d e s c r i p t i o n s i n t h e s c h e m a . C e r t a i n d i ff e r e n c e s a r e a l l o w e d t o e x i s t ; these differences are resolved by DDL and CDCS.
The COBOL subschema is generated by DDL source statements that identify the schema and subschema, s p e c i f y r e a l m s a n d t h e c o n t e n t a n d s t r u c t u r e o f r e c o r d s , i d e n t i f y r e l a t i o n s a m o n g r e a l m s t o b e u s e d , s p e c i f y r e c o r d q u a l i fi c a t i o n f o r r e l a t i o n processing, and indicate any changes in data format
required by the application program.
The DDL source statements describing the subschema a r e c o m p i l e d b y t h e D D L c o m p i l e r i n t o a n o b j e c t s u b s c h e m a , o r C O B O L s u b s c h e m a d i r e c t o r y. T h e schema must be compiled, however, before any sub schemas using it can be compiled. A COBOL program mer then uses a listing of the subschema to learn the names and descriptions of the data to be refer enced in the COBOL program. Data descriptions from
t h e s u b s c h e m a a r e a u t o m a t i c a l l y i n c l u d e d i n t h e COBOL program when it is compiled.
FORTRAN Subschemas
A FORTRAN subschema is defined through the facili ties of the DDL language. FORTRAN subschemas use statements similar to FORTRAN specification state ments to describe the parts of a data base that can
be accessed by a FORTRAN program. Data descrip tions in FORTRAN subschema source statements are w r i t t e n t o c o r r e s p o n d t o d a t a d e s c r i p t i o n s i n t h e s c h e m a . C e r t a i n d i ff e r e n c e s a r e a l l o w e d t o e x i s t ; these differences are resolved by DDL and CDCS.
The FORTRAN subschema is generated by DDL source statements that identify the schema and subschema, s p e c i f y r e a l m s a n d t h e c o n t e n t a n d s t r u c t u r e o f r e c o r d s , i n d i c a t e c h a n g e s i n d a t a f o r m a t r e q u i r e d b y t h e a p p l i c a t i o n p r o g r a m , i d e n t i f y r e l a t i o n s among realms to be used, and specify record quali fi c a t i o n f o r r e l a t i o n p r o c e s s i n g .
FORTRAN subschemas, like COBOL subschemas, cannot be compiled until the schema being used has been compiled. Once the schema has been compiled, the DDL source statements describing each subschema are compiled by the DDL compiler into an object sub schema, or FORTRAN subschema directory. A listing of the subschema is used by the FORTRAN programmer to obtain the names and descriptions of the data to be referenced in the FORTRAN program.
Query Update Subschemas
Q u e r y U p d a t e s u b s c h e m a s a r e d e fi n e d t h r o u g h t h e c a p a b i l i t i e s o f t h e D D L l a n g u a g e . Q u e r y U p d a t e subschemas describe in COBOL-like syntax the parts of a data base that can be accessed through Query U p d a t e d i r e c t i v e s . T h e d a t a d e s c r i p t i o n s i n Q u e r y Update subschemas are written to correspond to data d e s c r i p t i o n s i n t h e s c h e m a . C e r t a i n d i f f e r e n c e s between the subschema and schema data descriptions a r e a l l o w e d t o e x i s t ; t h e s e d i f f e r e n c e s a r e resolved by DDL and CDCS. For each subschema, the D D L s o u r c e s t a t e m e n t s u s e d a s i n p u t t o t h e D D L compiler name the schema and subschema, specify n e e d e d r e a l m s a n d t h e c o n t e n t a n d s t r u c t u r e o f r e c o r d s , i d e n t i f y r e l a t i o n s a m o n g r e a l m s t o b e u s e d , s p e c i f y r e c o r d q u a l i fi c a t i o n f o r r e l a t i o n processing, and indicate any changes in data format required by the Query Update program.
60485200 A 1-3
After the schema has been compiled, the DDL source statements describing the subschema are compiled by t h e D D L c o m p i l e r i n t o a n o b j e c t s u b s c h e m a , o r subschema directory. The names and descriptions of data to be referenced in a Query Update program are obtained from a listing of the subschema.
T h r o u g h f a c i l i t i e s o f D M S - 1 7 0 , a C D C S - c o n t r o l l e d data base can be accessed through Query Update directly by CRM. Refer to appendix J for Informa
t i o n a b o u t t h i s i n t e r f a c e . T h i s m a n u a l d i s c u s s e s only Query Update data base access through CDCS.
MASTER DIRECTORY DEFINITION
The master directory must be created by the data a d m i n i s t r a t o r b e f o r e a n y a p p l i c a t i o n p r o g r a m s a c c e s s i n g d a t a b a s e fi l e s c a n b e e x e c u t e d . T h e master directory contains all information about the data base known to CDCS. This includes information a b o u t s c h e m a s a n d s u b s c h e m a s a s p r e v i o u s l y d e s c r i b e d i n t h i s s e c t i o n . T h i s a l s o i n c l u d e s information about the following elements, which are d e s c r i b e d l a t e r i n t h i s s e c t i o n : d a t a b a s e p r o c e d u r e l i b r a r i e s , l o g g i n g s p e c i fi c a t i o n s f o r d a t a b a s e fi l e s , l o g fi l e s , a n d d a t a b a s e v e r s i o n s . I n a d d i t i o n , t h e m a s t e r d i r e c t o r y f u n c t i o n s a s t h e source of all data base and media descriptions for CDCS.
If a data base has versions, these data base ver s i o n s a r e d e fi n e d i n t h e m a s t e r d i r e c t o r y. A d a t a base version is a set of permanent files for areas d e s c r i b e d b y a s c h e m a . T h r o u g h d e fi n i t i o n o f v e r s i o n s i n t h e m a s t e r d i r e c t o r y a s i n g l e s c h e m a can be associated with more than one set of perma n e n t fi l e s .
To create or update the master directory, the data a d m i n i s t r a t o r u s e s t h e D B M S T R D u t i l i t y. I n p u t f o r t h e u t i l i t y c o n t a i n s i n f o r m a t i o n t h a t a s s o c i a t e s subschemas, a data base procedure library, log and r e c o v e r y fi l e s , a n d d a t a b a s e v e r s i o n s w i t h a schema. Input can also associate areas of particu l a r d a t a b a s e v e r s i o n s w i t h p e r m a n e n t fi l e s a n d l o g g i n g s p e c i fi c a t i o n s . T h e i n f o r m a t i o n a b o u t p e r m a n e n t fi l e s t h a t i s s p e c i fi e d i n t h e m a s t e r directory provides CDCS the information required to a t t a c h t h e p e r m a n e n t fi l e s , i n c l u d i n g t h e a c t u a l p e r m a n e n t fi l e a s s o c i a t e d w i t h a p a r t i c u l a r a r e a a n d v e r s i o n , i n d e x fi l e s , l o g a n d r e c o v e r y fi l e s , a n d p r o c e d u r e l i b r a r y fi l e s . A f t e r t h e m a s t e r directory has been generated, it must be stored as a permanent file.
In the process of maintaining a data base environ m e n t , t h e d a t a a d m i n i s t r a t o r m i g h t w a n t t o a d d information for one or more new schema definitions, d e l e t e o r m o d i f y e x i s t i n g s c h e m a i n f o r m a t i o n , o r m o d i f y p e r m a n e n t fi l e i n f o r m a t i o n f o r d a t a b a s e fi l e s a n d p r o c e d u r e l i b r a r y fi l e s . U n d e r a n y o f these circumstances, appropriate changes must be made to the master directory through a modification run. A new data base cannot be accessed by appli c a t i o n p r o g r a m s u n t i l t h e a p p r o p r i a t e i n f o r m a t i o n f ro m the c orres pondi ng s ch e ma an d su bsc hem a i s
a d d e d t o t h e m a s t e r d i r e c t o r y. S i m i l a r l y, w h e n information pertaining to a schema is deleted from t h e m a s t e r d i r e c t o r y, s u b s c h e m a s a s s o c i a t e d w i t h the schema can no longer be used by application p r o g r a m s . O n e o t h e r f o r m o f m o d i fi c a t i o n a l l o w s t h e a d d i t i o n o r d e l e t i o n o f i n f o r m a t i o n p e r t a i n i n g to subschemas. No subschema can be referenced by a user during execution unless information about that subschema exists in the master directory.
DATA BASE PROCESSING
O n c e a d a t a b a s e h a s b e e n d e fi n e d b y t h e d a t a a d m i n i str a t o r, t t ca n b e a c c e s s e d a n d mo d i fi e d b y users of the COBOL, FORTRAN, and Query Update a p p l i c a t i o n p r o g r a m m i n g l a n g u a g e s . T h e r e l a t i o n
ship of the elements involved in processing a data base is shown in figure 1-3.
The following subsections introduce the processing facilities of CDCS.
APPLICATION LANGUAGES
The data in a data base can be accessed by the following application languages: COBOL 5, FORTRAN | 5, and Query Update. Processing of the data base by COBOL, FORTRAN, and Query Update programs is c o n t r o l l e d a n d m o n i t o r e d b y C D C S . T h e s e application languages can be used in either batch or interactive mode.
COBOL Processing
A COBOL program accesses data base files through c o n v e n t i o n a l i n p u t / o u t p u t s t a t e m e n t s . T h e fi l e s are opened and closed and records are read, writ ten, deleted, and updated using the same means as f o r fi l e s t h a t a r e n o t p a r t o f a d a t a b a s e . R e l a tion processing is also accomplished by conventional COBOL statements. Data retrieved by the program is accessed in accordance with the way it is described in the COBOL subschema.
When a COBOL program using CDCS is to be compiled, t h e fi l e c o n t a i n i n g t h e s u b s c h e m a d i r e c t o r y m u s t fi r s t b e a t t a c h e d . O n c e t h e p r o g r a m i s c o m p i l e d u s i n g t h e s u b s c h e m a , i t c a n b e e x e c u t e d l a t e r without reattaching the subschema directory.
E x e c u t i o n o f a n i n p u t / o u t p u t s t a t e m e n t f o r a d a t a base file in a COBOL program causes the COBOL o b j e c t - t i m e r o u t i n e s t o r o u t e i n p u t / o u t p u t c a l l s t o CDCS. CDCS controls all processing of data base fi l e s .
FORTRAN Processing
X-»3«%k
/ * U ^ w
A FORTRAN program accesses data base files through DML statements coded within the FORTRAN program.
The DML consists of FORTRAN-like statements. These statements allow the FORTRAN user to access and modify data base files.
Recovery Utilities Input
COBOL Program
— — d a t a a d m i n i s t r a t o r
FORTRAN Subschema Directory
Query Update, Subschema
Directory
COBOL Subschema
Directory
Master Directory
Recovery Utilities
H L o g Files p^ L
CDCSCRM
Data Bases
FORTRAN/
DML
Program Query Update
Directives
COBOL Compiler
COBOL Object Program
DML Preprocessor
Query Update
FORTRAN Compiler
FORTRAN Object Program
Figure 1-3. Data Base Processing With CDCS
000®^
60485200 A 1-5
