RESUME

RESUME tells BMC AMI Load whether to add new data to the existing data in the table space.

Important

You can mix RESUME YES and REPLACE in one LOAD statement for different partitions by repeating the INTO TABLE clause for different field specifications. For more information, see the description for RESUME on the INTO TABLE clause (RESUME-INTO-TABLE-option).

YES

RESUME YES tells BMC AMI Load to add new data to the existing data in the table space.

Although LOAD RESUME YES always appends data at the end of the table space, BMC AMI Load uses shadow copies to rebuild or reorganize indexes on the table being loaded, and renames the indexes when the load process has completed.

BMC AMI Load can perform error cleanup processing on LOAD RESUME objects that are in must-complete state. To enable this feature, add the third, fourth, and fifth lines displayed in the following sample to the error_handling subroutine in the XSVRXERR-server-processing-error-automation-control-point:

Select
When Step_must_complete = 'YES' Then Do
  If Function_name = 'LOAD' & Action = 'CLEANUP' Then,
    Exit
  Else ,
    Action = 'ERROR'
  Exit
End
  When Function_name = 'REORG' Then Nop              /*OK*/
  When Function_name = 'COPY' Then Nop              /*OK*/
  Otherwise Exit
End

To run cleanup processing, use the CLEANUP parameter or the cleanup_rc variable in the cleanup_rc.

NO

RESUME NO functions differently depending on whether you specify RESUME NO, or default to it.

Defaulting to RESUME NO (specifying neither LOAD RESUME nor LOAD REPLACE) tells BMC AMI Load to load data into the table space if it is empty. BMC AMI Load terminates if it encounters data while reading the table space.

If you specify RESUME NO explicitly, BMC AMI Load does not check whether the table space is empty. In this case, you can include RESUME and REPLACE specifications at the partition level on the INTO TABLE clause (just as you can when you specify RESUME YES).

RESUME

YES

NO

On this page