changing the hash file path to mounted directory at project

[rkacham_DSX]

Hi,

Is there any way we can change the hash file path of all jobs to mounted directory at project level,
we need to change the hash file path from uv account path to mounted directory (directory path)

Thanks,
Ramesh

[kcbland]

Only thru opening each job in Designer.

[htrisakti3]

Have u tried this:

1. export existing job to dsx file
2. change the setting & export to different dsx file

compare two files & see if you can isolate the changes..
you can then try to export the whole project to dsx & make mass-changes Replace-all using text editors

I tried this before but only with changes in dir path..

[ray.wurlod]

It's always a good practice to use a job parameter for hashed file directory.

Had you done so, you would not have a problem.

Do you want to move the hashed files to the new location? That is a different question.

[Andal]

To follow htrisakti3 Solution, u have to add one extra job parameter in each job and you have to use that parameter, in your directory path.

I did this for my project through VB, which contains nearly 7000 jobs.


Rgds
Anand

[rkacham_DSX]

Thanks Ray,
we were using uv account path now we have the physical memory problem,wo we want to move these hash file to some mounted directory(out side to the uv account), is ther any way we can do that at project level

Thanks,
Ramesh[/quote]

[kcbland]

You're talking about changing the radio button on the stage properties from reflecting account to external directory, and then filling in the external directory value with a job parameter.

By my calculations, you have to figure out where this information is stored inside the dsx file and adjust accordingly. Then, you have to get a parameter added to every job to hold the directory path, and then figure out where in the dsx to store it. Most of the time, if an design option isn't used, you'll have to figure out where/how to add this information to the dsx.

Forget about it. Open every job in Designer and fix your problem. You or someone else made this sandwich, you're just going to have to eat it. Sorry.

[ray.wurlod]

Alternative solution.

Do the export with (that is, including) default-valued properties. It's a larger export file, but everything is in it. Then the modification is straightforward.