7.7.1 Notes on the Send JP1 Event job

The following provides precautions (items you should know in advance) for using the Send JP1 Event job. When defining the JP1 event you want to send, you specify the event level, event ID, and event destination host. After sending a JP1 event, you can check whether the JP1 event has reached the event destination host. JP1/Base must be installed in the destination host.

Important

Before executing the Send JP1 Event job, you must start the JP1/Base event service on the event-originating host and event destination hosts.

Examples of jobnets that use the Send JP1 Event job are as follows:

• Define a jobnet so that a JP1 event is sent if a specific job ends abnormally. In another jobnet, define the start condition so that the jobnet starts if the jobnet receives the JP1 event that is sent from the other jobnet. With these settings, the second jobnet starts when a specific job ends abnormally.

• Define a jobnet to send a JP1 event to the server on which JP1/IM - Manager is installed when a job ends, and check the sent JP1 event by using JP1/IM - View.

Cautionary notes

• The arrival confirmation facility for JP1 events merely allows you to wait until you can confirm that the event has arrived at the destination event server. The feature does not perform retries even if transmission fails. Therefore, when you execute a Send JP1 Event job while the event service is inactive at the destination, the job ends immediately regardless of whether Check interval or Check count is specified.

• If you do not check whether the JP1 event you sent has arrived at the destination, an error does not occur even if you specify the following event servers as event destination host names:

  - An event server that is not defined as the JP1/Base event server

  - An inactive event server

  - An event server that cannot receive JP1 events due to a network error or other problem

• The event server of the local host cannot acquire a sent JP1 event that specifies a destination host name other than the local host.

• When you send a JP1 event to the event server of another host with a destination host name specified, the JP1 event is not subject to retry processing according to the forward-limit setting in the event server settings file (conf) of JP1/Base.

• When you specify a macro variable as an event destination host name, message, or extended attribute, a double quotation mark (") in the passing information might result in the information being passed incorrectly or cause an error. Specify macro variables only if you are sure that they will not cause any problems with the passing information.

• If you do not specify a destination host name, JP1 events are sent to the event server of the host that executes the Send JP1 Event job.

• You cannot specify a User name in an action job. The sender of the JP1 event will be the primary OS user mapped to the User who registered or User who owns of the Send JP1 event job.

• When a logical host name that does not exist in the local host is specified in the JP1_HOSTNAME environment variable, even if the execution host of the Send JP1 Event job is a logical host, the name of the host that sends the event will be the name of the physical host.

• A Send JP1 Event job uses the JP1/Base event server functionality. For this reason, if you want to set up a transmission path for a JP1 event that traverses multiple LAN environments, you must make the settings on the JP1/Base side (in the conf file). For details about how to do so, see the JP1/Base User's Guide.

• In the API settings file for the JP1/Base event service, set keep-alive for the communication type of the server parameter. Setting close as the communication type can result in operational problems, including JP1/AJS3 being unable to issue JP1 events at startup, or Send JP1 Event jobs ending abnormally with message KAVT1040-E output to the integrated trace log. For details about the API settings file and how to set parameters, see the JP1/Base User's Guide.

To Page Top