Go to primary content
Oracle® Communications EAGLE Database Administration - GTT User's Guide
Release 46.8
F11880-02
Go To Table Of Contents
Contents

Previous
Previous
Next
Next

Changing a Global Title Translation

This procedure is used to change the routing objects for messages requiring global title translation in the database using the chg-gtt command.

The chg-gtt command uses these parameters.

:gta – Global title start address – along with the egta parameter, identifies all valid global titles for the given translation type to translate to the given pc or ssn parameters. These are the non-SS7 addresses transmitted to the STP for translation.

:type/typea/typei/typeis/typen/typens/typen24 – The translation type and network type of the translation type that is being assigned to the global title translation. The value of this parameter is shown in the rtrv-tt output and provisioned in the Adding a Translation Type procedure.

:ttn – The name of the global title translation type

:egta – Global title end address. This parameter, along with the gta parameter, identifies all valid global titles for the given translation type to translate to the given pc or ssn parameters. These are the non-SS7 addresses transmitted to the STP for translation.

:xlat – Translate indicator – defines the type of global title translation that is to be performed.

:ri – Route indicator – indicates whether a subsequent global title translation is required.

:pc/pca/pci/pcn/pcn24 – The point code of the signaling point that is to receive the message.

Note:

See Chapter 2, Configuring Destination Tables, in 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 – identifies the subsystem address that is to receive the message.

:gtmodid - the name of the GT modification identifier shown in the rtrv-gtmod output and provisioned in the Adding Global Title Modification Information procedure. The GT modification identifier contains the information to modify the numbering plan, nature of address indicator, and the prefix or suffix digits in the called party address or calling party address portion of outbound MSUs.

:mrnset – The MRN set ID, shown in the rtrv-mrn command. The mrnset parameter can be specified only if the Flexible GTT Load Sharing feature is enabled. If the Flexible GTT Load Sharing feature is enabled and the ri parameter value will be ri=gt when this procedure is completed, and the original global title translation being changed in this procedure did not have an MRN set ID assigned to it, the mrnset parameter must be specified with the chg-gtt command. The MRN set ID assigned to the global title translation in this step must contain the point code value that will be assigned to the global title translation being changed in this step.

:mapset – The MAP set ID, shown in the rtrv-mrn command. The mapset parameter can be specified only if the Flexible GTT Load Sharing feature is enabled. If the Flexible GTT Load Sharing feature is enabled and the ri parameter value will be ri=ssn when this procedure is completed, and the original global title translation being changed in this procedure did not have an MAP set ID assigned to it, the mapset parameter must be specified with the chg-gtt command. The MAP set ID assigned to the global title translation in this step must contain the point code and SSN values that will be assigned to the global title translation being changed in this step.

The status of the Flexible GTT Load Sharing feature is shown in the rtrv-ctrl-feat output. To enable the Flexible GTT Load Sharing feature, perform the Activating the Flexible GTT Load Sharing Feature procedure.

:loopset - The value of this parameter is the name of the loopset that is assigned to the GTT. This parameter can be specified only if the SCCP Loop Detection feature is enabled. Enter the rtrv-loopset command to verify that the SCCP Loop Detection feature is enabled. Perform the Activating the SCCP Loop Detection Feature procedure, if necessary.

:cggtmod - The calling party GT modification indicator. This parameter specifies whether or not calling party global title modification is required. The values for this parameter are yes (calling party global title modification is required) or no (calling party global title modification is not required). This parameter can be specified only if the AMGTT or AMGTT CgPA Upgrade feature is enabled. Enter the rtrv-ctrl-feat command to verify that either the AMGTT or AMGTT CgPA Upgrade feature is enabled. If the AMGTT or AMGTT CgPA Upgrade feature is not enabled, perform the Activating the Advanced GT Modification Feature procedure to enable the required feature.

:split – Split or change the range of global title addresses. If the split=yes parameter is specified, the existing range of global title addresses is split based on the values of the gta and egta parameters. New entries are created in the global title translation table for each new range created by the split parameter. The attributes of each new entry, other than the range of global title addresses, are the same as the original global title translation entry, if these values are not changed when the chg-gtt command is executed. If other attributes are changed when the chg-gtt command is executed, the changed values are in each new entry created by the split parameter.

If the split=no parameter is specified, the range of global title addresses is replaced with the new range of global title addresses specified by the gta and egta parameters.

The default value for the split parameter is yes.

Caution:

Changes to the range of global title addresses occur only if the both the gta and egta parameters are specified and the values for either of these parameters, or both parameters are different from the original values in the global title translation. If the gta and egta parameters are specified for the global title translation being changed, and you do not wish to change either of these values, make sure the gta and egta values shown in the rtrv-gtt output for the global title translation being changed are specified in the chg-gtt command.

The following examples illustrate how the split parameter works and ranges of global title addresses can be changed.

A global title translation entry in the database contains this range of global title addresses, 5556000 - 5558000.

rlghncxa03w 10-07-25 09:45:31 GMT  EAGLE5 42.0.0

TYPEA  TTN        NDGT
15     tst1       7

GTT TABLE IS     (27000 of 269999)     10 % FULL 

START GTA             END GTA               XLAT   RI     PC
5556000               5558000               DPCSSN GT     003-003-003
     MRNSET=114   SSN=254  GTMODID=---------  CGGTMOD = NO

Command Retrieved 1 Entries

The global title translation is changed with a new range of global title addresses, 5556800 - 5559000, and with the split=no parameter.

chg-gtt:ttn=tst1:gta=5556800:egta=5559000:split=no

The range of global title addresses is changed to 5556800 - 5559000.

rlghncxa03w 10-07-25 09:45:31 GMT  EAGLE5 42.0.0
 
TYPEA  TTN        NDGT
15     tst1       7

GTT TABLE IS     (27000 of 269999)      10 % FULL 

START GTA             END GTA               XLAT   RI     PC
5556800               5559000               DPCSSN GT     003-003-003
     MRNSET=114   SSN=254  GTMODID=---------  CGGTMOD = NO

Command Retrieved 1 Entries

In this example, the range of global title addresses is made smaller by specifying the range of global title addresses 5556500 - 5557500, and with the split=no parameter.

chg-gtt:ttn=tst1:gta=5556500:egta=5557500:split=no

rlghncxa03w 10-07-25 09:45:31 GMT  EAGLE5 42.0.0

TYPEA  TTN        NDGT
15     tst1       7

GTT TABLE IS      (27000 of 269999)     10 % FULL

START GTA             END GTA               XLAT   RI     PC
5556500               5557500               DPCSSN GT     003-003-003
     MRNSET=114   SSN=254  GTMODID=---------  CGGTMOD = NO

Command Retrieved 1 Entries

In this next example, the range of global title addresses is split with the gta=5556900 and egta=5557000 defining where the splits occur.

chg-gtt:ttn=tst1:gta=5556900:egta=5557000

Since the default value for the split parameter is yes, the split=yes parameter does not have to be specified to split the range of global title addresses. When the chg-gtt command is entered, three new global title translation entries with the new global title address ranges are created, and the original global title translation entry is removed from the database. Since the gta and egta parameter values specified in this example are within the original range of global title addresses, the original range of global title addresses is split into three new ranges. The START GTA value of the first new range is the original START GTA value and the END GTA value is the gta parameter value minus one. The START GTA value of the second new range is the gta parameter value and the END GTA value is the egta parameter value. The START GTA value of the third new range is the egta parameter value plus 1 and the END GTA value is the original END GTA value.

rlghncxa03w 10-07-25 09:45:31 GMT  EAGLE5 42.0.0
TYPEA  TTN        NDGT
15     tst1       7

GTT TABLE IS     (27000 of 269999)        10 % FULL 
START GTA             END GTA               XLAT   RI     PC
5556000               5556899               DPCSSN GT     003-003-003
     MRNSET=114   SSN=254  GTMODID=---------  CGGTMOD = NO

Command Retrieved 1 Entries


rlghncxa03w 10-07-25 09:45:31 GMT  EAGLE5 42.0.0
TYPEA  TTN        NDGT
15     tst1       7

GTT TABLE IS     (27000 of 269999)        10 % FULL 
START GTA             END GTA               XLAT   RI     PC
5556900               5557000               DPCSSN GT     003-003-003
     MRNSET=114   SSN=254  GTMODID=---------  CGGTMOD = NO

Command Retrieved 1 Entries


rlghncxa03w 10-07-25 09:45:31 GMT  EAGLE5 42.0.0
TYPEA  TTN        NDGT
15     tst1       7

GTT TABLE IS     (27000 of 269999)        10 % FULL 
START GTA             END GTA               XLAT   RI     PC
5557001               5558000               DPCSSN GT     003-003-003
     MRNSET=114   SSN=254  GTMODID=---------  CGGTMOD = NO

Command Retrieved 1 Entries

In this next example, the global title translation containing the range of global title addresses 5557001 - 5558000 is split into two new ranges with the gta=5557501 and egta=5558000 defining where the split occurs.

chg-gtt:ttn=tst1:gta=5557501:egta=5558000:split=yes

When the chg-gtt command is entered, two new global title translation entries with the new global title address ranges are created, and the original global title translation entry is removed from the database. The START GTA value of the first new range is the original START GTA value and the END GTA value is the gta parameter value minus one. The START GTA value of the second new range is the gta parameter value and the END GTA value is the egta parameter value. In this example, the egta parameter is also the original END GTA value.

rlghncxa03w 10-08-25 09:45:31 GMT  EAGLE5 42.0.0
TYPEA  TTN        NDGT
15     tst1       7

GTT TABLE IS      (27000 of 269999)      10 % FULL

START GTA             END GTA               XLAT   RI     PC
5557001               5557500               DPCSSN GT     003-003-003
     MRNSET=114   SSN=254  GTMODID=---------  CGGTMOD = NO

Command Retrieved 1 Entries


rlghncxa03w 10-07-25 09:45:31 GMT  EAGLE5 42.0.0
TYPEA  TTN        NDGT
15     tst1       7

GTT TABLE IS      (27000 of 269999)      10 % FULL
START GTA             END GTA               XLAT   RI     PC
5557501               5558000               DPCSSN GT     003-003-003
     MRNSET=114   SSN=254  GTMODID=---------  CGGTMOD = NO

Command Retrieved 1 Entries

The range of global title addresses can be changed so long as the new range of global title addresses does not overlap an existing range of global title addresses.

For example, using the range of global title addresses from the previous examples, 5556000 - 5558000, you wish to extend the range of global title addresses to 5556000 - 5559000. The range of global title addresses can be extended to 5559000 by specifying the egta=5559000 and split=no parameters with the chg-gtt command. However, if another range of global title addresses begins with the value 5558500, the egta=5559000 parameter cannot be specified with the chg-gtt command as the new range created with the egta=5559000 parameter would overlap the range of global title addresses beginning with the value 5558500. In this situation, the maximum value for the egta parameter would be 5558499.

Note:

The command line on the terminal can contain up to 150 characters. If the parameters and values specified with the chg-gtt command are too long to fit on the chg-gtt command line, perform the chg-gtt command as many times as necessary to complete the GTT entry.

The XLAT parameter does not have a SEAS equivalent. When global title translations are configured at the SEAS interface, the values for the SEAS parameters RI, DPC, and SSN, all mandatory parameters for the SEAS ADD-GTT and CHG-GTT commands, are converted to the EAGLE parameters and values shown in Table 3-8.

Table 3-8 SEAS and Global Title Translation Parameter Conversion

SEAS GTT Parameters GTT Parameters
RI DPC SSN XLAT RI PC/PCA SSN
G xxx-xxx-xxx 000 DPC GT xxx-xxx-xxx Not Specified
D xxx-xxx-xxx 002-255 DPCSSN SSN xxx-xxx-xxx 002-255
G xxx-xxx-xxx 002-255 DPCSSN GT xxx-xxx-xxx 002-255
D xxx-xxx-xxx 000 DPC SSN xxx-xxx-xxx Not Specified

Notes:

  • The SEAS RI=G parameter denotes global title routing, further global title translation is required.
  • The SEAS RI=D parameter denotes DPC routing, no further global title translation is required.
  • The RI=GT parameter denotes further global title translation is required and uses MTP routing.
  • The RI=SSN parameter denotes final global title translation and uses MAP routing.
  • The XLAT=DPC parameter indicates that the DPC & RI values in the MSU are to be replaced.
  • The XLAT=DPCSSN parameter indicates that the DPC, RI, & SSN values in the MSU are to be replaced.
  • The XLAT=DPCNGT parameter indicates that the DPC, RI, & TT values in the MSU are to be replaced.

The examples in this procedure are used to change the global title translation data for translation type 15 in the database.

If the translation type is defined as an alias, it cannot be used in the chg-gtt command.

If the translate indicator is equal to dpc (xlat=dpc) and the routing indicator is equal to ssn (ri=ssn), the point code and subsystem number specified in the chg-gtt command must be defined in the database as a mated application. Verify this by entering the rtrv-map command. If this point code and subsystem number is not defined as a mated application, perform one of these procedures to add the point code and subsystem number to the database as a mated application:

The point code and subsystem number do not have to be in the mated application table when the chg-gtt command is executed when these parameters are specified with the chg-gtt command.

  • ri=gt
  • xlat=dpcssn and ri=ssn

If the point code and subsystem are not in the mated application table when either of these parameters are specified with the chg-gtt command, the EAGLE creates a solitary mated application in the mated application table using the point code and subsystem values specified in the chg-gtt command.

If the xlat=dpcssn parameter is specified, the ssn parameter must be specified. Otherwise, the ssn parameter cannot be specified.

If a point code is the STP’s True PC, then the value of the XLAT parameter must be set to DPCSSN and the value of the RI parameter must be set to SSN. If the SSN parameter is specified and a point code is the STP’s True PC, then the subsystem number specified must exist in the SS-APPL table. This can be verified with the rtrv-ss-appl command. To execute the rtrv-ss-appl command, one or more features shown in Table 3-9 must be enabled, and turned on if necessary. The rtrv-ctrl-feat output shows the required status of the features.

Table 3-9 Feature Status

Feature Feature's Status Entry Displayed in the rtrv-ctrl-feat Output
LNP Enabled The entry LNP TNs with a quantity greater than zero (0)
EIR Enabled and Turned On EIR
INP Enabled and Turned On INP
ANSI-41 INP Query Enabled and Turned On ANSI-41 INP Query
V-Flex Enabled and Turned On VFLEX
ATINP Enabled ATINP
ANSI41 AIQ Enabled ANSI41 AIQ

The point code specified in the chg-gtt command (pc/pca, pci, pcn or pcn24) must be defined in the routing table. For ANSI point codes (pc/pca), the point code specified in the chg-gtt command, must be a full point code. That point code can be defined as a full point code in the destination point code table, or can be a member of a cluster point code defined in the destination point code table. Cluster point codes or a network routing point codes cannot be specified with this command. The rtrv-rte command can be used to verify the point codes in the routing table. The point codes are shown in the DPCA, DPCI, DPCN, or DPCN24 fields of the rtrv-rte command output. If the point code is not defined as a route, perform one of the Adding a Route procedures in Database Administration – SS7 User's Guide to define the point code as a route.

If the EAGLE’s point code is specified with the chg-gtt command, then the xlat=dpcssn and ri=ssn parameters must be specified. The EAGLE’s point code is shown in the PCA, PCI, PCN, or PCN24 fields of the rtrv-sid command output.

If the xlat=dpcngt parameter is specified, the ri=gt parameters must be specified.

A point code containing all zeros is not a valid point code.

