Page 1 of 1

Error Writing to RT STATUS

Posted: Wed Aug 09, 2006 8:18 am
by Meera
Hi,

I have some jobs developed in Release 4x. Datastage client is 7x. when i compiling the existing jobs iam getting the following error
Error writing to RT CONFIG.

when running the jobs
Error writing to RT STATUS.

I made some changes in the existing Job sequencer , when i run the sequencer , iam getting the following warning
code=-99 [General repository interface 'other error']

Please help me to solve this issue

Thanks
meera

Posted: Wed Aug 09, 2006 8:58 am
by ArndW
Can you create a new dummy job and compile it? If not, then you have an error in the RT_nnn files. If it is only for the old 4.x jobs that have been imported then it might be some other issue. Can you do a "save as" another name and compile the job? If yes, you have a UNIX permissions issue on the files.

Posted: Wed Aug 09, 2006 9:03 am
by kduke
If you do an exact search on chmod you will find several posts on how to fix this. The most complete is viewtopic.php?t=95616&highlight=chgrp+chmod

Posted: Wed Aug 09, 2006 9:08 am
by Meera
Hi

I can create new job, compile and run it. The existing job, i can "save as" with another name and compile it. But when iam running , iam getting the following error
JobControl (fatal error from DSRunJob): Job control fatal error (-99)
(DSRunJob) Error writing to RT_STATUS4


Thanks

Posted: Wed Aug 09, 2006 9:16 am
by ArndW
check UNIX access rights on the RT_STATUS4 and RT_LOG4 files as I mentioned earlier. Does your user have write permission?

Posted: Wed Aug 09, 2006 9:32 am
by Meera
Hi

It is the user issue. Now I am able to run the jobs.

Thanks for your help

Posted: Wed Aug 09, 2006 10:46 pm
by ray.wurlod
It's probably a good idea to put the command umask 002 into your dsenv script.

Posted: Fri Sep 05, 2014 7:00 am
by ulab
Please chek on the permissions on and inner files of RT_STATUS**

The inner files on this RT_STATUS** did not have 775 permissions as the folders are owned by other user ID

Posted: Fri Sep 05, 2014 7:52 am
by PaulVL
Ensure that the files in that rt_status / log / etc have the correct dstage group as opposed to the primary group of the orriginal user who created those files.

I'm hoping it's all dstage (or your site equivalent) but I have seen instances where it was not.

Posted: Fri Sep 05, 2014 8:43 pm
by qt_ky
This topic was dormant for over 8 years...

Posted: Fri Sep 05, 2014 9:32 pm
by chulett
Yup, what on other boards we would call a "thread necro". :wink: