Cluster I/O Protocols (CIP) Configuration and Management Manual (H06.16+, J06.05+)

How to Migrate From NonStop TCP/IP or NonStop TCP/IPv6 to CIP
Migrate the Environment
If you are running multiple TCP/IP subsystems and want to use CIP for your application but the
default TCP/IP process ($ZTC0) is assigned to either Nonstop TCP/IPv6 or conventional TCP/IP,
you can migrate your application to the CIP subsystem by adding a DEFINE or PARAM establishing
another (non $ZTC0) CIPSAM process as the transport service provider in the TACL environment
in which your program is running. The procedure documented here includes that final step of setting
the DEFINE or PARAM as well as the preliminary steps of preparing for using the CIP environment.
To migrate to the CIP networking environment:
1. Have your support provider install the CLIMs and bring up the subsystem.
2. Make any changes to your applications required by the compatibility differences documented
in this chapter.
3. Change the applications to use a CIPSAM process.
a. Find a CIPSAM process by using the SCF LISTDEV CIP command or create a CIPSAM
process (see Chapter 2 (page 62)) that matches the name of the TCP/IP process your
applications are using.
b. Set up the transport-service provider name for Guardian and OSS applications to the
CIPSAM process by entering one of these commands:
• ADD DEFINE =TCPIP^PROCESS^NAME, class map, file $cipsam-process-name
• PARAM TCPIP^PROCESS^NAME $cipsam-process-name
• Use these procedure calls to set the transport-service provider to a CIPSAM process:
◦ socket_set_inet_name() (for Guardian applications)
◦ socket_transport_name_set() (for OSS applications)
How to Migrate From NonStop TCP/IP or NonStop TCP/IPv6 to CIP 203