Go to primary content
Oracle® Communications EAGLE Database Administration - SS7 User's Guide
Release 46.7
E97335 Revision 1
Go To Table Of Contents
Contents

Previous
Previous
Next
Next

Changing the Attributes of a Cluster Point Code

This procedure is used to change the attributes of a cluster point code in the database, using the chg-dstn command.

Note:

Cluster entries can be provisioned only as ANSI destination point codes. Cluster entries cannot be provisioned for ITU international or ITU national destination point codes, and cannot be provisioned as a proxy point code. The ANSI alias point code for an ITU international or ITU national destination point code must be a full point code. An ANSI private point code must be a full point code.

To add a new cluster point code to the database, perform the Adding a Cluster Point Code procedure.

To remove a cluster point code from the database, perform the Removing a Destination Point Code procedure.

The cluster point code to be changed must be in the database.

The chg-dstn command uses these parameters:

:dpc/dpca – The destination point code in the database being changed

Note:

See Point Code Formats for a definition of the point code types that are used on the EAGLE.

Note:

Alias point codes (aliasi/aliasn/aliasn24) and secondary point codes (spc/spca) cannot be specified for a cluster point code.

:clli – The Common Language Location Identifier assigned to this point code

:domain – The network in which the destination entity or node exists- SS7.

:bei – Broadcast exception indicator that indicates whether transfer-prohibited (TFP) messages will be broadcast from this node. The bei=yes parameter means TFPs will not be broadcast. The bei=no parameter means TFPs will be broadcast.

:ipgwapc – (ANSI networks only)IP Gateway Adjacent Point Code indicator. Specify ipgwapc=yes to provide SS7 linkset definition compatibility for gateway connections to IP-SCPs. The default is ipgwapc=no.

:elei – For cluster point codes only. Specifies whether or not the EAGLE maintains a dynamic status exception list for each cluster route that may be used to reach the member signaling points making up the cluster. The elei=yes parameter means the EAGLE does not maintain an exception list for the cluster point code specified by the dpc parameter. The elei=no parameter means the EAGLE does maintain an exception list for the cluster point code specified by the dpc parameter.

:ncai – The nested-cluster-allowed indicator specifies whether or not the route to the cluster point code can be different from the route to a point code that is a member of the cluster point code. A point code is a member of a cluster point code if it has the same network identifier (NI) and network cluster (NC) values as the cluster point code. This parameter can be specified only for cluster point codes.

If the ncai parameter value is yes, the cluster point code is a nested cluster point code. Point codes that are members of this cluster point code can be assigned to routesets that are different from the routeset assigned to the cluster point code.

If the ncai parameter value is no, the cluster point code is not a nested cluster point code. Point codes that are members of this cluster point code must be assigned to the same routeset assigned to the cluster point code.

Refer to the Nested Cluster Routing section for more information on the nested cluster routing feature.

:nprst - NM bits reset. This parameter specifies whether the NM bits in an ITU IAM message should be set to 00. This parameter has two values.
  • off - Do not set NM bits to 00 in an ITU IAM message if the nptype option value in the rtrv-tifopts output is nm.
  • on - Set the NM bits to 00 in an ITU IAM message if the nptype option value in the rtrv-tifopts output is nm.

    The default value for this parameter is off.

:rcause - Release cause. This parameter specifies the condition that triggers the sending of a Release message. This parameter has these values.
  • 0 - 127
  • none - use the values specified for the rcausenp and rcausepfx parameters in the rtrv-tifopts output.

    The default value for this parameter is none.

    If the rlcopc parameter value in the rtrv-tipopts output is on and a value of 0-127 is specified for the rcause parameter, then the rcause parameter value overrides the values specified for the rcausenp and rcausepfx parameters in the rtrv-tifopts output.

:splitiam - This parameter specifies how and when to split an ITU IAM message into one IAM message and one SAM message. This parameter has these values.
  • 15-31 - The maximum number of CdPN digits allowed in the IAM message before the splitting occurs. The remaining digits, up to a total of 32, are encoded in the SAM message.
  • none - the value specified for the splitiam parameter in the rtrv-tifopts output is used to determine when to split the IAM message.

    The default value for this parameter is none.

