Rolls back the uncommitted changes made by all scratch, queue, and print activity and all top-level run units associated with the current task and terminates those run units. Its impact on SQL sessions associated with the task depends on whether those sessions are suspended and whether their transactions are eligible to be shared.
More information:
For more information about the impact of a #ROLLBAK TASK statement on SQL sessions, see the SQL Programming Guide.
For more information about run units and the impact of #ROLLBAK TASK, see the Navigational DML Programming Guide.
Central version only. Causes the affected run units and SQL sessions to remain active after their changes are backed out. Database access can be resumed without reissuing @BIND and @READY statements.
Note: The CONTINUE option should not be used in local mode if database changes have been made.
|
Copyright © 2014 CA.
All rights reserved.
|
|