LID

I'm not aware of any way to tell the difference, although you might be able to look at the process chain via ps -ef and figure it out. But I think a user logging in and starting a form via 'lapm' vs. a form started via desktop client login look the same: ksh->lapm.mon->lapm.srv.

Why does it matter? Are you trying to prevent desktop client / command line access to the server?

All the input fields entered on Desktop Client Logon screen (ie through frontend.exe) are captured in Windows Registry.

However, you could not use that information to determine if a user is logged in via Desktop Client vs. Desktop Client Logon. For example, I can login via Desktop Client Logon screen (ie through frontend.exe), logout, the login via Desktop Client (ie through univwin.exe), and the info is still in the Windows Registry.

While you cannot say so for sure, you can do a "reasonable guess" - in a login script put a command that captures user input. If it would be LAPM ... right after the login, then it's Desktop Client Logon. Again, it would be a guess, but I think a good one.

Not sure if this will help, but you can check out a script on Dave Schronce's site, which might be helpful:
http://www.schronce.net/l...on/login_menu.sh.txt

Thanks for the support. I got the solution.

Read the input from the script and check the below condition in the case statement for desktop client and desktop client login.

"setenv LATERM univwin")
eval $input
read input
eval $input
read input
eval $input;;

Thanks
Raja