HP 3000 Manuals HP 3000 Manuals
Maintenance Reports
It is important that you look at the maintenance reports when you run the
Maintenance job. Always keep the most recent maintenance reports. If a
problem occurs, there might be something in the past reports which gives
an indication as to the cause of the problem. The summary reports are:
MERROR This report details any database errors which were
encountered while performing the maintenance
activities, for example any datasets more than 85%
full. This report is only printed if any database
errors were encountered.
MERRQUE This is the Error Queue Summary report and it gives
details of messages which cannot be transmitted.
It is only produced if there are any such messages.
MREPORT This is the standard maintenance report produced by
the Maintenance job. It contains a series of
summary reports on different aspects of HP Desk,
such as items in the Local Database, mail nodes,
local users, and so on. Use the MAILREPORT command
to print additional copies.
The summary reports can be quite lengthy but do not be put off by this.
They contain a lot of useful information which will:
* Help you to fine tune your system.
* Let you check on how much your system is being used. Do you need
to expand your database?
* Provide information which maybe needed by your Hewlett-Packard
representative should you need to contact them concerning HP Desk.
There are two job control words in the third Maintenance job which affect
the maintenance reports:
* QUICKLIST - setting this to on suppresses MREPORT
* SHORTLIST - setting this to on causes any lines composed entirely
of zeros to be suppressed when MREPORT is produced.
Reading the Maintenance Reports
This section tells you how to use the maintenance reports to spot
potential problems with your system.
The main Maintenance reports are listed in the following order in this
chapter:
* MERROR report
* Error Queue Summary Report
* Item Summary Report
* Mail Node Summary Report
* Local User Summary Report
* User Statistics Report
* User Diary Usage Report
* Mail Node Statistics Report
* Local Data Set Summary Report
* Global Data Set Summary Report
* Native Data Set Summary Report
* Progress Messages
NOTE The Archive Tape Summary Report and the Catalog Summary Report are
the two maintenance reports which relate to HP File/Library.
If you do not have HP File/Library installed on your system, blank
reports are produced. The HP File/Library Administration manual
has further details.
MERROR Report
MERROR lists the data sets which are more than 85% full and the remote
nodes that have no routes configured to them. It is of use to your
Hewlett-Packard representative should you have a problem with your HP
Desk system.
If the Maintenance job does not encounter any problems with the
databases, MERROR is not produced. This will normally be the case.
However, you should always look to see if MERROR has been produced,
because if it has, you have a problem which requires your, or
Hewlett-Packard's attention.
If the MERROR report refers to corrupted items, look at the Item Summary
Report. This will tell you the number of corrupt basic or composite
items encountered while the Maintenance job was running and how many of
these it was able to patch.
NOTE If your databases have become corrupt, under no circumstances
should you attempt to patch them yourself. Always contact your
Hewlett-Packard representative first.
If the MERROR report refers to one or more data sets being more than 85%
full, look at both the Local and Global Data Set Summary reports. If
this is the case it is likely that the database will need expanding.
The information is arranged as follows:
* Error number
* Error message
* Item number
_________________________________________________________________________
| |
| |
| Error number 1 |
| MITEMCHECK (Prim 104, Aux 44) ==> |
| Could not delete item (probably corrupt) |
| Item number 33670985 |
| |
| Error number 2 |
| MITEMCHECK => |
| ** IMPORTANT please take note **** ERROR ON LOCAL DATABASE |
| Item number 23157145 |
| |
| Error number 3 |
| WARNING - THE NODE DATA SET ON LOCAL HPDESK DATABASE IS 97% FULL |
| |
_________________________________________________________________________
Example MERROR Report
Error Queue Summary Report
If the Transport System is not able to transmit a mail message to another
computer, it adds the message to an Error queue in the Local Database on
your computer. The next time you run the Maintenance job, an Error Queue
Summary Report gives information about messages in the Error queue as
follows:
* Item number
* Error number
* Error message
The header of each Error queue message is written to the spoolfile
MERRQUE.
As soon as the Error queue has been printed, its contents are deleted
from the database to recover space.
NOTE The number of items reported as being processed in the Progress
Messages Report on the Error queue may well exceed those reported
on the Error Queue Summary as being in error. This is because the
Error queue is used as a temporary store for items coming from
other systems, or items being copied from one area to another.
Hence, you may see an accumulation of items not seen in the
maintenance report, which is not an error condition, and is cleared
automatically by the system.
It may be that a message is too big to be transmitted or exceeds the
specified maximum item size on the computer for which it is destined. It
is a good idea to make the limits consistent over all of the machines in
an HP Desk network. You should encourage users not to try to send large
packages (containing a number of lengthy text items, spreadsheets and so
on) because HP Desk may not be able to transmit them. Tell them that if
they send the items separately, the items will be delivered to the
intended recipient much quicker.
The following error messages could appear in the Error Queue Summary
Report:
101 Message not transmitted - maximum transmission count exceeded
A message has exceeded the maximum number of 64 transmissions allowed
over the network. This indicates a fault in the configuration of your HP
Desk network; for example, a loop may have been set up inadvertently.
102 Message too large to transmit - destination database too small
A message has been presented to another computer for onward transmission
and this computer has indicated that its database is too small to accept
the message. In other words the remote computer is configured for a
maximum item size which is smaller than the message you are trying to
transmit.
103 Message too large to transmit - error encountered during
serialization
A message cannot be transmitted because it was too large. A message to
be transmitted must first be copied from the Local Database to a
temporary MPE file. This is called serialization. The end of the file
was encountered on the temporary file before all of the message was
copied. Either the message exceeded maximum allowed, or insufficient
disk space was available.
If the message is to be transmitted by EFT/FSC, other error messages that
could appear in the Error Queue Summary Report are as follows:
104 Message not transmitted - invalid message, reply or ack
105 Message not transmitted - missing distribution list
Messages 104 and 105 indicate internal problems with the operation of the
system, and should be reported to your Hewlett-Packard representative.
106 Message not transmitted - private message
This error will appear if a Private message is sent to an FSC gateway
which is configured to prevent the passage of Private messages. Such
messages are placed on the Error queue, and the event is logged to the
Audit file.
108 Message not transmitted - corrupt (IMAGE chain length/item count
disparity)
A message cannot be transmitted because it has become corrupt and
serialization failed. If this error appears in the Error Queue Summary
Report, contact your Hewlett-Packard representative.
_____________________________________________________________________________________________________________________________________
| |
| |
| HPDESK (B.05.00 ) Maintenance Report Error Queue Summary Report Date 27/07/92 Time 1043 Page # 1 |
| |
| Item # Error # Error Message |
| |
| 608647 102 Message too large to transmit - destinationdata base too small |
| |
| See the error queue file (MERRQUE) for a listing of each item.'*' indicates object could not be displayed. |
| |
_____________________________________________________________________________________________________________________________________
Example Error Queue Summary Report
Item Summary Report
This report tells you how many corrupt items were encountered while the
Maintenance job was running and how many it was able to patch. The
report is only produced if the garbage collection and structure check
phases of Mailmaint are performed. These are activated by setting the
flag in the Garbage Collection screen of Mailconfig. If the option to
switch out these phases has been selected, then this report will be
blank, apart from warning messages to that effect.
The Maintenance job reads all the items in the Local Database and
verifies that they are consistent. That is, it checks that their actual
content agrees with what they are meant to have. This is a useful check
to ensure that the mail items in the Local Database are in order.
The Local Database could have become corrupted due to a system or disk
failure unconnected with HP Desk. This check gives you some assurance
that HP Desk and mail items have not been harmed by such failures.
An Item Summary Report is written to MREPORT after database verification.
This report gives the number of items found to be corrupt, broken down
into seven categories:
* Basic items unsuccessfully deleted.
* Composite items unsuccessfully deleted.
* Items of unknown type unsuccessfully deleted.
* Basic items patched.
* Composite items patched.
* Corrupt basic items.
* Corrupt composite items.
You are advised to restore the database from a backup copy if any of the
item counts are non-zero.
The file MERROR contains further information about corrupt items.
The Item Summary report contains information about the garbage collection
phase as follows:
* Total number of items to start with.
* Basic items successfully deleted.
* Composite items successfully deleted.
* Good basic items.
* Good composite items.
In practice, when an HP Desk user deletes a mail item from a particular
area, say In Tray, only the pointers from that user's In Tray to the item
are deleted. That user may still have pointers to the item from other
areas such as Filing Cabinet, Calendar; and Work Area. Only when all
local users have deleted, from all their areas, all pointers to an item
will the item be removed. It is the job of the garbage collection phase
of the Maintenance job to remove such unwanted items from the Local
Database, freeing space for new items.
If any of the item counts marked with an asterisk (*) is anything other
than zero, you should issue a MAILOFF command and contact your
Hewlett-Packard representative. You might need to restore the databases
from the most recent backup copy.
____________________________________________________________________________________________________________________________________
| |
| |
| HPDESK (B.05.00 ) Maintenance Report Item Summary Report Date 27/07/92 Time 1043 Page # 2 |
| Item Count Explanation |
| 2000 Total number of items to start with |
| 255 Basic items successfully deleted |
| 313 Composite items successfully deleted |
| |
| 0 Basic items unsuccessfully deleted * |
| 0 Composite items unsuccessfully deleted * |
| 0 Items of unknown type unsuccessfully deleted * |
| 0 Basic items patched (IMAGE chain length did not equal HPDESK item count) * |
| 0 Composite items patched (IMAGE chain length did not equal HPDESK item count) * |
| 0 Corrupt basic items (IMAGE intrinsic error) * |
| 0 Corrupt composite items (IMAGE intrinsic error) * |
| |
| |
| 704 Good basic items |
| 728 Good composite items |
| * See the error file (MERROR) for more information. Non-zero counts indicate database should be recovered. |
| |
____________________________________________________________________________________________________________________________________
Example Item Summary Report - 1
When the Item Summary Report is run and there are no users on the system
the following will be true:
T = BD + CD + GB + GC
Where
T is the total number of items to start with
BD is the number of basic items successfully deleted
CD is the number of composite items successfully deleted
GB is the number of Good Basic items
GC is the number of Good composite items
Taking the values from the example table:
2000 = 255 + 313 + 704 + 728
It is possible that this total may not tally if Mailmaint has been run
concurrently with user interface sessions. Do not worry - this is
because users may have logged back onto HP Desk and created and deleted
items.
If the Garbage Collector is not configured to run, then the following
report is produced.
____________________________________________________________________________________________________________________________________
| |
| |
| HPDESK (B.05.00 ) Maintenance Report Item Summary Report Date 27/07/92 Time 1043 Page # 3 |
| |
| No wastebin emptying, garbage collection or structure checks done |
| |
| |
____________________________________________________________________________________________________________________________________
Example Item Summary Report - 2
Mail NodeSummary Report
The Maintenance job examines all the mailnodes recognized by your
computer and prints out the following information for each:
* The mailnode name.
* The mailnode type (remote or local).
* The number of item headers and content sectors belonging to each
mailnode queue: express (not yet implemented), urgent, normal,
and deferred.
* The number of messages mailed.
All mail items on node queues marked for delivery to your computer are
mailed. This count is recorded in the "Posted Messages" column.
A large build up of messages for a mailnode should be investigated. The
main points to check are:
* Configuration of the Mailnode.
* Availability of that Mailnode.
* The Computer name referred to in the Default Route is correct.
* Passwords specified are correct.
Messages are placed on the deferred queue automatically if, for example,
the remote system's database does not have sufficient capacity free. If
messages for a particular node frequently build up on the deferred queue,
both the remote database capacity and availability configuration for the
local computer should be checked.
If the JCW SHORTLIST is defined as non-zero in MAILMNT2.MAILJOB.HPOFFICE,
lines of the report composed entirely of zeros are suppressed.
_____________________________________________________________________________________________________________________________________
| |
| |
| HPDESK (B.05.00 ) Maintenance Report Mail Node Summary Report Date 27/07/92 Time 1043 Page # 3 |
| |
| Mail Node Type Express Urgent Normal Deferred Posted Messages |
| H S H S H S H S |
| USCORPAD Local 0 0 0 0 0 0 0 0 0 |
| USCORPLE Local 0 0 0 0 0 0 0 0 0 |
| SALE1 Remote 0 0 0 0 0 0 0 0 0 |
| MANF1AD Remote 0 0 0 0 0 0 0 0 0 |
| MANF1PC Remote 0 0 0 0 0 0 0 0 0 |
| MANF1PH Remote 0 0 6 11 6 7 0 0 0 |
| EUCORP Remote 0 0 5 10 3 6 0 0 0 |
| SALE2 Remote 0 0 11 21 9 13 0 0 0 |
| MANF2 Remote 0 0 3 8 8 8 0 0 0 |
| |
| Grand Totals 0 0 11 21 9 13 0 0 0 |
| |
| H: number of item headers (each header equals 1 sector) |
| S: number of item content sectors (1 sector equals 256 bytes) |
| |
_____________________________________________________________________________________________________________________________________
Example Mail Node Summary Report
Local UserSummary Report
If a user has more than a few items in their Out Tray, check that they
know how to mail messages.
The Maintenance job goes through all the users recorded as working on
your computer and prints out the following information:
* The name of the mailnode (location code and sublocation code) to
which the user is assigned.
* The user name.
* The number of "item headers" and "content sectors" belonging to
items in the user's In Tray, Out Tray, Pending Tray, Work Area,
List Area, and Filing Cabinet.
Each HP Desk item has an "item header" to identify the item's type,
subject, creation date, and so on. The item header takes one sector of
disk storage space.
"Content sectors" hold the contents of basic items (message text, HP Word
documents, DSG/3000 charts, and so on).
By totaling the number of item headers and content sectors, you have a
measure of how much disk space is being used by each HP Desk user. The
combined number of Item-Header and Item-Content sectors is displayed to
users each time they log onto HP Desk. When you impose either
system-wide or individual disk space limits you are specifying the
maximum number of Item-Header and Item-Content sectors which users can
take up.
The total number of item headers and content sectors for all users for a
mailnode is printed out. A grand total for all mailnodes is also given.
The totals are almost always greater than actual HP Desk database usage,
since one copy of an item can be associated with more than one user, but
is counted once for all of the users.
All messages still in users' Out Trays, marked as MAILED are mailed
again. This is to make sure that all messages are presented for
transmission to the Mailroom despite any failure. The total number of
such "re-posted" messages is recorded at the end of this report.
________________________________________________________________________________________________________________________________________
| |
| |
| HPDESK (B.05.00 ) Maintenance Report Local User Summary Report Date 27/07/92 Time 1043 Page # 4 |
| Mail Node User Name In Out Pending File Work List Line Total |
| H S H S H S H S H S H S H S |
| USCORPAD BINFORD,JOEL 9 27 3 11 3 6 125 521 2 35 10 33 152 633 |
| DELIVERY,GENERAL 0 0 0 0 0 0 2 0 0 0 0 0 2 0 |
| EATON,SANDY 46 152 0 0 0 0 28 136 5 29 1 6 80 323 |
| PAICE,CLARE 56 297 0 0 4 812 0 0 0 0 2 10 62 1119 |
| YANO,BOB 3 10 0 0 0 0 0 0 0 0 2 9 5 19 |
| Mail Node Totals 114 486 3 11 7 818 155 657 7 64 15 58 301 2094 |
| |
| USCORPLE BENTHAM,LIZETTE 0 0 0 0 0 0 2 0 0 0 0 0 2 0 |
| CARLSON,KRISTA 0 0 0 0 0 0 2 0 0 0 0 0 2 0 |
| DELIVERY,GENERAL 12 34 0 0 8 27 88 326 0 0 3 17 111 404 |
| PECK,JOANNE 12 40 0 0 15 52 154 968 0 0 8 36 189 1096 |
| USVOLK,DAVID 0 0 0 0 0 0 2 0 0 0 0 0 2 0 |
| Mail Node Totals 81 411 0 0 17 143 210 960 6 183 14 51 328 1748 |
| Grand Totals 219 971 3 11 47 1040 611 2911 13 247 40 162 933 5342 |
| Number of out tray messages reposted: 0 |
| H: number of item headers (each header equals 1 sector) |
| S: number of item content sectors (1 sector equals 256 bytes) |
| |
________________________________________________________________________________________________________________________________________
Example Local User Summary Report
User Statistics Report
The User Statistics report gives, for each user on each local mailnode
configured, a report on the number of HP Desk messages sent and received
since the Maintenance Program was last run (date and time given in the
Data Set Summary report), and the total number of messages sent and
received since the statistics were last initialized. For a new HP Desk
installation, this will help you identify which users are reluctant to
use the system and who might need further coaching on the advantages of
using HP Desk.
The report shows for each user:
* The numbers of messages sent and received since the last
Maintenance run. These are in the columns headed "C", under
"Sent" and "Received" respectively.
* The cumulative totals of messages sent and received since the
statistics were last initialized. These are in the columns headed
"T", under "Sent" and "Received" respectively.
* The total number of times a user has signed on to HP Desk since
the statistics were last reset.
* The date and time of the last sign on or sign off.
The T counts can be initialized to zero by streaming
MRESET.MAILJOB.HPOFFICE. This job will reset all the T counts to zero,
for both this report and the Mail Node Statistics report. This job
requires exclusive access to the database, for security and speed.
The cumulative total of all messages transmitted to a mailnode (the T
column) since the statistics were last initialized, may decrease if a
user is deleted from a mailnode. This is because the cumulative totals
are obtained by adding the cumulative totals for each individual user.
____________________________________________________________________________________________________________________________________
| |
| |
| HPDESK (B.05.00 ) Maintenance Report User Statistics Report Date 27/07/92 Time 1043 Page # 5 |
| Mail Node User Name Received Sent Total No of Sign On Last Signon/Signoff |
| * C T C T |
| USCORP BINFORD,JOEL 4 12 1 8 20 05/04/92 1605 |
| DELIVERY,GENERAL 0 1 0 0 3 05/04/92 1310 |
| EATON,SANDY 2 6 5 11 22 05/04/92 2007 |
| PAICE,CLARE 3 5 3 10 15 05/04/92 1631 |
| YANO,BOB 6 15 2 5 14 06/06/92 0900 |
| Mail Node Totals 15 39 11 34 74 |
| |
| USCORPLE BENTHAM,LIZETTE 0 5 0 1 3 12/06/92 0857 |
| CARLSON,KRISTA 0 0 0 0 0 12/06/92 1403 |
| DELIVERY,GENERAL User has never signed on. |
| PECK,JOANNE 5 18 6 12 10 12/07/92 0841 |
| USVOLK,DAVID 5 19 6 10 5 12/07/92 1811 |
| Mail Node Totals 15 47 18 30 32 |
| Grand Totals 35 112 31 70 130 |
| *C: count since last Maintenance Program run |
| *T: cumulative total |
| |
____________________________________________________________________________________________________________________________________
Example User Statistics Report
User DiaryUsage Report
The User Diary Usage Report gives, for each user on each local mailnode
configured, a report on the number of Calendar entries and insertions
they have. The earliest date and the latest date for which a user has an
entry are also listed. An entry can be inserted in the Calendar at more
than one date. The "No. of insertions" column includes all the entries
plus any multiple insertions of an entry. You can monitor the usage of
the Calendar facility and identify users who are using large amounts of
storage, from the information listed on this report.
If your databases are short of space, look through this report and note
Min Date for each user. If Min Date is more than a week ago, ask all
users to delete everything in their diaries from Min Date to Yesterday.
If you have HP Schedule installed on your system, you can also use this
report to ensure that all users are entering their appointments in their
Calendars.
_______________________________________________________________________________________________________________________________
| |
| |
| HPDESK (B.05.00 ) Maintenance Report User Diary Usage Report Date 27/07/92 Time 1043 Page # 6 |
| |
| Mail Node User Name No of No of Max Min |
| entries insertions Date Date |
| USCORPAD BINFORD,JOEL 10 10 12/31/92 01/01/91 |
| DELIVERY,GENERAL 0 0 The user's diary is empty. |
| EATON,SANDY 15 20 05/01/92 04/03/91 |
| PAICE,CLARE 7 7 12/12/92 02/08/91 |
| YANO,BOB 11 11 12/12/92 12/08/91 |
| Mail Node Totals 43 48 |
| USCORPLE BENTHAM,LIZETTE 8 11 03/26/92 01/11/91 |
| CARLSON,KRISTA 0 07 The user's diary is empty. |
| DELIVERY,GENERAL 0 0 The user's diary is empty. |
| PECK,JOANNE 0 0 The user's diary is empty. |
| USVOLK,DAVID 2 2 12/08/92 11/21/91 |
| Mail Node Totals 21 21 |
| Grand Totals 72 80 |
| |
_______________________________________________________________________________________________________________________________
Example User Diary Usage Report
Mail NodeStatistics Report
The Mail Node Statistics Report gives, for each mailnode configured for
your computer, a report on the number of messages transmitted to each
mailnode.
The totals are presented according to priority (Express, Urgent, Normal
and deferred). The C column refers to the number of messages transmitted
to a mailnode since the Maintenance job was last run. The T column is a
cumulative total of all the messages transmitted to a mailnode since the
statistics were last initialized.
Streaming the job MRESET.MAILJOB.HPOFFICE resets all the T counts to
zero, for both this report and the User Statistics report. This job
requires exclusive access to the database, for security and speed.
____________________________________________________________________________________________________________________________________
| |
| |
| HPDESK (B.05.00 ) Maintenance Report Mail Node Statistics Report Date 27/07/92 Time 1043 Page # 7 |
| |
| Mail Node Express Urgent Normal Deferred Total |
| C T C T C T C T C T |
| EUSALEAD 0 0 0 0 0 5 0 0 0 5 |
| EUSALESF 0 0 0 2 0 15 0 0 0 17 |
| EUSALETD 0 0 0 0 3 8 3 11 |
| EUSALEVS 0 0 2 4 5 6 7 10 |
| CORPHQAD 0 0 0 0 0 0 0 0 0 0 |
| CORPHQCR 0 0 6 20 12 30 18 50 |
| NYMANFAD 0 0 0 0 0 0 0 0 0 0 |
| |
| Grand Totals 0 0 8 24 20 44 0 0 25 71 |
| |
| C: count since last Maintenance Program run |
| T: cumulative total |
| |
____________________________________________________________________________________________________________________________________
Example Mail Node Statistics Report
Local Data Set Summary Report
The Local Data Set Summary report contains statistics showing:
* The number of entries currently being used in each data set in the
Local Database, and the maximum number of entries.
* The change in the amount of space used since the last Maintenance
job run. This part is applicable to the three data sets that are
used to hold item information.
* The date and time of the two most recent runs of the Maintenance
job.
The information in the Local Data Set Summary Report should be checked to
monitor how full the various data sets are, and at what rate they are
being filled. You can then make a decision as to whether or not you need
to enlarge the Databases.
When a data set is greater than 85% full the entry on the Local Data Set
Summary Report is marked with an asterisk. In addition, a message
appears in the Progress Messages report (see later).
In particular look at the maximum and current sizes for Item-Header,
Item-Structure, and Item-Content data sets. To ensure an efficient HP
Desk system, it is recommended that you keep the size of these three data
sets to 60% of capacity at most, particularly the Item-Header data set.
As the size of a data set begins to exceed 60%, it takes HP Desk an
increasingly longer time to perform tasks because of the way in which
items are stored in the databases by IMAGE.
It is a good idea to monitor the growth of your data sets regularly and
expand the databases before the size of the data sets can affect HP Desk
performance. Details of how to expand your databases are in Chapter 18
. Remember that some data sets, such as Item-Header and Item-Content,
increase to their maximum capacity through HP Desk usage. Others, such
as Local-User and Node, only need expanding when you add users, locations
and so on to your HP Desk system.
If disk space limits (that is limits on the size of users' Filing
Cabinets and Work Areas) have not been introduced, you should consider
doing so if the data sets are growing at a significant rate. If disk
space limits are already set, you should consider gradually reducing
them. However, if you do reduce the disk space limits you should inform
the users first.
____________________________________________________________________________________________________________________________________
| |
| |
| HPDESK (B.05.00 ) Maintenance Report Local Data Set Summary Report Date 27/07/92 Time 1043 Page # 8 |
| |
| Data Set Name Previous Set Usage Current Set Usage Maximum Set Capacity Set Usage Change |
| |
| LOCAL-CONTROL N/A 1 1 N/A |
| LOCAL-USER N/A 16 50 N/A |
| DESIGNATE N/A 7 10 N/A |
| NAME-INDEX N/A 13 50 N/A |
| NODE N/A 3 10 N/A |
| USER-XREF N/A 16 66 N/A |
| ITEM-HEADER 487 487 2503 0 |
| ITEM-STRUCTURE 529 529 2030 0 |
| ****ITEM-CONTENT 985 1384 1500 0 |
| COMPUTER N/A 0 4 N/A |
| ROUTE N/A 0 4 N/A |
| ENTRY-NAME-INDEX N/A 30 150 N/A |
| ENTRY-INDEX N/A 127 500 N/A |
| USER-DATE N/A 68 199 N/A |
| OWNS N/A 120 530 N/A |
| KEYWORD N/A 50 513 N/A |
| MAIL-ITEM-ENTRY N/A 18 100 N/A |
| MAIL-ITEM-SUBJ N/A 91 210 N/A |
| SIMPLE-ENTRY N/A 55 252 N/A |
| INSERTION N/A 299 790 N/A |
| FSC-PROGRAM N/A 0 16 N/A |
| NODE/NODE N/A 0 24 N/A |
| **** DATASET MORE THAN 85% FULL. |
| |
| Date and time of previous maintenance program run: 26/07/92 1040 |
| Date and time of this maintenance program run: 27/07/92 1043 |
| |
| |
____________________________________________________________________________________________________________________________________
Example Local Data Set Summary Report
Global Data Set Summary Report
The Global Data Set Summary Report contains statistics showing the number
of entries currently being used in each data set in the Global Database,
and the maximum number of entries.
The information in the Global Data Set Summary Report should be checked
to monitor how full the various data sets are, and at what rate they are
being filled. You can then make a decision as to whether or not you need
to enlarge the Databases.
When a data set is greater than 85% full the entry on the Global Data Set
Summary Report is marked with an asterisk. In addition, a message
appears in the Progress Messages report (see later).
____________________________________________________________________________________________________________________________________
| |
| |
| HPDESK (B.05.00 ) Maintenance Report Global Data Set Summary Report Date 27/07/92 Time 1043 Page #9 |
| |
| Data Set Name Current Set Usage Maximum SetCapacity |
| |
| COUNTRY 1 2 |
| |
| LOCATION-INDEX 2 5 |
| |
| NODE 3 10 |
| |
| NAME-INDEX 15 100 |
| |
| GLOBAL-USER 26 120 |
| |
| NODE-XREF 3 10 |
| |
| LOCATION 2 6 |
| |
| NODE-NODE-INDEX 1 30 |
| |
| GATEWAY-INDEX 0 5 |
| |
| FOREIGN-INDEX 0 20 |
| |
| FOREIGN-ALIAS 0 20 |
| |
| RESOURCE-INDEX 1 30 |
| |
| RESOURCE 1 10 |
| |
____________________________________________________________________________________________________________________________________
Example Global Data Set Summary Report
Native Data Set Summary Report
Where a Native Database is configured, a Native Data Set Summary Report
will be provided showing the number of entries currently being used in
each data set, and the maximum number of entries.
The information in the Native Data Set Summary Report should be checked
to monitor how full the various data sets are, and at what rate they are
being filled. You can then make a decision as to whether or not you need
to enlarge the Databases.
When a data set is greater than 85% full the entry on the Native Data Set
Summary Report is marked with an asterisk. In addition, a message
appears in the Progress Messages report (see later).
__________________________________________________________________________________________________________________________________________
| |
| |
| HPDESK (B.05.00 ) Maintenance Report Native Data Set Summary Report Date 27/07/92 Time 1043 Page # 10 |
| |
| Data Set Name Current Set Usage Maximum SetCapacity |
| |
| NAME-INDEX 45 150 |
| |
| AL-NAME-INDEX 23 150 |
| |
| USER-XSLATE 49 154 |
| |
__________________________________________________________________________________________________________________________________________
Example Native Data Set Summary Report
Progress Messages
After the Maintenance job completes each phase, a Progress Message is
displayed on the system console. To ensure that these messages are not
lost they are included on the last page of MREPORT.
If any data set on either HP Desk database is over 85% full, a message of
the following form is displayed:
WARNING - THE ITEM-HEADER DATA SET ON THE LOCAL HPDESK DATABASE IS 89%
FULL. PLEASE CONSIDER EXPANDING THE DATABASE.
The first message of the progress messages is "Databases are now locked".
This message is produced when the Maintenance job has got control of the
Databases and has them for exclusive access. The reason for this is that
there can be a delay between storing the Databases and starting up of the
Maintenance job. The message just confirms that everything has been
performed correctly to this point.
___________________________________________________________________________________________________________________________________
| |
| |
| HPDESK (B.05.00 ) Maintenance Report Progress Messages Date 27/07/92 Time 1043 Page # 11 |
| |
| Databases are now locked |
| |
| Error queue processing done (total of 6 items processed) |
| |
| Structure check done (0 corrupt items) |
| |
| Garbage collected (568 items deleted) |
| |
| Mail Node processing done (7 mailnodes) |
| |
| User processing done (14 users) |
| |
| Archive Summary complete (10 tapes found) |
| |
| Catalog Summary complete (114 catalogs found) |
| |
| Local control updated |
| |
___________________________________________________________________________________________________________________________________
Example Progress Message - 1
If the garbage collection and structure check phase of Mailmaint has been
switched out, then the report would look like the following:
____________________________________________________________________________________________________________________________________
| |
| |
| HPDESK (B.05.00 ) Maintenance Report Progress Messages Date 27/07/92 Time 1043 Page # 11 |
| |
| Databases are now open but not locked |
| |
| Error queue processing done (total of 6 items processed) |
| |
| No wastebin emptying, garbage collection or structure checks done |
| |
| Mail Node processing done (7 mailnodes) |
| |
| User processing done (14 users) |
| |
| Archive Summary complete (10 tapes found) |
| |
| Catalog Summary complete (114 catalogs found) |
| |
| Local control updated |
| |
____________________________________________________________________________________________________________________________________
Example Progress Message - 2