log summary past a date

mystuff · Post by **mystuff** » Fri Dec 21, 2007 3:03 pm

dsjob -logsum project job

gives the log information for a job, but it also fetches earlier logs as well.

Is it possible to specify somewhere to obtain logs of a job only after specified period of time or say logs after so and so date.

jdmiceli · Post by **jdmiceli** » Fri Dec 21, 2007 3:47 pm

Read the documentation or search DSGetLogSummary or DSGetLogEntry. You might be able to get what you are looking for from one or both of these if I understand your question correctly.

Merry Christmas!

mystuff · Post by **mystuff** » Mon Dec 24, 2007 8:46 am

I am writing a script, so I am looking how to do it using "dsjob -logsum". I didn't see any option in this command. Is there anyway to do it?

ArndW · Post by **ArndW** » Mon Dec 24, 2007 9:01 am

mystuff - as you've already guessed, the dsjob -logsum command will not let you filter the output; which is why jdmiceli suggested an alternate method.
I don't have a version of 7 to play with, but I think you might be able to use dsjob -jobinfo to get the message number or start date or wave number of the last run and then use the -logdetail option with the wave number or message number to retrieve that information.

chulett · Post by **chulett** » Mon Dec 24, 2007 9:11 am

The documentation shows the two options the command supports: -type to control what message types you want and -max to limit the number of records returned.

You'd need to pull a log summary and then use that to determine what information you want, what range of message numbers is needed. Then use the -logdetail option to pull the detailed logs for the rang in question.

chulett · Post by **chulett** » Mon Dec 24, 2007 9:12 am

D'oh... this is what happens when you get distracted and forget to click 'Submit' for 10 minutes.

mystuff · Post by **mystuff** » Mon Dec 24, 2007 9:58 am

ArndW

I don't have a version of 7 to play with, but I think you might be able to use dsjob -jobinfo to get the message number or start date or wave number of the last run and then use the -logdetail option with the wave number or message number to retrieve that information.

I don't see any option of wavenumber or message number in -logdetail. Am I missing something?

ArndW · Post by **ArndW** » Mon Dec 24, 2007 10:00 am

It is likely that you aren't missing anything, the -wave is probably a new option at Version 8.

mystuff · Post by **mystuff** » Mon Dec 24, 2007 10:05 am

Then don't I have any option using to filter out using datastage CL utilities

ArndW · Post by **ArndW** » Mon Dec 24, 2007 10:12 am

No, it seems not. But you can use the DSGet...() routines from a DataStage job to create exactly the type of log file you want; you can call this job using the dsjob command and then parse the output file as desired.

chulett · Post by **chulett** » Mon Dec 24, 2007 10:36 am

Not sure what you mean - the last parameter to the -logdetail function is the entry number you want. So you get the range from the summary function and then iterate through the range and pull all of the detail entries.

ray.wurlod · Post by **ray.wurlod** » Mon Dec 24, 2007 2:42 pm

Source code for dsjob is in the manuals. You can adapt that you suit your own particular needs.

Why not create a server job to read (and filter, based on job parameters) a job log (the name of which is given as a job parameter)?

jdmiceli · Post by **jdmiceli** » Thu Dec 27, 2007 8:25 am

You had mentioned that you were trying to do it from the command line, so what if you ran the dsjob -logdetail and piped it to a text file then used Perl or whatever to parse that file for what you are looking for.

Just a thought,

jdmiceli · Post by **jdmiceli** » Thu Dec 27, 2007 8:26 am

You had mentioned that you were trying to do it from the command line, so what if you ran the dsjob -logdetail and piped it to a text file then used Perl or whatever to parse that file for what you are looking for.

Just a thought,

DSguru2B · Post by **DSguru2B** » Thu Dec 27, 2007 10:33 am

dsjob -lognewest will provinde the entry number. You can use that with the -logdetail option. It does'nt showup in help but it works. Atleast in 7.5.1A, it does.
You can save the entry number and use that entry number to get the log details after a certain date.
Say you want your script to generate logs for the last six days, save the entry number six days in advance and use that to get the log entry.