Problem:
What is the correct way to configure/debug WOW Thin Client on a UNIX system?
Resolution:
First, make sure that you are using the version of WOW Thin Client on the Windows system that matches the version of the runtime. You cannot mix versions.
Next, make sure you are using a Runtime Plus version or Development version of the runtime on the UNIX/Linux system. The Runtime Plus and Development versions support Thin Client, while the regular Runtime does not. If unsure, contact Support and give us the serial number; we can check for you.
For normal execution:
1. Make sure the rpcstart script has execute permissions. For this example, it is located in the /usr/rmcobol directory and should look like this:
#!/bin/sh
#
TERM=dumb; export TERM
RM_LOAD_WOW_CLIENT=yes; export RM_LOAD_WOW_CLIENT
cd /usr/rmcobol && runcobol ./helowrld.cob k
(You can locate the rpcstart script anywhere, but make sure the rpcplus.ini file is in the same directory, and have the script change to that directory before executing the runcobol command.)
2. The entry in the /etc/inetd.conf file should look like:
rpcplus stream tcp nowait root /bin/sh rpcplus /usr/rmcobol/rpcstart
3. Whenever you change the inetd.conf file, you have to restart the service. This can be accomplished by using the command:
kill -HUP <pid>
Where <pid> is the process id of the inetd process. Use this command to determine whether inetd is listening:
netstat -a | grep "rpcplus"
This command should show an rpcplus port in a LISTEN state.
4. From the Windows system, make sure you can successfully ping the UNIX server.
For debugging:
1. Look at the rpcplus.log file for error messages. If nothing is obvious, continue.
2. Create a script file called "debugrpc" in the /usr/rmcobol directory, with the following contents:
#!/bin/sh
#
TERM=dumb; export TERM
RM_LOAD_WOW_CLIENT=yes; export RM_LOAD_WOW_CLIENT
cd /usr/rmcobol && ./runcobol ./helowrld.cob A=D
(You can use a program other than helowrld, but if it is not in the current directory, use the full path to it. Also, you can locate debugrpc in another directory, but you must put a copy of the rpcplus.ini file in the same directory, and change to it before executing the runcobol command.)
3. Modify the rpcplus.ini files on the server and the client systems to use a port not listed in the /etc/services file.
4. Make sure the debugrpc file has execute permissions, then type:
./debugrpc
When you hit the return key, it should sit there and wait for a client. If so, start the client. If not, send the error message and the log file to support@liant.com. If the client does not start, send a screenshot of the error it reports.
