The 
                  		  Rumba+ APPC Configuration tool simplifies the task of managing remote and local logical unit (LUs)s. A local LU represents the local
                  workstation, while the a LU represents the local workstation conversation partner. 
                  		
               
 
               	 
              
            	 
            
               LU properties
 
               		 
               		
               Because the concept of the LU has evolved, it is easier to understand the LU by looking at its properties: 
                  		
               
 
               		
                
                  		  
                  - Sessions have LUs at each end. 
                     		  
                  
- To establish a session, a client must have the server’s LU name, which is known as the remote LU. 
                     		  
                  
- In a hierarchical network, an LU has a defined global address that it uses to route data. 
                     		  
                  
- You can assign different LU names to a host’s different subsystems. 
                     		  
                  
Note: An LU name does not signify a machine or program name, it designates the role a machine or program has within a network. For
                  example, an LU name can designate a network server. 
                  		
               
 
               	 
              
            	 
            
               Logical unit configuration tips
 
               		 
               		
               Here are a few tips to consider when you use the 
                  		  Rumba+ APPC Configuration tool to add or change logical units: 
                  		
               
 
               		
                
                  		  
                  - For a computer client, the LU name default can be the computer name. The 
                     			 Rumba+ APPC Configuration tool does this automatically in the configuration process. 
                     		  
                  
- For a server, consider using an LU name alias based on the function, rather than the computer name. This minimizes disruption
                     if the function is moved to another computer. 
                     		  
                  
- When you are connected to a subarea SNA network, finding an LU name is problematic because you do not have network node services.
                     In this case, you must configure a remote LU and associate it with a route.