myrnap wrote:
Looks like the message had changed to DBLOOK_Usage with revision 76095, but the dblook tool only got updated with revision 109527.
So, this has already been fixed...just not in the release candidate.
Yes, this has been fixed with 109527. I have a cleanup/enhancement patch for dblook_test that, among other things, will add a test case to verify the messages so that this kind of problem is caught by the harness in the future. I hope to post the patch later today.
Army
