dmitry t

Thank you both Uwe and MishaF, You have been both very helpful. I'm running following JS instance: Release linux-x64 1.10.4 JOC Build: 7429d6eca97e97e374d27557eb73c2d26dc0ebf6 (2016-04-22) I'm moving forward with mixing setback and suspend option to handle failures in ETL. It is working solid and works in split (parallel) chains as well. I'm happy with the results. Dummy jobs can also be used to start specific notification processes. This approach seems to be handling another issue I had some time...

I guess what I need is to replicate a following functionality - if that is at all possible. If a job fails - go to setback mode for a job to retry a number of times defined in SetBack job option. If a Job or in case of a chain node is still fails after it reached maximu retries than suspend it. After a node is suspended an operator has an option to re-start a node from JOC or skip it.

Thank you MishaF, I've have actually done some research and I think I understand my dilemma a bit better now. But I'm still not 100% there, perhaps if I explain what I'm trying to do you can point me to the right approach. Simply put. I have a single JobScheduler(JS) job that I reuse multiple time in the chain (sequentually) that in turn launches a specific ETL job based on the parameter (name of ETL job) that I pass to it. During a nightly production run, If an ETL job fails due to some reason (ex....

Greetings, If this topic was discussed before please point me to the right location. But here is my dilemma. I'm using JobScheduler to execute batch ETL jobs at a particular time. I'm using a single job multiple times in the chain to launch ETL jobs: Below is the sample of my job: <job name="T_RUN_DMX_TASK_1" title="Run ETL DMX 1"> <settings> <mail_on_error><![CDATA[yes]]></mail_on_error></settings></job> <mail_on_delay_after_error ><![CDATA[last_only]]></mail_on_delay_after_error> </settings> <params...

Greetings, If this topic was discussed before please point me to the right location. But here is my dilemma. I'm using JobScheduler to execute batch ETL jobs at a particular time. I'm using a single job multiple times in the chain to launch ETL jobs: Below is the sample of my job: <job name="T_RUN_DMX_TASK_1" title="Run ETL DMX 1"> <settings> <mail_on_error><![CDATA[yes]]></mail_on_error></settings></job> <mail_on_delay_after_error ><![CDATA[last_only]]></mail_on_delay_after_error> </settings> <params...

Greetings, If this topic was discussed before please point me to the right location. But here is my dilemma. I'm using JobScheduler to execute batch ETL jobs at a particular time. I'm using a single job multiple times in the chain to launch ETL jobs: Below is the sample of my job: <job name="T_RUN_DMX_TASK_1" title="Run ETL DMX 1"> <settings> <mail_on_error><![CDATA[yes]]></mail_on_error></settings></job> <mail_on_delay_after_error ><![CDATA[last_only]]></mail_on_delay_after_error> </settings> <params...

Greetings, If this topic was discussed before please point me to the right location. But here is my dilemma. I'm using JobScheduler to execute batch ETL jobs at a particular time. I'm using a single job multiple times in the chain to launch ETL jobs: Below is the sample of my job: <job name="T_RUN_DMX_TASK_1" title="Run ETL DMX 1"> <settings> <mail_on_error><![CDATA[yes]]></mail_on_error></settings></job> <mail_on_delay_after_error ><![CDATA[last_only]]></mail_on_delay_after_error> </settings> <params...

Greetings, If this topic was discussed before please point me to the right location. But here is my dilemma. I'm using JobScheduler to execute batch ETL jobs at a particular time. I'm using a single job multiple times in the chain to launch ETL jobs: Below is the sample of my job: <?xml version="1.0" encoding="ISO-8859-1"?> <job name="T_RUN_DMX_TASK_1" title="Run ETL DMX 1"> <settings> <mail_on_error><![CDATA[yes]]></mail_on_error></settings></job> <mail_on_delay_after_error ><![CDATA[last_only]]></mail_on_delay_after_error>...