The following information guides you through the tasks you must perform to create the SNA infrastructure that WebSphere MQ requires. This example creates the definitions for a new partner node and LU on OS/2.
Use snamgr to enter the AT&T GIS SNA Server configuration panels. You need root authority to use snamgr.
Throughout the following example, only the panels containing information that must be added or updated are shown. Preceding each panel is a list of the sequence of panels that you must invoke to proceed from the initial menu to the relevant customization panel.
Setting up the local node involves the following steps:
Proceed through these panels:
1 SNA Manager
2 Configuration
3 SNA Subsystem Configuration
4 SNA Subsystem Configuration Creation
The panels are shown as figures representing the screens that appear. Instructions for completing the screens and entering the correct information to configure the SNA subsystem are given in the text after each figure.
+--------------------------------------------------------------------------------+ |5 Create a Configuration | | | | Enter a unique configuration identifier (0-255) 010 | +--------------------------------------------------------------------------------+
Enter the configuration identifier ((1)).
+--------------------------------------------------------------------------------+ |6 Parameter File Configuration | | Will LU 6.2 be used? Y | +--------------------------------------------------------------------------------+
Enter Y.
+--------------------------------------------------------------------------------+ |1 SNA Configuration of the Local Node | | | | Node Parameters: | | | | Node ID of Local Node 00 | | | | PU Resource Name (optional) GISPU | | | | Network Identifier (optional) NETID | | | | Control Point (CP) Name (optional) GISPU | | | | Local LU 6.2 Parameters: | | | | LU 6.2 Logical Unit Name GISLU | | | | Max Number of LU 6.2 Sessions 0100 | | | +--------------------------------------------------------------------------------+
Enter the values for Node ID of Local Node, PU Resource Name ((6)), Network Identifier ((2)), CP Name ((3)), LU 6.2 Logical Unit Name ((4)), and Max Number of LU 6.2 Sessions.
Proceed through these panels:
2 Local Configuration
Select Define a mode.
+--------------------------------------------------------------------------------+ |3 Conversation Mode Definition | | | | Mode Name #INTER | | | | Maximum Number of Sessions 008 | | | | Number of Locally Controlled Sessions 004 | | | | Honor Pending Conversation Requests Before | | an Existing Session is Terminated? N | | | | Number of Automatically Established Sessions 004 | | | | Code Set to be Used During Transmission of TP Data E | +--------------------------------------------------------------------------------+
Enter the values for Mode Name ((7)), Maximum Number of Sessions, and Number of Locally Controlled Sessions.
+--------------------------------------------------------------------------------+ |4 Conversation Mode Definition for Max RU | | | |Send Max RU Size Upper Bound 03840 | | | |Send Max RU Size Lower Bound 00128 | | | |Receive Max RU Size Upper Bound 03840 | | | |Receive Max RU Size Lower Bound 00128 | | | +--------------------------------------------------------------------------------+
2 Local Configuration
Select Define a RECEIVE_ALLOCATE local TP.
+--------------------------------------------------------------------------------+ |3 Receive_Allocate Transaction Program Definition | | | |TP name MQSERIES_______________________ | | | |TP start type A (M = Manual, A = Automatic) | | | | | |receive_allocate timer (seconds) -1__ (0 - 9999, -1) | | | |Incoming allocate timer (seconds) -1__ (0 - 9999, -1) | | | |Max number of auto-started TP instances 1_ (1 - 99) | +--------------------------------------------------------------------------------+
Enter the values for TP name ((5)), and set the TP start type to A.
cd /usr/lbin ln -s /opt/mqm/bin/amqcrs6a MQSeries (5)
To connect to a partner node you need to:
Proceed through these panels:
2 Local Configuration
Select End Local Configuration.
1 Remote Node Definition
Select Peer Node Definition.
+--------------------------------------------------------------------------------+ |2 Remote Node Configuration | | | |Remote Node Name OS2PU | | | |Type of Link Connection TR | | | |SNA Logical Connection ID 00 | | | |Link to Backup (Optional) ____ | | | +--------------------------------------------------------------------------------+
Enter the values for Remote Node Name ((10)), Type of Link Connection, and SNA Logical Connection ID.
+--------------------------------------------------------------------------------+ |3 SNA/TR Configuration for Connection 01 | | | |Token Ring Adapter ID 01 | | | |Maximum Send BTU Length 1033 | | | |Local XID 03E00018 | | | |Data link role of local system NEG_ | | | |Remote DLSAP 04 | | | |Remote MAC Address 10005AFC5D83 | | | |Route Discovery Command T | | | |Broadcast Timer 1_ | | | +--------------------------------------------------------------------------------+
Enter the values for Token Ring Adapter ID, Local XID ((9)), and Remote MAC address ((16)).
+--------------------------------------------------------------------------------+ |4 Configuration of TR Adapter 01 for Connection 01 | | | |Local DLSAP 04 | | | |Adapter Type ild_ | | | +--------------------------------------------------------------------------------+
Proceed through these panels:
+--------------------------------------------------------------------------------+ |1 LU 6.2 Logical Unit Definition | | | |To complete the definition of Remote | | Peer Node, OS2, you need to | | define at least one Remote LU 6.2 | | Logical Unit. | | | | Press CONT to Continue. | +--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+ |2 Partner LU 6.2 Definition | | | |Locally Known Name OS2LU | | | |Network Identifier NETID | | | |Network Name (LUNAME) OS2LU | | | |Uninterpreted Name OS2LU | | | |Session Capability P | +--------------------------------------------------------------------------------+
Enter the values for Locally Known Name ((12)), Network Identifier ((11)), Network Name (LUNAME) ((12)), and Uninterpreted Name ((12)),
+--------------------------------------------------------------------------------+ |3 Automatic Activation | | | |Auto Activate at Start of Day? N | +--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+ |4 LU 6.2 Partner Definition | | | |Do you want to define another | |remote LU 6.2 Logical Unit in | |the remote node, OS2? N | +--------------------------------------------------------------------------------+
Proceed through these panels:
1 SNA MANAGER
2 Configuration
3 CPI-C Side Information
+--------------------------------------------------------------------------------+ |4 Add a CPI-C Side Information File | | | |Enter the CPI-C Side Information File Name OS2CPIC | | | |(This name is the Symbolic Destination Name used by | | the CPI-C program to reference side information.) | +--------------------------------------------------------------------------------+
Enter the name of the CPI-C Side Information File ((14)).
+--------------------------------------------------------------------------------+ |5 Add CPI-C Side Information | | | |Symbolic destination name: OS2CPIC | | | |Partner LU name OS2LU | | | |Mode name #INTER | | | |TP name MQSERIES | | | |Conversation security type NONE___ | | | |Security user ID __________ | | | |Security password __________ | +--------------------------------------------------------------------------------+
Enter the values for Partner LU name ((12)), Mode name ((15)), and TP name ((13)).
The LU 6.2 connection is now established. You are ready to complete the configuration. Go to MQSeries for AT&T GIS UNIX configuration.