11.1.2 Setting up a log file trap

(1) Starting a log file trap

To start a log file trap:

1. Create an action definition file for log file trapping.

2. 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 15. Commands.

To Page Top

(2) Changing a setting

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

To Page Top

(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 15. Commands.

To Page Top

(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 15. Commands.

To Page Top

(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 15. Commands.

To Page Top

(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:

• Use a log-file trap startup definition file (jevlog_start.conf).

  In a log-file trap startup definition file, specify the log file traps that you want to start and the startup options for those log file traps. The log file traps you specify will start automatically when the log file trap management server (daemon) starts.

  For details on the log-file trap startup definition file, see Log-file trap startup definition file in 16. Definition Files.

  If you use a log-file trap startup definition file, check whether the required log file traps have started by viewing the startup record (KAVA3661-I) and startup results (KAVA3662-I) output to the log-file trap startup execution results log.

• 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 16. 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.

To Page Top

(7) Setting the language for log file traps (in UNIX)

You can set the language type for a log file trap by specifying the LANG environment variable when you start the trap. For details on the values that can be specified for the LANG environment variable, see 3.4.2 Setting the language (for UNIX).

The following describes how to specify UTF-8 as the language for log file traps.

To Page Top