You found the right post. You need to work this post in conjunction with a list of all the parameters within a job. This could take a search for each parameter. Lot of work.narasimha wrote:Did an exact search found 75 matches for @RECORD.
You can find a nice explaination here
Regarding DSUtility
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
How exactly?DSguru2B wrote:Only if you were sitting on a unix box. This would have been much easier.
Everything on DataStage on UNIX is available on DataStage on Windows.
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.
You may need to first list of parameters that been used. And you will need to loop through each parameter and find the list of jobs and stages using the query that Kim has used, instead of finding it for PROJDEF.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
-
- Participant
- Posts: 228
- Joined: Tue Oct 03, 2006 7:08 pm
-lparam will give you a list of all the parameters. So paraminfo is what you want now? You are seriously confusing.
IF you want to do this at the OS level, create a dos batch job that reads from a list, loops through the dsjob -paraminfo command and passes the parameter read from the list one by one. Or do as Kumar advised above.
IF you want to do this at the OS level, create a dos batch job that reads from a list, loops through the dsjob -paraminfo command and passes the parameter read from the list one by one. Or do as Kumar advised above.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
-
- Participant
- Posts: 228
- Joined: Tue Oct 03, 2006 7:08 pm