Changing the CIC Values in an Existing Routing Key Containing an Application Server

This procedure is used to change the CIC values in an existing routing key using the chg-appl-rtkey command. These parameters are used in this procedure.

:dpc/dpca/dpci/dpcn/dpcn24 – Destination point code value that is used to filter incoming MSUs.

:opc/opca/opci/opcn/opcn24 - The originating point code value that is used to filter incoming MSUs. This value must not specify a cluster route.

Note:

See the “Point Code Formats” section in the Database Administration - SS7 User's Guide for a definition of the point code types that are used on the EAGLE and for a definition of the different formats that can be used for ITU national point codes.

:si – The service indicator value that is used to filter incoming MSUs. The range of values for the service indicator parameter (si) can be a numerical value either 4, 5, or 13, or for selected service indicator values, a text string can be used instead of numbers. Table 4-18 shows the text strings that can be used in place of numbers for the service indicator values.

Table 4-18 Service Indicator Text String Values

Service Indicator Value	Text String
4	tup
5	isup
13	qbicc

:cics - Starting circuit identification code that is used to filter incoming MSUs. Specify with cice to identify the routing key to be changed.

:cice - Ending circuit identification code that is used to filter incoming MSUs. Specify with cics to identify the routing key to be changed.

:ncics - New starting circuit identification code that is used to filter incoming MSUs. Specify the ncics parameter and/or the ncice parameter to change the range of circuit identification codes assigned to the routing key.

:ncice - New ending circuit identification code that is used to filter incoming MSUs. Specify the ncice parameter and/or the ncics parameter to change the range of circuit identification codes assigned to the routing key.

:split - The circuit identification code value where the specified range of CIC values for the routing key specified by the cics and cice values is to be split into two routing keys. The CIC values in one routing key ranges from the cics value of the original routing key to a value equal to one less than the split value. The CIC values in the other routing key ranges from the split value to the cice value of the original routing key. All other parameters in both routing keys remain the same as in the original routing key. The range of CIC values cannot be split if the routing key contains a routing context parameter value.

:type - Key type. Identifies the type of routing key that will be changed. One of three values, type=full/partial/default. If type is not explicitly specified, type=full is assumed. Only the type=full parameter can be used in this procedure.

:rcontext – The routing context parameter value assigned to the routing key.

The chg-appl-rtkey command contains other parameters that are not used in this procedure.

:ssn – The subsystem number value that is used to filter incoming MSUs. See the Adding a Routing Key Containing an Application Server procedure for more information on using the ssn parameter with a routing key.

:nrcontext – The new routing context parameter value.

See the Changing the Routing Context Value in an Existing Routing Key procedure for changing the routing context parameter value in an existing routing key.

Rules for Changing the Range of CIC Values in an Existing Routing Key

The parameter combinations used by the chg-appl-rtkey command to change the range of CIC values in the routing key are shown in Table 4-19.

Table 4-19 Routing Key Parameter Combinations for Changing the Range of CIC Values in an Existing Routing Key