To specify the nprst or rcause parameters, the TIF Number Portability feature, part number 893018901, must be enabled. To specify the splitiam parameter, at least one of these features must be enabled.
  • TIF Number Portability - part number 893018901
  • TIF SCS Forwarding - part number 893022201
  • TIF Simple Number Substitution - part number 893024001
  • TIF Additional Subscriber Data - part number 893024501
  • TIF Generic Routing Number - part number 893025501

    The status of these features is shown in the rtrv-ctrl-feat output. Perform the procedures in TIF User's Guide to enable these features.

:sccpmsgcnv - The sccpmsgcnv parameter controls SCCP UDT(S)/XUDT(S) message conversion for the specified destination. This parameter can be specified only if the XUDT UDT Conversion feature is enabled and turned on. The rtrv-ctrl-feat output shows the status of the XUDT UDT Conversion feature. If the XUDT UDT Conversion feature is not enabled or turned on, perform the "Activating the XUDT UDT Conversion Feature" procedure in Database Administration - GTT User's Guide to enable and turn on the XUDT UDT Conversion feature. This parameter contains these values.
  • none - SCCP UDT(S)/XUDT(S) message conversion is not performed on messages for the destination.
  • udt2xudt - All UDT(S) messages for the destination are converted to XUDT(S) messages.
  • xudt2udt - All non-segmented XUDT(S) messages for the destination are converted to UDT(S) messages. Segmented XUDT(S) messages for the destination are not converted to UDT(S ) messages.
  • sxudt2udt - All segmented and non-segmented XUDT(S) messages for the destination are converted to UDT(S) messages.

The chg-dstn command also contains the homescp and homesmsc parameters. The values for these parameters are yes and no. The value no is the system default value for these parameters. The value yes for these parameters cannot be specified for a cluster point code. To specify the value yes for these parameters, perform the Adding a Destination Point Code or Changing a Destination Point Code procedures.

The value of the clli parameter cannot be in the DPC table and cannot match the CLLI of the EAGLE. Verify this by entering the rtrv-dstn and the rtrv-sid commands, shown in 1 and 3. If the value of the clli parameter matches any CLLI values in either of these outputs, choose another value for the clli parameter that does not match any CLLIs shown in either of these command outputs.

If a nested cluster point code is changed to a non-nested cluster point code (the value of the ncai parameter is changed from yes to no), any point codes that are members of this point code must be assigned to the same routeset as the cluster point code.

The elei (exception list exclusion indicator) parameter can be specified only for a cluster destination point code. Cluster destination point codes and the elei parameter can be specified only if the Cluster Routing and Management Diversity feature is turned on. Verify this with the rtrv-feat command. If the Cluster Routing and Management Diversity feature is turned on, the CRMD field should be set to on. If the Cluster Routing and Management Diversity feature is not turned on, enter the chg-feat:crmd=on command. For more information on the Cluster Routing and Management Diversity feature, refer to the Cluster Routing and Management Diversity (CRMD) section.

The ncai parameter can be specified only if the Nested Cluster Routing feature is on. This can be verified with the entry NCR = on in the rtrv-feat command output. If the nested cluster routing feature is not turned on, enter the chg-feat:ncr=on command. For more information on the nested cluster routing feature, refer to the Nested Cluster Routing section.

Note:

Once the Cluster Routing and Management Diversity and nested cluster routing features are turned on with the chg-feat command, they cannot be turned off.

The Cluster Routing and Management Diversity and nested cluster routing features must be purchased before you turn these features on with the chg-feat command. If you are not sure if you have purchased the Cluster Routing and Management Diversity and nested cluster routing features, contact your Sales Representative or Account Representative.

The examples in this procedure are used to change the attributes of the cluster point code 030-003-*.

