jevlogstop

Organization of this page

Function
Format
Required execution permission
Command directory
Arguments
Return values

Function

The jevlogstop command stops the log file trapping.

For details on the command you can use to stop all of the log file traps that were started by the jevlogstart command when a failover occurs in a cluster environment, see jevlogstop (cluster environment only).

To Page Top

Format

jevlogstop [-w] { ID-number | -a monitoring-target-name | ALL }

To Page Top

Required execution permission

In Windows: Administrators (If User Account Control (UAC) for Windows is enabled, you must execute the command from the administrator console.)

In UNIX: Superuser or JP1/Base administrator permission

To Page Top

Command directory

In Windows:: installation-folder\bin\
In UNIX:: /opt/jp1base/bin/

To Page Top

Arguments

`-w`

This option enables log data to be forcibly read before log file trapping stops, regardless of the monitoring interval. Monitoring continues until the time when the jevlogstop command is executed. If you omit this option, the log data output between the last monitoring and jevlogstop command execution is not monitored. The following figure shows how the stop timing differs depending on whether this option is specified.

Figure 15‒2: Stop timing options for log file monitoring

This command might take a long time to complete, depending on the amount of log data to be read and the number of JP1 events held during retry processing. Take care when using this option to stop log file trapping at failover in a cluster system.

`ID-number`

Specify the ID number of the log file trap that you want to stop. Process IDs are output to the standard output at execution of the jevlogstart command.

`-a` `monitoring-target-name`

Specify the name of the log file trap monitoring target to be stopped. You must use the -a option of the jevlogstart command to specify the monitoring target name.

`ALL`

Stops all log file traps started by the jevlogstart command and by JP1/AJS log file monitoring jobs.

To Page Top

Return values

`0`	Normal end
`1`	Invalid argument
`2`	The log-file trap management service or log-file trap management daemon is inactive.
`3`	No log file trap with the specified ID or monitoring target name exists (the trap has already stopped). No log file traps exist (when `ALL` is specified).
`255`	Other error

To Page Top