CP/M with PL/I-80 Micro Data Base Systems, P.O.

Volltext

(1)yi7. ®1. "4. %g> %¿p<. "9. u. MDBS. III. q. ^> Manual Q. o. System Specific Installation. t. f or. CP/M with PL/I-80 Micro Data Base Systems, P.O.. Box. Inc.. 248. Lafayette, Indiana 47902 USA. bj. November. 1981. Revised October 1984. Copyright Notice This entire manual is provided for the use of the customer and The entire contents have been copyrighted customer's employees. Micro Data Base Systems, Inc., and reproduction by any means is prohibited except as permitted in a written agreement with Micro Data Base Systems, Inc.. the by. Trademarks:. tuj. MOBS. is. Systems,. Diqital (C). COPYRIGHT. 1981,1984. registered trademark of Micro Data Base Inc. CP/M, MP/M and PL/l-80 are trademarks of Research. VisiCalc is a trademark of VisiCorp. a. Micro. tata Base Systems,. Inc.. ^0,.

(2) NEW. u. RELEASES,. VERSIONS,. AND. A WARNING. of the magnitude of the MOBS software necessarily continue to evolve over time. Realizing this, Micro Base Systems, Inc., vows to provide its users with updates to version for a nominal handling fee.. Any programming. endeavor. will Data 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. of our software is personalized to identify the some of licensee. several levels of this personalization, which involve encryption methods guaranteed to be combinatorially Our products have been produced with a very decipher. difficult to investment of capital and labor, to say nothing of the substantial years of prior involvement in the data base management area by our we Accordingly, princiyíls. are seriously concerned about any unauthorized copying of our products and will take any and all available legal action against illegal copying or distribution of our products.. Finally,. each copy There are. DISCLAIMER. u ". NOTICE. All rights. No reserved. part of this material shall be a system, stored in or transmitted by any means, retrieval electronic, mechanical, photocopying, recording, or otherwise, without written Ejermission from Micro Data Base Systems, Inc.. reproduced,. Although care has been taken in the preparation of this material, Micro Data Base Systems, Inc. assumes neither responsibility for errors or omissions, nor for damages resulting from the use of the Micro ijata Base Systems, information contained herein. Inc. does not warrant its accuracy nor guarantee the operation of the system in every instance described herein. The damages and for. and reader/user assumes any full liability all risk for the from of information use the contained herein, resulting 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 Recent improvements software systems. may not always be reflected in documentation.. 'Ik.j. (C). COPYRIGHT. 1981,1984. Micro. Data. Base Systems,. Inc..

