Datastage: Delete executable (parallel job)

jusami25 · Post by **jusami25** » Thu Nov 22, 2007 7:21 am

Hi All,

We have different Datastage environments. We have an error that is only happening in one environment (production). We think it may be due to a corrupted job.

Based on this, we have tried to recompile the job, and it did not work. We have tried also to import the job from the previous stage (pre-production) that it is a mirror from production, and it didn't work neither.

Does anybody have any idea about how we can delete the executable?

Thanks a lot in advance.

Maveric · Post by **Maveric** » Thu Nov 22, 2007 7:44 am

What happened when you tried to import the job? Did it give you an error or a warning. Posting that here might help. If the design time info is not imported then you wont be able to open the job designer but still be able to delete it from designer. You can delete from manager. Right click on the job name and select delete.

chulett · Post by **chulett** » Thu Nov 22, 2007 8:12 am

jusami25 wrote:Based on this, we have tried to recompile the job, and it did not work. We have tried also to import the job from the previous stage (pre-production) that it is a mirror from production, and it didn't work neither.

Simply saying "it didn't work" does help us help you at all. What didn't work about it? What errors did you get?

Did you try a Force compile of the allegedly corrupted job?

chulett · Post by **chulett** » Thu Nov 22, 2007 8:54 am

[sigh]

Saying "the run is bad" isn't any more helpful.

Suggestion: stop focusing on this "delete the executable" topic. Take a step back and explain in detail what the heck "the run is bad" means. What is different about the environment where you are having problems?

You do yourself a great disservice by obsessing on a perceived solution when you don't even know (or can articulate) what is wrong.

ray.wurlod · Post by **ray.wurlod** » Thu Nov 22, 2007 2:48 pm

What's different between the two environments? ("Nothing" is clearly not the correct answer.)

Please post the precise error messages that the job generates when run in the second environment.

keshav0307 · Post by **keshav0307** » Sat Nov 24, 2007 8:57 am

DELETE FROM DS_JOBS WHERE JOBNAME='<jobname>'

chulett · Post by **chulett** » Sat Nov 24, 2007 9:12 am

Umm... that will delete a wee bit more than just the executable.

ray.wurlod · Post by **ray.wurlod** » Sat Nov 24, 2007 12:27 pm

DataStage jobs do not just comprise a single executable component. There are configuration records, status records, log records for run time, and of course design time components also stored in Repository database tables as well.

Why, particularly, do you want to delete the executable? Without seeing the exact error messages you received, it's impossible to ascertain whether the executable is at fault. One way would be to delete the entire job (say from Designer) and then import just the job design components.

Deleting the record from DS_JOBS without deleting all the other components is singularly bad advice.

DSXchange

Datastage: Delete executable (parallel job)

Datastage: Delete executable (parallel job)

Re: Datastage: Delete executable (parallel job)