Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!umich!samsung!brutus.cs.uiuc.edu!psuvax1!psuvm!UKACRL!MWE
From: MWE@UKACRL.BITNET
Newsgroups: bit.listserv.ibm-main
Subject: (no subject given)
Message-ID: <IBM-MAIN%90020901180856@DEARN>
Date: 9 Feb 90 04:19:09 GMT
Sender: IBM Mainframe Discussion list <IBM-MAIN@RICEVM1>
Reply-To: IBM Mainframe Discussion list <IBM-MAIN@RICEVM1>
Lines: 12
Approved: NETNEWS@PSUVM Gateway

Message-id: <08 Feb 90 17:32:17 GMT MWE@UK.AC.RL.IB>
Date:     Thu, 08 Feb 90 17:32:17 GMT
From:     "Mike Ellwood (0235) 21900 X 6161" (MWE at UKACRL) <MWE@UK.AC.RL.IB>
To:       IBM-MAIN at DEARN
Subject:  Device Allocation Problem


I am tempted to say that this problem probably would not occur on a JES3
system, but that may be mere bigotry, and is no help to your immediate
problem!   However, if you ever meet the IBM  SE that (probably) convinced
your management to go to JES2 and not JES3, then I suggest that you DON't
but him a drink! :-)