Blocked Destination Point Code (BLKDPC) Screen Configuration

8 Blocked Destination Point Code (BLKDPC) Screen Configuration

Chapter 8, Blocked Destination Point Code (BLKDPC) Screen Configuration, contains the procedures necessary to configure blocked destination point code screens.

Introduction

The blocked DPC screen identifies DPC's that are not allowed to receive SS7 messages from another network. The gray shaded areas in Figure 8-4 shows the fields of the SS7 message that are checked by the blocked DPC screening function.

Gateway Screening Actions

If a match is found, the nsfi is equal to fail, the message is discarded and no further screening takes place.

If a match is not found, the nsfi is examined to determine the next step in the screening process. If the nsfi value is any value other than stop, the next screening reference (nsr) is identified and the screening process continues to the next screen identified by the nsfi and nsr parameter values.

If the nsfi is equal to stop, the screening process stops and the message is processed. If a gateway screening stop action set is specified with the screen, shown by the actname parameter value, the message is processed according to the gateway screening stop actions that are assigned to the gateway screening stop action set.

If the rdct (redirect) gateway screening stop action is specified,the message is diverted from the original destination and sent to another destination with the Database Transport Access feature, specified by global title translation, for further processing.
If the cncf gateway screening stop action is specified, the PIP parameter in the incoming ISUP IAM message is converted to the GN parameter. The GN parameter in the incoming ISUP IAM message is converted to the PIP parameter. The message is then sent to the node specified by the DPC in the routing label in the message. For more information on the Calling Name Conversion Facility feature, see Calling Name Conversion Facility (CNCF) Configuration.
If the tlnp gateway screening stop action is specified, ISUP IAMs that pass gateway screening are processed either by the ISUP NP with EPAP feature (if the ISUP NP with EPAP feature is enabled and turned on) or by the Triggerless LNP feature (if the Triggerless LNP feature is turned on). The ISUP NP with EPAP feature is discussed in more detail in the Feature Manual - G-Port. The Triggerless LNP feature is discussed in more detail in the ELAP Administration and LNP Feature Activation manual.
If the tinp gateway screening stop action is specified, ISUP IAMs that pass gateway screening are intercepted by the Triggerless ISUP based Number Portability (TINP) feature and converted to include the routing number (RN) if the call is to a ported number. The TINP feature is discussed in more detail in the Feature Manual - G-Port.
If the tif, tif2, or tif3 gateway screening stop actions are specified, TIF processing is applied to the message.
If the sccp gateway screening stop action is specified, MTP routed SCCP UDT/XUDT are forwarded to the service modules for further processing.

Blocked DPC Screening Actions

Figure 8-1 through Figure 8-3 show the screening actions of the blocked DPC screen.

Figure 8-1 Blocked DPC Screening Actions - Sheet 1 of 3

Figure 8-2 Blocked DPC Screening Actions - Sheet 2 of 3

Figure 8-3 Blocked DPC Screening Actions - Sheet 3 of 3

Figure 8-4 Blocked DPC Screening Functions

Adding a Blocked DPC Screen

This procedure is used to add a blocked destination point code (DPC) screen to the database using the ent-scr-blkdpc command. The parameters used by the ent-scr-blkdpc 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.

The examples in this procedure are used to add the blocked DPC screen data shown in Table 8-1 and based on the example configurations shown in Figure 2-3 and Figure 2-5.

Table 8-1 Example Gateway Screening Blocked DPC Configuration Table

Screening Reference	NI	NC	NCM	NSFI	NSR
gws9	C	C	C	cgpa	gw13
gws9	005	005	005	fail	----
gw12	C	C	C	cgpa	gw14
gw12	004	004	004	fail	----

Note:

If you using multiple-part ITU national point codes with gateway screening, see the 14-Bit ITU National Point Code Formats section.

The blocked DPC screen can reference one of the following screens.

Allowed Affected Destination Field
Allowed CGPA
Allowed ISUP

Verifying Gateway Screening Configuration

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

rtrv-scr-destfld:all=yes
rtrv-scr-cgpa:all=yes
rtrv-scr-isup:all=yes

Gateway Screening Configuration Procedures

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