(3) PREFACE. YJ great majority of MOBS features and facilities are and host programming system independent of the host operating languages, These include the some system aspects. specific there are DML command forms, procedures, command execution lines, installation and data item-host This manual language variable correspondences. the needed system aspects specific in order to use that are presents DDL/DMS, Although. MOBS. the. MDBS-QRS,. This manual. I.. File Names for N!DBS Software Fully Qualified File Names in CP/M Special Keys when Using Interactive. B.. E.. Installing. TESTING MDBS.DDL. PROCEDURES. and. MDBS.DMS. Testing. MDBS.FDL SYSTEM. DEPENDENT. DEFAULTS. File name defaults for areas File extension defaults Pages per area default Paqe size default Page size restrictions ITEM. A.. Non-numeric ijata Items Integer Data Items Unsigned Data Items Internal Decimal Data Items Real Data Items Repeating Data Items. F.. VI.. and. Utility. DATA. B. C. D. E.. CONTROL. A. B.. Software under. Environments. The Renaming. OPERATING. B. C: D.. MOBS. Contention Count Time. INVOKING. A.. V.. CP/N! MP/M. INSTALLATICN a.. IV.. eight chapters:. A.. F.. III.. consists of the following. NAMES. D. E.. u. and MDBS-IDML.. MDBS-DMU. FILE B. C.. II.. NIDBS-RCV,. -. HOST. LANGUAGE. VARIABLE. CORRESPONDENCE. PROCEDURES. Running an Application Special Link Files. Program. U( (C). COPYRIGHT. l98l,l982,l983. Micro. Data. Base Systems,. Inc..

(4) FILENAMES. I.. u. A.. File. for. Names. MDBS. Software. the software of MOBS add-on packages are furnished iri a collection of files. In the CP/W: PL/I (2.2 and later versions of CP/M) environment, these files have the following names: The. software. MOBS. and. read.me. contains special is provided, thisannouncements If file it which you should and comments notes,. FNDMS.PLI. external. read.. PL/I. PLI80.REL A.REL OS.REL Z.REL RTL.REL ddl.com DDLI.OVL DDL2.OVL DDL3.OVL SAMPLE.PLI qrs.com QRSI.OVL QRS3.OVL QRS4.CVL QRS5.CVL QRS6.CVL QRS7.OVL. QRS8.OVL idml.conj IDMLI.OVL IDML2.OVL IDML3.OVL IDML4.OVL IDML5.OVL. RCV1.OVL. RCV2.CVL cnv.com. LJ. (C). COPYRIGHT. component. mdbs.ddl MDBS.DDL MDBS.DDL PIDBS.DDL. direct. library. (used. in place. relocatable file object code overlay l overlay 2 overlay. of. DMS.REL). utility. 3. call. sample. program. (for use with. SAMPLE.DDL). support overlay l2 support overlay suppcrt overlay 3 support overlay support overlay support overlay support overlay 7 support overlay mdbs.idml" object code IDML support overlay l IDN!L support overlay 2 IDML support overlay IDML support overlay IDML support overlay mdbs.idml object code (RTL form) RIDML support overlay 1 RIDML support overlay 2 RIDML support overlay RIDML support overlay 4 RIDML support overlay messages for QRS, IDML error error messages for hdbs.dmu object code object code for the MDBS-RTL recovery program: RCV RCV support overlay l RCV support overlay 2 object code for the DDL conversion proqram: CNV 4. 5. 6. 8. 3. 4 5. RIDMLI.OVL RIDML2.OVL RIDML3.OVL RIDNIL4.OVL RIDML5.OVL UTIL.ERR dmu.ccm rcv.ccjm. MDBS.DMS MDBS.RTL DATACOD. QRS QRS QRS Q2S QRS QRS QRS QRS. QRS2.OVL. DMS.ERR. component. sample ddl specification mdbs.qrs object code. SAMPLE.DEL. ridml.com. interface. MDBS.DMS CP/M. interface. DATACOD.COM. u. definition include file library language. NDBS.DMS. DMS.REL. 3. 5. OMS. 1981.1984. Micro.

(5) Interactive. Special Keys when Using. C.. U. (ENTER) RETURN CONTROL-X. terminates. CONTROL-H. causes. interrupts line a input. CONTROL-I. causes. CONTROL-C. CONTROL-P CONTROL-S CONTROL-Q. MP/M. input line line entry. character. Software. CP/M. restarts the input in the line being deletion and. character to be placed control to the operating tab. under. in the line system (hard. returns interrupt) causes the prompt of the interactive software to appear (soft interrupt) toggles the interactive software output between and printer the console a pause in the output from interactive causes software software to resume, causes output from interactive pause following a CONTROL-S. ESCAPE. D.. a. an a. MDBS. Environments. software for use under CP/M (versions 2.2 and later) can P1P/M. used under also This manual applies equally to MP/M and NIP/M CP/M. is too large to allow the use of ÑIDBS-IDML or MOBSNote: QRS with a one user be used under MP/l4 with configuration. They can NI1)BS. the l-4, and over multiuser versions of. All be. MOBS. 4. \J. factors including the extent of application, design, the host language used, the quality of apelication programming, data volume, the hardware used, and the operating system. Due to the directory utilization CP/M approaches MP/M, and of is generally true that MDBS provides CP/M than under MP/M. faster access under NIDBS. access. an. sEjeeds depend on many the quality of scheme. it. Contention Count Time. E.. The command MCC. unit of time used with MP/P] for the OMS contention count clock tick (i.e., 1/50 or 1/60 of a second). See the is one the command MDBS DMS Manual. in. ~ /. \. mum.

(6) II.. bj. A. .. INSTALLATION AND TESTING PROCEDURES. Installation. l.. MOBS. DDL. is installed by simply copying ("PIP"ing with the and DDL3.OVL DDL2.OVL, option) the DDL.COM, DDLI.OVL, MDBS.IJDL a working disk. Because uses an overlay to files technique, this working disk must reside on the default drive in order to execute. MDBS.DDL. ov. 2. .. OMS. MDBS.. Prior. you to linking MDBS.DMS and your application proqram, to create a CP/É4 DMS library (to be called CPMD14S.IRL). LIB. This requires th e u s e o f CP/M'S library manager, by entering the following Create CPMDMS.IRL system operating need. command. line:. LIB. CPMDMSIII. RTL is to be If except same, that. =. DMS,OS,A,Z. used, the you should. procedure is the installation instead of CPMD¥S enter CPMRTL CP/M RTL this creates a library.. and RTL instead of OMS; The library creation process assumes that the DHS.REL (or RTL.REL for RTL), OSCPM.REL, A.REL, and Z.REL are on the default drive.. files. U/. Now. copy FNDMS.PLI. CPt4DNIS.IRL. to. a. (or. CPMRTL.IRL. working disk.. for. RTL). ,. PLI80.REL,. and. G ( C' ). 1. t-. 7.

(7) III.. u. The. operating system. INVOKINGMDBS.DDL command. string. for executing. is:. MDBS.DDL. fully-qualified-file-name -Bnnnn where the fully-qualified-file-name and -Bnnnn arguments are optional. the fully-qualified-file-name is omitted, then the MDBS.DDL program If responds with the : prompt and is ready for interactive usage (see VI-A,B of the MDBS :DDL Manual). If a fully-qualified-file-name is specified, then MDBS.DDL is executed on a batch basis (see VI-C of the MOBS DDL Manual). The contents of this file must be a valid DDL DDL. specification. DDL. will. For. instance,. TRIAL.DDL. cause TRIAL.DDL. to analyze the DDL specification on the default drive.. É4DBS.DDL. file. The. other environment.. optional. argument (-Bnnnn). u. u (C). COPYRIGHT. Micro. can. be. contained in the ignored. in. this.

(8) V. \6J. LANGUAGEVARIABLECORRESPONDENCE. DATAITEM-HOST. that This chapter shows the type, size, and value correspondences and of usage between PL/I variables. Correct data items exist knowledge a depends DML commands these of and on get create, put, FMSK) DML commands (e.g., Other correspondences. also require inµít be must where consistent with a the variable from a PL/I variable, data item of a earticular type and size. H1IJI3S. A.. Non—numeric. Data. Items. PL/I variable. ——MESÁ2áM—Ikem___ NRES_aize NDES_tyEe. ELLI_ty9£. binary. n. character. n. character. n. character. n. string. n. character. n. date. -. character. lO. time. -. character. 9. size. RL/T. varying. the maximum size for a PL/I character variable is 254, no than 254 bytes can be stored from a PL/I variable into a data item whose type is binary or character. the size of an MOBS binary If or character data item exceeds 254, then right blank occurs during storage and right truncation occurs during retrieval. Since. gj. more. fill. Integer Data Items. B.. with various host language variables that are consistent sizes of an integer data item are presented This table in Table V-l. also shows the mappings of data values from PL/I variables into during data storage (e.g., CRS, PFM, etc.). integer data items items to Similarly, the mappings of data values from integer data GEM) corresponding PL/I variables during data retrieval (e.g., are The. shown.. As. example, when storing a data value from a fixed binary (7) a variable into one byte integer data item, the value must(7) be in the Any other value for the fixed binary range -128 to 127. variable not be permitted and the DML command that attempts to store such a value return a command status of 33. When retrieving a data value from a 3 byte integer data item into a fixed binary (IS). will. an. will. GOf. (C). COPYRIGET. 1981,1984. Micro. Data. Base Systems,. V-l.

(9) to 32767 is appropriate value in the range -32768 deposited in the fixed binary (IS) variable. If the stored value is outside of this range, then the value of the PL/I variable is As a to store the value undefined. third example, suppose we want accomplished -32700 into a two byte inty;er data item. with a This is (15) a command variable having the value that uses put fixed binary. variable,. gj. an. -32700. C.. Unsigned. Data. Items. with various host language variables that are consistent V-2. Table presented unsigned data This table in item are sizes of mappings shows the of data values from PL/I variables also into etc.). unsigned data items during data storage (e.g., CRS, PUTN!, data items to Similarly, the mappings of data values from unsigned(e.oo., GETM) are corresponding PL/I variables during data retrieval The. an. shown.. data value from a fixed binary (7) data item, the variable's value must. when storing example, a unsigned byte one variable into be in the range -128 to 127. As. an. a. data value from a byte unsigned data item a appropriate an fixed binary (IS) value in the range into variable, the (15) variable. -32768 32767 fixed is deposited into binary to If as the value returned the unsiqned stored value is 65533, then is -3. If the unsigned value is greater than 65535, then the value of the PL/I variable will be undefined. When. retrieving. 3. a. it. 'u. As. a. third example, suppose we want to store the value 32769 a into This is accomplished with data item. put (15) binary variable having the value fixed. two byte unsigned command that uses a -32767.. a. D.. Internal. Decimal. Data. Items. The. host language variables that are consistent with various sizes of an idec data item are presented in Table V-3. This table also shows the largest relative error that can occur when storing data into various sizes of idec data items and when retrieving data from various sizes of idec data items. When. storing data values into an iáec data item, there is no When potential for overflow. retrieving data from an idec data item whose size does not exceed fifteen digits (i.e., n S 15), overflow the stored data value has an absolute value greater than occurs (jQñ l)/j()á. When retrieving data from an idec data item whose size exceeds the stored fifteen digits (i.e., n 15), overflow occurs data value has an absolute value greater than (l0l5-l)/l0d.. if. >. if. GJ. (C). COPYRIGHT. 1981,1984. Micro. Data Base Systems,. V-3.

(10) Table. U. i. MDBS. l : ). l. Data. Internal. V-3.. l. Item. Decimal. l ). F'L/I Varíable. i. ! MDBS. size. MOBS. type. idec n,d. n=l,2...or. i. !. 15. :. jidec n,d. E.. Real. n. Data. .>,. 16. !. Correspondences. PL/I type. . Data StorInR Largest Relative Error. fixed decinnal(n,d). O. fixed decimal(15,d). O. l. i. . . Data Retri-evíng Largest Relative Error. O. ). i i ). l ). 5.000. *. 1Q-i6. Items. The. host languaCe variables that are consistent with various a real data item are presented in Table V-4. This table shows the largest relative error that can occur when storing data into various sizes of real data items and when retrieving data from various sizes of real data items. sizes of. U/. Table iV also shows the overflow potential when storing and data. For instance, an attempt to store 1.7014 * yj38 into three byte real data item will result in an undefined value for that data item value.. retrieving a. L (C). COPYRIGHT. 1981,1984. l. Micro. Data. Base Systems,. V-5. !.

