File trigger event scheduled from CAWA EE (ESP) server to windows agent, monitoring remote file doesn't work

book

Article ID: 49571

calendar_today

Updated On:

Products

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

Issue/Introduction

Description:

A File Monitor job doesn't work when scheduled from CA Workload Automation EE ESP server to CA Workload Automation System Agent for Windows while monitoring a remote file. Example of job definition:

     FILE_TRIGGER XCSLD026.FW     
     FILENAME '\\xx\xxx\xxxxxxxxxxxxxx\Mass Updates\xxx Updates\+     
     OAEX\*.csv' CREATE NOCHANGE(1) CONTINUOUS($ESP.XCSLD026)     
     RUN DAILY     
     AGENT pmnams1578     
     ENDJOB 

Error:

     MgrMsg: pmnams1578 XCSLD026.FW/XCSFW.22/MAIN STATE FAILED Status("Scan     
     Failed") LStatus("The     
     D:\xx\xxx\xxxxxxxxxxxxxx\Mass Updates\xxx Updates\OAEX does not     
     exist or not a directory") SetEnd     
     Cmpc(1) Plugin(filemon) User(pmnams1578) Host(pmnams1578)

Solution:

The error is because the agent doesn't correctly interpret the initial "\" in the UNC path of the remote file. Before the official fix comes out, the workaround is to specify the monitored file as:

     '\\\xx\xxx\xxxxxxxxxxxxxx\Mass Updates\xxx Updates\OAEX\*.csv' 

That is, single quote, 3 backslashes at beginning and single backslashes follows.

Environment

Release:
Component: SYSAGT