HP-UX SNAplus2 R7 Administration Guide

Administering SNAplus2
Enabling and Disabling SNAplus2 on the Local System
that would cause the total amount of memory currently allocated to SNAplus2 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 and back-level 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
snapadmin.
Tracing on all interfaces degrades the performance of SNAplus2 components. After the software is enabled,
you can use the command-line administration program
snapadmin to stop tracing on any interfaces where it is
not required. For more information about tracing, refer to
HP-UX SNAplus2 Diagnostics Guide.
SNAplus2 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 HP-UX 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
snap 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 HP-UX SNAplus2 Diagnostics Guide.
Advanced Options for the snap start Command
In some cases, particularly when you are testing out new SNAplus2 configurations, you may want to start SNAplus2
with a configuration that you have saved to a temporary file (rather than with the standard configuration in the files /
etc/opt/sna/sna_node.cfg and /etc/opt/sna/sna_domn.cfg). To do this, you can use the following
additional options on the snap start command:
-n node_config_file -d domain_config_file
node_config_file is the full pathname of the file to which you have saved node configuration (instead of /etc/
opt/sna/sna_node.cfg), and domain_config_file is the full pathname of the file to which you have saved
domain configuration (instead of /etc/opt/sna/sna_domn.cfg).
Note
These options are not intended for general use. Do not use them unless you have a specific
requirement to do so.
The snapgetpd command will not operate correctly when SNAplus2 is running with
these options, because it always collects information from the standard configuration files.
Before using snapgetpd, ensure that you are running with the standard configuration
files by starting SNAplus2 without these options.
3.3.3 Disabling SNAplus2 Servers
Disabling the SNAplus2 software on a server automatically stops the SNAplus2 node and its associated connectivity
components. Disabling SNAplus2 also stops any other processes (such as a 3270 emulation program) from using
SNAplus2 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 SNAplus2 activity. Disabling the SNAplus2 software on a client stops any programs running on the client
from accessing SNAplus2 facilities.
If you need to disable SNAplus2 while users are active, warn users that SNAplus2 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.
67