Changing the Routing Context Value in an Existing Routing Key

This procedure is used to change the routing context value in an existing routing key using the chg-appl-rtkey command.

The routing key being changed in this procedure must contain a number for the routing context value. If the routing context value shown for the routing key contains dashes (-), this routing key cannot be used in this procedure. The dashes shows that the routing key does not have a routing context assigned to it.

To assign a routing context value to an existing M3UA routing key, the routing key must be removed by performing the Removing a Routing Key Containing an Application Server procedure, then re-enter the routing key with the routing context value by performing the Adding a Routing Key Containing an Application Server procedure. A routing context value must always be assigned to an SUA routing key.

These parameters are used in this procedure.

:rcontext – The current routing context parameter value, which has two functions:

Provides an index of the application server traffic that the sending ASP is configured or registered to receive.
Identifies the SS7 network context for the message. The routing context parameter implicitly defines the SS7 point code format used, the SS7 network indicator value, and the SCCP protocol type/variant/version used.

:nrcontext – The new routing context parameter value, from 0 to 4294967295. The new routing context value cannot be assigned to other routing keys.

The chg-appl-rtkey command contains other parameters that are not 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.

: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 from 0 to 15, or for selected service indicator values, a text string can be used instead of numbers. Table 4-21 shows the text strings that can be used in place of numbers for the service indicator values.

Table 4-21 Service Indicator Text String Values

Service Indicator Value	Text String	Service Indicator Value	Text String
0	snm	4	tup
1	regtest	5	isup
2	spltst	13	qbicc
3	sccp

:ssn – The subsystem number value that is used to filter incoming MSUs.

:cics - Starting circuit identification code that is used to filter incoming MSUs.

:cice - Ending circuit identification code that is used to filter incoming MSUs.

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

:ncics - New starting circuit identification code that is used to filter incoming MSUs.

:ncice - New ending circuit identification code that is used to filter incoming MSUs.

:split - The circuit identification code value where the specified range of the routing key specified by the cics and cice values is to be split into two entries.

See the Changing the CIC Values in an Existing Routing Key Containing an Application Server procedure for changing a routing key using the ncics, ncice, and split parameters.

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  M3UA   as7              FULL
310           6-006-6     5  SUA    as2              FULL
----------    6-006-7     5  M3UA   as8              FULL
1000          6-006-6     5  SUA    as2              FULL
500           6-006-6     5  SUA    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 and the RCONTEXT value shown in the rtrv-appl-rtkey output in 1 for the routing key being changed. For this example, enter this command.
rtrv-appl-rtkey:rcontext=310: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
310          6-006-6      5 ---   1-002-3      75         100
    ADPTR  TYPE      ASNAME             
    SUA    FULL      as2    
                                         
    ANAMES
    assoc1

STATIC Route Key table is (17 of 2000) 1% full
STATIC Route Key Socket Association table is (17 of 32000) 1% full
```
If the routing context value shown for the routing key is dashes (-), this routing key cannot be used in this procedure. The dashes show that the routing key does not have a routing context assigned to it.

To assign a routing context value to a M3UA routing key that does not have a routing context value, the routing key must be removed by performing the Removing a Routing Key Containing an Application Server procedure. Re-enter the routing key with the routing context value by performing the Adding a Routing Key Containing an Application Server procedure. If you do not wish to assign a routing context value to this routing key, but you wish to change the routing context value in another routing key, repeat this step with another routing key shown in 1. If you do not wish to assign a routing context value to this routing key, and do not wish to change the routing context value in another routing key, this procedure cannot be performed.

If the routing key contains a routing context value, continue the procedure with 3.

Display the association displayed in the rtrv-appl-rtkey output in 2, using the rtrv-assoc command with the association name shown in 2.

rtrv-assoc:aname=assoc1

This is an example of possible output.


rlghncxa03w 09-05-28 09:12:36 GMT EAGLE5 41.0.0
ANAME assoc1
      LOC      1203          IPLNK PORT  A          LINK  A
      ADAPTER  SUA           VER         SUA RFC
      LHOST    gw105.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.nc.tekelec.com
      ARHOST   ---
      LPORT    1030          RPORT       1030
      ISTRMS   2             OSTRMS      2          BUFSIZE  16
      RMODE    LIN           RMIN        120        RMAX     800
      RTIMES   10            CWMIN       3000       UAPS     10
      OPEN     YES           ALW         YES        RTXTHR   10000
      RHOSTVAL RELAXED

      ASNAMES
      as2

IP Appl Sock table is (4 of 4000) 1% full
Assoc Buffer Space Used (16 KB of 800 KB) on LOC = 1203

Repeat this step for each association name displayed in 2.

Note:

If theopen parameter value for all the associations assigned to the application server isno (shown in3), continue the procedure with5.

Change the value of the open parameter to no by specifying the chg-assoc command with the open=no parameter. For this example, enter this command.
chg-assoc:aname=assoc1:open=no

When this command has successfully completed, this message should appear.
```
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
CHG-ASSOC: MASP A - COMPLTD;
```
Caution:
TheIP connections using the associations specified in this step will not be able to carry any traffic when theopen parameter is changed tono.

Repeat this step for all the associations assigned to the application server that have the open=yes parameter value.
Change the routing key information to the database by entering the chg-appl-rtkey command with the current and new routing context values. For this example, enter this command.
chg-appl-rtkey:nrcontext=5280:rcontext=310

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 new routing context value specified in 5 and the display=all parameter. For this example, enter this command.

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

This is an example of the possible output.


rlghncxa03w 08-04-28 21:15:37 GMT EAGLE5 38.0.0
RCONTEXT   DPCI          SI SSN OPCI           CICS       CICE
5280         6-006-6      5 ---   1-002-3      75         100
    ADPTR  TYPE      ASNAME             
    SUA    FULL      as2    
                                         
    ANAMES
    assoc1

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

Note:

If4was not performed in this procedure, continue the procedure with8.

Change the value of the open parameter of the associations that were changed in 4 to yes by specifying the chg-assoc command with the open=yes parameter. For this example, enter this command.
chg-assoc:aname=assoc1:open=yes

When this command has successfully completed, this message should appear.
```
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
CHG-ASSOC: MASP A - COMPLTD;
```
Repeat this step for all the associations that were changed in 4.

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-42 Changing the Routing Context Value in an Existing Routing Key

Sheet 1 of 2

Sheet 2 of 2