DSJOBS table not being populated when using reorting assista
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 18
- Joined: Wed Feb 14, 2007 10:04 am
DSJOBS table not being populated when using reorting assista
Could some one please help I am trying to export DSJOBS data from the a project to the Oracle schema created from the Reporting directory when DS was installed.
I am able to view table definitions and alike but no Job data from DSJOBS, do I need to turn on an environment variable to enable the information for a job to be captured ?
I think I have bitten of more than I can chew at the moment!
Thanks
B
I am able to view table definitions and alike but no Job data from DSJOBS, do I need to turn on an environment variable to enable the information for a job to be captured ?
I think I have bitten of more than I can chew at the moment!
Thanks
B
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Reporting Assistant was deprecated in version 5.2. However, jobs should be able to be moved to the reporting database. Are you certain you had the Jobs check box selected during the Update phase?
Note also that Reporting Assistant does not work reliably with job sequences, shared containers or (in some cases) parallel jobs.
Note also that Reporting Assistant does not work reliably with job sequences, shared containers or (in some cases) parallel jobs.
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.
-
- Premium Member
- Posts: 18
- Joined: Wed Feb 14, 2007 10:04 am
Ray,
I have checked and double checked that the jobs box was ticked and all jobs were selected, the update takes seconds, which makes me dubious that there is any data to Update. Is there enything that needs to be turned on inorder for when the jobs run to gather the meta data?
Also you mention that the Reporting Assistant is deprecated and htere are other ways would you be able to point me in the right direction as I am struggling to use the search facility as I don't 100% know what to search for.
Many thanks,
B
I have checked and double checked that the jobs box was ticked and all jobs were selected, the update takes seconds, which makes me dubious that there is any data to Update. Is there enything that needs to be turned on inorder for when the jobs run to gather the meta data?
Also you mention that the Reporting Assistant is deprecated and htere are other ways would you be able to point me in the right direction as I am struggling to use the search facility as I don't 100% know what to search for.
Many thanks,
B
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Depends. What do you want to report? The intention (in deprecating the Reporting Assistant) was to force customers to use MetaStage for metadata reporting. With version 8 this has been replaced again, with some of the metadata reporting capabilities embedded in the metadata analysis server and more extensive functionality available through Metadata Workbench.
Then there are the various reports that folks here at DSXchange have developed querying the Repository database directly.
Then there are the various reports that folks here at DSXchange have developed querying the Repository database directly.
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.
-
- Premium Member
- Posts: 18
- Joined: Wed Feb 14, 2007 10:04 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Usage Analysis will do some of those. You might also like to use/adapt the tools downloadable from Chuck Smith's or Kim Duke's websites.
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.
DwNav uses Reporting Assistant data. I plan on uses the DataStage repository tables directly for version 8. Reporting Assistant does not extract PX job metadata or sequences. I extracted sequences to Reporting Assistant tables for DwNav. It was too much work to extract PX jobs when it may not work for future versions of DataStage. I think going forward browsing metadata repository tables directly makes more sense.
Parameter Navigator does extract and update PX job parameters but it may need to change for version 8. I have not tested it yet. Have not seen a need to convert to version 8 yet.
Parameter Navigator does extract and update PX job parameters but it may need to change for version 8. I have not tested it yet. Have not seen a need to convert to version 8 yet.
Mamu Kim
-
- Premium Member
- Posts: 18
- Joined: Wed Feb 14, 2007 10:04 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Try selecting a Table Definition and running a Usage Analysis on that.
It will show the jobs that reference any column(s) in that table definition.
You might also try selecting a Job that you know is invoked from a job sequence.
It will show the jobs that reference any column(s) in that table definition.
You might also try selecting a Job that you know is invoked from a job sequence.
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.