For the first entry for a specific screening reference, the value for the point code must be c, and the NSFI must be either stop or cgpa. If the NSFI is stop, the screening of the message will stop at the specified blocked DPC screen. If the NSFI is cgpa, then any message containing a point code that is not listed in the blocked DPC screen with a NSFI equal to fail, will continue to be screened with the allowed CGPA screen. All subsequent entries for that screening reference must contain a numeric point code value, the NSFI must be equal to fail, and the nsr parameter cannot be specified. Any message that contains a DPC in the blocked DPC screen with the NSFI equal to fail will be rejected from the network and the screening process is stopped.

The pcst parameter, specifying whether or not the ITU-I or 14-bit ITU-N point code is a spare point code, cannot be used with the zone=c or npc=c parameters.

Specifying a Range of Values

A range of values can be specified for the point code parameters ni, nc, or ncm.

If a range of values is specified for any of these parameters, and the value of the other parameters match existing values for the screening reference name, the range of values for the point code parameter cannot include any values for that parameter that are currently provisioned for the screening reference name.

For example, screening reference name scr1 contains these entries:

SR    NI       NC       NCM      NSFI    NSR/ACT
SCR1  C        C        C        CGPA    cg01
SCR1  240      001      010      FAIL    ------
SCR1  241      010      020      FAIL    ------

Another entry for screening reference scr1 with the ni value of 240 and the nc value of 001 cannot be specified if the range of values for the ncm parameter includes the value 010.

The ANSI point code parameter values can be specified as a single value, a range of values, or with an asterisk (*). The asterisk specifies all possible values for the ni, nc, and ncm parameters. Table 8-2 shows the valid combinations of these parameter values.

Table 8-2 Valid Value Combinations for ANSI Point Code Parameters

NI	NC	NCM
Single Value	Single Value	Single Value
Single Value	Single Value	Range of Values
Single Value	Single Value	Asterisk
Single Value	Range of Values	Asterisk
Single Value	Asterisk	Asterisk
Range of Values	Asterisk	Asterisk
Asterisk	Asterisk	Asterisk

A range of values can also be specified for an ITU-I or 24-bit ITU-N point code parameter using a combination of asterisks (*) and single values for the point code parameters. Table 8-3 shows the valid combinations of the ITU-I parameter values. Table 8-4 shows the valid combinations of the 24-bit ITU-N parameter values.

Table 8-3 Valid Value Combinations for ITU-I Point Code Parameters

ZONE	AREA	ID
Single Value	Single Value	Single Value
Single Value	Single Value	Asterisk
Single Value	Asterisk	Asterisk
Asterisk	Asterisk	Asterisk

Table 8-4 Valid Value Combinations for 24-Bit ITU-N Point Code Parameters

MSA	SSA	SP
Single Value	Single Value	Single Value
Single Value	Single Value	Asterisk
Single Value	Asterisk	Asterisk
Asterisk	Asterisk	Asterisk

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:
Thertrv-feat command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by thertrv-feat command, see thertrv-feat command description inCommands 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.
Turn the gateway screening feature on by entering this command.
chg-feat:gws=on

Note:
Once the gateway screening feature is turned on with thechg-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
```
Display all blocked DPC screens in the database using the rtrv-scr-blkdpc command. The following is an example of the possible output.
```
rlghncxa03w 06-10-25 15:25:30 GMT EAGLE5 36.0.0
SCREEN = BLOCKED DPC
SR    REF  RULES
IEC   YES     6
WRD2  YES     1
WRD3  NO      4
WRD4  YES     9
```
If the screening reference names that you wish to add with this procedure are not shown in the rtrv-scr-blkdpc command output, go to step 4. For this example, the screening reference names are not shown. If these screening reference names are shown in the rtrv-scr-blkdpc command output, make sure the screening data you wish to enter is not already in the database by entering the rtrv-scr-blkdpc command with the screening reference name. For example, enter the rtrv-scr-blkdpc:sr=iec command. The following is an example of the possible output.
```
rlghncxa03w 06-10-25 15:26:30 GMT  EAGLE5 36.0.0
SCREEN = BLOCKED DPC
SR    NI       NC       NCM      NSFI    NSR/ACT
IEC   240      001      010      FAIL    ------
IEC   241      010      *        FAIL    ------

SR      NPC                      NSFI    NSR/ACT
IEC     00235                    FAIL    ------

