DSXchange

When I try to delete a job from Job Repository, I get the following message:

Cannot open executable job file RT_CONFIG471

I tried compiling the job but was unable to do it. Following is the message.

Error calling subroutine: DSR_JOB (Action=5); check DataStage is set up correctly in project METL_DEV_R1
(Subroutine failed to complete successfully (30107))

How can I resolve this?

Hi Durga Prasad,
Try log out and log in again and check if you could do that.
It could be as you faced few days back. Check for the space available under /tmp or check the permission to the group or the user id, if it has been changed recently.

Hi Kumar,

Thanks for the reply. But there is sufficient tmp space and I am able to delete other jobs without any issues with the same user id. Is there any other possibility why this might be happening?

Thanks,

Hmm... Try to create a copy of the same job and Delete it. If that works the underlying config file and pointers might be corrupted for that job. You can then try an ugly approach by deleting from DS_JBOS and DS_JOBOBJECTS and if you find the RT_CONFIG471 and its log file you can delete it from unix.

Check the permission for RT_CONFIG471 in your project directory, by any change if that is been created by other user and if your current id dont have access to that file.

I have a similar problem where we seemed to be able to delete a job partially, but the job still displays in Manager, but not Director. When trying to delete the first time, Manager froze. From then on, attempting to delete results in this error message:
Cannot open executable job file RT_CONFIG806

the job failed to compile in Designer.
Error calling subroutine: DSR_JOB (Action=5); check DataStage is set up correctly in project OLYMPIC_S_CT
(Subroutine failed to complete successfully (30107))

The unix directories exist:
$ ls -ld *806*
drwxrwsr-x 2 koky dstage 4096 Jan 10 10:15 DS_TEMP806
drwxrwsr-x 2 koky dstage 4096 Jan 10 10:35 RT_SC806

Is there a uvsh command that I can use to delete the job from the repository files?

You may not completely delete a job because someone was in a unix directory for a supporting file, or if there were locks or processes still accessing those files. Now that you have a partially deleted job, your repository may show weird results.

You may need to use the DS.TOOLS menu to cleanup your project. Make sure you have everything exported that is valuable to you. Get everyone out and use the repair repository and reindex features under DS.TOOLS. The easiest way to make sure a project is clean is to create a new project and work out of there.

Durga Prasad,

I had a similar error message and this is what I did.

Logged on to Director - Job menu - Cleanup Resources.

On Cleanup Resouces Dialog box click "Show All" under "Process" and "Locks".

Select the PID# of the job and click "Logout". Click "Refresh"

Logout of Director and Designer. Log back in and try to delete.

HTH

I've already rebuilt the indexes on the project using the Rebuild Repository indices (option #2) in DS.TOOLS. Is there anything else I can try before moving the jobs to a new project?

By the way, I already tried cleared all the locks, and have now rebooted, but I still can't delete the job.

What about option #4 to Check Integrity of Job Files?

It's not enough to check disk space "now" - you must check while the job is running. You can have lots of free space "now" that is all consumed while the job is running.

From the Administrator client, at a time when you have exclusive access to the project, execute the command DS.CHECKER (this is the same as option #4 on the DS.TOOLS menu, but does not require you to log in on the server).

kcbland wrote:What about option #4 to Check Integrity of Job Files?

Option #4 on my DS.TOOLS is something different. I'll try the DS.CHECKER command.

DataStage Tools Menu

1. Report on project licenses
2. Rebuild Repository indices
3. Set up server-side tracing >>
4. Administer processes/locks >>
5. Adjust job tunable properties


1. List all processes
2. List state of a process
3. List state of all processes in a job
----------------------------------------------
4. List all locks
5. List locks held by a process
6. List locks held by all processes in a job
----------------------------------------------
7. Clear locks held by a process
8. Clear locks held by all processes in a job
----------------------------------------------
9. Logout a process
10. Logout all processes in a job
11. Clear status file for a job

ok, DS.CHECKER looked like it did some good... created missing files and deleted old ones...

So now, I can compile the job successfully. But I still can't delete the job. When I try, I get this:
Cannot open file RT_BP806.O

Here's the directory and its contents:
drwxrwxrwx 2 dsadm dstage 4096 Jan 10 13:13 RT_BP806.O
RT_BP806.O:
total 124
-rwxrwxr-x 1 dsadm dstage 120840 Jan 10 13:13 V0S203_CopyOft_P1P_CV00122_KNVP_criteria_4mayyin_xfmTrim.so

Any ideas? By the way, I exported the job and imported it successfully into a different project and was able to delete it without problem.

Try importing in the same project, when it says that the job already exists, want to continue, hit yes or ok. See what happens.

When trying to import into the same project, I get the same error:
Cannot open file RT_BP806.O

If I rename the job, I still can't delete the job. But this allows me to import the job without error (at which point I have two of the same jobs, just one is renamed).