Base Systems, O.

Volltext

(1)MDBS. Data. Documentation. System. Management. Version 1.04. Micro. Data P.. Base Systems, O.. Box. Lafayette,. Inc.. 248. Indiana 47902. (317). 448-1616. (317). 742-7388. August. 1980. Copyright Notice. This eustomer"s Micro. employees.. Data. prohibited. Base except. Base Systems, ©. manual. entire. COPYRIGHT. is provided for the use The. entire. Systems, as. contents have. Inc.,. permitted in. of". and a. the been. reproduction. written. agreement. customer. and the. copyrighted. by. by any means. is. with Micro. Data. Inc. 1979,. 1980,. Micro. Data. Base Systems,. Inc.. 1.

(2) MDBS. 2!at:. Manage:. a. ment. System. Documentation ?REFACE. Tk. i. t. ocj !. rnan"ctai. '3. in soCtware. innovaiions. wit!. sof't.ware. the. is the. management. techniques. ínríovatícmc. are. restructuring. suppc·rt. focal. the. computers.. types. as the. be. i-f"". t:yµe. on. combined. We. Ba. iev. be!. inquirü-es. o. t.. he. b 3-s e. 'iía" a The :e. [. t.wo '. j7y"7teTt". ""' 1>. that. capability. Th f'. The seconc!,. .. TJata. two. w .i t" r2. structures.. !v!imê. a. íj?á. E3sf±. .-."g. supporting. and. their ability to change, will become. they are already in mini— and mixi-":. i th w. chip"). a. t.. 1g7;g"s-. t.he. sophisti.c"ttéñ data. e. t.ha. hardware. of the dernrnds. riat-ure. its fantastic. i th. formidable tcol. a. purpose. such. a. i". o. th i s. ?. .. o. r. computing. power"í"v-l. a. data. mana¿"ing. \n'. Haseman. .. Martin,. D .. J. Englewood COPYRIGHT. manual. s. to the area. suitable. and. power. base. c) yj. management. enterprises. c. f". a. }. l. 1979,. .. ,. A. an d. .. is twoPold. base. data. of". Since. management.. real ly cari". we. First there is. t. do. complete. this. justice. references are:. Richard. Management, 2.. ". user. vast and important area. this topic 1. ©. their'. w. basis,. th. t. !7. The uÜcro—coírµuter.. introduc".or,y material to. i. iri. computer. highly. f. use as. .. Th e. is. w. as. will. system,. f. ?4anagement System.. software in uüicro"s. per—dollar. a-. o. it.s. :. rnêdicted. scene. (computer o. to "what.. retrieval. selective. us e. (DBMS). systems. mar,agernent. ar' e a. together in. Ba: 3e. management. and. computing. to eont:"o1 complex. com'{'i";nec!. í'at.a. base. exµerts Rave. micro—computers. advarice,. soghisticated. th e th e. i rí. data Many. dominate. is. of". devel"jµrr\e-nt. wiU"z. development.. innovation. first a. cc: ncerTjed. Z·3. .. D.. Comouter. Cliffs,. NJ,. 1980,. bFcro. B. Whinston,. .. Irwin. .. Inc.. Data—Base. Introduction ,. Homewood.. IL. ,. t. o. Da. ta. 1977.. Organizat.íori, Prericice. Ha. I ! ,. 1975. Data. Base Systems,. Inc.. 2.

(3) MDBS. Data. 248, second. goal. through the use. this. of OÍ". MDBS.DDL. Finally, we request in their view, we have used. there. actually. been. manual. these. that is. truly innovative. ©. COPYRIGHT. detailed. Here our. aim. from. our. in achieving these of. you achieved. tit. sQt"tware. 1979,. 1980,. companion. as. how. the. and. MDBS.DDL. expected. successful,. Have. goals.. MDBS.D!A.S. you should. results?. to what. we. feel is. product in the micro--computer. Micro. be. to. is. how. readers as to. suggestions in future versions to a. tour. guided. possible.. as. comments. a. points where the steps were unclear or ambiguous?. to incorporate a. have. MDBS.DMS.. and. been. is to give. manual. to follow our description and. Box. Inc.,. 1979.. and as comprehensive. complete. able. IN,. Lafayette,. MDBS. Base Management,. on Data. Holsapple, C., Primer. 3.. The. Documentation. System. Management. Data. Base Systems,. Inc.. finally a. Or We. been be have. plan. achieve. remarkable. and. area.. 3.

(4) MOBS. 2ata. Management. System. Documentation. TABLE. OF. CONTENTS. Page. I.. II.. INTRODUCTION... MDBS.DDL. !5. .. DATA. DESCRIPTIObl. ..... A.. Introduction...................................... B.. Features.. C.. Getting Started With. .. ... . .. ... . . . . . . . . . . . .. Initial. 2.. Relocating. 3.. Important. D.. MDBS. 1. 2. 3.. MDBS.DDL. 5.. LU)L. COPYRIGHT. . . . .. . . . .. . .. run........ -......... and. of. 2Z. Language.................... 25. and,. example................. Operation................................ Micro. 20. 23. owner/member. 1980,. 2C. patching MDBS.DDL........... Introduction................................. Text Entry/Commanci mode...................... 1979,. 18. addresses:. Specifications........................... Notes on Data Bm: e Files........... Modes. 2.. . .. Definitions................. IJDL Example.................................. Many—to—Many Example......................... Iritroduction. Multiple. 1.. . .. KIDBS.DDL........................... Description. 4.. El.. E.. Data. . . . . . . .. 1'7. i': '. MDBS.DDL..................... loading and test.. i.. Personalizing. ©. LANGUAGE..... Data. Base Systems,. Inc.. 25 27. 33 40. 44 7C). 72 72 75. 4.

(5) Data. MDBS. III.. Management 3.. Line editing. 4.. DDL. MDBS.DMS. analyzer. DATA. Documentation. mode............................ mode............................. MANAGEMENT. SYSTEM....................... 95 103 149. A.. Introduction...................................... 149. B.. Features. 150. C.. Getting Started With. D.. ............................... 1.. Relocating. 2.. Personalizing. MDBS. 1.. Data. MDBS.DMS..................... MDBS.DMS.......................... and. Management. patching MDBS.DMS........... System....................... Introduction............... ....... Calling procedure............................ Data management system routines..-............ 2. 3. IV.. System. CONCLUDING. REMARKS......................... 151. 151 151. 155 155 174 177 258. APPENDIX. 1............................................ 262. APPENDIX. 2............................................ 264. -. ©. COPYRIGHT. 1979,. 1980,. Micro. Data. Base Systems,. Inc.. 5.

(6) MDBS. Data. Management. System. Documentation DDL. (a). Mnemonic. By. Pa ge. BAGKSPACE-key. Delccte. BYE. Return. .. .. .. to operating system.. C. Change. a. Repeat. changes.. C. text.. C. Control. H. Control. P. Toggle. Control. X. Interrupt.. . . .. ap. Backspace. and. DDL. Data. .. text.. . .. . .. delete. . . .. . . . , .. line. a. of". B.acksp·ace and. format.. Enter line edit mcAe.. EN. Data. t-o. F'at-a.. description. IT. Fcítta. descrij"±:. L. List t e x t. ME. Data. N. Renumber. OW. Data. p. Print. PA. Data. de'umi"iption. R. Read. a. CC'"YF?IGHT. 1979,. iggj,. . .. ... thc'. text.. description space. text Micro. . .. ... . . . . . . .. . .. . . . . .. . .. . . . .. .. . . . . . . .. .. ... . .. 74 '74. . .. 73. .. 73. .. .. ... - .. Analyzer.. character.. . . . .. 80. 73. . . . . . .. 83. . . . . . . . .. 85. for dri'íe. . . .. . . . . . .. . . . . .. format Í"or. . .. file.. . . . . . . .. 79 83. . . . .. 83. . . . .. 86. . .. 83. . . . . . . . . . . . . . . . . . . . .. 88. . . . .. .. 83. ... .. . . . . . . . .. . . . . . . . . . . . . .. format tor member. .. 82. ... . . . . . .. .. format for end line.. format f"or owner.. ruler.. . . . . . .. í'ormat. ... ..... . . .. . .. . .. . . .. . . .. for password.. tile........................ Data. 1 C) Ci. .. . .. q. 97. ... . . . . . .. .. . . . . . .. 74. . . . .. ion format for" item. ... description. a.. . . . .. "7. ogerating system.. I. F. .. .. . . . . .. . . .. a. it ¿—d. Return. .. ...... ................ delete. description. ... character.. Language. description. .. . . . . . - . . . . . . . . .. input.. t-ext......... Definition. . .. . .. a. Data. Key. .e. . . . . . .. DR. ESCAPE-. . . .. operation.. outpu!-. Delete. .. of". Interrupt. D. Key. .. line. Ccmtr<il. ÚELETE. ©. COMMANDS. Base Systems,. Inc.. .. ... , . .. 83 9. O. 83 91. 6.

(7) Data. MDBS. ©. Management. Documentation. System. RE. Data. RETURN-Key. End. RETURN-Key. Move. S. Leave. SE. Data. W. Write. a. 1980,. Micro. COPYRIGHT. 1979,. description the. record....... 83. input....,....... 73. text........................ 96. current. through the. editor". description text. format for line. Oí7. mode................... format for set.......... file........................ Data. Base Systems,. Inc.. 99 83 93. 7.

(8) MDBS. Management. Data. System. Documentation DDL. (b). By. Function. Backspace Change. and. delete. line. a. def"inition. Data. description. End. the. . .. ... current. List text. Move. Read. .. e. te. ). ine.. x t-. .. a. COPYF'IGHT. text. .. ... . .. . .. . . .. . . . . .. iní?'Llt. ^. . . . . .. . . . . .. . . . . . .. . .. . . . .. . . . . . . . .. .. 73. ... .. ... .. 97. . . .. . . . . . . . . . . . . . . .. .. 82. . . - . . . .. 83. .. . . . . . . . .. . . - . . .. . . . . . . . .. . . . . . .. . .. . .. . . .. . . . . .. . . . . . .. . .. . .. - . .. . . -. .. ... . . . . . .. . . . . . . - .. .. , . . .. - . . . .. .. 73. . . . .. 85. . .. . .. '3 Q. . .. .. ... - .. q9. .. . . . .. , . . . . . . .. . . . . . . . . . . . . . .. . . . . . .. . .. . . . . .. . . .. . .. . . . . - . . . . . . . . .. . . . , .. . . , . .. . .. 86. . . ,. 96. . . .. . .. . . . . , . . . , . .. . . . . . . . . - . . . - . . . .. . . . - . . . . . . .. . . . . . . .. <4j L~". . .. 88 1 O C). . . .. . . . . . .. . . . .. . . . . .. . . . . . . - . . . . . . . .. . . .. . . . . . . . . 0 . . . . .. .. . . . . . .. . . .. 0 . .. . . . . . . . .. . .. . - . > . .. !980,. Micro. Data. 7 :"3. 79. ,. file................... ........... .... ..... 1979,. ga. ·. V * · * 0 t · O · * D 0 6 6 » 0 b . P b r E 4 P r + · P y · P · V · · t. to operating system.. Return. Write. a. ... 'jf. . . .. ruler.. charÁEes-. Restart. . .. .. .. .. .. analyzer.. c'cmman&m. mode.. a. t. "h. Penümber Repeat. mode. ri1e... text. a. .. line. text.. space. a. . .. . . .. . . . . . . . . . . . . . . . . . . . .. through. Print. ... Í7ormat.. editor. t-he. .. language. Enter line edit Leave. character".. a. text.. of". Data. Delete text-.. ©. COMMANDS. Base Systems,. Inc.. 93. 8.

(9) Documentation. System. Management. Data. MOBS. MESSAGES. ERROR. DDL. ?age A. DEPENDING. A. VARIABLE. CANNOT. HAVE. CANNOT. ITEM. TO. DISK. SYSTEM. DEPENDING. o'\í. ITEM. MUST. BE. Éí. DEPENDING. ON. ITEN. lvlUST. BE. BINARY. DEPENDING. ON. ITEM. t{oT. DUPLICATE. ITEP!. DUPLICATE. RECORD. DUPLICATE. FET. ERROR. .. . .. NAME. NAME. NAME. . . . . . . . .. EXPECTING. A. NUMBER. EXPECTING. A. RECORD,. EXPECTING. AUTO. EXPECTING. GET. FILE. HAS. NOT. IMPROPER. OR. DRIVE. . .. . . .. IN. MAN. MEMBER. INCORRECT. OWNER. ORDER. SET. CHARACTERISTICS. INVALID. SET. TYPE. ITEM KEY. READ. OR. COPYRIGHT. 1973,. ... ... 'n'EITE. UNDECLARED. .. . .. THLS. . . . .. RI'CCRU. .. ... . .. . . . . . . . . . . . . . . . . . . . .. . . .. . . . .. . . . . . . . . . . . . . . . . .. . . . . .. . .. . .. í12 113. . . . . . .. . . .. . .. . .. SO. . .. . . . .. . . .. ... . . . . . . . .. . . .. ... .. . .. ..... . . . . - .. . .. . . . . . . .. . . . . . .. .. . - . -. ... , . .. ... .. ... . . .. ... . .. .. . . .. Micro. . .. THAN. RECORD'S. . . . . . . . . . .. Data. 1(3. :. r' 8. 121. 122 Z23. 12-l !. 25. ' 2(3. .. LESS. !. !ZG. ... . .. .. ... . . .. . . .. , . . .. i5. 119. . . . . . . .. . . . . .. 1. j1. . . . . . . .. . . . . . .. .. ... i4. . .. .. DC. :. .. .. LINE. 11. j.. .. ... .. .. .. .. .. .. .. .. ... ACCESS. 1980,. If.!. . . . . . .. .. . . . . . . . . .. . . .. lj9. .l. ... . . . . . . . . . . .. . . . .. ...... . . . . . . . .. VARIABLE. BINARY. !08. . .. ... SET. . . .. . . - . .. INVALID. TYPE. . .. . . . . . . . . . . . . . . .. .. . . .. . . .. ITEM. ......... .-......... !0'7. ... DEFINED. PLEASE. . . .. INVALID. 106. .. ................... ........... CREATED:. ORDER. ... . .. DR. ZJNE. . .. RECOFD. A. . . . . . . . . . . . . . . . . . .. . .. . .. ... IN. ... .. t 1 C). . . . . . .. FIELD. A. NUMBER. INCORRECT. . . . . .. ITEM,. END. BEEN. . . .. . . . . . . . . .. . .. OR. RECORD. . . . . .. ... . . . . . . . . . . . .. pREvIc)Ugij.Y IN. . .. BYTE. TWO. 105. .. LAST. .. .. ... WITH. FIELD. REPEATED. A. BE. ........ OWNERS. OTHER. BE. MUST. ITEM. LENGTH. WRITE. CAN'T. e. ON. . . . .. . . . . . .. . . . . . . . . . . . . . . . .. Base Systems,. inc.. 12'7. 128. 9.

(10) MOBS. Kata MAY. Management. System. LENGTH. MAXIMUN N.LMES NG). rn:. FOR. RECORD CANNÜT. PAGES. LARGER. PASSWORD. ENTRY. PREMATURE. END. ACCESS. READ. ACCEGG. RECGRD. NOT. REPEATED. £OF?T. NOT. LINE. KEY. SYFJTEKJ. COPYRIGHT. OF. BE. E. 1979,. GET. ... . .. . .. . .. ... . . . .. . . .. ',. .. . . . . . . . . . .. F32 E. ... . . .. . .. . .. . . . . .. 256. . . .. .. ... . . .. .. ... .. .. . . . . . .. EXPECTED. .. . . .. ... .. . .. ... . . .. .. ACCEF3. 'S. .. . . . .. . , . . . .. .. 138. . . . . .. . . . .. .. 139. . .. . . .. . . .. i "tc). . . . . . .. i 42. . . . . . . . .. 143. . . . . . - . .. . . . . . . . . .. . .. . .. AND. . . . . . . . . . .. CURRENT. ... . .. .. . . . . . . .. . . . . . . . .. .. . .. . . .. ... ... ITEM. ..... Base Systems,. .. 144. . . .. 145. . . .. .. .. .. .. i46 .. ... . .. 147. . . . . .. . .. 148. . . . . . . . .. . . . . .. i-41. . .. . .. ... Data. . . . . .. . .. INVALID. . . . . . . .. Micro. 137. ... . . . .. . . . - . .. .. 136. . . . . . . . . . .. . . .. .. .. ... 23. 135. .. ... . . . . . . . . .. .. 3C. 131. ... . . . . . . . . . .. . . . . .. DZ7ENDTNG. MEMBER.. 1980,. .. . . . .. . . . . . .. . . . . . .. DEFINITION. 'T. CAb'. . .. : .\/PITE. FGR. RECORD. . .. . . . .. . . . . . . . .. IN. . . .. 129. . . . . . . .. . . .. THAR'. NOT. SET. .. .. ... . .. 3Y. LINE. LARGE. EQUAL GET. ... .. THAN. . . .. PAGE. BLANK. A. . . .. ON. . . . .. 1. ZORTJ. INF'U". TOO. FOR. . . . . .. . . .. FIT. BE. . . . . . . . .. GREATER. ITEM. ACCESS. SECOND. RF:. 2. . . . . . . . . . . .. EX7ECTED. FOUND. OR. DI\U31!3LE. BE. IG TO. FILE. A. 255. OR. $. A. DEI'/E. GREATER. EzccíRD. R/W. CEil. OF. LARGÉ. LINE. Tci. MUST. LINE. TOO WITH. THAN. PASSWORD. \'ARIA!3LE. OWNER. ROOM. LENGTH. PAGE. C:. START. ALLOCATED. ENñUgH. NUMBER. SIZE. AÑD/OR. XEMBER. ¡'.;¿y;. BINARY. Documentation. . . .. Inc.. I C).

(11) MDBS. Data. Management- System. Documentation. INDEX. Cornmand. ÁCS. Add. Current. AMS. Add. Member. CLOSE GMT COT CR CRS. DEFINE. COMMANDS. OÍ". unit to Set. run. ......,.......... .............................. Check Current of run unit Type ..¥.............. the data ............................. Type Check cLlrrer}t ...................... Check current Owner Type ....................... Create Record ................................M. Create Record and Store data ................... DEFINE data bloek............................. to Set. 184. a. Delete Record based. on. current Member. DRO. Delete Record based. on. current Owner. FFO FINDM FINDO FLM FLO FMSK FNM FNO. COPYRIGHT. 182. Member. DRM. FFM. 180. 183. Delete Record based on Current of run unit. EXTEND. 179. b¿)se. CLOSE. DEC. DRR. E). DML. Page. DML. CCT. OF. 185 186 1É37. 189. ...... í90. .......... ........... Delete Record based current Record .......... data block............................. Find First .......,...................... Find First Owner ............................... FIND ...............................,.... FIND Owner ......,....................,......... Find Last .....................,......... Find Last Owner ................................ based 'Sort Yey Find .................. Find Next ............................... Find Next Owner ................................. 192. on. EXTEND. a. Member. Member. Member. Member. oí":. Member. 1979,. 1980.. Micro. Data. Base Systems,. Inc.. 194. 196 198 200 201 202 2C3. 204 205 206 207 208. 11.

(12) MDBS. Data. Management. System. FC'FK. FP\' t"'"--;. Find. Owner'". Find. F"evi: >us. M±mber. Mind. F'"u?v.lo1j3. C:. }: .;,.)e't3(i. Sort key. on. . - . .. . .. . . . . . - - . . . .. .. X . . .. . . . . . .. Curr"e,"ít.. of". GETM. GET. data. !"""'cm:. 'currerzt. Member. GETO. GET. data. fror current. Üwner". GETR. GET. data. from. Record. GFC. GET. Field from Current. of". GFM. '-;et. Field f"rcm current. Member". GFO. Get. Field from current:. Owner. R. Get. Field. GMC. Get. Member. GCg. ge. '7)wn. GTC. Get. record-Type. oÍ". Current. GThC. Get. record-Type. of". current Member. GTO. Get recorcí-T,ype. OPEN. OPEN. PUTC. PUT. data. into Current of run unit. PUTK!. FUT. data. irAo current. Member. UTO. PUT. data. :nt:o. current.. Owner. FUTR. PUT. data. into current.. Record. RMS. Remove. current. RSM. Remove. all. SCM. Set. Current of run unit based. on. Member. seo. Set. Current.. of run unit based. on. Owner. SCR. Set. Current of r'jn unit based. on. Record. T". COPYRIGHT. 1979,. curr"e'nt. uniÁ.. run. Count. 1980,. . .. .. . .. . . .. .. . .. .. .. .. . . .. .. run unit.. . . .. , .. - .. . .. .. . .. . .. . . .. .. Micro. :. ". ?. .;. l. me Z 17. . . .. . .. , . . .. , . . . .. . .. . . . .. . .. . . .. .. :"'. .. ". g. of". .. 22 i. P. unit. run. of current Owner. k4embers. :. '"2C\ .. Member. 2.í. 215. . -. .... ,... ... '"'. ;"' ! S. . - .. . . .. .. ... ..... . . . . .. r "íounf. Set. .. . . .. . . .. I C'. "". . .. . . . .. current Record. t"rnm. base. :Z . ,. "i":'. "7) 1 :. frorú. data. :'Z'.:. .. wne". ciaf"a. e. . . .. . .. . . . . ,. GET. t. .. .. GEtC. GF. ©. I. Docuraentation. . .. ... . . .. ... . . .. . . .. .. . .. . .. . . . . .. . .. . . .. : 222. .. 223. . . . . .. Z24 :. X '">5. .. from . .. Data. .. . .. .. Set . . .. .. . . . .. . . - . . . .. . . . . .. . . .. ... . . .. . . .. . .. ... . . . .. . . . . .. . . .. . . . .. . . .. . .. . . . . . . . . . .. . . . . . . .. . . .. . .. 227 22t? 23C) ¿'32. .. 233. , . . .. 234. . . . . . .. 235. . .. 236. . . . .. . .. .. . . .. . . . . - . . . .. . . . . . . . . . .. Base Systems,. .. .. . .. . .. . . . . . .. Inc.. 23'7. 12.

(13) MDBS. Data. OÍ". unit. SFC. Set. Field in Current. SFM. Set. Field in current Member. SFO. Set. Field in cur-rent. SFR. Set. Field in current. Record. SMC. Set. Member. SMM. Set. current. Member. based. on. current Member. SMO. Set. current. Member. based. on. SMR. Set. current. Member. based. on. SOC. Set. Owner based. SOM. Set. current Owner based. on. current. SQQ. Set. current Owner tmsed. on. current Owner. SOR. Set. current Owner based. on. current Record. SRC. Set. Record. SRM. Set. current Record based. on. Member. SRO. Set. current Record bz'sed. on. Owner. STAT. return run S'TATistics. .. .. .. .. TOGGLE run optimization switch.. TOGGLE. (9. Documentation. System. Management. COPYRIGHT. based. on. on. based. on. run. Owner. Current. 1980,. Micro. ... .. .. .. . .. .. .. . .. . . .. Current. Data. 238. . .. . . . . .. 239 241. ........ .... ..... 242. .. .. .. .. .. -. 243 run unit. . . .. oí^. . . .. . .. .. .. . . . . . . . .. . . . . .. Z44. current Owner. . . . . . .. 245. current Record. . . . .. Current of run unit. .. 1'379,. .. . .. ... . . . . . . . .. ... of". run. . . .. . . . . . . . . .. Member. unit .. .. 248. . . . . . . .. 250. . . . . . .. 252. . .. 253. . - . . .. 254. . . . . . .. . . . . . . . . . . . . . .. .. Base Systems,. ... Inc.. 25'q. . .. 256. . . . ., .. 257. . . . . .. . . . . . . . . . .. 247. . . . . . .. . . . . . . .. .. ... Z4S. ... 1?.

(14) MOBS. Data. Management NEW. Any programming bound. t. c). End. signed New. r. MOBS. name.. copying. hard. our. COPYRIGHT. Realizing. wi. I. !. MIJB3,. c. ). products. several levels. i o. s. r. methods. 1979,. 1980,. seriously. will. Micro. I)?. entitled to. User. a. A.gr"."emer,t. gumâriteed. products were produced. in the data base management area.. copying. sermraZe. as. j;ersonal i zat.ion,. labor to say nothi: "ig. products and. .. is. th. and. are. the'. nalized with the. 1vU)BS. we. version. perso:. '".. capital. c. :zd. End. cc ciecyphe: of". Data. .. MOBS. f^. are. .. will. signed. is. only z-f'ter. In. considt=r:. be. as the. sc.on. t.heir. to. can be pr(?vided. t'i le with. on. system.s. this, Micrr'. encryption. action against i.llegal. ©. MDBS. involve. Accordingly, of". the. of previous versi.ons In. fj. There. which. involvement .. is. sort\/are. MDBS,. '33py. sizable investment prior. WARNING. cjf'. time.. Updat.es. Form. owners. ,. each. combinatorally. A. magnitude. over. rate str'-iU.ure (as. Finally,. o. the. evolve. MDBS. of". is received by. some. of". AND. to provide it.s users with updates. However. licensee's. to. [Jeer Agreement. preferential Form. VERSIONS,. handling fee.. versions. products.. RELEASES,. endeavor. vows. nomina!. a. r. Documentation. continue. Base Systems f" co. System. or. take. concerr,ed an y. distribution. Data. by. about.. anc".. a. i. l. of' our. Base Systems,. of". Inc.. the. t.. w. c. be. i Eh. year'¶:. prin3iµalt>. Za. O!" o. t". any uríauthcrized:. 2vai!?.b|e. lega!. products.. 14.

(15) MDBS. Documentation. System. líanagement. Data. íNTEIODUCTION. I.. and f'or. structures available. for. restructuring í'. i. I. However". must. user. data. files). and. These. Te|ationship3. refers. indicating. to. th. th e. and µr'ocessed. t. he. 1979,. machine. .data. 1980,. and. structure by the. Micro. as. Data. narííed. the. oí". not data. Base Systems,. in. c>f". that. def"ining. into. record. into logical record. types.. imply any physical managernerít.. initially MDBS.. made. names). terminology, do. base. is presented.. items. between. data. is. The process. is done via the. program. language.. (field. items. data. CODASYL. e1er,ients. data. the. and data. definition. use of' the. structure. take. strictly. relationships t: he. MOBS. mere. struct.uring. actual data storage location,. conceptual. e. Language). r. an. ir.. a. point.. grouping data. of". is not. sEart.ing. a. structure. f"orrnal. a. only conceptual. Nowhere. o. COPYRIGHT. consists. are. refer to. user. la. in. logical. various data. the. appropriate. defining. e:. da. in conventional data Kjrocessing. ,. storage allocation. a. is,. that.. MDBS. as. particular apptication.. a. structure. (o. a. hetu'een. list. may. types. does. system. defined;. be. 71 ). entirely in. is implemented. appAication. l. available. not-. ures that are. involved in. r. {Apri. recovery, th e. Icu". in designing. used. ideas. mdditional. man y. relationships a. logical. Th e. packages. Add—on. transacticns handlirig.. and query. base,. ides. MDBS. th e be. oí. kgging. system.. p1"cu/. initially. Ríitial!y I. a. f'eA:. each. r. which. a. data. systems.. Fo. 'i l. of. 2'!DBG. ,. mar)ip'Á!atioI1. 'ñ. a! low the. Base Task Grcmp Report. Data. CCJDASYL. t.ase. N!DBS. data. for defining. has components. retrieval of data.. storage and. the. management. e. (MD!3S). Base Systems. Data. The Micro. DDL. but. system. rather,. defined. (Data. he Th. is. ljef"init ior':. DDL.. Inc.. 15.

(16) MDBS. Data. Management. Alter o f'. the. need. desired. to access. application. An. requests the. data. f". cÍOé3 (o. r om. This. OMS. responsible. requests to the collection Language) The. o. to. Another. g. .. ,. invoking. RTL. !V1DBS.. is. power a. loss). recovery. which. may. data. the. be. A. utility.. rlonprocedur(3. cuts programming. add-ons. the. l l s. :'. t.. p¿!rforY.. ,. h. C'. i. t".. t.h e. applicatio». data. base;. t. i ch. ma k e. Pata. M3r:. he. Th e. structür'e.. wh. l. ("íat.7.. l?1ste¿"('j.. .. the. o!". DML. e. e. "ii!" i t-a. to. ph.ysi cal. I. MDBG.DDL. OÍ. in the. ?.¢!3!32. permit chemges to. Cc). dump. logs. an d a. u;". ¿-i. iµu!at.iori. third. queries. be. car.. add-on an d. MDBS.DRS.. dzz. zh e. a. t. MDBS.QRS. produccs Fu l i. MDBS.RTL,. 3. cr.. syster,:. whích. e. j,. ,. i.ata base. 3. restored autotüat-ica! is. bas. t. a. tcj da. made. of. event. Ther· e. .. made. bE:. i'e-]c¿íci. the. CJMC. it. tiay become. l! transactions. In. base. .. existing. ari. U). effort substantial ly.. found. and. C'ccasior;a!ly,. struc-t'-ire. logical. without the need. add—on. English—like, This. D!d3). of". c¿: .. M!JB3-. to. is designeá. system. of". since the last data base backuµ.. base .. add—ons. ,. the. alter. structure. consists. package. very useUi!. MDBS.DRE. base. (e. MDB3. basic. necessary The. th e t.h. bas. 3. writer. structure. cc'mpz"isir.g. commands. !7. the. via subroutine. made. are. dat. e. (MOW.. maintaining. r. 'n. ( o r". zí. u3. luto the. i. I. .. other",. ar" e. DMZ. o. t. requires. to know only the conceptual f^. to ). r. r". ,. t·:. programs. data. new. not, however. programs. is. place. or. routines. management. operations.. necessary. defined the application. dM:a from. program. directly. data. Documentation. has been. structure. course,. base.. System. .. ci-atní. crash. iy by accepts. desired r"eµort.s.. detai Is about and. MIJBZ.QRG. dt-he3e. User. ?. s. Manuals.. E). COPYRIGHT. 1979,. 19F3Q,. MicrQ. Data. Base Systems,. Inc.. ! C:. ".

(17) MDBS. Documentation. System. Managemen'c. Data. II A. ?v!D!3S .. ... DDL. Int-roduction. ,. Ir,. this section,. Description. In. Part. B. 3ata. list. we. Descr"ipt.ion. is. ]nstruc-ted. modif"icaticn" Tc. a. data. to see. Qr. how. such. the. data. I-J,. we. and then. proper tables.. g—up. ". E.. editing. a. '1979,. 1980,. of". which. MDBS. .. !JDL. tb. ;. t ."ien. zr e. m. Iii Sect.i.:. discuss such concepts. t":. t.l?.e i:. e. user". ind. o. for. must. user. iQicro. ].. !'. "ire the. and present.. describing. a. data. base. i II. !J .. used.. pnysical ly. This is a). and z-tza!ysis. .3.ata. to t'ais are alsa descr Jbed.. (DDL). the. is discussed in Section. COPYRIGHT. n. first. using the data description. IJ ). BOL. sect: íons.. ri. a. .. MDBS.. r. M,icro. also want to look ahead to Section. may. base,. o. (for. MDBS.DDL. l. "Da i".. proper, data base management c7ríc€pcs. conceK)t.s are. data. a. b. made. language. The user. create. Section. ©. base. description. structure.. To. data. ". t-o. can ba. Ii' Section. necessary.. LanÉ"uage). i n later. h ("w. 3ñ. Jhat. develop. !. cal. we. severa! features. described in more det.ai-. 's Svs'um %'. ldicro Data Ease. or. .iyzer/'Editor which. Ana. Base System 's. concF"r)trat.e. we. The. data. Data. !anE"uage. initial ize. óone by the anal. describe the structure. DDL. the. (as. discussed. data. base. with the. ana],yzer,/eaitor. yzer/editcr. permití:. i r,. t-ne. which. in?ut. ,. description.. Base Systems,. T. ríe. .. i. ":'.

