You can use the network discovery function in System Coordinator administration to perform tasks against a selected System Coordinator daemon within which your transaction manager is running as a service. First identify the daemon, and then use "T" (for Tasks) to see what tasks can be performed. One such task is the ability for administrators to control the location of ET data by performing ET data management activity between the transaction manager and Adabas databases.
For more information refer to the tasks option in the Network Discovery function of the Current Activity Displays section in Adabas System Coordinator Online Services.
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 "TM: 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
