This section describes the administrative functions relating to Adabas Transaction Manager that are found with Adabas System Coordinator.
You can use the network discovery function in System Coordinator administration to display/modify the transaction manager distributed transaction timeout. Use the tasks function against a System Coordinator daemon to see what can be performed as follows…
To display/modify the Transaction Manager distributed transaction
timeout
Use "T" on the row for the System Coordinator daemon where your transaction manager service is running to see the list of tasks allowed.
Select the "Set TM global transaction time limit" task and press PF5.
The following window will appear showing the current time limit:
10:30:49 Set TM Distributed Transaction Timeout 2011-03-03
Current target: 1650 Type: System Coord
Current distributed transaction timeout(secs): 720_____
PF3 Exit PF5 Set TMGTT
|
Modify the time limit by changing the value and pressing PF5.
You can use the network discovery function in System Coordinator administration to stop all sessions on a selected database that have been dormant for a specified number of seconds. Use the tasks function against a database to see what can be performed as follows…
To stop inactive sessions
Use "T" on the row for the appropriate database to see the list of tasks allowed.
Mark the "Stop inactive users" task, specify the dormant period and press PF5.
Current Activity Displays are now in System Coordinator. Refer to Activity Displays for more information.
You can use the current activity function in System Coordinator administration to perform tasks against a selected session. First identify the session, and then use the PF10 "tasks" function off the session statistics display to see what tasks can be performed. One such task is the ability for administrators to automatically stop a selected session in all databases where that session is active. This is a large productivity gain because it avoids the administrator having to seek out manually those databases where this session is active.
To stop an Adabas session
Use PF10 "Tasks" off the session statistics display to see the list of tasks allowed.
Mark the "Stop Adabas UQEs" task, and press ENTER.
You can use the network discovery function in System Coordinator administration to display/start ET data management activity. Use the tasks function against a System Coordinator daemon to see what can be performed as follows…
To display/start ET data management activity
Use "T" on the row for the System Coordinator daemon where your transaction manager service is running to see the list of tasks allowed.
Select the "ET data management" task and press PF5.
The following screen will appear:
11:28:39 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 ***** 2012-01-25
- ET data management - U1UTR0M2
Node ID: 20530
-- Recent ET data management activity ---------------- 2011-10-23 12:15:01
Status: Ended Result: Success
From: Adabas database 20532 To: Current TM
ET data reads: 1178 Replace: Yes
writes: 1178
-- Start ET data management activity ------------------------------------------
From (choose one): _ Current TM (mark)
_____ Other TM node (prior release)
_____ Adabas database
To (choose one): _ Current TM (mark)
_____ Other TM node (prior release)
_____ Adabas database
Replace (Y/N): _
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Exit Refr Start Menu
|
The most recent ET data management activity information is displayed as follows:
| Field | Description |
|---|---|
| Status | The status of the most recent activity. |
| Result | The result of the most recent activity. |
| From | Identifies the source from which the ET data was read. |
| To | Identifies the target in which ET data was stored. |
| Replace | Indicates whether or not ET data in the target location was overwritten by ET data from the source location, if both locations contained data for the same ETID. |
| ET data reads | The count of ET data read from the source location. |
| ET data writes | The count of ET data stored at the target location. |
Optionally, start a new activity by modifying the following fields and pressing PF5.
| Field | Description |
|---|---|
| From | Identify the source from which the ET data is to be read. |
| To | Identify the target in which ET data will be stored. |
| Replace | Indicates whether or not ET data in the target location will be overwritten by ET data from the source location, if both locations contain data for the same ETID. |
Note:
If you are upgrading from a prior release then the current release
notes will indicate whether or not ET data migration is necessary. If this is
the case then specify the following options to ensure your ET data is migrated
from the old release to the new release:
From: Define your old TM node id alongside ‘Other TM node (prior release)’
To: Mark ‘Current TM’
Replace: Y
Use the Daemon Group Parameter option in the Maintenance menu of the System Coordinator online administration to maintain TM controls as follows…
To maintain TM controls
Use "L" on the row for the appropriate System Coordinator group name to see the list of daemon members in which your transaction manager service is running.
Use "M" on the row for the daemon member in which your transaction manager service is running and for which you wish to maintain TM controls.
Use “PF11” to select the TM controls maintenance
12:50:36 ***** A D A B A S SYSTEM COORDINATOR 8.2.2 ***** 2012-02-27
- Adabas Transaction Manager Daemon Parameters - C11261M1
Run-mode: Pulsing (node 2650)
Group Name: WORKSHOP Daemon: ICFDCOR5 Operating System: Multi
SVC ID: 254 Node..: 2650
Distributed transaction timeout(secs)..: 720_____ (1 to 16777215)
Transaction recovery...................: NORMAL__ (Normal/Force/ForceALL)
Enforce ADARUN DTP=RM..................: No_ (Yes/No)
ET data storage location...............: RM (TM/RM
Open distributed transaction (system)..: NO (Yes/No)
Concurrency..: 100 (10 to 32767)
Command ==>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Upd Prods Menu
|
For information on each of these parameters refer to TM Controls.
To purge TM controls
The TM controls will automatically be purged when its associated daemon member is purged.
