HP 3000 Manuals HP 3000 Manuals
Expanding or Contracting the Databases
When you first create your databases, you only have a general idea of
what size they should be. Once your HP Desk system is running, you will
begin to get an idea of how it is used and how much is used. It is
important that you read the reports produced after the Maintenance job is
run because these tell you about how the various data sets in the
database are growing. See "Monitoring HP Desk" and Chapter 21
for further details about the format of these reports and how to use
them. You might find that the default values that you used when you
initially created the databases are too large for the organization and
you can make the databases smaller. More likely, however, you might find
that HP Desk is used more than you anticipated and the databases need
expanding.
If you are part of a network, remember that you will have transient
information in the databases, in addition to your own user information.
If your HP 3000 is an intermediate machine, or more especially the hub
machine in a network, the databases will contain copies of messages which
have been forwarded onto other computers until the Maintenance job is
run. If more messages are sent through your computer than you
anticipated, or you do not run the Maintenance job regularly, you will
need to expand your databases sooner than you thought.
If HP File/Library is installed on your HP Desk system, you will need to
expand the Item-Header, Item-Structure, and Item-Content data sets in
your databases.
Note that the database password is retained after database expansion or
contraction.
Deciding When to Expand
You need to expand your databases when the data sets become too small for
the requirements of your organization. Some data sets, such as
Item-Header and Item-Content, increase through the day-to-day usage of HP
Desk. As HP Desk usage increases the capacity of these data sets will
have to be increased too. The capacities of these major data sets are
reported to the console at the starting up and closing down of the
Garbage Collector. Other data sets, such as Local-User and Route, will
only need increasing when you increase the size of your HP Desk system
(by adding locations, routes, and so on).
Always expand your database before you need to. Ideally you should
expand if the Item-Header data set exceeds 60% of capacity or if the
Item-Content or Item-Structure data sets exceed 80% of capacity. Use the
Local, Global and Native Data Set Reports to check on the current sizes
of the data sets. If you wait until the MERROR report tells you that one
or more of your data sets is over 85% full, the performance of your HP
Desk system will already have been impaired. This is because the nearer
to capacity your databases become, the longer HP Desk takes to perform
tasks because of the way in which IMAGE structures the databases.
You can check on the current size of the data sets using the
MAILALTLOCSTATS command. This allows you to look at the database
statistic file, LOCSTATS.MAILDB.HPOFFICE, without having to purge the
databases first. You will then have a better idea of which data sets
need expanding.
Facilities Available
HP Desk includes its own facilities for database expansion, however,
these can take some time. You may decide to use other products to
perform the task, such as Hewlett-Packard's DBCHANGE product, or the
non-Hewlett-Packard ADAGER product.
HP Desk Facilities:
Before you expand or contract the databases, you must unload the existing
database contents to tape using the MAILUNLOAD command. If you expand or
contract the databases without unloading the data currently stored in
them, you will lose it. You will need separate tape sets to unload the
databases, one for the Global Database, one for the Local Database and a
third for the Native Database if one is configured. Under no
circumstance should you try to unload both databases onto one tape. For
further details on the MAILUNLOAD command, see Chapter 20 .
_________________________________________________________________________________
| |
| How to Expand or Contract Your Databases: |
| |
| 1. If the existing databases contain data, unload them, using the |
| MAILUNLOAD command. |
| |
| 2. Run the Configurator using the MAILCONFIG command. |
| |
| 3. When the Configurator Main Menu appears, press Expand |
| Database. |
| |
| 4. The Verification Menu appears with the message: |
| |
| The HPDESK Database still exists. Has it been UNLOADed? |
| |
| If you have not unloaded the existing data from the databases, |
| press NO. Leave the Configurator and go back to step 1. If |
| you press YES without first unloading the databases, the |
| existing contents will be destroyed. |
| |
| If you have unloaded your existing databases, or if your |
| existing databases contain no data, press YES. |
| |
| The following messages appear to inform you that the existing |
| databases have been purged: |
| |
| >> Data Base Global has been purged |
| >> Data Base Local has been purged |
| >> Data Base Native has been purged if |
| configured |
| |
| |
| 5. You are now at Database Definition 1. Change the appropriate |
| values and press Record Values. |
| |
| 6. You are now at Database Definition 2 which shows the database |
| size calculated by HP Desk from the values in the last |
| screen. If you are not satisfied with these figures |
| press Previous Screen and adjust the values (You can |
| adjust the values and return to this screen to assess the |
| results as often as you wish). Otherwise, press Record |
| Values. |
| |
| 7. You are now at Calendar/Diary Database Definition 1. Enter |
| appropriate values in the fields provided, or accept the |
| default values shown and press Record Values. |
| |
| 8. You are now at Calendar/Diary Database Definition 2. The |
| values you selected in the previous screen are displayed, |
| together with the results of HP Desk's calculations for the |
| number of users you declared earlier. You can return to the |
| previous screen and adjust the number of ENTRIES and LABELS per |
| user. When you are satisfied with the capacity generated by HP |
| Desk, press Build Database. |
_________________________________________________________________________________
__________________________________________________________________________________
| |
| 9. The Database Report appears. This details the amount of disk |
| space allocated to each component of the database. The report |
| continues over the next two screens, which you can read by |
| pressing Continue. |
| |
| 10. When the Calendar/Diary Database Report appears, press |
| Continue. |
| |
| 11. When the Native Database Report appears, press Continue. This |
| will only happen if a Native Database is in use. |
| |
| After a couple of minutes the following messages appear |
| informing you that the new databases have been created: |
| |
| >> Data Base Global has been created |
| >> ILR is enabled |
| >> Data Base Local has been created |
| >> ILR is enabled |
| >> Data Base Native has been created if |
| applicable |
| |
| >> ILR is enabled |
| |
| 12. If you have adjusted the size of an existing database which |
| contained data, press Exit and use the MAILLOAD command to |
| reload the data into the new database. |
| |
| 13. Once you have reloaded the data, start up HP Desk using the |
| MAILON command. You can now configure HP Desk with any |
| items that would not previously fit into the database if |
| necessary. |
__________________________________________________________________________________
CAUTION Bear the following in mind:
* On no account should you invoke DBUNLOAD.PUB.SYS manually
to unload the databases. This could destroy the
database.
* As the MAILUNLOAD command streams the job to perform a
chained unload to the database, some unusual error
conditions cannot be reported. Check the job listing
carefully before you proceed further and use the
Configurator to expand the databases.
* The Configurator runs the programs DBSCHEMA.PUB.SYS and
DBUTIL.PUB.SYS as son processes. You should remove any
lockwords set on either of these programs before
expanding or contracting the databases. Once the
expansion or contraction has been successfully completed,
remember to replace the lockwords.
Other Database Expansion Features
The fully supported method of HP Desk database expansion is to use the
features within Mailconfig, as described above. However, the ADAGER and
DBCHANGE products can be used to the same effect.
The use of ADAGER and DBCHANGE with HP Desk is supported for database
expansion and for Hewlett-Packard specified activities only. The logical
structure of the databases must be maintained and not altered in any way
through the use of these, or any other supported or unsupported tools.
CAUTION Extreme care must be exercised when using these tools since
their inappropriate use can cause irrecoverable damage to the
logical structure of the HP Desk database and thus the
malfunction of HP Desk itself.
NOTE MAILALTLOCSTATS should be used to adjust LOCSTATS to reflect the
changes where these products have been used to adjust data set
capacities dynamically. However, LOCSTATS is automatically updated
by MAILLOAD/MAILUNLOAD from within Mailconfig.