OSI/MHS Configuration and Management Manual

Managing Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
7-26
Verifying OSI Addresses in MTA Objects
This shows the state of the UAS1 Z0000DJ connection. The RTS process in the MR
group is waiting for an incoming association. The ACSE protocol is in the ATTACHED
state. This display verifies that all the connections that go through the OSI services
are already in place.
This display also shows to which OSI addresses your MHS subsystem is connected.
These addresses correspond to the addresses in your configuration file.
Verifying OSI Addresses in MTA Objects
To manage the OSI addresses in MTA objects, you must verify that the OSI addresses
are correctly identified. You do this by using the NAMES MTA command and the INFO
MTA command.
NAMES MTA Command
To monitor MTA-to-MTA connections, you first need to get the names of all the MTA
objects:
NAMES MTA $MHS1.*
This command displays the following screen.
This shows two MTAs: MTA2 and MTA3.
P-Sel.............
S-Sel.............
T-Sel............. 4D52 5832 3542
NSAP.............. 7032 8500 3012
Responding Address: (LOCAL)
Application-Name..
AE-Title:
AE-Title format. 0
AE-Qual.........
AP-Title........
P-Sel.............
S-Sel.............
T-Sel.............
NSAP..............
-> names mta $mhs1.*
MHS Names MTA \NEWYORK.*
MTA
MTA2
ROUTE
MTA2.PRIMARY1 MTA2.PRIMARY2 MTA2.PRIMARY3 MTA2.PRIMARY4
MTA
MTA3
ROUTE
MTA3.BACKUP1 MTA3.BACKUP2 MTA3.BACKUP3 MTA3.BACKUP4