1 1 - INSTALLATION INSTRUCTIONS FOR OLD INSTALLATIONS + ____________ ____________ ___ ___ _____________ 0 May 1980 - MTS distribution 4.3 uses the VAMX disk format rather than the IBM TSS VAM2 format employed in previous distributions. With VAMX, the disk address format is changed to realign the boundary between the public volume number and the relative page number (on a volume) so that the low-order 20 bits (instead of 16) are now used for the page number and the next higher 8 bits (instead of 12) are now used for the public volume number. The high-order 4 bits continue to be used for the segment number within a page (in catalog page addresses) and the DSCB number within a page (for DSCB addresses). The effect of the change to VAMX is that MTS can now support more than 65K pages per volume as is required for 3350 disks. Note that public volume numbers are now limited to the range 1-255. 0 Component 790 contains two programs which should be used to convert existing VAM2 packs to VAMX format, and which also convert the old VAMX format to the new one. The "old" VAMX format refers to the scheme, used at several MTS installations, whereby VAM2 and VAMX packs could be intermixed in one system. The only difference between this "old" and "new" style is that VAMX disk addresses formerly had the X'08000000' bit set in them, whereas the new ones do not. This constrains the D4.3 disk configuration to being solely VAMX. 0 The following steps give the basic procedure to be followed to install this distribution at installations which are currently running the previously distributed system. At installations where substantial changes have been made to the that system or where it is not desired that all of this distribution be installed at once, this procedure will have to be modified accordingly. 0 1. Restore DASDI and DISKCOPY to your current VAM2 system from the D4.3 FS tapes. You should consult the appropriate distribution driver file index (item 10067A or 10067B) for the object files for the components DASDI (598/2) and DISKCOPY (724/3). The index will indicate on which tape each is located and what the file numbers are. (DO NOT use component 724/2 since it will not work in pre- D4.3 systems and DO NOT try to use the IBM TSS DUMP/RESTORE program previously distributed since it will not generate VAMX relocation entries if it has to relocate any pages while restoring the D4.3 pack.) 0 2. Use this DASDI to initialize a VAMX disk pack as public volume 1 with a unique volume name; MTS431 would be a good choice. See the D4.3 General Notes for instructions on using FILE:DASDI. The following commands illustrate the use of this program: 1 2 - RUN D4.3DASDI Dxxx MTS431 VX 1 IPL SLOW $ENDFILE - where "Dxxx" is the device name of the disk to be initialized and "MTS431" is the volume name to be used for the disk pack. 0 3. Use DISKCOPY to restore the D4.3 system from the distributed VAMX dump/restore tape(s). You should specify the IPL option, but SWAP isn't necessary. You may wish to specify the SLOW option to lessen the interference with your normal operation. See the D4.3 General Notes for information on running DISKCOPY. The following commands illustrate the use of this program: - RUN D4.3DISKCOPY TAPE >Tnnn DISK Dxxx MTS431 IPL SLOW $ENDFILE - where >Tnnn is the device name on which the (first) D4.3 VAMX dump/restore tape is mounted. If you received the 1600 bpi distribution, you will be prompted to enter a second tape device name when DISKCOPY is ready for the second tape. 0 4. You will need a new set of TABLES for your D4.3 system. If you maintain your TABLES in assembly language form, you should consult the D4.3 TABLES description (item 10071). Note that in D4.3, 2305s must be named FF00-07, FF08-0F, FF10-17, etc. Be sure to use the D4.3 version of COPY:FILE.MACROS when you assemble your new version. This version of TABLES should only contain one disk volume, MTS431. 0 If you wish to use DECKGEN to build your D4.3 TABLES, IPL from the D4.3 test pack. This will probably put the machine in wait state (unless you have a 3066, 3270, or 1052-compatable device at address 740). To get the IPLREADER to talk to you, press "request" on a 1052 or "enter" on a 3066 or 3270 (i.e., cause an attention interrupt). When it asks if you want to run the current system, reply "NO" and enter the commands: - LOAD NAME=*IPL.DECKGEN START 1 3 - See the DECKGEN writeup (item 10073) for information on how to proceed from here. Since DECKGEN was loaded by the IPLREADER (instead of from tape) and therefore is told where the console is, it is not necessary to give an attention interrupt on the console to wake it up. Again, you should note that the MTS naming convention used for IBM 2305 fixed head files has been changed since D4.2. Be sure that the names you use for your 2305s are FF00-07, FF08-0F, etc. Make sure that you only include one public volume, MTS431. 0 5. You should now IPL from the D4.3 pack and again reply "NO" when asked if you want the current system. This time enter the commands: - LOAD NAME=*IPL.D4.3 REPLACE TABLES FROM xxx (Reply to the prompt for a printer address for a map) START - where xxx is the address of the tape written by DECKGEN + ___ (or containing the object deck for your assembled TABLES). D4.3 should now be running. 0 6. When initialization finishes, you should run RAMROD and create a new system from the D4.3SYS system, replace the deck TABLES.DUMMY in that new system with your own TABLES, rename TABLES.DUMMY to be TABLES, and delete the decks SEG0.NCA and SEG1.NCA. Having made these changes, you should then make this new system current. 0 7. Use this pack to get the new version of MTS working to your satisfaction. This will require making any local modifications to the resident system in the RAMROD file on the pack. This pack contains almost all of the public and semi-public files, but not all of the utility programs you may want. If additional programs are needed, move them from your production packs to the test pack using FM (1020) on your production system. Be sure to use the D4.3 version of FM and a private copy of the D4.3 file routines when doing this. 0 Because at UM we converted directly from VAM2 to D4.3 VAMX pack format, the programs which we actually used to perform the conversion did only that, i.e., they were not used to convert any old style VAMX packs. However, since several MTS installations are already using a mixture of VAM2 and old-style VAMX, D4.3 includes two versions of each of the two conversion programs: (1) the versions used here at UM to do the VAM2 to VAMX conversion and (2) those same programs with changes made to + ____ _______ ____ effect the old to new VAMX conversion in addition to the VAM2 to VAMX conversion. Whereas we can guarantee the operation of the versions we used for our conversion, the changed versions of the programs have never been used to perform an old to new style 1 4 - VAMX conversion, and so are somewhat suspect. They have been + ____ debugged, and have been verified to do nothing to packs already in the new VAMX format, and to properly convert fragments of old style VAMX packs. In addition, they have been used to convert a VAM2 pack to VAMX. 0 As mentioned above, there are two conversion programs: a PAT/DSCB conversion program (CONVV2VX) and a catalog conversion program (CONV.CAT). The PAT/DSCB conversion program converts the following items on a pack to the new VAMX format: (1) the label; (2) the relocation entries in the PAT; (3) the disk addresses in the DSCBs (file page addresses and DSCB type F links). The catalog conversion program converts the following items to the new VAMX format: (1) the catalog pointer in the label of PVN 1; (2) the segment allocation map in the first page of each catalog extent (each *MASTER.CATALOGn file); (3) the DSCB address contained in the first page of each catalog extent; (4) the backpointer to the extent header in each catalog page; (5) the self-ID in each catalog page; (6) the catalog addresses in each master index entry; (7) the catalog links in each file and sharing descriptor; (8) the DSCB address for the file in each file descriptor. Both programs are restartable after an unsuccessful partial run. 0 The following steps should be followed to convert your public volumes from VAM2 and/or old style VAMX to D4.3 VAMX. 0 8. On your regular system, run your current version of CHKVTOC to verify the correctness of all your public volumes' VTOC. Also run VNTD to verify the correctness of your catalog. This is just to ensure that neither of the conversion programs take any unexpected action if there is some inconsistency in the structures they change on the disk packs. 0 9. Make a copy of all your packs on tape using either the IBM TSS DUMP/RESTORE utility distributed with D4.2 or the MTS D4.3 DISKCOPY program (724/2) running from the MTS431 + _______ ____ ___ ______ system. These copies are for insurance in case of some + ______ disaster during the conversion. 0 10. From the MTS431 system, run the PAT/DSCB conversion program (CONVV2VX) along with your current (pre-D4.3) file routines and a complete set of D4.2 TABLES, i.e., TABLES which have DSKTAB entries for PVNs 1 through your maximum public volume number with the correct volume names for your public volumes. The PAT/DSCB conversion program will prompt for a public volume number for a pack to convert. It will print out the label for the volume and request confirmation for the conversion; reply "OK" to proceed. (If converting a VAM2 style pack, the program will complain about "# PAT BYTES = X'4040' LOOKS SUSPICIOUS". This is normal and you may respond affirmatively to the prompt whether to proceed. If you get this message with an old-style VAMX format pack, you should investigate further.) Depending on whether the pack being converted is 1 5 - VAM2 or VAMX, you will receive a message of either "CONVERTING LABEL, PAT, AND DSCB'S TO VX FORMAT" or "LABEL IS NOT IN V2 FORMAT". If you get the latter message, confirm the prompt if the pack is in the old VAMX format, and the conversion will proceed. (If you get the latter prompt for a VAM2 pack, something is probably wrong and should be investigated.) If you get the message "PAT BYTE COUNT ON MTSxxx IS nnn AND SHOULD BE mmm", this is just the conversion program telling you what it's doing to a VAM2 pack. For a VAMX pack, this message should not been issued. Next, if the pack has relocation entries and they appear to be VAM2, the program will prompt "OK TO CONVERT RELOCATION ENTRIES TO VAMX?" You should consider this and respond "Y" only if you are certain they are not already VAMX formatted. If you respond "N", they will not be touched, but conversion of the DSCB on the pack will proceed normally. (Any other response aborts the pack conversion at this point.) Subsequently, DSCB conversion begins. The PAT is scanned for DSCB pages and they are each read, converted, and written. At the end of this, the PAT is rewritten, and following that the label. 0 11. Using the D4.3 CHKVTOC, verify that the PAT/DSCB conversion was performed correctly. 0 12. Repeat steps 10 and 11 for each of your public volumes. 0 13. You must now modify the labels for all double density 3330 packs. In the label, at offset 13 (decimal), is a 4 character string which serves to identify the type of drive the disk pack is on. For proper unit check recovery, the D4.3 file routines use this field to distinguish between 3330 mod 1s and 3330 mod 11s. Any 3330 mod 11 packs must have this field changed to '333B', and you should run VAMREC to do this as follows: 0 RUN FILE:VAMREC Volume: Dxxx Cmd: MODIFY LABEL 13 "333B" Cmd: DISPLAY LABEL Cmd: RELABEL Cmd: $ENDFILE 0 Again, only 3330 mod 11s need this change. 0 14. From the D4.3 single pack system, run the catalog conversion program (CONV.CAT) along with a private version of the D4.3 file routines (FILE:FILERTNS) containing a set of D4.3 TABLES for your regular system, i.e., TABLES prepared as in step 4 above, but with a full complement of disk volumes for your regular packs rather than just MTS431. If you get the message, "ON PRODUCTION SYSTEM?" you've made an error in loading the program and should try again. The program will then print out a list of public volume labels for arcane reasons. It will take as long as two to five minutes to run, print out "CATPVN LABEL 1 6 - UPDATED" if it had to convert the pointer (in the label of PVN 1) to the first catalog extent, and then print out "CATALOG CONVERSION COMPLETE". Any other messages are errors and should be investigated. 0 15. Using the D4.3 VNTD, verify that the catalog conversion proceeded correctly by doing a "V,C". 0 At this point, you have finished the conversion of the format of your disk packs to VAMX. 0 16. You must replace the IPLREADER on your production IPL pack with the version from this distribution. Follow the procedure in the IPLREADER writeup (see packing list) making sure that you run it on the D4.3 pack (so you get + ___ the new IPLREADER), but write it on your production IPL + _____ pack, which is now VAMX also. 0 17. Many files on your production system need to be updated to contain programs or data for the new system. This should be done by using FM on the MTS431 pack to move the files to your regular packs. A list of the files which have changed since D4.2 is included at the end of this writeup. Go through this list and decide which files you want to move (many are optional). A complete list of all the files on the MTS431 pack is available in the file MTS:MTS431.FILES. Make a list in a file of all the files to be moved. Then enter the command: 0 RUN FILE:FM+FILE:FILERTNS(1,99)+tables+FILE:DASDUC+ - COPY:SYSDEFS PROT=OFF 0 where tables contains the D4.3 TABLES for your production + ______ __________ system. When FM reads from the terminal enter a $CONTINUE WITH line to read the list of files you produced above. FM will ask if it is OK to destroy some files, tell it OK or ALLOK. 0 18. You should also move your resident system for this distribution (as modified on your test pack) to *IPL.0 (or some other file) on your production IPL pack. Make sure that this system has the version of TABLES which corresponds to your production system. 0 19. You are now ready to IPL the new system. 0 20. Signon at the operator's console under userid MTS and enter: 0 RUN FILE:FILEUPD EXECPKEY=ACCMAINT 0=*DUMMY* 1=-EMPTY 0 This will update file storage records for all userids. It is important that this be done, since the file space for some userids will be incorrect as a result of running FM. It may be necessary to change some of the file names on $CONTINUE WITH lines at the end of FILE:FILEUPD to 1 7 - correspond to the names used in your system. 0 21. Add any local modules to *LIBRARY. Do not simply replace the new *LIBRARY with your old one, but rather merge the two. 0 22. Add any local messages to *SMDS. Again, do not just replace the new file with your old one, as there are several new messages in it. 0 23. Add any local changes to *SYSMAC. Again, these must be merged with the distributed version. 1 8 - The following files in your regular system may be destroyed, if you desire, since they are no longer used. In some cases the files no longer exist, while in others it is just the name that has changed. 0 *ALGOLWLIB FILE:DISKDUMP.S MTS.:UBCMACLIB *ALGOLWXLIB FILE:DS MTS.:USERS.S *DYSSUB FILE:DS.O NEW.:GOM *IPL.D4.2 FILE:DSKMAN.S NEW.:PASCAL *PL1LINKLIB1 FILE:FASTRSTR.O NEW.:PLUSLIB *USERS FILE:FASTRSTR.S SEG2:ALGW *XALGOLW FILE:PMAP.ISORT.S SEG2:ASMTDEFS APL.:_OLDNEWS FILE:TBLS.TEST.S SEG2:PIL COPY:ACCFORMAT FILE:VNTD.O SEG2:STDTV COPY:ED.COPY.M FILE:WHATSLEFT SYS.:CMDPIKUP.O COPY:PLUSINCLUDES MTA.:ASMHBLDLIN SYS.:HASPLOG00001 COPY:RMGRMACLIB MTA.:ASMHINFO UNSP:LIST COPY:STATDSECT MTA.:ASMHINFO.OS WSG.:DEDIT.PT DWB.:ASMTIDY.S MTA.:ASMHINVK WSG.:MNET DWB.:BLOKLETR.S MTA.:ASMHOPTIONS WSG.:NEWSYS.WF DWB.:CMDPIKUP.370 MTA.:BINEBCD WSG.:OLDSYS.WF DWB.:CVTOMR.D3 MTA.:BUFALLOC WSG.:RESSYS.WF DWB.:FSTATCMD4P MTA.:CCHSUBR DWB.:GOM.COMMON MTA.:DMPLST.SSCN DWB.:GOM.COMMOND MTA.:DUMP DWB.:GOM.COMMONG MTA.:FBJTJL DWB.:GOM.CONTAB MTA.:FIDCQ DWB.:GOM.CONVERT MTA.:FIDS.BLDLIN DWB.:GOM.LISTWRUP MTA.:FNDJTL DWB.:GOM.MATRIX MTA.:FOS.BDAM DWB.:GOM.PEEL MTA.:FOS.DDEF DWB.:GOM.PROGWRUP MTA.:JBRP DWB.:GOM.S MTA.:MIFMACTEST DWB.:GOM.SEQS MTA.:PRINTDUMP.W DWB.:GOM.SG MTA.:PTRUC DWB.:GOM.SYMTAB MTA.:REWIND DWB.:GOMMANUAL MTA.:SIOERR DWB.:GOMNEWS MTA.:SSXREF DWB.:JESMACLIB MTA.:STATBUFF DWB.:NONRESEQ MTA.:STATSUB DWB.:PERSTEST MTA.:TURNAROUND DWB.:PK.PERMIT MTA.:UC3330 DWB.:UBCTFZO.S MTA.:UMMPS.INFO DWB.:UNEPA.S MTS.:COMM ETC.:PLI MTS.:DISTINDEX ETC.:PL1DIRECTOR MTS.:DRIVER1600 ETC.:11ASROPMER MTS.:DRIVER6250 ETC.:11ASROPMLAM MTS.:DYSSUB ETC.:11ASROPM360 MTS.:INDEX1600 ETC.:11ASROP03 MTS.:INDEX6250 ETC.:11ASROP45 MTS.:MSG.S FILE:ACATALOG.O MTS.:MTS421.FILES FILE:CCATL.O MTS.:OXFORD FILE:COMBLIST MTS.:OXFORD.S FILE:DASDUC.O MTS.:RATENBR FILE:DISKCOPY.S MTS.:STDTV 1 9 - The following is a list of public, semi-public, and major private files which have changed or been added since D4.2. Note: files in this list marked with + are files which must be + ____ changed for VAMX, but which will also work properly with VAM2, i.e., the VAMX changes are upward compatible. However, files in this list marked with - are files which must be changed for + ____ VAMX, but which will not work properly with VAM2, i.e., the VAMX + ___ changes are not upward compatible. In addition, for VAMX the following decks must be changed in or added to the RAMROD resident system: UC3330, UCDISK, OPEN, CAT, RWSE, WRIT, TRAK, GETD, VOLG, and RSF. 0 *ACCOUNTING *FAKEOS *SORTLM *ACCOUNTING1 *FIXFEP *SPITDEBUG *ACCOUNTING2 *FORMAT *STATUS *ACCOUNTING3 *FTNTIDY *SYSMAC *ACCOUNTING4 *GFINFODSECT *S2L *ACCOUNTING5 *GOM *TAPECOPY +*ACCRESTORE *GTU *TAPERTN *ALGOLW *HGS *TAXIR *APC *HPS *T360MASTCONV *APLGM *HWTERM *UMIST *ARUDEF *IG.HP7221 +*VALIDATEFILE *ASCEBCD *INDEX *1052RTN *ASMG -*IPL.DECKGEN *11ASR *ASMGSYSMAC *IPL.D4.3 *2741RTN *ASMT -*IPL.0 *3036RTN *CCQUEUE *IPL.1 *3066RTN *CKID *IPL.2 -*3270RTN *CLSACC *IPL.3 *3284RTN *CLSCALC *ITX ACC.:ACCLIB *CLSED *LIBRARY ACC.:STAPROJECT *CLSFILESTATUS *LINKEDIT APL.:001NEWS *CLSLOG *LINK11 APL.:005SNOBOL *CLSMOUNT *LISP COPY:BJPDSCT *CLSMSG *LISPLIB COPY:CC.MACROS *CLSNET *MACUTIL COPY:CLSTV.SG *CLSNEW *MNETRTN COPY:CMDAREADSECT *CLSNEW2 *OVERDRIVE COPY:ED.MACROS *CLSNEW3 *PAG -COPY:FILE.MACROS *CLSPERMIT *PDP8RTN COPY:GLOBALDEFS *CLSPMF *PIL COPY:GLOBALSETS *CLSSDS *PLOTSYS COPY:IT.COPY_SECT *CLSSSTA *PL1 COPY:IT.DSECTS *CMD *PL360 COPY:JOBSTA *CNFGINFODSECT *PL360LIB COPY:LLMPSEQU *COBOLU *PRJDIRECTORY COPY:MISC.MACROS *COMBINE *PROJECT COPY:MTS.MACROS *DAVE *RATEFILE COPY:PCBDSECT *DAVE.GENLIB +*RESTORE COPY:PSA *DLG *SAV COPY:RM.MACROS *DSO *SDM COPY:SETPARM *DWB *SENSEDSECT COPY:UMMPS.MACROS *EBCDASC *SMDS DIST:COMM *EBCDBCD *SNOSTORM DIST:DISTINDEX *ENCRYPT *SORT DIST:DRIVER1600 1 10 - DIST:DRIVER6250 -FILE:CHKVTOC MTA.:CONFIG.U DIST:GENNOTES.WF FILE:CHKVTOC.W MTA.:DMPLST.VMFIN DIST:INDEX1600 FILE:CHONID.W MTA.:DRUMSTAT DIST:INDEX6250 FILE:CONV.CAT MTA.:EREPCMD DIST:NEWSYS.WF FILE:CONVERTING MTA.:EXIT DIST:OLDSYS.WF FILE:CONVV2VX MTA.:FAKEOS.GBLS DIST:RESSYS.WF FILE:CONVV2VX.AS MTA.:FIDSCMD DWB.:CMDTAPE.370 +FILE:DASDI MTA.:FOS.MACLIB DWB.:CMDUTIL FILE:DASDI.S MTA.:FOS.SVC59 DWB.:GOM.O FILE:DASDI.W MTA.:FOS.UPDATES DWB.:GOM.OG FILE:DASDUC MTA.:FOS.WTOTST DWB.:GOM.SEQS.O -FILE:DISKCOPY MTA.:IT.JOBPGM.S ETC.:ASMGF1 FILE:DISKCOPY.AS MTA.:IT.S ETC.:BASICHELPC +FILE:DISKDUMP MTA.:MCHCCH.S ETC.:BASICSIGNONM FILE:DOC.DESC.CAT MTA.:MCHMAC ETC.:BDAM FILE:DOC.DESC.LNE MTA.:MCHSUBR ETC.:DAVE.EXT FILE:DOC.DESC.SEQ MTA.:OC.S ETC.:DAVE.INIT FILE:DSKMAN MTA.:OLTEPCDS ETC.:DAVE.0 FILE:DSKMAN.W MTA.:OLTEPCDSBLDL ETC.:DAVE.1 -FILE:FILERTNS MTA.:OLTEPCMD ETC.:DAVE.2 -FILE:FIXCAT MTA.:OLTEPCRECDS ETC.:DAVE.3 +FILE:FIXSD MTA.:OLTEPTSTBLDL ETC.:DAVESUB FILE:FM MTA.:PDP.S ETC.:EDEXPLAIN FILE:FM.S MTA.:PDPBUG ETC.:EREPLIB FILE:FM.W MTA.:PRINTTRACE ETC.:EREP470LIB FILE:FSTEST MTA.:PRINTUC ETC.:FAKEOS.MSG -FILE:GETDSK MTA.:PRINTUC3330 ETC.:FIDS.BLDL -FILE:OPEN MTA.:PRNTCNTS ETC.:FIX.EXPLAIN +FILE:PDLIST MTA.:PRUC3330 ETC.:FIX.FIODSCT -FILE:PM MTA.:PUC ETC.:FIX.MESSAGES FILE:PM.S MTA.:READ3330LOG ETC.:FIX.UNITDSCT FILE:PM.W MTA.:SOFTCHK ETC.:FMTLIB +FILE:RECATALOG MTA.:TESTIOMAC ETC.:FOS.OLTS FILE:RECOVERING MTA.:UMMPS.U ETC.:M6800ASRERR -FILE:RWSEQ MTA.:UNITS.S ETC.:OBJUTILEXP FILE:SCRATCHSIZES MTA.:VMN.S ETC.:OLTEPBLDL FILE:STARFILES MTA.:V370 ETC.:OLTEPCDSLIB -FILE:TABLES.TEST MTA.:V370.S ETC.:OLTEPTSTLIB -FILE:TRAK MTA.:V370DEV.MAC ETC.:PASCALERRS FILE:UBC.DISK.W MTA.:V370DEV.UM ETC.:PLUSMESSAGES +FILE:UCDISK MTA.:470CCH ETC.:PL1LINKLIB +FILE:UC3330 MTS.:BROADCST ETC.:SNOSTORM -FILE:VAMREC MTS.:CHGFORMDATA ETC.:TSHAREID FILE:VAMREC.WRUP MTS.:CKID.S ETC.:TXTFODS -FILE:VNTD MTS.:CLSDUMMY.S ETC.:TXTFWIDS FILE:VNTD.W MTS.:CMDSTATUPD ETC.:11ASRERROR -FILE:VOLGET MTS.:CMDSUPD +FILE:ACATALOG -FILE:WRITEI MTS.:CONSOLE -FILE:ACATSUB +INIT:INIT MTS.:DBJP FILE:AMALGAMATE INIT:INITCMD MTS.:DCKPCHR.O -FILE:CALLRELDSK MTA.:ASMHDIR MTS.:DCKPCHR.S -FILE:CATALOG MTA.:ASMHMACUPD MTS.:DCKPCHR.W +FILE:CATSCAN MTA.:ASMHUPDNEW MTS.:DSRIUPD +FILE:CCATL MTA.:ASMHUTIL MTS.:DSRSUPD FILE:CCATL.W MTA.:CNVTEREP MTS.:DYSUPD FILE:CHKFILE MTA.:COBOLU MTS.:FILESTATUS.S 1 11 - MTS.:FNAMETRT RSTR:TAPEPREVIEW UNSP:EXPR_MESSLIB MTS.:FSUBUPD +RSTR:VALIDATEFILE UNSP:EXPR_MESS3P MTS.:GATEUPD -RSTR:VTOCREAD UNSP:EXPR_MESS3SB MTS.:HASP.D/A SEG2:ALGOLW UNSP:I8080ASR MTS.:INFOUPD SEG2:BASIC UNSP:JONMACLIBFMT -MTS.:IPLBOOT.O SEG2:EFL UNSP:LISTER -MTS.:IPLINIT.O SEG2:FIX UNSP:MACLIB +MTS.:IPLREAD.O SEG2:HASP UNSP:MACSCAN MTS.:IPLREAD.W SEG2:OBJUTIL UNSP:MACSCAN.360 MTS.:LLXUUPD SEG2:PRINTMAP UNSP:MACSCAN.370 MTS.:MACROSUPD SEG2:S2APL UNSP:MCS650XASR MTS.:MTSASM SEG2:S2FILES UNSP:M6800ASR MTS.:MTSUPD SEG2:S2L UNSP:PAS.BC MTS.:ON/OFFLINE SEG2:S2MAP UNSP:PAS.BC.DEBUG MTS.:PERMIT.S SEG2:TRTABLES UNSP:PAS.BC.LIB MTS.:PLIMUPD SEG2:TR3270 UNSP:PAS.SB MTS.:PRINTDUMP STRT:HSP UNSP:PAS.SB.LINK MTS.:PWC STRT:HWTPRINT UNSP:PAS.SB.LOG MTS.:RNBRUPD SYS.:CCP UNSP:PAS.SB.RUN -MTS.:ROD SYS.:CMDPIKUP UNSP:PAS.8000 MTS.:RSFUPD SYS.:CMDTAPE.O UNSP:PAS.8000.ERR MTS.:SSCNUPD SYS.:DIRPROGRAM UNSP:PAS.8000.RUN MTS.:STDDMP -SYS.:DSK UNSP:PASCAL.GN MTS.:SVC.W SYS.:FIXFEP UNSP:SIGCHECK$ MTS.:SYSDEFS SYS.:FIXLOG UNSP:SIGLOG MTS.:TESTPERSUB SYS.:HASPRECEIPTS UNSP:SOUNDEX MTS.:TIMTUPD SYS.:HASPSTAT UNSP:TAPEDRIVES MTS.:USUBUPD SYS.:ITX UNSP:TAPESHARE NEW.:CKSIG SYS.:ITXCMD UNSP:WRITEUPS NEW.:LOGPURGE SYS.:MSSCN UNSP:Z80ASR NEW.:PLUS SYS.:PLT WSG.:DCSTAT NEW.:PLUS.OBJLIB SYS.:SDM WSG.:FM.GEN NEW.:PLUS.SOURCEL TMTS:LOADMTS WSG.:MOUNTCMD RSTR:AUTOREST TMTS:POSTIPL WSG.:MSSCN RSTR:DEADFILEDES TMTS:TMTSLIB WSG.:PDP8 +RSTR:DEADSAVE UNSP:APPEND WSG.:SSRTN +RSTR:DEADUCATDES UNSP:BCPL.COMPILE WSG.:SSTA.CLS RSTR:DSF UNSP:BCPL.DEBUG WSG.:STATSCN RSTR:FASTRESTORE UNSP:BCPL.LIBHDR WSG.:TABLES -RSTR:FASTRSTR UNSP:BCPL.LIBRARY WSG.:TABLES.WF -RSTR:FILEDSCB UNSP:BCPL.STREAMH WSG.:TAPE -RSTR:FILESAVE UNSP:BCPL.TIDY WSG.:TAPECOPY -RSTR:FILESAVEOBJ UNSP:BCPL.XREF W009:BLKHDR RSTR:FS.MACROS UNSP:CATALOG W009:BLKHDR.S RSTR:FSTAPECOPY UNSP:COMPARE W009:CLSDRV.O RSTR:FSTEST UNSP:CONCORD W009:CLSDRV.S RSTR:MERGE UNSP:CONVSPIT W009:CLSINFO.S -RSTR:OLFSOBJ UNSP:COUNTW W009:I RSTR:RESTORE UNSP:CRLFASCEBC W009:PISTLE.S +RSTR:RST UNSP:EXPR.DEMO W009:PISTLE.W +RSTR:RSTFMT0 UNSP:EXPR.DOPE W009:UMLOAD.U +RSTR:RSTFMT1 UNSP:EXPR.IMPRINT W170:KWIC.SPELL +RSTR:RSTFMT2 UNSP:EXPR.MOTIVE W170:STOR -RSTR:SAVEFILE UNSP:EXPR.RATS RSTR:TAPEDIRLIST UNSP:EXPR.SCHIZ RSTR:TAPEOUT UNSP:EXPR.SOCFAC