Event Capture support for EXEC SQL call

We have assessed this requirement. We have no current plans for this to be implemented and so this requirement is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.

Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Transaction Processing
Product - CICS Transaction Server

For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Transaction Processing
Product - CICS Transaction Server

Email response from IBM rep with feedback from customer:

The customer wants the standard SQL call can be monitored, like INSERT, UPDATE, etc, and the related table name, record name, record value to be captuered.

What type of EXEC SQL requests do you want to capture ?

It should be noted that depending upon the type of SQL command issued by the application, it is not possible for CICS event processing to be able to see the table name and variables.

If for example you use cursors you can declare a cursor that when opened will perform a select on a table, eg

EXEC SQL DECLARE CSRR    CURSOR FOR    
         SELECT C1,NAME              
         FROM      OWNER.TSTCHOLD;      

From the application, you just issue EXEC SQL OPEN CSRR and all that we would see from the CICS side was that there was an open request for a cursor called CSRR. Inside DB2 it would then go an issue the select and CICS will know nothing about this.

What type of EXEC SQL requests do you want to capture ?

It should be noted that depending upon the type of SQL command issued by the application, it is not possible for CICS event processing to be able to see the table name and variables.

If for example you use cursors you can declare a cursor that when opened will perform a select on a table, eg

EXEC SQL DECLARE CSRR    CURSOR FOR    
         SELECT C1,NAME              
         FROM      OWNER.TSTCHOLD;      

From the application, you just issue EXEC SQL OPEN CSRR and all that we would see from the CICS side was that there was an open request for a cursor called CSRR. Inside DB2 it would then go an issue the select and CICS will know nothing about this.

What type of EXEC SQL requests do you want to capture ?

It should be noted that depending upon the type of SQL command issued by the application, it is not possible for CICS event processing to be able to see the table name and variables.

If for example you use cursors you can declare a cursor that when opened will perform a select on a table, eg

EXEC SQL DECLARE CSRR CURSOR FOR
SELECT C1,NAME
FROM OWNER.TSTCHOLD;

From the application, you just issue EXEC SQL OPEN CSRR and all that we would see from the CICS side was that there was an open request for a cursor called CSRR. Inside DB2 it would then go an issue the select and CICS will know nothing about this.