Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!psuvax1!psuvm!BCVMCMS!PAPP From: PAPP@BCVMCMS.BITNET (John F. Papp) Newsgroups: bit.listserv.ibm-main Subject: Device allocation Message-ID: Date: 8 Feb 90 15:10:14 GMT Sender: IBM Mainframe Discussion list Reply-To: IBM Mainframe Discussion list Lines: 13 Approved: NETNEWS@PSUVM Gateway You're right. It is working as designed. The answer is in what you've told the system to do. When you reply "HOLD", you are saying you want the job to hold on to all current allocations and wait until this particular allocation can be resolved via the available devices at the time. It doesn't change when you bring on a new device and locks up allocation for that class device until one is freed. Generally, you want "NOHOLD" as a default. This will release all currently allocated resources and allow you to bring online similarly classed devices. Also, I would normally bring the device online via the request not a vary command. -John-