Interactive Subsystem - Automatic Signon

Mike,

I have done similar things in the past by having a batch job acquire
the terminal.  The signon screen is briefly displayed by the owning
subsystem (I suppose you could modify the subsystem signon screen to
appear as blanks though I didn't bother going to that extreme), and the
appropriate terminal then acquired via the appropriate OVRDSPF and
subsequent application OPEN.

The one thing I can think of to watch out for is that the system does
consider the job to be batch (that is, not interactive) and so certain
CL and application defaults that change across these two environments
need to be explicitly stated or at least tolerated (CL DSP* commands
would be one example).

Bruce Vining

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