How You Direct Logging Output to a File
During a session, each process or program queries the value of II_GCA_LOG when it starts up. If this environment variable/logical is set to a file name, the program sends its trace output to the specified file in addition to sending the output to the errlog.log. If you want to see the GCC trace output for a Communications Server, set II_GCA_LOG and stop and restart the Communications Server.
After you restart the Communications Server, unset II_GCA_LOG. You can leave II_GCA_LOG set, but you receive trace output for any process that starts after it was set.
To send the GCC information that is logged in errlog.log to another file in addition to the log file, follow this process:
Windows and UNIX:
1. Log in as the installation owner.
2. Set the Ingres environment variable II_GCA_LOG to a file name.
3. Stop and restart the Communications Server. 
VMS:
1. Log in as the installation owner.
2. Define the logical II_GCA_LOG to a file name. If this is a production instance, define the logical at the system level. If this is a test instance, define the logical at the group level.
3. Stop and restart the Communications Server. 
Last modified date: 01/30/2023