(11) F.. U. Repeating. Items. Data. When. storing data into or retrieving data from a repeating data The appropriate kind of array for each ítem, a PL/I array is used. data item type and size is shown below, where represents the number of replications defined for the data item in the DDL specification Here, (with an occurs clause). "data" is the host language array being used for storage or retrieval. .. tn. Repeating. Data. Item. --=K?9íigÁtiQnsL mobs. tYpé. binary. n. data(m). char(n). character. n. data(m). char(n). string. n. data(m). char(n) varying. date. -. data(m). char(l0). time. -. data(m). char(9). 2. data(m) data(m). fixed(7) fixed. l2. data(m) data(m). fixed(7) fixed. data(m) data(m). fixed decimal(n,d) fixed decimal(l5,d). data(m). float. inteqer integer unsiqned unsigned. gj. of the PL/I Variable —__}=ÁY;—CLaka Form. MRES_size. idec iáec real. > —. .>,. l. n=l,2,...,or. 15. 16. Z. n. U (C). COPYRIGHT. 1981,1984. Micro. Data. Base Systems,.

(12) CONTROLPROCEDURES. VI.. W. A.. Running. an. Application. program. following steps are used to control the selective interfacing They assume routines with a PL/I application program. of MDBS.DMS completed. has been that installation as described in Chapter II The. l.. píoqram using the direct DML command your application DML used in the commands form (see Chapter VII). All be be externals, either explicitly declared to program must of or using the %inc1ude command with an edited" copy declarations FNDMS.PLI (containing only those external needed by the program). This is illustrated in Chapter VII.. 2.. Compile. Create. PLI where code. 3.. program. your. in the usual. manner.. For. instance,. PRG. PRG. is the. file. containing. Selectively link your compiled in the following way:. the PL/I program. program. and. MDBS.DMS. source toqether. LINK PRG[A],PLI80,CPMDMS.IRL[S]. \J. This assumes program. contains the compiled contains disk that working on is the that the program PLI30.REL arid CPMDNS.IRL (or CPMRTL.IRL in the case of RTL). It also assumes that this áisk is on the default drive. where. 4. B.. PRG.REL. Execute. the. linked program.. Special Link Files. can be used to optimize NOFLOAT, are FASTIO, NOCALC, NOIDEC, NODATE, NOTIME. NQREAL, and These are not always available in Those which are environments under all releases of MOBS. be linked with the application program. IE FASTIO is available canshould desired, you create CPÉ4DMS with the command line. Special. performance. which link files are provided These situations.. in certain. all. LIB. CPMDMSLI]=DMS,FASTIO,OS,A,Z. NOCALC instead of the command line shown in Chapter II. is If NOCALC by desired, then linked immediately prior to inserting is PLI80 in the LINK command line. If you desire to link any of the other special files, then insert the file name(s) prior to PLI80 an9 use PLI80ISI in place of PLI80 on the LINK command line.. it. u. Each. of the special link files (except FASTIO) disables certain a features. you invoke a DML command that attempts to process disabled feature, If then a command status of 34 results. MOBS. (C). COPYRIGHT. 1981,198'4. Micro. Data. Base Systems,.

