How to Configure Independent LU 6.2 Sessions on Communications Server for AIX V4

Contents

About this document
    Related documentation
Independent LU 6.2 configuration
    Configuring the LU 6.2 local LU profile
    Configuring the LU 6.2 partner LU profile
    Configuring the partner LU 6.2 location profile
    Configuring a mode profile
    Configuring the side information profile
    Configuring the transaction program name profile
Verifying profiles

About this document

This document applies to AIX Version 4.x.

  1. This document assumes that the link station associated with these LU6.2 sessions has been successfully configured. This means that the link station can be started, will connect, and will display as "active" when an sna -d l command is issued.

    With that assumption, the following information provides instructions for configuring and starting one or more independent LU 6.2 sessions between different machines.

  2. A "profile", as used in this document, is a collection of statements and questions arranged in "stanzas", which are then grouped by content into a profile. Most profiles have several default values.

  3. Items in a profile which are preceeded by an * must be completed for the profile to verify. Verification is required to make a profile available to SNA. Any verification errors must be corrected before attempting to use the new or changed profile.

  4. It should be noted that any item in a profile that is not mentioned in this document should be left at the default value.

  5. Because many installations do not use graphics, this document refers to smitty rather than smit. Smitty is the ascii version of the System Management Interface Tool and can be used in both graphics and non-graphics environments. If desired, using smit should provide identical results.

Related documentation

For more information on these items, refer to IBM document number SC31-8213, "Communications Server for AIX Configuration Reference".

The AIX and product documentation library is also available:
http://www.rs6000.ibm.com/resource/aix_resource/Pubs/index.html

Independent LU 6.2 configuration

The following profiles WILL be needed for an independent LU 6.2 configuration.

  1. LU 6.2 Local LU Profile (needed most of the time)

  2. LU 6.2 Partner LU

  3. Partner LU 6.2 Location

  4. Mode

The following profiles MAY be needed depending on the application using SNA.

  1. LU 6.2 Side Information

  2. LU 6.2 Transaction Program Name (TPN)

Configuring the LU 6.2 local LU profile

This section contains instructions for configuring the LU 6.2 Local LU profile. It assumes that no profile exists.

To create this profile, enter the following: 
			smitty sna
Select the following: 
			Configure SNA Profiles Advanced
			  Configuration Sessions LU 6.2
Notice that the title of each screen is the same as the option PREVIOUSLY selected. The F3 (Cancel) key will show the PREVIOUS selection.

  1. Select LU 6.2 Local LU.

    You will be offered several choices for what to do next. Assuming no useful profile exists, select Add a Profile.

  2. You will be presented with the following screen. 
    			   Add LU 6.2 Local LU Profile
Type or select values in entry fields.  Press Enter AFTER making
all desired changes.
                                                        [Entry Fields]
* Profile name                                       []
* Local LU name                                      []
  Local LU alias                                     []
  Local LU is dependent?                              no                       
     If yes,
        Local LU address (1-255)                     []                        #
        System services control point
           (SSCP) ID (*, 0-65535)                    [*]
        Link Station Profile name                    []                        
  Conversation Security Access List Profile name     []			       
  Recovery resource manager (RRM) enabled?            no
  
   Comments []
    Profile Name
    While this can be any valid AIX filename, it is advisable to use the Local LU name as the profile name. This will avoid confusion when looking for a specific Local LU in a list of profiles.

    Local LU Name
    The label next to the LU as defined in VTAM under the switched major node definitions.

    Local LU is Dependent?
    The answer to this question must be no for this to be an INDEPENDENT LU 6.2 session. This document is based on this parameter being set to no.

Configuring the LU 6.2 partner LU profile

This section contains instructions for configuring the LU 6.2 Partner LU profile. It assumes that no profile exists.

To create this profile, enter the following: 
			smitty sna
Select the following: 
			Configure SNA Profiles Advanced
			  Configuration Sessions LU 6.2
  1. Select LU 6.2 Partner LU.

    You will be offered several choices for what to do next. Assuming no useful profile exists, select Add a Profile.

  2. You will be presented with the following screen. 
    			Add LU 6.2 Partner LU Profile
Type or select values in entry fields.  Press Enter AFTER making
all desired changes.
                                                        [Entry Fields]
* Profile name                                       []
* Fully qualified partner LU name                    []
  Partner LU alias                                   []
  Parallel sessions supported?                        yes                      
  Session security supported?                         no                       
  Conversation security level                         conversation             
  
   Comments []
    Profile Name
    Again, while this name can be any valid AIX filename, consider using the Local LU profile name that was just configured. By assigning the same name to all profiles related to the Local LU, confusion can be avoided.

    Fully Qualified Partner LU Name
    The format is as follows: NetworkName.LUName. The NetworkName must match the name of the network where the partner LU is located. The LUName must match the Local LU on the remote system (this is the applid in VTAM). Remember to separate the two names with a period.

Configuring the partner LU 6.2 location profile

This section contains instructions for configuring the Partner LU 6.2 Location profile. It assumes that no profile exists.

