Network Statistics Reports [ HP DeskManager Administration ] MPE/iX 5.0 Documentation
HP DeskManager Administration
Network Statistics Reports
If your HP Desk system is part of a larger network, you can use the
network statistics reports to monitor the way it is running within that
network. The reports will help you to:
* Monitor messages to, from, and through your computer.
* Spot potential bottlenecks in the system.
* Pinpoint the cause of delays in the delivery of messages.
* Allocate your data communications charges both amongst your own
departments but also amongst the computers which route messages
through your machine.
* Determine how much individual users are making of the system.
You can also access the network statistics information programmatically
to use it with your own applications, such as billing programs. See the
HP DeskManager Customization manual for further details.
The reports that will supply you with network statistics are:
* User Statistics Report.
* User Mail Statistics Report.
* User Remote Mail Statistics Report.
* Incoming Mail Statistics Report.
* Outgoing Mail Statistics Report.
* Computer Statistics Report.
* Availability Statistics Report.
Enabling Network Statistics Reporting
________________________________________________________________________
| |
| |
| How to produce network statistics: |
| |
| 1. Turn on the network statistics by editing the STATISTICS JCW |
| in MAILMNT2 to equal on. |
| |
| 2. Run the Maintenance job using the MAILMAINT command. |
| |
| 3. When you want to print off the reports, type MAILSTREAM |
| STATSREP at the colon prompt to print off the network |
| statistics reports. |
| |
________________________________________________________________________
NOTE The network statistic facility will run only on the last output
from the Mailmaint job and log records to AUDITFIL and STATSFIL
produced since that time. That is, it will not be possible to
obtain meaningful results from these reports if the AUDITFIL and
STATSFIL have been switched since the last Mailmaint. If the
Mailmaint is only run weekly, you should ensure that the AUDITFIL
and STATSFIL are sufficiently large enough to accommodate all the
records produced over that period.
Altering the Network Statistics Files
The network statistics reports are produced by three jobs in
MAILJOB.HPOFFICE:
MAILMNT2 This is the third job in the HP Desk Maintenance
job which produces the raw data which appears in
the network statistics reports.
STATSCOM This job builds the output files in which the
individual network statistics reports are stored.
It then takes the raw network data and compresses
it to produce the network statistics reports. It
is streamed automatically by the Maintenance job.
STATSREP This job prints out the network statistics reports.
By editing these jobs you can specify which, if any, of the network
statistics reports are produced.
You can also alter the jobs to suit the needs of your organization. For
example, how long a period do you want the reports to cover: a day, a
week, a month? The length of time, together with the volume of mail
which travels to, from, and through your computer, determines how big the
files in which the reports are stored must be. If you decide that your
reports will cover a two week period, you will need larger files than if
you decide on a weekly reporting period. Similarly, if your computer is
the hub machine in a network, you will need larger files than if your
computer only transmits messages to and receives messages from one
computer.
You can alter the size of any of the temporary or permanent files by
editing the appropriate JCW in the relevant job;
* The seven build lines in the STATSCOM job control the sizes of the
output files which the network statistics are stored in.
The default size is 1024 sectors. However, you can alter the size
of each of the output files by changing the figure immediately
following DISC=. You will need to know about MPE file structures
to do this.
* You can alter the size of each of the temporary files used by
STATSCOM by changing the number at the end of each of the FILESIZE
JCWs.
* The DELETEFILES JCW in the STATSREP job, determines whether the
compression files are purged and rebuilt when the network
statistics reports are printed off. If you just want to print out
the network statistics reports in the middle of your reporting
period, set this JCW equal to off. This allows you to print off
the reports for the period to date without the files being purged
and rebuilt afterwards.
If you make this a permanent change, the network statistics for
the next reporting period will be appended to the network
statistics for this period. This means that the output files will
be continually growing and will become full at some point.
The default is on, which means that the output files are purged
after you print off the reports and new ones are created.
Editing The Jobs
If you want to change the network statistics reports, you have to edit
the jobs which produce them.
You can edit the network statistics jobs in the following ways:
* The STATISTICS JCW in MAILMNT2 determines whether or not network
statistics are produced. Setting this to on enables the
production of network statistics.
* The STATSREPORT JCWs in the STATSREP job specify whether each of
the network statistics reports should be printed. The default is
on, which means that particular report will be printed. If you
don't want a particular report printed, edit the line for that
report to read off.
* The following lines in the STATSCOM job control the size of the
output files which the network statistics are stored in:
!build user.mailstat.hpoffice;rec=-128,,,ascii;DISC=1023,8,1
!build usermail.mailstat.hpoffice;rec=-128,,,ascii;DISC-1023,8,1
!build userrem.mailstat.hpoffice;rec=-128,,,ascii;DISC=1023,8,1
!build nodein.mailstat.hpoffice;rec=-160,,,ascii;DISC=1023,8,1
!build nodeout.mailstat.hpoffice;rec=-128,,,ascii;DISC=1023,8,1
!build compstat.mailstat.hpoffice;rec=-128,,,ascii;DISC=1023,8,1
!build progav.mailstat.hpoffice;rec=-128,,,ascii;DISC=1023,8,1
By altering the figure immediately after DISC=, you can change the size
of the file. Do not attempt to do this unless you know about MPE file
structure.
* Each of the following lines controls the size of one of the
temporary files used by the compression program STATSCOM:
!setjcw tempuserfilesize = 2047
!setjcw tempnodeoutfilesize = 2047
!setjcw tempnodeinfilesize = 2047
!setjcw tempcompufilesize = 2047
!setjcw tempusermailfilesize = 2047
!setjcw tempworkfilesize = 2047
!setjcw templocalnodefilesiz = 2047
By altering the value of a particular JCW, you can alter the size
of the file it controls. It may be necessary to alter the size of
the temporary file used by STATSCOM if it is to process large
Audit and Stats files.
* Each of the following lines in STATSREP job specifies whether or
not the network statistics reports should be printed.
!setjcw compstatsreport = on
!setjcw nodeuotstatsreport = on
!setjcw nodeinstatsreport = on
!setjcw userremstatsreport = on
!setjcw usermailstatsreport = on
!setjcw userstatsreport = on
!setjcw progravstatsreport = on
The default is on, which means that particular report will be
printed. If you don't want a particular report printed, edit that
line to read off.
* Setting the DELETEFILES JCW to off, allows you to print off the
reports for the period to date without them being purged and
rebuilt afterwards. If you make this a permanent change, the
network statistics for the next reporting period will be appended
to the network statistics file for the next period. This means
that the output files will be continually growing and will become
full at some point.
The default is on which means that the output files are purged
after you print off the reports and new ones are created for the
next reporting period. If you find that a single reporting period
fills the report files, you can edit the STATSCOM job to increase
the size of the files that are built by the BUILD command
contained in that job.
User Statistics Report
This report lists the amount of disk space being used by HP Desk users.
For each user, the size of their combined Trays, their Work Area, and
Filing Cabinet is shown. The number of times a user has logged on is
also included.
This report is produced each time you run the Maintenance job and covers
the period since you ran it last. Each report is appended to the last
one until you run STATSREP. This means that if you run the Maintenance
job every day and choose to print off the network statistics reports
every week, the User Statistics report will contain five sets of data.
By comparing the reports, you can see the change of size in each users'
Trays, Work Area, and Filing Cabinet over a week.
The combined Tray size is a measure of the number of sectors taken up by
each users' In Tray, Out Tray Pending Tray and List Area.
All sizes are measured in the number of sectors taken up.
__________________________________________________________________________________________________________________
| |
| |
| HPDESK Network Statistics - User Statistics Report. Computer:- NEWYORK |
| |
| Combined No Daily |
| MAILNODE User Name Work Area Size Filing Size Tray Size Sign Ons |
| USCORPAD BINFORD,JOEL 1205 2015 0 3 |
| USCORPAD DELIVERY,GENERAL 0 0 0 1 |
| USCORPAD EATON,SANDY 936 3123 0 2 |
| USCORPAD PAICE,CLARE 1125 1907 69 1 |
| USCORPAD YANO,BOB 2019 4012 624 1 |
| USCORPLE BENTHAM,LIZETTE 2448 5244 424 3 |
| USCORPLE CARLSON,KRISTA 903 3172 513 3 |
| USCORPLE DELIVERY,GENERAL 0 0 0 1 |
| USCORPLE PECK,JOANNE 3052 914 63 0 |
| USCORPLE USVOLK,DAVID 4666 6913 150 3 |
| |
__________________________________________________________________________________________________________________
Example User Statistics Report
User MailStatistics Report
This report shows how many messages have been sent by each user. This
total is split over Urgent and Normal mail. The number of messages sent
with the acknowledgment set to Transmitted, Received, Delivered, Read,
and Reply is also shown.
This report also gives the average number of destinations and recipients
which each user sent messages to during the reporting period. This gives
you an indication of how widely distributed each user's messages are.
For example, one user could send messages to a large number of people at
a single destination (everyone in the Legal Department, say). Another
user might send messages to a large number of people, all of whom reside
at different mailnodes (for example, all of the company's Personnel
Managers).
___________________________________________________________________________________________________________________________________
| |
| |
| HPDESK Network Statistics - User Mail Statistics Report. Computer:- NEWYORK |
| |
| Mailnode User Name No. Messages |-----Acknowledgements---| Ave. No. of Ave. No. of |
| Urg. Norm. Trans RecRead Reply Dests. Nodes Recips. |
| USCORPAD BINFORD,JOEL 1 4 0 0 0 1 2 5 |
| USCORPAD DELIVERY,GENERAL 0 0 0 0 0 0 0 0 |
| USCORPAD EATON,SANDY 0 0 0 0 0 0 0 0 |
| USCORPAD PAICE,CLARE 0 2 0 0 0 0 1 2 |
| USCORPAD YANO,BOB 2 1 1 0 0 3 4 |
| USCORPLE BENTHAM,LIZETTE 0 3 0 0 0 0 0 0 |
| USCORPLE CARLSON,KRISTA 0 5 0 1 0 0 2 6 |
| USCORPLE DELIVERY,GENERAL 0 0 0 0 0 0 0 0 |
| USCORPLE PECK,JOANNE 0 3 0 0 1 0 2 3 |
| USCORPLE USVOLK,DAVID 1 3 0 1 0 1 3 4 |
| |
___________________________________________________________________________________________________________________________________
Example User Mail Statistics Report
User Remote Mail Statistics Report
This report gives details of the number of messages sent by local users
to remote mailnodes. Using this report you can work out how much of your
local data communications costs should be allocated to each of your
departments or cost centers.
For every user, the total size and number of messages is given for each
remote mailnode that the user sent to.
These figures do not include messages sent by your users as a result of
acknowledgment levels set on messages received from remote computers.
___________________________________________________________________________________________________________
| |
| |
| HPDESK Network Statistics - User Remote Mail Statistics Report. Computer:- NEWYORK |
| |
| MAILNODE User Name Sent to Mailnode Total Size No. of Msgs |
| USCORPAD BINFORD,JOEL MANF2AD 62 1 |
| USCORPAD YANO,BOB EUCORPLE 137 3 |
| USCORPAD YANO,BOB MANF3PC 9 1 |
| USCORPLE BENTHAM,LIZETTE MANF2AD 98 2 |
| USCORPAD BENTHAM,LIZETTE MANF3AD 30 1 |
| USCORPLE CARLSON,KRISTA MANF1PH 17 2 |
| USCORPLE PECK,JOANNE SALE2AD 23 1 |
| USCORPLE USVOLK,DAVID EUCORPLE 58 1 |
| USCORPAD USVOLK,DAVID SALE2SF 129 2 |
| |
___________________________________________________________________________________________________________
Example User Remote Mail Statistics Report
Incoming MailStatistics Report
This report shows the volume of mail arriving at your computer intended
for both local users and to be forwarded to remote users.
This report shows:
* The remote mailnodes which transmissions were received from.
* The name of the computer which forwarded the messages to your
computer.
* The number and size of Urgent transmissions which arrived on your
computer for local users.
* The number and size of Normal transmissions which arrived on your
computer for local users.
* The number and size of Urgent transmissions which arrived on your
computer and were through routed to users at remote mailnodes.
* The number and size of Normal transmissions which arrived on your
computer and were through routed to users at remote mailnodes.
* The average, shortest and longest time taken for transmissions to
travel from their senders' mailnodes to your computer. By
examining the amount of time it takes for a message to arrive, you
can assess how efficient the link to a particular computer is.
The number of transmissions are reported because this is a far more
accurate measure of the volume of data communications traffic than the
number of messages sent. If a user sends a message addressed to a number
of different mailnodes, more than one copy of the message may be
transmitted even though only one message is mailed.
In the case of an HP Desk system which uses hierarchical addressing and
the message is addressed to mailnodes which are routed through different
neighboring computers, more than one transmission of the message will be
sent. In the case of a system which does not use hierarchical
addressing, the number of transmissions will be the same as the number of
different mailnodes the message is addressed to.
________________________________________________________________________________________________________________________________________
| |
| |
| HPDESK Network Statistics - Incoming Mail Statistics Report. Computer:- NEWYORK |
| |
| |---------To Local Mailnodes----------| |---------Through Routed---------------| Time Since Posted |
| From Node Last Comp. Urg.Count Urg.Size NormCount NormSize Urg.Count Urg.Size NormCount NormSize Ave. Min. Max. |
| SALE101 SANFRAN 1 203 1 1 0 0 0 0 33 33 33 |
| EUCORPLE LONDON 0 0 0 0 2 56 10 377 309 219 354 |
| MANF2PC LONDON 0 0 0 0 3 85 3 58 161 161 161 |
| SALE102 SANFRAN 3 85 3 58 0 0 0 0 274 274 274 |
| MANF2AD LONDON 2 56 1 23 0 0 0 0 448 278 618 |
| MANF1AD CHICAGO 0 0 0 0 1 10 0 0 524 509 539 |
| EUCORPLE LONDON 0 0 2 17 0 0 0 0 8 7 17 |
| MANF1PH CHICAGO 0 0 9 343 0 0 0 0 12 3 29 |
| EUCORPAD LONDON 0 0 0 0 4 69 9 137 488 263 659 |
| |
________________________________________________________________________________________________________________________________________
Example Incoming Mail Statistics Report
Outgoing MailStatistics Report
This report is similar to the previous one, showing the volume of mail
leaving your computer. The report is split into mail sent by local users
and mail which is through routed from remote mailnodes. The number and
size of Urgent and Normal transmissions shown for both.
Using this report together with the Incoming Mail Statistics Report, you
can work out how much of your data communications costs is due to mail
sent by your own users and how much is due to mail routed through your
computer from remote mailnodes.
This report shows:
* The remote mailnodes which transmissions were sent to.
* The next computer which handled the transmissions from each remote
mailnode.
* The number and size of Urgent transmissions which left your
computer from local users.
* The number and size of Normal transmissions which left your
computer from local users.
* The number and size of Urgent transmissions which were routed
through your computer to users at remote mailnodes.
* The number and size of Normal transmissions which were routed
through your computer to users at remote mailnodes.
The number of transmissions are reported because this is a far more
accurate measure of the volume of data communications traffic than the
number of messages sent. If a user sends a message addressed to a number
of different mailnodes, more than one copy of the message may be
transmitted even though only one message is mailed.
In the case of an HP Desk system which uses hierarchical addressing and
the message is addressed to mailnodes which are routed through different
neighboring computers, more than one transmission of the message will be
sent. In the case of a system which does not use hierarchical
addressing, the number of transmissions will be the same as the number of
different mailnodes the message is addressed to.
________________________________________________________________________________________________________________________
| |
| |
| HPDESK Network Statistics - Outgoing Mail Statistics Report. Computer:- NEWYORK |
| |
| |-----------From Local Mailnodes-----------| |-----------Through Routed---------------| |
| Dest.Node Next Comp. Urg. Count Urg. Size Norm Count Norm Size Urg. Count Urg.Size Norm Count Norm Size |
| SALE102 SANFRAN 0 0 2 2 0 0 0 0 |
| MANF1AD CHIGCAGO 0 0 0 0 1 397 2 2 |
| MANF2PC LONDON 3 355 11 279 0 0 0 0 |
| EUCORPAD LONDON 0 0 1 12 0 0 0 0 |
| SAL2SF LONDON 0 0 0 0 1 34 1 12 |
| MANF2AD LONDON 0 0 0 0 2 18 5 143 |
| MANF1PH CHICAGO 0 0 0 0 1 9 0 0 |
| EUCORPLE LONDON 0 0 0 0 0 0 6 80 |
| SALE2AD LONDON 0 0 1 123 0 0 0 0 |
| SALE101 SANFRAN 2 261 1 13 0 0 0 0 |
| |
________________________________________________________________________________________________________________________
Example Outgoing Mail Statistics Report
Computer Statistics Report
This report gives details of communications between your local computer
and the next computer along each route you have configured. This
includes EFT and FSC gateways.
For each remote computer which your computer is connected to and has
either received messages from or sent messages to, this report shows:
* The total time (in minutes) that the line has been open.
* The number of times the line between the two computers was opened.
* The average, shortest, and longest time which a message was
delayed on your computer while on route to the next computer.
* The number of transmissions received from the remote computer.
* The number of transmissions sent to the remote computer.
If an entry only consists of zeros, it is not printed. This means that
if your local computer has not received messages from or sent messages to
a particular computer during the reporting period, that computer will not
appear on this report.
___________________________________________________________________________________________________________________
| |
| |
| HPDESK Network Statistics - Computer Statistics Report. Computer: - NEWYORK |
| |
| |----Time To Forward----| No. of Messages |
| Computer Line Open Time No. of Line Opens Ave. Min. Max. From To |
| CHICAGO 260 30 15 10 30 30 60 |
| LONDON 687 41 24 16 18 30 60 |
| SANFRAN 140 9 19 7 31 17 9 |
| |
___________________________________________________________________________________________________________________
Example Computer Statistics Report
Availability Statistics Report
This report shows you how long the user interface, the mailroom, and the
Transport Manager were unavailable for.
_______________________________________________________________________________________________________
| |
| |
| HPDESK Network Statistics - Availability Statistics Report. Computer:- NEWYORK |
| |
| Computer UI. Unav Time MR. Unav Time TM. Unav Time |
| NEWYORK 0 17 34 |
| |
_______________________________________________________________________________________________________
Example Availability Statistics Report
MPE/iX 5.0 Documentation