The following paragraphs summarize differences between NS 3000/V
and NS 3000/iX. Make sure that you account for these differences
that could affect your network when migrating to NS 3000/iX.
For system migration issues, refer to the MPE/iX Migration series
for more information.
Differences in Hardware |
 |
Some NS 3000/V hardware components are not part of
an NS 3000/iX network, such as the ATP for terminal connections,
and the INP for network links.
On an NS 3000/iX network, the DTC provides connections
for local or remote terminals and serial printers. The DTC also
provides MPE/iX access to X.25 through a DTC/X.25 Network Access
card. The Distributed Terminal Subsystem (DTS) LANIC on the MPE/iX
host is used for system-to-system X.25 connectivity.
Unsupported Network Connections |
|
Before migrating your network, identify any unsupported network
connections. The network connections that are not supported on NS 3000/iX
networks are as follows:
Asynchronous SERIAL Network Link and bisynchronous
link-level protocol. To ease migration, you can convert Asynchronous
SERIAL network links to the NS 3000/V Point-to-Point links
which can be converted to NS 3000/iX. Point-to-Point links
use the LAP-B protocol.
Connections to DS/3000 nodes. DS network services
are not supported on NS 3000/iX. If DS/3000 nodes are part
of an existing network, either migrate them to NS 3000/V
or maintain NS 3000/V connections to the DS/3000 nodes.
Differences in Configuration of Terminals and Printers |
|
On NS 3000/V networks, the SYSDUMP
program is used to perform I/O configuration which includes configuring
terminals, printers, and other I/O devices and drivers. On NS 3000/iX,
terminals and serial printers are configured on the host (using
NMMGR) and, if you are using PC-based network management, on the
OpenView Windows Workstation (using the OpenView DTC Manager software).
For more information on configuration using your OpenView Windows
Workstation, read Using the OpenView DTC Manager.
PAD devices on NS 3000/V are configured (using NMMGR)
as part of the X.25 network configuration. On NS 3000/iX
with PC-based network management, PAD devices are configured both
on the host (using NMMGR) and on the OpenView Windows Workstation
(using the OpenView DTC Manager software). (With host-based network
management, PAD devices are also configured using NMMGR.)
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 Network Services |
|
Differences in the support of network services between NS 3000/V
and NS 3000/iX can affect applications that users may currently
be running on the NS 3000/V network. These differences
are:
NS 3000/iX supports PTOP
for HPDESK only. 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 NS 3000/V network will need to be modified before
they can be run on an NS 3000/iX network. Refer to Using
NS 3000/iX Network Services for more information.
To Obtain Device Status Information |
|
On MPE V systems, the SHOWCOM command returns
status information about communication devices such as Local Area
Network Interface Controllers(LANICs). On NS 3000/iX systems,
this information is available with the LINKCONTROL...;STATUS
command.
