A.2 System Error Numbers of Messages KAVU2xxx-E and KAVU2xxx-W

You can use the system error number output in the messages KAVU2xxx-E and KAVU2xxx-W to narrow down the probable cause of the error.

The table below lists the causes inferred from system error numbers and the corrective action to take in each case. If the error persists after you take the indicated action, use the data collection tool to collect data, and then contact the system administrator.

Table A‒2: System error numbers of messages KAVU2xxx-E and KAVU2xxx-W
No.	System error number					Probable cause	Action
No.	Windows	HP-UX	Solaris	AIX	Linux	Probable cause	Action
1	10048	226	125	67	98	The port number for communication is already in use.	Perform the following: Make sure the port number used by JP1/AJS3 is not being used by another program.^#1 Check the number of sockets output by the `netstat` command that have `TIME_WAIT` status.^#2
2	10049	227	126	68	99	The IP address for communication by the local host differs from the IP address set in the NIC. The NIC that has the IP address used for communication by the local host is disabled.	Perform the following: Check the IP address of the local host set in the `hosts` file, DNS server, `jp1hosts` file, and `jp1hosts2` file.^#1 Check the status of the NIC.^#3
3	10053 10054	231 232	130 131	72 73	103 104	The connection was dropped due to a problem on the network.	Perform the following: Make sure the system has not been shut down.^#4 Check the status of the NIC.^#3
4	10051 10060 10064 10065	229 238 241 242	128 145 147 148	70 78 80 81	101 110 112 113	The remote system is inactive. The network to which the local system belongs is not connected to the remote LAN.	Perform the following: Make sure the remote system is active.^#5 Make sure the network to which the local system belongs is connected to the remote system.^#6
5	10061	239	146	79	111	The service that uses the specified port number on the remote system is inactive.	Perform the following: Make sure that the remote service that communicates with JP1/AJS3 is active.^#5 Check the port number used by the two systems.^#1

#1

If you need to change the port number or IP address settings, stop JP1/AJS3 first.

#2

If there are a large number of sockets in TIME_WAIT status, there might be a temporary shortage of free socket ports. In this case, wait until the number of TIME_WAIT sockets decreases and then re-execute the job.

For details, see 3.1.1(5) OS tuning in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

#3

If the NIC is inactive, first stop JP1/AJS3 and then start the NIC.

#4

To find out whether a network problem has occurred, check the system's network log.

#5

If the remote system is inactive or if the service that communicates with JP1/AJS3 is inactive, start the service.

There is no need to restart JP1/AJS3 on the local host (the host that outputs the messages KAVU2xxx-E and KAVU2xxx-W).

#6

If the IP bind method is set for the sending side in the communication settings, JP1/AJS3-based communication sometimes results in an error and a system error number is output, even though communication by the ping command and other OS commands is possible. For details, see 2.3.3 Connecting multiple LANs in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide. See also the description about how to use JP1/Base in an environment of distinct networks in the JP1/Base User's Guide.

To Page Top