for TURBODOS (1.2 and Subsequent Versions) Micro Data Base Systems, P.O

Volltext

(1)"a,. "": ,;<. MDBS Multiuser Supplement. :::. G%%,. for TURBODOS (1.2 and Subsequent Versions) Micro Data Base Systems, P.O. Box. Inc.. 248. Lafayette, Indiana 47902. :. USA. October 1982 Revised. December. 1984. Copyright Notice This entire manual is provided for the use of the customer and The entire the customer's employees. contents have been copyrighted by any means is by Micro Data Base Systems, Inc., and reproduction a except agreement as permitted in prohibited with Micro Data written Systems, Base Inc. Trademarks:. (C). COPYRIGHT. trademark of Micro Data Base registered TURBODOS of Software Systems, Inc. is a trademark CP/M 2000. a is trademark of Digital Research. MDBS. is. 1982,1983. a. Micro Data Base Systems,. Inc.. ^%.

(2) NEW. Any. programming. RELEASES,. endeavor. necessarily continue Base Systems, Inc., version for a nominal. VERSIONS,. of the. to evolve vows to. AND. magnitude over time.. provide handling fee.. its. A WARNING. of the MOBS software will Realizing this, Micro Data users with updates to this. versions of MOBS software will be considered as separate products. bona fide owners of previous versions are generally entitled However, to a preferential rate structure. New. each copy of our software is personalized to identify the There are several levels of this personalization, some of licensee. which involve encryption methods guaranteed to be combinatorially Our products have been produced with a very decipher. difficult to investment of to say nothing of the capital and labor, substantial base management involvement the data area by our of prior inwe years Accordingly, concerned about any principals. are seriously unauthorized copying of our products and will take any and all available legal action against illegal copying or distribution of our products.. Finally,. DISCLAIMER. All rights reserved. reproduced, stored in a. No. NOTICE. part of this material. shall. be. transmitted by any means, retrieval electronic, mechanical, photocopying, recording, or otherwise, without written permission from Micro Data Base Systems, Inc. system,. or. Although care has been taken in the preparation of this material, Micro Data Base Systems, Inc. assumes neither responsibility for or omissions, nor for damages resulting from the use of the errors information contained herein. Micro Data Base Systems, Inc. does not warrant its accuracy nor guarantee the operation of the system in every instance described herein. The damages and for. reader/user assumes risk for any liability and contained full all from the the use of herein, resulting information determining whether the information contained herein is suitable for user's intended purpose. Micro Data Base Systems, Inc. reserves the right to incorporate design improvements and new functions in its software products and may Recent improvements not always be reflected software systems. in documentation.. (C). COPYRIGHT. 1982,1983. Micro. Data. Base Systems,. Inc..

(3) TJRBODOS. MULTIUSER. TURBODOS. SUPPLEMENT. MULTIUSER. SUPPLEMENT. PREFACE. Although the great majority of MDBS features and"facilities are and host programming system independent of the host operating languages, there are some system specific aspects. These include the installation procedures, execution command lines, DML command forms, and data item-host This manual, language variable correspondences. together with CP/M System Specific Installation Manuals, presents the system specific aspects that are r.eeded in order to use MDBS DDL/DMS, MDBS-QRS,. MDBS-RCV,. This manual. I.. II.. IV.. (C). consists of the following. chapters:. INTRODUCTION. a. B.. Overview. C. D.. User. File. for. Names O. Software. MDBS. Contention Count Defaults. INSTALLATION Checking A. the TURBODOS Delay the B. Data Management Booting C.. III.. and MDBS-IDML.. MDBS-DMU. DML. A. B.. Executing. DIFFERENCE SETPBF. Multiuser. a. Run. IN. ENVIRONMENT. Commands. C. D.. Recovery. E.. Exceeding. f.. Buffer Flushing. Procedures. DBSTAT. the. ADMINISTRATION IN A A. Stats B. Reset C. Close D. Logout E. Quit Batch Usage of f.. COPYRIGHT. Function. Unit. MULTIUSER. A. Process System. 1982,1983. User. Limit .. MULTIUSER. ENVIRONMENT. DBMTR. Micro Data Base Systems,. Inc..

