Problem with RT_CONFIG file

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
katz
Charter Member
Charter Member
Posts: 52
Joined: Thu Jan 20, 2005 8:13 am

Problem with RT_CONFIG file

Post by katz »

Hi

I have a corrputed RT_CONFIG file which I am unable to get rid of. Somehow the job got corrupted (only this job) and I want to simply remove the job from the repository but am unable to delete it. I get the error message Cannot open executable job file RT_CONFIG454.

I have tried the CLEAR.FILE command, but it returns an error message Cannot Open File "RT_CONFIG454".

And I've tried a diagnostic with the fixtool, but it returns the following:

Start Diagnostics.

An error was encountered which prevents further diagnostics.
The file cannot be fixed with this tool.

Problem: File is physically too small. This is not a UniVerse file.

Action required: Check specified filename.


The filename is correct and does exist in the project folder.

My objective is to completely remove the job. So far I've not tried the "backup the entire project, delete the project, re-create it, and restore from the backup" option (my last resort). Is there another approach I can try?

Thanks mucho
DSguru2B
Charter Member
Charter Member
Posts: 6854
Joined: Wed Feb 09, 2005 3:44 pm
Location: Houston, TX

Post by DSguru2B »

Try doing an exact search on the statement "Cannot open executable job file RT_CONFIG"
That will get you a lot of posts.
If all fails, just stop and restart your DS server.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
kcbland
Participant
Posts: 5208
Joined: Wed Jan 15, 2003 8:56 am
Location: Lutz, FL
Contact:

Post by kcbland »

DSguru2B wrote: If all fails, just stop and restart your DS server.
This has no effect. The pieces and parts to this file are missing. Either the VOC entry points to missing constituent parts, or there's a permissions issue on the parts. The easiest thing to do is just copy another RT_CONFIGxxx directory contents (DATA.30, OVER.30, and the hidden .type30 files) to the RT_CONFIG454 directories. Then blow away the job.
Kenneth Bland

Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
DSguru2B
Charter Member
Charter Member
Posts: 6854
Joined: Wed Feb 09, 2005 3:44 pm
Location: Houston, TX

Post by DSguru2B »

:shock: Hmm. I got that by doing a search on the error message and one of the posters got the problem fixed by doing exactly that. I wasnt aware of that.
For your reference, heres the post
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
kcbland
Participant
Posts: 5208
Joined: Wed Jan 15, 2003 8:56 am
Location: Lutz, FL
Contact:

Post by kcbland »

Arnd was talking about releasing locks, kicking out users, etc. The last resort for releasing locks and killing runaway job zombie threads is a recycle.
Kenneth Bland

Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
DSguru2B
Charter Member
Charter Member
Posts: 6854
Joined: Wed Feb 09, 2005 3:44 pm
Location: Houston, TX

Post by DSguru2B »

Gotchya. :wink:
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
katz
Charter Member
Charter Member
Posts: 52
Joined: Thu Jan 20, 2005 8:13 am

Post by katz »

Thanks Kenneth, Your suggestion worked a treat and that job is now history. :)
Post Reply