At the end of the installation process, you should verify that the installation was successful by performing the steps described in this section.
to verify basic operation of the Adabas Transaction Manager
proxy:
If it is currently executing, stop the TP system where you will use Adabas Transaction Manager Online Services.
This must be a TP system in which the Adabas Transaction Manager
proxy has been installed, with job parameter setting
ATM=ON.
Start (or restart) the TP system so that the Adabas Transaction Manager proxy is loaded and initialized.
Log on to the Adabas Online System (AOS). Select Adabas Transaction Manager to invoke the Online Services application SYSATM.
SYSATM automatically searches for an active transaction manager daemon in the local system. If the Adabas Transaction Manager daemon is not active in the local system, a message is displayed indicating that status. You can ignore the message at this time.
Press Enter, then make a note of the Terminal ID that is displayed on the main menu.
Select Local User Information, then Local Users.
One of the listed items should be recognizable either as the Terminal ID you noted in step 4 or the User ID of your current session, depending on your TP environment. This verifies the basic operation of the Adabas Transaction Manager proxy.
to verify communication with the Transaction Manager daemon:
Start the transaction manager daemon and re-enter the SYSATM application.
The Adabas Transaction Manager daemon is identified automatically by the Adabas Transaction Manager proxy when you enter SYSATM.
Select Transaction Manager Daemon Information, then Display Zap Information.
Displaying the list of applied fixes provided by this function verifies that communication with the Adabas Transaction Manager daemon is functioning correctly, even if the list of fixes is empty.
Terminate your SYSATM session.
to verify two-phase commit operation:
Start two databases with the parameter setting ADARUN
DTP=RM: one database containing a standard Employees file and the
other database containing a standard Vehicles file.
In library SYSMTvrs (where vrs is the version, revision, and system maintenance level of Adabas Transaction Manager), modify the test program DEMODTP so that it correctly refers to the Employees and Vehicles files.
Execute the DEMODTP program, supplying a non-zero value when prompted for a new personnel number.
When the message “About to commit” is displayed
start a new session in your TP system
log on to the Adabas Online System (AOS)
select Adabas Transaction Manager, then Transaction Manager Daemon Information, and then Active Global Transactions specifying List Sequence E.
The display of your pending transaction should indicate that two databases are involved in it.
Note:
This test is not valid in a CICS/RMI environment in which Natural
executes in pseudo-conversational mode. In this mode, the INPUT statement that
displays the message “About to commit” causes CICS to take a syncpoint at
end-of-task and commit the pending Adabas updates. To verify correct operation
in a CICS/RMI environment, this test should be done in a Natural session that
was started with PSEUDO=OFF.
Note:
This test is not valid in an IMS/TM environment in which RRMS acts
as the superior transaction coordinator. In such an environment, the ADARUN
TMSYNCMGR parameter should take the value NONE for the
purposes of this test.
Display additional details of the transaction by marking it on the screen and pressing Enter.
Verify that the Adabas Transaction Manager proxy’s view of the transaction is correct by returning to the main menu and selecting Local User Information, then Local Users.
Return to the session where your transaction is waiting to be completed and press Enter.
Use SYSATM to check that the transaction is no longer open.
The user session itself should still be listed under both the Local Users option of Local User Information and the Global User Queue option of Transaction Manager Daemon Information.
Execute the program DEMODTP again to ensure that the personnel number was changed consistently in the Employees and Vehicles files.
You can now be assured of global transaction integrity in client environments and databases where the software is installed.
