On a Lawson 8.0.7 ESP7 environment running on Windows 2000 any changes made to the windows Environment Variables are not being reflected inside of the LID client. Is there a different place to configure the LID variables?

Well... Which variables are you changing?

Since LID is a telnet client, it should be reflecting the variables found on the TARGET system rather than the one it was started from.

Tell us more and we'll try to help.

There are a number of them but here is short one. The DATASET variable for TaxFactory if changed in the windows Environment Variables does not change in the LID client after a reboot.

This is happening from any LID client it is like it pulled the variables in some time ago and continues to use them. The information being used is from the previous admin who left the company over a year ago. Even the variables 'USERDOMAIN’, ’USERNAME’ and ‘USERPROFILE’ are his.

Unfortunately I'm the resident Unix Curmudgeon, so I'll step aside and let one of the young Windows Whippersnappers have a go at your problem.

g'luck!

I've seen this before. Check your opening scripts. When Lawson launches there are settings in configuration files. Then, when a person logs in, their account also may run a series of scripts. They include DOS Batch file, a UNIX script running under UNIX emulation, or a little bit of both.

Batch files can call UNIX scripts (they run as a Korn shell script in MKS Toolkit). and when "system variables" are reset there, it looks like they were set up in the Control Panel - but they weren't.

(Dave is wrong about Unix experience not needed in Windows. Of course you need it, that's what MKS is for.]

Happy Hunting - sounds like you had a real cowboy who set you up!

I have checked the windows side for anything resetting the variables. Are there startup processes in Lawson that could be reading these from somewhere?

And yes you are right on with this being installed by a cowboy...

On the unix side there is something that does this in /etc/ called lawson.env. I'm not sure what it would be on Windows side or if there is something similar on the Windows side. My assumption for windows would be System and User variables set in the "My Computer" level.

Something I learned from another Application is to check the %SYSTEMDIR%\Application Compatibility Scripts\ directory. You can create scripts in the LOGON directory that would run when users login via Terminal Services. Usually ".CMD" files. Obviously, not exactly the what I would expect from LID, but I don't know how LID works on Windows.

The really strange part is I get these variables in any LID session, even from sessions on different machines.

On Windows machines - there is no lawson.env file. You create the system variables (there are 2 needed - DATASET and TF80_CONNECT_STRING ) using the System\System Properities tab.

That is the goal, but the changes made to the system variables are not being reflected in Lawson.

Are you sure it was created as a system variable and not a user variable? (Sorry if that is a stupid question...not intended to be!! )

Where are you seeing the "old" variable? What do you see when you open TF on the server...in the lower-left corner of the program?

It is a system variable being set. If you into LID and do a ‘echo %DATASET’ you get a different variable.

I can get TaxFactory to work with no issues, but when I move to into Lawson then fun starts and I have traced back to this variable issue.

Yep..echo %dataset% gives me TF80, which matches the system variable. Not sure why you are not seeing the same thing...as long as you reboot the server after creating the variable, it should show up in LID. I created these myself, as part of the last upgrade. Very odd....wish I knew the answer!! :-(

If I think of anything...I'll let ya know.

From the way you describe it another script is being run after the User logs into LID replacing the system variables.

Out of curiosity I looked at the some of the documentation for LID and I see that you can pass Windows Domain information. You should probably check with your Windows server people to see if there are any Domain login scripts being run for your LID users that would set Lawson variables. If I were to guess I would say that it's a probably a generic script that was setup and that LID users were put into group that would run that script.

I have pulled the system off the network, so no network and/or domain scripts are being run. This is getting very puzzling..

So your running the LID session on the machine console?

At the moment, I also get the same results when running from a desktop with the LID.

I'm sorry a bit confused. If you pulled the server off the network then how can you connect to it from your desktop?

Sorry about that... Private segment with just the app server and a couple of workstations. All systems rebooted to clear any information from the domain and then login using cached information.

Ok, that clears up my confusion.

Have you checked the %LAWDIR%\system\profile.bat file?

Nothing there,

rem $Header: /cvs/cvs_archive/univ/system/profile.bat,v 1.6 2001/06/05 20:35:51 lawson Exp $

set LATERM=univwin
set PATH=%NetExpressPath%;%PATH%

Shoot..I don't know. The only I can think now is to try and do a text search in every file for %LAWDIR% on the server. Cause it's reseting the system variables somehow. Have you done a check in the registry?