Setting up the JES2 initialization deck

You need to set up your JES2 initialization deck to include the definitions for your NJE/TCP connections. The NJE/TCP parameters work similarly to those for SNA NJE.

Table 1. Comparison of NJE/SNA parameters and NJE/TCP parameters
NJE/SNA statement or parameter	Corresponding NJE/TCP parameter
LOGON(nnn) – defines interface between JES2 at this node and VTAM®	NETSRV(nnn) – defines interface between JES2 at this node and TCP/IP
APPL(xxxxxxxx) – maps an NJE node name to a VTAM application name. Used for both local and remote nodes. xxxxxxxx corresponds to an actual VTAM application name	SOCKET(xxxxxxxx) – maps an NJE node name to an IP address and port. Used for both local and remote nodes. xxxxxxxx is an abstract value used to reference the IP address and port combination.
LINE(nnnnn) UNIT=SNA – defines a logical connection	LINE(nnnnn) UNIT=TCP – defines a logical connection
$SN,A=xxxxxxxx – initiates an NJE connection with the specified VTAM application.	$SN,S=xxxxxxxx – initiates an NJE connection with the IP address and port defined on the SOCKET(xxxxxxxx) statement.

Other definitions that define your network (NJEDEF, NODE statements, additional parameters on LINE(nnnnn), etc.) are the same as for SNA and BSC connections. You can use TCP/IP connections in conjunction with SNA and BSC connections to talk to different nodes, or even as parallel connections to the same node.