LAN Client Problems

iopen Fails - Syntax Error

In this case, iopen fails with the error I_ERR_SYNTAX. If using the “lan,net_address” format, ensure that the net_address is a hostname, not an IP address. If you must use an IP address, specify the address using the bracket notation, lan[128.10.0.3], rather than the comma notation lan,128.10.0.3.

iopen Fails - Bad Address

An iopen fails with the error I_ERR_BADADDR, and the error text is core connect failed: program not registered. This indicates the Remote IO Server software has not registered itself on the server machine. This may also be caused by specifying an incorrect hostname. Ensure that the hostname or IP address is correct and, if so, check the Remote IO Server’s installation and configuration.

iopen Fails - Unrecognized Symbolic Name

The iopen fails with the error I_ERR_SYMNAME, and the error text is bad hostname, gethostbyname() failed. This indicates the hostname used in the iopen address is unknown to the networking software. Ensure that the hostname is correct and, if so, contact your network administrator to configure your machine to recognize the hostname. The ping utility can be used to determine if the hostname is known to your system. If ping returns with the error Bad IP address, the hostname is not known to the system.

iopen Fails - Timeout

An iopen fails with a timeout error. Increase the Client Delta Timeout configuration value via Connection Expert. See Using SICL with a LAN for more information.

iopen Fails - Other Failures

An iopen fails with some error other than those already mentioned. Try the steps at the beginning of this section to see if the client and server can talk to one another over the LAN. If the ping and rpcinfo procedures work, check any server error logs that may be available for further clues. Check for possible problems such as a lack of resources at the server (memory, number of SICL sessions, etc.).

I/O Operation Times Out

An I/O operation times out even though the timeout being used is infinity. Increase the LAN Maximum Timeout configuration value via Connection Expert. Also, ensure the LAN client timeout is large enough if ilantimeout is used. See Using SICL with a LAN for more information.

Operation Following a Timed Out Operation Fails

An I/O operation following a previous timeout fails to return or takes longer than expected. Ensure the LAN timeout being used by the system is sufficiently greater than the SICL timeout being used for the session in question. The LAN timeout should be large enough to allow for the network overhead in addition to the time that the I/O operation may take.

If ilantimeout is used, you must determine and set the LAN timeout manually. Otherwise, ensure the Client Delta Timeout configuration value is large enough (via Connection Expert). See Using SICL with a LAN for more information.

iopen Fails or Other Operations Fail Due to Locks

An iopen fails due to insufficient resources at the server or I/O operations fail because some other session has the device or interface locked. LAN server connections for SICL from previous clients may not have terminated properly. Consult your server’s troubleshooting documentation and follow the instructions for cleaning up any previous server processes.