cronjob error

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Re: cronjob error

Post by chulett »

ketfos wrote:A fatal error has occurred in DataStage.
Unable to re-open operating system file ""
You need to find out what this means. I wonder if the job instelf is corrupted somehow... can you run the job manually?
-craig

"You can never have too many knives" -- Logan Nine Fingers
ketfos
Participant
Posts: 562
Joined: Mon May 03, 2004 8:58 pm
Location: san francisco
Contact:

Post by ketfos »

Yes . I can run the batch and all the job in the batch manually
ketfos
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

OK. Do other jobs run out of cron ok and just this one has an issue or do all cron jobs fail? Honestly, I have no idea what might be going on, just trying to ask intelligent questions to try and narrow this down. You really should put this in front of your official support provider, IMHO.
-craig

"You can never have too many knives" -- Logan Nine Fingers
ketfos
Participant
Posts: 562
Joined: Mon May 03, 2004 8:58 pm
Location: san francisco
Contact:

Post by ketfos »

This is the only job we are having intermedient problem.
ketfos
PaulVL
Premium Member
Premium Member
Posts: 1315
Joined: Fri Dec 17, 2010 4:36 pm

Post by PaulVL »

Can you post the crontab entry please.
ketfos
Participant
Posts: 562
Joined: Mon May 03, 2004 8:58 pm
Location: san francisco
Contact:

Post by ketfos »

Below is the entry in Unix crontab

00 02 * * 1,2,3,4,5,6,0 /ardent/uv/DataStage/Projects/amdproj/dsr_sched.sh /a
rdent/uv/DataStage/Projects/amdproj /opt/IBM/InformationServer/Server/DSEngin
e DAILYJOB_JOBS 0/50/1/0/0 1 >/ardent/uv/DataStage/Projects/amdproj/dailyjobs.log 2>&1 #DSjobDS DSJ.amdproj.22.1
ketfos
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

In other words, the standard cron entry that DataStage creates. Still think you're going to need to involve your official support provider on this.

If you haven't already, try unscheduling it and then adding it back to the schedule, see if that helps.
-craig

"You can never have too many knives" -- Logan Nine Fingers
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

There's really no reason to be modifying the automatically generated crontab entries DataStage creates. Never mind the fact that they only have this issue with one particular job, all other scheduled jobs are working properly from what they noted.

I'd still be curious if "re-doing" the schedule helped... or if it changed the crontab entry at all.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply