Stopping TenexMaxc Operations142.Manually run the Micro-Exec memory test (so that Tenex will be informed of solidly failingregions of memory that it shouldn't use):*Test.Memory.Fast (T M F)3.Read in Tenex without starting it:*Read.Tenex.From.Area 0 (R T F A 0)4.Enter Exec DDT, turn on the "Checkdsk bypass" switch, and start Tenex:*EDDT EDDTCHKBYP/ 0 1 SYSGO1G7. STOPPING TENEXIn order to give users adequate notice and to protect files on disk, Tenex should ordinarily bestopped in the following manner.As long as possible before the scheduled downtime (preferably 24 hours or more), notify users by(optionally) putting a notice in the login message, setting the system downtime cell, and recording atelephone message.A.To put a notice in the login message,1 login as yourself and:@SNDMSG To: SYSTEM cc: Subject: Scheduled downtime Message:(An appropriate message giving date, time, and reason)^ZQ,S,?,carriage-return: SYSTEM -- ok@------------------------------1Do this only if the downtime is of unusual nature or duration. You must be a member of the "System" group to send messagesto SYSTEM.)fqX ;pi  _r2? ]K)YY YX Vg2"RRR O2F2LKL2JG2H%H|H%.H|2F[ F #>sX ;ArO 9w 6` 4:;* 2p .2X%/t.r+8+5 !+ )K)j) ''~'&, %6&,$a"6 u  ~7 l  Ut F{ g  D=[Maxc OperationsStopping Tenex15B.To set the system downtime cell, you must be a wheel or a maintenance person:@ENABLE (only if you are a wheel)!HALT, (do not omit the comma)[Superpassword:] GUESS !!AT mm/dd/yy hh:mm (date&time system going down)!!UNTIL mm/dd/yy hh:mm (date&time coming back up)!!DUE (TO REASON) reason (type ? for list) !!!C.To record a telephone message, go to the recording telephone (next to the Imp in the backroom) and follow the instructions posted there.The system will automatically start notifying users of the impending downtime beginning one hourbefore it is to occur. When the zero hour arrives, all jobs will be forcibly logged out except any joblogged in on the Maxc controlling terminal, new logins will be prevented, and "ShutdownComplete" will type out on the Maxc console. If there are now no jobs logged in, Tenex willshortly hit a BUGCHK (EDDT breakpoint) at SWHLT1, at which point Tenex is properly halted.If there is a job logged in on the Maxc controlling terminal, it will be necessary to halt Tenexmanually. To do this (for which you must be a wheel):@ENABLE !QUIT .Halt Tenex.Wait for the EDDT breakpoint at SWHLT1. A message such as "$8B>>CHKADR BUGCHK/SWHLT1" should be printed out. At this point it is safe to un-protect the NVIO/AltIO console("3301P") and return control to Midas ("M"). fpi