Re: Interactive Subsystem - Automatic Signon

     Mike,  This is easy to do, although this is a big security hole and 
     the auditors will have a hissy when they see it.
     
     1.  Create a user profile that has authority only to the applications 
     and files it needs. 
     2.  Create a subsystem just for that function
     3.  Create a routing program that only calls your application (routing 
     programs do not have to be QCMD)
     4.  Create a class for that job.  (ie timeslice 2000 priority 25)
     5.  Create a job description for the application.  Where it normally 
     says *RQD for user profile, put your new user profile in it.
     6.  Created the device description so it has a completely unique name 
     no other devices would use (IE   XXX3607 for controller 3, port6, 
     switch 7)  Also assumes no other device will have "XXX" as a prefix to 
     the name
     7.  Change the existing on line subsystem work station entries to use 
     prefixes, and remove *all
     8.  Add a workstation entry to your new subsystem and specifically 
     name the workstation name.  Make sure to specify the job description 
     you just created for this application
     9.  Start the subsystem.  When the terminal allocates, all you will 
     have to do is press the enter key, the terminal will sign on with the 
     user profile you created, and the routing entry will run the 
     application.  If the application ends, it will sign off the terminal.
     
     Be sure to remove observability from your application and only give 
     *USE  authority to that object.
     
     I have sample routing programs, device descriptions, subsystem 
     descriptions, etc if you want them.  Just email my private account and 
     I will forward them.
     
     Jim Oberholtzer
     Information Builders
     jim_oberholtzer@ibi.com
     630/971-6700
       


______________________________ Reply Separator _________________________________
Subject: Interactive Subsystem - Automatic Signon 
Author:  <MIDRANGE-L@midrange.com> at Tcpgate
Date:    12/9/98 9:47 AM


We have a situation whereby we want to setup a terminal to be used in a 
kiosk like function.  We would like to have the terminal not be required to 
be signed on by any user.  Is this possible?
     
Here's what we want to do:
     
We use Kronos for time keeping.  Since we have eliminated time cards an 
employee has no way to determine hours worked etc.  We would like to set up 
a terminal for use for time card review.  Assuming the terminal is already 
signed-on the only program running would be the time card review program. 
The terminal will be using a card-key authorization with a PIN.  I really 
don't want to have this terminal to be signed-on on a regular basis.  Is 
there a way to allocate a terminal to a subsystem and not require a userid 
and password manually keyed in?
     
Thanks
     
Mike Crump
     
     
+---
| 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 
+---
     

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