verifying that this is impossible

[Scott Preddy]

I would like to set a global variable to my entire oozie job and then
reference its value from various actions. I would like to use some "el
function stuff" when assigning this variable.
However I assume this is completely impossible because I cannot even do the
following. No matter what I try "controlFilePath2" is always undefined in
"echoControlFile", so trying the
"el function" does not even need to be explored.

<workflow-app xmlns="uri:oozie:workflow:0.4" name="sandbox1">
    <global>
        <job-tracker>${jobTracker}</job-tracker>
        <name-node>${nameNode}</name-node>
        <configuration>
           <property>
               <name>mapred.job.queue.name</name>
               <value>default</value>
           </property>
           <property>
               <name>controlFilePath2</name>
               <value>***Path***</value>
           </property>
        </configuration>
    </global>

    <start to="echoControlFile"/>

    <action name="echoControlFile">
        <shell xmlns="uri:oozie:shell-action:0.3">
        <job-tracker>${jobTracker}</job-tracker>
        <name-node>${nameNode}</name-node>
            <exec>echo.sh</exec>
            <argument>Control file path: ${controlFilePath2}</argument>
            <file>${scriptsDir}/echo.sh#echo.sh</file>
            <capture-output/>
        </shell>
        <ok to="end"/>
        <error to="fail"/>
    </action>

    <kill name="fail">
        <message>Job failed, error
message[${wf:errorMessage(wf:lastErrorNode())}]</message>
    </kill>
    <end name="end"/>
</workflow-app>
"workflow.xml" 53L,
1953C
40,13         Bot