This is directed to those wanting to use the korn shell under Windows SUA for the purpose of looking at log files, editing config files, etc. To me it sure beats the watered down LUU under LID for monitoring the system, but I still need to use LID to run the Lawson utilities. I'm running S3 9.0.1.x right now under Windows Enterprise Server (WS 2008). In order to set it up so you can use vi, you have to set the term, you can do it by instantiating the profile:
Start->Programs->Command Prompt
C:\Users\lawson>ksh
$. /etc/profile
Welcome to the SUA utilities.
DISPLAY=localhost:0.0
$ ps -eaf |grep ksh
lawson 205 777 11:06:43 n00 0:00.00 grep ksh
lawson 777 1 11:04:39 n00 0:00.13 /bin/ksh
lawson 6212 0 11:04:39 S02 0:00.02 D:\LUU\ksh.exe ksh $ echo Now I am going to tail the ios log, of course you could save some keystrokes and set lawdir or create an alias in your profile... Now I am going to tail the ios log, of course you could save some keystrokes and set lawdir or put an alias in your profile...
$ tail -f /dev/fs/D/lsfdev/log/system/ios.log | grep -i error & ... This is very powerful there are many ways you can hurt yourself (rm dash r comes to mind) if you aren't careful or don't know what your doing. But you are a system admin and you know this.