List of File Trigger Information fields
You can register the File Trigger Information. For the registration method, refer to Using the File Trigger Information.
You can use the File Trigger Information database only if HULFT10 Enterprise grade is installed.
Field List
Field Name |
Default Value |
Setting Value |
Optional |
Remarks |
|
---|---|---|---|---|---|
Screen |
File |
||||
TRGID |
|
Uppercase alphanumeric characters and "_" |
- |
Within 50 bytes |
|
COMMENT |
|
Characters |
✓ |
Within 60 bytes (*1) |
|
DIRECTORYNAME |
|
Characters |
- |
Within 200 bytes (*2)(*3) |
|
TARGETFILENAME |
|
Characters |
- |
Within 200 bytes (*3) |
|
JOBID |
|
Alphanumeric characters and "_" |
- |
Within 50 bytes |
|
SUBDIRECTORY |
No (N) |
(*4) |
✓ |
(*2) |
|
REGEX |
No (N) |
(*4) |
✓ |
(*2) |
|
CREATE |
Yes (Y) |
(*4) |
✓ |
||
DELETE |
Yes (Y) |
(*4) |
✓ |
||
MODIFY |
Yes (Y) |
(*4) |
✓ |
||
TYPE |
Time Stamp (T) |
(*4) |
✓ |
||
FILECHECK |
Yes (Y) |
(*4) |
✓ |
||
FILECHECKWAIT |
Yes (Y) |
(*4) |
✓ |
|
|
INTERVAL |
10 |
10–2678400 |
- |
Unit: seconds |
|
EXECUTION |
Yes (Y) |
(*4) |
✓ |
✓ |
: |
Optional |
- |
: |
Mandatory |
*1 |
: |
On the HULFT Manager Management Console, you can enter a string of up to 60 characters. When the destination host is HULFT Ver.8.1 or higher, the size of the string that you entered will be checked based on the code set that is set in HULFT at the connection destination. When HULFT checks and confirms that the size of the string meets the condition that is given in the remarks, the characters that you entered will be saved in HULFT. |
*2 |
: |
This field is displayed when HULFT Manager connects to HULFT Ver.8.1 or higher. |
*3 |
: |
The total length of the strings that you specify for Path to Directory (DIRECTORYNAME) and File Name (TARGETFILENAME) must be within 200 bytes. |
*4 |
: |
For the HULFT Manager Management Console, click a setting value on the pulldown list. |
Explanation of each field
This section explains the fields to be specified in the File Trigger Information. The parenthesized strings are the names of each field and you can use them as field tags in a parameter file when registering the information.
- Trigger ID (TRGID)
-
ID that identifies the file to be monitored
- Comment (COMMENT)
-
Comment for the trigger ID
- Path to Directory (DIRECTORYNAME)
-
Directory that contains the file to be monitored
This field is displayed when HULFT Manager connects to HULFT Ver.8.1 or higher.
You cannot use a regular expression or a wild card for this field.
- File Name (TARGETFILENAME)
-
Name of the file to be monitored
Depending on whether HULFT Manager connects to HULFT Ver.8.1 or higher or to HULFT lower than Ver.8.1, the contents to be specified differ as follows:
-
When HULFT Manager connects to HULFT Ver.8.1 or higher
Specify a file name.
Use a regular expression or a wild card to monitor multiple files at the same time.
When you use a wild card, you must specify 'No (N)' for Use Regular Expression (REGEX).
-
When HULFT Manager connects to HULFT lower than Ver.8.1
Specify the file name with a full path.
You can use an asterisk (*) for the file name. Entering an asterisk (*) allows you to monitor more than one file at the same time.
An asterisk (*) can be used for the file name, but not for the folder name.
(An entry such as '/home/users/usr1/*testdata/test.txt' is not allowed.)
A file name with an asterisk (*) that exceeds 200 bytes in a full path is exempted from monitoring.
-
- Job ID (JOBID)
-
The ID of the job to be started when HULFT detects creation, deletion, or modification of a file
- Monitor Subdirectories (SUBDIRECTORY)
-
Monitoring of subdirectories
This field is displayed when HULFT Manager connects to HULFT Ver.8.1 or higher.
This field specifies whether or not to monitor subdirectories.
-
Yes (Y)
-
No (N)
Omitting this field sets 'No (N).'
-
- Use Regular Expression (REGEX)
-
Use of a regular expression to specify the file name
This field is displayed when HULFT Manager connects to HULFT Ver.8.1 or higher.
Specify whether to use a regular expression to specify the file name.
-
Yes (Y)
-
No (N)
Omitting this field sets 'No (N).'
-
- Monitor Creation (CREATE)
-
Monitoring for the creation of a file
Specify whether to monitor for the creation of a new file.
-
Yes (Y)
-
No (N)
Omitting this field sets 'Yes (Y).'
-
- Monitor Deletion (DELETE)
-
Monitoring for the deletion of a file
Specify whether to monitor for the deletion of a file.
-
Yes (Y)
-
No (N)
Omitting this field sets 'Yes (Y).'
-
- Monitor Modification (MODIFY)
-
Monitoring for the modification of a file
Specify whether to monitor for the modification of a file.
-
Yes (Y)
-
No (N)
Omitting this field sets 'Yes (Y).'
-
- Monitoring Method (TYPE)
-
Definition when monitoring for modification
Specify how HULFT determines that the file was modified.
- Time Stamp (T):
-
Determine whether the file has been modified based on the time stamp
- File Size (S):
-
Determine whether the file has been modified based on the file size
Omitting this field sets 'Time Stamp (T).'
- Check File Occupancy (FILECHECK)
-
Checking file occupancy
Specify whether to check if the file has been used by any other processes or applications.
-
Yes (Y)
-
No (N)
Omitting this field sets 'Yes (Y).'
When you specify 'No (N),' you must specify 'No (N)' for Wait File Availability (FILECHECKWAIT).
-
- Wait File Availability (FILECHECKWAIT)
-
Behavior of HULFT when the checking file occupancy fails
Specify 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 (Y)
-
No (N)
You can specify either 'No (N)' or 'Yes (Y)' for this field when you specify 'Yes (Y)' for Check File Occupancy (FILECHECK).
The setting for this field is disabled and 'No (N)' is automatically set when you specify 'No (N)' for Check File Occupancy.
When you omit this field, this field is set to 'Yes' (Y) if you specify 'Yes' (Y) and 'No' (N) if you specify 'No' (N) for Check File Occupancy, respectively.
-
- Check Interval (INTERVAL)
-
Interval for checking files
Specify the interval for checking files in seconds.
- Activate Monitoring (EXECUTION)
-
Activation status of the registered trigger ID
Specify whether to make the registered trigger ID a target for monitoring.
-
Yes (Y)
-
No (N)
Omitting this field sets 'Yes (Y).'
-
Points to be noted when configuring settings
How to make the specified monitoring conditions effective
Mere creation, deletion, or modification of the File Trigger Information does not enable the change of the monitoring conditions.
To enable the change of the File Trigger Information, it is necessary to restart the Observe daemon or to execute the File Trigger Information Control command on HULFT at the connection destination.
File Name
-
Use a wild card in the file name to monitor multiple files at the same time.
When HULFT Manager connects to HULFT Ver.8.1 or higher and you use a wild card in the file name, specify 'No (N)' for Use Regular Expression.
You can use a wild card in HULFT Ver.8.1 or higher as shown below.
Example:
When you want to monitor all files with a txt extension in the directory that you specified for Path to Directory, enter '*.txt' for File Name.
-
When HULFT Manager connects to HULFT Ver.8.1 or higher, you can use a regular expression to monitor more than one file at the same time.
When you use a regular expression in the file name, specify 'Yes (Y)' for Use Regular Expression.
-
When HULFT Manager connects to HULFT Ver.8.1 or higher, if the total length of the directory name and the file name that you specify for Path to Directory and the file name exceeds 200 bytes, the file is not monitored. Pay attention to the number of bytes that you specify for Path to Directory and File Name when you use a regular expression or use an asterisk (*) for a wild card.