Job Management Partner 1/Base User's Guide

9.1.1 Setting up a log file trap

The following describes the procedures for starting a log file trap, changing the settings, checking the operating status, checking the settings, and stopping a log file trap. Set up a log file trap in the following files:

Action definition file for log file trapping
Specify the format of the monitored log file, the retry settings when monitoring fails and any other settings.

Log information definition file (jevlogd.conf)
Specify the maximum size and number of storable log files used for log file trapping. You can use the default settings under normal circumstances.

Organization of this subsection

(1) Starting a log file trap

(2) Changing a setting

(3) Checking the operating status

(4) Checking the settings

(5) Stopping a log file trap

(6) Starting a log file trap automatically

(1) Starting a log file trap

To start a log file trap:

Create an action definition file for log file trapping.

Execute the jevlogstart command.
The log file trapping starts, the ID is output to the standard output or to the syslog file. Take note of this ID as you will need it when stopping a log file trap or updating a definition file.
Also, you can specify a monitoring target name using the jevlogstart command. After the monitoring target name is specified, use the jevlogstop, jevlogreload, and jevlogstat commands to specify and operate the monitoring target names.
For details on the jevlogstart command, see jevlogstart in 13. Commands.

(2) Changing a setting

The following describes how to change settings in the action definition file for log file trapping and the log information definition file (jevlogd.conf).

(a) Changing a setting in the action definition file for log file trapping

Edit the action definition file for log file trapping.

Apply the settings.

If a parameter other than MARKSTR or ACTDEF is modified:

Restart the log file trapping function. Execute jevlogstop {ID-number|-a monitoring target name}, and then execute the jevlogstart command.

If the modified parameter is MARKSTR or ACTDEF:

Execute jevlogreload { ID-number|-a monitoring target name} without stopping log file trapping to apply the settings.

For details on the jevlogstart command, see jevlogstart in 13. Commands.

For details on the jevlogreload command, see jevlogreload in 13. Commands.

(b) Changing a setting in the log information definition file

Edit the log information definition file (jevlogd.conf).

Restart the log-file trap management service (or daemon).

(3) Checking the operating status

To check the operating status of a log file trap, execute the following command. From the return value, you can verify the status of the log file trap specified by the ID number in the command argument or monitoring target name.
jevlogstat{ID-number|-a monitoring target name}
You can also use the following command to display a list of IDs and monitoring target names of the log file traps in progress:
jevlogstat ALL 
For details on the jevlogstat command, see jevlogstat in 13. Commands.

(4) Checking the settings

To check the action definition information of the active log file trap, execute the following command. The execution result will be displayed on screen in the format of the action definition file for log file trapping.
jbsgetopinfo -o logtrap [-i ID-number|-a monitoring target name]
 
For details on the jbsgetopinfo command, see jbsgetopinfo in 13. Commands.

(5) Stopping a log file trap

To stop a log file trap, execute the following command:
jevlogstop {ID-number|-a monitoring target name}
To stop all the active log file traps, execute the following command:
jevlogstop ALL
For details on the jevlogstop command, see jevlogstop in 13. Commands.

(6) Starting a log file trap automatically

Upon restarting the system, active log file traps stop and are not restarted automatically. To restart the log file traps automatically when you restart the system, use the following procedure:

In Windows, create batch files and use the JP1/Base startup control to set up the batch files.
Create batch files and specify the appropriate jevlogstart command in each file. After that, in the start sequence definition file (JP1SVPRM.DAT), write ReadyCommand= followed by each batch file name specified by full path.
For details on the start sequence definition file, see Start sequence definition file (Windows only) in 14. Definition Files.

In UNIX, specify the jbs_start command.
Specify the command so that the log file trapping starts after the event service and the log-file trap management daemon have started.

Execute the jevlogstart command as a JP1/AJS job.

[Contents][Back][Next]

[Trademarks]