TCP/IP (Parallel Library) Migration Guide

Migration Considerations

HP NonStop TCP/IP (Parallel Library) Migration Guide—522272-003

3-6

Management Interfaces

This subsection describes differences in the management interfaces between the

conventional TCP/IP and Parallel Library TCP/IP. There is a different subsystem name

described in Subsystem Name on page 3-6. The subsection about SCF describes the

key differences in this interface, followed by a description of the new SCF attribute,

Master TCPMON on page 3-7. The SCF management interface is followed by a

Command-By-Command Configuration Comparison on page 3-7 which provides an

example of how the differences between Parallel Library TCP/IP and conventional

TCP/IP affect configuration. Finally, SPI Interface on page 3-12, describes the

differences in the SPI interface between the two subsystems.

Subsystem Name

The subsystem ID for conventional TCP/IP is ZTCI. The name for Parallel Library

TCP/IP is ZTCP.

PTCPIP replaces TCPIP as the subsystem name and should be used when requesting

SCF help.

SCF

For complete reference information about SCF and the SCF command syntax, see the

TCP/IP (Parallel Library) Configuration and Management Manual. For information

about the SCF interface to TCPSAM, see SCF on page 2-5.

Object Name Syntax

Another level of qualification is required for the SUBNET, ROUTE, and ENTRY objects.

In Parallel Library TCP/IP, the name syntax for these objects includes the MON object.

The pound sign (#) still precedes the MON name but the SUBNET, ROUTE, and

ENTRY objects no longer require the pound sign. Although placing a pound sign (#) in

front of those objects does not generate an error, the preferred way to specify the

object is without the pound sign (#) as shown in the following naming specifications:

SCF Objects

The following SCF objects from conventional TCP/IP are not supported in Parallel

Library TCP/IP:

•

SERVER

•

ADDRMAP

The MON object is new for Parallel Library TCP/IP.

SUBNET $TCPMAN-name.#TCPMON-name.subnet-name

ROUTE $TCPMAN-name.#TCPMON-name.route-name

ENTRY $TCPMAN-name.#TCPMON-name.entry-nameì