Can we export joblog to a file
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 106
- Joined: Thu Jun 08, 2006 8:51 am
Can we export joblog to a file
Hi All,
Can we export/save the joblog or job status to a file??
I want to use that file in some other application so that i can derive the elapsed time of the job and other details.
I just want to take the information about the job out of DataStage application...
Please reply... Thanks in Adv..
Regards
VC
Can we export/save the joblog or job status to a file??
I want to use that file in some other application so that i can derive the elapsed time of the job and other details.
I just want to take the information about the job out of DataStage application...
Please reply... Thanks in Adv..
Regards
VC
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
Re: Can we export joblog to a file
chitravallivenkat wrote:Hi All,
Can we export/save the joblog or job status to a file??
I want to use that file in some other application so that i can derive the elapsed time of the job and other details.
I just want to take the information about the job out of DataStage application...
Please reply... Thanks in Adv..
Regards
VC
I think u can use API function DSGetLogEntry to retrive log details and then redirect it to a file
Priyadarshi Kunal
Genius may have its limitations, but stupidity is not thus handicapped.
Genius may have its limitations, but stupidity is not thus handicapped.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You can use the Print dialog from Director (check Print To File).
You can create a DataStage job to do it.
You can create a routine using the DataStage API - depending on what you want you may need various of the DSGetLog... functions.
However, it's probable that most of the details you require are accessible from the API without accessing the log. Research the other DSGet...Info functions.
You can create a DataStage job to do it.
You can create a routine using the DataStage API - depending on what you want you may need various of the DSGetLog... functions.
However, it's probable that most of the details you require are accessible from the API without accessing the log. Research the other DSGet...Info functions.
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: 107
- Joined: Wed Sep 29, 2004 10:15 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Most of what you need is here - doesn't your Search button work?
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: 106
- Joined: Thu Jun 08, 2006 8:51 am
I have written two DataStage jobs that reproduce the Director log, and also the same details as shown in the Monitor window. Both of these are saved to CSV files on the Server. The files can then be FTP'd or whatever onto your PC.
Here are examples of the output:
Let me know if you would like a copy of the jobs.
Here are examples of the output:
Let me know if you would like a copy of the jobs.
No, the jobs are not automated, though can obviously be scheduled.
The Metrics job has the following parameters:
CATEGORY: Enter one or more categories here
PATH: Full path name to output csv file directory
FNAME: Output CSV file name
The Monitor Details job has the following parameters:
CATEGORY: EITHER: for report on one or more categories, enter them here
JOBNAME: OR: for report on single job only, enter job name here
PATH: Full path name to output csv file directory
FNAME: Output CSV file name
CATEGORY can be delimted by a comma, semicolon or space.
The logic is quite fun, and is primarily based on the contents of the RT_LOGnnnn Universe file. The DS_JOBS file is parsed for all jobs that meet the parameter criteria, then for each job selected the RT_LOG and RT_STATUS files are interrogated for the relevant details, and an array of the details is built.
Jobs that are running are ignored. Jobs running over midnight or for several days are catered for, as are multiple instances of jobs.
The array is then squirted out, a job at a time, as a semicolon-delimited file.
The Metrics job has the following parameters:
CATEGORY: Enter one or more categories here
PATH: Full path name to output csv file directory
FNAME: Output CSV file name
The Monitor Details job has the following parameters:
CATEGORY: EITHER: for report on one or more categories, enter them here
JOBNAME: OR: for report on single job only, enter job name here
PATH: Full path name to output csv file directory
FNAME: Output CSV file name
CATEGORY can be delimted by a comma, semicolon or space.
The logic is quite fun, and is primarily based on the contents of the RT_LOGnnnn Universe file. The DS_JOBS file is parsed for all jobs that meet the parameter criteria, then for each job selected the RT_LOG and RT_STATUS files are interrogated for the relevant details, and an array of the details is built.
Jobs that are running are ignored. Jobs running over midnight or for several days are catered for, as are multiple instances of jobs.
The array is then squirted out, a job at a time, as a semicolon-delimited file.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: