RE: Changing subsytem sign-on

Neil,

We did this at COMMON to allow people to enter requirements using a specific
ID to sign on remotely but not permitting anyone else to sign on using these
remote devices.  It works great.


>
>Haven't tried this, but what if  you created a new subsystem containing 
>the generic QPADEV* workstation entry, then set *PUBLIC authority to 
>this subsystem to *EXCLUDE, and authorized only the userid you want ?
>
>
>... Neil Palmer                                      AS/400~~~~~
>... NxTrend Technology -Canada       ____________          ___  ~
>... Markham,  Ontario,  Canada       |OOOOOOOOOO| ________  o|__||=
>... Phone: (905) 731-9000 x238       |__________|_|______|_|______)
>... url:http://www.NxTrend.com        oo      oo   oo  oo   OOOo=o\
>... mailto:NPalmer@NxTrend.com     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
>-----Original Message-----
>From:  Gary Feinstein [SMTP:gfeinste@planethollywood.com]
>Sent:  October 23, 1997 10:53
>To:    MIDRANGE-L@midrange.com
>Subject:       Re: Changing subsytem sign-on
>
>Neil,
>       Actually, I am shutting down QINTER for the purpose of not letting any
>users other than myself gain access to the system.  In the past I had
>users processing during EOD, causing locks on files, holding up my EOD
>jobs.  So, creating a generic QPADEV* workstation entry wont work. 
> Nice
>try though.
>:-(
>Gary
>
>> I use QPGMR instead.  Have QPGMR subsystem contain a workstation 
>entry
>> for QPADEV*  and if the backup fails for some reason and QINTER isn't
>> started when I connect in I get a signon display in QPGMR.
>> Now YES this DOES mean others could do the same, but our sole reason 
>for
>> ending QINTER is to make sure no locks are left on objects so the 
>backup
>> will be complete, and no one but me is stupidf enough to be signing 
>on
>> at 3am anyway, so I don't care.  If this suits you also then give it 
>a
>> try.
>> Yes - if you leave QPGMR subsystem up during the day other jobs may 
>get
>> signon displays here because of the workstation entry, so you could
>> either end QPGMR during the day, or set up another subsystem that is
>> only active when QINTER is down (maybe start this subsystem in the
>> dayend job just prior to ENDSBS QINTER, and after the STRSBS QINTER 
>runs
>> in the day-end job do an ENDSBS whateversubsystemyouuse *CNTRLD.
>>

+---
| 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
+---