Did you try to issue "CP Q devno" to query a new device (devno is the
address of it).
If it doesn't show, I guess you included an IODF statement in your SYSTEM
CONFIG. If I understand how IODF is implemented in z/VM, it could indeed
mean you need to transfer the IODF file made on z/OS onto your
On Monday, 08/10/2009 at 08:30 EDT, Charles Grady
wrote:
> OK here we go again...
>
> I our shop the z/OS folks manage the HCD and the creating of the LPAR
> definations.
> When they make changes they do a "hard activate" on a test z/OS LPAR and
then
> the rest
> of the z/OS LPARs get the ne
I do not completely get your question. But, here some facts:
- As opposed to z/OS, z/VM doesn't need an IOCDS, it questions the HW (or
LPAR in this case) to see what devices are available.
- when the IO config of zVM's LPAR is changed "in flight" by a z/OS, z/VM
will notice and for example bring t
OK here we go again...
I our shop the z/OS folks manage the HCD and the creating of the LPAR
definations.
When they make changes they do a "hard activate" on a test z/OS LPAR and then
the rest
of the z/OS LPARs get the new IOCDS defination by changing their IPL PARM.
z/VM does NOT
have a z/O
