This section provides an overview of the activity display functionality.
Activity displays are provided through System Coordinator administration by selecting Current activity displays at the main menu then Adabas client job information. At that point you will see a summary list of all the jobs that are known. Use "d" to select further detail for the job you are interested in. This will show further detail from Coordinator; then use PF11 to toggle until the Transaction Manager detail for the job is encountered as follows:
11:58:42 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 ***** 2012-03-07
- Transaction Manager Job Statistics - C12110M1
Run-mode: Pulsing (node 2650) Perspective: Daemon (node 2650)
Job Name: DAEFCI18
---Transaction activities summary ----------Done-----------------Undone--------
Adabas DTP: Single-phase: 20 (60%) 1 (50%)
Full: 0 (0%) 0 (0%)
Continuous operation: 0 (0%) 0 (0%)
Sub-total: 20 (60%) 1 (50%)
Adabas open DTP: Single-phase: 13 (39%) 1 (50%)
Full: 0 (0%) 0 (0%)
Continuous operation: 0 (0%) 0 (0%)
Sub-total: 13 (39%) 1 (50%)
Combined total: 33 (100%) 2 (100%)
---Other ----------------------------------------------------------------------
Recovery file reads and writes: 0 0
Duration (secs) average and peak: 0.42 11.13
RM and non-RM used count: 1 2
Transaction timeouts and heuristics: 0 3
Adabas dynamic commits and backouts: 2 0
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Refr Expan Prods Menu
|
Here Transaction Manager is displaying a breakdown of all transaction processing performed for the job, the following information is provided.
| Field | Description |
|---|---|
| Adabas DTP | Transactions affecting only Adabas resources. |
| Adabas open DTP | Transactions affecting Adabas resources and others. |
| Single-phase | The number of transactions affecting only a single Adabas. |
| Full | The number of distributed transactions. |
| Continuous operation | The number of transactions processed during TM outage. |
| Recovery file reads and writes | The number of recovery file reads and writes performed during transaction processing. |
| Duration (secs) average and peak | The average and peak duration time taken by Adabas Transaction Manager to apply or undo transactions. |
| RM and non-RM used count | The peak number of Adabas databases (RM and non-RM) used by a session. |
| Transaction timeouts | The number of transactions undone as a result of the distributed transaction time limit being exceeded. |
| Heuristics | The number of transactions heuristically completed either by the TM or by Adabas. |
| Adabas dynamic commits | When client runtime control Adabas transaction dynamics is set to FULL or FORCED, this is the number of times a session was transactional at the end of a TP message-pair. |
| Adabas dynamic backouts | When client runtime control Adabas transaction dynamics is set to TP, this is the number of response 240 sub-code 596s issued to prevent a transaction persisting a TP message-pair. |
Activity displays are provided through System Coordinator administration by selecting Current activity displays at the main menu then Adabas client job information. At that point you will see a summary list of all the jobs that are known. Use any undefined character to expand to see a list of all the sessions for the job. Again use any character to select a particular session. The detail for a session will show a list of one or more Adabas client connections (multiple will be shown where ADAMODE demands multiple connections). Again use any unassigned character to select one of these connections for further display. Finally use PF11 to toggle until the Transaction Manager detail for the connection is encountered as follows:
11:27:38 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 ***** 2012-03-08
- Transaction Manager Session Statistics - U1STS0M3
Node ID: LOCAL Session ID: CICSTC27 Hex: C3C9C3E2E3C3F2F7 Job Name: DAEFCI18
Terminal name: TC27 Network name: DAEFTC27 Login id: UKSTAD
---Transaction activities summary ----------Done-----------------Undone--------
Adabas DTP: Single-phase: 3 (100%) 0 (0%)
Full: 0 (0%) 0 (0%)
Continuous operation: 0 (0%) 0 (0%)
Sub-total: 3 (100%) 0 (0%)
Adabas open DTP: Single-phase: 0 (0%) 0 (0%)
Full: 0 (0%) 0 (0%)
Continuous operation: 0 (0%) 0 (0%)
Sub-total: 0 (0%) 0 (0%)
Combined total: 3 (100%) 0 (100%)
---Other ----------------------------------------------------------------------
Recovery file reads and writes: 0 0
Duration (secs) average and peak: 0.28 0.31
RM and non-RM used count: 0 1
Transaction timeouts and heuristics: 0 0
Adabas dynamic commits and backouts: 0 0
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Exit Refr Tasks Prods Menu
|
Here Transaction Manager is displaying a breakdown of all transaction processing performed for the session, the following information is provided.
| Field | Description |
|---|---|
| Adabas DTP | Transactions affecting only Adabas resources. |
| Adabas open DTP | Transactions affecting Adabas resources and others. |
| Single-phase | The number of transactions affecting only a single Adabas. |
| Full | The number of distributed transactions. |
| Continuous operation | The number of transactions processed during TM outage. |
| Recovery file reads and writes | The number of recovery file reads and writes performed during transaction processing. |
| Duration (secs) average and peak | The average and peak duration time taken by Adabas Transaction Manager to apply or undo transactions. |
| RM and non-RM used count | The peak number of Adabas databases (RM and non-RM) used by a session. |
| Transaction timeouts | The number of transactions undone as a result of the distributed transaction time limit being exceeded. |
| Heuristics | The number of transactions heuristically completed either by the TM or by Adabas. |
| Adabas dynamic commits | When client runtime control Adabas transaction dynamics is set to FULL or FORCED, this is the number of times a session was transactional at the end of a TP message-pair. |
| Adabas dynamic backouts | When client runtime control Adabas transaction dynamics is set to TP, this is the number of response 240 sub-code 596s issued to prevent a transaction persisting a TP message-pair. |
When running in local perspective, PF9 provides some additional session information:
12:33:41 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 ***** 2011-04-14
- Session Details - U1TMA0M1
Job Name: DAEFCI18 Co-ordinator: ATM Client Type: 00 - DTP
Terminal ID: TC27 E3C3F2F700000000 Net Name: DAEFTC27 C4C1C5C6E3C3F2F7
Client ID: 0000000000000000 Status: F00000000000 GT
CommID: 000CA10E 20980001 40404040 40404040 00FC7700 C3C9C3E2 E3C3F2F7
XID: C1C4C101 00000050 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 C2D80000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
ASA: 00000000 GTQE: 00000000
Last Function Call: 22 - WRAP CMD Transaction dynamics: FULL
DBNo. L/R DTP ETID Status | Pending Response Codes
640 R N 8060 ET | Resp. Subcode
135 R 8062 ET ¦
¦
¦
¦
¦
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Refr Top ErrI Menu
|