usage of "dsjob -logdetail" for multi instance job

ssunda6 · Post by **ssunda6** » Wed Sep 26, 2007 10:47 pm

Hi,

We are trying to capture logs of jobs into a table periodically.

The logic used is:
-dsjob -logsum -type STARTED <proj name> <job name>
-compare timestamps and get the required event ids.
-Pass them to "dsjob -logdetail" to get the required log.

But "logdetail" is fetching log entries of other invocation job when the job is of multi-instance type.

I have searched for a solution in posts. But couldnt find much.

Can we eliminate log of other invocations and get only the required log? ( using logdetail)

palmeal(a participant) mentioned in the follwing post:

http://dsxchange.com/viewtopic.php?t=96 ... 03193ed431

that they used .$DSN information to filter out the log from "logdetail" for multi instance jobs. I dont have idea on this. If anyone has idea, plz help.

Any other solutions would also help.

Regards,
ssunda.

chulett · Post by **chulett** » Thu Sep 27, 2007 7:30 am

Are you including the appropriate invocation id in the <job name> you use?

ssunda6 · Post by **ssunda6** » Wed Oct 03, 2007 2:46 am

Chulett,

I am using the appropriate invocation id.

The problem is, lets say for job "A", there are 2 instances - "a" and "b". And both instances ran at the same time.

The logs for both instances is maintained in "A" in the directory log .
Since both the instaces ran at same time, the log entries will be mixed up with both "a" and "b" job's logs.

So, when I am using "dsjob -logdetail" and passing the 'start' and 'end' event ids, though a particular instance name is specified, it is fetching even the log entries of other instance. It is not checking if all event ids belong to the same instance. Once start and end event ids are specified to -logdetail, it is fetching all event ids between them whether they belong to the same instance or not.

Is this a bug or can we filter out the correct log entries belonging to a particular instance.

Regards,
ssunda.

chulett · Post by **chulett** » Wed Oct 03, 2007 6:52 am

I don't believe this is a bug and just wanted to be sure you'd tried it with the Invocation Id. Honestly, this isn't something I've tried to do up to this point but since the Director can separate the log entries when viewing them, I'm sure it's possible, just not sure how.

If I get a chance, I'll play and see what (if anything) I can come up with. In the meantime, I would think others have already cracked this particular nut...

ssunda6 · Post by **ssunda6** » Wed Oct 03, 2007 7:00 am

Thanks Chulett.

"dsjob -logsum" is giving correct log belonging to that particular instance . Only "dsjob -logdetail" is giving this problem.

Has anyone else faced same problem with logdetail? If yes, please provide inputs on how this can be solved.

DSguru2B · Post by **DSguru2B** » Wed Oct 03, 2007 7:56 am

Dont you have to provide the event id for the -logdetail option. If you dont provide anything, it will take the last event id. Are you providing the event id(s)?

ssunda6 · Post by **ssunda6** » Thu Oct 04, 2007 7:11 am

DSguru2B,

I am providing both starting and ending event ids (whose log is to be fetched).