STAGE has unexpected STATUS value

roy · Post by **roy** » Thu May 26, 2005 1:33 am

Hi,
I have a DRS performing select max for a column to a Xfm poping a user status and outputing to /dev/null.
it was working fine till recently we started getting
the above message and the job aborts.
(searcing for the entire error got 4 results all leading to a forum page but no real post).

Thanks in advance,

chulett · Post by **chulett** » Thu May 26, 2005 5:42 am

Roy - not sure what you mean by "select max for a column to a Xfm poping a user status and outputing to /dev/null".

You might want to give more details on that.

Sainath.Srinivasan · Post by **Sainath.Srinivasan** » Thu May 26, 2005 5:48 am

I think he means writing the output to user status and connecting the link output to a (dummy) seq file with name as /dev/null in order to ignore any output from it.

Roy,

Did you check whether any value is populated into the user status?

chulett · Post by **chulett** » Thu May 26, 2005 5:50 am

Ok, I could see that. In addition to what was already asked, how exactly is the value getting 'popped' into the status area?

ray.wurlod · Post by **ray.wurlod** » Thu May 26, 2005 7:24 am

Something strange has been written, or failed to be written, to the RT_STATUSnn file record for that stage in the job. Clearing the status file for the job should remedy the problem.

roy · Post by **roy** » Mon May 30, 2005 9:13 am

Thank for the replies All,

After some "changes"/recompiles and such it started working.

I'll try clearing the ststus file Ray next time

,
I still need to verify this being persistant and not a random fluke now and then.

(yes you got the idea Sainath.Srinivasan, I can't recall if it did :roll:

, if I get the answer to that I'll update this post)

Thaks Guys

,

ray.wurlod · Post by **ray.wurlod** » Mon May 30, 2005 3:57 pm

Recompiling, among many other things, does have the effect of resetting stage information in the status file. Or causing another wave number to be used next time the job is run, depending on internal conditions, which I'd prefer not to discuss.