TCP/IP (Parallel Library) Migration Guide
Introduction
HP NonStop TCP/IP (Parallel Library) Migration Guide—522272-003
1-4
Summary of Differences Between Conventional
TCP/IP and Parallel Library TCP/IP
•
Fault-tolerance: Fault-tolerant behavior is different in some circumstances. See 
Event Management Service (EMS) on page 2-3 and Fault-Tolerant Behavior on 
page 3-4.
•
Guardian Socket Migration: There are programming considerations for 
enhancing performance when an application migrates a Guardian socket to 
another processor. See Guardian Socket Migration on page 3-5.
•
Management Interfaces: There are differences in the SCF and SPI interfaces to 
Parallel Library TCP/IP. See Management Interfaces on page 3-6.
•
NonStop Distributed Object Manager/MP: To use NonStop DOM over Parallel 
Library TCP/IP, download the most recent version of NonStop DOM. See 
Persistence Manager on page 3-10. 
•
Persistence Manager: There are differences in how you manage the Persistence 
Manager for TCP/IP. See Persistence Manager on page 3-10.
•
Platform: Parallel Library TCP/IP runs on NonStop S-series servers only.
•
Port Sharing: Listening applications running in multiple processors can share the 
same port. See Round-Robin Filtering on page 3-12.
•
Round-Robin Filtering: Incoming connections can be distributed among 
applications that share a port and run in different processors. See Round-Robin 
Filtering on page 3-12.
•
SCF: There are differences in some of the SCF objects and object-naming 
specifications. See Section 2, The New Socket Provider and the TCP/IP (Parallel 
Library) Configuration and Management Manual.
•
SNMP: There is a migration consideration for SNMP. See SNMP on page 3-12.
•
SPI: Subsystem Programmatic Interface (SPI) support is limited. See SPI Interface 
on page 3-12.
•
SRL: Parallel Library TCP/IP uses a private SRL. See Shared Run-Time Library 
(SRL) on page 3-12 for considerations regarding the SRL. 
•
SWAN: There are restrictions for the ServerNet wide area network (SWAN) 
subsystem. See SWAN on page 3-12.
•
System Configuration Database: Some configuration attributes are automatically 
stored in the system configuration database. See Section 4, Procedures for 
Migrating Applications to Parallel Library TCP/IP.
•
TELSERV: Static windows and servers in TELSERV must be added in your startup 
command file or by using SCF. In addition, the RESILIENT ON attribute of 
TELSERV does not work in combination with round-robin filtering. See Telserv on 
page 3-12.
•
Tracing: There are some new considerations for tracing. See Trace on page 2-5 
and Trace on page 3-13.










