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.ARPA
Path: utzoo!linus!philabs!prls!amdimage!amdcad!decwrl!ucbvax!daemon
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: Corruption of JBCSYSQUE.DAT
Message-ID: <9887@ucbvax.ARPA>
Date: Wed, 14-Aug-85 07:08:33 EDT
Article-I.D.: ucbvax.9887
Posted: Wed Aug 14 07:08:33 1985
Date-Received: Mon, 19-Aug-85 06:50:24 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 23

From: boulder!jon (Jon Corbet)

	We have recently (finally!) upgraded to VMS V4.1 + new XQP, and a
new problem has developed.  In SYSTARTUP.COM, there is a line of the form:

		$ start /queue /default=(burst=one) lpa0

where LPA0 is a basic, vanilla print queue.  Nothing fancy about it.  Every
now and then, this command simply hangs.  It seems to get caught in one of
two types of loops.  The first one looks like some sort of wait -- no CPU
time or other activity.  The other one looks like it is trying to shake the
disk drive apart.  In either case, it will not work until a brand new
JBCSYSQUE.DAT is created.
	Has anybody else seen this one?  I can't see that we are doing
anything nonstandard, and we aren't even running a cluster.  Any ideas would
be much appreciated.

Thanks,
	jon
---
Jonathan Corbet
National Center for Atmospheric Research, Field Observing Facility
{seismo|hplabs}!hao!boulder!jon		(Thanks to CU CS department)