DSXchange

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")?

Your syntax is invalid, which the error pointed out. The -logdetail function requires at least a 'first event id' and optionally a 'last event id'.

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")?

Yes, that's because I have a different version of dsjob -logdetail which supports an option called waves.

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.

Thanks, I feared that was the answer. Not terribly useful to have to go get event ids from Director right now.

Offshored2002 wrote:Thanks, I feared that was the answer. Not terribly useful to have to go get event ids from Director right now.

I had this feature rolled forward into 7.5.3. Can you upgrade to version 7.5.3?

Hmmm... you get the event id by using -logsum first, not by looking it up in the Director.