Login security

[Fairlight]

> Using @id assumes that the person starting the filePro app is the person
> who signed onto the computer.  This can be a very dangerous assumption if
> file access is being controlled.  I would love to be able to use putenv
> pfname,l_name when the person signs into my app.  However, it won't stick
> unless I run everything from my starting program from menus, screens and
> chaining to the processing table I need to use.
>
> Now there must be an easier way.

The way I've seen this handled in the past was to set up *clerk as a
persistant program where you logged in, and were given your menu choices
from there once you did.  You could put information in the environment once
they're logged in, and so long as that top-level *clerk remains active, any
children you SYSTEM off will get that information.  But you'd end up using
*clerk menus instead of runmenu, and eating an extra license per user.

mark->
-- 
          *****   Fairlight Consulting's Software Solutions   *****
OneGate Universal CGI Gateway:                  http://onegate.fairlite.com/
FairPay PayPal Integration Kit:                 http://fairpay.fairlite.com/
RawQuery B2B HTTP[S] Client & CGI Debugger:     http://rawquery.fairlite.com/
Lightmail Mail Sending Agent:                   http://lightmail.fairlite.com/
FairView Image Viewer for Integration:          http://fairview.fairlite.com/