LU names are a SNA thing. They don't apply with TCPIP sessions. What are they trying to do - identify the session somehow?
We are trying to make Automation point from CA work with a TN3270 session with a VM guest, The last step is to assign an LU name to the session. Don't see a way to do that in the VM world. Easy enough with MVS.