HP 3000 Manuals HP 3000 Manuals
Organizing an HP Desk Network
The example in Chapter 5 , examined the different levels into which a
single-computer system is organized. In this section we revisit these
levels from an HP Desk network perspective.
Configuring Mailnodes
When you build a HP Desk network, you specify the names of all the
mailnodes on the local computer. Each of the mailnode addresses must be
unique, as HP Desk uses these to locate routes and then users.
Defining the Names of Computers in the Network
In an HP Desk network, you need to configure only the local computer and
the computers it communicates with directly.
Each computer in the network must have a unique name. You should also
make the name something which makes that computer easily identifiable,
perhaps the name of the city or town it is situated in. The computer
name is important in an HP Desk network because although messages are
addressed to people at places, they are routed from, through, and to
individual computers.
In a HP DeskManagerPLUS network you have the option of configuring the
remote computer's IP Address to ensure extra security.
In our example, the Pharaoh Network Co-ordinator has decided that each
computer will have a seven character name which will be taken from its
geographical location. For example, the HP 3000 in New York will be
called NEWYORK, the one in Liverpool will be called LVRPOOL.
Defining Country Names and Codes
Use a naming convention which everyone in the network can easily
understand, when you plan a network. In our example, the Pharaoh Network
Co-ordinator decides that the country code will correspond to the
recognized abbreviation for that country.
For example, the United States will have the country code USA,
Switzerland will have the code SWITZ, and so on.
Locations
In a network each location code must be unique.
It is also possible to have different sublocations of a single location
residing on more than one machine. However, it is not possible to have
one mailnode, (location and sublocation), spread across two computers.
If two or more computers are host to different sublocations of a single
location, they form a local network which is not necessarily part of a
wider network.
In our example, the Network Co-ordinator at Pharaoh decides that each
machine will host one location with the exception of the HP 3000s at New
York, San Francisco, Melbourne and Singapore. As these three facilities
are small sales offices, they will share a location between them. It was
also decided to adopt the naming convention used for the original New
York system throughout the network.
So the Pharaoh Network Co-ordinator decisions are:
* Manufacturing divisions have the location code MANF suffixed by a
number. For example, the manufacturing site in Chicago will be
MANF2 and the one in Liverpool will be MANF3.
* Sales offices have the location code SALE suffixed by a number.
For example, the sales office in Geneva will be SALE2.
* Corporate offices have the location code CORP prefixed by the area
they have control over. For example, the European Corporate
Headquarters in London will be EUCORP.
Sublocations must be unique within the location they are on. However, a
sublocation code can be repeated within the network on separate
locations.
In a local network (for instance a single location spread over more than
one computer) the sublocation codes must be unique within the network.
This means that no two machines in a local network may use the same
sublocation code.
In our example, the individual HP Desk Administrators at the various
Pharaoh Company facilities have looked at the departments which they want
to put on their HP Desk systems and have passed the information to the
Network Co-ordinator. Each of the corporate offices has two departments
to put on their HP Desk systems. Each of the manufacturing divisions has
three. There is a similarity of function amongst the departments which
allows a consistent naming convention to be used.
Type of location Sublocation Name Sublocation Code
--------------------------------------------------------------------------------------
Corporate ADMINISTRATION AD
LEGAL LE
Manufacturing PRODUCTION CONTROL PC
PURCHASING PH
ADMINISTRATION AD
SALE1 has three sublocations: /01 for San Francisco, /02 for Melbourne
and /03 for Singapore. Because some SALE1/03 users will require their
Chinese names to be displayed by HP Desk, a Native Database will be
created on the Singapore computer. This will hold the non-USASCII native
names displayed locally and the corresponding USASCII names used
throughout the network for mailing purposes.
SALE2 will have two sublocations: /SF for the sales force and /AD for
administration.