![]() |
![]() |
Define the Data Link Control (DLC)
Getting to SNA Server/6000 via SMIT
Creating the Initial Node Definition
To create the initial node definition, follow these steps:
Figure 30. Initial Node Setup Screen
+--------------------------------------------------------------------------------+ | Initial Node Setup | | | |Type or select values in entry fields. | |Press Enter AFTER making all desired changes. | | | | [Entry Fields] | | Control Point name token_ring + [F13833D0] | | Control Point type appn_end_node + | | Local network name [DEIBMFD] | | XID node ID [05df333d] | | | | Optional link station information: | | | | Link station type token_ring | | Link station name [] | |* Calling link station? yes + | | Link address [] X| | | | | | | | | | | |F1=Help F2=Refresh F3=Cancel F4=List | |Esc+5=Undo F6=Command F7=Edit F8=Image | |F9=Shell F10=Exit Enter=Do | +--------------------------------------------------------------------------------+
Creating the Link/Mode/Side Information
Token Ring SNA DLC
Figure 31. Add Token Ring SNA DLC Profile Screen
+--------------------------------------------------------------------------------+ | Add Token Ring SNA DLC Profile | | | |Type or select values in entry fields. | |Press Enter AFTER making all desired changes. | | | |[TOP] [Entry Fields] | | Profile name [tok0.00001] | | Data link device name [tok0] + | | Force disconnect time-out (1-600 seconds) [120] #| | User-defined maximum I-Field size? yes + | | | |
·
·
·
| | Receive window count (1-127) [8] #| | Ring access priority 0 + | | Inactivity time-out (1-120 seconds) [48] #| | Response time-out (1-40, 500 msec intervals) [4] #| | Acknowledge time-out (1-40, 500 msec intervals) [1] #| | Local link name [F13833D0] | | Local SAP address (04-ec) [04] X| | Trace base listening link station? no + | | If yes, Trace format long + | | Dynamic link stations supported? yes + | | | | Link Recovery Parameters | |
·
·
·
| | | | Dynamic Link Activation Parameters | | Solicit SSCP sessions? yes + | | CP-CP sessions supported? no + | | Partner required to support CP-CP sessions? no + | | | | Dynamic Link TG COS Characteristics | |
·
·
·
| | | | Dynamic Link TG COS Characteristics | |
·
·
·
| | | | Comments [] | |[BOTTOM] | | | |F1=Help F2=Refresh F3=Cancel F4=List | |Esc+5=Undo F6=Command F7=Edit F8=Image | |F9=Shell F10=Exit Enter=Do | +--------------------------------------------------------------------------------+
Token Ring Link Station
Figure 32. Add Token Ring Link Station Profile Window
+--------------------------------------------------------------------------------+ | Add Token Ring Link Station Profile | | | |Type or select values in entry fields. | |Press Enter AFTER making all desired changes. | | | |[TOP] [Entry Fields] | | Profile name [BCTSO] | | Use APPN Control Point's XID node ID? yes + | |* SNA DLC Profile name [tok0.00001] + | |
·
·
·
| | Adjacent Node Address Parameters | | Access routing link_address + | | If link_name, Remote link name yes [] | | If link_address, | | Remote link address [400010000002] X| | Remote SAP address (04-ec) [04] X| | | | Adjacent Node Identification Parameters | |
·
·
·
| | | | Link Activation Parameters | | Solicit SSCP sessions? yes + | | Initiate call when link station is activated? yes + | | Activate link station at SNA start up? yes + | | Activate on demand? no + | | CP-CP sessions supported? no + | |
·
·
·
| | | | Restart Parameters | |
·
·
·
| | | | Transmission Group COS Characteristics | |
·
·
·
| | | | Comments [] | |[BOTTOM] | | | |F1=Help F2=Refresh F3=Cancel F4=List | |Esc+5=Undo F6=Command F7=Edit F8=Image | |F9=Shell F10=Exit Enter=Do | +--------------------------------------------------------------------------------+
Defining LU 6.2 Session
LU 6.2 Mode
Figure 33. Add LU 6.2 Mode Profile Window
+--------------------------------------------------------------------------------+ | Add LU 6.2 Mode Profile | | | |Type or select values in entry fields. | |Press Enter AFTER making all desired changes. | | | | [Entry Fields] | |* Profile name [TSMAPPC] | | Mode name [TSMAPPC] | | 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 [] | | | | | | | |F1=Help F2=Refresh F3=Cancel F4=List | |Esc+5=Undo F6=Command F7=Edit F8=Image | |F9=Shell F10=Exit Enter=Do | +--------------------------------------------------------------------------------+
Partner LU6.2 Profile
Figure 34. Add LU 6.2 Partner LU Profile
+--------------------------------------------------------------------------------+ | 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 [BCTSO] | | Fully qualified partner LU name [DEIBMA4.A4VTSM2] | | Partner LU alias [A4VTSM2] | | Parallel sessions supported? yes + | | Session security supported? no + | | Conversation security level none + | | | | Comments [] | | | | | | | | | | | | | | | | | |F1=Help F2=Refresh F3=Cancel F4=List | |Esc+5=Undo F6=Command F7=Edit F8=Image | |F9=Shell F10=Exit Enter=Do | +--------------------------------------------------------------------------------+
Partner LU 6.2 Location
Figure 35. Add Partner LU 6.2 Location Profile Window
+--------------------------------------------------------------------------------+ | 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 [BCTSO] | | Fully qualified partner LU name [DEIBMA4.A4VTSM2] | | Fully qualified owning Control Point (CP) name [DEIBMFD.FDW] | | Local node is network server for LEN node? no + | | Fully qualified network node server name [] | | | | Comments [] | | | | | | | | | | | | | | | | | | | |F1=Help F2=Refresh F3=Cancel F4=List | |Esc+5=Undo F6=Command F7=Edit F8=Image | |F9=Shell F10=Exit Enter=Do | +--------------------------------------------------------------------------------+
Side Information
Figure 36. Add LU 6.2 Side Information Profile Window
+--------------------------------------------------------------------------------+ | 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 [BCTSO] | | Local LU or Control Point alias [F13833D0] + | | Provide only one of the following: | | Partner LU alias [] + | | Fully qualified partner LU name [DEIBMA4.A4VTSM2] | | Mode name [TSMAPPC] + | | Remote transaction program name (RTPN) [ANYTHING] | | RTPN in hexadecimal? no + | | | | Comments [] | | | | | | | | | | | | | |F1=Help F2=Refresh F3=Cancel F4=List | |Esc+5=Undo F6=Command F7=Edit F8=Image | |F9=Shell F10=Exit Enter=Do | +--------------------------------------------------------------------------------+
Verify Configuration Profiles
Figure 37. Advanced Configuration Window
+--------------------------------------------------------------------------------+ | Advanced Configuration | | | |Move cursor to desired item and press Enter. | | | | Links | | Sessions | | SNA System Defaults | | Control Point | | Gateway Definitions | | Security | | Verify Configuration Profiles | | Export Configuration Profiles | | Import Configuration Profiles | | Migrate Configuration Profiles | | | | | | | | | | | |F1=Help F2=Refresh F3=Cancel F8=Image | |F9=Shell F10=Exit Enter=Do | +--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+ |servername bctso | |commmethod snalu6.2 | | symbolicdestination bctso | +--------------------------------------------------------------------------------+
The SNA Services/6000 setup is the same as the SNA Server/6000 setup except for one important difference-the partnerluname in the dsm.sys file specifies the "Connection Profile" name of the file that has the partner LU definition and not the actual partner LU name. This difference is attributed to the way that SNA Services/6000 implements the partner LU.