DataStage Director error
Moderators: chulett, rschirm, roy
DataStage Director error
Hi all,
I am in great need , pls help me.
I have scheduled to run jobs in production.
Now for the following couple of days the below error
is coming if i open the Director
Error calling subroutine: DSR_EXECJOB (Action=5); check DataStage is set up correctly in project AHAKORPROD
(Subroutine failed to complete successfully (30107))
and because of that the main seq is aborting and data is not migrating
The clients are after me
If i view seq log the below waring is coming and nothing else
Job control process(pid 4464) has failed
If i view the job it is as error getting job status
I would be very very thankful , if someone pls help me solving this problem
Thank you very much in advance
I am in great need , pls help me.
I have scheduled to run jobs in production.
Now for the following couple of days the below error
is coming if i open the Director
Error calling subroutine: DSR_EXECJOB (Action=5); check DataStage is set up correctly in project AHAKORPROD
(Subroutine failed to complete successfully (30107))
and because of that the main seq is aborting and data is not migrating
The clients are after me
If i view seq log the below waring is coming and nothing else
Job control process(pid 4464) has failed
If i view the job it is as error getting job status
I would be very very thankful , if someone pls help me solving this problem
Thank you very much in advance
First suggestion is always to search the forums for your error, more than likely you're not the first person to have the problem. For you, see if an exact search for "Error calling subroutine: DSR_EXECJOB (Action=5)" turns up anything helpful.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Re: DataStage Director error
I was having a similar error and it seemed the job was corrupted. I made a copy of the job, made sure it worked then deleted the old one and re-named the new one with the old-name and everything was finemajor wrote:
Error calling subroutine: DSR_EXECJOB (Action=5); check DataStage is set up correctly in project AHAKORPROD
(Subroutine failed to complete successfully (30107))
Re: DataStage Director error
rmcclure wrote:I was having a similar error and it seemed the job was corrupted. I made a copy of the job, made sure it worked then deleted the old one and re-named the new one with the old-name and everything was finemajor wrote:
Error calling subroutine: DSR_EXECJOB (Action=5); check DataStage is set up correctly in project AHAKORPROD
(Subroutine failed to complete successfully (30107))
Hi,
I did the same thing it worked as a job,
but failed again while i ran it through seq, giving same error.
Pls any other suggestions
Re: DataStage Director error
rmcclure wrote:I was having a similar error and it seemed the job was corrupted. I made a copy of the job, made sure it worked then deleted the old one and re-named the new one with the old-name and everything was finemajor wrote:
Error calling subroutine: DSR_EXECJOB (Action=5); check DataStage is set up correctly in project AHAKORPROD
(Subroutine failed to complete successfully (30107))
Hi,
I did the same thing it worked as a job,
but failed again while i ran it through seq, giving same error.
Pls any other suggestions
Re: DataStage Director error
rmcclure wrote:I was having a similar error and it seemed the job was corrupted. I made a copy of the job, made sure it worked then deleted the old one and re-named the new one with the old-name and everything was finemajor wrote:
Error calling subroutine: DSR_EXECJOB (Action=5); check DataStage is set up correctly in project AHAKORPROD
(Subroutine failed to complete successfully (30107))
Hi,
I did the same thing it worked as a job,
but failed again while i ran it through seq, giving same error.
Pls any other suggestions
then there is one good option you are having..
delete the sequnce and re-create the new one and attach the job again !
anyways ..if you are creating the job again and it is working fine..it seems to be weird error then..!
once job is failed using the sequence, have you tried running it independetly..is it still working..?
If it is still working, then you need to check with your sequnce propeties..
attach the job again..
and if it is not working..
then you know how to make it running....!
hope this helps...
----------
MK
delete the sequnce and re-create the new one and attach the job again !
anyways ..if you are creating the job again and it is working fine..it seems to be weird error then..!
once job is failed using the sequence, have you tried running it independetly..is it still working..?
If it is still working, then you need to check with your sequnce propeties..
attach the job again..
and if it is not working..
then you know how to make it running....!
hope this helps...
----------
MK