×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Very helpful - Thanks
All this started when an IBM tech came here for unrelated reasons and acted like it was odd that QCTL was not online when he noticed a console check.
I think I will just create DSP01 under CTL01 and ( maybe ? ) CHGSYSVAL QCONSOLE from QCONSOLE to DSP01.
Sound resonable?
Rob Berendt <rob@xxxxxxxxx> 6/17/2019 2:08 PM >>>
I have two related controller descriptions:
Controller Type Text
CTL01 6A59 Work Station Controller
QCTL 6A59 Controller description created during IPL.
CTL01 uses Resource name . . . . . . . . . . : CTL01
And is set to Online at IPL . . . . . . . . . . : *YES
It has one attached device: DSP01
QCTL uses the same Resource name . . . . . . . . . . : CTL01
But it is set to Online at IPL . . . . . . . . . . : *NO
It has one attached device: QCONSOLE
When you start subsystem QCTL it will use CTL01
When you start subsystem QSYSSBSD it will use QCTL
However YOU should never start QSYSSBSD. Only IBM will start that and only at certain rare instances, like OS upgrades, initial installs and related activities.
This is the way it is supposed to work.
If QCTLSBSD is set to QBASE (as shipped) instead of QCTL (as almost everyone does who does "traditional" interactive and batch work does) just substitute the subsystem description QBASE for QCTL.
In summary, you should not be trying to get the controller description QCTL to automatically start.
Rob Berendt
midrange.com
