HP 3000 Manuals

HP DeskManager Administration

HP Desk Organization 

HP Desk has a hierarchical organization.  Each level is made up of units
which are subdivisions of the units in the level above.  The
organizational structure starts at the geographical location of the HP
3000 running HP Desk and branches and subdivides down through
increasingly more specific levels to specific users.

When you configure your HP Desk system, you specify a code and a name for
each organizational level.  Codes are mandatory because they are HP
Desk's method of recognizing and addressing the different parts of the
system you build.  Names are optional and benefit users who use the
Directory.  To make an effective Directory, use names which are
meaningful and informative.

Whatever HP Desk structure you decide upon, the basic structure remains
the same.  The following diagram shows this hierarchy.


          HP Desk Organizational Structure 

Computer Name 

HP Desk requires you to specify a name for the computer it will run on.
Use any name of up to 8 characters, as long as it does not contain any
embedded spaces.  For example, R2D2 and NEWYORK are both valid names but
VAN GOGH isn't.  It is a good idea to give your HP 3000 a meaningful
name, perhaps the town or city it is situated in.  This becomes more
important when you are planning an HP Desk network.

Country 

The HP Desk organizational structure starts with the geographical
location of the HP 3000 which HP Desk is installed on.  This is usually
the country the computer is in.  However if you know that your system
will never expand beyond a single machine, or beyond the boundaries of
your country, it could be the town or city the computer is in.  Whichever
you choose, the HP Desk locations you configure (the next level of
organization down) will be associated with the geographical location.

The country code can be anything up to 8 characters and the country name
can be anything up to 36 characters.  Make the country name meaningful.

For example, at Pharaoh, they may choose USA as the country code, and the
country name United States of America.

Locations 

A location is the general address for a group of HP Desk users.
Generally those users have something in common, for example they all
perform a similar function within their organization.

Each location is described by a 6 character code and a 28 character name.

   *   The location code is the essential part an HP Desk address, as HP
       Desk works with it.  Each location code given to each location
       must be unique, even though it may reside on the same computer.

   *   The location name is an optional parameter used to help a user
       looking for a particular address.  It is useful to describe both
       where and what the location is.

For example, Pharaoh may choose to use USCORP as the location code, and
CORPORATE HQ, NEW YORK as the location name.


            

In our example, the HP Desk Administrator has decided to put the
Corporate Headquarters and the Manufacturing Division onto the HP Desk
system as separate locations.  The main reasons for this are:

   *   The Corporate Headquarters and the Manufacturing Division are
       separate groups with completely different functions.

   *   When the Pharaoh Company buy an HP 3000 for the factory, the
       manufacturing location, complete with all of its users, can be
       moved onto the new computer without any loss of information, using
       the Mailutil Program.  If the two locations have always been
       separate, no change of mail address will be necessary, so users
       will not be aware that anything has changed.  Furthermore, if the
       New York HP 3000 was part of a network, the acquisition of the
       second machine will not require any changes to the configuration
       of any computer in the network except the original New York
       machine if all of the mail to, from and within the USA is routed
       through that computer from the start.  The idea of routing mail
       through a network is covered in Chapter 6 .

The Pharaoh HP Desk Administrator has chosen the following location names
and codes:

               Location code                Location Name 

USCORP                                      CORPORATE HQ, NEW YORK
MANF1                                       NEW YORK MANUFACTURING PLANT

Sublocations 

Sublocations represent a group within a group and exist on locations.  A
location and a sublocation code together are referred to as a mailnode.
Sublocations are identified by:

   *   Sublocation code (two characters and mandatory).

   *   Sublocation name (28 character name and optional).

The sublocation code is used by HP Desk to locate users and is mandatory.

Examples of sublocation codes used at Pharaoh could be 01 or AD

Examples of sublocation names used at Pharaoh could be Legal or
Administration.  Use sublocation names that help users identify the
groups easily.

It is possible to configure more than one sublocation for each
location--providing each sublocation code for each sublocation is unique
for that location.  While it isn't possible to have two sublocations both
with the code /AD on the same location, two different locations can have
sublocations which have the code /AD.

If HP Desk is running on a single computer, as in our example, the
simplest arrangement is to have a single location and a single
sublocation.  However, you might decide to have more than one location,
each with several sublocations.  This allows you to separate departments
out for accounting purposes and gives you a system which is more flexible
and easier to expand at a later date.

In the Pharaoh example, both the Corporate Headquarters and the
Manufacturing Division have two departments to put onto HP Desk.  Each
one is a separate group with a different function.  The Administration
department and the Legal department will be sublocations on the USCORP
location, while the Purchasing department and the Production Control
department will be sublocations on the MANF1 location.  The sublocations
will be identified as follows:

          Location                 Sublocation Name             Sublocation Code 

USCORP                       Administration               AD
                             Legal                        LE

MANF1                        Production Control           PC
                             Purchasing                   PH

Tailoring HP Desk to your Organization 

The combined location and sublocation (for example, USCORP/LE) is called
a mailnode.  As any given combination of location code and sublocation
code can only occur once within an HP Desk system, the mailnode
represents a unique address for mailing purposes.

To build a single HP Desk system, you configure the:

   *   Locations
   *   Sublocations
   *   Local users

When a message arrives for a local mailnode HP Desk delivers the message
to the recipient, if they are configured as a user in the Local Database.

The Pharaoh Pilot Scheme Draft Report 

The Pharaoh Company set up a team to look at ways in which they could
best implement their single HP Desk system.  Here is their first draft
report documenting the various options.

Option A--The entire site on one HP Desk mailnode.

Choosing Option A means that both the Corporate Headquarters and the
Manufacturing Division exist on the same mailnode.

The benefits are:

   *   Ease of configuration of users when they change department.  As
       all users are on the same mailnode, the configuration does not
       need to change when someone moves department.

   *   Ease of access of information--As the HP Desk Notice Board, cover
       the entire site all users have easy access to information on the
       Notice Board.  Administration of the Notice Board is central, and
       thus easy to manage.

The issues are:

   *   Difficult to address a message to a particular department unless
       you know the names of people in that department.

   *   There will only be one General Delivery for the entire site.  This
       means that to resolve undelivered mail, the HP Desk Administrator
       needs to know the names of everyone on the site.

Option B--Many Locations and Sublocations.

Each department has their own location, and teams within that department
each have their own sublocation.  For example, the legal department could
be a location and the teams which deal with contracts and patents could
be sublocations on that location.  Choosing Option B means that users in
different teams are on different mailnodes.

The benefits are:

   *   Easy to locate users within departments.

   *   Easy to ensure that only relevant messages are passed onto the
       particular team or division.

   *   Best fit solution for a large one system HP Desk installation.

The issues are:

   *   Higher cost of decentralized maintenance of Notice Boards.

   *   More changes to configure on the Local Directory, when users move
       departments.

   *   Upgrading to a network solution means changing the local HP Desk
       structure, and disrupting users.

Option C--Functions represented by a Location.

A function could be represented by a location within a site and a
department could represent a sublocation within that function.

Choosing Option C means that each mailnode represents a specific
department.

The benefits are:

   *   Ease of locating users.  It is easier for users to search the
       Directory to find the address of someone within a specific
       department at a particular site.

   *   Decentralized administration.  Someone from each department can be
       assigned to administer General Delivery.

   *   Access of information.  Users can set up shared folders with
       people in their departments.  This will help them in their
       day-to-day work and will save on disk space.

This is what the HP Desk Administrator in our example has decided to do.
For example, /LE and /AD are both sublocations on the USCORP location.
The issues are:

   *   The configuration needs updating every time a user moves
       department.

   *   Decentralized responsibility for running and maintenance of HP
       Desk.

At Pharaoh they decide on Option C as the best option to start with.

Users 

After specifying country, location and sublocation information, on your
single HP Desk system you specify the local user information:

   *   Who is on the mailnode.

   *   What access rights they use.

   *   How much disk space they use.

   *   Whether they have special access rights.


NOTE  What your users are allowed to do directly impacts the size of your
      database.


Access Rights 

One of the things you specify when building your HP Desk system is
exactly what an individual user can do, such as:

   *   Read and delete items
   *   Create, edit and mail items
   *   Copy and file items
   *   Use the Calendar/Diary area of HP Desk
   *   Automatically file incoming and outgoing messages
   *   Be able to execute MPE commands from within HP Desk

The more users who create items, copy items, and so on, the more disk
space is used.  Users with autofile capability require more disk space.

Capability Groups 

You specify which, if any, capability groups each user belongs to.  When
you define capability groups, think about which groups within your
organization need the same capabilities to perform their jobs, or which
people work together on a regular basis.  The subject of capability
groups is covered more fully in Chapter 7 .

Disk Space Limits 

As HP Desk Administrator you can control the amount of disk space used by
imposing limits on the amount of information a user can retain in the
Work Area or the Filing Cabinet.  The default Work Area and Filing
Cabinet for all the users on the HP Desk system are set on the Local
Control Data screen.  If you don't give a value for the default limit, HP
Desk assumes that every user has unlimited space available within the
confines of the size of the database.

You can also set limits for individual users which override the system
limits.  These can be higher or lower than the system limits.

User Naming Conventions 

In HP Desk all users, regardless of their nationality, are addressed in
standard English using the USASCII character set.  If you are expecting
your HP Desk system to extend into places where other languages are
spoken, take account of users' preferences for being addressed in their
native language.

HP Desk allows you to include a Local Name, where required, when
configuring user information.  If a Local Name is configured, it will
replace the USASCII form of the user's name that is usually displayed
whenever the user signs on to HP Desk.  This can be in any character set
recognized by the local computer and terminal.

AdvanceMail and NewWave Mail Users 

If you a planning to run AdvanceMail or NewWave Mail as part of your HP
Desk system, you should be aware of the following:

If you will be using the Asynchronous version, each user will require an
MPE username and account in order to log onto the HP 3000.

AdvanceMail and NewWave Mail users might not be familiar with the HP 3000
and the procedure for logging on.  The file LOGON.HPD is provided to log
on users automatically.  When users first install AdvanceMail or NewWave
Mail on their personal computers, they have to edit this file to include
the MPE logon name and account which you have provided for them.

With NewWave Mail and AdvanceMail version A.02.00 or later, users are
supplied with sample files that, in addition to logging a user onto the
HP 3000, also establish the connection to the HP 3000.  The files will
need to be edited before they can be used.  Detailed information about
these connection method files will be found in the manuals AdvanceMail/PC 
Technical Guide and NewWave Mail Technical Guide.

If users do not need to log on to the HP 3000 for any other reason, it is
advisable to get a username and account set up just for personal computer
users to log on to.

   *   If you will be using the LAN version, you will need to have
       sufficient LAN virtual terminal devices configured to support the
       PC users.  This is because the AdvanceNet Monitor starts a virtual
       terminal session for each AdvanceMail user who connects to the HP
       3000.  See the Network Manager Reference Manual for details of how
       to configure a virtual terminal (TYPE = VTERM).

MPE/iX 5.0 Documentation