Maxc OperationsSoftware Maintenance Procedures6517. 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.17.1. MidasThe current sources for Midas are kept on the "Maxc2 Midas" Alto disk (maintained by Fiala).Reasonably current sources are also kept on [IVY] or [MAXC2] directories:MSOURCES.DM along with MIDAS.RUN, LOADER.MB, and DEBUG.MB. The various Midascommand files are kept on DGSOURCES.DM along with the sources for the microdiagnostics.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.17.2. AltIOAltIO is maintained by Taft using an Alto disk labelled "AltIO/Maxc2". Backup copies of thesource and command files are kept in a single dump-format file ALTIO.DM on Ivy. fpi0qXFpa`r$ ]KsU [U Y RrX Os)3 MU K; J#5" FXYC@  Au ?  <8^ :nO 8< 6` 5; 3CJ 1yQ /L ,<X+ ( I' & I'% $a I'3'"+ b IX' . I'0 a @ 1rX s!; U  >[^Software Maintenance ProceduresMaxc Operations66AltIO 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.17.3. TM, MemBash, SMIDiag, Alto MicrocodeThese pieces of software are kept as dump-format files in the directory on Ivy. The filesare TM.dm, MemBash.dm, SMIDiag.dm, and MaxcAltoCode23.dm. They are compiled and loadedby means of command files whose names follow the conventions used for AltIO.17.4. 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 theMaxc2 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.17.5. TenexThe Tenex system for Maxc2 is generated from a set of sources maintained on Maxc2 in the <134>directory (for Tenex version 1.34).The RUNFIL script LOADMAXC2.RUN may be used to assemble and load the new version ofTenex. Most of the source files are assembled for the system yielding .REL files with extensions.2RL. Some of the assemblies do not depend on any system parameters. When changes are madeto any system parameters in PARAMS.MAC or PROLOG.MAC, all the .2RL files should bedeleted to force reassembly of them.The result of assembling and loading a new Tenex is a file called MAXC2.SAV, plus some auxiliaryfiles whose extensions are .MAXC2. The bug string file and loader map are also printed on Clover;these should be placed next to the log book in the Maxc room.After loading a new Tenex for Maxc2, all that is necessary is to run Micro-Exec and installMAXC2.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.)fqX;pi  _s1" ]K01 [F TrX+ QNs01 OA ML FrX% Cs5 A'7 ?2 <J :2+ 8& 5xB 36 1Q 0# )WrX %sH $# &- N J I9 ~$  V B7+ w= > ;E pI )>\ TIMESROMAN  TIMESROMAN  TIMESROMAN  TIMESROMAN   j/ MaxcOps17.BravoRWeaverOctober 21, 1981 10:23 AM