File Trigger function

Monitored files, monitoring modes, and information for the job to be started are registered on the File Trigger Information screen or with the Management Information Batch Registration command (utliupdt). Conditions specified on the File Trigger Information screen or with the Management Information Batch Registration command are reread from the File Trigger Information files (hultrg.db) when the Observe daemon starts. When these conditions are loaded, the status of the targeted file is acquired and the monitoring target is determined. Once determined, the information for the monitoring target file is stored in the File Trigger Control file (TriggerID.trgcntl.dat), and is modified and used until the Observe daemon is terminated. The File Trigger Information is identified by a Trigger ID.

Note

  • You can use the File Trigger function if HULFT10 Enterprise grade is installed.

  • Even if a job ends unsuccessfully, file monitoring continues.

  • HULFT10 Enterprise grade achieves the File Trigger function by generating processes for the number of jobs that will startup for the number of IDs to be executed. However, the number of processes that can be generated is limited by the environment. Therefore, when you attempt to monitor many files, it is possible that monitoring might fail for some systems.

  • The number of File Trigger Control files is the same as the number of 'Y (Yes)'s for Activate Monitoring in the registered File Trigger Information. Therefore, disk usage increases proportionally with the number of file triggers to be executed.

  • The size of the File Trigger Control file increases proportionally with the number of files to be monitored.