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
Setting up Account Name in Hash File Stage
Moderators: chulett, rschirm, roy
Setting up Account Name in Hash File Stage
Last edited by ririr on Mon Oct 18, 2004 12:24 pm, edited 1 time in total.
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.
Kenneth Bland
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
Re: Setting up Account Name in Hash File Stage
You are correct kim.. This is a followup to my previous postririr wrote: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
Thanks
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
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.
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.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.