An ANSI point code or ITU international point code containing all zeros is not a valid point code and cannot be entered into the database. An ITU national point code containing all zeros is a valid point code and can be entered into the database.

Either the type parameter or the ttn parameter must be specified.

If the type parameter is specified, the translation type must be in the database. This can be verified with the rtrv-tt command.

If the type parameter is not specified, the translation type name must be assigned to a translation type in the database. This can be verified with the rtrv-tt command.

The end global title address (egta) must be greater than or equal to the start global title address (gta) and its length must be equal to the start global title address.

If the range as specified by the gta and egta parameters does not exactly match the existing range, the existing range is split. All addresses in the existing range that are outside the range specified by gta and egta, retain the original xlat, ri, pc, and ssn parameters. A new range is created and bounded by the gta and egta containing new values of xlat, ri, pc, and ssn as present in the command, and retaining parameter values from the previous range that do not have corresponding new values in the command.

However, if the ranges overlap, splitting cannot occur and the command is rejected. However, if the ranges overlap, splitting cannot occur, and the chg-gtt command is rejected with this message.

E2401 Cmd Rej:GTA range overlaps a current range

Along with error message 2401, a list of the overlapped global title addresses is displayed as shown in the following example.

rlghncxa03w 07-02-24 08:29:15 GMT EAGLE5 37.0.0

The following GTA ranges overlap the input GTA range

START GTA               END GTA
8005550000              8005551999
8005552000              8005553999
8005554000              8005555999

CHG-GTT: MASP A - Command Aborted

If the translation type is ANSI (type or typea), the pc type must be ANSI (pc or pca). If the translation type is one of the ITU types (typei, typen, or typen24) the pc type may be either of the ITU types (pci, pcn, or pcn24). If the ANSI/ITU SCCP Conversion feature is enabled, the domain (ANSI or ITU) of the translation type and point code do not have to be the same.

The values specified for the gta and egta parameters can be decimal digits (0-9) or hexadecimal digits (0-9, a-f, A-F). Hexadecimal digits can be specified only if the Hex Digit Support for GTT feature is enabled. Verify the status of the Hex Digit Support for GTT feature with the rtrv-ctrl-feat command. Refer to the Hex Digit Support for GTT section for more information on this feature. If the Hex Digit Support for GTT feature is not enabled, perform the Activating the Hex Digit Support for GTT Feature procedure to enable the Hex Digit Support for GTT feature.

Table 3-10 shows the valid combinations for the xlat, ri, and ssn parameters. All other combinations are rejected.

Table 3-10 Valid Parameter Combinations for the chg-gtt Routing Parameters

New or Existing XLAT Value New or Existing RI Value Routing Action SSN Value
DPC GT Translate DPC only and route on GT Cannot be specified. The current database entry is removed.
DPC SSN Translate DPC only and route on SSN Cannot be specified. The current database entry is removed.
DPCSSN GT Translate DPC and SSN and route on GT Must be specified.
DPCSSN SSN Translate DPC and SSN and route on SSN Must be specified.
DPCNGT GT Translate DPC, new translation type (TT), and route on GT Cannot be specified. The current database entry is removed.

Canceling the RTRV-GTT Command

