File Trigger service settings

If HULFT acknowledges a file trigger service, it changes the Observe Definition file in accordance with the environment in which the application works.

Note

If a file trigger is not started, do not include the parameter for the file trigger (HULTRG) in the Observe Definition file (service.db).

Description in the Observe Definition file

HULTRG [filename]

Parameter explanation

filename

The file name to output the job execution result is specified.

Specify a string of alphanumeric characters within 128 bytes. Specify the file name as a full path string. If you do not specify a file name, the default value '/dev/console' is used as the file name.

Job result output contents

ID=trigger ID FILENAME=Monitored File Name JOBID=Job ID
DATE=Job Start Date STIME=Job Start Time ETIME=Job End Time RC=Job Status Code JOB=Executed Job

<Output example>

ID=TRG01 FILENAME=/home/users/usr1/test.sh JOBID=JOB01 
ID=TRG01 FILENAME=/home/users/usr1/TEST.dat DATE=2014/12/01 STIME=21:50:28 ETIME=21:50:33 RC=0000 JOB=/home/users/usr/tool.sh (one line up to here) 
ID=TRG01 FILENAME=/home/users/usr1/TEST.dat DATE=2014/12/01 STIME=21:50:33 ETIME=21:50:35 RC=0000 JOB=/home/users/usr/tool.sh (one line up to here) 
ID=TRG01 FILENAME=/home/users/usr1/TEST.dat DATE=2014/12/01 STIME=21:50:35 ETIME=21:50:37 RC=0000 JOB=/home/users/usr/tool.sh (one line up to here)

= Remarks =

When two or more jobs are registered in the Job ID, HULFT repeats the descriptions from 'ID' to 'JOB' the number of times that the application executed the jobs and outputs them as execution results.

<Message explanation>

ID:

Trigger ID (50 bytes)

FILENAME:

Monitored file name

JOBID:

Job ID (50 bytes)

DATE:

Job start date

STIME:

Job start time (hh:mm:ss)

ETIME:

Job end time (hh:mm:ss)

RC:

Job status code, or signal No. (4 bytes) if ended due to a signal

JOB:

Job execution

Note

The job start date is displayed in the date format specified for Date Format (datefmt) in the System Environment Settings.