List of File Trigger Information fields
You can register the File Trigger Information. There are two ways to register the information.
-
Registration using the HULFT Management Console
=> Refer to Using the File Trigger Information
-
Registration by running commands with parameter files
=> Refer to Management Information Batch Registration command
You can use the File Trigger Information database only if the HULFT10 Server grade is installed.
Field List
In the table below, the check marks in the Optional column indicate the fields considered optional during registration from the HULFT Management Console. Optional fields and mandatory fields for registration by running commands with parameter files may differ from those for registration using the HULFT Management Console.
For details on optional fields and mandatory fields for the registration by running commands with parameter files, refer to Management Information Batch Registration command.
|
Field Name |
Default Value |
Setting Value |
Optional |
Remarks |
|
|---|---|---|---|---|---|
|
Screen |
File |
||||
|
TRGID |
|
Uppercase alphanumeric characters and "_" |
- |
Within 50 bytes |
|
|
COMMENT |
|
Characters |
✓ |
Within 60 bytes |
|
|
DIRECTORYNAME |
|
|
- |
Within 200 bytes (*1) |
|
|
TARGETFILENAME |
|
Characters |
- |
Within 200 bytes (*1) |
|
|
JOBID |
|
Alphanumeric characters and "_" |
- |
Within 50 bytes |
|
|
SUBDIRECTORY |
No (N) |
Y, N |
✓ |
|
|
|
REGEX |
No (N) |
Y, N |
✓ |
|
|
|
CREATE |
Yes (Y) |
Y, N |
✓ |
(*2) |
|
|
DELETE |
Yes (Y) |
Y, N |
✓ |
(*2) |
|
|
MODIFY |
Yes (Y) |
Y, N |
✓ |
(*2) |
|
|
TYPE |
Time Stamp (T) |
T, S |
✓ |
(*2) |
|
|
FILECHECK |
Yes (Y) |
Y, N |
✓ |
(*2) |
|
|
FILECHECKWAIT |
Yes (Y) |
Y, N |
✓ |
(*2) |
|
|
INTERVAL |
10 |
10–2678400 |
- |
Unit: seconds |
|
|
EXECUTION |
Yes (Y) |
Y, N |
✓ |
(*2) |
|
|
USER |
|
Characters |
✓ |
Within 20 bytes (*3) |
|
|
DOMAIN |
|
Alphanumeric characters |
✓ |
Within 64 bytes |
|
|
PASSWD |
|
Alphanumeric characters |
✓ |
Within 127 bytes |
|
|
✓ |
: |
Optional |
|
- |
: |
Mandatory |
|
*1 |
: |
The total size of the strings that you specify for Path to Directory (DIRECTORYNAME) and File Name (TARGETFILENAME) must be within 200 bytes. |
|
*2 |
: |
For the HULFT Management Console, click a setting value on the pulldown list. |
|
*3 |
: |
Count as 1 character, regardless of half-width or full-width characters. |
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 File Trigger Information
- Path to Directory (DIRECTORYNAME)
-
Folder that contains the file to be monitored
Specify this field with a full path.
You cannot use a regular expression or a wild card for this field.
- File Name (TARGETFILENAME)
-
Name of the file to be monitored
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).
- Job ID (JOBID)
-
ID of the job to be started when HULFT detects creation, deletion, or modification of a file
- Monitor Subdirectories (SUBDIRECTORY)
-
Monitoring of subfolders
Specify whether to monitor subfolders.
- Yes (Y):
-
Monitor subfolders
- No (N):
-
Do not monitor subfolders
Omitting this field sets 'No' (N).
- Use Regular Expression (REGEX)
-
Use of a regular expression to specify the file name
Specify whether to use a regular expression to specify the file name.
- Yes (Y):
-
Use a regular expression
- No (N):
-
Do not use a regular expression
Omitting this field sets 'No' (N).
- Monitor Creation (CREATE)
-
Monitoring for the creation of a new 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).
-
- User Name (USER)
-
Name of the user who starts a job
The spaces before or after the characters are deleted.
When you omit this field, the job is started by the user who started the Observe process.
- Domain Name (DOMAIN)
-
Domain name to which the user belongs
The spaces before or after the characters are deleted.
- Password (PASSWD)
-
User password
Points to be noted when setting
User Name
If you try to execute a job for which a user name is specified, the job may not be executed correctly in the following cases:
-
When the account information has already been set in the System Environment Settings
-
When a logon account is set for the HULFT service on the Services screen in Windows
For details, refer to the following:
HULFT10 for Windows Administration Manual : Operation by users other than Windows system administrator
How to make 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 process or to execute the File Trigger Information Control command on HULFT at the connection destination.
File Name
-
You can monitor more than one file at the same time by using either of the following options:
-
Regular expression
When you use a regular expression for the File Name, specify 'Yes' (Y) for Use Regular Expression.
-
Wild card
When you use a wild card in the file name, specify 'No' (N) for Use Regular Expression.
You can use a wild card as shown below.
Example:
When you want to monitor all files with an extension of txt in the folder that you specify for Path to Directory, specify '*.txt' for File Name.
-
-
If the total length of the directory name and the file name that you specify for Path to Directory and File Name exceeds 200 bytes, the file is not monitored. When you use a regular expression or use an asterisk (*) for a wild card, pay attention to the total length of the directory name and the file name.