Novell Home

Nifty Keystroke for the POA

Novell Cool Solutions: Feature
By Tay Kratzer

Digg This - Slashdot This

Posted: 14 May 1999
 

We didn't know we'd lost it, and we have no idea where he found it. But once again, Tay Kratzer, has dug up a little known tidbit about GroupWise. This time he's found a keystroke you can use to turn Diagnostic Logging on and off at the POA.

In case you didn't know, there are three different logging levels for the POA: Normal, Verbose, and Diagnostic. When you're troubleshooting problems on the POA, Diagnostic Logging, can quickly become your best friend. Here's why: With Diagnostic Logging turned on, the POA reports all the databases it's accessing (and just about every transaction you'd ever want to know about). Of course, this detailed logging doesn't come for free. (What does?) It will cost you some processing overhead, so you'll want to be careful when you and how you use it.

Here's one scenario where Diagnostic Logging would help out. Imagine you have a user who complains that when they read messages from a particular sender, they get an error. You think the problem is probably contained in one of the MSGXX.DB files, and the solution is to run GWCHECK on the MSGXX.DB of the sender. But which MSGXX.DB do you run GWCHECK on? Here's where Diagnostic Logging comes in. All you have to do is turn it on at the POA, and then have the user click the mail message that gives them the error. Now, look at the log of the POA, and you'll find the problem MSGXX.DB file. Pretty slick, don't you think?

Convinced? Ready to give it a try? Here's the scoop on the keystroke:

Make sure you have the POA user interface screen in front of you, then press "Ctrl-Z". When you do this, you'll see the POA report "Diagnostic mode enabled." When you're ready to turn it off, just press "Ctrl+Z" again, and you'll see the POA report "Diagnostic mode disabled." Happy troubleshooting.


Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com

© 2014 Novell