68P02900W22

DataGen
System Information
GSR9
68P02900W22-S
© 2008 Motorola, Inc. All Rights Reserved.

Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc. assumes no
liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained
herein. Motorola, Inc. reserves the right to make changes to any products described herein to improve reliability,
function, or design, and reserves the right to revise this document and to make changes from time to time in content
hereof with no obligation to notify any person of revisions or changes. Motorola, Inc. does not assume any liability
arising out of the application or use of any product, software, or circuit described herein; neither does it convey
license under its patent rights or the rights of others. It is possible that this publication may contain references to, or
information about Motorola products (machines and programs), programming, or services that are not announced
in your country. Such references or information must not be construed to mean that Motorola intends to announce
such Motorola products, programming, or services in your country.
Copyrights
This document, Motorola products, and 3rd Party Software products described in this document may include
or describe copyrighted Motorola and other 3rd Party supplied computer programs stored in semiconductor
memories or other media. Laws in the United States and other countries preserve for Motorola, its licensors, and
other 3rd Party supplied software certain exclusive rights for copyrighted material, including the exclusive right
to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly,
any copyrighted material of Motorola, its licensors, or the 3rd Party software supplied material contained in the
Motorola products described in this document may not be copied, reproduced, reverse engineered, distributed,
merged or modified in any manner without the express written permission of Motorola. Furthermore, the purchase
of Motorola products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any
license under the copyrights, patents or patent applications of Motorola or other 3rd Party supplied software,
except for the normal non-exclusive, royalty free license to use that arises by operation of law in the sale of a
product.
A list of 3rd Party supplied software copyrights are contained in the Supplemental information section of this
document.
Restrictions
Software and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No part
of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or
translated into any language or computer language, in any form or by any means, without prior written permission
of Motorola, Inc.
License Agreements
The software described in this document is the property of Motorola, Inc and its licensors. It is furnished by express
license agreement only and may be used only in accordance with the terms of such an agreement.
High Risk Materials
Components, units, or 3rd Party products used in the product described herein are NOT fault-tolerant and are NOT
designed, manufactured, or intended for use as on-line control equipment in the following hazardous environments
requiring fail-safe controls: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft Communication
Systems, Air Traffic Control, Life Support, or Weapons Systems (High Risk Activities). Motorola and its supplier(s)
specifically disclaim any expressed or implied warranty of fitness for such High Risk Activities.
Trademarks
Motorola and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service
names are the property of their respective owners.
The CE mark confirms Motorola, Inc. statement of compliance with EU directives applicable to this product. Copies
of the Declaration of Compliance and installation information in accordance with the requirements of EN50385 can
be obtained from the local Motorola representative or by contacting the Customer Network Resolution Center
(CNRC). The 24 hour telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information. Alternatively if you do not have access to CNRC or the
internet, contact the Local Motorola Office.
Jul 2008
Table
of
Contents
Contents
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
System Information: DataGen

Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Version information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Resolution of Service Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Incorporation of Change Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Cross references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Contacting Motorola . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
24–hour support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Questions and comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Security advice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Warnings, cautions, and notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Warnings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
General safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Electromagnetic energy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Caring for the environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
In EU countries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
In non-EU countries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
CMM labeling and disclosure table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Motorola document set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Ordering documents and CD-ROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Document banner definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Data encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Chapter 1: Overview of DataGen

Overview of DataGen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Introduction to DataGen and the Offline MIB . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Overview of DataGen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
DataGen functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Overview of the Offline MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Offline MIB functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
DataGen/Offline MIB integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
The DataGen and OLM platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
DataGen database structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
BSS database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
68P02900W22-S i
Jul 2008
Contents
DataGen and the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Loading network information into DataGen . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Introduction to loading network information . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Gathering network information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
The DataGen Directory Structure (DDS) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Main structure of the DDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Sub-structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
The Offline MIB directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
The Offline MIB file structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Main structure of the Offline MIB directory . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Supported platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Overview of supported platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Chapter 2: User and Group management using the usertool

User and Group management using the usertool. . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Introduction to usertool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Common Desktop Environment Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Usertool - Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Procedure list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
DataGen User management using the usertool. . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Introduction to user management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
User management parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
User administration utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Add a new user account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Modify a user account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Rename a user account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Delete a user account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
DataGen Group management using the usertool . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Introduction to group management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Group management parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Group Administration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Add a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Modify group information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Rename a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Delete a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Chapter 3: Operating DataGen

Overview of operating DataGen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
About this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Procedures for operating DataGen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Defining environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Overview of environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
HEX or decimal representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Version list order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Time slot order equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Automated running of Revgen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Default file import path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Default export path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Define default text editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Override area lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Output all elements in a script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Display only generic algorithm details in alg.mcd table . . . . . . . . . . . . . . . . . . . 3-8
DataGen - startup and shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Introduction to startup and shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Startup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
ii 68P02900W22-S
Jul 2008
System Information: DataGen Contents
Administration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12

Overview of tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Changing permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Optimizing the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Viewing the log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Customizing parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Installing the Options Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Database administration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Monitoring file and database capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Running usage script as a cronjob . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Verifying usage cronjob . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Running usage script manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Warning messages issued . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Reloading the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Dropping and recreating the db_dg Informix database. . . . . . . . . . . . . . . . . . . . 3-22
Importing existing CM database objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Creating a country/network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Overview of creating a country/network . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Country Admin option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Country Administration window - An Overview . . . . . . . . . . . . . . . . . . . . . . . 3-28
Creating a country . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
Editing a country . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
Creating a network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
Deleting a country/network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
Overview of deleting a country/network . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
Deleting the network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
Deleting the country . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
Creating a BSS area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
Overview of creating a BSS area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
New BSS Area window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
Creating a BSS area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
Opening a BSS area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39
Opening a BSS area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39
Copying a BSS area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41
Copying a BSS area procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41
Deleting a BSS area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43
Deleting an existing BSS area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43
Configuring BSS areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45
Introduction to configuring the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45
Explanation of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45
Functions and MCDF table relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45
Basic BSS with TS switch - Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47
Copying a BSS area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48
Expanding the BSS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48
Daisy Chain configuration with TS switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52
Overview of Daisy Chain configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52
Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52
Daisy chain configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53
The Service window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56
Functions of the Service window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56
Service window toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56
Service window menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58
File menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58
Edit menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63
Services menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-64
68P02900W22-S iii
Jul 2008
Contents
Converting a CM database object file to a script file . . . . . . . . . . . . . . . . . . . . . . . 3-66

Introduction to creating a script file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66
Invoking Revgen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66
Revgen window description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66
File menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67
Information area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67
Data area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67
Toolbar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67
Activating Revgen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-68
Activating auto Revgen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70
Completion of Revgen process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70
Generating a database script file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71
Overview of database script files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71
Running the script file generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71
Viewing a database script file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72
xedit window description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73
Using the toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74
File information areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74
File display area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74
Alternative text editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74
Viewing and editing DataGen files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77
Overview of editing DataGen files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77
Table Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77
Generic Table Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77
Topology Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77
Upgrader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78
Using the Table Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-79
Running the Table Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-79
Table Controller functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-80
User controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-80
Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-80
Command buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-80
File select buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-81
File status display area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-81
MCDF table files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-81
Creating MCDF files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-84
MCDF file procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-84
MCDF table editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-86
File status icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-88
Using the Generic Table Editor (GTE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-90
Introduction to the Generic Table Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-90
The File menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-90
The Edit menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-96
Fill Cells window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-97
Format menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-99
MCDF key equivalents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-104
Using the Topology Viewer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-105
Introduction to the Topology Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-105
Invoking the Topology Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-105
Using the Topology Viewer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-106
Cage hardware configuration button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-107
The MMI button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-109
Path File button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-109
Increase magnification button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-109
Decrease magnification button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-109
Generating a hardware report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-110
Overview of hardware reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-110
Procedure for generating a hardware report. . . . . . . . . . . . . . . . . . . . . . . . . 3-110
iv 68P02900W22-S
Jul 2008
Converting a database script file to a CM database object file . . . . . . . . . . . . . . . . . . 3-112

Overview of conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-112
Producing a CM database object using SYSGEN mode. . . . . . . . . . . . . . . . . . . . 3-112
Producing a CM database object using the DataGen binary object compiler . . . . . . . . . 3-112
Exporting object files to the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-115
Overview of exporting object files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-115
Exporting multiple binary object files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-115
Exporting a single binary object file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-116
Exporting OLM binary object files to the OMC . . . . . . . . . . . . . . . . . . . . . . . . 3-117
Difference Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-118
Introduction to the Difference Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-118
The Difference Reporter window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-118
Select BSS Area Details window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-119
Difference Reporter Information window . . . . . . . . . . . . . . . . . . . . . . . . . . 3-121
Difference Reporter Report window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-122
Upgrader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123
Overview of the Upgrade function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123
Upgrade BSS Area window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123
Upgrading a BSS Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-125
Upgrade multiple BSS areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-127
Resolving upgrade problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-127
Overview of DARBC and Enhanced XBL . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-129
Batch processing of binary object files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-130
Overview of batch processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-130
Revgen multiple binary object files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-131
Upgrade multiple binary object files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-134
Compile multiple MMI scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-135
Chapter 4: Operating the Offline MIB

Introduction to the Offline MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Overview of the Offline MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Task list before using OLM GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Task list for using the OLM GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Additional OLM tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Levels of users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Troubleshooting and other tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
OLM environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Using the cmutil.olm command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Starting/creating a network configuration in the OLM . . . . . . . . . . . . . . . . . . . . . . 4-6
Introduction to network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Starting the OLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Creating a network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Starting/exiting the OLM GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Starting the OLM GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Exiting the OLM GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Shutting down the OLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Front panel icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Offline MIB front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
About the Offline MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Configuration management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Find . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Xterm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
68P02900W22-S v
Jul 2008
Contents
Expert Offline MIB front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17

Finding devices and attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Overview of the Find function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Finding a Network Element, PCU, Site, or Cell. . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Finding an NE, PCU, Site, or Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Examples of using Find . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
Finding an attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Overview of finding attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Using the Navigation Tree: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Procedure list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Opening and closing a Navigation Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Opening the Navigation Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Warning window Invalid NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
Resolving inconsistencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
Closing the Navigation Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
Moving levels on a Navigation Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
Prerequisite to moving levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
Procedure for moving levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
Panner and porthole . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
Creating a BSS/RXCDR from the Navigation Tree . . . . . . . . . . . . . . . . . . . . . . . . 4-32
Introduction to creating an NE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
Procedure for creating a BSS or RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
Audit: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
Introduction to auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
Ways to audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
Running an audit from the Navigation Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
Introduction to auditing from the Navigation Tree . . . . . . . . . . . . . . . . . . . . . . 4-35
Audit from the Navigation Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
Modifying the network configuration from the Navigation Tree . . . . . . . . . . . . . . . . . 4-37
Device management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
Configuring cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
CellXchange: overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
Introduction to CellXchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
Overwrite a BSS/RXCDR binary object file . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
Overview of overwrite feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
Procedure for overwriting a BSS Binary object file. . . . . . . . . . . . . . . . . . . . . . 4-39
Verify and save overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42
Introduction to applying changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42
Verify and save NE database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43
Verify a network element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43
Save a network element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45
Verify and save network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Verify network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Aborting a verify network in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
Saving a network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51
Aborting a save network in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
Deleting a network configuration in the OLM . . . . . . . . . . . . . . . . . . . . . . . . . . 4-53
Introduction to deleting a network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-53
Delete network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-53
Network Expansion: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55
Overview of Network Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55
Additional OLM features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56
List of additional tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56
Using the autoclose function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-57
Overview of autoclose feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-57
Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-57
Procedure for using autoclose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-57
vi 68P02900W22-S
Jul 2008
Deleting a BSS or RXCDR from the Navigation Tree . . . . . . . . . . . . . . . . . . . . . . . 4-58

Introduction to deleting BSS or RXCDR network elements. . . . . . . . . . . . . . . . . . 4-58
Deleting BSS or RXCDR network elements . . . . . . . . . . . . . . . . . . . . . . . . . 4-58
Scheduling an audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-60
List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-60
Creating a scheduled audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-60
Modifying a scheduled audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-65
Deleting a scheduled audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-66
Auditing logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-67
List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-67
Viewing an audit log list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-67
Aborting an audit in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68
Inconsistency reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-69
Viewing an audit inconsistency report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-69
Deleting an audit log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-71
Audit log management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72
Overview of audit log management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72
Setting the delete period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72
Reload NE database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74
Introduction to reloading an NE database . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74
Procedure for reloading an NE database. . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74
Realign a network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-76
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-76
Procedure for realigning a network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-76
Compress or uncompress an OLM network . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78
Overview of compress and uncompress . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78
Compress a network procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78
Uncompress a network procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-79
Troubleshooting the OLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-80
Introduction to troubleshooting the OLM . . . . . . . . . . . . . . . . . . . . . . . . . . 4-80
OLM fails to start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-80
Database errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-81
General errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82
Specific operation fails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-83
Import errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-83
Introduction to the force shutdown feature . . . . . . . . . . . . . . . . . . . . . . . . . 4-83
Force shutdown OLM procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84
Reinitialize database procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-85
Chapter 5: Command line tools

Overview of command line tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Command line functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
User options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Copy Area (ca) command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Command line options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Example Copy Area usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
MMI Combiner (combine) command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
68P02900W22-S vii
Jul 2008
Contents
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Compile MMI script (compile) command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Auto-compile MMI script command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Example auto_compile usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Running cron jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Compress/uncompress binary object files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Delete database object (del) command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
MCDF filter command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
MMI command generator (gcmd) command . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Optimize DataGen database (dbaccess) command . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Lock/unlock BSS area (lock_adm) command . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
viii 68P02900W22-S
Jul 2008
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
Revgen command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
Auto-Revgen command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
Toggle permissions (tp) command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
Version upgrader (upg) command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29
Example of upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29
Auto-upgrader command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
Country administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
Introduction to country administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
Command Line Interface (CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
Invoking xcadm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
Using the xcadm GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Data fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
Action buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
CADM utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
Chapter 6: MCDF tables

Overview of MCDF tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Scope of MCDF tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
MCDF BSS and RXCDR tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
BSS table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Description of BSS table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Site (BTS-specific) table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
68P02900W22-S ix
Jul 2008
Contents
Description of Site (BTS-specific) table . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9

Cabinet table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Description of Cabinet table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Hardware table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Description of Hardware table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Generics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25
Description of Generics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25
Layout of elements in the MCDF Generics table . . . . . . . . . . . . . . . . . . . . . . . . . 6-26
Timer table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-45
Description of Timer table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-45
Layout of elements in the MCDF Timer table . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46
Modify Value table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-51
Description of Modify Value table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-51
Circuit table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-54
Description of Circuit table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-54
Channel table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-57
Description of Channel table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-57
Links table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-59
Description of Links table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-59
Paths table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-61
Description of Paths table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-61
LAPD table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-63
Description of LAPD table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-63
Cell table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-65
Description of Cell table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-65
Statistics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-75
Description of Statistics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-75
Layout of elements in the MCDF Statistics table . . . . . . . . . . . . . . . . . . . . . . . . . 6-76
Specifics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-108
Description of Specifics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-108
Layout of elements in the MCDF Specifics table . . . . . . . . . . . . . . . . . . . . . . . . . 6-110
RTF table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-154
Description of RTF table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-154
DRI table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-159
Description of DRI table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-159
Algorithm data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-163
Description of Algorithm data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-163
Neighbor table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-165
Description of Neighbor table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-165
Throttles table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-172
Description of Throttles table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-172
EAS table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-173
Description of EAS table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-173
Daughter table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-174
Description of Daughter table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-174
PIX table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-175
Description of PIX table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-175
KSW table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-176
Description of KSW table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-176
NSVC table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-178
Description of NSVC table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-178
Hop table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-179
Description of Hop table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-179
ACS table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-184
Description of ACS table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-184
Test Neighbor table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-192
Description of the Test Neighbor table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-192
Nail Connection Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-194
x 68P02900W22-S
Jul 2008
Contents
Description of the Nail Connection table . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-194
68P02900W22-S xi
Jul 2008
Contents
xii 68P02900W22-S
Jul 2008
List
of
Figures
List of Figures
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Figure 1-1: DataGen GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Figure 1-2: Offline MIB - Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Figure 1-3: DataGen/Offline MIB functions . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Figure 1-4: DataGen in a GSM environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Figure 1-5: DataGen-OMC integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Figure 1-6: Loading network information into DataGen . . . . . . . . . . . . . . . . . . . . . 1-10
Figure 1-7: Creating MCDF files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Figure 1-8: DataGen directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Figure 1-9: Example of Offline MIB directory structure . . . . . . . . . . . . . . . . . . . . . 1-13
Figure 1-10: Example of Offline MIB file structure. . . . . . . . . . . . . . . . . . . . . . . . 1-13
Figure 2-1: CDE desktop - front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Figure 2-2: The usertool icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Figure 2-3: CDE desktop front panel with open OMC Admin drawer. . . . . . . . . . . . . . . 2-5
Figure 2-4: Usertool menu window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Figure 3-1: Administration menu - omcadmin user. . . . . . . . . . . . . . . . . . . . . . . . 3-13
Figure 3-2: Permissions window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Figure 3-3: Confirm permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Figure 3-4: Administration menu - non-omcadmin user . . . . . . . . . . . . . . . . . . . . . 3-15
Figure 3-5: Example of a logfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Figure 3-6: Preferences window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Figure 3-7: Options Object Tool window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Figure 3-8: Country Administration window . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Figure 3-9: CADM Country File window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
Figure 3-10: CADM message window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
Figure 3-11: CADM Network File window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
Figure 3-12: New BSS Area window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
Figure 3-13: Warning message: name exceeds maximum valid length . . . . . . . . . . . . . . 3-37
Figure 3-14: Overwrite BSS Area Confirmation window . . . . . . . . . . . . . . . . . . . . . 3-37
Figure 3-15: The Service window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
Figure 3-16: Open BSS Area window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39
Figure 3-17: Locked Information window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40
Figure 3-18: Copy BSS Area window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41
Figure 3-19: Delete BSS Area window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43
Figure 3-20: Basic BSS with TS Switch - expanded . . . . . . . . . . . . . . . . . . . . . . . 3-51
Figure 3-21: Service window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56
Figure 3-22: Database Object window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59
Figure 3-23: Import Object - Information window . . . . . . . . . . . . . . . . . . . . . . . . 3-60
Figure 3-24: Export Object - Information window . . . . . . . . . . . . . . . . . . . . . . . . 3-61
Figure 3-25: History - Information window . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-62
Figure 3-26: Revgen window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-68
Figure 3-27: Running Revgen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-69
Figure 3-28: Invalid Options Object message . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72
Figure 3-29: Viewing a database script file . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73
Figure 3-30: Viewing an MMI script with vi . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-76
Figure 3-31: Partial view of typical Table Controller display . . . . . . . . . . . . . . . . . . 3-79
68P02900W22-S xiii
Jul 2008
List of Figures
Figure 3-32: Generics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-87

Figure 3-33: New MCDF input file message . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-91
Figure 3-34: MCDF Input File - Open option . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-91
Figure 3-35: Save To File window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-93
Figure 3-36: Print Setup window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-94
Figure 3-37: Print Table window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-95
Figure 3-38: Fill Cells window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-97
Figure 3-39: Find window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-100
Figure 3-40: Goto Cell window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-101
Figure 3-41: Replace window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-102
Figure 3-42: Topology Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-106
Figure 3-43: Topology Viewer menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-107
Figure 3-44: The Cage Number window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-107
Figure 3-45: The Cage Description window . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-108
Figure 3-46: Viewing a hardware report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-111
Figure 3-47: Binary Object Compiler window . . . . . . . . . . . . . . . . . . . . . . . . . . 3-113
Figure 3-48: Difference Reporter window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-118
Figure 3-49: Select BSS Area Details window . . . . . . . . . . . . . . . . . . . . . . . . . . 3-119
Figure 3-50: Difference Reporter - Information window . . . . . . . . . . . . . . . . . . . . . 3-121
Figure 3-51: Difference Reporter - Report window. . . . . . . . . . . . . . . . . . . . . . . . 3-122
Figure 3-52: Upgrade BSS Area window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123
Figure 3-53: Locked Information window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-125
Figure 3-54: Successful Upgrade Status window . . . . . . . . . . . . . . . . . . . . . . . . 3-126
Figure 3-55: Batch Tool window with Revgen selected. . . . . . . . . . . . . . . . . . . . . . 3-131
Figure 3-56: Revgen Batch Confirmation window . . . . . . . . . . . . . . . . . . . . . . . . 3-132
Figure 3-57: Revgen Batch Monitor window . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-133
Figure 3-58: Compile Batch Monitor window . . . . . . . . . . . . . . . . . . . . . . . . . . 3-136
Figure 4-1: Offline MIB Network Configurations window . . . . . . . . . . . . . . . . . . . . 4-7
Figure 4-2: OLM Network configuration creation window . . . . . . . . . . . . . . . . . . . . 4-7
Figure 4-3: Starting the OLM - Confirmation window . . . . . . . . . . . . . . . . . . . . . . 4-10
Figure 4-4: Opening a Network Configuration - Status window . . . . . . . . . . . . . . . . . 4-11
Figure 4-5: Offline MIB front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Figure 4-6: GUI Exit - Confirmation window . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Figure 4-7: OLM Shutdown Confirmation window . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Figure 4-8: Binary Database errors and warnings window for a Network Element. . . . . . . . 4-13
Figure 4-9: Expert desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Figure 4-10: Find window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Figure 4-11: Find window with a Cell and Navigation Tree selected . . . . . . . . . . . . . . . 4-21
Figure 4-12: Find Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Figure 4-13: Navigation Tree window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Figure 4-14: Invalid NEs window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
Figure 4-15: Navigation Tree window - showing panner . . . . . . . . . . . . . . . . . . . . . 4-31
Figure 4-16: BSS Binary configurations creation window . . . . . . . . . . . . . . . . . . . . 4-32
Figure 4-17: Information window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
Figure 4-18: Audit Inconsistency List window . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
Figure 4-19: BSS Binary configurations window . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
Figure 4-21: Binary Database error and warnings window. . . . . . . . . . . . . . . . . . . . 4-44
Figure 4-22: Offline MIB Database Operations window . . . . . . . . . . . . . . . . . . . . . 4-47
Figure 4-23: Offline MIB Verify Operation Monitor window . . . . . . . . . . . . . . . . . . . 4-48
Figure 4-24: Binary Database error and warnings window. . . . . . . . . . . . . . . . . . . . 4-49
Figure 4-25: Offline MIB Save Operation Monitor window . . . . . . . . . . . . . . . . . . . . 4-51
Figure 4-26: Delete network Confirmation window . . . . . . . . . . . . . . . . . . . . . . . 4-53
Figure 4-27: Deleting a BSS or RXCDR - Confirmation window . . . . . . . . . . . . . . . . . 4-58
Figure 4-28: Admin Options window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-61
Figure 4-29: Audit Scheduler window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-62
Figure 4-30: auSchedule Detailed View <Create> window . . . . . . . . . . . . . . . . . . . 4-63
Figure 4-31: Audit Logs window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68
xiv 68P02900W22-S
Jul 2008
List of Figures
Figure 4-32: Audit Logs Abort Confirmation window. . . . . . . . . . . . . . . . . . . . . . . 4-69

Figure 4-33: Audit Log Management window in Edit mode . . . . . . . . . . . . . . . . . . . 4-72
Figure 4-34: Reload Confirmation window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74
Figure 4-36: Compress from the OLM Network Configurations window . . . . . . . . . . . . . 4-79
Figure 4-37: Confirmation window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84
Figure 4-38: Reinitialize DataBase - Confirmation window. . . . . . . . . . . . . . . . . . . . 4-85
Figure 5-1: Country Admin in use confirmation window . . . . . . . . . . . . . . . . . . . . . 5-33
Figure 5-2: The xcadm GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Figure 6-1: Non-collocated BSS hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Figure 6-2: RXCDR Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
68P02900W22-S xv
Jul 2008
List of Figures
xvi 68P02900W22-S
Jul 2008
List
of
Tables
List of Tables
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Table 1-1: Supported platforms in GSR9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15

Table 3-1: Main menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Table 3-2: Function - MCDF table relationships . . . . . . . . . . . . . . . . . . . . . . . . . 3-46
Table 3-3: Revgen window file menu options. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67
Table 3-4: Revgen window file menu options. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67
Table 3-5: Table Controller - menu bar File and Select options. . . . . . . . . . . . . . . . . . 3-80
Table 3-6: File status icons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-88
Table 3-7: File menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-90
Table 3-8: Printer setup - menu buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-94
Table 3-9: Printer setup - data fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-94
Table 3-10: Printer setup - action buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-95
Table 3-11: Edit menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-97
Table 3-12: Fill cells - data fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-98
Table 3-13: Fill cells - options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-98
Table 3-14: Fill cells - action buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-98
Table 3-15: Format menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-99
Table 3-16: Find window - enable buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-100
Table 3-17: Action button definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-100
Table 3-18: Goto Cell - data fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-101
Table 3-19: Goto Cell - action buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-101
Table 3-20: Replace window - data fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103
Table 3-21: Replace window - enable buttons . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103
Table 3-22: Replace window - option buttons . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103
Table 3-23: Replace window - actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103
Table 3-24: Hot keys for MCDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-104
Table 3-25: Upgrader - list boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-124
Table 3-26: Upgrader - action buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-124
Table 4-1: Administrative tasks and user types . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Table 4-2: Reported inconsistencies or errors . . . . . . . . . . . . . . . . . . . . . . . . . . 4-70
Table 4-3: Realign a network - cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-76
Table 4-4: OLM fails to start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-80
Table 4-5: Database Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-81
Table 4-6: General operating errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82
Table 4-7: Specific operation error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-83
Table 4-8: Importing NE software errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-83
Table 5-1: Command line tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Table 5-2: Command line options (ca command) . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Table 5-3: Command line options (auto_compile command) . . . . . . . . . . . . . . . . . . 5-8
Table 5-4: Command line options (del command) . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Table 5-5: Command line options (filter command) . . . . . . . . . . . . . . . . . . . . . . . 5-14
Table 5-6: Valid file names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Table 5-7: Command line options (gcmd command) . . . . . . . . . . . . . . . . . . . . . . . 5-17
Table 5-8: Command Line options (lock_adm command) . . . . . . . . . . . . . . . . . . . . 5-20
Table 5-9: Command line options (revgen command) . . . . . . . . . . . . . . . . . . . . . . 5-22
Table 5-10: Command line options (auto_revgen command) . . . . . . . . . . . . . . . . . . 5-25
68P02900W22-S xvii
Jul 2008
List of Tables
Table 5-11: Command line options (tp command) . . . . . . . . . . . . . . . . . . . . . . . . 5-27

Table 5-12: Command line options (upg command) . . . . . . . . . . . . . . . . . . . . . . . 5-28
Table 5-13: Command line options (auto_upgrade command). . . . . . . . . . . . . . . . . . 5-30
Table 5-14: Action buttons definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
Table 6-1: BSS-specific table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Table 6-2: Valid Frequency Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Table 6-3: BTS-specific table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Table 6-4: Cabinet table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Table 6-5: Frequency Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
Table 6-6: Option dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
Table 6-7: Hardware table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Table 6-8: Generics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25
Table 6-9: Generics table - Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26
Table 6-10: Timer table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-45
Table 6-11: Timer table - elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46
Table 6-12: Modify Value table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-51
Table 6-13: Circuit table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-54
Table 6-14: Values of mtl_rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-56
Table 6-15: Channel table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-57
Table 6-16: Links table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-59
Table 6-17: Paths table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-61
Table 6-18: LAPD table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-63
Table 6-19: Cell table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-65
Table 6-20: Statistics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-75
Table 6-21: Statistics table - Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-76
Table 6-22: Specifics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-108
Table 6-23: Specifics table - Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-110
Table 6-24: RTF table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-154
Table 6-25: Range and values for rtf_ds0_count . . . . . . . . . . . . . . . . . . . . . . . . . 6-158
Table 6-26: DRI table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-159
Table 6-27: Algorithm data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-163
Table 6-28: Neighbor table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-165
Table 6-29: Throttles table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-172
Table 6-30: EAS table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-173
Table 6-31: Daughter table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-174
Table 6-32: PIX table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-175
Table 6-33: KSW table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-176
Table 6-34: NSVC table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-178
Table 6-35: Hop table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-179
Table 6-36: ACS table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-184
Table 6-37: Test Neighbor table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-192
Table 6-38: Nail Connection table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-194
xviii 68P02900W22-S
Jul 2008
About
This
Manual
System Information: DataGen

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
What is covered in this manual?
The DataGen product provides the user with the capabilities for performing offline configuration
management of Motorola GSM network entities (NEs). It is a collection of software tools used
to produce, edit, and update BSS databases.
The Offline MIB (OLM) can create new networks, and visualize and validate networks before
deployment into a live network. It has a common User Interface (UI) with the online Operations
and Maintenance Centre (OMC). BSS binary files are used to create the network which is
displayed in the hierarchical structure called the Navigation Tree. The manual is organized
into the following chapters:
• Chapter 1 Overview of DataGen, provides the user with the capabilities for performing
offline configuration management of Motorola GSM network entities (NEs).
• Chapter 2 User and Group management using the usertool, contains information on user
and group management using the OMC usertool. In addition, information is also available
in the following manuals:
DataGen/OLM Clean Install Guide provides information about installation procedures.
DataGen/OLM Upgrade and Migration Guide provides information about upgrade and
migration procedures.
Both guides are included in the manual Software Release Notes: DataGen
(68P02900W76).
• Chapter 3 Operating DataGen, describes the procedures used for operating DataGen and
its associated administrative tools.
• Chapter 4 Operating the Offline MIB, describes the procedures used for operating the
Offline MIB.
Information on performing Cell Xchange and Network Expansion from the Offline
MIB is provided in the manual Installation Configuration: GSM System Configuration
(68P02901W17).
• Chapter 5 Command line tools, provides information on Command line tools.
• Chapter 6 MCDF tables, provides description on Motorola Customer Data Format (MCDF)
tables.
For detailed information about the ranges, default values and dependencies of the parameters
in the MCDF tables, refer to the manual Technical Description: BSS Command Reference
(68P02901W23).
68P02900W22-S 1
Jul 2008
Pay particular attention to any cautions given in this manual and follow the instructions exactly.
Failure to do so could result in problems running the software.
2 68P02900W22-S
Jul 2008
Revision history
Revision history
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The following sections show the revision status of this document.
Version information
The following table lists the supported versions of this manual in order of issue:
Issue Date of issue Remarks

Q Sep 2004 GSM Software Release 7 Half-Rate
R Nov 2006 GSM Software Release 8 GMR-02
S Apr 2008 GSM Software Release 9
S Jul 2008 GSM Software Release 9 FP1
Resolution of Service Requests
The following Service Requests are resolved in this document:
Service
CMBP Number Remarks
Request
N/A N/A N/A
Incorporation of Change Notices
The following Change Notices (CN) are incorporated in this document:
CN Date CN Number Title
N/A N/A N/A
68P02900W22-S 3
Jul 2008
General information
General information
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Purpose
Motorola cellular communications documents are intended to instruct and assist personnel in
the operation, installation, and maintenance of the Motorola cellular infrastructure equipment
and ancillary devices. It is recommended that all personnel engaged in such activities be
properly trained by Motorola.
Motorola disclaims all liability whatsoever, implied or express, for any risk of damage, loss or
reduction in system performance arising directly or indirectly out of the failure of the customer,
or anyone acting on the customer's behalf, to abide by the instructions, system parameters,
or recommendations made in this document.
These documents are not intended to replace the system and equipment training offered by
Motorola. They can be used to supplement and enhance the knowledge gained through such
training.
NOTE
If this document was obtained when attending a Motorola training course, it will
not be updated or amended by Motorola. It is intended for TRAINING PURPOSES
ONLY. If it was supplied under normal operational circumstances, to support a major
software release, then corrections are supplied automatically by Motorola and posted
on the Motorola customer website.
Cross references
References made to external publications are shown in italics. Other cross references,
emphasized in blue text in electronic versions, are active links to the references.
This document is divided into numbered chapters that are divided into sections. Sections are
not numbered, but are individually named at the top of each page, and are listed in the table of
contents.
4 68P02900W22-S
Jul 2008
Text conventions
Text conventions
The following conventions are used in the Motorola cellular infrastructure documents to
represent keyboard input text, screen output text, and special key sequences.
Input
Characters typed in at the keyboard are shown like this.

Items of interest within a command appear like this.
Output
Messages, prompts, file listings, directories, utilities, and environmental

variables that appear on the screen are shown like this.
Items of interest within a screen display appear like this.
Special key sequences
Special key sequences are represented as follows:
CTRL-c or CTRL+C Press the Ctrl and C keys at the same time.
CTRL-SHIFT-c or Press the Ctrl, Shift, and C keys at the same time.
CTRL+SHIFT+C
ALT-f or ALT+F Press the Alt and F keys at the same time.
ALT+SHIFT+F11 Press the Alt, Shift and F11 keys at the same time.
¦ Press the pipe symbol key.
RETURN or ENTER Press the Return or Enter key.
68P02900W22-S 5
Jul 2008
Contacting Motorola
Contacting Motorola
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Motorola appreciates feedback from the users of our documents.
24–hour support
If you have problems regarding the operation of your equipment, contact the Customer Network
Resolution Center (CNRC) for immediate assistance. The 24–hour telephone numbers are listed
at https://mynetworksupport.motorola.com. Select Customer Network Resolution Center
contact information. Alternatively if you do not have access to CNRC or the internet, contact
the Local Motorola Office.
Questions and comments
Send questions and comments regarding user documentation to the email address:
mydocs@motorola.com.
Errors
To report a documentation error, call the CNRC (Customer Network Resolution Center) and
provide the following information to enable CNRC to open an SR (Service Request):
• The document type
• The document title, part number, and revision character
• The page number with the error
• A detailed description of the error and if possible the proposed solution
6 68P02900W22-S
Jul 2008
Security advice
Security advice
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Motorola systems and equipment provide security parameters that can be configured by the
operator based on their particular operating environment. Motorola recommends setting and
using these parameters following industry recognized security practices. Security aspects
to be considered are protecting the confidentiality, integrity, and availability of information
and assets. Assets include the ability to communicate, information about the nature of the
communications, and information about the parties involved.
In certain instances, Motorola makes specific recommendations regarding security practices.

The implementation of these recommendations and final responsibility for the security of the
system lies with the operator of the system.
Contact the Customer Network Resolution Center (CNRC) for assistance. The 24–hour
telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information, from the menu located to the left of the
Login box. Alternatively if you do not have access to CNRC or the internet, contact the Local
Motorola Office.
68P02900W22-S 7
Jul 2008
Warnings, cautions, and notes
Warnings, cautions, and notes

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The following describes how warnings and cautions are used in this document and in all
documents of this Motorola document set.
Warnings
Warnings precede instructions that contain potentially hazardous situations. Warnings are
used to alert the reader to possible hazards that could cause loss of life or physical injury. A
warning has the following format:
WARNING
Warning text and consequence for not following the instructions in the warning.
Cautions
Cautions precede instructions and are used when there is a possibility of damage to systems,
software, or individual items of equipment within a system. However, this damage presents
no danger to personnel. A caution has the following format:
CAUTION
Caution text and consequence for not following the instructions in the caution.
Notes
A note means that there is a possibility of an undesirable situation or provides additional

information to help the reader understand a topic or concept. A note has the following format:
NOTE
Note text.
8 68P02900W22-S
Jul 2008
Safety
Safety
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
General safety
The following general safety guidelines apply to Motorola equipment:

• The power jack and mating plug of the power cable must meet International
Electrotechnical Commission (IEC) safety standards.
NOTE
Refer to Grounding Guideline for Cellular Radio Installations – 68P81150E62.
• Power down or unplug the equipment before servicing.
• Using non-Motorola parts for repair could damage the equipment or void warranty.
Contact Motorola Warranty and Repair for service and repair instructions.
• Portions of Motorola equipment may be damaged from exposure to electrostatic discharge.

Use precautions to prevent damage.
Electromagnetic energy
Relevant standards (USA and EC) applicable when working with RF equipment are:
• ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure
to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.
• Council recommendation of 12 July 1999 on the limitation of exposure of the general

public to electromagnetic fields (0 Hz to 300 GHz) (1999/519/EC) and respective national
regulations.
• Directive 2004/40/EC of the European Parliament and of the Council of 29 April 2004 on
the minimum health and safety requirements regarding the exposure of workers to the
risks arising from physical agents (electromagnetic fields) (18th individual Directive within
the meaning of Article 16(1) of Directive 89/391/EEC).
68P02900W22-S 9
Jul 2008
Caring for the environment
Caring for the environment

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The following information describes national or regional requirements for the disposal of
Motorola supplied equipment and for the approved disposal of surplus packaging.
Contact the Customer Network Resolution Center (CNRC) for assistance. The 24–hour
telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information. Alternatively if you do not have access
to CNRC or the internet, contact the Local Motorola Office.
In EU countries
The following information is provided to enable regulatory compliance with the European Union
(EU) directives identified and any amendments made to these directives when using Motorola
equipment in EU countries.
Disposal of Motorola equipment
European Union (EU) Directive 2002/96/EC Waste Electrical and Electronic Equipment (WEEE)
Do not dispose of Motorola equipment in landfill sites. In the EU, Motorola in conjunction
with a recycling partner ensures that equipment is collected and recycled according to the
requirements of EU environmental law.
Disposal of surplus packaging
European Parliament and Council Directive 94/62/EC Packaging and Packaging Waste
Do not dispose of surplus packaging in landfill sites. In the EU, it is the individual recipient’s
responsibility to ensure that packaging materials are collected and recycled according to the
requirements of EU environmental law.
In non-EU countries
In non-EU countries, dispose of Motorola equipment and all surplus packaging in accordance
with national and regional regulations.
10 68P02900W22-S
Jul 2008
CMM labeling and disclosure table
CMM labeling and disclosure table

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The People’s Republic of China requires that our products comply with China Management
Methods (CMM) environmental regulations. (China Management Methods refers to the
regulation Management Methods for Controlling Pollution by Electronic Information Products.)
Two items are used to demonstrate compliance; the label and the disclosure table.
The label is placed in a customer visible position on the product.

• Logo 1 means the product contains no substances in excess of the maximum concentration
value for materials identified in the China Management Methods regulation.
• Logo 2 means that the product may contain substances in excess of the maximum
concentration value for materials identified in the China Management Methods regulation,
and has an Environmental Friendly Use Period (EFUP) in years. The example shown
uses 50 years.
Logo 1 Logo 2
The Environmental Friendly Use Period (EFUP) is the period (in years) during which the Toxic
and Hazardous Substances (T&HS) contained in the Electronic Information Product (EIP)
will not leak or mutate causing environmental pollution or bodily injury from the use of the
EIP. The EFUP indicated by the Logo 2 label applies to a product and all its parts. Certain
field-replaceable parts, such as battery modules, can have a different EFUP and are marked
separately.
The Disclosure table is intended only to communicate compliance with China requirements.
It is not intended to communicate compliance with EU RoHS or any other environmental
requirements.
68P02900W22-S 11
Jul 2008
Motorola document set
Motorola document set

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Motorola document sets provide the information to operate, install, and maintain the
Motorola equipment.
Ordering documents and CD-ROMs
With internet access available, to view, download, or order documents (original or revised), visit
the Motorola Lifecycles Customer web page at https://mynetworksupport.motorola.com, or
contact your Motorola account representative.
Without internet access available, order hard-copy documents or CD-ROMs from your Motorola
Local Office or Representative.
If Motorola changes the content of a document after the original printing date, Motorola
publishes a new version with the same part number but a different revision character.
Document banner definitions
A banner indicates that some information contained in the document is not yet approved for
general customer use. A banner is oversized text on the bottom of the page, for example,
PRELIMINARY — UNDER DEVELOPMENT.
Data encryption
In order to avoid electronic eavesdropping, data passing between certain elements in the
network is encrypted. In order to comply with the export and import requirements of particular
countries, this encryption occurs at different levels. The encryption may be individually
standardized or may not be present at all in some parts of the network in which it is normally
implemented. The document set covers encryption as if fully implemented. Limitations on the
encryption included in the particular software being delivered, are covered in the Release Notes
that accompany the individual software release.
12 68P02900W22-S
Jul 2008
Chapter
Overview of DataGen
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02900W22-S 1-1
Jul 2008
Overview of DataGen Chapter 1: Overview of DataGen
Overview of DataGen
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to DataGen and the Offline MIB
The DataGen tool provides the user with the capabilities for performing offline configuration
management of Motorola GSM network entities (NEs). It comprises of a collection of software
tools used to produce, edit, and update BSS databases. The database is a binary file containing
details specific to a BSS and its configuration.
DataGen is a flexible tool that reduces the time and effort required to produce accurate BSS
databases. The concept is that of front-office and back-office data management system. The
OMC (front office) incorporates the live data on the GSM network entities, and the back office
(DataGen) incorporates the offline data. Changes to the network can be carried out and verified
through the Offline MIB (OLM) before deployment to the network.
Overview of DataGen
DataGen converts BSS binary database objects into a specific database format (Informix). The
Informix database contains the following information:
• A representation of the information required to create a SYSGEN script for all supported
Base Station System (BSS) Releases.
This information includes the details relating to the syntax, parameters, and their
associated range values for the Man Machine Interface (MMI) commands in the SYSGEN
script.
• Configuration information for a specific BSS area. These areas are identified by
Country/Network, Name, Software Release, and Configuration Number. The Configuration
Number allows multiple versions to exist within the database.
DataGen functionality
DataGen consists of a suite of tools that operate on BSS databases (refer to Figure 1-1).
Figure 1-1 DataGen GUI
1-2 68P02900W22-S
Jul 2008
System Information: DataGen Overview of the Offline MIB
The following functions can be performed using these tools:

• Upload BSS parameter data from an operational network (using the OMC-R).
• Define global defaults.
• Modify parameters across part or all of a network.
• Manage software loads.
• Generate SYSGEN databases.
• Generate commands for the Operations and Maintenance Centre (OMC) to apply changes.
• Describe a cellular network in both physical and logical structure.
Overview of the Offline MIB
The Offline MIB (OLM) can create new networks, visualize, and validate networks before
deployment into a live network. It has a common User Interface with the online OMC. The OLM
front panel is accessed from the DataGen main menu (refer to Figure 1-2).
BSS binary files are used to create the network which is displayed as a tree-like representation
called the Navigation Tree. It is possible to update multiple BSS binary files simultaneously, for
example, by propagating neighbor changes from one BSS binary file to another.
Figure 1-2 Offline MIB - Front Panel
68P02900W22-S 1-3
Jul 2008
Offline MIB functionality Chapter 1: Overview of DataGen
Offline MIB functionality
The Offline MIB enables users to perform the following tasks:
• Provide a graphical representation of a network.
• Edit configuration management parameters.
• Propagate cell and neighbor parameters.
• Interface to Radio Frequency (RF) planning tools.
DataGen/Offline MIB integration
DataGen and the Offline MIB work together. The following functions can be performed (refer
to Figure 1-3):
• Import binary database object files from the OMC.
• Carry out upgrade using DataGen.
• Import multiple binary object files into the OLM and thus carry out the radio frequency
planning.
1-4 68P02900W22-S
Jul 2008
System Information: DataGen The DataGen and OLM platform
Figure 1-3 DataGen/Offline MIB functions
Upgrader
Input
Ta ble control
MCDF
tables DataGen Data Store MMI generator
BSS Revgen
database object file (Informix)
from OMC
Output
Delete Sysgen Compiler

script
Copy
Admin Report
Difference Reporter
Netwo rk Topology Display
Cage layout Display
BSS
database object file
from OMC
Audit
OLM OMC-R GUI
Database Operations
Admin
Help Find
ti-GSM-DataGen_Of fline MIB functions-00003-ai-sw
The DataGen and OLM platform
DataGen and the OLM are implemented on either a Sun Netra 440 platform or the 'Flexible
Platform'. For more information about the supported platforms, refer to Supported platforms
on page 1-15. DataGen and the OLM use many of the same software tools as the OMC-R, thus
maximizing compatibility between the two systems. Deploy DataGen on a shared Ethernet LAN
with the OMC-R to facilitate data interchange.
68P02900W22-S 1-5
Jul 2008
The DataGen and OLM platform Chapter 1: Overview of DataGen
Hardware
DataGen and the OLM is configured to run on a standalone processor with its own disk storage,
tape drive, and DVD drive. The system uses Sun UltraSPARC processor; CPU speed and RAM
are subject to change.
Standard peripherals include a DAT tape drive, a DVD-ROM drive, and monitor. The standard
system is configured for LAN Ethernet support.
Software
DataGen and OLM are built around the industry-standard Informix online database engine. This
runs on top of the Solaris UNIX Operating System. The user interface uses the OSF/Motif
windowing system. DataGen software is distributed on DVD-ROM together with all third-party
products.
Figure 1-4 DataGen in a GSM environment
Da ta Ge n NMC
OMC-R
OS I
Loca l Are a Ne twork
S ys te m
S e rve r
BSC GUI S e rve r OS I Proce s s or Ope ra tor

Works ta tions
X.25
BSC
BSC
BSC
ti-GS M-Da ta Ge n_in_GS M_e nvironme nt-0004-a i-s w
1-6 68P02900W22-S
Jul 2008
System Information: DataGen DataGen database structure
DataGen database structure

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
DataGen is a collection of software tools used to produce, edit, and update BSS databases.
BSS database
A BSS database contains many parameters which describe the configuration of the BSS
hardware and software. A BSS database can have two forms, a database script file and a
Configuration Management (CM) database object.
Database script file
A database script file is an ASCII file. The operator can read from or write into the database
script file. It can be produced manually by entering the text into an ASCII file. This process is
slow and is likely to introduce errors. Format the file precisely to contain the correct number
of line feeds and spaces. DataGen provides a faster and more accurate way to produce a
Database Script File.
Configuration Management (CM) database object
A CM Database Object (Binary Object) is the compiled database script file and cannot be read or
edited. The CM Database Object is produced by downloading a database script file into a BSC.
This object can then be uploaded and stored on a disk or at the OMC.
DataGen and the OMC
The code used by the BSS to convert the SYSGEN script into a binary object is ported to the
DataGen platform. It generates a binary object which can be then downloaded to the OMC
(refer to Figure 1-5).
For DataGen applications which are on the same Ethernet network as an OMC, the transfer of
the new binary object is initiated from the OMC using the load_db script. It is also possible for
DataGen to access the binary objects which are stored on the OMC. This allows binary objects
which are uploaded, to be imported into DataGen using Revgen.
68P02900W22-S 1-7
Jul 2008
DataGen and the OMC Chapter 1: Overview of DataGen
Figure 1-5 DataGen-OMC integration
Datagen Platform OMC Platform
GUI GUI
DATAGEN LOAD
CM
MANAGEMENT
RDB MIB
Topology
BSS MMI SCRIPT
DATABASE
BSS CM
DB Root
BSS Databases
OLM Binary
object cobh
bss_cork bss_cobh
BINARY
Binary
objects GENERATION
CellXchange
DATAGEN SYSTEM PROCESSOR OMC SYSTEM PROCESSOR

PLATFORM PLATFORM
ti-GS M-Da ta Ge n-OMC inte gra tion-00005-a i-s w
1-8 68P02900W22-S
Jul 2008
System Information: DataGen Loading network information into DataGen
Loading network information into DataGen

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to loading network information
The process for loading network information into DataGen is illustrated in Figure 1-6. To load
network information and import existing input files into DataGen, perform the following steps:
• Gather or create input files.
• Start up DataGen.
• Create a BSS area.
• Import input files into the new BSS area.
• Import binary object files into the Offline MIB.
68P02900W22-S 1-9
Jul 2008
Gathering network information Chapter 1: Overview of DataGen
Figure 1-6 Loading network information into DataGen
Hardware
Software
Configuration
Configuration
NETWORK
Input
Files
DATAGEN
Start-up Create Import

DataGen new BSS Input Files
Area
ti-GS M-Loa ding_ne twork_informa tion_into_Da ta Ge n-00006-a i-s w
Gathering network information
First gather the network configuration information for the network. This information is then
used to produce the input files which can be read by DataGen. The input files can be entered
directly into either of the two computer-based tools:
• The DataGen Table Controller
• Files conforming to the Motorola Customer Data File (MCDF) format
Both methods involve entering the information into a computer using a custom designed
software package.
1-10 68P02900W22-S
Jul 2008
System Information: DataGen The DataGen Directory Structure (DDS)
Figure 1-7 shows a graphical representation of the two methods for creating MCDF files.
Figure 1-7 Creating MCDF files
DataGen
Network
Information
MCDF Files
MCDF
format
ti-GS M-Cre a ting_MCDF_file s -00007-a i-s w
The DataGen Directory Structure (DDS)
All DataGen input and output files are stored in an area called the DataGen Directory Structure
(DDS). The starting point of the DDS is the directory dg. The directories after dg, are then
named according to the country and BSS area being stored.
A further (lower) directory level identifies the configuration number for the BSS area. This
allows the storage of more than one set of database information for each BSS area. The next
level down contains the DataGen input and output file directories. An example of the DataGen
directory structure is shown in Figure 1-8.
CAUTION
Do not create directories within the DataGen Directory Structure manually. DataGen
creates the directories automatically, thus ensuring that there are no syntax errors
in the directory names.
68P02900W22-S 1-11
Jul 2008
Main structure of the DDS Chapter 1: Overview of DataGen
Figure 1-8 DataGen directory structure
dg
Belgium UK Norway Qatar
London Manchester Birmingham
conf0 conf1
Input File Output File

Directories Directories
command
MCDF UPG 002

ti-GS M-Da ta Ge n_dire ctory_s tructure s -00008-a i-s w
Main structure of the DDS
The DDS is structured as follows:
/usr/gsm/DataGen/dg/<country>/<bss>/conf<N>
Where Is
country replaced by the name of the country
bss replaced by the name of the base
site
N replaced by the configuration
For example:
$HOME/dg/UK/testbss/conf0
All directories must be created by DataGen for each BSS area. Leave the directory creation to
DataGen to avoid problems with capitalization.
1-12 68P02900W22-S
Jul 2008
System Information: DataGen Sub-structure
Sub-structure
Inside the conf<N> directory, there are some other directories as follows:
• /command contains SYSGEN scripts created by DataGen.
• /002 contains files for use with Revgen.
• /upg contains files created by Upgrader.
• /MCDF contains files converted by MCDF, which can be edited.
• /diff contains files created by Diff reporter.
The Offline MIB directory structure
The directories below the OLM are created when an operator creates a network configuration in
the Offline MIB, as in Figure 1-9. When a BSS or RXCDR is created, a copy of the binary object
file in the Conf<N> directory is placed in the network directory (refer to Figure 1-8).
Figure 1-9 Example of Offline MIB directory structure
olm
Network 1 Network 2 Network 3 Network 4
ti-GS M-Exa mple _Offline _MIB_dire ctory_s tructure -00009-a i-s w
The Offline MIB file structure
Each network configuration can contain up to 256 binary object (.002) files. An example of
Offline MIB network structure is displayed in Figure 1-10.
Figure 1-10 Example of Offline MIB file structure
Network 2
London .002 Manchester .002 Birmingham .002 Liverpool .002
ti-GS M-Exa mple _Offline _MIB_file _s tructure -00010-a i-s w
68P02900W22-S 1-13
Jul 2008
Main structure of the Offline MIB directory Chapter 1: Overview of DataGen
Main structure of the Offline MIB directory
The Offline MIB directory structure is organized as follows:
/usr/gsm/DataGen/olm/<network_configuration>
Where Is
network_configuration replaced by the network configuration name,
which contains .002 files.
1-14 68P02900W22-S
Jul 2008
System Information: DataGen Supported platforms
Supported platforms
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of supported platforms
DataGen is configured to run as a standalone processor with its own disk storage, tape drive,
and DVD-ROM drive. Table 1-1 lists the hardware configurations supported.
Table 1-1 Supported platforms in GSR9
Processor Internal mirrored disks

Netra 440 (2 X 73 GB) X 2
NOTE
• The same configuration is used for Clean Install and Upgrade platforms.
• DataGen is supported on a Flexible Platform. Any Sun UltraSPARC machine that
meets the minimum specification set by Motorola can be used. For more details,
refer to the Bulletin number GSM_G_OMCR_056.
68P02900W22-S 1-15
Jul 2008
Overview of supported platforms Chapter 1: Overview of DataGen
1-16 68P02900W22-S
Jul 2008
Chapter
User and Group management using the

usertool
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02900W22-S 2-1
Jul 2008
User and Group management using the usertool Chapter 2: User and Group management using the usertool
User and Group management using the usertool

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to usertool
This chapter describes the procedures to manage users and groups on the DataGen processor
using the usertool utility.
Common Desktop Environment Manager
The Common Desktop Environment (CDE) Manager provides a desktop environment which can
be customized on a per user basis. It reduces window clutter and provides a graphical front
end to the UNIX file system. It provides an industry standard desktop manager and is available
for different SUN workstations. A batch scheduler is also provided which allows the user to
schedule cron jobs from the CDE.
The OMC Admin menu available from the CDE provides a Graphical User Interface (GUI) for
performing routine system administration tasks. It provides access from the front panel of the
desktop to the different SUN administration tools that support Solaris 8.
Usertool - Overview
Usertool is a utility that is used for managing users and groups on the DataGen processor.
Usertool can be accessed either from the command line (/var/install/bin/usertool) or from
the OMC Admin menu available in the Common Desktop Environment (CDE).
Usertool can be used to perform the following management tasks:

• Manage user accounts
• Manage groups
Procedure list
This chapter details the following procedures:

• DataGen User management using the usertool on page 2-3
• DataGen Group management using the usertool on page 2-13
2-2 68P02900W22-S
Jul 2008
System Information: DataGen DataGen User management using the usertool
DataGen User management using the usertool

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to user management
Usertool is a utility that enables the management of user accounts on a local system. A user
account enables a user to log on to a system and provides access to a home directory.
Usertool can be used to perform the following user management tasks:

• Add a new user account
• Modify a user account
• Delete a user account
• Copy a user account to a new user name
Before assigning the users to specific groups, ensure that the groups first exist. Before adding
user accounts, use usertool to add any groups to which the users are assigned. Refer to DataGen
Group management using the usertool on page 2-13 for more information.
User management parameters
The following parameters are available under User Administration in Usertool:

• User Name
The User Name specifies the login name the operating system uses to identify an
individual user. A user name must be a unique name, composed of lowercase alphabetical
characters (a-z) or digits (0-9). The first character of a user name must be a letter.
• Full Name
The Full Name can be any text string. It is generally a short description of the login, and
is used as the field for the user's full name.
NOTE
The user’s full name is displayed on the OLM GUI.
• Home Directory
The home directory of the user. It defaults to /home/<username>, where <username>

is the login name, for example: /home/bloggs1.
68P02900W22-S 2-3
Jul 2008
User administration utility Chapter 2: User and Group management using the usertool
• User ID (UID)
The User ID (UID) specifies the unique number by which the operating system can
identify a user. The maximum value is 2147483647. Keep the UIDs below 60000
to minimize the amount of software incompatibilities. Reserved UIDs include 60001
(nobody) and 65534 (nobody4).
• Group
This parameter specifies the primary group to which the user belongs. A group ID
number or group name can be specified. Group 110 (omc) is the default primary group
for DataGen users.
• Secondary Groups
This optional parameter specifies one or more groups to which the user also belongs. A
group ID number or group name can be specified. If more than one group is specified,
separate them from the other groups with commas.
• Account Locked
If the account is locked, the user cannot log in until the account is unlocked by the System
Administrator.
• Change Password
The parameter forces the user to change the password on the next login. This occurs only
once. Having chosen a new password, the user is not prompted for password change on
subsequent logins.
• Shell
This is the full path name of the program used as the user's shell on login. It is
recommended that the C-shell (/bin/csh) is used for DataGen users.
User administration utility
Procedure 2-1 Starting the Usertool
1 Usertool is the user administration utility. Usertool can be started from the
OMC Admin menu in the Common Desktop Environment (CDE) or from
the command line.
2 To start the usertool from the Common Desktop Environment (CDE), log
on to the CDE environment with user name root.
Continued
2-4 68P02900W22-S
Jul 2008
System Information: DataGen User administration utility
Procedure 2-1 Starting the Usertool (Continued)

3 From the front panel of the CDE Desktop (Figure 2-1), click the arrow on the
usertool icon (Figure 2-2) to open the OMC Admin drawer (Figure 2-3).
Figure 2-1 CDE desktop - front panel
Figure 2-2 The usertool icon
Figure 2-3 CDE desktop front panel with open OMC Admin drawer
4 The OMC Admin drawer provides access to administration applications as

in Figure 2-3. To start usertool, click the usertool icon. The usertool menu
is launched in a separate window as in Figure 2-4. Click the arrow again
to close the OMC Admin drawer.
Continued
68P02900W22-S 2-5
Jul 2008
User administration utility Chapter 2: User and Group management using the usertool
Procedure 2-1 Starting the Usertool (Continued)

5 To start usertool from the command line, run the
following command: /var/install/bin/usertool.
The usertool menu is displayed as in Figure 2-4.
Figure 2-4 Usertool menu window
6 The following user operations and group operations are available:
• Add user
• Modify user
• Rename user
• Delete user
• Add group
• Modify group
• Rename group
• Delete group
2-6 68P02900W22-S
Jul 2008
System Information: DataGen Add a new user account
Add a new user account
To add a new user to a group, perform the following procedure.
Procedure 2-2 Add a new user account
1 Start the usertool utility using the steps in User administration

utility on page 2-4. The usertool menu is displayed as in Figure 2-4.
Administration utility
----------------------
1. Add user
2. Modify user
3. Rename user
4. Delete user
5. Add group
6. Modify group
7. Rename group
8. Delete group
0. Exit
Action:
2 Enter 1 to select the Add User option.
The User Administration window is displayed as follows:

---------------------------
Username :
Full Name :
Home directory :
UID : 0
Group :
Secondary groups :
Account locked : n
Change password : n
Shell :
Done
Cancel
In this window, one field is highlighted with a bar which can be moved with
the cursor keys. The highlighted field can be modified by typing or deleting
as required. A help message is provided for each field. If any of the fields is
in conflict, a message to that effect is displayed.
NOTE
Refer to the section User management parameters on page 2-3
for more information about data fields.
Continued
68P02900W22-S 2-7
Jul 2008
Add a new user account Chapter 2: User and Group management using the usertool
Procedure 2-2 Add a new user account (Continued)

3 Enter the required data into the Username field. Many of the other fields are
automatically filled out with the default values for DataGen users as in the
following example:

---------------------------
Username : bloggs1
Full Name :
Home directory : /home/bloggs1
UID : 500
Group : omc
Secondary groups :
Account locked : n
Change password : n
Shell : /bin/csh
Done
Cancel
4 Modify the Full Name, Home Directory, UID, Group, and Shell as
appropriate. Accept the default values when using usertool to create
DataGen user accounts.
5 For DataGen users, ensure that the Group is set to OMC.
6 For DataGen users, ensure that the Shell is set to /bin/csh.
7 Select Done to save changes and create the user.
8 Enter required data into Path and click OK.
The List of user accounts displayed in the main window is updated to
include the new user account. A prompt is displayed requiring a password
to be selected for the new user.
9 Choose and confirm the password for the new user account. This password
must be communicated to the user to allow the new user to log in. The new
user has the appropriate environment settings automatically configured for
DataGen. The usertool utility exits automatically upon completion of the
requested operation.
2-8 68P02900W22-S
Jul 2008
System Information: DataGen Modify a user account
Modify a user account
To modify a user account, perform the following procedure.
Procedure 2-3 Modify a user account
1 Start the Usertool utility using the steps in User administration

----------------------
1. Add user
2. Modify user
3. Rename user
4. Delete user
5. Add group
6. Modify group
7. Rename group
8. Delete group
0. Exit
Action:
2 Enter 2 to select the Modify User option.

---------------------------
Username :
Full Name :
Home directory :
UID : 0
Group :
Secondary groups :
Account locked : n
Change password : n
Shell :
Done
Cancel
as required. A help message is provided for each field. If any of the fields
are in conflict, a message to that effect will be displayed.
NOTE
Continued
68P02900W22-S 2-9
Jul 2008
Rename a user account Chapter 2: User and Group management using the usertool
Procedure 2-3 Modify a user account (Continued)

3 Enter the user name to be modified into the Username field, the other
fields are automatically filled with the current settings of the user.

---------------------------
Username : bloggs1
Full Name : Joe Bloggs
UID : 500
Group : omc
Secondary groups :
Account locked : n
Change password : n
Shell : /bin/csh
Done
Cancel
4 Highlight each data field to be modified and enter the new data.
5 Select Done to save changes and modify the user account. The usertool utility
exits automatically upon completion of the requested operation.
Rename a user account
To rename a user account, that is, to change the username or login associated with the user ID,
perform the following procedure.
Procedure 2-4 Rename a user account
1 Start the usertool utility using the steps in User administration utility on
page 2-4. The usertool menu is displayed as in Figure 2-4.
----------------------
1. Add user
2. Modify user
3. Rename user
4. Delete user
5. Add group
6. Modify group
7. Rename group
8. Delete group
0. Exit
Action:
2 Enter 3 to select the Rename user option.
3 When prompted, enter the existing username of the account.
4 When prompted, enter the new username of the account. The usertool utility
2-10 68P02900W22-S
Jul 2008
System Information: DataGen Delete a user account
Delete a user account
To delete a user account, perform the following steps.
CAUTION
Deleting a user account permanently removes the home directory of the user and all
files contained within it.
Procedure 2-5 Delete a user account

----------------------
1. Add user
2. Modify user
3. Rename user
4. Delete user
5. Add group
6. Modify group
7. Rename group
8. Delete group
0. Exit
Action:
Continued
68P02900W22-S 2-11
Jul 2008
Delete a user account Chapter 2: User and Group management using the usertool
Procedure 2-5 Delete a user account (Continued)

2 Enter 4 to select the Delete User option.

---------------------------
Username :
Full Name :
Home directory :
UID : 0
Group :
Secondary groups :
Account locked : n
Change password : n
Shell :
Done
Cancel
are in conflict, a message to that effect will be displayed.
NOTE
3 Enter the user name to be deleted into the Username field, the other
fields are automatically filled with the current settings of the user.

---------------------------
Username : bloggs1
Full Name : Joe Bloggs
UID : 500
Group : omc
Secondary groups :
Account locked : n
Change password : n
Shell : /bin/csh
Done
Cancel
4 Select Done to delete the user account.
5 Select Done to save changes and modify the user account.
The usertool utility exits automatically upon completion of the requested
operation.
2-12 68P02900W22-S
Jul 2008
System Information: DataGen DataGen Group management using the usertool
DataGen Group management using the usertool

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to group management
Usertool is a utility that enables the management of groups on the local system. Usertool is
used to perform the following group management tasks:
• Add a new group
• Modify a group
• Rename a group
• Delete a group
Group management parameters
The following parameters are available under Group Administration in usertool:

• Group Name
Group Name specifies a name used to identify a user group. A group name contains
lowercase alphabetical characters (a-z) and digits (0-9). A group name can be 1 - 8
characters long.
• Group ID (GID)
Group ID specifies a group identification number used to identify a user's primary group.
The maximum value is 2147483647. To minimize the amount of software incompatibilities,
keep the GIDs below 60000. Reserved GIDs include 60002 (no access) and 65534 (no
group).
Group Administration Utility
The Group Administration Utility is usertool, which is the same utility used for user
administration. Usertool can be started from the OMC Admin menu in the Common Desktop
Environment (CDE) or from the command line. Refer to the section User administration utility
on page 2-4, which contains detailed instructions for starting the usertool utility.
68P02900W22-S 2-13
Jul 2008
Add a group Chapter 2: User and Group management using the usertool
Add a group
To add a new group, perform the following procedure.
Procedure 2-6 Add a group
1 Start the Usertool utility using the steps in User administration

----------------------
1. Add user
2. Modify user
3. Rename user
4. Delete user
5. Add group
6. Modify group
7. Rename group
8. Delete group
0. Exit
Action:
2 Enter 5 to select the Add Group option.
The Group Administration window is displayed as follows:
Group administration utility

----------------------------
Group :
GID : 0
Done
Cancel
are in conflict, a message to that effect is displayed.
NOTE
Refer to the section Group management parameters on page 2-13
3 Enter the required group name into the Group field:

----------------------------
Group : group1
GID : 500
Done
Cancel
4 An unused Group ID is automatically inserted into the GID field. Modify
the GID as appropriate, if desired.
5 Select Done to save changes and create the group. The usertool utility exits
automatically upon completion of the requested operation.
2-14 68P02900W22-S
Jul 2008
System Information: DataGen Modify group information
Modify group information
To modify group information, perform the following procedure.
Procedure 2-7 Modify group information

----------------------
1. Add user
2. Modify user
3. Rename user
4. Delete user
5. Add group
6. Modify group
7. Rename group
8. Delete group
0. Exit
Action:
2 Enter 6 to select the Modify Group option.

----------------------------
Group :
GID : 0
Done
Cancel
NOTE
Continued
68P02900W22-S 2-15
Jul 2008
Rename a group Chapter 2: User and Group management using the usertool
Procedure 2-7 Modify group information (Continued)

3 Enter the name of the group to be modified in the Group field. The GID data
field displays the current settings for the group, by default as given in the
following example:

----------------------------
Group : group1
GID : 500
Done
Cancel
4 Highlight the GID data field and enter the new data.
5 Select Done to save the changes and modify the group. The usertool utility
Rename a group
To rename a group, perform the following procedure.
Procedure 2-8 Rename a group

----------------------
1. Add user
2. Modify user
3. Rename user
4. Delete user
5. Add group
6. Modify group
7. Rename group
8. Delete group
0. Exit
Action:
2 Enter 7 to select the Rename Group option.
3 When prompted, enter the existing Group name.
4 When prompted, enter the new Group name.
5 Select Done to save the changes and rename the group. The usertool utility
2-16 68P02900W22-S
Jul 2008
System Information: DataGen Delete a group
Delete a group
To delete a group, perform the following procedure.
Procedure 2-9 Delete a group

----------------------
1. Add user
2. Modify user
3. Rename user
4. Delete user
5. Add group
6. Modify group
7. Rename group
8. Delete group
0. Exit
Action:
2 Enter 8 to select the Delete group option.

----------------------------
Group :
GID : 0
Done
Cancel
NOTE
Continued
68P02900W22-S 2-17
Jul 2008
Delete a group Chapter 2: User and Group management using the usertool
Procedure 2-9 Delete a group (Continued)

3 Enter the name of the group to be deleted in the Group field.
By default, the GID data field displays the current
settings for the group, as given in the following example:

----------------------------
Group : group1
GID : 500
Done
Cancel
4 Select Done to delete the group. The usertool utility exits automatically
upon completion of the requested operation.
2-18 68P02900W22-S
Jul 2008
Chapter
Operating DataGen
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02900W22-S 3-1
Jul 2008
Overview of operating DataGen Chapter 3: Operating DataGen
Overview of operating DataGen

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
About this chapter
This chapter provides an introduction to the DataGen menu structure and a detailed view of the
operational sequences involved in running DataGen. Use this in conjunction with Chapter 6
MCDF tables.
The information in this chapter is aimed primarily at new users of DataGen. The routines are set
in the order in which they would be performed.
The functionality of DataGen revolves around an Informix database. To create this database
from scratch would be an unnecessary waste of existing resources. Therefore, it is assumed
that the user works with an existing database and perform a variety of DataGen functions to
generate a working database.
If the user is successful in editing or creating new information in the database, then the
database compiles successfully and create a viable BSS script.
Procedures for operating DataGen
To operate the DataGen, perform the listed procedures in the following order:
• Importing existing CM database objects on page 3-26.
• Converting a CM database object file to a script file on page 3-66 - Using Revgen.
• Generating a database script file on page 3-71 - Using the MMI tool.
• Viewing and editing DataGen files on page 3-77 - Using the Service Window, Table
Controller, Generic Table Editor, and Topology viewer.
• Converting a database script file to a CM database object file on page 3-112 - Using the
Binary Object Compiler.
Other procedures for operating DataGen can be performed as required, including:
• Administration tasks on page 3-12
• Creating a BSS area on page 3-35
• Opening a BSS area on page 3-39
• Copying a BSS area on page 3-41
3-2 68P02900W22-S
Jul 2008
System Information: DataGen Procedures for operating DataGen
• Deleting a BSS area on page 3-43
• Configuring BSS areas on page 3-45
• Difference Reporter on page 3-118
• Upgrader on page 3-123
• Batch processing of binary object files on page 3-130
For information on operating the offline MIB, refer to Chapter 4 Operating the Offline MIB.
68P02900W22-S 3-3
Jul 2008
Defining environment variables Chapter 3: Operating DataGen
Defining environment variables

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of environment variables
Environment variables are variables that the shell or any other program can access to get
information unique to a specific user. DataGen can create and use several environment variables.
Certain variables can be set from the DataGen main menu by using the ADMIN - Preferences
option. Refer to Administration tasks on page 3-12 for more details.
NOTE
Set up these standard C shell environment variables before running DataGen.
HEX or decimal representation
The following two environment variables can be set up to allow the users to decide at the run
time whether they want HEX or DECIMAL representation:
• DG_HEX_CELL_IDS determines the format in which GSM cell ids are displayed.
• DG_HEX_POINT_CODES determines the format in which the elements opc and dpc are
displayed. The format applies to the MMI script and to MCDF.
Set the variables to yes to display the values in HEX using the
following commands in the C shell:
• setenv DG_HEX_CELL_IDS yes
• setenv DG_HEX_POINT_CODES yes
NOTE
These variables can also be set from the DataGen main menu using the ADMIN -
Preferences option. Refer to Administration tasks on page 3-12 for more details.
3-4 68P02900W22-S
Jul 2008
System Information: DataGen Version list order
Version list order
DG_VERSION_ORDER determines the ordering of the version list in both the Open and New
BSS dialog boxes. If this variable is not set, then DataGen displays the list in ascending order by
default. To display the list in descending order, set DG_VERSION_ORDER to yes by executing
the following command in the C shell:
setenv DG_VERSION_ORDER yes
Time slot order equipage
This feature is optional and allows the user a greater flexibility in the allocation of time slots. If
enabled, RSL and RTF time slots are retained when modifying a binary object file, otherwise,
the default values are applied.
Retain time slot order equipage is enabled, by default. If retaining the order is not required,
then disabling this function gives a significant performance improvement.
• To enable the time slot order equipage, enter the following command in the C shell:
setenv DG_AGGREGATE_ABIS yes
• To disable the time slot order equipage, enter the following command in the C shell:
setenv DG_AGGREGATE_ABIS no
NOTE
This variable can also be set from the DataGen main menu using the ADMIN -
Automated running of Revgen
Revgen converts a Binary Object File into an Informix format. Revgen can be invoked by
selecting the Services option from the Services menu, or by selecting the Revgen button.
• To automate the functioning of Revgen from the Service menu or Revgen button, enter
the following command in the C shell:
setenv DG_AUTO_REVGEN yes
• To disable the automated functioning of Revgen from the Service menu or Revgen button,
enter the following command in the C shell:
setenv DG_AUTO_REVGEN no
NOTE
Preferences option. Refer to Administration tasks on page 3-12 for details.
68P02900W22-S 3-5
Jul 2008
Default file import path Chapter 3: Operating DataGen
Default file import path
From the Service window, it is possible to import binary object files. The default directory path
is /usr/omc. The variable DG_IMPORT_PATH allows a user-defined import path. If the variable
is set and import object is selected, then the DG_IMPORT_PATH is displayed, regardless of
the previous paths selected.
To define an import path, enter the following command in the C shell:
setenv DG_IMPORT_PATH <directory_path>
For example:
setenv DG_IMPORT_PATH /usr/omc/import
NOTE
Default export path
The variable DG_EXPORT_PATH allows binary object files to be exported from the Service
window to an export directory.
To define an export directory, enter the following command in the C shell:
setenv DG_EXPORT_PATH <directory_path>
For example:
setenv DG_EXPORT_PATH /usr/omc/export
NOTE
3-6 68P02900W22-S
Jul 2008
System Information: DataGen Define default text editor
Define default text editor
From the Service window, it is possible to view the MMI scripts and compilation logs. The
variable DG_EDITOR allows the user to define which editor to launch when viewing MMI
scripts or compilation logs.
To define a text editor, enter the following command in the C shell:

setenv DG_EDITOR <text_editor>
Where Is
text editor textedit, vi, or xedit
NOTE
• This variable can also be set from the DataGen main menu using the ADMIN -
• To define another editor other than the three standard editors, refer to
Generating a database script file on page 3-71.
Override area lock
When a BSS area that is already in use is accessed, a warning message is displayed. The user
can unlock the area or cancel it.
• To automatically unlock the locked area without displaying the warning message, enter
the following command:
setenv DG_OVERRIDE_LOCK yes
• To return to the default state and present the warning message when accessing a locked
area, enter the following command:
setenv DG_OVERRIDE_LOCK no
NOTE
68P02900W22-S 3-7
Jul 2008
Output all elements in a script Chapter 3: Operating DataGen
Output all elements in a script
From the Service window, it is possible to generate a database script file by clicking the MMI
button or by selecting the Generate Script option.
By default, certain elements which are set to their default value are not output to the script.
• To output all elements, whether default or not, execute the following command:
setenv DG_ALL_CHG_ELEMENT yes
• To return to the default state, enter the following command:
setenv DG_ALL_CHG_ELEMENT no
NOTE
• Setting the value to Yes can result in compilation failures. Set the value to
Yes only to view the default values.
• This variable can also be set from the DataGen main menu using the ADMIN -
Display only generic algorithm details in alg.mcd table
The MCDF Algorithm data table (alg.mcd) has hundreds of rows of data for all cells. Each cell
is specified by the Location Area Code (LAC) and Cell Identifier (CI) in the table.
The ALG_TABLE_NEW environment variable is used to display only generic algorithm details
(the most repeating value for a particular algorithm) for cells with no Mobile Country Code
(MCC), Mobile Network Code (MNC), LAC and CI details specified. That is, any cells with
algorithm details which differ from the generic, are listed in the alg.mcd table, with complete
MCC, MNC, LAC, and CI information.
• Execute the following command to set this variable:
setenv ALG_TABLE_NEW TRUE
• To return to the default state, execute the following command:
unsetenv ALG_TABLE_NEW
If the environment variable ALG_TABLE_NEW is set, the MCDF exports the generic values of
the alg.mcd table as a single record.
During insert, if there are no generic values in the alg.mcd table, the values present in the
genercialg.dat file are inserted.
The format of the genericalg.dat file is same as alg.mcd, except that there should be no value
for cell id.
3-8 68P02900W22-S
Jul 2008
System Information: DataGen Display only generic algorithm details in alg.mcd table
The location of the genericalg.dat file is /usr/gsm/DataGen/current/bin. If the file is not

present in the specified location, the following values are inserted as generic values:
surround_cell 00 610
rel_tim_adv 00 810
rxlev_dl_ho 00 610
rxlev_dl_pc 00 210
rxlev_ul_ho 00 610
rxlev_ul_pc 00 210
rxqual_dl_ho 00 411
rxqual_dl_pc 00 211
rxqual_ul_ho 00 411
rxqual_ul_pc 00 211
68P02900W22-S 3-9
Jul 2008
DataGen - startup and shutdown Chapter 3: Operating DataGen
DataGen - startup and shutdown

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to startup and shutdown
DataGen has a comprehensive Graphical User Interface (GUI). It is accessed through a main
window which has seven menu options, providing complete DataGen functionality.
This section describes how to start DataGen, access the main window and shut down DataGen.
Startup
To start the DataGen GUI, open an Xterm window and enter the following command:
DataGen
The DataGen main menu is displayed as in Figure 1-1.
The following options can be selected from this menu: NEW, OPEN, UPG, COPY, DEL, DIFF,
BATCH, ADMIN, OLM, HELP, and EXIT (refer to Table 3-1).
Table 3-1 Main menu options
Select To
NEW Display a window where a new BSS area can be created.
OPEN Display a window where an existing BSS area can be viewed or
edited.
UPG Display a window where an existing BSS area can be upgraded
to a later version.
COPY Display a window where BSS areas can be copied.
DEL Display a window where an existing BSS area can be deleted.
DIFF Display a window where difference reports between sites and site
elements for BSS areas can be generated.
BATCH Display a window where multiple binary object files can be
revgened, upgraded, or compiled.
ADMIN Display a window where a range of Administration tasks can be
carried out. For example, Country administration.
OLM Display a window where an Offline MIB (OLM) can be launched.
RF planning and modifications to multiple BSS binary files can
be carried out.
HELP View the following Help message:
For DataGen Help please refer to the DataGen manual

supplied,
Continued
3-10 68P02900W22-S
Jul 2008
System Information: DataGen Shutdown
Table 3-1 Main menu options (Continued)

Select To
OLM On-Line help is available through the OLM GUI.

EXIT Shut down DataGen.
Shutdown
DataGen can be shut down either from an Xterm window or from the main menu as follows:
Xterm
To shut down DataGen from an Xterm window, first close all DataGen windows. In the Xterm
window from which DataGen was started, execute the following command:
exit
DataGen is then shut down and the main menu window is removed.
Main menu
To shut down DataGen from the main menu, select the EXIT option.
All open DataGen windows, including the main menu, are then removed and DataGen is shut
down.
68P02900W22-S 3-11
Jul 2008
Administration tasks Chapter 3: Operating DataGen
Administration tasks
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of tasks
Following is a list of tasks that can be carried out by selecting the ADMIN option from the
DataGen main menu:
• Country Admin
This option can be used to create a country or network configuration.
Refer to Creating a BSS area on page 3-35 for more details.
• Permissions
The DataGen user has a standard set of access permissions. This option allows the user to
set the status to access permitted or access denied.
• Defragment
To maximize free disk space, defragment or optimize the DataGen database.
• Logfile
Each task carried out within DataGen is monitored and the results are stored in a logfile.
This utility displays the logfile.
• Preferences
Several environment variables can be activated from within the Preferences menu. For
example, the default editor and import path for importing binary object files can be defined.
• Options
Once the binary option object files are copied from tape (or downloaded electronically from
the GSM Software Distribution and Licensing Centre) and uncompressed, they can be
installed using this feature.
NOTE
The following privileges are available for a user logged into the DataGen
processor as omcadmin:
• Permissions
• Defragment
• Options
3-12 68P02900W22-S
Jul 2008
System Information: DataGen Changing permissions
Changing permissions
To change or toggle access permissions for a user, perform the following procedure.
Procedure 3-1 Change permissions
1 Log on to the DataGen processor as omcadmin.

2 Start DataGen from an Xterm window and select ADMIN from the DataGen
main menu. Refer to DataGen - startup and shutdown on page 3-10 for details.
The Administration menu is displayed as shown in Figure 3-1.
Figure 3-1 Administration menu - omcadmin user
3 Select the Permissions option. The Permissions window is then displayed

as in Figure 3-2.
Figure 3-2 Permissions window
4 Enter the Username and click Toggle to grant or withhold the permissions.
NOTE
Enter valid users only, such as omcadmin, informix, and so on.
Continued
68P02900W22-S 3-13
Jul 2008
Optimizing the database Chapter 3: Operating DataGen
Procedure 3-1 Change permissions (Continued)

5 A Confirmation window is displayed, as shown in Figure 3-3.
Figure 3-3 Confirm permissions
6 Click OK to return to the Administration menu.
NOTE
Refer to the section Viewing the log file on page 3-15 for more
details.
Optimizing the database
To defragment or optimize the DataGen database, perform the following procedure.
Procedure 3-2 Optimize the database

main menu. Refer to DataGen - startup and shutdown on page 3-10 for
details. The Administration menu is displayed (refer to Figure 3-1).
3 Select the Defragment button. A status
window displays the following message:
Defragmenting the database, Please Wait ...
When the defragmentation is complete, a confirmation window is displayed.
4 Click OK to return to the Administration menu.
NOTE
After performing a defragmentation, exit the GUI and then reopen
it to access the previously created areas.
3-14 68P02900W22-S
Jul 2008
System Information: DataGen Viewing the log file
Viewing the log file
To view the log file, perform the following procedure.
Procedure 3-3 View the log file
1 Log on to the DataGen processor.

2 Start DataGen from an Xterm window and select the ADMIN option from
the DataGen main menu.
3 Select Logfile from the Administration menu (refer to Figure 3-4).
Figure 3-4 Administration menu - non-omcadmin user
NOTE
Figure 3-4 displays the default menu for non-omcadmin users.
4 The DataGen logfile displays the history of all the commands issued in
DataGen. If the logfile is open, the progress of a task can be viewed as it is
executed. An example of a logfile is displayed in Figure 3-5.
Figure 3-5 Example of a logfile
5 Press Ctrl+C to exit the logfile and return to the Administration menu.
68P02900W22-S 3-15
Jul 2008
Customizing parameters Chapter 3: Operating DataGen
Customizing parameters
From the Preferences menu, several different parameters can be customized. To view the
preferences available, perform the following procedure.
NOTE
It is not essential to select any of these criteria. If they are not required, skip these
steps and DataGen applies the default values.
Procedure 3-4 Customizing parameters

main menu. Refer to DataGen - startup and shutdown on page 3-10 for details.
The Administration menu is displayed as shown in Figure 3-1.
3 Select Preferences from the menu. The Preferences window is displayed
as in Figure 3-6. Several environment variables can be turned on from the
Preferences window for the current session.
Figure 3-6 Preferences window
Continued
3-16 68P02900W22-S
Jul 2008
System Information: DataGen Customizing parameters
Procedure 3-4 Customizing parameters (Continued)

4 Click the appropriate option to enable the required environment variables.
Refer to Defining environment variables on page 3-4 for a detailed
description.
NOTE
Retain Timeslot Order equipage is enabled, by default. This
retains RSL and RTF timeslots when modifying the binary file. If
retaining the order is not required, then disable this function to
give a significant performance improvement.
5 To select which editor to use when viewing MMI scripts or compilation logs,
enter one of the following in the Editor field:
• textedit
• vi
• xedit
NOTE
If an alternative editor is available, enter the name of the text
editor. Refer to Generating a database script file on page 3-71
for details.
6 To define the import path when importing binary object files, enter the path
in the Import Path field.
7 To define a directory where the binary object files are exported to, enter
the path in the Export Path field.
8 Click Save Defaults to save the settings. Click Close to return to the
Administration menu.
NOTE
Set the Preferences every time DataGen is closed and reopened.
9 To retain the standard DataGen default settings, shut down DataGen from
an Xterm window and restart DataGen. Refer to DataGen - startup and
shutdown on page 3-10 for details.
NOTE
An alternative to shutting down DataGen is to execute the following
command in the Xterm window from which DataGen was started:
source.cshrc
68P02900W22-S 3-17
Jul 2008
Installing the Options Object Chapter 3: Operating DataGen
Installing the Options Object
NOTE
Copy the Option Object files from tape (or downloaded electronically from the GSM
Software Distribution and Licensing Centre) uncompress and store in a directory
on the DataGen processor. Refer to the section Upgrade procedures in the
DataGen/OLM Upgrade/Migration Guide in the Software Release Notes: DataGen
(68P02900W76) for details.
To install Options Object files, perform the following procedure.
Procedure 3-5 Install the Options Object

main menu. The Administration menu is displayed as shown in Figure 3-1.
Continued
3-18 68P02900W22-S
Jul 2008
System Information: DataGen Installing the Options Object
Procedure 3-5 Install the Options Object (Continued)

3 Select Options from the menu. The Options Object Tool window is displayed
as in Figure 3-7.
Figure 3-7 Options Object Tool window
4 To locate the directory where the Options Object files are located, enter the
path in the Filter field and select the Filter button.
5 Select the Options Object file and click OK.
6 Select a country from the Country Name list.
7 Select a software version from the Software Version list.
8 Click Install. A Confirmation window is displayed. Click OK to continue.
When the installation is complete, a Confirmation window is displayed stating:
Object copied and linked. Refer to the Log File for

verification.
9 Click OK to continue. Refer to Viewing the log file on page 3-15 for details
on how to read the log file.
68P02900W22-S 3-19
Jul 2008
Database administration tasks Chapter 3: Operating DataGen
Database administration tasks

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Monitoring file and database capacities
The usage script is designed to monitor file system and Informix database capacities. The
omcadmin account has control of the script. The usage script can be executed manually or as
a cronjob.
NOTE
If the usage script is executed as a cronjob, it must be restarted after any upgrade
activity is carried out on DataGen.
Running usage script as a cronjob
• To run the usage script as a cronjob, log on to the DataGen processor as omcadmin.
Execute the following command:
cd /usr/omc/DataGen/current/cron
• To run the script, enter the following command:
crontab usage.cron
Verifying usage cronjob
To check if the usage script is activated as a cronjob, log on to the DataGen processor as
omcadmin.
Execute the following command:
crontab -l
3-20 68P02900W22-S
Jul 2008
System Information: DataGen Running usage script manually
Running usage script manually
• To run the usage script manually, log on to the DataGen processor as omcadmin. Execute
the following command:
cd /usr/omc/DataGen/current/cron
• To run the script, enter the following command:
usage
Warning messages issued
If either the file system or the Informix database reaches 85% capacity, the usage script sends a
report to all open DataGen sessions on the DataGen processor. If the error message Broken Pipe
is received, then system administration should be undertaken to protect DataGen integrity.
NOTE
If the usage script is running as a cronjob, a check is performed every two hours.
Reloading the database
It is possible to reload the Informix database and retain the current areas. This procedure
deletes and then recreates the tables within the DataGen Informix database (db_dg) that store
the area data. Upon completion of the procedure, it is necessary to run Revgen again for all
areas.
Example of when to reload the database
If all the MCDF tables are not displayed in the Table Controller (for example, the table only
displays up to the Specifics table), or if gcmd fails with an error relating to parameters not
found in the Informix database, then there could be a problem with the integrity of the database.
68P02900W22-S 3-21
Jul 2008
Dropping and recreating the db_dg Informix database Chapter 3: Operating DataGen
To resolve the problem, perform the following procedure.
Procedure 3-6 Reload the database
1 Log on to DataGen processor as omcadmin.

2 Enter the following command to verify that DataGen is not being accessed:
whodo
3 Close all open DataGen GUIs.
4 Enter the following command to start DGAdmin:
DGAdmin
5 Execute the following commands:
cd /usr/omc/DataGen/current/install
dbaccess db_dg upgrade.sql
6 Enter the following commands to validate the tables and MCDF files:
cd /usr/omc/DataGen/current/bin
valid_load -o c_tables.dat
valid_load -o mcdf.dat
7 Exit from the omcadmin account.
Dropping and recreating the db_dg Informix database
It is possible to destroy and recreate the DataGen Informix database (db_dg). Carry out this
procedure if the procedure for Reloading the database above was not successful or when the
data within the db_dg database is no longer required and a new database needs to be created.
CAUTION
This procedure permanently erases the dg_db Informix database and should be used
with caution.
To drop and recreate the db_dg Informix database, perform the following procedure.
Procedure 3-7 Drop and recreate the db_dg Informix database
1 Unload the OLM netwk_conf table.

2 Unload the DataGen configuration tables.
Continued
3-22 68P02900W22-S
Jul 2008
System Information: DataGen Dropping and recreating the db_dg Informix database
Procedure 3-7 Drop and recreate the db_dg Informix database (Continued)
3 Prepare to drop and recreate the Informix database.
4 Drop the database.
5 Create a database.
6 Load the OLM netwk_conf table.
7 Load the DataGen configuration tables.
Unloading the OLM netwk_conf table
The netwk_conf table exists in the DataGen Informix database (db_dg). It stores information
about OLM network configurations. This table must be unloaded to a file so that OLM network
configuration information can be recovered after dropping the db_dg database.
To unload the netwk_conf table, log on to DataGen processor as omcadmin. Enter the
following command (in the same line):
echo "unload to /usr/tmp/netwk_conf.unl select * from netwk_conf" | DGAdmin

dbaccess db_dg
Unloading the DataGen configuration tables
The country, network, bss_conf, bss_list, and conf_list tables exist in the DataGen Informix
database (db_dg). They contain configuration information for the DataGen BSS areas. These
tables must be unloaded to a file so that DataGen BSS area information can be recovered
after dropping the db_dg database.
To unload the tables, log on to DataGen processor as omcadmin. Enter the following commands
(all in one line):
echo "unload to /usr/tmp/country.unl select * from country" | DGAdmin dbaccess

db_dg
echo "unload to /usr/tmp/network.unl select * from network" | DGAdmin dbaccess

db_dg
echo "unload to /usr/tmp/bss_conf.unl select * from bss_conf" | DGAdmin dbaccess

db_dg
echo "unload to /usr/tmp/bss_list.unl select * from bss_list" | DGAdmin dbaccess

db_dg
echo "unload to /usr/tmp/conf_list.unl select * from conf_list" | DGAdmin

dbaccess db_dg
68P02900W22-S 3-23
Jul 2008
Dropping and recreating the db_dg Informix database Chapter 3: Operating DataGen
Preparing to drop and recreate the Informix database
Before dropping and recreating the Informix database, perform the following procedure.
Procedure 3-8 Prepare to drop and recreate the Informix database
1 Back up the Informix database. For details, refer to the section Backup
Procedures in the DataGen/OLM Clean Install Guide that is printed with
Software Release Notes: DataGen (68P02900W76).
2 Log on to DataGen processor as omcadmin.
3 Enter the following command to verify that DataGen is not being accessed:
whodo
4 Close all open DataGen GUIs.
5 Enter the following command to start DGAdmin:
DGAdmin
6 To display the INFORMIX-SQL main menu, type:
dbaccess
Dropping the database
To drop and recreate the Informix database, perform the following procedure.
Procedure 3-9 Drop the Informix database
1 Select Database from the main menu.

2 Select Drop from the Database menu.
3 Select the database to drop:
db_dg@<DataGen hostname>
Where DataGen hostname is the name of the DataGen processor.
A confirmation menu is displayed.
4 Select Yes to continue.
5 Select Exit and in all subsequent menus to return to the Admin prompt.
3-24 68P02900W22-S
Jul 2008
System Information: DataGen Dropping and recreating the db_dg Informix database
Creating a database
To recreate the Informix db_dg database, perform the following procedure.
Procedure 3-10 Recreate the Informix db_dg database
1 Execute the following commands to create a database:

/usr/omc/DataGen/current/install/CreateDatabase
2 To activate each user on the new Informix database, type:
tp -u <username>
Where username is the name of the DataGen user.
3 Exit from the omcadmin account.
Loading the OLM netwk_conf table
To recover the OLM network configuration information, the netwk_conf table previously
unloaded to a file must now be loaded into the DataGen Informix (db_dg) database.
To load the netwk_conf table, log on to DataGen processor as omcadmin. Execute the
command (in the same line):
echo "load from /usr/tmp/netwk_conf.unl insert into netwk_conf" | DGAdmin

dbaccess db_dg
The OLM network configurations are now visible in the OLM GUI.
Loading the DataGen configuration tables
In order to recover the configuration information for the DataGen BSS areas, the country,
network, bss_conf, bss_list, and conf_list tables, previously unloaded to a file must now be
loaded into the DataGen Informix (db_dg) database.
To load the tables, log on to DataGen processor as omcadmin. Execute the commands (in
the same line):
echo "load from /usr/tmp/country.unl insert into country" | DGAdmin dbaccess

db_dg
echo "load from /usr/tmp/network.unl insert into network" | DGAdmin dbaccess

db_dg
echo "load from /usr/tmp/bss_conf.unl insert into bss_conf" | DGAdmin dbaccess

db_dg
echo "load from /usr/tmp/bss_list.unl insert into bss_list" | DGAdmin dbaccess

db_dg
echo "load from /usr/tmp/conf_list.unl insert into conf_list" | DGAdmin dbaccess

db_dg
The DataGen BSS areas are now visible in the DataGen GUI.
68P02900W22-S 3-25
Jul 2008
Importing existing CM database objects Chapter 3: Operating DataGen
Importing existing CM database objects

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview
A Configuration Management (CM) database object is a binary format file. Before the
development of DataGen, such file could be created only by downloading an ASCII format script
file into a BSC in SYSGEN mode.
DataGen has the ability to convert script files into CM database objects and vice versa.
Procedure
Importing a CM database object comprises three separate routines, performed in a defined

sequence.
For this procedure Perform the following

Create a Country and Network, if not already Use the ADMIN option in the main menu
done. and select Country Admin to set up new
Country and Network definitions.
Create a New BSS Area. Use the New BSS Area window to define
the new BSS Area.
Import a CM database object. Use the Service window.
3-26 68P02900W22-S
Jul 2008
System Information: DataGen Creating a country/network
Creating a country/network
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of creating a country/network
Existing DataGen users with an earlier DataGen version can use this database to maintain
previously created country or network data. Refer to the section Restore procedures in
Software Release Notes: DataGen (68P02900W76) for information about restoring a database.
New DataGen users must create the required country or network data from the beginning. The
procedure for creating countries and networks in DataGen uses the Country Admin option
which is obtained by selecting ADMIN from the main menu.
Country Admin option
Perform the following procedure to access the Country Admin option.
Procedure 3-11 Accessing the Country Admin option
1 To access the Country Admin option for a new country or network, start
DataGen from an Xterm window and select ADMIN from the DataGen main
menu. The Administration menu is displayed as shown in Figure 3-4.
2 Select Country Admin from the Administration menu. The Country
Administration window is displayed as shown in Figure 3-8.
3 If the Country Admin option is already in use, a warning message is displayed.
Click OK to return to the Administration menu.
Figure 3-8 Country Administration window
68P02900W22-S 3-27
Jul 2008
Country Administration window - An Overview Chapter 3: Operating DataGen
Country Administration window - An Overview
The Country Administration window (as in Figure 3-8) enables users to create, update, and
edit Country and Network Administration files as follows.
File menu
The user option is Exit. The Exit option is used to exit from the Country Administration
window.
Country menu
The user options are:

• Edit
Select to use GTE to edit the default Country.
• Generate
Select to generate a Country Administration file from the DataGen database.
• Update
Select to update the DataGen database with the default Country Administration file.
NOTE
For NEW users where no country.std file exists, select Generate from the Country
menu to automatically generate a country.std file in the /home/omcadmin/dg/AD-
MIN directory. This also applies to the network.std file.
3-28 68P02900W22-S
Jul 2008
System Information: DataGen Country Administration window - An Overview
Network menu

• Edit
Select to use GTE to edit the default Network Administration file.
• Generate
Select to generate a Network Administration file from the DataGen database.
• Update
Select to update the DataGen database with the default Network Administration file.
NOTE
Country and Network menu options may be grayed out, according to which operations
are permitted at the time.
Data fields

• Country File
Displays the default Country Administration file name when the CADM GUI window
is opened.
• Network File
Displays the default Network Administration file name when the CADM GUI window is
opened.
68P02900W22-S 3-29
Jul 2008
Creating a country Chapter 3: Operating DataGen
Creating a country
To create a country using Country Admin option, perform the following procedure.
Procedure 3-12 Create a country using Country Admin
1 Select the Edit option from the Country menu in the Country
Administration window (as in Figure 3-8). The CADM Country File window
shown in Figure 3-9 is displayed.
Figure 3-9 CADM Country File window
2 From the Edit menu in the CADM Country File window, select Insert. Select
Insert to display a submenu with Before entry and After entry options. These
options allow the new entry is to be placed before or after an existing entry in
the displayed list of countries (if existing).
3 Type the name of the new country, press the Tab key, and then type the MCC
number followed by CR.
4 Select Store in DDS from the File menu in the CADM Country File window.
NOTE
The new data is saved only locally at this point.
5 Select Exit from the File menu to close the CADM Country File window.
Continued
3-30 68P02900W22-S
Jul 2008
System Information: DataGen Editing a country
Procedure 3-12 Create a country using Country Admin (Continued)

6 In the Country Administration window, select Country - Update to save the
updated Country list in the Informix database.
A Message window requesting confirmation is displayed as in Figure 3-10.
Figure 3-10 CADM message window
7 Click OK to confirm the update. A message is displayed showing that the

update has taken place.
NOTE
The new data is now permanently stored.
Editing a country
Once a country is created, it can be edited using the Edit option from the Country menu on the
Country Administration window.
Creating a network
A new network entry is created and edited in the same way as a new country entry, using the
following procedure.
Procedure 3-13 Create a network
1 Select Edit from the Network menu in the Country Administration

window as in Figure 3-8. The CADM Network File window is displayed
as in Figure 3-11.
Continued
68P02900W22-S 3-31
Jul 2008
Creating a network Chapter 3: Operating DataGen
Procedure 3-13 Create a network (Continued)

2 Perform step 2 as in Procedure 3-12, and enter the required data in the
MNC, NCC, Network Name, and Operator Name data fields.
Figure 3-11 CADM Network File window
3 Select Store in DDS from the File menu in the CADM Network File
window.
NOTE
The new data is saved locally.
4 Select Exit from the File menu to close the window.
5 In the Country Administration window, select Network-Update
to save the updated Network data in the Informix database. A Message
window requesting confirmation is displayed as in Figure 3-10.
6 Confirm the update by clicking the OK button. A message is displayed
showing that the update has taken place.
NOTE
The new data is now permanently stored.
3-32 68P02900W22-S
Jul 2008
System Information: DataGen Deleting a country/network
Deleting a country/network
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of deleting a country/network
To delete a country using the Country Administration Tool, the associated BSS areas and
network must first be deleted.
The BSS areas, network, and country must be deleted in the following order:
• BSS areas
• Network
• Country
To delete a BSS areas, refer to the section Deleting a BSS area on page 3-43 for details.
Deleting the network
After deleting the BSS areas, the network can also be deleted using the following procedure.
Procedure 3-14 Delete the network
1 From the DataGen main menu, select the ADMIN option.

2 Select Country Admin from the Administration menu bar. The Country
Administration window is displayed as in Figure 3-8.
3 Select Edit from the Network menu. The CADM Network File window is
displayed as in Figure 3-11, which shows a list of networks.
4 Click the number adjacent to the network to be deleted.
5 From the Edit menu, select Delete.
6 From the File menu, select Store in DDS.
7 From the File menu, select Exit to return to the Country Administration
window.
8 From the Country Administration window, select Update from the
Network menu. A Message window is displayed requesting confirmation of
the update.
9 Click OK to update the database.
68P02900W22-S 3-33
Jul 2008
Deleting the country Chapter 3: Operating DataGen
Deleting the country
After the BSS areas and its network is deleted, the country can be deleted using the same
sequence of steps as described for deleting the network.
In the Country Administration window, select the Edit option from the Country menu and
follow step 4 to step 9 of Procedure 3-14 to delete the country.
3-34 68P02900W22-S
Jul 2008
System Information: DataGen Creating a BSS area
Creating a BSS area

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of creating a BSS area
This section describes the New BSS Area window and the procedure for creating a BSS area.
New BSS Area window
From the DataGen main menu, select NEW (refer to Figure 1-1). The New BSS Area window is
displayed as shown in Figure 3-12.
Figure 3-12 New BSS Area window
The New BSS Area window has the following layout:
User input Country Name (automatically entered)

areas BSS Area
Software Version
Configuration number
Data field Area Comment
Action buttons Create
Close
Country Name
The list of available countries is already present in the window. All other columns are blank at
this time.
68P02900W22-S 3-35
Jul 2008
Creating a BSS area Chapter 3: Operating DataGen
BSS Area
When a Country Name is selected, any BSS areas currently configured for that country are
displayed.
Users can select an existing BSS area or else create a BSS area by typing the name of the new
BSS area in the text box below the BSS Area column.
Software Version
Once a Country Name is selected, the software versions available are listed in the Software
Version column. Select the appropriate software version.
Configuration number
When the software version is selected, the configuration numbers that exist are listed in the
Configuration number column. Three user options are available:
• Enter a new configuration number by typing the number in the text box below the
Configuration number column.
• Reuse an existing number by selecting from the list of numbers.
• If no configuration number is selected, the lowest configuration number available is

allocated to the new BSS area, by default.
Area Comment
The Area Comment data field allows the users to add useful information or comments, which
are displayed every time the BSS area is selected.
• When all entries are made, click Create. DataGen checks the entries and opens the
Service Window.
• Click Close to exit without creating a BSS area.
Creating a BSS area
To create a BSS area, perform the following procedure.
Procedure 3-15 Create a BSS area
1 Select a country from the Country Name list in the New BSS Area window
(refer to Figure 3-12).
Continued
3-36 68P02900W22-S
Jul 2008
System Information: DataGen Creating a BSS area
Procedure 3-15 Create a BSS area (Continued)

2 Click in the text box under the BSS Area column and enter the name of the
new BSS area. The name can have a maximum of 30 characters. If more than
30 characters are entered, a Warning window is displayed as in Figure 3-13.
Click OK to continue and then enter a BSS Area name limited to the
maximum length.
Figure 3-13 Warning message: name exceeds maximum valid

length

4 To obtain a configuration number automatically, do not select a number
but skip to step 6.
NOTE
If no configuration number is entered or selected, the lowest
configuration number available is assigned to the new BSS area.
5 Select a Configuration number from the list or enter a number in the data
field below the Configuration number list box. If an existing number is
reused, a Confirmation window is displayed as in Figure 3-14.
Figure 3-14 Overwrite BSS Area Confirmation window
Click OK to overwrite the existing BSS area or Cancel to return to the New
BSS Area window, and enter an alternative number.
Continued
68P02900W22-S 3-37
Jul 2008
Creating a BSS area Chapter 3: Operating DataGen
Procedure 3-15 Create a BSS area (Continued)

6 Click the Create button. After a short delay while the new BSS is being
created, the Service window is displayed. Refer to Figure 3-15.
Figure 3-15 The Service window
7 The Service window remains open on the DataGen desktop, allowing the
user to carry out most of the remaining DataGen functions. The Area
Comment data field allows the user to add useful comments which are
displayed each time the BSS area is selected. The functions of the grayed
toolbar icons are available only at a later stage. The following section
describes the layout and functionality of the Service window.
3-38 68P02900W22-S
Jul 2008
System Information: DataGen Opening a BSS area
Opening a BSS area

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Opening a BSS area
NOTE
The maximum number of BSS areas that can be opened at a time is 10.
To open an existing BSS area from the DataGen Main window, perform the following procedure.
Procedure 3-16 Open a BSS area
1 From the DataGen main menu, select Open. The Open BSS Area window is
displayed as shown in Figure 3-16.
Figure 3-16 Open BSS Area window
2 Select a country from the Country Name list in the Open BSS area window.
3 Select a BSS area from the BSS Area list.
4 Select the software version from the Software Version list.
5 Select the configuration number from the Configuration number list.
NOTE
Select multiple configuration numbers to open multiple
configurations simultaneously as shown in Figure 3-16.
Continued
68P02900W22-S 3-39
Jul 2008
Opening a BSS area Chapter 3: Operating DataGen
Procedure 3-16 Open a BSS area (Continued)

6 Click Open. After a short delay, the Service window is displayed. Refer to
The Service window on page 3-56 for details. The Service window provides
options which enable the users to view and edit DataGen input files. If another
user locks the BSS area, an Information window is displayed as shown in
Figure 3-17.
Figure 3-17 Locked Information window
NOTE
If the Override Lock parameter is enabled then the configuration
is unlocked automatically. Refer to Administration tasks on page
3-12 for details.
7 Click OK to override the lock or Cancel to return to the Open BSS Area
window.
NOTE
Information on the user holding the lock is found in the DataGen.log
file. Refer to Administration tasks on page 3-12 for details.
3-40 68P02900W22-S
Jul 2008
System Information: DataGen Copying a BSS area
Copying a BSS area

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Copying a BSS area procedure
The Copy function allows a BSS area to be copied to a new area with a new or specified
configuration number. To aid traceability when an area is copied, a default area comment is
inserted identifying the origin of the copied area.
To copy a BSS area, perform the following procedure.
Procedure 3-17 Copy a BSS area
1 From the DataGen main menu, select Copy. The Copy BSS Area window is
displayed as in Figure 3-18.
Figure 3-18 Copy BSS Area window

5 Select a Configuration number from the Configuration number list.
6 Enter the name of new BSS area in the field below the Target BSS list.
NOTE
To overwrite an existing BSS area, select the BSS area from the
Target BSS list.
Continued
68P02900W22-S 3-41
Jul 2008
Copying a BSS area procedure Chapter 3: Operating DataGen
Procedure 3-17 Copy a BSS area (Continued)

7 Enter a Configuration number in the field below the Target Config list. If
the number exists, DataGen assigns the next available number.
NOTE
If a configuration number is not entered, then DataGen automatically
assigns the lowest configuration number available.
The Area Comment field, by default, contains the following information:

Copied from <BSS Area><Configuration No>
Where, BSS area is the name of the original BSS area and Configuration No
is the configuration number of the original BSS area.
8 Click Copy to copy the selected BSS area to a new area.
NOTE
All columns in the Table Controller window for the new area are
blank because the structure is copied but not the input tables.
3-42 68P02900W22-S
Jul 2008
System Information: DataGen Deleting a BSS area
Deleting a BSS area

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Deleting an existing BSS area
NOTE
The maximum number of BSS areas that can be deleted at a time is 10.
To delete an existing BSS area, perform the following procedure.
Procedure 3-18 Delete a BSS area
1 From the DataGen main menu select DEL. The Delete BSS Area is displayed
as shown in Figure 3-19.
Figure 3-19 Delete BSS Area window
2 Select a country from the Country Name list in the Delete BSS Area window.
Continued
68P02900W22-S 3-43
Jul 2008
Deleting an existing BSS area Chapter 3: Operating DataGen
Procedure 3-18 Delete a BSS area (Continued)

5 Select the Configuration number from the Configuration number list.
NOTE
Select multiple configuration numbers to delete BSS areas
simultaneously. Locked areas are automatically unlocked.
6 Click Delete.
NOTE
It is possible to return to the DataGen main menu while the delete
process is running. If the same BSS area is selected, the following
message is displayed:
This area is already being deleted.
When the BSS area is deleted, an Information window displays the name of
the deleted BSS area.
7 Click OK to continue. The Delete BSS area window is now updated.
8 Click Close to return to the DataGen main menu.
3-44 68P02900W22-S
Jul 2008
System Information: DataGen Configuring BSS areas
Configuring BSS areas

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to configuring the BSS
This section provides two examples on BSS configuration:

• Expansion of a basic BSS and its TS by the addition of another Basic Transceiver Site (BTS).
• Daisy chaining BTSs with a TS.
For information about the Motorola Customer Data Format (MCDF) tables referenced in this
section, refer to Chapter 6 MCDF tables which comprises a complete list of all the DataGen
MCDF tables, including parameter values and ranges.
Explanation of terms
BSS area
The BSS area means both the GSM Base Station System (BSS) and the GSM Remote Transcoder
(RXCDR). These two subsystems run the same software.
BTS and BTS Site
The Motorola implementation of the GSM Base Transceiver System (BTS) differs from
the GSM specifications in that a Motorola BTS can support more than one cell. The GSM
recommendations specify that a BTS supports only one cell. In this section, the terms BTS and
BTS site refer to the Motorola BTS.
Functions and MCDF table relationships
Each configuration or equip function for a BSS uses an MCDF table that is populated with
parameters which are generic or specified by the user. Table 3-2 lists these functions and their
equivalent MCDF tables.
68P02900W22-S 3-45
Jul 2008
Functions and MCDF table relationships Chapter 3: Operating DataGen
Table 3-2 Function - MCDF table relationships
Function Equivalent MCDF table(s)

Equip Site (modify or add Site
new site)
Equip Cabinet Cabinet
Equip Cage (Automatically done when device is
equipped)
Site Configuration BTS, Generics and Statistics
Add Cell Cell, Generics, Timers and Specifics
Equip Devices Hardware, Modify Value and
Daughter
Equip Functions Hardware
Path Paths and Links
RTF RTF
BSP, DHP, BTP, LCF, MTL, DRI
Circuits, Path, RSL, OML Hardware
Circuits
KSW
PIX Card Daughter and PIX
Neighbor and Source Neighbor
Equip DRIM Hardware RTF
Handovers Algorithm
Equip Pen Hardware
Equip NSVC NSVC
3-46 68P02900W22-S
Jul 2008
System Information: DataGen Basic BSS with TS switch - Expansion
Basic BSS with TS switch - Expansion

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview
This section describes the procedures used to add another BTS site to the basic BSS. To expand
the basic network, it is necessary to modify the following MCDF tables:
• The bss.mcd table
• The cab.mcd table
• The hw.mcd table
• The modv.mcd table
• The link.mcd table
• The path.mcd table
• The lapd.mcd table
• The cell.mcd table
• The rtf.mcd table
• The dri.mcd table
• The ngbr.mcd table
• The dgtr.mcd table
• The pix.mcd table
To add another BTS site to a BSS area, perform the following procedure.
Procedure 3-19 Add a BTS site to a BSS area
1 Copy an existing BSS area to a new BSS area with a different configuration
number.
2 From the Table Controller window, open each of the tables and modify
their contents.
3 Save the file in the DDS, then validate and insert the files.
4 Open a Topology window to check whether the system has added an
additional site.
68P02900W22-S 3-47
Jul 2008
Copying a BSS area Chapter 3: Operating DataGen
Copying a BSS area
To copy an existing BSS area, perform the following procedure.
NOTE
A BSS area can be copied by selecting Copy from the DataGen main menu. Refer to
Copying a BSS area on page 3-41 for details.
Procedure 3-20 Copy a BSS area
1 Open an Xterm window, and enter the command to obtain the DGAdmin
prompt: DGAdmin
2 Copy an existing BSS area to a new BSS area having the
same <BSS Area name> but with a different <config> number
by executing the following command in the Xterm window:
ca -source <country name>:<BSS area name>:<configuration number>

[-area <new BSS area name> [-id <new BSS area id>]] [-config
<new configuration number>] [-title <new configuration title
string>]
For example:
ca -source Austria:Area1900:17 -area Area1900 -config 18
The following message is displayed:
New area successfully copied

Country: Austria
BSS Area name: Area1900
Configuration Number: 18
NOTE
The BSS area to be copied should be the BSS area that was built
using the procedure in the previous section.
3 Select Open from the DataGen main menu to display a BSS Area window.
A list of available countries is displayed.
4 Select the Country Name of the new BSS area. Then select the new BSS
Area name to display a list of software versions.
5 Select the correct Software Version and the new Configuration Number
in the list boxes.
6 Click the Open button. DataGen then checks the entries and opens a
Service window for the new BSS area. For more information about the
Service window, refer to The Service window on page 3-56.
Expanding the BSS
The procedure for entering reconfiguration parameters in the tables to expand the basic BSS is
the same for each table. The tables to be modified are listed in the overview of this section.
3-48 68P02900W22-S
Jul 2008
System Information: DataGen Expanding the BSS
Reconfigure for expansion
To reconfigure the necessary MCDF tables, perform the following procedure.
Procedure 3-21 Reconfigure MCDF tables for expanding the BSS
1 From the Service window, select the Service menu, then select Table
Controller to open a Table Controller window. Refer to the section Using
the Table Controller on page 3-79 for more information.
2 Select a <filename> check box, then click the File button in the Table
Controller window to display the <Filename.mcd> table window.
If new columns are to be added before the data can be modified, go to
step 3; else go to step 5.
3 Highlight the top right-hand cell of the table, then select Insert from the
Edit menu. Select After entry from the submenu displayed to add another
column to the table.
4 Repeat step 3 if more columns are to be added; otherwise go to step 5.
5 Enter the appropriate values in the data fields. Use the Return key to go to
the next data field. Refer to Chapter 6 MCDF tables for information about
values and ranges.
Continue to enter data until all the relevant data fields have been edited.
6 In the window which has been edited, open the File menu and select the
Store in DDS option.
7 Select Exit from the File menu to close the edited MCDF table.
8 Clear the current <filename> check box in the Table Controller window
and then select the next required <Filename> check box.
9 Repeat step 2 to step 8 until all the relevant MCDF tables have been edited.
68P02900W22-S 3-49
Jul 2008
Expanding the BSS Chapter 3: Operating DataGen
Insert and validate the reconfigured MCDF tables
To insert and validate the reconfigured MCDF tables, perform the following procedure.
Procedure 3-22 Insert and validate the MCDF tables
1 In the Table Controller window, open the Select menu.

2 Select the Select All Files option, then click Validate. The MCDF
files that are being validated are displayed in a Message window.
A second window then displays the following message:
Filtering of file(s) has completed.

3 Close the Message window, then open the Select menu again. Choose the
Select All Files option, then click Insert. The MCDF files
that are being inserted are displayed in a Message window.
A second window then displays the message:
Filtering of file(s) was successful database has been

updated.
To confirm that the BSS configuration is as expected, select the Topology icon in the Service
window or the Topology option from the Services menu in the Service window to display
the configuration. Refer to the section Using the Topology Viewer on page 3-105 for more
information.
Figure 3-20 shows the topology of the new BSS area with the additional site added.
3-50 68P02900W22-S
Jul 2008
System Information: DataGen Expanding the BSS
Figure 3-20 Basic BSS with TS Switch - expanded
68P02900W22-S 3-51
Jul 2008
Daisy Chain configuration with TS switch Chapter 3: Operating DataGen
Daisy Chain configuration with TS switch

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of Daisy Chain configuration
This section describes the procedures used to reconfigure the expanded basic network as
a Daisy Chain.
Perform the following steps:

• Copy an existing BSS area and assign a different configuration number to the copied
BSS area.
• From the Table Controller window, open each of the tables and modify their contents.
• Save the file in the DDS, then validate and insert the files.
• Open a Topology window to check that the additional site has been added by the system.
Preparation
To configure a BSS area as a Daisy Chain, it is easier to use an existing BSS area (such as the
expanded BSS configuration or another similar existing BSS configuration) by copying the area
and then assigning a different configuration number to the copied BSS area.
A BSS area can be copied using the procedure outlined in the section Basic BSS with TS
switch - Expansion or by selecting Copy from the DataGen Main menu. Refer to Copying a
BSS area on page 3-41 for details.
Procedure 3-23 Preparation
1 Once the BSS area is copied, select Open from the DataGen main menu to
display the BSS Area window.
2 The list of available countries is displayed. Select the following: Country
Name, BSS Area Name, Software Version and enter the new configuration
number.
Continued
3-52 68P02900W22-S
Jul 2008
System Information: DataGen Daisy chain configuration
Procedure 3-23 Preparation (Continued)

3 Click the Open button. DataGen then checks the entries and opens a
Service window for the new BSS area.
NOTE
For more information about the Service window, refer to The
Service window on page 3-56.
Daisy chain configuration
This procedure is used to the modify MCDF tables in order to reconfigure (as a Daisy Chain) the
copied version of the expanded BSS (or another BSS version). The files to be modified are:
• The link.mcd table
• The path.mcd table
• The lapd.mcd table
• The cell.mcd table
Daisy chain configuration
To reconfigure the necessary MCDF tables, perform the following procedure.
Procedure 3-24 Modify MCDF tables for Daisy Chain configuration
1 From the Service window, open the Service menu.

2 Select Table Controller to open a Table Controller window. Refer to the
section Using the Table Controller on page 3-79 for more information.
68P02900W22-S 3-53
Jul 2008
Daisy chain configuration Chapter 3: Operating DataGen
Links table
To modify the Links table, perform the following procedure.
Procedure 3-25 Modify the Links table
1 Select the Link check box, then select the File button in the Table
Controller window to display the <link.mcd> table window.
2 Use the cursor to highlight column 3, then open the Edit menu and select
Delete to delete the highlighted column.
3 Starting at the top of column 2 in the MCDF table window, change the
data in each data field as required. For more information about values and
ranges, refer to the Links table in Chapter 6 MCDF tables.
4 Continue to enter data until all the relevant fields are edited, then move the
cursor away from the edited data fields.
5 Open the File menu and select the Store in DDS option. Select Exit from
the File menu to close the edited MCDF table.
Paths table
To modify the Paths table, perform the following procedure.
Procedure 3-26 Modify the Paths table
1 Clear the check box in the Table Controller window, and select the Path
button to display the <path.mcd> table.
2 Use the cursor to highlight column 3, then select the Edit menu and choose
3 Starting at the top of column 2 in the Paths table window, change the data
in each data field each data field as required. For more information about
values and ranges, refer to the Paths table in Chapter 6 MCDF tables.
4 Continue to enter data until all the relevant data fields are edited, then
move the cursor away from the edited data fields.
3-54 68P02900W22-S
Jul 2008
System Information: DataGen Daisy chain configuration
LAPD table
To modify the LAPD table, perform the following procedure.
Procedure 3-27 Modify the LAPD table
1 Clear the Paths check box in the Table Controller window and select the
Lapd button to display the <lapd.mcd> table.
2 Use the cursor to highlight column 4, then select the Edit menu and choose
3 Starting at the top of column 3 in the Lapd table window, change the data in
each data field as required. For more information about values and ranges,
refer to the LAPD table in Chapter 6 MCDF tables.
4 Continue to enter data until all the relevant data fields are edited, then using
the Return key, move the cursor away from the edited data fields.
Cell table
To modify the Cell table, perform the following procedure.
Procedure 3-28 Modify the Cell table
1 Clear the Lapd check box in the Table Controller window and select the
RTF button to display the <rtf.mcd> table.
2 Change the data in each data field in the row Primary Path ID as required.
For more information about values and ranges, refer to the RTF table in
Chapter 6 MCDF tables.
3 Continue to enter data until all the relevant data fields are edited, then
move the cursor away from the edited data fields.
5 Clear the RTF check box in the Table Controller window and continue
with the procedure for inserting and validating MCDF tables. Refer to
Procedure 3-22.
To confirm that the BSS configuration is as expected, select the Topology icon in the Service
window or the Topology option from the Services menu in the Service window to display
the configuration. Refer to the section Using the Topology Viewer on page 3-105 for more
information.
68P02900W22-S 3-55
Jul 2008
The Service window Chapter 3: Operating DataGen
The Service window

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Functions of the Service window
The Service window provides several options which enables the users to view and edit DataGen
input files. When the Service window opens, details of the current BSS Area selected are
displayed as in Figure 3-21. The Service window contains a menu bar and a toolbar.
The toolbar contains the options which are used most frequently, allowing quicker access.
Figure 3-21 Service window
Service window toolbar
The Service window toolbar contains six buttons which have the following functionality:
3-56 68P02900W22-S
Jul 2008
System Information: DataGen Service window toolbar
Table Controller
The Table Controller button enables the user to create and edit BSS area data files. This
button has the same functionality as the Table Controller option in the Services menu.
Revgen/Compile
The Revgen/Compile button has dual functionality. When there is no data in the BSS area, the
Revgen function is displayed. When there is data in the BSS area, the Binary Object Compiler
function is enabled.
The Revgen button has the same functionality as the Revgen option, and the Compile button
has the same functionality as the Object Compiler option in the Services menu.
Topology
The Topology button enables the user to view a graphical representation of a BSS area. The
Topology button has the same functionality as the Topology option in the Services menu.
MMI
The MMI button creates a set of MMI command files for the selected area and concatenates
them. The MMI button has the same functionality as the Generate Script option in the
Services menu.
68P02900W22-S 3-57
Jul 2008
Service window menu bar Chapter 3: Operating DataGen
Exit
The Exit button closes the Service window and takes the user back to the DataGen main menu.
Help
The Help button displays the following message:

For DataGen Help please refer to the DataGen manual supplied, OLM On-Line help
is available through the OLM GUI.
Service window menu bar
The menu bar provides access to all options available whereas the toolbar provides access to
those tools which are used frequently. There are four main menus:
• File
• Edit
• Services
• Help
File menu
The following options are available from the File menu on the Service window:
• Import Object
• Export Object
• Make Directories
• Save
• History
• Exit
3-58 68P02900W22-S
Jul 2008
System Information: DataGen File menu
Import object
Select the Import Object from the File menu in the Service window. The Database Object
window is displayed as shown in Figure 3-22. This window enables the users to import .002
object files into DataGen.
To import a file into a BSS area, select the required directory from the Directories scroll box.
By default, the directory Filter is set to /usr/omc.
NOTE
• If the path is changed, the directory Filter is set to the last path used for
the current session, unless DG_IMPORT_PATH is defined. Refer to Defining
environment variables on page 3-4 for details.
• To import binary object files from an integrated OMC, the import path is:
/usr/omc/ne_data.
Figure 3-22 Database Object window
Click Filter to display the entries in the Files scroll box. Select the required file and click OK.
An Information window (as shown in Figure 3-23) is displayed when the file is imported to
the BSS area.
68P02900W22-S 3-59
Jul 2008
File menu Chapter 3: Operating DataGen
NOTE
The binary object creation Date and Time stamp is displayed in the Information
window.
Figure 3-23 Import Object - Information window
Export Object
The Export object option displays the default path, where the binary objects are exported.
To transfer binary object files from DataGen to a BSS, perform the following procedure.
Procedure 3-29 Transfer binary object files from Datagen to a BSS
1 Transfer the binary objects files to the OMC. Refer to Exporting object files
to the OMC on page 3-115 for more details.
2 Download the binary object files from the OMC to the BSS.
Continued
3-60 68P02900W22-S
Jul 2008
Procedure 3-29 Transfer binary object files from Datagen to a BSS (Continued)
3 Selecting Export Object from the File menu on the Service window
identifies the file path for the OMC operator. The following Information
window is displayed.
Figure 3-24 Export Object - Information window
NOTE
To define an alternative path to export the binary object files (002), refer to
Administration tasks on page 3-12 for details.
Make Directories
If an area exists in the DataGen database but does not have the corresponding directory
structure, for example, ~dg/country_name/area_name/conf_no/, the Make Directories
option can be used to create the directory structure.
Save
This option enables the DataGen user to save the current state of DataGen in case of
interruptions.
68P02900W22-S 3-61
Jul 2008
File menu Chapter 3: Operating DataGen
History
This option provides the following details of a BSS area as shown in Figure 3-25:
• Title
If a new BSS area is created, the title contains the following information: Country, BSS
area, Configuration Number, and Software version. The title reflects if the area is copied
or upgraded.
• Owner
• Creation Date
• Modified By
• Modification Date
Figure 3-25 History - Information window
Exit
Select the Exit option to close the Service window and return to the DataGen main window.
This option is the same as clicking the X button in the Service window.
3-62 68P02900W22-S
Jul 2008
System Information: DataGen Edit menu
Edit menu
The following options are available in the Edit menu of the Service window:
• Script
• Compile log
• Upgrade log
• Hardware report
Script
This option enables the user to view an MMI Script file using the X-Windows editor xedit. Refer
to the section Generating a database script file on page 3-71.
Compile log
This option enables the user to view the compile log file, using the X-Windows editor xedit,
running the object compiler. Refer to the section Generating a database script file on page
3-71 for details.
Upgrade log
This option enables the user to view the upgrade log file, using a text editor. The upgrade log
file is available for upgrades carried out through the GUI. The log file is not created if the
upgrade is carried out from the command line. Refer to Upgrader on page 3-123 for details on
how to upgrade a software release.
NOTE
Operators can define the default editor for editing scripts or viewing the compile or
upgrade logs. Refer to Administration tasks on page 3-12 for details.
Hardware Report
This option enables the user to view a hardware report a text editor. Refer to Generating a
hardware report on page 3-110 for details.
68P02900W22-S 3-63
Jul 2008
Services menu Chapter 3: Operating DataGen
Services menu
The following options are available in the Services menu of the Service window:
• Table Control
• Revgen
• Object Compiler
• Topology (after Revgen)
• Generate Script (after Revgen)
• Recombine Script
• Generate Hardware Report (after Revgen)
Table Control
Select this option to open a Table Controller window, view, and edit the BSS tables. Refer to
Using the Table Controller on page 3-79 for details.
Revgen
Select the Revgen option to activate the Revgen process and convert the selected object file
into a DataGen script file. The binary object file can be compressed or uncompressed. Refer to
Converting a CM database object file to a script file on page 3-66 for details.
Object Compiler
The Object Compiler enables the user to generate a .002 Object file from the MMI Script. The
.002 object files are automatically compressed.
Recombine Script
Select the Recombine Script option to enable the concatenation of many MMI script files into
a single file. This also generates individual site based MMI script files, for example: SITEXXX,
where site number replaces XXX.
Topology
The Topology option becomes available after the Revgen process is complete. Selecting this
option enables the users to view a graphical representation of a BSS area.
Generate Script
The option becomes available after the Revgen process is complete. Selecting this option
enables the user to generate an MMI script file and individual site files.
3-64 68P02900W22-S
Jul 2008
System Information: DataGen Services menu
Generate Hardware Report
The option becomes available after the Revgen process is complete. Selecting this option
enables the users to generate a hardware report which contains a list of all the device names,
function names, slot numbers, and Id devices within each cage. Refer to Generating a hardware
report on page 3-110 for details.
68P02900W22-S 3-65
Jul 2008
Converting a CM database object file to a script file Chapter 3: Operating DataGen
Converting a CM database object file to a script file

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to creating a script file
Converting a CM Database Object to a Database Script File enables upgrading to a later

software version, or changing some parameters in the existing software version. It also enables
the user to view the topology of a BSS area.
Invoking Revgen
Revgen is invoked either by selecting REVGEN from the Services menu or clicking the Revgen
button on the toolbar.
Depending on how the environment variable setenv DG_AUTO_REVGEN is set, selecting Revgen
can result in the following:
• The Revgen window opens.
• The Revgen window opens and Revgen starts automatically.
Refer to Defining environment variables on page 3-4 for details on how to set the environment
variable DG_AUTO_REVGEN. By default, this environment variable is not enabled.
The software version of the new BSS area MUST be the same as the imported CM database
object.
NOTE
Revgen can be run successfully only on a NEW BSS area. The CM database binary
object file can be compressed or uncompressed.
Revgen window description
The Revgen window (refer to Figure 3-26) is divided into four areas as follows:
• File menu on page 3-67
• Information area on page 3-67
• Data area on page 3-67
• Toolbar on page 3-67
3-66 68P02900W22-S
Jul 2008
File menu
Table 3-3 describes the File menu options in the Revgen window.
Table 3-3 Revgen window file menu options
Select To
Import BSS Object Specify and import a CM Database
object.
Run Revgen Start the Object conversion.
Remove Lock File Unlock a BSS area.
Exit Exit and close the Revgen windows.
Information area
The information area in the Revgen window contains three data fields as described in
Table 3-4.
Table 3-4 Revgen window file menu options
Information area Definition

BSS Area BSS area into which CM Database Object is to
be loaded, and the software version.
Status Informs the user of the status of Revgen.
Object Displays the path to the object which is to be
converted.
Data area
The data area displays information about the progress of the object conversion.
Toolbar
There are two buttons on the toolbar:

• Run Revgen - Select this option to start the object conversion.
• Exit - Select this option to exit from the Revgen Tool.
68P02900W22-S 3-67
Jul 2008
Activating Revgen Chapter 3: Operating DataGen
Activating Revgen
If the setenv DG_AUTO_REVGEN environment variable is not set to Yes, run Revgen as follows.
Procedure 3-30 Activate Revgen
1 Select the Revgen button or select Revgen from the Services menu.
The Revgen window is displayed as in Figure 3-26.
Figure 3-26 Revgen window
2 From the File menu, select Import BSS Object.

3 Select the required directory from the Directories list.
4 Click the Filter button to display the entries in the Files list.
Continued
3-68 68P02900W22-S
Jul 2008
System Information: DataGen Activating Revgen
Procedure 3-30 Activate Revgen (Continued)

5 Select the binary object file in the Files list.
6 Select Import. A Confirmation window is displayed when the import is
complete. Click OK.
7 The initial display of Revgen shows the BSS area and the software version of
the imported object. Check these details before running Revgen.
8 Click Run Revgen. The information and data areas display the details and
progress of the object conversion. An example is shown in Table 3-4.
Figure 3-27 Running Revgen
Continued
68P02900W22-S 3-69
Jul 2008
Activating auto Revgen Chapter 3: Operating DataGen
Procedure 3-30 Activate Revgen (Continued)

9 Click Exit to return to the Service window when the process is complete.
NOTE
If the Exit button is selected before Revgen is complete, the actual
conversion of the .002 object is not terminated, because it is running
as a background task. The Revgen tool is monitoring the status of
the logfile, and when Revgen is invoked again, the current status
of the logfile is displayed.
Activating auto Revgen
If the setenv DG_AUTO_REVGEN environment variable is set to Yes, run Revgen as follows:
Select the Revgen button or select Services - Revgen from the menu bar. This displays
the Revgen window and starts the Revgen process. The Information window displays the
details and progress of the object conversion. Table 3-4 displays an example of the window
on completion of Revgen.
Select the Exit button to return to the Service window when the process is complete.
NOTE
If the Exit button is selected before Revgen is complete, the actual conversion of the
.002 object is not terminated, because it is running as a background task. The Revgen
tool is monitoring the status of the logfile, and when Revgen is invoked again, the
current status of the logfile is displayed.
Completion of Revgen process
As the process is completing, the following message is displayed:

Loading BSS Area. Please wait. . .
Completion of the Revgen process may take several minutes for a large BSS area. On
completion, a new Service window is displayed with a full complement of tools.
NOTE
• If the BSS Area gets locked when trying to open it, refer to the section
Lock/unlock BSS area (lock_adm) command on page 5-20 in Chapter 5 Command
line tools.
• Alternatively, use the Remove Lock File option in the File menu.
3-70 68P02900W22-S
Jul 2008
System Information: DataGen Generating a database script file
Generating a database script file

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of database script files
After the Revgen process is completed successfully, it produces a database script file in the
DataGen output file directory.
The system also issues a report stating that the database tables are populated.
Running the script file generator
Generating a database script can be performed from the Services window (refer to Figure 3-28)
either by clicking the MMI button or selecting the Generate Script option in the Services
menu.
The database script generator uses the file data in the Service window (Country, BSS Area,
Software Version, and Configuration number) to identify the correct file. The operator is
informed when the script has been successfully created.
The database script file is stored in the output file directory of DataGen.
NOTE
• Each time a combined script is generated the original script is backed up with a
Date and Time stamp. For example COMBINED.BACKUP072498123425. This
allows the original script to be compared against the new script. Individual site
files are created, for example; SITE<XXX>, where site number replaces XXX.
• If the Options Object file is found to be missing or corrupt, an error message as
shown in Figure 3-28 is displayed. Refer to Administration tasks on page 3-12
for details of reinstalling the Options object file.
68P02900W22-S 3-71
Jul 2008
Viewing a database script file Chapter 3: Operating DataGen
Figure 3-28 Invalid Options Object message
Viewing a database script file
After a database script file has been created, it can be viewed by selecting the Script option in
the Edit menu of the Service Window.
The script file is displayed within a xedit window as shown in Figure 3-29. The script file can
be edited at this point, although this is not recommended unless an error has occurred as a
result of the compiler process. If the database script file is edited, DataGen does not hold any
record of changes which are made.
To define which editor to launch when viewing scripts, refer to Defining environment variables
on page 3-4 for details.
3-72 68P02900W22-S
Jul 2008
System Information: DataGen xedit window description
Figure 3-29 Viewing a database script file
xedit window description
The xedit window comprises three main areas:

• Toolbars
• File information areas
• File display area
68P02900W22-S 3-73
Jul 2008
Using the toolbars Chapter 3: Operating DataGen
Using the toolbars
There are three toolbars on the xedit window:

• quit: exits the xedit process.
• save: saves the combined script file to a specified location or name.
• load: loads a specified combined script file.
File information areas
The file information areas show the full path of the script file presented in the display area
of the xedit window.
File display area
This area in the xedit window displays the combined script file contents which can be edited
and saved with a new BSS name. The window can be scrolled using the Up and Down arrow
keys on the keyboard.
NOTE
A script file can also be generated and edited using an editor in an Xterm window,
for example, the UNIX editor vi.
Alternative text editor
Procedure 3-31 describes the steps involved in defining a text editor to view MMI scripts or
compilation logs other than the standard editors.
NOTE
When adding a new editor, verify that the editor runs on the system processor.
Verification can be done by entering the editor name from the command line and
ensuring that it launches correctly.
3-74 68P02900W22-S
Jul 2008
System Information: DataGen Alternative text editor
Procedure 3-31 Define a text editor
1 Log on to the DataGen processor as user root.

2 Copy the selected editor to the /usr/bin directory using the following
command:
cp <text_editor> /usr/bin
Where text_editor is the name of the text editor.

3 Change the permissions on the text editor to allow all users access to the file:
chmod 555 /usr/bin/<text_editor>
Continued
68P02900W22-S 3-75
Jul 2008
Alternative text editor Chapter 3: Operating DataGen
Procedure 3-31 Define a text editor (Continued)

4 If all operators require to use the editor, add the following line to the file:
/usr/omc/DataGen/current/config/local/cshrc.datagen:
setenv DG_EDITOR <text_editor>
Where text_editor is the name of the text editor.
NOTE
If only specific operators wish to use the editor, edit the .cshrc in
the home directory of the user.
For example, if setenv DG_EDITOR vi is entered, when the script

file is invoked from the Edit menu, it is displayed with the vi editor
as shown in Figure 3-30.
Figure 3-30 Viewing an MMI script with vi
3-76 68P02900W22-S
Jul 2008
System Information: DataGen Viewing and editing DataGen files
Viewing and editing DataGen files

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of editing DataGen files
After a CM database object has been uploaded and converted using the Revgen option in
the Service window, it can be manipulated and edited into a new format using the DataGen
tools. These tools comprise:
• Table Controller
• Generic Table Editor
• Topology Viewer
• Upgrader
• Difference Reporter
Table Controller
The Table Controller enables users to create MCDF (Motorola Customer Data Format) input
files by exporting file information from the Informix database.
It also enables users to validate input files and insert the file parameters back into the Informix
database.
Generic Table Editor
The Generic Table Editor enables MCDF files to be displayed and edited from the Table
Controller.
Topology Viewer
The Topology Viewer provides users with a graphical representation of the topology of the
complete BSS area and a view of all the cage hardware in a BSS area.
68P02900W22-S 3-77
Jul 2008
Upgrader Chapter 3: Operating DataGen
Upgrader
The Upgrader is a window-based tool which is invoked by selecting the UPG button from
the DataGen main menu.
The Upgrader creates a BSS area in the Informix database. The new BSS area is an exact copy
of the BSS area in the database which is to be upgraded.
The upgrade of the BSS area is then carried out on the copy of the area so that the original
area is unchanged.
Upgrader can also be invoked using the Command Line. Refer to Chapter 5 Command line
tools Version upgrader (upg) command for details.
NOTE
If any parameters in the BSS area are to be changed before the upgrade, it should
be done by altering the MCDF files. Refer to Using the Generic Table Editor (GTE)
3-78 68P02900W22-S
Jul 2008
System Information: DataGen Using the Table Controller
Using the Table Controller

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Running the Table Controller
To open the Table Controller window (as in Figure 3-31) from the Service window, either
select the Table Control option from the Services menu or click the Table Controller button.
Figure 3-31 Partial view of typical Table Controller display
68P02900W22-S 3-79
Jul 2008
Table Controller functions Chapter 3: Operating DataGen
Table Controller functions
The Table Controller has two functions:

• Editing input files using the Generic Table Editor and inserting them into the DataGen
database.
• Exporting data to create a set of MCDF files for the BSS area.
User controls
The Table Controller comprises four main areas:

• Menu bar on page 3-80
• Command buttons on page 3-80
• File select buttons on page 3-81
• File status display area on page 3-81
Menu bar
The menu bar provides the following options to manipulate DataGen input files as described in
Table 3-5.
Table 3-5 Table Controller - menu bar File and Select options
Option Definition
Exit When selected, exits and closes the Table controller
window.
Select all Files Selects all the displayed file types in the Table
controller window.
Deselect all Clears all file types in the Table Controller window.
Files
Command buttons
The command buttons are used to perform File, Validate, Insert, Export, and Report functions
on the files imported into the Table Controller.
File
Click File to open or create an input file. A check mark shown in the File column opposite an
input file button indicates that the file exists in the DataGen input file directory.
3-80 68P02900W22-S
Jul 2008
System Information: DataGen File select buttons
Validate
Click Validate to check that the parameters held in an input file are valid. A report is produced
informing the user of the result of validation. If the report file contains any warnings, then a W
is displayed in this column against the particular parameter.
Insert
Click Insert to insert the input files into the DataGen Informix Database. Files are validated
automatically as they are inserted and a report is produced informing the user of the result
of the insertion.
Export
Click Export to export data from the Informix database into the DataGen Table Controller.
Report
Click Report to display the reports produced after using the Validate and Insert options.
There is one table report per input file. The table reports must be read before another operation
is carried out on that table. A W character in the Validate or Insert column indicates the
presence of a warning in the report file which should be checked.
File select buttons
Each check box on the left-hand side of the Table Controller is used to select or clear a DataGen
input file (table file) containing BSS database parameters. The name next to the check box
identifies the contents of the file.
File status display area
This area of the Table Controller window displays icons identifying the status of each table
during each type of operation. For example, a tick shown in the file column opposite a file
select button indicates that the file has been correctly imported. Table 3-6 shows examples of
each of these icons.
MCDF table files
The following description provides a general introduction to the contents of each table file in
the Table Controller.
68P02900W22-S 3-81
Jul 2008
MCDF table files Chapter 3: Operating DataGen
For more detailed information, refer to Chapter 6 MCDF tables.

• BSS (bss) - The BSS table is at the top of the MCDF hierarchy and contains BSS-specific
information.
• SITE (bts) - The SITE table contains specific information regarding each site in the BSS
area.
• Hardware (hw) - The Hardware table contains information regarding all cages, default
cabinets, and full-height cards throughout the BSS area. Each entry in the table contains
details of one device, with respect to the site, cabinet, cage, and slot in which the device
resides.
NOTE
The cabinets and cages are not explicitly noted in the table; further information
is included within the details of the cards.
• Cabinet (cab) - The Cabinet (optional) table contains information about all the non-default
type cabinets throughout the BSS area.
• Generics (gene) - The Generics table contains a list of elements, including

Motorola-specific elements. For convenience, the Timer and Statistics elements have been
placed in separate files. Either the value from the value field (if present) or the Motorola
recommended value is set BSS-wide but can be overridden for a site or cell by values in the
specifics and cell tables. Also, values for the commands dnlk_vad_qtx, and msc_qt are
inserted using the Generics Table.
• Timer (time) - The Timer table contains a list of timer elements, including
Motorola-specific elements. Either the value from the value field (if present) or the
Motorola recommended value is set BSS-wide but can be overridden for a site or cell
by values in the Specifics table.
• Circuit (acct) - The Circuit table contains all MTL, LMTL, and OML signaling links. It also
contains the terrestrial circuits to time slots at the BSC for radio traffic channels.
• Channel (chan) - The Channel table is only required for Remote Transcoders and contains
the OML and MTL signaling links through the remote transcoder. It also contains details of
the traffic channels between the MSC and BSC on the remote transcoder. The MSIs and
MMSs required are given in detail in the Hardware table.
• Link (link) - The Link table is used for two different tasks:
Non-RXCDR area - contains details of the links between MMSs required by the paths.
RXCDR area - contains details of the links between the RXCDR and its BSCs used
by the XBL feature.
In both cases, the MSIs and the MMSs required are given in detail in the Hardware table.
• Modify Value (modv) - The Modify Value table details all the modify_value commands
related to MMS/LCF device functions within the area.
• PATHs (path) - The Paths table gives the details of all the paths within the BSS area
(providing signaling and traffic communication between the BSC and the BTSs), using the
links detailed in the Links table. Details of RSLs are also contained in this table.
3-82 68P02900W22-S
Jul 2008
System Information: DataGen MCDF table files
• LAPD (lapd) - The LAPD table contains details of the LAPD values for the RSLs and XBLs
in the area. The RSLs and XBLs required are given in detail in the Circuits and Paths tables.
• Cell (cell) - The Cell table contains the details of all the cells across the OMC or network
and also the external neighbors used by the specified cells. The optional fields in this table
contain information which override the defaults specified in the Generics table.
• RTF (rtf) - The RTF table contains details of the RTFs contained in the BSS area.
• DRI (dri) - The DRI table contains details of the DRIs specified in the Hardware table for
the BSS area. The DRI must have its cage and slot number detailed in the Hardware table.
• Statistics (stat) - The Statistics table contains a list of statistical elements. Either the
value from the value field (if present) or the Motorola recommended value is set BSS-wide,
but can be overridden for a site or cell by values in the Specifics table.
• Specifics (spec) - The Specifics table enables the user to define specific values for
chg_element and add_cell elements for a particular site or cell overriding the parameters
specified in the Generics, Timers, and Statistics tables.
NOTE
Elements that can exist in the Cell table are not shown in the Specifics table.
• Neighbor (ngbr) - The Neighbor table identifies the cell pairings network-wide, using
the bss_id to identify the BSS area containing the cell marked as the source. The bsic
and the bssh frequency are detailed in the Cell table. The fields classed as optional may
contain values overriding those specified in the Cell table.
• Algorithm (alg) - The Algorithm table specifies the algorithm data to be used across the
BSS area. These entries do not use the lac and ci fields. It also enables the user to define
specific algorithm data for defined cells identified by their lac and ci.
• Throttles (thro) - The Throttles table specifies throttles to be applied to device types for
the whole BSS area and links them to alarm numbers.
• EAS (eas) - The EAS table is used to specify alarm strings for alarm numbers used with
the BSS area.
• Daughter (dgtr) - The Daughter table is used to identify the half-height cards at a site in
the same way as the Hardware table specifies the full-height cards.
• PIX (pix) - The PIX Table specifies the hardware circuits that activate specific alarms in
an EAS device.
• KSW (ksw) - The KSW table specifies the data for the KSW configuration commands
(chg_ksw_config). This table only has entries for sites that implement expanded KSW
cards. Also, this table only contains entries that differ from the default values generated
within the BSS and BTS tables.
• NSVC (nsvc) - The NSVC table is used to specify all the parameters of the add_nsvc
command. This is used to allow the user to map an NS-VCI and DLCI to a specific GBL.
• Hop (hop) - The Hop table is used to specify the parameters of the chg_hop_params
command.
68P02900W22-S 3-83
Jul 2008
Creating MCDF files Chapter 3: Operating DataGen
• ACS (acs) - The Active Codec Set (ACS) table is used to specify the parameters for any
chg_acs_params commands.
• Test Neighbor (testngbr) - The Test Neighbor table specifies test neighbor details that
allow the cell to add frequencies to the bcch allocation list without having that frequency
considered for a handover .
• Nail Connection (Nailconn) - The Nail Connection table is used to nail the connections
through the BSC to equip the GBLs by specifying the parameters of the chg_ts_usage
command.
Creating MCDF files
MCDF files can either be created, using blank templates, or regenerated, using an existing
database.
MCDF file procedures
File creation procedure
To create files in MCDF format, it is necessary to Export the files from the Informix database.
NOTE
• The term Export means that the functions carried out in the Table Controller
serve to Export the files out of the Informix database, perform any editing
required (or simply view the tables), and then Insert the table back into the
database.
• If a configuration area has been imported and was created using an earlier
version of DataGen, it is necessary to re-export the MCDF files owing to changes
in the DataGen MCDF tables.
• Warning messages appear during the Export process, which can be safely
ignored as the export continues successfully.
3-84 68P02900W22-S
Jul 2008
System Information: DataGen MCDF file procedures
To create MCDF files, perform the following procedure.
Procedure 3-32 Create files in MCDF format
1 After the Object file has been converted to a Script file by the Revgen
process, select Table Control from the Services menu in the Services
window.
2 In the displayed Table Controller window, choose Select All Files from
the Select menu.
3 In the Table Controller window, select the Export button. A Message
window is displayed showing the progress of the Export function for each
file.
4 When the Message window indicates that all files are exported, click the
OK button. Each file, when correctly exported, is indicated by a check mark
in the File column.
File validation procedure
After the files are created, and/or edited using the GTE, the files must be validated and then
inserted back into the Informix database.
Validation can be carried out separately on each file or the whole file set can be validated in
one process. Validation comprises the following procedures:
• A check for missing fields
• A check for superfluous fields
• A check for illegal values
To validate all files, perform the following procedure.
Procedure 3-33 Validate all files
1 Open an Xterm window and enter the following command:
DGAdmin DGLog
The Validation Log window opens and displays errors and warnings about
the progress of the validation and insert process. This information is also
available by viewing the log file from the Administration menu. Refer to
2 In the Table Controller window, choose Select All Files from the Select
menu.
3 Click the Validate button. A Message window showing the progress of the
Validate function for each file is displayed.
4 When the Message window indicates that all files are validated, click OK.
Each correctly validated file is indicated by a check mark in the File column.
68P02900W22-S 3-85
Jul 2008
MCDF table editing Chapter 3: Operating DataGen
File insertion procedure
After successful validation, the files must be inserted back into the Informix database. To insert
the files, perform the following procedure.
Procedure 3-34 Insert validated files into the Informix database
1 Open an Xterm window and enter the following command:
DGAdmin DGLog
The Validation Log window displays the errors and warnings about the
progress of the validation and insert process. This information is also
available by viewing the log file from the Administration menu. Refer to
2 In the Table Controller window, choose Select All Files from the Select
menu.
3 Click the Insert button. A Message window showing the progress of the
Insert function for each file is displayed.
4 When the Message window indicates that all files have been inserted,
click OK. Each correctly inserted file is indicated by a check mark in the
File column.
NOTE
As each file is validated and inserted into the database, a report
is generated, the results of which can be viewed by selecting the
file and clicking Report.
Instead of carrying out separate Validate and Insert tasks on the selected files, users can
select the files and carry out the Insert task ONLY which automatically validates the files
before insertion.
However, creating a file or making a large number of edits to an old file increases the likelihood
of errors, particularly as many of the input files are interdependent. It is recommended that, in
such cases, separate validate and insert operations are performed.
The interdependency of the input files also means that a file can only be validated if all its
dependent files are validated and inserted or are currently selected.
MCDF table editing
After the MCDF files are created from the Informix database, they can be edited using the
Generic Table Editor (GTE). The following procedure uses a Generics table, which requires a
change to the Generics parameter ber_loss_daily, as an example of table editing.
3-86 68P02900W22-S
Jul 2008
System Information: DataGen MCDF table editing
Table editing procedure - example
To edit an MCDF table, perform the following procedure.
Procedure 3-35 Edit an MCDF table using the Generic Table Editor
1 In the Table Controller window, select the Generics Radio button, then select
the File button.
2 A Generics table (gene.mcd) is displayed as in Figure 3-32.
Figure 3-32 Generics table
3 Highlight the data field containing the value for ber_loss_daily.
Continued
68P02900W22-S 3-87
Jul 2008
File status icons Chapter 3: Operating DataGen
Procedure 3-35 Edit an MCDF table using the Generic Table Editor (Continued)
4 Enter the value 4, then press CR to save the entry.
5 From the Generics Table File menu, select Store in DDS, then select Exit.
The Generics Table window closes and the relevant Validate and Insert
columns in the Table Controller contain an asterisk (*).
6 Select the Generics file select button. A Report window displays the message
that the ber_loss_daily value was successfully updated in the database.
NOTE
• If an invalid entry is made to the MCDF tables, a report file is generated

informing the user of an error. In certain cases, a warning icon is displayed
in the Validate column and no further editing is allowed until the error is
corrected. Some input files, however, do not display a warning icon (for example,
out of range values). It is important therefore to read the Report file every time
a parameter is edited and inserted otherwise, the error may not be apparent to
the user until the file has been through the Binary Compiler process.
• If the validation log (DGLog) window is open, it is possible to monitor and
identify the problems as they occur.
File status icons
The File Status icons on the Table Controller window are defined as follows (refer to Table 3-6):
Table 3-6 File status icons
Validate Insert Export Report

Symbol File Meaning
Meaning Meaning Meaning Meaning
File does not File has File has N/A Report file
exist in DDS. not been not been does not
validated. inserted. exist.
File is being N/A N/A N/A N/A

edited.
File is File has been File has N/A Report file

available for validated been has been
editing. successfully. inserted read.
successfully.
N/A File is being File is being N/A N/A
edited. edited.
Continued
3-88 68P02900W22-S
Jul 2008
System Information: DataGen File status icons
Table 3-6 File status icons (Continued)

Validate Insert Export Report
Symbol File Meaning
Meaning Meaning Meaning Meaning
File is Error Error N/A N/A
unreadable. occurred occurred
during during
validation. insert.
File cannot N/A N/A N/A N/A

be written
to, that is,
Locked.
N/A Current Insert N/A Report file

file is operation is unread.
incomplete. needs more
Validation information
needs more
information.
N/A Warnings Warnings N/A N/A
produced produced
in report in report
file during file during
validation. insertion.
68P02900W22-S 3-89
Jul 2008
Using the Generic Table Editor (GTE) Chapter 3: Operating DataGen
Using the Generic Table Editor (GTE)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to the Generic Table Editor
The Generic Table Editor (GTE) allows the user to display and edit the MCDF input files.
An MCDF input file has three selections on its menu bar:

• File
• Edit
• Format
The File menu
Table 3-7 describes the File menu options.
Table 3-7 File menu options
Select To
New Create a new (empty) MCDF input file.
Open Open an existing file.
Store in DDS Save the current state of an edited file in the DataGen Directory
Structure (DDS).
Save As Save a file with a different, or new filename, using the Save As option
in the File menu.
Print Setup Set up printing parameters.
Print Print the current file to one of the available printers.
Restart Restore the file to its last saved version, before any modifications
were made.
Exit Close the input file.
3-90 68P02900W22-S
Jul 2008
System Information: DataGen The File menu
New option
To create an (empty) MCDF input file, select New from File menu in the MCDF input (.mcd)
file. A New message window is displayed as in Figure 3-33.
Figure 3-33 New MCDF input file message
Click OK to create an (empty) MCDF input file.
Open option
To open an MCDF input file, select the Open option from the File menu in the MCDF input file
window. The Open File window is displayed as shown in Figure 3-34.
Figure 3-34 MCDF Input File - Open option
68P02900W22-S 3-91
Jul 2008
The File menu Chapter 3: Operating DataGen
This window has the following functionality:

• Filter
This data field enables the user to specify a directory path, and the name of the file which
is to be opened. The wildcard character * can be used to display ALL files in a directory.
• Directories
This scrolled list box displays directories and subdirectories which can be selected by
double-clicking an entry, or highlighting an entry and pressing the Filter button.
• Files
This scrolled list box displays the files contained in the selected directory. To open a file,
highlight the file using the mouse button and press the OK button.
• Selection
This data field shows the selected path and filename.
• Buttons
The following buttons are available:

OK - Initiates the File à Open function.
Filter - Initiates the search process on the path displayed in the filter box, and display
the results in the Directories and Files list boxes.
Cancel - Cancels an operation.
Help - Help is not available in this version of DataGen. The following message is
displayed: For DataGen Help please refer to the DataGen manual supplied,
Store in DDS option
After editing an MCDF Input file, perform the following procedure to store the file in the
DataGen Directory Structure (DDS).
Procedure 3-36 Store MCDF Input file in the DataGen Directory Structure
1 Select the Store in DDS option from the File menu in the edited MCDF
Input file menu bar.
2 Select Exit to close the edited file.
3 In the Table Controller window, select the Insert button. A Message
window is displayed showing the results of the Insert process. The file is
validated automatically.
4 If the Insert was successful, click the OK button in the Message window.
A check mark is placed in the Insert column of the file type indicating
successful insertion.
3-92 68P02900W22-S
Jul 2008
Save As option
Figure 3-35 shows the Save To File window which is displayed when the Save As option is
selected in the MCDF Input File File menu. Using this option, existing files can be saved with a
different filename, or a new file can be saved with a new filename.
Figure 3-35 Save To File window
Print Setup option
Figure 3-36 shows the Printer Setup window which is displayed when Print Setup is selected
from the File menu.
NOTE
The default page size is A4.
68P02900W22-S 3-93
Jul 2008
The File menu Chapter 3: Operating DataGen
Figure 3-36 Print Setup window
The Printer Setup window enables the user to specify printing parameters using:
• Two menu buttons for page size and orientation
• Four data fields for print area parameters
• Four action buttons
The various printing parameters are defined in Table 3-8, Table 3-9, and Table 3-10.
Table 3-8 Printer setup - menu buttons
Select To
Page Size Display a drop down menu of available page sizes for printing. Select A4
page size from the menu to enter the default values into the data fields.
Orientation Display a drop down menu of page layout types.
Table 3-9 Printer setup - data fields
Select To
Resolution Display the default DPI for printing.
Height Display the default page width for printing.
Width Display the default page height for printing.
Scaling factor Display the default scaling factor, normally zero.
3-94 68P02900W22-S
Jul 2008
Table 3-10 Printer setup - action buttons
Select To
OK Confirm the displayed parameters and close the Printer Setup
window.
Apply Accept the displayed parameters.
Cancel Cancel the current operation.
Help Display the following Help message:

supplied, OLM On-Line help is available through the
OLM GUI.
Print option
The Print Table window is displayed when the Print option is selected from the File menu.
Figure 3-37 Print Table window
NOTE
The print command selects the appropriate command for postscript or text only
printer as in Figure 3-37. If no printer is set up, then none is displayed in the printer
list.
68P02900W22-S 3-95
Jul 2008
The Edit menu Chapter 3: Operating DataGen
The Print Table window allows the user to specify the printer output parameters. This window
has:
• Two option buttons allowing the following format selection:
Postscript - generates the printer output as a postscript file.
Text - generates the printer output as ASCII text.
• The Printers list box which displays the available printer names.
NOTE
For more information about installing printers, refer to Configuring the
printer in Software Release Notes: DataGen (68P02900W76).
• The Printer command data field allows the user to enter a print command for a printer
which is not included in the Printers list box as follows:
Print - sends the MCDF input file to the printer selected in the Printers list.
Cancel - cancels the current operation.
Help - not available in this version of DataGen. The following message is

displayed:
For DataGen Help please refer to the DataGen manual supplied,
The Edit menu
The Edit menu enables the user to perform general editing operations on the data contained in
the cells of an MCDF file.
Table 3-11 describes the Edit menu options.
NOTE
Before copying and pasting the cells, create the required number of columns and/or
rows required to contain the data.
3-96 68P02900W22-S
Jul 2008
System Information: DataGen Fill Cells window
Table 3-11 Edit menu options
Select To
Cut Cut the contents of the currently selected cells with the data being retained
in a buffer. However, subsequent cut operations overwrite the contents of the
buffer. The cut cells are left empty.
Copy Copy the contents of the currently selected cells into a buffer.
Paste Copy the contents of the buffer into the currently selected cells.
Clear Delete the contents of the currently selected cells. The data is NOT saved
into the buffer.
Fill Rapidly fill a range of cells with numerical data. For details, refer to the next
section Fill Cells window.
Insert Insert a new (empty) element (row/column) into the table, either before or
after the currently selected cell or row.
Delete Delete the contents of an entire row or column, when the appropriate
row/column has been selected.
Undo Undo the last operation: Cut, Copy, Paste, Clear, Fill, Insert, Delete, Undo,
or Replace.
NOTE
There is a single buffer for Cut or Copy operations. Only the last Cut or Copy
operation is retained in the buffer.
Fill Cells window
Figure 3-38 show the Fill Cells window which is displayed when the Fill option is selected
from the Edit menu in the MCDF input file.
Figure 3-38 Fill Cells window
68P02900W22-S 3-97
Jul 2008
Fill Cells window Chapter 3: Operating DataGen
The Fill Cells window allows the user to change the contents of multiple cells using:
• Four data fields for the cell parameters (refer to Table 3-12).
• Four option buttons in a Calculate area (refer to Table 3-13).
• Three action buttons (refer to Table 3-14).
Table 3-12 Fill cells - data fields
Select To
Start Specify the number of the starting cell.
Increment Specify the cell number increment (normally 1).
End Specify the end cell number.
Number of Cells Specify the number of cells to be filled.
Table 3-13 Fill cells - options
Clear To
Start Allow its associated data field to be modified.
Increment Allow its associated data field to be modified.
End Allow its associated data field to be modified.
Cell count Allow its associated data field to be modified.
Table 3-14 Fill cells - action buttons
Select To
OK Confirm the displayed parameters and close the Fill Cells window.
Cancel Cancel the current operation.
Help Display the following message:

OLM GUI.
Procedure for filling cells
To modify an MCDF input file using the Fill Cells window, perform the following procedure.
Procedure 3-37 Fill cells
1 Highlight the first cell to be filled.
Continued
3-98 68P02900W22-S
Jul 2008
System Information: DataGen Format menu
Procedure 3-37 Fill cells (Continued)

2 Enter data into the first cell.
3 Move the cursor off the cell.
4 Highlight the first and succeeding cells to be filled. The data fields in the
Fill Cells window now contain values relating to the highlighted cells, For
example: Start and End.
5 Select Fill from the Edit menu.
6 The value from the first highlighted cell is copied into all the highlighted
cells.
7 Repeat step 1 to step 6 for the remaining rows or columns to be filled.
Format menu
The Format menu enables the user to perform general search and replace operations.
Table 3-15 shows the definitions of the Format menu options.
Table 3-15 Format menu options
Select To
Find Search for the occurrence of a specific character string.
Goto Go to a specific cell.
Replace Search for a specific character string and replace with another
string.
Sort Sort certain MCDF tables.
Unlock Edit locked MCDF files.
68P02900W22-S 3-99
Jul 2008
Format menu Chapter 3: Operating DataGen
Find option
Enter the string to search for and select the appropriate search criteria (Exact match or Case
sensitive) for the search. Figure 3-39 shows the Find window.
Figure 3-39 Find window
The Find window has:

• One data field
• Two Enable buttons
• Four Action buttons
The Search For data field allows the user to specify the character string to find.
Table 3-16 and Table 3-17 describe the Enable buttons and the Action buttons.
Table 3-16 Find window - enable buttons
Select To
Exact match Specify that the string to be searched must be an exact match of the
string entered in the Search For data field.
Case Sensitive Specify that the search must be in the same case as the string
entered in the Search For data field.
Table 3-17 Action button definitions
Select To
Find First Find the first occurrence of the search string.
Find Next Find the next occurrence of the search string.
Cancel Cancel the operation.
Continued
3-100 68P02900W22-S
Jul 2008
Table 3-17 Action button definitions (Continued)

Select To

OLM GUI.
Goto option
Figure 3-40 shows the Goto Cell window which enables the user to move to a specific cell by
entering the appropriate column and row numbers. If the column or row selected lies outside of
the table, the last cell in that row or column is highlighted.
Figure 3-40 Goto Cell window
The Goto Cell window has:

• Two data fields (refer to Table 3-18).
• Three action buttons (refer to Table 3-19).
Table 3-18 Goto Cell - data fields
Field Enter
Column Column number
Row Row number
Table 3-19 Goto Cell - action buttons
Select To
OK Confirm the displayed parameters and close the Goto Cell window.
Continued
68P02900W22-S 3-101
Jul 2008
Format menu Chapter 3: Operating DataGen
Table 3-19 Goto Cell - action buttons (Continued)

Select To
Cancel Cancel the operation and close the Fill Cell window.

OLM GUI.
Replace option
This option enables the user to perform a search and replace operation on the contents of an
MCDF file using the Replace window shown in Figure 3-41.
Figure 3-41 Replace window
The Replace window has:

• Two data fields (refer to Table 3-20)
• Two enable buttons (refer to Table 3-21)
• Three option buttons (refer to Table 3-22)
• Three action buttons (refer to Table 3-23)
3-102 68P02900W22-S
Jul 2008
Table 3-20 Replace window - data fields
Field Enter
Search for The specific character string for
searching.
Replace with The replacement character string.
Table 3-21 Replace window - enable buttons
Select To
Exact match Specify that the string to be searched must be an exact match of the string
entered in the Search For data field.
Case sensitive Specify that the search must be in the same case as the string entered in
the Search For data field.
Table 3-22 Replace window - option buttons
Select To
Replace Single Specify that only the first occurrence of the search string is to be replaced.
Replace All Specify that all occurrences of the search string should be replaced.
Replace Query Display a query message for each search and replace action.
Table 3-23 Replace window - actions
Select To
OK Confirm the displayed parameters and close the Replace window.
Cancel Cancel the operation and close the Replace window.
For DataGen Help please refer to the DataGen manual supplied,

Sort option
The contents of some tables can be sorted. If a table cannot be sorted, this option is grayed out.
Unlock option
Some of the BSS area definition files contain locked data which must not be altered, although
the DataGen GUI provides the functionality to alter the data.
The Unlock button enables the user to unlock a table and change the locked values. A warning
is displayed to this effect.
68P02900W22-S 3-103
Jul 2008
MCDF key equivalents Chapter 3: Operating DataGen
MCDF key equivalents
Table 3-24 describes the key equivalents that are available when working on MCDF tables.
Table 3-24 Hot keys for MCDF
Action Hot keys

load Ctrl-O
save Ctrl-S
saveAs Ctrl-A
print Ctrl-P
restart Ctrl-R
quit Ctrl-E
cut Ctrl-X
copy Ctrl-C
paste Ctrl-V
clear Ctrl-B
fill Ctrl-F
insert Before Ctrl-J
insert After Ctrl-I
delete Ctrl-D
undo Ctrl-U
3-104 68P02900W22-S
Jul 2008
System Information: DataGen Using the Topology Viewer
Using the Topology Viewer

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to the Topology Viewer
NOTE
Selecting the Topology option causes the DataGen GUI to core, if the GMS license
(KEYS) is not purchased.
The Topology Viewer allows the user to display a graphical representation of a BSS Area
showing a BSC and its associated BTSs. Two topologies can be displayed at the same time
for comparison purposes.
The viewer has four data fields which show the Base Site System Description information
and a menu bar with Cage, MMI, Path File and Increase/Decrease magnification options.
The File menu has Exit option only.
Invoking the Topology Viewer
To display the Topology Viewer (as in Figure 3-42), either select Topology from the Services
menu or click the Topology icon on the Services window.
68P02900W22-S 3-105
Jul 2008
Using the Topology Viewer Chapter 3: Operating DataGen
Figure 3-42 Topology Viewer
Using the Topology Viewer
Use the buttons on the menu bar shown in Figure 3-43 to access the topology viewer options.
3-106 68P02900W22-S
Jul 2008
System Information: DataGen Cage hardware configuration button
Figure 3-43 Topology Viewer menu bar
The topology viewer options are described in greater detail in the following sections.
Cage hardware configuration button
The Cage selection on the menu bar and the Cage Number window allow the user to display
cage configurations for a BSC and BTSs displayed in the Topology Viewer window.
To display a cage configuration, perform the following procedure.
Procedure 3-38 Display a cage configuration
1 Click the Cage Hardware Configuration button on the Topology Viewer

window. Refer to Figure 3-43.
2 Click a BSC or BTS symbol (only green and yellow symbols are valid).
3 In the displayed Cage Number window, select the cage number. Refer
to Figure 3-44.
Figure 3-44 The Cage Number window
4 A Cage Description window is displayed as shown in Figure 3-45.
68P02900W22-S 3-107
Jul 2008
Cage hardware configuration button Chapter 3: Operating DataGen
The Cage Description window
The main section of the window contains a graphical representation of the layout of the
hardware within the selected cage. If necessary, this main section can be cut and printed,
enabling users to produce a hard copy showing cabinet configurations.
The Cage Description window has six data fields which show the Cage Description information.
The buttons on the left-hand side of the window are not enabled. The Message window shown
at the bottom is currently unused.
Select the Exit option from the File menu to close the window.
Figure 3-45 The Cage Description window
3-108 68P02900W22-S
Jul 2008
System Information: DataGen The MMI button
The MMI button
The MMI button enables the user to regenerate an MMI script for the current site. This
button performs exactly the same function as the MMI button located on the Service window,
described in the section The Service window on page 3-56.
Path File button
This button uses a text editor to display the path or connectivity information. For example:
PATH 0 = Site: 0 [MSI 2,0] connected to Site: 7 [MSI 3,0].
A copy of the file is stored in the users home directory:

/home/<username>/PathFile
If the file exists, a backup of the original file is made.
Increase magnification button
This button increases the magnification factor applied to the Topology Viewer to allow greater
definition.
Decrease magnification button
This button decreases the magnification factor applied to the Topology Viewer.
68P02900W22-S 3-109
Jul 2008
Generating a hardware report Chapter 3: Operating DataGen
Generating a hardware report

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of hardware reports
Operators can generate a hardware report containing a list of all the devices names, function
names, slot numbers, and Id devices within each cage per site. A default text editor is used
to open the report.
Procedure for generating a hardware report
To generate a hardware report, perform the following procedure.
Procedure 3-39 Generate a hardware report
1 Open the Service window (refer to Opening a BSS area on page 3-39 for
details).
2 From the Service window, select Generate Hardware Report from the
Services menu.
NOTE
The Generate Hardware Report option is available only if the BSS
area contains data.
The following message is displayed in a Status window:
Generating Hardware Report for Base Station System
When complete, a Confirmation window is displayed.

3 Click OK to continue.
Continued
3-110 68P02900W22-S
Jul 2008
System Information: DataGen Procedure for generating a hardware report
Procedure 3-39 Generate a hardware report (Continued)

4 To view the report, select Hardware Report from the Edit menu. The default
text editor displays the report as in the example shown in Figure 3-46. Refer
to Administration tasks on page 3-12 for details on how to define a default editor.
Figure 3-46 Viewing a hardware report
5 Close the report by using the appropriate command for the text editor in use.
68P02900W22-S 3-111
Jul 2008
Converting a database script file to a CM database object file Chapter 3: Operating DataGen
Converting a database script file to a CM database

object file
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of conversion
Conversion of a database script file to a database object file can be performed either on the
DataGen platform or in the BSS.
Producing a CM database object using SYSGEN mode
This process is normally carried out on a Test BSS which is not connected to the live network.
The Test BSS must first be entered into SYSGEN Mode. Once this is done, the Database Script
File can be downloaded to the BSS through a TTY interface connected to the Master GPROC.
The BSC then processes the information sent to it and produces a CM Database Object from this
information. The object file has the extension .002.
The CM database object must then be uploaded to the OMC so that it is available for
downloading to the live network when it is required.
Producing a CM database object using the DataGen binary

object compiler
DataGen uses the Binary Object Compiler to convert a script file into a CM database object.
The CM database object is automatically compressed. As a secondary function of compiling the
object, the compiler also validates the database.
NOTE
As a requirement for running the binary object compiler, install the Options Object
into DataGen, during the installation phase. The object compiler reads the Options
Object to ascertain what additional functionality the network supports. Refer to
Installing the options object in Software Release Notes: DataGen (68P02900W76)
for details.
The binary object compiler is executed either from the Services menu, or by clicking Run
Compiler shown in Figure 3-47.
3-112 68P02900W22-S
Jul 2008
System Information: DataGen Producing a CM database object using the DataGen binary object compiler
Figure 3-47 Binary Object Compiler window
The Compiler does a validation check on all parameters. If any errors are detected during the
Compile process, a message is generated in the main window. The errors should be corrected
using the Table Controller. Editing of the script using the MMI Script Generate command does
not update the Informix database, as it is in an output file directory.
The Binary Object Compiler window has two data fields which display the BSS Area informa-
tion and the Status of the compiler. There are two action buttons: Run Compiler and Exit.
The File menu has three selections:
• Run Compiler
• Remove Lock File
• Exit
68P02900W22-S 3-113
Jul 2008
Producing a CM database object using the DataGen binary object compiler Chapter 3: Operating DataGen
NOTE
All binary object files (.002) are compressed. Refer to Command Line tools,
Compress /uncompress binary object files for details on how to uncompress files.
To activate the compiler, click Run Compiler or select the Compile option from the File menu.
3-114 68P02900W22-S
Jul 2008
System Information: DataGen Exporting object files to the OMC
Exporting object files to the OMC

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of exporting object files
After a binary object is generated, it can be downloaded to the OMC. The three methods for
exporting object files are:
• Export multiple binary object files to the OMC
• Export a single binary object file to the OMC
• Export binary object files from the OLM to the OMC
NOTE
For more information about the requirements for this type of operation,
refer to DataGen-OMC Integration in Software Release Notes: DataGen
(68P02900W76).
Exporting multiple binary object files
To export multiple binary object files to the OMC, perform the following procedure.
Procedure 3-40 Export multiple binary object files
1 Ensure that the export path is set to the desired directory. For example,
/usr/omc/DataGen/dg/<Country>/<BSS Area Name>/<export>
Refer to Administration tasks on page 3-12, customizing parameters for
details on how to define a path to an export directory.
2 From the Service window (refer to Figure 3-21), select the Export option
from the File menu.
3 Click OK in the displayed Message window.
4 At the OMC, ensure that a sub directory exists in the database
directory with the same name as the BSS Area being exported from
DataGen. If a sub directory does not exist, create one. For example:
/usr/omc/ne_data/dbroot/BSS/BSSspecific/<BSS Area Name>
Continued
68P02900W22-S 3-115
Jul 2008
Exporting a single binary object file Chapter 3: Operating DataGen
Procedure 3-40 Export multiple binary object files (Continued)

5 At the OMC, invoke Utilities à OMC Database Utility, then select the
Load Database option. A load_db utility is invoked which opens a new
Xterm window and presents four load source options.
6 Select option 4 (User definable source and location) and input the requested
information.
7 After the download, check that the database object is located in the database
directory under the specified BSS Area name. For example:
/usr/omc/ne_data/dbroot/databases/<BSS Area Name>/<db_load
name>
NOTE
The setenv COUNTRY and COUNTRY_CODE variables are
to be set at the OMC, and must match the values set in the
country administrator (Country) table, in order for the available
configurations to be displayed.
Exporting a single binary object file
To export one object file that has been created using the DataGen GUI to the OMC, perform the
following procedure.
Procedure 3-41 Export a single binary object file
1 Verify that the binary object file is in the correct directory. For example:
/usr/omc/DG/dg/<Country>/<BSS Area Name>/conf<n>/002
Where the configuration number replaces n.
2 At the OMC, ensure that a sub directory exists in the database directory with
the same name as the BSS Area which is being exported from DataGen.
If a sub directory does not exist, create one. For example:
/usr/omc/ne_data/dbroot/BSS/BSSspecific/<BSS Area Name>

3 At the OMC, invoke Utilities à OMC Database Utility,
then select the Load Database option.
A load_db utility is invoked which opens a new Xterm window and presents
four load source options.
4 Select option 2 (DataGen), then input the requested information.
Continued
3-116 68P02900W22-S
Jul 2008
System Information: DataGen Exporting OLM binary object files to the OMC
Procedure 3-41 Export a single binary object file (Continued)

directory under the specified BSS Area name.
NOTE
The setenv COUNTRY and COUNTRY_CODE variables are
to be set at the OMC, and must match the values set in the
country administrator (Country) table, in order for the available
configurations to be displayed.
Exporting OLM binary object files to the OMC
To export multiple binary object files to the OMC from the Offline MIB, perform the following
procedure.
Procedure 3-42 Export multiple binary object files
1 At the OMC, invoke Utilities à OMC Database Utility.

2 Select the Load Database option.
A load_db utility is invoked which opens a new Xterm window and presents
four load source options.
3 Select option 3 (Off-Line MIB) and input the requested information.
directory under the specified BSS Area name. For example:
/usr/omc/ne_data/dbroot/databases/<BSS Area Name>/<db_load
name>
68P02900W22-S 3-117
Jul 2008
Difference Reporter Chapter 3: Operating DataGen
Difference Reporter
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to the Difference Reporter
Difference reports between sites and site elements for BSS areas can be generated using the
DIFF option from the DataGen main menu (refer to Figure 1-1).
Two different BSS Areas are chosen and a comparison of both the areas is started. A viewable
report is generated in which the sites common to both the areas are listed. Differences between
the two BSS Areas for each site are also listed. In addition, the report indicates the areas where
no differences between the sites are found.
The Difference Reporter window
Select DIFF from the DataGen main menu to display a Difference Reporter window as shown
in Figure 3-48.
Figure 3-48 Difference Reporter window
The Difference Reporter window displays the details of two BSS areas which can be selected
for comparison using the BSS Area Details window.
3-118 68P02900W22-S
Jul 2008
System Information: DataGen Select BSS Area Details window
Using the Difference Reporter window
The Difference Reporter window has two sets of four user input areas labeled as:
• Country
• BSS Name
• Version
• Config
The action buttons on the Difference Reporter window are used as follows:
Use To
Set Display a BSS Area Details window for Area 1 or Area 2
comparison (left or right-hand option).
Compare Begin the comparison between Area 1 and Area 2.
View View the Report File.
Exit Close and exit the DIFF function.
Select BSS Area Details window
The Select BSS Area Details window allows the user to select two BSS areas for comparison.
To open the window, select the left-hand or right-hand Set button for the relevant BSS area in
the Difference Reporter window. The Select BSS Area Details window is then displayed.
Refer to Figure 3-49.
Figure 3-49 Select BSS Area Details window
When the window is displayed for the first time, the BSS Name, Software Version, and Config
Version list boxes are blank. Only the Country Name list box contains a list of countries.
68P02900W22-S 3-119
Jul 2008
Select BSS Area Details window Chapter 3: Operating DataGen
Using the Select BSS Area Details window
The Select BSS Area Details window has four user selectable areas:
• Country Name
When Country Name is selected, a list of BSS names in the BSS area list is displayed.
• BSS Name
When a BSS Name is selected, the Software Versions in the next list box are displayed.
• Software Version
When a Software Version is selected, the configuration numbers in the last list box are
displayed.
• Config Version
Select the configuration number. The scroll bar can be used to step through the list of
configuration versions for a specified BSS area.
The action buttons on the Select BSS Area Details window are used as follows:
Use To
Cancel Cancel the operation and close the window.
Done Enter the selected details into the Difference
Reporter window for BSS Area 1 and Area 2.
3-120 68P02900W22-S
Jul 2008
System Information: DataGen Difference Reporter Information window
Difference Reporter Information window
The Information window is displayed after the user presses the Compare button in the
Difference Reporter main window to begin the comparison. The Information window displays
the progress of the Difference Reporter as in Figure 3-50.
Figure 3-50 Difference Reporter - Information window
Using the Information window
The Difference Reporter Information window has a text area which displays the progress of
the Difference Reporter and two action buttons which are used as follows:
Use To
View Report Display an Information window.
Close Close the Information window.
68P02900W22-S 3-121
Jul 2008
Difference Reporter Report window Chapter 3: Operating DataGen
Difference Reporter Report window
The results of the Difference Reporter process are displayed in a Report window as shown
in Figure 3-51.
Figure 3-51 Difference Reporter - Report window
Using the Report window
The Report window has a text box which displays Difference Report output. As reports can
be large, a horizontal scroll bar and a vertical scroll bar can be used to view different parts of
a report.
3-122 68P02900W22-S
Jul 2008
System Information: DataGen Upgrader
Upgrader
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of the Upgrade function
The Upgrade function allows the user to upgrade an earlier version of DataGen to a more recent
software release. This option can be invoked from the DataGen main menu by selecting the
UPG option (refer to Figure 1-1).
The existing BSS area is copied to a new BSS area. The MMI script changes and modifications
to parameter values are applied to this new area.
The following upgrade paths are supported:

• 1.7.6.0 to 1.8.0.0
• 1.7.6.0 to 1.9.0.0
• 1.8.0.0 to 1.9.0.0
Refer to Software Release Notes: DataGen (68P02900W76) for more information about the
upgrades supported.
Upgrade BSS Area window
When UPG is selected from the DataGen main menu, the Upgrade BSS Area window is
displayed as in Figure 3-52. This allows the user to select the BSS Area characteristics to be
upgraded. The Target Version is entered automatically by DataGen.
Figure 3-52 Upgrade BSS Area window
68P02900W22-S 3-123
Jul 2008
Upgrade BSS Area window Chapter 3: Operating DataGen
NOTE
To change parameters in the BSS area before the upgrade, modify the MCDF files.
Refer to Using the Generic Table Editor (GTE) on page 3-90 for details. Do not modify
the BSS area by editing and compiling the MMI script, as any changes made will be
lost after the upgrade.
The Upgrade BSS Area window has:

• Six list boxes (refer to Table 3-25).
• Two action buttons (refer to Table 3-26).
Table 3-25 Upgrader - list boxes
Select To
Country Name Display a list of country names.
BSS Area Display a list of available BSS Areas.
Software Version Display a list software versions.
Configuration Display a list of Configuration numbers for the software versions.
number
Target Version Display the available target versions automatically.
Target Config. Display a list of target Configuration numbers.
Table 3-26 Upgrader - action buttons
Select To
Upgrade Start the upgrade process and display a Status window.
Close Cancels the operation and close the Upgrade BSS Area window.
Area Comment field
By default, the area comment field contains the following information:
Upgraded from <BSS Area><Configuration NO>
Where Is
BSS area Name of the original BSS area.
Configuration No Configuration number of the original BSS area.
3-124 68P02900W22-S
Jul 2008
System Information: DataGen Upgrading a BSS Area
Upgrading a BSS Area
To upgrade a BSS Area, perform the following procedure.
Procedure 3-43 Upgrade a BSS Area
1 Select the UPG from the DataGen Main menu (refer to Figure 1-1). This
displays the Upgrade BSS Area window (refer to Figure 3-52).
2 Select a Country Name in the list box to display a list of BSS areas.
3 Select a BSS Area to display a list of Software Versions.
4 Select the required software version which is to be upgraded: a list of
associated configuration numbers is displayed.
5 Select a Configuration No.
6 Select a Target Version which is displayed in the list box automatically. To
obtain a target configuration number automatically, do not select a number from
the Target Config. list. DataGen then assigns the next available configuration
number.
NOTE
To overwrite an existing configuration, select the number from the
Target Config. list.
7 If the information displayed in the list box data fields is correct, click Upgrade.
If another user has locked the BSS area, an Information window is displayed
as shown in Figure 3-53. If this message is not displayed, proceed to step 9.
Figure 3-53 Locked Information window
Continued
68P02900W22-S 3-125
Jul 2008
Upgrading a BSS Area Chapter 3: Operating DataGen
Procedure 3-43 Upgrade a BSS Area (Continued)

8 Click OK to override the lock or Cancel to return to the Upgrade BSS Area
window.
NOTE
Information on the user holding the lock can be found in the
DataGen.log file. Refer to Administration tasks on page 3-12 for
details.
A Status window is displayed as shown in Figure 3-54.
Figure 3-54 Successful Upgrade Status window
Continued
3-126 68P02900W22-S
Jul 2008
System Information: DataGen Upgrade multiple BSS areas
Procedure 3-43 Upgrade a BSS Area (Continued)

If the upgrade is successful, the following message is
displayed in the Status window:
REPORT :- Upgrade completed successfully.

REPORT :- Starting gcmd for <Country:BSS_Area:Configuration_No>.
REPORT :- Gcmd completed without error.
NOTE
Wait until Gcmd has completed before closing the window.
9 Click Close to return to the Upgrade BSS Area window when Gcmd is
completed. If the upgrade is unsuccessful, the Status window displays the
following information:
REPORT :- Upgrade completed.

REPORT :- Please modify the area as detailed in the warnings.
REPORT :- Starting gcmd for <Country:BSS_Area:Configuration_No>
Gcmd completed without error
Refer to the section Resolving upgrade problems on page 3-127 for details.
Upgrade multiple BSS areas
It is not necessary to wait for the upgrade to be completed before starting to upgrade another
BSS area.
To upgrade a second BSS Area, select the Upgrade BSS Area window. Refer to Procedure 3-43
and carry out step 3 to step 9.
Resolving upgrade problems
During the upgrade process, problems may occur in the BSS area that prevent the successful
upgrading. The Status window identifies any problems occurred.
Depending on the nature of the problems, modifications can be done in one of two ways:
• Modify MCDF files
• Modify MMI scripts
68P02900W22-S 3-127
Jul 2008
Resolving upgrade problems Chapter 3: Operating DataGen
To resolve the upgrade problems, perform the following procedure.
Procedure 3-44 Resolve upgrade problems
1 If the upgrade is unsuccessful, for example, if changes are required in a

script, the following messages are displayed in the Status window:
REPORT :- Upgrade completed

REPORT :- Please modify the area as detailed in the warnings.
REPORT :- Starting gcmd for <Country:BSS_Area:Configuration_No>.
REPORT :- Gcmd completed without error.
2 Click Close in the Status window to return to the Upgrade BSS Area
window and Cancel to return to the DataGen main menu (refer to
Figure 1-1).
NOTE
Wait until Gcmd has completed before closing the window.
Modify MCDF files
Use the following procedure to modify the MCDF files.
Procedure 3-45 Modify MCDF files to resolve upgrade problems
1 Open the target BSS area window from the DataGen main menu. Refer
to Opening a BSS area on page 3-39 for details.
2 From the Service window, use the Table Controller to modify the MCDF
files and insert them back into the Informix database. Refer to Using the
Table Controller on page 3-79 for more details.
3 Generate an MMI script by clicking the MMI button or by selecting
Generate Script from the Services menu. Refer to Generating a database
script file on page 3-71 for more details.
4 Compile the created script file by selecting the Compile button or selecting
Object Compiler from the Services menu. Refer to Converting a database
script file to a CM database object file on page 3-112 for more details.
Modify MMI script
To modify the MMI script, perform the following procedure.
Procedure 3-46 Modify MMI script to resolve upgrade problems

Continued
3-128 68P02900W22-S
Jul 2008
System Information: DataGen Overview of DARBC and Enhanced XBL
1 Open the Target BSS Area window from the DataGen main menu. Refer to
Opening a BSS area on page 3-39 for more details.
2 View the MMI script file with a text editor and make the necessary changes.
Refer to Generating a database script file on page 3-71 for more details.
3 From the Services menu, compile the script file to generate a new BSS
binary object files. Refer to Converting a database script file to a CM
database object file on page 3-112 for more details.
4 Export the binary object file from the DataGen Directory structure. To
create an export directory, refer to Administration tasks on page 3-12 for
more details. From the Service window, select File à Export Object.
5 From the Service window, select File à Exit.
6 Create a BSS area and overwrite the existing configuration number. Refer to
Creating a BSS area on page 3-35 for more details.
7 Import the exported binary object file from the Service window. Refer to the
section Import object in The Service window on page 3-56 for more details.
8 Revgen the binary object from the Service window to update the BSS area
in DataGen. Refer to Activating Revgen in Converting a CM database
object file to a script file on page 3-66 for more details.
Overview of DARBC and Enhanced XBL
The Dynamic Allocation of RXCDR to BSC circuits (DARBC) alters the role of the terrestrial
circuit portion of the A-interface between a BSC and RXCDR (known as Ater channels), so
that the Ater channels between the Remote Transcoder (RXCDR) and BSC are allocated as
the channels are needed, rather than statically assigning the channels to a specific Circuit
Identifier Code (CIC).
The term XBL, refers to a Base Site Controller (BSC) transcoder (RXCDR) link. The new
Enhanced XBL (EXBL) feature provides robust communication between the BSC and the
RXCDR. The basis of the EXBL feature is to provide a generic messaging system between the
BSC and the RXCDR. This generic messaging system is used to suit both current operator
needs and the needs of future BSS features.
Dynamic Allocation of RXCDR-BSC Circuits (DARBC) and Enhanced XBL (EXBL) have
interdependent functionality.
For further technical details, refer to Technical Description: BSS Implementation

(68P02901W36).
68P02900W22-S 3-129
Jul 2008
Batch processing of binary object files Chapter 3: Operating DataGen
Batch processing of binary object files

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of batch processing
Batch processing of binary object (.002) files is carried out by selecting Batch from the DataGen
main menu. The following functions can be carried out on one or more binary object files:
• Revgen
Multiple binary object files can be selected and converted into a DataGen script file.
• Upgrade
Multiple binary object files can be selected and upgraded to higher versions of DataGen.
• Compile
Multiple scripts files can be selected and compiled to form binary object files.
• Export MCDF Files and/or Copy Area
When the Revgen or upgrade batch option is selected, it is also possible to automatically
copy and/or export the new areas.
NOTE
A default BSS Area name is derived from the binary object name minus the .002
extension. For example, BSS12.002 becomes BSS area BSS12. Use meaningful
binary names.
3-130 68P02900W22-S
Jul 2008
System Information: DataGen Revgen multiple binary object files
Revgen multiple binary object files
To revgen multiple binary object files, perform the following procedure.
Procedure 3-47 Revgen multiple binary object files
1 Start DataGen from an Xterm window and select BATCH from the DataGen
main menu (refer to Figure 1-1). The Batch Tool window is displayed.
2 Select the Revgen option (as shown in Figure 3-55).
Figure 3-55 Batch Tool window with Revgen selected
3 To export the revgened areas automatically, click Export MCDF Files; else
proceed to step 4.
4 To copy the revgened areas automatically, click Copy Area; else proceed to
step 5.
5 To locate the directory where the binary object files are located, enter the
path in the Filter field and click the Filter button. All files are revgened in
the directory. To revgen only one file in the directory, select the required file
from the Files list box.
NOTE
If files other than binary object files exist in the directory, then a
warning message is generated in the Batch Monitoring window. A
default import path can be defined. Refer to Defining environment
variables on page 3-4 for details.
6 Click OK.
Continued
68P02900W22-S 3-131
Jul 2008
Revgen multiple binary object files Chapter 3: Operating DataGen
Procedure 3-47 Revgen multiple binary object files (Continued)

7 On the Batch Tool window, select the following:
• Country (from the Country Name list)
• Software version (from the Software Version list)

8 Enter the starting configuration number in the Start Config field and click
Execute. If the number exists, DataGen assigns the next available number.
NOTE
To obtain a configuration number automatically, do not enter a
number. DataGen automatically assigns the lowest configuration
number available.
A Confirmation window is displayed as in Figure 3-56. Click OK to continue.
Figure 3-56 Revgen Batch Confirmation window
NOTE
If all the essential fields are not completed, an error window is
displayed stating:
All fields are not filled in.
Click OK to return to the Batch Tools window.
Continued
3-132 68P02900W22-S
Jul 2008
System Information: DataGen Revgen multiple binary object files
Procedure 3-47 Revgen multiple binary object files (Continued)

9 The Batch Monitor window is displayed as in Figure 3-57. The Batch Monitor
can be left open to monitor the batch processing.
Figure 3-57 Revgen Batch Monitor window
NOTE
If the Close button is selected, batch processing continues in the
background. The outcome can be found in the report file which is
located in the selected binary object file directory. The report has a
Date and Time stamp, for example: batch_ddmmyyyyhhmmss.rpt.
68P02900W22-S 3-133
Jul 2008
Upgrade multiple binary object files Chapter 3: Operating DataGen
Upgrade multiple binary object files
To upgrade multiple binary object files, perform the following procedure.
Procedure 3-48 Upgrade multiple binary object files
1 Perform step 1 of Procedure 3-47 Revgen multiple binary object files.

This displays the Batch Tool window (refer to Figure 3-55).
2 Select the Upgrade option.
3 To export the upgraded areas automatically, click Export MCDF Files; else
proceed to step 4.
4 To copy the upgraded areas automatically, click Copy Area; else proceed
to step 5.
5 To locate the directory where the binary objects files are located, enter the
path in the Filter field and select the Filter button. All files are upgraded
in the directory. To upgrade only one file, select the required file from the
Files list box.
NOTE
If files other than binary object files exist in the directory, then
an error message is generated in the Batch Monitor window.
A default import path can be defined. Refer to Defining
environment variables on page 3-4 for details.
6 Click OK.
7 On the Batch Tool window, select the following:
• Country (from the Country Name list)
• Software version (from the Software Version list)
NOTE
All the binary object files in the directory must be of the
same software version for the upgrade to be successful.
8 Select the target version to upgrade to from the Target Version list.
Continued
3-134 68P02900W22-S
Jul 2008
System Information: DataGen Compile multiple MMI scripts
Procedure 3-48 Upgrade multiple binary object files (Continued)

9 Enter the starting configuration number in the Start Config: field and click
Execute. If the number exists, DataGen assigns the next available number.
NOTE
• To obtain a configuration number automatically, do not

enter a number as DataGen assigns the lowest configuration
number available.
• From the Edit menu, on the Service window it is possible to
view the upgrade log file. Refer to The Service window on
page 3-56, Edit menu for details.
Compile multiple MMI scripts
To compile multiple MMI scripts, carry out the following procedure.
Procedure 3-49 Compile multiple MMI scripts
1 Refer to the procedure Revgen multiple binary object files and repeat
step 1. This displays the Batch Tool window (refer to Figure 3-55).
2 Select the Compile option.
3 To locate the directory where the script files are located, enter the path in the
Filter field and select the Filter button. All files are compiled in the directory.
To compile only one file from the directory, select it from the Files list box.
NOTE
If files other than script files (ASCII text) exist in the directory, then
a warning message is generated in the Batch Monitor window.
A default import path can be defined. Refer to Network
Expansion - Defining environment variables for details.
4 Click OK.
Continued
68P02900W22-S 3-135
Jul 2008
Compile multiple MMI scripts Chapter 3: Operating DataGen
Procedure 3-49 Compile multiple MMI scripts (Continued)

NOTE
All script files must be the of same software version and the correct
compiler version must be selected, else errors are generated.
7 Click Execute.
A Confirmation window displays the following message:
Compiling ALL files from selection:

/fanned/user43/users/mcdermjo/dev/scripts/1800c/scripts/temp/
Select OK to proceed or CANCEL to return.
8 Click OK to continue. The Batch Monitor window is displayed, refer to
Figure 3-58. This window can be left open to monitor the batch processing.
Figure 3-58 Compile Batch Monitor window
Continued
3-136 68P02900W22-S
Jul 2008
System Information: DataGen Compile multiple MMI scripts
Procedure 3-49 Compile multiple MMI scripts (Continued)
NOTE
If the Close button is selected, batch processing continues in the
background. To view the outcome, check the report file which is
located in the directory where the scripts reside.
Once the batch process is complete, the following files are generated for each script compiled:
• Binary object file (.002)
• Report file (.rpt)
The files are located in the directory where the scripts reside.
NOTE
If any of the scripts fail to compile, then only a report file is generated. This can
be used to identify the problem.
68P02900W22-S 3-137
Jul 2008
Compile multiple MMI scripts Chapter 3: Operating DataGen
3-138 68P02900W22-S
Jul 2008
Chapter
Operating the Offline MIB

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02900W22-S 4-1
Jul 2008
Introduction to the Offline MIB Chapter 4: Operating the Offline MIB
Introduction to the Offline MIB

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of the Offline MIB
A Configuration Management (CM) database object is a binary file. Until the development of
DataGen, it was possible to create a binary file only by downloading an ASCII format script file
to a BSS in SYSGEN mode.
DataGen allows the user to modify and carry out Radio Frequency (RF) planning on multiple
BSS binary files through the Offline MIB (OLM) which has a graphical user interface (GUI).
Users can run only one Offline MIB at a time. However, multiple GUIs for the same MIB can be
displayed and tasks may be carried out by several different users.
The task list orders the tasks in the sequence that they are routinely performed within the OLM.
Additional OLM features describe extra functions that are performed infrequently.
NOTE
Parameters such as circuits, channels, statistics (enabling/disabling/thresholds) and
time slot reservations cannot be modified using the OLM GUI.
Task list before using OLM GUI
The following list describes the general procedures which should be carried out before using
the OLM GUI:
• Import BSS binary files from the OMC into DataGen. Refer to the procedure DataGen
- OMC Integration in the DataGen/OLM Clean Install Guide included in the manual
Software Release Notes: DataGen (68P02900W76).
• The upgrade function is carried out from the front panel DataGen window, not from the
OLM GUI. For details, refer to Upgrader in Chapter 3 Operating DataGen.
• Circuits, channels, statistics (enabling/disabling/thresholds), time slot reservations must

be modified through MCDF tables or MMI scripts. The scripts are compiled to create BSS
binary object files. For details, refer to Chapter 3 Operating DataGen.
4-2 68P02900W22-S
Jul 2008
System Information: DataGen Task list for using the OLM GUI
Task list for using the OLM GUI
The following lists, in sequence, the procedures that are performed using the OLM GUI:
• Start the OLM from the DataGen front panel.
• Create a network configuration.
• From the Navigation Tree of the OLM, import the BSS binary files from DataGen into the
network.
NOTE
RXCDRs binary files can be added but channels cannot be modified or equipped.
Only hardware changes can be made.
• Audit the network. The OLM must reflect the current configuration of the BSS binary files.
• Modify the BSSs through the Navigation Tree and Detail Views.
• Perform CellXchange and implementing changes for multiple BSSs.
• Save and verify all NEs.
• Export BSS binary files to the OMC. Refer to Exporting object files to the OMC in
Chapter 3 Operating DataGen.
• Delete the network configuration in the OLM.
Further information
Further information on using the OLM can be found in Online Help.
Additional OLM tasks
To carry out additional tasks such as importing binary files from tape into the OLM directory
(Realign Network), refer to Additional OLM features on page 4-56.
NOTE
These tasks are not routine functions and should be carried out only by the
administrator or creator of the Offline MIB network.
68P02900W22-S 4-3
Jul 2008
Levels of users Chapter 4: Operating the Offline MIB
Levels of users
The four levels of users are:

• Administrator group.
• Owner and creator of the Offline MIB network.
• First user to launch the Offline MIB network.
• Subsequent GUI user of an Offline MIB network that is currently in use.
Table 4-1 shows the administrative tasks that the various users can perform on the Offline MIB.
Table 4-1 Administrative tasks and user types
User Type Administrative tasks

Shut down OLM Force shutdown Reinitialize OLM Delete OLM
on last GUI exit OLM network network config.
Admin Group √ √ √ √
Owner of √ √ √ √
OLM network
configuration
First to launch √ √
network
configuration
GUI √
Troubleshooting and other tasks
If problems are encountered when operating the Offline MIB, refer to the section
Troubleshooting the OLM on page 4-80 to help resolve the problems.
Many administrative tasks are located from the Network Configuration selection window
under the menu option Admin (refer to Figure 4-1). For more information about these tasks,
refer to:
• Reinitialize database procedure on page 4-85
• Introduction to the force shutdown feature on page 4-83
• Compress or uncompress an OLM network on page 4-78
OLM environment variables
The environment variable OLM_VERIFY_DB_LOGGING can be used to identify the relevant

sites and cells that errors apply to when verifying an NE database. Refer to Verify and save
network on page 4-46 for details on this procedure.
4-4 68P02900W22-S
Jul 2008
System Information: DataGen Using the cmutil.olm command
To enable the environment variable, perform the following procedure.
Procedure 4-1 Enable OLM_VERIFY_DB_LOGGING environment variable
1 Edit the file olmProcConfig.csh by executing the following commands:

cd /usr/omc/current/configvi olmProcConfig.csh
2 Insert the following line:
setenv OLM_VERIFY_DB_LOGGING ON
3 Save the file and exit the vi editor.
4 Exit and restart the OLM for the variable to be applied. Refer to
Starting/exiting the OLM GUI on page 4-9 for more information.
Using the cmutil.olm command
On the OLM, the command cmutil.olm is used, while on the OMC, the command cmutil is
used. When using cmutil.olm, the environment variable DBNAME must be set to the name of
the network on which the operation is to be performed, for example: set DBNAME = network1.
Other than that, cmutil.olm should perform similarly to cmutil.
For more information about using the cmutil command, refer to the manual Installation and
Configuration: GSM System Configuration (68P02901W17).
68P02900W22-S 4-5
Jul 2008
Starting/creating a network configuration in the OLM Chapter 4: Operating the Offline MIB
Starting/creating a network configuration in the OLM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to network configuration
This section describes the procedures to:

• Launch the Offline MIB from the DataGen main menu.
• Create a network configuration.
Starting the OLM
To start the OLM from the DataGen main menu, perform the following procedure:
Procedure 4-2 Starting the OLM
1 Click the OLM button, refer to DataGen - startup and shutdown in the
Chapter 3 Operating DataGen A status message is displayed.
2 Click OK to continue. The OLM Network Configurations window then
opens as shown in Figure 4-1.
Creating a network configuration
To create a network configuration, perform the following procedure.
Procedure 4-3 Create a network configuration
1 Select the Create button or select Edit à Create from the menu bar (refer
to Figure 4-1). The OLM Network Configuration Creation window is then
Continued
4-6 68P02900W22-S
Jul 2008
System Information: DataGen Creating a network configuration
Procedure 4-3 Create a network configuration (Continued)
Figure 4-1 Offline MIB Network Configurations window
Figure 4-2 OLM Network configuration creation window
Continued
68P02900W22-S 4-7
Jul 2008
Creating a network configuration Chapter 4: Operating the Offline MIB
Procedure 4-3 Create a network configuration (Continued)

2 Enter the name of the new network configuration and press the Tab key.
NOTE
The name cannot start with a number or include a hyphen.
3 Enter the Mobile Country Code (MCC) and press the Tab key.
4 Enter the Mobile Network Code (MNC). The RDN Class Network is
displayed.
5 Select Additional Information and enter a brief description of the network.
(But it is not mandatory to enter this information).
6 Select File à Create from the menu bar to create the network configuration.
7 Select File à Save from the menu bar to save the configuration.
8 Select File à Close from the menu bar to close the window and return to the
OLM Network Configurations window. The list is updated and now
contains the new network configuration name.
NOTE
To edit the Additional Information field, select Network
Detailed View from the Navigation Tree. Refer to Modifying the
network configuration from the Navigation Tree on page 4-37 for
more details.
4-8 68P02900W22-S
Jul 2008
System Information: DataGen Starting/exiting the OLM GUI
Starting/exiting the OLM GUI

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The following procedures are described in this section:

• Starting the OLM GUI
• Exiting the OLM GUI
• Shutting down the OLM
Starting the OLM GUI
To start the OLM GUI, perform the following procedure.
Procedure 4-4 Start the OLM GUI
1 From the DataGen main menu, select the OLM button, refer to DataGen -
startup and shutdown in Chapter 3 Operating DataGen. The Offline MIB
(OLM) Network Configurations window is displayed as in Figure 4-1.
2 Select the required network configuration name from the OLM Network
Configurations list. The selection is highlighted in black.
NOTE
By default, the first network configuration is selected.
3 Select Edit à Open from the menu bar (alternatively, click the Open button or
double click with left mouse button) to open the OLM GUI.
Continued
68P02900W22-S 4-9
Jul 2008
Starting the OLM GUI Chapter 4: Operating the Offline MIB
Procedure 4-4 Start the OLM GUI (Continued)

4 A Confirmation window displays a warning as shown in Figure 4-3. Click OK
to continue or Cancel to exit without opening the OLM GUI.
Figure 4-3 Starting the OLM - Confirmation window
While the OLM is starting, a Status window displays the following message:
Initialising...Please wait...
Starting the MIB process...
Initialising the Network Elements...
Starting the GUI application...
NOTE
It is possible to open only one network configuration at a time.
However, the GUI for the opened network can be displayed on several
machines. The InUse column on the OLM Network Configurations
window identifies the number of users that currently have the
network configuration GUI open (refer to Figure 4-4).
Continued
4-10 68P02900W22-S
Jul 2008
System Information: DataGen Starting the OLM GUI
Procedure 4-4 Start the OLM GUI (Continued)
Figure 4-4 Opening a Network Configuration - Status window
The OLM GUI opens and the front panel is displayed (refer to Figure 4-5). Refer
to the section Front panel icons on page 4-15 for more information about the
OLM front panel.
Figure 4-5 Offline MIB front panel
68P02900W22-S 4-11
Jul 2008
Exiting the OLM GUI Chapter 4: Operating the Offline MIB
Exiting the OLM GUI
To exit the OLM GUI, click Exit on the OLM front panel (refer to Figure 4-5).
A Confirmation window is displayed (Figure 4-6).
Click OK to exit the GUI and return to the OLM Network Configurations window.
Figure 4-6 GUI Exit - Confirmation window
NOTE
If the network configuration GUI is opened by more than one user, the message
shown in Figure 4-6 is displayed.
Shutting down the OLM
NOTE
The last user to exit the GUI shuts down the Offline MIB.
4-12 68P02900W22-S
Jul 2008
System Information: DataGen Shutting down the OLM
Perform the following steps to exit and shut down the OLM.
Procedure 4-5 Exit and shut down the OLM
1 Click Exit on the OLM front panel (refer to Figure 4-5). A Confirmation
window is displayed as shown in Figure 4-7.
Figure 4-7 OLM Shutdown Confirmation window
2 Click the Save à Exit button. If no errors exist within the network, the
Confirmation window closes and the OLM shuts down. If errors are detected,
proceed to step 3.
3 For each Network Element where errors exist, a Warning window is displayed,
detailing the location and errors found. Refer to Figure 4-8.
Figure 4-8 Binary Database errors and warnings window for a Network
Element
Continued
68P02900W22-S 4-13
Jul 2008
Shutting down the OLM Chapter 4: Operating the Offline MIB
Procedure 4-5 Exit and shut down the OLM (Continued)

4 Click the View More Details button to view more details of the errors found.
5 Click the Save NE button to save the Network Element with the reported
errors or go to step 6. If no more Network element errors are present, the
OLM shuts down.
6 Click Don't Save NE. If no more errors are present, the OLM shuts down.
NOTE
This can result in inconsistencies between the Offline MIB and the
specific NE database within the network configuration directory.
4-14 68P02900W22-S
Jul 2008
System Information: DataGen Front panel icons
Front panel icons

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Offline MIB front panel
The DataGen OLM front panel provides the top-level controls (icons) for the Offline MIB (OLM)
as in Figure 4-5. The name of the operator who has logged in is displayed at the top left of
the front panel.
About the Offline MIB
To show the current version of the OLM, place the cursor over the front panel, then press and
hold the right mouse button and select the About Offline MIB option.
Configuration management
Select the Config Mgmt icon to display the Navigation Tree. The Navigation Tree provides a
means of importing multiple BSS DataGen binary files. It displays a family tree representation
of all configurable objects. RF planning and modifications can be carried out on multiple BSSs.
Refer to Using the Navigation Tree: Overview on page 4-27 for details.
For more detailed information about using the Navigation Tree, refer to Network Operations,
OMC-R Online Help.
Administration
Select the Admin icon to view the Admin Options window. Administration is related to
the audit functions. All BSSs and RXCDRs must be audited before altering their BSS Binary
database files.
68P02900W22-S 4-15
Jul 2008
Find Chapter 4: Operating the Offline MIB
Find
Select the Find icon to invoke a search facility to locate a Network Entity, PCU, Site, or Cell
within a network. The Find function displays a Navigation Tree starting at the network object
defined in the Find criteria. The Find function can also be used to locate an attribute.
Once the required item is found it is possible to perform the following:

• Open the Navigation Tree with the found node as its root.
• Open a Detailed View for the node.
Help
Select this icon to invoke the contents page of the OLM online help. The Help option can also
be selected from many of the windows shown in the OLM section of the manual. The Help
option is described in the DataGen OLM Online Help facility.
Xterm
Select this icon to open an Xterm window.
Exit
The EXIT button is located beneath the icons in the OLM front panel. Click this button and then
confirm the action to exit from the OLM front panel.
4-16 68P02900W22-S
Jul 2008
System Information: DataGen Expert Offline MIB front panel
Expert Offline MIB front panel
The OLM front panel can be reduced in size to optimize screen coverage. To reduce the size,
place the cursor over the front panel, then press and hold the right mouse button. Select the
Expert Desktop option to resize the front panel (Figure 4-9).
Figure 4-9 Expert desktop
To return to the standard desktop, place the cursor over the front panel then press and hold the
right mouse button. Select the Standard Desktop option to return to the standard desktop
display.
68P02900W22-S 4-17
Jul 2008
Finding devices and attributes Chapter 4: Operating the Offline MIB
Finding devices and attributes

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of the Find function
The Find function is used to locate:

• Devices such as NEs, Sites, PCUs, or Cells within the network.
• Attributes such as attributes containing the string ho_margin.
From the Offline MIB front panel, select the Find icon to display a Find window. The Find
Devices option is selected by default. Search for NEs, Sites, PCUs, or Cells by entering
completely or partially the following details:
• NE Name
• Site Name
• Site Id
• PCU Name
• Cell Name
• GSM Cell Id
Once the required device has been found, it is possible to:

• Open the Navigation Tree with the found node as its root.
• Open a Detailed View for the node.
For more information about finding devices, refer to Finding an NE, PCU, Site, or Cell on page
4-19.
Select the Find Attributes option to open a Find Attribute window where details of the
required attribute are entered. For more information about finding attributes, refer to Finding
an attribute on page 4-24.
4-18 68P02900W22-S
Jul 2008
System Information: DataGen Finding a Network Element, PCU, Site, or Cell
Finding a Network Element, PCU, Site, or Cell

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Finding an NE, PCU, Site, or Cell
To find an NE, PCU, Site, or Cell, perform the following procedure.
Procedure 4-6 Find an NE, PCU, Site, or Cell
1 Select the Find button from the Offline MIB front panel. This displays the
Find window as in Figure 4-10 with the Find Devices option selected by
default.
Figure 4-10 Find window
Continued
68P02900W22-S 4-19
Jul 2008
Finding an NE, PCU, Site, or Cell Chapter 4: Operating the Offline MIB
Procedure 4-6 Find an NE, PCU, Site, or Cell (Continued)

2 Enter the name of the NE, PCU, Site, or Cell in the relevant Name field. An ID
can be entered for a Site or Cell in the relevant ID field. Click the Clear
button to remove the text from all the fields.
NOTE
The search performs an exact match on Site id or Cell id and a
partial match in all other fields. For example, Site id:1 is matched
with site 1 but not site 10. The text string SS1 is matched with
BSS1 and BSS10. The search is not case sensitive.
3 Click the Find NE(s), Find PCU(s), Find SITE(s) or Find CELL(s) button.
• Find NE(s) displays the network elements that match the criteria in
all fields. If a cell name is entered, it finds the NE containing the cell.
• Find PCU(s) displays the PCUs that match the criteria in all fields.
• Find SITE(s) displays the sites that match the criteria in all fields.
• Find CELL(s) displays the cells that match the criteria in all fields.
NOTE
• If no text is entered, the search displays all NEs, PCUs,

Sites, or Cells in the network.
• Alternatively, use Enter from the keyboard instead of the
Find buttons.
4 The result of the search is displayed in the Find Results area of the window.
The heading indicates the class of objects found, that is, Network Elements,
PCUs, Sites, or Cells.
NOTE
If no match is found, an Information window is displayed stating:
No matching <object> was found.
5 Click the required object in the Find Results box. The selection is
highlighted in inverse text, where object is the Network Element, PCU,
Site, or Cell.
6 For a Site or Cell, to obtain the parent view, click the Find Parent button;
else, go to step 7.
Continued
4-20 68P02900W22-S
Jul 2008
System Information: DataGen Finding an NE, PCU, Site, or Cell
Procedure 4-6 Find an NE, PCU, Site, or Cell (Continued)

7 From the Open section of the Find window, select either the Navigation
Tree or Detailed View button (refer to Figure 4-11). The Navigation Tree
opens with the found node as its root or a Detailed View opens for the node.
Figure 4-11 Find window with a Cell and Navigation Tree selected
8 From the menu bar on the Navigation Tree or Detailed View window, select
File à Close to return to the Find window.
9 Select Close to return to the Offline MIB front panel.
68P02900W22-S 4-21
Jul 2008
Examples of using Find Chapter 4: Operating the Offline MIB
Examples of using Find
The following are typical examples of when an operator can use the Find feature.
Finding a Site using BSS name and Site Id
To find a Site at a BSS by specifying the BSS name and the Site id, perform the following
procedure.
Procedure 4-7 Find a Site at a BSS
1 Select the Find button from the Offline MIB Front Panel to open the Find
window.
2 Enter the BSS name in the NE Name field and then enter the Site ID in
the Site id field.
3 Click Find Site(s). The result of the search is displayed in the Find Results
box.
Finding a BSS parent of a Cell
To find the BSS parent of a Cell, perform the following procedure.
Procedure 4-8 Find the BSS parent of a Cell
window.
2 Enter the name of the Cell in the Cell Name field, or its ID in the GSM
Cell id field.
3 Click Find Cell(s). The results of the search are displayed in the Find
Results box.
4 Select the Cell in the Find Results box.
5 Click Find Parent. The parent site of the Cell is displayed in the Find
Results box.
6 Select the Site and then click Find Parent. The parent BSS of the Cell is
displayed in the Find Results box.
4-22 68P02900W22-S
Jul 2008
System Information: DataGen Examples of using Find
Finding a Cell with a LAC
To search for Cells with a particular Location Area Code (LAC), perform the following procedure.
Procedure 4-9 Find a Cell with a LAC
window.
2 Enter the LAC in the third field of the GSM Cell Id.
3 Click Find Cell(s). All Cells with the specified LAC are displayed in the
Find Results box.
NOTE
Additional information about GSM Cell IDs can be found in
Technical Description: BSS Implementation (68P02901W36)
and Installation and Configuration: GSM System Configuration
(68P02901W17).
68P02900W22-S 4-23
Jul 2008
Finding an attribute Chapter 4: Operating the Offline MIB
Finding an attribute
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of finding attributes
The Find Attributes window (as in Figure 4-12) can be used to identify the exact name of
an attribute when only part of the attribute name is known. For example, searching for con
would list all attribute names containing con.
Figure 4-12 Find Attributes
4-24 68P02900W22-S
Jul 2008
System Information: DataGen Overview of finding attributes
Finding an attribute
To find an attribute, perform the following procedure.
Procedure 4-10 Find an attribute
1 Click the Find icon on the DataGen Front Panel. The Find window
Figure 4-10 is displayed with the Find Devices button selected, by default.
2 Click the Find Attributes button at the top of the window. The window is
ready to accept find criteria for an attribute (refer to Figure 4-12).
3 Select either Begins With, Ends With or Anywhere in the Attribute
Name field to search for an attribute whose name either begins with, ends
with or contains with the contiguous characters entered in step 4.
4 Enter at least three of the contiguous characters in the attribute name in the
Attribute name field.
For example, if searching for attribute names containing ho_margin in the
attribute name, entering mar would return many attribute names, but
entering ho_margin would return a more precise list of attribute names.
NOTE
The attribute name or search string cannot be less than three
characters.
5 Click either the OMC Naming or BSS Naming button to indicate the
naming convention of the attribute to be found.
6 Select the software version number associated with the attribute in the
Version field. The default is the latest software version.
NOTE
Some attributes can have a slightly different name in the OMC-R
database and the BSS database.
Continued
68P02900W22-S 4-25
Jul 2008
Overview of finding attributes Chapter 4: Operating the Offline MIB
Procedure 4-10 Find an attribute (Continued)

7 Click the Find Attribute button to start the search. Alternatively, press
RETURN. The results of the search are displayed in the Find Results
pane. Use the scroll bars to scroll through the results, if necessary. The
results are shown in the following format: classname::attributename
Where classname is the container name and attributename is the attribute
name.
For example, if the attribute Anywhere is selected and ho_margin is
entered as the search string in the Attribute Name field, the Find
Results pane would display the following list of attributes:
CELL::ho_margin_def
neighbour::ho_margin_cell
neighbour::ho_margin_rxqual
neighbour::ho_margin_rxlev
neighbour::ho_margin_type5
neighbour::congest_ho_margin
If no results are found, the following message is displayed:
No matching attribute found for given search string.
Printing the Find results
To print the results shown in the Find Results pane, click the Print button.
Saving the Find results
To save the results shown in the Find Results pane to a file, perform the following procedure:
• Click the Save button. The File Selection window is displayed.
• Enter the name of the file and the directory to which the Find results are to be saved.
Closing the Find window
To close the Find window, click the Close button.
4-26 68P02900W22-S
Jul 2008
System Information: DataGen Using the Navigation Tree: Overview
Using the Navigation Tree: Overview

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Procedure list
The following is a list of procedures available from a Navigation Tree window:

• Opening and closing a Navigation Tree on page 4-28
• Moving levels on a Navigation Tree on page 4-30
• Creating a BSS/RXCDR from the Navigation Tree on page 4-32
Further information
Further information on using the Navigation Tree can be found in the Online Help.
The Navigation Tree is similar to the OMC Navigation Tree except for the following details:
• The menu bar has an Offline MIB pull down menu bar.
• Load Mgt and Fault Mgt are not present in the menu bar.
68P02900W22-S 4-27
Jul 2008
Opening and closing a Navigation Tree Chapter 4: Operating the Offline MIB
Opening and closing a Navigation Tree

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Opening the Navigation Tree
To open a Navigation Tree, on the Offline MIB front panel (Figure 4-5), select the Config Mgmt
icon to display a Navigation Tree window as shown in Figure 4-13.
Figure 4-13 Navigation Tree window
4-28 68P02900W22-S
Jul 2008
System Information: DataGen Warning window Invalid NE
Warning window Invalid NE
When the Navigation Tree is opened, a comparison between the NEs in the MIB and the
BSS binary files in the configuration directory is carried out. If NEs exist in the MIB with
no corresponding BSS binary files, a Warning window listing all invalid NEs is displayed as
in Figure 4-14.
Figure 4-14 Invalid NEs window
Click Close to exit from the Warning window.
Resolving inconsistencies
The inconsistencies can be resolved by:

• Carrying out a realign from the Navigation Tree. Refer to Realign a network on page 4-76
and carry out step 5 to step 8 of Procedure 4-34.
OR
• Selecting the NEs and deleting them from the Navigation Tree. Refer to Deleting a BSS or
RXCDR from the Navigation Tree on page 4-58 for details.
Closing the Navigation Tree
To close a Navigation Tree, select File à Close from the menu bar.
68P02900W22-S 4-29
Jul 2008
Moving levels on a Navigation Tree Chapter 4: Operating the Offline MIB
Moving levels on a Navigation Tree

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Prerequisite to moving levels
A Navigation Tree must be open and displayed on the user terminal before attempting to move
levels on that tree. See the procedure for Opening and closing a Navigation Tree on page 4-28.
NOTE
In the event that the OLM has no BSS or RXCDR network object created, an empty
Navigation Tree window is displayed. Refer to Creating a BSS/RXCDR from the
Navigation Tree on page 4-32 for details on how to create BSSs or RXCDRs.
Procedure for moving levels
Assuming that the Navigation Tree is in the form shown in Figure 4-15, perform the following
procedure to move the levels.
Procedure 4-11 Move levels on a Navigation Tree
1 To expand the Navigation Tree to the second level, click the folder icon next
to the Network object. The various class buttons are displayed.
2 To open the branch of a tree under a button, click the folder icon beside
the button.
3 To close the branch of a tree under a button, click again on the folder icon
beside the button.
4-30 68P02900W22-S
Jul 2008
System Information: DataGen Panner and porthole
Figure 4-15 Navigation Tree window - showing panner
Panner and porthole
When the Navigation Tree diagram becomes larger in size than the display area of the
Navigation Tree window (Figure 4-15), a panner and porthole arrangement is used to control
the display. The tree is displayed in the porthole region on the right-hand side of the window,
and the display is controlled by means of a panner on the left.
To display different portions of the tree, move the panner as follows:
• Click and hold the left mouse button within the panner region.
• Move the mouse until the required area is in view within the porthole.
• Release the mouse button.
68P02900W22-S 4-31
Jul 2008
Creating a BSS/RXCDR from the Navigation Tree Chapter 4: Operating the Offline MIB
Creating a BSS/RXCDR from the Navigation Tree

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to creating an NE
Creating a BSS or RXCDR involves importing BSS binary files from DataGen into the OLM. The
original files remain in DataGen and a copy is imported into the OLM.
Procedure for creating a BSS or RXCDR
To create a BSS or RXCDR from the Navigation Tree window, perform the following procedure.
Procedure 4-12 Create a BSS or RXCDR
1 Click the BSS/RXCDR Node and select Edit à Create from the menu bar.
The BSS Binary configurations creation window is displayed as in
Figure 4-16.
Figure 4-16 BSS Binary configurations creation window
2 Select a country from the Country list.

3 Select a BSS area from the Area list.
4 Select a software version from the Software version list.
5 Select the configuration from the Configuration list.
Continued
4-32 68P02900W22-S
Jul 2008
System Information: DataGen Procedure for creating a BSS or RXCDR
Procedure 4-12 Create a BSS or RXCDR (Continued)

6 Click the Import database button. The message ReAlign Operation
successful is displayed in the status bar at the bottom of the Navigation
Tree window when the import is complete.
7 An Information window is displayed as shown in Figure 4-17. Click OK
to continue.
Figure 4-17 Information window
8 Repeat step 2 to step 6 to import the required number of BSS binary files
into the network configuration.
NOTE
The maximum number of BSS binary files that can be imported is
64. The BSS binary files must be from different areas containing
different cells.
9 Click Cancel to close the BSS Binary configurations creation window
and return to the Navigation Tree.
To audit the network, refer to the section Running an audit from the Navigation Tree on page
4-35.
68P02900W22-S 4-33
Jul 2008
Audit: overview Chapter 4: Operating the Offline MIB
Audit: overview
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to auditing
After creating a network element from the Navigation Tree, it is necessary to populate the
network elements (NEs) with device information. This is done by selecting the network and
carrying out an Audit and Apply to OMC.
Ways to audit
An audit can be carried out as follows:

• From the Navigation Tree
Current audits for the entire network can be set in progress from the Navigation Tree.
Refer to Running an audit from the Navigation Tree on page 4-35 for more information.
• Using the Admin icon on the Offline MIB front panel
Audit puts a significant load on the OLM in terms of processing power and memory usage.
It takes a considerable amount of time and therefore it is better to schedule the audit.
Refer to Scheduling an audit on page 4-60 for more information.
NOTE
The preferred way of using audit is on a per NE basis. Network-wide audits
are not recommended as they may cause degradation of the DataGen
machine due to resource consumption. For more information about Auditing
recommendations, refer to the manual Installation and Configuration: GSM
System Configuration (68P02901W17).
4-34 68P02900W22-S
Jul 2008
System Information: DataGen Running an audit from the Navigation Tree
Running an audit from the Navigation Tree

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to auditing from the Navigation Tree
An audit can be performed from the Navigation Tree. After the audit is complete, perform the
function, Apply to OMC.
Audit from the Navigation Tree
To carry out an audit from the Navigation Tree, perform the following procedure.
Procedure 4-13 Run audit from the Navigation Tree
1 From the Navigation Tree (refer to Figure 4-13), click the network node
for the whole network, then select either the individual BSS or multiple
BSSs to be audited.
NOTE
It is valid to select either the BSS, RXCDR, SITE, PCU, or the
entire network to be audited.
2 Select Config Mgt à Audit from the menu bar. The message Audit
operation successfully dispatched is displayed in the status bar at the
bottom of the Navigation Tree window.
3 To monitor the status of the audit, select Config Mgt à Audit Logs from
the menu bar.
4 From the Audit Logs window, monitor the audit until it shows a status of
having been finished.
5 Select the Audited Item (highlighted in inverse text).
Continued
68P02900W22-S 4-35
Jul 2008
Audit from the Navigation Tree Chapter 4: Operating the Offline MIB
Procedure 4-13 Run audit from the Navigation Tree (Continued)

6 Select File à Open from the menu bar or double-click the highlighted row.
An Audit Inconsistency List window is displayed as in Figure 4-18.
Figure 4-18 Audit Inconsistency List window
7 Select Options à Apply to OLM from the menu bar.

8 A Confirmation window is then displayed. Click OK to continue or Cancel
to abort the procedure. The progress is documented in the status bar.
9 When complete, select File à Close to close the window and to return to
the Navigation Tree. Inconsistencies that have been applied to the OLM
during the audit procedure are now visible on the Navigation Tree window,
that is, any devices deleted are removed from the Navigation Tree and any
new devices introduced are displayed.
4-36 68P02900W22-S
Jul 2008
System Information: DataGen Modifying the network configuration from the Navigation Tree
Modifying the network configuration from the

Navigation Tree
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Device management
From the Navigation Tree, it is possible to create, modify, save NE devices and parameters.
The procedures to carry out these operations are documented in Installation and Configuration:
GSM System Configuration (68P02901W17).
Creating or editing circuits, channels, statistics (enabling or disabling or threshold), and time
slot reservations are not supported from the Navigation Tree.
When required, use the Offline MIB pull-down menu to verify and save the new configuration.
NOTE
From the Navigation Tree, saving a detailed view of a device does not automatically
alter the BSS binary file. To update the BSS binary file, it is necessary to verify and
save the databases. For further information, refer to Verify and save NE database
Configuring cells
From the Navigation Tree, it is possible to add, modify, delete, and propagate certain cell
parameters. When certain cell parameters are changed the values are propagated to the
neighbor commands of the surrounding cells automatically.
The procedures for carrying out these tasks are documented in Installation and Configuration:
GSM System Configuration (68P02901W17).
When required, use the Offline MIB pull-down menu to verify and save the new configuration.
NOTE
From the Navigation Tree, saving a detailed view of a device does not automatically
alter the BSS binary file. To update the BSS binary file, it is necessary to verify and
save the databases. For further information, refer to Verify and save NE database
68P02900W22-S 4-37
Jul 2008
CellXchange: overview Chapter 4: Operating the Offline MIB
CellXchange: overview
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to CellXchange
CellXchange enables operators to perform the following tasks:

• Export parameters from the OLM network into a tab delimited format.
• Import parameters from a tab delimited format into the OLM network.
CellXchange can be carried out either in a live environment using the OMC-R CM MIB or in
an offline environment using the OLM. Refer to the manual Installation and Configuration:
GSM System Configuration (68P02901W17) for more information on performing CellXchange
from the OLM.
Running CellXImport on the OMC-R or OLM
On the Cell X Import Watcher window, Motorola recommends the following for the BSS
deployment setting:
• On the OLM, select Sequential mode.
Each BSS binary on the OLM has its own process running, so running several processes in
parallel on the OLM results in a lot of commands being sent out at the same time. Since
all of these commands run on the same machine, applying all the BSS changes results in
heavy loading on the OLM machine.
• On the OMC-R, select Parallel mode.
On the live OMC-R, the commands are sent out to individual BSS. Therefore, the loading on
the OMC-R is lesser since each BSS is running its own process.
4-38 68P02900W22-S
Jul 2008
System Information: DataGen Overwrite a BSS/RXCDR binary object file
Overwrite a BSS/RXCDR binary object file

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of overwrite feature
It is possible to copy BSS binary object file and overwrite the existing BSS binary object file in
the OLM.
NOTE
This feature overwrites the existing NEs and any changes made through the OLM
are lost.
Procedure for overwriting a BSS Binary object file
To overwrite a BSS Binary object file, perform the following procedure.
Procedure 4-14 Overwrite a BSS Binary object file
1 Select the network from the network selection window. Refer to

Starting/exiting the OLM GUI on page 4-9 for details.
2 Select Config Mgmt from the Front Panel to display the Navigation Tree.
Refer to Opening and closing a Navigation Tree on page 4-28 for details.
3 Select the BSS or RXCDR from the Navigation Tree.
Continued
68P02900W22-S 4-39
Jul 2008
Procedure for overwriting a BSS Binary object file Chapter 4: Operating the Offline MIB
Procedure 4-14 Overwrite a BSS Binary object file (Continued)

4 Select Offline MIB à Import NE Database from the menu bar. The BSS
Binary configurations window is displayed as in Figure 4-19.
Figure 4-19 BSS Binary configurations window
5 Select the database configuration as follows:
• Select the same country from the Country list.
• Select the same BSS or RXCDR area from the Area list.
• Select a software version from the Software version list.
• Select the configuration from the Configuration list.

6 Click Import database. The message Reload Operation successful is
displayed in the status bar at the bottom of the Navigation Tree window
when the import is complete. An Information window is displayed as shown
in Figure 4-20. Click OK to continue.
Continued
4-40 68P02900W22-S
Jul 2008
System Information: DataGen Procedure for overwriting a BSS Binary object file
Procedure 4-14 Overwrite a BSS Binary object file (Continued)

7 Click Cancel to close the window and return to the Navigation Tree.
An audit is initiated.
8 To view the status of the audit, select Config Mgt à Audit Logs from
the menu bar. When the audit and apply is complete, the Navigation Tree
reflects the new BSS binary object file.
68P02900W22-S 4-41
Jul 2008
Verify and save overview Chapter 4: Operating the Offline MIB
Verify and save overview

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to applying changes
The Navigation Tree is used to modify the network, and the information is saved in the OLM.
To apply the changes to the BSS databases (binary files) on disk, the following actions must
be performed:
• Verify - Ensures that all the parameters are correct in accordance with predefined BSS
rules. Once a validation is carried out it highlights any discrepancies that need corrective
action. It is possible to select individual NEs or an entire network. This option is available
under the Offline MIB pull-down menu.
• Save - Saves the BSS database file to disk and should be carried out regularly. Exiting the
OLM without saving, results in the loss of the changes effected. This option is available
under the Offline MIB pull-down menu.
NOTE
Do not deploy a saved BSS database without first carrying out a verify procedure.
The Verify and the Save actions for the entire network can be performed in a single step by
selecting Database Operations from the Offline MIB pull-down menu. This option provides a
complete list of all NEs in the network to which verify and save operations can be applied.
NOTE
By default, all NEs are selected. It is possible to deselect NEs from the list before
performing the Verify or Save action.
4-42 68P02900W22-S
Jul 2008
System Information: DataGen Verify and save NE database
Verify and save NE database

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Verify a network element
NOTE
• If the environment variable OLM_VERIFY_DB_LOGGING is set to ON, then a

detailed error file is found in the following location:
/usr/DataGen/olm/<Network_name>/<Network_name002>.verify
• Upon successive Verify actions, the file is over written. Refer to Introduction to
the Offline MIB on page 4-2 for details.
To verify a network element (NE), perform the following procedure.
Procedure 4-15 Verify a network element
1 Select the network from the Network Selection window. Refer to

2 Select Config Mgt from the Front Panel to display the Navigation Tree.
3 Select the NE from the Navigation Tree.
Continued
68P02900W22-S 4-43
Jul 2008
Verify a network element Chapter 4: Operating the Offline MIB
Procedure 4-15 Verify a network element (Continued)

4 Select Offline MIB à Verify NE Database from the menu bar on the
Navigation Tree window. If errors exist, a Warning window is displayed
detailing the location and errors found for each NE as in Figure 4-21. Click
the View More Details button to see detailed information for each site
and cell affected.
Figure 4-21 Binary Database error and warnings window
5 Click Close to continue. To resolve any errors found (for example, to add
NE devices and parameters), refer to Modifying the network configuration
from the Navigation Tree on page 4-37 for details.
6 Repeat step 3 to step 4. A message is displayed in the status bar at the
bottom of the Navigation Tree window when no errors are present:
Operation successful.
NOTE
Do not deploy a saved NE database without first carrying out a
verify procedure.
4-44 68P02900W22-S
Jul 2008
System Information: DataGen Save a network element
Save a network element
To save a NE, first refer to Procedure 4-15 Verify a network element and follow step 1
to step 4. The NE is then selected.
Select Offline MIB à Save NE Database from the menu bar on the Navigation Tree
window. The following message is displayed in the status bar at the bottom of the Navigation
Tree window:
Off-Line MIB operation in progress...
Operation successful.
NOTE
Carry out this procedure at regular intervals.
68P02900W22-S 4-45
Jul 2008
Verify and save network Chapter 4: Operating the Offline MIB
Verify and save network

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Verify network
NOTE
• If the environment variable OLM_VERIFY_DB_LOGGING is set to ON, a detailed

error file can be found in the following location:
/usr/DataGen/olm/<Network_name>/<Network_name002>.verify
• Upon successive Verify actions, the file will be over written. Refer to Introduction
to the Offline MIB on page 4-2 for details.
To verify the entire network, perform the following procedure.
Procedure 4-16 Verify the entire network
1 Select the network from the Network Selection window. Refer to

2 Select Config Mgmt from the Front Panel to display the Navigation Tree.
3 Select the Network node from the Navigation Tree.
4 Select Offline MIB à Database Operations from the menu bar on the
Navigation Tree window.
Continued
4-46 68P02900W22-S
Jul 2008
System Information: DataGen Verify network
Procedure 4-16 Verify the entire network (Continued)

5 Click Verify NE Database in the Offline MIB Database Operations
window (Refer to Figure 4-22). The Offline MIB Verify Operation Monitor
window is displayed as in Figure 4-23. This contains a list of all NE names
and the operation status. If the verification produces errors or warnings,
this is indicated in the Reason column.
Figure 4-22 Offline MIB Database Operations window
NOTE
By default, all NEs in the network are selected and highlighted in
the OLM Database Operations window. To deselect an NE, click
the NE in the list. The NE is then displayed in normal text.
Continued
68P02900W22-S 4-47
Jul 2008
Verify network Chapter 4: Operating the Offline MIB
Figure 4-23 Offline MIB Verify Operation Monitor window
6 If the status Operation successful is displayed for all NEs, click Close in
this window and in all the subsequent windows to return to the Navigation
Tree window. If the operation fails, select the Network Element. The
selected NE is then highlighted.
7 Click Show Errors/Warnings. This displays the Binary Database error
and warnings window, detailing the location, and errors found as in
Figure 4-24.
Continued
4-48 68P02900W22-S
Jul 2008
System Information: DataGen Verify network

8 Click the View More Details button to see detailed information for each
site and cell affected.
Figure 4-24 Binary Database error and warnings window
9 Click Close to return to the Offline MIB Verify Operation Monitor

window.
Writing errors to a file
To write the errors to a file, perform the following procedure.
Procedure 4-17 Write errors to a file
1 Click Save Errors/Warnings from the Monitor window.

A Confirmation window is displayed stating:
Off-Line MIB Verify operation results successfully saved.
The error file can be found in the following location:

/usr/DataGen/olm/<Network_name>/<Network_name>.result
2 Click Close to exit the OLM Verify Operation Monitor window.
3 Click Close in all subsequent windows to return to the Navigation Tree
window.
68P02900W22-S 4-49
Jul 2008
Aborting a verify network in progress Chapter 4: Operating the Offline MIB
Resolving errors
To resolve any errors found, for example, to add NE devices and parameters, refer to the section
Modifying the network configuration from the Navigation Tree on page 4-37.
Procedure 4-18 Resolve errors
1 After resolving the errors found, repeat step 3 to step 5 (from the Verify
Network procedure) to validate the modifications. If successful, the
Operation Status field in the OLM Verify Operation Monitor window
should display the status Operation successful for all NEs.
2 Click Close in this window and in all subsequent windows to return to the
Aborting a verify network in progress
As soon as a verify NE database operation commences, the details are displayed in the Offline
MIB Verify Operation Monitor window.
To abort a verify operation that is in progress, perform the following procedure.
Procedure 4-19 Abort a verify network in progress
1 Refer to the Verify network procedure (Procedure 4-16) and follow step 1
to step 5. The Offline MIB Verify Operation Monitor window is then
displayed (refer to Figure 4-23).
2 Click the Abort button. A Confirmation window is displayed.
3 Click OK to confirm the action and close the window. The Offline MIB
Verify Operation Monitor window is updated. The details in the
Operation Status field change to Operation aborted for NEs that are not
already verified.
4-50 68P02900W22-S
Jul 2008
System Information: DataGen Saving a network
Saving a network
To save the entire network, perform the following procedure.
Procedure 4-20 Save a network
1 Refer to the procedure Verify network (Procedure 4-16) and

repeat step 1 to step 4. If the save is successful, the Offline MIB
Database Operations window is displayed (refer to Figure 4-22).
If the save is not successful, a Binary Database error and warnings
window, detailing the location and errors found, is displayed similar to
that is shown in Figure 4-24. Click the View More Details button to see
detailed information for each site and cell affected. Click the Don't Save
NE button to display the Offline MIB Save Operation Monitor window
without saving the NE.
2 Click the Save NE Database button to save the NE database. The Offline
MIB Save Operation Monitor window is displayed as in Figure 4-25. This
contains a list of all the NE names and the status of the saved NE(s).
Figure 4-25 Offline MIB Save Operation Monitor window
NOTE
Do not deploy a saved network without first carrying out a verify
procedure.
68P02900W22-S 4-51
Jul 2008
Aborting a save network in progress Chapter 4: Operating the Offline MIB
Aborting a save network in progress
As soon as a save NE database commences, the details are displayed in the Offline MIB Save
Operation Monitor window.
To abort a save operation in progress, perform the following procedure.
Procedure 4-21 Abort a save operation
1 Refer to the procedure Saving a network, repeat step 1 to step 2. The

Offline MIB Save Operation Monitor window is displayed. Refer to
Figure 4-25.
2 Click the Abort button. A Confirmation window is displayed.
3 Click OK to confirm and close the Confirmation window. The Offline MIB
Save Operation Monitor window is then updated. The Operation Status
field displays the status Operation aborted for NEs that are not already
saved.
NOTE
For NEs that are saved, aborting does not rollback the saves
already carried out.
4-52 68P02900W22-S
Jul 2008
System Information: DataGen Deleting a network configuration in the OLM
Deleting a network configuration in the OLM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to deleting a network
It is recommended that the network configuration is archived and deleted, once the binary files
are transferred to the OMC. For details, refer to Exporting object files to the OMC Chapter 3
Operating DataGen.
Delete network configuration
To delete a network configuration, perform the following procedure.
Procedure 4-22 Delete a network configuration
1 From the DataGen main menu, select the OLM option. The Offline MIB
(OLM) Network Configurations window is displayed as shown in Figure 4-1.
2 Select the Network Configuration Name to be deleted. The selection is
highlighted.
NOTE
A network configuration can be deleted only by the owner or the
system administrator.
3 Click Delete. A Confirmation window is displayed as shown in Figure 4-26.
Figure 4-26 Delete network Confirmation window
Continued
68P02900W22-S 4-53
Jul 2008
Delete network configuration Chapter 4: Operating the Offline MIB
Procedure 4-22 Delete a network configuration (Continued)

4 Click OK. The Confirmation window closes.
The network configuration is then removed from the list and the following
information is displayed:
Database operation successfully completed

5 Click OK to close the window.
4-54 68P02900W22-S
Jul 2008
System Information: DataGen Network Expansion: overview
Network Expansion: overview

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of Network Expansion
The purpose of this feature is to support large scale network expansion in an offline
environment. This is achieved from the Navigation Tree by:
• Creating a BTS SITE by copying and pasting an existing BTS into a BSS configuration.
• Recreating a BTS within the same Intra-BSS or a different Inter-BSS.
• Deleting a BTS with its associated hardware devices and software functions in a single
operation.
• Batch and schedule Network Expansion operations to run at an appropriate time.
• Reviewing the transaction logs and maintaining a historical record of operations. It allows
the operator to progress intervened batch mode operations.
Network Expansion can be carried out either in a live environment using the OMC-R CM MIB or
in an offline environment using the OLM. Refer to the manual Installation and Configuration:
GSM System Configuration (68P02901W17) for more information on performing Network
Expansion from the OLM.
68P02900W22-S 4-55
Jul 2008
Additional OLM features Chapter 4: Operating the Offline MIB
Additional OLM features

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
List of additional tasks
Additional tasks that are carried out from the Offline MIB are:
• Using the autoclose function on page 4-57.
The Navigation Tree supports an autoclose feature. This feature controls the expanding
and closing of branches on the Navigation Tree.
• Deleting a BSS or RXCDR from the Navigation Tree on page 4-58.
It is possible to hierarchically delete a BSS or RXCDR from the Navigation Tree.
• Scheduling an audit on page 4-60.
To carry out an audit takes a considerable amount of time and where possible it is better to
schedule an audit.
• Auditing logs on page 4-67.
Audit logs provide a method of monitoring audits and also provide an audit history.
• Audit log management on page 4-72.
Audit log management can be used to automatically delete logs after a predefined period.
• Reload NE database on page 4-74.
It is possible to roll back to the previous saved version of an NE database.
• Realign a network on page 4-76.
BSS binary files can be copied to the appropriate directory in the OLM. The realign
function ensures that there is the same number of NEs in the Navigation Tree as there are
BSS binary files in the network directory.
• Compress or uncompress an OLM network on page 4-78.
It is possible from the Network configuration window under the Admin options to
compress or uncompress an offline MIB network.
4-56 68P02900W22-S
Jul 2008
System Information: DataGen Using the autoclose function
Using the autoclose function

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of autoclose feature
The Navigation Tree supports an autoclose feature. When this feature is turned on, expanding a
certain branch of a tree results in the automatic closing of any other branches that might be open
at that level. With the feature turned off, multiple branches of a tree at any given level is open.
Prerequisite
A Navigation Tree must be open and displayed on the user terminal before setting autoclose.
Procedure for using autoclose
To use the autoclose function, select View à Auto Close On/Off from the menu bar to toggle
the function. The default setting is Off.
NOTE
The autoclose function is a menu option. When selected, the alternate state is shown
in the menu window, that is, with Autoclose On selected. Autoclose Off is displayed
in the View menu.
68P02900W22-S 4-57
Jul 2008
Deleting a BSS or RXCDR from the Navigation Tree Chapter 4: Operating the Offline MIB
Deleting a BSS or RXCDR from the Navigation Tree

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to deleting BSS or RXCDR network elements
This option is used to hierarchically delete all BSS or RXCDR network elements from the OLM.
The associated binary files are also deleted from the network configuration directory.
Deleting BSS or RXCDR network elements
To delete BSS or RXCDR network elements, perform the following procedure.
Procedure 4-23 Delete BSS or RXCDR network elements
1 Select the specified BSS or RXCDR element from the Navigation Tree.
2 Select Edit à Delete from the menu bar on the Navigation Tree window (refer
to Figure 4-13). A Confirmation window as shown in Figure 4-27 is displayed.
Figure 4-27 Deleting a BSS or RXCDR - Confirmation window
Continued
4-58 68P02900W22-S
Jul 2008
System Information: DataGen Deleting BSS or RXCDR network elements
Procedure 4-23 Delete BSS or RXCDR network elements (Continued)
NOTE
• Since the OLM is performing a hierarchical delete of the NE, a

considerable delay may occur.
• A network can be selected and deleted from the Network
configuration selection window (Figure 4-1). Deleting
the network is faster than deleting individual NEs from the
Navigation Tree.
3 Click OK to continue. An Information window is displayed stating that the
operation was completed successfully.
4 ClickOK to return to the Navigation Tree.
68P02900W22-S 4-59
Jul 2008
Scheduling an audit Chapter 4: Operating the Offline MIB
Scheduling an audit
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
List of procedures
The procedures that can be performed using the Audit Scheduler Admin Option are:
• Scheduling an audit
• Modifying a scheduled audit
• Deleting a scheduled audit list
Creating a scheduled audit
To schedule an audit, perform the following procedure.
Procedure 4-24 Create a scheduled audit
1 Select the Admin icon from the Front Panel to display the Admin Options
window (Figure 4-28).
Continued
4-60 68P02900W22-S
Jul 2008
System Information: DataGen Creating a scheduled audit
Procedure 4-24 Create a scheduled audit (Continued)
Figure 4-28 Admin Options window
2 Select the Audit Scheduler option. The selection is highlighted in black.
Continued
68P02900W22-S 4-61
Jul 2008
Creating a scheduled audit Chapter 4: Operating the Offline MIB

3 Click OK. The Audit Scheduler window, is shown in Figure 4-29. This
contains a list of all scheduled audits, detailing their Scheduled Item, Status,
Deferred Time, Start Time, End Time, Interval, Execute Mode, Update
Mode, and Operator.
Figure 4-29 Audit Scheduler window
Continued
4-62 68P02900W22-S
Jul 2008
System Information: DataGen Creating a scheduled audit

4 To create an audit, select Edit à Create from the Audit Scheduler window.
The auSchedule Detailed View <create> window is displayed as in
Figure 4-30.
Figure 4-30 auSchedule Detailed View <Create> window
Continued
68P02900W22-S 4-63
Jul 2008
Creating a scheduled audit Chapter 4: Operating the Offline MIB

5 To insert the elements to be audited, click the Scheduled Element button.
The network Navigation Tree window is displayed.
6 Select the Network Element(s) to be audited in the usual way. For more
information about using the Navigation Tree, refer to Moving levels on a
Navigation Tree on page 4-30.
NOTE
It is valid to select either BSS, RXCDR, SITE, PCU, or the entire
network to be audited.
7 Select Config Mgt à Audit. The Navigation Tree window closes and the
selected element is displayed in the Scheduled Element Name field.
Entering schedule information
Enter schedule information in the Detailed View window as described in the procedure.
Procedure 4-25 Enter information in the Detailed View window
1 Only the Start Time field needs to be specified for one shot auditing. Click
the parameter that requires changing. The selected parameter is highlighted
in black. The parameters are ordered as follows: Month/Day/Year
Hour:Minute:Second
NOTE
Ensure that the Execute Mode is Oneshot.
Use the up/down arrow symbols to the right of the Start Time field to
change the parameter to the required value.
2 Verify that the Update Mode field is Apply to OMC.
If not, click the Execute Mode button. Hold the left mouse button down, and
scroll to Apply to OMC. Once this is highlighted, release the mouse button.
The selected option is then displayed in the Detailed View.
Continued
4-64 68P02900W22-S
Jul 2008
System Information: DataGen Modifying a scheduled audit
Procedure 4-25 Enter information in the Detailed View window (Continued)

3 Select the audit type to be performed by selecting
either the Full Audit or Per Site Audit option.
If the Per Site Audit option is selected, the available options in the Per
Site Audit Logging field are:
• List All Sites
• List Audited Sites
• List Unaudited Sites
NOTE
When the selected audit type is Full Audit, the Per Site Audit
Logging field is unavailable.
4 Verify that the Neighbor Propagation after Audit field is No unless
neighbor propagation after audit is required.
5 Once all the above information is entered into the Detailed View, select File à
Create from the menu bar. The new Scheduled Audit is created and can be
viewed in the Audit Scheduler window.
6 Close the Detailed View window by selecting File à Close from the menu
bar.
7 Close the Audit Scheduler window by selecting File à Close from the
menu bar.
Modifying a scheduled audit
All the limitations that apply to auditing also apply when modifying a scheduled audit. For more
information, refer to Procedure 4-24 Creating a scheduled audit.
To modify a scheduled audit, perform the following procedure.
Procedure 4-26 Modify a scheduled audit
1 Open an Audit Scheduler window. The Audit Scheduler window is

Continued
68P02900W22-S 4-65
Jul 2008
Deleting a scheduled audit Chapter 4: Operating the Offline MIB
Procedure 4-26 Modify a scheduled audit (Continued)

2 Select the audit to be modified. The selection is highlighted in black.
3 To open this audit for modification, select Edit à Detailed View from the
Audit Scheduler window. The auSchedule Detailed View window is
4 Select Edit à Edit from the menu bar. The Detailed View can now be edited.
The File à Revert option can be used before saving an edited auSchedule
Detailed View to return all changed fields to their previous state.
NOTE
It is not possible to revert to a previous version after an edited
version has been saved.
5 When all the required fields are changed, select File à Save from the menu
bar.
6 Close the Detailed View by selecting File à Close from the menu bar. The
modified Scheduled Audit can be viewed in the Audit Scheduler window.
menu bar.
Deleting a scheduled audit
Expired Scheduled Audits must be deleted from time to time to avoid using excess memory.
To delete a scheduled audit, perform the following procedure.
Procedure 4-27 Delete a scheduled audit
1 Refer to Procedure 4-24 Creating a scheduled audit and perform step 1 to

step 3. The Audit Scheduler window is displayed as in Figure 4-29.
2 Select the audit to be deleted.
3 Select Edit à Delete from the Audit Scheduler window. A Confirmation
window is displayed.
4 Click OK. The Scheduled Audit closes and the message Element Deleted is
displayed in the status bar.
menu bar.
4-66 68P02900W22-S
Jul 2008
System Information: DataGen Auditing logs
Auditing logs
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
List of procedures
The procedures that can be performed using the Audit Logs Admin Option are:
• Viewing an audit log list.
• Aborting an audit in progress.
• Viewing an audit inconsistency report.
• Deleting an audit log.
Viewing an audit log list
After an audit has taken place, information relating to this audit is placed in an audit log.
This information can be accessed and printed.
To view an audit log list, perform the following procedure.
Procedure 4-28 Viewing an audit log list
1 Select the Admin icon on the Front Panel to display the Admin Options
window (Figure 4-28).
NOTE
It is also possible to view the audit logs from the Navigation Tree
by selecting Config Mgt à Audit Logs from the menu bar.
Continued
68P02900W22-S 4-67
Jul 2008
Aborting an audit in progress Chapter 4: Operating the Offline MIB
Procedure 4-28 Viewing an audit log list (Continued)

2 Select Audit Logs option, then click OK. The Audit Logs window is
displayed. Refer to Figure 4-31. This contains a list of all completed audits,
detailing the Audited Item, Status, Reason, Actual Start Time, Actual
End Time, Update Mode, Operator, and Warning for NE Apply.
Figure 4-31 Audit Logs window
3 Close the Audit Logs window by selecting File à Close from the menu bar.
Aborting an audit in progress
As soon as a Scheduled Audit begins (see Scheduling an audit on page 4-60), the progress
details are displayed in the Audit log list.
To abort an audit in progress, perform the following procedure.
Procedure 4-29 Abort an audit in progress
1 Refer to the Viewing an audit log procedure (Procedure 4-28) and follow
step 1 and step 2 to open the Audit Logs window.
2 From the Audit Log list, select the audit to be aborted.
NOTE
The Status of an audit in progress is displayed as Active in the
Audit Log list.
Continued
4-68 68P02900W22-S
Jul 2008
System Information: DataGen Inconsistency reports
Procedure 4-29 Abort an audit in progress (Continued)

3 Select Options à Abort from the menu bar. A Confirmation window is
Figure 4-32 Audit Logs Abort Confirmation window
4 Click OK. The Confirmation window closes and the Audit Log list is updated.
The Status of the audit is now changed to Aborted.
5 Select File à Close from the menu bar to close the Audit Log window.
Inconsistency reports
After an audit has taken place, information relating to this audit is placed in an Audit Log.
Any inconsistencies found between the NE and OLM configuration database are placed in an
Inconsistency List. This information can be accessed and printed.
There is a distinction between an Audit Log, which is a general information message generated
as the outcome of an audit, and an Audit Inconsistency Report, which is a further extension to
show any inconsistencies discovered during an audit in a more detailed form.
Viewing an audit inconsistency report
To view an Audit Inconsistency report for a particular Scheduled Audit, perform the following
procedure.
Procedure 4-30 View an Audit Inconsistency report
step 1 and step 2. The Audit Logs window is displayed as in Figure 4-31.
Continued
68P02900W22-S 4-69
Jul 2008
Viewing an audit inconsistency report Chapter 4: Operating the Offline MIB
Procedure 4-30 View an Audit Inconsistency report (Continued)

2 From the Audit Log list, select the audit from which any inconsistencies
should be viewed. The selected audit is highlighted.
NOTE
An Audit Inconsistency report is valid only for an audit with a
Status of either Finished or Applied.
3 Select File à Open from the menu bar. An Audit Inconsistency List
window is then displayed (refer to Figure 4-18), detailing all elements where
inconsistencies were found during the audit. Information is displayed for
each reported inconsistency or error as in Table 4-2.
4 Select File à Close from the menu bar to close the Audit Inconsistency
report.
Table 4-2 Reported inconsistencies or errors
Column Identifies
Object Name The name of the configurable device.
Object Class The class (or type) of the configurable device.
Record Type Whether this record is reporting an inconsistency or an error,
and what type of inconsistency it is, if applicable.
The Record Type can be one of:
• Object Not at OMC
• Object Not at NE
• Attribute Differs
• Error Report
Apply Status The status of an attempted update to the system to remove an
inconsistency, or error indicates the error detected by the audit.
If an inconsistency is reported and an Apply to OMC or Apply
to NE operation is performed, this column indicates the result
of the operation. This can be Success or Failure. If an apply
operation is not attempted, this field is blank.
If an error is reported, this column describes the error.
Warning for NE The type of warning given when inconsistencies applied to a
Apply network element fail.
Attribute Name The name of the attribute that is inconsistent, if applicable.
Continued
4-70 68P02900W22-S
Jul 2008
System Information: DataGen Deleting an audit log
Table 4-2 Reported inconsistencies or errors (Continued)

Column Identifies
OMC Attr Value The value of the attribute at the OMC, if applicable.
NE Attr Value The value of the attribute at the NE, if applicable.
Reason The reason why an inconsistency fails to be applied, if
applicable.
Deleting an audit log
To delete an audit log, perform the following procedure.
Procedure 4-31 Delete an audit log
step 1 and step 2. The Audit Logs window opens on the screen as in
Figure 4-31.
2 Select the Audit Log to be deleted. The selection is highlighted.
3 Select Edit à Delete from the menu bar. Select Edit à Delete All to delete
all the logs. A confirmation of deletion window is displayed.
4 Click OK. The Confirmation window closes and the selected audit log is
removed from the list.
5 Close the Audit Logs window by selecting File à Close from the menu bar.
68P02900W22-S 4-71
Jul 2008
Audit log management Chapter 4: Operating the Offline MIB
Audit log management

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of audit log management
The Audit Log Management Admin option is used to delete audit logs after a predefined
period. This period is configurable between zero and seven days.
Audit logs can also be deleted manually. Refer to the procedure Deleting an audit log for
more information.
Setting the delete period
The operator is required to set the number of days for retaining the audit log files, after
which the OMC automatically deletes the files. If set to zero all the audit logs, except the
current one, are deleted.
To set the delete period, perform the following procedure.
Procedure 4-32 Set the delete period
1 Select the Admin icon on the Front Panel to open the Admin Options
window as in Figure 4-28.
2 Select the Audit Log Management option, then click OK.
The Audit Log Management window is displayed. Refer to Figure 4-33.
Figure 4-33 Audit Log Management window in Edit mode
Continued
4-72 68P02900W22-S
Jul 2008
System Information: DataGen Setting the delete period
Procedure 4-32 Set the delete period (Continued)

3 Select Edit à Edit from the menu bar.
4 Enter the number of days after which the log is to be deleted.
5 Select File à Save from the menu bar to save the change. The following
message is displayed in the status bar at the foot of the window:
Save completed
NOTE
To quit without saving, select File à Close. A Message window
displays the following:
There have been changes since you last saved. Pressing

OK will exit your current interface without saving.
6 Select File à Close to close the window.
68P02900W22-S 4-73
Jul 2008
Reload NE database Chapter 4: Operating the Offline MIB
Reload NE database
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to reloading an NE database
If changes are made to the network and the user wishes to return to a previous saved version of
the NE database, then Reload from the Offline MIB can be carried out.
Procedure for reloading an NE database
NOTE
If multiple NEs are changed, for example if an RF import, Cell or neighbor
propagation is carried out, then all the affected NEs must be included in the roll back.
To reload a previously saved version of an NE database, perform the following procedure.
Procedure 4-33 Reload an NE database
1 Refer to the procedure Verify and save NE database on page 4-43 and repeat
step 1 to step 4. The NE is selected.
2 Select Offline MIB à Reload NE Database from the menu bar on the
Navigation Tree. A Confirmation window is displayed as in Figure 4-34.
Figure 4-34 Reload Confirmation window
Continued
4-74 68P02900W22-S
Jul 2008
System Information: DataGen Procedure for reloading an NE database
Procedure 4-33 Reload an NE database (Continued)

3 Click OK to confirm the reload. The progress of the reload
NE Database is shown in the status bar at the bottom of the
Navigation Tree window. An Information window is displayed as:
Updating the OMC CM MIB - View Audit Log or inconsistency List's

Status Column for Completion: <NE_Name>
4 Click OK.
5 To monitor the status of the audit, select Config Mgt à Audit Logs from
the menu bar.
6 From the audit log list, monitor the audit until it shows a Finished status.
68P02900W22-S 4-75
Jul 2008
Realign a network Chapter 4: Operating the Offline MIB
Realign a network
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The realign function is a shortest method of putting BSSs and RXCDRs into a network
configuration. This is done from the Navigation Tree. Refer to Creating a BSS/RXCDR from the
Navigation Tree on page 4-32 for details. However, it is possible to copy NE binary files from a
tar tape or through ftp into the appropriate configuration directory in the OLM.
The realign function ensures that there is the same number of NEs in the MIB, as there are
BSS binary files in the configuration directory.
The following cases apply (refer to Table 4-3).
Table 4-3 Realign a network - cases
BSS Binary files Result

Action Required
(configuration directory) (MIB)
Add Shell NEs added Audit network
Replace NEs updated Reload database
Remove NEs deleted
NOTE
It is not possible to continue working on the network when a realign is in progress.
Procedure for realigning a network
To realign a network, perform the following procedure.
Procedure 4-34 Realign a network
1 Create a network configuration. Refer to Starting/creating a network

configuration in the OLM on page 4-6 for details.
2 Open the network configuration. Refer to Starting/exiting the OLM GUI on
page 4-9 for details.
3 Open a Navigation Tree using the Config Mgmt icon. Refer to Opening and
closing a Navigation Tree on page 4-28 for details.
Continued
4-76 68P02900W22-S
Jul 2008
System Information: DataGen Procedure for realigning a network
Procedure 4-34 Realign a network (Continued)

4 Open an Xterm window and copy the BSS binary files to:
/usr/omc/DataGen/olm/<network configuration name>
NOTE
The network configuration name is that created in step 1 above.
5 Select the network node and select Offline MIB à ReAlign Network from
the menu bar.
The message ReAlign Operation successful is displayed in the status bar
at the bottom of the Navigation Tree window when no errors are present.
An Information window is displayed as shown in Figure 4-35.
6 Click OK to return to the Navigation Tree window.

7 If new NEs have been added, then carry out an audit on the network. Refer
to Running an audit from the Navigation Tree on page 4-35 for details.
If NE binary files have been replaced, carry out step 8.
8 Select the NE and do a reload from the Offline MIB pull down menu. Refer
to Reload NE database on page 4-74. Reload NE database for details.
68P02900W22-S 4-77
Jul 2008
Compress or uncompress an OLM network Chapter 4: Operating the Offline MIB
Compress or uncompress an OLM network

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of compress and uncompress
It is possible to compress or uncompress an Offline MIB network from the OLM Network
Configurations window using the Admin options. All the binary files located in the selected
network configuration directory will be compressed or uncompressed.
When starting the OLM from the DataGen main menu, all compressed files are automatically
uncompressed. The compress function can be used when disk space is an issue.
NOTE
It is better to archive and delete old network configurations when the binary files are
transferred to the OMC.
Compress a network procedure
To compress a network, perform the following procedure.
Procedure 4-35 Compress a network
1 Open the OLM Network Configurations window (Figure 4-1) from the
DataGen main menu. Refer to Starting/creating a network configuration
in the OLM on page 4-6 for details.
2 Select the network configuration name from the list on the OLM Network
Configurations window. The selection is highlighted in black as in
Figure 4-36.
Continued
4-78 68P02900W22-S
Jul 2008
System Information: DataGen Uncompress a network procedure
Procedure 4-35 Compress a network (Continued)

3 Select Admin à Compress from the menu bar. A Confirmation window
is displayed.
Figure 4-36 Compress from the OLM Network Configurations

window
4 Click OK to continue or Cancel to abort.
Uncompress a network procedure
To uncompress a network without restarting the OLM from the DataGen front panel, perform
the following procedure.
Procedure 4-36 Uncompress a network
1 Refer to the Compress procedure and follow step 1 to step 2.

2 Select Admin à Uncompress from the menu bar. A Confirmation window
is displayed.
3 Click OK to continue or Cancel to abort.
68P02900W22-S 4-79
Jul 2008
Troubleshooting the OLM Chapter 4: Operating the Offline MIB
Troubleshooting the OLM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to troubleshooting the OLM
If the OLM does not function, refer to the information in Table 4-4 to Table 4-8 which details
errors that can occur and how to resolve them.
To investigate potential problems, perform the following procedure.
Procedure 4-37 Troubleshooting the OLM
1 Check the omcaudit file which is located in

/usr/omc/logs/omcaudityyyymmdd. If a problem occurs, the messages
are stored in the omcaudit file.
2 Refer to Table 4-4 to Table 4-8 for information on error messages and the
appropriate actions to be taken.
OLM fails to start
If the OLM fails to start, Table 4-4 shows the possible error messages that are displayed and
the appropriate action to be taken.
Table 4-4 OLM fails to start
Error/Warning Explanation Action

msgctl call failed The maximum message size Check using sysdef -i to verify
with main message and maximum bytes per value. Put in original values.
queuemsgget call failed queue is specified during the Reboot and open the network.
with main message queue DataGen install. These kernel
parameters should not be
altered.
It is not known what The size of the BSS binary Check file size of BSS binary file
BSS software version file is not specified in: and contact your local support
BSS Binary file /usr/omc/config/OLM.CNFG office.
<BSS_Name is>.
Continued
4-80 68P02900W22-S
Jul 2008
System Information: DataGen Database errors
Table 4-4 OLM fails to start (Continued)

Error/Warning Explanation Action
All copies of the If there is a heavy load on the Edit OLM.CNFG file and
ported BSS software system it may be necessary to increase the number for
have not started up in increase the start up time in NMASECM_WAIT_SECS
the allotted time. /usr/omc/config/OLM.CNFG parameter. Exit and restart
or the OLM. Refer to the
BSS binary file is corrupt. procedure Starting/exiting
the OLM GUI on page 4-9.
Recompile to create
a BSS binary file and
replace the existing one.
Open the network.
Failed fork to run The maximum number of Check using sysdef -i to verify
NmaseCm code. processes that can be run is value. Put in original value.
specified during the DataGen Reboot and open network.
install. This kernel parameter
should not be altered.
Problem accessing The administrator must Log in as omcadmin. From the
DataGen INFORMIX grant the user the connect command line invoke DGAdmin
database sql code -387: permission. by typing DGAdmin and enter
no connect permission the following command:
tp -u <username>
Database errors
Table 4-5 shows the error messages that are displayed and the appropriate actions to be taken.
Table 4-5 Database Errors
Error/Warning Action
Invalid NE To correct the error, carry out the following actions:
failed to open database
<Network name> sql error • Reinitialize the database. Refer to the procedure
<Number> Reinitialize database procedure on page 4-85.
Network name is <Name> it • Audit the network. Refer to the procedure Running
should be <Network Name> an audit from the Navigation Tree on page 4-35.
There is more than one
Network in this database
Rose message received from
an NE when only start up
messages expected
Continued
68P02900W22-S 4-81
Jul 2008
General errors Chapter 4: Operating the Offline MIB
Table 4-5 Database Errors (Continued)

Rejecting message because
unable to route message to
NE
Unable to route message to —
<BSS NAME>
Message from BSS with key
<number>rejected BSS unknown
NE %s in Binary directory Revert to the previously saved version of the NE database.
and in MIB do not have the Refer to Reload NE database on page 4-74 for details.
same software version and/or
type (BSS/RXCDR)
Unable to route message Check the version of BSS binary files as specified in
because NE is unknown. /usr/omc/config/OLM.CNFG and contact your local
support office.
NE %s is in MIB, not in BSS Contact your local support office.
Binary directory
NE %s is in BSS Binary Contact your local support office.
directory, not in MIB
General errors
Table 4-6 shows the error messages that are displayed and the appropriate actions to be taken.
Table 4-6 General operating errors
The number of Users in To correct the errors, carry out the following actions:
the Network Configurations
list is set to non-zero • Reset the number of users to zero. Refer to the
even though there procedure Force shutdown OLM in this section.
is no OLM GUI open.
The GUI hangs • Audit the network. Refer to the procedure Running
an audit from the Navigation Tree on page 4-35.
SMASE channel has been To correct the errors, carry out the following actions:
deleted.
OlmOmcInit channel has been • Force shutdown the OLM. Refer to Procedure 4-38
deleted Force a shutdown of the OLM on page 4-84 in this
section.
Unable to read from IPC
channels • Open the network. Refer to the procedure
Starting/exiting the OLM GUI on page 4-9.
4-82 68P02900W22-S
Jul 2008
System Information: DataGen Specific operation fails
Specific operation fails
If a specific task fails, Table 4-7 shows the error messages that are displayed and the appropriate
actions to be taken.
Table 4-7 Specific operation error
Fatal Off-Line MIB Operation To correct the error carry out the following actions:
Error
• View the audit log. Refer to the procedure Auditing
logs on page 4-67.
• Exit and restart the OLM. Refer to the procedure

Starting/exiting the OLM GUI on page 4-9.
Import errors
Table 4-8 shows the possible error that can occur and the appropriate actions to be taken
while importing the NE binary files.
Table 4-8 Importing NE software errors
Transaction timeout To correct the errors, carry out the following actions:
Link OOS
• Revert to the previously saved version of
Ported BSS S/W for <BSS Name> the NE database. Refer to the procedure
has not started Reload NE database on page 4-74.
msgsnd call failed for NE <BSS
Name>. or
msgrcv call failed for msg Q

msgget call failed with key • Exit and restart the OLM. Refer to the procedure
<number> for BSS <BSS Name>. Starting/exiting the OLM GUI on page 4-9.
Unable to route message to <BSS

Name> because ported BSS SW is
not started.
Introduction to the force shutdown feature
Force shutdown OLM function should be carried out only when the OLM is not functioning
correctly. This function shuts down the Offline MIB and resets the number of users to zero for
the network configuration.
68P02900W22-S 4-83
Jul 2008
Force shutdown OLM procedure Chapter 4: Operating the Offline MIB
NOTE
Any changes that are done since the last save was carried out are lost. The system
administrator, the person who created the network configuration or the first user to
launch the OLM network can carry out this task.
Force shutdown OLM procedure
To shut down the OLM and reset the number of users to zero for the network configuration,
perform the following procedure.
Procedure 4-38 Force a shutdown of the OLM
1 From the DataGen main menu, select the OLM option. The Offline MIB (OLM)
Network Configurations selection window is displayed. Refer to Figure 4-1.
2 Select the required network configuration name from the OLM Network
Configuration list. The selection is highlighted in black.
3 Select Admin à Force shutdown from the menu bar. A Confirmation
window is then displayed as in Figure 4-37.
Figure 4-37 Confirmation window
4 Click OK. The following message is displayed in an Information window:

Database operation successfully completed.
5 Click OK. The column Users in the Network configuration window is reset to
zero for the network.
NOTE
On opening the network, carry out an audit. Refer to Running an audit
from the Navigation Tree on page 4-35 for details.
4-84 68P02900W22-S
Jul 2008
System Information: DataGen Reinitialize database procedure
Reinitialize database procedure
The reinitialize function should be carried out only when the database has become corrupt. This
function shuts down and deletes all audited information in the Offline MIB.
NOTE
Only the person who created the network configuration, or the system administrator
can carry out this task.
To reinitialize the network database, perform the following procedure.
Procedure 4-39 Reinitialize the network database
1 Refer to Force shutdown OLM and perform step 1 and step 2. The OLM
Network Configurations window opens and the network is selected.
2 Select Admin à Reinitialize Database from the menu bar. A Confirmation
window is displayed as in Figure 4-38.
Figure 4-38 Reinitialize DataBase - Confirmation window
3 Click OK. The message Database operation successfully completed is

displayed in an Information window.
4 Click OK to close the window.
NOTE
On opening the network, it is seen that all the information that was
audited is lost. It is necessary to carry out a complete audit on the
shell NEs. Refer to Running an audit from the Navigation Tree on
page 4-35 for details.
68P02900W22-S 4-85
Jul 2008
Reinitialize database procedure Chapter 4: Operating the Offline MIB
4-86 68P02900W22-S
Jul 2008
Chapter
Command line tools

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02900W22-S 5-1
Jul 2008
Overview of command line tools Chapter 5: Command line tools
Overview of command line tools

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Command line functions
There are several software tools available for use in association with DataGen which are not
part of the Graphical User Interface (GUI), which can be accessed either from the GUI or the
command line.
Table 5-1 shows the user tools available for command line operation.
Table 5-1 Command line tools
Command line tools

Command name Invoked with Use Command line
or GUI
Auto-compile MMI scripts auto_compile Compile a number of MMI Both
scripts
Auto-revgen binary files auto_revgen Revgen a number of binary Both
files
Auto-upgrade binary files auto_upgrade Upgrade a number of Both
binary files
Copy Area ca Copies a BSS area to a new Both
configuration
MMI Combiner combine Combine GSM MMI Command line
command files
Compile MMI script compile Compile MMI scripts Both
Compress/ uncompress cpdb Compress or uncompress Both
.002 files the binary object files
Delete Database Object del Delete a DataGen BSS area Both
MCDF filters filter Export or import or validate Both
MCDF files.
MMI Command Generator gcmd Generates BSS command Both
file(s)
Dbaccess command dbaccess Optimize DataGen database Command line
Continued
5-2 68P02900W22-S
Jul 2008
System Information: DataGen General information
Table 5-1 Command line tools (Continued)

Command line tools
Command name Invoked with Use Command line
or GUI
Lock/Unlock BSS area lock_adm Locks or unlocks a BSS Command line
area
Revgen Command revgen Generate MMI files from Both
CM database objects
Toggle Permissions tp Toggle database Command line
permissions for a user
Version Upgrader upg Copies a BSS area to Both
a new configuration,
and upgrades the new
configuration
Country Administration xcadm Create new Country Both
(CADM) and Network files in the
DataGen database
General information
Most command line tools require that DGAdmin be run before they can be invoked, using the
following command:
DGAdmin
This command sets the user environment for DataGen. DGAdmin sets system variables in the
current environment to allow DataGen tools to function correctly. It changes the current prompt
to indicate that the environment has been set up for use with DataGen.
User options
There is a user option to display values in either Hexadecimal or Decimal (default) format.
Before starting DataGen, two variables must be set to allow MMI scripts to display GSM Cell
IDs, OPCs and DPCs in Hex.
Procedure
• Open an Xterm window and, if using the Bourne Shell (sh) interpreter, execute the
following commands:
DG_HEX_CELL_IDS=yes ; export DG_HEX_CELL_IDS

DG_HEX_POINT_CODES=yes ; export DG_HEX_POINT_CODES
• Open an Xterm window and, if using the C shell interpreter, execute the following
commands:
setenv DG_HEX_CELL_IDS yes

setenv DG_HEX_POINT_CODES yes
68P02900W22-S 5-3
Jul 2008
Copy Area (ca) command Chapter 5: Command line tools
Copy Area (ca) command

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Name
ca - Copies area.
Synopsis
ca -source <country name>:<BSS area name>:<configuration number> [-area <new BSS

area name> [-id <new BSS area id>]] [-config <new configuration number>] [-title
“<new/open Area comment>"]
See Table 5-2 for option descriptions.
Description
This utility allows a BSS area to be copied to a new configuration, or act as the basis with which
to generate a new BSS area at a given configuration. If no configuration number is specified for
the new configuration, the next available configuration number is used.
Command line options
An explanation of the command line options is given in Table 5-2.
Table 5-2 Command line options (ca command)
Option Description
<country name> The country name containing the objects.
<BSS area name> The BSS name for the original objects.
<configuration number> The configuration number of the BSS containing the
objects.
-area <new BSS area name> Define a new BSS area.
-id <new BSS area id> Define a BSS area id for the new area.
-config <new configuration Define a new configuration.
number>
-title <new configuration title The comment entered when creating the BSS area.
string>
5-4 68P02900W22-S
Jul 2008
System Information: DataGen Requirements
Requirements
Run DGAdmin before executing the copy command. Any parameters that contain spaces must
be entered between single quotes.
Output
Output from Copy Area utility is the insertion of a new BSS area configuration, or a new BSS
area in the DataGen database. The screen output informs the user of the Copy Area operation
and completion.
If the user opens the table controller screen for the new area created by the ca command,
all of the columns are blank. The File and Report columns are blank as the ca utility only
copies the database entry and not the input tables. The Validate and Insert columns are blank
because the records associated with the original database entry holding this information are
specifically excluded from the copy.
Example Copy Area usage
The Copy Area utility ca works from the command line. The following command line can be
customized to perform the required copy:
ca -source UK:Area10:0
NOTE
This example does not have a title string. By default, a comment is created for the
target area:
Copied from BSS area: <BSS Area> <Configuration No>
This copies configuration 0 of Area 10 to the next free configuration number within Area10.
To copy configuration 0 of area 10 to a new area and add the comment copy of Area 10, a
command of the following type must be used:
ca -source UK:Area10:0 -area Area11 -title “copy of Area 10"
NOTE
The next free configuration number in Area 11 is used and, if Area 11 does not exist,
it is created.
68P02900W22-S 5-5
Jul 2008
MMI Combiner (combine) command Chapter 5: Command line tools
MMI Combiner (combine) command

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Name
combine - Combines GSM MMI command files.
Synopsis
combine
Description
This utility generates a combined GSM MMI command file by combining the GSM MMI
command files under the command directory (generated by gcmd) when run under the BSS
area directory path.
Output
Output from the script is in the form of a combined GSM MMI command file, located under the
command directory and named COMBINED.
Example
To create an MMI script file, run the following command:
cd \<country>\<bss area>\<config no>\command combine
This generates an MMI script file called COMBINED.
NOTE
Each time a combined script is generated the original script is backed up with a Date
and Time stamp. For example, COMBINED.BACKUP072498123425.
Requirements
Run DGAdmin before executing the compile command.
5-6 68P02900W22-S
Jul 2008
System Information: DataGen Compile MMI script (compile) command
Compile MMI script (compile) command

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Name
compile - Compiles MMI script.
Synopsis
compile -C <country> -v <Version> <filename>
Where Is
country name of the country where the options object is located.
Version software version to compile with (1.7.6.0 or 1.8.0.0 or 1.9.0.0).
filename name of script file to compile.
Description
This utility allows an MMI script to be converted into a CM database object (binary object)
file. It outputs a binary object file and a report file and places them in the directory where
the script was run.
Example
The following is an example of using the compile command:
compile -C Austria -v 1.9.0.0 BSS_scr
The following files are generated on successful compilation:

• BSS_scr.002
• BSS_scr.rep
If the compilation fails, only the report file (.rep) is generated and this can be used to determine
the error.
Requirements
Run DGAdmin before executing the compile command.
68P02900W22-S 5-7
Jul 2008
Auto-compile MMI script command Chapter 5: Command line tools
Auto-compile MMI script command

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Name
auto_compile - Batch compiling of multiple MMI scripts.
Synopsis
auto_compile -C <Country> -v <Version> <filename or *>
Description
This utility allows a number of MMI scripts to be compiled sequentially. The software version
of the scripts must be the same and the correct compiler version must be selected. After
a successful compilation, the resultant binary and report files are created in the directory
where the scripts reside.
Table 5-3 Command line options (auto_compile command)
Option Description
-C <Country> The -C option identifies the country in which to insert the BSS
record.
-v <Version> The software version for compilation.
<filename or *> Define a directory where the scripts reside or a single MMI script.
Requirements
Run DGAdmin before executing the auto_compile command.
Any parameters that contain spaces must be entered between single quotes.
5-8 68P02900W22-S
Jul 2008
System Information: DataGen Output
Output
Output from the auto_compile utility is a batch logfile. This shows each operation of the batch
process and any relevant report file created along with its path. The result of each compile,
successful or not, appears in the logfile.
Once the batch process is complete the final message in the log file states:
BATCH COMPLETED
The batch file resides in the directory of the original binaries.
Example auto_compile usage
The auto_compile utility works from the command line. The following command line can be
customized to perform the required batch compile:
auto_compile -C Austria -v 1.9.0.0 ~/scr_objs/1900x/*
This compiles all existing MMI scripts in the specified directory using the corresponding 1900
compiler. On successful completion, the report files and binaries reside in the chosen batch
directory.
Running cron jobs
A cronjob can be set up to schedule the running of auto_revgen or auto_compile or auto

_upgrade batch jobs. If cronjobs are set up, then the specific path for the DGAdmin executable
and the auto_revgen or auto_upgrade or auto_compile scripts must be entered along with
the files to be run through the batch process.
For example, when setting up a crontab file, cron, containing an auto_revgen cronjob to be run
at 10.20 a.m. every day, the cron file should contain the following:
20 10 * * * /usr/omc/DataGen/bin/DGAdmin
/usr/omc/DataGen/current/bin/auto_revgen -m -d -C
Austria -v 1.9.0.0 -c 0 /usr/omc/test/1900x/objects/*
NOTE
The complete path for DGAdmin, batch process, and the location of the binary files
must be entered.
To run the cronjob job, log on to the DataGen processor as omcadmin and enter the following
command:
crontab cron
To check the status of the cronjob, enter the following command:
crontab -l
68P02900W22-S 5-9
Jul 2008
Compress/uncompress binary object files Chapter 5: Command line tools
Compress/uncompress binary object files

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Name
cpdb -c - compress 1760, 1800 or 1900 binary object (.002) files.
cpdb -u - uncompress 1760, 1800 or 1900 binary object (.002) files.
Synopsis
Compress
cpdb -c <database object filename> <compressed object filename>
Where Is
database object filename name of the .002 file to compress
compressed object filename the name of the compressed file
Uncompress
cpdb -u <database object filename> <uncompressed object filename>
Where Is
database object filename name of the compressed .002 file to
uncompress
uncompressed object filename the name for the uncompressed file
Description
The above command allows binary object files to be compressed or uncompressed from the
command line. Revgen converts the binary object file into a DataGen script file. Revgen can
use both compressed and uncompressed binary object files.
5-10 68P02900W22-S
Jul 2008
System Information: DataGen Example
Example
The following are two examples of using the compress and uncompress commands:
• cpdb -c BSS.002.uncompressed BSS.002.compressed
This compresses the file named BSS.002.uncompressed and names it

BSS.002.compressed.
• cpdb -u BSS.002.compressed BSS.002.uncompressed
This uncompresses the file named BSS.002.compressed and names it

BSS.002.uncompressed.
Requirements
Run DGAdmin before executing the compress or uncompress command.
68P02900W22-S 5-11
Jul 2008
Delete database object (del) command Chapter 5: Command line tools
Delete database object (del) command

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Name
del - Delete database object.
Synopsis
del <verification> <country> <BSS area> <configuration number>
Description
This utility deletes a DataGen BSS Configuration area.
NOTE
After the last Configuration area has been deleted, the BSS Area is also deleted.
Table 5-4 Command line options (del command)
Option Description
<verification>
• Off (0) performs action.
• On (1) verifies action without performing it (displays a

list with the number of rows that can be deleted from the
database).
<country> The country name.
<BSS area> The BSS name.
<configuration number> The configuration number of the BSS area.
The deletion must be specified to the <verification> <country> <BSS area> <configuration
number> level.
5-12 68P02900W22-S
Jul 2008
Example
The following is an example of how to use the delete command:
del 0 Austria Area10 0
where configuration number 0 is deleted from the Country (Austria) and BSS area (Area 10).
Requirements
Run DGAdmin before executing the delete command.
NOTE
If the BSS area is deleted, the related files in the DDS are also deleted.
68P02900W22-S 5-13
Jul 2008
MCDF filter command Chapter 5: Command line tools
MCDF filter command

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Name
filter - allows the insertion or validation or exportation of MCDF files from and to the DataGen
database.
Synopsis
filter [-insert(default) | -validate | -export] -area <country:bss area:config

no> [-files[FileName...]|all (default) ]
Description
This utility allows MCDF files to be exported from the DataGen database or inserted into the
DataGen database. It is also used to validate files.

Table 5-5 Command line options (filter command)
Option Description
–insert Insert the file or all files from the DataGen Directory Structure
(DDS) into the DataGen database.
–validate Validate the file or all files from the DDS. This checks the tables
for errors and does not affect the DataGen database.
–export Export the file or all files from the DataGen database into the DDS -
~/dg/country/BSS_area_name/configuration_number/MCDF/.
country The country name containing the BSS area.
bss area The BSS area name.
config no The configuration number to filter.
–files[FileName ...] | all] If All is selected, then all files will be either inserted, validated, or
exported. Otherwise, only the specific FileName or FileNames will
be used. Refer to Table 5-6 for valid FileNames.
Table 5-6 lists the valid file names to filter MCDF files.
5-14 68P02900W22-S
Jul 2008
System Information: DataGen Command line options
Table 5-6 Valid file names
FileName Table
bss BSS
bts Site
cab Cabinet
hw Hardware
gene Generics
time Timer
modv Modify Value
acct Circuits
chan Channels (The Channels table is
available in MCDF for RXCDR scripts
only).
link Links
path Paths
lapd Lapd
cell Cell
stat Statistics
spec Specific
rtf RTF
dri DRI
alg Algorithm
ngbr Neighbors
thro Throttles
eas EAS
dgtr Daughters
pix PIX
ksw KSW
nsvc Nsvc
hop Hop
acs ACS
testngbr Test Neighbor
nailconn Nail Connection
68P02900W22-S 5-15
Jul 2008
Example Chapter 5: Command line tools
Example
The following example demonstrates how to use the MCDF filter command:
filter -export -area Austria:Area10:0 -files all
This example exports all the MCDF files for country Austria, BSS Area, Area10,
and configuration number 0 to the directory:
~/dg/Austria/Area10/conf0/MCDF/.
Requirements
Run DGAdmin before executing the filter command.
The MCDF file structure is interdependent. Therefore, in certain cases, a file can only be
validated if all its dependent files have been validated. For further details, refer to the MCDF
BSS and RXCDR tables in Chapter 6 MCDF tables.
5-16 68P02900W22-S
Jul 2008
System Information: DataGen MMI command generator (gcmd) command
MMI command generator (gcmd) command

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Name
gcmd - generate BSS command file(s).
Synopsis
gcmd <Country>:<BSS area>:<Config No>[:Site name]
Description
This utility generates BSS command files from the DataGen database, for the objects specified
by the command line parameters.
Table 5-7 Command line options (gcmd command)
Option Description
<Country> The country name
<BSS area> The BSS area
<Config No> The configuration number of the BSS
<Site name> The site name (optional parameter)
Example
The following are examples of how to use the gcmd command:

• gcmd Austria:Area10:0
This example produces an MMI script for Austria BSS Area10, configuration number 0.
• gcmd Austria:Area10:0:1
This example produces an MMI script for site 1 only in Austria BSS Area10, configuration
number 0.
68P02900W22-S 5-17
Jul 2008
Requirements Chapter 5: Command line tools
Requirements
Run DGAdmin before executing the gcmd command.
Output
Output from the script is in the form of BSS command files which can be found in the directory
from where the command was run. A logfile is also produced and the user is mailed the
command status on completion.
5-18 68P02900W22-S
Jul 2008
System Information: DataGen Optimize DataGen database (dbaccess) command
Optimize DataGen database (dbaccess) command

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Name
dbaccess - optimize the DataGen database.
Synopsis
dbaccess db_dg clusters.sql
Description
In order to maximize free disk space, it is advisable to optimize the DataGen database. This
can be performed by running the script named clusters.sql.
NOTE
The DataGen GUI must be closed before running the command:
dbaccess db_dg clusters.sql
Example
The following is an example of how to use the dbaccess command:
cd /usr/informix/bin/dbaccess db_dg clusters.sql
Requirements
Run DGAdmin before executing the dbaccess command. Before starting the optimization,
execute the following command:
/usr/gsm/DataGen/bin/DGAdmin
68P02900W22-S 5-19
Jul 2008
Lock/unlock BSS area (lock_adm) command Chapter 5: Command line tools
Lock/unlock BSS area (lock_adm) command

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Name
lock_adm - lock or unlock a BSS area configuration.
Synopsis
lock_adm -area <country name:BSS area name:config_no> [-who | -lock | -unlock]
Description
This utility allows a BSS area configuration to be:

• Locked or Unlocked.
• Queried about when and where a lock was applied.
A BSS area configuration is automatically locked while the user is working on it and is
automatically unlocked when the user is finished. However, due to occasional error conditions,
a BSS area configuration can remain locked. If this happens, it must then be unlocked using
the lock_adm command before further progress can be made.
Table 5-8 Command Line options (lock_adm command)
Option Description
<country name> The country name of the configuration
<BSS area The BSS name of the configuration
name>
<config_no> The configuration number
–who Query about lock status
–lock Lock a configuration
–unlock Unlock a configuration
5-20 68P02900W22-S
Jul 2008
Example
The following example shows how to use the lock_adm command:
• This example is displayed if BSS Area10, configuration number 0 is locked or unlocked.
lock_adm -area Austria:Area10:0 -who
• The following example shows how to unlock an area:
lock_adm -area Austria:Area10:0 -unlock
NOTE
This command should not be used when another user is genuinely accessing an area.
The following example shows how to lock an area:
lock_adm -area Austria:Area10:0 -lock
Requirements
Run DGAdmin before executing the lock_adm command.
Output
The lock option locks a BSS area. The unlock option unlocks a BSS area. The who option gives
the process id, the user name, the host name and the time when the area was locked as shown
in the following example:
omcadmin kiran>DGAdmin lock_adm -area Austria:182188:0 -lock

DATAGEN DATABASE LOCK ADMINISTRATION TOOL
BSS Area is already locked
Area: Austria, 182188, 0
68P02900W22-S 5-21
Jul 2008
Revgen command Chapter 5: Command line tools
Revgen command
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Name
revgen - Generate MMI files from CM database objects.
Synopsis
revgen -d <CM Object Filename> -C <Country Name> -a <BSS Area Name> [-s <Sites
String>] [-i <area id>] [-c <config number>] [-r <reference config number>] [-B
<config file>] [-v <BSS Version Number>] [-n]
See Table 5-9 for options description.
Description
The CM Database Object does not contain all of the information needed to create a complete
DataGen record. The information missing is the name of the country, the BSS, and the names of
the sites. This information can be supplied in one of three ways:
• The database where a previous configuration version of the BSS exists.
• A configuration file.
• The command line.
The command line options indicate the preferred method. If the CM Database Object contains
a site that is not named by any of these sources, it will be given a default name Site <N>,
where N is the site number.
Table 5-9 Command line options (revgen command)
Option Description
-d <CM Object Filename> The -d option takes a further parameter and identifies the CM
Database Object's file name.
-C <Country Name> The -C option identifies the Country in which to insert the
BSS record.
Continued
5-22 68P02900W22-S
Jul 2008
System Information: DataGen Command line options
Table 5-9 Command line options (revgen command) (Continued)

Option Description
-a <BSS area name> The BSS name for the original objects.
-s <Sites String> The -s option takes a further parameter and identifies the
site names for the sites in the BSS. The names parameter is
a single option and must be placed in quotes. It consists of
the site number immediately followed by an equal sign (=)
and then the name of the site. The quotes prevent the names
parameter being split and information being lost. For example:
0=B06, 1=Hereford, 2=Upper Dunton
-i <area id> Define a BSS area ID.
-c <config number> The -c option takes a further parameter and identifies the
configuration version in which to insert the new DataGen
BSS record. If this option is not used, the Revgen process
will pick out the next available configuration in the indicated
BSS records.
-r <reference config The -r option takes a further parameter and identifies the
number> reference configuration number. This number identifies a
similar BSS which the Revgen utility uses to look up in the
unscheduled site names.
-B <config file> The -B option takes a further parameter and identifies a
configuration file to use to identify the BSS and the site
names. The structure of the configuration file is as follows.
Line 1 - The Country name.

Line 2 - The BSS name (and optionally BSS ID).
Line 3 - The configuration number (may be blank).
Line 4 onwards - Site numbers and names.
For example, a file with the contents:

UK
B06,6
0=B06
1=Hereford
2=Upper Dunton
would create a BSS record choosing the first available
configuration number in country UK and BSS name B06
with ID of 6. Set site 0 up with name B06, site 1 as
Hereford and site 2 as Upper Dunton.
-v <BSS Version Number> The -v option takes a further parameter and identifies the
configuration version number of the DataGen BSS record
for the reference configuration. This record will be used to
resolve any site numbers left unnamed by the -B or -s option.
If the reference contains the same site numbers with the
names that are required in the new record, then this is all that
needs to be supplied.
-n No SYSGEN generated.
68P02900W22-S 5-23
Jul 2008
Example Chapter 5: Command line tools
Example
The following is an example of how to use the revgen command:
revgen -d Area10.002 -C Austria -a Area10 -c 0 -v 1.9.0.0
This example creates a configuration number 0 for the CM Database Area10.002. The
configuration number (-c) is optional. If no configuration number is defined, the next available
number is used.
NOTE
If the DDS directory does not exist for the configuration, the command fails.
Therefore, before running the revgen command, type:
mkdir -p /home/<user_name>/dg/<country>/<BSS_area_name>/
<configuration_number>/002
Requirements
Run DGAdmin before executing the revgen command.
The DataGen database must be loaded with the GSM software versions, and any intermediate
software version requested by the upgrader to perform the Revgen.
Output
The output from this command is in the form of a set of GSM MMI command files, which
can be found in the relevant DDS command directory. The set of GSM MMI command files
are combined to produce one script (COMBINED) for the current DataGen BSS record. The
command status is mailed to the user upon completion.
5-24 68P02900W22-S
Jul 2008
System Information: DataGen Auto-Revgen command
Auto-Revgen command
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Name
auto_revgen - batch revgening of multiple binaries.
Synopsis
auto_revgen [-m] [-d] -C <Country> [-c <configuration number>] -v <Version>

<filename or *>
Refer to Table 5-10 for option descriptions.
Description
This utility allows a number of binaries of one software version to be revgened sequentially,
creating the database areas under relevant BSS areas in the database. The binaries must all be
of the version specified. The BSS areas are named after the binary file names.
Extra options are available to export all the MCDF tables for each new area and to copy each
new area upon Revgen completion. An optional initial configuration number can be specified
for the first new area, with subsequent new areas having the next available configurations
above the starting number.
Table 5-10 Command line options (auto_revgen command)
Option Description
-m Specifies that MCDF tables, should be exported after Revgen is
complete (optional).
-d Specifies that a copy of the new area should be made after Revgen is
complete (optional).
-C <Country> The -C option identifies the country in which to insert the BSS record.
-c <configuration> The configuration number to revgen the first binary (optional).
-v <Version> The software version to revgen the binaries.
<filename or *> Defines a directory where the binary or binaries reside.
68P02900W22-S 5-25
Jul 2008
Requirements Chapter 5: Command line tools
Requirements
Run DGAdmin before executing the auto-revgen command.
Output
Output from the auto_revgen utility is a batch logfile. This shows each operation of the batch
process and any relevant report file created along with its path. Any part of the batch process
which fails, will be reported along with an explanation. For example, when an attempted Revgen
is carried out on a non binary file.
Once the batch process is complete, the final message in the batch file states:
BATCH COMPLETED
Example
The auto_revgen utility works from the command line. The following command line can be
customized to perform the required batch Revgen:
auto_revgen -C Austria -v 1.9.0.0 ~/option_object/1900x/*
This revgens all existing binaries in the specified directory to the corresponding 1900 areas
in the database. If the BSS areas already exist in the database, then the next available
configuration, for each new area is used.
auto_revgen -m -d -C Austria -c 25 -v 1.9.0.0 ~/option_object/1900x/*
This command revgens all existing binaries. After each Revgen process, the MCDF tables
are exported for the new area. The area is copied to the next available configuration and the
MCDF tables for the copied area are exported. The process attempts to Revgen first and then
assigns the configuration number 25. If the number is already in use, the next available number
greater than 25 will be selected.
5-26 68P02900W22-S
Jul 2008
System Information: DataGen Toggle permissions (tp) command
Toggle permissions (tp) command

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Name
tp - Toggle Database Permissions.
Synopsis
tp -r | -u <user name> [<class>] [<mail address>]
Description
The DataGen user has a standard set of access permissions. This utility toggles between the
access permitted, and access denied states.
Table 5-11 Command line options (tp command)
Option Description
<-r> Re-allocate grant permissions to all registered users.
-u <user name> Toggle permissions for the specified user.
[<class>] [<mail address>] Update class or mail address for the specified user.
Example
The following is an example of how to use the toggle command:
tp -u smithd
This example switches between access permitted and access denied or vice versa for user
smithd.
Requirements
Run DGAdmin before executing the tp command.
68P02900W22-S 5-27
Jul 2008
Version upgrader (upg) command Chapter 5: Command line tools
Version upgrader (upg) command

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Name
upg - GSM BSS software version upgrader.
Synopsis
upg -C <country> -a <area> -c <config> -u <version> -t <target config>
Description
This utility copies the specified BSS area to a new configuration, and upgrades the new
configuration to the specified GSM BSS software version. If no parameters are specified, the
upgrader reports which upgrade paths are available. An upgrade path consists of a single
upgrade, or a series of upgrades to take the specified area from its current BSS/GSM software
version to an upgraded version.
Refer to Software Release Notes: DataGen (68P02900W76) for details of current upgrades
supported.
Table 5-12 Command line options (upg command)
Option Description
-C <country> BSS or RXCDR area country name.
-a <area> BSS or RXCDR area name.
-c <config> BSS or RXCDR area configuration to be upgraded.
-u <version> GSM software version to which area is to be upgraded.
-t <target Config > Target configuration number for upgrading.
Requirements
Run DGAdmin before executing the upg command.
The DataGen database must be loaded with the GSM software versions and any intermediate
software version requested by the upgrader.
5-28 68P02900W22-S
Jul 2008
System Information: DataGen Output
Output
Output from the upgrader consists of a screen report informing the user of the new configuration
number for the upgraded area and of the progress and status.
Example of upgrading
An example is shown below:
upg -C UK -a BSS_area -c 0 -u 1.9.0.0 -t 5
Where Is
Country UK
BSS area BSS area
Configuration 0 to version 1.9.0.0
Number
Configuration 5
Number
NOTE
If the specified target configuration exists, the upgrade is aborted.
68P02900W22-S 5-29
Jul 2008
Auto-upgrader command Chapter 5: Command line tools
Auto-upgrader command
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Name
auto_upgrade - batch upgrading of multiple binaries.
Synopsis
auto_upgrade [-m] [-d] -C <Country> [-c <start configuration number>] -v

<Version>-u <Upgrade Version> <filename or *>
Description
This utility allows a number of binaries of the same software version to be upgraded sequentially.
It creates new database areas under relevant BSS areas in the database. All the binary files
must be version specified. These new areas are then upgraded to the specified software version.
Extra options are available to export all the MCDF tables for each new area and to copy each
new area upon upgrade completion. An optional initial configuration number can be specified
for the first new area with subsequent new areas having the next available configurations
greater than the initial number.

Table 5-13 Command line options (auto_upgrade command)
Option Description
–m Specifies that MCDF tables, should be exported after
Revgen is complete (optional).
–d Specifies that a copy of the new area should be made after
Revgen is complete (optional).
–C <Country> The -C option identifies the Country in which to insert the
BSS record.
–c <start configuration> The configuration number to revgen the first binary
(optional).
Continued
5-30 68P02900W22-S
Jul 2008
System Information: DataGen Requirements
Table 5-13 Command line options (auto_upgrade command) (Continued)

Option Description
–v <Version> The software version of the binary files.
–u <Upgrade Version> The software version to which the resultant areas should
all be upgraded.
<filename or *> Define a directory where the binaries reside or a single
binary.
Requirements
Run DGAdmin before executing the auto_upgrade command.
Output
Output from the auto_upgrade utility is a batch logfile. This shows each operation of the batch
process and any relevant report files created and their location. Any part of the batch process
which fails is reported along with the reason for failure. For example, when an attempted
Revgen is performed on a non-binary file.
Once the batch process is complete the final message in the batch file states:
BATCH COMPLETED
Example
The auto_upgrade utility works from the command line. The following command line can be
customized to perform the required batch upgrade:
auto_upgrade -C Austria -v 1.8.0.0 -u 1.9.0.0 ~/scr_objs/1800x/*
This revgens all existing binaries in the specified directory to corresponding 1800 areas in
the database. If the BSS areas corresponding to the binary file names already exist in the
database, then the next available configuration for each new area is used in each case. Each
newly created 1800 area is then upgraded to 1900.
auto_upgrade -m -d -C Austria -c 25 -v 1.8.0.0 -u 1.9.0.0 ~/scr_objs/1800x/*
This command revgens all existing binaries as before. After each Revgen process, each area
is upgraded to 1900 and all MCDF tables are exported for the upgraded area. The upgraded
areas are then copied to the next available configurations and the MCDF tables for the copied
areas are exported. The process attempts to revgen and assign configuration number 25. If the
number is already in use, the next available number greater than 25 is selected.
68P02900W22-S 5-31
Jul 2008
Country administration Chapter 5: Command line tools
Country administration
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to country administration
The following describes how the DataGen user can create new Country and Network files in the
DataGen database using the Country Administration (CADM) feature. The various functions of
the CADM feature which enables the user to manipulate the files are:
• Administration files are created and edited using the Generic Table Editor (GTE). The GTE
is also used to save the files to a specified name or to a supplied standard file name.
• Default Country and Network administration files can be edited using the GTE. The GTE is
also used to save the files to a specified name or to a supplied standard file name.
• Generate or update operations can be performed on the default Country and Network
administration files.
• The CADM feature prompts the DataGen user to decide whether or not to notify the owners
and modifiers of BSS area configurations about Countries and Networks that cannot be
deleted. Notification is by email.
Command Line Interface (CLI)
A Command Line Interface (CLI), enables the DataGen user to generate and update Country and
Network administration files in the DataGen database using CADM utilities.
5-32 68P02900W22-S
Jul 2008
System Information: DataGen Invoking xcadm
Invoking xcadm
To invoke the Country Administration tool, execute the following procedure.
Procedure 5-1 Invoke the Country Administration tool
1 Start DataGen.
2 Open an Xterm window and execute the following commands:
DGAdmin
xcadm
If the Country Admin option is already in use, a warning message is

displayed. Refer to Figure 5-1.
3
Figure 5-1 Country Admin in use confirmation window
Click OK to continue.
Using the xcadm GUI
The xcadm GUI (Figure 5-2) is organized into three functional areas:
• Menu bar
• Data fields
• Action buttons
68P02900W22-S 5-33
Jul 2008
Menus Chapter 5: Command line tools
Figure 5-2 The xcadm GUI
Menus
The menu bar enables the DataGen user to Create, Update and Edit Country, and Network
Administration files as follows.
File menu
The Exit option is the only option available, which is used to exit from the Country
Administration window.
Network menu
The following options are available:

• Edit
Select to use GTE to edit the default Network Administration file.
• Generate
Select to generate a Network Administration file from the DataGen database.
• Update
Select to update the DataGen database with the default Network Administration file.
NOTE
Country and Network menu options are grayed out, depending on the operations
permitted at the corresponding time.
5-34 68P02900W22-S
Jul 2008
System Information: DataGen Data fields
Country menu
The following options are available:

• Edit
Select to use GTE to edit the default Country.
• Generate
Select to generate a Country Administration file from the DataGen database.
• Update
Select to update the DataGen database with the default Country Administration file.
NOTE
For NEW users where no country.std file exists, select Generate from
the Country menu to automatically generate a country.std file in the
/home/omcadmin/dg/ADMIN directory. This also applies to the network.std
file.
Data fields
The following data fields are displayed on the xcadm GUI:

• Country File
Displays the default Country Administration file name when the CADM GUI window
is opened.
• Network File
Displays the default Network Administration file name when the CADM GUI window is
opened.
Action buttons
Table 5-14 shows the definitions for the action buttons on the xcadm GUI.
Table 5-14 Action buttons definitions
Button Definition
Exit The Exit button closes the CADM window.
Help Not available in this version of DataGen.
68P02900W22-S 5-35
Jul 2008
CADM utilities Chapter 5: Command line tools
CADM utilities
The CADM utilities provide read and write access to the CADM administration files through the
File Format utilities (FFMT). FFMT utilities are part of the GTE functionality.
CADM administration files are held in the DataGen database in the following format:
• The file contains country definitions, one definition per line.
• Each field is separated by a @ character.
• The last field of each line is terminated by a new line character.
• Each field is permitted to contain embedded spaces.
The file record is entered with the following syntax:
<country_name>@<MCC><new_line_character>
Where Is
country_name the name of the country.
MCC the Mobile Country Code.
new_line_character the character which designates the end
of the record.
5-36 68P02900W22-S
Jul 2008
Chapter
MCDF tables
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02900W22-S 6-1
Jul 2008
Overview of MCDF tables Chapter 6: MCDF tables
Overview of MCDF tables

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Scope of MCDF tables
This specification gives in detail, the format of each of the files within the MCDF file set. Its aim
is to provide a clear, understandable description and format for the customer, the developer, and
any other audience which needs information about its scope.
This chapter defines the layout and format of each of the files within the MCDF file set.
NOTE
Refer to the appropriate DataGen manual Software Release Notes: DataGen
(68P02900W76) for Customer Committed Problem Resolutions to the software
release installed.
Ranges, default values, and dependencies
Due to MCDF supporting BSS versions 1.7.6.0, 1.8.0.0 and 1.9.0.0, it is important that
users adhere to all the ranges defined in the subsequent tables. Remember that ranges and
recommended values may change from one load to the next. Refer to the manual Technical
Description: BSS Command Reference (68P02901W23) for detailed information about the
parameters in the MCDF tables.
Viewing the MCDF tables
If accessing DataGen using Exceed and viewing the MCDF tables on a flat screen monitor, users
should maximize Exceed to avoid possible DataGen GUI truncation.
MCDF BSS and RXCDR tables
The following diagrams show which tables are mandatory and which are optional (refer to
Figure 6-1 and Figure 6-2).
6-2 68P02900W22-S
Jul 2008
System Information: DataGen MCDF BSS and RXCDR tables
Figure 6-1 Non-collocated BSS hierarchy
ti-GS M-Non-colloca te d_BS S _hie ra rchy-00117-a i-s w
68P02900W22-S 6-3
Jul 2008
MCDF BSS and RXCDR tables Chapter 6: MCDF tables
Figure 6-2 RXCDR Hierarchy
BSS Table
EAS Table
KSW Table
Cabinet Table
Hardware Table
MMS Table Daughter Table
PIX Table
Generics Table Circuits Table Channel Table Stats Table Throttles Table
Timers Table LAPD Table Links Table Specifics Table
Key
MCDF Table
Optional Table
File dependency ,
predecessor must exist
File dependency
if predecessor exists.
ti-GSM-RXCDR_Hierarchy-001 18-a i-sw
6-4 68P02900W22-S
Jul 2008
System Information: DataGen BSS table
BSS table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of BSS table
This table is at the top of the MCDF hierarchy and contains BSS-specific information along with
a field depicting the format of the MCDF file itself (refer to Table 6-1).
This table lists the fields as follows: Field name, Field width, range, and status.
Default filename: bss.mcd
Table 6-1 BSS-specific table
Field Name Field Width Range Status

Country 50 Text Mandatory
Used to verify the country name.
BSS Name 50 Text Mandatory
Used to verify the BSS name.
Software Version 50 30 characters Mandatory
Desired Text
Used to verify the GSM BSS software version.
BSS Serial 50 Text Optional
A complex code to refer to each BSS.
SPC BSC 50 0 to 16777215 Mandatory if
BSS area is
not an RXCDR
(refer Site
Type) otherwise
unused.
Used for element opc.
MSC Name 50 Text Optional
The name of the MSC the to which the BSS is connected.
SPC MSC 50 0 to 16777215 Mandatory if
the BSS area is
not an RXCDR
(refer Site
Type) otherwise
unused.
Used for element dpc.
Continued
68P02900W22-S 6-5
Jul 2008
Description of BSS table Chapter 6: MCDF tables
Table 6-1 BSS-specific table (Continued)

OMC Name 50 Text Optional
Used to group BSSs together into OMC regions.
XCDR Location 50 0 to 1 Mandatory if
BSS area is
not an RXCDR
(refer Site
Type), otherwise
unused.
Used for element transcoder_location:
0 RXCDR
1 BSC/
Collocated
Site Type 50 0, 1 or 3 Mandatory
Used for element fm_site_type:
0 Collocated
BSC/BTS
1 BSC
2 BTS
3 Remote
transcoder
BSC Type 50 0 to 3 Mandatory
Used for element bsc_type:
0 Non-Abis,
only DHP
1 Non-Abis,
only BSP
and LCF
2 Non-Abis,
BSP, LCF
and OMF
3 Abis, only
BSP
Network Indicator 50 0 to 3 Mandatory for
a Non-remote
transcoder area.
Used for element ni. Used for non-remote transcoder areas only.
Continued
6-6 68P02900W22-S
Jul 2008
System Information: DataGen Description of BSS table

A5 Encryption Order 50 0 to 7 for each Optional
of the entered
fields, with a
maximum of 8
fields.
The order of the A5 encryption algorithms to be used by the BSS.
Digit GSM Algorithm
0 No encryption
1 A5/1
2 A5/2
3 A5/3
4 A5/4
5 A5/5
6 A5/6
7 A5/7
5,3,1 The ciphering algorithms are
in the order A5/5, A5/3,A5/1
1,2,3,4,5,6,7,0 The order is A5/1 to A5/7
and no encryption.
Dynamic CSFP Reconfigure 50 1 character text Mandatory
'Y', 'y' or 'N', 'n'
depicting [Y]es
or [N]o.
The BSS area (in SYSGEN mode) performs a dynamic reconfigure of
GPROCs to CSFPs.
Frequency Types Allowed 50 1-15 Mandatory
Used for the frequency_type parameter of the freq_types_allowed command. This defines
the valid frequency types for the current BSS area.
The valid frequency types are defined below:
Numeric
Frequency Type
Entry
PGSM 1
EGSM 2
PGSM EGSM 3
DCS1800 4
PGSM DCS1800 5
EGSM DCS1800 6
Continued
68P02900W22-S 6-7
Jul 2008
Description of BSS table Chapter 6: MCDF tables

PGSM, EGSM DCS1800 7
PCS1900 8
PGSM PCS1900 9
EGSM PCS1900 10
PGSM, EGSM PCS1900 11
DCS1800 PCS1900 12
PGSM, DCS1800 PCS1900 13
EGSM, DCS1800 PCS1900 14
PGSM, EGSM, DCS1800 PCS1900 15
PCS1900 Frequency Blocks 50 A, B, C, D, E, Optional

F, ALL
The field is used to define the valid frequency blocks for PCS1900. Valid blocks are detailed in
Table 6-2.
NOTE
For a subset of blocks, a space character is required.
Table 6-2 Valid Frequency Blocks
Frequency
Block Channels
Parameter
ALL 512-810
A 512-585
D 587-610
B 612-685
E 687-710
F 712-735
C 737-810
All entries into this field must be separated with a space, for example, the blocks allowed are A,
B, D only, so the user must type:
A B D
Information must be entered this way when a subset of frequency blocks is required.
6-8 68P02900W22-S
Jul 2008
System Information: DataGen Site (BTS-specific) table
Site (BTS-specific) table

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Site (BTS-specific) table
This table contains information regarding each site in the BSS area (refer to Table 6-3).
Default filename: bts.mcd
Table 6-3 BTS-specific table

Site Name 50 Text Mandatory
The Unique Site Name.
Site Number 3 {28398} Mandatory
0 to 140, 253
With Increased
Network
Capacity
feature.
The Site Number within the BSS.
Site Configuration 5 Text Mandatory
The type of site: BSC, BSS, BTS or M_BTS (MCell family).
BTS Type 1 0 to 2 Mandatory if site number is
not 0 and site configuration
is a BTS, otherwise unused.
Used for element bts_type:
0 only BTP
1 only BTP and DHP2
2 only BTP, DHP, and

RSLP
Device Type 1 Boolean Mandatory if site number is
not 0, otherwise unused.
Used for element site_type:
0 Site type is BSP.

1 Site type is LCF.
Continued
68P02900W22-S 6-9
Jul 2008
Description of Site (BTS-specific) table Chapter 6: MCDF tables
Table 6-3 BTS-specific table (Continued)

Device ID 2 0 to 24 Mandatory if site number is
not 0, otherwise unused.
Used for element Device ID of LCF or BSP:
0-16 — BSP
0-24 — LCF
Range Device
0-16 BSP
0-24 LCF
RSL Rate 2 16 or 64 Mandatory
Used to determine the data rate of the RSL on BTSs.
CSFP algorithm 10 See below Optional
Used for determining the algorithm for dynamic configuration of CSFP and for the CSFP
download flow control percentage.
Entries are made in the following format:
Site 0: ALG
Sites other than 0: ALG_Pctg

{25423} PCU csfp_flow
Where ALG Is NONE
ANY
STBY
POOL
And Pctg ranges from 10% to 100% in steps of 10.
For example:
(Site 0) ANY
(Site other than 0) ANY_10
(Site other than 0) POOL_20
{25423} csfp_flow ranges from 10 to 100 in steps of 10. The default value is 10.
Dynamic Allocation 3 no/yes Optional. Applicable to In
Default is no. Cell sites only.
Used to indicate whether the site uses dynamic allocation of terrestrial backing resources.
6-10 68P02900W22-S
Jul 2008
System Information: DataGen Cabinet table
Cabinet table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Cabinet table
This mandatory table contains information about all of the non-default type cabinets throughout
the BSS area. Refer to Table 6-4. The default cabinet type is 0 (BTS4).
Default filename: cab.mcd
Table 6-4 Cabinet table

0 to 140, 253
With Increased
Network Capacity
feature.
The site number at which the cabinet is located (refer to the description in Table 6-3).
Cabinet ID 2 0 to 15 Mandatory
The CAB ID for the cabinet.
Cabinet Type 20 Text or Numeric Mandatory
in the range listed
below.
0 BTS_4D_48_VOLT
1 BTS_4D_27_VOLT
2 BSSC_48_VOLT
3 BSSC_27_VOLT
4 BTS_DAB
5 BSSC_DAB
6 EXCELL_4
7 EXCELL_6
8 TOPCELL
9 BTS_5
10 M_CELL_2
11 M_CELL_6
12 TCU_2
13 TCU_6
Continued
68P02900W22-S 6-11
Jul 2008
Description of Cabinet table Chapter 6: MCDF tables
Table 6-4 Cabinet table (Continued)

14 M_CELL_MICRO
15 M_CELLCITY
16 M_CELLARENA
18 HORIZONMACRO (THOR)
19 HORIZONMACRO_EXT (THOR_EXT)
20 M_CELLARENA_MACRO
21 PCU_CAB
22 HORIZONMICRO
23 HORIZONCOMPACT
24 HORIZONMACRO2
25 HORIZONMACRO2_EXT
26 HORIZON2MINI
27 HORIZON2MINI_EXT
28 {26481} HORIZON2MICRO
29 {26481} HORIZON2MICRO_EXT
Frequency Type 2 1 to 15 Mandatory
The valid frequency types are defined in Table 6-5.
Option dependencies are defined in Table 6-6.
NOTE
• The HORIZONMACRO/HORIZONMACRO_EXT cabinets can have PCS1900

as a valid frequency type. A PCS1900 cell with a HORIZONMACRO cabinet
must be a High Power cell. It can be set using the max_ts_bts prompt for
the add_cell command.
• Multiple frequency types within a single cabinet are not supported by the
HORIZONMACRO2 and HORIZONMACRO2_EXT cabinet types.
• {26481} The HORIZON2MICRO and HORIZON2MICRO_EXT cabinets
support single frequency type and do not support PCS1900.
HDSL Modem 3 yes/no Optional. Used only for
Default is no cabinet type 15/16/20.
Used for the prompted parameter: Is HDSL Modem allowed?
Integrated 3 yes/no Optional. Used only for
Antenna Default is no cabinet type 15/16.
Used for the prompted parameter: Is Integrated Antenna allowed?
6-12 68P02900W22-S
Jul 2008
System Information: DataGen Description of Cabinet table
Table 6-5 Frequency Types
Numeric
Frequency Type
Entry
PGSM 1
EGSM 2
PGSM EGSM 3
DCS1800 4
PGSM DCS1800 5
EGSM DCS1800 6
PGSM EGSM DCS1800 7
PCS1900 8
PGSM PCS1900 9
EGSM PCS1900 10
PGSM EGSM PCS1900 11
DCS1800 PCS1900 12
PGSM, DCS1800 PCS1900 13
EGSM, DCS1800 PCS1900 14
PGSM, EGSM, DCS1800 PCS1900 15
Table 6-6 Option dependencies
If Then
Both Infrastructure Sharing Homogeneous Each cabinet (within any given site)
Cabinet and Infrastructure Sharing supports multiple frequency types.
Heterogeneous Cabinet options have been Valid Range: 1 to 15.
purchased.
Both Infrastructure Sharing Homogeneous Only the first cabinet for any given
Cabinet and Infrastructure Sharing site need have this field set. Multiple
Heterogeneous Cabinet options have not frequency types within a single cabinet,
been purchased. or multiple frequencies within a number
of cabinets in a given site is not allowed.
Valid Range: 1, 2, 4 or 8.
Infrastructure Sharing Homogeneous Each cabinet for any given site
Cabinet has been purchased and can be configured to support
Infrastructure Sharing Heterogeneous a different frequency type.
Cabinet options has not been purchased. Valid Range: 1, 2, 4 or 8.
{28938} DataGen supports Incell BTS (Site) as an optional feature. DataGen allows the
equipage of an Incell BTS cabinet including cabinet type of 0 to 9, only if Incell Support feature
is unrestricted.
68P02900W22-S 6-13
Jul 2008
Hardware table Chapter 6: MCDF tables
Hardware table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Hardware table
This table contains information about all cages, default cabinets, and full height cards
throughout the BSS area. Each entry in the table contains details of one device noting the site,
cabinet, cage, and slot in which the device resides (refer to Table 6-7).
NOTE
The cabinets and cages are not explicitly noted in the table, more included within
the details of the cards.
Default filename: hw.mcd
Table 6-7 Hardware table

0 to 140, 253
With Increased
Network
Capacity
feature.
The Site number for this device/function.
Cabinet ID 2 0 to 15 Mandatory for non-M-Cell
sites and also at M-Cell
DRIs.
The CAB ID for this device/function.
Cage Number 2 0 to 15 Mandatory for
non-M-Cell/Horizon sites,
otherwise unused.
The CAGE ID for this device/function.
Slot Number 2 0 to 28 Mandatory for
otherwise unused.
The slot number for this device/function.
Continued
6-14 68P02900W22-S
Jul 2008
System Information: DataGen Description of Hardware table
Table 6-7 Hardware table (Continued)

Device Name 7 Text Optional
The name of this device at a BSS area:
BSS
AXCDR
{26740} The name of this device at a BSC area:
PSI
The name of this device at an RXCDR area:
RXCDR
ABSS
The name of this device at a non-M-Cell site:
DRI
GPROC
LCF
GCLK
KSW
MSI
XCDR
The name of this device at an M-Cell site:
DRI
GPROC (This can only denote a BTP, and no other function)
MSI
The name of this device at a PCU:
PCU
PSP
DPROC
MSI (PICP MSIs for use at the PCU)
GBL
GDS
GSL
Device ID 3 0 to 255 (valid Mandatory if Device Name
range is device is filled in.
dependent)
The first device ID for this device. {27955A} For PCU device, Device ID is either 0 or pcu_0.
DataGen does not support pcu_1 or pcu_2.
Second Device ID 3 0 to 255 (valid Optional
range is device
dependent)
This field is used only when a second device id is required. In the case of the DRI device, this
field is actually the RCU number per sector and has a range of 0 to 24.
For MSI/XCDR devices, this is used to define the MSI type (non-MCELL sites only).
Continued
68P02900W22-S 6-15
Jul 2008
Description of Hardware table Chapter 6: MCDF tables

MSI Type
255 MSI2 (non-MCell sites only)
21 MSI_NIU2 (Horizon II macro sites only)
11 RESERVED
10 RESERVED
9 MSI_NIU_EXT_HDSL (MCell sites only)
8 MSI_NIU_HDSL (M-Cellcity/M-Cellarena only)
7 MSI_EXT_HDSL (Non MCell and non-RXCDR sites only)
6 RESERVED
5 RESERVED
4 RESERVED
3 MSI_NIU (MCell sites only)
2 GDP (non-MCell sites only)
1 XCDR (non-MCell sites only)
0 MSI (non-MCell sites only)
NOTE
• Manual equipage of MSI is not allowed on Horizon II and Horizon II_ext

cabinets.
• {28351} Datagen supports up to two MSI of type E1_PMC and three GBL
devices on PXP DPROC.
MMS0 Protocol Type 4 TEXT (E1 or Optional (Mandatory if
HDSL) Integrated MCell HDSL
feature purchased and
msi_type is HDSL).
Used for the Enter MMS0 protocol type prompt in the equip MSI command.
MMS0 Timeslots 2 16 or 32 Optional (Mandatory if
Integrated MCell HDSL
MMS0 Protocol Type is
HDSL).
Used for the Enter the number of time slots supported on MMS0 prompt in the equip MSI
command.
Continued
6-16 68P02900W22-S
Jul 2008

MMS0 Modem Setting 6 TEXT (MASTER Optional (Mandatory if
or SLAVE) Integrated MCell HDSL
HDSL and msi_type is
NIU_HDSL).
Used for the Enter MMS0 modem setting prompt in the equip MSI command.
MMS1 Protocol Type 4 TEXT (E1 or Optional (Mandatory if
HDSL) Integrated MCell HDSL
msi_type is HDSL).
Used for the Enter MMS1 protocol type prompt in the equip MSI command.
MMS1 Timeslots 2 16 or 32 Optional (Mandatory if
Integrated MCell HDSL
HDSL).
Used for the Enter the number of time slots supported on MMS1 prompt in the equip MSI
command.
MMS1 Modem Setting 6 TEXT (MASTER Optional (Mandatory if
or SLAVE) Integrated MCell HDSL
HDSL and msi_type is
NIU_HDSL).
Used for the Enter MMS1 modem setting prompt in the equip MSI command.
Function Name 7 Text Mandatory for GPROC
devices. Used for PCU
DPROC devices and PCU
PICP MSIs.
The name of this function at a non-M-Cell site. (This is only valid for a GPROC device entry).
NONE (This is a redundant GPROC)
BSP
CSFP
DHP
LCF
OMF
RCF
RSLF
The name of this function at an M-Cell site. (This is valid only for a GPROC device entry).
BTP
The name of this function at a PCU.
DPROC (mandatory for a PICP MSI at the PCU)
{28351} PXP (for a PCU DPROC)
PICP (for a PCU DPROC)
PRP (for a PCU DPROC)
Continued
68P02900W22-S 6-17
Jul 2008

Function ID 5 See below Optional
The first ID of this function valid in GPROC and PCU entries, BSS, or RXCDR area entries.
Used as follows for non-M-Cell devices:
DEVICE FUNCTION RANGE USAGE
GCLK yes/no/<blank> Represents whether or not

a gclk clkx0 is equipped.
GPROC BSP 0-1 0 Controller, 1 Redundant
GPROC BTP 0-1 0 Controller, 1 Redundant
GPROC CSFP 0-1 CSFP ID
GPROC DHP 0-7 Second ID (First ID is Cage
Number)
GPROC LCF 0-24 First ID
GPROC OMF Not Used
GPROC RCF 0-7 First ID
GPROC RSLF 0-7 First ID
KSW yes/no/<blank> Represents whether or
not DRIs are allowed on a
highway.
Used as follows for M-Cell devices:
GPROC BTP 0 to 1 This is blank for a BTP in
an M-Cell Micro cabinet.
MSI 0 to 1 Used for MCU Card Frame
prompt.
Used as follows for PCU devices:
Continued
6-18 68P02900W22-S
Jul 2008

MSI (PICP) 1 to 6, 11 to 16 Used for the associated
DPROC ID.
GBL Used for the FIRST MMS
ID.
GDS N/A Used for BSC MMS ID 1.
GSL N/A Associated GDS ID.
PCU 0 to 65535 Used for nsei. The older
binaries contain the NSEI
parameter in the Generics
table.
{27955A}
NOTE
• Equipage of more than one PCU is not allowed. While upgrading from 1800
to 1900, if there are more than one PCU equipped, Upgrader retains only
pcu_0 and removes the others.
• Manual equipage of Cabinet and Cage devices is not allowed under PCU. They
are automatically equipped when PCU is equipped.
• While upgrading to 1900, upgrader sets the value of gds_connectivity to 0.
Used as follows for BSS area specific devices:
AXCDR yes/no Used to specify use of CIC
validation.
Second Function ID 3 0 to 1 Optional
(Allow for
expansion)
NOTE
In the case of AXCDR, the Second Function ID represents eac_mode.
The second ID of this function is valid for GPROC and PCU entries, BSS, or RXCDR area
entries. Used as follows:
Continued
68P02900W22-S 6-19
Jul 2008

GCLK yes/no/<blank> Represents whether a gclk
clkx1 is equipped.
NONE Not Used
BSP 0-2 Maximum number of MTLs
BTP 0-6 Maximum number of DRIs
CSFP Not Used
DHP 1-6 Maximum number of DRIs
LCF 0-2 Maximum number of MTLs
OMF Not Used
RCF Not Used
RSLF Not Used
The applicable range for an LCF Maximum number of MTLs is 0-2 (2 indicates a GPROC2
card is being used for this purpose). The applicable range for an LCF Maximum number of
LMTLs is 0-2.
Used for M-Cell devices as follows:
MSI 0 to 1 Used for NUI Slot Number
prompt.
MSI (PICP) 1 to 2 Used for DPROC SOCKET.
GBL N/A Used for the SECOND
MMS ID.
GDS N/A Used for BSC MMS ID 2.
GSL 0 to 24 Used as the GSL_LCF_ID.
BSS yes/no Used for transcoding type
(yes implies at a BSC, no at
an RXCDR).
Used as follows for RXCDR area specific devices:
ABSS 0 to 1 Specifies volume
control type
(0 off, 1 on).
Continued
6-20 68P02900W22-S
Jul 2008

{28000} The following attribute is supported using the Second Function ID for PCU:
Parameter Minimum Maximum Default
prp_fanout_mode 1 2 1
Third Function ID 3 0 to 254 Optional

The third ID of this function - valid in GPROC and PCU entries, BSS, or RXCDR area entries.
Used as follows:
GCLK yes/no/<blank> Represents whether or not

a gclk clkx2 is equipped.
NONE Not Used
BSP Not Used
BTP Not Used
CSFP Not Used
DHP Not Used
LCF 0 to 1
OMF Not Used Number supported CBLs.
RCF Not Used
RSLF Not Used
GBL 1 to 31 Used for the start time slot.
GDS N/A Used for PCU MMS ID1.
BSS yes/no Used for dynamic
allocation.
ABSS -15 to 15 Specifies downlink audio
level offset.
Fourth Function ID 3 0 to 99 Optional
The fourth ID of this function - valid for GPROC and PCU entries, BSS, or RXCDR area entries.
Used as follows for GPROC devices:
Continued
68P02900W22-S 6-21
Jul 2008

GPROC LCF 0 to 6 Used for the maximum
number of GSLs that the
LCF can manage.
GBL 1 to 31 Used for the end time slot.
GDS N/A Used for PCU MMS ID2.
BSS 0 to 255 Used for darbc related CIC
blocking.
ABSS -15 to 15 Specifies uplink audio level
offset.
Fifth Function ID 3 0 to 1 Optional
The fifth ID of this function - valid for PCU entries and BSS area specific entries.
Used as follows:
GDS N/A Used for GDS TYPE.
BSS 0 to 255 Used for darbc related CIC
unblocking.
GBL T391 Timer 2 5 to 29 Used only with the PCU
GBL device - optional.
Used to Enter the T391 timer prompt in the equip GBL command.
GBL T392 Timer 2 6 to 30 Used only with the PCU
Used to Enter the T392 timer prompt in the equip GBL command.
GBL N391 Counter 3 1 to 255 Used only with the PCU
Used to Enter the N391 counter prompt in the equip GBL command.
Continued
6-22 68P02900W22-S
Jul 2008

IP address 15 0 to 255 per byte Used only with the PCU
PSP device - optional.
Specifies the IP address of the PSP.
Subnet mask 15 0 to 255 per byte Used only with the PCU
Specifies the subnet mask of the PSP.
Router IP address 15 0 to 255 per byte Used only with the PCU
Specifies the router address of the PSP.
MSC MSI ID 3 0 to 123 Used only when MSI type
is GDP.
Specifies the id of a GDP whose MMS is available for routing the transcoding circuits of a
secondary GDP towards the MSC.
MSC MMS ID 1 0 only Used only when MSI type
is GDP.
Always set to zero, because MSIs cannot be used to provide MSC MMSs.
Transcoding 8 0 or 1 Used only when MSI type
Capability is GDP.
Specifies the transcoding functionality of the GDP board.
The following device parameters are supported:
Parameter Minimum Maximum Default

{26740} device_id 0 11 0
{26740} cage 0 13 N/A
{26740} slot 6 13 N/A
{26740} tdm_ts_blocks 2 10 2
{26740}{28337} 0 12 (for LCF) N/A (for LCF)
max_gsls 30 (for PSI) 0 (for PSI)
{28337} max_mtls 0 2 (for 64k MTL) N/A
31 (for HSP
MTL)
{28337} max_cbls 0 1 N/A
{26740} subnet_mask 128.0.0.0 255.255.255.0 255.255.255.0
{28351} 1.0.0.1 223.255.255.231 10.0.0.1
base_ip_address
Continued
68P02900W22-S 6-23
Jul 2008

{26740} 1.0.0.1 223.255.255.237 N/A
psi_base_ip_address
{28351} 128.0.0.0 255.255.255.254 255.255.255.0
gds_subnet_mask
{28351} gds_ip_address 1.0.0.1 223.255.255.231 10.0.0.1
{28351} 0 1 N/A
gds_connectivity
{28351 }bsc_eth psi_id: 0 psi_id: 11 N/A
bsc_eth_port: 0 bsc_eth_port: 0
{28351} pcu_eth dproc_id: 1 dproc_id: 16 N/A
pcu_eth_port: 0 pcu_eth_port: 0
{28351} gds_type 0 or TRAU 2 or N/A
LAPD_TRAU
6-24 68P02900W22-S
Jul 2008
System Information: DataGen Generics table
Generics table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Generics table
The Generics table contains a list of elements, including Motorola-specific elements. For
convenience, the timer and statistics elements have been placed in separate files. Either the
value from the value field (if present), or the Motorola recommended value, is set BSS-wide but
can be overridden for a site or cell by values in the Specifics and Cell tables.
Table 6-8 outlines the parameters of the Generics table.
Default filename: gene.mcd
Table 6-8 Generics table

Element Name 50 <element Mandatory
name>[,<index>]
Name of the element optionally followed by an index.
Recommended 11 -2, 147, 483, 647 to Mandatory
Value +2, 147, 483, 647
(Element dependent)
Recommended value of the element.
Value 11 -2, 147, 483, 647 to Optional
+2, 147, 483, 647
(Element dependent)
Overrides the recommended value of the element.
68P02900W22-S 6-25
Jul 2008
Layout of elements in the MCDF Generics table Chapter 6: MCDF tables
Layout of elements in the MCDF Generics table

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The elements in the Generics table are displayed in Table 6-9 as follows:
Table 6-9 Generics table - Elements
# Element Name Recommended Value

1 _bss_data,0 0
2 _bss_data,1 0
3 _bss_data,2 0
4 _bss_data,3 0
5 _bss_data,4 24
6 {31565} _cell_data,20 1
7 {34144} _site_data,1 0
8 aci_error_clr_thresh 0
9 aci_error_gen_thresh 6
10 aci_error_inc 0 if ECERM is not enabled.
1 if ECERM is enabled.
11 adap_ho_alt_trigger_rxqual 0
12 adap_ho_pbgt 0
13 adap_ho_rxlev 0
14 adap_ho_rxqual 0
15 adap_trigger_pbgt 0
16 adap_trigger_rxlev_dl 0
17 adap_trigger_rxlev_ul 0
18 adap_trigger_rxqual_dl 0
19 adap_trigger_rxqual_ul 0
20 adap_trigger_hop_rxqual_dl 0
21 adap_trigger_hop_rxqual_ul 0
22 addr_ind_bit_8 0
23 alt_qual_proc 0
24 amr_fr_dl_la_enabled 1
25 amr_fr_ul_la_enabled 1
26 amr_hr_dl_la_enabled 1
27 amr_hr_ul_la_enabled 1
28 amr_hr_res_ts 2
Continued
6-26 68P02900W22-S
Jul 2008
System Information: DataGen Layout of elements in the MCDF Generics table
Table 6-9 Generics table - Elements (Continued)

29 amr_bss_half_rate_enabled 0
30 amr_half_rate_enabled 0
31 amr_bss_full_rate_enabled 0
32 amr_full_rate_enabled 0
33 amr_new_calls_hr 101
34 amr_ms_monitor_period 40
35 amr_ms_high_cmr 95
36 amr_ms_low_cmr 99
37 amr_ms_high_rxqual 4
38 amr_ms_low_rxqual 2
39 amr_dl_thresh_adjust 3
40 amr_dl_la_mode_chg_min 5
41 {27703A} arp_i_be_1 93
42 {27703A} arp_i_be_2 97
43 {27703A} arp_i_be_3 101
44 {27703A} arp_bg_1 49
45 {27703A} arp_bg_2 53
46 {27703A} arp_bg_3 57
47 {27703A} arp_signal_sele 1
48 {27703A} arp_streaming_1 68
51 {30830} asym_edge_enabled 0
52 attach_detach 0
53 auto_dl_dur 50
54 auto_rf_loss_trace 0
55 ba_alloc_proc 0
56 band_preference None
57 band_preference_mode 0
58 bep_period 0
59 bep_period2 15
60 ber_loss_daily 5
61 ber_loss_hourly 4
62 blind_search_preference 0
Continued
68P02900W22-S 6-27
Jul 2008

63 bounce_protect_margin 0
64 bs_ag_blks_res 0
65 bs_pa_mfrms 0
66 bs_pag_blks_res 3
67 bs_pbcch_blks 2
68 bs_pcc_chans 1
69 bs_prach_blks 4
70 {23306} 0
bsp_overload_protection
71 bss_overload_control 12500
72 bssap_ss 254
73 bssgp block retries 3
74 bssgp_cbl_bit 0
75 bssgp_fc_period_c 10
76 bssgp_pfc_bit 0
77 bssgp_racap_retries 3
78 bssgp_reset_retries 3
79 bssgp_unblock_retries 3
80 bss_egsm_alm_allowed 0
81 bss_msc_overload_allowed 0
82 bts_escalation 60
83 bts_p_con_ack 1
84 bts_p_con_interval 2
85 bts_power_control_allowed 0
86 bts_txpwr_max_inner 0
87 bvci None
88 c31_hyst 0
89 c32_qual 0
90 call_trace_options 0
91 called_pci 0
92 calling_pci 0
93 carrier_disable_time 120
94 carriers_ins_pwr_fail 30
95 cbc_fast_select 0
Continued
6-28 68P02900W22-S
Jul 2008

96 cbc_intface_vers 0
97 cbc_vbind_cntr 0
98 cbs_outage_cntr 0
99 cbch_enabled 0
100 ccch_conf 0
101 ccch_load_period 40
102 cell_bar_access_class 0
103 cell_bar_access_switch 0
104 cell_bar_qualify 0
105 cell_reselect_hysteresis None
106 cell_reselect_offset 0
107 cell_reselect_param_ind 0
108 channel_reconfiguration_switch 0
109 cic_ccitt_order 0
110 cic_error_clr_threshold 0
111 cic_error_gen_threshold 6
112 cic_error_increment 1
113 ciph_mode_rej_allowed 0
114 clk_src_fail_reset_period 24
115 coincident_offset 0
116 confusion_msg_allowed 0
117 congest_at_source 0
118 congest_at_target 0
119 cp_option_reset_ckt 0
120 cp_option_rr_status 0
121 cr_calling 0
122 ct_flow_control_hi_level 60
123 ct_flow_control_lo_level 20
124 ct_flow_control_msc_trace 0
125 {30828} ctu2dcapopt None
126 ddtr_ctrl_enabled 0
127 decision_1_dl_rxlev_av_ih 0
128 decision_1_dl_rxlev_av_p 0
129 decision_1_dl_rxqual_av_h 0
Continued
68P02900W22-S 6-29
Jul 2008

130 decision_1_dl_rxqual_av_p 0
131 decision_1_n1 1
132 decision_1_n2 1
133 decision_1_n3 1
134 decision_1_n4 1
135 decision_1_n5 1
136 decision_1_n6 1
137 decision_1_n7 1
138 decision_1_n8 1
139 decision_1_ncell_rxlev_av_h_calc 0
140 decision_1_p1 1
141 decision_1_p2 1
142 decision_1_p3 1
143 decision_1_p4 1
144 decision_1_p5 1
145 decision_1_p6 1
146 decision_1_p7 1
147 decision_1_p8 1
148 decision_1_p_bgt_rxlev_av_h 0
149 decision_1_tim_adv_av_alg 0
150 decision_1_ul_rxlev_av_h 0
151 decision_1_ul_rxlev_av_ih 0
152 decision_1_ul_rxlev_av_p 0
153 decision_1_ul_rxqual_av_h 0
154 decision_1_ul_rxqual_av_p 0
155 decision_alg_type 0
156 delay_dl_rel_dur 50
157 delay_ul_rel_dur 18
158 direct_inner_zone_threshold 63
159 disuse_cnt_hreqave 0
160 dl_audio_lev_offset 0
161 dl_dtx_voice_data 0
162 dl_rxlev_ho_allowed 1
163 dl_rxqual_ho_allowed 1
Continued
6-30 68P02900W22-S
Jul 2008

164 dnlk_vad_dtx 0
165 dr_chan_mode_modify 0
166 dr_ho_during_assign 0
167 dr_preference 0
168 dr_standard_congest 0
169 {26740} 0
dsp_error_clr_thresh
170 {26740} 6
dsp_error_gen_thresh
171 {26740} dsp_error_inc None
172 dtx_required 2
173 dual_band_offset 0
174 dyn_step_adj 0
175 dyn_step_adj_fmpr 10
176 dynet_tchs_reserved 0
177 early_classmark_sending 0
178 efr_enabled 0
179 egprs_init_dl_cs 2
180 egprs_init_ul_cs 2
181 egsm_handover_threshold 0
182 emergency_class_switch 0
183 emergency_group_priority 0
184 en_incom_ho 0
185 enhanced_relief 0
186 eop_enabled 0
187 erc_ta_priority 50
188 {26740} 10
eth_rx_errors_threshold
189 {26740} 10
eth_tx_errors_threshold
190 extended_paging_active 0
191 {26881} ext_ul_dur 0
192 {26881} ext_utbf_nodata 0
193 fdd_gprs_qoffset 8
194 fdd_multirat_reporting 1
Continued
68P02900W22-S 6-31
Jul 2008

195 fdd_rep_quant 1
196 force_hr_usage 0
197 full_pwr_rfloss 0
198 gbl_thrput_period 50
199 gci_error_clr_thresh 0
200 gci_error_gen_thresh 6
201 gci_error_inc 0 if ECERM is not enabled.
202 gclk_qwarm_flag 0
203 global_reset_repetitions 0
204 gproc_slots 16
205 gprs_alarm_time 60
206 gprs_bs_cv_max 6
207 gprs_cell_reselect_hysteresis 0
208 gprs_com_ms_class 8
209 gprs_dl_pwr_mode 1
210 gprs_drx_timer_max 0
211 gprs_intraho_allwd 1
212 gprs_mac_mode 1
213 gprs_max_ul_ts 2
214 gprs_min_prr_blks 0
215 gprs_ms_pan_dec 1
216 gprs_ms_pan_inc 1
217 gprs_ms_pan_max 3
218 gprs_ms_txpwr_max_cch None
219 gprs_network_operation_mode 3
220 gprs_par_wait_ind 150
221 gprs_pb 1
222 gprs_pc_alpha 0
223 gprs_pc_meas_chan 0
224 gprs_penalty_time 0
225 gprs_reconfig_thresh_idle_tch 1
226 gprs_reselect_offset 16
227 gprs_rxlev_access_min 0
Continued
6-32 68P02900W22-S
Jul 2008

228 gprs_sched_beta 1
229 gprs_sig_bvci 0
230 gprs_smg30_t3192 500
231 gprs_t3168 4000
232 gprs_t3192 500
233 gprs_temporary_offset 0
234 gprs_ts_config_alg 0
235 gprs_type5_alg 0
236 gprs_ul_dl_bias 1
237 group_block_unblock_allowed 0
238 gsl_lcf_mapping 1
239 gsm_bss_half_rate_enabled 0
240 gsm_cell_id_format 1
241 gsm_half_rate_enabled 0
242 handover_power_level 2
243 handover_recognized_period 2
244 handover_required_curr_ch 0
245 handover_required_reject_switch 1
246 handover_required_sp_ver_used 0
247 hcs_thr 0
248 ho_exist_congest 0
249 ho_margin_def 8
250 ho_margin_usage_flag 0
251 ho_only_max_pwr 0
252 ho_pwr_level_inner 2
253 hop_count 255
254 hopping_support 0
255 hopping_systems_enabled,0 0
Continued
68P02900W22-S 6-33
Jul 2008

271 hopping_systems_hsn,0 0
287 hr_fr_hop_count 1
288 hr_intracell_ho_allowed 3
289 hr_res_ts 2
290 illegal_circuit_id 0
291 immediate_assign_mode 0 (not supported)
292 inact_cont_allow 1
293 improve_ts_enabled 0
294 imrm_dcs1800_weight 0
295 imrm_egsm_weight 0
Continued
6-34 68P02900W22-S
Jul 2008

296 imrm_force_recalc 0
297 imrm_pgsm_weight 0
298 imrm_umts_weight 0
299 inc_prp_cap_ena 0
300 intave 8
301 init_dl_cs 1
302 init_ul_cs 1
303 inner_hr_usage_thres 101
304 interband_ho_allowed None
305 inter_cell_handover_allowed 1
306 interfer_bands,0 63
311 interfer_ho_allowed 1
312 intra_cell_handover_allowed 1
313 l_rxlev_dl_h 10
314 l_rxlev_dl_p 30
315 l_rxlev_ul_h 10
316 l_rxlev_ul_p 30
317 l_rxqual_dl_h None
318 l_rxqual_dl_h_data None
319 l_rxqual_dl_h_hopping None
320 l_rxqual_dl_h_hopping_hr None
321 l_rxqual_dl_h_hr None
322 l_rxqual_dl_p None
323 l_rxqual_dl_p_data None
324 l_rxqual_dl_p_hopping None
325 l_rxqual_dl_p_hopping_hr None
326 l_rxqual_dl_p_hr None
327 l_rxqual_ul_h None
328 l_rxqual_ul_h_data None
329 l_rxqual_ul_h_hopping None
Continued
68P02900W22-S 6-35
Jul 2008

330 l_rxqual_ul_h_hopping_hr None
331 l_rxqual_ul_h_hr None
332 l_rxqual_ul_p None
333 l_rxqual_ul_p_data None
334 l_rxqual_ul_p_hopping None
335 l_rxqual_ul_p_hopping_hr None
336 l_rxqual_ul_p_hr None
337 l_rxqual_ul_p_amr_fr None
338 l_rxqual_ul_p_amr_hr None
339 l_rxqual_ul_h_amr_fr None
340 l_rxqual_ul_h_amr_hr None
341 l_rxqual_ul_h_hopping_amr_fr None
342 l_rxqual_ul_h_hopping_amr_hr None
343 l_rxqual_dl_p_hopping_amr_fr None
344 l_rxqual_dl_p_hopping_amr_hr None
345 l_rxqual_dl_p_amr_fr None
346 l_rxqual_dl_p_amr_hr None
347 l_rxqual_dl_h_amr_fr None
348 l_rxqual_dl_h_amr_hr None
349 l_rxqual_dl_h_hopping_amr_fr None
350 l_rxqual_dl_h_hopping_amr_hr None
351 l_rxqual_ul_p_hopping_amr_fr None
352 l_rxqual_ul_p_hopping_amr_hr None
353 land_layer1_mode 0
354 layer_number 0
355 lcs_mode 0
356 link_about_to_fail 2
357 link_fail 4
358 local_maintenance 1
359 low_sig_thresh 0
360 lta_alarm_range 7
361 ltu_fw_auto_download 1
362 max_gprs_ts_per_carrier 8
363 max_ms_dl_buffer 38400
Continued
6-36 68P02900W22-S
Jul 2008

364 max_ms_dl_rate 900
365 max_number_of_sdcchs None
366 max_pagenum_per_sec 65535
367 max_paging_per_sec 120
368 max_q_length_full_rate_channel 0
369 max_q_length_sdcch 0
370 max_retran 0
371 max_rst_ckt_timer_exps 1
372 max_tx_bts 0
373 max_tx_ms None
374 mb_preference 0
375 mb_tch_congest_thres 100
376 missing_rpt 0
377 mmi_cell_id_format 0
378 mms_cat_enable 0
379 mms_config_type 0
380 mms_config_type_pcu 0
381 msc_bss_overload_allowed 0
382 msc_preference 0
383 msc_qt 84
384 msc_release 0
385 ms_distance_allowed 0
386 ms_max_range 63
387 ms_p_con_ack 2
388 ms_p_con_interval 2
389 ms_power_control_allowed 1
390 ms_power_offset 0
391 ms_txpwr_max_cch 2
394 ms_txpwr_max_inner None
395 mspwr_alg 0
396 {27703A} 1
mtbr_downgrade_enabled
397 mtl_loadshare_granularity 0
398 {28337} mtl_rate 1
Continued
68P02900W22-S 6-37
Jul 2008

399 multiband_reporting 0
400 nacc_enabled 0
401 n_avg_i 2
402 ncc_of_plmn_allowed 255
403 nccr_enabled 0
404 nc_non_drx_period 2
405 nc_reporting_period_i 6
406 nc_reporting_period_t 2
407 neighbor_journal 0
408 new_calls_hr 101
409 ns_alive_retries 3
410 ns_block_retries 3
411 ns_unblock_retries 3
412 nsei None
413 num_audit_retries 1
414 num_gbl_dl_thrput_samples 10
415 num_gbl_ul_thrput_samples 10
416 number_of_preferred_cells 16
417 number_sdcchs_preferred None
418 option_alg_a5_1 0
425 option_emergency_preempt 0 (not supported)
426 option_preempt 0
427 outer_zone_usage_level 0
428 override_intra_bss_pre_transfer 0
429 pbgt_mode 0
430 pccch_drx_timer_max 3
431 pccch_enabled 0
432 pcr_enable 0
Continued
6-38 68P02900W22-S
Jul 2008

433 pcr_n1 127
434 pcr_n2 3750
435 {27955A} pcu_redundancy 0
436 penalty_time 0
437 percent_traf_cs 55
438 {27703A} pfc_be_arp 0
439 {27703A} pfm_sig_enabled 1
440 phase2_classmark_allowed 0
441 phase2_resource_ind_allowed 0
442 phase_lock_gclk 0
443 phase_lock_retry 255
444 pic_error_clr_thresh 0
445 pic_error_gen_thresh 6
446 pic_error_inc 0 if ECERM is not enabled.
447 pool_gproc_preemption 1
448 poor_initial_assignment 0
449 pow_inc_step_size_dl 2
450 pow_inc_step_size_ul 2
451 pow_red_step_size_dl 2
452 pow_red_step_size_ul 2
453 prach_s 8
454 prach_tx_int 14
455 primary_pcu -1
456 prioritize_microcell 1
457 priority_class 0
458 prm_gmsk_cap_fix_changed 0 (not supported)
459 protect_last_ts 0
460 prr_aggr_factor 3
461 {26740} 10
psi_trau_fill_frames_threshold
462 psi1_repeat_period 5
463 pwr_handover_allowed 1
464 pwrc 1
465 {27703A} qos_mbr_enabled 0
Continued
68P02900W22-S 6-39
Jul 2008

466 qos_mtbr_be_dl 2
467 qos_mtbr_be_ul 2
468 qos_mtbr_bg_dl 2
469 qos_mtbr_bg_ul 2
470 qos_mtbr_i1_dl 2
471 qos_mtbr_i1_ul 2
476 qsearch_c 15
477 qsearch_p 0
478 queue_management_information 50
479 rac None
480 ra_colour None
481 ra_reselect_hysteresis 0
482 rach_load_period 16
483 rach_load_threshold 1000
484 rach_load_type 0
485. radio_link_timeout 4
486 rapid_pwr_down 0
487 rci_error_clr_threshold 0
488 rci_error_gen_threshold 6
489 rci_error_increment 1
490 reconfig_fr_to_hr 101
491 red_loss_daily 16
492 red_loss_hourly 20
493 red_loss_oos 511
494 red_loss_restore 600
495 red_psp_audit_tmr 24
496 red_time_oos 25
497 red_time_restore 600
498 reestablish_allowed 0
499 remote_loss_daily 16
Continued
6-40 68P02900W22-S
Jul 2008

500 remote_loss_daily_pcu 16
501 remote_loss_hourly 20
502 remote_loss_hourly_pcu 20
503 remote_loss_oos 511
504 remote_loss_oos_pcu 511
505 remote_loss_restore 600
506 remote_loss_restore_pcu 600
507 remote_time_oos 25
508 remote_time_oos_pcu 25
509 remote_time_restore 600
510 remote_time_restore_pcu 600
511 report_resource_tch_f_high_water_mark 2
512 report_resource_tch_f_low_water_mark 12
513 res_gprs_pdchs 0
514 res_ts_less_one_carrier None
515 rf_res_ind_period 10
516 rpd_offset 8
517 rpd_period 2
518 rpd_trigger 45
519 rpt_bad_qual_no_mr 0
520 rsl_congestion_alarm_timer 60000
521 rsl_lcf_congestion_thi 60
522 rsl_lcf_congestion_tlow 25
523 rtf_path_enable 0
524 rxlev_access_min 0
525 rxlev_dl_zone 63
526 rxlev_min_def 15
527 rxlev_ul_zone 63
528 sccp_bssap_mgt 1
529 scr_enabled 0
530 sdcch_ho 1
531 sdcch_need_high_water_mark 2
532 sdcch_need_low_water_mark 12
533 sdcch_timer_ho 1
Continued
68P02900W22-S 6-41
Jul 2008

534 sdcch_tch_band_reassign_delay 0
535 search_prio_3g 1
536 secondary_freq_type None
537 second_asgnmnt 0
538 serving_band_reporting 3
539 sgsn_r 0
540 sgsn_release 0
541 sig_lnk_tst_allow 1
542 slip_loss_daily 4
543 slip_loss_hourly 10
544 slip_loss_oos 255
545 slip_loss_restore 600
546 smg_gb_vers 31
547 sms_dl_allowed 0
548 sms_tch_chan 2
549 sms_ul_allowed 0
550 ssp_burst_delay 200
551 ssp_burst_limit 10
552 ss7_mode 0
553 ssm_critical_overload_threshold 80
554 ssm_normal_overload_threshold 70
555 static_sync_timer 12000
556 stat_interval 30
557 stop_dri_tx_enable 0
558 stop_dri_tx_time 300
559 stp_pc None
560 stp_pc_enabled 0
561 {27703A} 1
stream_downgrade_enabled
562 {27703A} streaming_enabled 0
563 sw_pdtch_priority 14
564 sw_ts_less_one_carrier None
565 swfm_enable 0
566 switch_gprs_pdchs 0
Continued
6-42 68P02900W22-S
Jul 2008

567 sync_loss_daily 16
568 sync_loss_daily_pcu 16
569 sync_loss_hourly 20
570 sync_loss_hourly_pcu 20
571 sync_loss_oos 511
572 sync_loss_oos_pcu 511
573 sync_loss_restore 600
574 sync_loss_restore_pcu 600
575 sync_time_oos 25
576 sync_time_oos_pcu 25
577 sync_time_restore 600
578 sync_time_restore_pcu 600
579 t_avg_t 10
580 t_avg_w 10
581 tch_busy_critical_threshold 100
582 tch_busy_norm_threshold 100
583 tch_congest_prevent_thres 100
584 tch_flow_control 0
585 tch_full_need_low_water_mark 255
586 tch_usage_threshold 0
587 {31400} td_enabled 0
588 {25002} tdm_switch 0
589 temporary_offset 0
590 thp_be_weight 40
591 thp_bg_weight 40
592 thp_i2_weight 40
593 thp_i3_weight 40
594 {27703A} thp_stream_weight 40
595 threshold 7
596 timing_advance_period 4
597 tlli_blk_coding 0
598 trace_msgs_after_ho 5
599 trace_msgs_before_ho 5
600 trunk_critical_threshold 50
Continued
68P02900W22-S 6-43
Jul 2008

601 trunk_major_threshold 10
602 ts_alloc_flag 0
603 tsc_update_method 0
604 tx_integer 4
605 tx_power_cap 0
606 u_rxlev_dl_ih 45
607 u_rxlev_dl_p 40
608 u_rxlev_ul_ih 45
609 u_rxlev_ul_p 40
610 u_rxqual_dl_p None
611 u_rxqual_dl_p_amr_hr None
612 u_rxqual_dl_p_hr None
613 u_rxqual_ul_p None
614 u_rxqual_ul_p_hr None
615 ul_audio_lev_offset 0
616 ul_rxlev_ho_allowed 1
617 ul_rxqual_ho_allowed 1
618 umts_band_preferred 0
630 umts_cpich_ec_no_min -15
631 umts_cpich_rscp_min -90
632 unequipped_circuit_allowed 0
633 use_bcch_for_gprs 1
634 use_derived_ho_power 0
635 use_neighbor_pbgt_hreqave 0
636 volume_control_type 0
637 wait_for_reselection 10
638 wait_indication_parameters 5
639 worse_neighbor_ho 0
640 zone_ho_hyst 0
641 zone_pingpong_enable_win 30
642 zone_pingpong_disable_win 30
643 zone_pingpong_preferred_zone 255
644 zone_pingpong_count 3
6-44 68P02900W22-S
Jul 2008
System Information: DataGen Timer table
Timer table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Timer table
This table contains a list of timer elements, including Motorola-specific elements. Either the
value from the value field (if present) or the Motorola recommended value is set bss-wide, but
can be overridden for a site or cell by values in the Specifics table.
Table 6-10 outlines the parameters of the Timer table.
Default filename time.mcd
Table 6-10 Timer table

Element Name 50 <element Mandatory
name>[<index>]
Name of the timer element optionally followed by an index.
Recommended 11 -2,147,483,648 to Mandatory
Value +2,147,483,647
(Element dependent)
Recommended value of the timer element.
Value 11 -2,147,483,648 to Optional
+2,147,483,647
(Element dependent)
Overrides the recommended value for the timer element.
68P02900W22-S 6-45
Jul 2008
Layout of elements in the MCDF Timer table Chapter 6: MCDF tables
Layout of elements in the MCDF Timer table

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Table 6-11 shows the layout of the timer element parameters in the Timer table.
Table 6-11 Timer table - elements
# Element name Recommended value (ms)

1 add_access_class 60000
2 assign_successful 30000
3 bcch_info 2000
4 bounce_protect_cong_tmr 0
5 bounce_protect_qual_tmr 0
6 bsc_audit 120000
7 bsc_audit_response 30000
8 bssgp_dwnld_retry 3
9 bssgp_t1_timer 3
10 bssgp_t2_timer 60
11 {27717} bssgp_t4_timer 800
15 bssmap_t1 30000
16 bssmap_t4 50000
17 bssmap_t7 30000
18 bssmap_t8 28000
19 bssmap_t10 28000
20 bssmap_t11 28000
21 bssmap_t13 40000
22 bssmap_t19 30000
23 bssmap_t20 30000
24 bssmap_tqho 30000
25 bts_audit 60000
26 bts_audit_response 30000
27 carrier_free_immediate 120000
28 cbch_1 30000
Continued
6-46 68P02900W22-S
Jul 2008
System Information: DataGen Layout of elements in the MCDF Timer table
Table 6-11 Timer table - elements (Continued)

29 cbch_2 30000
30 cbch_3 35000
31 channel_act 10000
32 channel_teardown 28000
33 cipher_comp_ms 28000
34 ciphering_successful 30000
35 circuit_reset_ack 70000
36 clear_cmd_ext_ho 30000
37 clear_command 30000
38 dealloc_inact 5000
39 downlink_sync_timer 1000
40 dynet_retry_time 1000
41 early_classmark_delay 0
42 emerg_reserved 120000
43 ext_rtry_cand_prd 4000
44 ext_ho_allocation 30000
45 flow_control_t1 20000
46 flow_control_t2 30000
47 ho_ack 5000
48 ho_allocation 30000
49 ho_complete 28000
50 ho_request 28000
51 ho_successful 30000
52 hop_count_timer 0
53 initial_sync_timer 4000
54 lb_int_bssmap_t4 50000
55 lb_int_bssmap_t13 40000
56 lb_int_called_pci 0
57 llb_int_calling_pci 0
58 lb_int_clear_command 30000
59 lb_int_cr_calling 0
60 lb_int_dpc 0
61 lb_int_global_reset_repetitions 0
62 lb_int_sccp_released 30000
Continued
68P02900W22-S 6-47
Jul 2008

63 lb_int_sccp_tconn_est 30000
64 lb_int_sccp_tiar 30000
65 lb_int_sccp_tias 30000
66 lb_int_sccp_trel 10000
67 lb_int_spi 60000
68 lb_int_ss7_l2_t1 50000
69 lb_int_ss7_l2_t2 25000
70 lb_int_ss7_l2_t3 1400
71 lb_int_ss7_l2_t4 600
72 lb_int_ss7_l2_t5 100
73 lb_int_ss7_l2_t6 5000
74 lb_int_ss7_l2_t7 1000
75 lb_int_ss7_l3_t1 850
76 lb_int_ss7_l3_t2 1400
77 lb_int_ss7_l3_t4 850
78 lb_int_ss7_l3_t5 850
79 lb_int_ss7_l3_t12 1150
80 lb_int_ss7_l3_t13 1150
81 lb_int_ss7_l3_t14 2500
82 lb_int_ss7_l3_t17 1150
83 lb_int_ss7_l3_t22 270000
84 lb_int_ss7_l3_t23 270000
85 lb_int_ss7_slt_t1 8000
86 lb_int_t_stat_info 90000
87 lcs_perf_location 300000
88 lcs_segmentation 10000
89 lcs_supervision 30000
90 lmtl_loadshare_granularity 0
91 mode_modify 10000
92 mode_rr_modify_ack 28000
93 ms_sapi3_est 28000
94 neighbor_report_timer 10
95 ns_alive_timer 3
96 ns_block_timer 3
Continued
6-48 68P02900W22-S
Jul 2008
System Information: DataGen Layout of elements in the MCDF Timer table

97 ns_reset_period 125
98 ns_reset_timer 40
99 ns_test_timer 30
100 radio_chan_released 30000
101 register_exp 120000
102 rf_chan_rel_ack 10000
103 rr_ny1_rep 20
104 rr_T3101 5000
105 rr_T3103 30000
106 rr_T3105 60
107 rr_T3109 14400
108 rr_T3111_sd 1500
109 rr_T3111_tch 1500
110 rr_T3212 10
111 rtry_cand_prd 4000
112 sacch_info 2000
113 sccp_released 30000
114 sccp_tconn_est 30000
115 sccp_tiar 30000
116 sccp_tias 30000
117 sccp_trel 10000
118 sm_audit_response 30000
119 spi 60000
120 {28337} ss7_hsp_l2_t1 300000
121 ss7_l2_t1 50000
122 ss7_l2_t2 25000
123 ss7_l2_t3 1400
124 ss7_l2_t4 600
125 ss7_l2_t5 100
126 ss7_l2_t6 5000
127 ss7_l2_t7 1000
128 ss7_l3_t1 850
129 ss7_l3_t2 1400
130 ss7_l3_t4 850
Continued
68P02900W22-S 6-49
Jul 2008

131 ss7_l3_t5 850
132 ss7_l3_t12 1150
133 ss7_l3_t13 1150
134 ss7_l3_t14 2500
135 ss7_l3_t17 1150
136 ss7_l3_t22 270000
137 ss7_l3_t23 270000

138
NOTE
ss7_l3_t23 has a value of 270000 if ss7_mode = 0 (ITU) but ss7_l3_t23
has a value of 90000 if ss7_mode = 1 (ANSI).
139 ss7_slt_t1 8000
140 start_ack 30000
141 t_stat_info 90000
142 ts_free_immediate 50000
143 uplink_sync_timer 1000
144 valid_candidate_period 4000
6-50 68P02900W22-S
Jul 2008
System Information: DataGen Modify Value table
Modify Value table

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Modify Value table
This table contains the modify_value commands. The table is applicable only for MMS and LCF
device functions currently as DataGen only supports these devices within the modify_value
command.
Default filename: modv.mcd
Table 6-12 shows the MMS element parameters:
Table 6-12 Modify Value table

Location 3 0 to 120 Mandatory
This field identifies the location (Site) at which the MMS for the MSI/XCDR card, DYNET, or
LCF device resides. Used for the location parameter of the modify_value command.
Value Name 25 Refer Applicable Mandatory
Names below.
Applicable Names
MMS nbit
ber_oos_mon_period
ber_restore_mon_period
phase_lock_duration
mms_priority
hdsl_oos_mon_period
hdsl_restore_mon_period
LCF *max_opls
*max_opls is not currently supported, except for Motorola internal use.
DYNET shared_timeslots
Used for the value_name parameter of the modify_value command.
New Value 6 Refer Range Table Mandatory
below.
The applicable ranges are shown in the following table:
Continued
68P02900W22-S 6-51
Jul 2008
Description of Modify Value table Chapter 6: MCDF tables
Table 6-12 Modify Value table (Continued)

Value Name Minimum Value Maximum Value
nbit 0 1
ber_oos_mon_period 1 60
ber_restore_mon_period 1 18000
phase_lock_duration 0 3600
mms_priority 0 255
max_opls 0 1
hdsl_oos_mon_period 0 3598
hdsl_restore_mon_period 0 65534
shared_timeslots 0 31
Used for the new_value parameter of the modify_value command.
Device Function 5 TEXT Mandatory
MMS, LCF, and DYNET are the only applicable device functions for this table. Used for
dev_func parameter of the modify_value command.
Device Fn ID1 3 Based on site type Mandatory
below:
Used for the dev_fun_id1 parameter of the modify_value command.
MMS - Site Types: 0 to 56/71 at a BSC/RXCDR
0 to 9 at a non-M-Cell BTS
0 to 1 at an M-Cell2 BTS
0 to 3 at an M-Cell6 BTS
0 at an M-Cellmicro BTS
This value defines the MSI identifier for the MMS device function.
LCF: 0 to 24
This value defines the LCF id to which
this modify_value command relates.
DYNET: 0 to 19
This value defines the DYNET first id to which this modify_value
command relates.
Continued
6-52 68P02900W22-S
Jul 2008
System Information: DataGen Description of Modify Value table
Table 6-12 Modify Value table (Continued)

Device Fn ID2 2 0 or 1 Mandatory
Used for the dev_fun_id2 parameter of the modify_value command
MMS: This value defines the MMS identifier for the MMS device function.
LCF: 0 is the only applicable value.

DYNET: 0 to 2.
This value defines the DYNET second id to which this modify_value
command relates.
Device Fn ID3 2 0 Mandatory (Not
required for DYNET).
Used for the dev_fun_id3 parameter of the modify_value command.
This parameter must be entered as required by the modify_value command, but it serves no
purpose to the MMS/LCF/DYNET device functions. It is added to allow support of further
modify_value commands as and when required.
68P02900W22-S 6-53
Jul 2008
Circuit table Chapter 6: MCDF tables
Circuit table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Circuit table
Table 6-13 contains all MTL, LMTL, and OML signaling links. It also contains the terrestrial
circuits to timeslots at the BSC for radio traffic channels. (Typical commands supported are
chg_ts_usage and add_circuit/equip CIC).
NOTE
The MSIs and MMSs required are detailed in the hardware file.
Default filename: acct.mcd
Table 6-13 Circuit table

Site Number 1 0 Mandatory
Value must always be 0 unless Type = RES in which case the full range applies.
This field identifies the Site at which the MSI/XCDR card resides.
MSI 3 {22169} 0 to 95 Mandatory
(0 to 123
for RXCDR)
(0 to 123 for LMTL
devices)
This field refers to the MSI/XCDR ID of the entry.
MMS 1 0 to 1 Mandatory
This field refers to the MMS of the MSI/XCDR card of the entry.
Type 4 String width 4 Mandatory
The type of entry being referred to as follows:
Abbreviation Description
TCH Traffic channel
OML Operations and maintenance link device
OPL Optimization Link
MTL Message transfer link device
LMTL Location message transfer link device
XBL Transcoder base station link
CBL Cell Broadcast Link
RES Reserve specified timeslot(s)
Continued
6-54 68P02900W22-S
Jul 2008
System Information: DataGen Description of Circuit table
Table 6-13 Circuit table (Continued)

Device ID 2 See below Mandatory if Type is CBL,
OML, OPL, MTL, LMTL, or
XBL, otherwise unused.
This field contains the device id for the CBL, OML, OPL, MTL, LMTL, and XBL devices.
The range for the IDs are as follows:
ID Range
CBL 0
OPL 0
OML 0 to 3
MTL 0 to 15
LMTL5 0 to 15
XBL 0 to 9
Associated Device 3 1 to 128 Mandatory if not used for
ID signaling links.
Provides the ID of the associated RXCDR and AXCDR when at the BSS and the associated
BSS and ABSS when at the RXCDR.
At the BSC this is the device ID, which corresponds to the RXCDR which provides the TRAU
resource for the CIC.
At the RXCDR this is the device ID, which corresponds to the BSS which is managing the CIC.
(This field is not valid for local transcoding BSCs).
Start Timeslot 2 1 to 31 Mandatory
The Timeslot at which the defined block is to start.
End Timeslot 2 1 to 31 Mandatory if Type = TCH or
RES, otherwise unused.
The Timeslot at which the defined block is to end.
Start CIC 5 0 to 65,535 Mandatory if Type = TCH,
otherwise unused.
The CIC at which the defined block is to start.
End CIC 5 0 to 65,535 Mandatory if Type = TCH,
otherwise unused.
The CIC at which the defined block is to end.
Start Group 1 0 to 3 Mandatory if Type = TCH,
otherwise unused.
The starting group number for the start timeslot.
Continued
68P02900W22-S 6-55
Jul 2008
Description of Circuit table Chapter 6: MCDF tables
Table 6-13 Circuit table (Continued)

End Group 1 0 to 3 Mandatory if Type = TCH,
otherwise unused.
The ending group number for the end timeslot.
MSC MSI 3 0 to 71 Mandatory if Type = TCH,
otherwise unused.
MSI used to the MSC (valid only for local transcoding BSC and RXCDR sites).
MSC MMS 1 0 to 1 Mandatory if Type = TCH,
otherwise unused.
MSC used to the MSC (valid only for local transcoding BSC and RXCDR sites).
MSC Start Timeslot 2 1 to 31 Mandatory if Type = TCH,
otherwise unused.
The starting timeslot (valid only for local transcoding BSC and RXCDR sites).
MSC End Timeslot 2 1 to 31 Mandatory if Type = TCH,
otherwise unused.
The end timeslot (valid only for local transcoding BSC and RXCDR sites).
BSS Operator 20 20 character string Mandatory if Type = CBL,
otherwise unused.
Used for the BSS Operator name of the equip CBL command.
CBC Operator 20 20 character string Mandatory if Type = CBL,
otherwise unused.
Used for the CBC Operator name of the equip CBL command.
{28337}
DataGen supports the MTL parameter mtl_rate with the following values:
Table 6-14 Values of mtl_rate
Minimum Maximum Default Value definition

1 31 1 1: 64 kbps MTL
31: HSP MTL

Other values are reserved.
The attribute can be set to 31 only when the Increased Network Capacity optional feature
is unrestricted.
6-56 68P02900W22-S
Jul 2008
System Information: DataGen Channel table
Channel table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Channel table
Table 6-15 is required only for Remote Transcoders. This table contains the OML and MTL
signaling links through the remote transcoder. It also contains details of the traffic channels
between the MSC and the BSC on the remote transcoder. The MSIs and MMSs required are
detailed in the hardware table Table 6-7.
Default filename: chan.mcd

Table 6-15 Channel table

Type 4 TEXT Mandatory
The type of entry being referred to as follows:
TCH Traffic channel (add_channel)
LINK OML/MTL/CBL link (add_rxcdr_link/add_link)
MSI A 3 0 to 123 Mandatory
This field refers to the MSI ID of the A side.

MMS A 1 0 to 1 Mandatory
This field refers to the MMS ID of the A side.
Start Timeslot A 2 1 to 31 Mandatory
The A side Timeslot at which the defined block is to start.
End Timeslot A 2 1 to 31 Mandatory
The A side Timeslot at which the defined block is to end.
Start Group A 1 0 to 3 Mandatory if Type
is TCH, otherwise
unused.
The A side group at which the defined block is to start.
End Group A 1 0 to 3 Mandatory if Type
is TCH, otherwise
unused.
The A side group at which the defined block is to end.
MSI B 3 0 to 123 Mandatory
This field refers to the MSI ID of the B side.
Continued
68P02900W22-S 6-57
Jul 2008
Description of Channel table Chapter 6: MCDF tables
Table 6-15 Channel table (Continued)

MMS B 1 0 to 1 Mandatory
This field refers to the MMS ID of the B side.
Start Timeslot B 2 1 to 31 Mandatory
The B side Timeslot at which the defined block is to start.
End Timeslot B 2 1 to 31 Mandatory
The B side Timeslot at which the defined block is to end.
6-58 68P02900W22-S
Jul 2008
System Information: DataGen Links table
Links table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Links table
This table is used for two different tasks (refer to Table 6-16):
• Non-RXCDR area
Contains details of the links between MMSs required by the paths. May also contain
details of the links between the RXCDR and its BSCs used by the XBL feature (add_conn).
• RXCDR area
Contains details of the links between the RXCDR and its BSCs used by the XBL feature
(add_conn and add_bss_conn).
In both cases, the MSIs and MMSs required are detailed in the Hardware table.
Default filename: link.mcd
Table 6-16 Links table

Link Type 4 TEXT Mandatory
PATH - used for identifying links between MMSs required by the paths.
LINK - used for identifying add_conn commands within BSS or RXCDR configurations.
NOTE
Valid for 1620 onwards.
Link Number 3 0 to 999 Mandatory if
area is a BSC or
collocated, unused if
area is an RXCDR.
This field is used as an internal ID to refer to this point-to-point link in the PATHS table. This
number is used as a unique identifier for the LINK within the scope of the BSS.
Site Number A 3 {28398} Mandatory
0 to 140, 253
With Increased
Network Capacity
feature.
This field is used as the A end site identifier. Value must be 0 in the case of an RXCDR area.
Continued
68P02900W22-S 6-59
Jul 2008
Description of Links table Chapter 6: MCDF tables
Table 6-16 Links table (Continued)

TS_SWITCH/Marker Sites
This field may also indicate the TS_SWITCH (marker site) if the Aggregate Abis
option has been purchased.
254 is the value to insert if a TS_SWITCH is required.
NOTE
When the Link Type is LINK, Site Number A should always be 0 for the BSC. Site
Number B is the unique NE ID of the counterpart of the LINK (Transcoder).
MSI A 3 0 to 123, 254 Mandatory
This field is used as the A end MSI identifier.
If Site Number A is a TS_SWITCH (marker site), 254 must be entered as the MSI A value.
MMS A 3 0 to 1, 254 Mandatory
This field is used as the A end MMS identifier.
If Site Number A is a TS_SWITCH (marker site), 254 must be entered as the MMS A value.
Site Number B 3 {28398} Mandatory
0 to 140, 253
With Increased
Network Capacity
feature.
This field is used as the B end site identifier.
This field also indicates the TS_SWITCH (marker site) if the Aggregate Abis option is
purchased.
254 is the value to insert if a TS_SWITCH is required.
MSI B 3 0 to 123, 254 Mandatory
This field is used as the B end MSI identifier.
If Site Number B is a TS_SWITCH (marker site), 254 must be entered as the MSI A value.
MMS B 3 0 to 1, 254 Mandatory
This field is used as the B end MMS identifier.
If Site Number B is a TS_SWITCH (marker site), 254 must be entered as the MMS A value.
6-60 68P02900W22-S
Jul 2008
System Information: DataGen Paths table
Paths table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Paths table
Table 6-17 contains details of all the paths or Dynets within the BSS area (providing signaling
and traffic communication between the BSC and the BTSs), using the links detailed in the links
table. Details of RSLs are also contained in this table.
Default filename: path.mcd
Table 6-17 Paths table

Terminating Site 3 1 to 140 Mandatory
Number
This field is used as the SITE at which the PATH terminates.
For a DYNET device this site should be site 0 (BSC/BSS).
First ID 2 0 to 9 (PATH) Mandatory
0 to 19 (DYNET)
Device Type:
PATH: This field is used as the per SITE Unique PATH device ID.
DYNET: This field is used as the DYNET first device ID.
Second ID 1 0 to 2 Mandatory if DYNET
not applicable for
PATH.
This field is used at the DYNET second device ID. If defined, then an equip DYNET is assumed
else if empty an equip PATH will be inserted.
RSL First ID 3 0 to 140 Optional, each Site
requires an RSL but
not each path to each
site.
This field is used as the first device ID for the RSL device.
RSL Second ID 1 0 to 7 (dependent on Mandatory if the first
type of equipment RSL ID is present,
- see below) refer RSL First ID.
This field is used as the second device ID for the RSL device.
The range is as follows:
Continued
68P02900W22-S 6-61
Jul 2008
Description of Paths table Chapter 6: MCDF tables
Table 6-17 Paths table (Continued)

Field Range
Non-M-Cell 0 to 7
M-Cell2/6 BTS 0 to 5
M-Cellmicro BTS 0 to 1
DYNET Even numbers only (including 0).
LINKS 1 to 11 3 0 to 999 Mandatory
PATH Device
This field is used to identify the links in the chain (1 through 10) that composes the PATH.
Link 1 must terminate at site 0, and Link 10 must terminate at the value specified as the
Terminating Site Number. These links should be defined within the Links table.
It is an error to enter a link that does not terminate one end at the terminating site (refer
to first field above).
DYNET Device
This field is used to identify the links in the chain (1 through 11) that composes the
DYNET. Link 11 may only terminate at the BSC (site 0). These links should be
defined within the Links table.
6-62 68P02900W22-S
Jul 2008
System Information: DataGen LAPD table
LAPD table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of LAPD table
Table 6-18 contains details of the LAPD values for the RSLs and XBLs in the area. The RSLs and
XBLs required are detailed in the circuits and paths tables.
Default filename: lapd.mcd
Table 6-18 LAPD table

Device Type 10 TEXT Mandatory
RSL, XBL
First device ID 3 0 to 120 Mandatory
Type Range Usage
RSL 1-120 First Device ID
XBL 0-19 Device ID
Second device ID 3 0 to 7 Mandatory, if Device Type is
RSL or XBL.
Type Range Usage
RSL 0 to 7 First Device ID
XBL 1 to 254 Refer to the following Note
NOTE
• Identifies at the BSC the device ID which corresponds to the RXCDR which
provides the TRAU resource for the CIC.
• Identifies at the RXCDR the device ID which corresponds to the BSS which is
managing the CIC. This field is not valid for local transcoding BSCs.
XBL data rate 2 16 or 64 Mandatory if Device Type is
XBL AND 16Kbps LAPD XBL
option is purchased, otherwise
unused.
Used for the prompt Enter the data rate for the XBL of the equip XBL command.
Continued
68P02900W22-S 6-63
Jul 2008
Description of LAPD table Chapter 6: MCDF tables
Table 6-18 LAPD table (Continued)

XBL timeslot group 1 0 to 3 Mandatory if Device Type is
XBL AND 16Kbps LAPD XBL
option is purchased AND XBL
data rate of 16 is chosen,
otherwise unused.
Used for the prompt Enter the group of the timeslot where this device appears of
the equip XBL command.
T200 timer value 4 See below Optional
Minimum Maximum Step Size
1400 5000 50
Used for the LAPD T200 timer value.
N200 value 1 1 to 5 Optional
Used for the LAPD N200 value.
K value 3 See below Optional

Minimum Maximum
1 10
Used for the LAPD K value.
6-64 68P02900W22-S
Jul 2008
System Information: DataGen Cell table
Cell table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Cell table
Table 6-19 provides the details of all the cells across the OMC or network and also the external
neighbors used by the cells specified. The optional fields in this table contain information that
overrides the defaults, as specified in the Generics table on page 6-25. {28398} DataGen
supports 250 Cells with Increased Network Capacity feature.
Default filename: cell.mcd
Table 6-19 Cell table

BSS ID 3 0 to 255 or X Mandatory
The bss_id of the BSS in which this cell is located.
X being a cell external to the BSS area, that is, a neighbor of a cell inside this BSS area.
0 to 140, 253
With Increased
Network Capacity
feature.
The Site number, within the BSS, of the Site in which this cell is located. X is a cell external to
the BSS area, that is, a neighbor of a cell inside this BSS area.
MCC 3 3 digit numeric Mandatory
The Mobile Country Code.
MNC 3 3 digit numeric Mandatory
The Mobile Network Code.
The MNC can have optional third digit only for PCS1900 and GSM850 systems.
LAC 6 6 digit numeric Mandatory
The Location Area Code.
Digits can be entered either in decimal or hex. Hex numbers are to be followed by h or
preceded by 0x, for example, 1234h or 0x1234.
CI 6 6 digit numeric Mandatory
The Cell identifier.
Digits can be entered either in decimal or hex form. Hex numbers are to be followed by h or
Cell Name 31 31 character string Optional
The cell name.
Continued
68P02900W22-S 6-65
Jul 2008
Description of Cell table Chapter 6: MCDF tables
Table 6-19 Cell table (Continued)

Frequency Type 1 0, 1, 2, 4, 6 or 8 Mandatory
(See below)
External Neighbors:
Used for the Enter neighbor cell frequency type parameter of the add_neighbor command.
Internal Cells:
Used for the frequency_type parameter of the add_cell command.
The valid frequency types are:
Frequency Type Numeric Entry
PGSM 1
EGSM 2
DCS1800 4
PGSM and DCS1800 5
EGSM and DCS1800 6
PCS1900 8
bsic 4 0 to 63 (hex) Mandatory
Used for the bsic parameter of the add_neighbor command, when this cell is identified as a
neighbor to another cell.
egsm_bcch_sd 1 0 or 1 Optional
This parameter allows the BCCH ARFN to be within the GSM Extension band.
BCCH ARFN 4 Refer Frequency Mandatory
Type Channel
Groupings below:
Used for the bcch_freq_num parameter of the add_neighbor command, when this
cell is identified as a neighbor to another cell.
It is verified by the RTF table while assigning the absolute radio frequency channel to the RTF.
Frequency Type Channel Groupings:
Frequency BCCH
PGSM 1 to 124
EGSM 1 to 124 (975 to 1023, 0 if egsm_bcch_sd is enabled)
DCS1800 512 to 885
PCS1900 512 to 810
ho_margin_cell 3 -63 to 63 Optional
This value is for display purposes. The value is extracted from any add_neighbor commands.
rxlev_min_cell 2 0 to 63 Optional
This value is purely for display purposes. The value is extracted from any add_neighbor
commands.
Continued
6-66 68P02900W22-S
Jul 2008
System Information: DataGen Description of Cell table

ms_txpwr_max_def 2 0 to 39 Optional
For GSM 900

and GSM 900
Extended - 5 to 39,
odd values only.
For DCS 1800 and
PCS1900 - 0 to 30,
even values only.
This value may also be extracted for use with the Neighbor table on page 6-165.
Used for element ms_txpwr_max_def:
rxlev_access_min 2 0 to 63 Optional
If a value is not entered here, a generic value is used (refer to the Generics table on page 6-25).
Used for element rxlev_access_min:
ccch_conf 1 0, 1, 2, 4, 6
Optional, only
used if not an
external cell.
0: 1 Timeslot using Timeslot 0
1: Combined ccch and sdcch on Timeslot 0
2: 2 Timeslots using Timeslots 0 and 2
4: 3 Timeslots using Timeslots 0, 2 and 4
6: 4 Timeslots using Timeslots 0, 2, 4 and 6
Used for element ccch_conf:
bs_ag_blks_res 1 See below for range. Optional, only
used if not an
external cell.
Range:
if ccch_conf = 1: range 0 to 2
if ccch_conf not 1: range 0 to 7.
If a value is not entered here, a generic value is used (refer to the
Generics table on page 6-25).
Used for element bs_ag_blks_res
Continued
68P02900W22-S 6-67
Jul 2008

number_sdcchs_ 3 See below for range. Optional, only
preferred used if not an
external cell.
Range:
When the Increased SDCCH feature is enabled:
if ccch_conf = 1, the range is: 4, 12, 20, 28, 36, 44, 52, 60, 68, 76, 84, 92, 100, 108, 116, 124
if ccch_conf is not 1, the range is: 8,16, 24, 32, 40, 48, 56, 64, 72, 80,
88, 96, 104, 112, 120, 128
When the Increased SDCCH feature is not enabled:
if ccch_conf = 1, the range is: 4, 12, 20, 28, 36, 44
if ccch_conf is not 1, the range is: 8, 16, 24, 32, 40, 48
number_sdcchs_preferred must be <= max_number_of_sdcchs.
Used for element number_sdcchs_preferred:
max_number_of_ 3 12 to 128 Optional, only
sdcchs used if not an
external cell.
When the Increased SDCCH feature is enabled:
if ccch_conf = 1, the range is: 12, 20, 28, 36, 44, 52, 60, 68, 76, 84, 92, 100, 108, 116, 124
if ccch_conf is not 1, the range is: 16, 24, 32, 40, 48, 56, 64, 72, 80, 88, 96, 104, 112, 120, 128
When the Increased SDCCH feature is not enabled:

if ccch_conf = 1, the range is: 12, 20, 28, 36, 44
if ccch_conf is not 1, the range is: 16, 24, 32, 40, 48
The value should be greater than that of number_sdcchs_preferred.

If ext_range_cell is set, then the range is 16 to 20.
The max_number_of_sdcchs default is as follows:
If ccch_conf = 1 and Increased SDCCH feature is unrestricted: 60
If ccch_conf is not 1 and Increased SDCCH feature is unrestricted: 64
If ccch_conf = 1 and SDCCH is restricted: 44
If ccch_conf is not 1 and SDCCH is restricted: 48
Used for element max_number_of_sdcchs:
Continued
6-68 68P02900W22-S
Jul 2008

sdcch_need_high_ 3 See below Optional, only
water_mark used if not an
external cell.
Allowed ranges:
1 to 119 when the Increased SDCCH feature is unrestricted but 1 to 115 if ccch_conf = 1.
1 to 39 when the Increase SDCCH feature is restricted.
sdcch_need_high_water_mark must be greater than or equal to 9
sdcch_need_low_water_mark. It is used for element sdcch_need_high_water_mark:
sdcch_need_low_ 3 See below Optional, only
water_mark used if not an
external cell.
Allowed ranges:
10 to 128 when the Increased SDCCH feature is unrestricted.
10 to 48 when the Increase SDCCH feature is restricted.
sdcch_need_low_water_mark must be less than or equal to max_number_of_sdcchs.
Used for element sdcch_need_low_water_mark:
max_tx_ms 2 5 to 39 - PGSM Optional, only
and EGSM (Odd used if not an
values only). external cell.
0 to 36 - DCS1800
(Even values only).
0 to 32, 33 -
PCS1900 (Even
values only and
value 33).
Used for element max_tx_ms:
ms_txpwr_max_cch 2 5 to 39 - PGSM Optional, only
and EGSM (Odd used if not an
values only). external cell.
0 to 36 - DCS1800
(Even values only).
0 to 32, 33 -
PCS1900 (Even
values only and
value 33).
Used for element ms_txpwr_max_cch:
Continued
68P02900W22-S 6-69
Jul 2008

ms_max_range 3 0 to 630 to 219 (if Optional, only
ext_range_cell is used if not an
enabled). external cell.
Used for element ms_max_range:
ho_margin_def 3 -63 to 63 Optional, only
used if not an
external cell.
Used for element ho_margin_def:
rxlev_min_def 2 0 to 63 Optional
Used for element rxlev_min_def:
handover_power_level 2 0 to 15 Optional, only
used if not an
external cell.
Used for element handover_power_level:
cell_reselect_hysteresis 2 0 to 7 Optional, only
used if not an
external cell.
Used for element cell_reselect_hysteresis:
max_tx_bts 2 0 to 21 (for Optional, only
PCS1900 cells). used if not an
-1 to 21 (for external cell.
PGSM/EGSM and
DCS1800 cells).
Used for element max_tx_bts:
bcch_power_level 2 0 to 21 Optional, only
used if not an
external cell.
Used for element bcch_power_level:
Continued
6-70 68P02900W22-S
Jul 2008

inner_zone_alg 1 0 to 3 (3 is only Optional
valid when the Dual
Band Cell Opt is
purchased).
NOTE
Multi band must be enabled for inner_zone_alg to be modified.
Five parameters are associated with inner_zone_alg as follows:
• ms_txpwr_max_inner
• zone_ho_hyst
• rxlev_dl_zone
• rxlev_ul_zone
• neighbor_report_timer
These parameters may be set using the Generics table on page 6-25 or the Specifics table
on page 6-108.
Used for chg_cell_element inner_zone_alg:
ext_range_cell 1 0 to 2 Optional
One parameter is associated with ext_range_cell as follows:
ms_max_range (if ext_range is set then ms_max_range may be set between 0 and 219).
This parameter may be set using the Cell table field ms_max_range.
Used for chg_cell_element ext_range_cell:
hop_qual_enabled 1 0 to 1 Optional
Four parameters are associated with hop_qual_enabled as follows:
• l_rxqual_dl_h_hopping
• l_rxqual_dl_p_hopping
• l_rxqual_ul_h_hopping
• l_rxqual_ul_p_hopping
on page 6-108.
Continued
68P02900W22-S 6-71
Jul 2008

Used for chg_cell_element hop_qual_enabled:
data_qual_enabled 1 0 to 1 Optional
Four parameters are associated with data_qual_enabled as follows:
• l_rxqual_dl_h_data
• l_rxqual_dl_p_data
• l_rxqual_ul_h_data
• l_rxqual_ul_p_data
on page 6-108.
Used for chg_cell_element data_qual_enabled:
gprs_enabled 1 0 to 1 Optional
Two parameters are associated with gprs_enabled as follows:
• rac
• ra_colour
on page 6-108.
Used for chg_cell_element gprs_enabled:
network_control_order 1 0 to 4 Optional
ts_in_usf_active 1 0 to 3 Optional
inter_rat_enabled 1 0 to 3 Optional
The default value is 0.
qsearch_i 2 0 to 15 Optional
qsearch_c_initial 1 0 to 1 Optional

fdd_qoffset 2 0 to 15 Optional
fdd_qmin 1 0 to 7 Optional
gprs_cell_cgt_thr 1 1 to 4 Optional
Continued
6-72 68P02900W22-S
Jul 2008

gprs_num_pmrs 2 1 to 10 Optional
gprs_cr_margin 2 5 to 40 Optional
persistence 2 0 to 15 Optional
_level,0
Specifies the values of the access persistence level P(i) for each radio priority i (i = 1..4),
where radio priority 1 represents the highest radio priority. The default value is 4.
persistence_level,1 2 0 to 15 Optional
prach_max_ 1 0 to 3 Optional
retran,0
Maximum number of retransmissions allowed for each radio priority level on a per cell basis.
retran,1
retran,2
retran,3
{31400} tdd_qoffset 2 0 to 15 Optional.
Applies an offset
to RLA_C for
cell reselection
to access
TD-SCDMA
mode.
This is a configurable parameter. The default value is 8.
68P02900W22-S 6-73
Jul 2008
NOTE
• To avoid the need for two ms_max_range elements (add_cell and

chg_cell_element), the ms_max_range parameter for ext_range_cell may be
set in the ms_max_range field within the Cell table.
• A default value of 63 is inserted into the ms_max_range parameter of the
add_cell command as the chg_cell_element value overrides this. If this were
not so, the add_cell command would fail to compile with the new range.
6-74 68P02900W22-S
Jul 2008
System Information: DataGen Statistics table
Statistics table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Statistics table
Table 6-20, the Statistics table, contains a list of statistical elements. Either the value from
the value field (if present) or the Motorola recommended value is set bss-wide but may be
overridden for a site or cell by values in the Specifics table.
Default filename: stat.mcd
Table 6-20 Statistics table

Element Name 50 Text: Mandatory
<element name>
[,<index>]
Name of the statistics element, optionally followed by an index.
Recommended 11 -2, 147, 483, 648 Mandatory
Value to
+2, 147, 483, 647
(Element dependent)
Default value of the statistics element.
Value 11 -2, 147, 483, 648 Optional
to
+2, 147, 483, 647
(Element dependent)
Specific value of the statistics element.
68P02900W22-S 6-75
Jul 2008
Layout of elements in the MCDF Statistics table Chapter 6: MCDF tables
Layout of elements in the MCDF Statistics table

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The elements in the Statistics table are displayed in Table 6-21 as follows:
Table 6-21 Statistics table - Elements

1 access_per_agch,0 0
2 access_per_pch_cs,0 1
3 access_per_pch_cs_ps,0 1
4 access_per_pch_ps,0 1
5 access_per_ppch,0 0
6 access_per_rach,0 0
7 air_dl_control_blks,0 0
8 air_ul_control_blks,0 0
9 air_dl_tbf_failures,0 0
10 air_ul_tbf_failures,0 0
11 alloc_sdcch,0 1
12 alloc_sdcch_fail,0 1
13 alloc_sdcch_fail,2 2147483647
14 alloc_sdcch_carr,0 0
15 alloc_tch,0 1
16 alloc_tch_inner_zone,0 1
17 alloc_tch_fail_hr,0 0
18 alloc_tch_fail_inner_zone,0 1
19 alloc_tch_fail_inner_zone,2 2147483647
20 alloc_tch_hr,0 0
21 alloc_tch_fail,0 1
22 alloc_tch_fail,2 2147483647
23 alloc_tch_fail_hr_amr,0 0
24 alloc_tch_carr,0 0
25 alloc_tch_hr_amr,0 0
26 amr_fr_ul_codec_mode_usage,0 0
27 amr_fr_dl_codec_mode_usage,0 0
28 amr_hr_ul_codec_mode_usage,0 0
29 amr_hr_dl_codec_mode_usage,0 0
Continued
6-76 68P02900W22-S
Jul 2008
System Information: DataGen Layout of elements in the MCDF Statistics table
Table 6-21 Statistics table - Elements (Continued)

30 amr_fr_ul_adaptation,0 0
31 amr_fr_dl_adaptation,0 0
32 amr_hr_ul_adaptation,0 0
33 amr_hr_dl_adaptation,0 0
34 amr_increase_thresh_adjust,0 0
35 amr_decrease_thresh_adjust,0 0
36 assignment_redirection,0 1
37 ater_channel_status,0 0
38 ater_emerg_preempt_status,0 0
39 ater_preempt_rqd,0 0
40 ater_preempt_atmpt,0 0
41 ater_preempt_atmpt_swover,0 0
42 ater_preempt_fail,0 0
43 ater_preempt_fail,2 2147483647
44 ater_preempt_fail_swover,0 0
45 available_sdcch,0 0
46 available_tch,0 0
47 available_tch,4,0 0
Continued
68P02900W22-S 6-77
Jul 2008

67 available_tch_hr,0 0
68 available_tch_hr_amr,0 0
69 available_tch_dcs1800,0 0
70 available_tch_egsm,0 0
71 available_tch_pgsm,0 0
72 avg_simul_dl_tbfs,0 0
73 avg_simul_ul_tbfs,0 0
74 bad_ho_refnum_ms,0 0
75 bad_ho_refnum_ms,2 2147483647
76 ber,0 0
77 blocked_dl_tbfs,0 0
78 bss_availability 0
79 bss_ovld_msgs_tx,0 0
80 bsslap_abort_rcv,0 0
81 bsslap_abort_sent,0 0
82 bsslap_ms_pos_cmd,0 0
83 bsslap_ms_pos_resp,0 0
84 bsslap_rej,0 0
85 bsslap_reset,0 0
86 bsslap_ta_req,0 0
87 bsslap_ta_resp,0 0
88 bsslap_toa_req,0 0
89 bssmap_conless_info_rcv,0 0
90 bssmap_conless_info_sent,0 0
91 bssmap_perf_loc_abort_msgs,0 0
92 bssmap_perf_loc_req_msgs,0 0
93 bssmap_perf_loc_resp_msgs,0 0
94 bssmaple_conless_info_rcv,0 0
95 bssmaple_conless_info_sent,0 0
96 bssmaple_perf_loc_abort_msgs,0 0
97 bssmaple_perf_loc_req_msgs,0 0
Continued
6-78 68P02900W22-S
Jul 2008

98 bssmaple_perf_loc_resp_msgs,0 0
99 busy_cics,0 0
100 busy_cics,4,0 0
101 busy_cics,4,1 10
103 busy_cics,4,3 100
104 busy_cics,4,4 200
105 busy_cics,4,5 400
106 busy_cics,4,6 800
107 busy_cics,4,7 1200
108 busy_cics,4,8 1600
109 busy_cics,4,9 2200
110 busy_cics,5,0 9
113 busy_cics,5,3 199
114 busy_cics,5,4 399
115 busy_cics,5,5 799
116 busy_cics,5,6 1199
117 busy_cics,5,7 1599
118 busy_cics,5,8 2199
119 busy_cics,5,9 3200
120 busy_sdcch,0 1
121 busy_sdcch,4,0 0
Continued
68P02900W22-S 6-79
Jul 2008

141 busy_tch,0 1
142 busy_tch,4,0 0
143 busy_tch,4,1 1
144 busy_tch,4,2 3
145 busy_tch,4,3 5
146 busy_tch,4,4 7
147 busy_tch,4,5 9
148 busy_tch,4,6 11
149 busy_tch,4,7 13
150 busy_tch,4,8 15
151 busy_tch,4,9 17
152 busy_tch,5,0 0
153 busy_tch,5,1 2
154 busy_tch,5,2 4
155 busy_tch,5,3 6
156 busy_tch,5,4 8
157 busy_tch,5,5 10
158 busy_tch,5,6 12
159 busy_tch,5,7 14
160 busy_tch,5,8 16
161 busy_tch,5,9 400
162 busy_tch_carr,0 1
163 busy_tch_carr_hr,0 0
164 busy_tch_hr,0 0
165 busy_tch_hr,4,0 0
Continued
6-80 68P02900W22-S
Jul 2008

184 busy_tch_hr,5,9 400
185 busy_tch_hr_amr,0 0
186 busy_tch_hr_amr,4,0 0
Continued
68P02900W22-S 6-81
Jul 2008

206 busy_tch_carr_hr_amr,0 0
207 busy_tch_dcs1800,0 0
208 busy_tch_egsm,0 0
209 busy_tch_pgsm,0 0
210 call_sp_vers_downgrade_monitor,0 0
211 calls_queued,0 0
212 calls_queued,2 2147483647
213 calls_queued,2,0 65534
214 {32340} cell_barred_delay 0
215 ch_req_unsvcd_pcu,0 0
216 chan_dl_tx_pwr_lvl,0 0
217 chan_dl_tx_pwr_lvl,4,0 0
Continued
6-82 68P02900W22-S
Jul 2008

237 chan_req_cause_atmpt,0 0
238 chan_ul_tx_pwr_lvl,0 0
239 chan_ul_tx_pwr_lvl,4,0 0
259 chan_req_ms_blk,0 0
260 chan_req_ms_blk,2 2147483647
261 chan_req_ms_fail,0 0
262 chan_req_ms_fail,2 2147483647
263 chan_req_ms_fail,2,0 65534
266 channel_reqs_rec,0 0
267 channel_reqs_reject,0 0
Continued
68P02900W22-S 6-83
Jul 2008

268 channel_reqs_success,0 0
269 cipher_mode_fail,0 0
270 cipher_mode_fail,2 2147483647
271 classmk_update_fail,0 0
272 classmk_update_fail,2 2147483647
273 clr_cmd_from_msc,0 0
274 clr_req_to_msc,0 0
275 coding_scheme_change,0 0
276 congest_exist_ho_atmpt,0 0
277 congest_stand_ho_atmpt,0 0
278 congestion_lost_msu,0 0
279 congestion_lost_msu,2 2147483647
280 cong_rel_dl_scts,0 0
281 conn_refused,0 0
282 conn_req_to_msc,0 0
283 cpu_usage,0 0
284 cpu_usage,4,0 0
285 cpu_usage,4,1 11
Continued
6-84 68P02900W22-S
Jul 2008

303 cpu_usage,5,9 100
304. cs12_on_32k_chan,0 0
305 cs1234_on_64k_chan,0 0
306 cs_page_reqs,0 0
307 {33397} 0
cs_paging_msgs_from_msc,0
308 dl_bler_cs1,0 0
309 dl_bler_cs2,0 0
310 dl_bler_cs3,0 0
311 dl_bler_cs4,0 0
312 dl_bler_mcs1,0 0
321 dl_busy_pdtch,0 0
322 dl_busy_pdtch,4,0 0
Continued
68P02900W22-S 6-85
Jul 2008

342 dl_egprs_backhaul_demand,0 0
343 dl_egprs_backhaul_used,0 0
344 dl_llc_frames_gb,0 0
345 dl_llc_frames_pcu,0 0
346 dl_llc_data_volume,0 0
347 dl_pdtch_congestion,0 0
348 dl_pdtch_q_length,0 0
349 dl_pdtch_seizure,0 0
350 dl_radio_blks_1_ts,0 0
354 dl_rlc_ack_new_blks,0 0
355 dl_rlc_ddtr_blks,0 0
356 dl_rlc_nack_blks,0 0
357 dl_rlc_retx_blks,0 0
358 dl_rlc_stalled_blks,0 0
359 dl_rlc_unack_new_blks,0 0
360 dl_tbf_time_1_ts,0 0
364 dynet_assign_fail,0 0
365 dynet_call_rejects,0 0
366 egprs_64k_channel_width,0 0
367 egprs_64k_channels_switched,0 0
368 egprs_64k_not_avail,0 0
Continued
6-86 68P02900W22-S
Jul 2008

369 egprs_avail_pdtch,0 0
370 egprs_dl_asgn_pccch,0 0
371 er_intra_cell_ho_atmpt,0 0
372 er_intra_cell_ho_suc,0 0
373 {28351} {26740} 0
eth_rx_byte
374 {28351} {26740} 1
eth_rx_error
375 {28351} {26740} eth_rx_pkt 0
376 {28351} {26740} 0
eth_tx_byte
377 {28351} {26740} 1
eth_tx_error
378 {28351} {26740} eth_tx_pkt 0
379 {26881} ext_ul_exits,0 0
380 {26881} ext_ul_usf_usage,0 0
381 fer,0 0
382 fer_non_amr,0 0
383 fer_amr_fr,0 0
384 fer_amr_hr,0 0
385 fer_gsm_fr_efr,0 0
386 fer_gsm_hr,0 0
387 flow_control_barred,0 0
388 frmr,0 0
389 frmr,2 2147483647
390 g_rach_unsvcd_bts,0 0
391 gbl_link_ins,0 0
392 gbl_dl_data_thrput,0 0
393 gbl_flow_ctrl_sent,0 0
394 gbl_paging_reqs,0 0
395 gbl_dl_data_thrput_hist,0 0
396 gbl_dl_data_thrput_hist,4,0 0
Continued
68P02900W22-S 6-87
Jul 2008

416 gbl_ul_data_thrput_hist,0 0
417 gbl_ul_data_thrput_hist,4,0 0
Continued
6-88 68P02900W22-S
Jul 2008

437 gbl_ul_data_thrput,0 0
438 gbl_unavailable,0 0
439 gci_for_16kpd_demand,0 0
442 gprs_access_per_agch,0 0
443 gprs_access_per_rach,0 0
444 gprs_avail_pdtch,0 0
445 gprs_cell_congestion,0 0
446 gprs_cell_reselect_attmpt,0 0 (not supported)
447 gprs_cell_reselect_fail,0 0
448 gprs_channels_switched,0 0
449 gprs_32k_channels_switched,0 0
450 gprs_32k_dl_not_avail,0 0
451 gprs_32k_ul_not_avail,0 0
452 gprs_dl_asgn_pccch,0 0
453 gprs_dynet_failures,0 0
454 gprs_dynet_res_reqs,0 0
455 gprs_dynet_res_reqs,4,0 0
Continued
68P02900W22-S 6-89
Jul 2008

476 gprs_dynet_swi_reqs,0 0
477 gprs_dynet_swi_reqs,4,0 0
497 gprs_ms_neighbor_strong 0
498 gprs_pch_agch_q_length,0 0
499 gprs_ppch_pagch_q_length,0 0
500 gprs_prr_blk_usg,0 0
501 gprs_prr_blk_usg,4,0 0
Continued
6-90 68P02900W22-S
Jul 2008

521 gprs_rach_arrival,0 0
522 gprs_rach_arrival,4,0 0
Continued
68P02900W22-S 6-91
Jul 2008

542 {23306} 0
ho_blkd_bsp_overload
543 ho_fail_no_resources,0 0
544 ho_req_ack_to_msc,0 0
545 ho_req_from_msc,0 0
546 ho_req_msc_fail,0 0
547 ho_req_msc_fail,2 2147483647
558 ho_req_msc_proto,0 0
559 ho_req_msc_proto,2 2147483647
560 i_frames_rx,0 0
561 i_frames_tx,0 0
562 {31565} 0
ia_iar_msgs_per_agch,0
563 idle_pdtch_intf_band0,0 0
568 idle_tch_intf_band0,0 0
573 imm_assgn_cause,0 0
574 in_inter_bss_ho,0 1
575 in_intra_bss_ho,0 1
576 in_intra_bss_nc_atmpt,0 0
577 in_intra_bss_nc_suc,0 0
578 interband_activity,0 0
579 intf_on_idle,0 0
Continued
6-92 68P02900W22-S
Jul 2008

580 intf_on_idle,4,0 0
600 intra_bss_ho_cause_suc,0 0
601 intra_cell_ho,0 1
602 inv_est_cause_on_rach,0 0 (not supported)
603 invalid_frames_rx,0 0
604 invalid_frames_rx,2 2147483647
605 l_routing_syntax,0 0
606 l_routing_syntax,2 2147483647
607 l_routing_unknown,0 0
608 l_routing_unknown,2 2147483647
609 l_sccp_msgs,0 0
610 l_sccp_msgs_rx,0 0
611 l_sccp_msgs_tx,0 0
612 l_sif_sio_rx_opc,0 0
613 l_sif_sio_tx_dpc,0 0
Continued
68P02900W22-S 6-93
Jul 2008

614 l_sif_sio_type,0 0
615 l_sl_stop_congestion,0 0
616 lapd_congestion,0 0
617 lmtp_changeback,0 0
618 lmtp_changeover,0 0
619 lmtp_congestion,0 0
620 lmtp_congestion_lost_msu,0 0
621 lmtp_congestion_lost_msu,2 2147483647
622 lmtp_link_ins,0 0
623 lmtp_linkfail,0 0
624 lmtp_local_busy,0 0
625 lmtp_local_mgt,0 0
626 lmtp_local_sl_congestion,0 0
627 lmtp_local_sl_congestion,2 2147483647
628 lmtp_mgt_inhibit,0 0
629 lmtp_mgt_uninhibit,0 0
630 lmtp_msu_discarded,0 0
631 lmtp_msu_discarded,2 2147483647
632 lmtp_msu_rx,0 0
633 lmtp_msu_tx,0 0
634 lmtp_neg_acks,0 0
635 lmtp_neg_acks,2 2147483647
636 lmtp_re_tx,0 0
637 lmtp_re_tx,2 2147483647
638 lmtp_remote_mgt,0 0
639 lmtp_remote_proc,0 0
640 lmtp_remote_sl_congestion,0 0
641 lmtp_remote_sl_congestion,2 2147483647
642 lmtp_restoration,0 0
643 lmtp_sib_rx,0 0
644 lmtp_sib_tx,0 0
645 lmtp_sif_sio_rx,0 0
646 lmtp_sif_sio_tx,0 0
647 lmtp_sl_ack,0 0
Continued
6-94 68P02900W22-S
Jul 2008

648 lmtp_sl_ack,2 2147483647
649 lmtp_sl_alignment,0 0
650 lmtp_sl_alignment,2 2147483647
651 lmtp_sl_error_rate,0 0
652 lmtp_sl_error_rate,2 2147483647
653 lmtp_sl_fail,0 0
654 lmtp_sl_fail,2 2147483647
655 lmtp_sl_fibr,0 0
656 lmtp_sl_fibr,2 2147483647
657 lmtp_start_rpo,0 0
658 lmtp_start_rpo,2 2147483647
659 lmtp_stop_rpo,0 0
660 lmtp_su_error,0 0
661 lmtp_su_error,2 2147483647
662 lmtp_unavailable,0 0
663 ma_cmd_to_ms,0 0
664 ma_cmd_to_ms_blkd,0 1
665 ma_cmd_to_ms_blkd,2 2147483647
666 ma_complete_from_ms,0 0
667 ma_complete_to_msc,0 0
668 ma_fail_from_ms,0 0
669 ma_fail_from_ms,2 2147483647
670 ma_req_from_msc,0 1
671 ma_req_from_msc_fail,0 0
672 ma_req_from_msc_fail,2 2147483647
673 ma_req_sdcch_pg_rsp,0 0
674 ms_access_by_type,0 0
675 ms_tch_usage_by_type,0 0
676 msc_ovld_msgs_rx,0 0
677 msgs_discard_on_gproc,0 0
678 msgs_discard_on_rsl,0 0
679 msu_discarded,0 0
680 msu_discarded,2 2147483647
681 mt_lcs_on_sdcch,0 1
Continued
68P02900W22-S 6-95
Jul 2008

682 mtp_changeback,0 0
683 mtp_changeover,0 0
684 mtp_congestion,0 0
685 mtp_link_ins,0 1
686 mtp_linkfail,0 0
687 mtp_local_busy,0 0
688 mtp_local_mgt,0 0
689 mtp_mgt_inhibit,0 0
690 mtp_mgt_uninhibit,0 0
691 mtp_msu_rx,0 1
692 mtp_msu_tx,0 1
693 mtp_neg_acks,0 0
694 mtp_neg_acks,2 2147483647
695 mtp_re_tx,0 0
696 mtp_re_tx,2 2147483647
697 mtp_remote_mgt,0 0
698 mtp_remote_proc,0 0
699 mtp_restoration,0 0
700 mtp_sif_sio_rx,0 1
701 mtp_sif_sio_tx,0 1
702 mtp_sl_ack,0 0
703 mtp_sl_ack,2 2147483647
704 mtp_sl_alignment,0 0
705 mtp_sl_alignment,2 2147483647
706 mtp_sl_congestion,0 0
707 mtp_sl_congestion,2 2147483647
708 mtp_sl_error_rate,0 0
709 mtp_sl_error_rate,2 2147483647
710 {28337} 0
mtp_sl_error_rate_hsp
711 {28337} 2147483647
mtp_sl_error_rate_hsp,2
712 mtp_sl_fail,0 0
713 mtp_sl_fail,2 2147483647
714 mtp_sl_fibr,0 0
Continued
6-96 68P02900W22-S
Jul 2008

715 mtp_sl_fibr,2 2147483647
716 mtp_start_rpo,0 0
717 mtp_start_rpo,2 2147483647
718 mtp_stop_rpo,0 0
719 mtp_su_error,0 0
720 mtp_su_error,2 2147483647
721 mtp_unavailable,0 0
722 n2_expiry,0 0
723 n2_expiry,2 2147483647
724 no_pdtch_avail,0 0
725 no_pdtch_avail_time,0 0
726 num_cell_resel_cell,0 0
727 num_cell_resel_cell_pccn,0 0
728 num_cell_resel_cell_succ,0 0
729 num_emerg_access,0 0
730 num_emerg_rejected,0 0
731 num_emerg_tch_kill,0 0
732 num_emerg_term_sdcch,0 0
733 num_ho_to_3g_attempts,0 0
734 num_ho_from_3g_attempts,0 0
735 num_ho_from_3g_success,0 0
736 num_ho_to_3g_res_alloc_succ,0 0
737 num_ho_to_3g_success,0 0
738 num_multirat_ms_orig_call,0 0
739 {27717} 0
num_susp_resu_rcvd
740 num_t3121_expiry,0 0
741 ok_acc_proc,0 1
742 ok_acc_proc_suc_rach,0 0
743 out_ho_cause_atmpt,0 0
744 out_inter_bss_ho,0 1
745 out_inter_bss_ho,2 65534
746 out_intra_bss_ho,0 1
747 out_intra_bss_nc_atmpt,0 0
Continued
68P02900W22-S 6-97
Jul 2008

748 out_intra_bss_nc_suc,0 0
749 pacch_page_reqs,0 0
750 packet_sysinfo_req,0 0
751 packet_sysinfo_resp,0 0
752 page_req_from_msc,0 0
753 page_req_from_msc_fail,0 0
754 page_req_from_msc_fail,2 2147483647
755 page_req_from_smlc_fail,0 0
756 page_req_from_smlc_fail,2 2147483647
757 paging_requests_cs,0 0
758 paging_requests_ps,0 0
759 path_balance,0 0
760 path_balance,4,0 0
780 pch_agch_q_length,0 0
781 pch_q_page_discard,0 0
Continued
6-98 68P02900W22-S
Jul 2008

782 pch_q_page_discard,2,0 65534
783 pch_q_page_discard,2,1 65534
784 pdu_discard_fr,0 0
785 pdu_discard_llc,0 0
786 pfc_admission,0 0
787 {27703A} 0
pfc_admission_other,0
788 {27703A} 0
pfc_admission_traffic_class,0
789 pfc_downgrade_success,0 0
790 pfc_downgrade_failure,0 0
791 {27703A} pfc_gbr_dl,0 0
792 {27703A} pfc_gbr_ul,0 0
793 pfc_preemptions,0 0
794 {27703A} 0
pfc_preemptions_traffic_class,0
795 pfc_rejection,0 0
796 {27703A} 0
pfc_rejection_other,0
797 {27703A} 0
pfc_rejection_traffic_class,0
798 {27703A} 0
pfc_reject_causes,0
799 pfc_rej_dgrd_prmpt_prp,0 0
800 pfc_rej_dgrd_prmpt_cell,0 0
801 {27703A} 0
pfc_transfer_delay,0
802 pfc_upgrade,0 0
803 ppch_q_page_discard,0 0
804 preempt_cap 0
805 {23306} 1
processor_critical_overload
806 {23306} 1
processor_safe_overload
807 prp_load,0 0
808 prp_load,4,0 0
809 prp_load,4,1 3
Continued
68P02900W22-S 6-99
Jul 2008

810 prp_load,4,2 6
811 prp_load,4,3 11
812 prp_load,4,4 21
813 prp_load,4,5 41
814 prp_load,4,6 61
815 prp_load,4,7 101
816 prp_load,4,8 161
817 prp_load,4,9 261
818 prp_load,5,0 2
819 prp_load,5,1 5
820 prp_load,5,2 10
821 prp_load,5,3 20
822 prp_load,5,4 40
823 prp_load,5,5 60
824 prp_load,5,6 100
825 prp_load,5,7 160
826 prp_load,5,8 260
827 prp_load,5,9 400
828 prp_pd_demand,0 0
829 ps_page_reqs,0 0
830 {26740} 1
psi_trau_fill_frame_tx
831 queue_preempt_atmpt 0
832 rber,0 0
833 rf_losses_sd,0 1
834 rf_losses_sd,2 32767
835 rf_losses_tch,0 1
836 rf_losses_tch,2 32767
837 rf_losses_tch_hr,0 0
838 rf_losses_tch_hr,2 2147483647
839 rf_losses_tch_hr_amr,0 0
840 rf_losses_tch_hr_amr,2 2147483647
841 roc,0 0
842 roc,4,0 7
Continued
6-100 68P02900W22-S
Jul 2008

843 roc,4,1 14
844 roc,4,2 21
845 roc,4,3 28
846 roc,4,4 35
847 roc,4,5 42
848 roc,4,6 49
849 roc,4,7 55
850 roc,4,8 64
851 roc,4,9 6
852 roc,5,0 13
853 roc,5,1 20
854 roc,5,2 27
855 roc,5,3 34
856 roc,5,4 41
857 roc,5,5 48
858 roc,5,6 54
859 roc,5,7 63
860 roc,5,8 219
861 roc,5,9 0
862 routing_syntax,0 0
863 routing_syntax,2 2147483647
864 routing_unknown,0 0
865 routing_unknown,2 2147483647
866 {22266} rsl_link_ins 0
867 rsl_lcf_congestion,0 1
868 rsl_lcf_congestion,2 2147483647
869 {22266} rsl_rx_octets 0
870 {22266} rsl_tx_octets 0
871 sabm_tx,0 0
872 sccp_msgs,0 0
873 sccp_msgs_rx,0 0
874 sccp_msgs_tx,0 0
875 sdcch_congestion,0 0
876 sdcch_handover,0 1
Continued
68P02900W22-S 6-101
Jul 2008

877 second_assign_atmpt,0 0
878 second_assign_suc,0 0
879 sib_rx,0 1
880 sib_tx,0 1
881 sif_sio_rx_opc,0 0
882 sif_sio_tx_dpc,0 0
883 sif_sio_type,0 0
884 sl_congestion,0 0
885 sl_congestion,2 2147483647
886 sl_stop_congestion,0 0
887 sms_init_on_sdcch,0 0
888 sms_init_on_sdcch_ho_in,0 0
889 sms_init_on_sdcch_ho_out,0 1
890 sms_init_on_tch,0 0
891 sms_no_bcast_msg,0 0
892 tbf_dl_asgn_pacch,0 0
893 tbf_rel_pacch_lost,0 0
894 tbf_sessions,0 0
895 tch_cong_inner_zone,0 0
896 tch_congestion,0 0
897 tch_congestion_hr,0 0
898 tch_congestion_hr_amr,0 0
899 tch_cong_inner_zone_hr,0 0
900 tch_cong_inner_zone_hr_amr,0 0
901 tch_delay,0 0
902 tch_delay,4,0 0
903 tch_delay,4,1 10001
904 tch_delay,4,2 20001
905 tch_delay,4,3 30001
906 tch_delay,4,4 40001
907 tch_delay,4,5 50001
908 tch_delay,4,6 60001
909 tch_delay,4,7 70001
910 tch_delay,4,8 80001
Continued
6-102 68P02900W22-S
Jul 2008

911 tch_delay,4,9 90001
912 tch_delay,5,0 10000
913 tch_delay,5,1 20000
914 tch_delay,5,2 30000
915 tch_delay,5,3 40000
916 tch_delay,5,4 50000
917 tch_delay,5,5 60000
918 tch_delay,5,6 70000
919 tch_delay,5,7 80000
920 tch_delay,5,8 90000
921 tch_delay,5,9 100000
922 tch_preempt_atmpt,0 0
923 tch_preempt_fail_no_cand,0 0
924 tch_preempt_fail_no_cand,2 2147483647
925 tch_preempt_fail_timeout,0 0
926 tch_preempt_no_q_alloc 0
927 tch_preempt_rqd,0 0
928 tch_q_length,0 0
929 tch_q_length,4,0 0
Continued
68P02900W22-S 6-103
Jul 2008

949 tch_q_removed,0 1
950 tch_usage,0 0
951 tch_usage_ext_range,0 0
952 tch_usage_inner_zone,0 0
953 timer_exp_pap_conv,0 0
954 total_calls,0 1
955 total_gci_for_pd_demand,0 0
956 u_ber,0 0
957 u_ber,4,0 0
958 u_ber,4,1 1
959 u_ber,4,2 2
960 u_ber,4,3 3
961 u_ber,4,4 4
962 u_ber,4,5 5
963 u_ber,4,6 6
964 u_ber,4,7 7
965 u_ber,4,8 8
966 u_ber,4,9 9
967 u_ber,5,0 0
968 u_ber,5,1 1
969 u_ber,5,2 2
970 u_ber,5,3 3
971 u_ber,5,4 4
972 u_ber,5,5 5
973 u_ber,5,6 6
974 u_ber,5,7 7
975 u_ber,5,8 8
976 u_ber,5,9 9
977 ul_bler_cs1,0 0
978 ul_bler_cs2,0 0
Continued
6-104 68P02900W22-S
Jul 2008

979 ul_bler_cs3,0 0
980 ul_bler_cs4,0 0
981 ul_bler_mcs1,0 0
990 ul_busy_pdtch,0 0
991 ul_busy_pdtch,4,0 0
1011 ul_egprs_backhaul_demand,0 0
1012 ul_egprs_backhaul_used,0 0
Continued
68P02900W22-S 6-105
Jul 2008

1013 ul_llc_frames,0 0
1014 ul_llc_data_volume,0 0
1015 ul_pdtch_congestion,0 0
1016 ul_pdtch_q_length,0 0
1017 ul_pdtch_seizure,0 0
1018 ul_radio_blks_8psk_1_ts,0 0
1019 ul_radio_blks_8psk_2_ts,0 0
1020 {23292} 0
ul_radio_blks_8psk_3_ts,0
1021 {23292} 0
ul_radio_blks_8psk_4_ts,0
1022 ul_radio_blks_gmsk_1_ts,0 0
1023 ul_radio_blks_gmsk_2_ts,0 0
1024 {23292} 0
ul_radio_blks_gmsk_3_ts,0
1025 {23292} 0
ul_radio_blks_gmsk_4_ts,0
1026 ul_rlc_ack_new_blks,0 0
1027 {33863} ul_rlc_nack_blks,0 0
1028 ul_rlc_retx_blks,0 0
1029 {33863} ul_rlc_stalled_blks,0 0
1030 ul_rlc_unack_new_blks,0 0
1031 ul_tbf_time_8psk_1_ts,0 0
1032 ul_tbf_time_8psk_2_ts,0 0
1033 {23292} 0
ul_tbf_time_8psk_3_ts,0
1034 {23292} 0
ul_tbf_time_8psk_4_ts,0
1035 ul_tbf_time_gmsk_1_ts,0 0
1036 ul_tbf_time_gmsk_2_ts,0 0
1037 {23292} 0
ul_tbf_time_gmsk_3_ts,0
1038 {23292} 0
ul_tbf_time_gmsk_4_ts,0
1039 uplink_path_loss,0 0
1040 uplink_path_loss,4,0 47
Continued
6-106 68P02900W22-S
Jul 2008

1060 zone_change_atmpt,0 0
1061 zone_change_suc,0 0
68P02900W22-S 6-107
Jul 2008
Specifics table Chapter 6: MCDF tables
Specifics table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Specifics table
The Specifics table (Table 6-22) allows the user to specify specific values for chg_element
and add_cell elements for a particular site or cell overriding the parameters specified in the
Generics, Timers, and Statistics tables.
NOTE
• Elements that can exist in the Cell table are not shown in the Specifics table.
• Some elements exist here but do not exist in the Generics, Timer, or Statistics
table because of restrictions such as the elements have no specific default value,
or elements that are specific to particular site/cell configurations.
• Some elements that exist within the Generics, Timers, or Statistics tables do not
exist here because they are only required for site 0 (BSC). Therefore, there may
only be one instance of the element.
Default filename: spec.mcd
Table 6-22 Specifics table
Element Name 50 Text: Mandatory

<element name>
[,<index>]
This field identifies the element for which a specific value is required. The specific element
name is optionally followed by an index.
Continued
6-108 68P02900W22-S
Jul 2008
System Information: DataGen Description of Specifics table
Table 6-22 Specifics table (Continued)

0 to 140, 253
With Increased
Network Capacity
feature.
This field is used to identify the site at which the specific value is required.
For the following elements, this field is used for the BSS_ID (range 0 to 31 ) parameter of
the chg_element command, not the site number. In RXCDRs the Site Number for these
elements is fixed as site 0.
• efr_enabled
• dl_audio_lev_offset
• ul_audio_lev_offset
• volume_control_type
• enh_ter_cic_mgt_ena
LAC 6 6 digit numeric Optional
The Location Area Code. This field can be entered in decimal or hex form.
Hex numbers must be followed by h or preceded by 0x, for example, 1234h or 0x1234.
This field is used as the LAC of the Cell for which the specific value is required.
CI 6 6 digit numeric Optional (mandatory
if the LAC field
contains a cell's LAC).
The Cell identifier can be entered in decimal or hex form.
Hex numbers must be followed by h or preceded by 0x, for example, 1234h or 0x1234.
This field is used as the CI of the Cell for which the specific value is required.
Value 11 -2, 147, 483, 647 Mandatory
to
+2, 147, 483, 647
(Element dependent)
This field is used as the specific value.
68P02900W22-S 6-109
Jul 2008
Layout of elements in the MCDF Specifics table Chapter 6: MCDF tables
Layout of elements in the MCDF Specifics table

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The elements in the Specifics table are displayed in Table 6-23 as follows:
Table 6-23 Specifics table - Elements
# Element Name
1 {31565} _cell_data,20
2 access_per_agch,0
3 access_per_pch_cs,0
4 access_per_pch_cs_ps,0
5 access_per_pch_ps,0
6 access_per_ppch,0
7 access_per_rach,0
8 adap_ho_alt_trigger_rxqual
9 adap_ho_pbgt
10 adap_ho_rxlev
11 adap_ho_rxqual
12 adap_trigger_hop_rxqual_dl
13 adap_trigger_hop_rxqual_ul
14 adap_trigger_pbgt
15 adap_trigger_rxlev_dl
16 adap_trigger_rxlev_ul
17 adap_trigger_rxqual_dl
18 adap_trigger_rxqual_ul
19 air_dl_control_blks,0
20 air_dl_tbf_failures,0
21 air_ul_control_blks,0
22 air_ul_tbf_failures,0
23 alloc_sdcch,0
24 alloc_sdcch_carr,0
25 alloc_sdcch_fail,0
26 alloc_sdcch_fail,2
27 alloc_tch,0
28 alloc_tch_carr,0
29 alloc_tch_fail,0
Continued
6-110 68P02900W22-S
Jul 2008
System Information: DataGen Layout of elements in the MCDF Specifics table
Table 6-23 Specifics table - Elements (Continued)

# Element Name
30 alloc_tch_fail,2
31 alloc_tch_fail_hr,0
32 alloc_tch_fail_hr_amr,0
33 alloc_tch_fail_inner_zone,0
34 alloc_tch_hr,0
35 alloc_tch_hr_amr,0
36 alloc_tch_inner_zone,0
37 alt_qual_proc
38 amr_decrease_thresh_adjust,0
39 amr_fr_dl_adaptation,0
40 amr_fr_dl_codec_mode_usage,0
41 amr_fr_dl_la_enabled
42 amr_fr_ul_adaptation,0
43 amr_fr_ul_codec_mode_usage,0
44 amr_fr_ul_la_enabled
45 amr_full_rate_enabled
46 amr_half_rate_enabled
47 amr_hr_dl_adaptation,0
48 amr_hr_dl_codec_mode_usage,0
49 amr_hr_dl_la_enabled
50 amr_hr_res_ts
51 amr_hr_ul_adaptation,0
52 amr_hr_ul_codec_mode_usage,0
53 amr_hr_ul_la_enabled
54 amr_increase_thresh_adjust,0
55 amr_new_calls_hr
56 assignment_redirection,0
57 {30830} asym_edge_enabled
58 ater_channel_status,0
59 ater_emerg_preempt_status,0
60 ater_preempt_atmpt,0
61 ater_preempt_atmpt_swover,0
62 ater_preempt_fail,0
63 ater_preempt_fail,2
Continued
68P02900W22-S 6-111
Jul 2008

# Element Name
64 ater_preempt_fail_swover,0
65 ater_preempt_rqd,0
66 attach_detach
67 {25002} audit_type
68 auto_rf_loss_trace
69 available_sdcch,0
70 available_tch,0
71 available_tch,4,0
91 available_tch_dcs1800,0
92 available_tch_egsm,0
93 available_tch_hr
94 available_tch_hr_amr,0
95 available_tch_pgsm,0
96 avg_simul_dl_tbfs,0
97 avg_simul_ul_tbfs,0
Continued
6-112 68P02900W22-S
Jul 2008

# Element Name
98 bad_ho_refnum_ms,0
99 bad_ho_refnum_ms,2
100 band_preference
101 band_preference_mode
102 bep_period
103 bep_period2
104 ber,0
105 ber_loss_daily
106 ber_loss_hourly
107 blind_search_preference
108 blocked_dl_tbfs,0
109 bounce_protect_cong_tmr
110 bounce_protect_margin
111 bounce_protect_qual_tmr
112 bs_pa_mfrms
113 bs_pag_blks_res
114 bs_pbcch_blks
115 bs_pcc_chans
116 bs_prach_blks
117 bss_availability
118 bss_msc_overload_allowed
119 bss_ovld_msgs_tx,0
120 bssgp_block_retries
121 bssgp_dwnld_retry
122 bssgp_fc_period_c
123 bssgp_racap_retries
124 bssgp_reset_retries
125 bssgp_t1_timer
126 bssgp_t2_timer
127 bssgp_t5_timer
128 bssgp_t6_timer
129 bssgp_t8_timer
130 bssgp_unblock_retries
131 bts_escalation
Continued
68P02900W22-S 6-113
Jul 2008

# Element Name
132 bts_p_con_ack
133 bts_p_con_interval
134 bts_power_control_allowed
135 bts_txpwr_max_inner
136 busy_cics,0
137 busy_cics,4,0
138 busy_cics,4,1
139 busy_cics,4,2
140 busy_cics,4,3
141 busy_cics,4,4
142 busy_cics,4,5
143 busy_cics,4,6
144 busy_cics,4,7
145 busy_cics,4,8
146 busy_cics,4,9
147 busy_cics,5,0
148 busy_cics,5,1
149 busy_cics,5,2
150 busy_cics,5,3
151 busy_cics,5,4
152 busy_cics,5,5
153 busy_cics,5,6
154 busy_cics,5,7
155 busy_cics,5,8
156 busy_cics,5,9
157 busy_sdcch,0
158 busy_sdcch,4,0
159 busy_sdcch,4,1
160 busy_sdcch,4,2
161 busy_sdcch,4,3
162 busy_sdcch,4,4
163 busy_sdcch,4,5
164 busy_sdcch,4,6
165 busy_sdcch,4,7
Continued
6-114 68P02900W22-S
Jul 2008

# Element Name
166 busy_sdcch,4,8
167 busy_sdcch,4,9
168 busy_sdcch,5,0
169 busy_sdcch,5,1
170 busy_sdcch,5,2
171 busy_sdcch,5,3
172 busy_sdcch,5,4
173 busy_sdcch,5,5
174 busy_sdcch,5,6
175 busy_sdcch,5,7
176 busy_sdcch,5,8
177 busy_sdcch,5,9
178 busy_tch,0
179 busy_tch,4,0
180 busy_tch,4,1
181 busy_tch,4,2
182 busy_tch,4,3
183 busy_tch,4,4
184 busy_tch,4,5
185 busy_tch,4,6
186 busy_tch,4,7
187 busy_tch,4,8
188 busy_tch,4,9
189 busy_tch,5,0
190 busy_tch,5,1
191 busy_tch,5,2
192 busy_tch,5,3
193 busy_tch,5,4
194 busy_tch,5,5
195 busy_tch,5,6
196 busy_tch,5,7
197 busy_tch,5,8
198 busy_tch,5,9
199 busy_tch_carr,0
Continued
68P02900W22-S 6-115
Jul 2008

# Element Name
200 busy_tch_carr_hr,0
201 busy_tch_carr_hr_amr,0
202 busy_tch_dcs1800,0
203 busy_tch_egsm,0
204 busy_tch_hr,0
205 busy_tch_hr,4,0
206 busy_tch_hr,4,1
207 busy_tch_hr,4,2
208 busy_tch_hr,4,3
209 busy_tch_hr,4,4
210 busy_tch_hr,4,5
211 busy_tch_hr,4,6
212 busy_tch_hr,4,7
213 busy_tch_hr,4,8
214 busy_tch_hr,4,9
215 busy_tch_hr,5,0
216 busy_tch_hr,5,1
217 busy_tch_hr,5,2
218 busy_tch_hr,5,3
219 busy_tch_hr,5,4
220 busy_tch_hr,5,5
221 busy_tch_hr,5,6
222 busy_tch_hr,5,7
223 busy_tch_hr,5,8
224 busy_tch_hr,5,9
225 busy_tch_hr_amr,0
226 busy_tch_hr_amr,4,0
Continued
6-116 68P02900W22-S
Jul 2008

# Element Name
246 busy_tch_pgsm,0
247 bvci
248 c31_hyst
249 c32_qual
250 call_trace_options
251 called_pci
252 calling_pci
253 calls_queued,0
254 calls_queued,2
255 carrier_disable_time
256 carriers_ins_pwr_fail
257 cbc_fast_select
258 cbc_intface_vers
259 cbc_vbind_cntr
260 cbch_enabled
261 cbs_outage_cntr
262 ccch_conf
263 ccch_load_period
264 cell_bar_access_class
265 cell_bar_access_switch
266 cell_bar_qualify
267 cell_flush_reqs,0
Continued
68P02900W22-S 6-117
Jul 2008

# Element Name
268 cell_reselect_offset
269 cell_reselect_param_ind
270 ch_req_unsvcd_pcu,0
271 chan_dl_tx_pwr_lvl,0
272 chan_dl_tx_pwr_lvl,4,0
292 chan_req_cause_atmpt,0
293 chan_req_ms_blk,0
294 chan_req_ms_blk_2
295 chan_req_ms_fail,0
296 chan_req_ms_fail_2
297 chan_req_ms_fail_2,0
300 chan_ul_tx_pwr_lvl,0
301 chan_ul_tx_pwr_lvl,4,0
Continued
6-118 68P02900W22-S
Jul 2008

# Element Name
321 channel_reconfiguration_switch
322 channel_reqs_rec,0
323 channel_reqs_reject,0
324 channel_reqs_success,0
325 ciph_mode_rej_allowed
326 cipher_mode_fail,0
327 cipher_mode_fail,2
328 classmk_update_fail,0
329 classmk_update_fail,2
330 clk_src_fail_reset_period
331 clr_cmd_from_msc,0
332 clr_req_to_msc,0
333 coding_scheme_change,0
334 coincident_offset
335 confusion_msg_allowed
Continued
68P02900W22-S 6-119
Jul 2008

# Element Name
336 cong_rel_dl_scts,0
337 congest_at_source
338 congest_at_target
339 congest_exist_ho_atmpt,0
340 congest_stand_ho_atmpt,0
341 congestion_lost_msu,0
342 congestion_lost_msu_2
343 conn_refused,0
344 connection_code
345 conn_req_to_msc,0
346 cp_option_reset_ckt
347 cp_option_rr_status
348 cpu_usage,0
349 cpu_usage,4,0
350 cpu_usage,4,1
351 cpu_usage,4,2
352 cpu_usage,4,3
353 cpu_usage,4,4
354 cpu_usage,4,5
355 cpu_usage,4,6
356 cpu_usage,4,7
357 cpu_usage,4,8
358 cpu_usage,4,9
359 cpu_usage,5,0
360 cpu_usage,5,1
361 cpu_usage,5,2
362 cpu_usage,5,3
363 cpu_usage,5,4
364 cpu_usage,5,5
365 cpu_usage,5,6
366 cpu_usage,5,7
367 cpu_usage,5,8
368 cpu_usage,5,9
369 cr_calling
Continued
6-120 68P02900W22-S
Jul 2008

# Element Name
370 crm_timer_value,0
383 crmpc_timer_value,0
392 cs_page_reqs,0
393 {33397} cs_paging_msgs_from_msc,0
394 cs12_on_32k_chan,0
395 cs1234_on_64k_chan,0
396 d1_ba_alloc_proc
397 d1_missing_rpt
398 d1_ncell_proc
399 d1_sdcch_ho
400 d1_sdcch_timer_ho
401 decision_1_dl_rxlev_av_h
402 decision_1_dl_rxlev_av_ih
403 decision_1_dl_rxlev_av_p
Continued
68P02900W22-S 6-121
Jul 2008

# Element Name
404 decision_1_dl_rxqual_av_h
405 decision_1_dl_rxqual_av_p
406 decision_1_n1
407 decision_1_n2
408 decision_1_n3
409 decision_1_n4
410 decision_1_n5
411 decision_1_n6
412 decision_1_n7
413 decision_1_n8
414 decision_1_ncell_rxlev_av_h_calc
415 decision_1_p_bgt_rxlev_av_h
416 decision_1_p1
417 decision_1_p2
418 decision_1_p3
419 decision_1_p4
420 decision_1_p5
421 decision_1_p6
422 decision_1_p7
423 decision_1_p8
424 decision_1_tim_adv_av_alg
425 decision_1_ul_rxlev_av_h
426 decision_1_ul_rxlev_av_ih
427 decision_1_ul_rxlev_av_p
428 decision_1_ul_rxqual_av_h
429 decision_1_ul_rxqual_av_p
430 decision_alg_type
431 direct_inner_zone_threshold
432 disuse_cnt_hreqave
433 dl_audio_lev_offset
434 dl_bler_cs1,0
436 dl_bler_cs2,0
437 dl_bler_cs3,0
438 dl_bler_cs4,0
Continued
6-122 68P02900W22-S
Jul 2008

# Element Name
439 dl_bler_mcs1,0
440 dl_bler_mcs2,0
441 dl_bler_mcs3,0
442 dl_bler_mcs4,0
443 dl_bler_mcs5,0
444 dl_bler_mcs6,0
445 dl_bler_mcs7,0
446 dl_bler_mcs8,0
447 dl_bler_mcs9,0
448 dl_busy_pdtch,0
449 dl_busy_pdtch,4,0
469 dl_dtx_voice_data
470 dl_egprs_backhaul_demand,0
471 dl_egprs_backhaul_used,0
472 dl_llc_data_volume,0
Continued
68P02900W22-S 6-123
Jul 2008

# Element Name
473 dl_llc_frames_gb,0
474 dl_llc_frames_pcu,0
475 dl_pdtch_q_length,0
476 dl_pdtch_seizure,0
477 dl_radio_blks_1_ts,0
480 dl_radio_blks,4_ts,0
481 dl_rlc_ack_new_blks,0
482 dl_rlc_ddtr_blks,0
483 dl_rlc_nack_blks,0
484 dl_rlc_retx_blks,0
485 dl_rlc_stalled_blks,0
486 dl_rlc_unack_new_blks,0
487 dl_rxlev_ho_allowed
488 dl_rxqual_ho_allowed
489 dl_tbf_time_1_ts,0
492 dl_tbf_time,4_ts,0
493 downlink_sync_timer
494 dr_chan_mode_modify
495 dr_ho_during_assign
496 dr_msc_preference
497 dr_preference
498 dr_standard_congest
499 dtx_required
500 dual_band_offset
501 dyn_step_adj
502 dyn_step_adj_fmpr
503 dynet_assign_fail,0
504 dynet_call_rejects,0
505 dynet_retry_time
506 dynet_tchs_reserved
Continued
6-124 68P02900W22-S
Jul 2008

# Element Name
507 efr_enabled
508 egprs_64k_channel_width,0
509 egprs_64k_channels_switched,0
510 egprs_64k_not_avail,0
511 egprs_avail_pdtch,0
512 egprs_dl_asgn_pccch,0
513 egprs_init_dl_cs
514 egprs_init_ul_cs
515 egsm_handover_threshold
516 emergency_class_switch
517 en_incom_ho
518 enh_ter_cic_mgt_ena_val
519 enhanced_relief
520 er_intra_cell_ho_atmpt,0
521 er_intra_cell_ho_suc,0
522 erc_ta_priority
523 extended_paging_active
524 {26881} ext_ul_exits,0
525 {26881} ext_ul_usf_usage,0
526 {26881} ext_utbf_nodata
527 fdd_gprs_qoffset
528 fdd_multirat_reporting
529 fdd_rep_quant
530 fer,0
531 fer_amr_fr,0
532 fer_amr_hr,0
533 fer_gsm_fr_efr,0
534 fer_gsm_hr,0
535 fer_non_amr,0
536 flow_control_barred,0
537 frmr,0
538 frmr,2
539 full_pwr_rfloss
540 g_rach_unsvcd_bts,0
Continued
68P02900W22-S 6-125
Jul 2008

# Element Name
541 gbl_dl_data_thrput,0
542 gbl_dl_data_thrput_hist,0
543 gbl_dl_data_thrput_hist,4,0
563 gbl_flow_ctrl_sent,0
564 gbl_paging_reqs,0
565 gbl_thrput_period
566 gbl_ul_data_thrput,0
567 gbl_ul_data_thrput_hist,0
568 gbl_ul_data_thrput_hist,4,0
Continued
6-126 68P02900W22-S
Jul 2008

# Element Name
588 gbl_unavailable,0
589 gclk_qwarm_flag
590 global_reset_repetitions
591 gproc_slots
592 gprs_32k_channels_switched,0
593 gprs_32k_dl_not_avail,0
594 gprs_32k_ul_not_avail,0
595 gprs_access_per_agch,0
596 gprs_access_per_rach,0
597 gprs_avail_pdtch,0
598 gprs_bs_cv_max
599 gprs_cell_congestion,0
600 gprs_cell_reselect_attmpt,0
601 gprs_cell_reselect_fail,0
602 gprs_cell_reselect_hysteresis
603 gprs_channels_switched,0
604 gprs_dl_asgn_pccch,0
605 gprs_drx_timer_max
606 gprs_dynet_failures,0
607 gprs_dynet_res_reqs,0
608 gprs_dynet_res_reqs,4,0
Continued
68P02900W22-S 6-127
Jul 2008

# Element Name
628 gprs_dynet_swi_reqs,0
629 gprs_dynet_swi_reqs,4,0
Continued
6-128 68P02900W22-S
Jul 2008

# Element Name
649 gprs_intraho_allwd
650 gprs_min_prr_blks
651 gprs_ms_pan_dec
652 gprs_ms_pan_inc
653 gprs_ms_pan_max
654 gprs_ms_txpwr_max_cch
655 gprs_par_wait_ind
656 gprs_pb
657 gprs_pc_alpha
658 gprs_pc_meas_chan
659 gprs_pch_agch_q_length,0
660 gprs_penalty_time
661 gprs_ppch_pagch_q_length,0
662 gprs_prr_blk_usg,0
663 gprs_prr_blk_usg,4,0
Continued
68P02900W22-S 6-129
Jul 2008

# Element Name
683 gprs_rach_arrival,0
684 gprs_rach_arrival,4,0
704 gprs_reconfig_thresh_idle_tch
705 gprs_reselect_offset
706 gprs_rxlev_access_min
707 gprs_sig_bvci
708 gprs_smg30_t3192
709 gprs_t3168
710 gprs_t3192
Continued
6-130 68P02900W22-S
Jul 2008

# Element Name
711 gprs_temporary_offset
712 gprs_ts_config_alg
713 group_block_unblock_allowed
714 gsm_cell_id_format
715 gsm_half_rate_enabled
716 handover_recognized_period
717 handover_required_curr_ch
718 handover_required_reject_switch
719 hcs_thr
720 hdsl_losw_oos
721 hdsl_losw_restore
722 hdsl_snr_daily
723 hdsl_snr_daily_mon_period
724 hdsl_snr_hourly
725 hdsl_snr_hourly_mon_period
726 hdsl_snr_oos
727 hdsl_snr_restore
728 ho_exist_congest
729 ho_fail_no_resources,0
730 ho_margin_usage_flag
731 ho_only_max_pwr
732 ho_pwr_level_inner
733 ho_req_ack_to_msc,0
734 ho_req_msc_fail,0
735 ho_req_msc_fail,2
736 ho_req_msc_proto,0
737 ho_req_msc_proto,2
738 hop_count
739 hop_count_timer
740 hopping_support
741 hopping_systems_enabled,0
Continued
68P02900W22-S 6-131
Jul 2008

# Element Name
757 hopping_systems_hsn,0
773 hr_fr_hop_count
774 hr_intracell_ho_allowed
775 hr_res_ts
776 i_frames_rx,0
777 i_frames_tx,0
778 {31565} ia_iar_msgs_per_agch,0
Continued
6-132 68P02900W22-S
Jul 2008

# Element Name
779 idle_pdtch_intf_band0,0
784 idle_tch_intf_band0,0
789 illegal_circuit_id
790 imm_assgn_cause,0
791 immediate_assign_mode
792 imrm_dcs1800_weight
793 imrm_egsm_weight
794 imrm_force_recalc
795 imrm_pgsm_weight
796 imrm_umts_weight
797 in_inter_bss_ho,0
798 in_intra_bss_ho,0
799 in_intra_bss_nc_atmpt,0
800 in_intra_bss_nc_suc,0
801 init_dl_cs
802 init_ul_cs
803 initial_sync_timer
804 inner_hr_usage_thres
805 intave
806 inter_cell_handover_allowed
807 interband_activity,0
808 interband_ho_allowed
809 interfer_bands,0
Continued
68P02900W22-S 6-133
Jul 2008

# Element Name
814 interfer_ho_allowed
815 intf_on_idle,0
816 intf_on_idle,4,0
836 intra_bss_ho_cause_suc,0
837 intra_cell_handover_allowed
838 intra_cell_ho,0
839 inv_est_cause_on_rach,0
840 invalid_frames_rx,0
841 invalid_frames_rx,2
842 l_rxlev_dl_h
843 l_rxlev_dl_p
844 l_rxlev_ul_h
845 l_rxlev_ul_p
846 l_rxqual_dl_h
Continued
6-134 68P02900W22-S
Jul 2008

# Element Name
847 l_rxqual_dl_h_amr_fr
848 l_rxqual_dl_h_amr_hr
849 l_rxqual_dl_h_hr
850 l_rxqual_dl_h_data
851 l_rxqual_dl_h_hopping
852 l_rxqual_dl_h_hopping_amr_fr
853 l_rxqual_dl_h_hopping_amr_hr
854 l_rxqual_dl_h_hopping_hr
855 l_rxqual_dl_p
856 l_rxqual_dl_p_amr_fr
857 l_rxqual_dl_p_amr_hr
858 l_rxqual_dl_p_data
859 l_rxqual_dl_p_hopping
860 l_rxqual_dl_p_hopping_amr_fr
861 l_rxqual_dl_p_hopping_amr_hr
862 l_rxqual_dl_p_hopping_hr
863 l_rxqual_ul_h
864 l_rxqual_ul_h_amr_fr
865 l_rxqual_ul_h_amr_hr
866 l_rxqual_ul_h_hr
867 l_rxqual_ul_h_data
868 l_rxqual_ul_h_hopping
869 l_rxqual_ul_h_hopping_amr_fr
870 l_rxqual_ul_h_hopping_amr_hr
871 l_rxqual_ul_h_hopping_hr
872 l_rxqual_ul_p
873 l_rxqual_ul_p_amr_fr
874 l_rxqual_ul_p_amr_hr
875 l_rxqual_ul_p_data
876 l_rxqual_ul_p_hopping
877 l_rxqual_ul_p_hopping_amr_fr
878 l_rxqual_ul_p_hopping_amr_hr
879 l_rxqual_ul_p_hopping_hr
880 layer_number
Continued
68P02900W22-S 6-135
Jul 2008

# Element Name
881 link_about_to_fail
882 link_fail
883 local_maintenance
884 low_sig_thresh
885 lta_alarm_range
886 ltu_fw_auto_download
887 ma_cmd_to_ms,0
888 ma_cmd_to_ms_blkd,0
889 ma_cmd_to_ms_blkd,2
890 ma_complete_from_ms,0
891 ma_complete_to_msc,0
892 ma_fail_from_ms,0
893 ma_fail_from_ms,2
894 ma_req_from_msc,0
895 ma_req_from_msc_fail,0
896 ma_req_from_msc_fail,2
897 ma_req_sdcch_pg_rsp,0
898 max_gprs_ts_per_carrier
899 max_ms_dl_buffer
900 max_ms_dl_rate
901 max_q_length_full_rate_channel
902 max_q_length_sdcch
903 max_retran
904 max_rst_ckt_timer_exps
905 mb_tch_congest_thres
906 mms_cat_enable
907 mms_config_type
908 mms_config_type_pcu
909 ms_access_by_type,0
910 ms_distance_allowed
911 ms_p_con_ack
912 ms_power_control_allowed
913 ms_power_level_period
914 ms_power_offset
Continued
6-136 68P02900W22-S
Jul 2008

# Element Name
915 ms_tch_usage_by_type,0
916 ms_txpwr_max_inner
917 msgs_discard_on_gproc,0
918 msgs_discard_on_rsl,0
919 mspwr_alg
920 msu_discarded,0
921 msu_discarded,2
922 mt_lcs_on_sdcch,0
923 mtl_loadshare_granularity
924 mtp_changeback,0
925 mtp_changeover,0
926 mtp_congestion,0
927 mtp_link_ins,0
928 mtp_linkfail,0
929 mtp_local_busy,0
930 mtp_local_mgt,0
931 mtp_mgt_inhibit,0
932 mtp_mgt_uninhibit,0
933 mtp_msu_rx,0
934 mtp_msu_tx,0
935 mtp_neg_acks,0
936 mtp_neg_acks,2
937 mtp_re_tx,0
938 mtp_re_tx,2
939 mtp_remote_mgt,0
940 mtp_remote_proc,0
941 mtp_restoration,0
942 mtp_sif_sio_rx,0
943 mtp_sif_sio_tx,0
944 mtp_sl_ack,0
945 mtp_sl_ack,2
946 mtp_sl_alignment,0
947 mtp_sl_alignment,2
948 mtp_sl_congestion,0
Continued
68P02900W22-S 6-137
Jul 2008

# Element Name
949 mtp_sl_congestion,2
950 mtp_sl_error_rate,0
951 mtp_sl_error_rate,2
952 mtp_sl_fail,0
953 mtp_sl_fail,2
954 mtp_sl_fibr,0
955 mtp_sl_fibr,2
956 mtp_start_rpo,0
957 mtp_start_rpo,2
958 mtp_stop_rpo,0
959 mtp_su_error,0
960 mtp_su_error,2
961 mtp_unavailable,0
962 multiband_reporting
963 n_avg_i
964 n2_expiry,0
965 n2_expiry,2
966 ncc_of_plmn_allowed
967 neighbor_journal
968 neighbor_report_timer
969 new_calls_hr
970 no_pdtch_avail,0
971 no_pdtch_avail_time,0
972 ns_alive_retries
973 ns_alive_timer
974 ns_block_retries
975 ns_block_timer
976 ns_reset_period
977 ns_reset_timer
978 ns_test_timer
979 ns_unblock_retries
980 num_audit_retries
981 num_cell_resel_cell,0
982 num_cell_resel_cell_pccn,0
Continued
6-138 68P02900W22-S
Jul 2008

# Element Name
983 num_cell_resel_cell_succ,0
984 num_cell_resel_nei,0
985 num_cell_resel_nei_pccn,0
986 num_cell_resel_nei_succ,0
987 num_emerg_access,0
988 num_emerg_rejected,0
989 num_emerg_tch_kill,0
990 num_emerg_term_sdcch,0
991 num_gbl_dl_thrput_samples
992 num_gbl_ul_thrput_samples
993 num_ho_to_3g_attempts,0
994 num_ho_from_3g_attempts,0
995 num_ho_from_3g_success,0
996 num_ho_to_3g_res_alloc_succ,0
997 num_ho_to_3g_success,0
998 num_multirat_ms_orig_call,0
999 num_t3121_expiry,0
1000 number_of_preferred_cells
1001 ok_acc_proc,0
1002 ok_acc_proc_suc_rach,0
1003 option_alg_a5_1
1010 option_preempt
1011 out_ho_cause_atmpt,0
1012 out_inter_bss_ho,0
1013 out_inter_bss_ho,2
1014 out_intra_bss_ho,0
1015 out_intra_bss_nc_atmpt,0
1016 out_intra_bss_nc_suc,0
Continued
68P02900W22-S 6-139
Jul 2008

# Element Name
1017 outer_zone_usage_level
1018 override_intra_bss_pre_transfer
1019 pacch_page_reqs,0
1020 packet_sysinfo_req,0
1021 packet_sysinfo_resp,0
1022 page_req_from_msc,0
1023 page_req_from_msc_fail,0
1024 page_req_from_msc_fail,2
1025 paging_requests_cs,0
1026 paging_requests_ps,0
1027 path_balance,0
1028 path_balance,4,0
1048 pbgt_mode
1049 pccch_drx_timer_max
1050 pccch_enabled
Continued
6-140 68P02900W22-S
Jul 2008

# Element Name
1051 pch_agch_q_length,0
1052 pch_q_page_discard,0
1053 pch_q_page_discard,2,0
1054 pch_q_page_discard,2,1
1055 pcr_enable
1056 pcr_n1
1057 pcr_n2
1058 pdu_discard_fr,0
1059 pdu_discard_llc,0
1060 penalty_time
1061 percent_traf_cs
1062 pfc_admission,0
1063 pfc_admission_other,0
1064 {27703A} pfc_admission_traffic_class,0
1065 pfc_downgrade_failure,0
1066 pfc_downgrade_success,0
1067 {27703A} pfc_gbr_dl,0
1068 {27703A} pfc_gbr_ul,0
1069 pfc_preemptions,0
1070 {27703A} pfc_preemptions_traffic_class,0
1071 pfc_rej_dgrd_prmpt_cell,0
1072 pfc_rej_dgrd_prmpt_prp,0
1073 pfc_reject_causes,0
1074 pfc_rejection,0
1075 pfc_rejection_other,0
1076 {27703A} pfc_rejection_traffic_class,0
1077 {27703A} pfc_transfer_delay,0
1078 pfc_upgrade,0
1079 phase_lock_gclk
1080 phase_lock_retry
1081 phase2_resource_ind_allowed
1082 pool_gproc_preemption
1083 poor_initial_assignment
1084 pow_inc_step_size_dl
Continued
68P02900W22-S 6-141
Jul 2008

# Element Name
1085 pow_inc_step_size_ul
1086 pow_red_step_size_dl
1087 pow_red_step_size_ul
1088 ppch_q_page_discard,0
1089 prach_s
1090 prach_tx_int
1091 preempt_cap,0
1092 prioritize_microcell
1093 priority_class
1094 protect_last_ts
1095 prp_load,0
1096 prp_load,4,0
1097 prp_load,4,1
1098 prp_load,4,2
1099 prp_load,4,3
1100 prp_load,4,4
1101 prp_load,4,5
1102 prp_load,4,6
1103 prp_load,4,7
1104 prp_load,4,8
1105 prp_load,4,9
1106 prp_load,5,0
1107 prp_load,5,1
1108 prp_load,5,2
1109 prp_load,5,3
1110 prp_load,5,4
1111 prp_load,5,5
1112 prp_load,5,6
1113 prp_load,5,7
1114 prp_load,5,8
1115 prp_load,5,9
1116 ps_page_reqs,0
1117 psi1_repeat_period
1118 pwr_handover_allowed
Continued
6-142 68P02900W22-S
Jul 2008

# Element Name
1119 pwrc
1120 qos_mtbr_be_dl
1121 qos_mtbr_be_ul
1122 qos_mtbr_bg_dl
1123 qos_mtbr_bg_ul
1124 qos_mtbr_i1_dl
1125 qos_mtbr_i1_ul
1126 qos_mtbr_i2_dl
1127 qos_mtbr_i2_ul
1128 qos_mtbr_i3_dl
1129 qos_mtbr_i3_ul
1130 qsearch_c
1131 qsearch_p
1132 queue_management_information
1133 queue_preempt_atmpt,0
1134 ra_colour
1135 ra_reselect_hysteresis
1136 rac
1137 rach_load_period
1138 rach_load_threshold
1139 rach_load_type
1140 radio_link_timeout
1141 rapid_pwr_down
1142 rber,0
1143 reconfig_fr_to_hr
1144 red_loss_daily
1145 red_loss_hourly
1146 red_loss_oos
1147 red_loss_restore
1148 red_time_oos
1149 red_time_restore
1150 reestablish_allowed
1151 remote_loss_daily
1152 remote_loss_daily_pcu
Continued
68P02900W22-S 6-143
Jul 2008

# Element Name
1153 remote_loss_hourly
1154 remote_loss_hourly_pcu
1155 remote_loss_oos
1156 remote_loss_oos_pcu
1157 remote_loss_restore
1158 remote_loss_restore_pcu
1159 remote_time_oos
1160 remote_time_oos_pcu
1161 remote_time_restore
1162 remote_time_restore_pcu
1163 report_resource_tch_f_high_water_mark
1164 report_resource_tch_f_low_water_mark
1165 res_gprs_pdchs
1166 res_ts_less_one_carrier
1167 rf_losses_sd,0
1168 rf_losses_sd,2
1169 rf_losses_tch,0
1170 rf_losses_tch,2
1171 rf_losses_tch_hr,0
1172 rf_losses_tch_hr,2
1173 rf_losses_tch_hr_amr,0
1174 rf_losses_tch_hr_amr,0
1175 rf_res_ind_period
1176 roc,0
1177 roc,4,0
1178 roc,4,1
1179 roc,4,2
1180 roc,4,3
1181 roc,4,4
1182 roc,4,5
1183 roc,4,6
1184 roc,4,7
1185 roc,4,8
1186 roc,4,9
Continued
6-144 68P02900W22-S
Jul 2008

# Element Name
1187 roc,5,0
1188 roc,5,1
1189 roc,5,2
1190 roc,5,3
1191 roc,5,4
1192 roc,5,5
1193 roc,5,6
1194 roc,5,7
1195 roc,5,8
1196 roc,5,9
1197 routing_syntax,0
1198 routing_syntax,2
1199 routing_unknown,0
1200 routing_unknown,2
1201 rpd_offset
1202 rpd_period
1211 rpd_trigger
1212 rpt_bad_qual_no_mr
1213 rrs_timer_values,0
1217 rrsm_timer_value,0
Continued
68P02900W22-S 6-145
Jul 2008

# Element Name
1229 rrsmpc_timer_value,0
1230 rrsmpc_timer_value,1
1231 rsl_lcf_congestion,0
1232 rsl_lcf_congestion,2
1233 rsspc_timer_values,0
1234 rsspc_timer_values,1
1235 rxlev_dl_zone
1236 rxlev_ul_zone
1237 sabm_tx,0
1238 sccp_bssap_mgt
1239 sccp_msgs,0
1240 sccp_msgs_rx,0
1241 sccp_msgs_tx,0
1242 sdcch_congestion,0
1243 sdcch_tch_band_reassign_delay
1244 search_prio_3g
1245 second_assign_atmpt,0
1246 second_assign_suc,0
1247 secondary_freq_type
1248 serving_band_reporting
1249 sif_sio_rx_opc,0
1250 sif_sio_tx_dpc,0
1251 sif_sio_type,0
1252 sl_congestion,0
1253 sl_congestion,2
1254 sl_stop_congestion,0
1255 slip_loss_daily
1256 slip_loss_hourly
1257 slip_loss_oos
1258 slip_loss_restore
1259 smg_gb_vers
1260 sms_dl_allowed
1261 sms_init_on_sdcch,0
1262 sms_init_on_sdcch_ho_in,0
Continued
6-146 68P02900W22-S
Jul 2008

# Element Name
1263 sms_init_on_tch,0
1264 sms_no_bcast_msg,0
1265 sms_tch_chan
1266 sms_ul_allowed
1267 ss7_mode
1268 ssm_critical_overload_threshold
1269 ssm_normal_overload_threshold
1270 ssmpc_timer_value,0
1273 ssp_burst_delay
1274 ssp_burst_limit
1275 stat_interval
1276 static_sync_timer
1277 sw_ts_less_one_carrier
1278 switch_gprs_pdchs
1279 sync_loss_daily
1280 sync_loss_daily_pcu
1281 sync_loss_hourly
1282 sync_loss_hourly_pcu
1283 sync_loss_oos
1284 sync_loss_oos_pcu
1285 sync_loss_restore
1286 sync_loss_restore_pcu
1287 sync_time_oos
1288 sync_time_oos_pcu
1289 sync_time_restore
1290 sync_time_restore_pcu
1291 t_avg_t
1292 t_avg_w
1293 tbf_dl_asgn_pacch,0
1294 tbf_rel_pacch_lost,0
1295 tbf_sessions,0
1296 tch_busy_critical_threshold
Continued
68P02900W22-S 6-147
Jul 2008

# Element Name
1297 tch_busy_norm_threshold
1298 tch_cong_inner_zone,0
1299 tch_cong_inner_zone_hr_amr,0
1300 tch_cong_inner_zone_hr_amr,0
1301 tch_congest_prevent_thres
1302 tch_congestion,0
1303 tch_congestion_hr,0
1304 tch_congestion_hr_amr,0
1305 tch_delay,0
1306 tch_delay,4,0
1307 tch_delay,4,1
1308 tch_delay,4,2
1309 tch_delay,4,3
1310 tch_delay,4,4
1311 tch_delay,4,5
1312 tch_delay,4,6
1313 tch_delay,4,7
1314 tch_delay,4,8
1315 tch_delay,4,9
1316 tch_delay,5,0
1317 tch_delay,5,1
1318 tch_delay,5,2
1319 tch_delay,5,3
1320 tch_delay,5,4
1321 tch_delay,5,5
1322 tch_delay,5,6
1323 tch_delay,5,7
1324 tch_delay,5,8
1325 tch_delay,5,9
1326 tch_flow_control
1327 tch_full_need_low_water_mark
1328 tch_preempt_atmpt,0
1329 tch_preempt_fail_no_cand,0
1330 tch_preempt_fail_no_cand,2
Continued
6-148 68P02900W22-S
Jul 2008

# Element Name
1331 tch_preempt_fail_timeout,0
1332 tch_preempt_no_q_alloc
1333 tch_preempt_rqd,0
1334 tch_q_length,0
1335 tch_q_length,4,0
1355 tch_q_removed,0
1356 tch_usage,0
1357 tch_usage_ext_range,0
1358 tch_usage_inner_zone,0
1359 tch_usage_threshold
1360 temporary_offset
1361 threshold
1362 timer_exp_pap_conv,0
1363 timing_advance_period
1364 tlli_blk_coding
Continued
68P02900W22-S 6-149
Jul 2008

# Element Name
1365 total_calls,0
1367 ts_alloc_flag
1368 tsc_update_method
1369 tx_integer
1370 tx_power_cap
1371 u_ber,0
1372 u_ber,4,0
1373 u_ber,4,1
1374 u_ber,4,2
1375 u_ber,4,3
1376 u_ber,4,4
1377 u_ber,4,5
1378 u_ber,4,6
1379 u_ber,4,7
1380 u_ber,4,8
1381 u_ber,4,9
1382 u_ber,5,0
1383 u_ber,5,1
1384 u_ber,5,2
1385 u_ber,5,3
1386 u_ber,5,4
1387 u_ber,5,5
1388 u_ber,5,6
1389 u_ber,5,7
1390 u_ber,5,8
1391 u_ber,5,9
1392 u_rxlev_dl_ih
1393 u_rxlev_dl_p
1394 u_rxlev_ul_ih
1395 u_rxlev_ul_p
1396 u_rxqual_dl_p
1397 u_rxqual_dl_p_amr_hr
1398 u_rxqual_ul_p
1399 u_rxqual_ul_p_amr_hr
Continued
6-150 68P02900W22-S
Jul 2008

# Element Name
1400 ul_audio_lev_offset
1401 ul_bler_cs1,0
1402 ul_bler_cs2,0
1403 ul_bler_cs3,0
1404 ul_bler_cs4,0
1405 ul_bler_mcs1,0
1406 ul_bler_mcs2,0
1407 ul_bler_mcs3,0
1408 ul_bler_mcs4,0
1409 ul_bler_mcs5,0
1410 ul_bler_mcs6,0
1411 ul_bler_mcs7,0
1412 ul_bler_mcs8,0
1413 ul_bler_mcs9,0
1414 ul_busy_pdtch,0
1415 ul_busy_pdtch,4,0
Continued
68P02900W22-S 6-151
Jul 2008

# Element Name
1435 ul_egprs_backhaul_demand,0
1436 ul_egprs_backhaul_used,0
1437 ul_llc_data_volume,0
1438 ul_llc_frames,0
1439 ul_pdtch_q_length,0
1440 ul_pdtch_seizure,0
1441 ul_radio_blks_8psk_1_ts,0
1442 ul_radio_blks_8psk_2_ts,0
1443 {23292} ul_radio_blks_8psk_3_ts,0
1444 {23292} ul_radio_blks_8psk_4_ts,0
1445 ul_radio_blks_gmsk_1_ts,0
1446 ul_radio_blks_gmsk_2_ts,0
1447 {23292} ul_radio_blks_gmsk_3_ts,0
1448 {23292} ul_radio_blks_gmsk_4_ts,0
1449 ul_rlc_ack_new_blks,0
1450 {33863} ul_rlc_nack_blks,0
1451 ul_rlc_retx_blks,0
1452 {33863} ul_rlc_stalled_blks,0
1453 ul_rlc_unack_new_blks,0
1454 ul_rxlev_ho_allowed
1455 ul_rxqual_ho_allowed
1456 ul_tbf_time_8psk_1_ts,0
1457 ul_tbf_time_8psk_2_ts,0
1458 {23292} ul_tbf_time_8psk_3_ts,0
1459 {23292} ul_tbf_time_8psk_4_ts,0
1460 ul_tbf_time_gmsk_1_ts,0
1461 ul_tbf_time_gmsk_2_ts,0
1462 {23292} ul_tbf_time_gmsk_3_ts,0
1463 {23292} ul_tbf_time_gmsk_4_ts,0
1464 umts_band_preferred
1465 umts_cpich_ec_no_min
1466 umts_cpich_rscp_min
1467 unequipped_circuit_allowed
Continued
6-152 68P02900W22-S
Jul 2008

# Element Name
1468 uplink_path_loss,0
1469 uplink_path_loss,4,0
1490 uplink_sync_timer
1491 use_bcch_for_gprs
1492 use_derived_ho_power
1493 use_neighbor_pbgt_hreqave
1494 wait_for_reselection
1495 wait_indication_parameters
1496 worse_neighbor_ho
1497 zone_change_atmpt,0
1498 zone_change_suc,0
1499 zone_ho_hyst
68P02900W22-S 6-153
Jul 2008
RTF table Chapter 6: MCDF tables
RTF table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of RTF table
This table contains details of the RTFs contained within the BSS area (refer to Table 6-24).
Default filename: rtf.mcd
Table 6-24 RTF table

The MNC can have an optional third digit only for PCS1900 and GSM850 systems.
This field can be entered in decimal or hex.
Hex numbers are to be followed by h or preceded by 0x, for example, 1234h or 0x1234.
This field can be entered in decimal or hex. Hex numbers are to be followed by h or

0 to 140, 253
With Increased
Network Capacity
feature.
The Site number, within the BSS, of the Site where this RTF is located.
First ID 2 0 to 23 Mandatory
First device ID of the RTF.
Second ID 2 0 to 11 Mandatory
Second device ID of the RTF.
Continued
6-154 68P02900W22-S
Jul 2008
System Information: DataGen Description of RTF table
Table 6-24 RTF table (Continued)

Primary Path ID 1 0 to 9 Mandatory (If site
number is not 0 and
DRI is not redundant,
else unused. Not
required for RTFs
using Dynamic
Allocation).
The Primary Path ID used in the associated RTF function.
Redundant Path 1 0 to 9 Optional
ID
The Redundant Path ID used in the associated RTF function.
BCCH Carrier 1 Boolean Mandatory
Used for the carrier type prompt within the RTF equipage command.
0 NON_BCCH carrier
1 BCCH carrier
Frequency 4 Refer Frequency Mandatory if not

Type Table below. a BCCH carrier.
Optional if a BCCH
carrier, leave blank
to pick up value from
Cell table.
The Frequency Types are as follows:
Frequency Type BCCH NON-BCCH
PGSM 1 to 124 1 to 124
EGSM 1 to 124 (975 to 1023, 0*) 1 to 124 or 975
to 1023, 0
DCS1800 512 to 885 512 to 885
PCS1900 512 to 810 512 to 810
Used for the absolute radio frequency. channel prompt within the RTF equipage command.
If the RTF is a BCCH carrier, this frequency is checked against the BCCH ARFN in the Cell
Table. If the two frequencies are different, the BCCH frequency from the Cell Table will be
used.
The channel selected for a PCS1900 cell must be within the allowed frequency blocks.
(Refer to the BSS table, PCS1900 Frequency Blocks field).
* BCCH Frequency can be in extension band if egsm_bcch_sd is enabled in
the Cell table.
KSW pair 1 0 to 3 Optional
Used for the Managing KSW Pair prompt within the RTF equipage command.
Continued
68P02900W22-S 6-155
Jul 2008
Description of RTF table Chapter 6: MCDF tables

Carrier Capacity 4 TEXT Mandatory.
Not required for
RTFs using Dynamic
Allocation.
Valid Range: FULL or SUB.
Used for Capacity of the Carrier prompt within the RTF equipage command.
Cell Zone 1 0 to 1 Optional (Required if
non-BCCH carrier).
Used for the Enter Cell Zone prompt within the RTF equipage command.
TRX Power 2 -1 to 21 Optional (Mandatory
Reduction if Cell Zone = 1).
(trx_pwr_red)
Used for the Enter TRX transmit power reduction prompt within the RTF equipage command.
Extended Range 2 0 to 4 Optional
Timeslots (ext_range_cell
enabled).
Used for the Enter the number of extended range timeslots allowed prompt within the RTF
equipage command.
RSL Second ID 1 0 to 7 Optional (Applicable
only for 16 kbps
RSL).
Used for the Enter the optional second identifier for the associated RSL prompt within the
RTF equipage command.
Redundant RSL 1 0 to 7 Optional (Mandatory
Second ID if both RSL Second
ID and Redundant
PATH ID fields are
defined).
Used for the Enter the second identifier for the associated RSL prompt within the RTF
equipage command. This parameter is only applicable for redundant RTFs.
SDCCH Load 1 0 to 8 (see below) Optional (Only valid
if Cell Zone = 0).
If the Increased SDCCH feature is unrestricted, the range is as follows:
ccch_conf BCCH RTF Non-BCCH RTF
0 0 - 7 0 - 8
1 0 - 7 0 - 8
2 0 - 6 0 - 8
4 0 - 5 0 - 8
6 0 - 4 0 - 8
Used for the Enter SDCCH load prompt within the RTF equipage command.
Continued
6-156 68P02900W22-S
Jul 2008
System Information: DataGen Description of RTF table

SDCCH 3 0 to 250 Optional (Only valid
Placement if SDCCH load is non
Priority zero).
Used for the Enter SDCCH placement priority prompt within the RTF equipage command.
Channel 3 0 to 250 Mandatory
Allocation
Priority
Used for the Enter channel allocation priority prompt within the RTF equipage command.
FHI 1 to FHI 8 3 0 to 15, 255 Optional
Used for the Frequency Hopping Indicator prompt within the RTF equipage command.
TSC 1 to TSC 8 1 0 to 7 Optional if left
blank and RTF is a
BCCH carrier, value
calculated from bsic
in Cell table.
Used for the Carrier training sequence code prompt within the RTF equipage command.
pkt_radio_type 1 0 to 3 Optional. This
parameter is only
applicable for
EGPRS.
Used to specify the terrestrial resource capacity of an RTF.
rtf_ds0_count 1 Refer Table 6-25 for Optional. This
range and values. parameter is
prompted only when
VersaTrau feature
is purchased and
pkt_radio_type is 3.
The number of terrestrial timeslots configured for an RTF.
NOTE
While upgrading from 1760/1800 to 1900, the parameter rtf_ds0_count is set to
7 (BCCH) and 8 (NON-BCCH) RTFs, as DataGen cannot handle the change in the
number of timeslot allocations. Users are provided with a WARNING message
through Upgrader as follows:
GSR8 VersaTrau Feature can be used to reduce the number of backhaul

timeslots required to support EDGE carriers. During Upgrades to GSR8,
rtf_ds0_count will be set to 7 (BCCH) or 8 (NON_BCCH ) for a VersaTrau
RTF and the user can change this to any value between 3 to 7/8.
Continued
68P02900W22-S 6-157
Jul 2008
Description of RTF table Chapter 6: MCDF tables

amr_half_rate_ 1 0 to 1 Optional
enabled
Used to enable or disable AMR Half Rate at an RTF:
0 = disabled
1 = enabled
Allow 8k Trau 3 0 to 1, No or Yes Optional (Only
valid if the
amr_half_rate_enabled
parameter is
enabled).
Used to enable or disable 8k backhaul:
0 = disabled
1 = enabled
Not prompted for if the BTS is not AMR capable or the RTF is sub-equipped.
half_rate_enabled 1 0 to 1 Optional
Used to enable or disable GSM Half Rate at an RTF:
0 = disabled
1 = enabled
Table 6-25 Range and values for rtf_ds0_count
TRAU Edge VT BCCH Sub HR 8K Range Default

format purchased purchased equipped enabled allowed
16 N/A N/A N/A No No N/A 2 2
16 N/A N/A N/A Yes No N/A 1 1
16 N/A N/A N/A No Yes No 4 4
16 N/A N/A N/A Yes Yes No 2 2
16 N/A N/A N/A No Yes Yes 2 2
16 N/A N/A N/A Yes Yes Yes 1 1
32 N/A N/A N/A No N/A N/A 4 4
32 N/A N/A N/A Yes N/A N/A 2 2
64 Yes Yes N/A N/A No N/A 3 to 7 3
64 Yes Yes N/A N/A Yes Yes 3 to 8 3
64 Yes No No N/A No N/A 8 8
64 Yes No Yes N/A Yes Yes 7 7
6-158 68P02900W22-S
Jul 2008
System Information: DataGen DRI table
DRI table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of DRI table
This table contains details of the DRIs specified in the Hardware table for the BSS area (refer
to Table 6-26).
NOTE
The DRI must have its Cage and Slot number detailed in the Hardware table Table 6-7.
Default filename: dri.mcd
Table 6-26 DRI table

This field can be entered in decimal or hex. Hex numbers are to be followed by h or preceded
by 0x, for example, 1234h or 0x1234.
This field can be entered in decimal or hex. Hex numbers are to be followed by h or preceded
by 0x, for example, 1234h or 0x1234.
0 to 140, 253
With Increased
Network Capacity
feature.
The Site number, within the BSS, of the Site where this DRI is located.
Continued
68P02900W22-S 6-159
Jul 2008
Description of DRI table Chapter 6: MCDF tables
Table 6-26 DRI table (Continued)

First ID 2 0 to 23 Mandatory
First device ID of the DRI.
Second ID 2 0 to 24 Mandatory
Second device ID of the DRI.
Board Type 1 0 to 4 Optional
Type of DRI at non-M-Cell site:
0 Digital Radio Modified (DRIM)FOX/FMUX board at an M-Cell/Horizon macro site:
0 FOX
1 FMUX0
2 FMUX1
3 FMUX2
4 DIRECT
NOTE
• Must be DIRECT for an M-Cell micro site.

• The value of Board Type is not verified in the DRI table against the
cabinet_type.
TRU Identifier 1 0 to 6 Optional, only used for
non-M-Cell sites.
Topcell Radio Unit identifier.
TCU Port Identifier 2 0 to 5 (M-Cell) Optional, only used
for M-Cell sites.
M-Cell: Transceiver Control Unit Port identifier.
fm_cell_type 1 0 to 4 (depends on Mandatory
diversity_flag)
Used for the fm_cell_type prompt within the DRI equipage command as follows:
diversity_flag fm_cell_type Result
0 0 Non-diversity (RCUs only)
0 1 Use branch 1 of a DRCU in a non-diversity mode
0 2 Use branch 2 of a DRCU in a non-diversity mode
1 3 Shared diversity
1 4 Full diversity
Continued
6-160 68P02900W22-S
Jul 2008
System Information: DataGen Description of DRI table

Diversity 1 Boolean Mandatory
Used for the diversity flag prompt within the DRI equipage command.
0 No diversity
1 Diversity (requires
a DRCU)
Antenna number 1 1 to 6 Mandatory
Used for the antenna select number prompt within the RTF equipage command.
NOTE
Antenna number parameter is valid for the following cabinets:
• M-Cell6 (cab type 11)

• TCU6 (cab type 13)
• Horizon macro (cab type 18)
• Horizon macro_ext (cab type 19)
• Horizon II macro (cab type 24)
• Horizon II macro_ext (cab type 25)
• Horizon II mini (cab type 26)
• Horizon II mini_ext (cab type 27)
• {26481} Horizon II micro (cab type 28)
• {26481} Horizon II micro_ext (cab type 29)
Assigned RTF first 1 0 to 5 Optional
ID
First device ID of the RTF to assign to this DRI.
Assigned RTF 2 0 to 24 Optional
second ID
Second device ID of the RTF to assign to this DRI.
Opto Alarm State 2 0 to 1 Optional
Specifies the number alarm state for the Optocoupler:
Number Alarm status
0 Closed
1 Open
Continued
68P02900W22-S 6-161
Jul 2008
Description of DRI table Chapter 6: MCDF tables

Opto Alarm 2 0 to 1 Optional
Reporting
Indicates whether or not the alarm is reported when the Optocoupler enters the alarm state.
Opto Alarm Index 2 0 to 33 Optional
Specifies the alarm string displayed when an alarm is reported for the Optocoupler.
Combining Type 2 0 to 2 Optional
Used to describe the role of this DRI in system combining:
0 None or Hybrid
1 Non-Controlling
2 Controlling
Combiner Identifier 2 0 to 13 Optional
Used to reference the associated combiner for this DRI.
Cavity Number 2 0 to 5 Optional
Used to reference the associated combiner for this DRI.
{30828} Dri_density 1 1 to 3 Optional
1 = Single Density
2 = Double Density
3 = Double Density
with Capacity
The value of dri_density is 2 for Horizon macro, Horizon macro_ext, Horizon II macro,
Horizon II macro_ext, Horizon II mini, Horizon II mini_ext and Mcell6 cabinets. The value of
dri_density is 3 only if the following are true:
• The configured DRI is located in the Horizon II cabinets such as Horizon II macro,
Horizon II micro, Horizon II mini, Horizon II macro_ext, Horizon II micro_ext and
Horizon II mini_ext.
• The master cabinet for the SITE is either Horizon II macro, Horizon II micro or Horizon
II mini.
• The CTU2D Capacity feature is enabled, that is, the value of ctu2dcapOpt is 1.
{30828} 2 0 to 11 Mandatory when
Assoc_dri_id dri_density is 2 or 3.
6-162 68P02900W22-S
Jul 2008
System Information: DataGen Algorithm data table
Algorithm data table

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Algorithm data table
Table 6-27 specifies the algorithm data to be used across the BSS area. These entries do not
use the lac and ci fields.
It also allows the user to specify specific algorithm data for specific cells identified by their lac
and ci. These entries specify the lac and ci for the cell to which the specific algorithm data
applies and do not stop the cell picking up all the other standard algorithm entries for the
remaining algorithms or indexes into algorithms.
Default filename: alg.mcd
Table 6-27 Algorithm data table

Algorithm Name 30 Text Mandatory
This field identifies the Algorithm Data set to update the following:
• surround_cell
• rel_tim_adv
• rxlev_dl_ho
• rxlev_dl_pc
• rxlev_ul_ho
• rxlev_ul_pc
• rxqual_dl_ho
• rxqual_dl_pc
• rxqual_ul_ho
• rxqual_ul_pc
• interfer_alg
Algorithm ID 1 0 to 3 Mandatory if
Algorithm Name is
not interfer_alg,
otherwise unused.
This field gives the value for the algorithm ID/bin number field.
Algorithm Number 1 0 to 1 Mandatory
This field gives the value for the algorithm number field.
Continued
68P02900W22-S 6-163
Jul 2008
Description of Algorithm data table Chapter 6: MCDF tables
Table 6-27 Algorithm data table (Continued)

Algorithm Data 3 0 to 255 Mandatory
This field gives the value for the algorithm data field (for 1.6.1.3 and 1.6.2.0).
Index 2 0 to 32 Mandatory
This field gives the value for the algorithm index field (for 1.6.1.3 and 1.6.2.0).
0 index for Hreqave.

1 index for Hreqt.
2 index for qual_weight.
3 index for
qual_power_flag.
4 index for
qual_margin_flag.
5 index for
neigh_protect_flag.
6 index for
adj_qual_margin.
7 - 31 reserved for future
use.
hreqave 3 1 to 31 Optional
hreqt 3 1 to 31 Optional
w_qual 3 0 to 255 Optional
LAC 6 6 digit numeric Optional
The Location Area Code. This field can be entered in decimal or hex. Hex numbers will be
followed by h or preceded by 0x, for example, 1234h or 0x1234.
Location area code of cell to which this algorithm data is to be specifically applied.
CI 6 6 digit numeric Optional (mandatory
if the LAC field is
specified).
The Cell identifier. This field can be entered in decimal or hex form. Hex numbers will be
followed by h or preceded by 0x, for example, 1234h or 0x1234.
Cell Identity of cell to which this algorithm data is to be specifically applied.
To display only generic algorithm details for cells with no MCC, MNC, LAC, and CI details
specified, refer to Table 6-28.
6-164 68P02900W22-S
Jul 2008
System Information: DataGen Neighbor table
Neighbor table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Neighbor table
This table identifies the cell pairs network-wide, using the bss_id to identify the BSS area
containing the cell marked as the source. Refer to Table 6-28. The bsic and bcch frequency are
detailed in the Cell table. The fields classed as optional may contain values overriding those
specified in the cell table.
Default filename: ngbr.mcd

Table 6-28 Neighbor table

BSS ID 3 0 to 255 Mandatory
The bss_id of the BSS the source cell is in.
Source MCC 3 3 digit numeric Mandatory
The Mobile Country Code of the source.
Source MNC 3 3 digit numeric Mandatory
The Mobile Network Code of the source.
Source LAC 6 6 digit numeric Mandatory
The location Area Code of the source. This field can be entered in decimal or hex form. Hex
numbers will be followed by h or preceded by 0x, for example, 1234h or 0x1234.
Source CI 6 6 digit numeric Mandatory
The cell identifier of the source. This field can be entered in decimal or hex form. Hex
Neighbor MCC 3 3 digit numeric Not required for blind search
neighbors, mandatory for non
blind search neighbors.
The Mobile Country Code of the Neighbor.
Neighbor MNC 3 3 digit numeric Not required for blind search
neighbors, mandatory for non
blind search neighbors.
The Mobile Network Code of the neighbor.
The location area code of the neighbor. This field can be entered in decimal or hex form. Hex
Continued
68P02900W22-S 6-165
Jul 2008
Description of Neighbor table Chapter 6: MCDF tables
Table 6-28 Neighbor table (Continued)

Neighbor LAC 6 6 digit numeric Mandatory
Neighbor RNC Id 5 4 digit numeric Mandatory, if a UMTS neighbor.
Neighbor CI 6 6 digit numeric Mandatory

The location area code of the neighbor. This field can be entered in decimal or hex form. Hex
Sync 3 Boolean
no — Not synchronized
yes — Synchronized
Used to determine if the handovers between the cells are synchronized or not.
Coincident Cell 1 0 to 2 Optional. Only applies to
internal neighbors.
Used for element: coincident_mb parameter of the chg_cell_element command as follows:
0 Coincident Multiband is disabled at the cell.
1 Coincident Multiband utilizes better cell detection.
2 Coincident Multiband utilizes coincident cell redirection.
This will enable coincident Multiband at the source cell, not the neighboring cell.
Both neighbors must be within the same site if set to 2. If not within the same site, the value
must be set to 1, must be synchronized and must be neighbors of one another.
ho_margin_cell 3 -24 to 31 Optional for both external and
internal neighbors.
Used for element: ho_margin_cell

If this no value is entered here the ho_margin_def value for the source will be used.
rxlev_min_cell 2 0 to 63 Optional for both external and

internal neighbors.
Used for element: rxlev_min_cell

If no value is entered here the rxlev_min_def value will be used.
ms_txpwr_max_cell 2 0 to 43 Mandatory if the neighbor cell
is external to BSS ID, not used
if neighbor is internal.
Range for GSM 900 and GSM 900 Extended = 5-43. Odd values only.
Range for DCS 1800 and PCS1900 = 0-30. Even values only.
Used for element: ms_txpwr_max_cell

If this element is entered, it overrides the value extracted from the cell table.
Continued
6-166 68P02900W22-S
Jul 2008
System Information: DataGen Description of Neighbor table

BA List Type 10 Text (valid strings Optional
listed below).
Used for the add_neighbor parameter: ba_list_type
Valid text strings:
ba_bcch Place the neighbor in the ba_bcch list.
ba_sacch Place the neighbor in the ba_sacch list.
both Place the neighbor in both the ba_bcch and ba_sacch lists.
empty field Place the neighbor in both the ba_bcch and ba_sacch lists.
Valid for 1.6.1.3 and 1.6.2.0 only.
BA BCCH List Type 3 Yes or No Optional
The BA BCCH List Type should be set to Yes if the BA SACCH and BA GPRS List Types
are set to No, otherwise MCDF Insert fails.
Used for the add_neighbor prompt: Add neighbor to the BA BCCH List (yes/no)?
BA SACCH List Type 3 Yes or No Optional
The BA SACCH List Type must be set to Yes if the BA BCCH and BA GPRS List Types
are set to No, otherwise MCDF Insert fails.
Used for the add_neighbor prompt: Add neighbor to the BA SACCH List (yes/no)?
BA GPRS List Type 3 Yes or No Optional
The BA GPRS List Type must be set to Yes if the BA BCCH and
BA SACCH List Types are set to No, otherwise MCDF Insert fails.
Used for the add_neighbor prompt: Add neighbor to the BA GPRS List (yes/no)?
Power Budget 2 1 to 31 Optional if BSS Microcellular
hreqave option is purchased.
Used for the add_neighbor prompted parameter: Power budget surround cell hreqave.
Power Budget 2 1 to 7 Optional if BSS Microcellular
Algorithm Type option is purchased.
Used for the add_neighbor prompted parameter: Power budget algorithm type.
Interfering 3 Boolean Optional. Only applicable
Frequency where Concentric Cells
option is purchased,
inner_zone_alg is set to
interference for source cell
and the neighbor is being
added to the SACCH list.
Used for the add_neighbor prompt: Does this neighbor have a carrier with an
interfering frequency?
Inner Zone 2 0 to 63 Optional. Only applicable if
Handover Interfering Frequency is yes.
Threshold
Used for the add_neighbor prompt: Enter the threshold for inner zone handover.
Continued
68P02900W22-S 6-167
Jul 2008

Inner Zone 2 0 to 63 Optional. Only applicable if
Handover Margin Interfering Frequency is yes.
Used for the add_neighbor prompt: Enter the margin for inner zone handover.
Uplink rxlev 3 0-255 Optional if BSS Microcellular
(serving cell) option is purchased and power
budget algorithm type is 3.
Used for the add_neighbor prompted parameter: Uplink rxlev of serving cell.
Downlink rxlev 3 0-255 Optional if BSS Microcellular
(serving cell) option is purchased and power
Used for the add_neighbor prompted parameter: Downlink rxlev of serving cell.
Qualifying Time 3 0 to 255 Optional if BSS Microcellular
option is purchased and power
Used for the add_neighbor prompted parameter: Qualifying time.
Qualifying Delay 3 0 to 255 Optional if BSS Microcellular
Time option is purchased and power
Used for the add_neighbor prompted parameter: Qualifying delay time.
Neighbor Cell rxlev 2 0 to 63 Optional if BSS Microcellular
Threshold option is purchased and power
Used for the add_neighbor prompted parameter: Neighbor cell rxlev threshold.
Delay Time 3 0 to 255 Optional if BSS Microcellular
option is purchased and power
Used for the add_neighbor prompted parameter: Delay time.
Handover Static 3 0 to 127 Optional if BSS Microcellular
Offset option is purchased and power
Used for the add_neighbor prompted parameter: Handover static offset.
Handover Dynamic 3 0 to 127 Optional if BSS Microcellular
Offset option is purchased and power
Used for the add_neighbor prompted parameter: Handover dynamic offset.
Congestion 3 -63 to 63 Optional if BSS Directed Retry
Handover Margin option or Alternate Congestion
Relief option is purchased and
neighbor is placed on a SACCH
list.
Used for the add_neighbor prompted parameter: Neighbor congestion handover margin.
Continued
6-168 68P02900W22-S
Jul 2008

Directed Retry 3 yes or no Optional if BSS Directed
Allowed Retry option is purchased and
neighbor is placed on a SACCH
list AND neighbor is external.
Used for the add_neighbor prompt: Is directed retry allowed at this external
neighbor cell.
Adj Chan Intf Test 3 yes or no Optional if BSS Directed Retry

option is purchased.
Used for the add_neighbor prompt: Enable channel interference avoidance test.
Rxlev Diff Adj Chan 3 -63 to 63 Optional if Microcellular option
Intf Avoid is purchased and Channel
Interference Avoidance has
value 1.
Used for the add_neighbor prompt: Rxlev difference for channel interference
avoidance test.
Adj Channel Intf 3 -63 to 63 Optional if Microcellular option
HO Det Margin is purchased and Power Budget
Algorithm Type has a value of
7.
Used for the add_neighbor prompted parameter: Adjacent channel interference
handover detection margin.
Neighbor Range 8 Text EXTENDED Optional. Only applicable when
or NORMAL extended range cell option is
purchased and ext_range_cell
is enabled.
Used for the neighbor_range element of the add_neighbor command to allow the range to
be extended or normal range per neighbor.
Handover Margin 3 -63 to 63 Optional
rxqual
Used for the ho_margin_rxqual element of the modify_neighbor command.
rxlev
Used for the ho_margin_rxlev element of the modify_neighbor command.
Type5
Used for the ho_margin_type5 element of the modify_neighbor command.
Neighbor PBGT 3 0 to 255 Optional
The recommended value is 40. This parameter (adap_trigger_pbgt_nbr) specifies the
cumulative trigger level for the adaptive handover power budget algorithm. When the
threshold is exceeded, the system triggers a handover to a better cell.
Continued
68P02900W22-S 6-169
Jul 2008

fdd_arfcn 5 10562 to 10838 Mandatory, if a UMTS
Neighbor.
Scrambling Code 3 0 to 511 Mandatory, if a UMTS
Neighbor.
Diversity Enabled 1 0 to 1 Mandatory, if a UMTS
Neighbor.
Umts Measurement 2 0 to 20 Optional. This is a prompt for
Margin Default: 3 the add_neighbor command.
If a value is not specified
for this parameter, then the
default value is used. It
can be modified using the
modify_neighbor command
only when the 2G/3G handover
feature is unrestricted.
Measurement parameter used by handover algorithm.
Umts NCell Avg 2 1 to 12 Optional. This is a prompt
Period Default: 6 for add_neighbor command.
If a value is not specified
for this parameter, then
the default value is used.
It can be modified using
modify_neighbor command
only when 2G/3G handover
feature is unrestricted.
Neighbor averaging period measured in SACCH multiframes.
UMTS BCCH List 3 Yes or No Optional. This is an
Type Default: Yes add_neighbor command
prompt which is not prompted
when the Enhanced 2G/3G
feature is restricted.
Used for add_neighbor.
UMTS SACCH List 3 Yes or No Optional. This is an
Type Default: Yes add_neighbor command
prompt which is not prompted
when the Enhanced 2G/3G
feature is restricted.
Used for add_neighbor.
Continued
6-170 68P02900W22-S
Jul 2008

Blind Search FDD 5 10562 to 10838 Mandatory for creating blind
Arfcn Default: N/A search neighbor using the
add_neighbor command with
a placement type of umts_fdd.
Used for specifying fdd_arfcn value for blind search neighbor.
{31400} 5 10054 to 10121 Optional. Applicable when
tdd_arfcn Default: N/A TD-SCDMA and GSM
interworking feature is
purchased. Indicates the
TD-SCDMA frequency.
Read-Write attribute of UTRAN Neighbor Cell.
tdd_cell_param Default: N/A TD-SCDMA and GSM
interworking feature is
purchased. Indicates the
TD-SCDMA cell parameter.
tdd_tstd_mode Default: 0 TD-SCDMA and GSM
0 – Disabled interworking feature is
1 – Enabled purchased. Indicates the
TD-SCDMA Time Switched
Transmit Diversity mode.
tdd_sctd_mode Default: 0 TD-SCDMA and GSM
0 – Disabled interworking feature is
1 – Enabled purchased. Indicates the
TD-SCDMA cell diversity
capability (Space Code
Transmit Diversity).
68P02900W22-S 6-171
Jul 2008
Throttles table Chapter 6: MCDF tables
Throttles table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Throttles table
The Throttles table specifies throttles to be applied to device types for the whole BSS area and
links them to alarm numbers. Refer to Table 6-29.
Default filename: thro.mcd
Table 6-29 Throttles table

Device Name 7 Text Mandatory
The name of one of the following devices:
DRI
GCLK
KSW
MMS
LMTL
MTL
RSL
XBL
GSL
Alarm Index 3 0 to 254 Mandatory
Specifies the alarm number for the throttle.
Throttle Value 4 0 to 1440 Mandatory
Specifies the throttle value.
6-172 68P02900W22-S
Jul 2008
System Information: DataGen EAS table
EAS table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of EAS table
The EAS table is used to specify alarm strings for alarm numbers used with the BSS area.
Refer to Table 6-30.
Default filename: eas.mcd
Table 6-30 EAS table

Alarm Index 2 0 to 33 Mandatory
This field is used to identify the alarm number to give the string.
EAS Severity 1 0 to 4 Mandatory

This field is used as the severity number of this EAS alarm.
Alarm String 24 Text Mandatory
This field is used as the string equipped against this EAS alarm number.
68P02900W22-S 6-173
Jul 2008
Daughter table Chapter 6: MCDF tables
Daughter table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Daughter table
This table is used to specify the half height cards at a site in the same way as the hardware table
(Table 6-7) specifies the full height cards at a site, as described in Table 6-31.
Default filename: dgtr.mcd
Table 6-31 Daughter table

0 to 140, 253
With Increased
Network Capacity
feature.
The Site number of the device.
Cabinet ID 2 0 to 15 Mandatory
The CAB ID of the device.
Cage Number 2 0 to 15 Optional (Mandatory at
otherwise unused).
The CAGE ID of the device.

Slot Number 2 0 to 28 Optional (Mandatory at
otherwise unused).
The slot number of the device.
Device Name 7 Text Mandatory
The name of this device.
Device ID 3 0 to 255 (Valid Mandatory
range depends
on device)
The ID of this device. At present only one device can be put here.
NAME RANGE
Non-M-CELL EAS 0-7
M-CELL EAS 0-15 (must be the same as the Cabinet ID)
6-174 68P02900W22-S
Jul 2008
System Information: DataGen PIX table
PIX table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of PIX table
The PIX table specifies the hardware circuits which activate specific alarms in an EAS device
as in Table 6-32.
Default filename: pix.mcd
Table 6-32 PIX table

0 to 140, 253
With Increased
Network Capacity
feature.
The Site number for this EAS device. This is set in the Daughter table.
Device ID 2 0 to 15 Mandatory
Device ID of the EAS device. This is set in the Daughter table.
Opto Number 2 1 to 16 Mandatory
This field is used to select the Opto Number to configure.
The range is as follows:
M-cell site 1 to 16
Non-M-cell site 1 to 8
Off State 1 Boolean Mandatory
This field determines the default off state for the Opto (Optocoupler).
Initial Setting 1 Boolean Mandatory
This field is used to configure the initial settings of the relays. There are only four relays for
the number of Optos (8 Optos for a non-M-Cell EAS, 16 Optos for an M-Cell EAS).
Alarm Index 3 0 to 33 or MPF Mandatory
MPF represents the main power failure alarm. This field indicates which alarm string to use
from the EAS table.
Report Changes 1 Y or N ([Y]es or Mandatory
[N]o)
This field is used to decide whether to report the state changes (send alarm) for the specified
Opto Number.
68P02900W22-S 6-175
Jul 2008
KSW table Chapter 6: MCDF tables
KSW table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of KSW table
The KSW table specifies the data for the KSW configuration commands (chg_ksw_config)
as in Table 6-33. This table has entries only for sites that implement expanded KSW cards.
Also, this table contains the entries that differ from the default values (generated within the
BSS and BTS tables) only.
NOTE
This command is invalid at M-Cell sites and will not be generated for these sites.
Default filename: ksw.mcd

Table 6-33 KSW table

0 to 140, 253
With Increased
Network Capacity
feature.
The Site number within the BSS.
KSW pair 1 0 to 3 Mandatory
The KSW pair within a cage (corresponds to the Highway number that the KSW pair manages).
Highway 0 1 0 to 3 Mandatory
The KSWX card that handles TDM Highway 0.
This can be any of the following values:

0 Highway is managed by the current
KSW pair
1 EXP KSWX A0
2 EXP KSWX A1
3 EXP KSWX A2
Highway 1 1 0 to 3 Optional (Value must be
entered for Highway 0).
Continued
6-176 68P02900W22-S
Jul 2008
System Information: DataGen Description of KSW table
Table 6-33 KSW table (Continued)

68P02900W22-S 6-177
Jul 2008
NSVC table Chapter 6: MCDF tables
NSVC table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of NSVC table
The NSVC table is used to specify the parameters for any add_nsvc commands as in Table 6-34.
Default filename: nsvc.mcd
Table 6-34 NSVC table

Location 3 251 to 253 Mandatory
This field specifies the location of the PCU at which mapping between the Network
Service-Virtual Connection Identifier (NSVCI) and Data Link Connection Identifier (DLCI) to
a specific GBL is enabled.
NSVCI 5 0 to 65535 Mandatory
This field is used to identify the Network Service Virtual Connection ID on a GBL.
GBL Id 3 0 to 3 Mandatory
This field is used to specify the ID of the associated GBL.
DLCI 3 16 to 991 Mandatory
This field is used to specify the Data Link Connection Identifier.
FR Committed Info 4 0 to 1984 Mandatory
Rate
This field is used to specify the Frame Relay committed information rate.
FR Burst Size 4 0 to 1984 Mandatory
This field is used to specify the Frame Relay burst size.
FR Burst Excess 4 0 to 1984 Mandatory
This field is used to specify the Frame Relay burst excess.
6-178 68P02900W22-S
Jul 2008
System Information: DataGen Hop table
Hop table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Hop table
The Hop table is used to specify the parameters of the chhg_hop_params command as in
Table 6-35.
Default filename: hop.mcd
Table 6-35 Hop table

0 to 140, 253
With Increased Network
Capacity feature.
Used to identify the site at which the specific value is required.
LAC 6 6 digit number Mandatory
CI 6 6 digit number Mandatory
The Cell Identifier can be entered in decimal or hex form. Hex numbers are to be followed
by h or preceded by 0x, for example, 1234h or 0x1234.
Hopping FHI 1 0 to 3 Mandatory
Hopping system (FHI) for a cell.
Continued
68P02900W22-S 6-179
Jul 2008
Description of Hop table Chapter 6: MCDF tables
Table 6-35 Hop table (Continued)

Hopping Frequency 0 4 0 to 1023 Mandatory
Mobile allocation ARFCN for FHI.
Hopping Frequency 1 4 0 to 1023 Optional
Continued
6-180 68P02900W22-S
Jul 2008
System Information: DataGen Description of Hop table

Continued
68P02900W22-S 6-181
Jul 2008
Description of Hop table Chapter 6: MCDF tables

Continued
6-182 68P02900W22-S
Jul 2008
System Information: DataGen Description of Hop table

68P02900W22-S 6-183
Jul 2008
ACS table Chapter 6: MCDF tables
ACS table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of ACS table
The Active Codec Set (ACS) table is used to specify the parameters for any chg_acs_params
commands as in Table 6-36.
Default filename: acs.mcd
Table 6-36 ACS table

0 to 140, 253
With Increased
Network
Capacity feature.
This field is used to identify the site at which the specific value is required.
value
value
The Cell identifier can be entered in decimal or hex form. Hex numbers are to be followed by
h or preceded by 0x, for example, 1234h or 0x1234.
Acs Mode 3 0 to 2 Mandatory
This parameter specifies the rate:
0 Full Rate
1 Half Rate
2 Both Rates
Continued
6-184 68P02900W22-S
Jul 2008
System Information: DataGen Description of ACS table
Table 6-36 ACS table (Continued)

AMR FR ACS,1 3 0 to 6 Mandatory. Prompted for if
the AMR feature has been
purchased, the BTS type is AMR
capable, and the mode specified
on the command line is 0 or 2.
AMR codec mode that can be used for any given voice call in the uplink or downlink direction.
AMR FR Init Codec 3 0 to 6 Mandatory. Prompted for if the
Mode Active Codec Set contains more
than one codec mode.
The Codec Mode used at the beginning of a call. If one mode is entered for the FR ACS, then
the FR Initial Codec Mode defaults this mode (if valid).
AMR FR Uplink 3 0 to 63 Mandatory. Prompted for if the
Threshold,1 ACS contains more than one
codec mode.
Lower Full-Rate uplink decision threshold for switching from one mode to another.
codec mode.
codec mode.
Continued
68P02900W22-S 6-185
Jul 2008
Description of ACS table Chapter 6: MCDF tables

Hystersis,1 ACS contains more than one
codec mode.
The sum of the associated threshold and hysteresis used as the upper decision threshold for
switching the codec mode.
codec mode.
codec mode.
AMR FR Downlink 3 0 to 63 Mandatory. Prompted for if the
codec mode.
Lower Full-Rate downlink decision threshold for switching from one mode to another.
codec mode.
codec mode.
codec mode.
codec mode.
Continued
6-186 68P02900W22-S
Jul 2008

codec mode.
AMR FR Uplink Thresh 3 0 to 63 Mandatory. Prompted for if the
Hop,1 ACS contains more than one
codec mode.
Uplink switching threshold applied to frequency hopping channels.
Hop2 ACS contains more than one
codec mode.
codec mode.
AMR FR Uplink Hyst 3 0 to 15 Mandatory. Prompted for if the
codec mode.
Uplink hysteresis applied to frequency hopping channels.
codec mode.
codec mode.
Thresh Hop,1 ACS contains more than one
codec mode.
Downlink switching threshold applied to frequency hopping channels.
codec mode.
Continued
68P02900W22-S 6-187
Jul 2008

codec mode.
AMR FR Downlink Hyst 3 0 to 15 Mandatory. Prompted for if the
codec mode.
Downlink hysteresis applied to frequency hopping channels.
codec mode.
codec mode.
AMR HR ACS,1 3 2 to 6 Mandatory. Prompted for if
Continued
6-188 68P02900W22-S
Jul 2008

AMR HR Init Codec 3 2 to 6 Mandatory. Prompted for if the
Mode ACS contains more than one
codec mode.
This is the Codec Mode used at the beginning of a call. If one mode is entered for the HR ACS,
then the HR Initial Codec Mode defaults to this mode (if valid).
AMR HR Uplink 3 0 to 63 Mandatory. Prompted for if the
codec mode.
Lower half rate decision threshold for switching from one mode to another.
codec mode.
codec mode.
codec mode.
codec mode.
codec mode.
AMR HR Downlink 3 0 to 63 Mandatory. Prompted for if the
codec mode.
codec mode.
Continued
68P02900W22-S 6-189
Jul 2008

codec mode.
codec mode.
codec mode.
codec mode.
AMR HR Uplink Thresh 3 0 to 63 Mandatory. Prompted for if the
codec mode.
codec mode.
codec mode.
AMR HR Uplink Hyst 3 0 to 15 Mandatory. Prompted for if the
codec mode.
codec mode.
Continued
6-190 68P02900W22-S
Jul 2008

codec mode.
codec mode.
codec mode.
codec mode.
Hyst Hop,1 ACS contains more than one
codec mode.
codec mode.
codec mode.
68P02900W22-S 6-191
Jul 2008
Test Neighbor table Chapter 6: MCDF tables
Test Neighbor table

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of the Test Neighbor table
Table 6-37 contains test neighbor details. Test neighbors are used by operators to optimize their
cellular network. The test neighbor allows the cell to add frequencies to the bcch allocation
list without having that frequency considered for a handover.
Default filename: testngbr.mcd
Table 6-37 Test Neighbor table

Source MCC 3 3 digit numeric Mandatory
value
The Source Mobile Country Code.
Source MNC 3 3 digit numeric Mandatory
value
The Source Mobile Network Code.
The Source MNC can have an optional third digit only for PCS1900 and GSM850
systems.
Source LAC 6 6 digit numeric Mandatory
value
The Source Location Area Code.
This field can be entered in decimal or hex. Hex numbers are to be followed by
h or preceded by 0x, for example, 1234h or 0x1234.
Source CI 6 6 digit numeric Mandatory
value
The Source Cell Identifier can be entered in decimal or hex form. Hex numbers
are to be followed by h or preceded by 0x, for example, 1234h or 0x1234.
Neighbor Test Id 2 1 to 64 Mandatory
Unique ID used to distinguish one Test Neighbor from another Test Neighbor.
BA BCCH List 3 Yes or No Mandatory
Type Text
The BA BCCH List Type must be set to Yes if the BA SACCH and
BA GPRS List Types are set to No, otherwise MCDF Insert fails.
Used for the add_neighbor prompt:
Add neighbour to the BA BCCH List (yes/no)?
Continued
6-192 68P02900W22-S
Jul 2008
System Information: DataGen Description of the Test Neighbor table
Table 6-37 Test Neighbor table (Continued)

BA SACCH List 3 Yes or No Mandatory
Type Text
The BA SACCH List Type must be set to Yes if the BA BCCH and
BA GPRS List Types are set to No, otherwise MCDF Insert fails.
BA GPRS List 3 Yes or No Mandatory. Prompted
Type Text if NCCR purchased.
The BA GPRS List Type must be set to Yes if the BA BCCH and
BA SACCH List Types are set to No, otherwise MCDF Insert fails.
Neighbor Cell 2 1 to 8 Mandatory
Frequency Type
Test Neighbor Cell Frequency type.
Neighbor BCCH 4 0 to 1023 Mandatory
Frequency
Number
Test Neighbor Mobile Allocation ARFCN for FHI.
68P02900W22-S 6-193
Jul 2008
Nail Connection Table Chapter 6: MCDF tables
Nail Connection Table

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of the Nail Connection table
The Nail Connection table is used to specify the parameters of the chg_ts_usage command as
in Table 6-38 to nail the GBL through the BSC.
There are no default values for any of the parameters. Datagen conducts only the range check.
Dependency checks are not done on these parameters.
Default filename: nailconn.mcd
Table 6-38 Nail Connection table

Operation 9 Character Mandatory
Displayed in the MCDF table as Action. The valid values are NAIL and
NAIL_PATH.
Site 3 0, 1 to 100 Mandatory
(only for NAIL
operation)
Displayed in the MCDF table as Site Identifier.
mms1_id1 3 0 to 123 Mandatory
Displayed in the MCDF table as MMS 1 First Identifier.
Displayed in the MCDF table as MMS 1 Second Identifier.
mms1_ts/site_1_ts 2 1 to 31 Mandatory
Displayed in the MCDF table as Starting Timeslot for MMS 1.
Displayed in the MCDF table as MMS 2 First Identifier.
Displayed in the MCDF table as MMS 2 Second Identifier.
mms2_ts/site_2_ts 2 1 to 31 Mandatory
Displayed in the MCDF table as Starting Timeslot for MMS 2.
path_id1 3 0 to 100 Mandatory
(only for
NAIL_PATH
operation)
Displayed in the MCDF table as Path Identifier 1.
Continued
6-194 68P02900W22-S
Jul 2008
System Information: DataGen Description of the Nail Connection table
Table 6-38 Nail Connection table (Continued)

path_id2 1 0 to 9 Mandatory
(only for
NAIL_PATH
operation)
Displayed in the MCDF table as Path Identifier 2.
site_1 3 0 to 100 Mandatory
(only for
NAIL_PATH
operation)
Displayed in the MCDF table as Start Site.
site_2 3 0 to 100 Mandatory
(only for
NAIL_PATH
operation)
Displayed in the MCDF table as End Site.
num_ts 2 1 to 31 Mandatory
Displayed in the MCDF table as Number of Timeslots Requested.
68P02900W22-S 6-195
Jul 2008
Description of the Nail Connection table Chapter 6: MCDF tables
6-196 68P02900W22-S
Jul 2008
Index
Index
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Administration . . . . . . . . . . . . . . 3-12 Audit (contd.)

changing permissions . . . . . . . . . . 3-13 audit logs . . . . . . . . . . . . . . . . 4-67
country admin. . . . . . . . . . . . . . 3-27 from Navigation Tree . . . . . . . . . . 4-35
customising parameters. . . . . . . . . 3-16 inconsistency report . . . . . . . . . . 4-69
database administration tasks . . . . . 3-20 scheduling . . . . . . . . . . . . . . . 4-60
importing CM database objects . . . . . 3-26 Audit inconsistency report . . . . . . . . 4-69
installing the Options Object . . . . . . 3-18 viewing . . . . . . . . . . . . . . . . . 4-69
optimising the database. . . . . . . . . 3-14 Audit log management . . . . . . . . . . 4-72
viewing the log file . . . . . . . . . . . 3-15 Audit logs
Administration - CADM . . . . . . . . . . 5-32 deleting . . . . . . . . . . . . . . . . . 4-71
Administration icon viewing . . . . . . . . . . . . . . . . . 4-67
use of . . . . . . . . . . . . . . . . . . 4-15 Auto-compile MMI script command . . . . . 5-8
Audit . . . . . . . . . . . . . . . . . . . 4-34 Auto-Revgen command . . . . . . . . . . 5-25
aborting while in progress . . . . . . . 4-68 Auto-upgrader command . . . . . . . . . 5-30
Batch processing BSS area (contd.)

compile . . . . . . . . . . . . . . . . . 3-130 creating . . . . . . . . . . . . . . . . . 3-35
BSS area . . . . . . . . . . . . . . . . . 3-35 deleting . . . . . . . . . . . . . . . . . 3-43
configuring . . . . . . . . . . . . . . . 3-45 opening . . . . . . . . . . . . . . . . . 3-39
copying . . . . . . . . . . . . . . . . . 3-41
Cell Command line tools (contd.)

find . . . . . . . . . . . . . . . . . . . 4-23 lock/unlock BSS area (lock_adm) . . . . 5-20
CellXchange MCDF filter (filter) . . . . . . . . . . . 5-14
introduction . . . . . . . . . . . . . . . 4-38 MMI combiner (combine) . . . . . . . . . 5-6
Radio Frequency planning . . . . . . . 4-38 MMI command generator (gcmd) . . . . 5-17
CM database objects . . . . . . . . . . . 3-26 optimise DataGen database (dbac-
converting to a database script file . . . 3-66 cess) . . . . . . . . . . . . . . . . . . 5-19
cmutil.olm command . . . . . . . . . . . . 4-5 revgen . . . . . . . . . . . . . . . . . 5-22
Command line tools . . . . . . . . . . . . . 5-2 toggle permissions (tp) . . . . . . . . . 5-27
auto compile MMI Script (auto_com- uncompress binary object files (cpdb
pile) . . . . . . . . . . . . . . . . . . . . 5-8 -u). . . . . . . . . . . . . . . . . . . . 5-10
auto_revgen . . . . . . . . . . . . . . . 5-25 user options . . . . . . . . . . . . . . . . 5-3
auto_upgrade . . . . . . . . . . . . . . 5-30 version upgrader (upg) . . . . . . . . . 5-28
compile MMI script (compile) . . . . . . . 5-7 Compile MMI script (compile) command . . 5-7
compress binary object files (cpdb -c) . . 5-10 Compile multiple binary object files . . . . 3-130
copy area (ca) . . . . . . . . . . . . . . . 5-4 Compress OLM network . . . . . . . . . 4-78
delete database object (del) . . . . . . . 5-12 Compress/uncompress binary object files
general information . . . . . . . . . . . . 5-3 command . . . . . . . . . . . . . . . . . 5-10
68P02900W22-S IX-197
Jul 2008
Index
Configuration management icon . . . . . 4-15 Copy BSS binary files into OLM . . . . . . 4-76
Configuring BSS area(s) Copying a BSS area from the GUI . . . . . 3-41
basic BSS with TS switch - expansion . . 3-47 Country administration (CADM) . . . . . 5-32
daisy chain configuration with TS administration files . . . . . . . . . . . 5-36
switch . . . . . . . . . . . . . . . . . . 3-52 menus. . . . . . . . . . . . . . . . . . 5-34
functions and MCDF table relation- using the xcadm GUI . . . . . . . . . . 5-33
ships . . . . . . . . . . . . . . . . . . 3-45 Creating a BSS area . . . . . . . . . . . 3-35
Configuring BSS areas . . . . . . . . . . 3-45 Creating a BSS from Navigation Tree . . . 4-32
Converting a script file . . . . . . . . . . 3-112 Creating a network
binary object compiler . . . . . . . . . 3-112 Saving a network . . . . . . . . . . . . . 4-6
Sysgen mode . . . . . . . . . . . . . . 3-112 Creating a RXCDR from Navigation
Copy area (ca) command . . . . . . . . . . 5-4 Tree . . . . . . . . . . . . . . . . . . . . 4-32
Daisy chain configuration with TS DataGen database structure (contd.)

switch . . . . . . . . . . . . . . . . . . . 3-52 DataGen - OMC integration . . . . . . . . 1-7
Database DataGen directory structure . . . . . . . 1-11
dropping/recreating the db_dg Informix sub-structure . . . . . . . . . . . . . . 1-13
database . . . . . . . . . . . . . . . . 3-22 DataGen files . . . . . . . . . . . . . . . 3-77
reloading the Informix database . . . . 3-21 tools for editing . . . . . . . . . . . . . 3-77
save . . . . . . . . . . . . . . . . . . . 4-42 DataGen functions . . . . . . . . . . . . . 1-2
system performance . . . . . . . . . . 3-20 Defragmenting the database . . . . . . . 3-14
usage scripts . . . . . . . . . . . . . . 3-20 Delete database object (del) command . . 5-12
verify . . . . . . . . . . . . . . . . . . 4-42 Deleting a BSS area . . . . . . . . . . . . 3-43
warning messages . . . . . . . . . . . 3-21 Deleting a network . . . . . . . . . . . . 4-53
Database script files . . . . . . . . . . . 3-71 Deleting a network/country . . . . . . . . 3-33
alternative text editor . . . . . . . . . . 3-74 Device management
producing . . . . . . . . . . . . . . . . 3-71 from navigation tree . . . . . . . . . . 4-37
viewing . . . . . . . . . . . . . . . . . 3-72 Difference reporter . . . . . . . . . . . . 3-118
xedit window . . . . . . . . . . . . . . 3-73 menu option. . . . . . . . . . . . . . . 3-10
DataGen and OLM platform . . . . . . . . . 1-5 selecting BSS area details. . . . . . . . 3-119
DataGen database structure . . . . . . . . 1-7 using the information window. . . . . . 3-121
BSS database . . . . . . . . . . . . . . . 1-7 using the report window . . . . . . . . 3-122
CM database object . . . . . . . . . . . 1-7
database script file . . . . . . . . . . . 1-7
Environment variables Environment variables (contd.)

automate RevGen . . . . . . . . . . . . . 3-5 text editor. . . . . . . . . . . . . . . . . 3-7
defining . . . . . . . . . . . . . . . . . . 3-4 time slot order . . . . . . . . . . . . . . 3-5
display generic details in alg.mcd table . . 3-8 version order . . . . . . . . . . . . . . . 3-5
export path . . . . . . . . . . . . . . . . 3-6 Exiting the OLM GUI . . . . . . . . . . . 4-12
import path . . . . . . . . . . . . . . . . 3-6 Expanded BSS with TS . . . . . . . . . . 3-47
output to script . . . . . . . . . . . . . . 3-8 Expanding the network . . . . . . . . . . 4-55
override lock . . . . . . . . . . . . . . . 3-7 Expert desktop option. . . . . . . . . . . 4-17
setenv command . . . . . . . . . . . . . 3-4 Exporting object files . . . . . . . . . . . 3-115
setting from the GUI . . . . . . . . . . 3-12
IX-198 68P02900W22-S
Jul 2008
Index
Feature Feature (contd.)

22169 . . . . . . . . . . . . . . . . . . 6-54 30828 . . . . . . . . . . . . . . . 6-29, 6-162
22266 . . . . . . . . . . . . . . . . . . 6-101 30830 . . . . . . . . . . . . . . . 6-27, 6-111
23292 . . . . . . . . . . . . . . 6-106, 6-152 31400 . . . . . . . . . . . . 6-43, 6-73, 6-171
23306 . . . . . . . . . . . . . 6-28, 6-92, 6-99 31565 . . . . . . . . 6-26, 6-92, 6-110, 6-132
25002 . . . . . . . . . . . . . . . 6-43, 6-112 32340 . . . . . . . . . . . . . . . . . . 6-82
25423 . . . . . . . . . . . . . . . . . . 6-10 33397 . . . . . . . . . . . . . . . 6-85, 6-121
26481 . . . . . . . . . . . . . . . 6-12, 6-161 33863 . . . . . . . . . . . . . . 6-106, 6-152
26740 . . . . . . . . . . . . . . . . 6-15, 6-23 34144 . . . . . . . . . . . . . . . . . . 6-26
to 6-24, 6-31, 6-39, 6-87, 6-100 Find icon
26881 . . . . . . . . . . . . 6-31, 6-87, 6-125 use of . . . . . . . . . . . . . . . . . . 4-16
27703A . . . . . . . . . . . . . . 6-27, 6-37, Find, using . . . . . . . . . . . . . . . . 4-18
6-39, 6-42 to 6-43, 6-99, 6-141 examples
27717 . . . . . . . . . . . . . . . . 6-46, 6-97 BSS parent of a Cell. . . . . . . . . . 4-22
27955A . . . . . . . . . . . . . . . 6-15, 6-19 cell with LAC . . . . . . . . . . . . . 4-23
28000 . . . . . . . . . . . . . . . . . . 6-21 site with BSS name and Site Id . . . . 4-22
28337 . . . . . . . 6-23, 6-37, 6-49, 6-56, 6-96 finding attributes . . . . . . . . . . . . 4-24
28351 . . . . . 6-16 to 6-17, 6-23 to 6-24, 6-87 finding devices . . . . . . . . . . . . . 4-19
28398 . . . . . . . . . . . . . 6-9, 6-11, 6-14, overview . . . . . . . . . . . . . . . . 4-18
6-59 to 6-60, 6-65, 6-109, 6-154, 6-159, 6-174 printing results . . . . . . . . . . . . . 4-26
to 6-176, 6-179, 6-184 saving results . . . . . . . . . . . . . . 4-26
28938 . . . . . . . . . . . . . . . . . . 6-13 Functions - command line . . . . . . . . . . 5-2
Generic Table Editor (GTE) . . . . . . . . 3-90 Generic Table Editor (GTE) (contd.)
edit menu . . . . . . . . . . . . . . . . 3-96 hot keys for MCDF . . . . . . . . . . . 3-104
file menu . . . . . . . . . . . . . . . . 3-90 Group management . . . . . . . . . . . . 2-13
fill cells . . . . . . . . . . . . . . . . . 3-97 group parameters . . . . . . . . . . . . 2-13
format menu . . . . . . . . . . . . . . 3-99
Hardware configurations supported. . . . 1-15 Help icon

Hardware reports, generating . . . . . . 3-110 OLM GUI . . . . . . . . . . . . . . . . 4-16
Help button, DataGen . . . . . . . . . . . 3-11
Importing/exporting objects. . . . . . . . 3-58 Invalid NE. . . . . . . . . . . . . . . . . 4-29

Installing the Options Object . . . . . . . 3-18
Loading network information . . . . . . . . 1-9 Lock/Unlock BSS area (lock_adm) com-

gathering network information . . . . . 1-10 mand . . . . . . . . . . . . . . . . . . . 5-20
Locate NE, PCU, site or cell . . . . . . . . 4-19 Log files
68P02900W22-S IX-199
Jul 2008
Index
Log files (contd.)

viewing audit logs. . . . . . . . . . . . 4-67
MCDF files MCDF tables (contd.)

creating . . . . . . . . . . . . . . . . . 3-84 KSW table. . . . . . . . . . . . . . . . 6-176
editing tables . . . . . . . . . . . . . . 3-86 Lapd table . . . . . . . . . . . . . . . 6-63
inserting . . . . . . . . . . . . . . . . 3-86 Links table . . . . . . . . . . . . . . . 6-59
invalid data entry . . . . . . . . . . . . 3-88 Modify Value table . . . . . . . . . . . 6-51
validating . . . . . . . . . . . . . . . . 3-85 Neighbour table. . . . . . . . . . . . . 6-165
MCDF filter (filter) command . . . . . . . 5-14 NSVC table . . . . . . . . . . . . . . . 6-178
MCDF table hierarchy . . . . . . . . . . . 6-2 Paths table . . . . . . . . . . . . . . . 6-61
MCDF tables PIX table . . . . . . . . . . . . . . . . 6-175
ACS table . . . . . . . . . . . . . . . . 6-184 ranges, default values, dependencies . . . 6-2
Algorithm data table . . . . . . . . . . 6-163 RTF table . . . . . . . . . . . . . . . . 6-154
BSS table . . . . . . . . . . . . . . . . . 6-5 Site table . . . . . . . . . . . . . . . . . 6-9
Cabinet table . . . . . . . . . . . . . . 6-11 Specifics table . . . . . . . . . . . . . 6-108
Cell table . . . . . . . . . . . . . . . . 6-65 Statistics table . . . . . . . . . . . . . 6-75
Channel table . . . . . . . . . . . . . . 6-57 Test Neighbour table . . . . . . 6-192, 6-194
Circuit table. . . . . . . . . . . . . . . 6-54 Throttles table . . . . . . . . . . . . . 6-172
Daughter table . . . . . . . . . . . . . 6-174 Timer table . . . . . . . . . . . . . . . 6-45
DRI table . . . . . . . . . . . . . . . . 6-159 viewing . . . . . . . . . . . . . . . . . . 6-2
EAS table . . . . . . . . . . . . . . . . 6-173 MMI combiner (combine) command. . . . . 5-6
Generics table . . . . . . . . . . . . . 6-25 MMI command generator (gcmd) com-
Hardware table . . . . . . . . . . . . . 6-14 mand . . . . . . . . . . . . . . . . . . . 5-17
Hop table . . . . . . . . . . . . . . . . 6-179
Navigation tree Navigation Tree (contd.)

autoclose . . . . . . . . . . . . . . . . 4-57 opening . . . . . . . . . . . . . . . . . 4-28
Navigation Tree overwrite a BSS/RXCDR binary object
audit . . . . . . . . . . . . . . . . . . 4-35 file . . . . . . . . . . . . . . . . . . . 4-39
closing . . . . . . . . . . . . . . . . . 4-29 panner . . . . . . . . . . . . . . . . . 4-31
create BSS or RXCDR . . . . . . . . . . 4-32 porthole . . . . . . . . . . . . . . . . . 4-31
deleting a BSS/RXCDR . . . . . . . . . 4-58 Network
device management . . . . . . . . . . . 4-37 create . . . . . . . . . . . . . . . . . . . 4-6
introduction . . . . . . . . . . . . . . . 4-27 delete . . . . . . . . . . . . . . . . . . 4-53
moving levels . . . . . . . . . . . . . . 4-30 Network Expansion . . . . . . . . . . . . 4-55
Offline MIB (OLM) OLM GUI, using (contd.)

integration with DataGen . . . . . . . . . 1-4 additional features (contd.)
overview . . . . . . . . . . . . . . . . . 1-3 autoclose . . . . . . . . . . . . . . . 4-57
Offline MIB directory structure . . . . . . 1-13 compress/uncompress an OLM
main structure . . . . . . . . . . . . . 1-14 network . . . . . . . . . . . . . . . . 4-78
OLM file structure . . . . . . . . . . . 1-13 deleting a NE database . . . . . . . . 4-58
OLM GUI, using . . . . . . . . . . . . . . . 4-2 deleting a scheduled audit . . . . . . 4-66
additional features . . . . . . . . . . . 4-56 managing audit logs . . . . . . . . . 4-72
auditing logs . . . . . . . . . . . . . 4-67 modifying a scheduled audit . . . . . 4-65
IX-200 68P02900W22-S
Jul 2008
Index
OLM GUI, using (contd.) OLM GUI, using (contd.)

additional features (contd.) troubleshooting (contd.)
realigning a network . . . . . . . . . 4-76 specific operation fails . . . . . . . . 4-83
scheduling an audit . . . . . . . . . . 4-60 verify and save network . . . . . . . . . 4-42
cmutil.olm command . . . . . . . . . . . 4-5 OLM online Help . . . . . . . . . . . . . 4-16
deleting a network configuration . . . . 4-53 OMC
environment variables . . . . . . . . . . 4-4 exporting object files to the OMC . . . . 3-115
exiting the OLM GUI . . . . . . . . . . 4-12 importing binary object files from the
expert desktop . . . . . . . . . . . . . 4-17 OMC . . . . . . . . . . . . . . . . . . 3-58
front panel icons . . . . . . . . . . . . 4-15 Opening a BSS area . . . . . . . . . . . . 3-39
levels of users . . . . . . . . . . . . . . . 4-4 Operating DataGen . . . . . . . . . . . . . 3-2
shutting down the OLM . . . . . . . . . 4-12 overview . . . . . . . . . . . . . . . . . 3-2
standard desktop . . . . . . . . . . . . 4-17 procedures . . . . . . . . . . . . . . . . 3-2
starting the OLM GUI . . . . . . . . . . . 4-9 shutdown . . . . . . . . . . . . . . . . 3-11
task list . . . . . . . . . . . . . . . . . . 4-3 startup . . . . . . . . . . . . . . . . . 3-10
troubleshooting . . . . . . . . . . . . . . 4-4 Optimise DataGen database (dbaccess)
database errors . . . . . . . . . . . . 4-81 command . . . . . . . . . . . . . . . . . 5-19
fails to start . . . . . . . . . . . . . . 4-80 Optimising the database . . . . . . . . . 3-14
force shutdown . . . . . . . . . . . . 4-83 Overview - DataGen . . . . . . . . . . . . . 1-2
general operating errors . . . . . . . 4-82 Overwriting a BSS/RXCDR binary object
import errors . . . . . . . . . . . . . 4-83 file . . . . . . . . . . . . . . . . . . . . 4-39
reinitialise database . . . . . . . . . 4-85
Panner . . . . . . . . . . . . . . . . . . 4-31 Porthole . . . . . . . . . . . . . . . . . . 4-31
Radio Frequency planning Revgen (contd.)

overview . . . . . . . . . . . . . . . . 4-38 auto-Revgen. . . . . . . . . . . . . . . 3-70
Realign a network. . . . . . . . . . . . . 4-76 converting object files. . . . . . . . . . 3-66
Reload an NE database . . . . . . . . . . 4-74 menu options . . . . . . . . . . . . . . 3-66
Revert to saved network . . . . . . . . . 4-46 toolbar . . . . . . . . . . . . . . . . . 3-67
Revgen . . . . . . . . . . . . . . . . . . 3-66 Revgen command . . . . . . . . . . . . . 5-22
activating . . . . . . . . . . . . . . . . 3-68 Revgen multiple binary object files . . . . 3-130
Save NE database Service window (contd.)

Save NE. . . . . . . . . . . . . . . . . 4-43 File menu . . . . . . . . . . . . . . . . 3-58
Save network . . . . . . . . . . . . . . . 4-46 menu bar . . . . . . . . . . . . . . . . 3-58
aborting a save operation . . . . . . . . 4-52 Services menu . . . . . . . . . . . . . 3-64
Scheduling an audit . . . . . . . . . . . . 4-60 toolbar . . . . . . . . . . . . . . . . . 3-56
deleting . . . . . . . . . . . . . . . . . 4-66 Shutting down DataGen . . . . . . . . . . 3-11
modifying . . . . . . . . . . . . . . . . 4-65 Shutting down the OLM. . . . . . . . . . 4-12
Script file generator. . . . . . . . . . . . 3-71 Starting DataGen . . . . . . . . . . . . . 3-10
Service window Starting the OLM GUI. . . . . . . . . . . . 4-9
BSS area . . . . . . . . . . . . . . . . 3-56 Supported platforms . . . . . . . . . . . 1-15
Edit menu . . . . . . . . . . . . . . . . 3-63
68P02900W22-S IX-201
Jul 2008
Index
Table Controller . . . . . . . . . . . . . . 3-79 Tools - overview . . . . . . . . . . . . . . . 5-2

command buttons . . . . . . . . . . . . 3-80 Troubleshooting OLM
controls . . . . . . . . . . . . . . . . . 3-80 database errors . . . . . . . . . . . . . 4-81
creating MCDF files. . . . . . . . . . . 3-84 fails to start . . . . . . . . . . . . . . . 4-80
file select buttons . . . . . . . . . . . . 3-81 force shutdown . . . . . . . . . . . . . 4-83
file status display . . . . . . . . . . . . 3-81 general errors. . . . . . . . . . . . . . 4-82
files status icons . . . . . . . . . . . . 3-88 import errors . . . . . . . . . . . . . . 4-83
functions . . . . . . . . . . . . . . . . 3-80 reinitialise database. . . . . . . . . . . 4-85
menu bar . . . . . . . . . . . . . . . . 3-80 specific operation fails . . . . . . . . . 4-83
Toggle permissions (tp) command. . . . . 5-27
Uncompress OLM network . . . . . . . . 4-78 Usertool, using (contd.)

Upgrade multiple binary object files . . . 3-130 rename user account . . . . . . . . . . 2-10
Upgrader . . . . . . . . . . . . . . . . . 3-123 user administration utilities . . . . . . . . 2-4
Upgrading a BSS area . . . . . . . . . . 3-123 user management . . . . . . . . . . . . . 2-3
DARBC and EXBL . . . . . . . . . . . . 3-129 user management parameters . . . . . . 2-3
multiple BSS areas . . . . . . . . . . . 3-127 Using the CADM tool
resolving problems . . . . . . . . . . . 3-127 country administration . . . . . . . . . 3-27
upgrade procedure . . . . . . . . . . . 3-125 creating a new country . . . . . . . . . 3-30
Usage scripts . . . . . . . . . . . . . . . 3-20 creating a new network . . . . . . . . . 3-31
User and group management . . . . . . . . 2-2 deleting a country/network . . . . . . . 3-33
Usertool, using . . . . . . . . . . . . . . . 2-2 Using the Generic Table Editor
add group . . . . . . . . . . . . . . . . 2-14 Generic Table Editor (GTE) . . . . . . . 3-90
add new user account . . . . . . . . . . . 2-7 Using the Table Controller
delete group . . . . . . . . . . . . . . 2-17 editing MCDF tables . . . . . . . . . . 3-86
delete user account . . . . . . . . . . . 2-11 MCDF files . . . . . . . . . . . . . . . 3-84
group management parameters . . . . . 2-13 MCDF tables . . . . . . . . . . . . . . 3-81
modify group . . . . . . . . . . . . . . 2-15 Using the Topology Viewer . . . . . . . . 3-105
modify user account . . . . . . . . . . . 2-9 hardware configuration . . . . . . . . . 3-107
rename group . . . . . . . . . . . . . . 2-16
Verify NE database . . . . . . . . . . . . 4-43 Version upgrader (upg) command . . . . . 5-28

Verify network . . . . . . . . . . . . . . 4-46
aborting a verify operation . . . . . . . 4-50
Xterm icon . . . . . . . . . . . . . . . . 4-16
IX-202 68P02900W22-S
Jul 2008

68P02900W22

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

68P02900W22

Uploaded by

Copyright:

Available Formats

DataGen

© 2008 Motorola, Inc. All Rights Reserved.

System Information: DataGen

Chapter 1: Overview of DataGen

DataGen and the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Chapter 2: User and Group management using the usertool

Chapter 3: Operating DataGen

Administration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12

Converting a CM database object file to a script file . . . . . . . . . . . . . . . . . . . . . . . 3-66

Converting a database script file to a CM database object file . . . . . . . . . . . . . . . . . . 3-112

Chapter 4: Operating the Offline MIB

Expert Offline MIB front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17

Deleting a BSS or RXCDR from the Navigation Tree . . . . . . . . . . . . . . . . . . . . . . . 4-58

Chapter 5: Command line tools

Chapter 6: MCDF tables

Description of Site (BTS-specific) table . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9

Description of the Nail Connection table . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-194

Figure 1-1: DataGen GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Figure 3-32: Generics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-87

Figure 4-32: Audit Logs Abort Confirmation window. . . . . . . . . . . . . . . . . . . . . . . 4-69

Table 1-1: Supported platforms in GSR9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15

Table 5-11: Command line options (tp command) . . . . . . . . . . . . . . . . . . . . . . . . 5-27

System Information: DataGen

What is covered in this manual?

• Chapter 5 Command line tools, provides information on Command line tools.

The following sections show the revision status of this document.

Issue Date of issue Remarks

Resolution of Service Requests

The following Service Requests are resolved in this document:

Incorporation of Change Notices

The following Change Notices (CN) are incorporated in this document:

CN Date CN Number Title

N/A N/A N/A

Characters typed in at the keyboard are shown like this.

Messages, prompts, file listings, directories, utilities, and environmental

Special key sequences

Special key sequences are represented as follows:

Motorola appreciates feedback from the users of our documents.

Questions and comments

• The document title, part number, and revision character

• The page number with the error

• A detailed description of the error and if possible the proposed solution

In certain instances, Motorola makes specific recommendations regarding security practices.

Warnings, cautions, and notes

A note means that there is a possibility of an undesirable situation or provides additional

The following general safety guidelines apply to Motorola equipment:

• Power down or unplug the equipment before servicing.

• Portions of Motorola equipment may be damaged from exposure to electrostatic discharge.

• Council recommendation of 12 July 1999 on the limitation of exposure of the general

Caring for the environment

Disposal of Motorola equipment

Disposal of surplus packaging

CMM labeling and disclosure table

The label is placed in a customer visible position on the product.

Motorola document set

Ordering documents and CD-ROMs

Document banner definitions

Introduction to DataGen and the Offline MIB

Figure 1-1 DataGen GUI

The following functions can be performed using these tools:

• Define global defaults.

• Modify parameters across part or all of a network.

• Manage software loads.

• Generate SYSGEN databases.