File Trigger Jobs › Monitor a File that is Owned by a UNIX Owner or Group

Monitor a File that is Owned by a UNIX Owner or Group

You can define a File Trigger job to monitor a file that is owned by a specific UNIX owner or group. If the file is not owned by the specified owner or group, the following occurs:

• The job continues monitoring if the file trigger type is CREATE.
• The job completes if the file trigger type is DELETE or NOTEXIST.
• The job fails if the file trigger type is EXPAND, EXIST, SHRINK, or UPDATE.

Note: You can monitor a file owned by a specific owner or group on i5/OS if the file is not a QSYS object.

To monitor a file that is owned by a UNIX owner or group, specify the OWNER or GROUP operands in the FILENAME statement in the job definition.

Example: Monitor for the Creation of a File that Is Owned by a Specified UNIX User ID

This example monitors for the creation of a file named payroll.dat owned by JDOE:

AGENT SYSAGENT
FILENAME /data/payroll.dat CREATE OWNER(JDOE)

The job completes as follows:

• If the file does not exist when the job is readied, the job does not complete until the file is created.
• If the file exists and the owner of the file is JDOE when the job is readied, the job completes immediately.
• If the file exists or is created, but the owner of the file is not JDOE, the job does not complete. It waits until all specified criteria are satisfied, including the OWNER criteria. If the owner of the file changes to JDOE, the job completes.

Example: Monitor for the Existence of a File that Is Owned by a Specified UNIX Group

This example monitors for the existence of the payroll.dat file that is owned by the UNIX group ACCTS:

AGENT SYSAGENT
FILENAME /data/payroll.dat EXIST GROUP(ACCTS)

The job completes as follows:

• If the file exists and the file is owned by the group ACCTS when the job is readied, the job completes immediately.
• If the file exists and the file is not owned by the group ACCTS when the job is readied, the job fails.