RE: returning result from exec_program TEC 3.9

Thanks David,

Maybe the way to go yes... Shame as the theory of exec_program_local looked 
quite useful... thanks for the comments..

Dave

-----Original Message-----
From: owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx
[mailto:owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx]On Behalf Of David 
Krupa
Sent: 25 February 2005 11:51
To: tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx
Cc: owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx; 
tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx
Subject: RE: [tme10] returning result from exec_program TEC 3.9


Dave,

I had trouble with TASK_COMPLETE reporting successful execution of the task
even though the task had some troubles doing so. In fact, TASK_COMPLETE
just proves that the task was successfully spawned :-(. And this was not
enough for me. Also, setting WATCH STATUS to YES caused some TEC troubles
as well.
Therefore, I bypassed it as I described and using date_reception and
event_handle makes it also quite easy for handling the result back in TEC.

David



                                                                           
             "Hawkett, David"                                              
             <David.Hawkett@ac                                             
             e-ina.com>                                                 To 
             Sent by:                  
<tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx>            
             owner-tme10@lists                                          cc 
             .us.ibm.com                                                   
                                                                   Subject 
                                       RE: [tme10] returning result from   
             25/02/2005 11:15          exec_program TEC 3.9                
                                                                           
                                                                           
             Please respond to                                             
                   tme10                                                   
                                                                           
                                                                           




yes .. I was looking at similar originally..

re exec_program_local and TASK_COMPLETE there is one question... I see
TASK_COMPLETE contains the attribute trigger_event_id.... which "holds the
identifier of the event that triggered the launch"... but when it enters
TEC can this id actually be used to locate the calling event ?  I do not
see how.. ( and therefore what it's point is exactly)... otherwise ..yes I
can only see this possible by doing something as you suggest below with
date_reception, even_handle etc...

thanks

Dave

-----Original Message-----
From: owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx
[mailto:owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx]On Behalf Of David 
Krupa
Sent: 23 February 2005 14:28
To: tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx
Cc: owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx; 
tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx
Subject: RE: [tme10] returning result from exec_program TEC 3.9


I had some issues with exec_program_local (TEC 3.8 FP02) as well as other
methods that I tried .... So at the end I ended up with handling this issue
directly in the script (tec_task).
Basically, I am checking for the result of the execution  (0 or non-zero
result of the execution) and sending it back to TEC via another event where
I reference back date_reception and event_handle (to find original event
upon which the task was spawned). Date_reception and event_handle are
variables passed to exec_task.
Maybe not very efficient but it works ...

David




             "john willis"
             <john_willis@gulf
             soft.com>                                                  To
             Sent by:                  
<tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx>
             owner-tme10@lists                                          cc
             .us.ibm.com
                                                                   Subject
                                       RE: [tme10] returning result from
             23/02/2005 10:44          exec_program TEC 3.9


             Please respond to
                   tme10






Can't do it with exec_program/exec_task they are run in a different
process (TEC_Task).  You have two options:

1) Use the undocumented shell predicate (not recommended)
2) Use exec_program_local and it will generate another event when the
program completes with return code and feedback information.  Then in
another rule process the TEC_Task event that is sent back in.


John Willis
Gulf Breeze Software
www.gulfsoft.com
OpenESM Project
www.sourceforge.net/projects/gulfsoft


-----Original Message-----
From: owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx 
[mailto:owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx]
On Behalf Of Hawkett, David
Sent: Wednesday, February 23, 2005 4:25 AM
To: tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx
Subject: [tme10] returning result from exec_program TEC 3.9

Hi List,

Is it possible, and if so could somebody give me some pointers on the
predicates and structure to use to be able to return a result from a
perl script, triggered via exec_program, back to the rule so that the
rule can subsequently proceed dependent on the result returned via the
script ?

many thanks

Dave




____________________________________________________________
CONFIDENTIALITY
This e-mail and any attachments are confidential and also may be
privileged.
If you are not the named recipient, or have otherwise received this
communication in error, please delete it from your inbox, notify the
sender
immediately, and do not disclose its contents to any other person,
use them for any purpose, or store or copy them in any medium.
Thank you for your cooperation.
____________________________________________________________










____________________________________________________________
CONFIDENTIALITY
This e-mail and any attachments are confidential and also may be
privileged.
If you are not the named recipient, or have otherwise received this
communication in error, please delete it from your inbox, notify the sender
immediately, and do not disclose its contents to any other person,
use them for any purpose, or store or copy them in any medium.
Thank you for your cooperation.
____________________________________________________________










____________________________________________________________
CONFIDENTIALITY
This e-mail and any attachments are confidential and also may be privileged.
If you are not the named recipient, or have otherwise received this
communication in error, please delete it from your inbox, notify the sender
immediately, and do not disclose its contents to any other person,
use them for any purpose, or store or copy them in any medium.
Thank you for your cooperation.
____________________________________________________________