search cancel

File Trigger event unable to find file due to RegEx being interpreted literally

book

Article ID: 200773

calendar_today

Updated On:

Products

CA Workload Automation DE - Business Agents (dSeries) CA Workload Automation DE DSERIES- SERVER CA Workload Automation DE - System Agent (dSeries) CA Workload Automation DE - Scheduler (dSeries)

Issue/Introduction

A File trigger will not trigger a job event to run even though the file exists

Example:  /inbound/steve*[0-9][0-9].csv

Environment

Release : 11.5

Component : CA Workload Automation System Agent

Resolution

When using regular expressions in filenames, the file trigger event and job are interpreting literally. To address, please see https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/workload-automation-system-agent/11-3/installing/migrate-an-esp-system-agent-to-r11-3/migrate-an-esp-system-agent-to-11-3-changes-to-existing-features.html and scroll to the section that discusses Support for Regular Expressions in File Trigger Jobs.

Add the following parameters to your agentparm.txt file and recycle the agent for settings to take effect.

filemon.filename.r7regex=true
filemonplugin.scan.splitwildcard.disable=true