The job should be a job and not a sequence. The problem of status is even if the job is getting aborted the status still returns as 0 which is making difficult to get the status of the job. I want that for those runs for which the status is aborted the status should be something else which helps me in detect the error.OddJob wrote:Place the Job on a Sequence and call the Sequence from dsjob.
If you double-click on the Job Activity on the Sequence and select the 'Job' tab you can choose 'Reset if required, then run' from the 'Execute action' dropdown - your job will always run even if it is in status 'Aborted'.
1) Use the -jobstatus dsjob option as noted. The behaviour of it is well documented.pravin1581 wrote:1) How can i trap the status of the job thru dsjob command. 2) If any job gets aborted then is it necessary to compile the job in the designer before running the dsjob command ?
By detailing the use of a sequence I was trying to show you how to re-run an aborted job without having to compile or reset the job.If any job gets aborted then is it necessary to compile the job in the designer before running the dsjob command ?
I have tried using the option mode RESET, it resets the job but the job is not running.The command that i have tried is as follows:chulett wrote:1) Use the -jobstatus dsjob option as noted. The behaviour of it is well documented.pravin1581 wrote:1) How can i trap the status of the job thru dsjob command. 2) If any job gets aborted then is it necessary to compile the job in the designer before running the dsjob command ?
2) No. It does need to be RESET however and there is a specific dsjob 'run mode' for that. Your wrapper script needs to check for a condition requiring a reset and do so before running the job.
Code: Select all
dsjob -run -mode RESET projectname jobname
I have included -jobstatus in the command and it is working fine. It returns 2 if there is any warning in the job else 3 if the job is aborted and 1 if it is finished w/o any warning. But the problem of compiling still persists, it has to be compiled if it is getting aborted.ray.wurlod wrote:Any messages generated?
What is the exit status of dsjob?
Include -jobstatus option and post whether that makes a difference.
In case of job sequence i am aware of this property ("reset if required, then run") but i want the same in case of a job and not job sequence.ray.wurlod wrote:It does NOT have to be re-compiled if it aborted. It only needs to be reset. You can accomplish this with dsjob -run -mode RESET ...
You can also accomplish it automatically ("reset if required, then run") if running your job from a job sequence - the job sequence can be started from dsjob.
So the only way out is to recompile the job from the designer and then run it using dsjob command.ArndW wrote:There is no "reset if required" from the command line, but you can always just force a reset and then run the job.