I am trying to trap the log details from a parallel job. When I issue the command
dsjob -logdetail <project> <job_name>
The following comes back:
Invalid arguments: dsjob -logdetail [-useid] <project> <job|jobid> <first event id> [<last event id>]
Status code = -9999 DSJE_DSJOB_ERROR
Going into director and pulling out the event ids results in a valid command execution, but why can't DS just pull this info itself as a default (which seems to be implied by a recent thread about dsjob and "wave 0")?
Issuing dsjob -logdetail
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 17
- Joined: Wed Apr 16, 2008 6:39 am
- Location: Arlington, VA
-
- Participant
- Posts: 407
- Joined: Mon Jun 27, 2005 8:54 am
- Location: Walker, Michigan
- Contact:
Re: Issuing dsjob -logdetail
Yes, that's because I have a different version of dsjob -logdetail which supports an option called waves.Offshored2002 wrote:I am trying to trap the log details from a parallel job. When I issue the command
dsjob -logdetail <project> <job_name>
The following comes back:
Invalid arguments: dsjob -logdetail [-useid] <project> <job|jobid> <first event id> [<last event id>]
Status code = -9999 DSJE_DSJOB_ERROR
Going into director and pulling out the event ids results in a valid command execution, but why can't DS just pull this info itself as a default (which seems to be implied by a recent thread about dsjob and "wave 0")?
dsjob -logdetail <project> <job_name>
or
dsjob -logdetail <project> <job_name> -wave 0
-- Gives the latest log report.
dsjob -logdetail <project> <job_name> -wave -1
-- Gives the previous log report.
dsjob -logdetail <project> <job_name> -wave -2
-- Gives the log report before the previous.
Thanks.
-
- Participant
- Posts: 17
- Joined: Wed Apr 16, 2008 6:39 am
- Location: Arlington, VA
-
- Participant
- Posts: 407
- Joined: Mon Jun 27, 2005 8:54 am
- Location: Walker, Michigan
- Contact: