DSXchange

I don't see how RT_STATUS or RT_CONFIG issues can be corrected by releasing locks or clearing the status file.

You are in luck - we just went through this exact same thing with someone else, suggest you search for RT_CONFIG to find that conversation.

Hello Chulet,

I came across with post :
viewtopic.php?t=81201

I have tried pretty much,whatever i came across in most of the posts in DSX.The only thing i need to confirm is , "is it Disk full Issue?".

Thanks,

Not sure how a post from 2000 in the Oliver archives can be the 'recent' post I was hoping you would find.

viewtopic.php?t=112908

chulett wrote:Not sure how a post from 2000 in the Oliver archives can be the 'recent' post I was hoping you would find.

viewtopic.php?t=112908

Chulett,

Thanks for your quick response,

Actually i came across with this post before,but didn't get things like how he has resolved problem.
Could you elaborate more on this..where he has got this RT_CONFIG file.I searched out for this file in datastage /bin directory,but i didnt find any where.what i thought was ,if find that executable file i will clear it manually with the
command: clear.file RT_CONFIG319.

Right now the issue is resolved.
In my case "Disk was full" ,its an issue with space itself.Just cleared the disk and it worked out.

Thank you chulett,

Check the last four posts on the first page of the topic I linked to. There's nothing to do with 'bin' here or to be cleared.

Hi all,
sorry for delayed response.
I just cleared my disk space,as my disk was full.
This thing cleared my issue.

Thanks Chulett & all for your total support.

Hi,

We have faced simialr problems in our project due to some corrupt files. One thing you can always try out is to export the job and re-import it. When you re-import the job a fresh set of config and status files get created.

Note: When you import that the design and executable are linked to each other

Sai

saikir wrote:Hi,

We have faced simialr problems in our project due to some corrupt files. One thing you can always try out is to export the job and re-import it. When you re-import the job a fresh set of config and status files get created.

Note: When you import that the design and executable are linked to each other

Sai

Hello sai,
I tried with importing a job from my old backups,that too didn't work.
When you face problem with executable files i dont think we can export it .
It wont allow you to export,it will throw the same error.(cannot open executable job file RT_Config).

Thanks.....

When we face this kind of issue I remember we deleted the job from the repository and then reimported(promoted from version controller). This will do the same as sai said (a fresh set of config and status files get created), but can you check by deleting the job and promote/re-import the same job again.