Hi,
One of our client's existing DataStage jobs involves a process that reads from a hash file for a lookup. the hash file's metadata seems to have been manually entered.
I need to find the job that's creating this hash file to make some modifications. Is there a way to do this?
Find Job Creating The Hash File
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 376
- Joined: Sat Jan 07, 2012 12:25 pm
- Location: Piscataway
Find Job Creating The Hash File
Jerome
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
Seeing as how you are saying the metadata was "manually entered" I'm assuming you already tried #2 and it didn't work for you, even if you have the metadata saved in the repository. If I can find my DS_JOB notes, I'll post them but someone like Ray will probably wander by and pony up some search SQL. Eventually.
Worst case, export the project and do a string search in it for the hashed file's name.
Worst case, export the project and do a string search in it for the hashed file's name.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Premium Member
- Posts: 376
- Joined: Sat Jan 07, 2012 12:25 pm
- Location: Piscataway
Why should this be the last resort? Any specific reasons?chulett wrote:...
Worst case, export the project and do a string search in it for the hashed file's name.
Jerome
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
[shrug] No, not really.
I guess just because it involves exporting the entire project, searching for a string and then working back up from there to find the name of the job. Getting a query against DS_JOBOBJECTS would be much more better.
Or as I've mentioned many times over the years, we automated a process that took the daily project exports and then used jobs we adapted from Chuck Smith's website to parse them into database tables. Then you can easily use SQL to find things of this nature.
I guess just because it involves exporting the entire project, searching for a string and then working back up from there to find the name of the job. Getting a query against DS_JOBOBJECTS would be much more better.
Or as I've mentioned many times over the years, we automated a process that took the daily project exports and then used jobs we adapted from Chuck Smith's website to parse them into database tables. Then you can easily use SQL to find things of this nature.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers