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 codesA 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.
