Folks;
On my production box, I have just previlages at unix level to log files direcory and scripts file directory, I do not have access to Designer or Dictor to check the periodical speed at which my data is being loaded,
is there any way Could I check from unix level
thanks
Monitoring the job from unix
Moderators: chulett, rschirm, roy
Monitoring the job from unix
RRCHINTALA
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
What do you mean by "log files directory"? If this is the DataStage logs, they are tables and they are in the DataStage project directory. If you have permission here then, theoretically, you could monitor your jobs.
However, this would require knowledge of the internal workings of how DataStage records row counts and other periodic process information (such as status of jobs and active stages). Such knowledge is neither published nor in the public domain. So I expect the honest answer for you is NO.
If your database loader allows you to monitor loads, then perhaps you can use this. For example, if you force the loader to report every N rows, then you could watch it's log file using tail -f (which keeps the file open). If it's Red Brick, the same "keep open" technique can be used with the rblogview command.
However, this would require knowledge of the internal workings of how DataStage records row counts and other periodic process information (such as status of jobs and active stages). Such knowledge is neither published nor in the public domain. So I expect the honest answer for you is NO.
If your database loader allows you to monitor loads, then perhaps you can use this. For example, if you force the loader to report every N rows, then you could watch it's log file using tail -f (which keeps the file open). If it's Red Brick, the same "keep open" technique can be used with the rblogview command.
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.