This chapter describes the menu options of IRIS SNA LU 6.2. It is intended more as a reference guide than a tutorial. (To learn how to operate the product, refer to Chapter 3, “Getting Started with IRIS SNA LU 6.2.”)
This chapter presents three menus:
LU 6.2 Main Menu
LU 6.2 Session Operations Menu
LU 6.2 Application Menu
Each menu is shown as it appears on the screen, and its options and specific parameters are described in detail.
The IRIS SNA LU 6.2 Main Menu, shown in Figure 4-1, is accessed by entering the following command line at the IRIX prompt:
 | Note: Typing a character that does not correspond to a menu option causes the message Invalid option, press <return> to continue to appear. All menus function this way. |
The IRIS SNA LU 6.2 Main Menu contains two submenus: the LU 6.2 Session Operations Menu and the LU 6.2 Application Menu. The last three options displayed on the LU 6.2 Main Menu— Exit, Help, and Shell—are common to each menu of the IRIS SNA SERVER.
X | Exit | This option recalls any previous menu and, eventually, the IRIS SNA SERVER Main Menu. From the Main Menu, this option exits the program |
|---|---|---|
? | Help | This option displays on- line information about menu choices. |
! | Shell | This option spawns a shell in which to execute shell commands. Press <cntrl-d> to return to the current menu. |
The information contained in the brackets at the top right of each menu is the reference file name of the display appearing on the screen.
The following options are available:
The IRIS SNA LU 6.2 Session Operations Menu, shown in Figure 4-2, is accessed by option [a] of the IRIS SNA LU 6.2 Main Menu.
The IRIS SNA LU 6.2 Session Operations Menu provides options to manage sessions by issuing control operator commands. These commands initialize the connections between your node and partner LUs, set or change the limit on the number of active sessions between the LUs, and explicitly activate or deactivate sessions.
This section provides detailed information on the options available on the Session Operations Menu.
This option initializes the Service Manager Mode, the privileged logical connection between your LU and your partner's LU in a peer connection.
| Note: There is no Service Manager Mode in host-mediated connections. |
LUs use this privileged mode to negotiate the limits on the other modes between the two LUs. When session limits are initialized, changed, or reset on the user modes, the two LUs involved must agree on the new limits. This agreement is reached by having the source of the change allocate a conversation with a special agent program at the target. This agent program is called the Change Number of Sessions model, or CNOS.
The conversation between the source program issuing your command and the target CNOS program occurs over the Service Manager Mode. Consequently, the Service Manager Mode must be initialized by both LUs before any other mode can be initialized. There is no need for the two LUs to negotiate the session limits for the Service Manager Mode since the limits are pre-defined for all LUs by the LU 6.2 architecture.
Initialize the Service Manager Mode by giving the names of the local and remote LUs involved in this connection. A successful action produces the message, Mode Initialization Complete. If unsuccessful, a major and minor return code will be displayed (specific return code information is provided in the IRIS SNA SERVER Administration Guide).
This option issues the initsl control operator verb for the SNA Service Manager Mode (SNASVCMG).
This option establishes initial session limits and contention-winner minimums between the local LU and its partner for the specified mode. It activates any auto-initiated sessions specified by the mode-block definition and is valid only when session limits are 0. If the mode is for a peer connection, the Service Manager Mode for both LUs must already be initialized.
Enter the following information:
Local LU name
Remote LU name
Mode name
Session limits (maximum sessions, minimum first speakers, and minimum bidders)
The minimum first-speaker and bidder limits specified guarantee that each LU is allotted a minimum number of sessions on which to initiate a conversation (providing no conversation is active) without having to bid for the right to begin with a partner. The limits specified cannot exceed the limits configured for the mode block. The actual number of sessions started can be less than this number, however, if there are insufficient system resources to support the number of sessions requested.
The Initialize Session Limits option issues the initsl control operator verb.
This option explicitly activates a session with the remote LU using the properties defined by the specified mode. If the maximum number of first-speaker sessions has not been reached, the session is activated as a first-speaker session. Otherwise, the session is activated as a bidder session.
Enter this information:
Local LU name
Remote LU name
Mode name
The Activate Session option issues the actses control operator verb.
This option changes session limits and polarities specified earlier in option [b] for parallel-session connections between the local and remote LUs under the specified mode name.
Use this option to tailor the performance of LU 6.2, given varying levels of system activity. For example, when using LU 6.2 in an inventory distribution system, reduce session limits (which reduces the possible number of active programs that can use LU 6.2) during month-end accounting activities and increase session limits during the peak order-taking hours.
Enter the following information:
Local LU name
Remote LU name
Mode name
Session limits (maximum sessions, minimum first speakers, minimum bidders)
Responsibility: source or target?
The Responsibility: source or target? prompt refers to the side (either source or target) responsible for bringing down sessions in response to lowered session limits.
The Change Session Limits option issues the chgsl control operator verb.
This option resets the session limits to 0 for a given mode or all modes between the local and the remote LU. As conversation activity ends, the sessions are deactivated.
Enter the following information:
Local LU name
Remote LU name
All modes y/n (enter mode name only if you answer n)
Target is responsible y/n
Drain source y/n
Drain target y/n
Force reset y/n
All modes resets all modes between the local and remote LUs or a specific mode (for which you provide the name). Target is responsible determines whether or not the target initiates the session take-downs. Drain source and Drain target establish whether or not the source and target can drain their conversation requests. If yes, all pending conversation requests and new conversation requests can be honored if conversations are active. Force specifies whether or not session limits can be lowered if the partner is unable to be notified of this change. For example, if the communications line has dropped, the CNOS negotiation will fail. Specifying force=yes causes the limits to be reset.
The Reset Session Limits option issues the rstsl control operator verb.
This option deactivates a specific session immediately or when the current conversation allocated to the session is deallocated.
With auto-initiated sessions, the LU can automatically activate a session to keep the number of active sessions at the auto-initiated limit. That is, it activates them as quickly as you deactivate them. To terminate session activity in this case, use option [e] to reset session limits.
Enter the following information:
Local LU name
Remote LU name
Mode name
SCBID
Immediate Deallocation y/n
To determine the SCBID (Session Control Block ID), use option [j] to see the session status. When Immediate Deallocation=yes, the session is deactivated immediately, even if a conversation is using it. When Immediate Deallocation=no, the session is deactivated after any current conversation is completed.
The Deactivate Session option issues the dctses control operator verb.
Access the IRIS SNA LU 6.2 Application Menu, shown in Figure 4-3, from option [b] of the IRIS SNA LU 6.2 Main Menu.
Before using this menu, establish an active session between a local LU and the remote LU specified as a partner in Options [a] and [b]. To review the basic operations of file transfer, see the Quickstart in Chapter 3.
This option transfers any type of file to a UNIX system. When the screen displays the five fields described in Table 4-1, enter the letter (a, b, c, d, or e) of the field value to edit, then reposition the cursor and make the change.
Table 4-1. File Transfer Parameters
Field | Description |
|---|---|
[a] Local LU Name | The name of the local LU in your configuration. |
[b] Remote LU Name | The name of the remote LU to which the file is sent. |
[c] Mode Name | The name of the mode to use. |
[d] File To Send | The fully qualified pathname of the file on your system. |
[e] Receive As | The complete pathname where the file should be placed on the remote system. File names without pathnames are placed in the current working directory of the process that started the SNA Server. |
Apply these additional constraints:
A local LU and a remote partner LU must be active.
Sessions must exist between the local LU and the remote LU.
The file that is sent must exist on disk.
The path specified under the Receive As field must be a valid path.
Option [b] transfers a file to an IBM System/36. The file must be a text file of ASCII characters with new lines occurring at least at intervals of 138 bytes. The file is transformed from ASCII to EBCDIC and formatted for storage as a source file on the IBM peer.
Typical System/36 files are fixed-record, fixed-format files. Free-form IRIX files cannot be stored as is. Files are written in fixed records padded to 138 characters.
When the screen displays the six fields described in Table 4-2, enter the letter (a, b, c, d, e, or f) of the field you want to edit. Provide the new field value after the cursor is positioned on that field.
Table 4-2. IBM File Transfer Parameters
Field | Description |
|
|---|---|---|
[a] | Local LU | The name of the local LU in your configuration. |
[b] | Remote LU | The name of the remote LU receiving the file. |
[c] | Mode | The name of the mode to use. |
[d] | File To Send | The complete pathname of your system's file. |
[e] | Receiving Library | The library where the file is stored. This field can be left blank. |
[f] | Receiving File Name | The file name under which the file will be stored. This field cannot be left blank. If a library member is specified, the file will be stored as a source member, under this name, in the specified library. |
These additional constraints apply:
Both the local LU and remote LU must be active.
Sessions must exist between the local and remote LUs.
The file sent must exist on disk.
Files sent to an IBM System/36 are stored.
Field [f] cannot be blank.
This option enables you to enter IRIX commands locally for execution on a remote machine. Previously established permissions between the local and remote LUs determine the nature of the dialog.
Enter the letter (a, b, or c) of the field (Table 4-3) whose value you want to edit. Reposition the cursor on that field and enter the new value.
Table 4-3. Remote LU Parameters
Field | Description |
|
|---|---|---|
[a] | Local LU | The name of the local LU in your configuration from which you are executing commands. |
[b] | Remote LU | The name of the partner receiving the commands. |
[c] | Mode | The name of the mode to use. |
After supplying the values, press <enter> to present a prompt at which to enter the IRIX commands. When these commands are executed on the remote machine, their output, if any, is displayed on your terminal. Enter ls -l and press <enter> for an example. Press <cntrl-d> to end the session with the remote site.Application Menu Options