AutoSys Global Variables — Sharing Data Between Jobs

AutoSys global variables are name-value pairs stored in the Event Server that any job can read and write at runtime. They're the primary mechanism for passing data between jobs in a batch pipeline — processing counts, file paths, status flags, dates.

This is a feature that's easy to misuse (overusing globals creates hidden dependencies), but when used well it's powerful.

Setting a global variable from a job

Jobs set global variables using the sendevent command with the SET_GLOBAL event. This can be done from within the job's script or from the command line.

#!/bin/bash
# Script that processes records and sets the count as a global variable

RECORD_COUNT=$(wc -l < /data/processed_trades.csv)

# Set the global variable in AutoSys
sendevent -E SET_GLOBAL -G "TRADE_COUNT=${RECORD_COUNT}"

echo "Processed ${RECORD_COUNT} trades, set TRADE_COUNT global variable"
exit 0

Reading a global variable in a JIL condition

You can reference global variables in JIL conditions using the variable() function. This lets you create data-driven conditions.

/* Read a global variable in a condition */
insert_job: validate_trade_count
job_type: CMD
command: "/scripts/validate_count.sh ${TRADE_COUNT}"
machine: server01
owner: batch
condition: success(process_trades) AND variable(TRADE_COUNT) >= 1

/* Set a global variable via sendevent from command line */
# sendevent -E SET_GLOBAL -G "PROCESS_DATE=20260319"

/* Check current value of a global variable */
# autostatus -G TRADE_COUNT

Global variable naming, lifecycle, and best practices

Global variables persist in the Event Server until explicitly changed or cleared. They do not reset between daily runs — a value set yesterday is still there today unless something overwrites it. This is both powerful and dangerous.

Best practices: 1. Always use a naming convention with a workflow prefix (e.g., TRADING_RECORD_COUNT not just COUNT) 2. Reset flags and counters at the start of each workflow run, not the end 3. Document every global variable your workflow uses — undocumented globals become tribal knowledge 4. Audit global variables periodically with autostatus to catch stale or orphaned ones

# PATTERN: Reset globals at the START of a workflow (not end)
# Add this as the first job in your box:

insert_job: PRD_TRADING_RESET_GLOBALS
job_type: CMD
box_name: PRD_TRADING_EOD_BOX
command: /scripts/reset_trading_globals.sh
machine: server01
owner: batch
# No condition — first job in box

# reset_trading_globals.sh contents:
# sendevent -E SET_GLOBAL -G "TRADING_RECORD_COUNT=0"
# sendevent -E SET_GLOBAL -G "TRADING_STATUS_FLAG=PENDING"
# sendevent -E SET_GLOBAL -G "TRADING_PROCESS_DATE=$(date +%Y%m%d)"

# List all current global variables
autostatus -G %

Frequently Asked Questions