1 1 - M T S D I S T R I B U T I O N 4.0 + _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ ___ 0 August 1977 0 General Notes - Distribution 4.0 consists of 4 tapes at 6250 bpi or 10 tapes at 1600 bpi. Included in these are IBM TSS VAM2 format dump/restore tapes for a single 3330-1 pack MTS system designed to be used to get started (for new installations) or for conversion (for old installations). Instructions for these procedures are given in items 10003 and 10004 of the distribution documentation. 0 The remaining tapes (3 at 6250, 8 at 1600) contain source, object, command, data, and print files, and must be read using the *FS program. These tapes are volume label only (VLO) tapes. 0 Throughout the distribution, reference is made to the components of the distribution. Generally these references are made by a 3- or 4-digit component number, usually followed by a slash and a sub-component number. For example, the MTS accounting system has been assigned component number 104. However, the accounting system actually has many "pieces" and so it consists of components 104/1 through 104/110. 0 Component numbers 1 through 655 and 1000 through 1028 are compatible with the numbers used in distributions 3.0, 3.1 and 3.2; additional numbers are new components, or in some cases, old components which have been grouped under new numbers. Component numbers are assigned by each MTS installation in ranges. The number of a component doesn't necessarily indicate which installation is responsible for its maintenance (see the SHARE code for that), only which installation originally assigned the number. The installation assignment ranges are as follows: 0 Range SHARE Installation Name 0 0001-0999 UM University of Michigan 1000-1199 UBC University of British Columbia 2000-2199 UNE University of Newcastle upon Tyne 3000-3199 UQV University of Alberta 4000-4199 WSU Wayne State University 4200-4399 RPI Rensselaer Polytechnic Institute 4400-4599 SFU Simon Fraser University 0 The FS tapes are generated by the MTS *FS program based on information contained in a data file (known as a driver file), each line of which describes a component (or sub-component) of the system. Each component has a name, sub-name, SHARE installation code, type (source, object, MTS commands, etc.), a location (where *FS is to obtain it from), a pointer to descriptive comments (in another file), a contact person for the component at the installation principally responsible for its 1 2 - maintenance, and a locally responsible person. In the D4.0 driver file, the local persons, when given, are UM people for non-UM components -- each installation should fill in its own local names for components assigned to other installations. In this way a printout may be produced (using the *DEDIT program) for each staff member showing his or her subset of the D4.0 driver file information. 0 As *FS generated the D4.0 tapes, it added additional information to each line in the driver file including the distribution tape name and file number on which it wrote the component (tapes are named D4Tn), the FS name, information about the file size or tape blocking information if the component came from a non-FS tape, and the time and date when the file was saved. Components may be restored from these tapes using *FS either by reference to the FS name or to the file number. 0 Two versions of the distribution driver file are provided: 461/6 for the 6250 bpi tapes, and 461/7 for the 1600 bpi tapes. A printed copy of the appropriate driver file (6250 or 1600) is included in the distribution. Additional copies of this listing may be printed using the LIST command in *DEDIT. Note: the two versions of the driver file are identical except for the output tape names and file numbers since these are different at 6250 and 1600 bpi. Both driver files (MTS:D4DRIVER and MTS:D4DRIVER1600) are on the dump/restore pack along with the comment file (MTS:D4COMM). 0 A printed copy of the appropriate driver file index (6250 or 1600) is also included. Additional copies of the index may be printed by copying the appropriate file to *PRINT*. The 6250 index is component 461/14 (MTS:D4INDEX on the test pack); the 1600 index is component 461/15 (MTS:D4INDEX1600 on the test pack). 0 The tapes are as follows: 0 6250 bpi copy: + ____ ___ _____ 0 D4T1 *FS Format 1327 files -- components 001/1 to 498/85 except for 038/14, 387/30, 461/6 to 461/8, 461/11, 461/14, 461/15, and 468/3 to 468/5. 0 D4T2 *FS Format 1206 files -- components 500/1 to 672/31. 0 D4T3 *FS Format 777 files -- components 673/1 to 4000/5 plus 038/14, 387/30, 461/6 to 461/8, 461/11, 461/14, 461/15, and 468/3 to 468/5. 0 DUMP/RESTORE 1 IBM TSS VAM2 Dump/Restore Tape Contains: 1. TSS DASDI (IPLable deck) 2. TSS DUMP/RESTORE (IPLable deck) 1 3 - 3. TSS VAM2 UTILITIES (IPLable deck) tape mark 4. Dump/Restore data tape mark 5. Dump/Restore trailer tape mark tape mark 0 1600 bpi copy: + ____ ___ _____ 0 D4T1 *FS Format 487 files -- components 001/1 to 163/20 except for 038/14. 0 D4T2 *FS Format 414 files -- components 164/1 to 360/2. 0 D4T3 *FS Format 426 files -- components 387/1 to 498/85 except for 387/30, 461/6 to 461/8, 461/11, 461/14, 461/15, and 468/3 to 468/5. 0 D4T4 *FS Format 388 files -- components 500/1 to 549/2. 0 D4T5 *FS Format 483 files -- components 551/1 to 619/28. 0 D4T6 *FS Format 335 files -- components 620/1 to 672/31. 0 D4T7 *FS Format 457 files -- components 673/1 to 1032/17. 0 D4T8 *FS Format 320 files -- components 1033/1 to 4000/5 plus 038/14, 387/30, 461/6 to 461/8, 461/11, 461/14, 461/15, and 468/3 to 468/5. 0 DUMP/RESTORE 1 IBM TSS VAM2 Dump/Restore Tape #1 (Same format as 6250 bpi DUMP/RESTORE tape -- see above.) 0 DUMP/RESTORE 2 IBM TSS VAM2 Dump/Restore Tape #2 Contains: tape mark 1. Dump/Restore data tape mark 2. Dump/Restore trailer tape mark tape mark 1 4 - USE OF TSS DASDI AND DUMP/RESTORE + ___ __ ___ _____ ___ ____________ 0 The IBM TSS (Release 2.0) DASDI, DUMP/RESTORE, and VAM2 UTILITIES programs are at the beginning of the distributed dump/restore tapes. Printed copies of the writeups for DASDI and DUMP/RESTORE are included in the distribution as item 10010. 0 The MTS DASDI program (598) (not stand-alone) may be used (if MTS is available) to initialize a pack in VAM2 format; use of this program is described in the MTS Operator's Manual (item 10013). The TSS DASDI (stand-alone) on the dump/restore tapes will initialize a pack in either VAM2 or SAM format; it has been modified at UM to accept device addresses as high as FFF. IPLing the dump/restore tape once will load TSS DASDI. 0 MTS file system volumes (such as the distributed dump/restore pack) must be VAM2 format and are normally labeled MTS001, MTS002, etc. The public volume number for the distributed pack must be 1. MTS packs should be VOLTYPE PUBLIC and the PAT should be placed on a cylinder boundary (the PATD STRTADR parameter should be evenly divisable by 57) near the middle of the pack. The following are 0 The following TSS DASDI control cards are for a 3330-1 with volume label MTS001. To DASDI a 3330-11, use TODEV=333B (instead of 3330) and STRTADR=23199 (instead of 11685). 0 JOB INITIALIZE 3330-1 AS MTS001 MSG TODEV=1052,TOADDR=23F DADEF TODEV=3330,TOADDR=340,FORMTYPE=VAM2, X VOLID=SCRATCH,VOLTYPE=PUBLIC,PUBVOLNO=1 VLD NEWVOLID=MTS001 PATD STRTADR=11685 END LASTCARD 0 If a paging disk is to be used, it should also be initialized as a VAM2 pack with VOLTYPE=PAGING and a volume label of PAG001. No PUBVOLNO keyword is required in this case. 0 The HASP spooling pack(s) should be initialized as SAM pack(s) with volume label(s) SPOOL1, SPOOL2, etc. The following are sample control cards (which have not been tried) for a HASP + ___ DASDI: 0 JOB INITIALIZE 3330 AS SPOOL1 MSG TODEV=1052,TOADDR=23F DADEF TODEV=3330,TOADDR=340,FORMTYPE=SAM, X VOLID=SCRATCH,FLAGTEST=NO VLD NEWVOLID=SPOOL1 VTOCD STRTADR=1,EXTENT=1 END LASTCARD 1 5 - To load TSS DUMP/RESTORE, IPL from the distributed dump/restore tape and, when the tape stops, IPL again. The following are sample control cards for restoring the distributed dump/restore tape to a 3330-1 which has been initialized with the label MTS001. To restore to a 3330-11, use TODEV=333B (instead of 3330). 0 JOB RESTORE MTS001 FROM TAPE MSG TODEV=1052,TOADDR=23F RESTORE FROMDEV=2400,FROMADDR=581,TODEV=3330, X TOADDR=340,FORMTYPE=VAM2,VOLID=MTS001, X LABEL=RETAIN END 0 After restoring the distributed dump/restore pack, you are ready to proceed with the installation of MTS. We have provided two writeups to assist in doing this, one for new installations (item 10003) and another for installations which have previously used MTS (item 10004). 1 6 - LISTINGS IN THE DISTRIBUTION + ________ __ ___ ____________ - Listings have been included on the FS tapes for the most important components of the system. - Comp. No. Component Name 0 0041/5 GETSPACE/FREESPAC (370 listing) 0041/6 (360 listing) 0042/6 MTS (370 listing) 0042/7 (360 listing) 0045/7 SUPERVISOR (370 listing) 0045/8 (360 listing) 0046/7 CONFIG (370 listing) 0046/8 (360 listing) 0198/5 GUINFO/CUINFO (370 listing) 0198/6 (360 listing) 0354/5 LLXU (370 listing) 0354/6 (360 listing) 0387/14 HASP 0464/5 PLIMIT (370 listing) 0464/6 (360 listing) 0539/5 TIMNTRP (370 listing) 0539/6 (360 listing) 0578/5 RSF (370 listing) 0578/6 (360 listing) 0635/5 FSUB (370 listing) 0635/6 (360 listing) 0636/5 CMDS (370 listing) 0636/6 (360 listing) 0637/5 DSRS (370 listing) 0637/6 (360 listing) 0638/5 USUB (370 listing) 0638/6 (360 listing) 0639/5 DSRI (370 listing) 0639/6 (360 listing) 4000/4 GATE (370 listing) 4000/5 (360 listing) 1 7 - PATCHING THE SYSTEM + ________ ___ ______ - Patching shared memory: + ________ ______ _______ 0 Find out where the deck to be patched is loaded by checking a current map, by checking the file SEG2:S2MAP, or by using the LOADINFO CLS (enter the MTS command "#CLS W009:I" from a privileged user id, i.e., an id that can set PROT=OFF). 0 Use the System Status Routine (SSRTN) command 0 DISPLAY loc[+disp[+disp ...]] [n] 0 to display memory and the SSRTN command 0 MODIFY loc[+disp[+disp ...]] value[[,]value ...] 0 to change it. For example 0 DISPLAY 218500+6DBA 0 MODIFY 218500+6DBA 47F0 0 These SSRTN commands are legal from the 3270 operator's console when prefixed with a slash (/), as input to the JOBS job which may be run from any operator's console, or as input to the $SYSTEMSTATUS command when signed on using a privileged MTS user id. For a complete description of these and the other privileged SSRTN commands see the MTS Operator's Manual. 0 SDS may also be used to modify shared memory when used from a privileged id. In addition, the supervisor commands DIS and MOD may be used to display and modify routines loaded into unpaged memory (segment 0), but these commands are not legal when issued from a 3270 operator's console. 0 The IPLREADER has commands which allow a system to be patched at IPL time, see the IPLREADER description (item 10007) for more information. - Patching the System Object Deck: + ________ ___ ______ ______ _____ 0 Using RAMROD (MTS:RAMROD), CREATE a new system from the + ______ current system or GET a previously created system which has + ___ not yet been made current, but which will become the current system after the patches are made. Item 10008 contains a description of the use of RAMROD. Enter enough comments so that other people can tell what you've been up to. You will have been prompted for comments if you created a new system, otherwise you may use the ANNOTATE + ________ command to add comments. 0 Add REP cards to the deck(s) using the PATCH command. + _____ 1 8 - RENAME the new system with the correct version name and make it CURRENT. + _______ 0 For example: 0 # run mts:ramrod # EXECUTION BEGINS Using file "MTS:ROD" Proceed. list current UG117 created from UG057 23:06:01 08-11-77 08-11 23:00 REPLACED UMMPS TO FIX BUG IN GETSTK/SETSTK create newsys from ug117 Enter comments : ? 08-24 21:05 Just an example ? Done. patch taskstat Address Esdid Text : ? 30 01 58F0 just an example patch ? Enter comments : ? 08-24 just an example patch ? REP 000030 0158F0 just an example patch 21:15:25 08-24 OK ? ok Done. rename newsys ug247 "NEWSYS" is a system. ** RENAME system "NEWSYS" as "UG247" : OK ? ok Done. current There are 3 IPL files with prefix "*IPL. " Loading system "UG247" LOAD: Resident: 1000-27D80 UMLOAD Psect: 58000 Pageable: Contents of IPL file "*IPL.2": UL177 ENTRY=26E08 PSECT=100008 VIRTUAL=58000...ACD90 WRITTEN BY ID MTA. AT 06:24:38 07-17-77 COM 07-14 20:00 CHANGED CONFIG.CARD TO GIVE MORE SPACE TO COM 07-14 21:59 REPLACE TASKSSTAT, MINOR CHANGES. COM 07-15 13:35 NEW TABLES TO ADD MORE JOB TABLES. COM 07-17 06:20 REPLACED PDP WITH WHAT I HOPE IS THE D4.0 ** Write system "UG247" to IPL file "*IPL.2": OK ? ok System "UG247" has been written to IPL file "*IPL.2" IPL file stacked has been pushed. System "UG247" is now the current system. "UG247" : Released. System "UG247" has been Frozen. Done. stop # EXECUTION TERMINATED - 1 9 - Remember to Change the Source: + ________ __ ______ ___ _______ 0 It seems almost silly to mention this, but .... - Patching Decks Loaded by PISTLE: + ________ _____ ______ __ _______ 0 Decks loaded into shared VM by PISTLE (the post IPL system loader) can be patched in memory as described above. REP cards are added to the files from which PISTLE loads the object. It is a good idea to use PISTLE without specifying PAR=NOTEST to make sure the patched version will load. 0 PISTLE can also be used to load complete new versions of a deck into shared VM so long as all references to the module are made using a low core symbol table rather than external references that are already resolved, i.e., if the IPL option is not used to load it. PISTLE allows the automatic replacement of symbols in the low core symbol table LCSYMBOL, other low core symbol tables must be patched by hand. 1 10 - CHANGES TO COPY SECTIONS AND MACROS + _______ __ ____ ________ ___ ______ - Since the previous distribution, many copy sections have been moved into macro libraries. The following list should help you figure out where things are. Most (but not all) of the copy sections used by MTS have become macros in COPY:MTS.MACROS or COPY:FILE.MACROS. There are many more macros which are not listed below, but which are available in these two files. There are also many other copy sections and libraries which are kept in files belonging to the user id COPY. - Macro Name in COPY:MTS.MACROS Old_Name Older_Name + _______________ ___ ____ _____ ____ 0 CLSAREA COPY:CLSAREA MTS:CLSAREA CLSPLAN COPY:CLSPLAN MTS:CLSPLAN CLSTV COPY:CLSVECTOR MTS:CLSVECTOR FCBDSCT COPY:FCBDSECT MTS:FCBDSECT FDBDCT COPY:FDUBDSECT MTS:FDUBDSECT LXDCT COPY:MTS.LLXUDEFS MTS:LLXUDEFS MTSCTAB COPY:MTS.CONTAB MTS:CONTAB MTSEQU COPY:MTS.EQU MTS:MTS.EQU MTSEQU2 COPY:MTS.EQU2 MTS:MTS.EQU2 MTSTV COPY:MTS.TV --- RHTABLE COPY:MTS.RHTABLE MTS:MTS.RHTABLE SUBTV COPY:STANDARDTV MTS:STANDARDTV THEDSECT COPY:MTS.DSECT MTS:MTS.DSECT UBCDSECT COPY:UBCDSECTS --- WOPTRDCT COPY:WOPTRDSECT MTS:WOPTRDSECT - Macro Name in COPY:FILE.MACROS Old Name Older Name + ________________ ___ ____ _____ ____ 0 CATEQU COPY:CATEQU W045:NEWCATEQU DSCBDSCT COPY:DSCBDCT W045:DSCBDSCT DSKDSCT COPY:DSKDSCT W045:DSKDSCT FCBEQU COPY:FCBEQU W045:NEWFCBEQU ICEQU COPY:ICEQU W045:ICEQU PATEQU COPY:PATEQU W045:PATEQU - Current Name Old Name + _______ ____ ___ ____ 0 COPY:JOBSTA DBS:JOBSTA COPY:LLMPSEQU *LLMPSEQU COPY:MTS.MACROS MTS:MACROS COPY:PCBDSECT *PCBDSECT COPY:PSA MTA:PSA COPY:STATDSECT MTA:STATDSECT 1 11 - PRINTED DOCUMENTATION IN THE DISTRIBUTION + _______ _____________ __ ___ ____________ - The following lists all of the paper-copy documentation included in D4.0. An asterisk (*) in front of an item in the list below indicates that only a paper copy was shipped, otherwise there is a machine readable copy on the tapes and listed in the driver file. In addition, there are many more writeups on the tapes for which paper copies have not been shipped. Using the editor on the driver file to match for the letters "W" or "P" in column 45 will produce a complete list of all the machine readable documentation. 0 Since some items on the list below are not distribution components and do not appear on the FS tapes and hence don't have a component number, another number (the one in front of the entry below) was produced. This other number also facilitates the packing list. The component number for all items on tapes is given in parentheses after the items in the list. The paper copy that is sent with this distribution is stamped with both numbers (if applicable). [To make them readily distinguishable, distribution numbers are always given with a slash and are less than 10000; the other numbers start with 10000 and go up.] 0 No printed copies of the volumes of the UM MTS Manual have been included with the initial shipments of this distribution, but the TEXT360 master and print files are included on the FS tapes. If your installation needs a printed copy of any of the MTS volumes, send a request to: 0 The University of Michigan Computing Center ATTN: W. Scott Gerstenberger 1075 Beal Avenue Ann Arbor, MI 48109 USA 0 The audio tapes of the 33 system lectures which were given for the UM staff during the spring and summer of 1973 have not been updated and are not included in the distribution, but are available on request. Finally the documentation for the QUIC (584) and KWIC (583) programs has not been included, but is available on request. - Distribution Documentation + ____________ _____________ 0 This is documentation concerned with the installation of this distribution. 10000. General Notes, what you are reading now. (461/11) 10001A and 10001B. Driver file listing (LIST command to *DEDIT). 10002A and 10002B. Driver file index; a listing sorted by component names which serves as an index for 10001. (461/14 and 461/15) 1 12 - 10003. Installation instructions for New Installations. (461/9) 10004. Installation instructions for Old Installations. (461/10) 10005. Description of D4.0 System Object Deck (468/6) 10006. Tables writeup (004/3) 10007. Documentation for the IPLREADER and friends. (1021/9) 10008. Documentation for the RAMROD System Maintenance Utility. (1019/9) 10009. DECK GEN instructions (004/7) * 10010. TSS DASDI and DUMP/RESTORE instructions. * 10011. UM Machine Configuration Chart. - General + _______ 0 10012. Message Manual (555/5) - Operations + __________ 0 10013. MTS Operator's Manual (592) 10014. HASP Operator's Guide (387/26) * 10015. HASP Remote 360/20 Operator's Guide * 10016. HASP Remote 360/non-20 Operator's Guide * 10017. HASP Remote 1130/1800 Operator's Guide * 10018. HASP Remote System/3 Operator's Guide * 10019. HASP 2780 Remote Workstation Operator's Guide - Installation Descriptions (Internals) + ____________ ____________ ___________ 0 10020. HASP notes. (387/30) * 10021. SDS Storage Allocation. - How-To-Use Information + __________ ___________ 0 For systems or administrative users: 10022. Printing jobdumps. (400/13) * 10023. Modifying *LIBRARY. * 10024. Specifying keywords for EREP/370 (IFCEREP0) 0 For general user: 10025. List of current CCMEMOs (461/16) and the CCMEMOs themselves. * 10026. Computing Center Newsletter (v5n6 through v7n14) 10027. Computing Center Publications (711/1) 1 13 - DESCRIPTION OF THE DRIVER FILE LISTING + ___________ __ ___ ______ ____ _______ - 0 The following is a description of the driver file listing produced by the LIST command in *DEDIT (461/1). A printed copy of the appropriate listing (for 6250 or 1600 bpi) is included in the distribution. For each component (or sub-component), two lines of output are printed, followed by any comments associated with the component. - 0 LINE 1 + ____ _ 0 Num - component number and sub-number (if any) + ___ Component_Name - name of the component + _________ ____ Sub-name - name (if any) of the sub-component + ________ Type - component type as follows: + ____ B - binary (non-360/370) object C - MTS commands D - data L - listing M - messages O - object (OC=cards, OE=link-edited, OL=library) P - printed output (PF=FORMAT, PT=TEXT360, PX=TEXTFORM) S - source code (SA=assembler, SF=FORTRAN, SG=GOM, SP=PL/I, SS=SNOBOL4, SM=assembler macros, SX=XPL, S3=PL360, S6=Algol68) U - update deck (UU=*UPDATE, UI=*IEBUPDAT, UE=$EDIT commands) W - writeup input (WF=FORMAT, WT=TEXT360, WX=TEXTFORM) G - "goodness" code (G=good, O=OK, S=shakey (has bugs), + _ B=bad (needs rewrite)) Seq_ID - sequence id applied to component as it was saved + ___ __ S - save control (blank means normal, "#" means not + _ distributed, "@" means information incomplete, "=" means temporary hold, ">" means very large component) Location - file or tape from which the component was + ________ obtained. For tapes, the first parameter is the rack number, the second and third are the volume name (if labeled) and the tape id (if different from the volume name), then follow keywords for the label type, blocking format, and DSNAME (if any). File - the file number if the component was obtained from + ____ tape (optional for labeled or *FS tapes) 1 14 - LINE 2 + ____ _ 0 Tape - name of output tape on which the component was saved + ____ File - *FS file number on output tape + ____ Ver - *FS version number assigned to component as it was + ___ saved Ftype - the file type (LINE or SEQ) + _____ LRECL - the maximum record length of the component + _____ Size - the size of the component (in pages if the DevT + ____ field is PAGE, in tracks if DISK) DevT - the device type from which the component was + ____ obtained (PAGE for non-FS tapes and files, DISK for items obtained from older (before the page-formatted file system) *FS tapes) SHARE - installation SHARE code for the installation + _____ responsible for maintenance Person - the person responsible for the component at the + ______ installation given in the SHARE field Local Per - the person responsible for the component at the + _____ ___ local installation Date and Time - date and time component was saved + ____ ____ 1 15 - PEOPLE LIST FOR THE UNIVERSITY OF MICHIGAN COMPUTING CENTER + ______ ____ ___ ___ __________ __ ________ _________ ______ - The following is a list of UM Computing Center people whose names appear in the "person" field of the driver file listing. An asterisk (*) before a name means that the phone number is (313) 764-9595, otherwise it is (313) 764-2121. All correspondence should be addressed to: 0 The University of Michigan Computing Center 1075 Beal Avenue Ann Arbor, MI 48109 USA - BODWIN Bodwin, James M. BRILL Brill, Robert C. * DWB Boettner, Donald W. * EMERY Emery, Allan R. * ENGLE Engle, Charles F. FLANIGAN Flanigan, Larry K. FRONCZAK Fronczak, Edward J. GERSCH Gersch, Joseph E. GOODRICH Goodrich, Andrew C. H YOUNG Young, Howard B. HANSEN Hansen, James H. HARDING Harding, Leonard J. HELFFRICH Helffrich, George R. * K YOUNG Young, Kathleen A. * LIFT Lift, Gail H. LUBBERS Lubbers, Clark E. MANUAL (see SALISBURY) MERIT (see OGDEN) * MTA Alexander, Michael T. OGDEN Ogden, Jeffrey C. * PIRKOLA Pirkola, Gary C. * SALISBURY Salisbury, Richard A. SHERRY Sherry, Patrick M. STERKEN Sterken, James J. SWARTZ Swartz, Fred G. SWEET Sweet, Elizabeth A. TIFFANY Tiffany, L. Bernard * WSG Gerstenberger, W. Scott - Correspondence related to the administration of the UM Computing Center should be sent to the director: 0 Dr. Robert C. F. Bartels, Director The University of Michigan Computing Center 1075 Beal Avenue Ann Arbor, MI 48109 0 Telephone (313) 764-9572 1 16 - DISTRIBUTION 4.0 INITIAL MAILING LIST + ____________ ___ _______ _______ ____ - The following is a list of persons to whom the initial shipment of MTS Distribution 4.0 has been sent: - UBC Computing Centre 1600 bpi ATTN: John Hogg University of British Columbia Vancouver, B. C. V6T 1W5 CANADA 0 UNE Computing Laboratory 1600 bpi ATTN: Program Librarian The University Newcastle upon Tyne NE1 7RU ENGLAND 0 UQV Computing Services 6250 bpi ATTN: John Stasiuk The University of Alberta Edmonton, Alberta T6G 2H1 CANADA 0 WSU Computing and Data Processing 1600 bpi ATTN: Henry Bodzin Wayne State University Detroit, MI 48202 0 RPI Office of Computer Services 1600 bpi ATTN: Wilson Dillaway Rensselaer Polytechnic Institute Troy, NY 12181 0 SFU Computing Centre 6250 bpi ATTN: Charlie Benet Simon Fraser University Burnaby, B. C. V5A 1S6 CANADA 0 AMD Amdahl Corporation 6250 bpi ATTN: Bill Ehrman 1250 East Arques Avenue Sunnyvale, CA 94086 0 VIK Viktors Berstis 6250 bpi 366 Elton Hills Drive Rochester, MN 55901