Bad state not throwing error till stopping unix process

anjan.k · Post by **anjan.k** » Sat Mar 06, 2010 9:55 am

Hi,
I have few jobs invoking from unix box,out of 20 jobs one or other jobs once after invoking from unix they are just sitting in Has been reset state and not start running from the there,once i killed the unix process then it throws below error else script keeps hanging for long time and it never completes.Once we kill the process and restarts ,it will run fine,for a temp solution we are just killing the process and restarting the job.

Status code = 0
Error running job

Status code = -2 DSJE_BADSTATE

Status code = 0
Job Status : RESET (21) Job Controller : not available Job Start Time : Sat Mar 6 02:48:39 2010 Job Wave Number : 0 User Status : n\
ot available Job Control : 0 Interim Status : NOT RUNNING (99) Invocation ID : not available Last Run Time : Sat Mar 6 02:48:40 201\
0 Job Process ID : 0 Invocation List : CSEJB0013V Job Restartable : 0

Can you please help me out.

regards,
Anjan

ArndW · Post by **ArndW** » Mon Mar 08, 2010 5:10 am

If the job is not running and in a reset state, what process are you killing (which should not normally be done)? Have you tried resetting the job from the command line?

anjan.k · Post by **anjan.k** » Mon Mar 08, 2010 7:16 am

actually when i go and check in director it used to be in has been reset state only .It is daily job once after kill the unix process and run it will go through fine and will come to finished state.But when the next day it starts again it will go to has been reset state and doesnt run from there and unix process get hung.

ArndW · Post by **ArndW** » Mon Mar 08, 2010 7:54 am

The first thing is never to use kill from UNIX, particularly 'kill -9', unless there are no other options. In your case I'm still very confused as to what the situation and/or problem is.

Are you, or are you not, using RESET in the job call? Somehow your job must be getting from state 'finished' to state 'reset'.