(4) TURBOJX)S. MULTIUSER. SUPPLEMENT. MULTIUSER. TURBODOS. SUPPLEMENT. INTRODUCTION. I. Overview. A.. document Specific is a supplement to the CP/M System under Manuals the operations describing multiuser Installation TURBODOS describes the operating system (version 1.2 and greater). under the TURBODOS needed steps for using MOBS operating system.. This. It. III. multiuser access of an typical memory configuration during One memory bank contains data base is shown in Figure MDBS code that continuously MDBSDMS, the resident data management executes to support run units which need to access the data base. This memory bank also contains program buffers which hold data base Each of the other memory banks pages needed during MDBSDMS execution. buffer. typically contains a run unit along with a small communication The. I-l.. MDBS. TURBODOS. MASTER. Operating. TURBODOS. ]. SYstem. 64K. Disk Buffers Dynamic. Transient. &. Memory ProRra1n. Area. -. V"¶. L.". '-d. TURBODOS. TURBODOS. Slave. L-'. Slave. Slave Comnunication ". TURBODOS. Communication B,u.f.f.e.r.. Program. _ _. Buffer. Bu.f.f.e,r,. _ _. _ _. _ _. )"32K. >64K. MDBSDMS. Run-Unit-l. .. .. .. .. Run-Unit-n. .. u. —MDBS Data. Bá"j. Figure. (C). COPYRIGHT. I-1.. Multiuser Access. 1982,1983. to an. MDBS. Micro Data Base Systems,. Data. Base. Inc.. I-l.

(5) 'fURBODOS. MULTIUSER. - I -. SUPPLEMENT. TURBODOS. MULTIUSER. SUPPLEMENT. (MDBSDMS) RAM the TURBODOS system utilizes You need to adjust the number may memory. dynamic memory portion of enough the room for of disk buffers to allow the TURBODOS master. Howeyer, is desirable to avoid allowing more This adjustment can be room than is necessary for dynamic memory. TURBODOS made by regenerating system or by using the BUFFERS the of the command. The system adjustment (more or fewer operating nature depends, in part, on disk buffers) is determined experimentally. base and number processing the existence of non-data of users the data base processing. concurrently with. The data management of dynamic FIFO mechanism. it. It. File Names for MDBS Software with two exceptions, all files describedthe in Section I-A of the. B. CP/M. Specific Manual are provided with multiuser version of exceptions are OS.REL and DMS.REL whose contents are different than those of the CP/M DMS.REL. Although the TURBODOS DMS.REL consists of OMS interface code (rather than a library of OMS routines), is used in exactly the same manner as the CP/M DMS.REL during selective linking. MOBS.. System The. it. Four. additional. files are also provided: test program for TURBODOS. delay function resident data management code interactive multiuser administration buffer flush utility. DELAYl5.COt'4 MDBSDMS.COM DBMTR.COM DBSVU.COM. If is. the RTL form of MOBS provided and replaces. C.. User. Due. run. in. utility. named MDBSRTL.COM file following procedures. a. O. Under TURBODOS to the design of under user O: Resident. the. file. system is partitioned by user number. the following should always be programs. TURBODOS,. Code. (MDBSDMS. in Figure I-l) (the ddl analyzer) (the design modification utility) (the recovery utility). DMS. MDBS.DDL MDBS.DMU MDBS.RCV. that. to be used, then is MDBSDMS.COM the. process. single copy of MDBSDMS is executingat anygiven moment in environment. Since this resident DMS code operates against base one data at a time, each run unit must give the name of that data base (e.g., in the DBOPN command).. Note a. a. TURBODOS. D.. Contention Count Defaults See Chapter. I-2. I of your. (C). COPYRIGHT. MOBS. III. CP/M. 1982,1983. System. Micro. Specific. Manual.. Data Base Systems,. Inc..

