Adding a Screen Set

This procedure is used to add a screen set to the database using the ent-scrset command. The parameters used by the ent-scrset command are shown in the Gateway Screening Attributes section. The general rules that apply to configuring gateway screening entities are shown in the Gateway Screening Configuration section.

A maximum of 255 screen sets can be configured in the database. If the database contains 255 screen sets, any attempt to add another screen set with the ent-scrset command will be rejected. If the database contains 255 screen sets, and you wish to add another screen set, a current screen set must be removed or changed. To remove a screen set, perform the Removing a Screen Set procedure. To change an existing screen set, perform the Changing a Screen Set procedure.

The examples in this procedure are used to add the screen set data shown in Table 13-1 and based on the example configurations shown in Figure 2-3 through Figure 2-9.

Table 13-1 Example Gateway Screening Screen Set Configuration Table

Screen Set Name	Next Screening Function Identifier	Next Screening Reference	DESTFLD
gws1	opc	gws4	No
gws2	blkopc	gws5	No
ls01	sio	ls02	Yes
wrd1	dpc	iec	Yes
fld1	opc	fld2	No
isp1	opc	isp1	No
tup1	opc	tup1	No

The screen set can reference one of the following screens.

• Allowed OPC
• Blocked OPC
• Allowed SIO
• Allowed DPC
• Blocked DPC

Verifying the Gateway Screening Configuration

Enter the following commands to verify that these screens are in the database.

• rtrv-scr-opc:all=yes
• rtrv-scr-blkopc:all=yes
• rtrv-scr-sio:all=yes
• rtrv-scr-dpc:all=yes
• rtrv-scr-blkdpc:all=yes

Gateway Screening Configuration Procedures

If the desired screen is not in the database, perform one of these procedures to add the desired screen to the database or change an existing screen in the database.

• Adding an Allowed OPC Screen
• Adding a Blocked OPC Screen
• Adding an Allowed SIO Screen
• Adding an Allowed DPC Screen
• Adding a Blocked DPC Screen
• Changing an Allowed OPC Screen
• Changing a Blocked OPC Screen
• Changing an Allowed SIO Screen
• Changing an Allowed DPC Screen
• Changing a Blocked DPC Screen

1. Verify that the gateway screening feature is on, by entering the rtrv-feat command.

   If the gateway screening feature is on, the GWS field is set to on.

   Note:

   The rtrv-feat command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by the rtrv-feat command, see the rtrv-feat command description in Commands User's Guide.

   If the gateway screening feature is on, shown by the entry GWS = on in the rtrv-feat command output, skip step 2, and go to step 3.

2. Turn the gateway screening feature on by entering this command.

   chg-feat:gws=on

   Note:

   Once the gateway screening feature is turned on with the chg-feat command, it cannot be turned off.

   The gateway screening feature must be purchased before you turn this feature on with the chg-feat command. If you are not sure if you have purchased the gateway screening feature, contact your Oracle Sales Representative or Account Representative.

   When the chg-feat has successfully completed, this message should appear.

   rlghncxa03w 06-10-28 11:43:04 GMT EAGLE5 36.0.0
   CHG-FEAT: MASP A - COMPLTD

3. Display all the screen sets in the database using the rtrv-scrset command.

   The following is an example of the possible output.

   rlghncxa03w 06-10-25 15:25:30 GMT EAGLE5 36.0.0
   ENTIRE GWS DATABASE IS 1% FULL
   CDPA + AFTPC TABLES ARE 1% FULL
   THERE ARE 248 SCREEN SETS AVAILABLE
   
   THE FOLLOWING ARE OVER 80% FULL:
   SCRN  NSFI    NSR/ACT  FULL  RULES  TABLES  DESTFLD
   
   SCRN  NSFI    NSR/ACT  FULL  RULES  TABLES  DESTFLD
   ss01  OPC     opc1      51%  2075   22      YES
   ss02  OPC     opc2       2%    75   22      YES
   ss03  OPC     opc3       2%    75   22      YES
   ss04  OPC     opc1      51%  2075   22      NO
   ss07  OPC     opc1      51%  2075   22      YES
   ss09  OPC     opc1      51%  2075   22      NO
   ss28  OPC     opc1      51%  2075   22      YES

   If a gateway screening stop action set is to be assigned to the screen set being added to the database, go to step 4.

   Step 4 verifies the gateway screening stop action set names in the database. The gateway screening stop action set names are assigned only if the NSFI of the screen set being added in this procedure is STOP. If the NSFI of the new screen set will be STOP, but a gateway screening stop action set name will not be assigned to the new screen set, skip steps 4 and 5 and go to step 6. If the NSFI of the new screen set is not STOP, skip step 4 and go to step 5.

4. 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:26: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    cpcncf copy cncf 
   6    cncfrd cncf rdct 
   7    cpcfrd copy cncf rdct
   GWS action set table is (7 of 16) 44% full

   If the required gateway screening stop action set is not in the database, perform the Configuring Gateway Screening Stop Action Sets procedure to configure the required gateway screening stop action set.

   Note:

   If the NSFI of the screen set being added in this procedure is STOP, skip step 5 and go to step 6.
