Appendix BConfiguration Files
and then delete the node configuration file and delete all records from the domain configuration file except for the header record.
4.Start the SNAplus2 software.
5.Use the following command to define the configuration:
snapadmin
The value new.cfg stands for the name of the input file you are using (with the modifications that you made in step 1).
6.Use the following command to start the node (this also starts any resources that are defined in the file as being initially active):
snapadmin init_node
B.4.2 Sample Files Delivered with SNAplus2
The sample files are delivered in the directory /opt/sna/samples. The sample files are:
config1.cfg
Configuration for a LEN node, supporting 3270 emulation over an SDLC leased line (initially active) to a host that issues format 3 XIDs. The configuration includes two users, each with one 3270 emulation session.
config2.cfg
Configuration for an end node, supporting 5250 emulation over an SDLC switched line
config3.cfg
Configuration for a LEN node, supporting RJE over QLLC to a host that issues format 3 XIDs. The configuration includes a single RJE workstation with one LU.
config4.cfg
Configuration for a LEN node, supporting dependent APPC communications over an SDLC switched outgoing line (activated on demand) to an APPN end node. The configuration includes a single local LU.
config5.cfg
Configuration for a LEN node, supporting 3270 emulation with LU pools, using both Token Ring and Ethernet to a host that issues format 3 XIDs. The configuration includes a pool of LUs (some defined on each of the two host links), and two users each with two 3270 sessions using the pool.
config6.cfg
Configuration for a LEN node, supporting PU concentration. The upstream link is an SDLC leased line (initially active) to a host that issues format 3 XIDs; there are two downstream links over Token Ring. The configuration includes four downstream LUs used for 3270 emulation, mapped to four host LUs.
config7a.cfg, config7b.cfg
Configurations for a network node and an end node, communicating
632