You have to define the printers to your second level VM system.
My guess is that you also had to define them on the first level system.
Look at the SYSTEM CONFIG on the first level to see if you have a RDEVICE
similar to:
RDEVICE 00E TYPE IMPACT_PRINTER,
CLASSES S,
FOLDUP YES,
IMAGE_LIB IMAG3262
RDEVICE 00F TYPE IMPACT_PRINTER,
CLASSES A
RDEVICE 01E TYPE IMPACT_PRINTER,
CLASSES F,
FOLDUP YES,
IMAGE_LIB IMAG4248
And then copy it to the second level SYSTEM CONFIG.
Tom Duerbusch
THD Consulting
>>> Robert Payne <rpa...@tad.org> 9/15/2009 10:05 AM >>>
and I guess the "FORCE" option doesn't help ?
Darn the bad luck! Sorry but I'm out of ideas for now.
Bubba
-----Original Message-----
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu]on
Behalf Of Frank M. Ramaekers
Sent: Tuesday, September 15, 2009 9:28 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Printers to 2nd level VM...
Can do, but...
set rdevice 5336-5338 ty imp
HCPZRP6722I Characteristics of device 5336 were set as requested.
HCPZRP6722I Characteristics of device 5337 were set as requested.
HCPZRP6722I Characteristics of device 5338 were set as requested.
3 RDEV(s) specified; 3 RDEV(s) changed; 0 RDEV(s) created
Ready; T=0.01/0.01 09:27:15
q 5336-5338
PRT 5336 OFFLINE , PRT 5337 OFFLINE , PRT 5338 OFFLINE
Ready; T=0.01/0.01 09:27:22
vary on 5336-5338
HCPCPN6895I Device 5336 cannot be varied online because the device
HCPCPN6895I identification data is inconclusive.
H
