options[no-sync | sync] [remote-receive] [conv-off] [v5-unused] [KAJP1037-hntroff] [KAJP1037-syslogoff] [save-rep] [auto-forward-off] [suppress-notification-on] [threshold-suppress-notification-on] [rep-restore]

error-size file-size

trace-size file-size

evtlog-size file-size

fwderr-size file-size

log-keep log-file-count

repetition-noncheck-server { * | event-server-name } ...

restart number-of-restart retry-interval reset time

undisposedids { basic-code | basic-code-basic-code } ...

suppress-notification-interval notification-interval

threshold-suppress-notification-interval notification-interval

To Page Top

Parameters by type

Required parameters:

ports
forward-limit
include
db-size
remote-server (event-server-name, communication-type, and address)
options (remote-receive, v5-unused, KAJP1037-hntroff, KAJP1037-syslogoff, save-rep, suppress-notification-on, and threshold-suppress-notification-on)
undisposedids

Custom parameters:

client-bind
users
eventids
alt-userid
buffnum
remote-server (port)
options (no-sync | sync, conv-off, and auto-forward-off)
repetition-noncheck-server
restart
suppress-notification-interval
threshold-suppress-notification-interval

To Page Top

File name

conf

To Page Top

Storage destination directory

In Windows:

folder-specified-in-event-server-index-file\

shared-folder\jp1base\event\ (in a cluster system)

The default event server index file (index) is located at installation-folder\conf\event\servers\default\.

In UNIX:

directory-specified-in-event-server-index-file/

shared-directory/event/ (in a cluster system)

The default event server index file (index) is located at /etc/opt/jp1base/conf/event/servers/default/.

To Page Top

Description

Defines the operating environment for the event service. In this file, you mainly define the following information:

The IP address and port number for sending and receiving JP1 events
Which JP1 events are retrievable and the JP1 users permitted to acquire those events
Whether to retry upon a failed attempt to forward an event
The sending and receiving of JP1 events to and from a host running JP1/SES and JP1/AJS
The expiration time for JP1 events stored in the event database and the maximum size of the event database
The connection method for forwarding JP1 events to an event server at a remote host, and the procedure for handling transfer errors

To Page Top

Application of settings

Start or restart an event service to apply the settings. When you restart the event service, also restart services for which the event service is a prerequisite.

To Page Top

Definition details

The following conventions apply to entries in the event server settings file (conf).

