Our LOGIN has many entries of the form:

IF @LOGNAME="xxx" THEN SOME.MENU
IF @LOGNAME="xxx" THEN LOGOUT

This offends my sense of good programming. There must be a (probably
several) better way. Somewhere in the collected intelligence of the UV
community there is an answer. I would appreciate any suggestions.

Given the limitations of paragraphs themselves, not much more is possible to
be added directly into the login paragraph itself. One suggestion might be
to write a program that routed users based on name and insert that into the
login script instead. The only concern (and probably legit reason) for
the entire practice is making sure that phantoms reach the command line.

Mike

"Robert Stearns" <is (AT) uga (DOT) edu> wrote

On Mon, 29 Sep 2003 15:24:27 -0400, Robert Stearns <is (AT) uga (DOT) edu> wrote:

As the other poster mentioned, the only way to remedy this is to write
a basic program to do all the handling and just run that program from
the login proc.

To let phantoms passthu to a UV command prompt, i think the code in
basic would be something like

IF OCONV(@TTY,'MCU') = 'PHANTOM' THEN ABORT

I'm repling to my own question to ask a more detailed one.

Could I do something like:

<<MYLOGIN,@LOGNAME,1)>>
LOGOUT

where MYLOGIN is a simple database with @LOGNAME as its key and the
proper menu name as the 1st data value? Likewise, if the @LOGNAME is
missing from the database, no command would execute followed by LOGOUT
which is great by me!

Robert Stearns wrote:

Only in a BASIC program. Paragraphs are more of a TCL scripting
environment, Not much logic can be included. Add your logic in a program
and replace the @LOGNAME lines in the login paragraph with your program.

Something like:

PA
MENUROUTEPGM
......
......

Inside the MENUROUTEPGM program you can be as elegant as you like.
"Robert Stearns" <is (AT) uga (DOT) edu> wrote

We actually created a "STARTUP" paragraph per user.
The LOGIN program was something like... (and please understand, this is
simplified)

<<...logic to test for phantom process, or system maintenance, or
administrator...>>
OPEN "VOC" TO VOC.FILE
READV TEST FROM VOC.FILE,@LOGNAME:".STARTUP",0 THEN
CHAIN @LOGNAME.STARTUP
END ELSE
CHAIN "OFF"
END

Afterward, when a new user was set up, there was a VOC record of
<<login.name>>.STARTUP to be created that would send him to his parent menu
/ application / what ever. Has worked well.

"Robert Stearns" <is (AT) uga (DOT) edu> wrote