SI=4 (TUP)	SI=5 (ISUP)		SI=13 (QBICC)
dpci/dpcn/dpcn24=<the DPC assigned to the routing key> (See Note 1)	dpc/dpca=<the DPC assigned to the routing key> (See Note 1)	dpci/dpcn/dpcn24=<the DPC assigned to the routing key> (See Note 1)	dpc/dpca/dpci/ dpcn/dpcn24=<the DPC assigned to the routing key> (See Note 1)
si=4 (See Note 1)	si=5 (See Note 1)	si=5 (See Note 1)	si=13 (See Note 1)
opci/opcn/opcn24=<the OPC assigned to the routing key> (See Note 1)	opc/opca=<the OPC assigned to the routing key> (See Note 1)	opci/opcn/opcn24=<the OPC assigned to the routing key> (See Note 1)	opc/opca/opci/ opcn/opcn24=<the OPC assigned to the routing key> (See Note 1)
cics=<the CICS value assigned to the routing key> (See Notes 1 and 2)	cics=<the CICS value assigned to the routing key>^1, 2	cics=<the CICS value assigned to the routing key> (See Notes 1 and 2)	cics=<the CICS value assigned to the routing key> (See Notes 1 and 2)
cice=<the CICE value assigned to the routing key> (See Notes 1 and 2)	cice=<the CICE value assigned to the routing key> (See Notes 1 and 2)	cice=<the CICE value assigned to the routing key> (See Notes 1 and 2)	cice=<the CICE value assigned to the routing key> (See Notes 1 and 2)
type=full	type=full	type=full	type=full
ncics=<0 to 4095> (See Notes 2 and 3)	ncics=<0 to 16383> (See Notes 2 and 3)	ncics=<0 to 4095> (See Notes 2 and 3)	ncics=<0 to 4294967295> (See Notes 2 and 3)
ncice=<0 to 4095> (See Notes 2 and 3)	ncice=<0 to 16383> (See Notes 2 and 3)	ncice=<0 to 4095> (See Notes 2 and 3)	ncice=<0 to 4294967295> (See Notes 2 and 3)
rcontext=<the current routing context value assigned to the routing key> (See Notes 4 and 5)	rcontext=<the current routing context value assigned to the routing key> (See Notes 4 and 5)	rcontext=<the current routing context value assigned to the routing key> (See Notes 4 and 5)	rcontext=<the current routing context value assigned to the routing key> (See Notes 4 and 5)
1. The values for these parameters must be entered exactly as shown in the `rtrv-appl-rtkey` command output for the routing key being changed. However, text strings can be used in place of some numerical service indicator values. See Table 4-18 for a list of these text strings. The text string must correspond to the numerical value shown in the routing key being changed. 2. The `cics` and `cice` parameters must be specified and either the `ncics` or `ncice` parameters, or both, must be specified. If both the `ncics` and `ncice` parameters are specified, the value of the `ncics` parameter must be less than the value of the `ncice` parameter. If the `ncics` parameter is not specified, the value of the `ncice` parameter must be greater than or equal to the `cics` parameter value. If the `ncice` parameter is not specified, the value of the `ncics` parameter must be less than or equal to the `cice` parameter value. 3. The new CIC range cannot overlap the CIC range in an existing routing key. 4. If the routing key contains a numerical value in the `RCONTEXT` column in the `rtrv-appl-rtkey` output, the `rcontext` parameter and value can be used in place of the `dpc`, `si`, `opc`, `cics`, `cice`, or `type=full` parameters and values to identify the routing that is being changed with the `chg-appl-rtkey` command. However, if only the `rcontext` parameter is used to identify the routing key being changed, only one of these parameters, `ncics` or `ncice` can be specified with the `chg-appl-rtkey` parameter. If you wish to specify the `ncics` and `ncice` parameters with the `chg-appl-rtkey` parameter, the `dpc`, `si`, `opc`, `cics`, `cice`, or `type=full` parameters and values must be specified with the `chg-appl-rtkey` command. 5. If the routing key contains dashes in the `RCONTEXT` column in the `rtrv-appl-rtkey` output, the `dpc`, `si`, `opc`, `cics`, `cice`, or `type` parameters and values must be used with the `chg-appl-rtkey` command to identify the routing key being changed.

Rules for Splitting the Range of CIC Values in an Existing Routing Key

The parameter combinations used by the chg-appl-rtkey command to split the range of CIC values in the routing key are shown in Table 4-20.

Splitting the range of CIC values creates two routing keys. The CIC values in one routing key ranges from the cics value of the original routing key to a value equal to one less than the split value. The CIC values in the other routing key ranges from the split value to the cice value of the original routing key. All other parameters in both routing keys remain the same as in the original routing key. The range of CIC values cannot be split if the routing key contains a routing context parameter value.

Table 4-20 Routing Key Parameter Combinations for Splitting the Range of CIC Values in an Existing Routing Key

