Networking Concepts

Address Resolution

 

The centralized theory requires each node on the internet to have the

 

same network directory. This means that every node in the network

 

must have an entry in the network directory. The advantage to this is

 

that you update the network directory in one place, then copy it to the

 

rest of the world. The disadvantage is that network directories for large

 

internets are going to be large.

 

The recommended way to create and maintain your network directory

 

using the centralized method is to assign a single node as the central

 

administrative node. You configure the network directory on this node

 

and then copy it to all other nodes on the network. When the network

 

directory is updated, it is updated on the central administrative node,

 

then copied to the other nodes. This procedure decreases the possibility

 

of incompatible directories. You may want to assign a central

 

administrative node for each network or for the entire internet.

 

The decentralized theory suggests that each network directory be

 

configured individually on each node. The advantage to this is that you

 

can customize the network directory on each node for security purposes

 

using local and global entries. The network directory will also be

 

smaller because it will only contain entries for that particular node.

 

However, updates must be done manually on each node.

 

Copying and Merging Network Directory Files

 

The first time you configure the network directory, an entry for all

 

remote IP addresses must be added manually using the NMMGR

 

screens. After the first network directory is configured, you can use the

 

MPE STORE and RESTORE commands to copy the network directory to

 

other nodes. (This is assuming you have adopted the centralized

 

method of network directory maintenance. If you use the decentralized

 

method, you must always use NMMGR to create and maintain the

 

network directory.)

 

The network directory uses a KSAM file pair. Therefore, when copying a

NOTE

 

directory, be sure to copy both the data file and the key file. The system

 

names the key file automatically using the first six letters of the

 

network directory file name appended with a K. For example,

 

NSDIRK.NET.SYS is the name of the key file associated with the data file

 

NSDIR.NET.SYS.

 

Once a network directory has been established on each node in the

 

internet, you can set up a job stream to automate network directory

 

updates. The MERGEDIR command is part of a maintenance interface

 

provided primarily to support the updating of directories using a batch

 

job. Using this method, a job or series of jobs can be scheduled at

 

regular intervals to copy and then merge remote directories into the

 

local-system directory. See the MERGEDIR and the MAKESTREAM

 

commands in Using the Node Management Services (NMS) Utilities.

Chapter 2

37

Page 36 Page 38
Page 37
Image 37
HP E3000/IX, E3000 MPE/IX manual Copying and Merging Network Directory Files
Page 36 Page 38

E3000 MPE/IX, E3000/IX specifications

The HP E3000 series, particularly the E3000/IX and E3000 MPE/IX, represents a significant milestone in the evolution of business computing, developed by Hewlett-Packard (HP) during the late 1970s and early 1980s. These systems were designed to provide robust, reliable, and efficient operation for mid-sized businesses, leveraging the power of the MPE (Multi-Programming Executive) operating system.

One of the main features of the HP E3000 series is its multitasking capability. MPE/IX allows for multiple applications to run concurrently, maximizing the utilization of system resources. This is particularly beneficial for organizations that require simultaneous access to various business applications, ensuring enhanced productivity and efficiency.

The HP E3000/IX architecture is built on a powerful 16-bit or 32-bit microprocessor, enabling it to handle substantial workloads. The system architecture is known for its modular design, which allows for easy upgrades and customization. This flexibility is essential for businesses that need to adapt to changing demands without overhauling their entire computing infrastructure.

Another notable technology incorporated into the HP E3000 series is its support for a range of storage solutions. The E3000 systems were compatible with various disk drives, providing organizations with options for data storage that matched their performance and capacity requirements. Additionally, they featured advanced data management capabilities, such as built-in backup and recovery systems, ensuring that critical business information remained secure and accessible.

Beyond hardware capabilities, HP E3000/IX and MPE/IX systems provide extensive programming support. They included tools for developing custom applications, with support for languages such as COBOL, BASIC, and FORTRAN. This versatility made it easier for businesses to tailor their software solutions to their specific needs, enhancing operational effectiveness.

Networking capabilities were also a significant innovation of the E3000 series. The systems offered robust support for various networking protocols, allowing for seamless integration with other computing environments. This facilitated communication and collaboration within an organization, as well as with external partners and clients.

In summary, the HP E3000/IX and E3000 MPE/IX systems were pivotal in delivering reliable computing power to mid-sized enterprises. With their multitasking operating system, modular architecture, advanced data management, and programming support, these systems provided an adaptable and comprehensive solution for evolving business needs. The legacy of the E3000 series is evident in how it paved the way for modern enterprise computing, focusing on flexibility, scalability, and efficiency.
Top Page Image Contents