Data Manipulation Language Statements › #ROLLBAK—rolls back uncommitted changes made to the database

#ROLLBAK—rolls back uncommitted changes made to the database

The #ROLLBAK statement rolls back uncommitted changes made to the database through an individual run unit or through all database sessions associated with a task. A task-level rollback also backs out all uncommitted changes made in conjunction with scratch, queue, and print activity.

Whether the changes are automatically backed out depends on the execution environment:

• If the changes were made under the control of a central version that is journaling to a disk file, they are backed out automatically. The central version continues to process other applications during recovery.
• The changes are not backed out automatically under the following circumstances:
  • If the changes were made under the control of a central version that is journaling to a tape file.
  • If the changes were made in local mode.

  In these cases, the #ROLLBAK statement causes the affected areas to remain locked against subsequent access by other database sessions. They must be manually recovered. If changes cannot be backed out and CONTINUE was specified on the rollback request, a non-zero error status is returned to the application and if the request was for an individual run unit, that run unit is terminated.

  Note: For more information about manual recovery, see the Database Administration Guide.

If CONTINUE is not specified, run units (and SQL sessions) impacted by the #ROLLBAK statement end, and their access to the database is terminated. If CONTINUE is specified, impacted database sessions remain active after the operation is complete.

The #ROLLBAK statement is used in both the navigational and logical record facility environments. The #ROLLBAK TASK statement is also used in an SQL programming environment.

Currency

Following a #ROLLBAK statement, all currencies are set to null. Unless the CONTINUE option is specified, the issuing program or task cannot perform database access through an impacted run unit without executing another @BIND/@READY sequence.