RE: Secondary console in QCTL

[Adam_Driver@xxxxxxxxxx]

Thankyou to Alex and Chris for this.

I've made the entry in QINTER and there will be an IPL on Friday night, so
I'll let you know how it went. I probably used the wrong terminolgy
refering to these workstations as consoles (I just meant they were twinax
dumb terminals as opposed to the rest of the network which consists of PCs
on an ethernet WAN). DSP01 is obviously the system console, and I know
DSP05 won't work in restricted state even if it is in QCTL.

Thanks for your help

Adam Driver
Technical Consultant
Kaz Computer Services
Level 5, 66 Wentworth Ave
Surry Hills, Sydney    NSW   2010
Phone : + 61 2 9844 0386
www.kaz.com.au



                    "Alex A Moore"
                    <alexm@ellishosiery       To:     <midrange-l@midrange.com>
                    .com>                     cc:
                    Sent by:                  Subject:     RE: Secondary 
console in QCTL
                    midrange-l-admin@mi
                    drange.com


                    18/09/01 11:17 AM
                    Please respond to
                    midrange-l






You need to exclude DSP05 from QINTER by adding a workstation entry with
Control Job at *ENTER in the QINTER subsystem description.  This prevents
this device from being grabbed by QINTER at signon.  This is not a second
console though, the device is only in the controlling subsystem ( assuming
QCTL is your controlling subsystem ).  In restricted state, only one device
can be active.

Alex


-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com]On Behalf Of
Adam_Driver@kaz.com.au
Sent: Monday, September 17, 2001 6:30 PM
To: midrange-l@midrange.com
Subject: Secondary console in QCTL


Hi Everyone,

At the request of our operators I've added a second console, DSP05, as a
workstation named entry in the QCTL subsystem. However, it still starts up
in QINTER. I've had a look through the history log and you can see DSP05
varied on a few seconds before QCTL starts, so it should be available.
There are in fact two other terminals defined in QCTL (DSP02 and DSP03) and
you see messages that QCTL can't allocate them (Not sure why because they
eventually come up in QINTER). QCTL doesn't even seem to try and grab
DSP05.

Am I missing something? Would removing the other workstation entries form
QCTL make a difference? BTW, these particular terminals are twinax
connected dumb terminals (it's a large data centre and these terminals are
in the operations "flight deck" next to the computer room. All other access
to this machine is from PCs over an ethernet WAN). DSP01 is of course on
port 0 address 0. DSP05 is on port 4, address 3. One of the other
workstations mentioned above, DSP02, is on port 4, address 0. Is there
something I should be looking at there? The workstation type entries for
QCTL are *CONS and *ALL.

Many thanks in advance


Adam Driver
Technical Consultant
Kaz Computer Services
Level 5, 66 Wentworth Ave
Surry Hills, Sydney    NSW   2010
Phone : + 61 2 9844 0386
www.kaz.com.au