sp_listener...start starts additional listeners. These are listeners in addition to those listed in the interfaces file. You can specify that the listener start on a specific range of engines.
The command will not fail when you use the remaining parameter, in case the listener is already enabled on some engines. If you explicitly include an engine list, and the listener is running on one of the specified engines, the command fails.
For example, the following specifies that a listener starts for server ASE1251 on engine number three:
sp_listener “start”, ASE1251, “3”
Or you can specify that the listener start on a certain machine and port number using a certain protocol. This example specifies that a listener start on port 4556 using the tli protocol on the IP address of machine spartacus on all engines for which this listener is not already running:
sp_listener “start”, “tli:ASE1251:4556”
You can also specify a range of engine numbers. For example, the following specifies that listeners start on engines three through six, corresponding to all master ports registered in the interfaces file under server name ASE1251:
sp_listener “start”, “ASE1251”, “3-6”
The following starts listeners corresponding to master ports registered under server name ASE1251 in the interfaces file on all engines on which the corresponding listener is not already active:
sp_listener “start”, “ASE1251”, “3-6”, “remaining”
