{"id":17086,"date":"2022-01-31T01:23:28","date_gmt":"2022-01-31T00:23:28","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/how-to-manage-job-log-in-on-do-action\/"},"modified":"2022-05-31T16:32:20","modified_gmt":"2022-05-31T14:32:20","slug":"how-to-manage-job-log-in-on-do-action","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/how-to-manage-job-log-in-on-do-action\/","title":{"rendered":"How to trigger an action in On Do Action based of a text in the Job Log output"},"content":{"rendered":"

Normally we can trigger an On Do Action based on string found in the Job Output.
\nBut we would like to do the same for a Job log, that feature doesn\u2019t exist, but there is a way to make it working.
\nLet’s see how to proceed.<\/p>\n

<\/p>\n

Introduction<\/h2>\n

\nFor example: as a use case:
\nSee the blog How to automate a kill of one or several executing jobs in AJF at specific Date\/Time at once<\/a>, when the a running job is killed in purpose with the ctmkilljob utility, the job ends with a NOTOK State (red).
\nThe issue of that, if we manage a On-Do Action on NOTOK situations, those Actions will be triggered.
\nWe can avoid triggering those On-Do Actions for this specific context (job killed) by following the procedure below.
\nIn this example, we will re-use the same case which is to automate a Kill of a job from another job:<\/p>\n

Preparation<\/h2>\n

Define 2 jobs<\/h3>\n