Re: SOLVED - No signon screen -- MIDRANGE-L

× 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.

Hi Pete -

CTL02, then, has the current terminal in place, yet, it didn't give me a
signon.  Working the hunch that the QINTERXXX subsystem was a clue, I
did use WRKSBSD QINTER* and DID find a QINTER subsystem.  It has the
*CONS entry in it and *ALL. But, it wasn't started.  I started it and it
DID  give me a signon screen.  I has assumed, wrongly, that the
QINTER001 and QINTER002 subsystems were all that were needed.  For
telnet, yes, but for DSP020000 I needed to have QINTER running.


QINTER001 and QINTER002 obviously don't have a matching workstation entry.

You probably really don't want QINTER running as it can grab by type devices that you want as part in QINTER001 or QINTER002 by name unless you want to add name entries with AT(*ENTER) to QINTER for every name entry in QINTER001 and QINTER002.

Once your device is on CTL01 port 0 address 0 it will become the console device and should come up in your controlling subsystem.

You could add a name entry to your controlling subsystem so that it would come up there even not as the console.

-- Ken http://www.ke9nr.net/ Opinions expressed are my own and do not necessarily represent the views of my employer or anyone in their right mind.

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.