5. Enter the commands in the Verifying the Gateway Screening Configuration section to verify that the screen that will be specified by the NSFI/NSR parameter combination in step 6 is in the database.

   If the desired screen is not in the database, perform one of the procedures shown in the Gateway Screening Configuration Procedures section to add the desired screen to the database or change an existing screen in the database.

6. Add a new screen set to the database using the ent-scrset command.

   If a gateway screening stop action is to be assigned to the screen set being added, enter the ent-scrset command with the nsfi=stop parameter and the actname parameter with the name of a gateway screening stop action set shown in the output of the rtrv-gws-actset command executed in step 4.

   For this example, enter these commands.

   ent-scrset:scrn=gws1:nsfi=opc:nsr=gws4:destfld=no

   A message similar to the following should appear.

   rlghncxa03w 06-10-25 15:27:30 GMT EAGLE5 36.0.0
   ENT-SCRSET: SCREEN SET AFFECTED - GWS1  1% FULL
   ENT-SCRSET: MASP A - COMPLTD

   ent-scrset:scrn=gws2:nsfi=blkopc:nsr=gws5:destfld=no

   A message similar to the following should appear.

   rlghncxa03w 06-10-25 15:28:30 GMT EAGLE5 36.0.0
   ENT-SCRSET: SCREEN SET AFFECTED - GWS2  1% FULL
   ENT-SCRSET: MASP A - COMPLTD

   ent-scrset:scrn=ls01:nsfi=sio:nsr=ls02:destfld=yes

   A message similar to the following should appear.

   rlghncxa03w 06-10-25 15:29:30 GMT EAGLE5 36.0.0
   ENT-SCRSET: SCREEN SET AFFECTED - LS01  1% FULL
   ENT-SCRSET: MASP A - COMPLTD

   ent-scrset:scrn=wrd1:nsfi=dpc:nsr=iec:destfld=yes

   A message similar to the following should appear.

   rlghncxa03w 06-10-25 15:30:30 GMT EAGLE5 36.0.0
   ENT-SCRSET: SCREEN SET AFFECTED - WRD1  1% FULL
   ENT-SCRSET: MASP A - COMPLTD

   ent-scrset:scrn=fld1:nsfi=opc:nsr=fld2:destfld=no

   A message similar to the following should appear.

   rlghncxa03w 06-10-25 15:31:30 GMT EAGLE5 36.0.0
   ENT-SCRSET: SCREEN SET AFFECTED - FLD1  1% FULL
   ENT-SCRSET: MASP A - COMPLTD

   ent-scrset:scrn=isp1:nsfi=opc:nsr=isp1:destfld=no

   A message similar to the following should appear.

   rlghncxa03w 06-10-25 15:31:30 GMT EAGLE5 36.0.0
   ENT-SCRSET: SCREEN SET AFFECTED - ISP1  1% FULL
   ENT-SCRSET: MASP A - COMPLTD

   ent-scrset:scrn=tup1:nsfi=opc:nsr=tup1:destfld=no

   A message similar to the following should appear.

   rlghncxa03w 06-10-25 15:31:30 GMT EAGLE5 36.0.0
   ENT-SCRSET: SCREEN SET AFFECTED - TUP1  1% FULL
   ENT-SCRSET: MASP A - COMPLTD

7. Verify the changes using the rtrv-scrset command.

   The following is an example of the possible output.

   rlghncxa03w 06-10-25 15:32:30 GMT EAGLE5 36.0.0
   ENTIRE GWS DATABASE IS 1% FULL
   CDPA + AFTPC TABLES ARE 1% FULL
   THERE ARE 242 SCREEN SETS AVAILABLE
   
   THE FOLLOWING ARE OVER 80% FULL:
   SCRN  NSFI    NSR/ACT  FULL  RULES  TABLES  DESTFLD
   
   SCRN  NSFI    NSR/ACT  FULL  RULES  TABLES  DESTFLD
   fld1  OPC     fld2       1%     5   4       NO
   gws1  OPC     gws4       1%     9   7       NO
   gws2  BLKOPC  gws5       1%     5   4       NO
   isp1  OPC     isp1       1%     6   4       NO
   ls01  SIO     ls02       1%     3   3       YES
   ss01  OPC     opc1      51%  2075   22      YES
   ss02  OPC     opc2       2%    75   22      YES
   ss03  OPC     opc3       2%    75   22      YES
   ss04  OPC     opc1      51%  2075   22      NO
   ss07  OPC     opc1      51%  2075   22      YES
   ss09  OPC     opc1      51%  2075   22      NO
   ss28  OPC     opc1      51%  2075   22      YES
   tup1  OPC     tup1       1%     8   5       NO
   wrd1  DPC     iec        1%     6   5       YES

8. Backup the new changes using the chg-db:action=backup:dest=fixed command.

   The following 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 13-1 Add a Screen Set - Sheet 1 of 3

Figure 13-2 Add a Screen Set - Sheet 2 of 3

Figure 13-3 Add a Screen Set - Sheet 2 of 3