Kbase P102729: proquiet won't disable after hitting bithold
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/22/2011 |
|
Status: Verified
SYMPTOM(s):
proquiet won't disable after reaching bithold
proquiet won't disable after resetting bithreshold
Quiet point won't disable
No errors are displayed to the screen
proquiet logs in and out when proquiet is being run
FACT(s) (Environment):
All Supported Operating Systems
Progress 8.x
Progress 9.x
OpenEdge 10.x
CAUSE:
Bug# OE00114705
CAUSE:
The problem is that proquiet doesn't properly check for syntax errors and returns to the prompt without error. This gives the impression that the command has run successfully.
Example:
proquiet sports -C bihtreshold
"bithreshold" is incorrectly spelt, for example "bihtreshold". The effect of such a mistake is that it doesn't set the new bithreshold value.
FIX:
Re-run the proquiet commands making sure that the spelling and syntax are perfect:
proquiet <dbname> -C enable
proquiet <dbname> -C bithreshold <newvalue>
proquiet <dbname> -C disable