JR29220: USING COMMAND EDITOR CONNECTING TO Z/OS DB2 RESULTS IN CLAIMS (CS,C) ON THE TABLE WHICH CAUSES CONTENTION WITH Z/OS UTILITIES

APAR status

• Closed as Permanent restriction.

Error description

• When using the DB2 Command Editor to connect to z/OS DB2, you
  will see claims on the table you are selecting from if they have
  the "Display results for a single query on the Query Results
  page" checked.
  
  If the user does not commit or exit from Command Editor, this
  will cause contention with utilities run on z/OS DB2.  This
  includes backups.
  
  This can clearly be seen by the following:
  
  1) Open a TSO session to you z/OS DB2 server, go into the DB2I
  interactive panels and choose option 7 to run DB2 Commands
  
  2) Connect via command editor to the z/OS DB2 subsystem
  3) issued:  select * from tablename <i am using testlock>
  4) Issue the -display database(dbname) claimers
  
  DSNT397I  -NJLU
  NAME     TYPE PART STATUS             CONNID   CORRID
  CLAIMINFO
  -------- ---- ---- ------------------ -------- ------------
  --------
  TESTLOCK TS        RW                 SERVER   javaw.exe
  (CS,C)
   G91A5EA8.BE11.006B09153002=37 ACCESSING DATA FOR NT
  TS097421 TS        RW
  
  You will see that we have a Claim that will not be released
  until a commit is done.
  
  5) Hit commit and then ran the display again and the (CS,C) is
  no longer shown, although the
  DSNT397I  -NJLU
  NAME     TYPE PART STATUS             CONNID   CORRID
  CLAIMINFO
  -------- ---- ---- ------------------ -------- ------------
  --------
  TESTLOCK TS        RW
  TS097421 TS        RW
  ******* DISPLAY OF DATABASE TS09742  ENDED
  **********************
  
  So the claim is released when I hit the commit.
  
  The functionality of Insert and Delete are available if you run
  the Commit.
  
  The fix will automatically commit the data to avoid this
  contention.
  

Local fix

• Disable the query results page via unchecking "Display results
  for a single query on the Query Results page" in the tools
  Settings in Command Editor.
  

Problem summary

• Users Affected: Command Editor connections to z/OS tables.
  
  Problem Description:
  When using the DB2 Command Editor to connect to z/OS DB2, you
  will see claims on the table you are selecting from if they have
  the "Display results for a single query on the Query Results
  page" checked.
  
  If the user does not commit or exit from Command Editor, this
  will cause contention with utilities run on z/OS DB2.  This
  includes backups.
  
  Problem Summary:
  When using the DB2 Command Editor to connect to z/OS DB2, you
  will see claims on the table you are selecting from if they have
  the "Display results for a single query on the Query Results
  page" checked.
  
  If the user does not commit or exit from Command Editor, this
  will cause contention with utilities run on z/OS DB2.  This
  includes backups.
  

Problem conclusion

• Module:cc_UDBObj; Permanent Restriction
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  JR29221 JR29223

Fix information

Applicable component levels