Page 1 of 1
Job not showing up in Director
Posted: Wed May 23, 2012 2:36 pm
by Cheintze
We have a sequence job that was designed in DS Designer named D320_Court_Load_Seq. It consists of 3 jobs -- 1 to extract, one to load to a staging table (in DB2), then the 3rd loads to our production DB2.
The problem is that the 2nd job is not showing up at all in DS Director. It is there in the designer - and when I try to run the job, I get the following error:
Error calling subroutine: DSR_EXECJOB (Action=5); check DataStage is set up correctly in project DB2_DW
(Subroutine failed to complete successfully (30107))
I'm not sure what to do - or what I'm missing and I'm pretty inexperienced, so any help would be appreciated. The more detailed, the better!
Thanks in advance,
Clay
Posted: Wed May 23, 2012 4:32 pm
by ray.wurlod
Are you able to re-compile the 2nd job in Designer? If so, does it then show up in Director?
Error calling subroutine: DSR_EXECJOB (Action=5);
Posted: Thu May 24, 2012 5:37 am
by Cheintze
Yes, I was able to recompile the 2nd job and it shows up now in Director, however when I try to run the job, I'm still getting the same error message.
Error calling subroutine: DSR_EXECJOB (Action=5); check DataStage is set up correctly in project DB2_DW
(Subroutine failed to complete successfully (30107))
Posted: Thu May 24, 2012 7:41 am
by chulett
Sounded like your repositories (there are two) were not in sync and may still not be... that or there is some element of corruption there. Best to get your official support provider involved for help with that.
Re: Job not showing up in Director
Posted: Thu May 24, 2012 9:50 am
by PhilHibbs
Cheintze wrote:Error calling subroutine: DSR_EXECJOB (Action=5); check DataStage is set up correctly in project DB2_DW
(Subroutine failed to complete successfully (30107))
Usually when I get "check DataStage is set up correctly", it is cured by quitting the client program and connecting again. If this is not fixing it for you, then indeed you have a problem in your project, you could try bouncing the DataStage engine, failing that as Craig says, get on the red telephone.
Posted: Thu May 24, 2012 1:12 pm
by rmcclure
You can also try exporting the job, deleting it from Designer then re-importing.
Posted: Thu May 24, 2012 1:59 pm
by rprajput
As mentioned by Phil, quitting the client and reconnecting should resolve the issue but also make sure that you are not running out of memory on the box.
Posted: Thu May 24, 2012 5:13 pm
by SURA
Contacting the Service Provider is the best way. Though you can give a try by reindex may solve some time!