Jobs utilizing custom profiles fail with Exit Code 213 after upgrading System Agent from 11.3.x to 12.1.x.
search cancel

Jobs utilizing custom profiles fail with Exit Code 213 after upgrading System Agent from 11.3.x to 12.1.x.

book

Article ID: 434283

calendar_today

Updated On:

Products

Autosys Workload Automation Workload Automation Agent

Issue/Introduction

Following an upgrade from System Agent version 11.3.x to 12.1.x, certain AutoSys jobs that utilize custom job profiles fail immediately with Exit Code 213.
The jobs do not reach the execution phase and fail during the environment setup process Jobs failing with exit code 213.

Environment

System Agent 12.1.1 and later on Unix/Linux

Cause

The System Agent version 12.1 enforces strict Bourne-shell (/bin/sh) compliance for processing job profiles. Older versions (11.3.x) were more lenient and allowed Bash/Korn-shell syntax where variable assignment and the export command occur on the same line (e.g., export VAR=value). This syntax is not supported in the strict Bourne shell, causing the agent to encounter a syntax error and crash the setup process Jobs failing with exit code 213.

Resolution

To resolve this, two actions are required:

  1. Profile Syntax Correction: The custom job profiles must be updated to be strictly Bourne-shell compliant. This means separating the variable assignment from the export command onto two different lines.

    • Incorrect (Fails in 12.1): export VAR1=var1

    • Correct (Works in 12.1): VAR1=var1
                                                export VAR1

  2. Agent Configuration Verification: Ensure the agentparm.txt file is properly configured to force the command prefix (oscomponent.cmdprefix.force=true), guaranteeing the agent sources these updated profiles correctly.

 

Once the profile syntax is corrected, the agent will cleanly load the environment variables, and the jobs will execute successfully.