This function can be used to obtain information from an executing Adabas Transaction Manager.
To display the Transaction Manager Information menu
Select option 2 from the Online Services main menu. The following menu will appear:
12:29:09 ***** A D A B A S TRANSACTION MANAGER 8.2.2 ***** 2012-02-23
- Transaction Manager Information - T12000M1
Manager: 20530 Terminal: DAEETCLU
Code Service
---- --------------------------------------
0 Select a different Transaction Manager
1 Statistics
2 Active Transactions
3 Pending Response Codes
4 Known Databases
5 Partner Transaction Managers
6 Recovery File Functions
. Exit
---- --------------------------------------
Code ..: _
New Manager Node: _____
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Oper Exit Menu
|
| From this menu, you can | Code | Command |
|---|---|---|
| select a different transaction manager | 0 | |
| display statistics | 1 | 2.1 |
| display active transactions | 2 | 2.2 |
| display pending response codes | 3 | 2.3 |
| display known databases | 4 | 2.4 |
| display partner transaction managers | 5 | 2.5 |
| invoke recovery file functions | 6 | 2.6 |
The ID of the transaction manager you are currently working with is displayed on this screen and on most screens in this part of the application. For example,
Manager: 20531.
You can use PF2 to issue ATM operator commands to the
transaction manager with which you are working. If you omit the command prefix
ATM, SYSATM supplies it for you. For example, if you enter the command
NOLOG, it will be changed to ATM
NOLOG. The text you enter on the command line is not validated
before the command is issued, except to check whether the command will
terminate the transaction manager. If you enter the command ATM
HALT or ATM END (or simply
HALT or END), a window
appears asking you to confirm your intention to close down the transaction
manager. See section Operator
Commands for a complete description of all operator commands.
If your system contains more than one operating system image and Entire Net-Work is being used to connect them, you may wish to work with a transaction manager that is executing in a different operating system image. In this case, select option 0 and enter the ID of the transaction manager in the field New Manager Node.
Note:
Running more than one ID table in the same system with Entire
Net-Work providing the connection between users of each ID table is equivalent
to executing across different operating system images.
This option displays statistics maintained by the current transaction manager.
Selecting option 1, Statistics, from the Transaction Manager Information menu shows:
09:23:02 ***** A D A B A S TRANSACTION MANAGER 8.2.2 ***** 2011-10-22
- Transaction Manager Statistics - T12100M1
Manager: 20531
Code Service
---- ----------------------------------
1 Transactions
2 Recovery file
3 Other
. Exit
---- ----------------------------------
Code ..: _
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit
|
This function displays statistical information about transactions managed by the current transaction manager as shown here:
09:24:35 ***** A D A B A S TRANSACTION MANAGER 8.2.2 ***** 2011-10-22
- Transaction Statistics - T12110M1
Manager: 20531
--Transaction activities summary ----------Done-----------------Undone--------
Adabas DTP: Single-phase: 0 (0%) 0 (0%)
Full: 0 (0%) 0 (0%)
Sub-total: 0 (0%) 0 (0%)
Adabas open DTP: Single-phase: 0 (0%) 0 (0%)
Full: 0 (0%) 0 (0%)
Sub-total: 0 (0%) 0 (0%)
Combined total: 0 (100%) 0 (100%)
--Other ----------------------------------------------------------------------
Transaction timeouts and heuristics: 0 0
Duration (secs) average and peak: 0.00 0.00
Pending response codes: 0
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Refr Menu
|
The following information is provided:
| Field | Description |
|---|---|
| Single-phase | The number of transactions processed by this transaction manager which did not require full two phase commit processing and which resulted in a positive outcome (‘Done’) or negative outcome (‘Undone’).This statistic is provided for Adabas DTP (transactions that involve only the Adabas domain) and Adabas open DTP (transactions that involve other vendor domains). |
| Full | The number of transactions processed by this transaction manager which did require full two phase commit processing and which resulted in a positive outcome (‘Done’) or negative outcome (‘Undone’).This statistic is provided for Adabas DTP (transactions that involve only the Adabas domain) and Adabas open DTP (transactions that involve other vendor domains). |
| Transaction timeouts | The number of transactions processed by this transaction manager which were undone as a result of the distributed transaction time limit being exceeded. |
| Heuristics | The number of transactions processed by this transaction manager which have experienced some degree of heuristic termination, either by the transaction manger itself or by an Adabas RM. |
| Duration | The average duration and peak duration of transactions processed by this transaction manager. |
| Pending response | The number of transactions that have resulted in a response code but which have yet to be reported back to the corresponding client session. |
This function displays statistical information about the recovery file in use by the current transaction manager as you can see here:
09:26:45 ***** A D A B A S TRANSACTION MANAGER 8.2.2 ***** 2011-10-22
- Recovery file Statistics - T12120M1
Manager: 20531
--Summary --------------------------------------------------------------------
Blocksize..............: 4096 (bytes)
Reads and writes.......: 0 0
--Detail ---------------------------------------------------------------------
Usage.. Number of blocks
Recovery...............: 0
ET data................: 0
Pending response.......: 0
Suspect transactions...: 0
System migration.......: 0
General management.....: 0
Total: 0
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Refr Menu
|
The following information is provided:
| Section | Description |
|---|---|
| Summary | This section displays the blocksize of the recovery file and the read/write activity against the recovery file. |
| Detail | This section displays the number of blocks currently in use for each of the different types of information maintained in the recovery file. |
This function displays statistical information that can be used to monitor the use of the transaction manager's resources, as you see here:
09:28:02 ***** A D A B A S TRANSACTION MANAGER 8.2.2 ***** 2011-10-22
- Other statistics - T12130M1
Manager: 20531
--High water marks ------------------------------------------------------------
Item.. Maximum HWM Time
RRMS request queue (TMDRQ)..: 10 0
Concurrent transactions.....: - 1 2011-10-22 09:22:02
Peer TMs....................: - 1 2011-10-22 09:22:02
Known databases.............: - 4 2011-10-22 09:22:02
Peer TMs per transaction....: - 1 2011-10-22 09:22:02
Databases per transaction...: - 2 2011-10-22 09:22:02
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Refr Menu
|
Most entries in the list on this screen do not relate directly to any TM control, but are included for information. The following is a brief summary of the items listed
| Section | Description |
|---|---|
| High water marks | This section displays the high water marks (and the time the high water mark first occurred) for a number of items. Items which display a maximum value are transaction manager controls and this information can therefore be used to monitor that these controls are suitably defined. |
Option 2 provides information about all active transactions that involve the current transaction manager.
By default, active transactions are listed in the following format:
10:17:20 ***** A D A B A S TRANSACTION MANAGER 8.2.2 ***** 2006-04-13
- Transactions - T12200M2
Manager: 20531 Terminal: TCU5
<-------Client ID-------> Tx.Start Last Act
C CL Char Hex Jobname Status MMDD HH:MM MMDD HH:MM DBs TM
L TM?q ? E3D41B9800000001 DAEFCI18 GT OPEN 0413 10:17 0413 10:17 2 1
L TM?q ? E3D41B9800000012 DAEFCI18 GT OPEN 0413 10:17 0413 10:17 1
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Refr Top Flip Menu |
By pressing PF11, you can view the list in an alternative format, which correlates the transaction owner’s Communication ID with the Client ID:
10:22:50 ***** A D A B A S TRANSACTION MANAGER 8.2.2 ***** 2006-04-13
- Transactions - T12200M1
Manager: 20531 Terminal: TCU5
C L/R <----------------------Communication ID----------------------> Client ID
L 000F7100 20640000 B902BE37 DE383581 00000001 C3C9C3E2 C5F0F0F1 TM ?q ?
L 000F7100 20640000 B902C0D2 914965A2 00000001 C3C9C3E2 C5F0F0F2 TM ?q ?
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Refr Top Flip Menu |
PF11 can be used to switch back and forth between the two list formats.
The first list format provides the following information:
| Item | Description |
|---|---|
| C | Enter a non-blank character and press Enter to obtain more detailed information about a particular transaction. See Display Detailed Information for Transaction. |
| CL |
C: Contains one of the following transaction coordinator values:
L: Indicates whether the client is local to (L) or remote from (R) the manager; that is, whether or not the client is executing in the same operating system instance |
| Char | The transaction owner’s Client ID in character format. |
| Hex | The transaction owner’s Client ID in hexadecimal format. |
| Jobname | The name of the job under which the transaction is executing. |
| Status | A summary description of the transaction’s current status. See Display Detailed Information for Transaction for more information. |
| Tx.Start | The time at which the transaction began; that is, the time of the transaction’s first change-type command. |
| Last Act | The time at which the transaction manager was last asked to perform some action on the transaction. For example, when the transaction changed another database. |
| DBs | The number of databases that have been changed by the transaction. |
| TM | The number of remote ATM managers that are involved in the transaction. Blanks indicate that the transaction has not changed any remote databases. |
The second list format provides the following information:
| Item | Description |
|---|---|
| C | Enter a non-blank character and press Enter to obtain more detailed information about a particular transaction. See Display Detailed Information for Transaction. |
| L/R | Indicates whether the transaction’s owner is local to (L) or remote from (R) the transaction manager; that is, whether or not the client is executing in the same operating system instance. |
| Communication ID | The transaction owner’s Communication ID in hexadecimal format. |
| Client ID | The transaction owner’s Client ID in character format. |
Detail information for a transaction can be obtained by marking the C column in the Transaction screen and pressing Enter.
The following screen will appear:
07:17:35 ***** A D A B A S TRANSACTION MANAGER 8.2.2 ***** 2006-04-19
- Transaction Details - T12210M1
Manager: 20531 Terminal: TCP0
Clnt Type: 84 - LOCAL Client ID: TM?q ? E3D41B9800000012 Jobname: QTT81013
Status: 8000000000 - GT OPEN Co-ordinator: THIS ATM PRR ISN: 00000000
CommID: 000FA10E 20860000 40404040 40404040 00F64400 E3F8F1F0 F1F34040
XID: C1C4C101 00000050 00000002 5033000F A10E2086 00004040 40404040 404000F6
4400E3F8 F1F0F1F3 4040E3F8 F1F0F1F3 4040D8E3 E3F8F1F0 F1F3BEAD 3BBC0734
EC800000 00000000 00000000 00000000 00000000 00000000 00000000 C2D80000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Start: 04/19 07:17.32 Tx Timeout: 07:19.38
Pending Response: 000 Sub Code: 0000
<----------CHANGED DATABASES----------> | <---PARTICIPATING ATMs-->
DBNo. TM Node Status Resp/subcode | TM Node Status Err
20532 0021 CHANGED 0 0 | 20535 0020 BRANCH
20536 20535 0021 CHANGED 0 0 |
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Refr Top Flip Menu |
The following information is provided:
| Field | Description |
|---|---|
| Clnt Type | The type of client session in hexadecimal format followed by an indication of whether the client is local to or remote from the transaction manager. |
| Client ID | The Client ID in character and then in hexadecimal format. |
| Jobname | The name of the job under which the transaction is, or was executing |
| Status |
The transaction’s status codes in hexadecimal followed by an indication of the most important element of the codes in character format. Possible character indicators are:
|
| Coordinator |
The transaction coordinator that has control of the global transaction. Possible values are:
|
| PRR ISN | The ISN of the recovery record for the transaction. The ISN is located in the ATM recovery record (PRR) file. This field will normally contain zeros until the transaction reaches prepared status. |
| UAB | This field contains internal information which might be useful to Software AG’s support staff in problem resolution. |
| GTQE | This field contains internal information which might be useful to Software AG’s support staff in problem resolution. |
| CommID | The transaction owner’s 28-byte Adabas Communication ID. |
| XID | The Transaction ID of the transaction. |
| Start | The start time of the transaction. The date has the format MM/DD. |
| Tx Timeout | The time at which the transaction will reach the global transaction time limit. |
| Last Act | The time at which the ATM manager was last asked to perform some action on behalf of the transaction’s owner. The date has the format MM/DD. |
| Pending Response and Sub Code | The response code and subcode that the manager will return to the transaction owner when the opportunity arises. These fields normally contain zeros. |
The remainder of the screen displays
a list of databases changed by the transaction
a list of remote ATM managers that are responsible for remote branches of the transaction
If one or both of the lists is too long to fit on the display, “More” appears at the foot of the screen. Use PF8 to scroll down the list and PF7 to return to the top of the list.
| Field | Description |
|---|---|
| DBNo. | Database ID of the changed database. |
| Manager | The Node ID of the remote ATM manager executing in the same system image as the database. If the database is executing in the same system as the current manager, this field contains blanks. |
| Status |
The status of the database with respect to the current transaction, followed by a summary value. Possible summary values are:
|
| Rsp and Sub | Any response code and subcode that the database returned to the manager for the transaction. |
| Field | Description |
|---|---|
| Manager | The Node ID of the ATM manager participating in the current transaction. |
| Status |
The status of the ATM manager with respect to the current transaction, followed by a summary value. Possible summary values are:
|
| Err | Enter a non-blank character and press Enter to display details of any errors recorded in a manager’s feedback block. See Display Error Information. |
If the transaction is under the control of the host system transaction coordinator (HOST TC), PF9 at the foot of the screen is labelled “HstTC”. Pressing PF9 invokes the Host TC Token Display window showing the identifiers used by the host transaction coordinator for the transaction.
ATM records the details of errors in a feedback block in the transaction’s global transaction queue entry (GTQE).
If the error occurs while processing a request from an ATM client proxy or remote ATM manager, the feedback block is returned to the component that issued the request; otherwise, it remains intact in the GTQE.
To display the feedback block for a transaction, press PF10 on the Transaction Details screen.
To display the feedback block of a remote ATM manager participating in a transaction, type a non-blank character next to the ATM manager entry in the Participating ATMs list and press Enter.
The error information is displayed in a window with the following layout:
07:29:20 ***** A D A B A S TRANSACTION MANAGER 8.2.2 ***** 2006-04-19
- Transaction Details - T12210M1
Manager: 20531 +-------------Error Information-------------+ erminal: TCP0
Clnt Type: 84 - | 07:29:22 Error Information 2006-04-19 | Jobname: QTT81013
Status: 8000000 | T1ERRIM1 | PRR ISN: 00000000
CommID: 000FA10 | | F1F34040
XID: C1C4C10 | ERROR CODES - Primary: 00204 | 40404040 404000F6
4400E3F | Secondary: 00204 | F1F3BEAD 3E5BBCD9
4D00000 | Queueing: 00000 | 00000000 C2D80000
0000000 | Database No.: 20532 | 00000000 00000000
Start: 04/19 | Command Code: ET |
Last Act: 04/19 | Response/Sub-Code: 022 / 0021 |
| | 00
<----------CHA | AUTO-BACKOUT - Return Code: 00000 | ING ATMs-->
DBNo. TM Node | Database No.: | us Err
20532 | Command Code: |
| Response/Sub-Code: 000 / 0000 |
| |
| PF3 Exit |
| |
+-------------------------------------------+
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Refr Stop ET Top ErrI Menu
|
The following information is provided.
| Field | Description |
|---|---|
| ERROR CODES |
Describes one or more errors that occurred during processing of the transaction. The meaning of the error code in the fields Primary and Secondary can be found in the section Messages and Codes. In the example, an |
| AUTOBACKOUT |
If an error caused ATM to attempt an autobackout, this field provides details of any error that occurred during the autobackout process. The meaning of the error code in the Return Code field can be found in the section Messages and Codes. |
| Err | Enter a non-blank character and press Enter to display details of any errors recorded in an ATM feedback block. |
This function can be used if it becomes necessary to terminate a transaction by manual intervention. For example, a client session has abended without completing a transaction and it is necessary to free its resources.
Caution:
If you terminate a transaction branch or a part of a transaction
that is controlled by an external transaction coordinator, only the local
branch or local part of the transaction is affected. This could compromise the
integrity of the distributed transaction.
To invoke this function, press PF5 on the Transaction Details screen.
The following window will appear:
07:17:35 ***** A D A B A S TRANSACTION MANAGER 8.2.2 ***** 2006-04-19
- Transaction Details - T12210M1
Manager: 20531 Terminal: TCP0
Clnt Type: 84 - +-----------Stop Transaction Options------------+ ame: QTT81013
Status: 8000000 | 07:26:34 - Stop Transaction - 2006-04-19 | ISN: 00000000
CommID: 000FA10 | T1STOPM1 | 4040
XID: C1C4C10 | | 4040 404000F6
4400E3F | WARNING: Transaction integrity could be lost | BEAD 3BBC0734
EC80000 | Select one of the following functions: | 0000 C2D80000
0000000 | _ Stop a transaction | 0000 00000000
Start: 04/19 | _ Stop all trans in same service |
Last Act: 04/19 | _ Stop all transactions |
| |
<----------CHA | Select additional options as required: | ATMs-->
DBNo. TM Node | _ No rsp 9 for client | Err
20532 | _ Transfer to STJ |
| |
| PF1 Help PF3 Exit PF5 Confirm |
| |
+-----------------------------------------------+
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Refr Stop ET Top ErrI
|
Mark one of the following functions:
| Function | Description |
|---|---|
| Stop a transaction |
Terminate the transaction for which detail information is being displayed. |
| Stop all trans in the same service |
Terminate the transaction for which detail information is being displayed and all other incomplete transactions belonging to clients in the same address space. This option can be used, for example, to terminate all transactions belonging to clients in a given CICS region. When this option is invoked, a console message is issued so that the event can be audited. |
| Stop all transactions |
Terminate all incomplete transactions. When this option is invoked, a console message is issued so that the event can be audited. |
By default, the transaction manager attempts to complete (back out or commit) any incomplete transaction within the scope of the selected STOP function, according to the transaction’s current status. In the event that the outcome was a back out, the stopped transaction(s) will remain in the transaction manager’s list with a pending response 9 sub-code 92 (a subsequent STOP function against such a pending transaction will result in its removal from the list).
You can optionally increase the severity of the action to be applied to the selected incomplete transactions by marking one of the following options:
| Function | Description |
|---|---|
| No rsp 9 for client |
By selecting this option, no such pending response code will be retained and the transaction(s) will be immediately removed from the transaction manager’s list. Note: |
| Transfer to STJ |
Selecting this option will result in (a) the transfer of transaction details to the suspect transaction journal (STJ), (b) the removal of the transaction(s) from the transaction list, and (c) a console message identifying the transaction in question, but only under the following circumstances:
Note: Caution: |
Pressing PF6 from the Transaction Details screen will display any pending ET data if the transaction is partially through the commit process.
The ET data is displayed in hexadecimal and character format:
08:08:56 ***** A D A B A S TRANSACTION MANAGER 8.2.2 ***** 2006-04-18
- ET Data Display - T1ETDTM1
TM Node: 20531
Offset <-------- Memory Contents --------> <--Characters-->
00000000 C9E2D640 00010266 00000000 00000000 ISN ???
00000010 40404040 40404040 40404040 40404040
00000020 40404040 40404040 40404040 40404040
00000030 40404040 40404040 40404040 40404040
00000040 40404040 40404040 40404040 40404040
00000050 40404040 40404040 40404040 40404040
00000060 40404040 40404040 40404040 40404040
00000070 40404040 40404040 40404040 40404040
00000080 40404040 40404040 40404040 40404040
00000090 40404040 40404040 40404040 40404040
000000A0 40404040 40404040 40404040 40404040
000000B0 40404040 40404040 40404040 40404040
000000C0 40404040 40404040 40404040 40404040
000000D0 40404040 40404040 40404040 40404040
000000E0 40404040 40404040 40404040 40404040
000000F0 40404040 40404040 40404040 40404040
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Top Fwd
|
Selecting option 3, Pending Response Codes, from the Transaction Manager Information menu will display a list of client sessions for which the manager has pending response codes. Such a pending response code will be set, for example, when a transaction is timed out by the manager. The list looks like this:
07:42:39 ***** A D A B A S TRANSACTION MANAGER 8.2.2 ***** 2006-04-19
- Pending Response Codes - T12300M1
Manager: 20531 Terminal: TCP0
Rsp- Sub- Time
ID (Hex) Jobname code code MMDD HH:MM DBs
TM?q ? E3D41B9800000007 DAEFCI18 9 86 0419 07:40 1
TM?q ? E3D41B9800000011 QTT81013 9 86 0419 07:39 1
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
|
The following information is provided:
| Function | Description |
|---|---|
| C | Enter a non-blank character and press Enter to obtain more detailed information about a particular pending response code. See Display Pending Response Code Details. |
| ID | The Client ID of the client session for which the pending response code is set. The ID is shown both in character and hexadecimal formats. |
| Jobname | The name of the job under which the client session is or was executing. |
| Response code | The pending response code. |
| Sub-code | The pending response code’s subcode. |
| Time | The time at which the pending response code was set. The date has the format MM/DD. |
| DBs | The number of databases that took part in the transaction which caused the pending response code to be set. |
More detailed information about a pending response code can be obtained by marking the C column in the Pending Response Codes screen.
The following screen will appear:
07:53:46 ***** A D A B A S TRANSACTION MANAGER 8.2.2 ***** 2006-04-19
- Pending Response Codes - T12310M1
Manager: 20531 Terminal: TCP0
CommID: 000FA10E 20860000 40404040 40404040 00F64400 C3C9C3E2 E3C3E3F4
<--------------DATABASES-------------->
ID: CICSTCT4 DBNo. TM Node Status Resp/subcode
Job name: QTT81013 20532 0401 BKD OUT 0 0
Response code: 9
Sub-code: 86
MM/DD HH:MM.SS
Time: 04/19 07:39.00
ISN: 2
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Refr Del Menu |
The following information is provided on the left of the screen:
| Function | Description |
|---|---|
| CommID | The Adabas communication ID of the client session for which the pending response code is set. |
| ID | The last 8 bytes of the Adabas communication ID of the session for which the pending response code is set, in character format. |
| Jobname | The name of the job under which the client session is or was executing. |
| Response code | The pending response code. |
| Sub-code | The pending response code’s subcode. |
| Time | The time at which the pending response code was set. The date has the format MM/DD. |
| ISN | The ISN of the record which represents this pending response code in the manager’s PRR file. |
The right-hand side of the screen displays a list of the databases that were changed by the transaction which caused the pending response code to be set.
If the list is too long to fit on the display, “More” appears at the foot of the screen. Use PF8 to scroll down the list and PF7 to return to the top of the list.
Normally, a pending response code is kept in the manager’s memory, and possibly also in its recovery file, until the manager has an opportunity to return it to the transaction’s owner, or until the owner is known to have disappeared.
For more information, see the section Introduction, Pending Response Codes.
The Display Pending Response Code Details screen provides a facility for deleting the pending response code. To use this facility, display the details of the pending response code that you want to delete, then press PF5 (“Del”). You will be prompted to confirm your intention to delete the pending response code.
Note:
If you use this facility, the pending response code will be removed
from the manager’s memory and from the recovery file, so the owner of the
transaction will never receive the pending response code. This might mean, for
example, that the owning client will never become aware that the previous
transaction was backed out.
Selecting option 4, Display Known Databases, from the Transaction Manager Information menu will display a list of all databases in the network that are known to this ATM. The list includes all databases that are enabled for two-phase commit processing; that is,
all local databases that are running with ADARUN
DTP=RM, and
all remote databases that are running with ADARUN
LOCAL=NO and have been identified to the transaction manager by
remote ATMs.
Other databases may appear in the list, depending on the way they are used. The display has the following format:
08:13:38 ***** A D A B A S TRANSACTION MANAGER 8.2.2 ***** 2006-04-18
- Display Known Databases - T12400M1
Manager: 20531
Date/Time
C DB No. TM Node DTP Usage MM/DD HH:MM.SS
_ 131 20531 N
_ 20532 20531 Y 2 04/18 08:04.41
_ 20536 20535 Y 1 04/18 08:05.46
Mark with L(ist) or Q(uiesce)
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Refr Top
|
The following information is provided
| Field | Description |
|---|---|
| C |
Command input field. The following options are provided:
|
| DB No. |
The normal Database ID. |
| Manager |
The ID of the database’s local ATM. |
| DTP | Indicates whether the database is running
DTP=RM (Y) or DTP=NO (N).
|
| Usage | The number of open transactions that involve the database. |
| Date/Time | The time at which the database’s local ATM became aware that the database was active. This can be either the time at which the database was started or the time at which its local ATM started. |
Option 5, Display Partner Transaction Managers, on the Transaction Manager Information menu displays a list of remote ATMs in the network that are known to this ATM.
08:18:45 ***** A D A B A S TRANSACTION MANAGER 8.2.2 ***** 2006-04-18
- Display Partner ATMs - T12500M1
Manager: 20531
ATM Session: 43 COR Group: CORATM81 Date/Time
TM Node Jobname Status Session MM/DD HH:MM.SS Host TC
20535 ATM20535 84 ACTIVE 41 04/18 08:05.26 N
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Refr Top
|
The following information is provided.
| Field | Description |
|---|---|
| ATM Session |
The ATM Session field above the table on this display indicates the number of the current session of the ATM identified by the Manager field above it. Session numbers begin with 1 when the transaction manager is first started and increase by 1 each time it is restarted. |
| COR Group | This field above the table of partner ATMs displays the name of the Adabas System Coordinator group with which the local transaction manager and its partner ATMs are associated. |
| TM Node |
The ID of the remote ATM. |
| Jobname | The name of the transaction manager job. |
| Status |
The latest known status code for the remote transaction manager, together with a summary interpretation. Possible values are:
|
| Session | The number of the current session of the partner ATM manager. Session numbers begin with 1 when an ATM manager is first started and increase by 1 each time it is restarted. |
| Date/Time | The time at which the remote ATM manager was started. |
| Host TC | Indicates whether the remote ATM is interfacing to its local host transaction coordinator. Only RRMS under z/OS is currently supported as a local host transaction coordinator for an ATM manager. |
This option can be used to list and display recovery records, to browse the suspect transaction journal, to list and display migrated transaction records, and to list and display pending error records.
Selecting option 6, Recovery File Functions, from the Transaction Manager Information menu displays the following menu:
08:24:28 ***** A D A B A S TRANSACTION MANAGER 8.2.2 ***** 2006-04-18
- Recovery File Functions - T12600M1
Manager: 20531
Code Service
---- ----------------------------------
1 List Recovery Records
2 Browse Suspect Transaction Journal
3 List Migrated Transaction Records
4 List Pending Error Records
. Exit
---- ----------------------------------
Code: _
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Menu |
Select code 1 or 2 to list recovery records or browse the suspect transaction journal (STJ). The order in which records are displayed is not significant.
For both options, the resulting list has the following layout; only the subheading differs:
08:26:51 ***** A D A B A S TRANSACTION MANAGER 8.2.2 ***** 2006-04-18
- Suspect Transactions - T12610M1
Manager: 20531 Terminal: TCEQ
C L/R <----------------------Communication ID----------------------> Client ID
_ L 000F7100 20640000 40404040 40404040 00F1E100 B8E5C585 C647B560 TM?q ?
_ L 000F7100 20640000 40404040 40404040 00F71380 B8E71F47 3206D801 TM?q
_ L 000F7100 20640001 40404040 40404040 00F24880 E4D2D7C4 404040F2 TM?q ?
_ L 000F7100 20640000 40404040 40404040 00F11B80 B8EFAAF9 6445FE42 TM?q
Mark with D(isplay) or P(urge)
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12
Help Exit Refr Top Menu
|
The following information is provided
| Item | Description |
|---|---|
| L/R | Indicates whether the transaction’s owner is (or was) local to (L) or remote from (R) the transaction manager; that is, whether or not the client is (or was) executing in the same operating system instance. |
| Communication ID | The transaction owner’s Communication ID in hexadecimal format. |
| Client ID | The transaction owner’s Client ID in character format. |
For a more detailed display of an item, type D in the C column next to the item and press Enter. The resulting display has the same layout as the Transaction Details screen.
To delete a record from the STJ or the recovery record file, type P (for “purge”) in the C column next to the selected item and press Enter. You are prompted to confirm that the record should be deleted.
Caution:
The purge function is provided for housekeeping of the STJ file.
If you use it to delete a record from the recovery record file, you could
compromise the integrity of the related global transaction, and results are
unpredictable. Therefore, for audit purposes, a console message is issued when
a recovery record is deleted.
To list migrated transaction records, enter code 3. If a client executes in an environment in which dynamic transaction routing can take place, and the client’s session is migrated from one system image to another while the client has a global transaction in progress, a migrated transaction record (MTR) is created. An MTR is deleted when the transaction finally terminates. MTRs are stored in a central file store that is provided for the Adabas System Coordinator daemons in the associated COR group.
08:30:35 ***** A D A B A S TRANSACTION MANAGER 8.2.2 ***** 2006-04-18
- Migrated Transactions - T12630M1
Manager: 20531 Terminal: TCEQ
C <----------------------Communication ID----------------------> TM Node
_ 000F7100 20640000 40404040 40404040 00F71380 B8E71F47 3206D801 20535
Mark with D(isplay) or P(urge)
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12
Help Exit Refr Top Menu
|
The following information is provided.
| Field | Description |
|---|---|
| C |
Command input field. The following options are provided:
|
| Communication ID |
The client’s 28-byte Adabas Communication ID. |
| TM Node | The Node ID of the transaction manager that is currently local to the client who owns the transaction. |
The Display function produces a display with the following format:
08:33:14 ***** A D A B A S TRANSACTION MANAGER 8.2.2 ***** 2006-04-18
- Migrated Transactions - T12631M1
Manager: 20531 Terminal: TCEQ
CommID: 000F7100 20640000 40404040 40404040 00F71380 B8E71F47 3206D801
XID: C1C4C101 00000050 00000002 5033000F 71002064 00004040 40404040 404000F7
1380B8E7 1F473206 D801D7C4 F0F34040 4040C4C1 C5C6C3C9 F1F8B902 C6B15FFB
76610000 00000000 00000000 00000000 00000000 00000000 00000000 C2D80000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
CICS URID: 0000000000000000 Appl ID: TRUE:
RRS URID: 00000000000000000000000000000000
Owning ATM: 20535
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12
Help Exit Refr Menu
|
| Field | Description |
|---|---|
| CommID | The 28-byte Adabas Communication ID of the client who owns the transaction. |
| XID | The ID of the transaction. |
| CICS URID | If the transaction is controlled by the CICS syncpoint manager, the CICS URID might be displayed. |
| Appl ID | If the transaction is controlled by the CICS syncpoint manager, the CICS appl ID might be displayed. |
| TRUE | If the transaction is controlled by the CICS syncpoint manager, the name of the CICS Task Related User Exit might be displayed. |
| RRS URID | If the transaction is controlled by RRMS, the RRS URID might be displayed. |
| Owning ATM | The Node ID of the transaction manager that is currently local to the client who owns the transaction. |
To list pending error records, enter code 4. If a transaction fails in such a way that the ATM manager sets a pending response code, a pending error record might also be stored, so that the pending response code will survive a component failure, or restart of the transaction manager. Pending error records are listed like this:
07:41:53 ***** A D A B A S TRANSACTION MANAGER 8.2.2 ***** 2006-04-19
- Pending Error Records - T12640M1
Manager: 20531 Terminal: TCP0
Rsp- Sub- Time
C ID (Hex) Jobname code code MMDD HH:MM DBs
_ TM?q ? E3D41B9800000007 DAEFCI18 9 86 0419 07:40 1
_ TM?q ? E3D41B9800000011 QTT81013 9 86 0419 07:39 1
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Refr Top Menu |
The fields in this screen are as described in the section Display Pending Response Codes.
For a more detailed display of an item, type D in the C column next to the item and press Enter. The resulting display has the same layout as the Pending Response Code Details screen
To delete a pending error record, type P (for “purge”) in the C column next to the selected item and press Enter. You are prompted to confirm that the record should be deleted
Note:
If you delete a pending error record using this function, the
transaction manager retains details of the pending response code in memory. If
the owner of the transaction tries to do further transactional work during the
current execution session of the transaction manager, the pending response code
will be given. If you want to remove the pending response code from the
transaction manager’s memory as well as from the recovery file, use the
“delete” function of the Pending Response Details display.
