Removing a Route

This procedure is used to remove a route from the database using the dlt-rte command.

The dlt-rte command uses these parameters.

:dpc/dpca/dpci/dpcn/dpcn24 – The destination point code of the node shown in the rtrv-rte output.

Note:

See Point Code Formats 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.

:lsn – The name of the linkset that carries the traffic bound for the node specified by the destination point code.

:all – Are all routes associated with the DPC to be removed

The route to be removed must exist in the database. This can be verified in 1.

The last route to a DPC cannot be removed if it is reference by a mated application or concerned signaling point code group. If this condition exists, the command to remove the route from the database is rejected. Before removing the last route to a DPC from the database, enter the rtrv-cspc and rtrv-map commands to verify if the DPC to the route being removed from the database is referenced by either mated applications or concerned signaling point code groups. If rtrv-cspc command output shows a reference to the DPC of the route being removed by this procedure (in the PCA, PCI, PCN, or PCN24 fields), perform the "Removing Concerned Signaling Point Codes" procedure in Database Administration – GTT User's Guide. If the rtrv-map command output shows a reference to the DPC of the route being removed by this procedure (shown in the PCA, PCI, PCN, or PCN24 fields), perform the "Removing a Mated Application" procedure in Database Administration – GTT User's Guide.

The last route to a DPC cannot be removed if it is referenced by a route exception table entry. Use the rtrv-rtx command with the DPC value to display the route exception entries that reference the DPC of the route being removed. If route exception table entries reference the DPC of the route being removed, perform the Removing a Route Exception Entry procedure to remove the route exception table entries that reference the DPC of the route being removed.

The last route to a DPCdestination (Route DPC) cannot be removed if that route is referenced by the gateway screening redirect function’s DPC parameter. Use the rtrv-gws-redirect command to verify the DPC used for the gateway screening redirect function. If the gateway screening redirect function is referencing the destination of the route to be removed from the database, change the gateway screening redirect function’s DPC with the "Changing the Gateway Screening Redirect Parameters" procedures in Database Administration – Features User's Guide. The gateway screening redirect function can also be disabled by using the "Disabling the Gateway Screening Redirect Function" procedure in Database Administration – Features User's Guide.

The last route to a DPC cannot be removed if is referenced in the rtrv-pct output as either a REALPC or FILTPC value. Perform the Removing a Point Code and CIC Translation Entry procedure to remove the point code and CIC entries that reference the DPC of the route.

Either the lsn or all=yes parameters must be specified with the dlt-rte command. If the all=no parameter is specified, the lsn parameter must be specified. If the lsn parameter is specified, the linkset must be defined in the database as a route to the specified route DPC. The linkset name is shown in the LSN field of the rtrv-rte command output.

The route assigned to a full point code DPC cannot be removed from the database if that DPC is a member of a cluster point code in the database if the network cluster allowed indicator (ncai parameter of either the ent-dstn or chg-dstn command) is set to no. If the nested cluster allowed indicator is set to yes, the route to the full point code DPC that is a member of a cluster point code can be removed from the database, but the route to the cluster point code will not be removed from the database, even if the cluster point code and the full point code are assigned to the same route. When the route to the member of the cluster point code is removed from the database, the member of the cluster point code assumes all the attributes of the cluster point code and will use the same routes that are assigned to the cluster point code.

If a route assigned to a cluster point code is removed from the database, all routes to any members of that cluster are also removed from the database if the network cluster allowed indicator is set to no. If the nested cluster allowed indicator is set to yes, the route to the cluster point code can be removed from the database, but any routes to any point codes that are members of the cluster point code remain in the database, even if the cluster point code and its members are assigned to the same route. For more information, refer to the Nested Cluster Routing section.

The destination point code of the route being removed from the database cannot be in the mated relay node (MRN) table. Verify this by entering the rtrv-mrn command, specifying the destination point code of the route being removed from the database. If the destination point code of the route is shown in the rtrv-mrn command output, remove the point code from the MRN table, by performing the "Removing an MRN Group or MRN Group Entry" procedure in Database Administration – GTT User's Guide.

The destination point code of the route being removed from the database cannot be referenced by a global title translation entry shown in the rtrv-gtt or rtrv-gta outputs. Verify this by entering the rtrv-gtt or rtrv-gta command, specifying the destination point code of the route being removed from the database. If the destination point code of the route is shown in the rtrv-gtt output, remove the global title translation entry by performing the "Removing a Global Title Translation" procedure in Database Administration – GTT User's Guide. If the destination point code of the route is shown in the rtrv-gta output, remove the global title translation entry by performing the "Removing Global Title Address Information" procedure in Database Administration – GTT User's Guide.

The destination point code of the route being removed from the database cannot be shown in the rtrv-ppsopts output. Verify this by entering the rtrv-ppsopts command. Any references to the destination point code the rtrv-ppsopts output are removed in 12.

If the APC of the linkset assigned to the route being removed is the same as the DPC of the route, this route cannot be removed if a proxy point code is assigned to the DPC of the route, and the linkset assigned to this route contains these attributes:

• The LST=PRX parameter value
• The proxy point code that is assigned to the DPC of the route is also assigned to the linkset.

If the DPC of the route contains a proxy point code and the linkset contains the value PRX for the linkset type (LST) and the proxy point code value assigned to the route DPC, and there are other routes assigned to this DPC, the other routes to this DPC must be removed before this route can be removed with the dlt-rte command.

The examples in this procedure are used to remove all routes to DPC 003-003-003 from the database.

Canceling the RTRV-RTE Command

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

• Press the F9 function key on the keyboard at the terminal where the rtrv-rte command was entered.
• Enter the canc-cmd without the trm parameter at the terminal where the rtrv-rte command was entered.
• Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-rte command was entered, from another terminal other that the terminal where the rtrv-rte 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 current route configuration using the rtrv-rte 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           ALIASI     ALIASN/N24    LSN        RC    APCA
      001-002-003 --------- --------------    ls04       10    001-002-003
                                                  RTX:No  CLLI=ls04clli
      002-002-100 --------- --------------    ls01       10    002-002-100
                                              ls02       20    004-004-004
                                              ls03       30    003-003-003
                                                  RTX:No  CLLI=ls01clli
      002-007-008 --------- --------------    ls06       10    002-007-008
                                                  RTX:No  CLLI=ls06clli
      002-009-003 ---------- --------------   ls05       10    002-009-003
                                                  RTX:No  CLLI=-----------
      003-003-003 --------- --------------    ls03       10    003-003-003
                                              ls01       20    002-002-100
                                              ls02       30    004-004-004
                                                  RTX:No  CLLI=ls03clli
      004-004-004 --------- --------------    ls02       10    004-004-004
                                              ls01       20    002-002-100
                                              ls03       30    003-003-003
                                                  RTX:No  CLLI=ls02clli
      009-002-003 ---------- --------------   ls07       10    009-002-003
                                                  RTX:No  CLLI=-----------
      140-012-004    1-111-1      11121       ls000001   10    240-012-002
                                              ls000002   10    240-012-003
                                              ls000003   20    240-012-004
                                              ls000004   30    240-012-005
                                              ls000005   40    240-012-006
                                              ls000006   50    240-012-007
                                                  RTX:No  CLLI=dp1
      140-012-005 1-111-2       11122         ls000001   10    240-012-002
                                              ls000002   10    240-012-003
                                              ls000003   20    240-012-004
                                              ls000004   30    240-012-005
                                              ls000005   40    240-012-006
                                              ls000006   50    240-012-007
                                                  RTX:No  CLLI=dp2
      179-100-087 ---------- --------------   atmansi0   10    179-100-087
                                                  RTX:No  CLLI=-----------
      200-050-176 ---------- --------------   atmansi1   10    200-050-176
                                                  RTX:No  CLLI=-----------
   
      DPCI       ALIASN/N24       ALIASA      LSN        RC    APC
      2-234-5    11-13-3-3       240-111-111  ls100001   10    1-234-5
                                              ls100002   10    1-234-6
                                              ls100003   20    1-234-7
                                              ls100004   30    1-234-1
                                              ls100005   40    1-234-2
                                              ls100006   50    1-234-3
                                                  RTX:No  CLLI=idp1
      3-150-4 -------------   --------------  lsi7       10    3-150-4
                                                  RTX:No  CLLI=lsi7clli
   
      DPCN             ALIASA         ALIASI  LSN        RC    APC
      10685      ------------- ---------      lsn5       10    10685
                                                  RTX:No  CLLI=lsi5clli
      13111         011-222-111 0-001-1       ls200001   10    11111
                                              ls200002   10    11112
                                              ls200003   20    11113
                                              ls200004   30    11114
                                              ls200005   40    11115
                                              ls200006   50    11116
                                                  RTX:No  CLLI=ndp1
   
      DPCN24           ALIASA         ALIASI  LSN        RC    APC
   

2. Verify that the GTT feature is on, by entering the rtrv-feat command. If the GTT feature is on, the GTT 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 the rtrv-feat command, see thertrv-feat command description in Commands User's Guide.

   If the GTT feature is off, continue the procedure with 13 #GUID-B7525B57-48D1-4B99-8E3C-4DF18124466D/V709422.

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

3. Display the mated applications in the database, using the rtrv-map command and the DPC of the route being removed from the database. For this example, enter this command.

   rtrv-map:pca=003-003-003

   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
   003-003-003               252 10  SOL *N  *N  GRP01    OFF
   
   MAP TABLE IS (5 of 1024) 1 % FULL
   

   If the DPC of the route is shown in the rtrv-map command output (in the PCA, PCI, PCN, PCN24, MPCA, MPCI, MCPN, or MPCN24 fields), perform the " Removing a Mated Application" procedure in Database Administration – GTT User's Guide, to remove the remove the point code from the mated application that references the DPC of the route.

4. Display the group names in the database using the rtrv-cspc command.

   This is an example of the possible output.

   rlghncxa03w 06-10-07 00:27:31 GMT EAGLE5 36.0.0
   CSPC GRP   NETWORK                PERCENT FULL
   GRP01      ANSI                     3%
   GRP02      ITU-I                   81%
   GRP03      ITU-N                   54%
   GRP04      ANSI                    42%
   GRP05      ANSI                    15%
   GRP10      ANSI                    15%
   GRP15      ANSI                    15%
   

5. Display the point codes in the CSPC group shown in 4, in the GRP NAME field, using the rtrv-cspc command with the CSPC group name whose point codes are the same network type as the DPC of the route being removed.

   Repeat this step until all CSPC groups with the same network type as the DPC of the route have been displayed. For this example, enter this command.

   rtrv-cspc:grp=grp01

   This is an example of the possible output.

   rlghncxa03w 06-10-07 00:28:31 GMT EAGLE5 36.0.0
   CSPC GRP      PC            TYPE
   GRP01         003-003-003   A
                 009-009-009   A
   

   If the DPC of the route is in the CSPC group, perform the "Removing Concerned Signaling Point Codes" procedure in Database Administration – GTT User's Guide to remove the point code from the CSPC group that references the DPC of the route.
6. Display the status of the Intermediate GTT Load Sharing (IGTTLS) controlled feature by entering this command.

   rtrv-ctrl-feat:partnum=893006901

   The following is an example of the possible output.

   rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
   The following features have been permanently enabled:
   
   Feature Name              Partnum    Status  Quantity
   INTERMED GTT LOAD SHARING 893006901  off     ----
   
   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 IGTTLS feature is not enabled, continue the procedure with 8 #GUID-B7525B57-48D1-4B99-8E3C-4DF18124466D/V709422.

   If the IGTTLS feature is enabled, continue the procedure with 7.

7. Display the mated relay node (MRN) groups in the database, using the rtrv-mrn command, specifying the destination point code of the route that is being removed from the database. For this example, enter this command.

   rtrv-mrn:pca=003-003-003

   This is an example of the possible output.

   rlghncxa03w 10-07-07 00:34:31 GMT EAGLE5 42.0.0
   
        PC             RC
        003-003-003    10
        008-001-001    20
        240-012-007    30
        008-001-003    40
        008-001-004    50
        008-001-005    60
        008-001-006    70
        008-001-007    80
        008-001-008    90
   
   
   MRN table is (39 of 3000) 1% full.
   

   If the DPC of the route is not shown in the rtrv-mrn output in this step, continue the procedure with 8.

   If the DPC of the route is shown in the rtrv-mrn output in this step, perform the "Removing an MRN Group or MRN Group Entry" procedure in Database Administration – GTT User's Guide, and remove the remove the point code from the MRN group that references the DPC of the route. After the point code has been removed from the MRN group, continue the procedure with 8.

8. 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
   

9. Display the global title translations in the database using the rtrv-gtt command specifying a translation type from the rtrv-tt command output shown in 8, and the DPC of the route from the database.

   For this example, enter this command.

   rtrv-gtt:typea=10:pca=003-003-003

   This is an example of the possible output.

   rlghncxa03w 10-07-25 09:43:31 GMT  EAGLE5 42.0.0
   TYPEA  TTN        NDGT  
   10     scp2       6
   
   GTT TABLE IS  10 % FULL    (27000 of 269999)
   
   START GTA             END GTA               XLAT   RI     PC
   615370                615380                DPCSSN SSN    003-003-003
        MAPSET=6      SSN=254 NGT=---
   
   Command Retrieved 1 Entries
   

   Repeat this step for each translation type shown in 8.

   If the rtrv-gtt output shows any entries, perform the "Removing a Global Title Translation" procedure in Database Administration – GTT User's Guide to remove the entries shown in this step.

   If the rtrv-gtt output shows no entries or the "Removing a Global Title Translation" procedure was performed, continue the procedure with 10.

10. Display the GTT sets in the database using the rtrv-gttset command.

    This is an example of the possible output.

    rlghncxa03w 10-07-07 00:27:31 GMT EAGLE5 42.0.0
    GTTSN     NETDOM  NDGT
    lidb      ansi    10
    t800      ansi    10
    si000     itu     15
    imsi      itu     15
    abcd1234  itu     12
    
    GTT-SET table is (5 of 2000) 1% full.
    

11. Display the global title address (GTA) information for a GTT set from 10.

    Use the rtrv-gta command with the gttsn parameter value shown in 10, and with the DPC of the route that is being removed from the database. For this example, enter this command.

    rtrv-gta:gttsn=t800:pca=003-003-003

    This is an example of the possible output.

    rlghncxa03w 10-07-07 00:27:31 GMT EAGLE5 42.0.0
    GTTSN     NETDOM  NDGT
    t800      ansi    10
    GTA TABLE IS   1 % FULL  (17 of 269999)
    
    START GTA  END GTA    XLAT   RI     PC
    3365840000 3365849999 dpc    ssn    003-003-003
         MAPSET=6     SSN=0   CCGT=no  NTT=---
    
    Command Retrieved 1 Entries
    

    Repeat this step for each GTT set name type shown in 10.

    If the rtrv-gta output shows any entries, perform the "Removing Global Title Address Information" procedure in Database Administration – GTT User's Guide to remove the entries shown in this step.

    If the rtrv-gta output shows no entries or the "Removing Global Title Address Information" procedure was performed, continue the procedure with 12.

12. Enter the rtrv-ppsopts command to verify that the DPC of the route is not shown in the rtrv-ppsopts output. This is an example of the possible output.

    rlghncxa03w 10-07-20 09:07:58 GMT  EAGLE5 42.0.0
    Prepaid SMS Options
    -------------------
    BPARTYCHK     = OFF
    PPT       PCA/PCI/PCN                   SSN       RI        Set ID
    ---       --------------------          ----      ---       ------
    1         PCI:    1-001-1               25        SSN       DFLT
    2         --------------------          NONE      GT        DFLT
    3         --------------------          NONE      GT        DFLT
    4         PCI:    003-003-003           30        GT        1
    5         --------------------          NONE      GT        DFLT
    6         --------------------          NONE      GT        DFLT
    7         --------------------          NONE      GT        DFLT
    8         PCI:    1-001-1               75        SSN       1
    9         --------------------          NONE      GT        DFLT
    10        --------------------          NONE      GT        DFLT
    11        --------------------          NONE      GT        DFLT
    12        --------------------          NONE      GT        DFLT
    13        --------------------          NONE      GT        DFLT
    14        --------------------          NONE      GT        DFLT
    15        --------------------          NONE      GT        DFLT
    16        --------------------          NONE      GT        DFLT
    17        --------------------          NONE      GT        DFLT
    18        --------------------          NONE      GT        DFLT
    19        --------------------          NONE      GT        DFLT
    20        --------------------          NONE      GT        DFLT
    21        --------------------          NONE      GT        DFLT
    22        --------------------          NONE      GT        DFLT
    23        --------------------          NONE      GT        DFLT
    24        --------------------          NONE      GT        DFLT
    25        --------------------          NONE      GT        DFLT
    26        --------------------          NONE      GT        DFLT
    27        --------------------          NONE      GT        DFLT
    28        --------------------          NONE      GT        DFLT
    29        --------------------          NONE      GT        DFLT
    30        --------------------          NONE      GT        DFLT
    31        --------------------          NONE      GT        DFLT
    32        --------------------          NONE      GT        DFLT
    
    GTA
    ---
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    NONE
    

    Note:

    If the Flexible GTT Load Sharing feature is not enabled, the Set ID column is not displayed in thertrv-ppsopts output.

    If the rtrv-ppsopts output shows any entries that reference the DPC of the route, remove the reference using the chg-ppsopts command with the prepaid portability type (the PPT value) that contains the reference and either the pci=none or pcn=none parameters (depending on the type of point code the prepaid portability type contains).

    chg-ppsopts:ppt=4:pci=none

    This is an example of the possible output.

    rlghncxa03w 07-05-20 09:07:58 GMT  EAGLE5 37.0.0
    CHG-PPSOPTS: MASP A - COMPLTD
    

    Repeat this step for other entries shown in the rtrv-ppsopts output that reference the DPC of the route.

13. Verify whether or not the DPC of the route is referenced by the gateway screening redirect function by entering the rtrv-gws-redirect command.

    The following is an example of the possible output.

    rlghncxa03w 09-05-07 00:17:31 GMT EAGLE5 41.0.0
    ENABLED    DPCA           RI   SSN  TT   GTA
    on         003-003-003    GT   15   225  9105551212
    

    If the DPC of the route is shown in the DPC field, perform the "Changing the Gateway Screening Redirect Parameters" procedure in Database Administration – Features User's Guide to change the gateway screening redirect function’s DPC.

14. If the APC of the linkset assigned to the route being removed is the same as the DPC of the route, this route cannot be removed if a proxy point code is assigned to the DPC of the route, and the linkset assigned to this route contains these attributes.
    • The LST=PRX parameter value
    • The proxy point code that is assigned to the DPC of the route is also assigned to the linkset.

    A quantity of proxy point codes must be enabled for a proxy point code to be assigned to the DPC of the route and to the linkset, and for the linkset type to be PRX (LST=PRX). Enter this command to verify whether or not a proxy point code quantity is enabled.

    rtrv-ctrl-feat:partnum=893018701

    The following is an example of the possible output.

    rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
    The following features have been permanently enabled:
    
    Feature Name              Partnum    Status  Quantity
    Proxy Point Code          893018701  on      20
    
    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 a proxy point code quantity is not enabled, continue the procedure by performing one of these steps.

    • If the route that is being removed is not the last route to the DPC, continue the procedure by performing one of these steps.
      • If the DPC of the route is not an ANSI point code, continue the procedure with one of these steps.
        • Perform 19 if the RTX value of the route, shown in 1 is yes.
        • Perform 21if the RTX value of the route is no.
      • If the DPC of the route is an ANSI point code, continue the procedure with 18.
    • If the route that is being removed is the last route to the DPC, continue the procedure with 17.

    If a proxy point code quantity is enabled, continue the procedure with 15.

15. Verify if a proxy point code is assigned to the DPC of the route. Enter the rtrv-dstn command with the DPC of the route. For this example, enter this command.

    rtrv-dstn:dpca=003-003-003

    The following is an example of the possible output.

    rlghncxa03w 10-12-14 09:13:33 GMT EAGLE5 43.0.0
    
       DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
       003-003-003   rlghncbb334 no  ---    1-112-3         10-13-10-1   SS7
    
       PPCA         NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
       010-010-010  ---- no      none   off   none     no     no    none
    
    Destination table is (13 of 2000) 1% full
    Alias table is (0 of 12000) 0% full
    PPC table is (2 of 10) 20% full
    

    If a proxy point code is not assigned to the DPC of the route, continue the procedure by performing one of these steps.

    • If the route that is being removed is not the last route to the DPC, continue the procedure by performing one of these steps.
      • If the DPC of the route is not an ANSI point code, continue the procedure with one of these steps.
        • Perform 19 if the RTX value of the route, shown in 1 is yes.
        • Perform 21if the RTX value of the route is no.
      • If the DPC of the route is an ANSI point code, continue the procedure with 18.
    • If the route that is being removed is the last route to the DPC, continue the procedure with 17.

    If a proxy point code is assigned to the DPC of the route, continue the procedure with 16.

16. Verify the attributes of the linkset assigned to the route being removed by entering the rtrv-ls command with the name of the linkset. For this example, enter this command.

    rtrv-ls:lsn=ls03

    The following is an example of the possible output.

    rlghncxa03w 07-08-14 09:24:36 EST  37.0.0
    
                                     L3T SLT              GWS GWS GWS
    LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
    ls03          003-003-003   none 1   1   no  PRX 0    off off off no    off
    
                  PPCA          CLLI         TFATCABMLQ MTPRSE ASL8
                  010-010-010   -----------  1          ---    no
    
               IPGWAPC MATELSN    IPTPS  LSUSEALM SLKUSEALM GTTMODE
               no      ---------- ----   ---      ---       CdPA
    
    Link set table is (9 of 1024) 1% full.
    

    If the linkset contains the value PRX for the linkset type (LST) and the proxy point code value shown in 15, the other routes to this DPC must be removed before this route can be removed in 21.

    Whether or not the linkset contains the PRX linkset type and the proxy point code value shown in 15, continue the procedure by performing one of these steps.

    • If the route that is being removed is not the last route to the DPC, continue the procedure by performing one of these steps.
      • If the DPC of the route is not an ANSI point code, continue the procedure with one of these steps.
        • Perform 19 if the RTX value of the route, shown in 1 is yes.
        • Perform 21 if the RTX value of the route is no.
      • If the DPC of the route is an ANSI point code, continue the procedure with 18.
    • If the route that is being removed is the last route to the DPC, continue the procedure with 17.
17. Display the PCT (point code and CIC translation) entries by entering the rtrv-pct command.

    This is an example of the possible output.

    rlghncxa03w 10-12-17 16:02:05 GMT  EAGLE5 43.0.0
    
        EPCA             FILTPCA          REALPCA      SI  SSN  RELCAUSE
        001-001-001      *                002-002-002   5  ---   10
    
        ECICS = 10          ECICE = 20
        RCICS = 30          RCICE = 40
    
        001-001-001      *                003-003-003   5  ---   20
    
        ECICS = 70          ECICE = 80
        RCICS = 90          RCICE = 90
    
        006-006-006      003-003-003      020-020-020   3  200  ---
    
        ECICS = ----------  ECICE = ----------
        RCICS = ----------  RCICE = ----------
        
        007-007-007      009-009-009      008-008-008   3  135  ---
    
        ECICS = ----------  ECICE = ----------
        RCICS = ----------  RCICE = ----------
    
        007-007-007      010-010-010      008-008-008   5  ---   50
    
        ECICS = 200         ECICE = 224
        RCICS = 300         RCICE = 324
    
        EPCI             FILTPCI          REALPCI      SI  SSN  RELCAUSE
        1-001-2          2-002-2          2-002-2       3   10  ---
    
        ECICS = ----------  ECICE = ----------
        RCICS = ----------  RCICE = ----------
    
        EPCN             FILTPCN          REALPCN      SI  SSN  RELCAUSE
        00300            *                00200         *  ---  ---
    
        ECICS = ----------  ECICE = ----------
        RCICS = ----------  RCICE = ----------
    
    
     Unique EPC    is 4 of 250
     Unique RealPC is 5 of 250
    
     PCT table is (6 of 1000) 1% full.
    

    If the DPC of the route is shown in the rtrv-pct output, perform the Removing a Point Code and CIC Translation Entry procedure to remove the PCT entries whose REALPC or FILTPC values are the DPC of the route.

    If the DPC of the route is not shown in the rtrv-pct output, or the Removing a Point Code and CIC Translation Entry procedure was performed, continue the procedure by performing one of these steps.

    • If the DPC of the route is not an ANSI point code, continue the procedure with one of these steps.
      • Perform 19 if the RTX value of the route, shown in 1 is yes.
      • Perform 21 if the RTX value of the route is no.
    • If the DPC of the route is an ANSI point code, continue the procedure with 18.
18. Verify whether or not the DPC of the route is a member of a cluster point code by entering the rtrv-rte command with these parameters and values.
    • The dpca parameter containing the network and cluster values of the DPC of the route.
    • Three asterisks (***) for the network-cluster member value of the point code.
    • The mode=full parameter.

    For this example, enter this command.

    rtrv-rte:dpca=003-003-***:mode=full

    This is an example of the possible output.

    rlghncxa03w 10-12-17 16:00:32 GMT  EAGLE5 43.0.0
    
    DPCA             ALIASI           ALIASN/N24    RTX   CLLI
                                      LSN           RC    APCA
    003-003-*     --------------   --------------   No    -----------
                                      ls1           1     002-002-002
                                      ls2           2     003-003-003
    003-003-003      1-112-3          10-13-10-1    Yes   -----------
                                      ls1           1     002-002-002
                                      ls2           2     003-003-003
    
                     OPCA
                     011-011-011      ls3           1     004-004-004
    
    003-003-200      1-117-3          10-13-11-1    Yes   -----------
                                      ls1           1     002-002-002
                                      ls2           2     003-003-003
    
                     OPCA
                     010-010-010      ls3           1     004-004-004
    
    003-003-225   --------------   --------------   Yes   -----------
                                      ls1           1     002-002-002
                                      ls2           2     003-003-003
    

    If the DPC of the route is not a member of a cluster point code, continue the procedure by performing one of these steps.

    • Perform 19 if the RTX value of the route, shown in RTX field of the rtrv-rte output in 1, is yes and the last route to the DPC of the route is being removed.
    • Perform 21 if these either of these conditions are present.
      • The RTX value of the route is no.
      • The RTX value of the route is yes and the last route to the DPC is not being removed.

    If the DPC of the route is a member of a cluster point code, continue the procedure with 20.

19. Display the route exception table entries referencing the DPC of the route by entering the rtrv-rtx command with the DPC of the route being removed in this procedure. For this example, enter this command.

    rtrv-rtx:dpca=003-003-003

    rlghncxa03w 10-12-07 00:34:31 GMT EAGLE5 43.0.0
    
       DPCA          RTX-CRITERIA              LSN        RC    APC
    
       003-003-003   OPCA
                     007-007-007               ls01       1     002-002-100
    
    DESTINATION ENTRIES ALLOCATED:   2000
        FULL DPC(s):                   40
        EXCEPTION DPC(s):               1
        TOTAL DPC(s):                  41
        CAPACITY (% FULL):              1%
    ALIASES ALLOCATED:               12000
        ALIASES USED:                   0
        CAPACITY (% FULL):              0%
    

    If the DPC of the route being removed in this procedure is shown in the rtrv-rtx output, perform the Removing a Route Exception Entry procedure to remove all the route exception table entries shown in this step. After the exception routes have been removed, continue the procedure with 21.

20. Display the attributes of the cluster point code by entering the rtrv-dstn command with the cluster point code value shown in 18. For this example, enter this command.

    rtrv-dstn:dpca=003-003-*

    This is an example of the possible output.

    rlghncxa03w 10-12-28 21:16:37 GMT EAGLE5 43.0.0
    
       DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
       003-003-*     rlghncbb333 yes no   ----------      --------------   SS7
    
       SPCA         NCAI         RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
       -----------  no           none   off   none     no     no    none
    
    Destination table is (11 of 2000) 1% full
    Alias table is (6 of 8000) 1% full
    

    To remove all the routes to the cluster point code and all the routes to the members of the cluster point code (shown in 18) with the all=yes parameter of the dlt-rte command, the NCAI value of the cluster point code must be no. Perform the Changing the Attributes of a Cluster Point Code procedure to change the NCAI value of the cluster point code to no if required. The RTX=yes value in the rtrv-rte output shows that exception routes reference the DPC of the route. To remove the routes to the members of the cluster point code, the exception routes that reference the DPC of the routes must be removed. Perform the Removing a Route Exception Entry procedure to remove the exception routes shown in the rtrv-rte output in 18. After the NCAI value has been verified and changed in necessary, and any exception routes have been removed if necessary, continue the procedure with 21 specifying the cluster point code that was specified in this step and with the all=yes parameter.

    To remove all the routes to the cluster point code and without removing all the routes to the members of the cluster point code (shown in 18) with the all=yes parameter of the dlt-rte command, the NCAI value of the cluster point code must be yes. Perform the Changing the Attributes of a Cluster Point Code procedure to change the NCAI value of the cluster point code to yes if required. After the NCAI value has been verified and changed in necessary, continue the procedure with 21 specifying the cluster point code that was specified in this step and with the all=yes parameter.

    To remove a single route to the cluster point code or a route to a member of the cluster point code (shown in 18) with the lsn parameter of the dlt-rte command, the NCAI value of the cluster point code must be yes. Perform the Changing the Attributes of a Cluster Point Code procedure to change the NCAI value of the cluster point code to yes if required. The RTX=yes value in the rtrv-rte output shows that exception routes reference the DPC of the route. To remove the last route to the member of the cluster point code, the exception routes that reference the DPC of the route must be removed. Perform the Removing a Route Exception Entry procedure to remove the exception routes shown in the rtrv-rte output in 18. After the NCAI value has been verified and changed in necessary, and any exception routes have been removed if necessary, continue the procedure with 21 specifying the DPC of the route and with the lsn parameter.

21. Remove the routes from the database using the dlt-rte command. For this example, enter this command.

    dlt-rte:dpca=003-003-003:all=yes

    A specific route to a DPC can be removed from the database. To do this, specify the lsn parameter instead of the all parameter and the linkset name of the route you wish to remove. For this example, enter this command.

    dlt-rte:dpca=003-003-003:lsn=ls03

    If the linkset contains the value PRX for the linkset type (LST) (shown in 16) and the proxy point code value shown in 15, the other routes to this DPC must be removed before this route can be removed in this step. For this example, enter the dlt-rte command with the lsn parameter to remove the linksets ls01 and ls02 from route DPC 003-003-003, before removing linkset ls03. For this example, enter these commands.

    dlt-rte:dpca=003-003-003:lsn=ls01

    dlt-rte:dpca=003-003-003:lsn=ls02

    dlt-rte:dpca=003-003-003:lsn=ls03

    If the NCAI field value in 20 is no, and was not changed, enter the dlt-rte command specifying the cluster point code as the value of the dpca parameter. For this example, enter this command.

    dlt-rte:dpca=003-003-*:all=yes

    When either of these commands have successfully completed, this message should appear.

    rlghncxa03w 06-10-07 08:45:54 GMT  EAGLE5 36.0.0
    DLT-RTE: MASP A - COMPLTD
    

22. Verify the changes using the rtrv-rte command, specifying the destination point code of the route. For this example, enter this command.

    rtrv-rte:dpc=003-003-003

    If all routes to the DPC were removed in 21, this is an example of the possible output.

    rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 36.0.0
       DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
       003-003-003 ---------- --------------   ---------- -- -----------
                                                   RTX:No  CLLI=ls03clli
    

    If a specific route to the DPC was removed in 21, this is an example of the possible output.

    rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 36.0.0
       DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
       003-003-003 ----------- -----------     ls01       20    002-002-002
                                               ls02       30    004-004-004
                                                   RTX:No  CLLI=ls03clli
    

23. Back up 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-21 Removing a Route

Sheet 1 of 8

Sheet 2 of 8

Sheet 3 of 8

Sheet 4 of 8

Sheet 5 of 8

Sheet 6 of 8

Sheet 7 of 8

Sheet 8 of 8