OSI/AS Configuration and Management Manual
Installing and Configuring the Subsystem
OSI/AS Configuration and Management Manual—424119-001
4-33
Adding APPL ENTRY Objects
Considerations
•
Make sure that you have added any L5SERVER process that you refer to in these
commands. For example, the commands in the last example refer to TAPS process
$OSIM.#TAPS.OSI5A. You must register this process with the OSI manager, using
the SCF ADD PROCESS command.
•
Also make sure that you have added any L5PROFILE objects that you refer to in
these commands. For example, the command in the first example refers to profile
$OSIM.#L5.L5VSN2. You must add this profile to the OSI manager process using
the SCF ADD PROFILE command.
•
Notice that the last example does not assign an L5PROFILE object. If you do not
specify a Layer 5 profile for a TSEL address, all transport subdevices that use that
TSEL address are configured with default values, which are defined by the Layer 5
SERVICE object.
Adding APPL ENTRY Objects
Add APPL ENTRY objects to register local and remote applications with the OSI
manager process. An APPL ENTRY object defines an application name and associates it
with an OSI address hierarchy. You do not need to add these objects to your OSI
subsystem if your local user applications supply the information directly by means of
APS procedure calls.
Registering Local Applications
APPL ENTRY objects for local applications assign application names to OSI addresses
that are served by local NSAPs.
Examples
The following commands register two local application names in the MIB:
ADD ENTRY $OSIM.#APPL.LOCAL1, NSAP 9A0001, TSEL 0001 &
, SSEL 0001, PSEL 0001 &
, APTITLE (1 3 9999 1 7) &
, AEQUALIFIER 0329
ADD ENTRY $OSIM.#APPL.LOCAL2, NSAP 9A0001, TSEL 0002 &
, SSEL 0002, PSEL 0002 &
, APTITLE (1 3 9999 1 7) &
, AEQUALIFIER 0329
Each command and object-spec register a user application with the OSI manager process
$OSIM:
ADD ENTRY $OSIM.#APPL.LOCAL1
ADD ENTRY $OSIM.#APPL.LOCAL2
Each application registered to the same OSI manager process must have a name that is
unique within the OSI/AS subsystem. The choice of local application names is a local