🚀 go-pugleaf

> Did I forget something? I don't have to redefine new LUs
>and PUs to communicate back the other way do I? I thought that is what
>the symbolic destination name is for.
>
Yes, in a LEN situation, you must define the other node, the link to the other n
ode, and the LUNAMEs on the other node.  The Symbolic Destination name is used t
o fetch from the Side Information the LUNAME, TPNAME, and MODENAME to be used on
 the incipient conversation.

But think algorithmically.  Ok, I want to run TP PINGD on node FRED with mode BL
ANK.  Now, where is FRED and how do I get to it?  You might think that having on
ce established a session with FRED would tell me, but a LEN node has no memory.
 The only way is for the CM configuration to associate "FRED" (in the same NETID
 of course) with Ethernet Adapter 0, MAC address 400010002000 (for example).  Th
en he knows to go to the first Ethernet card and send a BIND packet to SAP 04 on
 that adapter.

>PS. Can Communications Manager/2 be setup so you can ping yourself?
>
Yes, but ping is not very exciting.  Generally, if your machine can ask itself i
f it is up then the answer is yes. AREXEC is a bit more exciting, cause at least
 then you can see something happening.  Note that when you access your own LUs,
you do not have to (and in fact cannot) define a link to yourself or define your
 own node as a partner or your own LUs as both local and partner LUs.  VERIFY wi
ll fail.  Just reference your own LU name in the Symbolic Destination and forget
 about other node defintions.