HP 3000 Manuals HP 3000 Manuals
MAILMAINT
The HP Desk Maintenance job (MAILMAINT) performs several functions which
ensure the integrity of the databases. It checks several elements in the
database for any corrupted items, reclaims space by deleting the contents
of users' Waste Baskets and reports any messages which might have been in
transition when the Maintenance job started. Once it has performed these
activities, it produces a series of reports on the status of the
databases (see Chapter 21 ).
The Maintenance job is in fact three separate jobs:
* The first job logs off users, shuts down HP Desk, and then
rebuilds the communications files.
* The second job stores the databases and associated files.
* The third job performs garbage collection, checks the structure of
the databases, produces reports, recalculates the sizes of users'
Filing Cabinets and Work Areas, and starts up HP Desk again.
As each job finishes, it streams the next one.
________________________________________________________________________
| |
| How to run the Maintenance job: |
| |
| 1. Load a back-up tape or cartridge on the tape drive. |
| |
| 2. Type MAILMAINT. |
| |
| 3. Reply to the request to load a tape. It may take several |
| minutes for this request to be displayed once you issue the |
| Mailmaint command (perhaps as much as 30 minutes on a busy |
| system), because it has to log users off and perform a shutdown|
| of the necessary processes. |
| |
| 4. Load additional tapes as necessary. |
________________________________________________________________________
The Mailmaint command will log off any HP Desk users so that no-one is
accessing the HP Desk databases when it performs the maintenance
activities. Remember that NewWave Mail, AdvanceMail and any applications
that utilize the HP Desk Intrinsics will not receive the messages warning
them that they should log off from HP Desk. The Mailmaint job may
alternatively be scheduled to run at predetermined times automatically.
How to Switch out the Garbage Collection Phase from Mailmaint
If you have HP DeskManagerPLUS installed and intend to utilize the Bin
Emptier and Garbage Collector facilities then you can request that the
garbage collection phase of Mailmaint is skipped. As already indicated,
this will significantly reduce the time for the job to complete. Do this
as follows:
________________________________________________________________________
| |
| How to Switch Out of the Garbage Collection Phase: |
| |
| 1. Type MAILCONFIG. |
| |
| 2. Select the System Menu, and then the Garbage Collection |
| screen. |
| |
| 3. At the question Do you want garbage collection during Mailmaint|
| type N and press Modify. |
________________________________________________________________________
When Mailmaint next runs it will perform all the tasks indicated above
except for waste bin emptying garbage collection and structure checking.
Running Mailmaint Concurrently with User Sessions
All of the Mailmaint activity except storing and rebuilding of certain
files can, if required, take place while users are logged onto the user
interface. To minimize the time that the HP Desk user interface is
available, you can change Mailmaint so that it issues the equivalent of a
MAILUSERON command once the store phase has been completed. Users can
then log back onto HP Desk while Mailmaint completes the remainder of its
tasks.
NOTE Other components of HP Desk (for example the Mailroom and the
transport system) will remain disabled until Mailmaint completes
its processing.
This facility is likely to be of interest to users of standard HP Desk,
on whose systems Mailmaint performs the Waste Basket emptying and garbage
collection. To allow concurrent running of Mailmaint with user interface
sessions use a text editor such as TDP/3000 to change the CONCURRENT JCW
in MAILMNT2.MAILJOB.HPOFFICE to equal on. The JCWs are towards the front
of the job and are preceded by explanatory comments. When you run the
Maintenance job now, the first job will run as usual, warning any users
to leave HP Desk and then logging off anyone who does not do so. Once
the second job has completed, the user interface is enabled and you can
inform users that HP Desk is available again.
If you decide to allow concurrent maintenance, it is a good idea to run
the Maintenance job at a time when few people use HP Desk. This is
important because if large numbers of people log back onto HP Desk after
the store job has completed:
* It will take the Maintenance job significantly longer to complete
the rest of the maintenance tasks.
* Users will find that HP Desk will take longer than usual to carry
out commands.
If the Maintenance job fails after the store job has been completed, you
will have to restore the databases using the backup copy which has just
been made. If you users have done any work since they logged back onto
HP Desk, it will have been lost.
If you intend to incorporate the Mailmaint run in your daily backup
procedures, then the store of files by the second Mailmaint job is
unnecessary. Backing up of the HP Desk databases and associated files
are discussed in a later section. You can modify the job to
skip the store by setting the STOREDATABASES JCW in the file
MNTSTORE.MAILJOB.HPOFFICE to off. If this is done, the next tine that
Mailmaint is run, the second job will have no effect other than to
initiate the third job.
NOTE Do not attempt to alter the maintenance jobs unless you have both
programming and MPE experience.
For more details on customization of Mailmaint, refer to the MAILMAINT
command in Chapter 20 .
Security Measures
When first installed, all three jobs execute as MGR.HPOFFICE. The store
job requires OP capabilities to run because it has to handle privileged
files. To allow the store job to work properly, MGR.HPOFFICE is given OP
capabilities when HP Desk is installed. If you don't want this user to
have such wide-ranging capabilities, you can move the store job to
another user and account (OPERATOR.SYS, for example) which already has OP
capabilities.
Once you have moved the store job, you must edit the first two lines of
the Maintenance jobs to reflect the new group and account names, as well
as the passwords. Comments detailing which lines to change are
included in the job stream files MAILMAIN.MAILJOB.HPOFFICE and
MNTSTORE.MAILJOB.HPOFFICE.
NOTE Do not attempt to alter the Maintenance job unless you have both
programming and MPE experience.