SR      ZONE   AREA     ID       NSFI    NSR/ACT
IEC     1      003      4        FAIL    ------
IEC     1      003      5        FAIL    ------
IEC     C      C        C        CGPA    cg01
```
If a gateway screening stop action set is to be assigned to the blocked DPC screen 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 being added in this procedure is STOP. If the NSFI of the new screen will be STOP, but a gateway screening stop action set name will not be assigned to the new screen, skip steps 4 and 5 and go to step 6. If the NSFI of the new screen is not STOP, skip step 4 and go to step 5.
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    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 being added in this procedure is STOP or FAIL, skip step 5 and go to step 6.
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 7 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.

Note:
If the point code being added in this procedure is not an ITU-I or 14-bit ITU-N spare point code, skip this step and to step 7.

Note:
If the point code being added in this procedure is an ITU-I or 14-bit ITU-N spare point code and the screening reference contains ITU-I or 14-bit ITU-N spare point codes, skip this step and go to step 7.
Display the status of the ITU National and International Spare Point Code Support feature by entering the rtrv-ctrl-feat command with the ITU National and International Spare Point Code Support feature part number.
Enter this command.

rtrv-ctrl-feat:partnum=893013601

This is an example of the possible output.
```
rlghncxa03w 06-10-25 15:25:30 GMT EAGLE5 36.0.0
The following features have been permanently enabled:

Feature Name              Partnum   Status Quantity
Spare Point Code Support  893013601 on     ----

The following features have been temporarily enabled:

Feature Name              Partnum   Status Quantity   Trial Period Left
Zero entries found.

The following features have expired temporary keys:

