Restrict the use of RR isolation level in RC/Browse,RC/Edit or RC/Update

Products

• RC/Update for DB2 for z/OS

Issue/Introduction

Can the tools such as RC/Browse,RC/Edit or RC/Update be locked down so that only with isolation level UR is ever invoked?

Environment

z/os DB2

Resolution

1. Q1) Can these tools such as RC/Browse , RC/Edit , RC/Update be locked down so that only with isolation level UR is ever invoked?  
   A1) Currently, the RCU products only utilize Cursor Stability (CS) or Uncommitted Read (UR). The Repeatable Read (RR) isolation level is never used by these tools. Isolation levels can be specified via the RC/Edit parmlib member or the "RC/Edit Parameters" profile panel; if no level is specified, the product defaults to CS.
2. Q2)If looking at removing ALL access too issue RR isolation plans, would there be a specific authority setting within the panels to achieve this? Or would it most likely need to look into setting up RACF profiles to controls these plans?
   A2) Because RCU products do not use RR isolation levels, there are no specific RR-level plans generated by our tools. Broadcom product plans are bound with CS by default unless specifically and manually modified by the customer.  
3. Q3) Are there any locations that an end user can manually edit their SQL within these panels in order to hard code WITH UR/CS/RR isolation levels? Such as where the WHERE clause is coded within the RC/BROWSE panel. 
   A3) There are currently no locations within the panels, such as the WHERE clause in RC/Browse, where an end user can manually edit or append SQL to hard-code isolation levels like WITH RR, RS, CS, or UR.