I have a self-service report here for which some code should not be executed when it gets called by ReportCaster.

Is there some way to identify that RC is calling the fex as opposed to a normal user?

We could add an execution parameter in the RC schedule, but that's prone to forgetting to do so. I'm looking for a reliable way to detect that RC is executing the current fex.

This message has been edited. Last edited by: Kerry,

I wonder if you can add a var to the FEX like &REPORTMODE

When run manually, set it to 'NOTORC' and in the RC set up, set that value to 'RC'.

When the code executes, -IF &REPORTMODE EQ 'RC' THEN GOTO :SKIPTHECODE;

Would that work?

That is exactly what I was referring to in the 3rd paragraph. That does work, but it's too easy to forget to apply such parameters after deploying a report to a different server with a different RC environment.

I was kind of hoping that RC would be running from an environment where some parameters could be set to distinguish between those modes of operation.

I'm starting to think that we may be able to set a global variable in a "User Profile", provided we can figure out as which user RC is running and provided that the user profile does get applied from RC.

WebFOCUS automatically set &FOCFOCEXEC to RCASTER when running thru RC.

Another way to put my question:

How do we determine whether a report is running in interactive mode or not?

Running interactively, you get the name of your procedure in that variable, otherwise you can make a negative test, i.e. NE 'RCASTER'

You'll still have to remember to write somekind of condition to SKIPCODE or not. Could be an -INCLUDE. But still something to remember.

quote:

Originally posted by H Lidholm:
Running interactively, you get the name of your procedure in that variable, otherwise you can make a negative test, i.e. NE 'RCASTER'

Sorry, I hadn't seen your reply yet when I realised how to rephrase my question. That's a useful answer, thanks!

quote:

You'll still have to remember to write somekind of condition to SKIPCODE or not. Could be an -INCLUDE. But still something to remember.

Lucky for us, the code that we need to skip is already part of a conditional -INCLUDE.

If running a fex via RC, you can refer to variables &DSTOWNER and &DSTEDAUSER which are set and thus indicate that the fex is running via RC and not MRE.