I have few multi-instance jobs which run for 1-2 min and finishes successfully.
Smetime this jobs keeps on running for hours and then we have to kill them and rerun.
Today again while job were running forever then I used dsjob command to get information of this job,I got below results -
bin/dsjob -jobinfo TestProj ABCTest.Id1
Job Status : RUNNING (0)Job Controller : not available
Job Start Time : Mon Dec 28 02:04:15 2009
Job Wave Number : 65
User Status : not available
Job Control : 0
Interim Status : NOT RUNNING (99)
Invocation ID : ABCTest
Last Run Time : Wed Dec 31 19:00:00 1969
Job Process ID : 9154730
Invocation List : djpIsdd
Status code = 0
Can someone tell me the difference between Job status and Interim Status .Looks like this info may be useful for me !!
Thanks
Job running forever
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 39
- Joined: Sun Apr 15, 2007 11:30 pm
Job running forever
"Books are as useful to a stupid person as a mirror is useful to a Blind person."
-
- Participant
- Posts: 39
- Joined: Sun Apr 15, 2007 11:30 pm
@chulett,Job is still running while i ran the command,in that case intrim status should also be as Running.
Nagarjuna,This job is reading a flat file,doing a look-up and loading into a Db2 table.
I do not understand what is happening with the job !!
Nagarjuna,This job is reading a flat file,doing a look-up and loading into a Db2 table.
I do not understand what is happening with the job !!
"Books are as useful to a stupid person as a mirror is useful to a Blind person."
No. Reread what I posted more carefully... and then put it from your mind as it won't help here. This kind of thing is typically a locking issue in the target database, have your DBA check when this occurs again.deepak.hsbc wrote:@chulett,Job is still running while i ran the command,in that case intrim status should also be as Running.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers