3.2.1 Specifying the Path to SNAP-IX Programs

SNAP-IX executable programs are stored in a directory specific to SNAP-IX; when you run the programs, you need to specify the path to this directory. You can specify the path either by adding the directory to your PATH environment variable before you run the programs for the first time, or by including the directory name each time you run the programs.

The Motif administration program is stored in the directory /opt/sna/bin/X11, and the other programs are stored in the directory /opt/sna/bin. If you add these directories to the definition of the PATH environment variable in your .login or .profile file, SNAP-IX locates the programs automatically. Alternatively, you can specify the directory name when you run the program, as in the following examples:

/opt/sna/bin/sna start

/opt/sna/bin/snaadmin query_node

/opt/sna/bin/X11/xsnaadmin

The sample command lines shown in this manual assume that you have added the directories to your PATH environment variable, and do not include the directory names.

3.2.2 Enabling SNAP-IX Servers

This section describes how to enable SNAP-IX on a computer that was installed as a server (that is, with the SNA node components installed). If you are enabling SNAP-IX on a client, see Enabling SNAP-IX on Solaris Clients.

You must enable SNAP-IX on the local system before you can configure or manage the local node (either locally or from a remote SNAP-IX node).

To enable the SNAP-IX software, enter the following command at the Solaris command prompt:

sna start [ -s ] [
 -m kernel_memory_limit] [ 
-t ] [ 
-c ]

When you install SNAP-IX, the installation utility automatically updates the startup file the sna start command. This ensures that SNAP-IX is started automatically at system startup. If you do not want SNAP-IX to be started automatically, you can remove or comment out this line, and then follow the instructions in this section to enable the SNAP-IX software manually.

The parameters and options for the sna start command are as follows:

-s

Specifies that SNAP-IX should not write messages to the system console. If you do not use this option, SNAP-IX writes messages to the console when it ends, and also writes the text of certain error log messages to the console as well as to the log file.

-m kernel_memory_limit

Specifies the maximum amount of kernel memory, in kilobytes, that SNAP-IX should use at any time. (Kernel memory is used for internal data structures.) If a component of SNAP-IX attempts to allocate kernel memory that would cause the total amount of memory currently allocated to SNAP-IX components to exceed this limit, the allocation attempt fails.

If you do not use this option, kernel memory usage is not limited.

-t

Activates tracing on all interfaces between kernel components, and also client/server tracing. (This option does not turn on DLC tracing.) Tracing enables you to diagnose problems that occur during startup. If you do not use this option, tracing is inactive at all interfaces; you can then activate it on specific interfaces as required, using the command-line administration program snaadmin.

Tracing on all interfaces degrades the performance of SNAP-IX components. After the software is enabled, you can use the command-line administration program snaadmin to stop tracing on any interfaces where it is not required. For more information about tracing, refer to SNAP-IX Diagnostics Guide.

-c

Specifies that SNAP-IX should update its stored information about adapter cards installed in the Solaris computer, to delete information about adapter cards that have been removed since you installed SNAP-IX. For more information, refer to Checking Adapter Cards from the Command Line. If you do not use this option, SNAP-IX retains existing information about adapter cards even if they have been removed.

SNAP-IX writes messages to standard error (normally your terminal's screen) to indicate that it is initializing, and to indicate whether initialization completes successfully.

If initialization fails, the messages include information about the cause of the error, and (where appropriate) additional information such as the Solaris operating system error message. The text written to standard error may also include a message indicating that you can find further information in the error log file. The sna start command then ends with a nonzero exit code that indicates the nature of the error.

For more information about exit code values, refer to SNAP-IX Diagnostics Guide.

3.2.3 Disabling SNAP-IX Servers

Disabling the SNAP-IX software on a server automatically stops the SNAP-IX node and its associated connectivity components. Disabling SNAP-IX also stops any other processes (such as a 3270 emulation program) from using SNAP-IX resources on this server.

In general, you should stop individual services as users finish using them, and only disable the system when there is no SNAP-IX activity. Disabling the SNAP-IX software on a client stops any programs running on the client from accessing SNAP-IX facilities.

If you need to disable SNAP-IX while users are active, warn users that SNAP-IX is stopping, and give them time to finish their activities before you disable the software. Use the Motif administration program or the command-line administration program to view details of active users.

If a 3270 emulation program is using LUs on the node when you disable the SNAP-IX software, all 3270 emulation sessions using these LUs end. The program continues to run, but the user cannot use the sessions until the software is re-enabled. If the RJE workstation program is running, it automatically exits. Applications using the APPC, CSV, LUA, NOF, or MS APIs are notified by a COMM_SUBSYSTEM_ABENDED return code, LU0 applications by an LU0_EVENT_*_BAD or LU0_EVENT_*_SESS_FAIL return code, HLLAPI applications by a HARC_SYSTEM_ERROR return code, and CPI-C applications by a CM_PRODUCT_SPECIFIC_ERROR return code.

To disable the SNAP-IX software, enter the following command at the Solaris command prompt:

sna stop

If SNAP-IX is disabled successfully, sna stop returns an exit code of 0. Any other exit code indicates that an error occurred and that the SNAP-IX software was not disabled. Refer to SNAP-IX Diagnostics Guide for more information about exit code values.