This chapter explains how to configure the IRIS SNA SERVER using the IRIS SNAView graphical user interface network management tool. Topics covered include selecting the configuration file, selecting the communications device, and configuring the server for your connection. Detailed instructions for completing the fields in the SNAView windows are provided. The chapter concludes with a tutorial approach to creating your first IRIS SNA SERVER configuration.
The way in which you prepare the IRIS SNA SERVER for operation depends on whether you plan to use an existing configuration file or to create a new one (either from scratch or by modifying an existing configuration file).
If you use an existing configuration file, follow these steps:
Select the SNA configuration through your choice of a configuration file as described in Section , “Selecting the Configuration File.”
Select the appropriate communications device (Token Ring or SDLC) as described in Section , “Selecting the Device (SDLC/Token Ring).”
Activate the Gateway as described in Chapter 4.
Activate the Line as described in Chapter 4.
After the Line is activated, you can begin using SNA applications.
To create a new configuration file and activate the IRIS SNA SERVER for one of these three possible connections—SNA 3270 or 3770 Host, SNA LU 6.2 Host, and SNA LU 6.2 Peer-to-Peer—perform these procedures:
Open a configuration file similar to the one you want to create.
If you are creating a completely new configuration file, select the “New” File menu item to open the configuration file. To modify a file, select “Open” and open a file similar to the one that you want to create; this file will serve as a template.
Select the appropriate communications protocol device for your
configuration (SDLC or token ring).
Press either the 3270/3770 Host, LU 6.2 Host, or LU 6.2 Peer button in the Configuration Panel, which displays the Connection Configuration window for each connection.
Complete the information requested in the respective Connection
Configuration window.
Save the new configuration file using either “Save” or “Save As...”.
Activate the Gateway.
Activate the Line.
Before configuring the server, you need to collect information about the partner system to which the IRIS SNA SERVER communicates. If the server is to be configured for the 3270/3770 or LU 6.2 host, follow the instructions given in Section , “Configuring the Server for the 3270/3770 Host Connection.” If the server is to be configured for the LU 6.2 host connection, also see Section , “Additional Information for the LU 6.2 Host Connection.” If the server is to be configured for the LU 6.2 peer-to-peer connection, follow the instructions given in Section , “Configuring the Server for an LU 6.2 Peer-to-Peer Connection.”
The kind of IBM host information you collect depends on the means by which the IRIS SNA SERVER communicates with the IBM host. There are five possible configurations:
SDLC leased line
SDLC dial line
Token ring through the 3174 controller
Token ring through the 3172 controller
Token ring through NCP Network Token Ring Interface (NTRI)
Instructions for each configuration are given below. If your connection is for an LU 6.2 host, you will need to collect additional information; see Section , “Additional Information for the LU 6.2 Host Connection.”
From your IBM host system administrator, request the following VTAM information:
PU:MAXDATA=nnn
PU:MAXOUT=n
PU:ADDR=xx
GROUP:NZRI=(NO)YES
GROUP:DUPLEX=(FULL)HALF
LU:LOCADDR=nnn
where n represents decimal numbers and x, y, z are hexadecimal digits
Request the following IBM host VTAM definitions from your IBM host system administrator:
PU:IDBLK=xxx
PU:IDNUM=yyyyy
PU:MAXDATA=nnn
PU:MAXOUT=n
PU:ADDR=xx
GROUP:NZRI=(NO)YES
GROUP:DUPLEX=(FULL)HALF
LU:LOCADDR=nnn
where n represents decimal numbers and x, y, z are hexadecimal digits
From your IBM host system administrator, request:
An LU:LOCADDR value from the IBM host VTAM definitions for each of the 3270 and 3770 sessions allowed on the workstation. LU:LOC values are three-digit numbers.
The type of each 3270 and 3770 session. The type is either TERMINAL (for 3270 terminal sessions), 3770 (for 3770 LU sessions), or PRINTER (for 3270 printer sessions).
From your 3174 system administrator, request some of the 3174 Local Controller configuration values specified during 3174 customization. You need one set of values for each of your token ring boards. The values that you need were given during 3174 customization in response to these questions:
Question 900: Token-Ring Network Address for the Gateway
The value required is the token ring address of the token ring controller PU— the 3174 controller itself. It is 12 hexadecimal digits.
Question 940: Ring Address Assignment
The value required is the token ring address of the downstream PU (DSPU) assigned to the IRIS SNA SERVER. It is 12 hexadecimal digits.
Question 941: Ring Transmission Definition
Two values specified in this question are required: the maximum
I-Frame size and the maximum window size of the DSPU assigned to the IRIS SNA SERVER. (These values are conceptually equivalent to MAXDATA and MAXOUT in the VTAM definition.) Possible values of the maximum I-Frame size are 265, 521, 1033, 2042, 4105, and 8201. Possible values of the maximum window size are 1, 2, 4, and 7.
From your IBM host system administrator, request the following VTAM information about the 3172:
PU:MACADDR=xxxxxxxxxxxx
PU:SAPADDR=n
From you IBM host system administrator, request the following VTAM information about the PU definition for the workstation:
PU:MAXDATA=nnnn
PU:MAXOUT=n
PU:IDBLK=xxx
PU:IDNUM=yyyyy
PATH:DIALNO=xxyyzzzzzzzzzzzz
LU:LOCADDR=nnn
where n represents decimal numbers and x, y, z are hexadecimal digits
From your IBM host system administrator, request the following NCP information about the LINE definition for the NCP:
LINE:LOCADD=xxxxxxxxxxxx
From your IBM host system administrator, request the following VTAM information about the PU definition for the workstation:
PU:MAXDATA=nnnn
PU:MAXOUT=n
PU:IDBLK=xxx
PU:IDNUM=yyyyy
PATH:DIALNO=xxyyzzzzzzzzzzzz
LU:LOCADDR=nnn
where n represents decimal numbers and x, y, z are hexadecimal digits
In addition to the information described above, the following information is required for each LU:
LLU_Name
The name of the LU for the LU:LOCADDR as defined in VTAM.
Mode_Name
LU:DLOGMOD=<name>
CICS definition
DFHTCT NETNAME=<lu_name>
where <lu_name> matches the LLU_Name.
DFHTCT MODENAME=<mode_name>
where <mode_name> matches the Mode_Name.
DFHTCT FEATURE=SINGLE(PARALLEL)
DFHTCT MAXSESS=(n,m)
Required only if FEATURE=PARALLEL. n and m are both decimal numbers.
An executable configuration file is a text file that stores parameters for the configuration definition verbs in a way that can be interpreted by the IRIS SNA SERVER executables. The configuration files are stored in the directory
/usr/sna/rsrc.
You configure the IRIS SNA SERVER for your applications through your selection of a configuration file. You can either create this file or select one of the sample files provided by Silicon Graphics.
When the main window of the IRIS SNA SERVER's graphical user interface IRIS SNAView is first displayed (see Figure 3-1), the cursor is positioned in the Configuration field.
Enter the configuration file name at the keyboard and press <Return>.
This action assumes that you know the name of the configuration file in the /usr/sna/rsrc directory that you want to use.
or
Select one of the files from the File pull-down menu in the menu bar. To select a file, select “Open” in the File menu and click the right mouse button. The dialog box shown in Figure 3-1 is displayed.
Move the mouse cursor and select the configuration file from the menu listing. Press the OK button to select this file as the current configuration file. (You can also press Cancel to return to the main window or press Help for additional information.) The configuration file name is displayed in the Configuration text box of the Information Panel.
 | Note: The currently selected configuration file (the file name that appears in the Configuration field) is automatically loaded whenever you restart the system. |