(6) TURBODOS. MULTIUSER. TURBODOS. SUPPLEMENT. MULTIUSER. SUPPLEMENT. II. INSTALLATION The installation Delay of MOBS involves testing the TURBODOS Process Function,, starting the data base manager by executing MDBSDMS, and then executing individual run units. Checking. A.. the. Delay. TURBODOS. Process. Function. version 1.2, the multiuser data management system This function is a uses the Delay Process function call. number 125 of the documented as function part of standard TURBODOS checks is a program that to assure that the Delay Process function has been correctly implemented. Execute DELAY15.COM. implemented, the following Delay Process is correctly If three lines will be displayed: Under. TURBODOS TURBODOS TURBODOS, DELAY15.COM manual.. NIDBS. TurboDOS III program will. This Testing Completed. Process Testing delay for approximately 15 seconds Delay. substantial final line is not displayed after waiting for a TURBODOS has of time, then the Delay Process function of your You not been correctly implemented and is not operating properly. should contact your hardware/operating system vendor to ask them for instructions about how to make the Delay Process function operate. If the period. properly.. Booting the Data Management System. B.. Under the execute. the TURBODOS operating system generated above, you now resident data management code under user O, as follows:. MDBSDMS. -Bnnnn. -Lfilenamel. filename2. The. -B and -L arguments are optional. The filename2 argument is required. It is the name of the physical file to which the main area of the desired MDBS data base has been assigned (in that data base's DDL specification). source option is not Ifof theits -Bmemory segment. remaining entire a smaller space If of size nnnn decimal on the command line. The -L option can be to specify the file (filenamel) to which all transactions are tortl be logged. If this option is not used, transactions are logged to the log file as declared in the data base's DDL source specification. All filenames must be fully qualified. When MDBSDMS has completed its initialization phase (depending on the current system load, this may take up to a minute), the following message is displayed: MOBS III Data Management System Initiated At this point, users may start their tasks. The console on which the message is displayed is dedicated to the data management system until another console terminates the MDBSDMS execution with the Close option of DBMTR (see Chapter IV of this manual). space. (C). COPYRIGHT. used, MDBSDMS uses for program buffers. is desired, then use -Bnnnn used in conjunction with. 1982,1983. Micro. Data. Base Systems,. the. Inc.. II-1.

(7) TURBODOS. C.. MULTIUSER. Executing. a. SUPPLEMENT Run. -. II. -. TURBODOS. SUPPLEMENT. MULTIUSER. Uñit. The. procedure for executing a run unit is procedyre used in a CP/M environment (see Chapters CP/M System Specific Manual).. to the identical and VI of your. II. Note that run units are not restricted to application but can also include executing instances of QRS and IDML. invoked as described in the CP/M System Specific Manual. RCV. and. they should. II-2. DMU be run. cannot be executed in multiuser mode. under user in single user mode.. (C). programs, These are. When needed,. O. COPYRIGHT. 1982,1983. Micro. Data Base Systems,. Inc..

(8) SUPPLEMENT. MULTIUSER. TURBODOS. SUPPLEMENT. MULTIUSER. TURBODOS. DMLDIFFERENCEINAMULTIUSERENVIRONMENT. III. SETPBF. A.. multiuser environment, SETPBF is invoked just as In a TURBODOS However, described in Chapter VII of the CP/M System Specific Manual. the run the argument of size indicates has a different effect. Its The appropriate size communication buffer (recall Figure I-l). unit's DDL base initialization and is Analyzer during data is computed by bythetheDDL Analyzer with the label: displayed. it. If your of host discussion. not make use of invocation is of no concern. above. the. to you.. Commands. Multiuser. B.. then. SETPBF,. does. language. SETPBF. environment. buffer size for multiuser. communication. xiv of the mdbs dms shows Table the multiuser locking contention protocols. (This table supersedes Table XIV-l of the DMSUser's Manual for all manual revisions prior to and including Revision 82A). commands described in Chapter The multiuser Manual are available in a multiuser environment.. Rm1kiit3. Locking Contention protocols. Multiuser. III-I.. Table. III-I. Oi$connect all member (owner) records from set-2. &ttewpt8 Find. or. locked record. Modify locked record. permitted. not. retrieve Rim hm. lhít. PmUve lock on & record. Create record. permitted. not. relevant. Connect record. Disconnect a record. into set-2. frm set-2. permitted. not. if8ameA for. permitted has the CO md CM =t-2 as B. Delete record. permitted not has the CO(CM) for set-2 as B and CM(CO) of set-2 for A 18 non-. permitted. not. ifsameA. null Active lock on. Active lock OIl all recorU of & record. permitted. not. relevant. not. relevant. not. relevant. not. relevant. permitted. not. relevant. not. permitted. not. relevant. Rot. permitted. not. relevant. not. relevant. permitted. not. permitted. not. permitted. not. permitted. not. pemitted set-l " 8et"2. not. permitted. not. not. permitted. if. 8et-I if set—2. type. AcUve lock on recQrd8 of »et—l. Ul. riot. a record. not permitted through 8et-l. if. attempt to mdify 8ort key value of. 8et"l. record if auto owner member. aet"l. Ia or. of. ". permitted. 8et-l if et-2. ". if record owner or ber. of. is mera-. Bet-l. The unit of time used with Turbodos for the OMS contention count See the command is one clock tick (i.e., 1/50 or 1/60 of a second). MCC command in the MDBS DMS Manual. (C). COPYRIGHT. 1982,1983. Micro. Data. Base Systems,. Inc.. III-I.

(9) TIJRBOIJOS. C.. SUPPLEKENT. MULTIUSER. -. III. -. Since page posting is generally environment, posting is not allowed Thus. result in effect.. be used. but have. a. all. Because run LGFILE command should no effect other than. units a. used,. other. log transactions to a single log file, the has a multiuser environment. It 34. of. not be used in command status. displays. Exceeding. statistics for. the. aggregate. of. all. run. units.. the User Limit. If. too many run units attempt to use a command status simultaneously, of 67 (User Limit DBOPN the offending run unit. from the of F.. If no. DBSTAT DBSTAT. E.. not meaningful in a multiuser with the multiuser version of. not PIFD and TRABT commands should 34, command status message of. the. they. D.. SUPPLEMENT. MULTIUSER. procedures. Recovery. MDBS.. TURBODOS. the. data. Exceeded). base results. Buffer Flúshing. the data management system does optimize speed under TURBODOS, background buffer flushing. not perform automatic If periodic buffer flushing is desired, a terminal can be dedicated to the DBSVU utility while MDBSDMS is executing.invokedDBSVU will flush the buffers by entering: periodically. This utility is To. DBSVU. n. where n is a positive seconds between flushes is assumed.. the approximate number of indicating DBSVU. performed by If no n is specified, 300. integer. Since DBSVU uses the DBSAVE command, can generate the same status numbers as DBSAVE. In addition, there are two other One kinds of possible errors. is a command line argument error that results from specifying a non-positive integer value for n. The other is a communication error which indicates that the OMS is not executing or a hardware/operating system error has been encountered.. it. command. DBSVU. is terminated by pressing the Escape key or Control-C. If closed by DBMTR (see next Chapter) before terminating hang and necessitate resetting may the slave running. data base is DBSVU, then DBSVU the. DBSVU.. ÍII-2. (C). COPYRIGHT. 1982,1983. Micro Data Base Systems,. Inc..

(10) TURBODOS. MULTIUSER. TURBODOS. SUPPLEMENT. MULTIUSER. SUPPLEMENT. ADMINISTRATIONINAMULTIUSERENVIRONMENT. IV.. is an interactive multiuser administration utility that can is not counted executed simultaneously with various run units. It 4 MDBS, DBMTR a For as run unit. can through multiuser versions of be executed the same time that four run units are executing. It is at invoked by entering DBMTR. be. l. DBMTR. the operating system command following prompts:. on. MDBS. (C). line.. responds with. DBMTR. Multi-User Data System Monitor Copyright 1982 Micro Data Base Systems,. Inc.. the. Ver. 3.00. Option Summary: and operational statistics display communication Stats: communications Reset: reset Close: close data base and shut down communications Logout: log out one or more users from the data base system Quit: exit monitor Option (Stats, A.. Reset,. Close,. Logout, Quit). ?. Stats. Paging statistics with respect to the entire are displayed multiuser environment (i.e.,thoseaggregate of all run units). These are identical to provided by the DBSTAT command (see statistics MDBS DMS Manual). In addition, B.. the. TURBODOS. user. number. is displayed.. Reset. This. function is used in the case of inadvertent or untimely a termination of run unit. It resets the FIFOS used for inter-task. communication. C.. Close. This function d. be. (C). terminates. execution of. MDBSDMS.. Logout. If. used. unit terminates before invoking DBCLS, to force a data base close for that run unit. a. run. COPYRIGHT. 1982,1983. Micro. Data. Base. Systems,. this function. Inc.. can. IV-l.

(11) TURBODOS. E.. SUPPLEMENT. MULTIUSER. IV. -. TURBODOS. MULTIUSER. SUPPLEMENT. Quit This function. F.. -. exits. Batcti Usage of. the multiuser. administration. DBMTR. of the five options described above DBMTR, invoked by indicating line that For instance, desired option. Any command. dbmtr. monitor.. specified on the first letter of the. can be the. s. When an option with the statistics option. executes DBMTR is specified on the command line, the menu is not displayed and there is an automatic exit from DBMTR after the option's task is completed. The Multiple options can be specified with no separators. options are processed in the order in which they are specified. (If then the remaining one of the options causes processing to terminate, For instance, specified options are ignored.) dbmtr. Is. performs the logout automatically exiting. IV-2. (C). option from. COPYRIGHT. and. DBMTR.. then the. 1982,1983. statistics. option,. Micro Data Base Systems,. before. Inc..

(12) DOCUMENTATION MDBS. Document. COMMENT. FORM. Title:. comments and suggestions welcome and appreciate Use this help us to improve our manuals and products. manual. express your views concerning this. all. We. that can form to. please do not use this form to report system problems or request materials, etc. System problems should be reported MDBS by phone or telex, to or in a separate letter addressed Requests support the of division. technical attention published materials should be addressed to the attention of marketing division.. to to. the. for. the. Sender: (position). (name). (telephone). (company) (address). (city, state, zip) COMMENTS:. of comment are general presentation, format, organization, completeness, clarity, accuracy, etc. If a comment applies to specific page or pages, please cite the page number(s).. Areas. Continue on additional. pages,. as needed.. Thank. you. for. your. response.. a.

(13)