Removing an Association from an Application Server

This procedure is used remove an association from an application server using the dlt-as command.

The dlt-as command uses these parameters:

:asname – The application server name containing the association being removed in this procedure.

:aname – The name of the association being removed from the application server.

The association name and application server name combination must be in the database.

The open parameter value in the association assigned to the application server specified in the dlt-as command must be no. This can be verified with the rtrv-assoc command. Use the chg-assoc command to change the value of the open parameter.

If the association is the only association assigned to the application server, the application server is removed from the database. The application server cannot be removed from the database if it is assigned to a routing key. This can be verified with the rtrv-appl-rtkey command.

Canceling the RTRV-AS, RTRV-ASSOC, and RTRV-APPL-RTKEY Commands

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

  • Press the F9 function key on the keyboard at the terminal where the rtrv-as, rtrv-assoc, or rtrv-appl-rtkey commands were entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-as, rtrv-assoc, or rtrv-appl-rtkey commands were entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-as, rtrv-assoc, or rtrv-appl-rtkey commands were entered, from another terminal other that the terminal where the rtrv-as, rtrv-assoc, or rtrv-appl-rtkey 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 Manual User's Guide.

  1. 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 (3 of 250) 1% full.
    
  2. Display the associations to be removed from the application server 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.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
          as1
    
    IP Appl Sock table is (4 of 4000) 1% full
    Assoc Buffer Space Used (16 KB of 800 KB) on LOC = 1203
    
  3. Change the value of the open parameter to no by specifying the chg-assoc command with the open=no parameter.

    Note:

    If the value of theopen parameter shown in2isno, continue the procedure with4.

    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;
    
  4. If the association is the only association assigned to the application server, the application server is removed from the database.

    Note:

    If the application server specified in this procedure contains more than one association, continue this procedure with 5.

    The application server cannot be removed from the database if it is assigned to a routing key. Verify the routing keys that the application server is assigned to by entering the rtrv-appl-rtkey command with the application server name that will be specified in 5 and the display=all parameter. For this example, enter this command.

    rtrv-appl-rtkey:asname=as1:display=all

    
    rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
    
    RCONTEXT   DPCI          SI SSN OPCI           CICS       CICE       LOC
    ----------   6-024-7      5 ---   1-057-4      150        175        STATIC
    
        ADPTR  TYPE      ASNAME             
        M3UA   FULL      as1    
                                             
            ANAMES
            assoc1           assoc2           assoc3           assoc5
            assoc6
    
    RCONTEXT   DPCI          SI SSN OPCI           CICS       CICE       LOC
    ----------   2-100-7      6 --- -----------    ---------- ---------- STATIC
    
        ADPTR  TYPE      ASNAME             
        M3UA   FULL      as1    
                                             
            ANAMES
            assoc1           assoc2           assoc3           assoc5
            assoc6
    
    STATIC Route Key table is (7 of 2000) 1% full
    STATIC Route Key Socket Association table is (7 of 32000) 1% full
    

    If the application server is assigned to any routing keys, remove the routing keys referencing the application server by performing the Removing a Routing Key Containing an Application Server procedure.

  5. Remove the association from the application server from the database using the dlt-as command.

    For this example, enter this command.

    dlt-as:asname=as1:aname=assoc1

    Note:

    If the association being removed from the application server is the only association assigned to the application server, the application server is removed from the database.
    This is an example of possible inputs and outputs:
    
    rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
    DLT-AS:  MASP A - COMPLTD;
    
  6. Verify the changes using the rtrv-as command with the application server name specified in 5.

    For this example, enter this command.

    rtrv-as:asname=as1

    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      assoc2
                                          assoc3
                                          assoc5
                                          assoc6
    
    AS table is (3 of 250) 1% full.
    
  7. Change the value of the open parameter to yes by specifying the chg-assoc command with the open=yes parameter.

    Note:

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

    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;
    
  8. 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-32 Removing an Association from an Application Server



Sheet 1 of 2



Sheet 2 of 2