(18) ,;. MOBS. B. Data. Management. Documentation. System. Features. .. MDEIS.DDL. allows the user. initialize the. data. a. data. Entry/Command. 2. Deleting. 4.. Saving. 5. .. Ret.r"ieving. .. Renumbering. DDL.. and,. can be. Suc h. c!. is dcfined using description. a. or upper" case). This. th e. if. no. edited. DDL. is. via the. supports:. mode. l. th e. editor. ine. processes. da. a. detected,. initializes o r logical error i" detected,. errors are. syntactical. I. message. is displayed and the user. a. using. analyzer. base.. f". .. an. formats and other text entry aids.. Finally,. description. structure. i n lower. MDBS.DDL.. structure. e. Listing. -. entered, the t.ext .. (DDL). bas. entry. well as providing. MDBS. data. a. base. (either. of. mode. Text. data. language. 3.. 6. Once. A. .. into the computer. 1.. as. ba s e. description. entered Text. to describe. can. quickly. correct. the. ta. o. r. bas. e. a. data. an. error. problem. using the text entry or edit features. MDBS. supports the fol lowing i. .. 2.. COPYRIGHT. 1979,. Character,. integer,. internal. decimal,. 1980,. work:. length records.. Variable and Í"ixed. record ©. features for data base design. floating point (real), logical, externa!. decimal. ,. an d. binary. fields (data items).. Micro. Data. Base Systems,. t. nc. .. 18.

(19) i4}L);2S. Data. .-2. 'Doeumentat. System. i\áanagerne.nt. cm e—to—many. {jr-"--tc_íme,. ,. s: €:t-. ':'!2¿Fny. :. Sc. E. 'Led. '-. ,. i on many_: ío—one. ,. and many_to—. ,. types.. I FO. F. .. IFO. n. ,. e. x. t prior. ,. s e t:. immaterial. and. -:. jrderZn,gs.. 5. .. Automatic. .. Read. t":. O. Record. t.yp es. may (. g. These A. ,. base. maximum). reccmd. M""'ny Fu-. i'eatu.res. data. hard. .. ;. l. are be. can. an d. t:. network. i. .. e. .. recursive set".). ,. e. can. data. structures.. drives. the. be. can. over. set.. number. a. o. '". drives. f". 8. floppy (mini—or. ful!— sized) or. base. is organized using. a. paging. A. logically contain 3191 pages restricted to, at most, 65536 bytes. {subject. supported. to opermting. system.. an d. can. Thus. system. a. page. single. drive. logiealiy. is. large data bases can. constraints. on. the. size. be of'. fi le).. Gnc: e. a. data- tú'íse descr i.pZion. t. initialized,. ©. T. ane í'éñ. a. disks.. The data. a. same. !1.. in Section. physical ly spread. the. .. Dart1cipat.e ín. ypes. discussed. o'?. other occurrences. own. at. organizat-ion.. oe. 7. 7. " ·. '"'ecord- type 8. via passwords. protection. access. item, recora aria set levels. z-he m. write. and. into sets.. record insertion. or manual. host. lar)guz: gc. take. up the. CCTYRIGPÁ. Fi. e. user. ( ¿;uch. 1980,. ear,. as BASIC). discussion. 1"'7.9,. has been. of". Micro. í\'!DF3:. ezzsi. us. ;.. Data. 'l,. entered. y access. i-rig. MDBS.. the DMS.. an d. data In. a. data. base. Section. bas e. through III. a we. DMS.. Base Systems,. Ir.c.. 19.

(20) MOBS. Data. Management. System. C.. Getting Started with. 1.. initial The. the. Loading. details. MDBS.DDL. execute. specific are when. supplied DDL. program. its f"ul!y qualifi-ed VER. MDBS.DDL. (C). COPYRIGHT. Reg. #. Your. MDBS.DDL. and Test. package. is. which. Documentation. (see. Run. to your system 'Iou purchase manual. name) which. MDBS. in the. outlined the. for making an the. MDBS. system. t.est. of. manual. specific. system.. system. initial. !2rief"\y.. you. will. manual. specific. f"'or. will display:. X.X 1979,. 1980,. \'Jicro. Data. Base Systems,. Incorporated. XXXXX name. and. address. At. in. this point. file. generated. name). by the. The MDBS.DDL. their article BYTE published in ©. COPYRIGHT. sample. procedure. 1979,. Gagíe, Systems And magazine. 1980,. data. specific. base. deseriptiorj. stored. for. fully. manual. is shown below. the. (underlined. text is. system):. used by was This example "Data—Bame. 1. a. (again see the system. INVNTRY. qualified. you can read. M.. Micro. Data. G.. Koehíer, and A.B.. Micro—Computers: Base Systems,. Inc.. An. in Overview",. Whi"nston. ZO.

(21) System. Management. Data. MDBS. Documentation "Read. FILENA}j'"i. computer. INVNTRY. fully qualified f"ile. list this. smal. l. data. the. prompt:. sample. basc·. exists. this. you should. th e. on. purpome).. this description. type. DDL.. The complete. with. respond. base. looks. sequence. "Enter FILENAME?. computer. PROCESSING. not. system. specif'ic. manual. please. cal. ©. COFWRIGHT. DDL. computer. out,gut). you have. }. temporary. displayed. be. Analyzer". Micro 1979,. for. (without. command. generated. rame. output. CCJMPLETED. had.. Data. file. prompt. fully qualified f'ile. (DDL. Ir. a. which. name. like. name. DDL. (use. then. will initialized.. DZ)L DATA-BASF. initialize a This will result in. qualified file. fully. a. description. data. a. actually. FILENAME?. drive of your system. first. and. INVNTRY. To. The data. line numbers). prompt. "L".. DATA-BASE. to which. command. type. description. with. a. for. name. To. Fi le". R. euecessf"ul. a. and. ,. I. r. c. .. try again.. Rase Systems,. 1980,. run. Micro. Data. In. re—read. still. y ou. Í"or. this. s. gctic-F) and the. have. no. :. uc k. ,. help.. Base Systems,. Inc.. 21.

(22) MDBS. 2.. Data. Management. Relocating Under. MDBS.DDL. Systems.. a. For. Documentation. MW3S.DDL. opera-ting. some. at. System. position. it. systems,. other than that supplied. thi.s purpose,. have. we. provided. desiraiAe. be. may. a. by. to locate. Micro. relocatable. !J)aÜ f"o""rr.. Ease oí' the —. data. description. analyzer can be. of. the. the. system. ©. analyzer and. COPYRIGHT. specific. 1979,. ORGed. manual. 1930,. a. relocator. an. to any place in memory.. for further. Micro. so that.. Data. executable Please. refer. form. to. information.. Base Systems,. Inc.. 22.

(23) Personalizing. Important Addresses:. 3.. consists of. MDBS.DDL. are. contiguous. The. size of the. patch. manual.. program. work. area. area. These. immediately follows the program. area.. increased. through. decreased. or. Entr;,'. these. alter. may. of". as shown. each. system. the. in. specific. follows.. item. Point. this point, all program variables and regions either physically or logically re—initialized. Registers are. Upon. saved H:. j. entry but. a. should be aware or in. that the user. addresses. brief description. Initial. region and work area region.. be. can. MDBS.DDL. Patching. and. em.. The user A. a. several. are. MDBS.DDL.. the. 'm: mk. to the sys. There. (a). ancí. Documentation. System. Managem'"nt. Data. MDBS. at. the. are not. entering stack is preserved.. I/O Entry Points operating systems. Dif"f"erent. and. printers free sYstem. of. disks in. system. handle. variety. a. this. keep. specií"ics the I/O inf"ormation relevant. I/O. instruction"i. To. of ways.. is published in the system. non—standard.. input and output to terminals,. should. routines. of the system. specific. specific. be. manual.. made. manual. for your. Patches. in accordance. to. with the. manual.. ... (C). Echo Toggle. (Default. This byte is: checked echo echoing. input. to. the. 00. hex). to see if" the user wants output. will take place-. device.. If it. It. the. to. have. byte value. is the value. one,. Base Systems,. Inc.. no. MDBS.DDL. is zer~í,. echoing. will. be performed.. G. COPYRIGHT. 1979,. 1980,. Mie: -o. Data. s>m w»m.·.

(24) MDBS. Data. (d). Last. Management Word. Th e. hex). OBFFF. stored here gives the. MDBS.DDL. memory. starting. field.. Needless. may. program f'. i ts. r om. the. to say,. that. Note. use. load. last aval lable word cjf memory. address. MDBS.. make. sure. !. a l. uses. to t.he value. up. user" should. ijDL. -V,. in this. that lhe. !. t. as. of memory is physical ly beyond the end of the program.. word (e). Documentation. of Memory (Def"ault. address. that the. System. (Default. Control Byte. Screen. byte should. This. one. of". hex). the. following. than. characters. values:. Byte. Width. Screen less. have. OB. or. equal. to 64. greater than or equal characters. tCj. 80. Value. 1 1. (OB. hex). 15. (OF. hex). greatest. per to 80 characters N) (ca: line it. 64. than N/5. l. cu". irzteger less. equal. t-. o. :. -1. (t) Re-entry Point If. th e. to. wishes. user. MDBS.DDL.. re—enter. varimbles and regions, then he must issue. program. ;:'resen"ving. whi le. jump. a. to. ].. al th. j.. s. address.. In data. the. next.. description. illustrated with. ©. COPYRIGHT. section. we. langut-tge. discuss the data descript.ion and í"eatures. o. r. a. data. bas. language. e. design. Th e. ar e. examples.. 1979,. 1980,. Micro. Data. Base Systems,. Inc.. 24. --.

