Xref: utzoo comp.sys.dec:2670 comp.os.vms:22621
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uwm.edu!fps!brodie
From: brodie@fps.mcw.edu
Newsgroups: comp.sys.dec,comp.os.vms
Subject: Re: INCA release date question (DEC maint product)
Message-ID: <3374.25d95b8f@fps.mcw.edu>
Date: 14 Feb 90 18:22:23 GMT
References: <3370.25d7d1f0@fps.mcw.edu> <6278.25d931f0@pbs.uucp>
Distribution: usa
Organization: Medical College of Wisconsin, Milwaukee, WI
Lines: 27

In article <6278.25d931f0@pbs.uucp>, sdroppers@pbs.uucp (Seton Droppers) writes:
> 
> It was not my impression that one needed VAXSIM, only a modem.  Can anyone
> comment?  This is important since we are currenly a third party maitenance
> site.
> -- 
> Seton Droppers  -- "Anything that I say is my opinion and not my employer's."
> Public Broadcasting Service, 1320 Braddock Pl. Alexandria, VA 22314
> (UUCP: ...{vrdxhq,csed-1,ida.org}!pbs!sdroppers) (Voice: 703/739-5100)
> (VAX/VMS running DECUS UUCP 1.1, ANU News 5.9C)

well, the "rules" were not real clear (or even known) at the time.
I think you just had to be under dec maintenance (i.e, need an "access number"
for colorado/atlanta), and a modem.   Integration with vaxsim is a future
possibility.

(think about it, VAXSIM sees a bunch of disk errors, hooks into DSNlink
(or whatever it's called now), tells colorado about the disk errors and
a specialist is notified about it and checks out your system, all while
you're asleep....!)
-------------------------------------------------------------------------------
Kent C. Brodie - Systems Manager		brodie@fps.mcw.edu
Medical College of Wisconsin	     voice:	+1 414 778 4500
				     FAX:       +1 414 778 6694

"The worst thing you can do to a VAX/VMS system is log in."
			-Said at a local DECUS vax performance seminar