Maxc OperationsSoftware Maintenance Procedures8522. SOFTWARE MAINTENANCE PROCEDURESThis section outlines maintenance procedures for selected pieces of software that are in fact stillmaintained at all. The primary intent is to document the location of the sources and to identify thecurrent maintainers.22.1. MidasMaxc2 only. The current sources for Midas are kept on the "Maxc2 Midas" Alto disk (maintainedby Fiala). Reasonably current sources are also kept on [IVY]directories: MSOURCES.DM along with MIDAS.RUN, LOADER.MB, and DEBUG.MB. Thevarious Midas command files are kept on DGSOURCES.DM along with the sources for themicrodiagnostics.Before initializing Midas on a new disk, be sure that you have the following files ready:Midas.Programs(see below)Gacha10.alThe font Midas usesMidas.MidasThe initialization command fileMidas.Programs contains a list of file names separated by blanks, commas, or carriage-returns. Thenames must be typed in UPPER-CASE. This list serves two purposes. First, file pointers are builtfor all of the names to speed up OpenFile. Next, the list of names for the "Run-Program"command menu is built. If the file name contains no extension, then hint FP's will be built forboth name.MB and name.MIDAS and name will be put in the "Run-Program" menu. (However,the hint FP's are not built unless the file exists, and the file name will not be put in the "Run-Program" menu unless name.MIDAS exists.) If the file name contains an extension, then it will beput in the quick OpenFile table, but won't appear in the "Run-Program" menu.Midas creates and uses the following files:Midas.State~40 pagesBuilt for quick init by Midas/IMidas.Resume~40 pagesBuilt before calling AltIO for resumeMidas.FixUps2 pagesBuilt when external fixups occur in .MB files beingloaded (Current microcode never uses this.)Midas.Errors2 pagesWritten when "Compare" failsMidas.SymTab100 pagesWritten when symbol table overflows core buffersAltogether this is about 200 disk pages. It is desirable to do this with a pretty clean disk, so thatthe files wind up contiguous on the disk and near to each other.22.2. NVIOMaxc1 only. NVIO is maintained by Taft using a Nova disk labelled "NVIO". Backup copies ofthe source files are kept in the directory on Maxc1. fpi0qXFpa`r$ ]KsU [U Y RrX Ot sR MC K> J#8 HY DXYAu  ? =  :n^ 8O 6< 5` 3C; 1yJ /Q -L *rX+ ' I' $ I'% " I'3' +  IX' c I'0 a '@ frX t sP *; =](Software Maintenance ProceduresMaxc Operations86The NVIO source files all have the extension .NS, while command files for assembling and loadingthese sources have extensions .AS and .CF. Instructions for building a new version of NVIO areincluded as comments at the beginning of the source file C.NS.22.3. AltIOMaxc2 only. AltIO is maintained by Taft using an Alto disk labelled "AltIO/Maxc2". Backupcopies of the source and command files are kept in a single dump-format file ALTIO.DMon Ivy.AltIO may be compiled and loaded by executing the command files CompileAltIO.cm andLoadAltIO.cm respectively. AltIO makes use of a number of other Alto software packages availablefrom the directory. These packages are listed in LoadAltIO.cm.22.4. TM, MemBash, SMIDiag, Alto MicrocodeMaxc2 only. These pieces of software are kept as dump-format files in the directory onIvy. The files are TM.dm, MemBash.dm, SMIDiag.dm, and MaxcAltoCode23.dm. They arecompiled and loaded by means of command files whose names follow the conventions used forAltIO.22.5. Tenex and Diagnostic MicrocodeSources for Maxc1 and Maxc2 Tenex microcode are maintained on the "Maxc1/2 TenexMicrocode" Alto disk by Fiala. Sources for Maxc1 and Maxc2 microdiagnostics are maintained onthe "Maxc1/2 Microdiagnostics" Alto disk by Fiala.These are backed up by Alto dump files stored on the IVY directory. Common sourcesare used for both Maxc1 and Maxc2 with conditional assemblies used for parts of the microcodethat are different on the two systems.Cross reference listings of Tenex microcode sources are obtained by FTPing the sources to theMaxc1 ERF directory and doing RUNFIL CRREF.RUNFIL, which uses MCROSS to produce thecross reference listing. The same procedure is used for microdiagnostic sources except that theDCRREF.RUNFIL command file is used.22.6. TenexThe Tenex systems for both Maxc1 and Maxc2 are generated from a common set of sourcesmaintained on Maxc1 in the <134> directory (for Tenex version 1.34). Differences between the twosystems are dealt with by conditional assembly.)fqX;pi  _s7) ]KS [> TrX QNt s8 O/, M JG1" H|01 FF ?rX+ <t s9 :I 89 7 0_rX% ,s5 +"'7 )W2 %J $2+ "P& B 6 IQ ~# rX LsF E /2 p=\Maxc OperationsSoftware Maintenance Procedures87The RUNFIL scripts LOADMAXC1.RUN and LOADMAXC2.RUN may be used to assemble andload new versions of Tenex. Most of the source files are separately assembled for each system,yielding .REL files with extensions .1RL and .2RL. However, some of the assemblies do notdepend on any system parameters, so Maxc1 and Maxc2 share common .REL files for these. Whenchanges are made to any system parameters in PARAMS.MAC or PROLOG.MAC, all the .1RLand .2RL files should be deleted to force reassembly of them.The result of assembling and loading a new Tenex is a file called MAXC1.SAV or MAXC2.SAV,plus some auxiliary files whose extensions are .MAXC1 or .MAXC2. The bug string file and loadermap are also printed on Ears; these should be placed next to the log book in the Maxc room.After loading a new Tenex for Maxc1, all that is necessary is to run Micro-Exec and installMAXC1.SAV on an unused save area (e.g., 19) for stand-alone checkout. The "Read.Tenex.From.-File" and "Write.Tenex.To.Area" commands should be used for this purpose.After constructing a new Tenex for Maxc2, one should transfer the various required files to Maxc2by means of PUPFTP. These files are <134>MAXC1.SAV, BUGTABLE.MAXC2 andMONSYMS.MAXC2. These files should be transferred to the same directories andpreserving the version numbers. They may then be deleted on Maxc1. Then the file MAXC2.SAVshould be installed on a Maxc2 save area as explained above. fpi0qXFp _s9 ]KN [G YV WJ V!= RA P8( O\ K> IE HI Da BK A @ ?A N =v< =/=* TIMESROMAN  TIMESROMAN  TIMESROMAN  TIMESROMAN  TIMESROMAN  qj/JMaxcOps22.bravoRWeaverNovember 25, 1980 1:37 PM