[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::hackers_v1

Title:-={ H A C K E R S }=-
Notice:Write locked - see NOTED::HACKERS
Moderator:DIEHRD::MORRIS
Created:Thu Feb 20 1986
Last Modified:Mon Aug 03 1992
Last Successful Update:Fri Jun 06 1997
Number of topics:680
Total number of notes:5456

351.0. "Longest uptime of VMS ?" by MARVIN::WARWICK (Whack your porcupine) Wed Nov 05 1986 12:04

    
    	This isn't really a HACKERS topic, but I couldn't think of anywhere
    else to put it.
    
    	What is the record for continuous uptime for a VMS system ?
    The longest I've ever seen in over 2 years (in Engineering...) is
    this:
    
VAX/VMS V4.4  on node JYNNAN 30-OCT-1986 16:42:05.90   Uptime   80 07:54:29
    	
    	This is a 780 that is part of a large cluster. Anyone do better?
        
    
    Trev
T.RTitleUserPersonal
Name
DateLines
351.1CAFEIN::PFAUYou can't get there from hereWed Nov 05 1986 15:376
    The best I can remember around here (parvax, cafein) is about 35
    days.
    
    80 days?  That's almost three months!!!
    
    tom_p
351.2SQM::RICOThu Nov 06 1986 10:531
	What about PM?  No PM in 80 days??
351.3PM ? We have PM every afternoon !MARVIN::WARWICKWhack your porcupineThu Nov 06 1986 13:552
    
    	
351.452 and countingTOPCAT::GEISENHAINERThu Nov 06 1986 14:053
    My uVAX (HULK) has been up for 52 days. It will most likely stay
    up until we have a power hit or I get my hands on SDC V4.5... If
    that works out to over 80, I'll post it here...
351.5A WHAT?? No WAY!ASIA::MCLEMANEnjoy Oregon Wines!Thu Nov 06 1986 14:077
    re: .2
    
    PM's??? Do they still do those?? I haven't seen one on our systems
    for a while. :-)
    
    Jeff
    
351.6How about 108 days?MDADMN::EATONDDan EatonThu Nov 06 1986 14:117
    One of my field service buddies reports an 11/730 that ran for 108
    days. The system was brought down then to upgrade VMS otherwise
    it might of made it out to around 178 days since its on a 6 month
    PM schedule.
    
    Dan Eaton
    
351.7ERIS::CALLASO jour frabbejais! Calleau! Callai!Fri Nov 07 1986 10:347
    ERIS was up for 62 days once. Would have been longer if the *%$&*%
    people building ZK3 hadn't cut the power lines to ZK1! 
    
    TRIFID (the VMS QAR system), in the days when it was a 730, was
    once up for 91 days. And this was on FT1 of VMS V4!
    
    	Jon
351.895 days so far for a home systemFALEK::FALEKex-TU58 KingFri Nov 07 1986 12:552
    Tim Garrison (a guy in our group)'s home microvax 2 has been up
    for 95 days so far. His landlord pays the electric bill...
351.9PM = Promotional MaintenanceTURRIS::AMARTINAlan H. MartinSun Nov 09 1986 13:203
The reliability of one of the KL's I used in Marlboro (KL2137? MRFORT?)
went up after we increased the time between PMs.
				/AHM
351.10PM = Provocative MaintenanceSHEILA::PUCKETTOpen the pod bay doors please HALMon Nov 10 1986 00:470
351.11PM = Premeditated MaintainancePHENIX::SMITHWilliam P.N. (Wookie::) SmithMon Nov 10 1986 10:203
    That's usually performed by the system mangler, unless you have
    a Eunichs system with a 'sysmgr', which is pronounced sis mugger.
    
351.1218 months .................TROPPO::RICKARDDoug Rickard - waterfall minder.Tue Nov 11 1986 07:5219
	A customer in Sydney, Australia had a 780 that stayed up for 
approx 18 months. Fixed applications, did not (WOULD NOT) upgrade VMS, 
and restricted field service to doing voltage checks and seeing if the 
fans were going at PMs. System finally came to grief because there is a 
funny with the clock. At boot time, the time read from the battery 
backup clock forms the high order part of the time-date, the low order 
part is derived from some internal high speed interrupt. It turns out 
that there is no carry from the low order to the high order, so that 
after the system had been up for about 18 months without a reboot, ALL 
SYSTEM TIMES WENT WRONG. This affected all file stamping, etc, etc, and 
really caused a screw up. Engineering were finally able to tell us that 
we had to reboot at least once every 18 months. By the way, it was about 
VMS V1.6, so maybe thats saying something.......

		Doug.



351.13REGINA::OSMANand silos to fill before I feep, and silos to fill before I feepTue Nov 11 1986 15:4310
Oh well.  So much for using VMS to manage a long-trip rocket voyage !

Unless of course the more recent VMS versions have been fixed to allow
more than 18 months of up-time.

Of course, the only for-sure way is to TEST it.  Perhaps every new
release should be started on a machine in a corner somewhere and left
up FOREVER or until it crashes, as a test for longevity.

/Eric
351.14ULTRA::PRIBORSKYTony PriborskyTue Nov 11 1986 15:593
    18 months without some kind of power outage?   Wow.   DEC certainly
    COULDN'T do it - we religiously take down entire plants once a year.
    Must need to PM the transformers or something...
351.15ERIS::CALLASO jour frabbejais! Calleau! Callai!Wed Nov 12 1986 16:2710
    re .13:
    
    Why can't you re-boot the ship's computer? When I was at Nasa, we did
    it. But then we never had satellites big enough to fit a 780 on them. 
    
    On the other hand, the people I worked with often said (to us wimps who
    used M, VMS, and Twenex), "If you're using an operating system, you're
    not *really* doing real-time." 
    
    	Jon
351.16longevityAIWEST::DRAKEDave (Diskcrash) Drake 619-292-1818Sun Nov 16 1986 21:315
    As an OEM we had a 780 stay up well over 150 days. You should have
    seen the queue job numbers! The fan on the LSI-11 took it down.
    We ran 3.x  circa 1981-1982. I agree with the note that suggested
    "Methusala" testing for longevity, you never know what evil lurks
    behind the curtains...