Check the Communications Server on UNIX
If the communications server process (iigcc) did not start, check the communications server.
To check the communications server
1. Verify that no local environment variables are set in the local user environment that contains the string GCC. At the operating system prompt type the command:
BSD:
printenv | grep GCC
System V:
env | grep GCC
The environment variable II_GCNxx_PORT will be set in the Enterprise Access symbol table. This variable should have the following features:
• Not be visible from the UNIX environment using the printenv or env commands.
• Be visible in the Ingres environment. Verify by typing ingprenv.
2. Use the ps -aux (BSD) or ps - ef (System V) to see if the iigcc process is running. If the process is not running, use the following command to start the communication server process manually:
ingstart -iigcc
3. If you are still having problems, set the following trace to capture diagnostic data and attempt to restart the communications server:
Bourne shell:
II_GCC_TRACE=4
II_GCA_LOG=stdio
export II_GCC_TRACE II_GCA_LOG
ingstart -iigcc
C shell:
setenv II_GCC_TRACE 4
setenv II_GCA_LOG stdio
iirun iigcc
4. If you corrected a communications server problem, verify that Enterprise Access will now start as usual:
a. Shut down the partially-started installation with the ingstop command.
b. Restart the installation with the ingstart command.
Last modified date: 08/22/2022