Previous Topic: Monitor a File that is Owned by a UNIX Owner or GroupNext Topic: FTP Jobs


Monitor a File on a Remote Windows Computer

You can define a File Trigger job to monitor a file on a remote Windows system if the agent runs as a Windows service under the local system account.

To monitor a file on a remote Windows computer

  1. Verify with your agent administrator that the agent is running as a Windows service under the local system account.
  2. Ask your scheduling manager administrator to define a user ID and password on the scheduling manager that has access to the file on the remote Windows computer.
  3. Specify the file name to monitor in the FILENAME statement in the job definition using UNC (Universal Naming Convention). A UNC name is the name of a file or other resource that begins with two backslashes (\\), indicating that it exists on a remote computer.
  4. Specify the user ID and the domain the user ID belongs to in the USER statement.

Example: Monitor for an Update to a File on a Remote Windows System

This example monitors for an update to the payroll.dat file on a remote Windows computer named CYBNT. The job runs under JSMITH, which is a user ID on CYBNT and is in the CYBDOM domain. JSMITH is defined on the scheduling manager and has access to the AccountingFiles directory.

AGENT SYSAGENT
FILENAME \\CYBNT\AccountingFiles\payroll.dat UPDATE
USER CYBDOM\JSMITH