File Trigger Information (UNIX/Linux)
The information on file trigger function is registered.
You can use the File Trigger Information when you install HULFT7 for UNIX/Linux-EX.
Field List
|
Field Name |
Default Value |
Setting Value |
Optional |
Remarks |
|---|---|---|---|---|
|
Trigger ID |
|
Uppercase alphanumeric characters |
- |
Within 8 bytes |
|
Comment |
|
Characters |
✓ |
Within 60 bytes |
|
File Name |
|
Characters |
- |
Within 200 bytes |
|
Job ID |
|
Alphanumeric characters |
- |
Within 8 bytes |
|
Monitor Creation |
Yes |
(*1) |
- |
|
|
Monitor Deletion |
Yes |
(*1) |
- |
|
|
Monitor Modification |
Yes |
(*1) |
- |
|
|
Monitoring Method |
Time Stamp |
(*1) |
- |
|
|
Check File Occupancy |
Yes |
(*1) |
- |
|
|
Wait File Availability |
Yes |
(*1) |
- |
(*2) |
|
Monitoring Interval |
10 |
From 10 to 2678400 |
- |
Unit: second |
|
Activate Monitoring |
Yes |
(*1) |
- |
|
|
✓ |
: |
Optional |
|
- |
: |
Mandatory |
|
*1 |
: |
On screen, select an option. |
|
*2 |
: |
Available only when the Check File Occupancy is set to 'Yes.' |
Explanation of Each Field
Each field to be set in the File Trigger Information is explained.
- Trigger ID
-
ID to recognize the file to be monitored
- Comment
-
Comment on the File Trigger Information
- File Name
-
The name of the file to be monitored
Specify the name using the absolute path.
You can use asterisk (*) for the File Name. Entering asterisk (*) allows you to monitor more than one file at the same time.
Asterisk (*) can be used for the File Name, but not for the Directory Name. (Entry such as '/home/users/usr1/*testdata/test.txt' is not allowed.)
The File Name with asterisk (*), which exceeds 200 bytes in absolute path, is exempted from monitoring.
- Job ID
-
ID to be started up when HULFT detects creation, deletion, or modification of a file
- Monitor Creation
-
Monitoring the creation of new file
This field specifies whether to monitor the creation of new file.
-
Yes
-
No
-
- Monitor Deletion
-
Monitoring the deletion of file
This field specifies whether to monitor the deletion of file.
-
Yes
-
No
-
- Monitor Modification
-
Monitoring the modification of file
This field specifies whether to monitor the modification of file.
-
Yes
-
No
-
- Monitoring Method
-
Definition when monitoring modification
This field specifies what determines modification of file.
- Time Stamp:
-
Determining modification by time stamp of the file
- File Size:
-
Determining modification by file size of the file
- Check File Occupancy
-
Checking file occupancy
This field specifies whether to check if the file has been used by any process or applications.
-
Yes
-
No
-
- Wait File Availability
-
Behavior when HULFT fails in checking file occupancy
This field specifies whether to have HULFT wait until the application can confirm the availability or to have the attempt end at the time when the application fails in checking file occupancy.
- Yes:
-
Wait
- No:
-
Do not wait
This field is effective only if the Check File Occupancy is set to 'Yes.'
- Monitoring Interval
-
Interval of monitoring file
This field specifies the interval to monitor file in seconds.
- Activate Monitoring
-
Activation status of the registered Trigger ID
This field specifies whether to make the registered Trigger ID target of monitoring.
- Yes:
-
Activate monitoring of file in accordance with settings
- No:
-
Do not activate monitoring of file
Mere creation, deletion, or modification of the File Trigger Information does not enable the change of the monitoring conditions. To make the change of the File Trigger Information effective, it is necessary to restart the Request Acknowledge daemon or to execute the File Trigger Information Control command on HULFT at the connection destination.