Setting up Account Name in Hash File Stage

[ririr]

Hello -

I wanted to modify the hash file stages in some of our jobs to use the account name instead of directory path. What information do I need in order to handle the above situation.

Any help is appreciated!!

Thanks

[kcbland]

Leaving the field blank will default the job to creating/looking for the hash file in the project. By explicitly naming the account (project), you "lock" the hash file to that named project. Better to use a job parameter in this field. However, leaving it blank works the best since it doesn't care which project it is in.

[kduke]

Ken

I think they want to know an automated way to change all the jobs from path to account. Is that correct?

[ririr]

Hello -

I wanted to modify the hash file stages in some of our jobs to use the account name instead of directory path. What information do I need in order to handle the above situation.

Any help is appreciated!!

Thanks

You are correct kim.. This is a followup to my previous post

Thanks

[ray.wurlod]

The obvious method is to use the Designer client, and modify your jobs properly.

You will retort that you don't want to do that, you prefer automatic to manual.

In this case your only possibility is carefully to hack an export file.

In either case, as suggested, if you want to use an explicit account name, make it a job parameter. This insulates you against different account names existing in development, UAT and production environments.

[kduke]

You could also hack the DS_JOBOBJECTS file. Of course this may violate your license agreement but how do you think we learned it.