Removing a Destination Point Code

This procedure is used to remove a destination point code from the database, using the dlt-dstn command.

The dlt-dstn command uses this parameter:

:dpc/dpca/dpci/dpcn/dpcn24 – The destination point code being removed from the database

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.

The destination point code to be removed must exist in the database, but cannot be assigned to any routes. Enter the rtrv-rte command to see if the destination point code to be removed is assigned to any routes. If the destination point code is assigned to any routes, perform Removing a Route to remove these routes.

The destination point code cannot be defined as an adjacent point code for a linkset. Enter the rtrv-ls to see if the destination point code to be removed is defined as an adjacent point code for a linkset. If the destination point code is defined as an adjacent point code for a linkset, perform Removing a Linkset Containing SS7 Signaling Links.

The destination point code cannot be removed if all of these conditions are present:

• The destination point code is a member of a cluster point code. This is shown by entering the rtrv-dstn command and specifying the destination point code with three asterisks (***) for the network cluster member value of the destination point code instead of the actual network cluster value of the destination point code.
• The NCAI value of the cluster point code is no. This is shown by entering the rtrv-dstn command and specifying the cluster point code.
• The destination point code is the DPC of an exception route. This is shown by entering the rtrv-rtx command and specifying the destination point code that is being removed.

If the destination point code meets these conditions, perform the Removing a Route Exception Entry procedure to remove the exception route entries that reference the DPC that is being removed.

The destination point code cannot be in the mated relay node (MRN) table. Verify this by entering the rtrv-mrn command, specifying the destination point code being removed from the database. If the destination point code 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 cannot be in the mated application (MAP) table. Verify this by entering the rtrv-map command, specifying the destination point code being removed from the database. If the destination point code is shown in the rtrv-map command output, remove the point code from the MAP table, by performing the Removing a Mated Application" procedure in Database Administration - GTT User's Guide.

The destination point code cannot be defined as an end office internal point code. Verify this by entering the rtrv-rmt-appl command. If the destination point code is shown in the rtrv-rmt-appl command output, perform the “Removing an End Node Internal Point Code” procedure in Database Administration - IP7 User's Guide to remove the internal point code.

If the point code being removed in this procedure is a proxy point code, the proxy point code cannot be removed if the proxy point code is assigned to a destination point code or assigned to a linkset. Proxy point codes are shown in the rtrv-dstn:dpc=<DPC value> output with the entry PRX=yes. To verify if the proxy point code is assigned to a destination point code, enter the rtrv-dstn command with the ppc parameter equal to the proxy point code value. This will display all the destination point codes that reference the proxy point code. These destination point codes must be removed before the proxy point code can be removed.

To verify if the proxy point code is assigned to a linkset, enter the rtrv-ls command with the ppc parameter equal to the proxy point code value. This will display all the linksets that reference the proxy point code. These linksets must be removed before the proxy point code can be removed.

Canceling the RTRV-DSTN and RTRV-LS Commands

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

• Press the F9 function key on the keyboard at the terminal where the rtrv-dstn or rtrv-ls command was entered
• Enter the canc-cmd without the trm parameter at the terminal where the rtrv-dstn or rtrv-ls command was entered
• Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-dstn or rtrv-ls command was entered, from another terminal other than the terminal where the rtrv-dstn or rtrv-ls 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 destination point codes, using the rtrv-dstn command.

   This is an example of the possible output.

   rlghncxa03w 10-12-17 16:02:05 GMT  EAGLE5 43.0.0
   Extended Processing Time may be Required
   
      DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
      000-005-000   ----------- yes --- ----------      --------------   SS7
      000-007-000   ----------- yes --- ----------      --------------   SS7
      001-001-001   ----------- yes --- ----------      --------------   SS7
      001-001-002   ----------- yes --- ----------      --------------   SS7
      001-207-000   ----------- yes --- ----------      --------------   SS7
      002-002-002   ----------- yes --- ----------      --------------   SS7
      002-004-100   ----------- yes --- ----------      --------------   SS7
      003-003-003   ----------- yes --- ----------      --------------   SS7
      004-004-004   ----------- yes --- ----------      --------------   SS7
      007-*-*       ----------- yes --- ----------      --------------   SS7
      007-007-007   ----------- yes --- ----------      --------------   SS7
      008-001-001   ----------- yes --- ----------      --------------   SS7
      008-001-003   ----------- yes --- ----------      --------------   SS7
      008-001-004   ----------- yes --- ----------      --------------   SS7
      008-001-005   ----------- yes --- ----------      --------------   SS7
      008-001-006   ----------- yes --- ----------      --------------   SS7
      008-001-007   ----------- yes --- ----------      --------------   SS7
      008-001-008   ----------- yes --- ----------      --------------   SS7
      030-045-*     rlghncbb010 yes yes ----------      --------------   SS7
      111-011-*     rlghncbb000 yes yes ----------      --------------   SS7
      240-012-*     rlghncbb000 yes yes ----------      --------------   SS7
      240-012-004   rlghncbb001 yes ---    1-111-1         10-13-9-3-fr  SS7
      240-012-005   rlghncbb002 yes ---    1-112-2         10-13-10-0-ge SS7
      240-012-006   rlghncbb003 yes ---    1-112-3         10-13-10-1-fr SS7
      240-012-007   ----------- yes ---    1-117-3         10-13-11-1-fr SS7
      240-012-008   ----------- yes ---    1-113-5         10-13-10-2-ge SS7
   
      DPCI          CLLI        BEI ELEI   ALIASA          ALIASN/N24    DMN
      0-015-0       ----------- no  --- --------------   --------------  SS7
      0-017-0       ----------- no  --- --------------   --------------  SS7
      1-011-1       ----------- no  --- --------------   --------------  SS7
      1-011-2       ----------- no  --- --------------   --------------  SS7
      1-207-0       ----------- no  --- --------------   --------------  SS7
      2-131-1       rlghncbb023 no  ---    222-210-000     11-11-8-1-ge  SS7
      2-131-2       ----------- no  ---    222-211-001     11-11-8-2-fr  SS7
      2-131-3       ----------- no  ---    222-211-002     11-11-8-3-ge  SS7
      3-003-3       ----------- no  --- --------------   --------------  SS7
      4-163-5       ----------- no  ---    250-200-007  --------------   SS7
   
      DPCN          CLLI        BEI ELEI   ALIASA          ALIASI        DMN
      7-9-10-1-fr   ----------- no  ---    210-090-100     1-75-6        SS7
      7-9-10-1-ge   ----------- no  ---    210-100-100     2-175-6       SS7
      10-12-0-0-fr  ----------- no  --- --------------   --------------  SS7
      10-15-2-3-fr  rlghncbb013 no  ---    222-200-200     2-121-1       SS7
      10-15-2-3-ge  rlghncbb013 no  ---    222-100-200     2-100-1       SS7
      10-15-3-0-fr  rlghncbb013 no  ---    222-200-201     2-121-2       SS7
      10-15-3-0-ge  rlghncbb013 no  ---    222-100-201     2-100-2       SS7
   
   DESTINATION ENTRIES ALLOCATED:   2000
       FULL DPC(s):                   38
       EXCEPTION DPC(s):               3
       NETWORK DPC(s):                 1
       CLUSTER DPC(s):                 3
       TOTAL DPC(s):                  45
       CAPACITY (% FULL):             2%
   ALIASES ALLOCATED:               8000
       ALIASES USED:                  29
       CAPACITY (% FULL):             1%
   X-LIST ENTRIES ALLOCATED:         500
   RTRV-DSTN: MASP A - COMPLTD
   

   If a quantity of proxy point codes is enabled, the number of proxy point codes that are provisioned in the database are shown at the end of the rtrv-dstn output as shown in this example.

   DESTINATION ENTRIES ALLOCATED:   2000
       FULL DPC(s):                   38
       EXCEPTION DPC(s):               3
       NETWORK DPC(s):                 1
       CLUSTER DPC(s):                 3
       Proxy DPC (s)                   2
       TOTAL DPC(s):                  47
       CAPACITY (% FULL):             2%
   ALIASES ALLOCATED:               8000
       ALIASES USED:                  29
       CAPACITY (% FULL):             1%
   X-LIST ENTRIES ALLOCATED:         500
   RTRV-DSTN: MASP A - COMPLTD
   

2. Verify whether or not the DPC to be removed from the database is a DPC of a route, by entering the rtrv-rte command with the DPC that is to be removed from the database. For this example, enter these commands.

   rtrv-rte:dpca=240-012-007

   This is an example of the possible output.

   rlghncxa03w 07-05-17 16:02:05 GMT  EAGLE5 37.0.0
   
      DPCA           ALIASI      ALIASN/N24    LSN        RC    APCA
      240-012-007    1-117-3     10-13-11-1-fr ls04       10    240-012-007
                                               ls02       20    004-004-004
                                               ls03       30    003-003-003
                                                  RTX:No  CLLI=ls04clli
   

   rtrv-rte:dpca=002-002-002

   rlghncxa03w 07-05-17 16:02:05 GMT  EAGLE5 37.0.0
      DPCA           ALIASI      ALIASN/N24    LSN        RC    APCA
      002-002-002 ----------- --------------   ls20       10    002-002-002 
                                                  RTX:No  CLLI=-----------

   If the DPC being removed from the database is a DPC of a route, perform the Removing a Route procedure to remove the route from the database.

3. Verify whether or not the DPC to be removed from the database is an APC of a linkset, by entering the rtrv-ls command. This is an example of the possible output.

   rlghncxa03w 07-05-10 11:43:04 GMT EAGLE5 37.0.0
   
                                    L3T SLT              GWS GWS GWS
   LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
   e1e2          001-207-000   none 1   1   no  B   6    off off off no    off
   ls1305        000-005-000   none 1   1   no  A   1    off off off no    off
   ls1307        000-007-000   none 1   1   no  A   1    off off off no    off
   e1m1s1        001-001-001   none 1   1   no  A   7    off off off no    off
   e1m1s2        001-001-002   none 1   1   no  A   7    off off off no    off
   ls01          002-004-100   none 1   1   no  A   1    off off off no    off
   ls20          002-002-002   none 1   1   no  PRX 1    off off off no    off
   
                                    L3T SLT              GWS GWS GWS
   LSN           APCI   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
   e1e2i         1-207-0       none 1   1   no  B   4    off off off ---   on
   ls1315        0-015-0       none 1   1   no  A   1    off off off ---   off
   ls1317        0-017-0       none 1   1   no  A   1    off off off ---   on
   e1m2s1        1-011-1       none 1   1   no  A   7    off off off ---   off
   e1m2s2        1-011-2       none 1   1   no  A   7    off off off ---   off
   
   Link set table is (11 of 1024) 1% full.
   

   Perform the Removing a Linkset Containing SS7 Signaling Links procedure to remove the linkset from the database.

4. 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:

   The rtrv-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 the rtrv-feat command description in Commands User's Guide.

   If the GTT feature is off, continue the procedure with 8.

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

5. Display the mated applications in the database, using the rtrv-map command and the DPC being removed from the database. For this example, enter these commands.

   rtrv-map:pca=244-012-007

   This is an example of the possible output.

   rlghncxa03w 10-07-25 09:42:31  GMT  EAGLE5 42.0.0
   
   PCA          Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   244-012-007               252 10  SOL *N  *N  GRP01    OFF
   
   MAP TABLE IS (5 of 1024) 1 % FULL
   

   rtrv-map:pca=002-002-002

   This is an example of the possible output.

   rlghncxa03w 10-07-25 09:42:31  GMT  EAGLE5 42.0.0
   
   PCA          Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
   002-002-002               254 10  SOL *N  *N  GRP01    OFF
   
   MAP TABLE IS (5 of 1024) 1 % FULL
   

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

   If no entries are shown in the rtrv-map output, or the "Removing a Mated Application" procedure was performed in this step, continue the procedure with 6.

6. Verify that the IGTTLS feature is enabled, by entering the rtrv-ctrl-feat command with the IGTTLS part number. Enter this command.

   rtrv-ctrl-feat:partnum=893006901

   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
   Intermed GTT Load Sharing 893006901  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 rtrv-ctrl-feat output in 6 shows that the IGTTLS feature is not enabled, continue the procedure with 8.
   • If the rtrv-ctrl-feat output in 6 shows that the IGTTLS feature is enabled, continue the procedure with 7.
7. Verify whether or not the DPC is in the mated relay node table using the rtrv-mrn command, specifying the destination point code being removed from the database. For this example, enter these commands.

   rtrv-mrn:pca=244-012-007

   This is an example of the possible output.

   rlghncxa03w 09-05-07 00:34:31 GMT EAGLE5 41.0.0
   
        PC             RC
        007-007-007    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.
   

   rtrv-mrn:pca=002-002-002

   This is an example of the possible output.

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

   If the destination point code is shown in the rtrv-mrn command output, remove the point code from the MRN table, by executing the "Removing an MRN Group or MRN Group Entry" procedure in Database Administration - GTT User's Guide.

8. Verify whether or not the DPC is defined as an end office internal point code using the rtrv-rmt-appl command. This is an example of the possible output.

   rlghncxa03w 09-05-28 09:12:36 GMT EAGLE5 41.0.0
   IPCA             SI SSN
   003-003-003      3  100, 110-119, 200
                    5
   
   IPCI             SI SSN
   3-003-3          3  5, 50-100, 250
                    5
   
   IPCN             SI SSN
   10-12-0-0-fr     3  250
                    5
   
   IPCN24           SI SSN
   

   If the destination point code is shown in the rtrv-rmt-appl command output, go to the “Removing an End Node Internal Point Code” procedure in Database Administration - IP7 User's Guide to remove the internal point code.

9. If the point code being removed in this procedure is a proxy point code, the proxy point code cannot be removed if the proxy point code is assigned to a destination point code or assigned to a linkset. Proxy point codes are shown in the rtrv-dstn output with the entry PRX=yes.
   1. If the number of proxy point codes is not shown in rtrv-dstn output in 1, there are no proxy codes in the database. Continue the procedure with 15.Continue the procedure by performing one of these steps.

      Continue the procedure with 15 if the destination point code is not an ANSI point code.

      Continue the procedure with 12 if the destination point code is an ANSI point code.

   2. If the number of proxy point codes are shown in rtrv-dstn output in 1, verify whether or not the DPC being removed is a proxy point code. Display the DPC being removed in this procedure using the rtrv-dstn command specifying the point code being removed. For this example, enter this command.

      rtrv-dstn:dpca=002-002-002

      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
         002-002-002   ----------- no  --- ----------      --------------   SS7
      
         PPCA         NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
         -----------  ---- yes     15     on    17       no     no    none
      
      DESTINATION ENTRIES ALLOCATED:   2000
          FULL DPC(s):                   38
          EXCEPTION DPC(s):               3
          NETWORK DPC(s):                 1
          CLUSTER DPC(s):                 3
          Proxy DPC (s)                   2
          TOTAL DPC(s):                  47
          CAPACITY (% FULL):             2%
      ALIASES ALLOCATED:               8000
          ALIASES USED:                  29
          CAPACITY (% FULL):             1%
      X-LIST ENTRIES ALLOCATED:         500
      RTRV-DSTN: MASP A - COMPLTD
      

   • If the DPC is a proxy point code, shown by the value YES in the PRX column, continue the procedure with 10.
   • If the DPC is not a proxy point code, continue the procedure with 15.continue the procedure by performing one of these steps.
     • Continue the procedure with 15 if the destination point code is not an ANSI point code.
     • Continue the procedure with 12 if the destination point code is an ANSI point code.
10. Display the linksets in the database that have the proxy point code assigned to them by entering the rtrv-ls command with the ppc parameter. The ppc parameter value is the proxy point code being removed in this procedure. For this example, enter this command.

    rtrv-ls:ppc=002-002-002

    This is an example of the possible output.

    rlghncxa03w 07-05-28 21:16:37 EDT EAGLE5 37.0.0     
         
    PPCA = 002-002-002
                                         L3T SLT              GWS GWS GWS     
    LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS    
    ls1305        000-005-000   none 1   1   no  A   1    off off off no    off
    e1m1s2        001-001-002   none 1   1   no  A   7    off off off no    off
    
    Link set table is (10 of 1024) 1% full. 
    

    The linksets displayed in this step have the proxy point code assigned to them. Perform the Removing a Linkset Containing SS7 Signaling Links procedure to remove these linksets. After the linksets have been removed, continue the procedure with 11.

    If no linksets are displayed in this step, then no linksets have the proxy point code assigned to them. Continue the procedure with 11.

11. Display the point codes in the database that have the proxy point code assigned to them by entering the rtrv-dstn command with the ppc parameter. The ppc parameter value is the proxy point code being removed in this procedure. For this example, enter this command.

    rtrv-dstn:ppc=002-002-002

    This is an example of the possible output.

    rlghncxa03w 09-05-28 21:16:37 EDT EAGLE5 41.0.0
    
    PPCA   =    002-002-002
    
       DPCA          CLLI        BEI ELEI   ALIASI           ALIASN/N24    DMN
       000-005-000   ----------- no  --- ----------      --------------    SS7
       001-001-002   ----------- no  --- ----------      --------------    SS7
    
    Destination table is (42 of 2000) 2% full
    Alias table is (29 of 8000) 1% full
    PPC table is (2 of 10) 10% full
    

    If no point codes are displayed in this step, then no point codes have the proxy point code assigned to them. Continue the procedure with 15.Continue the procedure by performing one of these steps.

    • Continue the procedure with 15 if the destination point code is not an ANSI point code.
    • Continue the procedure with 12 if the destination point code is an ANSI point code.

    If point codes are displayed in this step, these point codes have the proxy point code assigned to them. Remove these point codes by entering the dlt-dstn with the point code value shown in the rtrv-dstn output.

    For this example, enter these commands.

    dlt-dstn:dpca=000-005-000

    dlt-dstn:dpca=001-001-002

    When the dlt-dstn command has successfully completed, and the Cluster Routing and Management Diversity feature is turned off (CRMD = off in the rtrv-feat command output), this message should appear.

    rlghncxa03w 09-05-17 15:35:05 GMT EAGLE5 41.0.0
    Destination table is (40 of 2000) 2% full 
    PPC table is (2 of 10) 20% full
    DLT-DSTN: MASP A - COMPLTD
    

    If the Cluster Routing and Management Diversity feature is turned on (CRMD = on in the rtrv-feat command output), this is an example of the message that should appear when the dlt-dstn command has successfully completed.

    rlghncxa03w 09-05-17 15:35:05 GMT EAGLE5 41.0.0
    DESTINATION ENTRIES ALLOCATED:   2000
        FULL DPC(s):                   36
        EXCEPTION DPC(s):               3
        NETWORK DPC(s):                 1
        CLUSTER DPC(s):                 3
        Proxy DPC (s)                   2
        TOTAL DPC(s):                  45
        CAPACITY (% FULL):             2%
    ALIASES ALLOCATED:               8000
        ALIASES USED:                  29
        CAPACITY (% FULL):             1%
    X-LIST ENTRIES ALLOCATED:         500
    RTRV-DSTN: MASP A - COMPLTD
    

    After the point codes have been removed, continue the procedure with 15.continue the procedure by performing one of these steps.

    • Continue the procedure with 15 if the destination point code is not an ANSI point code.
    • Continue the procedure with 12 if the destination point code is an ANSI point code.
12. Verify whether or not the destination point code is a member of a cluster point code by entering the rtrv-dstn command with these parameters and values.
    • The dpca parameter containing the network and cluster values of the destination point code.
    • Three asterisks (***) for the network-cluster member value of the point code.

    For this example, enter these commands.

    rtrv-dstn:dpca=240-012-***

    This is an example of the possible output.

    rlghncxa03w 10-12-17 16:00:32 GMT  EAGLE5 43.0.0
       DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
       240-012-*     rlghncbb000 yes yes ----------      --------------   SS7
       240-012-004   rlghncbb001 yes ---    1-111-1         10-13-9-3-fr  SS7
       240-012-005   rlghncbb002 yes ---    1-112-2         10-13-10-0-ge SS7
       240-012-006   rlghncbb003 yes ---    1-112-3         10-13-10-1-fr SS7
       240-012-007   ----------- yes ---    1-117-3         10-13-11-1-fr SS7
       240-012-008   ----------- yes ---    1-113-5         10-13-10-2-ge SS7
    
       Destination table is (45 of 2000) 2% full
       Alias table is (29 of 8000) 1% full
    

    rtrv-dstn:dpca=002-002-***

    This is an example of the possible output.

    rlghncxa03w 10-12-17 16:00:32 GMT  EAGLE5 43.0.0
       DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
       002-002-002   ----------- yes --- ----------      --------------   SS7
    
    Destination table is (45 of 2000) 2% full
    Alias table is (29 of 8000) 1% full
    

    Continue the procedure by performing one of these steps.

    • Continue the procedure with 15 if the destination point code is not a member of the cluster point code.
    • Continue the procedure with 13 if the destination point code is a member of a cluster point code.
13. Display the attributes of the cluster point code shown in 12 by entering the rtrv-dstn command with the cluster point code shown in 12.

    For this example, enter this command.

    rtrv-dstn:dpca=240-012-*

    This is an example of the possible output.

    rlghncxa03w 10-12-17 16:00:32 GMT  EAGLE5 43.0.0
       DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
       240-012-*     rlghncbb000 yes yes ----------      --------------   SS7
    
       SPCA         NCAI      RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
       -----------  no        none   off   none     no     no    none
    
       Destination table is (45 of 2000) 2% full
       Alias table is (29 of 8000) 1% full
    

    Continue the procedure by performing one of these steps.

    • Continue the procedure with 15 if the NCAI value of the cluster point code is yes.
    • Continue the procedure with 14 if the NCAI value of the cluster point code is no.
14. Display the route exception table entries referencing the destination point code by entering the rtrv-rtx command with the destination point code that is being removed in this procedure. For this example, enter these commands.

    rtrv-rtx:dpca=240-012-007

    This is an example of the possible output.

    rlghncxa03w 10-12-07 00:34:31 GMT EAGLE5 43.0.0
    
       DPCA          RTX-CRITERIA              LSN        RC    APC
    
       240-012-007   OPCA
                     007-007-007               ls01       1     002-004-100
    
     DESTINATION ENTRIES ALLOCATED:   2000
         FULL DPC(s):                   38
         EXCEPTION DPC(s):               3
         NETWORK DPC(s):                 1
         CLUSTER DPC(s):                 3
         TOTAL DPC(s):                  45
         CAPACITY (% FULL):              1%
     ALIASES ALLOCATED:               8000
         ALIASES USED:                  29
         CAPACITY (% FULL):              1%
     X-LIST ENTRIES ALLOCATED:         500
    

    rtrv-rtx:dpca=002-002-002

    This is an example of the possible output.

    rlghncxa03w 10-12-07 00:34:31 GMT EAGLE5 43.0.0
    
       DPCA          RTX-CRITERIA              LSN        RC    APC
    
       002-002-002   OPCA
                     007-007-007               ls01       1     002-004-100
    
    DESTINATION ENTRIES ALLOCATED:   2000
         FULL DPC(s):                  38
         EXCEPTION DPC(s):              3
         NETWORK DPC(s):                1
         CLUSTER DPC(s):                3
         TOTAL DPC(s):                 45
         CAPACITY (% FULL):             1%
     ALIASES ALLOCATED:              8000
         ALIASES USED:                 29
         CAPACITY (% FULL):             1%
     X-LIST ENTRIES ALLOCATED:        500
    

    If the destination point code that is being removed in this procedure is not shown in the rtrv-rtx output, continue the procedure with 15.

    If the destination point code that is 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 15.