To create this profile, enter the following: 
			smitty sna
Select the following: 
			Configure SNA Profiles Advanced
			  Configuration Sessions LU 6.2
  1. Select Partner LU 6.2 Location.

    You will be offered several choices for what to do next. Assuming no useful profile exists, select Add a Profile.

  2. You will be presented with the following screen. 
    		       Add Partner LU 6.2 Location Profile
Type or select values in entry fields.  Press Enter AFTER making
all desired changes.
                                                        [Entry Fields]
* Profile name                                       []
* Fully qualified partner LU name                    []
  Partner LU location method                          owning_cp                
  If owning_cp,
     Fully qualified owning Control Point (CP) name  []
     Local node is network server for LEN node?       no                       
     Fully qualified network node server name        []
  If link_station,
     Local LU name                                   []
     Link Station Profile name                       []                        
  
  Comments                                           []
    Profile Name
    Again, consider using the same profile name used for the previous profiles.

    Fully Qualified Partner LU Name
    This is the same name as defined in the Partner LU 6.2 profile.

    Fully Qualified Control Point Name
    Format: NetworkName.CPName. This is the NetworkName (see the Partner LU 6.2 profile) and the control point (CP) name that will control this resource.

    This name can be found by executing the following command with Communications Server (SNA) running and the link station connected. 

    			sna -d l
    The entry under Adjacent CP name is the correct NetworkName.CPName to be used.

Configuring a mode profile

This section contains instructions for configuring a Mode Profile.

NOTE: While the other profiles have a default template that can be used as a model, several Mode Profiles are provided with Communications Server. These profiles contain parameter values that are suitable for many application needs, and they are ready to be used. IBM-supplied mode names are reserved. You cannot define a new Mode Profile with a mode name used by one of these modes. If you do not know the mode required by the remote LU, check with the administrator of the remote system. The mode name also appears in the Side Information Profile for the sessions that use this Mode Profile to define their session characteristics.

The Side Information Profile is configured in a subsequent section of this document.

To create the Mode Profile, enter the following: 
			smitty sna
Select the following: 
			Configure SNA Profiles Advanced
			  Configuration Sessions LU 6.2
  1. Select LU 6.2 Mode.

    You will be offered several choices for what to do next.

    1. To choose from a list of ready-to-use profiles, select Change/Show a Profile. Then press F4 to see the list. To see a desired profile, select it and press enter.

    2. If one of the Mode Profiled meets requirements, no further work is needed. Note the profile name and press the F3 key to exit.

    3. If none of the pre-defined Mode Profiles is satisfactory, create a new Mode Profile by selecting Add a Profile.

  2. You will be presented with the following screen. 
    			     Add LU 6.2 Mode Profile
 Type or select values in entry fields.  Press Enter AFTER making
 all desired changes.
                                                        [Entry Fields]
