OSI/MHS Configuration and Management Manual

OSI Address Configuration in OSI/MHS

OSI/MHS Configuration and Management Manual—424827-003

D-20

Use of SSEL and PSEL Addresses

The configurations shown in the examples can easily be extended to use SSEL and

PSEL addresses. In the ADD GROUP #MR command, these addresses are included

in the definition of IN(D). Here is an example:

ADD GROUP $zmhs.#mr.amr1, &

mr-p-selector 4C4F435053454C, &

mr-s-selector 4C4F435353454C, &

mr-t-selector 313131, &

mr-nsap 3233343232333530303136313031

In the ADD MTA command, SSEL and PSEL addresses can be included in OUT(S)

and IN(S) addresses. Here is an example.

== Adding SSELs and PSELs to an adjacent MTA

ADD MTA $zmhs.#Carl, &

rem-pselector-1 52454D5053454C, &

rem-sselector-1 52454D5353454C, &

rem-tselector-1 4D4853415431, &

rem-nsap-1 333131303432313030303931323036, &

loc-pselector-1 4C4F435053454C, &

loc-sselector-1 4C4F435353454C, &

loc-tselector-1 313131, &

loc-nsap-1 3233343232333530303136313031, &

rem-applic-context MTS-TRANSFER

It is not necessary to identify the SSELs and PSELs to the OSI stack. However, IN(S)

values in an incoming association are checked against the configured values, and a

validation failure occurs if the values do not match.