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: <9904@ucbvax.ARPA>
Date: Wed, 14-Aug-85 21:45:08 EDT
Article-I.D.: ucbvax.9904
Posted: Wed Aug 14 21:45:08 1985
Date-Received: Mon, 19-Aug-85 20:51:42 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 13

From: MRL%MIT.MFENET@LLL-MFE.ARPA



We recently also had a problem with our SYSTARTUP.COM hanging on an attempt
to start a print queue.  We believe our problem was that we had recently
changed the SCSNODE definition (we do not yet have a cluster, however).
This causes device names to be displayed with SCSNODE preceeding them,
i.e. _SCSNODE$DEVICE.  We think the job queue got confused on this.  The
problem was solved by creating a new JBCSYSQUE.DAT.  The weird thing was
that before we did that, we were able to start the queues running by simply
stopping and then restarting the job manager WITHOUT creating a new
JBCSYSQUE.DAT .