(25) MDBS. Management. Data. D. (Data. DDL. .. .. The. i terns. is. i. DDL. structure. 3ñcÍ. of. used. s. DATA-ITEM. a. representation. item,. descriptions. These. an d. be. an. of. a. A. a. on". item. named. collection. RECORD-OCCURRENCE. is. of". two. be. used. may. only within. in more tlían within. items Consider. the RECORD ITEM ITEM ITEM ITEM. COPYRIGHT. one. the. AGE). data—. a. "repeating. A. I. ,.. optionally. the. same. record type.. ). OÍ". on e. There. each. name.. record-type.. ". of values \. o. ,. be. '. ,. we. data—. :. ":rbitrary. sp'ecified.. names. data—item. order, type. u. data-items. an. record—type. same. specified. more. the. of". may. r. The data—item. (The The. be. an d. mus. t. name. may. size. o. f". record type are defined in the record description.. a. f"ol lowing EMPLOYEE NUMBER 7AME !/1AGE. "i'AX. 1979,. have. i3. .-. zero,. contained by the record—type.. record—types. unique. may. sampling. a. of occurrences in the data base. ©. data. t. ITEM—OCCURRENCE AGE. .. of". len&th" .,.QjL==La_rray.. number. the. o. array whose maximum rep! i-cation factor. to. be. terms. An. ( Eg. be an occurrence. def"ined. be. in. are. data--item.. ·· ". current.. is. a. "depending. a. ae. the. RECORD—TYPE. items.. might. 21. o?\é?—dimensional. 'f · .' . ·. indicates. OÍ". value. a. or. a ge. specii"i -i;. .~~N%~~~Nu. No. (or logical). conceptual. a. is the smallest unit of named data.. item" acts as. A. describe. formally. to. base.. data. a. A. which. Definitions. record types, and sets.. ,. must. Language). Definition. Introduction. 1. Documentation. System. 1980,. example INT CHAR REAL REAL. Micro. ot. a. record description:. 8. 20 8 8. Data. Base Systems,. Inc.. 25.

(26) MDBS. Data. Management. The above. data-items: (taxes. System. Documentation. example. defines. NUMBER. (employee. withheld).. ". The. record—type. a. number) ". types. o. character,. rea. l. maximum. 20. characters in ler.gth.. óf7. ,. (1520. be. might. and. A. ,. "Record—type". occurrence" data. values. th e. name. is. up. l. ernployees. of. occurrences. the. ,. t-he. SET. is. record—types ar. are. declared. e. a. as. record—types.. occurrences. order of the Th e. names. EMPLOYEE of". the. a. be. an. "record-. an d. ,. values.. "members". request each. A. of". using. If. z". th·: ±. the. in. th e. DMS. a!. it. on e. record—types.. !. would. One. or more. and one or more record—types. of the set... Any record—type. of one or more. set occurrence. a. of". group. NAF-IE.. data-item. lared as the "owners". have. may. of each of the record—types. memEer. ""Y. record—type would. definition [or. and. between. relationship. A. to be. of the data—iten'.u.. would. program. (the value). th e. There. .. TAX. integer,. re. this. structure. a. desired (using the. declared as the owner record—type member. 158. 42). ,. and. is specified. to the actual data and the. record—type. dec. NAME. 3. occurrence of. def"ining. in. application. named. data—items. and. An. (wages). WAGE. r our. record occurrence, and they are sUmed. a. are. request the occurrence. th e. 7520 . 20. to reler. make. may. r. containing. in the company.. used. used. is. example). A. SMITH,. of the record—type. of al. above. B. NAME,. ,. respectively,. tor each employee. occurrence. names. rea!,. EMPLOYEE. The. sets; an. may. liktt'".'ise r,umber. arbiti"ary. be. ror. of. "set order" (the logical. record occurrences) must be declared.. set is t.r'" basic struct.ural. unit. of". tlú". data. base.. I. t". is used. between recorA—2:.y;:'es. In different. t o define th e relationship particular, the set links ezch owner record occurrence to it-3 related ©. COPYRIGHT. 1979,. 1980,. Micro. Data. Base Systems,. Inc.. 2é. --.

(27) MDBS. DDL. .. A of". Example. simple but. address, dat.a. structure. data. definition. section.. of'. 7i gure II.D. " '"'. Note. used. no data. tb e as. word. us e. in three insert. e. name. by the. —--. OT. '¶:. differe record. a. the. on l y. are. o. has been. shown.. thi s. r. defined,. record. The. type. special recorc'. predM"ined. a. in the data base.. There. by. is only. in the data base and there is. record—type.. Th e. SYSTEM. the. data. record. is. t ype. NUMBER e. ,. tc. CHAR. a l. !. contains the customer A l. .. contains. I. of". the. data—items. specification.. Th e. number". re!aLing to. NAME. i tem. ,. a. store g}]aracter data,. i tern. foilows. size. the. CHAR.. Th e. when. is. portions. (CUSTOMER). record—type. t.h. recc)[""d. Data—item. customer. remaining. in this section.. CUSTOMER. indicated. sets, is to data. SYSTEM. with. associate.-i. customer.. in these. t.he. of". discussed later The. th e. and ZIP). NUMBERS. permits access. instance. in. actual options avaiÁuble f'or the. t"mt only one record type. as owner. which. KÍDBS.DDL. The. 1.. detai led. e. while three sets Oames,. on e. lists. orgcmizations sorted in. or. o í'. SYSTEM,. is the need to maintain. problem. business. c"ommon. Consider th e diíferent orders. a company which maintains lists of" customers sort: od by name, The !4DB2 s,y3tern handles and zi-p code. this problem using the. people. case. examples.. through. This is best explained. record occurrences.. member. 2. Documentation. System. Management. Data. '2ree. sets is the key to maintaining the customer. orders. in. the. Th e. proper". record is created. a. COPYRIGHT. MDBS.. Note. DMS. location that this. system. wi. I. l. automatically. in each of these is. a. logical. record is only physical ly present in one place. 1979,. 1980,. Micro. Data. Base Systems,. Inc.. file. three sets construct By. use. of". 27.

(28) MDBS. Data. Management. approprÑate o. r. t: y. ,. DML. us e. accessed. A I. o. conmands,. r. other. Examples. three. i. f". o. given. a DML. in. sets the. r. Documentation. (NAME. for set. tmt. each. t:h e. set;. such. t.hat. LIFO each. of". member. the. in the set defined. new. record. set;. NEXT. after. an d. set;. that the. ef"ficieneies In. th e. MDBS. specified.. COPYRIGHT. added. set beíore the. to the end the. added becomes. —. a. t description. The. system. These. 1979,. that.. member. as t. c. o f'. the. ¿". set. "L. is. record occurrence is. new. "current.". Inem: ,'jer. the. record of'. set". to. Note. orúr.. !êa. 1. th e. certain. i-ze. possible.. of Figure II.D.1 as occurrences. the of". "AUTO". specification. record. CU3TOI','!EF. tyoe. will automatical ly be inserted in set ONORDER word "MAN" (for manual) could also ;'"ñiíve been. options. 1980,. if. used. e. thc. set. such. oí" ]. ar. logically 'je first is ioi;ically placed. sy'U.em. be. occurs. t'aere. ,. to the f'ront. MDBS. user. recc.rd. SORTED. logically. PRIOR. is. field-. record oí the set ("current". member ;. t!i e. be. set orders exist... record occurrence. rú=w. is. Each customer. set ordering al lows the. Also, the specification ©. an d. about. the. created, the records. by the. ). care. —. This indicates. appears. are. the. and shouk2 se. a. .. does not. I MMAT IMMAT. et c. "sort. key". The. Besides. are. in Section. SORTED.. ,. nírrence. discussion). DML. logically placed in. —. oc.:. "current". the. th e. in. III.D.. iustrated. are. beccnnes. occurrence. eU"ícíent.iy,. ii. orders. are. accessed. can. yet three logical. record occurrences. —. be. sorted list. oí' '"'ecords. set to be sorted upon.. rec- : ,rd. new. 1. NAMES. re\.ord occurrences. —. a. are. II.D.. six allowable set. are. FIFO. also:. commands,. Figure. only once in the data base, There. record can. of such programs. stated for each set defined. SysA: em. "1: N" Micro. ar. e. discussed. fur-b-her. in 3+ctio. states that the relationship 'Jata. Base Systems,. Inc.. i. I!.IJ.5.. between. the 28.

(29) each. relationship. member". many. this. only. of. type. supported. relationship. not. but. occurrences,. support. systems. For. relationship.. one—to—many. the. by. is described in the next section.. system. MDBS. a. (N: M). many—to—many. a. ——. be. may. base. data. Most. versa.. is. members. its there. occurrence. owner. vise. seb and. the. of. owner. Documentation. System. Management. Data. MDBS. 0. Developing does. DDL. the. for. a. not require any knowledge. The user take. However,. of data much. storage. (Data. DML. insight. is read. will. easier to understand. set relationships.. gained. be By. ir. the. what. seeing. Also, the additional. the. the. examples. programs. the. IJML. it. available,. are data. will. system. describing. sect.ion. system. Language).. application. commands. to design. how. MOBS. Management. for. retrieval. and. will (Section III.D).. be. t-he. of. to be used in the. base. only to define the data base structure;. needs. care. data. base and. will. establish extremely. be. helpful. Our. example. inf"ormation. customer one or. Suppose. has even. associated. to keep each. a. extended. to include more. record of orders. customer. may. have. that. have. what. just. structure. represents. for. example. one. customer.. (one. customer. a. data. of Figure a. customer. define the complete. record descri.ption 1979,. 1980,. after Micro. Thus. to. base. II.D.1,. we. the. for. set relationship. derine. this. a. second. II.D.2).. example,. description. Data. orders),. many. order (see Figure DDL. we. we. tor the. Base Systems,. Inc.. a. several (or. with. structure. COPYRIGHT. wish. Conceptually,. be. order though. which. ©. can. Each. the. new. we. II.D.1. zero) orders that have been placed.. extend. actually. that. placed.. "one—to—many". natural. Figure. of7. is. is called. a. which. is. In. order to. record or course,. would CUSTOMER. add. a. type. to the. record. 29.

(30) MOBS. Data. Management. System. that in record type. Note. (for order. NUMBER. price).. QUANTITY. and PRICE have. is. stored. to. be. specification. BIN. is. maintained in be. and INT. in added. CO?YRIGHT. F a. I FO. is. first—in,. whi.":. h the. to the. 1973,. t: o. store. 1920,. eac h ,. data. "2". the. the. binary. [o. r". ;.q'cr-c. 7g"r. but.. storage exceed. r. usec2. to stcr·m. decimal. format.. indicate i l) e. Th. .. ler,gt-.h. that two. -. i'. 8. REAL. e. bytes.. types are also supported. to. each. h. basis, which the. Bqlgc?. is. Th e. orders. the. customer,. orders were received.. after all. é-iata,. neve. is. va. ( t.h e. I"R'CE. r?duc-í-. c). packed BIP'. items:. a. respectively.. will. TY. aí't.er". customer. first—out. DDL. t.. real number whose data. tha, t. so. ,. QUANTI. REAL. binary dat-a type. digit.. a. itern. of". t-.. hold chareíetar. data. instead. da. (the stock rüsmber. PART. ,. (Binary) and. since. The. (Integer). links. ONORDER. set. sequence. PRICE. five. ordered) anti. items. binary Th e. located. a!. for. (Logical). ordering. ?. t','pes a. as. BASICs.. mari y. bytes should. would. data. values in binary format.. c ommon. The. data. the. this application.. in. integral. (the quantity. f. o. def"ined. (order date). This is reasonab!e. requirement.s.. LOG. Three. have. we. DATE. ,. QUANTITY. ,. invoice QUANTITY. ORDER. numb'zms). of the part ordered). É35535. Documentation. orders. will normally The. set-. new. record descripti. Systexs, I d c. .. ")ñ3. will be. s e t. be. th e. dE'3cription 72Lre. gi'ieri.. ?Q.

(31) MDBS. Data. Management. RECORD ITEM ITEM ITEM ITEM ITEM. CUSTOMER NUMBER NAME ADORERS. SET. CITY ZIP-CVJE. 8 20 20 ZD 5. NAMES. AUTO. Í:N. SYSTEI'4 CUSTC'"."ER. SET. NUMBERS. OWNER MEMBER. SYSTEid CUSTQÉIER. SET. ZIP. AUTO. AUTO. record. Customer Customer Customer. CHAR CHAR CHAR CHAR CHAR. OWNER MEMBER. OWNER MEMBER. Documentation. System. number name. Street address City Zip code Sorted SORTED. NAME. SORTED. NUMBER. SGRTED. ZIP-CODE. by. Name. Sortcu"! by Number. 1:N. 1:N. Sorted by Zip code. SYSTEM CUSTCMER. END. FIGURE DDL. 9. COPYRIGHT. Declarations. 1979,. 1980,. Micro. II.D.1 for Multiply. Data. Sorted Records. Base Systems,. Inc.. 31.

(32) MDBS. Data. Management. System. Documentation. RECORD. ORDER. ITEM. NUMBER. CHAR. 6. Order. number. ITEM. DATE. CHAR. 8. Date. received. ITEM. PART. CHAR. 6. Part. number-. ITEM. QUANT'TY. BIN. 2. Quantity ordered. ITEM. PRICE. REAL. 8. Unit cost. SET. ONORDER. MAN. Custemer. I. Link customers. : N. FIFO OWNER. CUSTOIW"R. K!ENB"R. ORDER. orders. to orderc. END. FIGURE DDL. ?. COPYRIGHT. 1979,. Declarations. t980,. Micro. II.D.2 for Cu3toIner. Orders. Data. Base Systems,. Inc.. 32.

(33) MOBS. 3. Examp). Many—to—Many. .. restricticn. conceptualize. in. imagine. example,. ... that. titles. to. able to obtain: keyword,. given given. book.. boo k. c an. between. If forced. introd'iíce. records. such. va !ue. however,. we. book—keyword when C. .. authors. COPYRIGHT. many. We. wish. corresponding corr"c:. keywords. t.. ¿sponding. an d. books,. an. have. we. l'.ey\t.".jrds.. many—to—many. a. As. so. o. a. t.o. a. since. on e. relat.ion: íhip exists. "one—to—many". records". "link. to adopt. us the A. DDL. a. sets, wh. database. Description. i eh. woul. e. are. ,. Language). ,. f.o. These. rest.ric'ted. data. be. d. used. systemm. highly unnatural. link records contain no (Data. w. dateg. little. has. descriptiori. of'. is shown in Figure II.D.3.. set relations. The. books. sets in conventional. Nríce. structure. a. keywords,. I. artificial. force. which,. conceptual. describes. oí". c::"\. nnd books.. many—to—many. structure. A. list of" sorted list of. in which. system. number. a. sorted. A. keyword. each. by. classified. 2 ). ,. bibliography. i. a I. re. storage and processing.. both. r. restricted to standard. are. to. simulate. I). severa'. keywords we. link. a: "id. have. be. may. Sinc"". o. computerized. book be. terms. wh. .. harder to. program. structures. unnatural. These. to maintain.. anf7. set üccurrence.. a. the. t?. one—to—many. unnatural data structures. of". use. of. members. t?. a. require. unnecessari ly, making. programs. ineff"icien"'". quite. the. fújrce. may. DIVÍL. complicates. owner' and the. th e. .. systems. base. data. between. relatiQric.hip Thi". e. (COñÁSYL). Standard. Documentation. System. Management. Data. mus. t. involved are create. a l i. 197IL. ·--'. introduced), 1980,. of". an occurrence. pair' in our database. a: ". one—to—many. Micro. In the. Data. a. relationships. reccu"d. type. more complex. LINK. example. actual data relati'.mships Base Systems,. Inc.. for each (such. as. present. 33.

