This chapter contains connectivity maintenance procedures, including:
The Communications Server starts up automatically when you start up your Ingres instance. Sometimes, however, it is necessary to stop the Communications Server.
You can start the local instance's Communications Server using Ingres Visual Manager (IVM). For specific instructions, see IVM online help.
You can also start the Communications Server using the command line utilities.
To start the Communications Server at the command line
ingstart -iigcc
The configured number of Communications Servers (set during installation) is started.
You can stop the local instance's Communications Server using Ingres Visual Manager (IVM). For specific instructions, see IVM online help.
You can also stop the Communications Server using the command line utilities.
You can stop the local instance's Communications Servers using Visual Performance Monitor. This "soft" shutdown operation waits for all sessions to end before stopping the server. Close the sessions (or ask users of those sessions to close them) before shutting down a server. For specific instructions, see Visual Performance Monitor online help.
To stop the communications server at the command line
ingstop -iigcc
The configured number of Communications Servers is stopped.
Note: To increase the configured number of servers, you must reconfigure Ingres Net using Configuration Manager (vcbf) or the Configuration-By-Forms (cbf) utility.
You can stop or quiesce the local instance's Communications Server using the Network Server Control screen in netutil.
The Network Server Control screen contains the following tables:
Lists the server IDs of the Communications Servers and the Bridge Servers on the local instance.
Lists server TYPEs (COMSVR, BRIDGE).
Note: You cannot obtain information about remote Communications Servers from this screen.
If the local instance has only one Communications Server, the Network Server Control screen menu selections are:
Stops the highlighted Communications Server after all sessions currently in progress terminate
Stops the highlighted Communications Server immediately, disconnecting any open sessions
Displays help screens
Returns you to the netutil startup screen
If the local instance has more than one Communications Server, the menu contains two additional selections:
Stops all Communications Servers after the sessions currently in progress terminate
Stops all Communications Servers immediately, disconnecting any open sessions
You can stop or quiesce a Communications Server using the Network Server Control screen in netutil.
To stop a single Communications Server
The Network Server Control screen appears.
A pop-up screen appears with the following prompt:
Really stop network server [server ID]?
Yes — Stop
No — Don't Stop
Netutil stops the Communications Server and returns to the Network Server Control screen.
You are returned to the netutil startup screen.
To stop multiple Communications Servers
A pop-up screen appears with the following prompt:
Really stop all network servers?
Yes — Stop
No — Don't Stop
Netutil stops all local Communications Servers and returns to the Network Server Control screen.
You are returned to the netutil startup screen.
To quiesce a single Communications Server
A pop-up screen appears with the following prompt:
Really quiesce network server [server ID]?
Yes — Quiesce
No — Don't quiesce
Netutil quiesces the Communications Server and returns to the Network Server Control screen.
You are returned to the netutil startup screen.
To quiesce multiple Communications Servers
A pop-up screen appears with the following prompt:
Really quiesce all network servers?
Yes — Quiesce
No — Don't quiesce
Netutil quiesces all local Communications Servers and returns to the Network Server Control screen.
You are returned to the netutil startup screen.
Note: For instructions on stopping or quiescing Communications Servers using netutil non-interactive mode, see the chapter "Establishing Communications."