Executable configuration files used by IRIS SNAView have file names without suffixes. Configuration resources files with suffixes are used by the VT100 configuration tools, not IRIS SNAView. See the IRIS SNA SERVER VT100 Interface Guide for a description of these VT100 configuration files.
Silicon Graphics-supplied configuration files whose names begin with sna or contain 3270 are associated with 3270/3770 host configurations. Those with an lu or a 62 as part of their name are associated with LU 6.2 host or LU 6.2 Peer-to-Peer configurations.
The configuration file that you select depends on the type of connection and whether you are using the SDLC or token ring configuration. Although both types of communication boards can be installed in the same workstation, the sample files available from Silicon Graphics, which are listed in are exclusive to either token ring or SDLC for the 3270/3770 and LU 6.2 hosts.
Configuration SDLC Token Ring
3270/3770 sna3270 tr3270[1]
sna3770
sna3270l tr3270l[2]
LU 6.2 Host lu62host
LU 6.2 Peer sdlc62p tr62p
sdlc62s tr62s
lu62loop
Sample Configuration Files Associated with SDLC or Token Ring
The device that you select must be appropriate for the configuration file as shown in Table 3-1. For example, if you select sna3270 as the configuration file for a 3270/3770 host configuration, you must select the SDLC device. (If you select a token ring configuration, an error message is displayed.)
To select the SDLC device, press the SDLC1 radio button in the Device Selection area of the Configuration Panel (see Figure 3-1 for the location of this area). This message is displayed in the message line section of the Information Panel:
SDLC 1 is selected in the current configuration. |
SDLC1 is the first SDLC configuration. Four different SDLC configurations are possible. One system can have up to two SDLC communication boards, each having two ports. Board 0 is associated with SDLC1 and SDLC2. Board 1 is associated with SDLC3 and SDLC4.
For a token ring configuration, press the T/R1 radio button in the Device Selection area of the Configuration Panel. (Figure 3-1 shows this button after selection.) When you select a configuration file, the token ring node name and the appropriate Line and Gateway are automatically chosen. (The Gateway is your current local workstation name and cannot be changed.) The token ring node name, which appears in the text box, is the same as the adjacent link station (and is displayed in the Adj Link Station text box in the Operation Panel).
This section describes configuration procedures for the 3270 IBM data communications protocol that provides communication between a dumb terminal and an IBM mainframe computer and 3770 Remote Job Entry emulation. First, you will collect the necessary VTAM host information as described in Section , “Collecting Host Information for 3270/3770 and LU 6.2 Host Connection,” then use the 3270/3770 Host Configuration window and its related dialog boxes to set the configuration parameters. The sequence of windows and the dialog box that you will access is shown in Figure 3-2.
| Note: All of the dialog boxes have the Apply, Cancel, and Help buttons across the bottom of the window. Press Apply to accept the information you have entered in the dialog box and to return to the previous window/dialog box. Press Cancel to negate the information and to return to the previous window/dialog box. Press Help to receive help information about the dialog box. |
To configure the IRIS SNA SERVER for the 3270/3770 host connection, use the 3270/3770 Host Configuration window to:
Select the connection type
Select the link type
Enter device-specific information
Define the Physical Unit
Define the number of Logic Units
Figure 3-3 shows the 3270/3770 Host Connection Configuration window, which is displayed when you press the 3270/3770 Host button in the Configuration Panel of the IRIS SNAView main window.
Instructions for entering the configuration information in the window follow.
| Note: You can create a dual-purpose configuration file for both 3270/3770 and LU 6.2 host connections. After completing the 3270/3770 Host Connection Configuration window, press the LU 6.2 Host configuration type button and complete its Connection Configuration window. |
To define a new configuration, follow these steps, which are described in detail below:
Select the connection type
Select the link type
Enter SDLC-specific information (if appropriate)
Enter Token Ring-specific information (if appropriate)
Define the PU
Define the LU
Three radio buttons at the top left-side of the window indicate the type of physical equipment used as a connection:
Leased Line for point-to-point cable connection
Dial Line for a dial-up telephone synchronous modem connection
LAN for a token ring connection
Select the appropriate connection. Leased Line is the default.
Three radio button at the top right of the widow represent the link types: Primary, Secondary, and Negotiable (the default). They indicate which link station (this workstation or the ring station at the other end of a connection) assumes the primary link station role or secondary link station role, or if the link type is negotiable.
Select the appropriate link type.
If you are using the SDLC communications, enter the following information in the SDLC-specific area of the window:
Auto dial
| Note: This parameter is ignored if the connection type is not Dial Line. |
Specifies the protocol that controls a modem's dialer function.
Press the Manual radio button if you intend to dial yourself (this is the default). A Define Phone Number dialog box is displayed. Enter the three-digit area code and tab over to the next field. Enter the first three digits of the phone number, press <Tab>, and enter the last five digits. If you enter this field incorrectly, an error message is displayed.
Press the Synchronous Auto Dial Language (SADL) radio button for automatic system dialing (if the modem at the other end also supports SADL).
Encoding
Indicates method of transmission coding, which must match that on the other end of the line. Press either the non-return on zero (NRZ) or non-return on zero inverted (NRZI) radio button. NRZI is the default.
If the VTAM definition is GROUP:NRZI=YES, press NRZI. If it is NO, press NRZ.
Duplex
Indicates the send and receive protocol. In half-duplex mode, send and receive requests cannot be transmitted simultaneously (as they can in full-duplex mode). Press the full- or half-duplex radio button as appropriate. Full-duplex mode is the default.
If the VTAM definition is GROUP:DUPLEX=FULL, press the full-duplex button. If DUPLEX=HALF, press the half-duplex button.
If you are using token ring, enter the following information in the token ring-specific area of the window:
Remote MAC_Addr
The token ring protocol remote MAC addresses. Enter 12 hexadecimal characters for each. Obtain this information for these controllers from the following sources:
3174 Controller
See Question 900 in“Token Ring through the 3174 Controller” in Section .
3172 Controller
PU:MAXADDR=xxxxxxxxxxxx
3745 Controller
NCP definition LINE:LOCADD=xxxxxxxxxxxx
See the section on MAC Addressing in the Token Ring Administration Guide for additional information.
Remote Sap_Addr
The remote Sap address, which is used for token ring protocol, is needed for token ring protocol. For the 3174 and 3745 controllers, the value is always 4. For the 3172 controller the PU:SAPADDR=n.
Local Sap_Addr
The local Sap address, which is used for token ring protocol, has valid values ranging from 4 to 254 divisible by 4, or the value 5. The default is 4. The Local Sap_Addr of the local station should match that of the Remote Sap_Addr at the remote station.
The value for 3174 controller is always 4. For the 3172 or 3745 controllers, the value is yy of PATH:DIALNO=xxyyzzzzzzzzzzzz. (Convert the hexadecimal value yy to a decimal number.)
Local GRP_Addr (Optional)
The local group address consists of up to 12 hexadecimal characters. Consult with your system programmer regarding this address.
Enter this information in the PU Definitions area of the window to define the Physical Unit:
Local XID
Identifies the local node to the partner during link establishment.
The number consists of eight hexadecimal characters without embedded blanks. After entering the first three characters, press <Tab> to advance to the next text box. Enter the last five characters and press <Return>.
The value for the various configurations follows:
SDLC Leased Line
Not used.
SDLC Dial Line
PU:IDBLK=xxx
PU:IDNUM=yyyyy
TR 3174
Not used.
TR 3172 and TR 3745
PU:IDBLK=xxx
PU:IDNUM=yyyyy
Address
The PU default value, which is significant for SDLC connections only where PU:ADDR=xx. (C1 is the value for token ring connections.)
Max Data
Indicates the maximum basic transmission unit (BTU) length that can be sent and received on the line. Enter valid values of either 265 (the default), 1033, 2057, 3849, or 4105.
The value for TR 3174 can be obtained from Question 941(see “Token Ring through the 3174 Controller” in Section , “Collecting Host Information for 3270/3770 and LU 6.2 Host Connection.”
The value for the other configurations is nnn in PU:MAXDATA=nnn.
Max Out
Indicates the maximum number of frames that can be sent or received before acknowledgment is required. Enter a value in the range of 1 to 7 (the default is 7).
The value for TR 3174 can be obtained from Question 941(see “Token Ring through the 3174 Controller” in Section , “Collecting Host Information for 3270/3770 and LU 6.2 Host Connection.”
The value for the other configurations is n in PU:MAXOUT=n.
Defining LUs is simplified by the Use Default check box (the default), which provides appropriate defaults for your configuration. If you do not wish to define LUs, accept this default setting, which follows these conventions:
| Note: The default number of LUs is four. If you want to use a different number, enter this amount in the Number of LUs text entry box. |
To define your own LUs, follow these steps:
Enter the number of LUs (a maximum of 254) for the current configuration in the Number of LUs text box.
Click on the Use Default check box until the box is empty.
The check box toggles between using the defaults (on) and not using them (off).
The Please Wait message appears on the screen before the Define LU dialog box is displayed (see Figure 3-4).
Enter the LU names (a maximum of 254) in the Name text box.
Enter the LU address (1 to 254).
Select the 3270/3770 Host connection type, either Terminal (the default) or Non-Terminal (for printers or the 3770) radio button.
Press the Apply button to record the changes. Press Cancel to negate the changes. Press Help to receive help information about defining LUs.
| Note: These configuration procedures are necessary only if you want to generate a new configuration. Otherwise, use one of the existing configuration files and select the communications device (token ring or SDLC) only. |
This configuration is for interprocess communication services within peer-to-peer environments. Communication takes place between two programs, one running locally and one running remotely on a partner workstation, or even on the same local workstation.
To configure the IRIS SNA SERVER for an LU 6.2 Peer-to-Peer Connection, follow the steps listed below. The configuration parameters used on this end of the peer-to-peer connection should match those used on the other end of the connection. (In this guide, unless specified otherwise, match means use the same values.) The sequence of windows and dialog boxes that you may access is shown in Figure 3-5.
Select the configuration file as described in “Selecting the Configuration File”.
Press the LU 6.2 Peer button (border is highlighted) in the Configuration Panel of the IRIS SNAView main window. The LU 6.2 Peer-to-Peer Connection Configuration window shown in Figure 3-6 is displayed.
Use the LU 6.2 Peer-to-Peer Connection Configuration window to:
Select the connection type
Select the link type
Enter device-specific information
Define the PU
Define LUs
Enter the configuration information in the window by following the instructions given below.
The fields in this window are almost identical to those in the 3270/3770 Host Connection Configuration window. The Other Properties... button at the bottom of the window, however, is not grayed out. After defining the LUs, you can set advanced properties for peer-to-peer connections, although they are not required.
To define a new configuration, follow these steps, which are described in detail below:
Select the connection type
Select the link type
Enter SDLC-specific information (if appropriate)
Enter token ring-specific information (if appropriate)
Define the PU
Define the LU
Define partners
Define mode
Define transaction program resources
Define other properties-TP (optional)
Set LU security (optional)
Define other properties-Peer-to-Peer (optional)
Three radio buttons at the top left of the window indicate the type of physical equipment used as a connection:
Leased Line for point-to-point cable connection
Dial Line for a dial-up telephone synchronous modem connection
LAN for a token ring connection
Select the appropriate connection. Leased Line is the default.
Three radio buttons at the top right of the window represent the link types: Primary, Secondary, and Negotiable (the default). They indicate which link station (this workstation or the ring station at the other end of a connection) assumes the primary link station role or secondary link station role, or if the link type is negotiable.
Select the appropriate link type.
| Note: If one side of the connection is specified as Primary, the other side cannot also be specified as Primary; it must be Secondary or Negotiable. Likewise, if one side of the connection is specified as Secondary, the other side cannot also be specified as Secondary; it must be Primary or Negotiable. |
If you are using the SDLC communications, enter the SDLC-specific information related to these items:
Auto dial
| Note: This parameter is ignored if the connection type is not Dial Line. |
Specifies the protocol that controls a modem's dialer function. Press the Manual radio button if you intend to dial yourself (this is the default). A Define Phone Number dialog box is displayed. Enter the three-digit area code and tab over to the next field. Enter the first three digits of the phone number, press <Tab>, and enter the last five digits. If you enter this field incorrectly, an error message is displayed.
Press the SADL radio button for automatic system dialing (the modem at the other end must also support SADL).
Encoding
Indicates method of transmission coding, which must match that on the other end of the line. Press either the non-return on zero (NRZ) or non-return on zero inverted (NRZI) radio button (the default). You must specify the same setting at both ends of a connection.
Duplex
Indicates the send and receive protocol. In half-duplex mode, send and receive requests cannot be transmitted simultaneously (as they can in full-duplex mode). Press the full- or half-duplex radio button as appropriate. Full-duplex mode is the default.You must specify the same setting at both ends of a connection.
If you are using token ring, enter the following information in the token ring- specific area of the window:
Remote MAC_Addr
The token ring protocol remote MAC addresses. Enter 12 hexadecimal characters for this address. See the section on MAC Addressing in the Token Ring Administration Guide for additional information.
Remote Sap_Addr
The remote Sap address used for token ring protocol. Valid values range from 4 to 252 mod 4, or the value 5. The default is 4. The Remote Sap_Addr of the local station should match the Local Sap_Addr of the remote station.
Local Sap_Addr
The local Sap address, which is used for token ring protocol, has valid values ranging from 4 to 254 divisible by 4, or the value 5. The default is 4. The Local Sap_Addr of the local station should match that of the Remote Sap_Addr at the remote station.
Local GRP_Addr
The local group address consists of up to 12 hexadecimal characters. Consult with your system programmer regarding this address.
Enter this information in the PU Definitions area of the window to define the PU.
Remote XID
Identifies the partner to the local node if it is a peer and is received by the local node from its partner during link establishment. Request this number from the system administrator at the remote site. The Remote XID defined at the local station should match the Local XID defined at the remote station.
The number consists of eight hexadecimal characters without embedded blanks. After entering the first three characters, press <Tab> to advance to the next text box. Enter the last five characters and press <Return>.
Local XID
The exchange ID, sent from this node to the partner, identifies the local node to the partner in an XID exchange at link establishment. Request this number from the system administrator at the local site. The Local XID defined at the local station should match the Remote XID defined at the remote station.
The number consists of eight hexadecimal characters without embedded blanks. After entering the first three characters, press <Tab> to advance to the next text box. Enter the last five characters and press <Return>.
Address
The PU default value, which is decided by the local station (usually C1).
Max Data
Indicates the maximum basic transmission unit (BTU) length that can be sent and received on the line. Enter valid values of either 265 (the default), 521, 1033, 2057, 3849, or 4105.
Max Out
Indicates the maximum number of frames that can be sent or received before acknowledgment is required. Enter a value in the range of 1 to 7 (the default is 7).
Defining LUs is simplified by the Use Default check box (the default), which provides appropriate defaults for your configuration. If you do not wish to define LUs, accept this default setting, which follows these conventions:
All of the LU names have the form LUi and an address equal to i (where i ranges from 1 to 254). For example LU1 has the address 1; LU2 has the address 2; LU3 has the address 3, and so forth.
All remote LU names have the form RLUi
All transaction program names have the form TPi.
All mode names have the form Modei.
| Note: The default number of LUs is four. If you want to use a different number, enter this amount in the Number of LUs text entry box. |
To define your own LUs, follow these steps:
Enter the number of LUs (a maximum of 254) for the current link connection in the Number of LUs text box.
Click on the Use Default check box until the box is empty.
The check box toggles between using the defaults (on) and not using them (off).
The Please Wait message appears on the screen before the Define LU dialog box is displayed (see Figure 3-7).
Enter the LU names in the Name text box (it should match the partner name at the peer configuration).
Enter the LU address (1 to 254).
Enter the number of partners.
This is the maximum number of partners for an LU; the values range from 1 (the default) to 154.
Press the Define Partner? radio button to display the Define Partner dialog box shown in Figure 3-8. Follow these steps to define the partner resources:
Enter the partner's name in the Name text box.
The partner's name should be the LU Name of the peer configuration.
Enter the LU 6.2 mode name in the Mode Name text box (up to eight ASCII characters).
The transaction programs (TPs) use this name to identify the mode when requesting conversations. The name consists of up to eight ASCII characters (no embedded blanks). Use the same mode name at the peer configuration.
Enter the number of TPs.
The values range from 1 (the default) to 255. Reserve one for the architected CNOS service transaction program (s2_cnos) if parallel sessions are supported.
Select the Parallel? check box to indicate if the session is parallel. If the session is not parallel, leave the check box empty.
Parallel is the default.
Define the Mode.
You can either accept the default mode settings or define your own as described in “Defining the Mode” below.
The Define Mode dialog box is shown in Figure 3-9.
Complete the information listed in the Other Properties (Mode) dialog box by following these steps:
Enter the Send Pacing Count , which regulates the message unit transmission rate of the component.
The Send Pacing Count is the Receive Pacing Count of the peer configuration. Values range from 0 to 21; the default is 7.
Enter the Receive Pacing Count , which regulates the message unit transmission rate of the receiving component.
The Receive Packing Count is the Send Pacing Count of the peer configuration. Values range from 0 to 21. The default is 7.
Enter the Maximum RU Length (size), which is the highest limit that an RU can have before it segments.
The limit is agreed upon with the partner. Values range from 256 to 4096. The default is 1024.
Enter the Minimum RU Length, or size, which is the low-end range of the maximum RU size (the high-end range) agreed upon with the partner.
Values are 8 to 256. The default is 256.
Enter the Maximum Sessions , which indicates the maximum possible number of simultaneously active sessions.
Values range from 1 to 254. The value must be 1 if parallel sessions are not supported. The default is 6.
Define the Minimum First Speaker, which is the minimum number of sessions in which the local LU is the contention winner.
Values are from 0 to 254, but cannot be greater than the value for maximum sessions and cannot be greater than the number of Maximum Sessions minus the number of Minimum First Speaker of the peer configuration. The default is 3.
Define the number of Auto-initiated Sessions.
This value states the minimum number of sessions automatically started when session limits are initialized. Values range from 0 to 254, but cannot exceed the number of first-speaker sessions. The default
is 3.
Indicate whether there is a Blank Mode Name.
If it is blank, no name is sent to the partner, and any name received is accepted. Only one blank mode can be specified for a remote LU. Select the check box to indicate Yes. The default is No (check box empty).
Enter the LU-LU password in hexadecimal characters (up to 16). This value is optional.
Check whether or not to Initiate Type.
This value specifies whether or not the host can queue an initiation request if the intended partner is unable to start a session (for host-controlled environments only). Yes (check box filled in) is the default.
Define the Network Qualifier name (optional).
This is the extension of the network name used in cross-network communications to ensure the uniqueness of the network name. It consists of up to eight ASCII characters.
Check whether or not conversation-allocated requests are queued (Queued Binds text box).
Session activation requests are queued at the remote site. The default is Yes (check box filled in).
Indicate the level of security accepted by the remote LU.
The security options are None (the default), User ID/Passwd, and Verified. If you select User ID/Passwd, a dialog box requesting that you enter the User ID and Password is displayed.
Press the appropriate radio button to indicate who has responsibility for session re-initiation after an abnormal session termination.
The options are Either (the default), Operator, Primary LU, and Secondary LU. This parameter applies only to non-parallel sessions.
Press the appropriate button to Apply the data or to Cancel the entries.
Select the Define TP? check box to define the transaction program resources for LU 6.2 applications.
To define transaction program resources, complete the following information in the Define TP dialog box, as shown in Figure 3-10.
In the Name text box enter the name of the transaction program (up to eight ASCII characters without embedded blanks).
This name is defined in the configuration file. A second definition is an asterisk (*), which indicates any transaction program is acceptable.
You can change the default values if you want. If you do not wish to define an optional set of advanced resources for the transaction program, press the Apply button.
To define advanced features, select the Other Properties check box.
The Other Properties (TP) dialog box shown in Figure 3-11 is displayed. Set the following fields:
Select the PIP data check box if Program Initialization Parameter (PIP) is supported.
PIP data is supported if the check box is filled in (the default). In this case, the program can use PIP data, although it is not required to do so. If the box is empty, this program cannot receive or send PIP data (such as command-line arguments).
Select the Data Mapping check box if Data Mapping is supported (box filled in). The default is Not Supported.
Define whether the program supports Function Management Header (FMH) data. The default is Not Supported (check box empty).
Assign LUW, which states whether the program allows generation of a Logical Unit of Work (LUW). The default is No (box empty).
Define the Sync Level , which states whether the program supports sync level CNFRM.
If the check box is filled in, the value is CNFRM (the default), and the program can issue CONFIRM and CONFIRMED. If it is empty, those verbs are not allowed.
Mapped specifies access to mapped verbs. Basic specifies access to basic verbs. Either specifies access to both.
Define the Privilege value, which specifies the type of control operator verbs that the transaction program can issue. Valid values are None, CNOS, SESS, DEFN, DISP, SRVC, or none (no check box selected).
Press the Apply button to accept the values you have chosen. When you are returned to the Define TP dialog box, press Apply, which returns you to the Define Partner dialog box.
Press the Apply button to record the changes. Press Cancel to negate the changes. Press Help to receive help information about defining TPs.
To specify the level of security accepted by the remote LU, set LU security parameters by following these steps:
Press the Other Properties... button in the Define LU dialog box.
The Other Properties (LU - LU 6.2/Peer-to-Peer) dialog box shown in Figure 3-12 is displayed.
Enter the Network Qualifier in the text entry box.
Enter the User ID (eight ASCII characters) for the person authorized to access programs at this LU.
Enter the password of the user specified in User ID (eight ASCII characters).
Enter the Profile name for the user specified in User ID (eight ASCII characters).
Press the Apply button to record the changes. Press Cancel to negate the changes. Press Help to receive help information.
Next, advanced properties can be set if you do not want to use the default values. Press the Other Properties... button at the bottom of the LU 6.2 Peer-to-Peer Connection window to display the Other Properties dialog box, which is shown in Figure 3-13. Follow these steps to complete the peer-to-peer configuration.
Press the transmission rate radio button that applies: DCE for Data Communications Equipment (the default) or Non-DCE.
Enter the Idle Count time in milliseconds.
This value specifies the maximum time allowed from poll to response.
The valid range is from 100 to 1000; the default is 800.
Enter the maximum number of frames to be sent or received before acknowledgment is required in the Max I-Frame text entry box.
The range is from 1 to 7 (the default).
Enter the maximum number of times the IRIS SNA SERVER should re-transmit the connection in case of error in the Max Retry text entry box.
The value range is from 0 to 30; the default is 3.
Enter the maximum allowed time for non-productive receive or transmit in the Non-Prod Timeout text entry box.
The valid range is from 1000 to 3000 (in milliseconds); the default is 1000.
Press the Apply button to set these properties. Press Cancel to nullify them. Press Help for additional information.
| Note: These configuration procedures are necessary only if you want to generate a new configuration. Otherwise, use one of the existing configuration files and select the communications device (token ring or SDLC) only. |
To configure the server for an LU 6.2 host connection, first collect the necessary IBM host information as described in Section , “Collecting Host Information for 3270/3770 and LU 6.2 Host Connection,” and Section , “Additional Information for the LU 6.2 Host Connection,” then follow the steps given in Section , “Configuring the Server for the 3270/3770 Host Connection,” except those for defining LUs. Instead of defining 3270/3770 LUs, you need to define Local LU, Mode, and Transaction Programs for an LU 6.2 host connection.
Instructions for defining LUs for the LU 6.2 host connection follow. See Figure 3-14 for an overview of this configuration procedure.
| Note: You may use the default values for other properties of LUs that are not discussed below. If, however, you want to define other properties, such as modes, partners, or LU 6.2 transaction program resources, refer to Section , “Configuring the Server for an LU 6.2 Peer-to-Peer Connection.” |
You may also create a dual-purpose configuration file for both and LU 6.2 and 3270/3770 host connections. After completing the LU 6.2 Host Connection Configuration window, press the
3270/3770 Host configuration type button and complete its Connection Configuration window.
In the LU 6.2 Host Connection window, enter the number of LUs for the current link connection in the Number of LUs text box. Select the User Defaults check box by clicking on it until it is filled in, which displays the Define LU dialog box shown in Figure 3-7.
Enter the following information in the text entry boxes:
The LU name (same as LLU_Name).
LU address as defined in LU:LUCADDR for the LU 6.2 LU.
Then click on the Define Partners? check box in the Define LU dialog box, which displays the Define Partners dialog box shown in Figure 3-15.
Complete the Define Partners dialog box as follows:
Enter the mode name as defined in LU:DLOGMOD in the text entry box.
If DFHTCT FEATURE=SINGLE, the configuration is set. Go to
Step 6.
If FEATURE=PARALLEL, select the Define Mode? check box, which displays the Other Properties (Mode) dialog box shown in
Figure 3-9.
In the Maximum Session text entry box, enter the number n from DFHTCT MAXSESS=(n,m).
In the Minimum First Speaker text entry box, enter the number m from DFHTCT MAXSESS=(n,m).
Press the Apply button to return to the Define LU dialog box. Press Apply from this dialog box to return to the LU 6.2 Host Connection window. Press Apply again to return to the IRIS SNAView main window.
Select the File pull-down menu and save the file as described in Chapter 2.
Before starting SNA applications, you need to create a new configuration and activate the server. Since the procedure for doing this through the graphical user interface is similar for all configurations, follow these steps using the tr3270 configuration file as a guide. (As shown in Table 3-1, tr3270 is a Silicon Graphics-supplied 3270/3770 host configuration file that uses the token ring communications device.)
| Note: In the following steps, the only difference between using tr3270 and sna3270 as the configuration file is the device. tr3270 is for token ring; sna3270 is for SDLC. |
As superuser, start IRIS SNAView. After the main window is displayed, select “Open” from the File pull-down menu.
The Open Config File dialog box is displayed.
Move the mouse cursor to tr3270 under Conf File and click on the right mouse button to select it. Press the OK button.
As shown inFigure 3-16, the Configuration file text box now displays tr3270. The Line is sna3270 and the Gateway is your local workstation name. The Information Panel displays:
TR 1 is selected in current config |
The four text display windows show the first item in the Adjacent Link Station for each token ring. SNA 3270 is displayed in the device selection text display window and in the Adj Link Station text display window.
Move the pointer to the IRIS SNA SERVER Configuration Panel.
Select TR/1, which is the only option (the others are dimmed and therefore unselectable).
Press the 3270/3770 Host button, which displays the 3270/3770 Host Connection Configuration window shown in Figure 3-17.
| Note: Incorrect server configurations are not allowed. In this example, clicking any other configuration button than 3270/3770 Host displays a warning message. You are requested to select the correct configuration. |
In the LU Definition section (lower right-hand area of window),
change the Number of LUs to 4. Directly below, select the Use Defaults check box, which is usually filled in (the default).
| Note: If you do not want to change any of the LU definitions in subsequent configuration settings, click on the Use Defaults check box until it is filled in. When the box is filled, you do not have to define anything. |
The Define LU dialog box is displayed (see Figure 3-18).
The four LUs range from SLU01-SLU04 with addresses of 1 to 4, respectively. All are of the type Terminal.
Change the second LU name from SLU02 to MYLU02 by selecting the text window. Edit the field, replacing SLU02 with MYLU02. Press <Return>. Press the Apply button, which makes your change permanent and closes the dialog box. The number of LUs in the Connection window is now 4.
Press the Apply button in the 3270/3770 Host Configuration window to make the changes you requested. The window disappears and you return to the main window.
From the pull-down File menu in the SNAView main window, select
“Save As...”. Select a specific file and press the OK button. Press Quit.
Saving the configuration enables you to use the new configuration file when you restart the IRIS SNA SERVER.
After creating this sample configuration, you should able to make the necessary modifications for creating another configuration. To simplify your task, use one of the supplied configuration files and modify it accordingly. To display the existing configuration files, select “Open” from the File pull-down menu.
The next step is to activate the IRIS SNA SERVER. See the instructions given for this tutorial example in , Section , “Activating the IRIS SNA SERVER: A Tutorial.”