HP-UX SNAplus2 R7 Administration Guide

Managing SNAplus2 Client/Server Systems
IP Networking Requirements
11.1.1 Setting Up IP Port Numbers
SNAplus2 uses both TCP/IP and UDP/IP communications to send client/server data across the LAN. By default, it
uses the port number 1553 for both types of communications. For most installations, this port number should be
suitable; you do not need to change it.
If you encounter problems enabling the SNAplus2 software, check the error log file for messages indicating that the
port number used by SNAplus2 clashes with the port number used by another program. If you find such messages,
take the following steps:
1. Check the /etc/services file on the computer where the error occurred, to see if another program is listed
as using the port number 1553 for either TCP/IP or UDP/IP communications. If this is the case, first try to
change the other program to use a different port.
2. If you cannot do this, or if no program is listed as using port 1553, find another port number that is not listed
in the file as being used by any program. Check the /etc/services file on all other SNAplus2 computers
in the same domain, to ensure that the number is not used on any other computer.
3. In the /etc/services file on each computer in the domain, add two lines in the following form:
sna-cs nnnn/tcp
sna-cs nnnn/udp
The nnnn entry is the new port number. This must be set to the same value on all computers in the SNAplus2
domain.
4.
WINDOWS
If your SNAplus2 domain includes Windows clients, add the same two lines to the services file on each
Windows computer. The services file is in the same format as the HP-UX file, and is generally stored
in the home directory of the Windows TCP/IP software; see your Windows TCP/IP documentation for more
information if necessary.
5. Re-enable the SNAplus2 software.
11.1.2 LAN Access Timeout
If the client is communicating with SNAplus2 servers across a network for which connection charges are payable,
you may want to ensure that the TCP/IP connection from the client is dropped automatically after applications on
the client have stopped using SNAplus2 resources. This does not automatically disable the SNA software on the
client; it remains active, and attempts to re-establish contact with a server if an application requires it at a later time.
The lan_access_timeout parameter (in the sna_clnt.net file for a HP-UX client, the sna.ini file for a Win16
client, or the Registry for a Win32 client) enables you to disable the SNA software on the client. The TCP/IP
connection is dropped when none of the following events have occurred on the client for the specified time:
• APPC or CPI-C conversations active (or attempts to start a conversation)
• 3270 or LUA sessions active
• CSV TRANSFER_MS_DATA verbsfrom a Windows client
• RJE workstations active
• MS verbs (HP-UX clients only)
• NOF verbs (except the query_central_logger or query_node_all verbs)
• Administration commands (except the following events, which do not cause the client to restart the connection):
• Error or audit messages logged by the client (these are logged locally on the client, even if central logging
is being used)
144