OSI/MHS Configuration and Management Manual

OSI Address Configuration in OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
D-3
Configuring the OSI Stack and OSI/MHS in Separate
Files
MR-T-SELECTOR 4D5258323541, &
MR-NSAP 703285003011
== OSI stack configuration for MRGRP1
add entry #tsel.4D5258323541, server $uosi.#taps.uas1
add entry #nsap.703285003011, &
server $UOSI.#TSP.UTS1, &
profile $UOSI.#L4.L4WAN, &
snpa 11, &
netaddr-mode normal
add entry #snpa.11, server $uosi.#nsp.x25a,
profile $uosi.#L3.mta1proA
== #L3 profile for X.25 connection
add profile #L3.mta1proA, x25destaddr '703285003011', &
x25remotenet x25xa, &
x25negotiate (L3window,pktsize, thruput), &
x25port 11
Configuring the OSI Stack and OSI/MHS in Separate Files
The first three steps of this approach to configuration—creating a clean environment,
configuring the common processes, and configuring the common profiles—are
identical to the first three steps of the approach described above. The difference in the
two approaches lies in step 4, configuring OSI addresses.
The procedure below suggests that you use an ADD ENTRY #APPL command to
define each object to be configured in the OSI stack configuration file. The ADD
ENTRY #APPL command groups the components of an OSI address together and
assigns a name to them. (Note that the APPL object referred to here is an OSI object.
It is not the same as the OSI/MHS APPL object.)
Some applications can refer directly to OSI APPL names. OSI/MHS does not currently
support OSI APPL names; however, it is good practice to use them. The ADD ENTRY
#APPL command lets you record which OSI/MHS object a given address applies to—
information that may otherwise be lacking from the stack configuration file. The use of
ADD ENTRY #APPL also allows you to verify the OSI stack configuration by using the
SCF CHECK command.
To configure the OSI stack:
1. Create a clean environment.
a. Stop all OSI processes and delete any unwanted database files.
b. Make sure that X25AM, PAM (in G06 and later RVUs), and TLAM (in D-series
RVUs) lines are stopped and that these lines have been set with the correct
parameters.
Note. SCF does not allow duplicate OSI addresses. If you have two or more groups listening
on one address, configure the first group, then use a comment to indicate that the additional
groups use the same address.