OSI/MHS Configuration and Management Manual
Configuring Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
5-12
MTA (Adjacent MTA) Object
MTA (Adjacent MTA) Object
In the sample configuration, a password exchange is required when an association is
established, so you must use the first three attributes listed below. The other attributes
are optional.
•
REM-LOGON-VALIDATION (REM-LOGON)—must have a value of ON.
•
REM-OUR-PASSW (OUR-PWD)—specifies the password of the source (sending)
MTA. The source MTA sends this password to the adjacent MTA, along with an
association request. This allows the adjacent MTA to check the identity of the
sending MTA.
•
REM-THEIR-PASSW (THEIR-PWD)—specifies the password of the adjacent
(receiving) MTA. The sending MTA receives this password from an adjacent MTA
and uses it to validate the identity of the adjacent MTA.
•
REM-APPLIC-CONTEXT (CONTEXT)—specifies the MTS transfer-protocol
application context that is supported by the adjacent MTA.
•
REM-DIALOGUE-MODE (MODE)—must have a value of MONOLOGUE.
An MTA object uses the following OSI addresses for the remote or destination
addresses of an MTA object:
•
REM-TSELECTOR-n (REMn-TSEL)
•
REM-NSAP-n (REMn-NSAP)
For the local or source addresses of an MTA object, it uses:
•
LOC-TSELECTOR-n (LOCn-TSEL)
•
LOC-NSAP-n (LOCn-NSAP)
•
REM-MTA-NAME (REM-MTA)—specifies the MTA name of the adjacent (remote)
MTA; used by other MTAs to identify the adjacent MTA.
•
COUNTRY-NAME (COUNTRY)—specifies the complete name of the country in
which the adjacent MTA resides.
•
REM-ADMD—specifies the name of the ADMD that serves the adjacent MTA.
•
REM-PRMD—specifies the name of the PRMD that serves the adjacent MTA.
This attribute is required to configure a PRMD.
ROUTE Object
The ROUTE object attributes defined to an OSI/MHS subsystem provide the criteria for
selecting outgoing message routes.
•
PRI—selects the priority of the route. The range is 1 to 99, where 1 is the highest
priority. In the examples in this section, primary route objects have a priority of 1;
backup route objects have a priority of 10.