Re: Signon to subsystems other than QINTER

with later versions of OS400 and some client TN5250 program, you can name
your device name with TCP/IP.
Carl Galgano
EDI Consulting Services, Inc.
540 Powder Springs Street
Suite C19
Marietta, GA  30064
770-422-2995
mailto: cgalgano@ediconsulting.com
http://www.ediconsulting.com
EDI, Communications and AS400 Technical Consulting

-----Original Message-----
From: joberhol@compures.com <joberhol@compures.com>
To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com>
Date: Tuesday, June 08, 1999 9:17 AM
Subject: Re: Signon to subsystems other than QINTER


>Stuart,
>
>Is there any way, with QINTER ended, to sign on from a client access
>session?
>
>
>While all of the suggestions for changing the subsystem descriptions to add
>a workstation entry will work, they are not secure enough and rely on
>device names to be very static and will not work in a TCP/IP environment
>where the device names tend to change.  Why not consider a system where one
>subsystem (TFRCTL) will be the only subsystem to offer a signon screen,
>that is the workstation entry will be *SIGNON.  Create your own interactive
>subsystems for the users(INTPRD) and yourself,(INTMIS) with the workstation
>entries set to *ENTER.  That way the only way into the interactive
>subsystems will be via TFRCTL.  Then put a routing program on the TFRCTL
>subsystem that will determine who the user is, and route the job to the
>correct subsystem.  If the target subsystem is not up, issue a polite
>message and end the job.  This way you can leave your own subsystem up all
>the time during back ups etc, and just take down the production interactive
>subsystem (INTPRD).  Regarding security, you can build into the routing
>program any checking you wish, and because it runs before the job actually
>gets any control, there is almost no way to beat it. As an added benefit,
>it is also really easy to stop enterprising folks on the system from
>submitting batch jobs to the interactive job queues.  You wind up with much
>better control, and much less work,  I have done a talk like this at COMMON
>for the last three years, and will send you  (anyone) the code and complete
>set up if you wish.
>
>Jim Oberholtzer
>Computech Resources, Inc.
>414/785-8111
>+---
>| 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
+---