Each line of the text file is no more than 1,024 bytes and the file size is no more than 2 GB.
Separate parameter keywords with a space (code 0x20) or a tab (code 0x09).
Do not insert a space or any other characters in front of the parameter name and hash mark (#) (code 0x23) at the start of a line.
A hash mark (#) (code 0x23) at the start of a line indicates a comment. You can enter a comment or line space anywhere in a file.
Letters are case sensitive.

ports address receiver-port AP-port

Specify the IP address and port number to be used by the event server when connecting to a remote program. The values specified here do not apply to receiving events from hosts running either of the pre-version 6 programs, JP1/SES or JP1/AJS.

address

Specify the IP address in one of the following forms. We recommend that you specify <jp1hosts2>, unless there is a good reason to do otherwise.

If you omit the ports parameter, the event server name is used.

0.0.0.0

No set address. The system determines the IP address.

For a system that only runs on physical hosts, specify the IP address.
IPv4 addresses

Specify numbers separated by periods (example: 172.16.50.50). You can specify multiple IP addresses. Multiple IP addresses are useful when you use event services in an environment with multiple networks.

When you specify multiple IP addresses, separate them with a colon (example: 172.16.50.50:172.16.50.51:172.16.50.52). You can assign no more than four IP addresses.

Note:

If you specified an IP address other than the IP address returned to the primary server by the OS name resolution, you must explicitly specify the IP address in the server parameter in the API settings file (api).
<jp1hosts2>

Specify <jp1hosts2> if you want the event server to communicate using the JP1/Base communication protocol. To communicate using IPv6 addresses, specify <jp1hosts2> and delete the client-bind parameter.

Note:

If you use the IP binding method as the communication protocol, jp1hosts information or jp1hosts2 information is referenced. If you want to use jp1hosts information, you must explicitly specify the IP address in the server parameter in the API settings file (api).
host-name

Specify a name that is no more than 255 bytes and can be converted into an IP address by the system's hosts file or name server.

If you specify a physical host name in Windows, the host name might not resolve to the intended IP address.

receiver-port

Specify the port number for receiving JP1 events forwarded from a remote server. Use either of the following:

port-number

Specify the port number using numbers.
Service name

Specify the tcp service name defined in the system's services file. As a general rule, specify jp1imevt for the service name. This value is used when the ports parameter is omitted.

AP-port

Specify the port number for receiving requests from an application to issue or acquire JP1 events. Use either of the following:

port-number

Specify the port number using numbers.
Service name

Specify the tcp service name defined in the system's services file. As a general rule, specify jp1imevtapi for the service name. This value is used when the ports parameter is omitted.

client-bind address

Specify the IP address the event server uses to send JP1 events to other programs. This parameter is useful when you use event services in an environment with multiple networks. Under normal circumstances, there is no need to specify client-bind. When you omit it, JP1 events are sent from the IP address specified in the ports parameter. If you specify multiple addresses, events are sent to the address specified first.

To communicate using IPv6 addresses, specify <jp1hosts2> in the ports parameter and delete the client-bind parameter. Note that this parameter setting is not applicable when transferring events to hosts running either of the pre-version 6 programs, JP1/SES or JP1/AJS.

address

Specify the IP address using either of the following methods:

0.0.0.0

No specific IP address is set, and the system automatically assigns one. Specify this value as a general rule when you enable multi-LAN connectivity.
IP-address

Specify numbers separated by periods. This address is used to send events.

users {* | user-name}...

Specify the users permitted to acquire JP1 events.

You can specify this parameter more than once. The permitted users are equivalent to the sum of all the specifications. When the users parameter is omitted, no users can acquire JP1 events.

*: All users can acquire JP1 events.
user-name: Specify a user name. The specified user can acquire JP1 events.

eventids {* | basic-code | basic-code:extended-code}...

Specify which event IDs can be acquired by programs. If a JP1 event is issued whose ID is not specified, an error will not occur, but the event cannot be acquired.

You can specify this parameter more than once. The retrievable event IDs are equivalent to the sum of all the specifications. When the eventids parameter is omitted, no JP1 events can be acquired.

*: All JP1 events can be acquired.
basic-code: Specify the basic code for each event ID, using no more than 8 hexadecimal digits. The extended code is always 0.
basic-code:extended-code: Specify the basic and extended code for each event ID, using no more than 8 hexadecimal digits each, using a colon to separate the two codes.

alt-userid alternate-user-ID alternate-group-ID

Specify a value to be set in the event data, replacing the numerical user ID or group ID which are not recognized in the Windows and Java execution environment.

In alternate-user-ID and alternate-group-ID, specify a number from -1 to 65,535. If a value is not specified, -1 is used for both values.

forward-limit retry-time

Specify the retry timeout period for forwarding JP1 events that have failed to be sent. The system resends the JP1 events specified in the forwarding settings file (forward) at regular intervals, specified by the retry-interval parameter, until the transfer succeeds or the specified time elapses. Specify a number from 0 to 86400 (seconds). The default is 0 (no retries are performed). When you specify the forward-limit parameter, specify a value greater than the retry interval specified for the retry-interval parameter.

after-error forwarding-suspension-period

Specify the length of time that JP1 event transfer will be suspended after it fails to be forwarded to a remote server. During the specified time, the remote server is assumed to be in an error state and, as a result, no JP1 events will be forwarded to that server. Specify a number from 0 to 2147483647 (seconds). The value must be less than the retry-interval parameter. The default is 30.

retry-interval transfer-retry-interval

Specify the interval at which the system will attempt to resend JP1 events that failed. Specify a number from 60 to 2147483647 (seconds). The value must be greater than the after-error parameter. The default is 600.

Correlation between the parameters related to retrying

The parameters related to retrying JP1 event transfers are forward-limit, after-error, and retry-interval. By default, if a JP1 event fails to be forwarded, JP1/Base will retry at 600-second intervals for a maximum of 3,600 seconds.

In a cluster system, if a failover occurs on the sending or receiving host while a JP1 event is being transferred, the transfer will fail. In the JP1/Base settings, always enable retries to ensure that JP1 events will be forwarded successfully.

The following figure shows the correlation between the parameters related to retrying JP1 event transfers:

Figure 16‒2: Correlation between the parameters related to retrying JP1 event transfers

If another JP1 event is transferred within the retry interval not within the after-error suspension period, at the same time, JP1/Base will also reattempt to transfer the event that failed to transfer before.

If the event service is restarted or reloaded while JP1/Base is reattempting to transfer a JP1 event, the JP1 event will be resent after the event service is restarted, provided the forward-limit time has not elapsed.

buffnum SES-event-count

This parameter links the JP1/SES event with the product to use. For details on this parameter, see J. Linking with Products That Use JP1/SES Events.

include ses-conf file-name

This parameter links the JP1/SES event with the product to use. For details on this parameter, see J. Linking with Products That Use JP1/SES Events.

include ajs-conf

This parameter links the JP1/SES event with the product to use. For details on this parameter, see J. Linking with Products That Use JP1/SES Events.

expire event-expiration-time

Specify the length of time for storing issued JP1 events in the event database. JP1 events are stored in the event database for the specified time and while they are in the database, they can be viewed from JP1/IM - View. If the JP1 events stored in the database reach the capacity specified in the db-size parameter, events might be deleted even though the expiration time has not yet been reached. Specify a number from 0 to 2147483647 (seconds). If an expiration time is not specified, the default is 31536000 (365 days).

db-size event-database-capacity

Specify the event database capacity. When the specified size is reached, JP1 events might be deleted, starting from the oldest ones, even though the expiration time specified in the expire parameter has not been reached. The JP1/Base event service occupies up to twice the amount of disk space specified in this parameter. Specify a number from 0 to 2147483647 (bytes). The default is 2147483647.

The following is the formula for calculating the capacity required for the event database in respect to the number of days for which events are stored. Use this formula as a guide for specifying the capacity:

[a x (b + 64) + (c x 64)}x d]/2 (bytes)

a: Number of events registered per day^#

b: Average size per event. (You must actually measure this size.)

c: Number of events transferred per day

d: Number of days for storage

#: The events registered daily include those generated on the local host, JP1/SES events, JP1 events received from other hosts, and transferred events.

On AIX, make sure that fsize for ulimit is not exceeded when changing db-size in the event server environment setting file (conf). Increase fsize when setting a value for db-size that exceeds fsize.

remote-server event-server-name communication-type [address [port]]

Specify the method for connecting to a remote server for event transfers. You can specify multiple remote-server parameters if the value in event-server-name is different in each case.

event-server-name

Specify the event server name in either of the following ways:

event-server-name

Specify a specific event server name that is no more than 255 bytes.
*

Specify an asterisk to indicate all of the event servers, other than those that have been individually specified.

When this specification is omitted, events can be forwarded only to event servers that are explicitly specified.

communication-type

Specify the method for connecting to the specified remote server:

close

When you need to forward a JP1 event to a remote server, establish a TCP/IP connection from the sending server, and forward the event. If no JP1 event to be forwarded is issued for two seconds or more, the connection will be disconnected.
ses

This parameter links the JP1/SES event with the product to use. For details on this parameter, see J. Linking with Products That Use JP1/SES Events.
keep-alive

When you need to forward a JP1 event to a remote server, establish a TCP/IP connection from the sending server, and forward the event. After the event transfer, keep the connection open so it can be reused until the remote event server shuts down. Note, however, that we recommend that you specify close or ses rather than keep-alive because the following note applies.

Note

When a connection is severed, and then recovered, the first attempt to transfer a JP1 event after the connection is recovered might fail. A connection might be severed, either because the firewall is set up to do so when there is no communication between the servers, or because a temporary communication error occurred.

address

Specify the IP address in one of the following formats. We recommend that you specify <jp1hosts2>, unless there is a good reason to do otherwise.

IP-address

Specify numbers separated by periods (example: 172.16.50.50).
<jp1hosts2>

Specify <jp1hosts2> if you want the event server to communicate using the JP1/Base communication protocol. Also specify <jp1hosts2> if you want to communicate using IPv6 addresses. jp1hosts information or jp1hosts2 information is referenced when the IP address of the destination host is resolved.
host-name

Specify a name that is no more than 255 bytes and that can be converted into an IP address by the system's hosts file or name server.

The specified address must match the value set in the ports parameter for the event server specified in the event server settings file (conf).

The default host name is the event server name.

port

Specify the port number using one of the following methods:

port-number

Use numbers to specify the port number.
Service name

Specify the tcp service name defined in the system's services file.

The specified address must match the value set in the ports parameter for the event server specified in the event server settings file (conf).

The default is the same value as the transfer port of the local event server.

forward-timeout amount-of-time-to-wait

Specify the length of time to wait for a response from the destination server when forwarding a JP1 event. If no response is received within the specified time, the system assumes that the transfer failed.

Specify a number from 10 to 600 (seconds). The default is 90.

options [no-sync | sync] [remote-receive] [conv-off] [v5-unused] [KAJP1037-hntroff] [KAJP1037-syslogoff] [save-rep] [auto-forward-off] [suppress-notification-on] [threshold-suppress-notification-on] [rep-restore]

Specify option flags. You can specify the parameter and a flag on different lines.

no-sync | sync

Specifying no-sync flag (not recommended):

This setting is performance-centric, and is retained for compatibility reasons. The no-sync flag allows the system to buffer JP1 events that are written to the database. Specifying this flag might improve performance when JP1 events are generated. However, issued JP1 events might be lost if the system shuts down unexpectedly due to a failure. Do not specify this flag unless there is a special reason to do so.

Specifying sync flag (recommended in a cluster environment):

This setting is reliability-centric and ensures that a JP1 event is written to disk each time the event is issued.

Specifying the sync flag ensures that the JP1 events are acquired even after restarting the system. Writing each JP1 event to disk at the time it is issued might, however, cause a performance decrease when issuing JP1 events. Note that, if a delay occurs while the events are written to disk, there might be a significant delay in acquiring JP1 events from a program such as JP1/IM - Manager. At this time, the event database might be switched before JP1 events are obtained, causing those JP1 events to be lost. Therefore, if you specify the sync flag, make sure that the number of JP1 events that occur on the system does not exceed the registration performance. Carry out investigations in advance as the registration performance varies depending on the environment.

Omitting the flag (recommended in a non-cluster environment):

This is the default operation, in which performance and reliability are balanced. The system buffers the events and writes them to disk every 10 seconds.

remote-receive

Allows JP1 events to be acquired by a program running on a remote host over a network.

You must specify this flag to search for JP1 events on a remote host using the JP1/IM - View GUI connected to that host, and to view information in the pre-Version 6 program JP1/AOM-EE.

conv-off

This flag links the JP1/SES event with the product to use. For details on this flag, see J. Linking with Products That Use JP1/SES Events.

v5-unused

Suppresses the use of all of the functions related to the compatibility with the pre-Version 6 programs, JP1/SES and JP1/AJS. When you specify this flag, the processes used for the compatibility with JP1/SES and JP1/AJS will not start. Therefore, JP1/Base will be unable to exchange events with JP1/OJE and other products that use the JP1/SES protocol.

Do not remove this flag unless it is linked with the programs that are compatible to pre-version 6. For details on the linkage with pre-Version 6 products, see J. Linking with Products That Use JP1/SES Events.

KAJP1037-hntroff

Suppresses output of the KAJP1037-E (event transfer failure) message to the integrated trace log.

KAJP1037-syslogoff

Suppresses the KAJP1037-E (event transfer failure) message being output to the syslog (in UNIX) or the event log (in Windows).

save-rep

Keeps the event database duplication prevention table in a file. The duplication prevention table prevents JP1 events from being registered twice.

If you specify the save-rep flag, make sure that the directory that stores the event database has a minimum capacity of 32 + total number of the source event servers x 288 bytes. For details on the duplication prevention table, see 2.3.2 Event database.

When you specify the save-rep option for the first time in a given environment, execute the jevdbmkrep command after changing the setting and before starting the event service.

auto-forward-off

Disables the function that forwards the events listed below, even if they do not match the filter conditions. If you specify this flag, like other events, these events will only be forwarded if they match the filter conditions.

Event reporting of JP1/Base startup (00004724)
Event reporting of JP1/Base shutdown (00004725)
Event reporting of a threshold-based suppression (00003D0B)
Event reporting of a stop of a threshold-based suppression (00003D0C)
Event reporting of a stop of all threshold-based suppressions (00003D0D)
Event reporting of the continuation of threshold-based suppressions (00003D0E)

suppress-notification-on

Issues a JP1 event reporting that the event forwarding state activated by the jevagtfw command is continued. Specify this flag on the event server for the manager host on which the jevagtfw command was executed.

threshold-suppress-notification-on

Issues a JP1 event, reporting to the manager that the event forwarding state activated by a threshold is continued. Specify this flag on the event server for the agent host on which the threshold-based suppression of event-forwarding was set up.

rep-restore

Automatically repairs the event database duplication prevention table if it is corrupted when the event service starts. This parameter is invalid if the save-rep flag is not specified.

Note

The KAJP1017-E message informing a transfer error will be output to the integrated trace log and syslog (in UNIX) or the event log (in Windows), even if you have specified KAJP1037-hntroff or KAJP1037-syslogoff. Monitor for transfer errors by checking the KAJP1017-E message.

The KAJP1037-E message can also be checked by the event service transfer error log (fwderr.*).

error-size file-size

Specify the maximum size that will be used for the event service error log files (error.*). When a file exceeds the specified size, it is overwritten starting from the beginning. Specify a number from 65536 to 2147483647 (bytes). The default is 500000.

The following shows the formula for calculating the required capacity of an event service error log file in relation to the number of days for which events are stored. Use this formula as a guide for specifying the file size.

a + (b x c) x d (bytes)

a: Basic part (1 KB)

b: Average error message size (approx. 120 bytes)

c: Number of errors per day

d: Number of days for storage

trace-size file-size

Specify the maximum size of an event transfer trace log file (trace.*). When a file exceeds the specified size, it is overwritten from the beginning. Specify a number from 65536 to 2147483647 (bytes). The default is 1,000,000.

The following shows the formula for calculating the required capacity of an event transfer trace log file in relation to the number of days for which you want to store events. When specifying the file size, consider the amount of log data output per day and the number of events acquired per day.

a + (b + c + d) x e (bytes)

a: Basic part (1 KB)

b: Amount of output log data necessary to register one event x Number of events registered per day

c: Amount of output log data necessary to acquire one event x Number of events acquired per day

d: Amount of output log data necessary to transfer one event x Number of events transferred per day

e: Number of days for storage

The amount of output log data differs according to the operation of the event service; however, the following can be used as a reference value for the amount of output log data.

Table 16‒12: Amount of log output (event transfer trace log)
Amount of log output (in bytes)
Registering an event	Acquiring an event^#1	Transferring an event^#2 (retries if the transfer fails)
Approx. 150^#3	Approx. 150^#3	Approx. 1,500

#1: Event acquisition includes JP1 events acquired by other applications. The value above comes from the amount of data output to a log when the 10th JP1 event is acquired from an event database containing ten events. The output amount varies depending on the number of JP1 events registered in an event database and where a JP1 event is registered.

#2: When transferring a JP1 event, the amount of data output to a log is the maximum if the transfer fails and is performed again.

#3: The amount of data output to a log when the communication type is set to close in the API settings file (api). If you set the communication type to keep-alive, the amount of log data will be smaller. However, make an estimate on the assumption that the communication type is set to close.

The number of events acquired per day represents how often events are acquired via the event acquisition function from the user application or JP1 series programs. You can use the following formula as a guideline for the number of events JP1 series products acquire per day.

Number-of-events-acquired^#1 x number-of-events-registered-in-event-database + number-of-events-registered-per-day^#2

#1: The number of JP1/IM events acquired from the event database is equivalent to the sum of the following numbers:

Number of times JP1/IM - View is started
Number of times JP1/IM - View searches for events

#2: If event reception jobs for JP1/AJS are registered for execution, JP1/AJS acquires events that are newly registered with the event database. JP1/AJS acquires a registered event only once even if multiple event reception jobs are registered.

evtlog-size file-size

Specify the maximum size (in bytes) of an event service trace log file (imevterr.*). When a file exceeds the specified size, it is overwritten from the beginning. Specify a number from 65536 to 2147483647 (bytes). The default is 1,000,000.

The following is the formula for calculating the capacity required for an event service trace log in respect to the number of days for which events are stored. When specifying the file size, consider the amount of log output per day and the number of events acquired per day.

a + (b + c + d) x e (bytes)

a: Basic part (1 KB)

b: Amount of log output necessary to register one event x Number of events registered per day

c: Amount of log output necessary to acquire one event x Number of events acquired per day

d: Amount of log output necessary to transfer one event x Number of events transferred per day

e: Number of days for storage

The amount of output log data differs according to the operation of the event service; however, the following can be used as a reference value for the amount of output log data.

Table 16‒13: Amount of log output (event service trace log)
Amount of log output (in bytes)
Registering an event	Acquiring an event^#1	Transferring an event^#2 (retries the transfer if it fails)
Approx. 3,000	Approx. 7,000	Approx. 3,000

#2: When transferring a JP1 event, the amount of data output to a log is the maximum if the transfer fails and is performed again.

Number-of-events-acquired^#1 x number-of-events-registered-in-event-database + number-of-events-registered-per-day^#2

#1: The number of JP1/IM events acquired from the event database is equivalent to the sum of the following numbers:

Number of times JP1/IM - View is started
Number of times JP1/IM - View searches for events

fwderr-size file-size

Specify the maximum size of an event service transfer error log file (fwderr.*). When a file exceeds the specified size, it is overwritten starting from the beginning. Specify a number from 65536 to 2147483647 (bytes). The default is 1,000,000.

The following shows the formula for calculating the required capacity of an event transfer error log file in relation to the number of transfer failures for which you want to store events.

Number-of event-transfer-failure-to-store x ( 150 + length-of-event-server-name + length-of-destination-event server-name)

If there are multiple destination servers, the length of the destination event server name is equal to the length of the longest server name among the destination event server names.

log-keep number-of- log-files.

Specify the maximum number of event service error log files, event transfer trace log files, event service trace log files and event service transfer error log file that can be created. A log file is created when the event service starts. If the number of log files at event service startup exceeds the specified count, files are deleted, starting from the oldest. Specify a number from 0 to 50. The default is 5. When 0 is specified, logs are not kept.

repetition-noncheck-server { * | event-server-name } ...

Specify the name of the event server that suppresses the duplication registration check. The duplication registration check checks whether a JP1 event has already been registered when receiving a JP1 event. A JP1 event is a duplicate of another if its source event server name, source event database serial number, and the time of registration are the same as the other one.

You can use the duplication check to prevent an event from being lost when forwarding a JP1/SES protocol event through several routes.

You can specify this parameter multiple times. The event servers that suppress duplication registration are equivalent to the sum of all the specifications. When this parameter is omitted, the duplication registration check is performed on the JP1 events from all source event servers.

*: In this case, the duplication registration checks from all source event servers are suppressed.
event-server-name: Specify the name of each event server that suppresses the duplication registration check. Event server names are case sensitive.

restart number-of-restart retry-interval reset time

Set the JP1/Base to restart if an error occurs in the event service process on the physical host. To restart JP1/Base, specify the number of restarts, the interval at which the system will attempt to restart, and the restart count reset time. The process will restart only if the number of abnormal terminations during the period specified by the reset time is less than the number of restart times. The recovery message (KAJP1072-I) is output when the process restarts. The message is also sent out as a JP1 event (event ID: 00003D04). Therefore, if you see this JP1 event, then you know that the event service process was restarted. This parameter is valid only in the UNIX version of JP1/Base, not in the Windows version. If you omit this parameter, the process will not restart even after the event service process has been abnormally terminated. Instead, the event service will stop.

Also, when an event service is restarting, the JP1 event transferred from the sending host will not be received. JP1/Base will try to re-send the JP1 event, assuming that JP1/Base is set to do so on the sending host. However, if the retry interval is exceeded, the transfer will fail. To prevent such failures, make sure that the value you set for number of restarts x retry interval is less than the retry limit for forwarding JP1 events (forward-limit parameter) in the conf parameter on the sending host.

Number of restarts: Specify how many times the system will attempt to restart. The recommended value is 4. Specify a number from 0 to 99. If 0 is specified, the process does not restart. If you specify a number less than 0, the system uses 0. If you specify a number greater than 99, the system uses 99.
Retry interval: Specify how long an event service process will wait to restart after it ends abnormally. If a restart fails, the process will wait until the specified interval elapsed before another attempt is made to restart the service. The recommended value is 15 (seconds). Specify a number from 0 to 3600. If you specify a number less than 0, the system uses 0. If you specify a number greater than 3600, the system uses 3600.
Reset time: Specify the number of seconds that will elapse after the process is restarted, before the number of restarts is reset. The number of restarts is reset the specified time after the process is restarted. The recommended reset time is 3600 (seconds). Specify a number from 3600 to 2147483647 (seconds). If you specify a number less than 3600, the system uses 3600. If you specify a number greater than 2147483647, the system uses 2147483647.

The following figure illustrates the process action using the recommended values (the number of retries is 4, the retry interval is 15, and the reset time is 3600).

Figure 16‒3: Example of action when an event service process ends abnormally

In this example, the number of restarts is reset 3,600 seconds after the process is restarted if the process does not end abnormally within 3,600 seconds. Then, the next time the process ends abnormally, the restart count starts from 1. If the process ends abnormally again within 3,600 seconds after the reset, the restart count is not reset. If the number of restarts reaches the specified value, the system no longer attempts to restart the process.

Notes

Only the child processes of the jevservice process, whose process ID can be confirmed in the jevstat command, can be restarted by specifying the restart parameter.
If the parent process ends abnormally, the event service stops.
A separate retry count is used for each child process.

The jevservice process has the following 6 types of child processes.

Table 16‒14: Event service process composition
Parent process name	Child process name	Overview
`jevservice`	`jevservice` (LogTrc)	Outputs the messages recorded in syslog or the integrated trace log.
	`jevservice` (DBMngr)	Manages the event database.
	`jevservice` (SESEmu)	This is the SES compatibility function. When the `v5-unused` flag is specified in the options parameter, this function is not used.
	`jevservice` (EvtAPI)	Accepts registration or acquisition requests of JP1 events.
	`jevservice` (FwdRcv)	Receives the forwarded JP1 events.
	`jevservice` (FwdMgr)	Forwards JP1 events.

undisposedids { basic-code | basic-code-basic-code } ...

Specify the event IDs that are excluded from discarding of the received events for event forwarding suppression. Even when the setting to discard events received from an agent is enabled, the JP1 events with the event IDs specified here are received from the agent.

You can specify multiple values for this parameter. If you omit this parameter, all the JP1 events that are subject to discard are discarded.

Note that log file trapping and event log trapping might generate a large volume of events, depending on the condition. Therefore, in the initial settings, JP1 events whose event IDs are 3A71 (JP1 events converted by event log trapping) are discarded. This means that event IDs (2000-3A70, 3A72-7FFF7FFF) other than 3A71 are specified for the undisposedids parameter.

basic-code: Specify the event ID basic code in a hexadecimal value of 1 to 8 digits.
basic-code-basic-code: Specify the range for event ID basic codes, each in a hexadecimal value of 1 to 8 digits separated by a hyphen.

suppress-notification-interval notification-interval

Specify an interval for issuing a JP1 event reporting that event forwarding activated by the jevagtfw command is continued. Specify a decimal value from 60 to 86,400 (seconds). If you omit this parameter, 3,600 (seconds) is assumed.

This parameter is enabled only when the suppress-notification-on flag is specified in the options parameter.

threshold-suppress-notification-interval notification-interval

Specify an interval for issuing a JP1 event reporting that event forwarding activated by a threshold is continued. Specify a decimal value from 60 to 86,400 (seconds). If you omit this parameter, 3,600 (seconds) is assumed.

This parameter is enabled only when the threshold-suppress-notification-on flag is specified in the options parameter.

To Page Top

Note

In JP1/Base 11-00 or later, you no longer need to specify the log-level parameter. However, if you do specify it, JP1/Base operation is not adversely affected.

To Page Top

Definition examples

# For port number, use jp1imevt and jp1imevtapi defined 
# in the system services file.
ports 0.0.0.0 jp1imevt jp1imevtapi
# Programs executed only in user root and adm can acquire 
# JP1 events.
users root adm 
# Only the JP1 events that have an ID of 2000, 2001, 3000, 
# or 3001 can be issued and acquired by API of JP1/SES.
# Programs compatible to JP1/Base can issue and acquire all 
# JP1 events.
eventids *
eventids 2000 2001 3000 3001
# If you are using Windows on your local computer, or 
# if you are using UNIX on your
# local computer but JP1 events are issued by Java,
# when you forward JP1 events in UNIX environment, user ID 
# or Group ID will be interpreted as 1001 and 100.
alt-userid 1001 100
# If forwarding of a JP1 event fails, JP1/Base will retry 
# forwarding. 
# Retry will continue until either the JP1 event is sent 
# successfully or one hour 
#(3600 seconds) elapses.
forward-limit 3600
# If forwarding events to a remote host fails, to prevent 
# network load from increasing, no events will be sent to 
# this host within the next 300 seconds.
after-error 300 
# To add settings to the above userids and evendids, 
# see JP1/SES environment settings 
# file /usr/bin/jp1_ses/jpevent.conf.
include ses-conf /usr/bin/jp1_ses/jpevent.conf 
# JP1 events received 31 days (2,678,400 seconds) ago 
# will be deleted.
# Also, if data amount of the stored JP1 events reaches 
# 1,000,000 bytes, JP1 events will be deleted from 
# the oldest ones.
expire 2678400
db-size 1000000
# JP1 events can be acquired from a remote host.
# (Make sure to specify the host if you want to refer to the 
# JP1/AOM - EE information from JP1/M-Console View that is 
# connected to another computer.)
options remote-receive 
# Allows the OS to buffer JP1 events written to the disk.
options no-sync 
# Host 1 and host 2 are within the local LAN, so you can 
# leaving them connecting to TCP/IP.
# Other computers (except host 3) are connected by phone 
# line dial ups, so the connections will be frequently interrupted.
# Host 3 uses JP1/SES, not JP1/Base.
remote-server host1 keep-alive 
remote-server host2 keep-alive 
remote-server host3 ses 
remote-server *    close 
# Set the maximum size of the error log file to 500,000 bytes,
# and the trace log file to 1,000,000 bytes.
# If the capacity exceeds the specified size, data will be 
# overwritten starting from the top the file.
# If there are five or more log files, files will be deleted 
# from the older ones.
error-size 500000 
trace-size 1000000 
log-keep 5

To Page Top