Skip to main content
Solved

Setting a flag when execution is done


  • Starter
  • 1 reply

Hi,

We use TX as a part of our value chain of systems using data. We need to programatically be able to check if the execution is done, so the following jobs can start.
I know TX can send an email when completed, but we really do not want to build the check on emails.

Does anyone have a good idea on how to do this?

Hope you can help.

Best regards

Michael Vaisgaard

Best answer by JTreadwell

Hi Michael, You can also execute packages from the command line. In which case TX will return with exit codes after completion. 

see this article for more info: https://legacysupport.timextender.com/hc/en-us/articles/210439143-How-to-Start-an-Execution-Package-from-the-Command-Line

View original
Did this topic help you find an answer to your question?

2 replies

Forum|alt.badge.img
  • Contributor
  • 51 replies
  • April 8, 2020

Hi Michael,

TX can run a script before and / or after the complete BU / DWH is processed.

You could create a simple custom table with a "Processed" and / or a "Date Processed" field that you perform a TRUNCATE against before BU / DWH processing starts and a SET or UPDATE statement against that after the BU and / or DWH is processed.

In your value chain you can then check against the status of the table. If it hasn't been marked as processed, don't start the next job yet.

We use this way of working as well for systems that depend on a BU or DWH being completely processed.

Kind Regards,

Wim


JTreadwell
Employee
Forum|alt.badge.img+5
  • Employee
  • 179 replies
  • Answer
  • April 15, 2020

Hi Michael, You can also execute packages from the command line. In which case TX will return with exit codes after completion. 

see this article for more info: https://legacysupport.timextender.com/hc/en-us/articles/210439143-How-to-Start-an-Execution-Package-from-the-Command-Line


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings