OSI/AS Configuration and Management Manual

Routine Management Tasks
OSI/AS Configuration and Management Manual—424119-001
5-24
Altering ENTRY Objects
$OSIM.#TSP.L4A and NSP process $OSIM.#NSP.L3A to provide Layer 3 and
Layer 4 protocol services to users of this APPL ENTRY.
It is assumed that this example uses either a LAN or an X.25 network that
implements the 1984 X.25 standard, so that the default NETADDR-MODE setting
(NORMAL) applies.
•
The command to add a TSEL ENTRY object assigns a TAPS server process to the
TSEL. For example:
ADD ENTRY $OSIM.#TSEL.0011, L5SERVER $OSIM.#TAPS.L5A
Since the APPL ENTRY object called LOCAL1 references TSEL 0011, the OSI
manager process selects TAPS process $OSIM.#TAPS.L5A to provide Layer 5
services to users of this APPL ENTRY.
The following command registers a remote application named REMOTE1:
ADD ENTRY $OSIM.#APPL.REMOTE1, NSAP 9B0002 &
, TSEL 0002 &
, SSEL 0003
In this case, the NSAP address, the TSEL identifier, and the SSEL identifier belong to
the remote application and are not associated with processes belonging to your local
OSI/AS subsystem. Even so, the NSAP entry must still exist in the local MIB, as
follows:
ADD ENTRY $OSIM.#NSAP.9A0002
Altering ENTRY Objects
You can alter ENTRY objects to change the selection of processes that service particular
connections, to change the protocol configurations (the profiles) that these processes
implement, or to change other connection-related attributes.
The following command changes the profile associated with a local SNPA ENTRY
object:
ALTER ENTRY $OSIM.#SNPA.0002, L3PROFILE $OSIM.#L3.NPFILE2
The new profile could, for example, contain a new X.25 destination address. All future
calls through SNPA 0002 are routed to the new address.
The following command changes the SNPA associated with an NSAP ENTRY object:
ALTER ENTRY $OSIM.#NSAP.9A0001, SNPA 0002
The new SNPA could be served by a different X25AM or TLAM process on D-series
releases (or PAM process on G06 and above releases), or it could have a different
profile.
The following command changes the TAPS process associated with a TSEL ENTRY
object:
ALTER ENTRY $OSIM.#TSEL.0012, L5SERVER $OSIM.#TAPS.L5B
The effect is that applications that use TSEL 0012 are served by a new TAPS process.