This is the unique name of the SNAP-IX configuration file. The
default for this name is sna_node.cfg.
Although it is possible to edit this file, it is strongly recommended
that configuration is done using xsnadmin.
(2) Control point name
This is the unique Control point name for this workstation. In the
SNA network, the Control point is an addressable location (PU type
2.1). Your network administrator will assign this to you.
(3) Node ID to send
This is the unique ID of this workstation. On other platforms this
is often referred to as the Exchange ID or XID.
Your network administrator will assign this ID for you.
(4) Network name
This is the unique ID of the network to which you are connected. It
is an alphanumeric value and can be 1-8 characters long. The network
name works with the Control point name to uniquely identify a system.
Your network administrator will tell you the value.
(5) Local APPC LU
An LU manages the exchange of data between transactions. The local
APPC LU name is the name of the LU on your system. Your network
administrator will assign this to you.
(6) APPC mode
This is the name given to the set of parameters that control the APPC
conversation. This name must be defined at each partner system.
Your network administrator will assign this to you.
(7) Invokable TP
WebSphere MQ applications trying to converse with this workstation will
specify a symbolic name for the program to be run at the receiving end.
This will have been defined on the channel definition at the sender.
For simplicity, wherever possible use a transaction program name of MQSERIES,
or in the case of a connection to VSE/ESA, where the length is limited to 4
bytes, use MQTP.
(8) Local MAC address
This is the network address of the token-ring card. The address to
be specified is found in the ether value displayed in response to the
ifconfig tr0 command issued at a root level of
authority. (Tr0 is the name of the machine's token-ring
interface.) If you do not have the necessary level of authority, your
Sun Solaris system administrator can tell you the value.
(9) Port name
This is a meaningful symbolic name that is used to associate the
definitions with a network interface (in this case, a Token-Ring
adapter). A separate Port must be defined for each physical device
attached to the workstation.
(10) Full path to executable
This is the path and name of the script file that invokes the WebSphere MQ
program to run.
(11) Local queue manager
This is the name of the queue manager on your local system.
(10) Link station name
This is a meaningful symbolic name by which the connection to a peer or
host node is known. It defines a logical path to the remote
system. Its name is used only inside SNAP-IX and is specified by
you. The connection must be associated with an existing Link and owned
by one local node. You must define one connection for each partner or
host system.
(18) CPI-C symbolic destination name
This is a name given to the definition of a partner node. You
choose the name. It need be unique only on this machine. Later
you can use this name in the WebSphere MQ sender channel definition.
(20) Node ID to receive
This is the unique ID of the partner workstation with which you will be
communicating. On other platforms this is often referred to as the
Exchange ID or XID. For a connection to a host
system any values except 000 FFFFF and FFF FFFFF may be
specified. Your network administrator will assign this ID for
you.