HP 3000 Manuals HP 3000 Manuals
Monitoring HP Desk
An important part of the day to day running of HP Desk is monitoring the
system.
There are a number of measures which exist to allow monitoring of the
status of various activities. These can be used along with other
troubleshooting facilities (see Chapter 23 ) to ensure the product is
running efficiently:
* Console Reports
* Console Messages
* General Delivery
* MAILMAINT Reports
* Desklog Reports
Console Reports
The following operator commands display reports on the system console:
* MAILSHOWUSER
* MAILNODEREPORT
* MAILSHOWNODE
* MAILROUTEINFO
Use the MAILSTATUS command to check on the status of the jobs currently
running under the Supervisor. These reports are particularly useful for
checking on mail build up or lost messages. If your users are sending
messages which are not being received, use the MAILROUTEINFO command to
see what routes are configured to the affected mailnode.
See Chapter 20 for further details.
Console Messages
During HP Desk operations messages are displayed on the system console
giving information about:
* Requests to the Supervisor to start or stop various HP Desk
programs.
* Mailroom start up and shutdown.
* Transport system start up and shutdown.
* General start up and shutdowns, for example with FSC.
* Attempt to open a line to a remote computer by the Master Truck.
* Line close information by the Master Truck.
* Slave Truck log on and log off from a remote computer.
* Sign on and sign off by an HP Desk user.
* Maintenance and recovery status messages.
* Garbage Collector (Shredder) start up and shut down
* NewWave Mail and AdvanceMail start up and shut down if installed.
It is always a good idea to log the console messages. If something goes
wrong, you have a log of the console messages produced immediately
before, during, and after the problem occurred.
All messages produced by HP Desk appear on the system console by default.
You can use the HP Desk Configurator to switch off the reporting of
informational or warning messages to the console.
All messages are also written to a file or device which can be used to
produce a printed copy. This is usually the $STDLIST file for the
program or, for programs like the Master Trucks that run in their own
background jobs, the Job List File. The printed copy is not available to
you until you issue a MAILMANOFF, MAILOFF or MAILSHUTDOWN command.
Warning messages are always reported in the printed copy but you can use
MAILCONFIG to suppress Informational messages.
The Slave Trucks work slightly differently. They use a deferred spool
file called SLAVELOG as their printed copy file. Informational messages
produced by Slave Trucks are not written to SLAVELOG. This is because a
large number of Slave Trucks may be started on a busy machine and so an
unacceptably large number of informational messages could be produced.
General Delivery
General Delivery at each mailnode requires monitoring at frequent
intervals. You should check the General Delivery's In Tray at least once
a day. You could set up a UDC using the NEWMAIL command to do this.
Messages usually arrive at General Delivery because:
* The intended recipient is not configured as an HP Desk user.
* The sender has typed the recipient's name incorrectly.
* The sender has typed the recipient's address incorrectly.
* The sending machine's configuration is incorrect.
Any user in the message Distribution List to whom HP Desk could not
deliver the message is highlighted by >.
For example:
To: > Martin DENT/EUCORP/LE
Once you have found out who the intended recipient is:
* Try to forward the message to the intended recipient in the usual
way. Before you do add a note to let the recipient know why HP
Desk could not deliver the message (for example the name was
spelled incorrectly).
* Print out any message which you cannot forward. Assuming that the
problem is not due to bad configuration, reply to the sender
explaining that the recipient is not an HP Desk user and they
should send a hard copy in future. If there is more than one
person HP Desk did not recognize, you can use the BURST command to
print a copy for each of them. See Chapter 19 for further
details.
* Once you have dealt with any messages in the In Tray, delete them.
Whenever the Mailroom is unable to deliver mail to the intended recipient
on its mailnode, the Mailroom sends an explanation to the originator of
the "lost" message. Situations in which an explanation is sent include:
* One or more addressee's name is unknown to the Local Database.
This may be because that person is not configured as an HP Desk
user or the sender has spelled the name incorrectly.
* When an addressee is unknown and the message has to be destroyed
because it is marked Private and therefore cannot be delivered to
General Delivery.
* When the Maintenance job reports the presence on the MERROR file
of a message that is too big to be accepted into the database.
Desklog Reports
A Desklog is an error report which is produced when an HP Desk program
encounters an error for which there is not an existing error message.
The Desklog is produced as the program attempts to close down tidily.
The Desklog is generated as a deferred spool file.
If HP Desk encounters such a problem while performing a task for a user,
a message appears on the user's screen telling them that HP Desk cannot
complete this task, that a Desklog has been produced, and that they
should contact their HP Desk Administrator. You should log on as that
user to see the list of spool files. You should type the SPOOK command
in MPE/V, and LISTSPF in MPE/XL. You will see a deferred spool file
called DESKLOG containing details of what has gone wrong. It is a good
idea if you encourage users to write down what they were trying to do
when the problem occurred. Have this information to hand if you have to
contact Hewlett-Packard. It will make analyzing the problem easier.
Not all Desklogs are about internal HP Desk problems. For example, if a
user doesn't have the capability to save a file and tries to, a Desklog
is produced. This might be an indication that some of your users have
insufficient capabilities to perform their jobs.
Other conditions for which Desklogs are produced are:
* Attempts to access a device which is currently unavailable.
* Data communication errors.
* Terminal parity errors.
* File System errors.