SI=4 (TUP)	SI=5 (ISUP)		SI=13 (QBICC)
dpci/dpcn/dpcn24=<the DPC assigned to the routing key> (See Note 1)	dpc/dpca=<the DPC assigned to the routing key> (See Note 1)	dpci/dpcn/dpcn24=<the DPC assigned to the routing key> (See Note 1)	dpc/dpca/dpci/ dpcn/dpcn24=<the DPC assigned to the routing key> (See Note 1)
si=4 (See Note 1)	si=5 (See Note 1)	si=5 (See Note 1)	si=13 (See Note 1)
opci/opcn/opcn24=<the OPC assigned to the routing key> (See Note 1)	opc/opca=<the OPC assigned to the routing key> (See Note 1)	opci/opcn/opcn24=<the OPC assigned to the routing key> (See Note 1)	opc/opca/opci/ opcn/opcn24=<the OPC assigned to the routing key> (See Note 1)
cics=<the CICS value assigned to the routing key> (See Note 1)	cics=<the CICS value assigned to the routing key> (See Note 1)	cics=<the CICS value assigned to the routing key> (See Note 1)	cics=<the CICS value assigned to the routing key> (See Note 1)
cice=<the CICE value assigned to the routing key> (See Note 1)	cice=<the CICE value assigned to the routing key> (See Note 1)	cice=<the CICE value assigned to the routing key> (See Note 1)	cice=<the CICE value assigned to the routing key> (See Note 1)
type=full	type=full	type=full	type=full
split=<0 to 4095> (See Note 2)	split=<0 to 16383> (See Note 2)	split=<0 to 4095> (See Note 2)	split=<0 to 4294967295> (See Note 2)
1. The values for these parameters must be entered exactly as shown in the `rtrv-appl-rtkey` command output for the routing key being changed. However, text strings can be used in place of some numerical service indicator values. See Table 4-18 for a list of these text strings. The text string must correspond to the numerical value shown in the routing key being changed. 2. The `split` parameter value must be greater than the `cics` parameter value and less than the `cice` parameter value.

Canceling the RTRV-APPL-RTKEY Command

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

Press the F9 function key on the keyboard at the terminal where the rtrv-appl-rtkey command was entered.
Enter the canc-cmd without the trm parameter at the terminal where the rtrv-appl-rtkey command was entered.
Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-appl-rtkey command was entered, from another terminal other that the terminal where the rtrv-appl-rtkey 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.

Display the current routing key information in the database by entering the rtrv-appl-rtkey command.

The following is an example of the possible output.


rlghncxa03w 08-04-28 21:15:37 GMT EAGLE5 38.0.0

RCONTEXT    DPC          SI  ADPTR  ASNAME           TYPE
----------  123-234-123   5  M3UA   as12             FULL
----------  005-005-001   5  M3UA   as9              FULL
----------  005-005-001   5  M3UA   as9              FULL
2500        006-006-001   5  SUA    as10             FULL

RCONTEXT    DPCI         SI  ADPTR  ASNAME           TYPE
----------    2-100-7     6  M3UA   as4              FULL
100           3-137-6     6  SUA    as1              FULL
225           4-035-7     5  SUA    as7              FULL
----------    6-006-6     5  M3UA   as2              FULL
----------    6-006-7     5  M3UA   as8              FULL
----------    6-006-6     5  M3UA   as2              FULL
----------    6-006-6     5  M3UA   as2              FULL
----------    6-006-8     3  M3UA   as3              FULL
----------    6-006-8     5  M3UA   as5              FULL
----------    6-024-7     5  M3UA   as4              FULL
----------    6-024-7     5  M3UA   as4              FULL
300           7-008-7     6  SUA    as6              FULL

RCONTEXT    DPC          SI  ADPTR  ASNAME           TYPE
----------  ***********  **  M3UA   as11             DEFAULT

STATIC Route Key table is (17 of 2000) 1% full
STATIC Route Key Socket Association table is (17 of 32000) 1% full

Display the specific routing key information for the routing key being changed by entering the rtrv-appl-rtkey command with the display=all parameter.
If the routing key being changed contains a routing context value, specify the rcontext parameter and value shown in the rtrv-appl-rtkey output in 1 for the routing key being changed.

If the routing key being changed does not contain a routing context value, specify the DPC, SI, and TYPE values shown in the rtrv-appl-rtkey output in 1 for the routing key being changed. The service indicator value for the routing key to be used in this procedure is either 4, 5, or 13.

For this example, enter these commands.

rtrv-appl-rtkey:dpc=123-234-123:si=5:type=full:display=all

This is an example of the possible output.
```
rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0

RCONTEXT   DPC           SI SSN OPC            CICS       CICE
---------  123-234-123    5 --- 122-124-125    1          1000

    ADPTR  TYPE      ASNAME 
    M3UA   FULL      as12

    ANAMES
    assoc20

STATIC Route Key table is (17 of 2000) 1% full
STATIC Route Key Socket Association table is (17 of 32000) 1% full
```
rtrv-appl-rtkey:rcontext=225:display=all

