cannot open executable job file RT_CONFIG0

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

coface
Premium Member
Premium Member
Posts: 57
Joined: Fri Aug 10, 2007 8:13 am

cannot open executable job file RT_CONFIG0

Post by coface »

Hello,
when starting the DataStage Director a message box with the following error pops up:
cannot open executable job file RT_CONFIG0

This error occured suddenly, no changes to DataStage or the OS have been made. But I've noticed that the /tmp directory didn't have any space left (filled to 100%). Cleaning up the directory didn't help at all.
I'm astonished about the 0 in the error message (RT_CONFIG0). There is no directory RT_CONFIG0 in the filesystem. When viewing the details of the job the parameter "Wave#" has the value 0 (which seems strange to me).
Does anybody know how to solve this problem?

Any help will be appreciated
Rgds
Jan Hauschildt
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

Can you try to DS.REINDEX, it might be a defect index.
coface
Premium Member
Premium Member
Posts: 57
Joined: Fri Aug 10, 2007 8:13 am

cannot open executable job file RT_CONFIG0

Post by coface »

ArndW wrote:Can you try to DS.REINDEX, it might be a defect index.
Hello,
I have already tried that before (sorry for not mentioning it) - but that didn't help at all.

Rgds
Jan Hauschildt
coface
Premium Member
Premium Member
Posts: 57
Joined: Fri Aug 10, 2007 8:13 am

cannot open executable job file RT_CONFIG0

Post by coface »

ArndW wrote:Can you try to DS.REINDEX, it might be a defect index.
Hello,
I have already tried that before (sorry for not mentioning it) - but that didn't help at all.

Rgds
Jan Hauschildt
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

That means that one or more of your DataStage hashed files might be corrupt, most likely caused by the disk full condition. If the project directory didn't fill up then I would try a quick multiple job force compile of the whole project from the designer - this might (low probability) clean things up, but is easy to do.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

My punt would be DS_JOBS, because there should never be a job number 0.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

I think so as well, and if the SELECT for the multiple job compile fails then it would point there as well.
coface
Premium Member
Premium Member
Posts: 57
Joined: Fri Aug 10, 2007 8:13 am

Post by coface »

ArndW wrote:I think so as well, and if the SELECT for the multiple job compile fails then it would point there as well.
the force compile didn't help...

@ray:
what do you mean by DS_JOB?

Rgds
Jan H.
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

Did the multiple job in fact go and compile your project's jobs?

From the Administrator or from TCL, execute the command "COUNT DS_JOBS". Do you get a record count or an error message?
coface
Premium Member
Premium Member
Posts: 57
Joined: Fri Aug 10, 2007 8:13 am

Post by coface »

ArndW wrote:Did the multiple job in fact go and compile your project's jobs?

From the Administrator or from TCL, execute the command "COUNT DS_JOBS". Do you get a record count or an error message?
the multiple compile has compiled all jobs - just the one which causes the error not.
Executing the command COUNT DS_JOBS returns "198 records counted".

Might it be helpful to delete all jobs and to redeploy them?

I'm still wondering where the job number 0 comes from...

Rgds
Jan H.
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

Can you save the job that isn't working under another name, delete the original, rename & recompile the copy?
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Is there any warning of the form "non numeric where numeric required, zero used" in the job log or anywhere else? (I'm puzzling over the zero in the RT_CONFIG0 name still.)
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
coface
Premium Member
Premium Member
Posts: 57
Joined: Fri Aug 10, 2007 8:13 am

Post by coface »

ArndW wrote:Can you save the job that isn't working under another name, delete the original, rename & recompile the copy?
I have exported all jobs and deleted them. After importing all jobs again the error still occurs.

Rgds
Jan H.
coface
Premium Member
Premium Member
Posts: 57
Joined: Fri Aug 10, 2007 8:13 am

Post by coface »

ray.wurlod wrote:Is there any warning of the form "non numeric where numeric required, zero used" in the job log or anywhere else? (I'm puzzling over the zero in the RT_CONFIG0 name still.)
No, no entries like "non numeric" found.

Rgds
Jan H.
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

At the TCL prompt or from the administrator, enter:

UVFIXFILE DS_JOBS
UVFIXFILE DS_JOBOBJECTS

and please post the results.
Post Reply