OdiStartScen in async mode: variables lost in execution queue

Question

I have the following case:
- a scenario must be called for each row in a database table
- this scenario has a variable, declared in the scenario parent package: variable values are read from the table
- rows are more than the "maximum number of sessions" for the agent
- execution of the scenarios should run in parallel
So I made a procedure, with only one step. The source command is something like "SELECT col1 alias1 FROM MyTable". The target command, on Sunopsis API, is OdiStartScen -SCEN_NAME=MyScenario "-GLOBAL.VAR1=#alias1"
When the procedure is executed by the agent, I have the following outcomes:
- if OdiStartScen is run synchronously (-SYNC_MODE=1): OK, no problem
- if OdiStartScen is run asynchronously (-SYNC_MODE=2) AND the number of rows in MyTable is less than the "Maximum number of sessions" set in Topology Manager for the executing agent: OK, no problem
- if OdiStartScen is run in async mode, and the number of rows in MyTable is greater then the maximum number of sessions, then the execution is OK only for the first rows of the table. Successive executions get enqueued, but when it's time for the agent to run them, Operator reports the followin error: "Variable has no value".
So it seems to me that variable values don't get enqueued, is it correct?

Answer 1

OK, my suggestion is:
It will be necessary add a new procedure at the process.
Create a new procedure and:
1) at 1º step:
Target Tab
Technology: javascript
code:
<@String vSS="";@>
2) 2º step
Source Tab:
Exact the same query, technology and Logical Schema as where the problem happens.
Target tab
Technology: javascript
code:
<@vSS+=" select 'OdiStartScen -SCEN_NAME=TESTPARALLEL -SCEN_VERSION=001 -SYNC_MODE=2 -GLOBAL.HOST=#p_host -GLOBAL.LAST_DATE=#p_last_date' as vComm from dual union";@>
*** VERY IMPORTANT: do not let any return carriage at the above command... probably it will appear into two lines at you screen but be sure that there is no return carriage character. I mean, the 2 lines are just because it can not be showed at just one.
3) 3º step
Target tab
Technology: javascript
code:
<@vSS=vSS.substring(0,vSS.length()-5);@>
4) now, a small change at your original procedure...
at the step where the select was done change the code to:
Source tab --> keep all but the code:
New code:
<@=vSS@>
Target tab --> keep all but the code:
New code:
#vComm
I believe that will solve the problem... I converted the parameters to strings then they do not need to exist as parameter at a new agent (balance)
obs.: Must be done in 2 procedures, because a javascript limitation.
Make any sense?
Please, try it and let me now... As I wrote the code with no ODI maybe could have some typed mistake, if you get any error let me now. (You can address me by my email at profile)
Edited by: Cezar Santos on 04/12/2008 16:52