Setting $UserStatus from a Parallel Job

[blewip]

Does anyone know how you set the UserStatus from a Parallel Job.

I have a routine that calls DSSetUserStatus(Arg1). I can call this from a Server job no problem. However when I use a BASIC transformer in a PX job to call the same routine, it doesn't work.

Is there another way to set the UserStatus?

Cheers

[blewip]

Error Message is

Log_Job_Details(BASIC_Transformer_49).#0.BASIC_Transformer_49 (DSSetUserStatus): Error reading Job Status record. JobNo = 46 JobName = Log_Job_Details.#0 WaveNo = 1

[cpratima]

You cannot call routines from a parallel job because PX does not understand the BASIC language that routines use. You will have to write the logic through a Build stage using C language.

[blewip]

Thanks cpratima, so you're saying that I need write some c++ code.

I have been looking at the Parallel Job Advanced Developers Guide, is this the best one for showing me what to do.

I am guessing there is an equivalent to the call that I am using at the moment.

In the Server Routine I Call DSSetUserStatus(Arg1)

Do you know what call I use in the c code for my Parallel Routine?

[chulett]

You cannot call routines from a parallel job because PX does not understand the BASIC language that routines use.

I'm afraid this isn't true. You can call routines from the BASIC Transformer as the OP is trying to do.

My guess (don't know for sure) is that PX jobs may not have a 'User Status' area like Server jobs do.

[ArndW]

I think that Craig is correct, the user status is not the same in Px. What would work is doing the same thing from an after-job subroutine call instead of from a BASIC transform - that way at least you know it is only getting called one time instead of once per node defined in the $APT_CONFIG_FILE

[blewip]

My guess (don't know for sure) is that PX jobs may not have a 'User Status' area like Server jobs do.

That's possible I am new to PX, however in the Sequence you can access the $UserStatus for the particular PX Job using ActivityVariables. I am accessing $JobName and this seems to work, $JobStatus may work as well.

From what ArndW was saying it may be more complex though with each node potentially having a $UserStatus