(13) DMLCOMMANDFORMAT. VII.. U. oriented language that permits giK.ect invocation example for each DML command in of DML commands (see the record/direct NJDBS DMS Manual). The precise calling forms for áirect DML usage the A below. and are illustrated in the examples presented in Appendix É\.. PL/I is. a. Command. Status and Required. E£.c.Q.rg. Declarations. status variable. must. be. The. command. All. used in a PL/I commands The following declarations program: DML. externals. lanquage. declared to. be. must program are required. fixed. be. in. a. defined as PL/I host. dcl 0 0 0. definitions for all. external. DML. commands. to. be. used. in program. O 0 0. eO. fixed;. The. U. commands appear in are also furnished on the FNDMS.PLI conjunction with the PL/I %inc1ude. declarations for the external These. DML. Appendix declarations be used in This can file. file command. This is an alternative to explicitly specifying external definitions. It is accomplished with the following declarations: B.. %include. dcl eO. B.. 'FNDMS.PLI'. fixed;. Special The. Commands. only special and. are. SETPBF. (C). COPYRIGHT. ALTEOS.. commands that can be used in this These commands are not required.. environment. u 1981,1984. Micro. Data. Base Systems,. Inc.. VII-I.

(14) !. Command. Find. D.. 'FNDFJS.PLI'. %include. u. Examples. dcl varl char(5) var2 fixed binary(7) 0 * 0. eO eO. fmsk fmsk. = =. ('setl',addr(varl)); ('set5',addr(var2));. setl and set5 specification.. Here, DDL. E.. Get and Put %include. dcl. are. Command. of sets that have been. specified in. a. specified in. a. Examples. 'FNDMS.PLI'. fixed decimal. var. names. (7,2);. 0 0 0. eO. =. var eO. U. F.. = =. gfc('ytdearn',addr(var)); var + 1029.00 pfc('ytdearn',addr(var));. Assignment %include. dcl. Command. Examples. 'FNDé'lS.PLI'. fixed;. var e 0 0. var. eO. = =. 3;. smu('setl',addr(var));. 0 0 0 eO. som('setl,set2'); Here, setl and set2 are names of sets that DDL =. have. specification.. been. 'kaj. (C). COPYRIGHT. 1981,1984. Micro. Data. Base Systems,. VII-3.

(15) INTERACTIVE ADD-ONPACKAGES. VIII.. U. add-on packages be invoked as follows: MOBS. are. provided on. files.. COM. The packages. can. MDBS-CNV. A.. To. operatinq. invoke system. the. NIDBS.CNV interactive used: line is. the. program,. following. command. CNV. B.. MDBS-IDML Before. working disk. be using IDML, on the default. IDp1L.cct4,. Omitting. IDMLI.OVL,. the. command. To. operating. U. invoke system. that the following. IDML2.OVL,. has. IDML3.OVL. sure. drive:. IDML3.OVL,. effect. of. MDBS.IDML interactive line is used:. the. Elles reside on IDNIL5.OVL. IDML4.OVL,. disabling program,. the. a. IDP1L. the. DEFINE. following. command. IDML. The. alternative startup the The aná/or default line. file STARTUP. IE an alternative must have the name: startup file command name (seefile used the must be fully qualified is on line, Imust be followed by the number of B). If the -13 parameter is used, bytes being allocated. This number should exceed the minimum OMS data base buffer region during size displayed by MDBS.DDL DDL the Manual). example, of For (VI-B-4 to use initialization the startup information on the and allocate 2560 bytes, START.IDM file the operating system command line is: user. specify the name of an command -B parameter on this. optionally. can. it. it. 14DBS. IDML. If be. OMS. START.IDM. results, then the number of bytes should of insufficient room in memory results an IDML increased. If then theerrornumber of bytes should be reduced. with the -B option, a. command. -B2560. status of. 31. U (C). COPYRIGHT. 1981,1984. Micro. Data. Base Systems,.

(16) D.. bj. MDBS-DMU. invoke system. To. operating. MDBS.DMU interactive line is used:. the. program,. the. following. command. DNIU. E.. MDBS-RCV. used file name qualified file MDBS.RCV interactive A. command. log. line. with the within program,. is used:. a form of MOBS must be fully To invoke the (see I-B). the following operating system. RTL CP/M. RCV Ee. s9r9 t: mke Q. The F.. uí. log buffer. ñ£G£SSÁKY. kÁ£kgEs. before using. size in this environment. RCV.. is 128 bytes.. MDBS-CBRU To. operating. invoke system. the. Compact-Backup-Restore is used:. command. Utility,. CBRU. YJ. GJ. (C). COPYRIGHT. 1981,1984. Micro. Data. Base Systems,. Inc.. the. following.

(17) Appendix. \j. eO eO eO eO eO eO eO eO eO eO eO. eO eO. eO eO eO eO eO eO eO eO. nj. yj. eO eO eO eO eO eO eO eO eO eO eO eO eO eO eO eO eO eO eO eO eO eO eO eO eO eO eO eO eO eO eO eO eO eO eO. eO. = ALTEOS() = = = = = = CCU(addr(var)) = = = DBCLS() = DBCLSM'area') = DBENV(addr(var)) = DBOPN(addr(var)) = = DBSAVE() = DBSTAT(addr(var)) = DRC() = = = = = = = = = = = = = = FNC)('set') = = = = = = = = = GETC(addr(var)) = = = = = = = = GTC(addr(var)) = = = = = LGCPLX() = LGENDX() = = LGFLSH(). AMM('setl,set2,set3') AMO('setl,set2,set3') AOM('setl,set2,set3') AOO('setl,set2,set3') AUI(addr(var)) CRA('record,area',addr(var)) CRS('record',addr(var)). DBOPNA('area',addr(var)) DRM('set') DRO('set') FDRK('record',addr(var)) FFM('set') FFO('set') FFS(1'area'l) FLM('set') FLO('set') FMI('item,set',addr(var)) FMSK('set',addr(var)) FNM('set') FNMI('item,set',addr(var)) FNMSK('set',addr(var)) FNOI('item,set',addr(var)) FNOSK('set',addr(var)) FNS(I'area1) FOl('item,set',addr(var)) FOSk('set',addr,(var)) FPM('set') FPC)('set') FRK('record',addr(var)) GETM('set',addr(var)) GETO('set',addr(var)) GFC('item',addr(var)) GFM('item,set',addr(var)) GFO('item,set',addr(var)) GMC('set',addr(var)) GOC('set',addr(var)) GTM('set',addr(var)) GTO('set',addr(var)) 1MS('set') IOS('set') LGFILE(addr(var)) NOTE:. A. eO eO eO eO. eO eO eO eO eO eO eO eO eO eO. eO eO eO eO. eO eO eO eO eO eO. eO eO eO eO. eO eO. eO eO. eO eO. eO eO eO eO eO eO eO eO eO eO eO eO eO eO eO eO eO eO eO. MRTF(l'record'1) MRTP('record') MSF(I'set'1) MSP('set') PFC('item',addr(var)) PFM('item,set',addr(var)) PFO('item,set',addr(var)) pIFD(addr(var)) PUTM('set',addr(var)) PUTO('set',addr(var)) RMS('set') ROS('set') RSM('set') RSO('set') SCM('set') SCO('set'). SETPBF(addr(var),var) SMC('set') SME('set'). SM('setl,set2'). SMN('set') SMO('setl,set2') SMU('set',addr(var)) SOC('set') SOE('set') SOM('setl,set2') SON('set') SOO('setl,set2') SOU('set',addr(var)) SUM('set',addr(var)). SUO('set',addr(var)). TCT('record') TMN('set') TMT('record,set') TON('set') TOT('record,set'). XMM('setl,set2,set3') XMO('setl,set2,set3') eO XOM('setl,set2,set3') XOO('setl,set2,set3') an optional argument eO. II indicates. = LGMSG(addr(var)) = MAU(addr(var)) = MCC(addr(var)) = MCF() = MCP() = = = = = NCI() = = = = = PUTC(addr(var)) = = = = = = = = SCN() = = SCU(addr(var)) = = = = = = = = = = = = = = SUC(addr(var)) = = SUN(addr(var)) = = SUU(addr(var)) = TCN() = = = = = = TRABT() = TRBGN() = TRCOM() = TUN(addr(var)) = = = eO =.

(18) \J. Appendix B. External Declarations. ,j. nj (C). COPYRIGHT. 1981,1982,1983. Micro. Data. Base Systems,. Inc..

(19) Appendix. u. U. U. B. alteos returns (fixed), amm entry (char(26) var) returns (fixed), amo entry (char(26) var) returns (fixed), var) returns (fixed), aom (char(26) entry aoo entry (char(26) var) returns (fixed), aui entry (pointer) returns (fixed), ccu entry (pointer) returns (fixed), cra entry (char(l7), pointer) returns (fixed), crs entry (char(8), var, pointer) returns (fixed), dbcls returns (fixed), dbclsa entry (char(8) var) returns (fixed), dbenv entry (pointer) returns (fixed), dbopn entry (pointer) returns (fixed), dbopna entry (char(8) var, pointer) returns (fixed), dbsave returns (fixed), dbstat entry (pointer) returns (fixed), drc returns (fixed), drm entry (char(8) var) returns (fixed), dro entry (char(8) var) returns (fixed), fdrk entry (char(8) var, pointer) returns (fixed), ffm entry (char(8) var) returns (fixed), ffo entry (char(8) var) returns (fixed), entry (char(8) var) returns (fixed), ffs f1m entry (char(8) var) returns (fixed), f1o entry (char(8) var) returns (fixed), fmi entry (char(l7) var, pointer) returns (fixed), fmsk entry (char(8) var, pointer) returns (fixed), fnm entry (char(8) var) returns (fixed), fnmi entry (char(l7) var, pointer) returns (fixed), fnmsk entry (char(8) var, pointer) returns (fixed), fno entry (char(8) var) returns (fixed), fnoi entry (char(l7) var, eointer) returns (fixed), fnosk entry (char(8) var, pointer) returns (fixed), fns entry (char(8) var) returns (fixed), fol entry (char(l7) var, pointer) returns (fixed), fosk entry (char(8) var, pointer) returns (fixed), fpm entry (char(8) var) returns (fixed), fpo entry (char(8) var) returns (fixed), frk entry (char(8) var, pointer) returns (fixed), getc entry (pointer) returns (fixed), getm entry (char(8) var, pointer) returns (fixed), geto entry (char(8) var, pointer), returns (fixed), gfc entry (char(8) var, pointer) returns (fixed), gfm entry (char(l7) var, pointer) returns (fixed), gfo entry (char(17) var, pointer) returns (fixed), gnic entry (char(8) var, pointer) returns (fixed), goc entry (char(8) var, pointer) returns (fixed), gtc entry (pointer) returns (fixed), gtm entry (char(8) var, eointer) returns (fixed), gto entry (char(8) var, pointer) returns (fixed), ims entry (char(8) var) returns (fixed), los entry (char(8) var) returns (fixed), lgcplx returns (fixed), lgendx returns (fixed), (pointer) returns (fixed), lgfile entry lgflsh returns (fixed),.

(20) DOCUMENTATION. u. MDBS. COMMENT. FORM. Title: _. Document. welcome and appreciate all comments and suggestions Use this help us to improve our manuals and products. views manual. concerning this express your. 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, or in a separate to letter addressed Requests support division. attention of the technical published materials should be addressed to the attention of marketing division.. to tc. the. for. the. Sender:. (position). (name). (telephone). (company). rj. (address). (city, state, zip) COMMENTS:. Areas of comment are general presentation, format, organization, completeness, a comment applies to etc. clarity, accuracy, specific page or pages, please cite the page number(s).. If. nj Continue. on. additional. pages,. as needed.. Thank you. for your. response.. a.

(21)