• Subject: RE: CPU at 100%
  • From: "Shaw, David" <dshaw@xxxxxxxxxxx>
  • Date: Tue, 25 Jan 2000 15:16:25 -0500

Ken,

Just remember that for *CONS to work, the system value QCONSOLE has to be set
correctly.

Dave Shaw

-----Original Message-----
From: Sims, Ken [mailto:KSIMS@SOUTHERNWINE.com]

Hi Jim -

>Date: Tue, 25 Jan 2000 08:05:31 -0800
>From: Jim Langston <jlangston@conexfreight.com>
>Subject: CPU at 100%
 ...
>2. How do I get my console to always log on to QCTL instead of
>   QINTER at a high run priority so I can actually get in and find out
>   what is wrong before I ABEND the system?

The proper way to do this is ...

1. Your controlling subsystem should have a workstation TYPE entry of *CONS
which specifies
AT(*SIGNON).  You may also want to have a workstation TYPE entry of *ALL
which specifies
AT(*ENTER) so that other terminals can TFRJOB into QCTL.  It is best if
there are no workstation NAME entries in your controlling subsystem.

2. Any other subsystems which have workstation TYPE entries should also
include a workstation TYPE entry of *CONS which specifies AT(*ENTER) to make
sure that these subsystems cannot grab the console.

3. Any other subsystems which have generic workstation NAME entries that
would include the system console should also include a workstation NAME
entry with the specific name of your console device which specifies
AT(*ENTER) to make sure that these subsystems cannot grab the console.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].