ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Unix Agent in mode Batch job remains in status Active after :EXIT 0

book

Article ID: 226689

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

On Agents Unix/Linux in mode batch (start_type=batch), JOBS with :EXIT X in the Process or Preprocess have a different behavior compared to mode fork.

For example, if the job contains :EXIT 0 in the Process or Preprocess, the results are:

  1. JOBS.UNIX.EXIT0_PROCESS - job finishes in ENDED_VANISHED - disappeared (different behavior than in fork)
  2. JOBS.UNIX.EXIT0_PREPROCESS - Job remains in Active Status (different behavior than in fork) with the following in Activation log:
    2021-08-30 17:47:40 - U00020411 The command 'EXIT 0000000000' in 'JOBS.UNIX.EXIT0.PREPROCESS(1)', line '00002' stopped the generation of this task.

Cause

This has been confirmed to be a limitation/problem of the batch mode of the Unix Agents.

Environment

Release : 12.x

Component : AUTOMATION ENGINE

Subcomponent: Unix Agent

Resolution

This will be fixed in an ulterior version of the Unix Agent via the case AE-27013

Powered by Wolken Software