Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!decwrl!ucbvax!"
From: "@ucbvax.BERKELEY.EDU
Newsgroups: mod.computers.vax
Subject: (none)
Message-ID: <8603141219.AA15516@ucbvax.berkeley.edu>
Date: Thu, 13-Mar-86 00:54:00 EST
Article-I.D.: ucbvax.8603141219.AA15516
Posted: Thu Mar 13 00:54:00 1986
Date-Received: Sat, 15-Mar-86 02:45:54 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 27
Approved: info-vax@sri-kl.arpa

RT BERGGREEN" <art@acc.arpa>
Subject: VMS SYSGEN Question
To: "info-vax" <info-vax@sri-kl>
Reply-To: "
ART BERGGREEN" <art@acc.arpa>


We have been seeing a problem under VMS 4.2 with CONNECT in SYSGEN.
When we try to issue CONNECT commands to configure a terminal
port driver (YCDRIVER) for a board which happens not to be in
the system, we often get a machine check in the Unit Initialization
of the port driver.  It is my understanding that the Unit Init
routine is NOT supposed to be called for offline devices.
The machine check never occurs connecting unit 0 (when the CRB, IDB
and first UCB get created), but usually happens on the CONNECT
for the second unit.  This probably won't show up if the terminal
driver is always AUTOCONFIGURED, but if the STARTUP command files
try to configure a nonstandard system, any missing devices can
cause grief.

Anyone else seen any CONNECT problems or have any ideas?

Any VMS developers listening? (Seems like a real bug)

					Art Berggreen
					<Art@ACC.ARPA>

------