Because the rtrv-gtt command used in this procedure can output information for a long period of time, the rtrv-gtt command can be canceled and the output to the terminal stopped. There are three ways that the rtrv-gtt command can be canceled.

  • Press the F9 function key on the keyboard at the terminal where the rtrv-gtt command was entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-gtt command was entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-gtt command was entered, from another terminal other that the terminal where the rtrv-gtt 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, go to Commands User's Guide.

  1. Display the translation types in the database using the rtrv-tt command. This is an example of the possible output.
    rlghncxa03w 10-07-25 09:42:31 GMT  EAGLE5 42.0.0
    TYPEA      TTN        NDGT
    1          lidb       5
    2          c800       10
    3          d700       6
    5          scp1       6
    10         scp2       6
    15         scp3       3
    
    ALIAS      TYPEA
    30         5
    40         10
    50         3
    65         3
    
    TYPEI      TTN        NDGT
    105        itudb      8
    
    ALIAS      TYPEI
    7          105
    
    TYPEN      TTN        NDGT
    120        dbitu      7
    
    ALIAS      TYPEN
    8          120
    
    TYPEIS     TTN        NDGT
    
    ALIAS      TYPEIS
    
    TYPENS     TTN        NDGT
    
    ALIAS      TYPENS
  2. Verify that the EGTT feature is on, by entering the rtrv-feat command. If the GTT feature is on, the EGTT field should be set to on.

    Note:

    Thertrv-feat command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by thertrv-feat command, refer to thertrv-feat command description in Commands User's Guide.

    If the EGTT feature is off, continue the procedure with 5.

    If the EGTT feature is on, continue the procedure with 3.

  3. Display the features that are enabled by entering the rtrv-ctrl-feat command.

    The following is an example of the possible output.

    rlghncxa03w 10-07-28 21:15:37 GMT EAGLE5 42.0.0
    The following features have been permanently enabled:
    
    Feature Name              Partnum    Status  Quantity
    Command Class Management  893005801  on      ----
    LNP Short Message Service 893006601  on      ----
    Intermed GTT Load Sharing 893006901  on      ----
    HC-MIM SLK Capacity       893012707  on      64
    
    The following features have been temporarily enabled:
    
    Feature Name              Partnum    Status  Quantity     Trial Period Left
    Zero entries found.
    
    The following features have expired temporary keys:
    
    Feature Name              Partnum
    Zero entries found.
  4. Display the GTT selectors in the database by entering the rtrv-gttsel command with the TTN value associated with the translation type that will be assigned to the global title translation. The TTN value is shown in the rtrv-tt output in 1.

    To specify of the TTN value, the parameters shown in Table 3-11 must be specified with the rtrv-gttsel command. The parameters that can be specified are dependent on the features that are enabled, shown in 3.

    Table 3-11 RTRV-GTTSEL Parameters

    Feature that is Enabled Parameter that must be Specified for the TTN Value
    Neither the Origin Based SCCP Routing nor the Flexible Linkset Optional Based Routing, shown asFlex Lset Optnl Based Rtg in thertrv-ctrl-feat output, is enabled. gttsn
    Origin Based SCCP Routing cdgtasn,cggtasn
    Flexible Linkset Optional Based Routing cdgttsn,cggttsn

    For this example, enter this command.

    rtrv-gttsel:gttsn=scp3

    rlghncxa03w 10-07-28 21:15:37 GMT EAGLE5 42.0.0
    
    GTIA    TT     NP      NAI  SELID GTTSN
     2      15     --      ---  none  scp3
    GTII    TT     NP      NAI  SELID GTTSN
    
    GTIN    TT     NP      NAI  SELID GTTSN
    
    GTIN24  TT     NP      NAI  SELID GTTSN
    
    GTIIS   TT     NP      NAI  SELID GTTSN
    
    GTINS   TT     NP      NAI  SELID GTTSN

    If any of the entries shown in the rtrv-gttsel output do not have the default values for the advanced GTT parameters, or if a GTT selector entry with the TTN value was removed with the dlt-gttsel command, the remainder of this procedure cannot be performed. Choose another GTT entry to change and repeat this step. The GTT entry should contain another translation type and TTN value.

    If all of the entries shown in the rtrv-gttsel output have the default values for the advanced GTT parameters, and none of the GTT selector entries with the TTN value were removed with the dlt-gttsel command, continue the procedure with 5.

  5. Display the global title translations in the database using the rtrv-gtt command specifying a translation type, translation type name, or both from the rtrv-tt command output shown in 1.

    For this example, enter this command.

    rtrv-gtt:typea=15

    This is an example of the possible output.

    rlghncxa03w 10-07-25 09:43:31 GMT  EAGLE5 42.0.0
    TYPEA  TTN        NDGT
    15     scp3       3
    
    GTT TABLE IS      (27000 of 269999)      10 % FULL
    
    START GTA             END GTA               XLAT   RI     PC
    800                   900                   DPC    SSN    001-001-001
         SSN=---   GTMODID=---------
    919                   919                   DPCSSN SSN    002-002-002
         SSN=50    GTMODID=---------
    
    Command Retrieved 2 Entries
    Continue the procedure with 7 if either of these conditions are present.
    • The GTT entry does not contain a range of global title addresses.
    • The GTT entry does contain a range of global title addresses and the range of global title addresses is not being split.
    The GTT entry does contain a range of global title addresses and the range of global title addresses is being split, continue the procedure with 6 if these conditions are present.
    • The number of global title addresses when the range of global title translations is split will not exceed the maximum number of global title translations.
    • The number of global title addresses when the range of global title translations is split will exceed the maximum number of global title translations and the maximum number of global title translations is less than 1,000,000. Perform the Enabling the XGTT Table Expansion Feature procedure to increase the maximum number of global title translations. After the Enabling the XGTT Table Expansion Feature procedure has been performed, continue the procedure with 6.

    The number of global title addresses when the range of global title translations is split will exceed the maximum number of global title translations and the maximum number of global title translations is 1,000,000; the range of global title addresses cannot be split. Continue the procedure with 7.

  6. Display the GTT path entries by entering the rtrv-gttapath command with these parameters.
    • cdgttsn - the TTN value shown in the rtrv-gtt output in 5.
    • cdgta - the START GTA value shown in the rtrv-gtt output in 5.

    For this example, enter this command.

    rtrv-gttapath:cdgttsn=scp3:cdgta=800

    This is an example of the possible output.

    rlghncxa03w 10-07-25 09:43:31 GMT  EAGLE5 42.0.0
    
    GTTPN   OPGTTSN         CGGTTSN         CDGTTSN
    --------------------------------------------------
    
    path1   ---------       ---------       scp3
        CDGTA = 800                          ECDGTA = 900
    
    
    GTT-PATH table is (5 of 10000) 1% full.

    The range of global title addresses cannot be split if entries containing the TTN and the GTA values shown in the rtrv-gttapath output. If entries are displayed in the rtrv-gttapath output, perform the Removing a GTT Action Path Entry procedure to remove the entries shown in the rtrv-gttapath output.

    Continue the procedure with 7 if no entries are shown in this step; if the entries in the rtrv-gttapath output will not be removed; or the Removing a GTT Action Path Entry procedure has been performed.

  7. Continue the procedure by performing one of these steps.
    Continue the procedure with 10 if any of these actions will occur.
    • The gtmodid and cggtmod=yes parameters will not be specified in this procedure.
    • The gtmodid=none parameter will be specified in this procedure and the cggtmod=yes parameter will not be specified in this procedure.
    • If only the cggtmod=yes parameter will be specified in this procedure and entries are shown in the rtrv-gtt output (in 5) that contain the cggtmod=yes parameter value.

    If only the cggtmod=yes parameter will be specified in this procedure and no entries are shown in the rtrv-gtt output (in 5) that contain the cggtmod=yes parameter value, continue the procedure with 9.

    If the gtmodid parameter with a value other than none will be specified in this procedure, continue the procedure with 8.

  8. Display the GT modification entries by entering the rtrv-gtmod command. This is an example of the possible output.
    rlghncxa03w 10-07-25 09:43:31 GMT  EAGLE5 42.0.0
    
    GTMODID   NTT  NGTI  GT0FILL  NNP  NNAI  NPDD  NSDD  PRECD  CGPASSN
    modid2     --     2       ON   --    --    --    --    PFX       --
          NPDS=                       NSDS=
    modid5     --     2      OFF   --    --    --    --    PFX       --
          NPDS=                       NSDS=
    modid10    --    --      OFF    5     5    --    --    PFX       --
          NPDS=                       NSDS=
    modid11    --    --      OFF    5     5    --    --    PFX       --
          NPDS=                       NSDS=
    modid20    --     2       ON   --    --    --    --    PFX       --
          NPDS=                       NSDS=
    modid7     --     2      OFF   --    --     4     4    PFX       --
          NPDS=2345                   NSDS=12ae
    
    
    GTMOD table is (6 of 100000) 1% full.

    If the NGTI value of the GT modification entry that will be assigned to the GTT entry is 4, the GTT entry must contain an ITU point code.

    If the GT modification entry that you wish to assign to the GTT entry is not shown in the rtrv-gtmod output, perform the Adding Global Title Modification Information procedure to add the desired GT modification entry.

    Note:

    Either the AMGTT or AMGTT CgPA Upgrade features must be enabled to specify the cggtmod=yes parameter for the GTT entry.
    If the GT modification entry that you wish to assign to the GTT entry is shown in the rtrv-gtmod output or the Adding Global Title Modification Information procedure was performed, continue the procedure by performing one of these steps.
    • Continue the procedure with 10 if any of these actions will occur.
      • The cggtmod=yes parameter will not be specified in this procedure.
      • The cggtmod=yes parameter will be specified in this procedure and entries are shown in the rtrv-gtt output (in 5) that contain the cggtmod=yes parameter value.
    • The cggtmod=yes parameter will be specified in this procedure and no entries are shown in the rtrv-gtt output (in 5) that contain the cggtmod=yes parameter value. Continue the procedure with 9.
  9. To specify only cggtmod=yes parameter in this procedure, one of these the Advanced GT Modification features must be enabled.
    • AMGTT - 893021801
    • AMGTT CgPA Upgrade - 893021803

    Enter the rtrv-ctrl-feat command to verify the status of the AMGTT or AMGTT CgPA Upgrade feature.

    The following is an example of the possible output.

    rlghncxa03w 10-07-28 21:15:37 GMT EAGLE5 42.0.0
    The following features have been permanently enabled:
    
    Feature Name              Partnum    Status  Quantity
    IPGWx Signaling TPS       893012814  on      20000
    ISUP Normalization        893000201  on      ----
    Command Class Management  893005801  on      ----
    LNP Short Message Service 893006601  on      ----
    Intermed GTT Load Sharing 893006901  on      ----
    HC-MIM SLK Capacity       893012707  on      64
    
    The following features have been temporarily enabled:
    
    Feature Name              Partnum    Status  Quantity     Trial Period Left
    Zero entries found.
    
    The following features have expired temporary keys:
    
    Feature Name              Partnum
    Zero entries found.

    If none of the required Advanced GT Modification features are shown in the rtrv-ctrl-feat output in this step (AMGTT, AMGTT CgPA Upgrade), perform the Activating the Advanced GT Modification Feature procedure to enable the AMGTT feature. After the AMGTT feature has been enabled, continue the procedure with 10.

    If either the AMGTT or AMGTT CgPA Upgrade features are shown in the rtrv-ctrl-feat output in this step, continue the procedure with 10.

  10. If the domain (ANSI or ITU) of the point code and the translation type assigned to the global title translation type will be different, and the ngti parameter will be specified with the global title translation, the ANSI/ITU SCCP Conversion feature (SCCP Conversion) must be enabled. If the ANSI/ITU SCCP Conversion feature is not being used, continue the procedure with 11.

    Verify that the ANSI/ITU SCCP Conversion feature is enabled by entering the rtrv-ctrl-feat:partnum=893012001 command.

    The following is an example of the possible output.

    rlghncxa03w 07-02-28 21:15:37 GMT EAGLE5 37.0.0
    The following features have been permanently enabled:
    
    Feature Name           Partnum    Status  Quantity
    SCCP Conversion        893012001  on      ----
    
    The following features have been temporarily enabled:
    
    Feature Name           Partnum    Status  Quantity  Trial Period Left
    Zero entries found.
    
    The following features have expired temporary keys:
    
    Feature Name           Partnum
    Zero entries found.

    If the ANSI/ITU SCCP Conversion feature is not enabled, perform the Activating the ANSI/ITU SCCP Conversion Feature procedure to enable the ANSI/ITU SCCP Conversion feature.

  11. Hexadecimal digits (0-9, a-f, A-F) can be specified as values for the gta or egta parameters only if the Hex Digit Support for GTT feature is enabled. Verify the status of the Hex Digit Support for GTT feature by entering the rtrv-ctrl-feat command with the Hex Digit Support for GTT feature part number.

    Enter this command.

    rtrv-ctrl-feat:partnum=893018501

    The following is an example of the possible output.

    rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
    
    The following features have been permanently enabled:
    
    Feature Name               Partnum     Status       Quantity
    Hex Digit Support for GTT  893018501   on           ----
    
    The following features have been temporarily enabled:
    Feature Name      Partnum     Status    Quantity   Trial Period Left
    Zero entries found.
    
    The following features have expired temporary keys:
    Feature Name Partnum
    Zero entries found.

    If the Hex Digit Support for GTT feature has not been enabled, perform the Activating the Hex Digit Support for GTT Feature procedure to enable this feature. After the Hex Digit Support for GTT feature is enabled, continue the procedure by performing one of these steps.

    If the LOOPSET value will be changed, continue the procedure with 12.

    If the LOOPSET value will not be changed, continue the procedure with 14.

  12. If the LOOPSET field appears in the output shown in 5, the SCCP Loop Detection feature is enabled, continue the procedure with 13.

    If the LOOPSET field appears in the output shown in 5, the SCCP Loop Detection feature is not enabled. Perform the Activating the SCCP Loop Detection Feature procedure to enable the SCCP Loop Detection feature. After the SCCP Loop Detection Feature has been enabled, perform the Adding a Loopset procedure to add the required loopset. After the loopset has been added, continue the procedure with 14.

  13. Display all the loopsets in the database by entering this command.
    rtrv-loopset:num=1000:force=yes

    This is an example of the possible output.

    LoopSet       Mode       Point Codes
    ======================================================================
    cary2        notify      005-015-005       007-007-007       (ANSI)
                             033-004-003       033-007-003
                             005-027-005       007-004-007            
    
    cary4        notify      005-012-005       007-026-007       (ANSI)
                             003-049-003       033-002-003
                             005-008-055       007-014-007
    
    apex3        discard     005-017-008       007-017-009       (ANSI)
                             033-005-043       005-014-005
                             005-017-005       007-014-007
                             033-002-043       005-038-005
                             007-009-027       033-003-043
                             005-012-005       007-002-027
    
    apex4        discard     005-007-008       027-007-009       (ANSI)
                             033-005-003       005-004-055
                             027-001-007       033-008-003
                             033-007-003       005-003-055
                             027-008-007
    
    ral5           notify    005-005-005       007-007-007       (ANSI)
                             003-004-003       003-001-003
                             005-007-005       007-004-007
                             003-002-003       005-008-005
                             007-009-007       003-003-003
                             005-002-005       007-002-007
    
    ral6           notify    005-007-008       007-007-009       (ANSI)
                             003-005-003       003-007-003
                             005-007-005
    
    dunn1          discard   005-002-055       007-051-007       (ANSI)
                             003-008-033
    
    rtp9           discard   005-002-005       007-001-007       (ANSI)
                             003-008-003       003-007-003
                             005-003-005       007-008-007
                             005-004-005
    
    rtp5           discard   005-007-008       007-007-009       (ANSI)
                             003-005-003
    
    rtp1           discard   005-005-005       007-007-007       (ANSI)
                             003-004-003       003-007-003
                             005-007-005       007-004-007
                             005-004-005
    
    rtp2           notify    005-007-008       007-007-009       (ANSI)
                             003-005-003
    
    
    rlghncxa03w 07-03-07 08:50:15 GMT Rel 37.0.0
    LOOPSET table is (11 of 1000) 1% full
    RTRV-LOOPSET: MASP A - COMPLTD

    Note:

    If thertrv-loopset command is entered with no other parameters specified, a maximum of 50 entries are displayed. To display more than 50 entries, theforce=yes parameter must be specified with the rtrv-loopset command and the num parameter value must be greater than 50. Since there can be a maximum of 1000 loopsets in the database, to display all the loopsets in the database, theforce=yes andnum=1000 parameters must be specified with thertrv-loopset command.

    If the required loopset is shown in the rtrv-loopset output, continue the procedure with 14.

    If the required loopset is not shown in the rtrv-loopset output, perform the Adding a Loopset procedure to add the required loopset. After the loopset has been added, continue the procedure with 14.

  14. Continue the procedure by performing one of these steps.
    • If the routing indicator value will be is SSN when this procedure is finished, continue the procedure by performing one of these steps.
      • If the xlat parameter value will be dpc when this procedure is completed, continue the procedure by performing one of these steps.
        • If the point code value will not be changed and the Flexible GTT Load Sharing feature is not enabled (the MAPSET field is not shown in rtrv-gtt), continue the procedure with 22.
        • If the point code value will not be changed; the Flexible GTT Load Sharing feature is enabled and the MAPSET value will not be changed, continue the procedure with 22.
        • If the point code value will not be changed; the Flexible GTT Load Sharing feature is enabled and the MAPSET value will be changed, continue the procedure with 20.
        • If the point code value will be changed, continue the procedure with 20.
      • If the xlat parameter value will be dpcssn when this procedure is completed, continue the procedure by performing one of these steps.
        • If the point code, SSN, and MAPSET value (if the Flexible GTT Load Sharing feature is enabled, the MAPSET field is shown in rtrv-gtt) will not be changed, continue the procedure with 22.
        • If the point code will be changed, continue the procedure by performing one of these steps.
          • If the new point code value will not be the EAGLE’s point code, continue the procedure with 20.
          • If the new point code value will be the EAGLE’s point code, continue the procedure with 19.
          • If only the SSN value will be changed, continue the procedure with 19.
          • If the Flexible GTT Load Sharing feature is enabled and only the MAPSET value will be changed, continue the procedure with 19.
      • If the routing indicator value will be GT when this procedure is finished, continue the procedure by performing one of these steps.
        • If the Flexible GTT Load Sharing feature is not enabled; the MRNSET value will not be specified and the point code value will not be changed, continue the procedure with 22.
        • If the Flexible GTT Load Sharing feature is not enabled but the point code value will be changed, continue the procedure with 16.
        • If the Flexible GTT Load Sharing feature is enabled and the point code will be changed, whether or not the MRNSET value will be changed, continue the procedure with 15.
        • If the Flexible GTT Load Sharing feature is not enabled; the point code will not be changed, but the mrnset parameter will be specified, perform the Activating the Flexible GTT Load Sharing Feature procedure followed by the Provisioning MRN Entries procedure. When this is completed, continue the procedure with 22.
  15. The point code and MRN set ID specified for the global title translation must be shown in the rtrv-mrn command output. The point code must be assigned to the MRN set that will be assigned to the global title translation.

    Enter the rtrv-mrn command to verify that the required MRN set is configured in the database, and that the required point code is assigned to the MRN set. The following is an example of the possible output.

    rlghncxa03w 07-02-28 21:15:37 GMT EAGLE5 37.0.0
    
    
    MRNSET   PC             RC
    DFLT     001-001-001    10
             001-001-002    20
             001-001-003    30
    
    MRNSET   PC             RC
    110      001-001-001    10
             001-001-005    20
             001-001-006    30
             001-001-003    40
             001-001-008    50
    
    MRNSET   PC             RC
    111      001-001-001    30
             001-001-005    30
             001-001-006    30
             001-001-003    30
             001-001-008    30
    
    MRNSET   PC             RC
    112      001-003-001    10
             001-003-002    10
             001-003-003    30
             001-003-004    30
             001-003-006    60
             001-003-007    60
             001-003-008    80
             001-003-009    80
    
    MRNSET   PCN               RC
    113      s-1-1-1-0123-aa   1
             s-1-1-1-0235-aa   2
             s-1-1-1-0235-aa   3

    Note:

    If theWeighted GTT Load Sharing feature is enabled, the WT, %WT, and THR columns are shown in thertrv-mrn output

    If the required MRN set is not shown in the rtrv-mrn output, or if the required point code is not assigned to the required MRN set, provision the required MRN set by performing the Provisioning MRN Entries procedure. After provisioning the required MRN set, continue the procedure with 22. If the required MRN set is shown in the rtrv-mrn output, or if the required point code is assigned to the required MRN set, continue the procedure with 22.

  16. Display the destination point codes in the database by entering the rtrv-dstn command. This is an example of the possible output.
    rlghncxa03w 10-12-10 11:43:04 GMT EAGLE5 43.0.0
    Extended Processing Time may be Required
    
       DPCA          CLLI        BEI ELEI   ALIASI           ALIASN/N24    DMN
       001-207-000   ----------- no  --- --------------   --------------   SS7
       001-001-001   ----------- no  --- --------------   --------------   SS7
       001-001-002   ----------- no  --- --------------   --------------   SS7
       001-005-000   ----------- no  --- --------------   --------------   SS7
       001-007-000   ----------- no  --- --------------   --------------   SS7
       008-012-003   ----------- no  --- --------------   --------------   SS7
       003-002-004   ----------- no  --- --------------   --------------   SS7
       009-002-003   ----------- no  --- --------------   --------------   SS7
       010-020-005   ----------- no  --- --------------   --------------   SS7
    
       DPCI          CLLI        BEI ELEI   ALIASA           ALIASN/N24    DMN
       1-207-0       ----------- no  --- --------------   --------------   SS7
       0-015-0       ----------- no  --- --------------   --------------   SS7
       0-017-0       ----------- no  --- --------------   --------------   SS7
       1-011-1       ----------- no  --- --------------   --------------   SS7
       1-011-2       ----------- no  --- --------------   --------------   SS7
    
    
    Destination table is (14 of 2000) 1% full
    Alias table is (0 of 12000) 0% full
    PPC table is (1 of 20) 5% full

    If the required point code is not shown in the rtrv-dstn output, perform the "Adding a Destination Point Code" procedure in Database Administration - SS7 User's Guide to add the required point code. A proxy point code cannot be assigned to the point code.

    After the new point code has been added, and perform one of the Adding a Route procedures in Database Administration - SS7 User's Guide and add the required route to the database. After the route has been added, continue the procedure with 22.

    If the required point code is shown in the rtrv-dstn output, continue the procedure with 17

  17. Display the point code that will be assigned to the global title translation by using the rtrv-dstn command and specifying the point code. For this example, enter this command.
    rtrv-dstn:dpca=010-020-005

    This is an example of the possible output.

    rlghncxa03w 10-12-10 11:43:04 GMT EAGLE5 43.0.0
    
       DPCA          CLLI        BEI ELEI   ALIASI           ALIASN/N24    DMN
       010-020-005   ----------- no  --- --------------   --------------   SS7
    
       PPCA         NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
       009-002-003  ---- no      50     on    20       no     no    none
    
    Destination table is (14 of 2000) 1% full
    Alias table is (0 of 12000) 0% full
    PPC table is (1 of 20) 5% full

    A proxy point code (a point code value is shown in the PPC column) cannot be assigned to the point code. If a proxy point code is shown in this step, choose another point code from the rtrv-dstn output in the previous step and repeat this step.

    If a proxy point code is not shown in this step, continue the procedure with 18.

  18. The point code specified with the chg-gtt command must be the DPC of a route, unless the point code is the EAGLE’s point code.

    Enter the rtrv-rte command with the dpc parameter specifying the point code to be used with the chg-gtt command to verify whether or not the point code is the DPC of a route. For this example, enter these commands.

    rtrv-rte:dpca=003-003-003

    This is an example of the possible output.

    rlghncxa03w 07-02-07 11:43:04 GMT  EAGLE5 37.0.0
    DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
    002-002-003   --------   ------------   ls05       10   002-002-003
                                            ls15       30   089-047-123
                                            lsa8       50   077-056-000
                                                   RTX:No  CLLI=ls05clli

    rtrv-rte:dpca=002-002-003

    This is an example of the possible output.

    rlghncxa03w 07-05-07 11:43:04 GMT  EAGLE5 37.0.0
    DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
    003-003-003   --------   ------------   ls07       10   003-003-003
                                            ls08       30   025-025-150
                                            lsa5       50   066-030-100
                                                   RTX:No  CLLI=ls07clli

    If the point code is not shown in the rtrv-rte output, perform one of the procedures in Database Administration - SS7 User's Guide and add the required route to the database.

    If the point code is shown in the rtrv-rte output or if the required route was added, continue the procedure with 22.

  19. If the ri=ssn and xlat=dpcssn parameters are specified with the chg-gtt command, and you wish to use the EAGLE’s point code for the value of the pc parameter of the chg-gtt command, the point code value must be in the EAGLE’s self ID table.

    Display the EAGLE self-identification, using the rtrv-sid command. This is an example of the possible output.

    rlghncxa03w 07-02-10 11:43:04 GMT EAGLE5 37.0.0
       PCA            PCI         PCN              CLLI            PCTYPE
       010-020-030   1-023-1      12-0-14-1       rlghncxa03w       OTHER
                   s-1-023-1    s-12-0-14-1
       CPCA
       002-002-002       002-002-003       002-002-004      002-002-005
       002-002-006       002-002-007       002-002-008      002-002-009
       004-002-001       004-003-003       050-060-070
       
       CPCI
       1-001-1           1-001-2           1-001-3          1-001-4
       1-002-1           1-002-2           1-002-3          1-002-4
       2-001-1           7-222-7
       
       CPCN
       2-0-10-3          2-0-11-0          2-0-11-2          2-0-12-1
       2-2-3-3           2-2-4-0           10-14-10-1
    Continue the procedure with 22 if either of these actions will be performed.
    • The current point code of the GTT entry is shown in this step and the point code and SSN values of the GTT entry are not being changed, and the GTT entry contains a MAPSET value, the point code and SSN values of the GTT entry must be in the default MAP set. The MAPSET value in the GTT entry cannot be changed.
    • The current point code of the GTT entry is not shown in this step; the point code of the GTT entry is not being changed, but the SSN value of the GTT entry is being change and the GTT entry does not contain a MAPSET value.
    • The current point code of the GTT entry is not shown in this step and the GTT entry contains a MAPSET value and the MAPSET value of the GTT entry will not be changed.
    Continue the procedure with 20 if either of these actions will be performed.
    • The new point code value of the GTT entry is shown in this step.
    • The current point code value of the GTT entry is shown in this step and is not being changed, but the SSN value of the GTT entry is being changed.
    • The point code value of the GTT entry is not shown in this step; the SSN value of the GTT entry will be changed, and the GTT entry contains a MAPSET value.
    • The point code value of the GTT entry is not shown in this step; the point code and SSN values of the GTT entry are not being changed; the GTT entry contains a MAPSET value and the MAPSET value will be changed.
  20. Enter the rtrv-map command with the pc parameter specifying the required point code to verify that the required data is in the mated application table.
    The ssn parameter with the new SSN value must be specified with the rtrv-map command if these conditions are present.
    • The point code value of the GTT entry is not shown in 19; the point code and SSN values of the GTT entry are not being changed; the GTT entry contains a MAPSET value and the MAPSET value will be changed.
    • The current point code value of the GTT entry is shown in 19 and is not being changed, but the SSN value of the GTT entry is being changed whether of not the GTT entry contains a MAPSET value.

    For this example enter this command.

    rtrv-map:pca=002-002-003

    If the Flexible GTT Load Sharing feature is not enabled, this is an example of the possible output.

    rlghncxa03w 09-07-25 09:42:31  GMT  EAGLE5 41.1.0
    
       PCA            Mate PCA      SSN RC MULT SRM MRC GRP NAME SSO
       002-002-003                  250 10  SOL *Y  *Y  GRP01     ON
    
    
    MAP table is (37 of 1024) 4% full.

    If the Flexible GTT Load Sharing feature is enabled, this is an example of the possible output.

    rlghncxa03w 09-07-25 09:42:31  GMT  EAGLE5 41.1.0
    
       MAPSET ID=DFLT
       PCA            Mate PCA      SSN RC MULT SRM MRC GRP NAME SSO
       002-002-003                   55  5  DOM YES YES -------- OFF
                      001-001-002    15 15  DOM YES YES -------- ON
                      001-001-003    25 20  DOM YES YES -------- ON
                      001-001-002    40 35  DOM YES YES -------- OFF
    
       MAPSET ID=1
       PCA            Mate PCA      SSN RC MULT SRM MRC GRP NAME SSO
       002-002-003                  254  5  DOM YES YES -------- OFF
                      001-001-002    10 15  DOM YES YES -------- ON
                      001-001-003    20 20  DOM YES YES -------- ON
                      001-001-002    40 35  DOM YES YES -------- OFF
    
       MAPSET ID=    2
       002-002-003                    5 10  SOL *Y  *Y  -------- OFF
    
    MAP table is (12 of 36000) 1% full.

    Note:

    If the Weighted GTT Load Sharing feature is enabled, the WT, %WT, and THR columns are shown in thertrv-map output.
    If the parameter values for the ri and xlat parameters will be ri=ssn and xlat=dpc when this procedure is completed, the point code value must be in the mated application table. If the point code value is not in the mated application table when the chg-gtt command is executed, the force=yes parameter must be specified with the chg-gtt command. However, the point code value of the GTT entry must be the DPC of a route. If the GTT entry has a MAPSET value and the MAPSET value is being changed, but the point code value of the GTT entry is not being changed, the new MAP set must contain the current point code value of the GTT entry.
    • Continue the procedure with 16 if either of these actions will be performed.
      • The point code value of the GTT entry is being changed and the new point code value is not shown in the rtrv-map output.
      • The rtrv-map output does not contain another MAP set with the current point code value.
    • Continue the procedure with 22 if either of these actions will be performed.
      • The point code value of the GTT entry is being changed and the new point code value is shown in the rtrv-map output.
      • The rtrv-map output does contain another MAP set with the current point code value.

    If the parameter values for the ri and xlat parameters will be ri=ssn and xlat=dpcssn, the point code, subsystem number, and MAPSET values (if the Flexible GTT Load Sharing feature is enabled) that will be in the GTT entry when this procedure is finished must be shown in the rtrv-map output in this step.

    If the required point code, subsystem number, or MAPSET values are not shown in the rtrv-map output, perform one of these procedures to add the required information to the mated application table.

    If the point code value of the GTT entry when this procedure is finished will not be the EAGLE's point code, continue the procedure with 22.

    If the point code value of the GTT entry when this procedure is finished will be the EAGLE's point code, continue the procedure with 21.

  21. Enter the rtrv-ss-appl command to verify that either the LNP, EIR, INP, V-Flex, ATINPQ, or AIQ subsystem number (depending on which feature is on) is the subsystem application table.

    This is an example of the possible output.

    rlghncxa03w 08-09-28 14:42:38 GMT EAGLE5 39.2.0
    APPL       SSN       STAT
    LNP        254       ONLINE
    
    SS-APPL table is 20% FULL (1 of 5)

    If the subsystem number is shown in the rtrv-ss-appl output, continue the procedure with 22.

    If no subsystem number is shown in the rtrv-ss-appl output, or if the rtrv-ss-appl command is rejected, go to one of these user's guides, depending on the type of subsystem you wish to use, and enable the feature if necessary, and add the subsystem to the subsystem application table.

    • EIR subsystem – go toEIR User's Guide.
    • INP subsystem – go to INP/AINPQ User's Guide.
    • LNP subsystem – go to ELAP Administration and LNP Feature Activation Guide.
    • V-Flex subsystem – go to V-Flex User's Guide.
    • ATINPQ subsystem – go to ATINP User's Guide.
    • AIQ subsystem – go to Analyzed Information Features User's Guide.

    Note:

    If the Flexible GTT Load Sharing feature is enabled, a MAP set ID must be specified for the final global title translation. The point code and SSN specified for the final global title translation being changed in this procedure must be assigned to the MAP set ID that will be assigned to the final global title translation. Perform 20 to verify that the required MAP set is configured in the database.

    Note:

    If the Flexible GTT Load Sharing feature is not enabled, and theri parameter value will bessn, thexlat parameter value will bedpcssn, the point code value will not be the EAGLE’s point code, and the SSN parameter value will not be the EAGLE’s subsystem number when this procedure is completed, continue the procedure with 22.
  22. Change the global title translation using the chg-gtt command using the parameter combinations shown in Table 3-12.

    For this example, enter this command.

    chg-gtt:type=15:gta=800:egta=850:xlat=dpcssn:ri=gt:pc=003-003-003:ssn=254 :mrnset=114

    chg-gtt:type=15:gta=919:xlat=dpcssn:ri=ssn:pc=002-002-003:ssn=254:mapset=1 :loopset=rtp2

    This message should appear.

    rlghncxa03w 07-02-25 09:44:31  GMT  EAGLE5 37.0.0
    CHG-GTT:  MASP A - COMPLTD
    

    Table 3-12 Change GTT Parameter Combinations

    RI = GT XLAT= DPCNGT RI = GT XLAT= DPCSSN RI = GT XLAT= DPC RI = SSN XLAT= DPCSSN RI = SSN XLAT= DPC
    Mandatory Parameters

    TYPE/TYPEA/

    TYPEI/TYPEN

    TYPEIS/TYPENS

    TYPEN24 (See Notes 2 and 3)

    TYPE/TYPEA/

    TYPEI/TYPEN

    TYPEIS/TYPENS

    TYPEN24 (See Notes 2 and 3)

    TYPE/TYPEA/

    TYPEI/TYPEN

    TYPEIS/TYPENS

    TYPEN24 (See Notes 2 and 3)

    TYPE/TYPEA/

    TYPEI/TYPEN

    TYPEIS/TYPENS

    TYPEN24 (See Notes 2 and 3)

    TYPE/TYPEA/

    TYPEI/TYPEN

    TYPEIS/TYPENS

    TYPEN24 (See Notes 2 and 3)

    GTA (See Notes 10, 12, and 14) GTA (See Notes 10, 12, and 14) GTA (See Notes 10, 12, and 14) GTA (See Notes 10, 12, and 14) GTA (See Notes 10, 12, and 14)
    Optional Parameters (See Notes 19 and 20)

    PC/PCA/PCI/

    PCN/PCN24 (See Notes 1, 3, and 6)

    PC/PCA/PCI/

    PCN/PCN24 (See Notes 1, 3, and 6)

    PC/PCA/PCI/

    PCN/PCN24 (See Notes 1, 3, and 6)

    PC/PCA/PCI/

    PCN/PCN24 (See Notes 1, 3, and 6)

    PC/PCA/PCI/

    PCN/PCN24 (See Notes 1, 3, and 6)

    TTN (See Notes 12, 13, and 14) TTN (See Notes 12, 13, and 14) TTN (See Notes 12, 13, and 14) TTN (See Notes 12, 13, and 14) TTN (See Notes 12, 13, and 14)
    EGTA(See Notes 10, 15, and 18) EGTA (See Notes 10, 15, and 18) EGTA (See Notes 10, 15, and 18) EGTA (See Notes 10, 15, and 18) EGTA (See Notes 10, 15, and 18)
    GTMODID (See Note 5) GTMODID (See Note 5) GTMODID (See Note 5) GTMODID (See Note 5) GTMODID (See Note 5)
    >MRNSET (See Notes 7 and 16) >MRNSET (See Notes 7 and 16) >MRNSET (See Notes 7 and 16) >MAPSET (See Notes 7 and 16) MAPSET (See Notes 7 and 16)
    SPLIT (See Note 18) SPLIT (See Note 18) SPLIT (See Note 18) SPLIT (See Note 18) SPLIT (See Note 18)
    >LOOPSET (See Note 11) >LOOPSET (See Note 11) >LOOPSET (See Note 11) >LOOPSET (See Note 11) LOOPSET (See Note 11)
    >CGGTMOD (See Note 4) >CGGTMOD (See Note 4) >CGGTMOD (See Note 4) >CGGTMOD (See Note 4) CGGTMOD (See Note 4)
      SSN   SSN FORCE (See Note 8)
    Parameter Values:

    TYPE/TYPEA/TYPEI/TYPEIS/TYPEN/TYPENS/TYPEN24 – The translation type from the TYPE/TYPEA/TYPEI/TYPEIS/TYPEN/TYPENS/TYPEN24 column of the rtrv-tt output – See Note 2

    TTN – The translation type name from the TTN column of the rtrv-tt output.

    GTA – 1 - 21 digits or 1 - 21 hexadecimal digits

    PC/PCA/PCI/PCN/PCN24 – See Note 1

    SSN – 0 - 255

    EGTA – 1 - 21 digits or 1 - 21 hexadecimal digits. Default = same as the GTA value

    FORCE – yes, no. Default = no

    LOOPSET – Loopset name from the rtrv-loopset output

    SPLIT - yes, no. Default = yes

    MRNSET – MRN set ID from the rtrv-mrn output

    MAPSET – MAP set ID from the rtrv-map output

    CGGTMOD – yes, no. Default = no

    GTMODID – GT modification identifier from the rtrv-gtmod output

    Notes:

    1. The pc/pca/pci/pcn/pcn24 parameters are used to assign either ANSI, ITU-I, ITU-I spare, 14-bit ITU-N, 14-bit ITU-N spare, or 24-bit ITU-N point codes to the global title translation (GTT).
      • pc/pca = ANSI point code
      • pci = ITU-I or ITU-I spare point code
      • pcn = 14-bit ITU-N or 14-bit ITU-N spare point code
      • pcn24 = 24-bit ITU-N point code.
    2. The type/typea/typei/typen/typeis/typens/typen24 parameters specify the translation type and the network type of the translation type.
      • type/typea = ANSI translation type
      • typei = ITU-I translation type
      • typen = ITU-N translation type
      • typeis = ITU-I spare translation type
      • typens = ITU-N spare translation type
      • typen24 = ITU-N24 translation type
    3. The domain (ANSI or ITU) of the point code and translation type must be the same, unless the ANSI/ITU SCCP Conversion feature is enabled. If the ANSI/ITU SCCP Conversion feature is enabled, a GTT may contain an ANSI point code and an ITU translation type, or an ITU point code and an ANSI translation type. Whether the ANSI/ITU SCCP Conversion feature is enabled or not, the translation type parameters typei, typeis, typen, typens, or typen24 can be specified with either the pci, pcn, or pcn24 parameters.
    4. The cggtmod=yes parameter can be specified only if the AMGTT or AMGTT CgPA Upgrade feature is enabled.
    5. A GT modification identifier entry can contain the ngti=4 parameter value only if the point code value in the GTT entry is an ITU point code.
    6. If the point code is the EAGLE’s point code, then the xlat parameter value must be dpcssn and the ri parameter value must be ssn.
    7. The mrnset parameter can be specified only, and must be specified, if the Flexible GTT Load Sharing feature is enabled.
    8. If the pc/pca/pci/pcn/pcn24 parameter value is not shown in the rtrv-map output, the force=yes parameter must be specified with the ent-gtt command.
    9. The mapset parameter can be specified only, and must be specified, if the Flexible GTT Load Sharing feature is enabled.
    10. Hexadecimal digits (0-9, a-f, A-F) can be specified for the gta or egta parameters only if the Hex Digit support for GTT feature is enabled.
    11. The loopset parameter can be specified only if the SCCP Loop Detection feature is enabled.
    12. Either the type parameter or the ttn parameter must be specified.
    13. If the type parameter is not specified, the translation type name must be assigned to a translation type in the database. This can be verified with the rtrv-tt command.
    14. If the type and ttn parameters are specified, the specified translation type must be in the database and the specified translation type name must be assigned to the translation type.
    15. The end global title address (egta) must be greater than or equal to the start global title address (gta) and its length must be equal to the start global title address.
    16. Specifying the mrnset=none parameter removes the MRN set ID assignment from the global title translation.
    17. Specifying the mapset=none parameter removes the MAP set ID assignment from the global title translation.
    18. The range of global title addresses assigned to a global title translation can be extended, reduced, or split to create a new range of global title addresses. Refer to the split parameter description section in this procedure for information on changing the range of global title addresses.
    19. Unless a default value is shown in this table, the value of any optional parameter that is not specified in this procedure is not changed.
    20. At least one optional parameter must be specified.
  23. Verify the changes using the rtrv-gtt command specifying the translation type, translation type name, or both used in 22. If the num parameter is specified with the rtrv-gtt command, and the value of the num parameter is greater than 1000, the force=yes parameter must be specified with the rtrv-gtt command.

    For this example, enter this command.

    rtrv-gtt:typea=15:gta=800

    This is an example of the possible output.

    rlghncxa03w 10-07-25 09:45:31 GMT  EAGLE5 42.0.0
    TYPEA  TTN        NDGT  
    15     scp3       3
    
    GTT TABLE IS      (27000 of 269999)      10 % FULL
    
    START GTA             END GTA               XLAT   RI     PC
    800                   850                   DPCSSN GT     003-003-003
         MRNSET=114   SSN=254  GTMODID=---------  CGGTMOD = NO
         LOOPSET = none
    
    Command Retrieved 1 Entries

    rtrv-gtt:typea=15:gta=919

    This is an example of the possible output.

    rlghncxa03w 10-07-25 09:43:31 GMT  EAGLE5 42.0.0
    TYPEA  TTN        NDGT
    15     scp3       3
    
    GTT TABLE IS      (27000 of 269999)      10 % FULL
    
    START GTA             END GTA               XLAT   RI     PC
    919                   919                   DPCSSN SSN    002-002-003
         MAPSET=1     SSN=254  GTMODID=---------  CGGTMOD = NO
         LOOPSET = rtp2
    
    Command Retrieved 1 Entries
  24. Backup the new changes using the chg-db:action=backup:dest=fixed command. These messages should appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first.
    BACKUP (FIXED) : MASP A - Backup starts on active MASP.
    BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
    BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
    BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.

Figure 3-23 Change a Global Title Translation - Sheet 1 of 14

Figure 3-24 Change a Global Title Translation - Sheet 2 of 14

Figure 3-25 Change a Global Title Translation - Sheet 3 of 14

Figure 3-26 Change a Global Title Translation - Sheet 4 of 14

Figure 3-27 Change a Global Title Translation - Sheet 5 of 14

Figure 3-28 Change a Global Title Translation - Sheet 6 of 14

Figure 3-29 Change a Global Title Translation - Sheet 7 of 14

Figure 3-30 Change a Global Title Translation - Sheet 8 of 14

Figure 3-31 Change a Global Title Translation - Sheet 9 of 14

Figure 3-32 Change a Global Title Translation - Sheet 10 of 14

Figure 3-33 Change a Global Title Translation - Sheet 11 of 14

Figure 3-34 Change a Global Title Translation - Sheet 12 of 14

Figure 3-35 Change a Global Title Translation - Sheet 13 of 14

Figure 3-36 Change a Global Title Translation - Sheet 14 of 14