Page 1 of 1

Cannot find record JOBPARAMINSTS in executable job

Posted: Mon Nov 20, 2006 7:26 pm
by cocardoso
I'm trying to figure out why DataStage is returning this message when I access the Schedule View under Director:

Cannot find record JOBPARAMINSTS in executable job file RT_CONFIG2417

I have been already tried to:

- Restart the DataStage Server
- Recompile all the Sequences
- Clear the crontab file
- Export / Import the Jobs

I don't know what to do now! Someone can shed a light ?

Thank you in advance,
Cesar.

Posted: Mon Nov 20, 2006 8:12 pm
by kduke
The job number is 2417. You could do a

SELECT * FROM DS_JOBS WHERE JOBNO = '2417';

To find out which job it is then try to fix this one job.

Posted: Mon Nov 20, 2006 8:19 pm
by ray.wurlod
Welcome aboard! :D

This is an executable job, not a job sequence. Recompiling that particular job may well re-create the job parameter instances record in that job's configuration file. Please try it and let us know the outcome.

Posted: Tue Nov 21, 2006 7:18 am
by cocardoso
Thank for the replies!

Kduke,
I'm using DataStage version 5.2 and I didn't see any way to execute this query. I am a new user, bear with me :) Could you send me some step by step to execute these queries under unix environment?

Ray,
Thanks for the welcome message!! I'm expecting to use this forum a lot, and can help many people in a near future. Sorry, but I'm not a premium user yet, and I couldn't see your whole post.

Best regards,
Cesar.

Posted: Tue Nov 21, 2006 7:58 am
by DSguru2B
Indeed. This site has helped thousands and will continue to do for many more. You can get access to premium content for a little over a quarter a day. If your from brazil that will be a little over half a brazillian real :wink:

Posted: Tue Nov 21, 2006 8:04 am
by chulett
cocardoso wrote:I'm using DataStage version 5.2 and I didn't see any way to execute this query.

Use the Administrator... find the Project and click the 'Command' button.

Posted: Tue Nov 21, 2006 10:47 am
by cocardoso
Chulet,
Worked! Thank you.

But now, what can I do to solve this terrible problem? :(

DSguru2B,
I agree with you, it is so cheaper and I already started the process here in the company where I'm working to buy a subscription. I'm concerned with this problem :(

Thank you everybody!!!
Cesar.

Posted: Tue Nov 21, 2006 11:45 am
by chulett
Recompile the job you just looked up, see if that fixes the problem.

Posted: Tue Nov 21, 2006 12:48 pm
by cocardoso
Craig,

Continue with the same error after the recompile.
Any idea?

Thanks,
Cesar.

Posted: Tue Nov 21, 2006 1:23 pm
by ray.wurlod
Add one extra parameter to the job properties. It doesn't have to do anything. Then recompile. This will force a new parameters collection to be built.

Then remove the job from the Schedule (if indeed it is there), and re-schedule it. This process should prompt for job parameter values and, based on what you provide, build a JOBPARAMINSTS record in the job configuration file.

Posted: Tue Nov 21, 2006 9:04 pm
by kduke
What he said and if that does not work then Save As a new job name. Next delete the old job. Rename the Save As version back to the original name. Then do eveything Ray said again.