Table 12-4 Return codes of pdpgbfon
Return code | Description | Action |
---|---|---|
0 | Global buffer read operation was completed. | None |
4 | Buffer miss occurred (some pages were not read), because there were not enough buffer sectors when data was read into the global buffer. | If necessary, increase the number of global buffer sectors. If a single global buffer is shared among multiple resources, a page of another resource may be read into the global buffer by another job before or during execution of pdpgbfon. In this case, sweeping a page of the other resource out of the global buffer is also treated as a buffer miss; therefore, whether the buffer miss applies to the target resource's page or another resource's page cannot be determined. If you are using only the return code to determine whether or not all pages were read into the global buffer successfully, do not execute any other job until pdpgbfon has terminated. |
8 | pdpgbfon terminated abnormally (global buffer read operation was cancelled). | The table and index status is guaranteed and can be accessed from UAPs even after abnormal termination. To re-execute pdpgbfon, see the displayed error message and eliminate the cause of the error. |
12 | pdrorg terminated abnormally (pdrorg that runs as an extension of pdpgbfon terminated abnormally). | The table and index status is guaranteed and can be accessed from UAPs even after abnormal termination. To re-execute pdpgbfon, see the displayed error message, eliminate the cause of the error, then re-execute pdpgbfon. |