Removing Gateway Screening Stop Action Sets

This procedure is used to remove a gateway screening stop action set from the database or a gateway screening stop action from a gateway screening stop action set from the database using the chg-gws-actset command.

The database can contain a maximum of 16 gateway screening stop action sets, with each set containing a maximum of 10 gateway screening stop actions. Five gateway screening stop actions have been defined.

The chg-gws-actset command uses these parameters in this procedure.

:actid – The ID number of the gateway screening stop action set. The value of this parameter is from 4 to 16.

:force – The force=yes parameter must be specified when changing the gateway screening stop actions of an existing gateway screening stop action set.

:all=none – Sets the value of each gateway screening stop action in the gateway screening stop action set to none.

:act1 to :act10 – One of ten gateway screening stop actions being removed from the gateway screening stop action set.

The first three gateway screening stop action sets (actid=1, actid=2, and actid=3) cannot be changed or removed.

No other optional parameters can be specified all=none parameter.

The force=yes parameter must be specified when changing an existing gateway screening stop action set.

1. Display the gateway screening stop action sets in the database with the rtrv-gws-actset command.

   This is an example of the possible output.

   rlghncxa03w 06-10-25 15:27:30 GMT EAGLE5 36.0.0
   ACT  ACT    ACT  ACT  ACT  ACT  ACT  ACT  ACT  ACT  ACT  ACT
   ID   NAME   1    2    3    4    5    6    7    8    9    10
   --   ------ ---- ---- ---- ---- ---- ---- ---- ---- ---- ----
   1    copy   copy
   2    rdct   rdct
   3    cr     copy rdct
   4    cncf   cncf
   5    cpnf   copy cncf
   6    cfrd   copy cncf rdct
   7    cnrd   cncf rdct
   8    tlnp   tlnp
   9    tlcp   copy tlnp
   
   GWS action set table is (9 of 16) 56% full

2. Either remove a gateway screening stop action set from the database or remove a gateway screening stop action from a gateway screening stop action set from the database by entering the chg-gws-actset command.

   If you wish to remove the gateway screening stop actions from an existing gateway screening stop action set (stop action sets 4 through 16), enter the chg-gws-actset command with the all=none, actid, and force=yes parameters, as shown in this command example.

   chg-gws-actset:actid=4:all=none:force=yes

   If you wish to remove individual gateway screening stop actions from an existing gateway screening stop action set (stop action sets 4 through 16), enter the chg-gws-actset command with the stop action parameter (act1 through act10) value equal to none and the force=yes parameter, as shown in this command example.

   chg-gws-actset:actid=5:act2=none:force=yes

   Caution:

   Caution must be used when changing the stop actions in existing gateway screening stop action sets because these gateway screening stop action sets may be used by one or more gateway screening rules. Changes in the existing gateway screening stop action sets will change how MSUs that pass gateway screening are processed.

   When each of these commands have successfully completed, this message should appear.

   rlghncxa03w 06-10-25 15:30:30 GMT EAGLE5 36.0.0
   CAUTION: GWS action set may be referenced by one or more GWS rules
   CHG-GWS-ACTSET: MASP A - COMPLTD

3. Verify the changes using the rtrv-gws-actset command.

   This is an example of the possible output.

   rlghncxa03w 06-10-25 15:31:30 GMT EAGLE5 36.0.0
   ACT  ACT    ACT  ACT  ACT  ACT  ACT  ACT  ACT  ACT  ACT  ACT
   ID   NAME   1    2    3    4    5    6    7    8    9    10
   --   ------ ---- ---- ---- ---- ---- ---- ---- ---- ---- ----
   1    copy   copy      
   2    rdct   rdct      
   3    cr     copy rdct 
   4    ----   ----      
   5    cpcncf copy  
   6    cncfrd cncf rdct 
   7    cpcfrd copy cncf rdct
   8    tlnp   tlnp
   9    cpnp   copy tlnp
   
   GWS action set table is (8 of 16) 50% full

4. Backup 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-27 Remove Gateway Screening Stop Action Sets