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



As a follow-up question, I understand that this will work, but can someone
explain why it is necessary to do this in QINTER? If the device is
available when QCTL comes up, why doesn't QCTL just grab it?

I'm just trying to get a better understanding of how all this works.
Thanks!

midrange-l@midrange.com writes:
>As others pointed out you need to add specific entries to QINTER with the
>option set to *ENTER instead of *SIGNON.  This will keep the subsystem
>from
>grabbing the device when it starts up.  Second point already made was that
>these are only in the controlling subsystem not backup consoles.  The only
>real backup console on an AS400 that I know of is CTL02 Port 0 Switch 0.
>This can be accessed in restricted state if you have problems with CTL01.
> I
>would make sure this is in your secure flight deck and assigned to QCTL at
>*SIGNON and QINTER at *ENTER.  I usually name them CONSOLE1 AND CONSOLE2.
>
>Christopher K. Bipes   mailto:ChrisB@Cross-Check.com
>Operation & Network Mgr        mailto:Chris_Bipes@Yahoo.com
>CrossCheck, Inc.       http://www.cross-check.com
>6119 State Farm Drive  Phone: 707 586-0551 x 1102
>Rohnert Park CA  94928 Fax: 707 586-1884


Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA  01376
413-863-4357 x444
mnaughton@juddwire.com



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.