Move the WRK dir

[gerie]

This is probably a dumb question, but I don't seem to find an answer anywhere.
I want to move my WRK dir from my C: to a seperate disk with more space. However, I want to know if I can do that without problems and what configurations etc do I have to change in order to make it work. Can I move it or do I need to reinstall (not really an option:awink? Can I move it while my db is online?
I was searching the internet and some forums, but I don't find anything about this issue.

DB Progress 10.1B
OS Windows 2003 server

 

[rstanciu]

search the regedit->HKEY LOCAL MACHINE/Software/PSC you can change the WRKDIR without reinstall,
another option is to change the starup.pf -T parameter used for temporary files. The database server don't use the WRKDIR.

 

[gerie]

I was hoping for something like this. Thnx

 

[RealHeavyDude]

Please be aware:

The WRKDIR setting in the registry is not really relevant for many thing. Mostly it's the default location for log files and the icons that get created during install use this setting too. Other than that you're not bound to it in any way.

Each process has its own working directory which is determined by in which directory you start it. Plus, each process will generate temporary files which are located per default in the working directory unless you specify the -T startup parameter.

Regards, RealHeavyDude.

 

[gerie]

Please be aware:

The WRKDIR setting in the registry is not really relevant for many thing. Mostly it's the default location for log files and the icons that get created during install use this setting too. Other than that you're not bound to it in any way.

Each process has its own working directory which is determined by in which directory you start it. Plus, each process will generate temporary files which are located per default in the working directory unless you specify the -T startup parameter.

Regards, RealHeavyDude.

But if I do adjust the registry, the temp files will be writen to the directory in the registry? If so, I can just change the registry without having to worry about losing diskspace when large temp files are generated.

 

[RealHeavyDude]

Per default, the temporary files will be written in the working directory of the process (Progress session), but that is not the working directory in the registry. It is the directory in which you started the session (the directory that you see under "start in" in the properties of the Windows shortcut, or the directory you cd'd into before calling the prowin32.exe in a command file).

You can test this easily:
Start a Proenv, cd to some directory and just start the prowin32.exe (will pop up the editor if you have development license installed) and you will see files like lbi*, rcd*, srt* created exactly in that directory which will disappear as soon as you stop the session gracefully.

If you change the registry setting for the WRKDIR it will have no effect on this behavior. Instead the only way to change this "globally" is to add the -T parameter to the startup.pf in the installation directory. This startup.pf is customized during installation and will be used by every Progress session you start.

Still, there are occasions where a core dump is generated when the Progress session crashes and this file gets created in your working directory regardless of the -T setting.

HTH, RealHeavyDude.

 

[rstanciu]

change all WorkPath registry variables and edit the file C:\Progress\OpenEdge10.2A\startup.pf (or %DLC%\startup.pf)
and add :
-T c:\tmp
... it works ! ... see the temp-files in c:\tmp