J.3 Notes on using JP1/SES events

(1) Notes on overwrite installation

After installing JP1/Base, execute the following command to use functions of JP1/SES whose version is 5 or earlier after starting the JP1/Base event service:

jevmkcompat -r

Execute the following command to restore the environment in which you use functions of JP1/SES after starting the JP1/SES service:

jevmkcompat -u

To Page Top

(2) Limitation on the number of pseudo operators

The maximum number of pseudo operators that can be connected simultaneously is limited. A pseudo operator signifies a program that obtains JP1/SES events.

For the compatibility function of Windows version 5, no more than 52 pseudo operators can be used together. Among them, a maximum of 20 pseudo operators are used exclusively for the JP1/AJS ajsevget command. Ensure that no more than 20 ajsevget commands are executed simultaneously. The other 32 pseudo operators are provided for custom jobs of JP1/OJE Client for VOS3, Mainframe, VOS1, or VOS K. Ensure that no more than 32 custom jobs are executed simultaneously.

For the compatibility function of UNIX version 5, no more than 32 pseudo operators can be used together. Ensure that the number of pseudo operators does not exceed 32. For details on programs that can be pseudo operators, see the appropriate manuals for installed Hitachi products.

To Page Top

(3) Operating systems that do not support V5 compatibilities

The OSs that do not support either some or all V5 compatibilities are shown in the following table.

Table J‒2: OSs that do not support some or all V5 compatibilities

OS	Limitation
Windows	Allows event transmission and reception through JP1/SES protocols. Registration and reception of events using the JP1/SES interface (e.g. the ajsevput and ajsevget commands) is not allowed.
Solaris non-global zone	None of the V5 compatibilities can be used.

To Page Top

(4) Notes on using the tmpwatch command (Linux only)

Files stored in the /tmp directory that are not updated for more than 240 hours, and files in the /var/tmp directory other than special device files that are not updated for more than 720 hours are deleted automatically by the tmpwatch command because of the default settings in Red Hat Linux.

The event service for JP1/Base on a physical host creates the files below in the /var/tmp directory.

• /var/tmp/jp1_ses/.JP1_SES_pidfile

• /var/tmp/jp1_ses/.rpidfile#1

• /var/tmp/jp1_ses/.ses_conhost

• /var/tmp/jp1_ses/.ses_wanted

• /var/tmp/jp1_ses/.ses_wanted_2

When the event service receives SES protocol events without the above files, the CPU usage for the jesrd process might be 100%.

If the SES event needs to be received, update the dates of the files above by periodically executing the touch command (once in a maximum of 720 hours) to prevent them from being deleted while the event service on the physical host is running.

Example: A shell file for updating dates once every hour

#!/bin/sh
while :
do
  ps -C jesrd 1>/dev/null 2>/dev/null
  if [ $? = 0 ]
  then
    touch "/var/tmp/jp1_ses/.JP1_SES_pidfile"
    touch "/var/tmp/jp1_ses/.rpidfile#1"
    touch "/var/tmp/jp1_ses/.ses_conhost"
    touch "/var/tmp/jp1_ses/.ses_wanted"
    touch "/var/tmp/jp1_ses/.ses_wanted_2"
  fi
  sleep 3600
done

Note that if the tmpwatch command is executed with the -a option specified, special device files are also deleted.

Do not specify the -a option for the command, because the event service might terminate abnormally when the special device files are deleted.

To Page Top

(5) Notes on using the V5 compatibilities (UNIX only)

To use V5 compatibilities, a symbolic link must be set as follows:

#ls -l /usr/tmp
lrwxrwxrwx . . . . /usr/tmp -> ../var/tmp

If these settings have not been configured in the environment you are using, execute the following command to set a symbolic link.

#ln -s ../var/tmp /usr/tmp

To Page Top