There are a number of differences between the way NS is implemented
on MPE V systems and the way it is implemented on MPE/iX systems.
These differences affect the network itself, some of the applications
that users may run over the network, and the command used to obtain
status information about the network. Since it is helpful to understand
these differences as you prepare to move an existing MPE V network
to MPE/iX, they are summarized below.
Differences in the Network |
 |
A number of the methods available for making connections to
an MPE V network are not available with NS 3000/iX.
If your MPE V network includes one of these you will need
to modify your network configuration before attempting to use the
network on MPE/iX systems. More information on the specific steps
required to modify or remove unsupported links or connections can
be found later in this appendix.
The connection methods that are not supported on NS 3000/iX
are:
Asynchronous Network Link.
Bisynchronous link-level protocol.
In addition, while it is possible to access a DS/3000 node
directly from an NS 3000/V node, this capability is not
supported on NS 3000/iX. A user of an NS 3000/iX
network who wants to access a DS/3000 node must first access an
MPE V NS node. This is because the DS/3000 code that was included
as a subset of the NS 3000/V code is not provided with
NS 3000/iX.
Differences in Configuration Files |
|
NS 3000/V network configuration files are separated
into two files, the NMCONFIG file, which contains
link information, and the NSCONF file, which
contains the transport configuration and other subsystems you have
purchased such as SNA.
NS 3000/iX systems have a single NMCONFIG.PUB.SYS
file that contains information for the network transport, for NetIPC
and link-level logging, and also for the Datacommunications and
Terminal Subsystem (DTS). NMCONFIG.PUB.SYS
also contains information for any other subsystems you have purchased
such as SNA.
Differences in Applications Support |
|
There are also differences in the implementations of NS 3000/V
and NS 3000/iX that will affect certain applications that
users may currently be running on your MPE V network. These differences
are as follows:
NS 3000/iX supports PTOP
for HPDESK only.
On NS 3000/iX PTOP is not supported for applications
other than HPDESK. Network users who are running PTOP programs will
need to convert them to NetIPC/RPM programs before running them
on an NS 3000/iX network. Refer to the NetIPC
3000/XL Programmer's Reference Manual and the Using
NS 3000/iX Network Services for more information.
Nowait I/O RFA is not available with NS 3000/iX.
Privileged mode programs that use nowait I/O Remote File Access
over an MPE V network will need to be modified before they can be
run on an NS 3000/iX network. Refer to the Using
NS 3000/iX Network Services for more information.
Difference in How to Obtain Status Information |
|
On MPE V systems the SHOWCOM command returns
status information about a communication device, and is used to
determine line activity and quality. This information is still available
on NS 3000/iX, but is accessed through a different command.
Use the LINKCONTROL STATUS command to access
status information on NS 3000/iX.
