13.6 Notes

  1. Table 13-26 lists and describes the return codes of pdconstck and explains the actions to be taken.

    Table 13-26 Return codes of pdconstck and actions to be taken

    Return codeDescriptionAction
    0Terminated normally.None
    4Terminated normally, but there was a constraint that lacked integrity as a result of integrity checking (this includes cases such as when integrity checking on constraints was cancelled because the number of violation key values exceeded the specified maximum).Correct the integrity of the constraints resulting in check pending status and then re-execute.
    8Terminated abnormally.If necessary, eliminate the cause of the error and then re-execute.
    Note
    If an error occurs during pdconstck's termination processing after return code 0 or 4 has been output with the KFPL50001-I message, the return code remains 0 or 4, not 8.
  2. When pdconstck is executed while the security audit facility is being used, the audit trails that are acquired depend on the return code:
    When the return code is 0 or 4:
    Audit trails are acquired if SUCCESSFUL or ANY is specified for WHENEVER in CREATE AUDIT.
    When the return code is 8:
    Audit trails are acquired if UNSUCCESSFUL or ANY is specified for WHENEVER in CREATE AUDIT.
  3. If you selected utf-8 as the character encoding in the pdsetup command, a BOM is not added to the file that is output by pdconstck.