The job chain node attribute on_error="suspend" should suspend an order when a job without monitor exits with error

Current Situation

With the following precondition

• a job is configured with <job stop_on_error="yes">
• and a job node in a job chain is configured with <job_chain_node on_error="suspend">
• then the job terminates with exit code > 0

A shell job with preprocessing monitor then shows the following behavior:

• The order will be displayed as being suspended in JOC
• The job ist stopped.
• After resuming the order is in the status running
• If the job is unstopped then the order again is displayed as being suspended in JOC.

A shell job without pre-processing monitor shows this behavior:

• The order will be displayed with the status running in JOC
• The job is stopped
• After resuming the order is in the status running
• If the job is unstopped then the order again is displayed as running in JOC

Desired Behavior

• The desired behavior for jobs without pre-processing monitor is the same as for a shell jobs with pre-propressing monitor.

Workaround
As a workaround, you can add a dummy pre-processing monitor to your jobs.

1. 1. Add a <monitor.use> element to your jobs

      <job  order="yes" stop_on_error="yes">
          <script  language="shell">
              <![CDATA[
      /u01/informatica/JOB_SCHED/infa_call_wf.sh wf_FEED_ACCOUNT_EXTRACT 3NF
              ]]>
          </script>
          <monitor.use  monitor="/dummy_monitor"/>
          <run_time />
      </job>
      

   2. Then add the dummy monitor to the root folder.

       <monitor  name="dummy_monitor" ordering="0">
                  <script  language="java:javascript">
                      <![CDATA[
      function spooler_process_before(){
          return true;
      }
                      ]]>
                  </script>
              </monitor>