jevlogreload
- Organization of this page
Function
The jevlogreload command reloads the action definition file for log file trapping. This command can only reload the values of the MARKSTR and ACTDEF parameters in the action definition file you specify with the jevlogstart command upon startup.
Format
jevlogreload { ID-number | -a monitoring-target-name | ALL }
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
Command directory
- In Windows:
-
installation-folder\bin\
- In UNIX:
-
/opt/jp1base/bin/
Arguments
ID-number
Specify the ID number of the log file trap that you want to reload. Process IDs are output to the standard output at execution of the jevlogstart command.
-a monitoring-target-name
Specify the monitoring target name of the log file trap that you want to reload. You must use the -a option of the jevlogstart command to specify the monitoring target name.
ALL
Reloads all log file traps started by the jevlogstart command and by JP1/AJS log file monitoring jobs. However, do not modify the action definition file for log file trapping started by JP1/AJS log file monitoring jobs. If you modify and then reload the action definition file, you might no longer be able to perform monitoring correctly.
Note
If you specify a value different from that specified upon startup for any parameter other than MARKSTR and ACTDEF, the command fails to reload the file and results in an error. If you want to modify a parameter other than MARKSTR and ACTDEF, restart the log file trapping. If the command is executed while trapping is in progress, the command waits until trapping is completed before reloading the file.
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). |
|
4 |
The action definition file contains an error. |
|
5 |
An error occurred during opening of the action definition file. |
|
6 |
The event server is inactive. |
|
7 |
Insufficient system resource such as memory |
|
8 |
Permission check error |
|
10 |
Reload failed partially. |
|
255 |
Other error |