goog@a.cs.okstate.edu (GOOG ??) (07/31/88)
I was at a DECUS LUG meeting recently and we received some information on VMS 5.0 and how quickly you can update. In addition, we received the announcement of VMS 5.0-1 which should be coming out in mid-August. The memo reads as follows... KNOWN PROBLEMS FIXED IN VMS 5.0-1 VMS V5.0-1 fixes the following problems existing in VMS Version 5.0 systems: o At times, system dumps are not written out for MicroVAX 3000 series processors in a Local Area VAXcluster. o For 6200 series processors: - Powerfail recovery does not work properly - Memory errors are not recorded correctly - AUTOGEN can incorrectly size system parameters causing boot failures - System crashes can occur because of locking erros in multiprocessing code o For 88x0 series processors: - Console synchonization problems can cause data corruption - At times, powerfail recovery does not work correctly - At times, memory error handling and recording does not work properly o At times, system crashes are caused by: - Volume shadowing - LTDRIVER - ETDRIVER - RMS $REWIND - SET ACL/DELETE/OBJECT=QUEUE o At times, data corruption is caused in: - RMS Recovery Unit Journals (RMS Journaling) - RMS Sequential Files - DECnet transmissions o At times, data from tapes is not transferred: - From tapes which have bad blocks on a TU81+ - By COPY operations o Dynamic memory allocation performs much worse than in VMS Version 4.7 o At times, the JOB CONTROLLER gets stuck in an endless loop o Incorrect time stamps with page fault erros affect page fault monitoring when using MONITOR and PCA Steve Koinm Internet: goog@a.cs.okstate.edu Systems Administrator steve@nemo.math.okstate.edu Department of Mathematics Oklahoma State University UUCP: rutgers!okstate!goog Stillwater, OK 74078 -------------------------------------------------------------------------------- " " -Harpo Marx