Job Management Partner 1/Base User's Guide

9.1.2 Notes on log file trapping

Note the following points when you use log file trapping:

Stop the log file trap before you edit or delete a log file that is being monitored by log file trapping. If you attempt to edit or delete a log file while the trap is in progress, the monitoring position in the file might change and the trap will fail to convert the data correctly.

The log file trapping function cannot extract data written to a log file unless the data has actually been written to a disk. This means that sometimes you might not be able to retrieve log messages as soon as they occur because the data has not been written to a disk yet.

It will take a long time for the first JP1 event to be generated if the log write-position is near the end of the file.
Notes on monitoring the integrated trace log or syslog file

When you use a log file trap to monitor the integrated trace log or syslog file, attempts to transfer the log data to JP1 events might fail repeatedly. In such a case, the transfer error message KAJP1037-E is output to the integrated trace log or syslog file. If you specify the settings as the following to monitor the integrated trace log or syslog file, the transfer error message KAJP1037-E will also be converted into a JP1 event. If the default setting is used for the forwarding settings file (forward), the JP1 transfer-failure events will also be forwarded.
Setting example:

When monitoring the integrated trace log or syslog file:
 
ACTDEF=<Error>11 "KAJP....-E" 
ACTDEF=<Error>11 "-E" 
 
When monitoring the syslog file:
 
ACTDEF=<Error>11 "error" 
 
To prevent the event transfer from looping, change the setting in the action definition file for log file trapping, so that a log file trap will not trap the KAJP1037-E message. A setting example is shown below.
Setting example 1:
 
MARKSTR="KAJP1037-E"
 
Setting example 2:
 
ACTDEF=<Error>11 "KAJP....-E"
       !"KAJP1037-E"
 
Using JP1/AJS log file monitoring jobs

If you wish to use a JP1/AJS log file monitoring job, you must first start both the Windows log-file trap management service (or UNIX log file trap management daemon) and the event service. JP1/AJS log file monitoring jobs are executed using the JP1/Base log file trapping function.

For details on log file monitoring jobs, see the Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide, Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide, Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide, and the Job Management Partner 1/Automatic Job Management System 3 Administration Guide.

[Contents][Back][Next]

[Trademarks]