The Resource Control Table (RCT), or CICS DB2 attachment facility, contains the information required for CICS to establish its connection to DB2. The FILE transaction's DB2 facility lets you view information and statistics on each entry in the active RCT.
The display format is presented as if the RCT existed as a DB2 table. This display is similar to the information provided by the IBM‑supplied DSNC DISP STAT command, but provides more complete and easily accessed information.
The following table summarizes the differences between the CA InterTest for CICS DSNCRCT Display and the CICS DSNC Display.
|
CA InterTest for CICS DSNCRCT Display |
CICS DSNC Display |
|---|---|
|
Gives all RCT transactions |
Gives only the first transaction in a group |
|
User transactions appear in alphabetical order |
Transactions in RCT order |
|
Shows the Authorization ID |
Does not show the Authorization ID |
To display the RCT, enter the keyword DSNCRCT in the DB2 command area. CA InterTest for CICS redisplays the keyword as SELECT * FROM DSNCRCT for compatibility with other DB2 data table displays; however, SELECT command clauses are not supported with DSNCRCT.
The CA InterTest for CICS RCT display includes 15 columns of information, requiring three panels for display. To scroll to the next or previous panel of columns, press PF11 or PF10. To see a Structured Display of the columns, press PF12.
The following screen shows the initial RCT display showing columns 1 to 8.
CA InterTest File DB2 Facility EXEC SQL # Cols 015 Max Loc 00190 Loc 00001 Page 001 SELECT * FROM DSNCRCT3 1---------2------------3------------4-------5-------6---------7--------8------- Tran Id | *Plan Id | *Auth Id | Auths | Calls | Commits | Aborts | Waits| ----------+------------+------------+-------+-------+---------+--------+------+ DSNC | | | 0 | 0 | 0 | 0 | 0| POOL | DSN8CC21 | | 0 | 0 | 0 | 0 | 0| CNTL | FILE21 | INTRTST | 0 | 0 | 0 | 0 | 0| CORE | FILE21 | INTRTST | 0 | 0 | 0 | 0 | 0| DB2A | ASMSQL | DEVMPL | 0 | 0 | 0 | 0 | 0| DB2C | COBSQL | DEVMPL | 0 | 0 | 0 | 0 | 0| DB2P | PLISQL | DEVMPL | 0 | 0 | 0 | 0 | 0| D8CS | DSN8CC21 | | 0 | 0 | 0 | 0 | 0| D8PP | DSN8CQ21 | | 0 | 0 | 0 | 0 | 0| D8PS | DSN8CP21 | | 0 | 0 | 0 | 0 | 0| D8PT | DSN8CH21 | | 0 | 0 | 0 | 0 | 0| D8PU | DSN8CH21 | | 0 | 0 | 0 | 0 | 0| FILE | FILE21 | INTRTST | 0 | 0 | 0 | 0 | 0| HELP | FILE21 | INTRTST | 0 | 0 | 0 | 0 | 0| _______________________________________________________________________________ 1 Help 2 CMND list 3 END 4 Large CMND 5 Log On 6 DataType FC 7 Page bwd 8 Page fwd 9 Page 1 10 Scrl. -> 11 Scrl. <- 12 Structure
The first eight columns are defined next.
Tran ID—Lists all CICS transactions that issue SQL calls. The first two entries are system transactions; the rest are user transactions listed in alphabetical order. The system transactions are defined next.
Plan ID—Indicates the plan name associated with the transaction.
Auth ID—Indicates the authorization identification concatenated to the table name when the associated transaction is used to access a data table.
Auths—Indicates the number of authorizations (sign‑on invocations) for transactions associated with this entry.
Calls—Indicates the number of SQL calls issued by transactions associated with this entry.
Commits—Indicates the number of sync points issued for transactions associated with this entry.
Aborts—Indicates the number of sync point rollbacks and abends issued for transactions associated with this entry.
Waits—Indicates the number of times that all available threads for this entry were busy and the associated transactions had to either wait or be diverted to the pool.
The second panel shows all the DB2 thread statistics, which are kept in the RCT. The following screen shows a sample display of the second panel of columns.
CA InterTest File DB2 Facility EXEC SQL # Cols 015 Max Loc 00190 Loc 00080 Page 001 SELECT * FROM DSNCRCT3 9------------10---------------11------------12---------------13--------------- | Max Thread | Max Act Thread | High Thread | Curr Thread Lvl | Thread Subtask| +------------+----------------+-------------+-----------------+---------------+ | 1 | 1 | 0| 0 | 1| | 3 | 3 | 0| 0 | 0| | 0 | 0 | 0| 0 | 0| | 0 | 0 | 0| 0 | 0| | 2 | 2 | 0| 0 | 0| | 2 | 2 | 0| 0 | 0| | 2 | 2 | 0| 0 | 0| | 1 | 1 | 0| 0 | 0| | 1 | 1 | 0| 0 | 0| | 1 | 1 | 0| 0 | 0| | 1 | 1 | 0| 0 | 0| | 1 | 1 | 0| 0 | 0| | 0 | 0 | 0| 0 | 0| | 0 | 0 | 0| 0 | 0| _______________________________________________________________________________ 1 Help 2 CMND list 3 END 4 Large CMND 5 Log On 6 DataType FC 7 Page bwd 8 Page fwd 9 Page 1 10 Scrl. --> 11 Scrl. <-- 12 Structure
Columns 9 through 13 are defined next.
Max Thread—Indicates the maximum number of threads the attachment facility should be prepared to connect for this transaction group.
Max Act Thread—Indicates the maximum number of threads the attachment facility should allow to be connected for this transaction, group, or pool before requests must either wait or be diverted to the pool.
High Thread—Indicates the maximum number of threads required by transactions associated with this entry since the connection was started. This number includes transactions forced to wait on a thread or diverted to the pool.
Curr Thread Lvl—Indicates the current number of threads associated with this entry at this time.
Thread Subtask—Indicates the maximum number of z/OS subtasks or threads that should be started when the attachment facility is started.
The third panel contains two columns that deal with dynamic plan selection. The following screen shows columns 14 and 15 of the RCT display.
CA InterTest File DB2 Facility EXEC SQL # Cols 015 Max Loc 00190 Loc 00159 Page 001 SELECT * FROM DSNCRCT3 14-------------15-------------- |*Exit Prog Id | Dym User Area | +--------------+---------------+ | | **** | | | **** | | | **** | | | **** | | | **** | | | **** | | | **** | | | **** | | | **** | | | **** | | | **** | | | **** | | | **** | | | **** | _______________________________________________________________________________ 1 Help 2 CMND list 3 END 4 Large CMND 5 Log On 6 DataType FC 7 Page bwd 8 Page fwd 9 Page 1 10 Scrl. --> 11 Scrl. <-- 12 Structure
Exit Prog ID—Indicates the name of the exit program, which dynamically allocates the plan name for transactions associated with this entry.
Dym User Area—Displays the contents of the fullword in the RCT entry reserved for dynamic exit program use.
Note: The RCT statistics are kept on an entry basis, not on a transaction basis. This means that all transactions in a group (sharing the same Plan ID) will have the same statistics.
|
Copyright © 2012 CA.
All rights reserved.
|
|