Database

See notice on first age
Alcatel-Lucent CDMA Network

Executive Cellular Processor (ECP)
Release 29.0 and later
DBsubquery, DBsubsum, and DBsubreport.pl Optional Feature
Description
401-612-168
Issue 16
October 2007
Alcatel-Lucent - Proprietary
This document contains proprietary information of Alcatel-Lucent and
is not to be disclosed or used except in accordance with applicable agreements.
Copyright 2007 Alcatel-Lucent
Unpublished and Not for Publication
All Rights Reserved
See notice on first age
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their
respective owners.
The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright 2007 Alcatel-Lucent. All Rights Reserved.
Limited warranty
Alcatel-Lucent provides a limited warranty to this product.
See notice on first page
Contents
DBsubquery, DBsubsum, and DBsubreport.pl Optional Feature Description

Overview
..........................................................................................................................................................................................
................................................................................................................................................
......................................................................................................................................................................................
Prerequisites
....................................................................................................................................................................................
DBsubquery
..................................................................................................................................................................................
Structure of hazard statements

Availability
DBsubreport.pl Tool
DBsubsum Tool
10
................................................................................................................................................................
37
.........................................................................................................................................................................
44
.............................................................................................................................................................
64
....................................................................................................................................................................
65
Special Considerations
Feature interactions
Implementing the features
......................................................................................................................................................
Activating the features/tools
..................................................................................................................................................
Procedure 1: Prevent interference-ECP
.............................................................................................................................
68
69
.......................................................................................................................
71
..................................................................................................................
72
......................................................................................................................
74
Procedure 4: Prevent all RC/V activity-ECP

Procedure 5: Run DBsubquery-ECP/OMP
67
............................................................................................
Procedure 2: Update backup subscriber databases-ECP

Procedure 3: Perform a tape backup-ECP
66
Procedure 6: Verify the backup databases-ECP
.............................................................................................................
Procedure 7: Replace the Master Databases-ECP

Procedure 8: Restore RC/V permissions-ECP
75
........................................................................................................
77
................................................................................................................
78
...................................................................................................................................................................................................................................
401-612-168
iii
Issue 16, October 2007
Contents
Related documentation
History of Revisions
.............................................................................................................................................................
79
.................................................................................................................................................................
80
Abbreviations and Terminology
...........................................................................................................................................
Appendix A: Query Fields and Conversion Tables
......................................................................................................
Appendix B: DBsubquery Update Capable Additional Fields
..............................................................................
83
86
118
Index
...................................................................................................................................................................................................................................
401-612-168
iv
List of tables
DBsubquery Command Options
DBsubquery Update Capable Command Line Options
DBsubreport.pl Field Definitions
DBsubsum Field Definitions
Query Fields
atech Conversions
IS-53-A Preferred Language (deft_pl Conversions)
dntype Conversions
ecp_level Conversions
10
fatype Conversions
11
..........................................................................................................................
11
..............................................................................
27
........................................................................................................................
37
.................................................................................................................................
44
.................................................................................................................................................................
86
....................................................................................................................................................
112
..................................................................................
112
.................................................................................................................................................
113
...........................................................................................................................................
114
..................................................................................................................................................
114
mpci Conversions
....................................................................................................................................................
114
12
mpdc Conversions
...................................................................................................................................................
115
13
mrstype Conversions
14
msstat Conversions
15
paging_serv Conversions
16
pgnum Conversions
17
slotidx_c Conversions
18
sndisp Conversions
19
svcalw_c Conversions
20
vman_option Conversions
..............................................................................................................................................
115
..................................................................................................................................................
115
......................................................................................................................................
116
.................................................................................................................................................
116
............................................................................................................................................
116
..................................................................................................................................................
116
............................................................................................................................................
....................................................................................................................................
117
117
...................................................................................................................................................................................................................................
401-612-168
v
List of tables
21
DBsubquery Update Capable: Values and Checks
.....................................................................................
118
...................................................................................................................................................................................................................................
401-612-168
vi
List of figures
Example 1: Format file
............................................................................................................................................
15
Example 2: Format file
............................................................................................................................................
15
Example 1: Output file with +f/+p Option
Example 2 (Screen 1): Output file with +f/+p Option
Screen and file output format for DBsubquery with +L Option
............................................................
18
Screen and file output format for DBsubquery with +l Option
.............................................................
19
Example 1: Standard DBsubquery Output
......................................................................................................
19
Example 2: DBsubquery long output directed to the screen
......................................................................................................
...............................................................................
17
17
...................................................................
20
Example 3 (Screen 1): Displaying the query syntax
...................................................................................
21
10
...................................................................................
22
11
...................................................................................
23
12
Display fields screen
.................................................................................................................................................
31
13
Specify value screen
.................................................................................................................................................
32
14
Verify value screen
....................................................................................................................................................
33
15
Example output from DBsubquery +r option
16
Example: DBsubquery +f/+p option format file
17
Example: How to create DBsubreport.pl input_file
18
Example: DBsubreport.pl input_file content
19
Example: DBsubreport.pl execution
20
Example: output_file content
.................................................................................................
...........................................................................................
36
38
....................................................................................
39
..................................................................................................
40
...................................................................................................................
41
................................................................................................................................
41
....................................................................................................................................................................................................................................
401-612-168
vii
List of figures
21
Example: output_file1 content
..............................................................................................................................
42
22
Example: mec_list_file content
............................................................................................................................
43
23
Example: output_file1 content (with l option used)
24
Example of DBsubsum Screen Output
25
.................................................................................
43
.............................................................................................................
45
DBsubsum Output Example (Part 1)
.................................................................................................................
47
26
.................................................................................................................
48
27
.................................................................................................................
49
28
.................................................................................................................
50
29
.................................................................................................................
50
30
.................................................................................................................
51
31
.................................................................................................................
51
32
.................................................................................................................
52
33
.................................................................................................................
53
34
...............................................................................................................
54
35
...............................................................................................................
55
36
...............................................................................................................
56
37
...............................................................................................................
57
38
...............................................................................................................
58
39
...............................................................................................................
59
40
...............................................................................................................
60
41
...............................................................................................................
61
42
...............................................................................................................
62
43
...............................................................................................................
62
...................................................................................................................................................................................................................................
401-612-168
viii
DBsubquery, DBsubsum, and

DBsubreport.pl Optional Feature
Description
Overview
...................................................................................................................................................................................................................................
Purpose
This document describes the DBsubreport.pl tool and the DBsubquery, DBsubquery +f
Formatted Output Option, DBsubquery +p Private Data Option, DBsubquery Update
Capable, and DBsubsum optional features for the CDMA network (formerly
Flexent /AUTOPLEX wireless networks). The document provides the following
information:
availability and special system requirements

feature capabilities and interactions with other CDMA network features
information about how this feature affects other system interfaces
feature implementation procedures
Reason for reissue
Issue 16 of this document supports Releases 29 and later. Changes support:
R29.0 FID 13104.0, OneBTS platform support for Advanced Wireless Spectrum
(Band Class 15).
This feature adds the bc15_aws field to Table 5, Query Fields (p. 86) and Table
21, DBsubquery Update Capable: Values and Checks (p. 118).
R30.0 FID 12395.1, CDMA Full IMSI Feature Interactions for MIN-Based IMSI
This feature introduces the +S query option and imsi/min fields to the DBsubquery
tool and introduces the DBsubreport.pl tool. See the following for more
information:
+S option: Table 1, DBsubquery Command Options (p. 11)
Fields imsi and min: Table 5, Query Fields (p. 86)
DBsubreport.pl tool description: DBsubreport.pl Tool (p. 37)
See CDMA Full IMSI and Related Features Optional Feature Description,
401-612-297 for a full feature description.
...................................................................................................................................................................................................................................
401-612-168
1
DBsubquery, DBsubsum, and DBsubreport.pl Optional

Feature Description
Overview
Description of the DBsubquery tool +r option has been added.

See the following for more information:
+r option: Table 2, DBsubquery Update Capable Command Line Options
(p. 27)
+r usage and example: Deleting subscriber records (p. 35)
MR183346 - DBsubquery support for IHLR to SDHLR Migration - part III.
In R28SU6 and later releases, the following new database fields are supported for
querying/printing by the DBsubquery tool and have been added to Table 5, Query
Fields (p. 86) : fa_dn[1-15], fa_iddd[1-15], fa_pstn[1-15], feat_ctl[1-15],
icf_act[1-15], ppdn[1-4], tt_busy[1-15], tt_na[1-15], tt_npr[1-15], tt_rf[1-15].
MR181049 - MPCAP feature (to support IHLR to USDS migration).
In R28SU6 and later releases, the following new database fields are supported for
querying/printing by the DBsubquery tool and have been added to Table 5, Query
Fields (p. 86) : mpdc2 and mpdc3 (supporting the MPCAP feature).
MR184331 - DBsubquery support for IHLR -> SDHLR migration - part IV.
In R29SU1 and later releases, the following new database field is supported for
querying/printing by the DBsubquery tool and has been added to Table 5, Query
Fields (p. 86) : hlrcrbt_act (HLR Based Customized Ring Back Tone Activated).
Feature summary
The following summarizes the features described in this document.

DBsubquery/DBsubsum feature (FID 2792.0)
The DBsubquery/DBsubsum feature allows for auditing of the subscriber databases.

DBsubquery +f Formatted Output Option feature (FID 2792.1)
The DBsubquery +f Formatted Output Option feature enhances the functionality of the
DBsubquery tool by directing the format file field values into the specified output file.
DBsubquery +p Private Data Option feature (FID 4122.0)
The DBsubquery +p Private Data Option feature enhances the functionality of the
DBsubquery tool by allowing a secured means to print fields such as akey or ssd to an
output field.
DBsubquery Update Capable features (FID 2792.2/3129.0)
The DBsubquery Update Capable features are an enhancement to the existing

DBsubquery feature that provides expanded search criteria, allows the user to mark or
unmark records and/or change the values in fields in those records within the same
command invocation, and allows the mark/unmark and change function to be executed
in trial mode.
...................................................................................................................................................................................................................................
401-612-168

Feature Description
Overview
CDMA Full IMSI Feature Interactions for MIN-Based IMSI feature (FID 12395.1)
The CDMA Full IMSI Feature Interactions for MIN-Based IMSI feature (FID 12395.1)
is an enhancement to the existing CDMA Full IMSI feature that introduces the
DBsubquery +S option allowing the user to print keys in the form of IMSI and
introduces the DBsubreport.pl tool. See CDMA Full IMSI and Related Features
Optional Feature Description, 401-612-297 for a full feature description.
Benefits
The DBsubquery feature allows for quick analysis of subscriber-related service trends,
rapid marketing analysis, and timely auditing of the subscriber databases. It allows the
user to query application databases to extract specific information. The key fields in
the query match can be printed to a file for later reference. Furthermore, it adds
DBsubsum, a tool that creates a quick summary of the subscriber database.
The DBsubquery Update Capable feature is an enhancement to the existing
DBsubquery feature and is meant to be used in place of many commonly requested
DBmagic tools. It offers the following benefits:
The user can invoke DBsubquery under the DBsubquery Update Capable feature
and for the subscriber database records that meet the search criteria, the user can:
mark or unmark records
change the values in a select set of fields in those records
perform both functions, mark/unmark and change, within the same invocation.
In performing a change operation, the user is given a chance to change the set
of fields and new values they entered or to halt the DBsubquery tool. This
allows the user to see how the tool interpreted the values entered and to make
changes to those values.
The search criteria of DBsubquery is expanded to include those records whose keys
are represented in a query bypass file (for which no Query? expression is
needed). One possible query bypass file is an output file populated by a prior
invocation of DBsubquery.
The user can perform a trial run on the proposed change or mark/unmark operation
to see how subscriber records would be affected, without making the actual
changes.
Important! These features give service providers the tools to do various queries of
the subscriber database. Therefore, the features are often referenced as tools.
Intended audience
This document is intended for engineers, technicians, and administrators who

implement or maintain the DBsubquery, DBsubquery +f Formatted Output Option,
DBsubquery +p Private Data Option, DBsubquery Update Capable, DBsubsum optional
features for the CDMA network.
...................................................................................................................................................................................................................................
401-612-168
3

