• Subject: RE: Changing subsytem sign-on
  • From: James Turnbull <jamest@xxxxxxxxxx>
  • Date: Wed, 22 Oct 1997 12:02:37 +1000

You need to look at your subsystem descriptions.  Take a close look at
the Workstation name and type entries and the ADDWSE command.  You can
change the QINTER subsystem to stop it from acquiring any new devices
and then change QCTL to allow it to acquire all devices.


James Turnbull

AS/Tech Consulting

        -----Original Message-----
        From:   Gary Feinstein [SMTP:gfeinste@planethollywood.com]
        Sent:   Wednesday, 22 October 1997 8:40
        To:     midrange-L@midrange.com
        Subject:        Changing subsytem sign-on

        Does anyone know how to change the system (V3R7) so when a user
signs on
        they go to QCTL subsystem instead of QINTER?  The user is not at
the
        system console.  I am running TCP/IP as the comm protocol.  Can
this be
        done?  
        Thanx,
        Gary Feinstein
        AS/400 System Administrator 
        Planet Hollywood International
        +---
        | This is the Midrange System Mailing List!
        | To submit a new message, send your mail to
"MIDRANGE-L@midrange.com".
        | To unsubscribe from this list send email to
MAJORDOMO@midrange.com
        |    and specify 'unsubscribe MIDRANGE-L' in the body of your
message.
        | Questions should be directed to the list owner/operator:
david@midrange.com
        +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| 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].