This section describes the procedure for installing Entire Net-Work TCP/IP Option on BS2000/OSD host systems.

The information in this section uses the substitution variable vrs, which stands for the current version, revision, and system maintenance (SM) level of the product; for example: "612".

• Installation Prerequisites

• Installation Steps

• Starting the TCP/IP Line Driver

---

Installation Prerequisites

The Entire Net-Work TCP/IP line driver uses the Sockets subsystem which is a component of Open Net Server (for specific information, see the section TCP/IP Transport Providers Supported).

Installation Steps

1. Ensure that BCAM is up and running.

2. Ensure that the Sockets subsystem has been created and started. Check the status and version of the Sockets subsystem using the following command:

   SHOW-SUBSYSTEM-STATUS SUBSYSTEM-NAME=SOCKETS

3. Ensure that the appropriate entries have been added to the BCAM resource definitions (TCP partners, etc.) or that DNS name resolution is enabled.

Starting the TCP/IP Line Driver

The Entire Net-Work TCP/IP line drivers (TCPI/TCPX) consist of a component running in the main Entire Net-Work task and one separate subtask, that serves all three line drivers. The subtask is the actual TCP protocol handler. It performs the TCP/IP processing.

If you are running Sockets 2.2 or later, incoming calls to the Entire Net-Work from Sockets is signaled by a P1 event. A separate subtask is no longer necessary to maintain asynchronous processing.

If you are running a version of SOCKETs earlier than 2.2, two tasks are required for the following reasons:

• Both Adabas and the Sockets interface require a synchronous wait. Only one synchronous wait per task is possible.

• The BS2000/OSD kernel does not support multiple tasks within one address space. Socket calls are therefore processed by a separate operating system task, referred to as the TCP/IP line driver subtask.

The subtask is started automatically by the main task according to the parameters in the NWBS2SUB variable in the STARTP procedure; no separate operator action is required. The parameters for the subtask are constructed within the STARTP procedure. If necessary, however, the JOB-CLASS, LIBrary, or ELEment values may be changed.

/ DECLARE-VARIABLE - 
/       NWBS2SUB(INIT=-
                      /'ENTER-PROC FROM  = (LIB = WCP&VERSION..LIB,-       
                      / ELE = SUBTASKPROC),-               
                      / PROC-PAR= (WTCLIB= WTC&VERSION..LIB,-
 /WCPLIB= WCP&VERSION..LIB,-
 /DUMP = &DUMP),-
 /JOB-CLAS = *STD,-               
 / RESOURCE= *PAR(CPU-LIMIT=&TIME),-
 / SYS-OUTP = *DELETE)')