Canceling the RTRV-DSTN and RTRV-RTE Commands

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

  • Press the F9 function key on the keyboard at the terminal where the rtrv-dstn or rtrv-rte command was entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-dstn or rtrv-rte command was entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-dstn or rtrv-rte command was entered, from another terminal other than the terminal where the rtrv-dstn or 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, refer 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-10 11:43:04 GMT EAGLE5 43.0.0
    Extended Processing Time may be Required
    
       DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
       020-002-*     rlghncbb000 yes yes ----------      --------------   SS7
       240-012-004   rlghncbb001 yes ---    1-111-1         10-13-9-3     SS7
       240-012-005   rlghncbb002 yes ---    1-112-2         10-13-10-0    SS7
       240-012-006   rlghncbb003 yes ---    1-112-3         10-13-10-1    SS7
       240-012-007   ----------- yes ---    1-117-3         10-13-11-1    SS7
       240-012-008   ----------- yes ---    1-113-5         10-13-10-2    SS7
       030-003-*     rlghncbb333 yes yes ----------      --------------   SS7
       030-003-100   rlghncbb334 yes ---    1-112-3         10-13-10-1    SS7
       030-003-200   rlghncbb335 yes ---    1-117-3         10-13-11-1    SS7
       030-003-225   rlghncbb336 yes --- ----------      --------------   SS7
    
       DPCI          CLLI        BEI ELEI   ALIASA          ALIASN/N24    DMN
       2-131-1       rlghncbb023 no  ---    222-210-000     11-11-8-1     SS7
       2-131-2       ----------- no  ---    222-211-001     11-11-8-2     SS7
       2-131-3       ----------- no  ---    222-211-002     11-11-8-3     SS7
       4-163-5       ----------- no  ---    250-200-007     15-11-5-1     SS7
    
       DPCN          CLLI        BEI ELEI   ALIASA          ALIASI        DMN
       7-9-10-1      ----------- no  ---    210-090-100     1-75-6        SS7
       10-15-2-3     rlghncbb013 no  ---    222-200-200     2-121-1       SS7
       10-15-3-0     rlghncbb013 no  ---    222-200-201     2-121-2       SS7
    
    
    DESTINATION ENTRIES ALLOCATED:   2000
        FULL DPC(s):                   20
        EXCEPTION DPC(s):               0
        NETWORK DPC(s):                 0
        CLUSTER DPC(s):                 2
        TOTAL DPC(s):                  22
        CAPACITY (% FULL):             1%
    ALIASES ALLOCATED:               8000
        ALIASES USED:                  28
        CAPACITY (% FULL):             1%
    X-LIST ENTRIES ALLOCATED:         500
    RTRV-DSTN: MASP A - COMPLTD
    

    If the CLLI value for the cluster point code is not being changed in this procedure, continue the procedure with 3.

    If the CLLI value for the cluster point code is being changed in this procedure, continue the procedure with 2.

  2. Display the self-identification of the EAGLE using the rtrv-sid command.

    This is an example of the possible output.

    rlghncxa03w 07-05-10 11:43:04 GMT EAGLE5 37.0.0
       PCA             PCI          PCN                CLLI              PCTYPE
    
       010-020-030     0-123-1      12-0-14-1          rlghncxa03w       OTHER
    
       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
    

    If the CLLI value for the cluster point code is being changed in this procedure, that CLLI value cannot be shown in the CLLI fields of either the rtrv-dstn (1) or the rtrv-sid command outputs.

  3. Display the attributes of the cluster point code being changed, by entering the rtrv-dstn command and specifying the cluster point code that is being changed.

    For this example, enter this command.

    rtrv-dstn:dpca=030-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
       030-003-*     rlghncbb333 yes yes ----------      --------------   SS7
    
       SPCA         NCAI         RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
       -----------  yes          none   off   none     no     no    none
    
    DESTINATION ENTRIES ALLOCATED:   2000
        FULL DPC(s):                   20
        EXCEPTION DPC(s):               0
        NETWORK DPC(s):                 0
        CLUSTER DPC(s):                 2
        TOTAL DPC(s):                  22
        CAPACITY (% FULL):             1%
    ALIASES ALLOCATED:               8000
        ALIASES USED:                  28
        CAPACITY (% FULL):             1%
    X-LIST ENTRIES ALLOCATED:         500
    RTRV-DSTN: MASP A - COMPLTD
    
    Continue the procedure by performing one of these steps.
    • If the nprst, rcause, splitiam, sccpmsgcnv, or ncai parameter values will not be changed, continue the procedure with 10.
    • If only the ncai parameter value will be changed, continue the procedure by performing one of these steps.
      • If the current ncai parameter value is no, continue the procedure with 8.
      • If the current ncai parameter value is yes, continue the procedure with 6.
    • If the sccpmsgcnv parameter value will be changed and the nprst, rcause, or splitiam parameter values will not be changed, continue the procedure with 5.
    • If the nprst, rcause, or splitiam parameter value will be changed, continue the procedure with 4.
  4. Display the features that are enabled by entering the rtrv-ctrl-featcommand. This is an example of the possible output.
    rlghncxa03w 10-12-17 15:35:05 GMT  EAGLE5 43.0.0
    The following features have been permanently enabled:
    
    Feature Name              Partnum   Status Quantity
    HC-MIM SLK Capacity       893012707 on     64
    TIF Number Portability    893018901 off    ----
    XUDT UDT Conversion       893035301 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.
    
    To specify the nprst or rcause parameters, the TIF Number Portability feature, part number 893018901, must be enabled. To specify the splitiam parameter, at least one of these features must be enabled.
    • TIF Number Portability - part number 893018901
    • TIF SCS Forwarding - part number 893022201
    • TIF Simple Number Substitution - part number 893024001
    • TIF Additional Subscriber Data - part number 893024501
    • TIF Generic Routing Number - part number 893025501

    Perform the procedures in TIF User's Guide to enable these features as required.

    Continue the procedure by performing one of these steps.
    • If the sccpmsgcnv or ncai parameter values will not be changed, continue the procedure with 10.
    • If only the ncai parameter value will be changed, continue the procedure by performing one of these steps.
      • If the current ncai parameter value is no, continue the procedure with 8.
      • If the current ncai parameter value is yes, continue the procedure with 6.
    • If the sccpmsgcnv parameter value will be changed, continue the procedure with 5.
  5. To specify the sccpmsgcnv parameter the XUDT UDT Conversion feature must be enabled and turned on.
    If 4 was performed and the rtrv-ctrl-feat output in 4 shows that the XUDT UDT Conversion feature is enabled and turned on, continue the procedure by performing one of these steps.
    • If the ncai parameter values will not be changed, continue the procedure with 10.
    • If the ncai parameter value will be changed, continue the procedure by performing one of these steps.
      • If the current ncai parameter value is no, continue the procedure with 8.
      • If the current ncai parameter value is yes, continue the procedure with 6.

    If 4 was performed and the rtrv-ctrl-feat output in 4 shows that the XUDT UDT Conversion feature is not enabled and turned on, perform the "Activating the XUDT UDT Conversion Feature" procedure in Database Administration - GTT User's Guide to enable and turn on the XUDT UDT Conversion feature.

    If 4 was not performed, enter this command to verify the status of the XUDT UDT Conversion feature.

    rtrv-ctrl-feat:partnum=893035301

    This is an example of the possible output.

    rlghncxa03w 10-12-17 15:35:05 GMT  EAGLE5 43.0.0
    The following features have been permanently enabled:
    
    Feature Name              Partnum   Status Quantity
    XUDT UDT Conversion       893035301 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 this step shows that the XUDT UDT Conversion feature is not enabled or turned on, perform the "Activating the XUDT UDT Conversion Feature" procedure in Database Administration - GTT User's Guide to enable and turn on the XUDT UDT Conversion feature.

    If the rtrv-ctrl-feat output in this step shows that the XUDT UDT Conversion feature is enabled and turned on, or the "Activating the XUDT UDT Conversion Feature" procedure was performed in this step, continue the procedure by performing one of these steps.
    • If the ncai parameter values will not be changed, continue the procedure with 10.
    • If the ncai parameter value will be changed, continue the procedure by performing one of these steps.
      • If the current ncai parameter value is no, continue the procedure with 8.
      • If the current ncai parameter value is yes, continue the procedure with 6.
  6. Enter the rtrv-dstn command with the cluster point code being changed, but with three asterisks for the network-cluster member value of the cluster point code instead of one asterisk.

    For this example, enter this command.

    rtrv-dstn:dpca=030-003-***

    This is an example of the possible output.

    rlghncxa03w 09-05-28 21:16:37 GMT EAGLE5 41.0.0
    
       DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
       030-003-*     rlghncbb333 yes yes ----------      --------------   SS7
       030-003-100   rlghncbb334 yes no     1-112-3         10-13-10-1    SS7
       030-003-200   rlghncbb335 yes no     1-117-3         10-13-11-1    SS7
       030-003-225   rlghncbb336 yes no  ----------      --------------   SS7
    
    Destination table is (20 of 2000) 1% full
    Alias table is (28 of 8000) 1% full
    RTRV-DSTN: MASP A - COMPLTD
    

    If the cluster point code does not have any member point codes in the database, continue the procedure with 8.

    If the cluster point code has member point codes in the database, continue the procedure with 7.

  7. Display the routes to the members of the cluster point code, shown in 6, in the database using the rtrv-rte command with the DPC values shown in 6 for the members of the cluster point code.

    For this example, enter these commands.

    rtrv-rte:dpca=030-003-100

    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
       030-003-100    1-112-3    10-13-10-1    ls000300   10    030-003-100
    
                                                   RTX:No  CLLI=rlghncbb334
    

    rtrv-rte:dpca=030-003-200

    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
       030-003-200    1-117-3    10-13-11-1    ls000301   10    10 030-003-200
    
                                                   RTX:No  CLLI=rlghncbb335
    

    rtrv-rte:dpca=030-003-225

    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
       030-003-225 ---------- --------------   ls000301   10    030-003-300
    
                                                   RTX:No  CLLI=rlghncbb336
    

    If the NCAI parameter is being changed from YES to NO, the routes to the point codes that are members of the cluster point code being changed must be removed from the database. Perform the Removing a Route procedure to remove these routes from the database. For this example, the routes to point codes 030-003-100, 030-003-200, and 030-003-225 must be removed. Continue the procedure with 10.

  8. Verify that the nested cluster routing feature is on with the rtrv-feat command.

    If the nested cluster routing feature is turned on, the NCR field should be set to on. In this example, the nested cluster routing feature is off.

    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, see thertrv-feat command description in Commands User's Guide.

    If the nested cluster routing feature is on, continue the procedure with 10.

    If the nested cluster routing feature is off, continue the procedure with 9.

  9. Turn the nested cluster routing feature on by entering this command.

    chg-feat:ncr=on

    Note:

    Once the nested cluster routing feature is turned on with thechg-feat command, it cannot be turned off

    The nested cluster routing feature must be purchased before you turn this feature on with the chg-feat command. If you are not sure if you have purchased the nested cluster routing features, contact your Sales Representative or Account Representative.

    When this command has successfully completed, this message should appear.

    rlghncxa03w 07-05-10 11:43:04 GMT EAGLE5 37.0.0
    CHG-FEAT: MASP A - COMPLTD
    
  10. Change the attributes of the cluster point code, using the chg-dstn command.

    If the rcause, nprst, and splitiam parameters will be specified for the cluster point code, one or more of the features shown in 4 must be enabled.

    If the sccpmsgcnv parameter will be specified for the cluster point code, the XUDT UDT Conversion feature, shown in the rtrv-ctrl-feat output in either 4 or 5, must be enabled.

    For this example, enter this command.

    chg-dstn:dpca=030-003-*:clli=ls09clli:ncai=no:elei=no:nprst=on:rcause=5 :splitiam=20:sccpmsgcnv=xudt2udt

    When this command has successfully completed, this message should appear.

    rlghncxa03w 07-05-17 15:35:05 GMT EAGLE5 37.0.0
    
    DESTINATION ENTRIES ALLOCATED:   2000
        FULL DPC(s):                   20
        EXCEPTION DPC(s):               0
        NETWORK DPC(s):                 0
        CLUSTER DPC(s):                 2
        TOTAL DPC(s):                  22
        CAPACITY (% FULL):             1%
    ALIASES ALLOCATED:               8000
        ALIASES USED:                  28
        CAPACITY (% FULL):             1%
    X-LIST ENTRIES ALLOCATED:         500
    CHG-DSTN: MASP A - COMPLTD
    
  11. Verify the changes using the rtrv-dstn command, and specifying the cluster point code that was entered in 10 with the dpca parameter.

    For this example, enter this command.

    rtrv-dstn:dpca=030-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
       030-003-*     ls09clli    yes no  --------------   --------------  SS7
    
       SPCA         NCAI         RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
       -----------  no           5      on      20     no     no    xudt2udt
    
    DESTINATION ENTRIES ALLOCATED:   2000
        FULL DPC(s):                   20
        EXCEPTION DPC(s):               0
        NETWORK DPC(s):                 0
        CLUSTER DPC(s):                 2
        TOTAL DPC(s):                  22
        CAPACITY (% FULL):             1%
    ALIASES ALLOCATED:               8000
        ALIASES USED:                  28
        CAPACITY (% FULL):             1%
    X-LIST ENTRIES ALLOCATED:         500
    RTRV-DSTN: MASP A - COMPLTD
    
  12. 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-26 Changing the Attributes of a Cluster Point Code



Sheet 1 of 4



Sheet 2 of 4



Sheet 3 of 4



Sheet 4 of 4