(34) MOBS. Data. Management. System. quicjcly become unclear. that. it. books. and keywords.. wastage. is. quite. MOBS A. In. sorted order between. the. ink. records. permits. explicit. l. results. in. a. .. the. data. base. that. means. Use. rim all. that. t h e set is. to. necessary such. handled. th e. as. th. b y. a. a. sorted order. for. keywords. of. many—to--many. schema. ·2. that. Note. given book. a. second. a. anc". set The. order.. that the members. indicates. the. of". se. t. that the. f'irst. s. et. set are also. this feature al lows one or t.o list- all books for. o. f. ,. based been. COPYRIGHT. used. ,. for notational. sets. Many—to—many. .. t. The terms. and are. i e.. se. a. required.. assigned. distinction between t h e owners since the rigid one—to--many ordering is no "owner" and "member" are thus arbitrarily. sets blurs the. many—to—many. members. —. pointers. li'!I)BS f. keyword. of". longer. a!lowí: the. situations. conveniently. be. of many-·to—. use. is used which. for set. S3, the specification. speeif"ication. either given. ©. is. of Figure II.D.4.. maintained in. be. have. r. structure. is. c an. e. indicatc-s. ordering. Member. o. a. this structure. with. records are to be maintained in sorted. owner. sets. Th. declaration. the. ordering. cl. use. System. internal. sets.. exai'üp}. declaration. an. Management. special. such. bibliography. a. the. Also,. problem. to maintain. t o automc'tically maintain. represent. to. additional. dif1"icult. Data. sets.. system. to. An. of data base storage space.. Th e many. Documentation. DML. a. commands. on. Sort. such Key. 1980,. Micro. Find. as. (FMSK). the. are. OWner"y. Data. only.. like conventional. processed. re. defined to process 1979,. convenience. used. OÍ7. '¿ FbIIvI. Member. Next. Additional a. set:. Base Systems,. Find. Inc.. (one—to—many) '). -m. DML. d. Find. commands. Next. Owner 34.

(35) MDBS. (FNO). Data. Management. and. Find. System. Owner. described in section. Documentation. based. on. Micro. Data. Sort. Key (FOSK).. These. are. fully. III.. .. ©. COPYRIGHT. 1979,. 198C,. Base Systems,. Inc.. 35.

(36) MD13S. Data. Management. System. Documentation. BOOK. KEYWORD. LINK. I. Data. Diagram. for. FIGURE. ©. COPYRIGHT. 1979,. 1980,. Micro. Many—to—Many. II.D.3. Data. Example. (a). Base Systems,. Inc.. 36.

(37) MDBS. Data. Management. RECORD ITEM ITEM ITEM. BOOK. TITLE. Documentation. System. 30. AUTHORS PUBLISHR. CHAR CHAR CHAR. RECORD ITEM. KEYWORD KEYWO72. CHAR. ío. RECORD. LINK. SET. SI. OWNER MEMBER. SYSTEU BOOK. SET. S2. OWNER MEI'4BER. SYSTEM KEYWC'AJ. SET. S3. Book Book. BOOK. SET. S4. 60. Keyword. Link record AUTO. AUTO. MAN. 1:N SORTED. TITLE. SORTED. KEYWORD. 1:N. 1:N. Sorted. list. Sorted. list. of". of". books. keywords. Linkage set for books. LINK MAN. 1: M. Linkage IMMAT. OWNER MEMBER. title. Author(s' Publisher. 30. IMMAT OWNER MEMBER. record. tor. KEYWC'?D. set. J'eywcu"ds. LINK. END. DDL. Tor. Link Record Example. FIGURE. ©. COPYRIGHT. 197.9,. 1980,. Micro. II.D.3. Data. (b). Base Systems,. Inc.. 37.

(38) -. MDBS. Data. Management. System. Documentation. BOOK. l. S3. KEYWORD }. Data. Diagram. for Many—to-Many Example. FIGURE. ©. COPYRIGHT. 1979,. 1980,. Micro. II.D.4. Data. (a). Base Systems, y. Inc.. 38.

(39) MDBS. Data. Management. RECORD ITEM ITEM ITEM. BOOK. TITLE. System. Documentation. 30. AUTHORS PUBLISHR. CHAR CHAR CHAR. RECORD ITEM. KEYWORD KEYWORD. CHAR. 10. SET. SI. AUTO. 1:N. OWNER MEMBER. SYSTEM BOOK. SET. S2. OWNER MEMBER. SYSTEM KEYWORD. SET. S3 SORTE3 BOOK KEYWORD. OWNER MEMBER. Book Book. record. title Author(s) Publisher. 30 6C). Keyword. AUTO. SORTED. TITLE. SORTED. KEYWORD. SORTED. KEYWORD. 1:N. MAN. list. Sorted. list. of". of". books. keywords. Book/keyword. N: M. TITLE. Sorted. relationship. END. DDL. for Many-to-Many FIGURE. i9. COPYRIGHT. 1979,. !980, Micro. II.D.4. Data. example (b). Base Systems,. Inc.. 39.

