A Data Flow (ETL process) is not recognizing a global variable.

I’m running the following fex:

-****************************************************
EX DATE_ROUTINES/calc_7_days_prior
-RUN

-TYPE &&LSTMONDAY &&SUNDAY

EX CMASAP REQ_NAME=040_update_work_wod
-RUN

-EXIT
-****************************************************


When 040_update_work_wod runs, it abends with the error below. I’m using the global variable &&LSTMONDAY in the filter of 040_update_work_wod Data Flow.

Submitted for deferred
Request - 040_update_work_wod (Owner: eda) submitted.
work_wod type Oracle Existing target
Issuing PREPARE
0 ERROR AT OR NEAR LINE 143 IN PROCEDURE 040_updaFOCEXEC *
(FOC295) A VALUE IS MISSING FOR: &LSTMONDAY
Output retrieved
Elapsed run time 0:00:00

If I place DATE_ROUTINES/calc_7_days_prior as an rpc within the 040_update_work_wod right before the Data Flow, it works OK.

Any hlp is most appreciated.
Thanks,
Jim

I found where you have to place PARM after the
CMASAP statement like:

EX CMASAP REQ_NAME=040_update_work_wod,PARMS="&&MON=&&LSTMONDAY"

This doesn't seem to work, so my question is
how can you set a parm to equal a parm on the CMASAP statement???

After talking with IBI, they said you cannot pass parameters to a workflow on version 5.33.
Version 7.1 will allow parameters to be passed to a work flow.

Jim,

I can confirm that you can pass parameters at 7.1 . We are doint it right now.

Jim, are you sure that IBI told you this. I have two different instances where I am setting global variables for use in process flows and it works fine. I am using 5.3.3.

Ken