ROLLBACK (Rollback)

ROLLBACK Command syntax diagram

 

Purpose

The Rollback (ROLLBACK) command is used to restart the current transaction and reestablish the last commitment boundary as the current commitment boundary for the commitment definition associated with the program issuing the command.

When the ROLLBACK command is issued:

• Changes made to database files and other commitment resources under commitment control for the commitment definition since the last commitment boundary was established are rolled back. Updates, additions, or deletions made to the database file's data since that commitment boundary are rolled back or removed, and the original entries are put back in the files. Records that were added to the files remain as deleted records. The files are repositioned to the last commitment boundary. Changes made to other commitment resources are rolled back as well.
• All record locks held for files opened under commitment control for the commitment definition are released.
• Locks on object level commitment control resources, acquired when the resources were created or changed during the transaction, are released.

More information on the use of commitment control is in the Backup and recovery topic in the Information Center.

There are no parameters for this command.

Example for ROLLBACK

ROLLBACK

This command reestablishes the last commitment boundary (the point at which a Commit (COMMIT) command or Rollback (ROLLBACK) command was last issued) for the commitment definition associated with the program issuing the command.

Error messages for ROLLBACK

*ESCAPE Messages

CPF83D0

Commitment operation not allowed.

CPF835F

Commit or rollback operation failed.

CPF8350

Commitment definition not found.

CPF8359

Rollback operation failed.

CPF8367

Cannot perform commitment control operation.

*STATUS Messages

CPF83E6

Commitment control operation completed with resynchronization in progress.