(40) MDBS. Data. Management. System. Documentation —.. 4. Owner/Mernber. Multiple. .. Mo"t. th e. set relationships. se. t. example. of". this within. oyees. payrol. Ir. I. needed. to define. record.. be. ma y. a. (which. tújurj. than. delined as. wage. concept. a. the. is f1irther extended. MDBS. in. actua. by. ].. d.. an. cc)rr"3!sponding. 'be. different.. des. i ."ab. re'·": clrd. types. a. t. c). as. Special. record type. allowing. l e. members. set type.. a. of"". contains. membership,. many. of". t. grouping. to be possitle. as. An DEPT. " ype. require. might. it. ,. (or owr.ers). routines are aval lable to determine active member '(or owner) of' a set. is. i on. would. y. in Úact,. MDBS;. MDBS. Th. to. record type SALARIED. and SALARIED. member"). reco"""d. EMF'L'-'YEE. un. ,. of". record type.. owner. record type. employees"). y. member. corresporAing. ,. presu!nab]. EMPLOYEE. types. with. hourly. as. the. as. Suppose. This is permitted in. SET1.. OÍ". EMPLOYEE. such. wish. we. record type defined as tht: owner. defined. depart.ment.s.. information both. one. set (SET1). a. member. employees. t o salaried allow. be. information. l. seniority.. payrol. would. an d. have. another. tu" d. type. (Department) emp!. Example. sc.c. of the. to have mmp. the. record type. same. record. -.··. as both. type.. Imagine. a. its set. record. owner SUF'ERVIS. wh. t ype. i ch. an. d.. indicates. i. t. '3. member. tne hourly. F'.~mKq~~. employees. ( EMPLOYEE. ). ¶KS~bK .. > . .a. hierarchy. wh o .. .. . ...,. .. o. f. supervision. supervise. other. hourly. eínploy.'es.. A ~Me. .. . . .. c an. be. conveniently. repres=nted by such. a ~. ~w"~ , , ..,.. data. ~. ©. \. structure. (Fi gure. II.D.5). · .· .""m'*. .. COPYRIGHT. 1979,. 1980,. Micro. Bata. Base Systems,. Inc.. 4C\.

(41) MDBS. .P. Data. Management. RECORD ITEM ITEM I TEM ITEM ITEM. E!.4PLOYEE NU7.¢BER STATUS bIA!'7E WAGEEATE ADIJ QEÍ3S. !T"M. CITY. RECORD ITEi'.4 ITEM ITEM ITEM ITEM. ZALARIEJJ i'ñjÉ.'i7ER. ITEN SET. SI. AUTO. -. 1. C)\'/NEE MENBER. SYÁTE!.7 EMF'LC)YEE. SET. S2 SYCTEM. 21Eb1E?ER. SALARIED. SET. SUF'EF: VIS. P. '4 b,. Emr)ioy+Q. 8 20. 3t.r·eet. 23. City. Hourly. :. -.ddi-ess. state. ar\.-' c',. empl. oyee number stat.u: í.. 20 8 '20. 2mp!o;""c. narn·:. 25. City. Cl. -. Hourly rate. Gtírz·Qt 3cÍcÍress. 1:6!. í""aí·:. Em!7!c'yee SORTED. NUMBER. SORTED. NUMBER. FORTED. NUbqBK:. '! : H7. 1 : ?'1. EMPLOYEE SAL,'4RIED E!4FLOYEE. R. !. state. )istnumber". by employee. Salaried employees: by erítpioyee. number'. Supervisory. re}atj.LDp-3hiDc.. SALARIED. '¶ DLI!-.. for Employee. Gu.pervision. ""IGURE. T). status. name i",at-.e. Em;: ' i 0.)/"-± E: í!j)íoVt£·z·. (3. MAN. number. F.KlK)!oyec"·. 2C). AUTCJ. 9\",'NER. /FIER O'i/b'ER b.iEMBER K4E\1BER. '·,. TfjF. record. Employee Empíoy'ze. 6 6. 7aj¿Ári'-". HAFE WACTRATE ADL'REGG C J TY. O':. t. CHAR CHAR CHAF' REAL. CHAR Ci-íAE. CHAE CHilE CH/',F: REAL CHAR CHAR. ST,'",. Documentation. System. COPYRIGHT. í979,. 19?C,. ?4. LCro. Data. II. Exmnple. .D.5. Base Systems,. t nc. .. 41. ..

