I have a report stored in a file named test.fex which is stored in the folder
Developer Studio Desktop/WebFOCUS Environments/DEV/Managed Reporting/Domains/rwkTest/Standard Reports/projectA

Within this fex file is a "call" to a function
-MRNOEDIT EX projectA/functionA 'parameterA', 'parameterB'

The file functionA.fex is stored in the folder
Developer Studio Desktop/WebFOCUS Environments/DEV/Data Servers/EDASERVE/Applications/projectA

When test.fex is run from the location metioned at the top of this post, it works fine. However, the way our system was set up (years ago), in order to be executed from a Java UI, I need to move the test.fex to the folder
Developer Studio Desktop/WebFOCUS Environments/DEV/Data Servers/EDASERVE/Applications/projectA (which happens to be the same folder that the function is stored in, and also where the master files are stored). Now the call to the function fails with this error message ...

0 ERROR AT OR NEAR LINE 24 IN PROCEDURE _ADHOCRQFOCEXEC *
(FOC303) CONTROL LINE NOT RECOGNIZED IN FOCEXEC: -MRNOEDIT EX projectA/functionA 'parameterA', 'parameterB'

I have tried various ways of referencing the function. Can you suggest what I am missing?

thanks

Richard

NOTES:
1 - some names were simplified to make this an easier read (we do not call our functions functionA, etc)
2 - I am not running it from the Java UI; I am still running it manually from WF as a test before trying the UI
3 - I have a workaround that works; it involves the INCLUDE keyword; but have been asked to research why the EX method stops working

EXEC is what you need see my earlier in year post on EX and EXEC not being the same.

See this documentation of MRNOEDIT

-MRNOEDIT is a managed reporting preprocesssor directive, not a dialog manager directive.

When your fex was executed under aegis of MR, it worked fine -- MR removes "-MRNOEDIT" from the line before passing the modified fex code to WFRS, so dialog manager on WFRS is able to handle it, and the referenced fex is located by WFRS within its app folders.

But in your second scenario your fex is executed as is (with the -MRNOEDIT prefix intact) by WFRS, and the dialog manager scan chokes on the unknown MRNOEDIT directive.

This message has been edited. Last edited by: j.gross,