HP 3000 Manuals HP 3000 Manuals
Migration from NS3000/V to
NS3000/XL and NS3000/XL Links
by Everett Thomas and Mike Genevro--Information Networks Division
This article discusses the migration from NS3000/V to NS3000/XL. For a
brief comparison of DS/3000 and NS3000/XL, see the article entitled
"Migration from DS/3000 to NS3000/XL and NS3000/XL Links."
Differences Between NS3000/V and NS3000/XL
NS3000/XL is a compatible subset of NS3000/V, the powerful networking
software available on the MPE V/E-based members of the HP 3000 family.
Missing Features
The following list specifies the features that are available in NS3000/V,
but are not available in NS3000/XL:
* Wide-area network links are not supported.
* Program-to-Program communication (PTOP) is not available. For
information on translating your PTOP applications, refer to the
translation procedures in Appendix B of the NetIPC 3000/XL
Programmer's Reference Manual (P/N 5958-8600).
* No-wait I/O Remote File Access for privileged mode programs is not
available.
* The SHOWCOM command, which displays line activity and error status,
is not available under NS3000/XL. However, much of the information is
available under NS3000/XL through the LINKCONTROL STATUS command.
* Automatic log on of private sessions for the Remote File Access (RFA)
and the Remote Database Access (RDBA) services is not available.
* The NSINFO and NSSTATUS intrinsics and the SERVICES option of the
DSLINE command are not available.
Changed Features
The features that changed from NS3000/V to NS3000/XL are as follows:
* When using the Virtual Terminal service in NS3000/XL, if the physical
terminal is connected to an NS3000/XL system, it must be terminal
type 10. If the physical terminal is connected to an NS3000/V
system, the terminal must be terminal type 10, 14, or 16.
* When using Network File Transfer (NFT) or Remote File Access (RFA) in
NS3000/XL, only files with MPE V characteristics are supported. For
instance, the mapped access file system feature of MPE XL is not
supported by NFT and RFA in NS3000/XL.
* Remote Database Access in NS3000/XL is supported only for TurboIMAGE
databases. Remember that an IMAGE database on a DS/3000 node can be
accessed by using an intermediate NS3000/V node.
* Under NS3000/V, node configuration is done through a combination of
the system utility (SYSDUMP) and NMMGR. Under NS3000/XL, node
configuration is accomplished solely through NMMGR.
* There is no direct migration or conversion of configuration files
between NS3000/V and NS3000/XL. Users must completely configure their
HP 3000 Series 900 system as a node on their LAN. This process is
simple and straightforward. A step-by-step guide is provided in
Appendix A of the NS3000/XL Network Manager Reference Manual (P/N
36920-90002).
* NS3000/V uses two configuration files to hold configuration data:
NMCONFIG.PUB.SYS and NSCONF.NET.SYS. The latter of these files may be
optionally renamed to any legal filename of the user's choice,
provided the group and account names remain the same (i.e.,
filename.NET.SYS). Multiple versions of the NSCONF.NET.SYS file can
be created and selectively activated.
* NS3000/XL uses a single configuration file with a required filename,
NMCONFIG.PUB.SYS. NMCONFIG.PUB.SYS is the only file that will be
recognized by the HP 3000 Series 900 system as an active network
configuration file. As an additional constraint, this configuration
file must reside on the system disc (LDEV 1).
* Since the services supported by NS3000/XL are fixed, it is not
necessary to stream CONFJOB.NET.SYS to complete the installation of
the services, as is done on NS3000/V.
Error Messages: NS3000/V to NS3000/XL
To learn about NS3000/XL error messages and recovery procedures, refer to
the NS3000/XL Error Message and Recovery Manual (P/N 36920-90004).