Changing an Application Server

This procedure is used change the characteristics of an existing application server using the chg-as command.

The chg-as command uses these parameters:

:asname – The name of the application server being changed.

:mode – The traffic mode assigned to the application server, either loadshare or override.

:tr – The application server recovery timer, 10 - 2000 milliseconds.

The mode parameter value cannot be changed unless the open parameter value of the all the associations assigned to the application server is set to no. This can be verified with the rtrv-assoc command.

The association assignments for an application server cannot be changed with this procedure. To change an association assignment for an application server, go to the Removing an Association from an Application Server procedure and remove the association from the application server, then perform one of these procedures to add another association to the application server:

Canceling the RTRV-AS and RTRV-ASSOC Commands

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

Press the F9 function key on the keyboard at the terminal where the rtrv-as or rtrv-assoc commands were entered.
Enter the canc-cmd without the trm parameter at the terminal where the rtrv-as or rtrv-assoc commands were entered.
Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-as or rtrv-assoc commands were entered, from another terminal other that the terminal where the rtrv-as or rtrv-assoc commands were 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 application servers in the database using the rtrv-as command.

This is an example of possible output.


rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0

AS Name           Mode        Tr ms   Association Names
as1               LOADSHARE   10      assoc1
                                      assoc2
                                      assoc3
                                      assoc5
                                      assoc6

as2               OVERRIDE    10      assoc7
as3               LOADSHARE   10      assoc4

AS table is (2 of 250) 1% full.

Note:

If themode parameter will not be specified with thechg-as command in5, continue the procedure with5.

Display one of the associations assigned to the application server shown in 1 using the rtrv-assoc command and specifying the association name shown in the rtrv-as output in 1.

For this example, enter this command.

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  M3UA          VER         M3UA RFC
      LHOST    gw105.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.ncd-economic-development.southeastern-corridor-ash.gov
      ARHOST   ---
      LPORT    1030          RPORT       2345
      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
      as1

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

Note:

If the value of theopen parameter shown in this step isno, 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
```
Note:
If all the associations assigned to the application server been displayed, continue the procedure with5.
Repeat 2 and 3 for all associations assigned to the application server being changed.
Change the application server in the database using the chg-as command.
For this example, enter this command
chg-as:asname=as1:mode=override:tr=1000

This is an example of possible inputs and outputs:
```
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
CHG-AS:  MASP A - COMPLTD;
```

Verify the changes using the rtrv-as command.

This is an example of possible output.


rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0

AS Name           Mode        Tr ms   Association Names
as1               OVERRIDE    1000    assoc1
                                      assoc2
                                      assoc3
                                      assoc5
                                      assoc6

as2               OVERRIDE    10      assoc7
as3               LOADSHARE   10      assoc4

AS table is (2 of 250) 1% full

Note:

If the value of theopen parameter was not changed in3, continue the procedure with8.

Change the value of the open parameter 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 associations that were changed in 3.

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-40 Changing an Application Server

Sheet 1 of 2

Sheet 2 of 2