Feature Description
Overview
To obtain technical support, documentation, and training or submit feedback
The Online Customer Support (OLCS) web site (http://support.lucent.com/) provides

access to technical support, related documentation, related training, and feedback tools.
The site also provides account registration for new users.
Contents
Availability
Prerequisites
DBsubquery
10
DBsubreport.pl Tool
37
DBsubsum Tool
44
Special Considerations
64
Feature interactions
65
Implementing the features
66
Activating the features/tools
67
Procedure 1: Prevent interference-ECP
68
69
Procedure 3: Perform a tape backup-ECP
71
72
Procedure 5: Run DBsubquery-ECP/OMP
74
75
Procedure 7: Replace the Master Databases-ECP
77
Procedure 8: Restore RC/V permissions-ECP
78
Related documentation
79
80
83
86
Appendix B: DBsubquery Update Capable Additional Fields
118
...................................................................................................................................................................................................................................
401-612-168

Feature Description
Structure
of hazard statements
...................................................................................................................................................................................................................................
Overview
Hazard statements describe the safety risks relevant while performing tasks on
Alcatel-Lucent products during deployment and/or use. Failure to avoid the hazards
may have serious consequences.
General structure
Hazard statements include the following structural elements:
Item
Structure element
Purpose
Personal-injury symbol
Indicates the potential for personal injury

(optional)
Hazard-type symbol
Indicates hazard type (optional)
Signal word
Indicates the severity of the hazard
Hazard type
Describes the source of the risk of damage or

injury
Damage statement
Consequences if protective measures fail
Avoidance message
Protective measures to take to avoid the hazard
Identifier
The reference ID of the hazard statement

(optional)
...................................................................................................................................................................................................................................
401-612-168
5

Feature Description
Signal words
The signal words identify the hazard severity levels as follows:

Signal word
Meaning
DANGER
Indicates an imminently hazardous situation (high risk) which, if

not avoided, will result in death or serious injury.
WARNING
Indicates a potentially hazardous situation (medium risk) which,

if not avoided, could result in death or serious injury.
CAUTION
When used with the personal injury symbol:

Indicates a potentially hazardous situation (low risk) which, if
not avoided, may result in personal injury.
When used without the personal injury symbol:
Indicates a potentially hazardous situation (low risk) which, if
not avoided, may result in property damage, such as service
interruption or damage to equipment or other materials.
...................................................................................................................................................................................................................................
401-612-168

Feature Description
Availability
...................................................................................................................................................................................................................................
Release availability
The following table identifies the software releases in which the features are available.
Feature
Available in
Releases 9.0 and later
DBsubquery +f Formatted Output Option

feature (FID 2792.1)
Releases 9.0 with SU 97-0006 and

later
DBsubquery +p Private Data Option feature

(FID 4122.0)
Releases 14.0 with SU 99-0008 and

later
DBsubquery Update Capable Additional Fields

(FID 2792.2) and DBsubquery Update Capable
feature (FID 3129.0)
DB Migration Tools-Phase 1 (FID 7077)
CDMA Full IMSI Feature Interactions for

MIN-Based IMSI (FID 12395.1)
Market availability
The DBsubquery/DBsubsum feature and related features are available in all markets,
except for the CDMA Full IMSI Feature Interactions for MIN-Based IMSI optional
feature (FID 12395.1), which is available in the international market only.
Restricted Availability
The DBsubquery Update Capable Additional Fields feature (FID 2792.2) that is
described in this document has Restricted Availability (RA) status. Restricted
Availability means that a feature has been developed for specific customers only.
Restricted Availability features have been tested in specific environments for those
select customers and have not been designated as Generally Available (GA). These
features may be made available to other customers, but additional development may be
needed. Please contact your customer team to determine whether additional
development is necessary to activate these features and arrange for testing of these
features in your network.
...................................................................................................................................................................................................................................
401-612-168
7

Feature Description
Prerequisites
...................................................................................................................................................................................................................................
Introduction
The DBsubquery/DBsubsum feature and related features have the following

prerequisites.
Supported technologies
The DBsubquery/DBsubsum feature and related features are independent of all air
interfaces.
HLR configuration
The DBsubquery/DBsubsum feature and related features are independent of all HLR
configurations.
Software requirements
The following summarizes the features described in this document.

The DBsubquery/DBsubsum feature (FID 2792.0) requires ECP Releases 9.0 or later.
The DBsubquery/DBsubsum feature is not dependent on other features.
DBsubquery +f Formatted Output Option feature (FID 2792.1)
The DBsubquery +f Formatted Output Option feature (FID 2792.1) requires ECP
Releases 9.0 with SU 97-0006 or later. The DBsubquery +f Formatted Output Option
feature is dependent on DBsubquery/DBsubsum (FID 2792.0).
DBsubquery +p Private Data Option feature (FID 4122.0)
The DBsubquery +p Private Data Option feature (FID 4122.0) requires ECP Releases
14.0 with SU 99-0008 or later. The DBsubquery +p Private Data Option feature is
dependent on DBsubquery/DBsubsum (FID 2792.0).
DBsubquery Update Capable feature (FID 3129.0)
The DBsubquery Update Capable feature (FID 3129.0) requires ECP Releases 15.0 or
later. The DBsubquery Update Capable feature (FID 3129.0) is dependent on
DBsubquery/DBsubsum (FID 2792.0).
DB Migration Tools-Phase 1 (FID 7077)
The DB Migration Tools-Phase 1 feature (FID 7077) requires ECP Releases 20.0 or
later. The DB Migration Tools-Phase 1 feature (FID 7077) is not dependent on other
features.
...................................................................................................................................................................................................................................
401-612-168

Feature Description
Prerequisites
CDMA Full IMSI Feature Interactions for MIN-Based IMSI (FID 12395.1)
The CDMA Full IMSI Feature Interactions for MIN-Based IMSI feature (FID 12395.1)
requires ECP Releases 30.0 or later and is dependent on the CDMA Full IMSI feature
(FID 2034.0).
Hardware requirements
The feature set has no hardware requirements beyond the standard hardware in a
CDMA network.
...................................................................................................................................................................................................................................
401-612-168
9

Feature Description
DBsubquery
...................................................................................................................................................................................................................................
Introduction
The following information describes the functionality and operation of the DBsubquery
feature.
Functionality
The DBsubquery feature is a tool that does the following:
recognizes over 200 different keywords

allows the user to query subscriber applications databases for up to 12 fields
simultaneously and print keys
adds DBsubsum, a tool that creates a quick summary of the subscriber database
prints fields requested from an input file to an output file (+f Option)
prints private data requested from an input file to an output file (+p Option)
allows marking/unmarking and updating of subscriber records (Update Capable)
allows the user to query subscribers that have specific WIN services listed on the
Subscriber and Feature Information (sub) RC/V form.
prints the subscriber information for specific WIN services on the
Subscriber and Feature Information (sub) RC/V form
How the feature operates
The DBsubquery command is entered at the UNIX system shell prompt and generates
a list of Mobile Identification Numbers (MINs) and additional information about each
MIN, depending on the options and match criteria entered. The results of the
DBsubquery command are stored in the user-specified output_file.
The syntax of the DBsubquery, DBsubquery +f Option, and the DBsubquery +p Option
is described below. For various command options, refer to Table 1, DBsubquery
Command Options (p. 11) .
For DBsubquery, the syntax is as follows:
DBsubquery [+{sklL(L1)x}] [+n ## ] [output_file]
For the +f Option, the syntax is as follows:

DBsubquery [+{sklL(L1)x}] [+n
## ] [+f format_file] [output_file]
For the +p Option, the syntax is as follows:

DBsubquery [+{sklL(L1)x}] [+n
## ] [+p format_file] [output_file]
Or, to get help:

DBsubquery -h
...................................................................................................................................................................................................................................
401-612-168
10

Feature Description
DBsubquery
or
man DBsubquery
Table 1
(on the OMP)
Option
Definition
format_file
The name of the file that contains valid field names whose
values are to be printed. Required for +f, +p
output_file
The name of the file to receive the search results. Using a file
name of here causes the results to be output to the screen.
+x
Transfer backup subscriber databases from ECP

(/1apx10/dbackup) to the current directory on the OMP (OMP
only).
+s
Display the syntax for search criteria
+k
Display list of valid keywords for the search
+L
The +L (long) option adds the following information for each

subscriber listed in the output file:
Directory Number ( dn)
Serial number ( srno)
Mobile Equipment Identifier ( MEID)
Origination major class ( omaj)
Termination major class ( tmaj)
Primary dialing class ( dc1)
Secondary dialing class ( dc2)
Switch Identification ( sw)
Primary Exchange Carrier ( pic)
Immediate Call Forwarding ( icf)
Call Forwarding Busy Line ( cfbl)
Call Forwarding Dont Answer ( cfda)
Call Forwarding No Page Response ( cfnpr)
Message Recording Service ( mrs)
Call Waiting ( cw)
Three-way Calling ( twc)
Long MIN Paging Active ( exmin)
Billing number ( billno)
...................................................................................................................................................................................................................................
401-612-168
11

Feature Description
Table 1
Option
DBsubquery
(continued)
Definition
+L1
1
(see Table Note )
The +L1 option adds the following information for each

subscriber listed in the output file (provides DBsubsearch +L1
functionality):
Directory Number ( dn)
Visited DCS Identifier ( vdcsid)
Visited ECP Identifier ( vecpid)
Visited System Identifier ( vsid)
+l
Same as +L, except that the column headings shown on the

screen are printed so that they vertically align with the fields
they describe (when output is directed to the screen rather than
a file).
+n##
Terminate search after ## matches.
-h
The -h (help) option signals DBsubquery to print a usage

message and quit.
+f
Output the format file field values into the specified output
file.
+p
Output the format file field values into the specified output file
(private data).
+S
Display IMSI instead of msid along with each record in the

output (options +f/+p/+l/+L/+L1).
Notes:
1.
Null values will be dashes (-) for +L1 output. For this +L1 option, the service provider
needs to perform a BKUP ccfdb via the craft shell or the TICLI, in order to see
meaningful data in the vdcsid, vecpid, and vsid fields. For more information on the TICLI
refer to Procedure 2: Update backup subscriber databases-ECP (p. 69).
Important! The plus (+) symbol precedes each of the fields rather than the more
common practice of using the minus (-) symbol for this purpose. The minus symbol
can still be used, but it is now interpreted as a request to print usage information
for the option rather than run a query.
DBsubquery - {hskl(L1)fpx}
For example, entering the following command displays the input query syntax:
DBsubquery -s
But, typing the line below displays the same information and then proceeds to
run a query and write the results to a file named my_output:
...................................................................................................................................................................................................................................
401-612-168
12

Feature Description
DBsubquery +s
DBsubquery
my_output
The exception to this rule is the help option (-h), which cannot be used with
the plus (+) symbol.
Entering the Search Criteria
When the DBsubquery command is entered, it responds with a prompt like the one
below:
Query?
To exit the DBsubquery tool without running a query, just press Return or type q to
quit. Otherwise, enter the query criteria using the following syntax:
Important! Spaces are required between fields, operators, and values.
FIELD = | != | < | > VALUE [AND|OR FIELD = | != | < | > VALUE]
For example,
npa = 708 AND cw != 1
Up to twelve criteria, joined with and/oroperations are permitted per query (with
DBSQ FAF activated).
The & may be substituted for AND.
The | (pipe) may be substituted for OR.
Field names are not case sensitive.
Parentheses are allowed around a field/value comparison
DBsubquery finds records that meet user-specified criteria in the backup copy of the
subscriber database. The criteria are logical expressions that contain subscriber
database field names, logical operators, and values, such as the following:
cgsa
!=
(which translates to CGSA not equal to 2).

The user enters the expression at the tools Query? prompt. DBsubquery then
determines, based on the field names that the user entered, which subscriber databases
must be examined. DBsubquery opens the database files and reads the records. It then
compares the values in the fields for the records to the values that the user entered in
the Query? expression as criteria. If any of those records meet the specified criteria,
their keys, in the form of Mobile Station Identifiers (MSIDs) or International Mobile
Subscriber Identification number (IMSIs), are written in the following format:
msid (10 digits; for example 3125551212)

imsi (8-15 digits; for example 101166309830000)
They are placed in the specified output_file. The number of records searched and the
number of records that met the search criteria are reported to the screen.
...................................................................................................................................................................................................................................
401-612-168
13

Feature Description
DBsubquery
If the DBsubquery tool is running on the ECP, it reads the subscriber database files in
the backup directory /1apx10/database backup directory.
If the tool is running on the OMP, it reads the subscriber database files in the current
working directory.
Field Names
For information on specific fields and ranges, refer to Appendix A: Query Fields and
Conversion Tables (p. 86) .
Special Considerations for Variable-Length Directory Numbers
The dn, npa, nxx, and mdn fields are only defined for 10-digit National Significant
Numbers (NSNs).
When querying, if any of these field names are used at the Query? prompt, then only
records having 10-digit NSNs will match.
If the 10-digit restriction is undesirable, use the nsn field instead. DBsubquerys ? and
* wildcards may be combined with digits as in the following examples:
nsn = 708 ???????
nsn = 708*
find NSNs that beginning with 708 and followed by any 7 digits
find NSNs beginning with 708, followed by any number of digits, including
none.
nsn =
??? 555*
find NSNs that begin with any three digits, followed by 555, followed by any
number of digits, including none.
Also, when any of these fields are included in output, if some records contain an nsn
that is not 10-digits in length, the dn, npa, nxx, and mdn fields printed for these records
will be filled with NULL character specified.
Format File (+f/+p Option)
The +f Option and +p Option have a required input file.

This required format file specifies the settings of the null values, the input/output
delimiter, and fields to print. Fields are printed in the order in which they appear in the
+f format file, including the msid.
...................................................................................................................................................................................................................................
401-612-168
14

Feature Description
DBsubquery
The input file takes the following required format:
1st non-blank line: NULL=[null]

NULL= This character is used to indicate null values in the output file [default
is a space]
2nd non-blank line: DELIMITER=[delimiter]
DELIMITER= This character is used to separate keywords in the input file and
both key and keyword database values in the output file [default is a space]
All subsequent lines: keyword [keyword keyword...]
keyword- If there is more than one keyword, they must be separated by the
specified delimiter
The delimiter specified on the delimiter line must be used between fields on a line. For
example, if DELIMITER=; then keywords would appear in the format: keyword1;
keyword2;keyword3.
Field names can be one per line or up to a maximum of 256 characters per line. The
order in which the fields are input gives the order of the output field values.
The following figures are two examples of a format file:
Figure 1 Example 1: Format file
NULL=DELIMITER=
dn npa nxx mdn nsn
sms_wi
Figure 2 Example 2: Format file

NULL=DELIMITER=;
pic;
hldgt;ccfmax
mrsno;cwdatime;paacx;stdlidx;
ctrace;lsa_listl;mpci;
cfbl;cw;cfnpr;cfda;cd;icf;icfab;icfnoad;ccfnoad;mrs;
Ccfbmrs;icfbmrs;cpnd;cpnr;cw;cwar;twc;cp_ct;icsr;caldelact;
...................................................................................................................................................................................................................................
401-612-168
15

Feature Description
DBsubquery
Output File Examples (without +f/+p Option)
When the DBsubquery tool is finished, the output file specified at the command line
will contain the MSIDs for which a match is found and/or all the fields defined in the
format file if +f/+p option is specified. Each line of the file contains information on
one matching MSID. The standard output file will contain one of the following MSID
fields:
A standard output file is one without the +f/+p option.
Mobile Station Identification Number (msid)

International Mobile Station Identification Number (imsi)
Each line of the standard output file has one of the formats shown below:
msid
imsi
The following are msid examples:

2122672900
2122672901
2122672902
2122672903
The following are imsi examples:

011026309220000
011026304990000
011026303690000
011026309830000
Output File Examples (with +f/+p Option)
The following figures are two examples of an output file with the +f/+p Option:
Important! In Figure 4, Example 2 (Screen 1): Output file with +f/+p Option
(p. 17), a dash (-) is used for the NULL character in the format file. The output
file in Figure 3, Example 1: Output file with +f/+p Option (p. 17) is based on the
input file in Figure 1, Example 1: Format file (p. 15). The output file in Figure 4,
Example 2 (Screen 1): Output file with +f/+p Option (p. 17) is based on the
input file in Figure 2, Example 2: Format file (p. 15).
...................................................................................................................................................................................................................................
401-612-168
16

Feature Description
DBsubquery
Figure 3 Example 1: Output file with +f/+p Option

3123676602
3123676603
3123676604
3123676605
3123676606
3123676607
3123676608
3123676609
3123676610
3123676611
3123676612
3123676613
3123676614
3123676615
3123676640
3123676641
3123676642
3123676643
3123676602
3123676603
3123676604
3123676605
3123676606
3123676607
3123676608
3123676609
3123676610
3123676611
3123676612
3123676613
3123676614
3123676615
3123676640
3123676641
3123676642
3123676643
312
312
312
312
312
312
312
312
312
312
312
312
312
312
312
312
312
312
367
367
367
367
367
367
367
367
367
367
367
367
367
367
367
367
367
367
6602
6603
6604
6605
6606
6607
6608
6609
6610
6611
6612
6613
6614
6615
6640
6641
6642
6642
3123676643
3123676643
3123676643
3123676643
3123676643
3123676643
3123676643
3123676643
3123676643
3123676643
3123676643
3123676643
3123676643
3123676643
3123676643
3123676643
3123676643
3123676643
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
Figure 4 Example 2 (Screen 1): Output file with +f/+p Option

3123676602
;3123676602
;---;---;---;---;---;---;553
3123676603
;3123676603
;---;---;---;---;---;---;553
3123676604
;3123676604
;---;---;---;---;---;---;553
3123676605
;3123676605
;---;---;---;---;---;---;553
3123676606
;3123676606
;---;---;---;---;---;---;553
3123676607
;3123676607
;---;---;---;---;---;---;553
3123676608
;3123676608
;---;---;---;---;---;---;553
3123676609
;3123676609
;---;---;---;---;---;---;553
3123676610
;3123676610
;---;---;---;---;---;---;553
;0011;------------;1
;--;30;----;----;00;---;--;n;n;n;n;n;n;n;n;n;n;n;n;n;n;n;y;n;n;n;y;
;0011;------------;1
;0011;------------;1
;0011;------------;1
;0011;------------;1
;0011;------------;1
;0011;------------;1
;0011;------------;1
;0011;------------;1
...................................................................................................................................................................................................................................
401-612-168
17

Feature Description
DBsubquery
DBsubquery +L Option
DBsubquerys +L option gives a long dump which adds the following fields to the
MSID field:
Directory Number (dn)

Serial number (srno)
Mobile Equipment Identifier (MEID)
Origination major class (omaj)
Termination major class (tmaj)
Primary dialing class (dc1)
Secondary dialing class (dc2)
Switch Identification (sw)
Primary Exchange Carrier (pic)
Immediate Call Forwarding (icf)
Call Forwarding Busy Line (cfbl)
Call Forwarding Dont Answer (cfda)
Call Forwarding No Page Response (cfnpr)
Message Recording Service (mrs)
Call Waiting (cw)
Three-way Calling (twc)
Long MIN Paging Active (exmin)
Billing number (billno)
Figure 5, Screen and file output format for DBsubquery with +L Option (p. 18)
shows an example of the screen output format of DBsubquery when the +L option is
used (Query used to generate output: billno != min). The heading explains the contents
of the output and is included only when the output is directed to the screen (using
here). An output file omits the heading and starts with the first matching user entry.
Figure 5 Screen and file output format for DBsubquery with +L Option
Field values, separated by semi-colons, appear in the following order:
msid
nsn
srno
meid
3129639882
;3129639882
;h00000000;h00000000000000;
3129639883
;3129647529
;h00000000;h00000000000000;
3129639884
;3129647528
;h00000000;h00000000000000;
3129639885123 ;3129647530123 ;h00000000;h00000000000000;
312963988612345;31296475321244;h00000000;h00000000000000;
o
t
maj maj dc1 dc2 sw pic
001;001;001;002;01;0011;
001;001;001;002;16;0011;
001;001;001;002;16;0011;
001;001;001;002;16;0011;
001;001;001;002;16;0011;
c
e
c c f
x
i f f n m
t m
c b d p r c w i
f l a r s w c n
0;0;0;0;0;0;0;1
0;0;0;0;0;0;0;1
0;0;0;0;0;0;0;1
0;0;0;0;0;0;0;1
0;0;0;0;0;0;0;1
billno
;1014
;5000
;5001
;5001
;5001
...................................................................................................................................................................................................................................
401-612-168
18

Feature Description
DBsubquery
DBsubquery +l Option
This option generates the same output data that the +L option generates. However, the
headings shown on screen align with the columns in the output data as shown in
Figure 6, Screen and file output format for DBsubquery with +l Option (p. 19).
Important! Since the heading does not appear in output directed to a file, output
files that are generated with the +L option are identical to those generated with the
+l option.
Figure 6 Screen and file output format for DBsubquery with +l Option
msid
nsn
srno
meid
3129639882
;3129639882
;h00000000;h00000000000000;
3129639883
;3129647529
;h00000000;h00000000000000;
3129639884
;3129647528
;h00000000;h00000000000000;
3129639885123 ;3129647530123 ;h00000000;h00000000000000;
312963988612345;31296475321244;h00000000;h00000000000000;
o
t
maj maj dc1 dc2 sw pic
001;001;001;002;01;0011;
001;001;001;002;16;0011;
001;001;001;002;16;0011;
001;001;001;002;16;0011;
001;001;001;002;16;0011;
c
e
c c f
x
i f f n m
t m
c b d p r c w i
f l a r s w c n
0;0;0;0;0;0;0;1
0;0;0;0;0;0;0;1
0;0;0;0;0;0;0;1
0;0;0;0;0;0;0;1
0;0;0;0;0;0;0;1
billno
;1014
;5000
;5001
;5001
;5001
DBsubquery Example 1: Standard Output
Figure 7, Example 1: Standard DBsubquery Output (p. 19) shows an example of the
DBsubquery command used to find all MSIDs with an area code of 212 and the Call
Waiting feature active. The results are placed into a file named npa212cw.
Figure 7 Example 1: Standard DBsubquery Output
DBsubquery npa212cw
Query ? npa = 212 AND cw = y
Beginning database search now, please be patient!
Progress marks indicate 1000s of subscriber records searched.
SUMMARY OF QUERY PROCESSING
Primary
#Records
#Records
#Records
Search DB
Read
Matching
Not Matching
========================================================================
mufdb
18737
3
18734
File "npa212cw" created for any matched mobile #s.
...................................................................................................................................................................................................................................
401-612-168
19

Feature Description
DBsubquery
DBsubquery Example 2: Long output directed to the screen
Figure 8, Example 2: DBsubquery long output directed to the screen (p. 20) shows
an example of the DBsubquery command used to find all billing numbers that do not
match their corresponding MSIDs. Since the output filename here is used, the results
are displayed on the screen rather than in an output file.
Figure 8 Example 2: DBsubquery long output directed to the screen
DBsubquery +l here
Query ? billno != Min
c
e
c c f
x
i f f n m
t m
o
t
c b d p r c w i
msid
nsn
srno
meid
maj maj dc1 dc2 sw pic f l a r s w c n billno
3129639882;3129639882;h00000000;h00000000000000;001;001;001;002;01;0011;0;0;0;0;0;0;0;1;104
3129639883;3129647529;h00000000;h00000000000000;001;001;001;002;16;0011;0;0;0;0;0;0;0;1;500
3129639884;3129647529;h00000000;h00000000000000;001;001;001;002;16;0011;0;0;0;0;0;0;0;1;501
3129639885;3129647529;h00000000;h00000000000000;001;001;001;002;16;0011;0;0;0;0;0;0;0;1;5001
3129639886;3129647528;h00000000;h00000000000000;001;001;001;002;16;0011;0;0;0;0;0;0;0;1;5001
3129639887;3129647528;h00000000;h00000000000000;001;001;001;002;16;0011;0;0;0;0;0;0;0;1;5001
Primary
#Records
#Records
#Records
Search DB
Read
Matching
Not Matching
========================================================================
mufdb
2576
3
2573
DBsubquery Example 3: Displaying the Query Syntax
Figure 9, Example 3 (Screen 1): Displaying the query syntax (p. 21), Figure 10,
Example 3 (Screen 2): Displaying the query syntax (p. 22), and Figure 11, Example
3 (Screen 3): Displaying the query syntax (p. 23) show the +s option used to display
the syntax for entering queries. The query in this example searches for entries with
dntype equal to m.
...................................................................................................................................................................................................................................
401-612-168
20

Feature Description
DBsubquery
Figure 9 Example 3 (Screen 1): Displaying the query syntax

DBsubquery searches the backup copy of the subscriber database(s)
mufdb ccfdb subauxdb audb subuzdb dn2pdb laesdb p2ldndb s2pdb
for those records which either:
(a) Satisfy the "Query?" criteria, or
(b) Match those in bypass_file (if the +i option is given).
If any of the +c, +m or +u options are specified, records
meeting (a) or (b) may also be
- updated according to a set of fields & values expressed
via subsequent prompt screens,
- marked, or
- unmarked, respectively.
Both updating AND marking/unmarking operations on those records
may be requested simultaneously.
The following applies ONLY to "Query?" criteria ((a) above):
==============================================================
=> While only numeric values are used internally for matching
purposes, YES/NO values may be entered as either y or n,
or as 1 or 0, respectively.
=> DN Types may be entered as one of the letters {hatsrmdulocnpexfgbyjkqw}
for values {0-21}and {26}, respectively, or simply as a
decimal number between 0 and 255.
=> Values for certain keywords may be specified with
?, * or "null" (case-insensitive), where:
? means match on any character IN THAT
POSITION of the value string
* means match on ANY character
from the current position onward in the value string.
"null" means match on zero values for that keywords
Database field equivalent.
...................................................................................................................................................................................................................................
401-612-168
21

Feature Description
DBsubquery

EXAMPLE #1: The "Query?" expression:
billno = 123?567
matches on records with the 1st 3 characters of billno = "123",
ANYTHING in the 4th character and "567" in characters 5-7.
EXAMPLE #2: The "Query?" Expression:
ccfdgt = 630555*
matches on records with the 1st 6 digits of ccfdgt = "630555"
and ANYTHING else thereafter.
ccfbdgt = *
matches on ALL records.
Icfdgt = null
matches on records with zero in the icfdgt field.
...................................................................................................................................................................................................................................
401-612-168
22

Feature Description
DBsubquery

Values for pic must be specified with four characters
(eg, pic = 0288).
Note that a 0 is internally stored as ten,
but if a match on a true zero (null) is desired, use a -
to represent that digit (eg. pic = -288 finds all 288
pics which have not yet been expanded to true four digit 0288 pics).
If no pic is desired, null or ---- may be
specified (eg. pic = null will find all records without a pic.
=> Values for mpci may be entered as one of the following strings:
{553, 54b, 95, 136, 3388, 136a, t136a}for values {0-6},
respectively, OR
as a decimal number from 0-31.
=> Valid OP codes are =, !=, >, and <.
=> Valid BOOL codes are:
and, & (ANDing)
or, | (ORing).
Up to 11 BOOL codes (12 KW_NAME OP VALUE logic sets) are permitted.
=> Alphas in KW_NAME/VALUE/BOOL are case-insensitive.
The example below is a valid query (from a syntax perspective):
pic > nUlL & NpA = 708 Or Cw != y And icF = 0 | dntype = X
Query syntax is: [(] KW_NAME OP VALUE [)] [ [(] BOOL KW_NAME OP VALUE [)] [ . . . ]]
The entire query must be typed on one line. Enter return (or q) to quit.
Query? dntype = m
DBsubquery +f Option Feature
The +f Option feature provides a tool that allows subscriber data other than key values
to be output and provide output of the subscriber data in a flexible ASCII format that
can be used by the service provider to audit subscriber features. The +f Option feature
adds the capability for the service provider to specify the format of the output file
defining the following:
NULL character output

delimiter
which fields to print in addition to the key field
order of these fields
...................................................................................................................................................................................................................................
401-612-168
23

Feature Description
DBsubquery
This option specifies the settings of the null values, the input/output delimiters, and
fields to print. Fields are printed in the order in which they appear in the +f input
format file including msid.The fields are printed out in a fixed length format and in the
same way the values appear in the CDMA network Recent Change/Verify (RC/V)
screens.
Use of the +f Option requires a query expression to obtain the keys (msids) of
matching records. The result of the query is the key values of the matching records and
all the user specified fields in the +f Option input file printing to the output file. This
is in contrast to a query without the +f Option where only the MSID is printed.
Important! It is recommended to use this option only on the OMP due to high
volume of Input/Output (I/O) that may be required.
DBsubquery +p Option Feature (OMP only)
Like the +f Option feature, the +p Option feature provides a tool that allows subscriber
data other than key values to be output and provide output of the subscriber data in a
flexible ASCII format that can be used by the service provider to audit. In addition, it
allows the user to print private data fields, such as akey and ssd. This option requires a
changeable password. When no password has been established, the user will be
prompted for a password to encrypt! If it is desired to change the password, enter the
password, chgpwd, at the password prompt. The password file name is /etc/dbsqppwd.
Important! If the /etc/dbsqppwd is missing, it needs to be created by the user with
root permissions only.
Important! Also, when run, a major alarm message is written to the Read Only
Printer (ROP).
The +p Option feature adds the capability for the service provider to specify the format
of the output file defining the following:
NULL character output

delimiter
which fields to print in addition to the key field
order of these fields
prints restricted data
This option specifies the settings of the null values, the input/output delimiters, and
fields to print. Fields are printed in the order in which they appear in the +p input
format file including msid. The fields are printed out in a fixed length format and in
the same way the values appear in the CDMA network RC/V screens.
The +p Option does not add new fields but allows fields not normally viewable to be
printed.
...................................................................................................................................................................................................................................
401-612-168
24

Feature Description
DBsubquery
Use of the +p Option requires a query expression in order to obtain the keys (msids)
of matching records. The result of the query is the key values of the matching records
and all the user specified fields in the +p Option input file printing to the output file.
Important! Alcatel-Lucent recommends that you use this option only on the OMP
due to the high volume of input/output (I/O) that may be required.
DBsubquery Update Capable Feature
The DBsubquery Update Capable feature allows the user to change, mark, or unmark
subscriber database records that meet user-specified search criteria. These records have
matched the search criteria that the user specified at the Query? prompt or are
represented in the query bypass file. For more information on marking or unmarking,
refer to Marking/Unmarking Subscriber Records Marking/Unmarking Subscriber
Records (p. 34).
This section describes how to use the DBsubquery Update Capable feature. It covers
the following:
DBsubquery Update Capable Additional Fields feature

Using the DBsubquery Update Capable Command Line Options
Changing Field Values
Marking/Unmarking Subscriber Records
Performing a Query Bypass
Halting the DBsubquery Tool Within a Change Operation
Method of Procedures for DBsubquery Update Capable feature (ECP/OMP)
The DBsubquery Update Capable Feature allows the user to perform queries in two
ways:
Type in a logical expression, such as cgsa != 2

The tool searches the database for records that satisfy the expression.
Supply a query bypass file with user-supplied record keys.
The tool searches the database for records with keys represented in the query
bypass file.
For information on how to use the command options, refer to Using the DBsubquery
Update Capable Command Line Options Using the DBsubquery Update Capable
Command Line Options (p. 27). For information on the query bypass, refer to
Performing a Query Bypass Performing a Query Bypass (p. 34).
The DBsubquery Update Capable feature can update the fields listed in Table 21,
DBsubquery Update Capable: Values and Checks (p. 118) in subscriber records.
...................................................................................................................................................................................................................................
401-612-168
25

Feature Description
DBsubquery
After fields are chosen, the DBsubquery Update Capable feature gives the user a
chance to change the set of fields and new values entered or to halt the DBsubquery
tool. This allows the user to verify the values that they have entered and allows the
user to re-enter those values if desired.
After the values are provided, DBsubquery Update Capable feature validates the values
in each field chosen by the user. The values for a respective field must be within the
range of values shown in Table 21, DBsubquery Update Capable: Values and Checks
(p. 118). The value for NULL is 0 for all fields except the pic field, which requires the
NULL value be entered as null.
When the DBsubquery tool is invoked and any of the DBsubquery Update Capable
options are specified, a log file is created. This log file is called DBsubq_uc.log, and it
is located in the /user/DBLOG directory (ECP) and /omp-data/logs/DBLOG directory
(OMP). The log file contains the following information:
The command line that the user entered (minus the \ character)
Example: DBsubquery +vci dns_file +d;
An indication of the requested operation (for example, Marking or Unmarking)
and the run mode for the tool (for example, Update Mode or Verify-Only
Mode). If the user entered the +v (verify only) option at the command line, the
tool is running in the Verify-Only mode. Otherwise, it is running in the Update
mode.
If the user entered the +c (change) option, the set of fields that were changed and
their new values
If the user entered the +i (query bypass to read input file instead), the name of the
user-specified query bypass file and the number of record keys read from that file
A count of the number of records
that were changed, marked, or unmarked
that were not changed because they didnt meet the search criteria
that were not changed because they failed the checks described in Table 21,
DBsubquery Update Capable: Values and Checks (p. 118).
The expression typed at the Query? prompt (if applicable).
If the user includes the +v option at the command line, the numbers represent what
would have been the counts had the DBsubquery tool been run in an update mode.
Any errors found. The count of records and a brief message describing the reason
for the failed change are included in the log file.
The DBsubquery Update Capable feature runs on both the OMP and the ECP.
DBsubquery Update Capable Additional Fields Feature
The DBsubquery Update Capable Additional Fields feature adds further capabilities to
the existing DBsubquery Update Capable feature.
...................................................................................................................................................................................................................................
401-612-168
26

Feature Description
DBsubquery
Without the DBsubquery Update Capable Additional Fields feature, the DBsubquery
Update Capable feature allows the user to update only 14 fields from the subscriber
database. With this feature, more than 100 fields can be updated. To view all the fields
and their associated ranges and checks, refer to Table 21, DBsubquery Update
Capable: Values and Checks (p. 118).
Using the DBsubquery Update Capable Command Line Options
Table 2, DBsubquery Update Capable Command Line Options (p. 27) shows the
command options that are available for the DBsubquery Update Capable feature. The
Command Usage column in this table lists the rules for DBsubquery command line
option combinations.
Table 2
Option
Task It Performs/Input
Required
Command Usage
+c
Indicates that the selected

subscriber database records
(either those matching the
Query? prompt or, if +i is
used, those records represented
in the query bypass file) are to
be changed in the fields
specified by the user.
Either +u or +m can be
used with +c, but not
both. This option may also
be used with +i and +v.
Indicates that the set of

subscriber records matching
the Query? prompt (or if +i is
given, the set of records
represented in the input file)
are to be marked (if +m is
given) or unmarked (if +u is
given).
Either +m or
specified on
line, but not
options may
with +c, +i,
Indicates that the subscriber

records to be processed are
those represented in the query
bypass file instead of those
specified at the Query?
prompt.
A valid filename must be

specified, along with the
+i and at least one of the
+c, +m, or +u options. The
+v option is also allowed.
Change selected records
+m
Mark selected records

+u
Unmark selected records
+i bypass_file
Query bypass to read

bypass_file
(no Query? prompt
appears)
+u can be
the command
both. These
also be used
and +v.
A full pathname can be given

for the bypass_file. By default,
the file is assumed to reside in
the current working directory.
...................................................................................................................................................................................................................................
401-612-168
27

Feature Description
DBsubquery
Table 2
Option
Required
Command Usage
+d delim
Indicates that the query bypass

file named with the +i option
contains a delimiter character
delim separating the NPA,
NXX, and MDN values on
each line of the file. The
delimiter character delim
must be given with the +d
option with a \ character
preceding delim on the
command line if that character
is a UNIX special character.
See Table Note 1.
Use of the +d option

requires a delimiter
character and the +i
option. Delimiter
characters can not be the
digits 0 to 9, or the letter
a.
Delimiter character in
query bypass file
(continued)
Example:
DBsubquery +m +i
filename +d\;
+e
Transfer databases from

the OMP to the ECP
(works only on the
OMP)
Indicates that the databases are

to be transferred (copied) from
the current directory on the
OMP to the /1apx10/database
backup directory on the ECP.
Requires at least one of

the +c, +m, or +u options.
This option overwrites the

existing copies of the
subscriber database files
(mufdb [See Table Note 2],
ccfdb [See Table Note 2],
subauxdb, audb, p2ldndb,
s2pdb, subuzdb [See Table
Note 3], and dn2pdb) in the
ECP database backup directory.
+r
Remove selected records
Indicates that subscriber

database records marked with
+m option will be removed.
The +r option may NOT

be combined with other
+ options.
...................................................................................................................................................................................................................................
401-612-168
28

Feature Description
DBsubquery
Table 2
Option
Required
Command Usage
+v
Indicates that a verify-only run

or a trial run is desired. No
database changes are made, but
counts are made on what the
operation would have affected.
Use of the +v option

requires use of at least
one of the +c, +m, or +u
options. The +v option
can be used with the +i
option.
Verify-Only Qualifier
Example:
(continued)
DBsubquery +m +i
filename +v
+x
Transfer databases from

ECP (works only on the
OMP)
+D
Query Bypass file

contains Directory
Numbers (DNs) [default]
Indicates that the databases are

to be transferred (copied) from
/1apx10/database backup
directory on the ECP to the
current directory on the OMP.
This assumes that the OMP has
sufficient disk space to house
the databases.
May be combined with

any of the +c, +m, +u, +v,
or +i options, if desired.

file named with +i option
contains DNs. These values
can be NSNs 1 through 14
digits long, and the query
bypass file can have a mixture
of lines of differing lengths.
Requires the +i option.

The +d option may be
used (but is not required)
along with the +D. By
default, the +i query
bypass file is assumed to
contain DNs.
Note: The DNs may be

delimited by the +d delimiter
character.
+I
Query Bypass file

contains IMSIs
+M
Query Bypass file

contains Mobile
Identification Numbers
(MINs)
Denotes that the query bypass

contains the IMSI values.
These values can be 5-15
digits long and the query
bypass file can have a mixture
of lines of differing lengths.

No delimiter characters
(as in +d option) are
allowed.

contains only 10-digit MIN
values.

No delimiter characters
(as in +d option) are
allowed.
...................................................................................................................................................................................................................................
401-612-168
29

Feature Description
DBsubquery
Notes:
1.
UNIX special characters include the semicolon (;), pound sign (#), and so on.
2.
With ECP R20, if the HVLR is running on the AP server, mufdb and ccfdb have their
backup copies on the OMP. Therefore, these files are located in the /omp-data/dbbackup,
otherwise, the backup copies remain in the ECP backup directories. Beginning with ECP
R22.0, these files are located in the /omp-data/official/OFCdbbackup directory.
3.
Starting with ECP R20, if the DB Tools Migration Phase 1 feature (FID 7077) is running
on the AP server, subuzdb backup copy is kept on the OMP.
The following are command line examples:
Using query method (NO input file):

DBsubquery +c (change subscriber records only)
DBsubquery +m (mark records only)
DBsubquery +cm (change and mark records)
DBsubquery +vc (verify what changes would have occurred)
DBsubquery +vcu (verify changing and unmarking of records)
Using input file record (where the dns_file contains subscriber directory numbers
formatted WITH a specified delimiter):
DBsubquery +ci dns_file +d \;
708;713;1234
Using input file record (where the dns_file contains subscriber directory numbers
formatted WITHOUT a specified delimiter):
DBsubquery +ci dns_file
7087131234
Changing Field Values
Records that meet the search criteria can be updated within a certain set of fields by
specifying +c on the command line. This can be done by answering the appropriate
prompts in the user interface. The user interface displays a series of prompts to display
fields, choose fields, delete fields and input field value(s). Opportunities are given to
re-display fields, choose more fields, delete other fields, and change field values until
the user is satisfied. After the final fields are chosen and the values are entered, the
user is prompted to complete the transactions as shown on the screen and therefore
change the database records.
Important! In prompting for a response, the default value for the given prompt is
displayed in parenthesis as in (y/[n]) where n is the default. This is the value
taken if the user presses Return or enters an invalid value.
...................................................................................................................................................................................................................................
401-612-168
30

Feature Description
DBsubquery
Display Fields
A menu of changeable fields can be viewed by answering y to the following prompt:

Display fields to update? (y/[n]):
If y is chosen, the user is prompted to select the fields to display:

Select which fields to display (< to quit):
Valid choices are: all, an individual field number, a range of field numbers, or fields
that begin with a single alphabet letter. The following are examples:
Example:
Select which fields to display (< to quit): all
(for all fields)
Example:
Select which fields to display (< to quit): 77
(for an individual field)
Example:
Select which fields to display (< to quit): 60-100
(for a range of field
numbers)
Example:
Select which fields to display (< to quit): c
(for fields that begin with a
single alphabet letter)

At the DISPLAY=> prompt, enter the fields to display.
Screens are split to allow the user to easily view a limited number of fields at one
time. The user is prompted to continue viewing fields if they do not fit on one screen.
If all is chosen, Figure 12, Display fields screen (p. 31) appears and the user is
prompted to enter y or n to continue. The user is prompted to continue to display fields
until all the fields have been displayed.
Figure 12 Display fields screen
[1 ] acr
[2 ] apx_only
[3 ] ascp_active
[4 ] async_auth
[5 ] async_crypt
[6 ] autossd
[7 ] caldelact
[8 ] caldlalo
[9 ] ccfact
[10] ccfdt
Continue? (Y/[n])
[41
[42
[43
[44
[45
[46
[47
[48
[49
[50
]
]
]
]
]
]
]
]
]
]
icsr
ignore_esn
immbill
insnd_all
insnd_bnum
insnd_dstar
insnd_ilata
insnd_inter
insnd_loc
insnd_nodgt
[81
[82
[83
[84
[85
[86
[87
[88
[89
[90
]
]
]
]
]
]
]
]
]
]
mwi_active
omaj
paac
pgch
pgnum
pic
pin_active
pref_ev
pref_8k
pref_13k
[121]
[122]
[123]
[124]
[125]
[126]
[127]
[128]
[129]
[130]
rpin_type
sdt_active
sendtone
smsorigres
smstermres
sos_avail
so7_auth
so8_auth
so15_auth
so16_auth
...................................................................................................................................................................................................................................
401-612-168
31

Feature Description
DBsubquery
Update/Delete Fields
If the user enters y at the Display more fields? prompt, the above scenario
continues until the user chooses to stop. If the user chooses n, the following appears on
the screen:
Choose field(s) to update by entering number(s) desired at the
CHOICES=> prompt (< to quit) (examples: 1,2,3, 1,10, 15, 60,70, 71,
72)
CHOICES=>
At the CHOICES=> prompt, the list of numbers representing the desired fields (white
space is ignored) is typed, separated by a comma and terminated with a Return. If < is
typed, DBsubquery aborts immediately. If numbers are followed by a Return, the
following prompts appear:
Choose more fields? (y/[n])
Delete field(s)? (y/[n])
The Delete field(s)? (y/[n]) prompt allows the user to choose fields to delete. At
this point, if the user does not choose more fields or does not delete fields, a prompt to
enter an update value for each field chosen appears on the screen.
Example:
If the response at the CHOICES=> prompt was 1,2,3,4, then the following prompts
appear (one at a time):
Figure 13 Specify value screen
Specify
Specify
Specify
Specify
value
value
value
value
for
for
for
for
"acr": y or n (or 1 or 0, respectively):

"apx_only": y or n (or 1 or 0, respectively):
"ascp_active": y or n (or 1 or 0, respectively):
"async_auth": y or n (or 1 or 0, respectively):
Enter the desired update value after each Specify value for... prompt. Press Return
to view and answer the next Specify value for... prompt. When all the
Specify value for... prompts are answered, a final verification screen such as the
following appears:
...................................................................................................................................................................................................................................
401-612-168
32

Feature Description
DBsubquery
Figure 14 Verify value screen

You chose the following field(s) to update:
value for "acr" is 1
value for "apx_only" is 1
value for "ascp_active" is 1
value for "async_auth" is 1
Is this correct (y/[n])? (< to quit)
Answering < at the Is this correct (y/[n])? (< to quit) prompt causes
DBsubquery to abort immediately.
Answering y at the Is this correct (y/[n])? (< to quit) prompt causes
DBsubquery to verify that the update value(s) entered are allowable. If any of the
update value(s) are disallowed, error messages for each disallowed value appear and
the original changeable fields menu is displayed (giving you a chance to re-try). If all
of the update value(s) are allowed, the tool continues processing.
If n, N or anything other than y, Y, or < is typed at the
Is this correct (y/[n])? (< to quit) prompt, the original changeable fields
menu re-appears (giving you a chance to re-try).
If all values input given are valid, the user is allowed to continue to add/delete further
fields with the following prompt:
Choose more fields to update? (y/[n])
If more updates are chosen, the user is returned to the Display screen and goes through
the menus as before. Otherwise, if no more updates are chosen, the user is prompted to
continue with update. If the user chooses y, then updates are completed. If the user
chooses n, the DBsubquery aborts immediately.
One of either the +m (mark) or +u (unmark) operations (but not both) may be given
along with the +c option.
Important! The options +f, +l or +L may not be specified along with +c.
Whenever the change operation (+c) is requested and the set of fields to change and
their new values is specified, DBsubquery verifies that the changes will not cause an
inconsistency in the database for any of the records meeting the search criteria. This is
done because such inconsistencies may prevent subsequent access of the records for
update via Recent Change.
If DBsubquery finds that any changes would cause database inconsistencies, it logs the
number of such records, writing in DBsubq_uc.log a text explanation of the discovered
inconsistency. Any records meeting the search criteria and having such inconsistencies
...................................................................................................................................................................................................................................
401-612-168
33

Feature Description
DBsubquery
detected in them is not be updated. There is an exception to this rule: cpop_auth must
be set to y when cpop_act is y. The tool cannot enforce this dependency. The tool
users must ensure that these two fields are populated properly.
DBsubquery can do a trial-run of the mark (+m), unmark (+u) or change (+c)
operations if the +v option appears on the command-line. With this, no updates to the
subscriber databases are performed, but statistics on what the tool would have updated
are output.
Marking/Unmarking Subscriber Records
The DBsubquery Update Capable feature marks or unmarks those subscriber records
which the user has specified. Use the command +m to mark records and +u to unmark
records, on the command line or through an input file, that meet the search criteria.
Important! To mark the record means to make the record invisible to Recent
Change and call processing. To unmark the record means to make the record
visible again to Recent Change and call processing.
After the user enters the +m or +u option, the DBsubquery Update Capable feature
searches for the matching records in all the subscriber databases. These databases
include mufdb, ccfdb, subauxdb, audb, subuzdb, laesdb, dn2pdb, p2ldndb, and
s2pdb.
Example:
DBsubquery +m
(mark subscriber records only - query method)
DBsubquery +ui dns_file +d \; (unmark records only - use query bypass file
dns_file containing DNS delimited by the delimiter ;)
Performing a Query Bypass
The user can skip the querying phase by specifying a query bypass. To do this, the
user must supply, in the query bypass file, the set of subscriber keys or DNs that are to
be marked, unmarked, or changed. By default, the query bypass file is assumed to
contain DNs. A mark, unmark, or change command must be included with the query
bypass file on the command line.
A query bypass file must appear in one of these sample formats (in each case, only 1
key or DN value is allowed per line in the file):
DN with no delimiters [default]

Note: The +D option may accompany +i to indicate that the bypass file has DNs.
DN, with npa, nxx, mdn delimited by the delimiter character argument +d
Note: The +D option may accompany +i to indicate that the bypass file has DNs.
...................................................................................................................................................................................................................................
401-612-168
34

Feature Description
DBsubquery
10-digit MIN
Note: the +M option must accompany the +i.
IMSI values (5-15 digits, where each IMSI can be a different length)
Note: the +I option must be given along with +i.
The following examples pertain to a query bypass file of DNs:

Example:
DBsubquery +ci dns_file +d \- (change only - use delimiter -)
DBsubquery +mi dns_file +d \; (mark only - use delimiter ;)
DBsubquery +cmi dns_file +d
(change and mark - use delimiter
DBsubquery +vci dns_file +d \,(verify changes only - use delimiter ,)

DBsubquery +vcui dns_file +d\: (verify change, and unmark - delimiter
:)
See Table 2, DBsubquery Update Capable Command Line Options (p. 27) for the
command line options to use when performing a query bypass.
Halting the DBsubquery Tool Within a Change Operation
After the user has selected fields and entered values in those fields in the Final
Changeable Fields Verification screen (as previously described), the values are verified.
To quit or to return to the Changeable Fields Selection Screen, at the
Is this correct (y/n/q[quit]) [Default is n]? prompt, enter one of these
letters, depending on the action you want to take:
Enter n or N (or any character other than y, Y, q, or Q) to return to the screen to

select different fields to change.
Enter q or Q to halt DBsubquery and make no changes to the fields.
Enter y or Y to verify that the entered values are correct. If all the entered values
are found to be allowable, the tool continues to process the database records as
indicated via the command-line options (updating, and if +m or +u was given,
marking or unmarking records).
Important! If any of the entered values are not allowed, an error message for each
disallowed value appears and the user is returned to the Changeable Fields
Selection screen.
Deleting subscriber records
After the user has marked selected subscriber database records with +m option, those
records can be deleted using the +r option. Figure 15, Example output from
DBsubquery +r option (p. 36) shows an example of the +r option output.
...................................................................................................................................................................................................................................
401-612-168
35

Feature Description
DBsubquery
Figure 15 Example output from DBsubquery +r option

DBsubquery +r
Now searching for records to remove in: mufdb
5 10 15 20 25 30
Now searching for records to remove in: ccfdb
5 10 15 20 25 30
Now searching for records to remove in: subauxdb
Now searching for records to remove in: audb
Now searching for records to remove in: subuzdb
Now searching for records to remove in: dn2pdb
5 10 15 20 25 30
Now searching for records to remove in: p2ldndb
Now searching for records to remove in: s2pdb
Now searching for records to remove in: submbrdb
Now searching for records to remove in: subpltdb
SUMMARY OF UPDATE PROCESSING
#Unchanged
(no match
#Unchanged
#Records
on search
(update
DB NAME
Read
#Removed criteria)
failed)
====================================================
mufdb
34131
5109
29022
0
ccfdb
34131
5109
29022
0
*** NO RECORDS PROCESSED FOR UPDATE IN subauxdb ***
audb
2
2
0
0
*** NO RECORDS PROCESSED FOR UPDATE IN subuzdb ***
dn2pdb
34137
5113
29024
0
p2ldndb
3
2
1
0
s2pdb
20
0
20
0
*** NO RECORDS PROCESSED FOR UPDATE IN submbrdb ***
*** NO RECORDS PROCESSED FOR UPDATE IN subpltdb ***
Look in /omp-data/logs/DBLOG/DBsubq_uc.log for results of DBsubquery (Update-Capable)
processing.
NOTICE: The subscriber DBs have been modified as initially described.
DBsubquery (Update-Capable):
(Elapsed time: 4 secs)
Completed:
Tue May 15 10:56:45 2007
Important! Records are deleted after entering the DBsubquery +r command

without any request for confirmation.
...................................................................................................................................................................................................................................
401-612-168
36

Feature Description
DBsubreport.pl
Tool
...................................................................................................................................................................................................................................
Introduction
The following information describes the functionality, benefits, and operation of the
DBsubreport.pl tool introduced by the CDMA Full IMSI Feature Interactions for
MIN-Based IMSI feature (FID 12395.1) in R30.0. Refer to CDMA Full IMSI and
Related Features Optional Feature Description, 401-612-297 for the full feature
description.
Functionality
DBsubreport.pl tool is a UNIX command-line tool that generates two reports based on
data provided by DBsubquery tool:
Summary of all the unique MIN Escape Codes in the subscriber (ccf) database,
ordered by MIN Escape Code, and the number of records for each MIN Escape
Code.
Summary of all mobiles MINs and DNs corresponding to a MIN Escape code in
the Subscriber (ccf) database.
How the tool operates
The tool runs on the OMP only. Type the following to execute the DBsubreport.pl tool.
DBsubreport.pl -i input_file -o output_file [-l mec_list_file] [-h]
Table 3
Field
Definition
-i
Required option used to specify the input file name.

Example: -i input_file
input_file
The file name (may include the path to it) that contains
columns of data gotten from DBsubquery tool.
-o
Required option used to specify the output file name, which is

the first report file name.
Example: -o output_file
output_file
The file name (may include the path to it) which is the name
of the first report generated by the tool. The second report is
generated with trailing 1.
...................................................................................................................................................................................................................................
401-612-168
37

Feature Description
Table 3
DBsubreport.pl Tool
(continued)
Field
Definition
-l
Option used to limit the number of MECs in the second report

(showing all mobiles MINs and DNs corresponding to each
MIN Escape Code). If not specified, all records from input_file
are printed.
Example: -l mec_list_file
mec_list_file
The file name (may include the path to it) containing the
min_esc codes list (one per line), that the user would like to
see in the second report.
-h
Display help info.
Example use scenario
To be able to run DBsubreport.pl first user needs to dump records from subscriber
databases using DBsubquery tool. In this case, it is best to do run the DBsubquery tool
on the OMP platform because the subsequent running of the DBsubreport.pl tool may
only occur on the OMP.
First, the DBsubquery +f/+p option format file must be populated with the following
three fields: min_esc, min, and dn with a semicolon ( ; ) used as delimiter (no other
delimiter character is allowed in this case). See Figure 16, Example: DBsubquery
+f/+p option format file (p. 38) for an example of the format file content and syntax.
Figure 16 Example: DBsubquery +f/+p option format file
NULL=DELIMITER=;
min_esc;min;dn;
Secondly, the DBsubquery tool must be run on the OMP to create the input_file to be
used by the DBsubreport.pl tool. At the Query? prompt, any query expression which is
understandable by DBsubquery is acceptable. See Figure 17, Example: How to create
DBsubreport.pl input_file (p. 39) for an example of DBsubquery execution and
Query? prompt input.
...................................................................................................................................................................................................................................
401-612-168
38

Feature Description
DBsubreport.pl Tool
Figure 17 Example: How to create DBsubreport.pl input_file
DBsubquery +f format_file input_file

Query? min = 65335230??
5 10 15 20 25 30
File "input_file" created for any matched mobile #s.
Primary
#Records
#Records
#Records
Search DB
Read
Matching
Not Matching
=============================================
mufdb
34119
36
34083
Based on the command syntax used in Figure 17, Example: How to create
DBsubreport.pl input_file (p. 39), the DBsubquery results are written to a file named
input_file. That file contains the four fields. The first field is msid (or IMSI) which
DBsubquery always adds with +f/+p options (this field is not processed by
DBsubreport.pl later, so the content of this field is unimportant for this scenario). The
next fields are: min_esc, min, and dn, as requested in the DBsubquery format_file
shown in Figure 16, Example: DBsubquery +f/+p option format file (p. 38). An
example of the resulting input_file is shown in Figure 18, Example: DBsubreport.pl
input_file content (p. 40).
...................................................................................................................................................................................................................................
401-612-168
39

Feature Description
DBsubreport.pl Tool
Figure 18 Example: DBsubreport.pl input_file content
310026543213015;00011;----------;6533523015;
310026543213016;00011;----------;6533523016;
310026543213017;00011;----------;6533523017;
310026543213018;00011;----------;6533523018;
310026543213019;00011;----------;6533523019;
310026543213020;00022;----------;6533523020;
310026543213021;00022;----------;6533523021;
310026543213022;00022;----------;6533523022;
310026543213023;00022;----------;6533523023;
310026543213024;00022;----------;6533523024;
310026543213025;00022;----------;6533523025;
310026543213026;00022;----------;6533523026;
310026543213027;00022;----------;6533523027;
310026543213028;00022;----------;6533523028;
310026543213029;00022;----------;6533523029;
310026543213030;00033;6533523030;6533523030;
310026543213031;00033;6533523031;6533523031;
310026543213032;00033;6533523032;6533523032;
310026543213033;00033;6533523033;6533523033;
310026543213034;00033;6533523034;6533523034;
310026543213035;00033;6533523035;6533523035;
310026543213036;00033;6533523036;6533523036;
310026543213037;00033;6533523037;6533523037;
310026543213038;00033;6533523038;6533523038;
310026543213039;00033;6533523039;6533523039;
310026543213040;00044;6533523040;6533523040;
310026543213041;00044;6533523041;6533523041;
310026543213042;00044;6533523042;6533523042;
310026543213043;00044;6533523043;6533523043;
310026543213044;00044;6533523044;6533523044;
310026543213045;00044;6533523045;6533523045;
310026543213046;00044;6533523046;6533523046;
310026543213047;00044;6533523047;6533523047;
310026543213048;00044;6533523048;6533523048;
310026543213049;00044;6533523049;6533523049;
123456789012345;-----;----------;1234567890;
After the input_file is created, the DBsubreport.pl tool may be run.
...................................................................................................................................................................................................................................
401-612-168
40

Feature Description
DBsubreport.pl Tool
Important! The DBsubreport.pl tool works only on data provided in the input_file,
so it does not matter if the input_file is provided by DBsubquery or some other
tool. Only the format of the input_file content is important, so DBsubreport.pl does
not directly need any subscriber databases in order to run.
See Figure 19, Example: DBsubreport.pl execution (p. 41).
Figure 19 Example: DBsubreport.pl execution
DBsubreport.pl -i input_file -o output_file

reading input file ...
printing to output file output_file
printing to output file output_file1
The DBsubreport.pl tool creates two files with the reports in its output. The name of
the second file is created by adding a trailing 1 (one) to the name of the first file.
The first report (output_file) is a short summary of all the records, in which each line
includes the ordered unique min_esc code with corresponding numbers of records
(found in the input_file). The second report (output_file1) is a detailed report in which
content is grouped by unique min_esc codes listing all the records (with min and dn
fields) for each. For examples of tool output, see Figure 20, Example: output_file
content (p. 41) and Figure 21, Example: output_file1 content (p. 42).
Figure 20 Example: output_file content
min_esc
-------------00011
00022
00033
00044
#
---------1
5
10
10
10
-------------------------Total records
36
...................................................................................................................................................................................................................................
401-612-168
41

Feature Description
DBsubreport.pl Tool
Figure 21 Example: output_file1 content

min_esc
---------
min
----------
dn
----------
-----
----------
1234567890
00011
----------------------------------------------
6533523015
6533523016
6533523017
6533523018
6533523019
00022
-------------------------------------------------------------------------------------------
6533523020
6533523021
6533523022
6533523023
6533523024
6533523025
6533523026
6533523027
6533523028
6533523029
00033
6533523030
6533523031
6533523032
6533523033
6533523034
6533523035
6533523036
6533523037
6533523038
6533523039
6533523030
6533523031
6533523032
6533523033
6533523034
6533523035
6533523036
6533523037
6533523038
6533523039
00044
6533523040
6533523041
6533523042
6533523043
6533523044
6533523045
6533523046
6533523047
6533523048
6533523049
6533523040
6533523041
6533523042
6533523043
6533523044
6533523045
6533523046
6533523047
6533523048
6533523049
The syntax used in Figure 19, Example: DBsubreport.pl execution (p. 41) causes the
tool to print all the input_file content. However, the number of records can be limited
on two levels: in DBsubquery (by specifying a range at the Query? prompt), and in
the DBsubreport.pl tool using the -l option.
...................................................................................................................................................................................................................................
401-612-168
42

Feature Description
DBsubreport.pl Tool
Figure 22, Example: mec_list_file content (p. 43) shows an example of the
mec_list_file content included when the user wants to limit output_file1 content to two
min_esc codes only: 00033 and 00044.
Figure 22 Example: mec_list_file content
00033
00044
Running DBsubreport.pl -i input_file -o output_file l mec_list_file,

creates output_file1 with content like shown in Figure 23, Example: output_file1
content (with l option used) (p. 43). The first report, output_file, remains the same as
shown in Figure 20, Example: output_file content (p. 41) as it is not impacted by the
-l option.
Figure 23 Example: output_file1 content (with l option used)
min_esc
---------
min
----------
dn
----------
00033
6533523030
6533523031
6533523032
6533523033
6533523034
6533523035
6533523036
6533523037
6533523038
6533523039
6533523030
6533523031
6533523032
6533523033
6533523034
6533523035
6533523036
6533523037
6533523038
6533523039
00044
6533523040
6533523041
6533523042
6533523043
6533523044
6533523045
6533523046
6533523047
6533523048
6533523049
6533523040
6533523041
6533523042
6533523043
6533523044
6533523045
6533523046
6533523047
6533523048
6533523049
Invoking the DBsubreport.pl help option
To obtain help on DBsubreport.pl tool, type the following command on the OMP:
DBsubreport.pl h
The DBsubreport.pl command usage displays.

...................................................................................................................................................................................................................................
401-612-168
43

Feature Description
DBsubsum
Tool
...................................................................................................................................................................................................................................
Introduction
The following information describes the functionality, benefits, and operation of the
DBsubsum Tool.
Functionality
DBsubsum Tool is a UNIX command-line tool that produces a summary of the

contents of the Mobile Unit Features Database (mufdb).
Benefits
Generated as a regular report, the summary produced by the DBsubsum Tool can be
used to spot irregularities in subscriber configuration. Once such an irregularity is
detected, the corresponding subscriber record or records can be identified using the
DBsubsearch or the DBsubquery tool.
How the feature operates
Type the following to execute the DBsubsum tool.

DBsubsum [+xmicaw]
or
DBsubsum [-hxmicaw],
to get help
Important! Before running the DBsubsum tool on the OMP, the user must be in
the current directory where the databases reside.
The tool prints a brief summary of the searchs results to the screen (See Figure 24,
Example of DBsubsum Screen Output (p. 45)). Refer to Table 4, DBsubsum Field
Definitions (p. 44) for field definitions for Figure 24, Example of DBsubsum Screen
Output (p. 45).
Important! The 15 Digit DN feature is not compatible with DBsubsum. Therefore,
there are no impacts on the DBsubsum tool as a result of the 15 Digit DN feature.
Table 4
Field
Definition
+x
Transfer mufdb to current directory on OMP.
+m
Print summary of MSIDs over first 6 characters in addition to features

printed.
Note: Absence of the +i or +m gives a default of the summary of
NPA-NXXs in addition to the feature summaries.
...................................................................................................................................................................................................................................
401-612-168
44

Feature Description
Table 4
DBsubsum Tool
(continued)
Field
Definition
+i
Print summary of IMSIs over first 8 characters in addition to features

printed print.
Note: Absence of the +i or +m gives a default of the summary of
NPA-NXXs in addition to the feature summaries.
+c
Summarizes features in the ccf database. Optional field.
+a
Summarizes features in the subaux database. Optional field.
+w
Prints summary counts of subscribers with the WIN Trigger Index Counts
report.
The complete results are written to a file named DBsubsum.log. An example is shown
in the following figures.
Figure 24 Example of DBsubsum Screen Output
Dbsubsum
DBsubsum:
DBsubsum:
DBsubsum:
DBsubsum:
DBsubsum:
DBsubsum:
DBsubsum:
DBsubsum:
DBsubsum:
DBsubsum:
DBsubsum:
DBsubsum:
DBsubsum:
DBsubsum:
DBsubsum:
DBsubsum:
DBsubsum:
DBsubsum:
DBsubsum:
Execution Status:
00000
00001
00001
00002
00003
00003
00004
00005
00005
00006
00006
00006
00007
00007
00007
00008
00008
00008
second
second
second
second
second
second
second
second
second
second
second
second
second
second
second
second
second
second
update:
update:
update:
update:
update:
update:
update:
update:
update:
update:
update:
update:
update:
update:
update:
update:
update:
update:
Checked,
In Use,
Counted,
25000,
50000,
75000,
100000,
125000,
150000,
175000,
200000,
225000,
25000,
50000,
75000,
100000,
125000,
150000,
175000,
200000,
225000,
25000,
50000,
75000,
100000,
125000,
150000,
175000,
200000,
225000,
25000,
50000,
75000,
100000,
125000,
150000,
175000,
200000,
225000,
25000,
50000,
75000,
100000,
125000,
150000,
175000,
200000,
225000,
25000,
50000,
75000,
100000,
125000,
150000,
175000,
200000,
225000,
Marked
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
DBsubsum: Started: Fri Jun 25 15:31:56 2004
Important! On the OMP, the directory path in the DBsubsum.log file is the path
from where DBsubsum is executed. For example, if mufdb is under /usr/tmp and
DBsubsum is executed from /usr/tmp, the output path is /usr/tmp/mufdb.
...................................................................................................................................................................................................................................
401-612-168
45

Feature Description
DBsubsum Tool
Invoking the DBsubsum help option
To obtain help on the DBsubsum tool, enter the following command:

DBsubsum -h
The DBsubsum command usage displays.

DBsubsum screen output
The following are the screen outputs:

#Records:
The total number of records for which disk space has been allocated. If
subscriber records have been deleted, some of these records may be empty until the
space is reused by new subscribers.
#In Use:
The total number of records that actually contain subscriber data (are not
empty).
#Unused:
The number of counted records that are currently unused. These are
typically records which have been deleted.
#Counted:
The number of records that are used to create the summary.
Bad Keys:
The number of subscriber records that contain marked keys. Marked

keys are hidden from view by Recent Change and call processing.
Bad Sw #s:
Time:
The number of references to switches that are not in the range 1-16.
The length of time that DBsubsum required to generate this log file.
DBsubsum.log file contents

Summary of mufdb record processing:
Summary of mufdb records processed.
Mobile Subscriber Feature Summary:
This is a list of subscriber features,

including a breakdown of how many subscribers have each feature and how many
do not. A very small number of subscribers (fewer than 10) in the Y column for
any feature probably indicates subscribers who are mistakenly assigned features
that are not offered. Similarly, a very small number of subscribers in the N
column may indicate features that are part of your organizations standard service,
but are denied to a few by mistake.
...................................................................................................................................................................................................................................
401-612-168
46

Feature Description
DBsubsum Tool
Figure 25 DBsubsum Output Example (Part 1)

Summary of mufdb record processing:
#Records: 229666 (644 blocks)
#In Use: 229666 (of 229666)
#Unused:
0
#Counted: 229666
# Marked:
0
Bad Sw#s:
0
Time:
5 seconds
Mobile Subscriber Feature Summary
Feature
#With (=Y) #Without (=N)
acr
=
0
allow_5dgt_pcc=
0
allow_intl_roam= 154101
anfx_auth
=
2
Anfx_crypt
=
1
apx_only
=
0
ascp_active
=
0
async_auth
= 202395
async_crypt
=
4
audb_exists
=
5
caldlalo
=
2572
ccf_no_ad
=
0
ccf_svc_ord
=
0
ccfb_no_ad
=
0
Ccfb_svc_ord =
0
ccfbbmrs
=
0
ccfbmrs
=
0
cdpd_crypt
=
0
cfbl
=
0
cfd_ihlr
=
02217
Cfd_noad
=
0
cfd_svcord
=
0
cfda
= 202265
cfnpr
= 202256
cnap
=
0
cp_authct
=
24
229666
229666
75565
229664
229665
229666
229666
27271
229662
229661
227094
229666
229666
229666
229666
229666
229666
229666
229666
227449
229666
229666
27401
27410
229666
229642
...................................................................................................................................................................................................................................
401-612-168
47

Feature Description
DBsubsum Tool

cp_fixedsub
cp_rorane
cpnd
cpnr
cw
cwar
dnd_auth
enhccf
exmin
fa_skip
fax_auth
fax_crypt
fldpg
fltr_is41_oi
forced
ftc_dtmf
Ftc_tntype
ghost
glsfeatctl
glsregnot
hli3d
homeonly
icf
icf_no_ad
icf_svc_ord
icfab
ignore_esn
insnd_10dgts
insnd_11dgts
insnd_12dgts
insnd_13dgts
insnd_14dgts
insnd_15dgts
insnd_1dgt
insnd_1rsv
insnd_2dgts
insnd_2rsv
insnd_3dgts
insnd_3rsv
insnd_4dgts
insnd_5dgts
insnd_5rsv
Insnd_6dgts
insnd_7dgts
insnd_8dgts
insnd_9dgts
insnd_all
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
0
0
203390
8076
221356
229545
0
229665
7668
0
202398
5
3023
0
2
0
0
9418
0
1
0
54
209676
0
0
209699
0
1
1
1
1
1
1
1
0
55
0
1
0
56
56
0
55
1
55
1
0
229666
229666
26276
221590
8310
121
229666
1
221998
229666
27268
229661
226643
229666
229664
229666
229666
220248
229666
229665
229666
229612
19990
229666
229666
19967
229666
229665
229665
229665
229665
229665
229665
229665
229666
229611
229666
229665
229666
229610
229610
229666
229611
229665
229611
229665
229666
...................................................................................................................................................................................................................................
401-612-168
48

Feature Description
DBsubsum Tool

insnd_inter
insnd_loc
insnd_nodgt
insnd_olata
insnd_pound
insnd_rtvc
insnd_star
ip_crypt
lcr
mas_auth
mbillalw
mp_act
mrs
mwi_active
p_arl
paac
pgch
pin_active
ppdn
projacc
psofpr
q_arl
rasa
rfc_asn
rpin_type
sdt_active
so15_auth
so16_auth
so33_auth
so7_auth
so8_auth
spanc_active
spina_home
spina_roam
stol_unit
sub_coi
sub_ocoi
subaux_exists
sui
trig_pro
twc
vad_auth
vp_active
vp_netinit
wac_bc_auth
wac_conf_auth
win_att
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
1
2
1
1
1
1
1
0
0
209682
0
0
185759
172736
0
0
0
12673
0
0
0
0
0
0
43704
0
0
0
56754
1
0
0
0
0
0
0
229666
1
0
1
209434
0
4
0
0
0
0
Primary Rate Center:
229665
229664
229665
229665
229665
229665
229665
229666
229666
19984
229666
229666
43907
56930
229666
229666
229666
216993
229666
229666
229666
229666
229666
229666
185962
229666
229666
229666
172912
229665
229666
229666
229666
229666
229666
229666
0
229665
229666
229665
20232
229666
229662
229666
229666
229666
229666
The number of subscribers assigned to each rate center.
Cellular Geographic Service Areas
The number of subscribers assigned to
each CGSA.
Routing Class Summary:
Dialing Class:
The number of subscribers in each routing class.
The number of subscribers in each dialing class.
...................................................................................................................................................................................................................................
401-612-168
49

Feature Description
DBsubsum Tool

Primary Rate Center
1
229666
Cellular Geographic Service Areas

4
229666
Routing Class Summary

7
10
Dialing Class:
0
1
4
5
7
10
22
125
128
205
229664
2
#dc1
#dc2
227840
1
0
0
0
0
0
1811
0
14
0
1
148239
1
72002
1
9420
0
1
0
Directory Number Types
The number of subscribers with each MIN type.

Directory Number Types
h
a
r
u
l
o
p
x
b
y
229589
3
19
1
7
2
4
1
3
37
Major Classes:
The number of Subscribers in each Originating, Terminating, and

Visited Major Class.
...................................................................................................................................................................................................................................
401-612-168
50

Feature Description
DBsubsum Tool

Major Classes:
0
1
2
5
8
11
14
15
138
Orig
0
1842
1851
412
2
225455
101
2
1
Term
Visited
0
227808
1857
0
0
0
0
0
1
220102
6
431
9125
0
2
0
0
0
Presubscribed InterLATA Carrier Assignments:
Summary of subscribers by
preferred long distance carrier assignment.

Presubscribed InterLATA Carrier Assignments
Null
0001
0211
0222
0223
0288
0333
0432
0444
0555
0732
0777
0850
0873
5050
9999
14
9
1
366
1
11
2447
3
7
6
11
2
1
2
226782
3
Automatic Call Trace Value Distribution:
Summary of subscribers whose

calls are traced by the call tracing value assigned to them.
Message Recording Service Index Summary:
Summary of subscribers using
MRS, listed by MRS index.

Position Det Cap:
Summary of the mobiles with the position determination
capability.
...................................................................................................................................................................................................................................
401-612-168
51

Feature Description
DBsubsum Tool
Immediate Billing Index Summary:
Summary of subscribers with immediate
billing, listed by group number.

Special Routing Summary:
Summary of subscribers with special routing.
Court Ordered Surveillance:
The number of subscribers that are under Court
Ordered Surveillance.
Automatic Call Trace Value Distribution
None Found
Message Recording Service Index Summary
3
4
5
7
1
1
29
221644
Position Det Cap:

0
1
0
229666
91084
138582
91084
138582
Immediate Billing Index Summary

101
Special Routing Summary

None Found
Court Ordered Surveillance
None Found
Mobile Serial Number Manufacturer Code Distributions:
A breakdown of
subscribers by the manufacturer code of their mobiles. The left column shows the
number of mobiles with each manufacturer code. The middle column shows each
code in decimal, hexadecimal, and octal form. On the right is the name of the
manufacturer corresponding to each code.
Note that more manufacturer codes have been added and old ones replaced by the
current manufacturer mobile code license. This will result in fewer unknown
manufacturer mobiles.
...................................................................................................................................................................................................................................
401-612-168
52

Feature Description
DBsubsum Tool

Mobile Serial Number Manufacturer Code Distributions
17
106
1
2
1
138
6323
5503
19436
16585
8771
824
1782
7
1546
571
26279
3379
1
16539
4
10
1504
590
4132
4749
1767
1
16793
1
1
129
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
0
2
10
11
22
53
61
63
66
68
69
72
74
76
78
81
82
83
85
93
94
96
97
99
100
101
102
103
104
106
108
110
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
0x00
0x02
0x0a
0x0b
0x16
0x35
0x3d
0x3f
0x42
0x44
0x45
0x48
0x4a
0x4c
0x4e
0x51
0x52
0x53
0x55
0x5d
0x5e
0x60
0x61
0x63
0x64
0x65
0x66
0x67
0x68
0x6a
0x6c
0x6e
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
o000
o002
o012
o013
o026
o065
o075
o077
o102
o104
o105
o110
o112
o114
o116
o121
o122
o123
o125
o135
o136
o140
o141
o143
o144
o145
o146
o147
o150
o152
o154
o156
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
"Invalid"
"Invalid"
"Invalid"
"Invalid"
"Invalid"
"LG ELECTRONICS INC."
"MOTOROLA"
"SAMSUNG TELECOMMUNICATIONS AMERICA INC."
"MOTOROLA"
"LG ELECTRONICS"
"KYOCERA WIRELESS CORPORATION"
"NOKIA MOBILE PHONES"
"RESEARCH IN MOTION"
"SAMSUNG TELECOMMUNICATIONS AMERICA, INC."
"MOTOROLA"
"NOKIA"
"MODOTTEL CO., LTD."
"TOSHIBA AMERICA INFORMATION SYSTEMS"
"NOKIA"
"AIR PRIME INC."
"CURITEL COMMUNICATIONS, INC."
"SIERRA WIRELESS, INC."
"SAMSUNG ELECTRONICS CO., LTD."
"ERICSSON INC."
"VACOM WIRELESS, INC."
"MOTOROLA INC. CELLULAR SUBSCRIBER"
"ANYDATA.NET"
"NOKIA"
...................................................................................................................................................................................................................................
401-612-168
53

Feature Description
DBsubsum Tool

1
1
559
12
6099
3553
17
1002
43
366
12
10
27
29
12
6190
7757
24
101
1
3
6
199
48
1
2949
4965
12
34
192
9727
82
1
250
312
5
1
2645
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
111
114
115
116
117
119
125
128
129
130
131
133
134
135
136
138
141
142
146
148
150
154
156
157
158
159
160
162
164
165
168
172
173
174
175
176
178
179
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
0x6f
0x72
0x73
0x74
0x75
0x77
0x7d
0x80
0x81
0x82
0x83
0x85
0x86
0x87
0x88
0x8a
0x8d
0x8e
0x92
0x94
0x96
0x9a
0x9c
0x9d
0x9e
0x9f
0xa0
0xa2
0xa4
0xa5
0xa8
0xac
0xad
0xae
0xaf
0xb0
0xb2
0xb3
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
o157
o162
o163
o164
o165
o167
o175
o200
o201
o202
o203
o205
o206
o207
o210
o212
o215
o216
o222
o224
o226
o232
o234
o235
o236
o237
o240
o242
o244
o245
o250
o254
o255
o256
o257
o260
o262
o263
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
"TELIRAN"
"ERICCSON, INC."
"QUALCOMM, INCORPORATED"
"LG INFORMATION & COMMUNICATIONS, Ltd"
"MOTOROLA, INC."
"STANDARD TELECOM CO., LTD."
"MEID mobile"
"OKI"
"MOTOROLA"
"E. F. JOHNSON"
"FUJITSU"
"MITSUBISHI"
"NEC"
"MATSUSHITA (PANASONIC)"
"TOSHIBA"
"GOLDSTAR PRODUCTS CO., LTD"
"INTERNATIONAL SYSTCOM (NOVATEL)"
"ERICCSON INC."
"ROBERT BOSCH CORPORATION (BLAUPLUNKT)"
"ALPINE ELECTRONICS OF AMERICA"
"SONY CORPORATION (JAPAN)"
"MOBIRA (Nokia-Kinex)"
"ERICSSON GE MOBILE COMMUNICATIONS, INC."
"AT&T TECHNOLOGIES, INC."
"KYOCERA WIRELESS CORP."
"HYUNDAI"
"TECHNOPHONE LIMITED"
"HUGHES NETWORK SYSTEMS"
"TMC COMPANY LIMITED (NOKIA)"
"MOTOROLA INTERNATIONAL"
"UNIDEN CORPORATION OF AMERICA"
"UNIDEN CORPORATION OF JAPAN"
"SHINTOM WEST CORPORATION OF AMERICA"
"TOTTORI SANYO ELECTRIC CO. LTD."
"SAMSUNG COMMUNICATIONS"
"EMPTEL ELECTRONICS COMPANY LTD."
"KYOCERA WIRELESS CORP.
...................................................................................................................................................................................................................................
401-612-168
54

Feature Description
DBsubsum Tool

1
16
5
7
1175
1615
12
1
31
436
832
3
1
5669
1942
1866
1906
206
1
10
150
1763
525
8124
41
72
1
1512
161
17844
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
186
189
191
193
195
201
206
208
211
212
213
214
216
218
219
223
224
226
228
233
235
237
241
242
247
248
251
252
253
254
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
0xba
0xbd
0xbf
0xc1
0xc3
0xc9
0xce
0xd0
0xd3
0xd4
0xd5
0xd6
0xd8
0xda
0xdb
0xdf
0xe0
0xe2
0xe4
0xe9
0xeb
0xed
0xf1
0xf2
0xf7
0xf8
0xfb
0xfc
0xfd
0xfe
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
o272
o275
o277
o301
o303
o311
o316
o320
o323
o324
o325
o326
o330
o332
o333
o337
o340
o342
o344
o351
o353
o355
o361
o362
o367
o370
o373
o374
o375
o376
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
"DNC"
"NEC AMERICA, INC."
"DIGITAL SECURITY CONTROLS"
"MATSUSHITA COMM.INDUSTRIAL CORP. OF AMERICA"
"MOTOROLA, INC."
"L.G. INFORMATION & COMMUNICATIONS"
"SIERRA WIRELESS INC."
"JRC INTERNATIONAL INC."
"SONY ELECTRONICS (USA)"
"MOTOROLA, INC."
"MOTOROLA, INC."
"STANDARD COMMUNICATIONS CORP."
"NIPPONDENSO AMERICA, INC."
"NOKIA (HONG KONG)"
"NOKIA (TMC CO. LTD)"
"MOTOROLA, INC."
"MOTOROLA, INC."
"NOKIA (Manau, Brazil)"
"PHILLIPS CONSUMER COMMUNICATIONS"
"MOTOROLA"
"TOSHIBA AMERICA INFORMATION SYSTEMS,INC."
"SANYO Electric Corporation Limited"
"ERICSSON, INC."
"GARMIN INTERNATIONAL"
"MOTOROLA"
"KYOCERA WIRELESS CORP."
MEID Distribution by hexidecimal Manufacturer Code:
This section lists all

4-byte manufacturer codes found within the MEID field of subscriber records,
followed by a count of subscribers having each manufacturer code. The blank
MEID field entry shows the number of subscribers for which no MEID is
populated.
CDMA Modes of Service Allowed:
The number of subscribers allowed each
mode of service.
Pin Types:
The number of subscribers with each pin type.
WIN Triggered Service Index [1-255] Counts:
The WIN Trigger Index

Counts report provides a matrix of WIN services [1-10] and a count of the number
of times a service index [1-255] has been assigned.
Summary of ccfdb record processing:
Summary of records from the ccf
database.
...................................................................................................................................................................................................................................
401-612-168
55

Feature Description
DBsubsum Tool

MEID Distribution by hexidecimal Manufacturer Code
42 23
00 00
00 00
blank
00 00
af 34
23 bd
MEID
14
897
81
228674
CDMA Mode(s) of Service Allowed

n
d
Pin Types:
0
4
21915
207751
Home
Roam
226685
2981
218740
10926
WIN Triggered Service Index [1-255] Counts:

Index Srv[1] Srv[2] Srv[3] Srv[4] Srv[5] Srv[6] Srv[7] Srv[8] Srv[9] Srv[10] Totals
2
1
0
0
0
0
0
0
0
0
0
1
Summary of ccfdb record processing:
#Records: 230124 (541 blocks)
#In Use: 230124 (of 230124)
#Unused:
0
#Counted: 230124
# Marked:
0
Time:
3 seconds
Mobile Subscriber Feature CCF Summary:
Summary of features from the ccf
database.
...................................................................................................................................................................................................................................
401-612-168
56

Feature Description
DBsubsum Tool

Mobile Subscriber Feature CCF Summary
Feature
#With (=Y) #Without (=N)
alwarg
an800vce
asdtmfc_act
att
auth_cnt_rcv
below_lsp
caldelact
callreg
cap_3g1x
ccf
ccf_iddd
ccfb
ccfb_iddd
cd
cfd_act
cfd_iddd
cp_arcap
cp_ct
cp_salsa
crbt_act
dnd_act
docr_block
enh_rc
guts_wi
mas_isdst
mas_multiloc
mitmrt_act
ota_wi
otapa_cap
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
5
59083
0
1
224048
0
228159
6720
202961
190
1
190
1
4634
0
0
227633
16
0
0
0
0
99988
0
117651
0
1
0
170637
230119
171041
230124
230123
6076
230124
1965
223404
27163
229934
230123
229934
230123
225490
230124
230124
2491
230108
230124
230124
230124
230124
130136
230124
112473
230124
230123
230124
59487
...................................................................................................................................................................................................................................
401-612-168
57

Feature Description
DBsubsum Tool
pcs_cap
pin_isdst
pref_13k
qpch_sup
rvr_isdst
rvr_timeout
sendtone
serv_stat
sms_wi
sos_avail
spina_fsc
ssdconf_nrcv
Tbusy
tnoanswer
trigless_flag
uzserv
valssd
vman_mail
vman_option
wac_bc_act
wac_conf_act
win_icdd
SMS Restriction:
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
0
8540
287
99988
0
0
0
0
1626
145
0
95
1537
1
0
0
213718
36787
0
0
0
0
230124
221584
229837
130136
230124
230124
230124
230124
228498
229979
230124
230029
228587
230123
230124
230124
16406
193337
230124
230124
230124
230124
Summary of mobiles with SMS origination and/or termination
restrictions.
Vocoder Pref:
Summary of mobiles with preferred 8K/EVRC/SMV vocoder
selection.
Special Routing Selection:
Summary of mobiles allocated to selectable special
routing.
Mobile Protocol Revision:
Summary of mobiles protocol revisions of all

mobiles, broken down according to the revision number.
...................................................................................................................................................................................................................................
401-612-168
58

Feature Description
DBsubsum Tool
SMS Restriction:Orig
y
n
Vocoder Pref:
0
1
2
3
Term
27070
203054
8K
12378
217746
EVRCSMV
230011
0
3
110
229982
142
0
0
230124
0
0
0
Special Routing Selection

0
230124
Mobile Protocol Revision

0
1
2
3
4
5
6
7
12
16
22
26
29
32
33
50
53
76
87
99
154
221
222
47147
1
1
102747
9756
1
70449
1
3
1
3
2
1
2
1
1
1
1
1
1
1
1
1
...................................................................................................................................................................................................................................
401-612-168
59

Feature Description
DBsubsum Tool
MUSDN Customer Changeable Primary ESN:
Summary of mobiles with Mobile

Unit Switchable Directory Number (MUSDN) feature enabled.
Summary of subauxdb record processing:

the subaux database.
LSA Users:
Summary of subauxdb records from
Summary of mobiles with the Limited Service Area (LSA) feature
enabled.
MUSDN Customer Changeable Primary ESN

0
230124
Summary of subauxdb record processing:

#Records:
#In Use:
#Unused:
#Counted:
Time:
1 (1 blocks)
0 (of 1)
1
0
0 seconds
LSA Users:
Active
0
Non-Active
0
Mobile Subscriber Distributions by NPA-NXX and Switch:
A breakdown of
subscribers by NPA-NXX and the switches that are homed on.
...................................................................................................................................................................................................................................
401-612-168
60

Feature Description
DBsubsum Tool

Mobile Subscriber Distributions by NPA-NXX and Switch
1. 401-486
2. 401-439
3. 401-374
4. 401-741
5. 401-258
6. 401-529
7. 781-820
8. 774-218
9. 401-862
10. 401-487
11. 401-578
12. 401-959
13. 508-243
14. 401-524
15. 401-447
16. 781-910
17. 401-465
18. 774-991
19. 781-248
20. 401-595
21. 401-742
22. 401-474
23. 774-644
24. 508-230
25. 401-378
26. 774-254
27. 401-792
28. 401-480
29. 401-864
30. 508-240
31. 508-457
32. 774-571
33. 401-842
34. 401-458
35. 401-848
36. 100-102
37. 617-422
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
9820
9307
9839
9797
9671
9794
9823
5625
9794
9824
9821
1
9622
9855
9752
9819
9818
1124
9847
8562
9823
9790
3048
433
8293
2602
199
9742
9534
380
267
2250
516
760
96
29
55
Sw_04=9820
Sw_04=9090
Sw_04=9839
Sw_04=9797
Sw_04=9366
Sw_04=9794
Sw_10=9823
Sw_04=2
Sw_04=9794
Sw_04=9824
Sw_04=9821
Sw_04=1
Sw_10=9622
Sw_04=9855
Sw_04=9752
Sw_10=9819
Sw_04=9818
Sw_10=1124
Sw_10=9847
Sw_04=8553
Sw_04=9823
Sw_04=9790
Sw_10=3048
Sw_10=433
Sw_04=8287
Sw_10=2602
Sw_04=199
Sw_04=9742
Sw_04=9524
Sw_10=380
Sw_10=267
Sw_10=2250
Sw_04=516
Sw_04=760
Sw_04=96
Sw_10=29
Sw_10=55
Sw_10=87
Sw_15=130
Sw_10=181
Sw_15=124
Sw_10=5610
Sw_15=13
Sw_15=9
Sw_15=6
Sw_15=10
...................................................................................................................................................................................................................................
401-612-168
61

Feature Description
DBsubsum Tool

38.
39.
40.
41.
42.
43.
44.
45.
46.
47.
48.
49.
50.
51.
52.
53.
54.
55.
56.
57.
58.
59.
60.
61.
62.
63.
508-228
315-430
508-430
401-829
617-457
617-429
506-866
765-427
917-617
317-431
000-000
506-467
508-289
506-466
914-629
201-280
724-388
508-959
506-636
506-650
908-705
540-894
206-437
561-252
941-218
401-297
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
62
1
154
63
21
8
1
1
3
1
4
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
Subscriber Totals by Switch:
Sw_10=62
Sw_10=1
Sw_10=154
Sw_04=63
Sw_10=21
Sw_10=8
Sw_10=1
Sw_10=1
Sw_10=3
Sw_10=1
Sw_10=3
Sw_10=1
Sw_10=1
Sw_10=1
Sw_10=1
Sw_10=1
Sw_10=1
Sw_10=1
Sw_10=1
Sw_10=1
Sw_10=1
Sw_10=1
Sw_10=1
Sw_10=1
Sw_10=1
Sw_04=1
Sw_15=1
The number of subscribers homed on each
switch.
Subscriber Totals by Switch
Sw_04 = 173927
Sw_10 = 55446
Sw_15 = 293
TOTAL = 229666
DBsubsum: Completed: Fri Jun 25 15:32:04 2004 (Elapsed time: 8 secs)
...................................................................................................................................................................................................................................
401-612-168
62

Feature Description
DBsubsum Tool
DB Tools Migration Phase 1
The DB Tools Migration Phase 1 (FID 7077) supports
the migration of the subuzdb backup files to the OMP when Database Evolution
Support for FMM-Application Processors (DBMS-APs) is integrated into the MSC.
the migration of the ccfdb and mufdb backup files to the OMP when Home Visitor
Location Registration-APs (HVLR-APs) is integrated into the MSC.
With ECP Release 20.0 and later, the subuzdb, ccfdb and mufdb backup files are
written to the following OMP directory: /omp-data/dbbackup and not to the ECP
database backup directory. Beginning with ECP Release 22.0, these files are located in
the /omp-data/official/OFCdbbackup directory.
The backup locations of the other databases remain in the ECP directory.
As a result of the DB Tools Migration Phase 1, the backup file that is referred to as
/1apx10/dbbackup is now replaced by database backup directory.
...................................................................................................................................................................................................................................
401-612-168
63

Feature Description
Special
Considerations
...................................................................................................................................................................................................................................
Introduction
This section describes the subscriber perspective, service provider perspective, and
caveats of the DBsubquery feature.
Service Provider Perspective
The size of the databases being queried (smaller is faster) may influence the time
required for each option to execute. The number of fields that are being printed affects
how long the DBsubquery +f /+p Option(s) take to execute and the space required.
RC/V activity is not an issue for the DBsubquery feature.
Service providers can use DBsubquery Update Capable to perform marking,
unmarking, and updating operations on the following:
typical subsets of the subscriber database (such as all subscribers within a certain
NPA range, for example: npa = 708)
hard to find subsets of the subscriber database (such as any subscribers with
dntype = s)
Subsets of the subscriber database that are represented in a query bypass file.
Queries Involving Disk Databases
All of the database tools covered in this document can be executed only on the backup
copies of disk databases.
Caveats
The user should be aware of the following:
Users must have root permissions to run the +p Option. Also, the +p Option runs
only on the OMP.
Users must have root permissions to run in update mode (that is, without using
the +v option) and perform mark, unmark, or change operations. Users do not need
root permissions to do any of those operations in verify-only mode (that is, with
the +v option).
If running the DBsubquery Update Capable feature on the OMP with the +x option,
ensure that there is sufficient file space in the present working directory to hold all
of the subscriber database files.
...................................................................................................................................................................................................................................
401-612-168
64

Feature Description
Feature
interactions
...................................................................................................................................................................................................................................
Introduction
The DBsubquery feature does not interact with other features.
...................................................................................................................................................................................................................................
401-612-168
65

Feature Description
Implementing
the features
...................................................................................................................................................................................................................................
Overview
To activate the Database Subquery feature, +f Option tool, and the +p Option tool,
perform the following procedure:
Activating the features/tools (p. 67)
To implement the DBsubquery Update Capable feature on the ECP/OMP, perform the
following procedures in sequence. Because the DBsubquery Update Capable feature
replaces many of the DBmagic tools, some of the procedures followed when using
DBmagic should also be used for the DBsubquery Update Capable feature. The
procedures include:
Procedure 1: Prevent interference-ECP (p. 68)
Procedure 2: Update backup subscriber databases-ECP (p. 69)
Procedure 3: Perform a tape backup-ECP (p. 71)
Procedure 4: Prevent all RC/V activity-ECP (p. 72)
Procedure 5: Run DBsubquery-ECP/OMP (p. 74)
Procedure 6: Verify the backup databases-ECP (p. 75)
Procedure 7: Replace the Master Databases-ECP (p. 77)
Procedure 8: Restore RC/V permissions-ECP (p. 78)
...................................................................................................................................................................................................................................
401-612-168
66

Feature Description
Activating
the features/tools
...................................................................................................................................................................................................................................
Purpose
This procedure activates the Database Subquery feature, +f Option tool, and the +p
Option tools in a CDMA network.
Procedure
Perform the following steps:

...................................................................................................................................................................................................
To activate the Database Subquery feature, +f Option tool, and the +p Option tools, ask
your account executive to activate the following entries in your Feature Activation File
(FAF):
DBsubsearch Multi-Query for MUF, CCF, and SUBAUX (DBSQ)
This FAF entry activates the DBsubsearch Multi-Query for MUF, CCF, and
SUBAUX.
Database Survey (DBS)
This FAF entry activates the DataBase Survey feature.
DBsubquery +f option (DBSQF)

This FAF entry activates the +f Option
tool and the full functionality of
DBsubquery.
DBsubquery +p option (DBSQP)
This FAF entry activates the + p Option tool and the full functionality of
DBsubquery.
...................................................................................................................................................................................................
To enable the DBsubquery Update Capable feature and DBsubquery Update Capable
Additional Fields feature, contact your Lucent Technologies Account Representative
and request the following feature be activated in the FAF:
DBsubquery Update-Capable (DBSUBQUC)
This FAF entry activates the DBsubquery Update Capable feature and DBsubquery
Update Capable Additional Fields feature and gives full functionality of
DBsubquery.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-612-168
67

Feature Description
Procedure
1: Prevent interference-ECP
...................................................................................................................................................................................................................................
Purpose
Any changes that are made to the subscriber databases while the DBsubquery tool is
running are lost when the newly rebuilt databases replace the originals. For this reason,
it is important to prevent such changes from occurring. This is accomplished by
performing the following:
Preventing Automatic Backups

Preventing Manual Database Changes
Procedure

...................................................................................................................................................................................................
Preventing automatic backups

Check the file /usr/lib/crontab to see if any automatic database backups are scheduled.
Also check any remote maintenance computers to see if they are programmed to
initiate a database backup. Stop any scheduled database backup by using the ed
editor to insert a # as the first character of the crontab line that schedules the backup
or by temporarily renaming the crontab file itself.
...................................................................................................................................................................................................
Preventing manual database changes

Impose a freeze (to the degree possible) on any and all subscriber recent changes.
Any recent changes made between now and Procedure 7: Replace the Master
Databases-ECP (p. 77) will be lost. The best way to do this is to run the DBsubquery
tool only when RC/V activity that affects the subscriber databases would normally not
occur at all (for example, after hours, scheduled maintenance period, and so on). This
is a good time to warn anyone using RC/V that they will be forced to log off later in
this procedure.
...................................................................................................................................................................................................
Proceed to Procedure 2: Update backup subscriber databases-ECP (p. 69).

END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-612-168
68

Feature Description
Procedure
2: Update backup subscriber databases-ECP
...................................................................................................................................................................................................................................
Purpose
This procedure to update the backup subscriber databases on the ECP.

Before you begin
If the Mobility Manager Technician Interface (FMM-TI) feature is enabled, the

command must be executed using the Technician Interface Command Line Interface
(TICLI). If the FMM-TI feature is disabled, the craft shell must be used.
Procedure

...................................................................................................................................................................................................
On the ECP, enter the following command at the Technician Interface (craft shell or
the TICLI) to back up the on-line subscriber database files:
BKUP:DATABASE;DB SUBSCRIBER!
...................................................................................................................................................................................................
Wait for the following messages before continuing:

REPT:DATABASE BACKUP, NAME MUFDB, COMPLETED
REPT:DATABASE BACKUP, NAME CCFDB, COMPLETED
REPT:DATABASE BACKUP, NAME SUBAUXDB, COMPLETED
REPT:DATABASE BACKUP, NAME AUDB, COMPLETED
REPT:DATABASE BACKUP, NAME SUBUZDB, COMPLETED
REPT:DATABASE BACKUP, NAME P2LDNDB, COMPLETED
REPT:DATABASE BACKUP, NAME DN2PDB, COMPLETED
REPT:DATABASE BACKUP, NAME CNIDDB, COMPLETED
REPT:DATABASE BACKUP, NAME UZDB, COMPLETED
REPT:DATABASE BACKUP, NAME S2PDB, COMPLETED
REPT:DATABASE BACKUP, NAME WINCRDDB, COMPLETED
REPT:DATABASE BACKUP, NAME WINSRVDB, COMPLETED
REPT:DATABASE BACKUP, NAME WINTDADB, COMPLETED
...................................................................................................................................................................................................................................
401-612-168
69

Feature Description
...................................................................................................................................................................................................
Proceed to Procedure 3: Perform a tape backup-ECP (p. 71).

END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-612-168
70

Feature Description
Procedure
3: Perform a tape backup-ECP
...................................................................................................................................................................................................................................
Purpose
This procedure is used to perform a tape backup on the ECP. This is necessary in case
an error occurs when the original databases are replaced and the original databases
need to be restored.
Procedure

...................................................................................................................................................................................................
Write the new backup files to tape.

On the ECP, enter the following command at the UNIX prompt:
disktotape
...................................................................................................................................................................................................
When the first tape is complete, the user is prompted to mount the second tape. Both
tapes are necessary to get a complete backup of all the subscriber databases.
Mount the second tape and repeat Step 1.
...................................................................................................................................................................................................
Proceed to Procedure 4: Prevent all RC/V activity-ECP (p. 72).

END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-612-168
71

Feature Description
Procedure
4: Prevent all RC/V activity-ECP
...................................................................................................................................................................................................................................
Purpose
CAUTION
Service-disruption hazard
RC/V activity that occurs while the master databases are being replaced may cause
database corruption.
It is therefore important to prevent RC/V activity at this time. Execute the commands in
this procedure exactly as shown. Other measures for preventing RC/V activity (such as,
removing TTY ports from service) are NOT sufficient.
Use this procedure to prevent RC/V activity by removing RC/V execute permissions.
Procedure

...................................................................................................................................................................................................
Enter the following commands at the UNIX prompt to prevent future use of RC/V by
removing execute permission from the RC/V program files:
chmod -x /1apx10/ubin/apxrcv
chmod -x /1apx10/testbin/apxsub
chmod -x /1apx10/testbin/apxhome
chmod -x /1apx10/testbin/apxfmr
chmod -x /1apx10/ubin/DBrcvftam
...................................................................................................................................................................................................
Enter the following commands at the UNIX prompt to stop all current use of the RC/V
subsystem:
pkillp /1apx10/ubin/apxrcv
pkillp /1apx10/testbin/apxsub
pkillp /1apx10/testbin/apxhome
pkillp /1apx10/testbin/apxfmr
pkillp /1apx10/ubin/DBrcvftam
...................................................................................................................................................................................................................................
401-612-168
72

Feature Description
...................................................................................................................................................................................................
After you execute any of these commands, if the system reports file not found,
reenter the command that produced the error (the error is caused by incorrectly
entering the command). Otherwise, the system simply responds with another prompt.
...................................................................................................................................................................................................
Proceed to Procedure 5: Run DBsubquery-ECP/OMP (p. 74).

END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-612-168
73

Feature Description
Procedure
5: Run DBsubquery-ECP/OMP
...................................................................................................................................................................................................................................
Purpose
Use this procedure to run DBsubquery on the ECP/OMP.

Before you begin
Important! Before running the DBsubquery tool on the OMP, the user must be in
the current directory where the databases reside.
Procedure

...................................................................................................................................................................................................
Choose a sample of directory numbers (seed numbers) and verify them by using
apxrcv and selecting the sub RC/V form.
...................................................................................................................................................................................................
Log onto the ECP with an ID having root permissions and update the appropriate
subscriber databases by entering the following at the UNIX prompt:
DBsubquery
(with desired options)
Answer all prompts and run the tool in update or verify mode.
...................................................................................................................................................................................................
Proceed to Procedure 6: Verify the backup databases-ECP (p. 75).

END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-612-168
74

Feature Description
Procedure
6: Verify the backup databases-ECP
...................................................................................................................................................................................................................................
Purpose
CAUTION
Service-disruption hazard
Master database corruption may occur if errors are not resolved.
Do not proceed to Procedure 7: Replace the Master Databases-ECP (p. 77) until
you have resolved all problems identified during this procedure.
Use this procedure to verify the backup databases on the ECP.
Procedure

...................................................................................................................................................................................................
If any database appears to be incorrect after verification, review all steps to make sure
they were performed correctly.
...................................................................................................................................................................................................
Because all work up to this point has been done in backup and temporary directories
(not the on-line directories), a delay at this point does not affect the system or its
subscribers adversely.
...................................................................................................................................................................................................
Depending on the ECP release installed, a minimum of four and a maximum of eight
of the new databases should now be in /1apx10/database backup directory. Verify that
they have been correctly copied.
a) On the ECP, enter the following command at the UNIX prompt to invoke the RC/V
interface:
apxrcv -dbf /1apx10/database backup directory/mufdb
b) When prompted for a form name, enter sub.

c) The sub form appears. Verify a sample group of subscriber directory numbers by
entering several directory numbers from every exchange code that should be in the
database. Validate changed fields and/or marked records.
d) Exit RC/V.
Important! Do not proceed to Procedure 7: Replace the Master Databases-ECP
(p. 77) until you have resolved all problems identified thusfar.
...................................................................................................................................................................................................................................
401-612-168
75

Feature Description
...................................................................................................................................................................................................
Proceed to Procedure 7: Replace the Master Databases-ECP (p. 77).

END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-612-168
76

Feature Description
Procedure
7: Replace the Master Databases-ECP
...................................................................................................................................................................................................................................
Purpose
Use this procedure to replace the master databases on the ECP.

Procedure

...................................................................................................................................................................................................
If results are incorrect, back out the changes by transferring (copying) the master
databases to the /1apx10/database backup directory on the ECP which overwrites what
DBsubquery changed, or overwrite with a tape copy of the backup.
Important! While the databases are being copied, some subscribers attempting to place
calls may be temporarily denied service because their subscriber record cannot be
found by the system. This is a temporary problem and will only last until the database
copy has been completed. Calls that are already established will not be affected.
...................................................................................................................................................................................................
If results are correct, commit the changes by transferring (copying) the backup
databases to the master databases (/1apx10/dbdata on the ECP). The CDNs are also
updated.
...................................................................................................................................................................................................
At the Technician Interface (craft shell or TICLI), enter the following command:
COPY:DB SUBSCRIBER;UCL
Result: The COPY:DB SUBSCRIBER;UCL command causes all subscriber databases to
be copied. Do not continue until the following message is displayed:

REPT:AP:COPY DB mufdb COMPLETED SUCCESSFULLY
...................................................................................................................................................................................................
Proceed to Procedure 8: Restore RC/V permissions-ECP (p. 78).

END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-612-168
77

Feature Description
Procedure
8: Restore RC/V permissions-ECP
...................................................................................................................................................................................................................................
Purpose
Use this procedure to restore RC/V permissions on the ECP.

Procedure

...................................................................................................................................................................................................
On the ECP, enter the following commands at the UNIX prompt to restore RC/V
permissions:
chmod +x /1apx10/ubin/apxrcv
chmod +x /1apx10/testbin/apxsub
chmod +x /1apx10/testbin/apxhome
chmod +x /1apx10/testbin/apxfmr
chmod +x /1apx10/ubin/DBrcvftam
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-612-168
78

Feature Description
Related
documentation
...................................................................................................................................................................................................................................
References
The following CDMA network documents provide additional information:
DataBase Password Security, 401-600-046

RC/V Form Security, 401-600-047
Customer Documentation Catalog, 401-610-000
Database Update Manual, 401-610-036
Text Recent Change and Verify Reference Manual, 401-610-038
UNIX Users Guide, 401-610-048
DataBase Survey (DBS) and Enhanced DBsubsearch for CCF (DBSE) Optional
Feature Description, 401-612-024
Delete Subscriber Database Records (DSDR) Optional Feature Description,
401-612-148
CDMA Full IMSI and Related Features Optional Feature Description, 401-612-297
...................................................................................................................................................................................................................................
401-612-168
79

Feature Description
History
of Revisions
...................................................................................................................................................................................................................................
Introduction
The following information was added, deleted, or updated in previous issues of this
document.
Issue 15
Issue 15 (June 2006) of this document included the following new query fields in
Table 5, Query Fields (p. 86) for the IHLR to SDHLR migration for Release 25
SU8.
arg
crbt_auth
crbt_rd_idx
fltr_is41_01
Issue 15 (June 2006) of this document also included the following new query field for
Release 28. The Table 5, Query Fields (p. 86) and Table 21, DBsubquery Update
Capable: Values and Checks (p. 118) tables were updated to include these fields.
bc2_tacs
bc3_jtacs
bc7_700
bc8_1800
bc9_900
bc10_sec800
bc14_uspcs
Issue 14
Issue 14 of this document included updated values and the new cpop_act and
cpop_auth fields in the following tables for Release 26 SU04 and later:
Table 5, Query Fields (p. 86)

Table 21, DBsubquery Update Capable: Values and Checks (p. 118)
Issue 13
Issue 13 updated the document to included the values and the new pref_evb and
pref_smv fields in the following tables for Release 27 and later:

Table 21, DBsubquery Update Capable: Values and Checks (p. 118)
...................................................................................................................................................................................................................................
401-612-168
80

Feature Description
Issue 12
Issue 12 updated the document to included the new query fields for a IHLR to
SD-HLR migration. The following new fields were added to Table 5, Query Fields
(p. 86) for Releases 24, 25 .
allow_intl_roam
crbt_act
delinquent
hlrcrbt_rd_idx
lamt
lcr_dn
lcr_dnlast
mitmrt_act
p_arl
pref_smv
q_arl
ssdupdctr
subssd
Issue 11
Issue 11 updated the document to include information on WIN Enhancements for

DBsubquery feature 10903.1. The following table was updated to include new WIN
service information.
Issue 11 also updated the DBsubquery tool description for the Wireless Priority Service
feature (FID 8919.11), as follows:
Added the hwps_priority query field to the Table 5, Query Fields (p. 86) table
for Release 25.
Issue 10
Issue 10 (February 2005) was revised to include the WIN services on the Subscriber
and Feature Information (sub) form that the user can now query, print and update. This
revision supports feature 10903.1 and add the following changes:
Added general information about the WIN services fields being supported by the
DBsubquery tool. For details see, Functionality (p. 10)
Added the WIN services fields to Appendix A: Query Fields and Conversion
Tables (p. 86) .
...................................................................................................................................................................................................................................
401-612-168
81

Feature Description
Issue 10 (February 2005) updated the DBsubsum tool description as follows:
Added the +c and +a options to DBsubsum Tool (p. 44)

Added the following fields to DBsubsum.log file contents (p. 46) :
Position Det Cap
SMS Restriction
Vocoder Pref
Special Routing Selection
Mobile Protocol Revision
MUSDN Customer Changeable Primary ESN
LSA Users
Changed the sequence of Dbsubsum output fields in DBsubsum screen output
(p. 46)
Updated the Dbsubsum output screens to reflect the new sequence of output fields
in DBsubsum screen output (p. 46)
Issue 10 updated the DBsubquery tool description for the Wireless Priority Service
feature (FID 8919.11), as follows:
Added the hwps_priority query field to Table 5, Query Fields (p. 86)
Issue 10 updated the DBsubquery tool description for the MEID Provisioning Support:
RCV SUB form and tools feature (FID 12330.3), as follows:
Added the Mobile Equipment Identifier (MEID) field to the +L option on Table 1,
DBsubquery Command Options (p. 11)
Added the MEID field to DBsubquery +L Option (p. 18)
...................................................................................................................................................................................................................................
401-612-168
82

Feature Description
Abbreviations
and Terminology
...................................................................................................................................................................................................................................
Introduction
This section defines the terminology and abbreviations used in this document.
A
audb Authentication Database

AMA Automated Message Accounting
C
ccfdb Custom Calling Features Database

CDN Call Processing Database Node
D
(Database) Record A collection of logically related information referenced by a key.

A key may be made up of multiple fields.
Directive A word used to direct an action in a survey.
DB Database
DBS Data Base Survey
DBSQ DBsubsearch Multi-Query for MUF, CCF, and SUBAUX
DBSQF Data Base Subquery +f
DBSQP Data Base Subquery +p
DBSUBQUC Data Base Subquery Update Capable
DBsubquery Data Base Subscriber data Query tool
DBsubsearch Data Base Subscriber data Search tool
DBsurvey Data Base Survey tool
DN Directory Number
E
ECP Executive Cellular Processor

ESN Electronic Serial Number
...................................................................................................................................................................................................................................
401-612-168
83

Feature Description
Form An image displayed on the RC/V terminal, used to enter (in non-Text RC/V)
and/or display the contents of a given database. It may consist of one or more
screens.
FAF Feature Activation File
FID Feature Identifier
G
GA Generally Available
I
IMSI International Mobile Station Identification

K
Key One or more fields used to identify a unique record. On the form (screen
version), key field numbers are prefaced by an asterisk (*) [for example, WCell
Site Number.....*1)___ ].
L
LSA Limited Service Area

M
MIN Mobile Identification Number

MRS Message Recording Service
MSC Mobile Switching Center
MSID Mobile Station Identifier
MUSDN Mobile Unit Switchable DN
N
NSN National Significant Number

O
OMP Operations and Management Platform
...................................................................................................................................................................................................................................
401-612-168
84

Feature Description
PIN Personal Identification Number

PID Process Identification Number
Q
Query A search/survey of a database(s) based on the field(s) of the CDMA network

application databases.
R
RA Restricted Availability
RC/V Recent Change and Verify
RLS Route List Selector
ROP Read-Only Printer
S
Screen The portion of the form that can be displayed on the terminal. A form may
consist of more than one screen.
Syntax The orderly arrangement of words or directives.
SM Service Measurements
SSD Shared Secret Data
SU Software Update
T
TI Technician Interface
TICLI Technician Interface Command Line Interface
W
WIN Wireless Intelligent Network
...................................................................................................................................................................................................................................
401-612-168
85

Feature Description
Appendix
A: Query Fields and Conversion Tables
...................................................................................................................................................................................................................................
Purpose
This appendix contains a table defining the query fields and tables mapping query field
values to their respective RC/V field values.
Query Field Definitions
The following table gives the query fields and valid ranges.
A y in the NULL column indicates that it is a querable on the NULL value. A value
in the NULL column indicates the value to query on for a NULL.
All valid ranges showing y,n are also querable as 1,0 or Y, N.
Fields can be queried for Out of Range values.
In fields noted below, wildcards may be used in the query. The ? wildcard
represents any single digit, and the * wildcard represents any number of trailing
digits - including none.
Table 5
Query Fields
Queryable
Valid Range
Queryable
NULL
Printable
with
Option
aav
0-255
+f, +p
ac_cadence
1-63
+f, +p
ac_pitch
0-3
ack_msgs
0-255
+f, +p
acr
y, n
+f, +p
P=permanent
Query
only
Field Name
ac_act
RC/V Name (if

different from
field name)
mufdb
D=Demand
blank
Notes
+f, +p
All Calls
Activation
RC/V field
name WIN
service.
Use to query
any services
satisfying
search criteria.
...................................................................................................................................................................................................................................
401-612-168
86

Feature Description
Table 5
Query Fields
(continued)
Field Name
RC/V Name (if

different from
field name)
Queryable
Valid Range
Queryable
NULL
Printable
with
Option
Notes
ac_act1 ac_act10
mufdb
P=permanent
+f, +p
All Calls
Activation
RC/V field
name WIN
service.
D=Demand
akey
+p
valid query on
<0, >0, =0, =y,
=n
allow_intl_
roam
y, n
+f, +p
null=y=1
alwarg
y,n
+f, +p
anfx_auth
y,n
+f, +p
anfx_crypt
y,n
+f, +p
apx_only
y,n
+f, +p
arg
1-63
+f, +p
ascp_active
y, n
+f, +p
asdtmfc_act
y, n
+f, +p
async_auth
y, n
+f, +p
async_crypt
y, n
+f, +p
atech
0-7
+f, +p
Refer to Table
6, atech
Conversions
(p. 112)
y, n
Query
only
Advanced
Terminiation
Trigger RC/V
field name WIN
Service.
att
ccfdb
Use to query
any services
satisfying
search criteria.
...................................................................................................................................................................................................................................
401-612-168
87

Feature Description
Table 5
Query Fields
(continued)
Field Name
RC/V Name (if

different from
field name)
Queryable
Valid Range
Queryable
NULL
Printable
with
Option
Notes
att1 - att10
ccfdb
y, n
+f, +p
Advanced
Terminiation
Trigger RC/V
field name WIN
Service.
audb_exists
no equivalent
y, n
+f, +p
auth_act
y, n
+f, +p
auth_over
y, n
+f, +p
autossd
y, n
+f, +p
bc2_tacs
y, n
+f, +p
bc3_jtacs
y, n
+f, +p
bc6_imt2k
y, n
+f, +p
bc7_700
y, n
+f, +p
bc8_1800
y, n
+f, +p
bc9_900
y, n
+f, +p
bc10_sec800
y, n
+f, +p
bc14_uspcs
y, n
+f, +p
bc15_aws
y, n
+f, +p
billno
0-999 999 999

999 999 999 99
+f, +p
bill_typ
0-255
256
+f, +p
caldelact
y, n
+f, +p
caldlalo
y, n
+f, +p
callreg
y, n
+f, +p
ccfact
y, n
+f, +p
ccfbact
y, n
+f, +p
ccfbbmrs
y, n
+f, +p
can use
wildcards and
hex letters a-f,
A-F
...................................................................................................................................................................................................................................
401-612-168
88

Feature Description
Table 5
Query Fields
(continued)
Queryable
Valid Range
Queryable
NULL
Printable
with
Option
Notes
ccfbdgt
0-999 999 999

999 999
+f, +p
can use
wildcards and
hex letters a-f,
A-F
ccfb_ic
0000-9999
+f, +p
can use
wildcards and
hex letters a-f,
A-F
ccfb_iddd
y, n
+f, +p
ccfbmrs
y, n
+f, +p
ccfbnoad
y, n
+f, +p
ccfbsvcord
y, n
+f, +p
ccfci
0000-9999
+f, +p
can use
wildcards and
hex letters a-f,
A-F
ccfdgt
0-999 999 999

999 999
+f, +p
can use
wildcards and
hex letters a-f,
A-F
ccfdt
5-72
+f, +p
ccfi3d
y, n
+f, +p
ccfmax
0-255
+f, +p
ccfnoad
y, n
+f, +p
ccfsvcord
y, n
+f, +p
cd
y, n
+f, +p
cdpd_crypt
y, n
+f, +p
cell_bc
y, n
+f, +p
cfbl
y, n
+f, +p
cfda
y, n
+f, +p
cfd_act
y, n
+f, +p
0999999999999999
+f, +p
Field Name
cfd_dgt
RC/V Name (if

different from
field name)
ccfdb
...................................................................................................................................................................................................................................
401-612-168
89

Feature Description
Table 5
Query Fields
(continued)
Field Name
RC/V Name (if

different from
field name)
Queryable
Valid Range
Queryable
NULL
Printable
with
Option
cfd_ic
ccfdb
y, n
+f, +p
cfd_iddd
ccfdb
y, n
+f, +p
cfd_ihlr
mufdb
y, n
+f, +p
cfd_noad
mufdb
y, n
+f, +p
cfd_svcord
mufdb
y, n
+f, +p
cfnpr
y, n
+f, +p
cgsa
1-16
+f, +p
cnap
y, n
+f, +p
y, n
Query
only
cnid_assgnd
mufdb
Notes
CNID Assigned
RC/V field
name WIN
Service.
Use to query
any services
satisfying
search criteria.
y, n
+f, +p
cp_arcap
y, n
+f, +p
cp_authct
y, n
+f, +p
cpc
0-15
cp_ct
y, n
+f, +p
cp_fixedsub
y, n
+f, +p
cpnd
y, n
+f, +p
cpnr
y, n
+f, +p
cp_rorane
y, n
+f, +p
cp_salsa
y, n
+f, +p
cpop_act
y, n
+f, +p
cpop_auth
y, n
+f, +p
crbt_act
y, n
+f, +p
cnid_
assgnd1 cnid_
assgnd10
mufdb
CNID Assigned
RC/V field
name WIN
Service.
+f, +p
...................................................................................................................................................................................................................................
401-612-168
90

Feature Description
Table 5
Query Fields
(continued)
Queryable
Valid Range
Queryable
NULL
Printable
with
Option
crbt_auth
y, n
+f, +p
crbt_rd_idx
1-7
+f, +p
ctrace
0-255
+f, +p
ctsurtg
1-255
+f, +p
cuimiu
y, n
cw
y, n
+f, +p
cwact
y, n
+f, +p
cwar
y, n
+f, +p
cwdatime
5-72
+f, +p
dc1
1-255
+f, +p
dc2
1-255
+f, +p
deft_pl
0-255
+f, +p
delinquent
y, n
+f, +p
deny_
redirect
y, n
Field Name
dn
RC/V Name (if

different from
field name)
no equivalent
00000000009999999999
Notes
+f, +p
Refer to Table
7, IS-53-A
Preferred
Language
(deft_pl
Conversions)
(p. 112)
+f, +p
y
+f, +p
can use
wildcards and
hex letters a-f,
A-F
This field only
matches or
prints for
records with
10-digit NSN.
dnd_act
y, n
+f, +p
dnd_auth
y, n
+f, +p
dntype
0-255
+f, +p
...................................................................................................................................................................................................................................
401-612-168
91

Feature Description
Table 5
Query Fields
(continued)
Queryable
Valid Range
Queryable
NULL
Printable
with
Option
docr_
minutes
0-1440
+f, +p
docr_inv_
atmpts
0-9
+f, +p
docr_block
y, n
+f, +p
docr_level
0-9
+f, +p
dwnload
y, n
+f, +p
ecp_level
1-4
+f, +p
enh_rc
y, n
enhccf
y, n
+f, +p
ensmsorigres
0-3
+f, +p
Field Name
RC/V Name (if

different from
field name)
Notes
Refer to Table
9, ecp_level
Conversions
(p. 114)
+f, +p
0=b
1=a
2=i
3=u
b=block direct
a=allow direct
i=force indirect
u=undefine
exmin
y, n
+f, +p
expday
day
1-31
+f, +p
expmon
month
1-12
+f, +p
expyear
year
00-99
<0
+f, +p
fa_control
00000000 - ffffffff
+f, +p
hexidecimal
...................................................................................................................................................................................................................................
401-612-168
92

Feature Description
Table 5
Query Fields
(continued)
Field Name
RC/V Name (if

different from
field name)
Queryable
Valid Range
Queryable
NULL
fa_dn
subpltdb
0y
9999999999999999
Printable
with
Option
Notes
Query
Only
Flexible Alerting
Member DN
RC/V field
name, can use
wildcards and
hex letters a-f,
A-F
fa_dn1 fa_dn15
subpltdb
0y
9999999999999999
+f, +p
Flexible Alerting
Member DN
RC/V field
name, can use
wildcards and
hex letters a-f,
A-F
fa_iddd
subpltdb
y, n
Query
Only
Flexible Alerting
IDDD RC/V
field name
fa_iddd1 fa_iddd15
subpltdb
y, n
+f, +p
Flexible Alerting
IDDD RC/V
field name
fa_pstn
subpltdb
y, n
Query
Only
Flexible Alerting
Force PSTN
RC/V field
name
fa_pstn1 fa_pstn15
subpltdb
y, n
+f, +p
Flexible Alerting
Force PSTN
RC/V field
name
fa_skip
y, n
255
+f, +p
fatype
0-2
+f, +p
fax_auth
y, n
+f, +p
fax_crypt
y, n
+f, +p
Refer to Table
10, fatype
Conversions
(p. 114)
...................................................................................................................................................................................................................................
401-612-168
93

Feature Description
Table 5
Query Fields
(continued)
Field Name
RC/V Name (if

different from
field name)
Queryable
Valid Range
Queryable
NULL
Printable
with
Option
Notes
feat_ctl
subpltdb
y, n
Query
Only
Flexible Alerting
Feat Ctl RC/V
field name
feat_ctl1 feat_ctl15
subpltdb
y, n
+f, +p
Flexible Alerting
Feat Ctl RC/V
field name
fldpg
y, n
+f, +p
fltr_is41_oi
y, n
+f, +p
fmr
y, n
+f, +p
y, n
+f, +p
forced
no equivalent
ftc_dtmf
y, n
+f, +p
ftc_tntype
c, b
+f, +p
c=continuous
b=burst
ghost
y, n
+f, +p
ghost_dcs1
1-255
+f, +p
ghost_dcs2
1-255
+f, +p
glsfeatctl
y, n
+f, +p
glsregnot
y, n
+f, +p
gnatd
5-72
+f, +p
guts_wi
y, n
+f, +p
hlci
0000-9999
+f, +p
can use
wildcards and
hex letters a-f,
A-F
0-15
+f, +p
4th digit of pic
hldgt
0-999 999 999

999 999
+f, +p
can use
wildcards and
hex letters a-f,
A-F
hli3d
y, n
+f, +p
hlrcrbt_act
y, n
+f, +p
hlci4
no equivalent
...................................................................................................................................................................................................................................
401-612-168
94

Feature Description
Table 5
Query Fields
(continued)
Queryable
Valid Range
Queryable
NULL
Printable
with
Option
hlrcrbt_rd_
idx
1-255
+f, +p
homeonly
y, n
+f, +p
hpin_type
0-4
+f, +p
Field Name
RC/V Name (if

different from
field name)
Notes
...................................................................................................................................................................................................................................
401-612-168
95

Feature Description
Table 5
Field Name
hwps_
priority
Query Fields
RC/V Name (if

different from
field name)
(continued)
Queryable
Valid Range
Queryable
NULL
Printable
with
Option
Notes
0-15
+f, +p
Wireless
Priority Service
(WPS) user
priority levels
can be queried
by discrete
values.
Printing
permissions in
RFSadmin tool
(wpsuser form).
NOTE: If
password
protection has
been enabled
for the wpsuser
form, query
requests to
either search
for and/or
include in the
output data
related to the
hwps_priority
subscriber
attribute will
result in a
separate prompt
for the
appropriate
password.
If the incorrect
(or no)
password is
provided, the
DBsubquery
request will
fail.
icf
y, n
+f, +p
...................................................................................................................................................................................................................................
401-612-168
96

Feature Description
Table 5
Query Fields
(continued)
Field Name
RC/V Name (if

different from
field name)
Queryable
Valid Range
Queryable
NULL
Printable
with
Option
Notes
icf_act
subpltdb
D = drop leg
Query
Only
Flexible Alerting
ICF Action
Q = query hlr
RC/V field
name
icf_act1 icf_act15
subpltdb
D = drop leg
+f, +p
Q = query hlr
Flexible Alerting
ICF Action
RC/V field
name
icfi3d
y, n
+f, +p
icfab
y, n
+f, +p
icfact
y, n
+f, +p
icfbmrs
y,n
+f, +p
icfci
0000-9999
+f, +p
can use
wildcards and
hex letters a-f,
A-F
icfdgt
0-999 999 999

999 999
+f, +p
can use
wildcards and
hex letters a-f,
A-F
icfmax
0-255
+f, +p
icfnoad
y, n
+f, +p
icfsvcord
y, n
+f, +p
icsr
y, n
+f, +p
ignore_esn
y, n
+f, +p
immbill
1-255
+f, +p
imsi
00000000 999999999999999
+S
insnd_all
y, n
+f, +p
Option +S can
be used with
+f/+p/+l/+L/+L1.
Can use
wildcards and
hex letters a-f,
A-F.
...................................................................................................................................................................................................................................
401-612-168
97

Feature Description
Table 5
Field Name
Query Fields
RC/V Name (if

different from
field name)
(continued)
Queryable
Valid Range
Queryable
NULL
Printable
with
Option
insnd_aterm
0-3
insnd_bnum
y, n
+f, +p
insnd_dstar
y, n
+f, +p
insnd_ilata
y, n
+f, +p
insnd_inter
y, n
+f, +p
insnd_loc
y, n
+f, +p
insnd_nodgt
y, n
+f, +p
insnd_olata
y, n
+f, +p
insnd_pound
y, n
+f, +p
insnd_rtvc
y, n
+f, +p
insnd_star
y, n
+f, +p
insnd_1dgt
y, n
+f, +p
insnd_2dgts
y, n
+f, +p
insnd_3dgts
y, n
+f, +p
insnd_4dgts
y, n
+f, +p
insnd_5dgts
y, n
+f, +p
insnd_6dgts
y, n
+f, +p
insnd_7dgts
y, n
+f, +p
insnd_8dgts
y, n
+f, +p
insnd_9dgts
y, n
+f, +p
insnd_10dgts
y, n
+f, +p
insnd_11dgts
y, n
+f, +p
insnd_12dgts
y, n
+f, +p
insnd_13dgts
y, n
+f, +p
insnd_14dgts
y, n
+f, +p
insnd_15dgts
y, n
+f, +p
insnd_1rsv
y, n
+f, +p
insnd_2rsv
y, n
+f, +p
insnd_3rsv
y, n
+f, +p
Notes
+f, +p
...................................................................................................................................................................................................................................
401-612-168
98

Feature Description
Table 5
Query Fields
(continued)
Queryable
Valid Range
Queryable
NULL
Printable
with
Option
insnd_
dpound
y, n
+f, +p
insnd_5rsv
y, n
+f, +p
ip_crypt
y, n
+f, +p
iscp_pcrid
16-1039
+f, +p
korean_bc
y, n
lamt
0-3
+f, +p
lcr
y, n
+f, +p
lcr_dn
0-fff fff fff fff ff
+f, +p
lcr_dnlast
0-f
+f, +p
Field Name
RC/V Name (if

different from
field name)
Notes
+f, +p
ldn
ldnlist, ldn
not queryable
lirm
ccfdb
1-255
+f, +p
Location
Information
Restriction
Mode RC/V
field name WIN
service
000-999
+f, +p
can use
wildcards and
hex letters a-f,
A-F
lock
+f, +p
lsa_levell
lsalvl[1-8]
0-65535
+f, +p
valid query on
<0, >0, =0
lsa_listl
lsanum [1-8]
0, 1
+f, +p
valid query on
<0, >0, =0
marked
y, n
+f, +p
mas_auth
y, n
+f, +p
mas_dalats
no equivalent
0-255
+f, +p
Day portion of
MAS
mas_holats
no equivalent
0-255
+f, +p
Hour portion of
MAS
mas_lats
valid query on
<0, >0, =0
...................................................................................................................................................................................................................................
401-612-168
99

Feature Description
Table 5
Query Fields
(continued)
Printable
with
Option
Notes
0-255
+f, +p
Minute portion
of MAS
0-255
+f, +p
Month portion
of MAS
Field Name
RC/V Name (if

different from
field name)
Queryable
Valid Range
mas_milats
no equivalent
mas_molats
no equivalent
Queryable
NULL
mas_reason
0-4
+f, +p
max_alert
1-15
mbillalw
y, n
+f, +p
mccpe_act
0-2
+f, +p
mdn
0000-9999
+f, +p
+f, +p
can use
wildcards and
hex letters a-f,
A-F
This field only
matches or
prints for
records with
10-digit NSN.
meid
h000000000000
00 - hffffffffffffff
+f, +p
can use
wildcards
min
0000000000 9999999999
+f, +p
Can use
wildcards and
hex letters a-f,
A-F.
00000-99999
00000
+f, +p
mitmrt_act
y, n
+f, +p
mp_act
y, n
+f, +p
mpci
0-6
mpdc
0-15
min_esc
ccfdb
+f, +p
Refer to Table
11, mpci
Conversions
(p. 114)
+f, +p
Refer to Table
12, mpdc
Conversions
(p. 115)
...................................................................................................................................................................................................................................
401-612-168
100

Feature Description
Table 5
Query Fields
(continued)
Queryable
Valid Range
Queryable
NULL
Printable
with
Option
Notes
mpdc2
0-15
+f, +p
Refer to Table
12, mpdc
Conversions
(p. 115)
mpdc3
0-15
+f, +p
Refer to Table
12, mpdc
Conversions
(p. 115)
mp_freq
10-20470
+f, +p
mp_on_time
5-255
+f, +p
mp_off_time
5-255
+f, +p
mrs
y, n
+f, +p
mrsact
y, n
+f, +p
mrsno
1-10
+f, +p
0-2
+f, +p
mrs_i
y, n
+f, +p
mrs_iact
y, n
+f, +p
mrsuid
00001-99999
00000
+f, +p
Field Name
mrstype
RC/V Name (if

different from
field name)
no equivalent
Refer to Table
13, mrstype
Conversions
(p. 115)
valid query on
>0
can use
wildcards and
hex letters a-f,
A-F
msid
0000000000- 999
999 9999
+f, +p
can use
wildcards and
hex letters a-f,
A-F
...................................................................................................................................................................................................................................
401-612-168
101

Feature Description
Table 5
Field Name
Query Fields
RC/V Name (if

different from
field name)
msid_type
(continued)
Queryable
Valid Range
Queryable
NULL
1, 0
Printable
with
Option
Notes
+f, +p
1=subscriber
key is of the
imsi type
0=subscriber
key is of the
min type
msstat
0-3
+f, +p
mwi_active
y, n
+f, +p
0-13
+f, +p
na_qos_
plevel
mufdb
nmt_bc
y, n
no_msgs
1-255
0, blank
+f, +p
npa
000-999
+f, +p
Refer to Table
14, msstat
Conversions
(p. 115)
+f, +p
can use
wildcards and
hex letters a-f,
A-F
This field only
matches or
prints for
records with
10-digit NSN.
nsn
0-999 999 999

999 99
+f, +p
can use hex

letters a-f, A-F
nxx
000-999
+f, +p
can use
wildcards and
hex letters a-f,
A-F This field
only matches or
prints for
records with
10-digit NSN.
omaj
1-255
+f, +p
ota_wi
y, n
+f, +p
...................................................................................................................................................................................................................................
401-612-168
102

Feature Description
Table 5
Query Fields
(continued)
Notes
Queryable
Valid Range
Queryable
NULL
Printable
with
Option
otapa_cap
y, n
+f, +p
p_arl
y, n
+f, +p
paac
y, n
+f, +p
paacx
0-65535
+f, +p
paging_serv
0-7
+f, +p
pats_day
0-31
+f, +p
pats_hour
00-23
+f, +p
pats_minute
00-55
+f, +p
pcs_bc
y, n
pcs_cap
y, n
+f, +p
pcspanc
0-15
16
+f, +p
pgch
0-1
255
+f, +p
pgnum
0-3
+f, +p
Refer to Table
16, pgnum
Conversions
(p. 116)
pic
0000-9999
+f, +p
can use
wildcards and
hex letters a-f,
A-F
pin_active
y, n
+f, +p
need FAF
pin_digits
0-65535
+f, +p
0y
9999999999999999
Query
Only
Field Name
ppdn
RC/V Name (if

different from
field name)
submbrdb
Refer to Table
15,
paging_serv
Conversions
(p. 116)
+f, +p
Flexible Alerting
Preferred Pilot
DNs RC/V field
name, can use

wildcards and
hex letters a-f,
A-F
...................................................................................................................................................................................................................................
401-612-168
103

Feature Description
Table 5
Query Fields
(continued)
Field Name
RC/V Name (if

different from
field name)
Queryable
Valid Range
Queryable
NULL
ppdn1 ppdn4
submbrdb
0y
9999999999999999
Printable
with
Option
Notes
+f, +p
Flexible Alerting
Preferred Pilot
DNs RC/V field
name, can use

wildcards and
hex letters a-f,
A-F
pps
not queryable
+f, +p
pref_ev
0-7
+f, +p
null=0. Formal
valid query
range 0-5 was
expanded to 0-7
to help
diagnose the
3-bit field
pref_evb
0-7
+f, +p
null=0. Formal
valid query
range 0-5 was
expanded to 0-7
to help
diagnose the
3-bit field
pref_8k
0-7
+f, +p
null=0. Formal
valid query
range 0-5 was
expanded to 0-7
to help
diagnose the
3-bit field
pref_13k
0-7
+f, +p
null=0. Formal
valid query
range 0-5 was
expanded to 0-7
to help
diagnose the
3-bit field
...................................................................................................................................................................................................................................
401-612-168
104

Feature Description
Table 5
Query Fields
(continued)
Queryable
Valid Range
Queryable
NULL
Printable
with
Option
Notes
pref_smv
0-7
+f, +p
null=0. Formal
valid query
range 0-5 was
expanded to 0-7
to help
diagnose the
3-bit field
projacc
y, n
+f, +p
prqlevel
1-15
+f, +p
psofpr
y, n
+f, +p
Field Name
psrf
RC/V Name (if

different from
field name)
psrf[1-7]
+f, +p
q_arl
y, n
qpch_sup
y, n
rac1
1-255
+f, +p
rac2
1-255
+f, +p
rasa
rc
1-255
+f, +p
reguznum
0-1677215
+f, +p
reguztype
0, 1, 2
+f, +p
valid query on
<0, >0, =0
+f, +p
+f, +p
+f, +p
valid query on
<0, >0, =0
0=public
1=private
2=residential
rfc_asn
y, n
+f, +p
rlp_tmr
0,5-3600
4095
+f, +p
rpin_type
0-4
+f, +p
rrc
0-31
+f, +p
rvr_mth
0-12
+f, +p
rvr_day
0-31
+f, +p
rvr_hr
0-23
+f, +p
rvr_min
00-59
+f, +p
rvr_intday
0-7
+f, +p
...................................................................................................................................................................................................................................
401-612-168
105

Feature Description
Table 5
Query Fields
(continued)
Queryable
Valid Range
Queryable
NULL
Printable
with
Option
rvr_inthr
00-23
+f, +p
sb_msc_pg
0-31
scr_idx
0-65534
65535
+f, +p
sdt_active
y, n
+f, +p
Field Name
sec_msid
RC/V Name (if

different from
field name)
no equivalent
sendtone
serv_indx
mufdb
Notes
+f, +p
0000000000 9999999999
+f, +p
y, n
+f, +p
1-255
Query
only
Service Index
RC/V field
name WIN
service.
Use to query
any services
satisfying
search criteria.
serv_indx1 serv_indx10
mufdb
1-255
+f, +p
Service Index
RC/V field
name WIN
service.
serv_stat
ccfdb
a=active
Query
only
Service Status
RC/V field
name WIN
service. Use to
query any
services
satisfying
search criteria.
+f, +p
Service Status
RC/V field
name WIN
service.
i=inactive
serv_stat1 serv_stat10
ccfdb
a=active
i=inactive
...................................................................................................................................................................................................................................
401-612-168
106

Feature Description
Table 5
Query Fields
(continued)
Field Name
RC/V Name (if

different from
field name)
Queryable
Valid Range
Queryable
NULL
Printable
with
Option
Notes
simaddr_i
mufdb
1-255
+f, +p
SIM
Destination
Address Index
RC/V field
name WIN
service
slotidx_c
0-15
15
+f, +p
Refer to Table
17, slotidx_c
Conversions
(p. 116)
sme_on
y, n
+f, +p
sms_wi
y, n
+f, +p
smstermres
y, n
+f, +p
0=y, 3=n
smsorigres
y, n
+f, +p
0=y, 3=n
sndisp
0-255
+f, +p
Refer to Table
18, sndisp
Conversions
(p. 116)
sos_avail
y, n
+f, +p
so7_auth
y, n
+f, +p
so8_auth
y, n
+f, +p
so15_auth
y, n
+f, +p
so16_auth
y, n
+f, +p
so33_auth
y, n
spanc_active
y, n
+f, +p
spanc_
ancmnt
1-255
+f, +p
spina_home
y, n
+f, +p
spina_roam
y, n
+f, +p
split_npa
cp_othnpa
+f, +p
0-3
+f, +p
sppa
1-255
+f, +p
srfcntl
0-7
+f, +p
srno
*h (1-ffffffff)
+f, +p
...................................................................................................................................................................................................................................
401-612-168
107

Feature Description
Table 5
Field Name
Query Fields
RC/V Name (if

different from
field name)
(continued)
Queryable
Valid Range
Queryable
NULL
Printable
with
Option
srno2
*h (1-ffffffff)
+f, +p
srno3
*h (1-ffffffff)
+f, +p
ssd
+p
ssdupdctr
0-15
+f, +p
stdlidx
0-65535
+f, +p
stol_unit
y, n
sub_allow_pl
y, n
+f, +p
y, n
+f, +p
sub_coi
y, n
+f, +p
sub_ocoi
y, n
+f, +p
subssd
y, n
+f, +p
sui
y, n
+f, +p
svcalw_c
0-2
sw
1-16
target
not queryable
subaux_
exists
tbusy
no equivalent
ccfdb
y, n
Notes
valid query on
<0, >0, =0
+f, +p
+f, +p
null=n=1
Refer to Table
19, svcalw_c
Conversions
(p. 117)
+f, +p
+p
Restricted field
Query
only
TBusy Trigger
RC/V field
name WIN
service.
Use to query
any services
satisfying
search criteria.
tbusy1 tbusy10
tmaj
ccfdb
y, n
+f, +p
1-2
+f, +p
TBusy Trigger
RC/V field
name WIN
service.
...................................................................................................................................................................................................................................
401-612-168
108

Feature Description
Table 5
Query Fields
(continued)
Field Name
RC/V Name (if

different from
field name)
Queryable
Valid Range
Queryable
NULL
Printable
with
Option
Notes
tnoanswer
ccfdb
y, n
Query
only
TNoAnswer
Trigger RC/V
field name WIN
service.
Use to query
any services
satisfying
search criteria.
tnoanswer1 tnoanswer10
ccfdb
trig_pro
tt_busy
subpltdb
y, n
+f, +p
TNoAnswer
Trigger RC/V
field name WIN
service.
0, 1
+f, +p
valid query on
0=a, 1=w
D = drop leg
Query
Only
Flexible Alerting
Term Trigs Busy
Q = query hlr
RC/V field
name
tt_busy1 tt_busy15
subpltdb
D = drop leg
+f, +p
Q = query hlr
Flexible Alerting
Term Trigs Busy
RC/V field
name
tt_na
subpltdb
D = drop leg
Q = query hlr
Query
Only
Flexible Alerting
Term Trigs
NoAns RC/V
field name
tt_na1 tt_na15
subpltdb
D = drop leg
+f, +p
Q = query hlr
Flexible Alerting
Term Trigs
NoAns RC/V
field name
tt_npr
subpltdb
D = drop leg
Q = query hlr
Query
Only
Flexible Alerting
Term Trigs NPR
RC/V field
name
...................................................................................................................................................................................................................................
401-612-168
109

Feature Description
Table 5
Query Fields
(continued)
Field Name
RC/V Name (if

different from
field name)
Queryable
Valid Range
Queryable
NULL
Printable
with
Option
Notes
tt_npr1 tt_npr15
subpltdb
D = drop leg
+f, +p
Flexible Alerting
Term Trigs NPR
Q = query hlr
RC/V field
name
tt_rf
subpltdb
D = drop leg
Q = query hlr
Query
Only
Flexible Alerting
Term Trigs RF
RC/V field
name
tt_rf1 tt_rf15
subpltdb
D = drop leg
+f, +p
Q = query hlr
Flexible Alerting
Term Trigs RF
RC/V field
name
twc
y, n
+f, +p
uzdisplay
y, n, o
+f, +p
uzonly
y, n
+f, +p
uznum
1-1677215
+f, +p
uztone
y, n
+f, +p
vad_id
000-999
+f, +p
vad_auth
y, n
+f, +p
valssd
y, n
+f, +p
vdcsid
0-16
255
+f, +p
vecpid
0-15
255
+f, +p
vmaj
1-255
+f, +p
vman_mail
y, n
+f, +p
vman_option
0-255
255
+f, +p
valid query on
0=n, 1=y, 2=o
can use
wildcards and
hex letters a-f,
A-F
Refer to Table
20,
vman_option
Conversions
(p. 117)
...................................................................................................................................................................................................................................
401-612-168
110

Feature Description
Table 5
Query Fields
(continued)
Queryable
Valid Range
Queryable
NULL
Printable
with
Option
Notes
vms_id
000-999
+f, +p
can use
wildcards and
hex letters a-f,
A-F
vp_active
y, n
+f, +p
vp_netinit
y, n
+f, +p
vsid
1-37767
+f, +p
Field Name
vssw
RC/V Name (if

different from
field name)
vssw[1-16]
+f, +p
wac_bc_act
y, n
+f, +p
wac_bc_auth
y, n
+f, +p
wac_conf_
act
y, n
+f, +p
wac_conf_
auth
y, n
+f, +p
wac_dcsid
0-16
+f, +p
wac_ecpid
0-15
+f, +p
wac_sid
1-32767
+f, +p
wect_act
y, n
win_att
y, n
+f, +p
win_icdd
y, n
+f, +p
win_critical
y, n
+f, +p
win_cat
y, n
+f, +p
win_cdt
y, n
+f, +p
1-255
+f, +p
wincrd_i
mufdb
win_tra
valid query on
<0, >0, =0
+f, +p
y, n
WIN Critical
Restriction
Index RC/V
field name WIN
service.
+f, +p
xdcsid
no equivalent
0-16
255
+f, +p
xecpid
no equivalent
0-15
255
+f, +p
...................................................................................................................................................................................................................................
401-612-168
111

Feature Description
Table 5
Query Fields
(continued)
Field Name
RC/V Name (if

different from
field name)
Queryable
Valid Range
Queryable
NULL
Printable
with
Option
xsid
no equivalent
1-32767
+f, +p
Table 6
atech Conversions
Query Field
RC/V Field Conversion
NULL
acc
c-dcch
cdma
p-dcch
Table 7
Notes
Query Field
RC/V Field
Query Field
RC/V Field
NULL
31
NAVAHO
ENGLISH
32
HUNGARIAN
FRENCH
33
MON-KHMER
SPANISH
34
GUJARATI
GERMAN
35
UKRAINIAN
PORTUGUESE
36
CZECH
CANTONESE
37
PEN-DUTCH
MANDARIN
38
MIAO
HANGUL
39
NORWEGIAN
BAHASA
40
SLOVAK
10
HINDI
41
SWEDISH
11
URDU
42
SERBIAN
12
TAGALOG
43
KRU
13
YOUROBA
44
ROMANIAN
14
SWAHILI
45
LITHUANIAN
15
GAELIC
46
FINNISH
16
HEBREW
47
PUNJAB
...................................................................................................................................................................................................................................
401-612-168
112

Feature Description
Table 7
(continued)
Query Field
RC/V Field
Query Field
RC/V Field
17
JAPANESE
48
FORMOSAN
18
RUSSIAN
49
CROATIAN
19
ARABIC
50
BOSNIAN
20
DUTCH
51
TURKISH
21
ITALIAN
52
ILOCANO
22
POLISH
53
BENGALI
23
VIETNAMESE
54
DANISH
24
GREEK
55
FLEMISH
25
YIDDISH
56
SYRIAN
26
THAI
57
TAMIL
27
LAOTIAN
58
SAMOAN
28
PERSIAN
59
MALAYALAM
29
CREOLE
60
CAJUN
30
ARMENIAN
61
AMHARIC
Table 8
dntype Conversions
Query Field
10
11
12
...................................................................................................................................................................................................................................
401-612-168
113

Feature Description
Table 8
dntype Conversions
(continued)
Query Field
13
14
15
16
17
18
19
20
21
22
26
Table 9
ecp_level Conversions
Query Field
Table 10
fatype Conversions
Query Field
off
single
multi
Table 11
mpci Conversions
Query Field
553
54B
95
...................................................................................................................................................................................................................................
401-612-168
114

Feature Description
Table 11
mpci Conversions
(continued)
Query Field
136
136A
T136A
Table 12
mpdc Conversions
Query Field
Mobile is not a CDMA.
CDMA Pilot Phase + GPS-MS is capable

of supporting Advanced Forward Link
Trilateration (A-FLT) and Global
Positioning System (GPS) for location
determination.
CDMA Pilot Phase Only- MS is capable

of supporting A-FLT only for location
determination.
GPS only - Mobile station (MS) is

capable of supporting only GPS for
location determination.
Table 13
mrstype Conversions
Query Field
Table 14
msstat Conversions
Query Field
...................................................................................................................................................................................................................................
401-612-168
115

Feature Description
Table 15
paging_serv Conversions
Query Field
fa
NULL
Table 16
pgnum Conversions
Query Field
Table 17
slotidx_c Conversions
Query Field
15
NULL
Table 18
sndisp Conversions
Query Field
...................................................................................................................................................................................................................................
401-612-168
116

Feature Description
Table 18
sndisp Conversions
(continued)
Query Field
255
Table 19
svcalw_c Conversions
Query Field
255
NULL
Table 20
vman_option Conversions
Query Field
255
NULL
...................................................................................................................................................................................................................................
401-612-168
117

Feature Description
Appendix
B: DBsubquery Update Capable Additional Fields
...................................................................................................................................................................................................................................
Purpose
This appendix contains a table of the valid field values and checks of the DBsubquery
Update Capable Additional Fields feature.
Query Field Definitions
Valid ranges that are 1 or 0 can be y or n, respectively (that is 1= y and 0 = n).

All valid ranges showing y,n can also be used for queries with the following values:
1
0
Y
N
Table 21
Changeable Field Name
Values
ac_cadence
1-63 (or 0 for NULL)
ac_pitch
0-3
ack_msgs
1-255 (or 0 for NULL)
acr
1 or 0 (or y or n, respectively)
apx_only
ascp_active
async_auth
async_crypt
autossd
bc2_tacs
y or n (or 1 or 0 respectively)
bc3_jtacs
bc6_imt2k
bc7_700
bc8_1800
bc9_900
Checks
Must be set to y if
paging_serv = a.
Must be set to y if
async_crypt = y.
async_auth must be set to y if

async_crypt = y.
...................................................................................................................................................................................................................................
401-612-168
118

Feature Description
Table 21
Appendix B: DBsubquery Update Capable Additional

Fields
Values
bc10_sec800
bc14_uspcs
bc15_aws
caldelact
caldlalo
ccfact
ccfdt
5-72 (0 for NULL)
ccfi3d
ccfmax
0-255 (0 for NULL)
cd
cdpd_crypt
y, n
cell_bc
y or n (or 1 or 0, respectively)
cfd_act
y, n (0 for NULL)
cfd_iddd
y, n (0 for NULL)
cfd_ihlr
y, n (0 for NULL)
cfd_noad
y, n (0 for NULL)
cfd_svcord
y, n (0 for NULL)
cgsa
116 (0 for NULL)
cnap
cpnd
cpnr
cpop_act
(continued)
Checks
If cdpd_crypt = y, then
so8_auth or so16_auth or
so34_auth must be y.
Value cannot be NULL if

dntype values =a, m, or p
cpop_auth must be set to y

when cpop_act is y. This tool
cannot enforce this dependency.
The tool user must make sure
these fields are populated
correctly.
...................................................................................................................................................................................................................................
401-612-168
119

Feature Description
Table 21

Fields
(continued)
Values
Checks
cpop_auth
cpop_auth must be set to y

when cpop_act is y. This tool
cannot enforce this dependency.
The tool user must make sure
these fields are populated
correctly.
cuimiu
cw
cwar
cwdatime
5-72 (0 for NULL)
dc1
1255 (0 for NULL)
dc1 cannot equal dc2
dc2
1255 (0 for NULL)
dc2 cannot equal dc1
deny_redirect
ecp_level
1-4 (0 for NULL)
enhccf
enh_rc
ensmsorigres
b, a, i, u
exmin
fa_control
00000000 - ffffffff hexadecimal
fa_skip
fax_auth
fax_crypt
fldpg
fmr
ftc_dtmf
cw must be set to n if mp_act =

y
exmin cannot be changed due

to phone number or serial
number conflict or dntype is
not equal to h
Must be set to y if
paging_serv = f
Must be set to y if
fax_crypt = y
fax_auth must be set to y if

fax_crypt = y
If ftc_dtmf = y, the FTC DTMF

Feature must be active in the
FAF file.
...................................................................................................................................................................................................................................
401-612-168
120

Feature Description
Table 21

Fields
Values
ftc_tntype
c, b
ghost
ghost_dcs1
1-255
ghost_dcs2
1-255
glsfeatctl
gnatd
5-72 (0 for NULL)
hlci
0000-9999 (or 0 for NULL)
hldgt
0-999 999 999 999
(continued)
Checks
glsfeatctl must be set to n if

glsregnot = n
0-999 999 999 999 999

hli3d
hpin_type
0-4
icfab
icfi3d
icfmax
0-255 (0 for NULL)
icfnoad
icfsvcord
icsr
ignore_esn
immbill
1-255 (0 for NULL)
insnd_all
insnd_bnum
insnd_dstar
insnd_ilata
insnd_inter
insnd_loc
insnd_nodgt
insnd_olata
insnd_pound
insnd_rtvc
insnd_star
...................................................................................................................................................................................................................................
401-612-168
121

Feature Description
Table 21

Fields
Values
insnd_1dgt
insnd_2dgts
insnd_3dgts
insnd_4dgts
insnd_5dgts
insnd_6dgts
insnd_7dgts
insnd_8dgts
insnd_9dgts
insnd_10dgts
insnd_11dgts
insnd_12dgts
insnd_13dgts
insnd_14dgts
insnd_15dgts
ip_crypt
korean_bc
lcr
mas_auth
max_alert
1-15
mbillalw
min_esc
00000-99999
mpci
553, 54B,95, 136, 136A, T136A
mpdc
1-4
mrs
(continued)
Checks
If ip_crypt = y, then so7_auth

or so15_auth or so33_auth must
be y.
if mwi_active is set to y,
mrs must = y
if vms_id = 000 or NULL,

mrs must = n
if icfbmrs or ccfbmrs or
ccfbbmrs is set to y, then
mrs must = y
...................................................................................................................................................................................................................................
401-612-168
122

Feature Description
Table 21

Fields
Values
mrsact
mrs_i
mrs_iact
mrsno
110 (0 for NULL)
msstat
u, a, i
mwi_active
na_qos_plevel
0-13 (0 for NULL)
nmt_bc
no_msgs
1-255 (0 for NULL)
omaj
117 (or 0 for NULL) or 32 or

255
(continued)
Checks
vms_id must not be set to 000

or NULL if mrs_i = y
mrs must be set to y if

mwi_active = y
omaj can be set to 117 (or 0

for NULL) or 32 or 255 for all
dntypes
if dntype is not set to u, and
omaj = 6, 7, 9, 10, 12, or 13,
then stdlidx must not = NULL
paac
1-255 if dntype is u
dntype must be set to u
pin_active must not be set

to y if paac = y
if paac is set to y, then

paacx must not be set to 0
(or NULL)
paac must not be set to y if

pin_active = y
spina_home must not be set

to y if pin_active = y
pcs_bc
pgch
1 or 0 (required for dntypes h,

r)
pgnum
1-4 (or 0 for NULL)
pic
00009999 (or 0 for NULL)
pin_active
...................................................................................................................................................................................................................................
401-612-168
123

Feature Description
Table 21

Fields
(continued)
Values
Checks
pref_ev
1-5 (or 0 for NULL)
When n of 5 Vocoder
Preferences (from the group
8K,13K, EVRC, EVRCB, SMV)
are populated, the unique
integer values 1-n must be
used.
pref_evb
1-5 (or 0 for NULL)
When n of 5 Vocoder
used.
pref_8k
1-5 (or 0 for NULL)
When n of 5 Vocoder
used.
pref_13k
1-5 (or 0 for NULL)
When n of 5 Vocoder
used.
pref_smv
1-5 (or 0 for NULL)
When n of 5 Vocoder
used.
projacc
psofpr
qpch_sup
rac1
1255 (0 for NULL)
rac2
0-255 (For user administration

only)
rasa1 - rasa24
Value cannot be 0 if dntype =

h, r, or p
...................................................................................................................................................................................................................................
401-612-168
124

Feature Description
Table 21

Fields
(continued)
Values
Checks
rc
1-255
Value cannot be NULL if

dntype = h, r, or p
rlp_tmr
0, 5-3600 (4095 for NULL)
rpin_type
0-4
sdt_active
smstermres
smsorigres
sendtone
sos_avail
so7_auth

be y.
so8_auth
so15_auth

be y.
so16_auth
so33_auth

be y.
spanc_ancmnt
if spanc_active = y,
spanc_ancmnt must be 1-255.
spina_home
pin_active must not equal y

if spina_home = y
omaj must not equal 32 if

spina_home = y
spina_roam
sppa
1-255 (0 for NULL)
sub_coi
svcalw_c must be set to c or d

if sdt_active = y
omaj must not equal 32 if

spina_roam = y
...................................................................................................................................................................................................................................
401-612-168
125

Feature Description
Table 21

Fields
Values
sub_ocoi
sw
116 (0 for NULL)
tmaj
(continued)
Checks
Value cannot be 0 if dntype

= a, m, or p
corresponding vssw index

must = y (for example, if
sw = 2, then vssw[2] must
= y)
1-3 if dntype is not equal to

u
tmaj must be set to 1 - 3 if

dntype is not equal to u
1-255 if dntype is equal to

u
tmaj must be set to 1-255

and not NULL if dntype is
equal to u
if dntype is not equal to u,

then tmaj must not equal to
3 if Deny Automatic Collect
Call/Mobile Termination
feature is turned off
twc
twc must be set to y if IS41

Call Transfer feature is off and
cp_authct = y
vad_id
000-999 (000 for NULL)
vad_auth must be set to y if

vad_id > 000
vad_auth
1255 (0 for NULL)
1-17 if OIPDN feature

inactive
Value must be set to NULL if

dntype = u
1-255 if OIPDN feature

active
vman_mail
vms_id
000-999 (0 for NULL)
if mrs or mrs_i = y, vms_id

must not = 000
vp_active
vp_active must be set to y

if vp_netinit = y
svcalw_c must be set to c

or svcalw_c must be set to
d if vp_netinit = y
vssw1 - vssw16
sw number is set for the vssw

element, therefore the vssw
element must = y
...................................................................................................................................................................................................................................
401-612-168
126

Feature Description
Table 21

Fields
Values
wect_act
(continued)
Checks
...................................................................................................................................................................................................................................
401-612-168
127
Index
A Appendix A, 86
Appendix B, 118
availability of the feature, 7
.............................................................
C comments, to submit, 3
.............................................................
R requirements of the feature
hardware, 9
software, 8
Revision history, 80
.............................................................
.............................................................
D DBsubquery, 10
S software requirements, 8
DBsubquery Update Capable

Additional Fields, 118
Special Considerations:
DBsubquery, 64
DBsubquery: Special
Considerations, 64
support, to obtain technical, 3
DBsubreport.pl, 37
DBsubsum, 44
documentation, to order, 3
.............................................................
T technical support, to obtain, 3
training, to order or register

for, 3
.............................................................
F Feature implementation, 66
Feature interactions, 65
.............................................................
H hardware requirements, 9
History of revisions, 80
.............................................................
I
Implementing the features, 66
.............................................................
Q Query Fields and Conversion
Tables, 86
...................................................................................................................................................................................................................................
401-612-168
IN-1

Database

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Database

Hochgeladen von

Copyright:

Verfügbare Formate

See notice on first age

Alcatel-Lucent CDMA Network

See notice on first age

Alcatel-Lucent provides a limited warranty to this product.

DBsubquery, DBsubsum, and DBsubreport.pl Optional Feature Description

Structure of hazard statements

Implementing the features

Activating the features/tools

Procedure 1: Prevent interference-ECP

Procedure 4: Prevent all RC/V activity-ECP

Procedure 2: Update backup subscriber databases-ECP

Procedure 6: Verify the backup databases-ECP

Procedure 7: Replace the Master Databases-ECP

Abbreviations and Terminology

Appendix A: Query Fields and Conversion Tables

Appendix B: DBsubquery Update Capable Additional Fields

DBsubquery Command Options

DBsubquery Update Capable Command Line Options

DBsubreport.pl Field Definitions

DBsubsum Field Definitions

IS-53-A Preferred Language (deft_pl Conversions)

DBsubquery Update Capable: Values and Checks

Example 1: Format file

Example 2: Format file

Example 1: Output file with +f/+p Option

Example 2 (Screen 1): Output file with +f/+p Option

Screen and file output format for DBsubquery with +L Option

Screen and file output format for DBsubquery with +l Option

Example 1: Standard DBsubquery Output

Example 2: DBsubquery long output directed to the screen

Example 3 (Screen 1): Displaying the query syntax

Example 3 (Screen 2): Displaying the query syntax

Example 3 (Screen 3): Displaying the query syntax

Display fields screen

Specify value screen

Verify value screen

Example output from DBsubquery +r option

Example: DBsubquery +f/+p option format file

Example: How to create DBsubreport.pl input_file

Example: DBsubreport.pl input_file content

Example: DBsubreport.pl execution

Example: output_file content

Example: output_file1 content

Example: mec_list_file content

Example: output_file1 content (with l option used)

Example of DBsubsum Screen Output

DBsubsum Output Example (Part 1)

DBsubsum Output Example (Part 2)

DBsubsum Output Example (Part 3)

DBsubsum Output Example (Part 4)

DBsubsum Output Example (Part 5)

DBsubsum Output Example (Part 6)

DBsubsum Output Example (Part 7)

DBsubsum Output Example (Part 8)

DBsubsum Output Example (Part 9)

DBsubsum Output Example (Part 10)

DBsubsum Output Example (Part 11)

DBsubsum Output Example (Part 12)

DBsubsum Output Example (Part 13)

DBsubsum Output Example (Part 14)

DBsubsum Output Example (Part 15)

DBsubsum Output Example (Part 16)

DBsubsum Output Example (Part 17)