File Trigger Information

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

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 registration by running commands with parameter files, refer to Management Information Batch Registration command.

Table 2.14 List of File Trigger Information Fields

Field Value		Default Value	Setting Value	Optional	Remarks
Screen	File
Trigger ID	TRGID		Uppercase alphanumeric characters and "_"	-	Within 50 bytes
Comment	COMMENT		Characters	✓	Within 60 bytes
Path to Directory	DIRECTORYNAME		Characters	-	Within 200 bytes (*1)
File Name	TARGETFILENAME		Alphanumeric characters	-	Within 200 bytes (*1)
Job ID	JOBID		Alphanumeric characters and "_"	-	Within 50 bytes
Monitor Subdirectories	SUBDIRECTORY	N	Y, N	✓
Use Regular Expression	REGEX	N	Y, N	✓
Monitor Creation	CREATE	Y	Y, N	✓
Monitor Deletion	DELETE	Y	Y, N	✓
Monitor Modification	MODIFY	Y	Y, N	✓
Monitoring Method	TYPE	T	T, S	✓
Check File Occupancy	FILECHECK	Y	Y, N	✓
Wait File Availability	FILECHECKWAIT	Y	Y, N	✓
Check Interval	INTERVAL	10	10–2678400	-	Unit: seconds
Activate Monitoring	EXECUTION	Y	Y, N	✓

✓	:	Optional
-	:	Mandatory

*1

:

The total length of the strings that you specify for Path to Directory (DIRECTORYNAME) and File Name (TARGETFILENAME) must be within 200 bytes.

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)

Directory 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 'N' (Do not use a regular expression) 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 subdirectories

Specify whether to monitor subdirectories.

Y:

Monitor subdirectories

N:

Do not monitor subdirectories

Omitting this field sets 'N' (Do not monitor subdirectories).

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.

Y:

Use a regular expression

N:

Do not use a regular expression

Omitting this field sets 'N' (Do not use a regular expression).

Monitor Creation (CREATE)

Monitoring for the creation of a new file

Specify whether to monitor for the creation of a new file.

Y:

Yes

N:

No

Omitting this field sets 'Y' (Yes).

Monitor Deletion (DELETE)

Monitoring for the deletion of a file

Specify whether to monitor for the deletion of a file.

Y:

Yes

N:

No

Omitting this field sets 'Y' (Yes).

Monitor Modification (MODIFY)

Monitoring for the modification of a file

Specify whether to monitor for the modification of a file.

Y:

Yes

N:

No

Omitting this field sets 'Y' (Yes).

Monitoring Method (TYPE)

Definition when monitoring for modification

Specify how HULFT determines that the file was modified.

T:

Determine whether the file has been modified based on the time stamp

S:

Determine whether the file has been modified based on the file size

Omitting this field sets 'T' (Determine the modification of a file by referring to the time stamp).

Check File Occupancy (FILECHECK)

Checking file occupancy

Specify whether to check if the file has been used by any other processes or applications.

Y:

Yes

N:

No

Omitting this field sets 'Y' (Yes).

When you specify 'N' (No), you must specify 'N' (No) 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.

Y:

Wait

N:

Do not wait

You can specify either 'Y' (Yes) or 'N' (No) for this field when you specify 'Y' (Yes) for Check File Occupancy (FILECHECK).

Specify 'N' (No) for this field when you specify 'N' (No) for Check File Occupancy. If you specify 'Y' (Yes) for this field, an error occurs.

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.

Y:

Yes

N:

No

Omitting this field sets 'Y' (Yes).

Points to be noted when setting