This chapter first describes the menu options of the IRIS SNA SERVER. It is intended more as a reference guide than a tutorial. Four menus are presented in this chapter:
Network Operations Menu
Configuration Menu
Define Resource Menu
Logging and Trace Menu
Each menu is shown as it appears, and its options and specific parameters are described in detail. When a selected option regards a node operator or configuration verb, the name of that verb is provided (for more information on each verb, refer to the IRIS SNA SERVER Programming Guide, Chapter 2, “Programming with the SNA SERVER Verbs”). The first part of the chapter concludes with a description of the core programs, which contain information for creating your own control scripts
The last part of the chapter provides instructions for running the network configuration program and for running the network operations program for both SDLC and token ring connections.
To access to the IRIS SNA SERVER menus from a VT100 terminal with the IRIS SNA SERVER software product installed, enter the following command line at the IRIX™ prompt:
/usr/sna/etc/menu-name |
where menu-name is:
 | Note: You must load the SDLC code every time the IRIX system is rebooted. To load SDLC, enter at the IRIX prompt: |
/usr/sna/etc/ldSDLCn |
where n is either 0 or 1, depending on whether you are using Controller 0 or 1.
The Network Operations Menu is accessed by entering at the shell prompt:
/usr/sna/etc/netOper |
which displays the menu shown in Figure 2-1.
The Network Operations Menu options activate the node processes, start and stop links, and call the Logging and Trace Menu. This menu functions on the default configuration specified in option [d] Set Current Configuration of the Configuration Menu. (When controlling a number of configurations, use option [f] of the Network Operations Menu to change the default.)
A “message(s) waiting” comment displayed in the middle of the screen indicates that a node operator message was generated. To see it, select option [h] Display Messages.
| Note: Many of the line activation/deactivation events are asynchronous. It is critical, therefore, that you display all messages to find out the true outcome of your request. |
This option activates the default configuration, initializes the environment, and starts the SNA background processes (s2_schd). Whenever this option is selected, a confirmation is requested. The response message either indicates that the node processes are already active, or confirms that the command to activate the server was accepted.
This option activates the physical unit (PU), which logically opens SNA for operations. Be sure the IRIS SNA SERVER is active, however, before starting the PU. Other requests issued prior to activating the PU are queued until the PU is activated.
A message confirms that the command was accepted. If it was not accepted, major and minor return codes are displayed (specific return code information is contained in Appendix B, “Major and Minor Return Codes,” of the IRIS SNA SERVER Administration Guide). Use option [h] Display Messages, to see the results of this command.
This option activates a specific logical unit (LU) and makes it available to LU 6.2 application programs. Programs cannot attach to the local LU until it is activated. If the PU is not active, the LU activation is queued. On host connection, LU activation is performed by the hosts; thus, this type of local LU cannot be activated locally.
Enter the name of a local LU defined in the current configuration. A message confirms that the command was accepted. If it was not accepted, major and minor return codes are displayed (specific return code information is contained in Appendix B, “Major and Minor Return Codes,” of the IRIS SNA SERVER Administration Guide). Use option [h] Display Messages, to see the results of this command.
This option prepares the physical device specified in the line definition for communications. The PU and LU that use this line must already be active. For a line configured as a leased connection, this option establishes the communications link. If the line is configured as multipoint (switched), this option prepares the device, but does not establish the connection. To make the connection, activate the adjacent link station (see option [e]), since a number of remote stations can be defined for the same switched or multipoint line.
Enter the line name that corresponds to the one defined in the current configuration. An accepted command is confirmed by a message. If the command is unacceptable, major and minor return codes are displayed (specific return code information is contained in Appendix B, “Major and Minor Return Codes,” of the IRIS SNA SERVER Administration Guide). Use option [h] Display Messages, to see the message.
This option issues the actline node operator verb.
This option activates a specific adjacent link station of a multipoint or switched line (leased lines do not use this option). Specify whether the station is to be connected (so you can dial out to the station) or enabled (so the station can dial in to you). A station enabled for dial-in can also be connected for dial-out by reselecting this option; if the call is disconnected, the station remains enabled so that the remote station can call in.
Enter the station name that corresponds to the one defined for a partner in the current configuration. After specifying whether the station is to be connected or enabled, a message confirms that the command was accepted. If it was not, major and minor return codes are displayed (specific return code information is contained in Appendix B, “Major and Minor Return Codes,” of the IRIS SNA SERVER Administration Guide). Use option [h] Display Messages, to see the results of this command.
A successful connection causes the message station [name] successfully contacted to appear. No message means the connection has not been made. This option issues the actsta node operator verb.
This option runs a control script, a file that contains activation or deactivation commands issued on a routine basis. With a control script, you run a single file rather than separate commands. (For more information on creating control scripts, see , “Core Programs,” on core programs s2_mscp or s2_lgcp.)
This option displays node operator messages. After a message is displayed, it is removed from the operator-message queue. Copies of messages are placed in the system log (if it is active) for reference. Occasionally, when the operator's queue is full, messages are discarded on a first-in/first-out basis, and a message-queue-overflow comment is placed in the queue and in the system log. Operator messages are also placed in the system log. If the log was running at the time of the overflow, the overflow message is still visible; otherwise, it is lost.
Use this option whenever you receive an indication that messages are waiting. Many of the line activation/deactivation events are asynchronous, so it is important to display messages to find out the true outcome of your request.
This option presents the Logging and Trace Menu. It controls and displays the output of the logging or link trace features of the SNA network. Both features are useful in problem isolation and problem solving.
This option presents a Display Station Status screen that shows the status of the lines, partners, and sessions for the current configuration.
This option displays a Display Host Status screen that shows the status of LUs attached to the host control point. It also shows session IDs and the IDs of the programs allocating the LU.
This option deactivates a particular adjacent link station of a multipoint or switched line (if the line is leased, ignore this option).
Enter the station name that corresponds to the one defined for a partner in the current configuration. Use option [h] Display Messages, to see the results of this command.
When the connection is established, the message station [name] successfully disconnected shows. If this message does not appear, the disconnection has not been made. This option issues the dctsta node operator verb.
This option deactivates a specific line and causes an orderly take-down of the connection.
This option also clears any pending activation request; for example, one that may have remained to a non-enabled partner. Any session using a deactivated line is terminated.
Enter the line name of an active line. If the name is accepted, a confirmation message appears. If not accepted, a major and minor return code is displayed (see Appendix B, “Major and Minor Return Codes,” in the IRIS SNA SERVER Administration Guide). Use option [h] Display Messages to see the results of this command. This option issues the dctline node operator verb.
This option deactivates a specific LU and abnormally terminates all sessions with that LU. Programs that were using the sessions will receive errors on subsequent conversation verb calls that indicate session failure.
The LU name entered must be that of an active local LU. A message confirms that the command was accepted. If the command was not accepted, major and minor return codes are displayed (specific return code information is contained in Appendix B, “Major and Minor Return Codes,” in the IRIS SNA SERVER Administration Guide). Use option [h] Display Messages to see the results of this command. This option issues the dctlu node operator verb.
This option deactivates the PU, which shuts down the operations of the SNA configuration without actually terminating the background process. All open communications devices are closed (causing abnormal line terminations) and all local LUs are deactivated. Display messages and logging remain active, but you cannot display station status. A confirmation message indicates that the command was accepted. Use option [h] Display Messages to see the results of this command.
This option terminates the IRIS SNA SERVER processes, closes any open communications devices, and deactivates the default configuration. You are asked to confirm that this is what you really want to do.
If the IRIS SNA SERVER was active when you issued the deactivation request, a message confirms that the command was accepted. At this point, you can no longer access messages or use the status displays.
| Note: Option [p] is not the preferred way to terminate communications sessions. It abnormally closes the communications lines at the remote site, which sometimes requires manual intervention to reset modems or lines. |
The Network Configuration Menu shown in Figure 2-2 is accessed by entering /usr/sna/etc/netOper at the IRIX prompt.
This menu defines, displays, and generates SNA configurations. You can have many different configurations, each defining a particular remote system, or you can have one large configuration that defines all of the remote systems in your network. In either case, the configuration is managed through the options of the Configuration Menu.
All configuration elements available are in the resources directory named in the variable STRSC in the /usr/sna/etc/SNAENV file. The IRIS SNA SERVER is initially installed with sample configurations in the directory /usr/sna/rsrc. Use this directory as your resource directory or use a private set of resources.
This section presents the options of the Configuration Menu.
Before creating a configuration, gather all necessary input information as described in , “Collecting Configuration Data.”
This option displays the Define Resource Menu which defines the discrete network elements or resources and organizes them into configurations.
| Note: Because of the menu's size and importance, the options of the Define Resource Menu are described separately in , “The Define Resource Menu.” |
This option provides information on the components of a specific configuration. When selected, it presents a list of existing configurations. Select a configuration and a screen appears with the information shown in Table 2-1. The LU Name, NetName, Wait, Partner, Rmt LU, Mode, Program, and Network Name fields are applicable only to LU6.2 configurations. The LU and DAF fields are applicable only to LU0-3, which is included as part of the IRIS SNA SERVER.
Table 2-1. Display Configuration Field Information
Field | Description |
|---|---|
Local Node | The name of the local node for this configuration. |
The ID of the local node used in XID exchange at link establishment. | |
Autostart | An option that indicates whether the node process begins when node initialization is complete. |
LU Name | The name of a local LU configured in the selected node configuration. |
NetName | The network name of the LU. If entered, this name must match the remote site's name for the LU. |
Wait | The time-out value for programs attached to this LU. |
Partner | The name of the partner. |
Rmt Node | The name of the remote node for this partner. |
Rmt LU | A remote LU name at the previously specified remote node. |
Mode | The name of the mode under which a session with the preceding partner would run. |
Station | The name of the station used for the session. This name was entered as part of the partner definition. |
Line | The name of the line component used for a session with the preceding partner. |
Type | The connection type of a session between the preceding local LU and partner. The options are preceding local LU and partner. The options are MULTI, LEASED, or SWITCHED. |
Program | The local name for the transaction program. |
Network Name | The network name for the preceding transaction program. |
The name of the secondary LU of LU type 0-3. | |
The LU destination address of the named secondary LU of LU type 0-3. |
Select this option after creating or modifying a configuration with the Define Resource Menu to make the new configuration executable.
Within the resource directory, executable configurations are those files with a .Z suffix. They are generated from the configuration-definition directories, which have an .X suffix.
Choose a configuration from the screen displays list of existing configurations. A Generation Successful message indicates the entry of a valid configuration. The generation takes approximately two minutes.
This option selects the configuration that is controlled by commands issued from this or subsequent menus.
The Define Resource Menu, shown in Figure 2-3, is accessed from the Configuration Menu (option [a]).
The options of the Define Resource Menu add, change, or delete the definition of a particular component within a given configuration. To make these modifications effective, return to the Configuration Menu and select option [c] to generate a configuration and option [d] to establish it as the current working configuration.
More information about this menu see, “Defining Resources.”
Select option [a] through [j] to view the Define Resource Block screen (Figure 2-4). The screen prompts for an action to perform on the resource selected. If you select [a] for Add or [b] for Change, enter the file name of a resource to see a screen of values for that particular resource. Select a field value to alter by entering the letter of the field. This places the cursor on the field line. To delete the field, select [c]. Respond to the prompts for the resource file name and confirmation. All resource definition options work in this way.
| Note: Characters entered are automatically converted to uppercase, the default for all name fields on the configuration screens. |
The following information describes the values for each resource being defined. A detailed explanation of configuration procedures also appears in, “Running the Network Configuration Program.”
This option adds, changes, or deletes a local node definition. It also stores the parameters for the dfnnode verb. Table 2-2 describes these values.
| Note: Configuration parameters that indicate support or non-support of a function accept 1, y, Y, S, or s for SUPPORT and 0, n or N for NON-SUPPORT to accommodate multiple-language environments. |
Table 2-2. Values for the Local Node Option
This option adds, changes, or deletes a remote node definition. It also stores the parameters for the dfncp verb. Table 2-3 describes the values.
Table 2-3. Values for the Define Remote Node Option
Value | Description |
|---|---|
Accept Maint. | This value indicates whether Maintenance Service RUs are Service RUs accepted from the host and is relevant only if the control point type is HOST. Options are YES (enter 1) or NO (enter 0). The default is NO. |
This value identifies the partner to the local node if the partner is a peer. This number is received by the local node from the partner during link establishment and is available from the system administrator at the remote site. When communicating with another LU 6.2 node, this number must correspond to the one entered by the partner in the Exchange ID field of option [a] Define Local Node. The value must be either eight hex (0-F) characters without embedded blanks or NONE if the remote CPU ID (see below) is specified. This field is optional. If neither the Exchange ID nor the CPU ID field is entered, the type field must be entered. | |
This is a null-terminated string of twelve hex [0-F] characters. The first two characters (representing the first byte of the CPU ID) are the PU type (usually 05 for PU type 5). The remaining ten characters (representing the final five bytes) are an implementation-dependent binary identifier. On a characters. The first two characters (representing the VTAM host, the five bytes are set to the subarea identifier of the host, specified by the SSCPID keyword in the VTAM ATCSTR definition. This value must match the value sent by the SSCP in bytes three through eight of the actpu request. This field is optional. If neither the Exchange ID nor the CPU ID field are entered, the type field must be entered. | |
Control Point Type | This value indicates the type of control point. Values are HOST or PEER. |
Controller Type | This parameter describes the type of IBM controlleremulated, and is relevant only if the control point type is HOST. Options are 3274, 3276, 4700, OTHR. The is HOST. Options are 3274, 3276, 4700, OTHR. The default is 3274. |
Load Module Name | Name of the load module returned on the ACTPU. This parameter is relevant only if the control point type is HOST. |
This option adds, changes, or deletes a line definition. It also stores the parameters for the dfnline verb. Table 2-4 describes the values for option [c] Define Line.
Table 2-4. Values for the Define Line Option
This option adds, changes, or deletes a station definition. It also stores the parameters for the dfnsta verb. Table 2-5 lists descriptions of the values for the Define Station option.
Table 2-5. Values for the Define Station Option
Value | Description |
|---|---|
Line Name | This is the name of a previously defined line used to reach the station. Enter ? to list the available lines. |
This value, the Synchronous Data Link Control address, must match the partner's SDLC address. Enter any two hex (0-F) characters, except 00 or FF. | |
The remote node name is the name for the remote node at the other end of the line. The node must have already been defined. Enter ? for a list of available remote nodes. | |
Phone Number | This is the phone number to the remote PU. It is returned in a node operator message to indicate which phone number to use for a manual switched (dial-up) connection. The field value is either a phone number or NONE. Special characters and letters are accepted to support autodial modems. Autodial automatically dials this number for you. For more specific autodial requirements, see dfnline in the man pages. |
The interval between polls to this station is a value not implemented by the Silicon Graphics SDLC in release 1.0. | |
The exchange ID identifies the local node to the partners in XID exchange at link establishment. It must be eight hex characters (0-9 and A-F) and embedded blanks are not allowed. This exchange ID overrides the exchange ID declared in the local node definition for this station only. This parameter is relevant only if the control point type is HOST. | |
This is the maximum BTU length that can be sent and received on this line. Values are 265 (the default), 521,1033, 2057, 3849, and 4105. If a value is not specified, the BTU value given in the line definition is the default. If both values are given, this value supersedes the BTU value in the line definition. | |
The maximum number of frames sent or received before acknowledgment is required. Values range from 1 to 7. If a value is not specified, the I-Frame value given in the line definition is the default. If both values are given, this value supersedes the I-Frame value in the line definition. |
| Note: Local node, remote node, and line resources are independent source characteristics and can be combined to generate a number of configurations. A station resource, however, is dependant on a specific Line resource and Remote Node resource. |
This option adds, changes, or deletes a secondary LU definition. It also stores the parameters for the dfnslu verb. Table 2-6 describes the values of the Define Secondary LU option.
Table 2-6. Value Descriptions for the Define Secondary LU
Value | Description |
|---|---|
Control Point Name | An existing control point name must be used for the secondary LU control point name. |
Pool Name (Optional) | The name of the secondary LU's LU pool. Use the pool name instead of a secondary LU name on an ALLOCATE request so the user can select from a group of LUs. |
LU Destination Address | |
Correlation Wrap Count | This value limits the number of correlation table entries used by LU exception response chains. Definite response chains are not affected by this value. Values range from 0 to 10. The default value is 10. |
Bulk Rate | This parameter, if set, gives a lower priority to traffic on this LU. Set it for such bulk data transfer LUs as printers. |
Terminate Session | This value specifies whether an active session with this secondary LU is deactivated when the communication line goes down. If SUPPORT is specified, the session is terminated with an UNBIND of type 0x0F. It is not intended to replace an orderly shutdown, which is still the responsibility of the transaction program. Values are NOT_SUP (the default) and SUPPORT. |
| Note: Local node, remote node, and line are source characteristics that can be combined to generate a number of configurations. A secondary LU, however, is dependent on a specific remote node resource. |
This option adds, changes, or deletes a local LU definition and stores the parameters for the dfnllu verb. Table 2-7 describes the values.
Table 2-7. Values for the Define Local LU Option
This option adds, changes, or deletes a remote LU definition. It also stores the parameters for the dfnrlu verb. Table 2-8 describes option [g]values.
Table 2-8. Values for Define Remote LU Option
This option adds, changes, or deletes a mode definition. It also stores the parameters for the dfnmode verb. Table 2-9 describes the option's values.
Table 2-9. Values for the Define Mode Option
This option adds, changes, or deletes a partner definition. Table 2-10 lists and describes the values for this option.
Table 2-10. Values for the Define Partner Option
Value | Description |
|---|---|
Remote LU Name | This, the local name for the remote LU, is chosen from previously defined remote LUs. Enter ? for a list of available remote LUs. |
Mode Name | The mode defines the service options used for the sessions with the remote LU. Choose from previously defined modes. Enter ? for a list of the available modes. |
Station Name | The station communicates with the partner. Choose a name from previously defined stations. The special value LOCAL indicates you are to use the internal loopback station. Data traffic is routed back at path control, rather than sent out to the data link layer. Enter ? for a list of the available stations. If parallel sessions are used, match the station specified here to the CNOS adjacent link station specified in the remote-LU definition. |
This option adds, changes, or deletes a transaction program definition. Table 1-10 lists the values for option [j] Define Transaction Program.
Table 2-11. Values for the Define Transaction Program Option
This option adds, changes, or deletes a configuration definition. The option cannot be selected, however, if the local node, local LUs, partner LUs, and transaction programs for this configuration are not defined.
When this option is selected, the Configuration Editor screen window appears with a series of prompts. Respond to the prompts, according to the information listed in Table 2-12.
Table 2-12. Configuration Editor Screen Prompts
Prompt | Response |
|---|---|
Select Local Node | Choose a local node for this configuration from thedisplayed list of pre-defined local nodes. |
Select Stations | Choose a station for this configuration from the displayed list of pre-defined stations. |
Select Secondary LUs | Choose a secondary LU for this configuration from the displayed list of previously defined secondary LUs. |
Select Local LUs | From the displayed list of previously defined local LUs, indicate the local LU for this configuration. |
Select Partners | From the displayed list of previously defined partners, indicate the partner for this configuration. |
Select Transaction | From the displayed list of previously defined Programs transaction programs, indicate the transaction program for this configuration. |
The Logging and Trace Menu controls the system log and the link-level trace access capabilities of the IRIS SNA SERVER. It is accessed through option [i] of the Network Operations Menu.
The IRIS SNA SERVER provides a logging capability to track different levels of messages within the node and notify the operator of events—both normal and abnormal—in the network. Operator messages (viewed by selecting option [h] of the Network Operations Menu) provide first level network event feedback. Logging is enabled by selecting option [c] Start Logging.
Log settings determine which messages are logged. Use option [b] Change Logging Values to update the log settings shown in Table 2-13.
Table 2-13. Message Logging Settings
Field | Value | Description |
|---|---|---|
Class | o | Operator Responses to the node |
| l | Log Logging messages |
| d | Dev Messages to help |
| t | Trace Trace statements |
Type | i | Info Status messages, |
| n | Notify Notification messages |
| e | Error Error messages |
| d | Diag Diagnostic messages |
Severity | 1-99, where: |
|
| 0 | Severity to remain unchanged |
| 10 | Lowest level, used for second-level text |
| 20 | Normal informational messages, such as |
| 30 | Node-operator messages, line |
| 40 | Error messages, abnormal terminations of |
| 90 | Program errors |
Because some events are visible only when the system log is running, it is a good practice to run the log when the node is active. Always run it when investigating a problem or abnormal event.
| Note: For option [c] to take effect, set the logging-messages parameter in option [a] Define Local Node of the Define Resource Menu to YES. |
The link trace feature writes trace data in raw form to a disk file specified in option [g] Start Link Trace. This raw file is processed by option [i] Display Link Trace and option [j] Print Link Trace to create a formatted file showing both the SNA headers and the data in a number of possible formats. An additional feature of option [g] captures and displays the SDLC control frames.
The following Logging and Link Trace Menu Options are available.
This option displays current settings of the log message queue. (See
Table 2-13 for the settings.) This option issues the dspmsgq node operator verb.
This option updates current settings of the log message queue. To change any of the values, enter either the number or log setting letter and press <enter>. To enable multiple types of classes of messages, enter multiple letters; for example, to enable all types of messages, enter INED and press <enter>.
This option enables the log message queue when you provide the name of the output log file. Log files are written in the directory named by the run-time variable STLOG in /usr/sna/etc/SNAENV.
This option uses the IRIX-supplied pg command to view formatted messages that are in the log file specified in option [c] Start Logging.
This option uses the IRIX-supplied pr and lp commands to print a formatted copy of the log file messages. The name of the log file requested is the same one specified in option [c] Start Logging.
This option starts the link trace facility and prompts for the responses shown in Table 2-14. This option runs the s2_ltrc core program.
This option stops the link trace facility and the writing of records to the raw output file specified in option [g]. Data written previously, however, is still available for display by the ltap function (see the s2_ltap core program). From the displayed list of active trace processes, select and enter the process ID of the trace to stop. An attempt to stop a trace process started by another user, however, can fail and produce a message requesting you try again using the authority of the trace initiator.
Table 2-14. Prompts for Start Link Trace
This option displays the trace output on the screen. The raw data output is formatted (based on the options selected) and presented to the screen using the IRIX pg command. Table 2-15 lists the prompts and responses for the Display Link Trace option. This option runs the s2_ltap core program.
Select an appropriate response to these screen prompts:
Table 2-15. Prompts for the Display Link Trace Option
Prompt | Response |
|---|---|
Trace File Name | Enter the file name specified as the output file at the start of the trace. |
Display Data in ASCII? | Enter A to translate the data using the ASCII character set; E (or press <enter>, since this is the default) to translate the data using the EBCDIC character set; or D to translate the Function Management Header (FMH) data using the EBCDIC character set and the unformatted data using the ASCII character set. |
Convert Based on FMD? | If the RU category is Function Management Data( FMD) and the Format Indicator is off, enter Y toconvert it to ASCII. Enter N or press <enter> totranslate the text to EBCDIC. |
Show Outbound Only? | Enter N or press <enter> to display both inbound and outbound data flows. Enter Y to display only outbound flows. |
Print Ruler? | Enter Y to display an offset ruler 64 bytes long with the RU data, enter N, or press <enter>. |
This option prints the trace output. Based on the options selected, the raw trace output is formatted and printed using the IRIX pr and lp commands.
This option runs the s2_ltap core program.
Provide appropriate responses to these screen prompts:
Table 2-16. Prompts for Printing Link Trace Output
Prompt | Response |
|---|---|
Trace File Name | Enter the file name specified as the output file when the trace was started. |
Display Data in ASCII? | Enter A to translate the data using the ASCII character set; E (or press <enter>, since this is the default) to translate the data using the EBCDIC character set; or D to translate Function Management Header (FMH) data into EBCDIC characters and unformatted data into ASCII characters. |
Convert Based on FMD? | If the RU category is Function Management Data (FMD) and the Format Indicator is off, enter Y to convert it to ASCII. Enter N or press <enter> to translate the text to EBCDIC. |
Show Outbound Only? | Enter N or press <enter> to display both inbound and outbound data flows. Enter Y to display only outbound flows. Enter Y to display an offset ruler 64 bytes long with the RU data. Otherwise, enter N or press <enter>. |
The supplemental manual or man pages describe the use and parameters of the nine core programs of the IRIS SNA SERVER. Table 2-17 describes each program.
Program | Package | Description |
|---|---|---|
s2_init | Core | The Node Initializer Program activates the s2_schd and s2_tpi processes and issues the initial configuration-definition verbs. |
s2_lgcp | Core | The Log Operator Program. |
s2_log | Core | The System Log Program receives log messages and writes the system log. |
s2_ltap | Device Driver | The Link Trace Analysis Program. |
s2_ltrc | Device Driver | The Link Trace Program. |
s2_pump | Device Driver | The Downloader Program is issued to load the SDLC software to an intelligent communications controller. |
s2_mscp | Core | The Node Operator Program. |
s2_schd | Core | The SNA Server Program. |
Two of these programs, s2_mscp and s2_lgcp, create control scripts that do not use the supplied menus. The other seven programs are more commonly run from the user package menus than from the command line and, therefore, are not usually explicitly started.
When the IRIS SNA SERVER is installed, these programs are placed in
/usr/sna/bin. There is no requirement that the /usr/sna/bin directory be in your path when using the user package. If you are not using the menus, add this directory to your path list or use the user package run-time variable STBIN to qualify their names. With the exception noted in s2_init, these programs make no assumption about the location of the core programs.
To start the Network Configuration program, enter this command line at the IRIS prompt:
/usr/sna/etc/netConf |
To create a new SNA configuration file or update an existing configuration file, follow these steps, which are described below:
Step 1: Collect Configuration Data
Step 2: Define Resource
Step 3: Define Configuration
Step 4: Generate Configuration
Step 5: Set Current Configuration
Collect the following IBM HOST VTAM definitions:
PU:IDBLK=xxx
PU:IDNUM=yyyyy
PU:MAXDATA=nnn
GROUP:NRZI=(NO) YES
GROUP:DUPLEX=(FULL) HALF
PU:ADDR=xx
PU:MAXOUT=n
LU:LOCADDR=xx
If you are defining a configuration for a host connection (PU Type 2), define:
Local Node
Remote Node
Line
Station
Secondary LU
If you are defining a configuration for a peer connection (PU 2.1 and LU 6.2), you need to define every resource in the Define Resource Menu except the Secondary LU.
To apply the host configuration data to an SNA configuration, define the necessary resources by selecting [a] Define Resource Menu from the Network Configuration Menu. A detailed Define Resource Menu is then displayed.
Define the following resources for your configuration file on a host connection:
Local Node
Exchange ID = xxxyyyyy
where xxx is from PU:IDBLK and yyyyy is from PU:IDNUM
Verb Message Buffer Size = nnn
set nnn to 256 if PU:MAXDATA=265
set nnn to 512 if PU:MAXDATA=521Remote Node
Controller Type = 3274
set to 3274 even if you are configuring a 3770 connection.Line
IRIX Device File = /dev/si1Each SNA SDLC controller provides two ports, and two SNA SDLC controllers are supported. The Device File names are:
/dev/si1 Controller 0, Line 1
/dev/si2 Controller 0, Line 2
/dev/si3 Controller 1, Line 1
/dev/si4 Controller 1, Line 2
Maximum BTU Length = nnn
where nnn is from PU:MAXDATA
Maximum I-Frames = n
where n is from PU:MAXOUT
Transmission Coding = NRZ
Set to NRZ if GROUP:NRZI=NO
Set to NRZI if GROUP:NRZI=YES
Half-Duplex/Full-Duplex: FDX
Set to FDX if GROUP:DUPLEX=FULL
Set to HDX if GROUP:DUPLEX=HALF
Station
SDLC Address = xx
where xx is from PU:ADDR
Exchange ID = NONE
This field is not used on a host connection.
Maximum BTU Length = nnn
where nnn is from PU:MAXDATA. This value supersedes the setting in the associated Line definition.
Maximum I-Frames = n
where n is from PU:MAXOUT. This value supersedes the setting in the associated Line definition.
Secondary LU
LU Destination Address = xx
where xx is from LU:LOCADDR
After all resources have been defined, the final configuration must be put together by selecting [k] Define Configuration from the Define Resource Menu.
Every time a resource is added to the configuration or is deleted from the configuration, you need to define the configuration again before continuing to the next step.
After the configuration is defined to the Network Configuration program, the final configuration file readable to the IRIS SNA programs still needs to be generated by selecting [c] Generate Configuration from the Network Configuration Menu.
Whenever a resource of an existing configuration is updated, the final configuration is not updated until this Generate Configuration step is completed.
You may create a number of configuration files in your database. However, only one configuration is used by the IRIS SNA SERVER. Set the current configuration by selecting [d] Set Current Configuration from the Network Configuration Menu (or perform this step from the Network Operations Menu).
 | Caution: If the SNA gateway process (s2_schd) is running, a new configuration does not take effect until next time the SNA gateway is started. |
| Note: If you have IRIS Token Ring installed, see, “Running the Network Operations Program with Token Ring.” |
To start the Network Operations program, at the shell prompt enter:
/usr/sna/etc/netOper |
A Network Operations Menu window is then displayed.
If this warning message is displayed when you try to run the Network Operations program:
You must set your current configuration before continuing |
enter x to return to the Network Operations Menu, the main menu of the Network Operations program.
| Note: This warning message is displayed every time a new user wants to run the Network Operations program. If you share one IRIX login id, such as root or guest, select [f] Set Current Configuration to check if the current configuration is correct. |
Enter f to Set Current Configuration. A Set Current Configuration menu is then displayed. Enter the letter corresponding to the desired configuration and you will see the selected configuration displayed at the Current Configuration:line in the Menu/Form section. The current configuration is now set. Entering x returns you to the main menu.
If the IRIS SNA SERVER is configured to connect to an IBM Host, the correct sequence of operations in running the Network Operations program is as follows:
Load the SDLC code to the SNA SDLC controller if it is not yet loaded.
To load SDLC, enter at the IRIX prompt:
/usr/sna/etc/ldSDLCn
where n is either 0 or 1, depending on whether you are using Controller 0 or 1.
You must load the SDLC code every time the IRIX system is rebooted.
Note: Do not load the SDLC code when a communication has already been established with a remote system. The load will not be successful. At the Network Operations Menu, select the following menu items:
— [f] Set Current Configuration
Do this to make sure you have the expected configuration.
— [a] Activate SNA Server
This activates the SNA gateway process s2_schd.
— [b] Activate Physical Unit — [d] Activate Line — [e] Activate Adjacent Link Station
Do this if the Adjacent Link Station is a switched line and then dial the phone number.
After the SNA gateway process is running, you may always check the communication link status, the logical unit status, or new messages from the IRIS SNA SERVER by selecting:
[j ] Display Station Status [k ] Display Host Status [h ] Display Messages |
To determine whether the communication line has been established with the remote system, from the Network Operations Menu, select [j] Display Station Status, which displays a status screen. The status of the Line should become active after you [d] Activate Line on that line. When the status of the Adjacent Link Station (ALS) becomes active also, the communication line with the remote host is established.
If the communication line is not established, go through the following checklist. See, “Defining Resources,” for more information.
Do you have the cable connected to the right port? There are two ports available for each SNA SDLC controller.
Is the cable from the SNA SDLC controller port securely connected to the modem? If a modem eliminator is used instead, is the other cable securely and properly connected to the remote system?
If it is a switched line, do you have the correct Exchange ID defined to the Local Node resource?
If it is a switched line, check the value of the Connection Type field of the Line definition. If it is set to SWITCHED instead of LEASED (MULTI is invalid), you need to activate the station explicitly, after you have activated the line, by selecting option [e] Activate Adjacent Link Station from the Network Operations Menu. An Activate Station form is displayed. Fill in the proper station name and set the Dial field to 0 - Connect. Execute the form by pressing the <enter> key again. Then dial the phone.
Do the values in fields of Transmission Coding (NRZI) and Half- Duplex/Full-Duplex in the Line definition conform to the settings at the remote system? Does the value in the SDLC Address field in the Station definition conform to the setting at the remote system?
Did the operator of the remote host system activate the line and the PU through VTAM V,NET,ACT commands yet? If the process of establishing link connection fails while you are trying to get your configuration straight, the status of the host system may not be in sync with your IRIS SNA system. Ask the VTAM operator to deactivate the PU and LINE completely and activate them again.
If none of the above works, perform a physical link trace according to instructions in , “Performing a Trace.” Send the link trace to an SGI Customer Support Engineer who can interpret the SNA protocols, correct the problem, and then re-establish a connection.
After the Line is active and the Station is active, you can run 3270 or RJE after performing these steps:
Check whether the LU is active or not by selecting option [k] Display Host Status from the Network Operations Menu.
A Host Status Display screen is displayed.
Look for the SSCP-LU column of the desired REMOTE/SLU.
If a number is displayed in the column, the LU is active. Furthermore, if a number is displayed in the LU-LU column of the desired REMOTE/SLU, the LU is active and the LU-LU session is being used by a process.
There are two possible reasons LU may not active after the Station has been active.
The LU is not defined to the host. Make sure the LU Destination Address in your configuration is defined at VTAM LU:LOCADDR.
The initial status of the LU is set to INACTIVE at VTAM. Ask the VTAM operator to activate the LU with a VTAM V,NET,ACT command.
There are four stages involved in obtaining a trace at the physical link level:
Starting the link trace.
To start a link trace, select [i] Logging and Trace Menu from the Network Operations Menu. Select from the Logging and Trace Menu option [g] Start Link Trace, which displays a Start Trace form.
Fill out the form.
The file name entered is relative to the /usr/sna/log directory. See , “Running the Network Configuration Program,” to determine the pathname of the device to be filled into the form. Finally, execute the form by pressing the <enter> key from the Action Selection section of the screen.
-
To stop a link trace, select [i] Logging and Trace Menu from the Network Operations Menu. Select from the Logging and Trace Menu option [h] Stop Link Trace and select the trace you want to stop. Remember to always turn off the trace when you do not need to run the link trace. The trace output can become too big to read. Running a link trace decreases the link performance. And, if the SNA gateway is terminated with a dangling link trace process, unexpected results can happen when the SNA gateway is restarted.
Displaying or printing the link trace.
The link trace feature writes trace data in raw form to a disk file specified at Start Link Trace. To print a link trace, select [i] Logging and Trace Menu from the Network Operations Menu. Select from the Logging and Trace Menu option [j] Print Link Trace. The raw form of trace data is decoded and piped to the IRIX lp program. To display a link trace, select from the Logging and Trace Menu option [i] Display Link Trace. The raw form of trace data is decoded and displayed to the window with the IRIX pg program.
Alternatively, the raw form of trace data may be decoded to a output file by entering the following command from a shell prompt of an IRIX window:
/usr/sna/bin/s2_ltap {trace filename} > {output filename}
Interpreting the link trace.
This is the ultimate goal of running a link trace and requires extensive understanding of IBM SNA protocols, as well as the underlying LU application protocols such as 3270, 3770, or DIA protocols. This discussion is beyond the scope of this documentation.
To start the Network Operations program, at the shell prompt enter:
/usr/sna/etc/netOper |
If the following warning message is displayed when you attempt to run the Network Operations program:
You must set your current configuration before continuing |
enter x to return to the Network Operations Menu, the main menu of the Network Operations program.
Enter f to set the current configuration, which displays a Set Current Configuration Menu. Enter the letter corresponding to the desired configuration, and you will see the selected configuration displayed at the Current Configuration: line in the Menu/Form section. The current configuration is now set. Enter x to return to the main menu.
This warning message is displayed every time a new user attempts to run the Network Operations program. If you share one IRIX login ID (for example, root, or guest), select [f] Set Current Configuration to check if the current configuration is correct.
If the IRIS SNA SERVER is configured to connect to an IBM host, the correct sequence of operations in running the Network Operations program is as follows:
At the Network Operations Menu, select the following menu items:
[f] Set Current Configuration
Do this to make sure you have the expected configuration.
[a] Activate SNA Server
This activates the SNA gateway process s2_schd.
[b] Activate Physical Unit
[d] Activate Line
After the SNA gateway process is running, you may always check the communication link status, the logical unit status, or new messages from the IRIS SNA SERVER by selecting:
[j] Display Station Status
[k] Display Host Status
[h] Display Messages
After the Line is active and the Station is active, perform these procedures before running the 3270 or RJE:
Check whether or not the LU is active by selecting [k] Display Host Status from the Network Operations Menu.
A Host Status Display screen is displayed.
Look for the SSCP-LU column of the desired REMOTE/SLU.
If a number is displayed in the column, the LU is active. Furthermore, if a number is displayed in the LU-LU column of the desired REMOTE/SLU, the LU is active and the LU-LU session is being used by a process.
There are two possible reasons LU may not activate after the Station has been active:
The LU is not defined to the host. Make sure the LU Destination Address in your configuration is defined at VTAM LU:LOCADDR.
The initial status of the LU is set to INACTIVE at VTAM. Ask the VTAM operator to activate the LU with a VTAM V,NET,ACT command.