Transaction Detail (PF6)

Using the Realtime Monitor › Transaction Detail (PF6)

Transaction Detail (PF6)

PM-Rnn.n SYSTEM71 CA, Inc. V71 08.348 10:40:20.69 CMD--> Window : 02 Refresh: 10 02 Transaction Detail > Task Task Bound Task Subschma Transaction DBMS Pages Pages Number Code Program Status Acc_Mod Status Calls Writn Read 2 RHDCRUAL WAIT IDMSNWK7 H 113 0 1002 2 RHDCRUAL WAIT IDMSNWK7 H 9 0 0 3 RHDCRUAL WAIT IDMSNWKL H 314 0 21 3 RHDCRUAL WAIT IDMSNWKL A 3 0 0 4 RHDCRUAL WAIT IDMSNWK6 A 731 0 33 4 RHDCRUAL WAIT IDMSNWK6 A 3 0 0 5 RHDCRUAL WAIT IDMSSECU H 165 0 3 5 RHDCRUAL WAIT IDMSSECU H 9 0 0 6 RHDCRUAL WAIT IDMSNWK8 A 3 0 0 6 RHDCRUAL WAIT IDMSNWK8 A 3 0 0 7 RHDCRUAL WAIT IDMSSECS A 141 0 2 7 RHDCRUAL WAIT IDMSSECS A 3 0 0 8 RHDCLGSD WAIT IDMSNWK9 A 3 0 0 9 RHDCLGSD WAIT IDMSNWK9 A 3 0 0 10 RHDCLGSD WAIT IDMSNWK9 A 3 0 0

PM-Rnn.n SYSTEM71 CA, Inc. V71 08.348 10:40:20.69 CMD--> Window : 02 Refresh: 10 02 Transaction Detail < > Calc Task Pages Pages Rcrds Rcrds Frags Updat Selct Locks Bfore After Store Number Read Reqst Reqst Curnt Stord Locks Locks Reqst Image Image Noovr 2 1002 1023 24 0 0 1 0 25 0 0 0 2 0 1 1 0 0 1 0 2 0 0 0 3 21 90 95 26 0 1 0 86 0 0 0 3 0 0 0 0 0 1 0 1 0 0 0 4 33 357 560 357 0 0 1 1 0 0 0 4 0 0 0 0 0 0 1 1 0 0 0 5 3 32 32 0 0 1 0 33 0 0 0 5 0 1 1 0 0 1 0 2 0 0 0 6 0 0 0 0 0 0 1 1 0 0 0 6 0 0 0 0 0 0 1 1 0 0 0 7 2 26 26 0 0 0 1 1 0 0 0 7 0 0 0 0 0 0 1 1 0 0 0 8 0 0 0 0 0 0 1 1 0 0 0 9 0 0 0 0 0 0 1 1 0 0 0 10 0 0 0 0 0 0 1 1 0 0 0

PM-Rnn.n SYSTEM71 CA, Inc. V71 08.348 10:40:20.69 CMD--> Window : 02 Refresh: 10 02 Transaction Detail < > Calc Calc Via Via Lvls Task Store Store Store Store New SR8s SR8s Orphs Levl SR8 Srch Number Noovr Ovrfl Noovr Ovrfl Index Erasd Stord Adopt Spawn Split Wrst 2 0 0 0 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0 0 0 0 0 5 0 0 0 0 0 0 0 0 0 0 0 5 0 0 0 0 0 0 0 0 0 0 0 6 0 0 0 0 0 0 0 0 0 0 0 6 0 0 0 0 0 0 0 0 0 0 0 7 0 0 0 0 0 0 0 0 0 0 0 7 0 0 0 0 0 0 0 0 0 0 0 8 0 0 0 0 0 0 0 0 0 0 0 9 0 0 0 0 0 0 0 0 0 0 0 10 0 0 0 0 0 0 0 0 0 0 0

PM-Rnn.n SYSTEM71 CA, Inc. V71 08.348 15:49:30.57 CMD--> Window : 02 Refresh: 10 02 Transaction Detail < Lvls Lvls Last Task Levl SR8 Srch Srch Verb Current Current Number Spawn Split Wrst Best Num Area_Name Record_Name 2 0 0 0 0 005F DDLDCRUN 2 0 0 0 0 0036 3 0 0 0 0 005F 3 0 0 0 0 0036 4 0 0 0 0 005F DDLDCMSG 4 0 0 0 0 0036 5 0 0 0 0 005F DDLSEC 5 0 0 0 0 005F DDLSEC 6 0 0 0 0 0036 6 0 0 0 0 0036 7 0 0 0 0 005F DDLDML 7 0 0 0 0 005F DDLDML 8 0 0 0 0 0038 DDLDCLOG LOGREC-143 9 0 0 0 0 0038 DDLDCLOG LOGREC-143 10 0 0 0 0 0038 DDLDCLOG LOGREC-143

Screen Description

The Transaction Detail screen displays a line of information for each active transaction.

What To Look For

Look for a high number in the Frags Stord, Calc Store Ovrfl, and Via Store Ovrfl fields. A high number in any of these fields indicates that target pages for records stored by a transaction were full, forcing CA IDMS to store the records on other pages. This situation can degrade access efficiency for the database.
Look for information on index levels on this screen.
Look for information on implied locks maintained by each active transaction on this screen. Too many locks can cause a task to use a lot of storage. Use COMMITs to release locks. The task should release explicitly locked records as soon as possible.

You can also use the Application Monitor (see Using the Application Monitor) to view transaction activity through a period of time and to identify transactions causing overflow problems. In addition, you can use the IDMSDBAN utility to analyze space availability for database pages. If a large number of pages in the database are full, you should consider increasing the database page size or the number of pages in the database.