TCP/IP (Parallel Library) Configuration and Management Manual

Configuring Parallel Library TCP/IP for Complex and
Heavy-Use Environments
HP NonStop TCP/IP (Parallel Library) Configuration and Management Manual—522271-006
3-14
Configuration Example for the Standard Listening
Model
The TCPIPUP2 File
The following TACL command file starts the processes, adds and starts subsystem
objects through SCF, and sets appropriate parameters. To add comments, use the
word “comment” or a double equal sign (==). Some lines are discussed separately
after the example. Substitute real values for variables (indicated in italics). (See the
Configuration Form 1 on page 1-5 and page 1-12 for procedures for determining these
values.)
The RUN command:
LISTNER/NAME $LSN0, NOWAIT, PRI 170, CPU 0/1, &
OUT $ZHOME, TERM $ZHOME, $SYSTEM.ZTCPIP.PORTCONF LOG_GOTCONN
starts the LISTNER processes responsible for starting the ECHO, FINGER, and FTP
servers when the LISTNER process receives a client request. Run these processes at
a high priority. This command also specifies the location of the PORTCONF file used to
designate which ports the LISTNER is to listen to. Since the LISTNER requires
privileged access to some Parallel Library TCP/IP ports, always log on with a super
group ID.
Example 3-2. TCPIPUP2 for the LISTNER Process
comment ==== TCPIPUP2 =========TCPIPUP2 ========
comment TACL command file to bring up Parallel Library TCP/IP
comment subsystem
comment Use DNS for name resolution; (no host file DEFINE)
DELETE DEFINE =TCPIP^HOST^FILE
comment ADD and START SUBNETS
SCF/IN $SYSTEM.TCPIP.SCFSBNT/
comment Initialize LISTNER for FTPSERV, ECHOSERV,
comment and FINGSERV
comment Define the TCPSAM process for the LISTNER to use
DELETE DEFINE =TCPIP^PROCESS^NAME
ADD DEFINE =TCPIP^PROCESS^NAME, class map, file $ZSAM0
comment Start the LISTNER
LISTNER/NAME $LSN0, NOWAIT, PRI 170, CPU 0/1, &
OUT $ZHOME, TERM $ZHOME,&
$SYSTEM.ZTCPIP.PORTCONF
comment ====== END OF TCPIPUP2 ==== END OF TCPIPUP2 ==
Note. The LOG_GOTCONN option enables the logging of "got connection" messages.
You can use these messages to monitor FTP requests. If you do not specify the
LOG_GOTCONN option, the "got connection" messages are not logged.