Moving from v7.7.05 to v8.1.04. Is there some new trick in getting variables passed via EXEC? This no longer seems to work:

EXEC SET_CONN DB_CONN=P

That is to say, &DB_CONN appears not to be set to P for use within the SET_CONN procedure. As I said, it works fine in v7.7.05!

Thanks,

Craig

This message has been edited. Last edited by: <Kathryn Henning>,

It should work.

Do you need to Execute the fex or can you -INCLUDE it ?

I usually do -INCLUDE procedures, but would prefer to keep this as is, as I EXEC this procedure and a few others in many applications. Hoping to limit my code remediation to those things that truly break going from v7.7 to v8! Will play with it again tomorrow morning...

Craig

What is P?
If it's a string literal, perhaps the solution is to quote it? If it's not, then I'm not familiar with what you're doing and I'd appreciate a pointer

We use EX in WF8.1, also with parameters, and haven't seen the issue you describe. Then again, from the documentation it would appear that EXEC calls a maintain procedure, so perhaps not related to the issue? (-INCLUDE would be in the same boat though)

I have a fex named "showvars" with just -? & within it. Trying the following within both WF 8.0.08 and WF 8.1.04 shows the variable P = Something

EX showvars P=Something

 CURRENTLY DEFINED & VARIABLES:
 &&MAS_FULLINFO= N
 &ACCEPTS      =        0
 &APPROOT      = C:\ibi\apps
 &AUTOINDEX    = NO
 &BASEIO       =        0
 &CHNGD        =        0
 &DATE         = 07/13/15
 &DBMSERR      =        0
 &DELTD        =        0
 &DMY          = 130715
 &DMYY         = 13072015
 &DUPLS        =        0
 &ECHO         = OFF
 &FOCFEXNAME   = showvars
 &FOCFOCEXEC   = showvars
 &FOCGRAPHCNT  =        0
 &FOCINCLUDE   =
 &FOCNEXTPAGE  =        0
 &FORMAT       =        0
 &INDEXIO      =        0
 &INPUT        =        0
 &INVALID      =        0
 &LINES        =        0
 &MDY          = 071315
 &MDYY         = 07132015
 &NOMATCH      =        0
 &P            = Something
 &READS        =        0
 &RECORDS      =        0
 &REJECTS      =        0
 &SETFILE      =
 &SORTIO       =        0
 &TOD          = 12.49.25
 &TRANS        =        0
 &YMD          = 150713
 &YYMD         = 20150713

So I would ask what you have within the focexec being executed? Also make sure that it is the one that you think it is by issuing the FOCEXEC extension of the WHENCE command -

WHENCE SET_CONN FOCEXEC

T

This message has been edited. Last edited by: Tony A,

Ahem (red faced), got back into this first thing this morning, and it looks like it's working fine, after all.

The EXEC version of the "Execute" command hits a procedure on the Reporting Server. From the Help:

"Note: When EXEC is used in Managed Reporting, it is important to note that there is a difference between EX and EXEC. EX statements coded in a procedure are processed by the WebFOCUS Client, which looks for the procedure in the Managed Reporting repository. Procedures that are referenced with an EXEC statement are not processed by the WebFOCUS Client, they are only passed to the WebFOCUS Reporting Server for processing, and these procedures are not looked for in the Managed Reporting repository."

By the way, I wrote that SET_CONN procedure so that I can dynamically connect to our Dev, QA, BA, or Prod database "on the fly" with one set of metadata files. Take a look at "Parameterizing Master and Access File Values Using Variables" in the Help.

Craig