15. Remove the destination point code from the database, using the dlt-dstn command. For this example, enter these commands.

    dlt-dstn:dpca=240-012-007

    dlt-dstn:dpca=002-002-002

    When the dlt-dstn command has successfully completed, and the Cluster Routing and Management Diversity feature is turned off (CRMD = off in the rtrv-feat command output), this message should appear.

    rlghncxa03w 09-05-17 15:35:05 GMT EAGLE5 41.0.0
    Destination table is (41 of 2000) 2% full 
    DLT-DSTN: MASP A - COMPLTD
    

    If the Cluster Routing and Management Diversity feature is turned on (CRMD = on in the rtrv-feat command output), this is an example of the message that should appear when the dlt-dstn command has successfully completed.

    rlghncxa03w 09-05-17 15:35:05 GMT EAGLE5 41.0.0
    DESTINATION ENTRIES ALLOCATED:   2000
        FULL DPC(s):                   36
        EXCEPTION DPC(s):               1
        NETWORK DPC(s):                 1
        CLUSTER DPC(s):                 3
        TOTAL DPC(s):                  41
        CAPACITY (% FULL):             2%
    ALIASES ALLOCATED:               8000
        ALIASES USED:                  27
        CAPACITY (% FULL):             1%
    X-LIST ENTRIES ALLOCATED:         500
    DLT-DSTN: MASP A - COMPLTD
    

    If a proxy point code quantity is enabled and and the Cluster Routing and Management Diversity feature is turned off (shown with the CRMD = off entry in the rtrv-feat command output), this message should appear.

    rlghncxa03w 09-05-17 15:35:05 GMT EAGLE5 41.0.0
    Destination table is (41 of 2000) 2% full 
    Alias table is (27 of 12000) 1% full
    PPC table is (1 of 10) 10% full
    DLT-DSTN: MASP A - COMPLTD
    

    If the Cluster Routing and Management Diversity feature is turned on (CRMD = on in the rtrv-feat command output), and a proxy point code quantity is enabled, this message should appear.

    rlghncxa03w 09-05-17 15:35:05 GMT EAGLE5 41.0.0
    DESTINATION ENTRIES ALLOCATED:   2000
        FULL DPC(s):                   33
        EXCEPTION DPC(s):               0
        NETWORK DPC(s):                 1
        CLUSTER DPC(s):                 2
        Proxy DPC (s)                   1
        TOTAL DPC(s):                  37
        CAPACITY (% FULL):             2%
    ALIASES ALLOCATED:               8000
        ALIASES USED:                  27
        CAPACITY (% FULL):             1%
    X-LIST ENTRIES ALLOCATED:         500
    DLT-DSTN: MASP A - COMPLTD
    

16. Verify the changes using the rtrv-dstn command with the DPC specified in 15. For this example, enter these commands.

    rtrv-dstn:dpca=240-012-007

    rtrv-dstn:dpca=002-002-002

    This is an example of the possible output for both of these commands.

    rlghncxa03w 09-05-17 16:02:05 GMT  EAGLE5 41.0.0
    
    No destinations meeting the requested criteria were found
    
    Destination table is (36 of 2000) 2% full
    Alias table is (27 of 8000) 1% full
    

17. 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 2-31 Removing a Destination Point Code

Sheet 1 of 3

Sheet 1 of 4

Sheet 2 of 3

Sheet 2 of 4

Sheet 3 of 3

Sheet 3 of 4

Sheet 4 of 4