NIO CommKit Host Interface Installation and System Administration Manual

4-14

Administering the CommKit Software and the STREAMS Listener

Administering the STREAMS TLI Listener

A Datakit network can handle incoming calls through the CommKit server

or through an alternate method known as the Network Listener Service

(NLS). The Network Listener Service is incorporated into the HP-UX

STREAMS environment. This allows you to create custom modules and

push these modules onto the CommKit STREAMS stack and create new

applications.

NLS requests are handled by a listener process that determines how to

respond from a database of available services in the /usr/net/nls directory.

Each CommKit interface board has one listener process associated with it,

which is identiﬁed by its network speciﬁcation (net_spec). The network

speciﬁcations are:

• dktp0 for the first interface board

• dktp1 for the second

• dktp2 for the third

• dktp3 for the fourth

• dktp4 for the fifth

• dktp5 for the sixth

• dktp6 for the seventh

• dktp7 for the eighth

You manage the NLS database and the listener process by using the nlsad-

min command. The nlsadmin command forms the basis for the /sbin/init.d/

dkit script that controls the NLS service.

The listener process monitors the network interface for NLS service requests

directed to its address. By convention, the listener address is the same as the

CommKit server address, but with its letters in uppercase. For example, if

the CommKit server address is hpams5x, the listener address would be

HPAMS5X, if the server address is hpams5x1, the listener address would be

HPAMS5X1. There should be a listener process for each interface that will be

receiving service requests.