ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

I rolled back an update using Data Studio's rollback option. Although Detector increased the ABORT count, it didn't display the ROLLBACK SQL call. Why?

book

Article ID: 40611

calendar_today

Updated On:

Products

Bind Analyzer for DB2 for z/OS SQL-Ease for DB2 for z/OS SYSVIEW Performance Management Option for DB2 for z/OS Plan Analyzer for DB2 for z/OS Subsystem Analyzer for DB2 for z/OS

Issue/Introduction

Introduction: 

This document states why a ROLLBACK performed by DB2 Connect is not displayed as an SQL Call.

Question: 

I rolled back an update using Data Studio's rollback option. Although Detector increased the ABORT count, it didn't display the ROLLBACK SQL call. Why?

Environment:  

z/OS 1.11 and above.

Answer: 

CA Detector currently only displays a ROLLBACK SQL call when the command is issued (or, written). Eg:

1)  EXEC SQL

         ROLLBACK

     END-SQL ;

2) Or, if the ROLLBACK command is entered into a DB2 Command processor (like ISQL or Data Studio). Eg:

    UPDATE  TEAM           

       SET PHONE = 'x9999'

    WHERE NAME = 'Greg'  ;

    ROLLBACK ;

 

 

 

 

Environment

Release:
Component: PDT
Powered by Wolken Software