Page 2 of 2

Posted: Tue Jun 30, 2009 8:21 am
by pklcnu
priyadarshikunal wrote:also in case of run time error, can you please post the error message?
I am getting problem while running the job, compilation is fine . I am not passing the InvocationID as parameter. I am ticking the check box 'Allow Mutiple Instance' in the sequence job properties. When I click the Run button it is asking for Invocation ID by default along with other parameters . When I enter any value in to this default Invocation ID field it is running fine as long as it is text or number but if I enter any Dot or # value it is throwing error at entry level it self.

Your input will be much appreciated.......thanks

Posted: Tue Jun 30, 2009 8:24 am
by chulett
What's your exact "7.x" version of DataStage?

Posted: Tue Jun 30, 2009 8:27 am
by pklcnu
chulett wrote:What's your exact "7.x" version of DataStage? ...
7.5.2

Posted: Tue Jun 30, 2009 8:38 am
by chulett
Works fine for me on 7.5.2. Use the "..." External Parameter Helper to pick the right value from the Start Loop stage rather than typing it by hand. Should end up looking something like this:

#StartLoop_Activity_Stage_Name.$Counter#

Posted: Tue Jun 30, 2009 9:27 am
by priyadarshikunal
pklcnu wrote:
priyadarshikunal wrote:also in case of run time error, can you please post the error message?
I am getting problem while running the job, compilation is fine . I am not passing the InvocationID as parameter. I am ticking the check box 'Allow Mutiple Instance' in the sequence job properties. When I click the Run button it is asking for Invocation ID by default along with other parameters . When I enter any value in to this default Invocation ID field it is running fine as long as it is text or number but if I enter any Dot or # value it is throwing error at entry level it self.

Your input will be much appreciated.......thanks
so basically you sequence itself is multi-instance not the JOB?

Posted: Tue Jun 30, 2009 9:34 am
by pklcnu
priyadarshikunal wrote:
pklcnu wrote:
priyadarshikunal wrote:also in case of run time error, can you please post the error message?
I am getting problem while running the job, compilation is fine . I am not passing the InvocationID as parameter. I am ticking the check box 'Allow Mutiple Instance' in the sequence job properties. When I click the Run button it is asking for Invocation ID by default along with other parameters . When I enter any value in to this default Invocation ID field it is running fine as long as it is text or number but if I enter any Dot or # value it is throwing error at entry level it self.

Your input will be much appreciated.......thanks
so basically you sequence itself is multi-instance not the JOB?
I tried both......Job and the sequence with multiple instace

Posted: Tue Jun 30, 2009 9:35 am
by priyadarshikunal
You can pass the invocation ID only to a down stream multi-instance job/sequence from start loop activity. Not when running the Parent job itself.

Are you running that sequence manually 20 times or through script or other sequence?

Posted: Tue Jun 30, 2009 9:39 am
by priyadarshikunal
pklcnu wrote: I tried both......Job and the sequence with multiple instace
do it like that

a sequence (not multi-instance).

Start loop activity ->(multi-instance job) -> end loop activity

in that multi-instance job - open properties go to invocation ID
use external Parameter Helper to pick the right value from the Start Loop stage. Compile and then run.

and then let us know the results.

Posted: Tue Jun 30, 2009 9:41 am
by pklcnu
priyadarshikunal wrote:You can pass the invocation ID only to a down stream multi-instance job/sequence from start loop activity. Not when running the Parent job itself.

Are you running that sequence manually 20 times or through script or other sequence?
The job runs through sequence only for 20 times for the 20 values mentioned in the start loop activity........i am not running the job individually.......just one click on run button of sequence runs the loop job for 20 times....

Posted: Tue Jun 30, 2009 9:45 am
by priyadarshikunal
pklcnu wrote:The job runs through sequence only for 20 times for the 20 values mentioned in the start loop activity........i am not running the job individually.......just one click on run button of sequence runs the loop job for 20 times....
My first statement still hold true.

Are you doing in same way what I proposed in my earlier post?