Feature Name              Partnum
Zero entries found.
```
If the ITU National and International Spare Point Code Support feature is enabled, go to step 7.

If the ITU National and International Spare Point Code Support feature is not enabled, perform the “Activating the ITU National and International Spare Point Code Support Feature” procedure in Database Administration - SS7 User's Guide to enable the ITU National and International Spare Point Code Support feature as required. After the feature has been enabled, go to step 7.
Add a new blocked DPC screen to the database using the ent-scr-blkdpc command.
If a gateway screening stop action is to be assigned to the blocked DPC screen being added, enter the ent-scr-blkdpc 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.

The following list contains the values for ni, nc, ncm, zone, area, id, npc, msa, ssa, and sp parameters:
- ni - 0-255, c, or an asterisk (*)
- nc - 0-255, c, or an asterisk (*)
- ncm - 0-255, c, or an asterisk (*)
- zone - 0-7, c, or an asterisk (*)
- area - 0-255, c, or an asterisk (*)
- id - 0-7, c, or an asterisk (*)
- npc - 1 - 16383, c, or an asterisk (*)
- msa - 0-255, c, or an asterisk (*)
- ssa - 0-255, c, or an asterisk (*)
- sp - 0-255, c, or an asterisk (*)
A range of values can be specified for the ni, nc, and ncm parameters. See the “Specifying a Range of Values” section for more information on how the asterisk and a range of values are used for the ni, nc, and ncm parameters.

To add a spare point code to the blocked DPC screen, the pcst=s parameter must be specified. To add a non-spare point code to the blocked DPC screen, the pcst parameter does not have to be specified. If the pcst parameter is specified for a screen containing an ITU-I or 14-bit ITU-N non-spare point code, the value must be none. The pcst parameter cannot be used with the zone=c or npc=c parameters.

For this example, enter these commands.

ent-scr-blkdpc:sr=gws9:ni=c:nc=c:ncm=c:nsfi=cgpa:nsr=gw13

A message similar to the following should appear.
```
rlghncxa03w 06-10-25 15:28:30 GMT  EAGLE5 36.0.0
ENT-SCR-BLKDPC: SCREEN SET AFFECTED - GWS9  1% FULL
ENT-SCR-BLKDPC: MASP A - COMPLTD
```
ent-scr-blkdpc:sr=gws9:ni=005:nc=005:ncm=005:nsfi=fail

A message similar to the following should appear.
```
rlghncxa03w 06-10-25 15:29:30 GMT  EAGLE5 36.0.0
ENT-SCR-BLKDPC: SCREEN SET AFFECTED - GWS9  1% FULL
ENT-SCR-BLKDPC: MASP A - COMPLTD
```
ent-scr-blkdpc:sr=gw12:ni=c:nc=c:ncm=c:nsfi=cgpa:nsr=gw14

A message similar to the following should appear.
```
rlghncxa03w 06-10-25 15:30:30 GMT  EAGLE5 36.0.0
ENT-SCR-BLKDPC: SCREEN SET AFFECTED - GW12  1% FULL
ENT-SCR-BLKDPC: MASP A - COMPLTD
```
ent-scr-blkdpc:sr=gw12:ni=004:nc=004:ncm=004:nsfi=fail

A message similar to the following should appear.
```
rlghncxa03w 06-10-25 15:31:30 GMT  EAGLE5 36.0.0
ENT-SCR-BLKDPC: SCREEN SET AFFECTED - GW12  1% FULL
ENT-SCR-BLKDPC: MASP A - COMPLTD
```

Verify the changes using the

rtrv-scr-blkdpc

command with the screening reference name used in step 7. For this example, enter these commands.

rtrv-scr-blkdpc:sr=gws9

The following is an example of the possible output.

rlghncxa03w 06-10-25 15:32:30 GMT  EAGLE5 36.0.0
SCREEN = BLOCKED DPC
SR    NI       NC       NCM      NSFI    NSR/ACT
GWS9  C        C        C        CGPA    GW13
GWS9  005      005      005      FAIL    ------

rtrv-scr-blkdpc:sr=gw12

The following is an example of the possible output.

rlghncxa03w 06-10-25 15:33:30 GMT  EAGLE5 36.0.0
SCREEN = BLOCKED DPC
SR    NI       NC       NCM      NSFI    NSR/ACT
GW12  C        C        C        CGPA    GW14
GW12  004      004      004      FAIL    -----

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 8-5 Add a Blocked DPC Screen - Screen 1 of 5

Figure 8-6 Add a Blocked DPC Screen - Screen 2 of 5

Figure 8-7 Add a Blocked DPC Screen - Screen 3 of 5

Figure 8-8 Add a Blocked DPC Screen - Screen 4 of 5

Figure 8-9 Add a Blocked DPC Screen - Screen 5 of 5

Removing a Blocked DPC Screen

This procedure is used to remove a blocked destination point code (DPC) screen from the database using the dlt-scr-blkdpc command. The parameters used by the dlt-scr-blkdpc 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.

The example in this procedure removes the blocked DPC screen iec with the point code 240-001-010 from the database.

Note:

If you using multiple-part ITU national point codes with gateway screening, see the 14-Bit ITU National Point Code Formats section.

The c-c-c entry cannot be removed from the blocked DPC screen unless all other entries in the blocked DPC screen have been removed. The c-c-c entry cannot be removed from the blocked DPC screen if other screens reference the blocked DPC screen. If the last entry (c-c-c) in the blocked DPC screen is removed, the blocked DPC screen is removed. The blocked DPC screen can be referenced by one of the following screens.

Screen Set
Allowed OPC
Blocked OPC
Allowed SIO
Allowed DPC

Verifying the Gateway Screening Configuration

Enter the following commands to verify that none of these screens reference the blocked DPC screen being removed from the database.

rtrv-scrset:nsfi=blkdpc
rtrv-scr-opc:nsfi=blkdpc
rtrv-scr-blkopc:nsfi=blkdpc
rtrv-scr-sio:nsfi=blkdpc
rtrv-scr-dpc:nsfi=blkdpc

Gateway Screening Configuration Procedures

To change the NSFI of any of these screens, perform one of these procedures.

Display the blocked DPC screens in the database using the rtrv-scr-blkdpc command.

The following is an example of the possible output.

rlghncxa03w 06-10-25 15:25:30 GMT EAGLE5 36.0.0
SCREEN = BLOCKED DPC

SR    REF  RULES
IEC   YES     6
WRD2  YES     1
WRD3  NO      4
WRD4  YES     9

From the rtrv-scr-blkdpc output, display the blocked DPC screen you wish to remove using the rtrv-scr-blkdpc command with the screening reference name. For this example, enter this command.

rtrv-scr-blkdpc:sr=iec

The following is an example of the possible output.

rlghncxa03w 06-10-25 15:25:30 GMT  EAGLE5 36.0.0
SCREEN = BLOCKED DPC
SR    NI       NC       NCM      NSFI    NSR/ACT
IEC   240      001      010      FAIL    ------
IEC   241      010      *        FAIL    ------ 
SR      NPC                      NSFI    NSR/ACT
IEC     00235                    FAIL    ------
SR      ZONE   AREA     ID       NSFI    NSR/ACT
IEC     1      003      4        FAIL    ------
IEC     1      003      5        FAIL    ------
IEC     C      C        C        CGPA    cg01

Enter the commands in the Verifying the Gateway Screening Configuration section to verify that the screen being removed is not referenced by other screens in the database.

If the screen being removed is referenced by other screens, perform the procedures shown in the Gateway Screening Configuration Procedures section to change the NSFI of those screens to reference other screens or change the NSFI of these screens to STOP.
Remove the blocked DPC screen from the database using the dlt-scr-blkdpc command with the screening reference name shown in the rtrv-scr-blkdpc output in step 1 and with the point code parameter values (ni, nc, ncm, or zone, area, id, npc, msa, ssa, or sp) of the screen being removed from the database. The values for these parameters must be entered exactly as shown in the rtrv-scr-blkdpc output.
To remove an entry containing either an ITU-I or a 14-bit ITU-N spare point code, the pcst=s parameter must be specified with the dlt-scr-blkdpc command.

To remove an entry containing either an ITU-I or a 14-bit ITU-N non-spare point code, the pcst parameter does not have to be specified with the dlt-scr-blkdpc command. If the pcst parameter is specified, the value must be none.

The pcst parameter cannot be used with the zone=c or the npc=c parameters.

For this example, enter this command.

dlt-scr-blkdpc:sr=iec:ni=240:nc=001:ncm=010

A message similar to the following should appear.
```
rlghncxa03w 06-10-25 15:26:30 GMT  EAGLE5 36.0.0
DLT-SCR-BLKDPC: SCREEN SET AFFECTED - IEC 25% FULL
DLT-SCR-BLKDPC: MASP A - COMPLTD
```

Verify the changes using the rtrv-scr-blkdpc command with the screening reference name used in step 3.

For this example, enter this command.

rtrv-scr-blkdpc:sr=iec

The following is an example of the possible output.

rlghncxa03w 06-10-25 15:27:30 GMT  EAGLE5 36.0.0
SCREEN = BLOCKED DPC
SR    NI       NC       NCM      NSFI    NSR/ACT
IEC   241      010      *        FAIL    ------ 

SR      NPC                      NSFI    NSR/ACT
IEC     00235                    FAIL    ------

SR      ZONE   AREA     ID       NSFI    NSR/ACT
IEC     1      003      4        FAIL    ------
IEC     1      003      5        FAIL    ------
IEC     C      C        C        CGPA    cg01

If the screen removed in step 3 was the last screen contained in the specified screening reference, the screening reference is removed from the database. The following message is displayed.

E2573 Cmd Rej: SR or NSR does not reference an existing SR

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 8-10 Remove a Blocked DPC Screen - Sheet 1 of 2

Figure 8-11 Remove a Blocked DPC Screen - Sheet 2 of 2

Changing a Blocked DPC Screen

This procedure is used to change the attributes of a blocked destination point code (DPC) screen in the database using the chg-scr-blkdpc command. The parameters used by the chg-scr-blkdpc 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.

The example in this procedure is used to change the point code 003-003-003 for the blocked DPC screen gw12 to 230-230-230.

Note:

If you using multiple-part ITU national point codes with gateway screening, see the 14-Bit ITU National Point Code Formats section.

If the current ni, nc, and ncm are equal to the character “c”, only the next screening function identifier and next screening reference can be changed. The next screening function identifier cannot be equal to fail. If the next screening function identifier is not equal to stop, the next screening reference must be specified. Otherwise, only the blocked DPC can be changed.

The blocked DPC screen can reference one of the following screens.

Allowed Affected Destination Field
Allowed CGPA
Allowed ISUP

Verifying the Gateway Screening Configuration

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

rtrv-scr-destfld:all=yes
rtrv-scr-cgpa:all=yes
rtrv-scr-isup: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.

If the NSFI is stop, the screening of the message will stop at the specified blocked DPC screen. If the NSFI is either cgpa, destfld, or isup, then any message containing a point code that is not listed in the blocked DPC screen with a NSFI equal to fail, will continue to be screened with either the allowed CGPA, allowed DESTFLD, or allowed ISUP screen. All subsequent entries for that screening reference must contain a numeric point code value, the NSFI must be equal to fail, and the nsr parameter cannot be specified. Any message that contains a DPC in the blocked DPC screen with the NSFI equal to fail will be rejected from the network and the screening process is stopped.

The pcst or npcst parameters, specifying whether or not the ITU-I or 14-bit ITU-N point code is a spare point code, cannot be used with the zone=c or npc=c parameters.

Specifying a Range of Values

A range of values can be specified for the point code parameters ni, nc, or ncm.

For example, screening reference name scr1 contains these entries:

SR    NI       NC       NCM      NSFI    NSR/ACT
SCR1  C        C        C        CGPA    cg01
SCR1  240      001      010      FAIL    ------
SCR1  241      010      020      FAIL    ------

Another entry for screening reference scr1 with the ni value of 240 and the nc value of 001 cannot be specified if the range of values for the ncm parameter includes the value 010.

The ANSI point code parameter values can be specified as a single value, a range of values, or with an asterisk (*). The asterisk specifies all possible values for the ni, nc, and ncm parameters. Table 8-5 shows the valid combinations of these parameter values.

Table 8-5 Valid Value Combinations for ANSI Point Code Parameters

NI	NC	NCM
Single Value	Single Value	Single Value
Single Value	Single Value	Range of Values
Single Value	Single Value	Asterisk
Single Value	Range of Values	Asterisk
Single Value	Asterisk	Asterisk
Range of Values	Asterisk	Asterisk
Asterisk	Asterisk	Asterisk

A range of values can also be specified for an ITU-I or 24-bit ITU-N point code parameter using a combination of asterisks (*) and single values for the point code parameters. Table 8-6 shows the valid combinations of the ITU-I parameter values. Table 8-7 shows the valid combinations of the 24-bit ITU-N parameter values.

Table 8-6 Valid Value Combinations for ITU-I Point Code Parameters

ZONE	AREA	ID
Single Value	Single Value	Single Value
Single Value	Single Value	Asterisk
Single Value	Asterisk	Asterisk
Asterisk	Asterisk	Asterisk

Table 8-7 Valid Value Combinations for 24-Bit ITU-N Point Code Parameters

MSA	SSA	SP
Single Value	Single Value	Single Value
Single Value	Single Value	Asterisk
Single Value	Asterisk	Asterisk
Asterisk	Asterisk	Asterisk

Display the blocked DPC screens in the database using the rtrv-scr-blkdpc command.
The following is an example of the possible output.
```
rlghncxa03w 06-10-25 15:25:30 GMT EAGLE5 36.0.0
SCREEN = BLOCKED DPC
SR    REF  RULES
GW12  YES     2
IEC   YES     6
WRD2  YES     1
WRD3  NO      4
WRD4  YES     9
```
From the rtrv-scr-blkdpc output, display the blocked DPC screen you wish to change using the rtrv-scr-blkdpc command with the screening reference name. For this example, enter this command.

rtrv-scr-blkdpc:sr=gw12

The following is an example of the possible output.
```
rlghncxa03w 06-10-25 15:25:30 GMT  EAGLE5 36.0.0
SCREEN = BLOCKED DPC
SR    NI       NC       NCM      NSFI    NSR/ACT
GW12  C        C        C        CGPA    GW14
GW12  003      003      003      FAIL    ------
```
If a gateway screening stop action set is to be assigned to the blocked DPC screen being changed in the database, go to step 2.

Step 2 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 being changed in this procedure is STOP. If the NSFI of the screen will be changed to STOP, but a gateway screening stop action set name will not be assigned to the screen, skip steps 2 and 3 and go to step 4. If the NSFI of the screen will not be STOP, skip step 2 and go to step 3.
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 being changed in this procedure will be STOP or FAIL, or if the NSFI of the screen is not being changed, skip step 3 and go to step 4.
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 5 is in the database.

If the desired screen is not in the database, go to 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.

Note:
If any of these conditions apply to this procedure, skip this step and go to step 5:
- The point code in the screen is not being changed.
- The screen being changed contains either an ANSI or 24-bit ITU-N point code.
- The ITU-I or 14-bit ITU-N non-spare point code in the screen is not being changed to an ITU-I or 14-bit ITU-N spare point code.
- The point code in the screen is an ITU-I or 14-bit ITU-N spare point code or the screening reference contains other screens with ITU-I or 14-bit ITU-N spare point codes.
Display the status of the ITU National and International Spare Point Code Support feature by entering the rtrv-ctrl-feat command with the ITU National and International Spare Point Code Support feature part number.
Enter this command.

rtrv-ctrl-feat:partnum=893013601

This is an example of the possible output.
```
rlghncxa03w 06-10-25 15:25:30 GMT EAGLE5 36.0.0
The following features have been permanently enabled:

