I am running up to 12 concurrent instances of a parallel job. These are kicked off from CA Autosys (scheduler) and all logs need to be written out to files. How do I get the log summary and details of 1 specific instance/invocation? When I use dsjob -logsum to get the log summary, it returns the logs for all invocations that were running at that time. It doesn't matter what I specify - job or jobInvocationId.
Running:
dsjob -run -mode NORMAL -jobstatus myproject myjob.site1
dsjob -run -mode NORMAL -jobstatus myproject myjob.site2
... etc.
Log Summary - all retrieve exact same results:
1) dsjob -logsum myproject myjob
2) dsjob -logsum myproject myjob.site1
3) dsjob -logsum myproject myjob.site2
So... how do I get the log info for just site1? If I look in Director, it shows all logs for the job, grouped by invocation and even color coded to a certain extent. Obviously, DS know how to link an event not just to a job, but to a specific invocation because that's what it's doing in Director. Now, how do I do this from the command line?
Retrieving log sum/dtl of a single invocation
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Welcome aboard! :D
I'm not sure you can do this with dsjob as supplied. Director client sends a request that constrains on invocation ID, but I'm not aware that this capacity exists in dsjob.
You can view source code for dsjob in the Server Job Developer's Guide (servjdev.pdf), since dsjob was originally an example program to show how to use the DataStage C API. In a quick scan through that code I could not see any way to constrain on invocation ID.
I'm not sure you can do this with dsjob as supplied. Director client sends a request that constrains on invocation ID, but I'm not aware that this capacity exists in dsjob.
You can view source code for dsjob in the Server Job Developer's Guide (servjdev.pdf), since dsjob was originally an example program to show how to use the DataStage C API. In a quick scan through that code I could not see any way to constrain on invocation ID.
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.
FYI, the DS BASIC APIs that retrieve log file rows from the main or individual instance job have the same issue. It returns all log rows for all instances, you'll have to loop thru all rows and parse for your jobname.invocationid rows.
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