Hi ,
I want to capture log file that is generated after executing a job and save it to a particular location. Please advise me how to go for this. do we have any functions to catch this.
thanks in advance.
ram...
capture error log
Moderators: chulett, rschirm, roy
Search the forum, we've covered using the DS BASIC APIs in a user-written after-job routine to dump out log messages generated in the run to a text file. In fact, this question gets asked almost every day.
Kenneth Bland
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
I like the SQL solutions. I do not like the API solutions for logs and row counts. Row counts are easiest with dsjob -report. IMHO. The API works best for starting and stopping jobs.
I just wrote a routine which will change these SQL statements into html. I will post it soon. I want to tie this to an email so you can email the last run's log when a job fails. Most email programs will display html. If a sequence fails then it should find the first failed job and mail that log. It would be easy to ftp html files these to a web server. I am not sure I would ever do that, others will.
I still do not know why people want these log files on successful runs. Please explain this to me.
I just wrote a routine which will change these SQL statements into html. I will post it soon. I want to tie this to an email so you can email the last run's log when a job fails. Most email programs will display html. If a sequence fails then it should find the first failed job and mail that log. It would be easy to ftp html files these to a web server. I am not sure I would ever do that, others will.
I still do not know why people want these log files on successful runs. Please explain this to me.
Mamu Kim