* Profile name                                       []
  Mode name                                          []
  Maximum number of sessions (1-5000)                [8]                       #
  Minimum contention winners (0-5000)                [4]                       #
  Minimum contention losers (0-5000)                 [0]                       #
  Auto activate limit (0-500)                        [0]                       #
  Upper bound for adaptive receive pacing window     [16]                      #
  Receive pacing window (0-63)                       [7]                       #
  Maximum RU size (128,...,32768: multiples of 32)   [1024]                    #
  Minimum RU size (128,...,32768: multiples of 32)   [256]                     #
  Class of Service (COS) name                        [#CONNECT]
  
  Comments                                           []
    Mode Name
    The local node includes this mode name in SNA network control messages it sends to the node containing the partner LU. A mode with the same name should be defined in the node containing the partner LU. The session parameters associated with the mode can be negotiated between the local and partner LUs.

Configuring the side information profile

This section contains instructions for configuring the Side Information Profile. It assumes that no profile exists.

To create this profile, enter the following: 
			smitty sna
Select the following: 
			Configure SNA Profiles Advanced
			  Configuration Sessions LU 6.2
  1. Select LU 6.2 Side Information.

    You will be offered several choices for what to do next. Assuming no useful profile exists, select Add a Profile.

  2. You will be presented with the following screen. 
    		       Add LU 6.2 Side Information Profile
Type or select values in entry fields.  Press Enter AFTER making
all desired changes.
                                                        [Entry Fields]
* Profile name                                       []
  Local LU or Control Point alias                    []                        
  Provide only one of the following:
     Partner LU alias                                []                        
     Fully qualified partner LU name                 []
  Mode name                                          []                        
  Remote transaction program name (RTPN)             []
  RTPN in hexadecimal?                                no                       
  
  Comments                                           []
    Profile Name
    Again, consider using the same profile name used for the previous profiles. If you have not been consistent with the naming to this point, it is strongly recommended that this profile name be the same as the LU 6.2 Partner LU Profile.

    Local LU or Control Point Alias
    To identify the local LU for any conversations initiated by Transaction Programs (TPs) using this Side Information Profile, enter the alias of either a local LU or the node control point. If you enter an alias, it must match an alias defined in either the Control Point Profile or an LU 6.2 Local LU Profile. If no value is entered in this field, the node control point serves as the local LU for the Side Information Profile.

    The TP cannot override this value; the local LU cannot be changed by a local TP.

    Mode Name
    This must be defined on the computer as well as the remote side. Talk to administrators of the remote system to make sure that it is added.

    RTPN (Remote Transaction Program Name)
    This item normally can be left blank, but check the the application to ensure that it is not needed.

Configuring the transaction program name profile

This section contains instructions for configuring the Transaction Program Name Profile. It assumes that no profile exists.

To create this profile, enter the following: 
			smitty sna
Select the following: 
			Configure SNA Profiles Advanced
			  Configuration Sessions LU 6.2
  1. Select LU 6.2 Transaction Program Name(TPN).

    You will be offered several choices for what to do next. Assuming no useful profile exists, select Add a Profile.

  2. You will be presented with the following screen. 
    			   Add LU 6.2 TPN Profile
Type or select values in entry fields.  Press Enter AFTER making
all desired changes.
  
[TOP]                                                   [Entry Fields]
* Profile name                                       []
  Transaction program name (TPN)                     []
  Transaction program name (TPN) is in hexadecimal?   no                       
  PIP data?                                           no                       
     If yes, Subfields (0-99)                        [0]                       #
  Use Command Line Parameters?                        no                       
  Command Line Parameters                            []
  Conversation type                                   either                   
  Sync level                                          none/confirm             
  Resource security level                             none                     
     If access, Resource Security Access List Prof.  []
* Full path to TP executable                         []
  Multiple instances supported?                       no                       
  Use user ID from ATTACH?                            no                       
  User ID                                            [100]                     #
  Server synonym name                                []
  Restart action                                      once                     
  Communication type                                  signals                  
     If IPC, Communication IPC queue key             [0]                       #
  Time out Attaches?                                  yes                       
    If yes, time-out value (0-3600 seconds)          [60]                      #
* Standard input file/device                         [/dev/console]             
* Standard output file/device                        [/dev/console]             
* Standard error file/device                         [/dev/console]             
  Comments                                           []
[BOTTOM]
    Transaction Program Name (TPN)
    This field specifies the name of the TP provided in the inbound allocation request. The name must match the TP name specified in the allocation request of the source TP. TP names registered by ALLOCATE_LISTEN should not be entered in this field.

    NOTE: You must provide an entry in this field if this profile specifies a target TP that can be started by a remotely initiated allocation request.

    Full Path to the TP Executable
    Enter the full path and executable name for the TP on the local system. The AIX program corresponding to this executable name is invoked by Communications Server for AIX as a result of receiving an inbound allocation request. For example, if the name of the application program executable is svrprog, and it is in the /bin directory, enter the following path name for this field: 
    		 /bin/svrprog
    NOTE: You must enter a value if this profile specifies a target TP that can be started in response to an inbound allocation request. Enter a dummy value in this field for TPs registered using ALLOCATE_LISTEN.

Verifying profiles

At this point, all profiles necessary to establish a session between an LU on this RISC machine and a Partner LU on another machine should be in place. To make these profiles available to Communications Server (SNA), the profiles must be verified.

  1. Ideally, verify the profiles with SNA inactive. Issue the following command from the command line: 
       
	   verifysna -U
    This can be executed through smitty from any screen in the Configure SNA Profiles path. Use care to select normal_update before pressing the enter key.

  2. If the Communications Server (SNA) cannot be brought down, the profiles can be verified dynamically from the command line by issuing the following: 
      
	   verifysna -R
    This can also be executed from smitty screens by selecting the dynamic_update option.

    Dynamic updating of the profiles puts them into position for SNA to use them, but in many cases SNA is using the current profiles, and the new ones cannot be read until SNA is stopped and then restarted.

When the profiles have been verified and read, and SNA is up and running, the session can be started by the application on this RISC machine if the application can use the Side Information profile. An application session can be started on the Partner machine, if allowed, by using the TPN profile.

A manual session can be started by using smitty sna and selecting the Manage SNA Resources option. Select Start SNA Resources and then Start an SNA Session. You will be presented with the following screen: 

	                      Start an SNA Session
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
  
                                                        [Entry Fields]
  Specify one of the following:
     Local LU name                                   []                        
     Local LU alias                                  []                        
  
  Specify one of the following:
     Fully qualified partner LU name                 []                        
     Partner LU alias                                []                        
  
  Mode name                                          [#INTER]                  
  
  Session type                                        conwinner
Enter the required information and press enter. The session should start. If no error messages are returned, sessions can be verified by issuing the following on the command line: 
sna -d s
You should see your sessions under the headings in the display that is returned. The headings are as follows: 
(Display LU 6.2 Session Information)
             Local            Partner        Mode      Link
 CGID       LU name           LU name        name     station     State
------ ----------------- ----------------- -------- ----------- ----------



[ Doc Ref: 9064782739918     Publish Date: Oct. 16, 2000     4FAX Ref: 3057 ]