A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.
Moderators: chulett, rschirm, roy
-
PrachiTrivedi
- Participant
- Posts: 3
- Joined: Thu May 14, 2009 12:45 pm
Post
by PrachiTrivedi »
Hi ,
We are facing the following issue when we try to stop the jobs before shutting down the dsengine .
The jobs are already in running status and we are trying to stop them
Could anyone let us know why this can happen
Status code = 0
Error stopping job
Status code = -99 DSJE_REPERROR
Status code = 0
Status code = 0
Status code = 0
Error stopping job
Status code = -99 DSJE_REPERROR
Status code = 0
Error running job
Status code = -2 DSJE_BADSTATE
-
ArndW
- Participant
- Posts: 16318
- Joined: Tue Nov 16, 2004 9:08 am
- Location: Germany
-
Contact:
Post
by ArndW »
What kind of jobs are you talking about - sequences might give different types of errors than server or PX jobs.
-
chulett
- Charter Member
![Charter Member Charter Member](./images/ranks/charter_member%s.gif)
- Posts: 43085
- Joined: Tue Nov 12, 2002 4:34 pm
- Location: Denver, CO
Post
by chulett »
And you are 'stopping' them how? Where does the 'using scripts' part come into the picture exactly?
-craig
"You can never have too many knives" -- Logan Nine Fingers
-
Chhotu
- Participant
- Posts: 1
- Joined: Tue Nov 18, 2008 2:27 pm
Post
by Chhotu »
The jobs are stopped using a shell script ..the script is fired from a unix server with command lines to stop the job
-
invincibleDeepak
- Participant
- Posts: 14
- Joined: Sun Jun 07, 2009 12:26 pm
- Location: Mumbai
Post
by invincibleDeepak »
Try to stop the jobs from root login for datastage engine if not doing so.
regards
Deepak Kumar
Datastage Developer
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
-
Contact:
Post
by ray.wurlod »
What actual commands are you using to request the jobs to stop. "Scripts" is not a useful start point for diagnosis.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.