NS3000/iX Operations and Maintenance Reference Manual (36922-90039)

122 Chapter7
Commands
NETCONTROL START
Discussion
In order for internetwork communications to be possible, you must
activate at least one network interface using the NET keyword.
When this command is entered with an X.25 NI name, the system
accesses the DTC/X.25 Network Access subsystem to verify that the
X.25 line is started. If the line is not started, the command fails. If the
X.25 line is started, the command is successfully completed if
everything is correct. This enables the X.25 address that is associated
with this system in the DTC/X.25 Network Access, and connections can
be generated or accepted from this system.
Example 1
In Example 1, the node has one LAN link configured (LAN1) plus
loopback (LOOP). Starting the network requires issuing a NETCONTROL
START for each configured network interface (NET=niName). Once both
network interfaces (and related entities) of the network transport have
been successfully initiated, as indicated by the lack of error messages,
any other related subsystems installed on the node can be initiated.
This node, as is typically the case, has NS 3000/iX Services installed.
:NETCONTROL START;NET=LAN1
:NETCONTROL START;NET=LOOP
:NSCONTROL START
Refer to the NSCONTROL command pages in this section for more
information.
Be aware that to successfully initialize a node, the commands must be
issued in the order shown: first all required NETCONTROL commands,
then any NSCONTROL commands.
This first example provides an overview of initializing a node, showing
where NETCONTROL fits into the process. The next five examples
examine the START function and how it affects the entities defined for
initialization (Figure 7-1). As will be shown in the examples, the
keywords included with the START function and the entities affected
determine which events occur at initialization. To understand this
relationship, it is helpful to see the events that occur when the network
transport is initialized.
Example 2
Example 2 shows the events associated with the START function at
initiation. As indicated in the status report, the general transport is not
active. Therefore, the first events of initiation are to initialize the
control process (CP) and the general protocols. Compare the displayed
events to the defined entities of Figure 7-1. The events displayed in this