AutoSys OMTF Job Slow to Transition to RUNNING Status on Large Files

Products

• Workload Automation Agent

Issue/Introduction

When executing an OMTF (Output Monitoring and Text Filtering) job against a large target file, there is a noticeable delay in transitioning the job status from STARTING to RUNNING.

Environment

 

• Product: AutoSys Workload Automation / System Agent

• Component: OMTF Job Type / File Monitoring

 

Cause

The System Agent is hardcoded to read and process target files starting sequentially from the beginning (top) of the file. For very large log or data files, reading through the entire file from the start causes execution latency before the agent can evaluate the condition and update the job state to RUNNING.

Resolution

If timing and performance are critical, consider replacing or supplementing the OMTF job with a custom script run as a Command (CMD) job that inspects the end of the file rather than reading from the beginning.

Script Example (Linux / UNIX):

Bash

 

#!/bin/sh
FILE="<filename>"

# Verify the file exists before starting
if [ ! -f "$FILE" ]; then
    echo "Error: File $FILE does not exist."
    exit 1
fi

# Tail newly added lines (-n 0) and exit on first match (-m 1)
tail -n 0 -f "$FILE" | grep -m 1 "ERROR" > /dev/null
echo "String 'ERROR' detected in $FILE. Exiting script."
exit 0

 

Additional Information

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on the respective region.