On Aug 8, 2011, at 00:34, John P. Hartmann wrote: > WAIDEV > (Or, perhaps, WAITDEV.)
> See pipeline news. > Thanks. AHELP tells me: ... ! 1. A real device is already present for the virtual device. This means that ! a terminal is already present. This cannot occur for readers and channel ! to channel adapters. Is this because those device types are obsolete? Might this not yet happen in a second level VM if a virtual reader defined at first level is ATTACHed to the second level VM, where it would appear real? Or is support for real readers completely absent from CP nowadays? > On 8 August 2011 03:33, Glenn Knickerbocker <[email protected]> wrote: >> On Sun, 7 Aug 2011 14:46:32 -0600, gil wrote: >> >> Rather than reinvent the whole server, check out PIPESERV: >> >> http://www.vm.ibm.com/download/packages/descript.cgi?PIPESERV >> Thanks also. I need to check which is more suitable. A broader question. Does WAITDEV (and perhaps other builtin stages) modify the I/O new PSW? Do they restore it before running CMS or CMD? (CP shouldn't matter.) Is there a risk that interrupts will be lost while CMS owns the PSW? Is there a compatibility matrix of Pipeline stages versus CMS commands available? Thanks, gil