(42) MOBS. Data. Management. System. Fina! ly, consider subroutines.. It. a. Record Set. SI. member. a. r' P. .'. To. se. obtain routine,. a. !. l. Muc h. base. in turn more. complex. COPYRIGHT. and.. of". name. The data. 1979,. te. that. o. is. f". each. a. CALL. so=c: i. a. '. and the í:. a. ort.ed. basic tools. 1980,. ir'.. Micro. a. clear,. Zkzta. 17?2£. iv to. all. ca3Ñ. led.. c...ulc!. of". sL'.l'·r'{.-)\.íC': .:"-,.. thos.±. than. s. used. in intuit:. ck-z. e. !"TlBS. ive. Base Systerrm,. z:.. ±'. the. -;. 3!L?BS. Cl. 'I.c!. a. ',:)e. ;"..'n e. rn.ízde. t. r. I") e. 7CCÑJÑ"ü-c-!ñCt". :",l1ed.. pos£-i: 3j") 'si'th. t. and !. cal. s. specií"icid. t c:. i-. owner. the. make. ": '?. CALL. that. fled routi/","-' of t. i:u.. bM--h. as. 'acces. prement. 3íê. :. arid then. list. of". Ií.!j.G.. ly-. easi £U3?2. members. conveniently. Fj.,c: '..1.re. subrcmt. CALL. lists. szíbrouf.ines. in. type 1 I. computer. subroutine in the system. necessary. of set t-'me. structures. GUBR. record. ?. c.7-ñ. ¿"í.}j. i th. list. produce-. of". type. powerful elata structures. systems. flexibility.. ©. t-o. cross—refc,u'ence.. to be accesseci. Gimiíarív,. current owner of' set type. to. ñ?ñie w. e. member. records in sequence. accessed. routine rec-: n"d. sorted.. a. routine tk.e currer)t.. most. É>jerj. stores the. t t yp. used. to be MAe to obtain sor': -?d. al lows any subroutine. specified. data. base. Consider. S'UBR. type. many—to—many. a. cal. I. routi: je.. gíven. data. a. is desirable. subroutines which by. Documentation. '. i3. :"r'3'2'!7s. other e: At.rem(=. c-"j2ñ. tine. way.. Inc:. .. 42.

(43) MDBS. Data. É'!ana3em(3r.t. System. RECORD ÍTEM. SUB??. NA?.4F. CHAR. SET. SI. AUTO. 2í','lUR M7\iBER. SYSJTÉM SUER. SET. CALL. Documentation. Subroutine. 8. 1 :. MAN SORTED. N SORTED. NAME. Sorted names. SORTED. NAME. Subroutine cal ling relat.io: -íship. 1 : II!. NAME. (,, °'"""' '7". ?. ltiEMBER END. ,. for Subroutine Cross—reference FIGL'RE. COPYRIGHT. ooí". SU 'R DDL. g. list. name. 1979,. 1980,. Micro. Data. Example. II.D.6. Base Systems,. Inc.. 43.

(44) MDBS. 5. Data DDL. .. I DDL. Management. Documentation. Specification the. n. System. lists. following. specifications in. parameters. a. is presented. det.ai. presented to the. l. DDL. Th e. .. of". summary. o. the. paramepers. This cectior. r. d. '-'. in. r. details. whi ck. ±. tlm:. eac-h. f'or. eac h. of the i'. o. the. ""'". sections must be. analyzer is:. (optional). FILES. DRIVE "". PASSWORDS RECORD. (optional). ITEM SET C':,'NER. MEMBER END. line of text rnust be preceded. Each b. lank. entered. (See. the. P. ii lustrates. a. typical. descriptions. of". the. specification Before the. ©. column. that. so. space. Th. various kind-s of. l. ines. nv.raber. digit line II. is. an d. a. to the si: &'z character. refer. Section. f7. stream.. DDL. .. E). F i. .. gi.gur'=. that.. l. gm-e Í"gj. ap,?ears. in. can appear. I. D .. .. 7. lo':ing a. DDL —--. stream.. presenting. th e. various relationships. COPYRIGHT. o. 4. a. would. 1. command. by. 1979,. 1980,. I. ayouts. between. Micro. ,. the. access. Data. following levels:. Base Systems,. summary. one. m'.-'st-. inc. .. is gi·ven. ac7-,ar. on. to:. ----. l|l1 m...

(45) MDBS. Management. Data. any data. For. For. type, record type or set. item. its write any data. Documentation. System. leve!. access item. I:. its. read. level. access. type. level. i t s read aecems level " the read access. o. f". its. record.. t ype i ts. write. level. " the write access. levezl. access. oí". its record. its. depending. t yp e For. any. variable read. its. on. its. i. any. líe. read. its. wr. it i te. which. For. th e. =. write. level. access. of. its. the any. it. s,. the read access. level. o. r. an y. t. in. se. +. level. access. ES. the write access. level of any set in. participates these. conventions are not observed.. (but not mandatory). fol lowing. that the data. bas. e. designer. convention:. sort key reñí which. COPYRIG}iT. level. 'oart.icipates. is recommended. i ts. S. level of'. item. c·n. will result if'. errors. observe. level. access. acc'ess. which. It. the read access. record type. its. DDL. =. e r.í. deper.din,q Fcm. level. access. t: .. wr. length item type. access. it. 1979,. is. a. 198Ci.. 1evel. s the. read. access. level for the set(s). sort key Micro. Data. Base Systems,. Inc.. 45.

(46) MDBS. Dnta. Management. its write. N. DDL. o. errors. wi. is }. l. Documentation. level. access. it. which. System. m. the. write access. level for the. set(s). sort key. a. result. if". a. designer decides. not. to f"ollow thie. convention.. ©. COPYRIGHT. 1979,. 1980,. Micro. Data. Base Systems,. Inc.. 46 m~'.

(47) .--. MDBS. Data. Management. System. Documentation DRIVE. The DRIVE on. i. ine. particular. a. drive. specifies. the number of data base pages that drive.. The second. 1.. user"s. Th e. drive 2,. Columns. Parameter. 1—5. "DRIVE". 8. Line. e t. c. .. The. reside. f"irst physical drive is called DRIVE. !. inc:. Kivout. J. '.s:. Description —. liríe type. Drive number. 12— 15. Number. OÍ". pages. allowed. on. Notes: 1.. 2. "". .. The. drive numbers must be one of 1,2,3,4,5,6,7,. The. last drive line. drive lines with the. will. same. be. used. if". there. ar e. or 8. two. o. r. more. drive number.. ·.. 3. .. 4.. ©). The number The DRIVE. COPYRIGHT. 1979,. of". pages. must. be non—zero.. lines must immediately follow. 1980,. Micro. Data. Base Systems,. a. FILES. Inc.. card.. 47.

(48) MDBS. Data. Management. System. Documentation END. The. END. description. line. is. used. to the. DDL. analyzer".. Columns. Parameter. 1-3. "END". tc. Line. signify The. the. end. of. the. data. base. format is:. Description. - line. type. -.-. ©. COPYRIGHT. 1979,. 1980,. Micro. Data. Base Systems,. Inc.. 48.

(49) Management. Data. MD2S. Documentation. System. FILES The FILES. line and FILES section (which wh. section. optional. i eh. 2. The data. .. Th e. base. ri lename. maximum number. reside (default. is 3.. The data. If" the. FILES. missing. section information. .. 1. base. the. name. FILES. ,. of". I),. page. ,. disk drives. t-he. which. data. base. wil. }. a. ful ly. and. size (def"au1t. is 512). is prompted. for. FILENAME?. with the standard defaults,. line format. lumns. 1. on. by:. together. is used in place of. is: Description. Parameter "FILES". 1—5. 8—. is. section.. The FILES Co. description,. data. a. consists of:. DATA-BASE. is. from. section is not present, the user. qualified filename. Th. This is an. using standard defaults.. supplied by the system The FILES. if. ,. lines). DRIVE. includes the. to define the data base name, size and location.. used. ar e. Line. 9. Data. —. base. according. line type Í"i. le name.. This must be. t o th e conventions. fully qua1ií"ied of". the. operating. system. ©. COPYRIGHT. 1979,. 1980,. Micro. Data. Base Systems,. Inc.. 49.

(50) MDBS. Data. Management. System. 23. Documentation. Maximum. 26-29. disk. drive. drive. number. number. of". Data 25€3. 1. the. A. this. ,. maximal. base page. .. number".. recommended. f"ielc'. such. size.. Calling must. Í7i.rst.. contain the. index.. This must be value. t-h e. multiple. a. of". is 512.. Notes: When. 1.. to. the. section is missing, the def"au!t.s. equivalent. ar€:. :. 2.. FILES. "prompt. DRIVE. 1. Suppose. drive.. .. name". 512. 1. 50. the. Column. DRIVE. 3. FILES. wanted. user. 23 would. his data base. contain the. the. on. number". 3.. first. There. and. third. ',\'c)1-líd. be. no. line for drive 2.. Th e. first. drive must always. is not enough room need. t. th e. gerierat.e. c). the. on. be used. C'.r3¿a. a. drive to hold. first data. in. base. base'.. ali of. ,. art. errc.r. on. the. first. II. i: h e. tab les x:. mc"ssage. there. 'il!. be. generated. The. 4. name. not 5. .. DDL. of the data base the For. course, COPYRIGHT. an. case, a. that the ©. analyzer expects. multiple. first the. file. error. 13. file. specified. drive have 1980,. a. system Micrú>. in colurnr,s. drive having 8—19.. II". this. the. is. generated.. drive data base,. MDBS.D!4S. 1979,. a. file. the. DDL. analyzer rü±Qijires. with the data basc· filename.. requires that al. Data. ünly. Base Systems,. i. réi'erenced >")c.. O C. drives 50.

(51) MDBS —-. ©. Data. Management. have. a. COPYRIGHT. file. System. Documentation. with the data base filename,. 1979,. 1980,. Micro. Data. Base Systems,. Inc.. 51.

(52) MDEIS. Data. Management. System. Documentation ITEM. ITEM. The. record—type. and access. line defines Parameters. data. a. within. 1-4. "ITEM" Item. i5. t- yµ e. iz. s. ,. t=. defined. replications. ,. Item. 7—20. INT. Description. name. tí"ii"j. —. i t =m. The. .. {Integar). IN. —. Th e. —. o t.. s. tar. t:. name. i tb. w. a. 2. i teíi. i. hoí:. your. t. host language. your. integer. aí'í. L'?. th e. by. variables. has. The item. —. va. ríi:. }to3e. \.':. i t em áy. s. i ze. only be. 1. I. and. uc±. stor'eti in. 13. (true,/. zero/one. a. c'ríe. byte i n. dat.a base.. i. padded Micro. -:. Binary. (Character) an d. i: stored under. bytes in length.. (Logical). the. are:. value is limited. false). 1980,. y!. valid. a. for real variables.. (Binary). or. 1979,. t. is stored under. The item. specified.. CHAR. mug.. contain. format for integer variables.. maximum. LOG. name. The item. --. Í"ormat B. must. Valid item tyoes. t:ype.. language REAL. field. sign ("j': ") or be blank.. dollar. COPYRIGHT. ±. - line type. for" the. 3. th: iñQst recently. levels. Parameter. 1. item. define the item 's. Columns. 8—. Line. —. The. stored. s3. or.. Data. th. e. ite: as. is. ,í. a. right. Base Systems,. ¿Ik. character. 3tring. leiágth. 3t.ring,. fixed \k/. i. Inc.. t'. h. blari7s. i. l"'. 52.

(53) MOBS. Data. Management. Documentation. System. necessary. IIJFC. (Internal. host. your. ). —. The item. language. format.. Decimal. clecir,ial. Item. 21—24. Size. .. e. .. COBOL. ,. ror. format.. language. (i.e.,. CC'BÜL. uridem. external. fields. with. of". bytes. picture).. size.. Th. in. is. value. record. a. the. is. number. the. ror. occurrencE. i t em. .. vary according to the item type:. ranges. INTeger. i. is stored. The item. —. variables,. S999. allocated. imal). Dec. host. yo u.r. ¿j. (. fields).. COMPUTAT!ONAL-3. (External. internal. ror. variables,. decimal. XDEC. is stored under. an. REAL. d-. should. The number. —. be the. number. oÍ". of bytes specified. bytes. language. host. t o store internally (see. variables 1. manu3. ). .. Using. result. in wasted. using. a. i.. space. size. standard default. (see. l9ote. always. INT. in'ceger the. by. .your. and. real. MDBS.. SYS. size larger than this wi. a. smaller. tPr'zt. used.. the. t h e data will result. base;. n. MDBS.SYS. wijl. in. manua. use the. I !. a l ). .. default. value. BINary. —. The. size 127. from ©. COPYRIGHT. 1979,. 1980,. Micro. size c). to. may. be. r. 1. be. stored.. -32767 Data. 1. byt.e. c). 2. r. allows values from through. A. size of 32767. Base Systems,. to. Inc.. 2 be. bytes. —127. A. through. allows veCues stored. 53.

(54) MDBS. Data. Management. System. Documentation. LOGical. The. --. CHARacter. —. largest-. it. e m. size. may. Th e. size. ".'Crin% i'·jo. .. be. only. t. byte.. should. size tQ. bytes need. L) t?. be. equal. ztored. a! locatc·d. be. to the in. t.h. is. string. !"or. headc'rs. 2@—28. (optional)ReaA access. !. access zero 30—32. ev. ¢X·l .. be. riay. A. be. o. r. leve!. iñcú.-y. zero. item. leve!. specified. access. here. by. her'e A. be. a. iterri"s read. the. read. leve!. access. vali.d data. may. 255. and. zero. ÍÚás2. o. i". user.. n\.Im}.?er. between. zero. to deí'ine. the. record's. write. writ.e. acc'.±".s. level. a. —. between. to deCine. with. ac: cessed. (optional)i'dr"i.te accé3s may. nurrkcr. a. —. specified. be. ma y. level. record with. a. created, deleted. cc-. and 255. altere{:. .:. 3.?y. any. valid data base user. "'7Á. 36—43. (optional)0epending record 47 ). ,. by. item. name.. is. type. the the. of". value. This other data depending—on). only. be. record specified. yp e 7ú"nc|. replications. i tern. if". f". the. is assumed to repeat. C). COPYRIGHT. 1979,. 1980,. A. .. for the I. .. can item. is called the. item. depending. no. it.em a. is. a. Nicro Data Base Systems,. Inc.. a 4t3—. controlled. depending item. item. of". (. name. i tern. repeated. fixed number. f". in t.his record.. data. t. o. columns. be. depending l z,s. item. (see. item. another data. sprcified t.. last data. repeated. a of". ncin.ber. If" the. ,. Cl. r. can Cy f7. a. name. is. item,. it. times.. 54.

(55) Documentation. System. Management. Data. MDBS. ?. (opticnal)Replication ~repeated. 44—47. If" the. field.. item, the replication. is. a. a. is specified. factor. item. is. i t. em. data. f th e. length. variable. is the maximum number. factor. is allowed to repeat-.. t!"ie item. of times. I. item, the replication. this. in. V. íactor.. Notes: If" no read. 1 .. level (columns. access. level for the item. access. deíaul. will. leve! of the record containing 2. .. Th e. read. .. .. 6. .. The. write access. .. A. access. iteñj.. be. great:. er. level for the item must be. than. o. r. containirg%. greater. t.P'.an. o. r. level for the record typc: containing. item.. variable. item. in. Th e. r ead. a. length data. 1979,. item. can. only be sµecif"ied as the. i. act:. record type. an d be. depending—on. COPYRIGHT. read. t.h e. leve! Í"or the record type. to the write access. type must. ©. to. level tor the item rríust. to the read access item.. the 5. access. the. equal. i:. read. level for the item must not exceed the write. access. The read equal. 4. the. the. is specified,. level.. access 3. 26—28). write. equal item. 1980,. to. levels of. access the. read. and. a. variable. write access. length item. levels. OÍ". i. t.. s. type.. Micro. Data. Base Systerns,. Inc.. 55.

(56) Data. MDBS. Management. System. Doctzmentation MEMBER. The The. MEK'1BER. Line. line is used to specif"y. a. member. record type. of". a. set... format is: Column. Parameter. 1-6. "MEMBER". 8—15. Record. - line type type. that. type type. Description. of". name i.. s. a be. t.r"eat.ec!. fol low. th e. to. defined. previously as.. a. rn.cunber. record record.. .. Notes: 1.. One. each. jg. COPYRIGHT. or more. MEMBER. set in the. 1979,. 1980,. I. DDL. ines. must. Q:. Ñí\'ER. Un=(s). ror. specification.. Micro. Data. Base Systems,. Inc.. se.

(57) MDBS. Data. Documentation. System. Eianagement. (J7.'NER. OWNER. Th e. The. line. is used. t".:. Line. 3peciry. j. re(zorc'-. an. owner. a. previously. type. of". a. set.. format is: Co. 1. I. ". -5 15. 8—. Description. Parameter. umns. OWÍIEE. Record type. ". l. -. i. type. (or. "íî e. name. S2t"STEM). t ype of'. .. defined. record. that is to be treat.ed as an owner. record type. Notes: 1 .. 2. ©. .. One. or more. DDL. specification.. SY3TEM. COPYRIGHT. O\'IldER. owned. 1"í79,. sets. 1980,. lines must f"ollow each. may. Micro. have. SET. i. ine. pair in. the. only one owner.. Dat.a Base Systems,. Inc.. 57.