Job Management Partner 1/Base User's Guide
The following describes the procedures for starting and stopping event log trapping. Set up a event log trap in the following files:
- Action definition file for event log trapping
Specify the conditions for converting event log data into a JP1 event and the event-log monitoring interval.
- Organization of this subsection
- (1) Starting the event log trapping function
- (2) Changing a setting while a trap is active
- (3) Check the settings
- (4) Stopping the event log trapping function
- (5) Starting the event log trapping function automatically
(1) Starting the event log trapping function
The following describes the procedure for starting the event log trapping function:
To change the settings:
- Edit the action definition file for event log trapping (ntevent.conf).
- Start the event-log trapping service.
From the Control Panel, open the Services dialog box and start the JP1/Base EventlogTrap service.
- Notes
- If the event server is inactive and no connection retry setting has been entered in the action definition file, the server will fail to start.
- If no action definition file for event log trapping (ntevent.conf) exists, or if the file is invalid, the service will fail to start and this information will be output to the event log and integrated trace log.
- If an invalid log type or invalid regular expression is specified in a filter condition in the action definition file for event log trapping (ntevent.conf), by default that condition is considered invalid, but the service is successfully started or the settings are successfully reloaded. Alternatively, you can specify that service startup and reloading of settings should fail when a filter condition is invalid. For details, see the filter-check-level parameter of Action definition file for event log trapping (Windows only) in 14. Definition Files.
- Event log entries are monitored starting from the time the trapping service starts. Entries before the service starts cannot be monitored.
(2) Changing a setting while a trap is active
To change the settings:
- Edit the action definition file for event log trapping (ntevent.conf).
- Apply the settings.
- If you changed the server parameter:
- Restart the event-log trapping service.
- If you changed a parameter other than server:
- Do not stop the event-log trapping service. Instead, execute the jeveltreload command to apply the changes.
(3) Check the settings
To check the action definition information of the active event log 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 (ntevent.conf).
jbsgetopinfo -o evttrapFor details on the jbsgetopinfo command, see jbsgetopinfo in 13. Commands.
(4) Stopping the event log trapping function
To stop event log trapping, stop the event-log trapping service. From the Control Panel, open the Services dialog box and stop the JP1/Base EventlogTrap service.
(5) Starting the event log trapping function automatically
Upon restarting the system, active event log traps stop and are not restarted automatically. If you want to start an event log trap automatically after the system is restarted, use the JP1/Base startup control to automatically start event log trapping.
In the start sequence definition file (JP1SVPRM.DAT), delete the hash mark (#) at the beginning of the following parameter lines:
#[Jp1BaseEventlogTrap] #Name=JP1/BaseEventlogTrap #ServiceName=JP1_Base_EventlogTrapFor details on the start sequence definition file, see Start sequence definition file (Windows only) in 14. Definition Files.
All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.