Page 1 of 1
Re: cronjob error
Posted: Mon Apr 30, 2012 2:13 pm
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?
Posted: Mon Apr 30, 2012 2:22 pm
by ketfos
Yes . I can run the batch and all the job in the batch manually
Posted: Mon Apr 30, 2012 3:14 pm
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.
Posted: Mon Apr 30, 2012 4:39 pm
by ketfos
This is the only job we are having intermedient problem.
Posted: Mon Apr 30, 2012 8:28 pm
by PaulVL
Can you post the crontab entry please.
Posted: Mon Apr 30, 2012 9:43 pm
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
Posted: Tue May 01, 2012 5:57 am
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.
Posted: Fri May 04, 2012 6:10 am
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.