Does any one have idea of auditing the datastage job in the job level for no.of records extracted, transformed, inserted or rejected. I have been using @INROWNUM which is not a workaround.
Thank you.
Job level Auditing in Datastage 8.1
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The DataStage API functions remain viable in version 8.1; you can download ETLstats and adapt its techniques.
If you have it and you are generating operational metadata, then you can use Metadata Workbench to perform these analyses.
HOWEVER, to have this work generically, you need a consistent naming convention for those links that read, write, handle rejects, read by key, and other ("transformation?").
If you have it and you are generating operational metadata, then you can use Metadata Workbench to perform these analyses.
HOWEVER, to have this work generically, you need a consistent naming convention for those links that read, write, handle rejects, read by key, and other ("transformation?").
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.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The after-job subroutine could look after that. But why write code when you have a perfectly good GUI? Certainly the after-job subroutine can capture the data, but it could also run a small job to write them into your audit table.
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.