🚀 go-pugleaf

>I'm trying to get the APING.EXE on an OS/2 machine to communicate
>with the APINGD.EXE on another OS/2 machine. Can I do direct
>Peer-to-peer communication with the other OS/2 machine, or do
>we have to have some type of network node server. If a network node
>server is needed, can I set up one of my OS/2 machines to be the
>network node server?

Before there was APPN, SNA defined PU 2.1 as a link between two peer nodes.  Lat
er on, this was renamed "LEN", but it remains a feature of current software like
 CM/2.  To use LEN, you must configure the other node, the physical link to the
other node, and the LUNAMES found on the other node.  For a pair of machines, yo
u should configure each to the other.

In the Communications Manager Setup program, under Local Node Characteristics, c
lick the button labelled "End node - no network node server".

Under SNA Connections, Create an entry for the other node.  The type is "To peer
 node".  You choose a type of Link (Ether, Token, SDLC), and then configure para
meters appropriate for the link.  For a LAN, you configure the MAC address assig
ned to the adapter card of the other machine.  Leave 04 as the SAP.  The NETID s
hould be the same on the two machines.  Generally, the node name on this machine
's "Connection to a Peer Node" panel should match the data in the other machines
 "Local Node Characteristics" and visa versa.

Hey, but don't be so quick to click OK.  There is another button labelled "Defin
e Partner LUs".  Click it and then define the LUNAMES on the other machine much
as you will define LUs on your own machine.  Yes, you can use the LUNAME implied
 by the Node name, or you can create separate LUs.  What is important is that by
 defining the remote LUs under the "Connection to a Peer Node" panel, the utilit
y knows to associate these LUNAMES with that node and therefore with the LAN MAC
 address that you used to configure the Peer node.

Later on, when you use the remote LUNAME either explicitly or through Side Infor
mation, CM finds that the name is on the partner node, and from the partner node
 selects the right like (LAN or SDLC) and the right address to use to physically
 make the connection.  It then sends the partner node a BIND with the LUNAME to
establish a session, and starts a transaction with the TPNAME that your program
uses.

Of course, I provide no information on TPNAME since you get that from the instal
lation instruction for the application.