This is an example of the possible output.
```
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0
RCONTEXT   DPCI          SI SSN OPCI           CICS       CICE
225          4-035-7      5 ---   2-007-3      2000       3000

    ADPTR  TYPE      ASNAME             
    M3UA   FULL      as7    
                                         
    ANAMES
    assoc15

STATIC Route Key table is (17 of 2000) 1% full
STATIC Route Key Socket Association table is (17 of 32000) 1% full
```
Change the CIC values of the routing key by entering the chg-appl-rtkey command.
The parameters required for the chg-appl-rtkey command are determined by the type of change being made to the routing key. Go to one of these sections to determine the required parameter combination.
- Rules for Changing the Range of CIC Values in an Existing Routing Key
- Rules for Splitting the Range of CIC Values in an Existing Routing Key
To change the range of CIC values for this example, enter these commands.

chg-appl-rtkey:dpca=123-234-123:si=5:opca=122-124-125:cics=1:cice=1000:ncice=2000

chg-appl-rtkey:dpci=4-035-7:si=5:opci=2-007-3:cics=2000:cice=3000:ncice=4000

If a routing context value is assigned to the routing key, the rcontext parameter and value assigned to the routing key can be used to identify the routing key being changed instead of the dpc, si, opc, cics, and cice parameters. If the rcontext parameter is specified only one of these parameters, ncics or ncice, can be specified with the chg-appl-rtkey parameter.

For this example, enter this command.

chg-appl-rtkey:rcontext=225:ncice=4000

To split the range of CIC values for this example, enter this command.

chg-appl-rtkey:dpca=123-234-123:si=5:opca=122-124-125:cics=1:cice=1000:split=500

When this command has successfully completed, the following message should appear.
```
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0
CHG-APPL-RTKEY: MASP A - COMPLTD
```

Display the new routing key information in the database by entering the rtrv-appl-rtkey command with the display=all parameter.

If the routing key being changed contains a routing context value, specify the rcontext parameter and value specified in the chg-appl-rtkey command in 3. The DPC, SI, CICS, and CICE parameters and values used in 3 can be specified in the rtrv-appl-rtkey command for routing keys containing routing context values.

If the routing key being changed does not contain a routing context value, specify the DPC, SI, CICS, and CICE parameters and values specified in the chg-appl-rtkey command in 3. If the ncics or ncice parameters were specified in 3, the NCICS or NCICE values specified in 3 must be specified for the cics or cice parameters in this step.

For this example, enter these commands.

rtrv-appl-rtkey:dpca=123-234-123:si=5:cics=1:cice=2000:display=all


rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0

RCONTEXT   DPC           SI SSN OPC            CICS       CICE
---------  123-234-123    5 --- 122-124-125    1          2000

    ADPTR  TYPE      ASNAME 
    M3UA   FULL      as12

    ANAMES
    assoc20

STATIC Route Key table is (17 of 2000) 1% full
STATIC Route Key Socket Association table is (17 of 32000) 1% full

rtrv-appl-rtkey:dpci=4-035-7:si=5:cics=2000:cice=4000 :display=all

rtrv-appl-rtkey:rcontext=225:display=all

This is an example of the possible output.


rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0
RCONTEXT   DPCI          SI SSN OPCI           CICS       CICE
225          4-035-7      5 ---   2-007-3      2000       4000

    ADPTR  TYPE      ASNAME             
    SUA    FULL      as7    
                                         
    ANAMES
    assoc15

STATIC Route Key table is (17 of 2000) 1% full
STATIC Route Key Socket Association table is (17 of 32000) 1% full

rtrv-appl-rtkey:dpca=123-234-123:si=5:cics=1:cice=1000 :display=all


rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0
RCONTEXT   DPC           SI SSN OPC            CICS       CICE
---------- 123-234-123    5 --- 100-100-100    1          499

    ADPTR  TYPE      ASNAME 
    M3UA   FULL      as12

    ANAMES
    assoc20

RCONTEXT   DPC           SI SSN OPC            CICS       CICE
---------- 123-234-123    5 --- 122-124-125    500        1000

    ADPTR  TYPE      ASNAME 
    M3UA   FULL      as12

    ANAMES
    assoc20

STATIC Route Key table is (18 of 2000) 1% full
STATIC Route Key Socket Association table is (18 of 32000) 1% full

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 4-41 Changing the CIC Values in an Existing Routing Key Containing an Application Server

Sheet 1 of 2

Sheet 2 of 2