Configuring the Network Directory

Add Nodes to Network Directory File

Fields

Node name

The name of the node for which you want network

 

 

directory information. The node name field must

 

 

contain a fully qualified node name, in the form

 

 

nodename.domain.organization, when used to add,

 

 

modify, delete, or rename a node.

 

 

The node name field when used with the Prev Page

 

 

and Next Page function keys allows you to browse

 

 

through a specified part of the network directory. You

 

 

can enter part of a node name in this field to designate

 

 

which node names you want displayed. For example, if

 

 

you enter the value NIK, and press the [Next Page]

 

 

function key, the list of nodes will begin with the first

 

 

matching node name, for example

 

 

NIKOLAI.FINANCE.IND, and continue through the rest

 

 

of the alphabet until all node names between the letters

 

 

NIK and Z are listed.

 

Global?

The global/local setting for node name. The acceptable

 

 

values are Y or N. When the Prev Page and Next Page

 

 

function keys are used, only node names whose

 

 

global/local setting matches the value in this field are

 

 

displayed.

 

 

Entries can be configured as either global or local in the

 

 

network directory. Global entries (the default) can be

 

 

merged into other directories using the MERGEDIR

 

 

command. Local entries are not merged into other

 

 

network directories. The local entries are used for

 

 

configuring localized network directory entries, thus

 

 

providing a mechanism to restrict directory data from

 

 

being propagated throughout the network.

 

 

A situation where this type of restriction could be

 

 

useful is when you want to change the configuration for

 

 

users on a single host, but not for everyone else. You

 

 

can configure two network directory entries: one local,

 

 

used by host users, and one global, used by everyone

 

 

else when establishing connections to the host. For

 

 

example, suppose Node A sets up a new link to Node C,

 

 

but Node A does not want other nodes (already

 

 

connected to A) to know about Node C until the new

 

 

link is tested. Users on Node A can configure a local

 

 

entry, which contains information about the new link

 

 

not included in the global entry configured for users on

 

 

other nodes.

 

 

Other uses of local entries include restricting certain

 

 

nodes from communicating with the internet, or being

 

 

able to direct which way to access remote nodes

 

 

depending on your configuration of local entries. When

158

Chapter 11

Page 158
Image 158
HP E3000 MPE/IX, E3000/IX manual Name of the node for which you want network

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.