Hi Ravi,

To submit the second job once the first completes, set the
Wait Until Status parameter in the first GenericJobLauncher
to NotInQueue.

The exitcode port does not work and has been removed from
the actor in svn.

  --dan


On 10/30/12 7:12 AM, Ravi Kumar wrote:
Hello Daniel,

Thanks a lot for quick response. I tried to create workflow with this approach that you mentioned in this thread, 
connecting output port "success" to next "GenericJobLauncher".  As per my understanding 
"success" port is a boolean flag to indicate if job launch was successful. But we want to execute second 
process only when first process completes successfully. I am not able to add this dependency with second 
"GenericJobLauncher".
Can you please let me know whether we can put this dependency with subsequent 
"GenericJobLauncher" or not? If yes how?

There is a output port "exitcode" provided with "GenericJobLauncher". As per 
documentation it says, If the exit code is 0, the command was performed successfully. But I didn't get any 
output on this "output" port even after job completes successfully.  So I am not able to use this 
output(exitcode) port as trigger to next Actor.

For your information: I am using -Kepler 2.3 on Linux machine(Rad Hat 6.1) with 
'PBS' scheduler.
Thanks in advance.


Regards,
Ravi

-----Original Message-----
From: Daniel Crawl [mailto:[email protected]]
Sent: Saturday, October 27, 2012 3:01 AM
To: Ravi Kumar
Cc: [email protected]; Trilok Khairnar
Subject: Re: [kepler-dev] Query regarding 'GenericJobLauncher' actor


Hi Ravi,

The output port "success" can be used to trigger another GenericJobLauncher or 
any other actor. I've attached a workflow demonstrating this with two GenericJobLauncher 
actors.

    --dan


On 10/26/12 6:44 AM, Ravi Kumar wrote:
Hi All

I have a kepler workflow which uses mainly Exec Actor, in which two exec actor can be run 
in parallel. Now I want to use "GenericJobLauncher" actor instead of Exec so 
that each process can be run on different node on grid. In my original workflow 
'exitCode'  output port of first 'Exec' Actor  is connected to 'trigger' input port of 
next 'Exec' actor. But with 'GenericJobLauncher' actor there is no input port like 
trigger, also 'exitCode' output port is commented in code and it's not working.

Can someone tell me correct way to use GenericJobLauncher, whether I am trying 
in right direction or not.
Is it possible to use 'GenericJobLauncher' actor in between two Exec Actor? If 
yes how?

For your information:
I am using Kepler 2.3 and 'PBS' scheduler.

Thanks in Advance.

Regards,
Ravi


DISCLAIMER
==========
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.



_______________________________________________
Kepler-dev mailing list
[email protected]
http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev



DISCLAIMER
==========
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.


_______________________________________________
Kepler-dev mailing list
[email protected]
http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev

Reply via email to