Feedback
Did this article resolve your question/issue?

   

Article

PROQUIET return codes

« Go Back

Information

 
TitlePROQUIET return codes
URL NameP41028
Article Number000141242
EnvironmentProduct: Progress
Version: 8.x, 9.x
Product: OpenEdge
Version: 10.x, 11.x
OS: All supported platforms
Question/Problem Description
What are the return codes for PROQUIET?
What are the non-zero return codes when enabling a quiet point?
What are the non-zero return codes when disabling a quiet point?
Steps to Reproduce
Clarifying Information
 
 
Error Message
Defect Number
Enhancement Number
Cause
Resolution
Unless there are specific reasons at the time that the "proquiet -C enable" cannot establish a quiet point, there is no need to run a script to query PROQUIET return codes once the database has been quiesced.

Once all the necessary latches to prevent any type of writes from the database have been acquired by the broker, we acknowledge through shared memory that the quiet point was enabled. This is communicated to the requester process and it is then free to print the enabled message (5583) and return to the (quiet point requester) user with an appropriate return code = 0.


PROQUIET return codes

A return code of 0 = success and a return code of non-zero indicates failure.

Progress reserves the right to change non-zero return code values and their meanings as we deem necessary without notification.  
The following is a listing of the non-zero return codes in 10.2B

Non-zero return codes when enabling proquiet : (proquiet -C enable)

2    Cannot enable proquiet with a single AI file
4    Quiet point has already been requested.
6    Enabling the quiet point is already in effect.
16   Broker died during a quiet point enable request or does not exist when attempting to enable the quiet point.

If a quiet point is currently enabled or active when proquiet -C enable is run:
 
3    The BI threshold has been reached. You must extend the BI using the bithreshold option first before you can disable the quiet point.
16   Broker does not exist or a shutdown request was received

If a quiet point was not enabled or active: (proquiet -C disable)
 
5    Quiet point cannot be enabled because of an ai switch failure
7    Quiet point does not need to be disabled.
Workaround
Notes
Last Modified Date11/20/2020 7:31 AM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.