Feature Name              Partnum   Status Quantity
Spare Point Code Support  893013601 on     ----

The following features have been temporarily enabled:

Feature Name              Partnum   Status Quantity   Trial Period Left
Zero entries found.

The following features have expired temporary keys:

Feature Name              Partnum
Zero entries found.
```
If the ITU National and International Spare Point Code Support feature is enabled, go to step 5.

If the ITU National and International Spare Point Code Support feature is not enabled, perform the “Activating the ITU National and International Spare Point Code Support Feature” procedure in the Database Administration Manual - SS7 to enable the ITU National and International Spare Point Code Support feature as required. After the feature has been enabled, go to step 5.
Change the attributes of a blocked DPC screen using the chg-scr-blkdpc command.

If a gateway screening stop action is to be assigned to the blocked DPC screen being changed, enter the chg-scr-blkdpc 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 2.

The current values for the ni, nc, ncm, zone, area, id, npc, msa, ssa, and sp parameters must be entered exactly as shown in the rtrv-scr-blkdpc output in step 1.

The following list contains the values for the nni, nnc, nncm, nzone, narea, nid, nnpc, nmsa, nssa, and nsp parameters:
- nni – 0 - 255, c, or an asterisk (*)
- nnc – 0 - 255, c, or an asterisk (*)
- nncm – 0 - 255, c, or an asterisk (*)
- nzone – 0 - 7, c, or an asterisk (*)
- narea – 0 - 255, c, or an asterisk (*)
- nid – 0 - 7, c, or an asterisk (*)
- nnpc – 1 - 16383, c, or an asterisk (*)
- nmsa – 0 - 255, c, or an asterisk (*)
- nssa – 0 - 255, c, or an asterisk (*)
- nsp – 0 - 255, c, or an asterisk (*)
A range of values can be specified for the nni, nnc, and nncm parameters. See the “Specifying a Range of Values” section for more information on how the asterisk and a range of values are used for the nni, nnc, and nncm parameters.

To change an ITU-I or 14-bit ITU-N spare point code to a non-spare point code, both the pcst=s and npcst=none parameters must be specified with the chg-scr-blkdpc command.

To change an ITU-I or 14-bit ITU-N non-spare point code to a spare point code, the npcst=s parameter must be specified with the chg-scr-blkdpc command. The pcst parameter does not have to be specified.

If the current point code in the screen being changed is either an ITU-I or 14-bit ITU-N spare point code, the pcst=s parameter must be specified with the chg-scr-blkdpc command.

If the current point code in the screen being changed is either an ITU-I or 14-bit ITU-N non-spare point code, the pcst parameter does not have to be specified with the chg-scr-blkdpc command. If the pcst parameter is specified for a screen containing either an ITU-I or 14-bit ITU-N non-spare point code, the pcst parameter value must be none.

The pcst or npcst parameters cannot be used with the zone=c or npc=c parameters.

For this example, enter this command.
chg-scr-blkdpc:sr=gw12:ni=003:nc=003:ncm=003:nni=230:nnc=230 :nncm=230

The following message appears.
```
rlghncxa03w 06-10-25 15:27:30 GMT  EAGLE5 36.0.0
CHG-SCR-BLKDPC: SCREEN SET AFFECTED - GW12  1% FULL
CHG-SCR-BLKDPC: MASP A - COMPLTD
```
Verify the changes using the rtrv-scr-blkdpc command with the screening reference name used in step 5.
For this example, enter this command.

rtrv-scr-blkdpc:sr=gw12

The following is an example of the possible output.
```
rlghncxa03w 06-10-25 15:28:30 GMT  EAGLE5 36.0.0
SCREEN = BLOCKED DPC
SR    NI       NC       NCM      NSFI    NSR/ACT
GW12  C        C        C        CGPA    GW14
GW12  230      230      230      FAIL    ------
```

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 8-12 Change a Blocked DPC Screen - Sheet 1 of 5

Figure 8-13 Change a Blocked DPC Screen - Sheet 2 of 5

Figure 8-14 Change a Blocked DPC Screen - Sheet 3 of 5

Figure 8-15 Change a Blocked DPC Screen - Sheet 4 of 5

Figure 8-16 Change a Blocked DPC Screen - Sheet 5 of 5