Re: Virtual controller load

It just creates new virtual controllers.
WRKCTLD CTLD(*VWS)
Controller
QPACTL01
QPACTL02
QPACTL03
...
QPACTL10
QVIRCD0001
QVIRCD0002
QVIRCD0003
...
QVIRCD0010
Commonly with a text like "Controller created for" followed by your lpar
name.

Heck, one time I deleted them all and let them all rebuild. Allowed to me
thin down virtual controllers also.
Our application uses a "workstation data area". That doesn't get
destroyed with the device. People's 5250 sessions are configured with a
device name. Normally it's "PC name" with a session id at the end. So if
my PC is GDL164 then I'll have GDL164S1 as one session, GDL164S2 as
another and so on. So if I delete GDL164S2 it will get recreated and pick
up that old workstation data area. Since my laptop is portable, does it
make sense to have GDL164S1 tied to printer P01A01 when one day I could be
using it in one building and the next in another city? Most printouts
never physically print. We have them go to a dummy printer and if they
really want them to print they reassign it. How many people really print
the printout from Item Master Maintenance and keep it?



Rob Berendt