|
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. Option 4 from DSPSBSD will let you look the workstation NAME entries for a subsystem. Option 5 will let you look at the workstation TYPE entries. Personally, I have QCTL set up as described in #1 above. I do not use QINTER. I created our own interactive subsystems, none of which have workstation TYPE entries. They use generic workstation NAME entries instead. This insures that any device which does not met my naming conventions for at least the first part of the name will not get a signon screen. I use the department as the first part of the device name. This lets me put the different departments into different subsystems. I have one subsystem for our local MIS, another subsystem for our remote MIS, and a third subsystem that covers everyone else. Since our console has a name that fits in with our local MIS devices, I have an AT(*ENTER) entry for it in our local MIS subsystem as described in #3 above. Ken Southern Wine and Spirits of Nevada, Inc. Opinions expressed are my own and do not necessarily represent the views of my employer or anyone else. +--- | 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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.