Oracle® Communications EAGLE Database Administration - GTT User's Guide Release 46.7 E97332-02 |
|
![]() Previous |
![]() Next |
This procedure is used to change the mated application
type of an existing mated application (MAP) group or MAP set using the
chg-map
command with the
rc
parameter.
chg-map
command contains other
parameters that are not used in this procedure. Perform these procedures as
applicable to change the other parameter values.
chg-map
command can also be used to
add point code/SSN entries to an existing MAP group or MAP set. This action is
not covered in this procedure. If you wish to add point code/SSN entries to an
existing MAP group or MAP set, perform one of these procedures.
The
chg-map
command in this procedure uses
these parameters.
:pc/pca/pci/pcn/pcn24
–
The point code of the primary signaling point that is to receive the message.
Note:
The point codes can be either an ANSI point code (pc/pca), ITU-I or ITU-I spare point code (pci), a 14-bit ITU-N or 14-bit ITU-N spare point code (pcn), or a 24-bit ITU-N (pcn24) point code.Note:
Refer to Chapter 2, Configuring Destination Tables, in the Database Administration - SS7 User's Guide for a definition of the point code types that are used on the EAGLE and for a definition of the different formats that can be used for ITU national point codes.:ssn
– Subsystem number
– the subsystem address of the primary point code that is to receive the
message.
:rc
– The relative cost
value of the primary point code and subsystem, defined by the
pc
/pca
/pci
/pcn
/pcn24
and
ssn
parameters. The
rc
parameter has a range of values
from 0 to 99.
:mapset
– The MAP set
ID that the mated applications are assigned to, shown in the
rtrv-map
output. MAP set IDs are shown
only if the Flexible GTT Load Sharing feature is enabled. The
mapset
parameter value cannot be
changed in this procedure. If the
rtrv-map
output shows the
MAPSET
field, the
mapset
parameter must be specified
with the
chg-map
command. If the
rtrv-map
output does not show the
MAPSET
field, the Flexible GTT Load
Sharing feature is not enabled. The
mapset
parameter cannot be specified
with the
chg-map
command. The
mapset
parameter has two values.
dflt
– to change the
mated application in the default MAP set. The EAGLE’s true point code (shown in
the
rtrv-sid
output) and subsystem can
be assigned only to the default MAP set.
The mated application to be changed must be in the database.
If an existing dominant, load shared, or combined dominant/load shared mated application is being changed to a solitary mated application, the existing mated application must be removed from the database, and the new solitary mated application, containing the primary point code and subsystem from the mated application that was removed, must be added to the database.
If the mated application contains the EAGLE’s true point code, the relative cost value assigned to this point code must be the lowest value in the mated application.
Canceling the
RTRV-MAP
Command
Because the
rtrv-map
command used in this
procedure can output information for a long period of time, the
rtrv-map
command can be canceled and
the output to the terminal stopped. There are three ways that the
rtrv-map
command can be canceled.
F9
function key on the keyboard at
the terminal where the
rtrv-map
command was entered.
canc-cmd
without the
trm
parameter at the terminal where
the
rtrv-map
command was entered.
canc-cmd:trm=<xx>
, where
<xx>
is the terminal where the
rtrv-map
command was entered, from
another terminal other that the terminal where the
rtrv-map
command was entered. To
enter the
canc-cmd:trm=<xx>
command, the
terminal must allow Security Administration commands to be entered from it and
the user must be allowed to enter Security Administration commands. The
terminal’s permissions can be verified with the
rtrv-secu-trm
command. The user’s
permissions can be verified with the
rtrv-user
or
rtrv-secu-user
commands.
For more information about the
canc-cmd
command, refer to
Commands User's Guide.
Figure 2-112 Change the Mated Application Type - Sheet 1 of 6
Figure 2-113 Change the Mated Application Type - Sheet 2 of 6
Figure 2-114 Change the Mated Application Type - Sheet 3 of 6
Figure 2-115 Change the Mated Application Type - Sheet 4 of 6
Figure 2-116 Change the Mated Application Type - Sheet 5 of 6
Figure 2-117 Change the Mated Application Type - Sheet 6 of 6