Gsr7 Half Rate: System Information Datagen

SYSTEM INFORMATION
DATAGEN
GSM SOFTWARE RELEASE 7 HALF RATE
GSR7
Half Rate
68P02901W22-Q
GSR7 Half
68P02900W22-Q
SYSTEM INFORMATION
Rate
DATAGEN
GSM SOFTWARE RELEASE 7 HALF RATE
System Information: DataGen
© 1996 -2004 Motorola, Inc. 68P02900W22-Q
All Rights Reserved 09-Sep-2004

Copyrights
The Motorola products described in this document may include copyrighted Motorola computer programs stored in semiconductor memories or other media.
Laws in the United States and other countries preserve for Motorola certain exclusive rights for copyright computer programs, including the exclusive right to
copy or reproduce in any form the copyright computer program. Accordingly, any copyright Motorola computer programs contained in the Motorola products
described in this document may not be copied or reproduced 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, except for the rights that arise by operation of law in the sale of a product.
Restrictions
The software described in this document is the property of Motorola. It is furnished under a license agreement and may be used and/or disclosed only in
accordance with the terms of the agreement. Software and documentation are copyright 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.
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola assumes no liability resulting from any inaccuracies or omissions
in this document, or from the use of the information obtained herein. Motorola 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 does not assume any liability arising out of the application or use of any product or circuit described herein;
neither does it convey license under its patent rights of others.
Trademarks
Motorola and the Motorola logo are registered trademarks of Motorola Inc.
Intelligence Everywhere, M-Cell and Taskfinder are trademarks of Motorola Inc.
All other brands and corporate names are trademarks of their respective owners.
09-Sep-2004
Table
of
Contents
Contents
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Issue status of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Version information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Resolution of service requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Feature references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Cross references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Data encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Reporting safety issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Failure to comply with warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
General warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Warning labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Specific warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
General cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Caution labels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Specific cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Special handling techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Motorola manual set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Ordering manuals and CD-ROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
GMR amendment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
GMR availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
GMR instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
GMR amendment record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
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
68P02900W22-Q i
09-Sep-2004
Contents
The DataGen and OLM platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

DataGen database structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
BSS database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Sub-structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
The Offline MIB Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
The Offline MIB file structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Main structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Supported platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Chapter 2: User and Group management using the Admintool

User and Group management using the Admintool. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Introduction to the Admintool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Common Desktop Environment Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Admintool - overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Procedure list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
DataGen User management using the Admintool . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Introduction to user management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
User management parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
User password parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Other parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
User administration utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Display user account information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Add a new user account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Modify a user account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Change a user’s password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
DataGen Group management using the Admintool . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Introduction to group management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Group management parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Group administration utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Display group account information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Add a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Modify group information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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
Automate running of Revgen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Default file import path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Default export path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
ii 68P02900W22-Q
09-Sep-2004
System Information: DataGen Contents
Define default text editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Override area lock. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Output all elements in a script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
DataGen - startup and shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Introduction to startup and shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Administration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Overview of tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Changing permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Optimising the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Viewing the log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Customising 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-20
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 new country/network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Overview of creating a new country/network . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Country Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Country Administration window - overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
Creating a new country . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
Editing a country . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
Creating a new network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
Deleting a country/network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
Overview of deleting a country/network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
Deleting the network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
Deleting the country. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
Creating a new BSS area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
Overview of creating a BSS area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
New BSS Area window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
Creating a new BSS area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
Opening a BSS area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
Opening a BSS area procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
Copying a BSS area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40
Copying a BSS area procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40
Deleting a BSS area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-42
Deleting a BSS area procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-42
Configuring BSS area(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44
Introduction to configuring the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44
Explanation of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44
Functions and MCDF table relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44
Creating and configuring a basic BSS with a TS switch . . . . . . . . . . . . . . . . . . . . . . . . . 3-46
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46
Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46
Configuration of a BSS table and Table Controller. . . . . . . . . . . . . . . . . . . . . . . . . . 3-48
68P02900W22-Q iii
09-Sep-2004
Contents
Configuration of MCDF tables for a basic BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51

Basic BSS with TS switch - Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54
Copying a BSS area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-55
Expanding the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56
Daisy Chain configuration with TS switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58
Overview of Daisy Chain configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58
Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58
Daisy chain configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59
The Service window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-62
Functions of the Service window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-62
Service window toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-62
Service window menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-64
File menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-64
Edit menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-68
Services menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-69
Converting a CM database object file to a script file . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71
Introduction to creating a script file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71
Invoking Revgen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71
Revgen window description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71
File menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72
Information area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72
Data area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72
Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72
Activating Revgen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73
Activating auto Revgen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74
Completion of Revgen process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-75
Generating a database script file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-76
Overview of database script files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-76
Running the script file generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-76
Viewing a database script file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77
xedit window description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78
Using the toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78
File information areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78
File display area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-79
Alternative text editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-79
Viewing and editing DataGen files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-81
Overview of editing DataGen files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-81
Table Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-81
Generic Table Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-81
Topology Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-81
Upgrader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-81
Using the Table Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83
Running the Table Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83
Table Controller functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-84
User controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-84
Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-84
Command buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-84
File select buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85
File status display area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85
MCDF table files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85
Creating MCDF files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-88
MCDF file procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-88
MCDF table editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-90
iv 68P02900W22-Q
09-Sep-2004
File status icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-92

Using the Generic Table Editor (GTE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-94
Introduction to the Generic Table Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-94
The File menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-94
The Edit menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-100
Fill Cells window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-102
Format menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-104
MCDF key equivalents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-108
Using the Topology Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-109
Introduction to the Topology Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-109
Invoking the Topology Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-110
Using the Topology Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-111
Cage hardware configuration button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-111
The MMI button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-113
Path File button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-114
Increase magnification button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-114
Decrease magnification button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-114
Generating a hardware report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-115
Overview of hardware reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-115
Procedure for generating a hardware report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-115
Converting a database script file to a CM database object file . . . . . . . . . . . . . . . . . . . . . . . 3-117
Overview of conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-117
Producing a CM database object using SYSGEN mode . . . . . . . . . . . . . . . . . . . . . . . 3-117
Producing a CM database object using the DataGen binary object compiler . . . . . . . . . . . . . . 3-117
Exporting object files to the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-120
Overview of exporting object files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-120
Exporting multiple binary object files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-121
Exporting a single binary object file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-122
Exporting OLM binary object files to the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123
Difference Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-124
Introduction to the Difference Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-124
The Difference Reporter window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-124
Select BSS Area Details window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-125
Difference Reporter Information window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-127
Difference Reporter Report window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-128
Upgrader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-129
Overview of the Upgrade function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-129
Upgrade BSS Area window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-129
Upgrade BSS Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-131
Upgrade multiple BSS areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-133
Resolving upgrade problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-133
Overview of DARBC and Enhanced XBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-135
Batch processing of binary object files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-136
Overview of batch processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-136
Revgen multiple binary object files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-137
Upgrade multiple binary object files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-139
Compile multiple MMI scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-141
Chapter 4: Operating the Offline MIB

Introduction to the Offline MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Overview of the Offline MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Task list prior to using OLM GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Task list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
68P02900W22-Q v
09-Sep-2004
Contents
Additional OLM features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Levels of users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Troubleshooting the OLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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-11
Shutting down the OLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Front panel icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Offline MIB front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
About the Offline MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Configuration management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Find . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Xterm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Expert Offline MIB front panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Finding a Network Element or Site or Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Overview of Find function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Locating an NE, Site or Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Examples of using Find . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Using the Navigation Tree: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
Procedure list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
Opening and closing a Navigation Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Opening the Navigation Tree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Warning window invalid NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Resolving inconsistencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Closing the Navigation Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Moving levels on a Navigation Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Prerequisite to moving levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Procedure for moving levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Panner and porthole . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Creating a BSS/RXCDR from the Navigation Tree. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Introduction to creating an NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Procedure for creating a BSS or RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Audit: overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
Introduction to auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
Ways to audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
Running an audit from the Navigation Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
Introduction to auditing from the Navigation Tree . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
Audit from the Navigation Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
Modifying the network configuration from the Navigation Tree. . . . . . . . . . . . . . . . . . . . . . 4-32
Device management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
Configuring cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
CellXchange: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
Introduction to CellXchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
vi 68P02900W22-Q
09-Sep-2004
Overwrite a BSS/RXCDR binary object file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34

Overview of overwrite feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
Procedure for overwriting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
Verify and save: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
Introduction to applying changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
Verify and save NE database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
Verify a network element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
Save a network element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
Verify and save network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
Verify network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
Aborting a verify network in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43
Saving a network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44
Aborting a save network in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44
Deleting a network configuration in the OLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Introduction to deleting a network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Delete network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Network Expansion: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47
Overview of Network Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47
Additional OLM features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48
List of additional tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48
Using the autoclose function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49
Overview of autoclose feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49
Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49
Procedure for using autoclose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49
Deleting a BSS or RXCDR from the Navigation Tree . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
Scheduling an audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51
List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51
Creating a scheduled audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51
Modifying a scheduled audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55
Deleting a scheduled audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56
Auditing logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-57
List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-57
Viewing an audit log list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-57
Aborting an audit in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58
Inconsistency reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-59
Viewing an audit inconsistency report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-60
Deleting an audit log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-61
Audit log management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-62
Overview of audit log management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-62
Setting the delete period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-62
Reload NE database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64
Introduction to reloading an NE database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64
Procedure to reload an NE database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64
Realign a network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-66
Introduction to realigning a network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-66
Procedure for realigning a network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-66
Compress or uncompress an OLM network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68
Overview of compress and uncompress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68
Compress procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68
Uncompress procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-69
Troubleshooting the OLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-70
Introduction to troubleshooting the OLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-70
68P02900W22-Q vii
09-Sep-2004
Contents
Error OLM fails to start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-70

Database errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72
General errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-73
Specific operation fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-73
Import errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74
Introduction to the force shutdown feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74
Force shutdown OLM procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-75
Reinitialise database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-75
Chapter 5: Command line tools

Overview of command line tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Command line functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
User options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Copy Area (ca) command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Command line options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Example Copy Area usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
MMI Combiner (combine) command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Compile MMI script (compile) command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Auto-compile MMI script command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Example auto_compile usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Running cron jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Compress/uncompress 16xx binary object files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Delete database object (del) command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
viii 68P02900W22-Q
09-Sep-2004

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
MCDF filter command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
MMI command generator (gcmd) command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
Optimise DataGen database (dbaccess) command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Lock/unlock BSS area (lock_adm) command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
Revgen command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29
Auto-Revgen command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
Toggle permissions (tp) command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
68P02900W22-Q ix
09-Sep-2004
Contents
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
Version upgrader (upg) command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
Example of upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
Auto-upgrader command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37
Country administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39
Introduction to country administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39
The Command Line Interface (CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39
Invoking xcadm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
Using the xcadm GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
The menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41
Data fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
Action buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
CADM utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43
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-10
Description of Site (BTS specific) table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Cabinet table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
Description of Cabinet table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
Hardware table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
Description of Hardware table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
Generics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26
Description of Generics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26
Layout of elements in the MCDF Generics table. . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26
Generics table elements for GSM Half Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-44
Timer table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46
Description of Timer table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46
Layout of timer elements in the MCDF Timer table . . . . . . . . . . . . . . . . . . . . . . . . . 6-46
Modify Value table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-52
Description of Modify Value table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-52
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
x 68P02900W22-Q
09-Sep-2004
Contents
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-73
Description of Statistics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-73
Layout of the elements in the MCDF Statistics table . . . . . . . . . . . . . . . . . . . . . . . . . 6-74
Statistics table elements for GSM Half Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-100
Specifics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-102
Description of Specifics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-102
Description of Specifics table for GSM Half Rate . . . . . . . . . . . . . . . . . . . . . . . . . . 6-141
RTF table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-143
Description of RTF table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-143
Description for GSM Half Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-147
DRI table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-148
Description of DRI table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-148
Algorithm data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-153
Description of Algorithm data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-153
Neighbour table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-155
Description of Neighbour table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-155
Throttles table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-161
Description of Throttles table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-161
EAS table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-162
Description of EAS table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-162
Daughter table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-163
Description of Daughter table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-163
PIX table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-165
Description of PIX table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-165
KSW table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-166
Description of KSW table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-166
NSVC table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-168
Description of NSVC table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-168
Hop table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-169
Description of Hop table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-169
ACS table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-174
Description of ACS table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-174
68P02900W22-Q xi
09-Sep-2004
Contents
This page intentionally left blank.
xii 68P02900W22-Q
09-Sep-2004
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-7
Figure 2-2: Admin Tool icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Figure 2-3: CDE Desktop Front Panel with open OMC Admin drawer . . . . . . . . . . . . . . . . . . 2-8
Figure 2-4: Admintool: Users window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Figure 2-5: Admintool: Modify User window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Figure 2-6: Admintool: Add User window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Figure 2-7: Set User Password window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Figure 2-8: Admintool: Groups window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Figure 2-9: Admintool: Add Group window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Figure 2-10: Admintool: Modify Group window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Figure 2-11: Admintool: Warning window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Figure 3-1: DataGen main menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Figure 3-2: Administration menu - omcadmin user . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Figure 3-3: Permissions window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Figure 3-4: Confirm permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Figure 3-5: Administration menu - non-omcadmin user . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Figure 3-6: Example of a logfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Figure 3-7: Preferences window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Figure 3-8: Options Object Tool window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Figure 3-9: Country Administration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Figure 3-10: CADM Country File window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
Figure 3-11: CADM message window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
Figure 3-12: CADM Network File window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
Figure 3-13: New BSS Area window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
Figure 3-14: Warning message: name exceeds maximum valid length. . . . . . . . . . . . . . . . . . . 3-36
Figure 3-15: Overwrite BSS Area confirmation window . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
Figure 3-16: The Service window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37
Figure 3-17: Open BSS Area window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
Figure 3-18: Locked information window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39
Figure 3-19: Copy BSS Area window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40
Figure 3-20: Delete BSS Area window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-42
Figure 3-21: Information window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43
68P02900W22-Q xiii
09-Sep-2004
List of Figures
Figure 3-22: Basic BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46

Figure 3-23: Service window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47
Figure 3-24: Basic Table Controller window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47
Figure 3-25: BSS table (bss.mcd) window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49
Figure 3-26: Table Controller window (Part 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50
Figure 3-27: Table Controller window (Part 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51
Figure 3-28: Basic BSS with TS Switch - expanded . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-57
Figure 3-29: Service window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-62
Figure 3-30: Database Object window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-65
Figure 3-31: Import Object - information window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66
Figure 3-32: Export Object - information window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66
Figure 3-33: History - information window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67
Figure 3-34: Revgen window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73
Figure 3-35: Running Revgen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74
Figure 3-36: Invalid Options Object message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77
Figure 3-37: Viewing a database script file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78
Figure 3-38: Viewing an MMI script with vi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-80
Figure 3-39: Partial view of typical Table Controller display . . . . . . . . . . . . . . . . . . . . . . . 3-83
Figure 3-40: Generics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-91
Figure 3-41: File status icons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-93
Figure 3-42: New MCDF input file message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-95
Figure 3-43: MCDF Input File - Open option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-95
Figure 3-44: Save To File window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-97
Figure 3-45: Print Setup window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-98
Figure 3-46: Print Table window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-99
Figure 3-47: Fill Cells window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-102
Figure 3-48: Find window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-104
Figure 3-49: Goto Cell window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-105
Figure 3-50: Replace window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-106
Figure 3-51: Topology Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-110
Figure 3-52: Topology Viewer menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-111
Figure 3-53: The Cage Number window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-112
Figure 3-54: The Cage Description window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-113
Figure 3-55: Viewing a hardware report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-116
Figure 3-56: Binary Object Compiler window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-118
Figure 3-57: Difference Reporter window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-124
Figure 3-58: Select BSS Area Details window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-125
Figure 3-59: Difference Reporter - Information window . . . . . . . . . . . . . . . . . . . . . . . . . 3-127
Figure 3-60: Difference Reporter - Report window . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-128
Figure 3-61: Upgrade BSS Area window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-130
Figure 3-62: Locked information window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-132
Figure 3-63: Successful upgrade Status window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-132
Figure 3-64: Batch Tool window with Revgen selected. . . . . . . . . . . . . . . . . . . . . . . . . . 3-137
Figure 3-65: Revgen batch confirmation window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-138
Figure 3-66: Revgen Batch monitor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-139
Figure 3-67: Compile Batch monitor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-142
Figure 4-1: OLM Network Configurations window . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
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-10
Figure 4-5: Offline MIB front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Figure 4-6: GUI exit - confirmation window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Figure 4-7: OLM shutdown confirmation window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Figure 4-8: Binary Database Error and warning window for a Network element . . . . . . . . . . . . . . 4-13
xiv 68P02900W22-Q
09-Sep-2004
List of Figures
Figure 4-9: Expert desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16

Figure 4-10: Find window - selecting Find NE(s). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Figure 4-11: Find window with a Cell and Navigation Tree selected . . . . . . . . . . . . . . . . . . . 4-20
Figure 4-12: Navigation Tree window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Figure 4-13: Invalid NEs window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Figure 4-14: Navigation Tree window - showing panner . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Figure 4-15: BSS Binary configurations creation window . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Figure 4-17: Audit Inconsistency List window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
Figure 4-18: BSS Binary configurations window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
Figure 4-20: Binary Database error and warnings window . . . . . . . . . . . . . . . . . . . . . . . . 4-38
Figure 4-21: Offline MIB Database Operations window . . . . . . . . . . . . . . . . . . . . . . . . . 4-41
Figure 4-22: Offline MIB Verify Operation Monitor window . . . . . . . . . . . . . . . . . . . . . . . 4-41
Figure 4-23: Binary Database error and warnings window . . . . . . . . . . . . . . . . . . . . . . . . 4-42
Figure 4-24: Offline MIB Save Operation Monitor window . . . . . . . . . . . . . . . . . . . . . . . 4-44
Figure 4-25: Delete network Confirmation window . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Figure 4-26: Deleting a BSS or RXCDR - Confirmation window . . . . . . . . . . . . . . . . . . . . . 4-50
Figure 4-27: Admin Options window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51
Figure 4-28: Audit Scheduler window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
Figure 4-29: auSchedule Detailed View <create> window . . . . . . . . . . . . . . . . . . . . . . . . 4-53
Figure 4-30: Audit Scheduler window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55
Figure 4-31: Audit Logs window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58
Figure 4-32: Audit Logs abort confirmation window . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-59
Figure 4-33: Audit Log Management window in Edit mode . . . . . . . . . . . . . . . . . . . . . . . 4-63
Figure 4-34: Reload Confirmation window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-65
Figure 4-36: Compress from the OLM Network Configurations window . . . . . . . . . . . . . . . . . 4-69
Figure 4-37: Confirmation window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-75
Figure 4-38: Reinitialise DataBase - Confirmation window. . . . . . . . . . . . . . . . . . . . . . . . 4-76
Figure 5-1: Country Admin in use confirmation window . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
Figure 5-2: The xcadm GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41
Figure 6-1: Non-collocated BSS hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Figure 6-2: RXCDR Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
68P02900W22-Q xv
09-Sep-2004
List of Figures
xvi 68P02900W22-Q
09-Sep-2004
List
of
Tables
List of Tables
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Table 1: Manual version history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Table 2: Service requests resolved in this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Table 1-1: Supported platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Table 1-2: Supported platforms in GSR7 Half Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Table 3-1: Main menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Table 3-2: Function - MCDF table relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45
Table 3-3: Revgen window File menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72
Table 3-4: Revgen window File menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72
Table 3-5: Table Controller - menu bar File and Select options . . . . . . . . . . . . . . . . . . . . . . 3-84
Table 3-6: File menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-94
Table 3-7: Printer setup - menu buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-98
Table 3-8: Printer setup - data fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-99
Table 3-9: Printer setup - action buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-99
Table 3-10: Edit menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-101
Table 3-11: Fill cells - data fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-102
Table 3-12: Fill cells - options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103
Table 3-13: Fill cells - action buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103
Table 3-14: Format menu options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-104
Table 3-15: Find window - enable buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-105
Table 3-16: Action button definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-105
Table 3-17: Goto Cell - data fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-106
Table 3-18: Goto Cell - action buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-106
Table 3-19: Replace window - data fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-107
Table 3-20: Replace window - enable buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-107
Table 3-21: Replace window - option buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-107
Table 3-22: Replace window - actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-107
Table 3-23: Hot keys for MCDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-108
Table 3-24: Upgrader - list boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-130
Table 3-25: Upgrader - action buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-130
Table 4-1: Administrative tasks and user types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Table 4-2: Realign a network - cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-66
Table 4-3: OLM fails to start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-71
Table 4-4: Database Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72
Table 4-5: General operating errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-73
Table 4-6: Specific operation error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-73
Table 4-7: Importing NE software errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74
Table 5-1: Command line tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Table 5-2: Command line options (ca command) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Table 5-3: Command line options (auto_compile command) . . . . . . . . . . . . . . . . . . . . . . . 5-12
Table 5-4: Command line options (del command) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Table 5-5: Command line options (filter command) . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Table 5-6: Valid file names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
68P02900W22-Q xvii
09-Sep-2004
List of Tables
Table 5-7: Command line options (gcmd command) . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21

Table 5-8: Command Line options (lock_adm command) . . . . . . . . . . . . . . . . . . . . . . . . 5-25
Table 5-9: Command line options (revgen command) . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
Table 5-10: Command line options (auto_revgen command) . . . . . . . . . . . . . . . . . . . . . . . 5-31
Table 5-11: Command line options (tp command) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
Table 5-12: Command line options (upg command) . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Table 5-13: Command line options (auto_upgrade command) . . . . . . . . . . . . . . . . . . . . . . 5-37
Table 5-14: Action buttons definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
Table 6-1: BSS specific table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Table 6-2: Frequency Types Allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Table 6-3: Valid Frequency Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Table 6-4: BTS specific table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Table 6-5: Cabinet table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
Table 6-6: Frequency Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
Table 6-7: Option dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
Table 6-8: Hardware table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
Table 6-9: Generics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26
Table 6-10: Generics table - elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-27
Table 6-11: Generics table elements for GSM Half Rate . . . . . . . . . . . . . . . . . . . . . . . . . 6-44
Table 6-12: Timer table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46
Table 6-13: Timer table - elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-47
Table 6-14: Modify Value table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-52
Table 6-15: Circuit table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-54
Table 6-16: Channel table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-57
Table 6-17: Links table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-59
Table 6-18: Paths table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-61
Table 6-19: LAPD table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-63
Table 6-20: Cell table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-65
Table 6-21: Statistics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-73
Table 6-22: Statistics table - elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-74
Table 6-23: Statistics table - elements for GSM Half Rate . . . . . . . . . . . . . . . . . . . . . . . . 6-100
Table 6-24: Specifics table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-103
Table 6-25: Specifics table - elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-104
Table 6-26: Specifics table - elements for GSM Half Rate . . . . . . . . . . . . . . . . . . . . . . . . 6-141
Table 6-27: RTF table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-143
Table 6-28: RTF table for GSM Half Rate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-147
Table 6-29: DRI table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-148
Table 6-30: Algorithm data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-153
Table 6-31: Neighbour table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-155
Table 6-32: Throttles table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-161
Table 6-33: EAS table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-162
Table 6-34: Daughter table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-163
Table 6-35: PIX table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-165
Table 6-36: KSW table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-166
Table 6-37: NSVC table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-168
Table 6-38: Hop table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-169
Table 6-39: ACS table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-174
xviii 68P02900W22-Q
09-Sep-2004
About
This
Manual

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
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 visualise and validate networks before deployment into
a live network. It has a common User Interface (UI) with the online OMC. BSS binary files are used to create
the network which is displayed as a tree-like representation called the Navigation Tree.
In addition, the manual contains information on user and group management using the OMC Admintool. It
describes the procedures used for operating DataGen and associated administrative tasks. It also describes
the procedures used for operating the Offline MIB and provides information on command line tools and
Motorola Customer Data Format (MCDF) tables.
Information on performing Cell Xchange and Network Expansion from the Offline MIB is provided in the
manual Installation & Configuration: GSM System Configuration (68P02901W17) from GSR7.
Users should 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.
68P02900W22-Q 1
09-Sep-2004
Issue status of this manual

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The following shows the issue status of this manual since it was first released.
Version information
The following table lists the versions of this manual in order of issue:
Table 1 Manual version history
Manual
Date of issue Remarks
issue
C 31 May 1996 Issue C - Software Release 1.4.0.x
D 28 Mar 1997 Issue D - Software Release 1.4.1.x
E 29 Aug 1997 Issue E - GSM Software Release 2
F 27 Apr 1998 Issue F - GSM Software Release 3
G 12 Mar 1998 Issue G - GSM Software Release 4
H 14 Jul 2000 Issue H - GSM Software Release 4.1
J 31 Jul 2001 Issue J - GSM Software Release 5
K 30 Nov 2001 Issue K - GSM Software Release 5.1
L 30 Nov 2002 Issue L - GSM Software Release 6
M 02 May 2003 Issue M - GSM Software Release 6 (Horizon II)
P 13 Nov 2003 Issue P - GSM Software Release 7
Q 09 Sep 2004 Issue Q - GSM Software Release 7 Half-Rate
2 68P02900W22-Q
09-Sep-2004
Resolution of service requests
The following Service Requests are now resolved in this manual:
Table 2 Service requests resolved in this manual
Service GMR
Remarks
Request Number
1079031 N/A Updated field width of Transcoding Capability in the
Hardware table. Refer to Chapter 6.
1100310 N/A Neighbour PBGT parameter added to MCDF Neighbour
table. Refer to Chapter 6.
1104262 N/A Added PCU as device name for nsei to MCDF Hardware
table. Refer to Chapter 6.
68P02900W22-Q 3
09-Sep-2004
General information
General information
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
• 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 customers behalf, to abide by the instructions, system
parameters or recommendations made in this manual
• If this manual 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
will be supplied automatically by Motorola in the form of General Manual Revisions (GMRs).
Purpose
Motorola cellular communications manuals 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.
Failure to comply with Motorola’s operation, installation and maintenance

instructions may, in exceptional circumstances, lead to serious injury or death.
These manuals are not intended to replace the system and equipment training offered by Motorola, although
they can be used to supplement and enhance the knowledge gained through such training.
Feature references
Most of the manuals in the set, of which this manual is part, are revised to accommodate features released
at Motorola General System Releases (GSRn) or GPRS Support Node (GSNn) releases. In these manuals,
new and amended features are tagged to help users to assess the impact on installed networks. The tags are
the appropriate Motorola Roadmap DataBase (RDB) numbers or Research and Development Prioritization
(RDP) numbers. The tags include index references which are listed in the manual Index. The Index includes
the entry feature which is followed by a list of the RDB or RDP numbers for the released features, with
page references and hot links in electronic copy.
4 68P02900W22-Q
09-Sep-2004
General information
The tags have the format: {nnnn} or {nnnnn}

Where: is:
{nnnn} the RDB number
{nnnnn} the RDP number
The tags are positioned in text as follows:
New and amended feature information Tag position in text

New sentence/s or new or amended text. Immediately before the affected text.
Complete new blocks of text as follows: Immediately after the headings as follows:
• Full sections under a main heading • Main heading
• Full paragraphs under subheadings • Subheading

New or amended complete Figures and Tables After the Figure or Table number and before
the title text.
Warning, Caution and Note boxes. Immediately before the affected text in the box.
General command syntax, operator input or On a separate line immediately above the
displays (in special fonts). affected item.
For a list of Roadmap numbers and the RDB or RDP numbers of the features included in this software
release, refer to the manualSystem Information: GSM Overview (68P02901W01), or to the manual System
Information: GPRS Overview (68P02903W01).
Cross references
Throughout this manual, references are made to external publications, chapter numbers and section names.
The references to external publications are shown in italics, chapter and section name cross references
are emphasised blue in text.
This manual is divided into uniquely identified and numbered chapters that, in turn, 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.
Data encryption
In order to avoid electronic eavesdropping, data passing between certain elements in the GSM and GPRS
network is encrypted. In order to comply with the export and import requirements of particular countries,
this encryption occurs at different levels as individually standardised, or may not be present at all in some
parts of the network in which it is normally implemented. The manual set, of which this manual is a part,
covers encryption as if fully implemented. Because the rules differ in individual countries, limitations
on the encryption included in the particular software being delivered, are covered in the Release Notes
that accompany the individual software release.
68P02900W22-Q 5
09-Sep-2004
General information
Text conventions
The following conventions are used in the Motorola cellular infrastructure manuals to represent keyboard
input text, screen output text and special key sequences.
Input
Characters typed in at the keyboard are shown like this.
Output
Messages, prompts, file listings, directories, utilities, and environmental
variables that appear on the screen are shown like this.
Special key sequences

Special key sequences are represented as follows:
CTRL-c Press the Control and c keys at the same time.

ALT-f Press the Alt and f keys at the same time.
¦ Press the pipe symbol key.
CR or RETURN Press the Return key.
6 68P02900W22-Q
09-Sep-2004
Reporting safety issues
Reporting safety issues

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Whenever a safety issue arises, carry out the following procedure in all instances. Ensure that all site
personnel are familiar with this procedure.
Procedure
Whenever a safety issue arises:
Procedure 1 Safety issue reporting
1 Make the equipment concerned safe, for example by removing power.

2 Make no further attempt to adjust or rectify the equipment.
3 Report the problem directly to the Customer Network Resolution Centre, Swindon +44
(0)1793 565444 or China +86 10 88417733 (telephone) and follow up with a written
report by fax, Swindon +44 (0)1793 430987 or China +86 10 68423633 (fax).
4 Collect evidence from the equipment under the guidance of the Customer Network
Resolution Centre.
68P02900W22-Q 7
09-Sep-2004
Warnings and cautions

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The following describes how warnings and cautions are used in this manual and in all manuals of this
Motorola manual set.
Warnings
A definition and example follow below:
Definition of Warning
A warning is used to alert the reader to possible hazards that could cause loss of life, physical injury, or ill
health. This includes hazards introduced during maintenance, for example, the use of adhesives and solvents,
as well as those inherent in the equipment.
Example and format
Do not look directly into fibre optic cables or data in/out connectors. Laser
radiation can come from either the data in/out connectors or unterminated fibre
optic cables connected to data in/out connectors.
Failure to comply with warnings
Observe all warnings during all phases of operation, installation and maintenance of the equipment described
in the Motorola manuals. Failure to comply with these warnings, or with specific warnings elsewhere in
the Motorola manuals, or on the equipment itself, violates safety standards of design, manufacture and
intended use of the equipment. Motorola assumes no liability for the customer’s failure to comply with
these requirements.
Cautions
A definition and example follow below:
8 68P02900W22-Q
09-Sep-2004
Definition of Caution
A caution means that there is a possibility of damage to systems, software or individual items of equipment
within a system. However, this presents no danger to personnel.
Example and format
Do not use test equipment that is beyond its due calibration date; arrange for
calibration to be carried out.
68P02900W22-Q 9
09-Sep-2004
General warnings
General warnings
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Observe the following specific warnings during all phases of operation, installation and maintenance of
the equipment described in the Motorola manuals:
• Potentially hazardous voltage.
• Electric shock.
• RF radiation.
• Laser radiation.
• Heavy equipment.
• Parts substitution.
• Battery supplies.
• Lithium batteries,
Failure to comply with these warnings, or with specific warnings elsewhere in the Motorola manuals, violates
safety standards of design, manufacture and intended use of the equipment. Motorola assumes no liability for
the customer’s failure to comply with these requirements.
Warning labels
Warnings particularly applicable to the equipment are positioned on the equipment. Personnel working with
or operating Motorola equipment must comply with any warning labels fitted to the equipment. Warning
labels must not be removed, painted over or obscured in any way.
Specific warnings
Specific warnings used throughout the GSM manual set are shown below, and will be incorporated into
procedures as applicable.
These must be observed by all personnel at all times when working with the equipment, as must any other
warnings given in text, in the illustrations and on the equipment.
10 68P02900W22-Q
09-Sep-2004
General warnings
Potentially hazardous voltage
This equipment operates from a potentially hazardous voltage of 230 V a.c. single
phase or 415 V a.c. three phase supply. To achieve isolation of the equipment from
the a.c. supply, the a.c. input isolator must be set to off and locked.
When working with electrical equipment, reference must be made to the Electricity at Work Regulations 1989
(UK), or to the relevant electricity at work legislation for the country in which the equipment is used.
Motorola GSM equipment does not utilise high voltages.
Electric shock
Do not touch the victim with your bare hands until the electric circuit is broken.
Switch off. If this is not possible, protect yourself with dry insulating material and
pull or push the victim clear of the conductor.
ALWAYS send for trained first aid or medical assistance IMMEDIATELY.
In cases of low voltage electric shock (including public supply voltages), serious injuries and even death,
may result. Direct electrical contact can stun a casualty causing breathing, and even the heart, to stop. It
can also cause skin burns at the points of entry and exit of the current.
In the event of an electric shock it may be necessary to carry out artificial respiration. ALWAYS send for
trained first aid or medical assistance IMMEDIATELY.
If the casualty is also suffering from burns, flood the affected area with cold water to cool, until trained
first aid or medical assistance arrives.
68P02900W22-Q 11
09-Sep-2004
General warnings
RF radiation
High RF potentials and electromagnetic fields are present in this equipment

when in operation. Ensure that all transmitters are switched off when any
antenna connections have to be changed. Do not key transmitters connected
to unterminated cavities or feeders.
Relevant standards (USA and EC), to which regard should be paid 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
• CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields High Frequency (10
kHz to 300 GHz).
Laser radiation
Do not look directly into fibre optic cables or optical data in/out connectors. Laser
radiation can come from either the data in/out connectors or unterminated fibre
optic cables connected to data in/out connectors.
Lifting equipment
When dismantling heavy assemblies, or removing or replacing equipment, a

competent responsible person must ensure that adequate lifting facilities are
available. Where provided, lifting frames must be used for these operations.
When dismantling heavy assemblies, or removing or replacing equipment, the competent responsible person
must ensure that adequate lifting facilities are available. Where provided, lifting frames must be used for
these operations. When equipment has to be manhandled, reference must be made to the Manual Handling
of Loads Regulations 1992 (UK) or to the relevant manual handling of loads legislation for the country in
which the equipment is used.
12 68P02900W22-Q
09-Sep-2004
General warnings
Parts substitution
Do not install substitute parts or perform any unauthorized modification of

equipment, because of the danger of introducing additional hazards. Contact
Motorola if in doubt to ensure that safety features are maintained.
Battery supplies
Do not wear earth straps when working with stand-by battery supplies. Use
only insulated tools.
Lithium batteries
Lithium batteries, if subjected to mistreatment, may burst and ignite. Defective

lithium batteries must not be removed or replaced. Any boards containing
defective lithium batteries must be returned to Motorola for repair.
Contact your local Motorola office for how to return defective lithium batteries.
68P02900W22-Q 13
09-Sep-2004
General cautions
General cautions
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Observe the following cautions during operation, installation and maintenance of the equipment described
in the Motorola manuals. Failure to comply with these cautions or with specific cautions elsewhere in the
Motorola manuals may result in damage to the equipment. Motorola assumes no liability for the customer’s
failure to comply with these requirements.
Caution labels
Personnel working with or operating Motorola equipment must comply with any caution labels fitted to the
equipment. Caution labels must not be removed, painted over or obscured in any way.
Specific cautions
Cautions particularly applicable to the equipment are positioned within the text of this manual. These must be
observed by all personnel at all times when working with the equipment, as must any other cautions given
in text, on the illustrations and on the equipment.
Fibre optics
Fibre optic cables must not be bent in a radius of less than 30 mm.
Static discharge
Motorola equipment contains CMOS devices. These metal oxide semiconductor

(MOS) devices are susceptible to damage from electrostatic charge. See the
section Devices sensitive to static in the preface of this manual for further
information.
14 68P02900W22-Q
09-Sep-2004
Devices sensitive to static
Devices sensitive to static

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Certain metal oxide semiconductor (MOS) devices embody in their design a thin layer of insulation that is
susceptible to damage from electrostatic charge. Such a charge applied to the leads of the device could
cause irreparable damage.
These charges can be built up on nylon overalls, by friction, by pushing the hands into high insulation packing
material or by use of unearthed soldering irons.
MOS devices are normally despatched from the manufacturers with the leads short circuited together, for
example, by metal foil eyelets, wire strapping, or by inserting the leads into conductive plastic foam. Provided
the leads are short circuited it is safe to handle the device.
Special handling techniques
In the event of one of these devices having to be replaced, observe the following precautions when handling
the replacement:
• Always wear an earth strap which must be connected to the electrostatic point (ESP) on the
equipment.
• Leave the short circuit on the leads until the last moment. It may be necessary to replace the
conductive foam by a piece of wire to enable the device to be fitted.
• Do not wear outer clothing made of nylon or similar man made material. A cotton overall
is preferable.
• If possible work on an earthed metal surface or anti-static mat. Wipe insulated plastic work
surfaces with an anti-static cloth before starting the operation.
• All metal tools should be used and when not in use they should be placed on an earthed surface.
• Take care when removing components connected to electrostatic sensitive devices. These
components may be providing protection to the device.
When mounted onto printed circuit boards (PCBs), MOS devices are normally less susceptible to electrostatic
damage. However PCBs should be handled with care, preferably by their edges and not by their tracks and
pins, they should be transferred directly from their packing to the equipment (or the other way around) and
never left exposed on the workbench.
68P02900W22-Q 15
09-Sep-2004
Motorola manual set
Motorola manual set

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Motorola manual sets provide the information needed to operate, install and maintain the Motorola
equipment. Manuals for the GSM, GPRS and UMTS products are available on the following media:
• Printed hard copy.
• Electronic, as fully navigable PDF files on:

◦ The Motorola customer support web site at:
(https://mynetworksupport.motorola.com/index.asp).
◦ CD-ROM produced in support of a major system software release.
Each CD-ROM includes all manuals related to a specified main GSM, GPRS or UMTS software release,
together with current versions of appropriate hardware manuals, and has additional navigation facilities. A
snapshot copy of on-line documentation is also included, though it will not be updated in line with subsequent
point releases.
The CD-ROM does not include Release Notes or documentation supporting specialist products such as
MARS or COP.
Ordering manuals and CD-ROMs
Use the Motorola 68Pxxxxxxxx order (catalogue) number to order hard copy manuals or CD-ROMs.
All orders must be placed with your Motorola Local Office or Representative.
16 68P02900W22-Q
09-Sep-2004
GMR amendment
GMR amendment
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Changes to a manual that occur after the printing date are incorporated into the manual using General Manual
Revisions (GMRs). GMRs are issued to correct Motorola manuals as and when required. A GMR has the
same identity as the target manual. Each GMR is identified by a number in a sequence that starts at 01
for each manual at each issue.
GMR availability
GMRs are published as follows:
• Printed hard copy - Complete replacement content or loose leaf pages with amendment list.
◦ Remove and replace pages in this manual, as detailed on the GMR instruction sheet.
• Motorola service web - Updated at the same time as hard copies.
• CD-ROM - Updated periodically as required.
GMR instructions
When a GMR is inserted in this manual, the amendment record below is completed to record the GMR.
Retain the instruction sheet that accompanies each GMR and insert it in a suitable place in this manual for
future reference.
68P02900W22-Q 17
09-Sep-2004
GMR amendment
GMR amendment record
Record the insertion of GMRs in this manual in the following table:
GMR number Incorporated by (signature) Date

01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
18 68P02900W22-Q
09-Sep-2004
Chapter
1
Overview of DataGen
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02900W22-Q 1-1
09-Sep-2004
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 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/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.
Included in this information are 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-Q
09-Sep-2004
System Information: DataGen Overview of DataGen
These tools include functionality to:

• Upload BSS parameter data from an operational network (via 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, visualise 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, propagating
neighbour changes from one BSS Binary file to another.
Figure 1-2 Offline MIB - Front Panel
68P02900W22-Q 1-3
09-Sep-2004
Offline MIB functionality
The Offline MIB enables users to:
• Provide a graphical representation of a network.
• Edit configuration management parameters.
• Propagate cell and neighbour parameters.
• Interface to Radio Frequency (RF) Planning tools.
DataGen / Offline MIB integration
DataGen and the Offline MIB work together in the following ways (refer to Figure 1-3):
• Binary database object files can be imported from the OMC.
• Upgrading may be carried out from DataGen.
• Multiple binary object files can be imported into the OLM and Radio Frequency planning
can be carried out.
1-4 68P02900W22-Q
09-Sep-2004
System Information: DataGen Overview of DataGen
Figure 1-3 DataGen/Offline MIB functions

#

#

$

! " #
#
#%
#

$%

&
$

The DataGen and OLM platform
DataGen and/or the OLM is implemented on either a Sun Ultra 5/10/60 or Sun Netra 440 platform. DataGen
and the OLM use many of the same software tools as the OMC-R, thus maximizing commonality between
the two systems. DataGen should be deployed on a shared Ethernet LAN with the OMC-R to facilitate
data interchange.
68P02900W22-Q 1-5
09-Sep-2004
Hardware
DataGen and the OLM is configured to run on a standalone processor with its own disk storage, tape drive
and CD-ROM drive. The system processor uses a Sun Ultra station which has, at a minimum, a 200 MHz
processor, with 512 Mbyte of RAM.
Sun Netra 440 is supported if the Half Rate option is purchased.

Standard peripherals include a DAT tape drive, a CD-ROM drive and monitor. The standard system is
configured for LAN Ethernet support.
Software
DataGen and OLM is 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 CD-ROM together with all third party products.
Figure 1-4 DataGen in a GSM environment.
DataGen NMC
OMC-R
OSI
Local Area Network
System
Server
BSC GUI Server OSI Processor Operator

Workstations
X.25
BSC
BSC
BSC
1-6 68P02900W22-Q
09-Sep-2004
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:
Database script file

A database script file is an ASCII file which may be read from, or written to. It can be produced manually by
entering text into an ASCII file. This process is very slow and is likely to introduce errors. The file must be
formatted precisely to contain the correct number of line feeds and spaces. DataGen provides a faster, 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 Sun Ultra
Platform and 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 have been uploaded to be
imported into DataGen using Revgen.
68P02900W22-Q 1-7
09-Sep-2004
DataGen database structure Chapter 1: Overview of DataGen
Figure 1-5 DataGen-OMC integration

"# "#

"$ $"$

&

!

!

% &

$

!

% "$ $
'
"$

1-8 68P02900W22-Q
09-Sep-2004
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:
1. Gather or create input files.
2. Start up DataGen.
3. Create new BSS area.
4. Import input files into new BSS area.
5. Import binary object files into the Offline MIB.
68P02900W22-Q 1-9
09-Sep-2004
Loading network information into DataGen Chapter 1: Overview of DataGen
Figure 1-6 Loading network information into DataGen

!

Gathering network information
The first task is to gather network configuration information for the network. This information is then used to
produce input files which can be read by DataGen. The input files may be entered directly into either
of 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-Q
09-Sep-2004
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
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 below 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.
Directories for DataGen MUST NOT be created manually. DataGen creates the
directories automatically, thus ensuring there are no syntax errors in the directory
names.
68P02900W22-Q 1-11
09-Sep-2004
Figure 1-8 DataGen directory structure

! "# $
Main structure
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 number.
For example:
$HOME/dg/UK/testbss/conf0
All directories must be created by DataGen for each BSS area. Users are strongly advised to leave the
directory creation to DataGen in order to avoid problems with capitalization.
1-12 68P02900W22-Q
09-Sep-2004
Sub-structure
Inside the conf<N> directory there may be a number of 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.
The Offline MIB Directory Structure
The directories below the OLM are created when a user creates a new 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

The Offline MIB file structure
Each network configuration can contain up to 128 binary object (.002) files. An example of one 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
68P02900W22-Q 1-13
09-Sep-2004
Main structure
The Offline MIB DDS is structured as follows:

/usr/gsm/DataGen/olm/<network_configuration>
Where: is:
network_configuration replaced by the network configuration
name which contains .002 files.
Supported platforms
DataGen is configured to run as a standalone processor with its own disk storage, tape drive and CD-ROM
drive. Table 1-1 and Table 1-2 list the hardware configurations supported.
Table 1-1 Supported platforms
Processor External mirrored disks External mirrored disks

Ultra 5 (3 x 9Gb) x 2 (3 x 36Gb) x 2
Ultra 10 (3 x 9Gb) x 2 (3 x 36Gb) x 2
Ultra 60 (3 x 9Gb) x 2 (3 x 36Gb) x 2
Table 1-2 Supported platforms in GSR7 Half Rate
Processor Internal mirrored disks

Netra 440 (2 x 72Gb) x 2
Note that the same configuration is used for Clean Install and Upgrade platforms.
Netra 440 is only supported if the Half Rate option is purchased.
DataGen GSR7 Half Rate is supported on a new “Flexible Platform”. Customers may use any
Sun UltraSPARC machine, provided that it meets a minimum specification set by Motorola. For
more details, refer to Bulletin Number GSM_G_OMCR_050.
1-14 68P02900W22-Q
09-Sep-2004
Chapter
2
User and Group management using the
Admintool
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02900W22-Q 2-1
09-Sep-2004
User and Group management using the Admintool Chapter 2: User and Group management using the Admintool
User and Group management using the Admintool

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to the Admintool
This chapter describes the procedures required to add new users and groups to the DataGen processor using
the Admintool. The Admintool can be accessed through the Common Desktop Environment (CDE) Manager.
If DataGen is configured as a NIS client, user and group information must be configured on
the NIS server and should not be carried out on the DataGen processor. For details, refer to
Configuring DataGen as a NIS client in the System Administration Guide provided with
Software Release Notes: DataGen (68P02900W76).
Common Desktop Environment Manager
The Common Desktop Environment (CDE) Manager provides a desktop environment which can be
customised 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.
2-2 68P02900W22-Q
09-Sep-2004
System Information: DataGen User and Group management using the Admintool
Admintool - overview
Admintool is a GUI based utility which is used for managing DataGen users, Informix users and so on, on
the DataGen processor. The utility is run from the Common Desktop Environment (CDE). It can be used to
perform the following management tasks:
• Manage user accounts
• Manage groups
• Manage hosts
• Manage printers
• Manage serial port services
• Manage software
When setting up new DataGen users, it is necessary to use the New DG User option in the OMC
Admin Tool Drawer as environment settings also need to be set up.
Do not use Admintool to create new DataGen users directly.
Procedure list
This chapter details the following procedures:

• "DataGen User management using the Admintool" on page 2-4
• "DataGen Group management using the Admintool" on page 2-13
68P02900W22-Q 2-3
09-Sep-2004
DataGen User management using the Admintool Chapter 2: User and Group management using the Admintool
DataGen User management using the Admintool

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to user management
Admintool can be used to perform the following user management tasks:

• Display user accounts
• Add a new user account
• Modify a user account
• Change a users password
• Delete a user account
• Copy a user account to a new user name
Admintool is a graphical user interface (GUI) that enables users to manage 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.
Before assigning users to specific groups, ensure that the groups first exist. Before adding user accounts, use
the Admintool to add any groups to which users will be assigned. Refer to "DataGen Group management
using the Admintool" on page 2-13 for more information.
2-4 68P02900W22-Q
09-Sep-2004
System Information: DataGen DataGen User management using the Admintool
User management parameters
The following parameters are available under the Admintool:users option:

• User Name
This 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). A user name’s first character must be a letter.
• User ID (UID)
This specifies the unique number by which the operating system can identify a user. The
maximum value is 2147483647. It is recommended that UIDs be kept below
60000 to minimize the amount of software incompatibilities. Reserved UIDs
include 60001 (nobody) and 65534 (nobody4).
• Primary Group
This specifies a group ID number or group name that the operating system assigns to files
created by the user. Assuming the correct permissions are set, these files can
then be accessed by users in the same group. Group 10 (staff) is the default
primary group that is appropriate for most users.
• Secondary Groups (Optional)

This parameter specifies one or more groups to which the user
also belongs. A group ID number or group name may be specified. If more than one group is
specified, they must be separated from the other group(s) with commas.
• Comment
Enter the user name, as it is to be displayed on the Offline MIB standard GUI.
• Login Shell
This specifies a login shell (Bourne, Korn, or C-shell) for the user. Select Other to specify a
shell not in the list. It is recommended that the C-shell is used for DataGen purposes.
68P02900W22-Q 2-5
09-Sep-2004
User password parameters
The password option specifies the means by which a user sets up a password. Password options are as follows:
• Cleared until first login
Users are prompted to set their password at initial
login.
• Account is locked
Account is locked. No user may access this account.
• No password - setuid only

Account cannot be logged into, but account programs are
allowed to run.
• Normal password
Displays the Set Password window, which allows a password
to be assigned to the account when adding the user.
Min Change, Max Change, Max Inactive, Expiration Date and Warning
data fields should NOT be used if the configuration of the DataGen machine
as a NIS client is intended.
• Min Change (Optional)

Specifies the minimum number of days allowed between password changes. This
can be used to prevent a user from changing a password and immediately
changing it back to the original password.
• Max Change (Optional)

Specifies the maximum number of days the user can go without having to set up a new
password. If the password is not changed within this number of days, the
user account is locked until you modify the user accounts Password field to
Normal Password or Cleared until first login.
• Max Inactive (Optional)

Specifies the maximum number of days the user account can
be inactive before the user account is locked. The user account remains locked until the user
accounts Password field is modified to Normal Password or Cleared until first login.
• Expiration Date (Optional)

Specifies the day, month, and year when the user account
expires and is locked. The user account remains locked until the user accounts Password field
is modified to Normal Password or Cleared until first login.
• Warning (Optional)
Specifies when users will start receiving warning messages about their password expiring.
2-6 68P02900W22-Q
09-Sep-2004
Other parameters
The following parameters are also available under the Admintool: Users option:
• Create Home directory
Specifies whether to automatically create the user’s home directory.
• Path
Specifies the path for the user’s home directory, for example, /home/omcadmin
or /usr/informix.
User administration utilities
From the front panel of the CDE Desktop (Figure 2-1), click the Admin Tool icon (Figure 2-2). The
Admintool: Users window (Figure 2-4) is displayed.
Figure 2-1 CDE Desktop - Front Panel
Click the arrow above the Admin Tool icon to open the OMC Admin drawer.
Figure 2-2 Admin Tool icon
68P02900W22-Q 2-7
09-Sep-2004
The OMC Admin drawer provides access to the User Administration applications as in Figure 2-3. Click
the arrow again to close the OMC Admin drawer.
Figure 2-3 CDE Desktop Front Panel with open OMC Admin drawer
Display user account information
To display the user accounts for a particular system from the CDE Desktop, click the Admin Tool icon.
The Admintool: Users window (Figure 2-4) is displayed. The default view is a view of all users on the system.
Figure 2-4 Admintool: Users window
To display information for a particular user, double click on a user name to open an Admintool: Modify
User window as shown in Figure 2-5.
2-8 68P02900W22-Q
09-Sep-2004
Click Cancel to close the window.
Figure 2-5 Admintool: Modify User window
Add a new user account
To add a new user to a group, perform the following steps:

1. From the CDE Desktop, click the arrow above the Admin Tool icon to open the OMC Admin
drawer.
2. Select New DG User.

The Admintool: Users window is displayed with File, Edit and Browse menus.
68P02900W22-Q 2-9
09-Sep-2004
3. Open the Edit menu and select Add.
The Admintool: Add User window is displayed as in Figure 2-6.
Figure 2-6 Admintool: Add User window
4. Enter the required data into the User name, User ID, Primary Group, Comment, and
Secondary Groups (optional) data fields.
Refer to the section User management parameters earlier in this chapter for more
information about data fields. Multiple users may be set up in one Admintool:
Add User session.
5. Ensure that the login shell is set for the C shell option.
6. If the System Administrator has supplied a default password, ensure that the Password scroll
box is set to Normal Password; otherwise, set to Cleared until first login.
2-10 68P02900W22-Q
09-Sep-2004
7. Ensure the Create Home Dir: check box is enabled.
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.
9. Exit Admintool, by selecting the Exit option in the File menu.

The new user is created as a DataGen user, that is, dg and olm links are created.
Modify a user account
To modify a User account, perform the following steps:

1. Open the Admintool: Users window.
2. Select the User Account entry to be modified in the displayed Admintool: Users window
(see Figure 2-4).
3. Select Modify from the Edit menu to display the Admintool: Modify User window (as in
Figure 2-5).
4. Highlight each data field to be modified and delete its contents.
5. Enter the new data into the relevant data field.
6. Click OK.
Change a user’s password
To change a user’s password, perform the following steps:

1. Highlight a User Name entry in the Admintool: Users window (see Figure 2-4).
2. Select the Modify option from the Edit menu.

The Admintool: Modify User window is displayed as in Figure 2-5, with the selected user
name shown in the User Name data field.
68P02900W22-Q 2-11
09-Sep-2004
3. Select Normal Password from the Password menu.

The Set User Password window is displayed as shown in Figure 2-7.
Figure 2-7 Set User Password window
4. Enter a password in the Enter Password data field.
A password must be 6 to 8 characters in length contain at least two alphabetic

characters (A-Z, a-z) and at least one numeric or special character different
from the user’s login name.
5. Re-enter the password in the Verify Password data field.
6. Click OK to set the password.
Password aging may be set up using the Min Change, Max Change, Max
Inactive, Expiration Date and Warning fields. See the section User management
parameters earlier in this chapter for descriptions of each of these fields.
2-12 68P02900W22-Q
09-Sep-2004
System Information: DataGen DataGen Group management using the Admintool
DataGen Group management using the Admintool

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to group management
Admintool is a GUI based utility which is used for managing groups on the DataGen processor. The utility is
run from the Common Desktop Environment (CDE). It is used to perform the following group management
tasks:
• Display group account information
• Add a group
• Modify group information
• Delete a group
The Admintool: Groups option may be used to manage the group file on the local system.
Before assigning users to specific groups, ensure that the groups first exist. Before adding user accounts, use
the Admintool: Groups option to add any groups to which users will be assigned.
Group management parameters
The following parameters are available under the Admintool: Add Group option:
• Group Name
Group Name specifies a name used by the system to identify a user’s group. A
group name contains lowercase alphabetical characters (a-z) and digits (0-9). A
group name can be 1 to 8 characters long.
• Group ID (GID)
Group ID specifies a group identification number used by the system to identify a user’s
primary group. The maximum value is 2147483647. To minimize the amount of
software incompatibilities, GIDs should be kept below 60000. Reserved GIDs
include 60002 (noaccess) and 65534 (nogroup).
• Members List (Optional)

The Members List optional parameter specifies users or groups who
belong to this group. If there is more than one member in the list, then
the names are separated with a comma. Spaces are not allowed.
Example: user1, user2, user3.

To delete user name(s), select the name(s) with the mouse and click Delete.
68P02900W22-Q 2-13
09-Sep-2004
DataGen Group management using the Admintool Chapter 2: User and Group management using the Admintool
Group administration utilities
Group administration utilities are similar to user administration utilities (refer to "DataGen User
management using the Admintool" on page 2-4). From the front panel of the CDE Desktop (Figure 2-1),
click the Admin Tool icon (Figure 2-2). The Admintool: Users window (Figure 2-4) is then displayed with
File, Edit and Browse menus.
Display group account information
To display the group accounts for a particular system from the CDE Desktop, click the Admin Tool icon to
open the Admintool: Users window.
Select the Groups option from the Browse menu. The Admintool: Groups window is displayed as in
Figure 2-8.
Figure 2-8 Admintool: Groups window
Group options are defined in the section Group management parameters earlier in this chapter.
2-14 68P02900W22-Q
09-Sep-2004
Add a group
To add a new group, perform the following steps:

1. Select Add from the Edit menu in the Admintool: Groups window.
An Admintool: Add Group window is displayed as shown in Figure 2-9.
Figure 2-9 Admintool: Add Group window
2. Enter the following parameters:

◦ Group Name
◦ Group ID
◦ Members List
Group options are defined in the section Group management parameters

earlier in this chapter.
3. Click OK.
The list of groups displayed in the Admintool: Groups window is updated to include the
new group.
4. Verify that the new group has been added by locating the new group in the Admintool:
Groups window.
68P02900W22-Q 2-15
09-Sep-2004
Modify group information
To modify group information such as adding and deleting members, perform the following steps:
1. Highlight the Group to be modified in the Admintool: Groups window.
2. Select Modify from the Edit menu.

The Admintool: Modify Group window is displayed as shown in Figure 2-10.
Figure 2-10 Admintool: Modify Group window
3. Enter the information to be modified into the data fields as required.
4. Click OK.
5. Verify that the group has been modified by locating the group information in the Admintool:
Groups window.
Refer to the section Group management parameters earlier in this chapter for a description of
each field in the Admintool: Modify Group window.
2-16 68P02900W22-Q
09-Sep-2004
Delete a group
To delete a group, perform the following steps:

1. Highlight the Group to be modified in the Admintool: Groups window.
2. Select Delete from the Edit menu.
3. The Admintool: Warning window is displayed as shown in Figure 2-11, requesting

confirmation of the deletion.
Figure 2-11 Admintool: Warning window
4. Click OK.
The selected group is deleted and the group information displayed in the Admintool: Groups
window is updated.
68P02900W22-Q 2-17
09-Sep-2004
2-18 68P02900W22-Q
09-Sep-2004
Chapter
3
Operating DataGen
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02900W22-Q 3-1
09-Sep-2004
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. It should be used in conjunction with Chapter 6 - MCDF Tables.
The information in this chapter is aimed primarily at new users of DataGen and the routines are set out in the
order in which they would normally 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 will work with an
existing database and perform a variety of DataGen functions to generate a working database.
If the user has been successful in editing or creating new information in the database, then the database should
compile successfully and create a viable BSS script.
Procedures for operating DataGen
The following procedures for operating DataGen should be performed in the order in which they are listed:
1. "Importing existing CM database objects" on page 3-26
2. "Converting a CM database object file to a script file" on page 3-71

- Using Revgen
3. "Generating a database script file" on page 3-76

- Using the MMI tool
4. "Viewing and editing DataGen files" on page 3-81

- Using the Service Window, Table Controller, Generic Table Editor and Topology viewer
5. "Converting a database script file to a CM database object file" on page 3-117

- Using the Binary Object Compiler
6. "Exporting object files to the OMC" on page 3-120
3-2 68P02900W22-Q
09-Sep-2004
System Information: DataGen Overview of operating DataGen
Other procedures for operating DataGen may be performed as required, including:

• "Administration tasks" on page 3-11
• "Creating a new country/network" on page 3-27
• "Deleting a country/network" on page 3-32
• "Creating a new BSS area" on page 3-34
• "Opening a BSS area" on page 3-38
• "Copying a BSS area" on page 3-40
• "Deleting a BSS area" on page 3-42
• "Configuring BSS area(s)" on page 3-44
• "Difference Reporter" on page 3-124
• "Upgrader" on page 3-129
• "Batch processing of binary object files" on page 3-136
For information on operating the offline MIB, refer to Chapter 4.
68P02900W22-Q 3-3
09-Sep-2004
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 in order to get information
unique to a specific user. Several environment variables can be created and used by DataGen.
Certain variables can be set from the DataGen main menu by using the ADMIN - Preferences option. Refer
to "Administration tasks" on page 3-11 for more details.
These standard C shell environment variables must be set up prior to running DataGen.
HEX or decimal representation
Two environment variables can be set up to allow users to decide at run time whether they want HEX
or DECIMAL representation.
DG_HEX_CELL_IDS determines in what format GSM cell ids are displayed.
DG_HEX_POINT_CODES determines in what format the elements opc and dpc are displayed. The
format applies to the MMI script and to MCDF.
The variables should be set to yes to display the values in HEX. This can be achieved using the following
commands in the C shell:
setenv DG_HEX_CELL_IDS yes
setenv DG_HEX_POINT_CODES yes
These variables can also be set from the DataGen main menu using the ADMIN - Preferences
option. Refer to "Administration tasks" on page 3-11 for more details.
3-4 68P02900W22-Q
09-Sep-2004
System Information: DataGen Defining environment variables
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 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 will give a significant performance improvement.
To enable time slot order equipage, enter the following command in the C shell:
setenv DG_AGGREGATE_ABIS yes
To disable time slot order equipage, enter the following command in the C shell:
setenv DG_AGGREGATE_ABIS no
This variable can also be set from the DataGen main menu using the ADMIN - Preferences
Automate running of Revgen
Revgen converts a binary object file into an Informix format. Revgen may be invoked by selecting the
Services option from the Services menu, or by selecting the Revgen button.
To automate the running 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 running of Revgen from the Service menu or Revgen button, enter the following
command in the C shell:
setenv DG_AUTO_REVGEN no
68P02900W22-Q 3-5
09-Sep-2004
option. Refer to "Administration tasks" on page 3-11 for details.
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 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
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
3-6 68P02900W22-Q
09-Sep-2004
System Information: DataGen Defining environment variables
Define default text editor
From the Service window it is possible to view 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 or vi or xedit
This variable can also be set from the DataGen main menu using the ADMIN -
Preferences option. Refer to "Administration tasks" on page 3-11 for more details.
To define another editor other than three standard editors, refer to "Generating a database
script file" on page 3-76.
Override area lock
When accessing a BSS area that is already in use, a warning message is displayed allowing the opportunity
to unlock the area or cancel.
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
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 from the Service menu.
68P02900W22-Q 3-7
09-Sep-2004
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, run 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
Setting the value to yes may result in compilation failures and should be used only to view
default values.
3-8 68P02900W22-Q
09-Sep-2004
System Information: DataGen DataGen - startup and shutdown
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 3-1.
Figure 3-1 DataGen main menu
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.
68P02900W22-Q 3-9
09-Sep-2004
DataGen - startup and shutdown Chapter 3: Operating DataGen
Table 3-1 Main menu options
Select To
NEW Display windows where a new BSS area can be created.
OPEN Display windows where an existing BSS area can be viewed or
edited.
UPG Display windows where an existing BSS area can be upgraded to
a later version.
COPY Display windows where BSS areas can be copied.
DEL Display windows where an existing BSS area can be deleted.
DIFF Display windows where difference reports between sites and site
elements for BSS areas can be generated.
BATCH Display windows where multiple binary object files may be
Revgened, upgraded or compiled.
ADMIN Display windows where a range of Administration tasks may be
carried out for example Country administration.
OLM Display windows 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, OLM On-Line
help is available via 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, run 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.
3-10 68P02900W22-Q
09-Sep-2004
System Information: DataGen Administration tasks
Administration tasks
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of tasks
The following is a list of tasks that may be carried out by selecting the ADMIN option from the DataGen
main menu:
• Country Admin
This option allows a new country or network configuration to be created.
Refer to "Creating a new country/network" on page 3-27 for more details.
• Permissions
The DataGen user has a standard set of access permissions. This utility changes between
access permitted and access denied states.
• Defragment
To maximise free disk space, it is advisable to defragment or optimise 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 and uncompressed,
they may be installed by using this feature.
The following options are only available if the user is logged into the DataGen
processor as omcadmin: Permissions, Defragment and Options.
68P02900W22-Q 3-11
09-Sep-2004
Administration tasks Chapter 3: Operating DataGen
Changing permissions
To change or toggle access permissions for a user, carry out the following procedure:
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-9 for details.)
The Administration menu is displayed as shown in Figure 3-2.
Figure 3-2 Administration menu - omcadmin user
3. Select the Permissions option.

The Permissions window is then displayed as in Figure 3-3.
Figure 3-3 Permissions window
3-12 68P02900W22-Q
09-Sep-2004
4. Enter the Username and click Toggle to grant or withhold permissions.
Enter valid users only, such as omcadmin, informix and so on.

A confirmation window is displayed, as shown in Figure 3-4.
Figure 3-4 Confirm permissions
5. Click OK to return the Administration menu.
Refer to the section on Viewing the log file for more details.
68P02900W22-Q 3-13
09-Sep-2004
Optimising the database
To defragment or optimise the DataGen database, run the following commands:

The Administration menu is displayed (refer to Figure 3-5).
3. Select the Defragment button.

A status window is displayed stating:
Defragmenting the database, Please Wait ...
When the defragmentation is complete, a confirmation window is displayed.
4. Click OK to return the Administration menu.
After performing a defragmentation, exit the GUI and then re-open it to access
the previously created areas.
3-14 68P02900W22-Q
09-Sep-2004
Viewing the log file
To view the log file, perform the following steps:

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-5.
Figure 3-5 Administration menu - non-omcadmin user
Figure 3-5 displays the default menu for non-omcadmin users.

The DataGen logfile is displayed, showing a 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-6.
Figure 3-6 Example of a logfile
4. Enter Ctrl+C to exit the logfile and return to the Administration menu.
68P02900W22-Q 3-15
09-Sep-2004
Customising parameters
From the Preferences menu, several different parameters can be customised. To view the preferences
available, run the following commands:
It is not essential to select any of these criteria. If they are not required, simply omit these
steps and DataGen applies default values.
The Administration menu is displayed (as shown in Figure 3-5).
3. Select Preferences from the menu.

The Preferences window is displayed as in Figure 3-7.
Figure 3-7 Preferences window
Several environment variables can be turned on from the Preferences window for the current
session.
3-16 68P02900W22-Q
09-Sep-2004
4. Click the appropriate option buttons to enable the required environment variables. Refer to
"Defining environment variables" on page 3-4 for a detailed description.
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 or vi or xedit.
If an alternative editor is available, enter the name of the text editor. Refer to
"Generating a database script file" on page 3-76 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 will be 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.
Preferences needs to be set 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-9 for details.
An alternative to shutting down DataGen is to execute the following

command in the Xterm window from which DataGen was started:
source .cshrc
68P02900W22-Q 3-17
09-Sep-2004
Installing the Options Object
The Option Object files must be copied from tape, uncompressed and stored in a directory on
the DataGen processor. Refer to the section Upgrade procedures in Software Release Notes:
DataGen (68P02900W76) for details.
To install Options Object files, run the following commands:
The Administration menu is displayed (as shown in Figure 3-5).
3. Select Options from the menu.

The Options Object Tool window is displayed as in Figure 3-8.
Figure 3-8 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.
3-18 68P02900W22-Q
09-Sep-2004
8. Click the Install button. 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 for details on how to read the logfile.
68P02900W22-Q 3-19
09-Sep-2004
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 may be executed manually or as a cronjob.
If the usage script is executed as a cronjob, it must be re-started after any upgrade activity
has been 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 has been activated as a cronjob, log on to the DataGen processor as omcadmin.
Execute the following command:
crontab -l
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
3-20 68P02900W22-Q
09-Sep-2004
System Information: DataGen Database administration tasks
To run the script, enter the following command:

usage
Warning messages issued
If either the file system or the Informix database reach 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.
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 may be a problem with the integrity of the database.
68P02900W22-Q 3-21
09-Sep-2004
To resolve the problem, execute the following commands:

1. Log on to DataGen processor as omcadmin.
2. Enter the following command to verify that no-one is accessing DataGen:

whodo
3. Close all open DataGen GUIs.
4. Start DGAdmin by entering:

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). This procedure should be carried
out 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.
This procedure will permanently erase the dg_db Informix database and should
be used with caution.
3-22 68P02900W22-Q
09-Sep-2004
To drop and recreate the db_dg Informix database, carry out the following steps in this order:
1. Unload the OLM netwk_conf table.
2. Unload the DataGen configuration tables.
3. Prepare to drop and recreate the Informix database.
4. Drop the database.
5. Create a new database.
6. Load the OLM netwk_conf table.
7. Load 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 (all
one 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 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-Q 3-23
09-Sep-2004
Preparing to drop and recreate the Informix database

Before dropping and recreating the Informix database, carry out the following steps:
1. Back up the Informix database. Refer to the section Backup Procedures in Software Release
Notes: DataGen (68P02900W76) for details.
2. Log on to DataGen processor as omcadmin.
3. Enter the following command to verify that no-one is accessing DataGen:

whodo
4. Close all open DataGen GUIs.
5. Start DGAdmin by entering:

DGAdmin
6. To display the INFORMIX-SQL main menu, type:

dbaccess
To drop and recreate the Informix database, use the following steps:
Dropping the database

To 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: is:
DataGen hostname name of the DataGen processor
A confirmation menu is displayed. Select yes to continue.
4. Select Exit and in all subsequent menus to return to the Admin prompt.
3-24 68P02900W22-Q
09-Sep-2004
Creating a new database

To recreate the Informix db_dg database:
1. Execute the following commands to create a new database:
/usr/omc/DataGen/current/install/CreateDatabase
2. To activate each user on the new Informix database, type:

tp -u <username>
Where: is:
username 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 (all one line):
echo "load from /usr/tmp/netwk_conf.unl insert into netwk_conf" | DGAdmin
dbaccess db_dg
The OLM network configurations should now be 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 (all one 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 should now be visible in the DataGen GUI.
68P02900W22-Q 3-25
09-Sep-2004
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. Until the development of
DataGen, it was only possible to create such a file 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: Do the following:

Create a Country and Network, if not already done Use the ADMIN option in the main menu 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-Q
09-Sep-2004
System Information: DataGen Creating a new country/network
Creating a new country/network

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of creating a new country/network
Existing DataGen users with an earlier DataGen version can use this database to maintain previously created
country/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/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
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-5).
Select Country Admin from the Administration menu. The Country Administration window is displayed as
shown in Figure 3-9.
If the Country Admin option is already in use, a warning message is displayed. Click OK to return to the
Administration menu.
Figure 3-9 Country Administration window
68P02900W22-Q 3-27
09-Sep-2004
Creating a new country/network Chapter 3: Operating DataGen
Country Administration window - overview
The Country Administration window (as in Figure 3-9) enables users to create, update, and edit Country and
Network Administration files as follows:
File menu
The user option is:
• Exit
Use the Exit option to exit from the Country Administration window.
Network menu
The user options are:
• 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.
Country and Network menu options may be greyed out, according to which
operations are permitted at the time.
Country menu
• 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.
For NEW users where no country.std file exists, select Generate from
the Country menu to automatically generate a country.std file in the
/omcadmin/dg/ADMIN/country directory. This also applies to the network.std
file.
3-28 68P02900W22-Q
09-Sep-2004
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.
Creating a new country
To create a new country using Country Admin option, perform the following steps:
1. Select the Edit option from the Country menu in the Country Administration window
(as in Figure 3-9).
The CADM Country File window shown in Figure 3-10 is displayed.
Figure 3-10 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.
68P02900W22-Q 3-29
09-Sep-2004
Creating a new country/network Chapter 3: Operating DataGen
4. Select Store in DDS from the File menu in the CADM Country File window.
The new data is only saved locally at this point.
5. Select Exit from the File menu to close the CADM Country File window.
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-11.
Figure 3-11 CADM message window
7. Confirm the update by clicking the OK button.

A message is displayed showing that the update has taken place.
The new data is now permanently stored.
Editing a country
Once a country has been created, it can be edited using the Edit option from the Country menu on the
Country Administration window.
3-30 68P02900W22-Q
09-Sep-2004
Creating a new network
A new network entry is created and edited in the same way as a new country entry, using the same sequence of
steps.
1. Select Edit from the Network menu in the Country Administration window (as in Figure 3-9).
The CADM Network File window is displayed as in Figure 3-12.
2. Perform Step 2 as for Country, and enter the required data in the MNC, NCC, Network Name
and Operator Name data fields.
Figure 3-12 CADM Network File window
3. Select Store in DDS from the File menu in the CADM Network File window.
The new data is only saved locally at this point.
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-11.
6. Confirm the update by clicking the OK button.

A message is displayed showing that the update has taken place.
The new data is now permanently stored.
68P02900W22-Q 3-31
09-Sep-2004
Deleting a country/network Chapter 3: Operating DataGen
Deleting a country/network
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of deleting a country/network
To delete a country using the Country Administration Tool, the associated BSS area(s) and network must
first be deleted.
The BSS area(s), network and country must be deleted in the following order:
1. BSS area(s)
2. Network
3. Country
To delete a BSS area(s), refer to the section "Deleting a BSS area" on page 3-42 for details.
Deleting the network
After deleting the BSS areas(s), the network can then be deleted using the following steps:
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-9.
3. Select Edit from the Network menu.

The CADM Network File window is displayed as in Figure 3-12 showing a list of networks.
4. Click on 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.
3-32 68P02900W22-Q
09-Sep-2004
System Information: DataGen Deleting a country/network
Deleting the country
After the BSS areas(s) and its network have been deleted, the country can be deleted using the same sequence
of steps as described above for the network.
On the Country Administration window, select the Edit option from the Country menu and follow Step 4
to Step 9 above to delete the country.
68P02900W22-Q 3-33
09-Sep-2004
Creating a new BSS area Chapter 3: Operating DataGen
Creating a new BSS area

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

User input areas Country Name (automatically entered)
BSS Area
Software Version
Configuration No.
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.
BSS Area
When a Country Name has been selected, any BSS areas currently configured for that country are displayed.
3-34 68P02900W22-Q
09-Sep-2004
System Information: DataGen Creating a new BSS area
Users can select an existing BSS area or else create a new 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 has been selected, the software versions available are listed in the Software Version
column. Select the appropriate software version.
Configuration No.
When the software version has been selected, the configuration numbers that already exist are listed in the
Configuration No. column. Three user options are available:
• Enter a new configuration number by typing the number in the text box below the
Configuration No. column.
• Re-use an existing number by selecting from the list of numbers.
• No selection. 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 users to add useful information or comments which are displayed every
time the BSS area is selected.
When all entries have been made, click Create. DataGen checks the entries and opens the Service Window.
Click Close to exit without creating a new BSS area.
68P02900W22-Q 3-35
09-Sep-2004
Creating a new BSS area Chapter 3: Operating DataGen
Creating a new BSS area
To create a new BSS area, perform the following steps:

1. Select a country from the Country Name list in the New BSS Area window (refer to
Figure 3-13).
2. Click in the text box under the BSS Area column and enter the name of the new BSS area.
The name may have a maximum of 30 characters. If more than 30 characters are entered, a
warning window is displayed as Figure 3-14. Click OK to continue and then enter a BSS
Area name limited to the maximum length.
Figure 3-14 Warning message: name exceeds maximum valid length
4. To obtain a configuration number automatically, do not select a number but skip ahead to Step 6.
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 No. list box.
If re-using an existing number, a confirmation window is displayed as in Figure 3-15.
Figure 3-15 Overwrite BSS Area confirmation window
3-36 68P02900W22-Q
09-Sep-2004
System Information: DataGen Creating a new BSS area
Click OK to overwrite the existing BSS area or Cancel to return to the New BSS Area window,
and re-enter an alternative number.
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-16.
Figure 3-16 The Service window
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.
Note that the Service window shown here has two of the toolbar icons greyed out (these
functions will become available at a later stage). The following section describes the layout
and functionality of the Service window.
68P02900W22-Q 3-37
09-Sep-2004
Opening a BSS area Chapter 3: Operating DataGen
Opening a BSS area

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Opening a BSS area procedure
To open an existing BSS area from the DataGen Main window, use the following steps:
1. From the DataGen main menu, select Open.
The Open BSS Area is displayed as shown in Figure 3-17.
Figure 3-17 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 No. list.
Select multiple configuration numbers to open multiple configurations

simultaneously as shown in Figure 3-17.
3-38 68P02900W22-Q
09-Sep-2004
System Information: DataGen Opening a BSS area
6. Click Open.
After a short delay, the Service window is displayed. Refer to "The Service window" on
page 3-62 for details. The Service window provides options which enable users to view and
edit DataGen input files.
If the BSS area is locked by another user, an information window is displayed as shown in
Figure 3-18.
Figure 3-18 Locked information window
If the Override Lock parameter is enabled then the configuration is unlocked

automatically. Refer to "Administration tasks" on page 3-11 for details.
7. Click OK to override the lock or Cancel to return to the Open BSS Area window.
Information on the user holding the lock may be found in the DataGen.log file.
Refer to "Administration tasks" on page 3-11 for details.
68P02900W22-Q 3-39
09-Sep-2004
Copying a BSS area Chapter 3: Operating DataGen
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 where the
area was copied from.
To copy a BSS area, carry out the following procedure:
1. From the DataGen main menu, select Copy.
The Copy BSS Area window is displayed as in Figure 3-19.
Figure 3-19 Copy BSS Area window
5. Select a configuration number from the Configuration No. list.
6. Enter the name of new BSS area in the field below the Target BSS list.
To overwrite an existing BSS area, select the BSS area from the Target BSS list.
3-40 68P02900W22-Q
09-Sep-2004
System Information: DataGen Copying a BSS area
7. Enter a configuration number in the field below the Target Config list.
If the number already exists, DataGen assigns the next available number.
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: is:
BSS area name of the original BSS
area
Configuration No configuration number of
the original BSS area
8. Click Copy to copy the selected BSS area to a new area.
All columns in the Table Controller window for the new area are blank because the
structure is copied but not the input tables.
68P02900W22-Q 3-41
09-Sep-2004
Deleting a BSS area Chapter 3: Operating DataGen
Deleting a BSS area

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Deleting a BSS area procedure
To delete an existing BSS area, use the following steps:

1. From the DataGen main menu select DEL. The Delete BSS Area is displayed as shown in
Figure 3-20.
Figure 3-20 Delete BSS Area window
2. Select a country from the Country Name list in the Delete BSS Area window.
5. Select the configuration number from the Configuration No. list.
Select multiple configuration numbers to delete BSS areas simultaneously. Locked

areas are automatically unlocked.
3-42 68P02900W22-Q
09-Sep-2004
System Information: DataGen Deleting a BSS area
6. Click Delete. An Information window is displayed briefly as shown in Figure 3-21.
Figure 3-21 Information window
It is possible to return 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, a second 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.
68P02900W22-Q 3-43
09-Sep-2004
Configuring BSS area(s) Chapter 3: Operating DataGen
Configuring BSS area(s)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to configuring the BSS
Three examples of BSS configurations are provided:

• Configuration of a basic BSS with a Timeslot Switch (TS)
• Expansion of the 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
These terms are used as follows:
BSS area
The BSS area means both the GSM Base Station System (BSS) and the GSM Remote Transcoder (RXCDR).
These two sub-systems 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 will support 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 a MCDF table that is populated with parameters which
may be generic or specified by the user. Table 3-2 lists these functions and their equivalent MCDF table(s).
3-44 68P02900W22-Q
09-Sep-2004
System Information: DataGen Configuring BSS area(s)
Table 3-2 Function - MCDF table relationships
Function Equivalent MCDF table(s)

Equip Site (modify or add new Site
site)
Equip Cabinet Cabinet
Equip Cage (Automatically done when device is equipped)
Site Configuration BTS, Generics & Statistics
Add Cell Cell, Generics, Timers & Specifics
Equip Devices Hardware, Modify Value & Daughter
Equip Functions Hardware
Path Paths & Links
RTF RTF
BSP, DHP, BTP, LCF, MTL, DRI
Circuits, Path, RSL, OML Hardware
Circuits
KSW
PIX Card Daughter & PIX
Neighbour & Source Neighbour
Equip DRIM Hardware & RTF
Handovers Algorithm
Equip Pen Hardware
Equip NSVC NSVC
68P02900W22-Q 3-45
09-Sep-2004
Creating and configuring a basic BSS with a TS switch Chapter 3: Operating DataGen
Creating and configuring a basic BSS with a TS

switch
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview
This section describes the procedure for configuring a basic BSS, as shown in Figure 3-22. In this example,
the new basic BSS has a Base Site Controller (BSC) and one Base Transceiver Site (BTS) connected through
a Timeslot (TS) switch.
Figure 3-22 Basic BSS
Preparation
Before configuring the basic BSS, start DataGen and create a new BSS area. Refer to the procedure
"Creating a new BSS area" on page 3-34 for more information.
3-46 68P02900W22-Q
09-Sep-2004
System Information: DataGen Creating and configuring a basic BSS with a TS switch
Once the new BSS area has been created, DataGen checks the entries and opens the Service window as in
Figure 3-23. For more information about the Service window, refer to "The Service window" on page 3-62.
Figure 3-23 Service window
Select Table Control from the Services menu to display a basic Table Controller window (as in Figure 3-24).
This window enables the user to configure a BSS table for the new BSS area. Refer to the section "Using the
Table Controller" on page 3-83 for more information.
Initially, only the BSS file is displayed by the Table Controller (as in Figure 3-24). The remaining
MCDF files are not displayed until the BSS area is defined and the edited bss.mcd file is stored
in the DDS.
Figure 3-24 Basic Table Controller window
68P02900W22-Q 3-47
09-Sep-2004
Configuration of a BSS table and Table Controller
To open and configure a new (blank) BSS table, perform the following steps:
1. Select the BSS button in the Table Controller window.
2. Select the File button to open a blank BSS table (bss.mcd) window (as in Figure 3-25).
3. The BSS area data is shown in the first four data fields: Country, BSS Name, Software
Version Desired and BSS ID.
4. Enter the appropriate data in each VALUE field. Refer to BSS table in Chapter 6, MCDF
Tables for more information on the permitted values and ranges.
The BSS Serial value continues to show NOT YET AVAILABLE until a later
DataGen version.
5. When all the required data has been entered, move the cursor to the first RANGE field, then
open the File menu and select Store in DDS.
6. Select Exit from the File menu to close the BSS window and return to the Table Controller
window.
3-48 68P02900W22-Q
09-Sep-2004
7. Click Validate. A message window displays the following information: Filtering of file(s)
has completed. Close the message window.
Figure 3-25 BSS table (bss.mcd) window
8. Select the BSS and click Insert. A message window displays the following information:
Filtering of file(s) was successful database has been updated. Close the message window.
68P02900W22-Q 3-49
09-Sep-2004
The Table Controller window now displays check boxes for each MCDF file as in Figure 3-26
and Figure 3-27.
Figure 3-26 Table Controller window (Part 1)
3-50 68P02900W22-Q
09-Sep-2004
Figure 3-27 Table Controller window (Part 2)
9. To configure the parameters for the MCDF tables, continue to the next section.
Configuration of MCDF tables for a basic BSS
The procedure for entering configuration parameters for the remaining tables is the same for each table.
The parameters for the following tables may be left blank, and if so, will assume default values (assigned
by the DataGen processor):
• Generics table
• Timer table
• Statistics table
• Specifics table
• Throttles table
68P02900W22-Q 3-51
09-Sep-2004
Alternatively, users can manually assign their own parameter values to the above tables, using the values
and their ranges for these tables given in Chapter 6 - MCDF Tables.
Configuration procedure
To configure an MCDF table, perform the following steps:
1. Select the MCDF check boxes in the Table Controller window in the order of their appearance
(see Figure 3-26). Once the MCDF table is selected, click the File button to display a blank
<filename.mcd> table.
2. Place the cursor in the top left-hand data field and enter the appropriate value. Refer to Chapter
6 - MCDF Tables for information on table values and their ranges.
3. Continue to enter data until all the relevant data fields have been edited, then move the
cursor back to the first data field.
4. Open the File menu and select the Store in DDS option to store the data.
5. Select Exit from the File menu to close the edited MCDF table.
6. Clear the current MCDF check box in the Table Controller window and select the next required
MCDF check box to display the next <filename.mcd> table.
7. Repeat Step 2 to Step 6 until all required MCDF tables have been edited. Then perform
the next procedure.
MCDF table(s) insert and validate procedure

To insert and validate the configured MCDF table(s), perform the following steps:
1. In the Table Controller window, open the Select menu.
2. Select the Select All Files option, then click Validate.

The MCDF Files being validated are displayed in a message window. A second window
then displays the 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 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
3-52 68P02900W22-Q
09-Sep-2004
4. Close the message window.
The dashes and crosses under the File, Validate, and Insert buttons in the Table
Controller window are replaced by a tick for each MCDF file successfully
processed.
5. 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 Services window to display
the configuration. (Refer to the section "Using the Topology Viewer" on page 3-109
for more information).
68P02900W22-Q 3-53
09-Sep-2004
Basic BSS with TS switch - Expansion Chapter 3: Operating DataGen
Basic BSS with TS switch - Expansion

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview
This section describes the procedures used to add another BTS site to the basic BSS described in the previous
section. To expand the basic network, it is necessary to modify the following MCDF tables:
• The bss.mcd table (Site 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
The following procedures are also required:

• Copy an existing BSS area to a new BSS area with a different configuration number.
• From the Table Controller window, open each of the tables listed above in turn 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.
3-54 68P02900W22-Q
09-Sep-2004
System Information: DataGen Basic BSS with TS switch - Expansion
Copying a BSS area
To copy an existing BSS area (such as the Basic BSS in the previous section), perform the following steps:
A BSS area may be copied by selecting Copy from the DataGen main menu. Refer to "Copying
a BSS area" on page 3-40 for details.
1. Open an Xterm window, and enter the command: DGAdmin to obtain the DGAdmin prompt.
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:Area1600:17 -area Area1600 -config 18
A message similar to the following is displayed:
New area successfully copied
Country: Austria
BSS Area name: Area1600
Configuration Number: 18
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.
The 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-62.
68P02900W22-Q 3-55
09-Sep-2004
Basic BSS with TS switch - Expansion Chapter 3: Operating DataGen
Expanding the BSS
The procedure for entering reconfiguration parameters in the tables so as to expand the basic BSS is the same
for each table. The tables to be modified are listed in the overview of this section.
Reconfigure for expansion

To reconfigure the necessary MCDF tables, perform the following steps:
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-83 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 need to be added before the data can be modified, go to Step 3; otherwise
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 need to be added; otherwise go to Step 5.
5. Enter the appropriate values in the data fields. Use the Return key to step 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. Then carry
out the MCDF table(s) insert and validate procedure as detailed in the previous section
"Creating and configuring a basic BSS with a TS switch" on page 3-46.
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-109 for more information).
3-56 68P02900W22-Q
09-Sep-2004
System Information: DataGen Basic BSS with TS switch - Expansion
Figure 3-28 shows the topology of the new BSS area with the additional site added.
Figure 3-28 Basic BSS with TS Switch - expanded
68P02900W22-Q 3-57
09-Sep-2004
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.
The following procedures are necessary:
• 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 listed above in turn 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 may 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-40 for details.
Once the BSS area has been copied, select Open from the DataGen main menu to display the BSS Area
window.
The list of available countries is displayed. Select the following: Country Name, BSS Area Name, Software
Version and enter the new configuration number. 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-62.
3-58 68P02900W22-Q
09-Sep-2004
System Information: DataGen Daisy Chain configuration with TS switch
Daisy chain configuration
This procedure is used to 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 - procedure

To reconfigure the necessary MCDF Tables, perform the following steps:
• From the Service window, open the Service menu.
• Select Table Controller to open a Table Controller window. Refer to the section "Using the
Table Controller" on page 3-83 for more information.
For each table to be modified, perform the following steps.
Links table
To 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 have been 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.
68P02900W22-Q 3-59
09-Sep-2004
Daisy Chain configuration with TS switch Chapter 3: Operating DataGen
Paths table
To 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 Delete to delete
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.
cursor away from the edited data fields.
LAPD table
To 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 Delete to delete
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 have been edited, then using the Return
key, move the cursor away from the edited data fields.
3-60 68P02900W22-Q
09-Sep-2004
System Information: DataGen Daisy Chain configuration with TS switch
Cell table
To 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.
cursor away from the edited data fields.
5. Clear the RTF check box in the Table Controller window and continue with the MCDF
table(s) insert and validate procedure as detailed in the section "Creating and configuring
a basic BSS with a TS switch" on page 3-46.
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 Services window to display the configuration. (Refer to the
section "Using the Topology Viewer" on page 3-109 for more information).
68P02900W22-Q 3-61
09-Sep-2004
The Service window Chapter 3: Operating DataGen
The Service window

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Functions of the Service window
The Service window provides several options which enables 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-29. 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-29 Service window
Service window toolbar
The Service window toolbar contains six buttons which have the following functionality:
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.
3-62 68P02900W22-Q
09-Sep-2004
System Information: DataGen The Service window
Revgen/Compile
This 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.
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 via the OLM GUI’.
68P02900W22-Q 3-63
09-Sep-2004
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
Import object
Selecting Import Object from the File menu in the Service window displays the Database Object window as
shown in Figure 3-30. This window enables 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.
3-64 68P02900W22-Q
09-Sep-2004
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-30 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-31) is displayed when the file has been imported to the BSS area.
68P02900W22-Q 3-65
09-Sep-2004
The binary object creation Date and Time stamp is displayed in the information window.
Figure 3-31 Import Object - information window
Export Object
Select this option to display the default path to where binary objects are exported.
To transfer binary object files from DataGen to a BSS, first transfer the binary objects files to the OMC.
Refer to "Exporting object files to the OMC" on page 3-120 for more details. Next, download the binary
object files from the OMC to the BSS.
Selecting Export Object from the File menu on the Service window only identifies the file path for the OMC
operator. The following information window is displayed:
Figure 3-32 Export Object - information window
To define an alternative path to export the binary object files (002) to, refer to "Administration
tasks" on page 3-11 for details.
3-66 68P02900W22-Q
09-Sep-2004
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.
History
This option provides the following details to identify a BSS area as follows:
• 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-33 History - information window
Exit
Selecting this option closes the Service window, returning to the DataGen Main window. This option is the
same as clicking the X button in the Service window.
68P02900W22-Q 3-67
09-Sep-2004
Edit menu
The following options are available from the Edit menu in the Service window:
• Script
• Compile log
• Upgrade log
• Hardware report
Script
This option enables the user to view an MMI Script file via the X-Windows editor xedit. Refer to the section
"Generating a database script file" on page 3-76.
Compile log
This option enables the user to view the compile log file, via the X-Windows editor xedit, running the object
compiler. Refer to the section "Generating a database script file" on page 3-76 for details.
Upgrade log
This option enables the user to view the upgrade log file, via a text editor. The upgrade log file is available for
upgrades carried out via the GUI. The log file is not created if the upgrade is carried out from the command
line. Refer to "Upgrader" on page 3-129 for details on how to upgrade a software release.
Users may define the default editor for editing scripts or viewing the compile or upgrade logs.
Hardware Report
This option enables the user to view a hardware report via a text editor. Refer to "Generating a hardware
report" on page 3-115 for details.
3-68 68P02900W22-Q
09-Sep-2004
Services menu
The following options are available from the Services menu in 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-83 for details.
Revgen
Selecting this option activates the Revgen process and converts 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-71 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 if the software version is 1.6.0.0 or greater.
Recombine Script
Selecting this option enables the concatenation of a number of MMI script files into a single file. This
also generates individual site based MMI script files, for example: SITEXXX where XXX is replaced by
the site number.
Topology
The option becomes available after the Revgen process is complete. Selecting this option enables 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.
68P02900W22-Q 3-69
09-Sep-2004
Generate Hardware Report

The option becomes available after the Revgen process is complete. Selecting this option enables the user to
generate a hardware report which contains a list of all the devices names, function names, slot numbers and Id
devices within each cage. Refer to "Generating a hardware report" on page 3-115 for details.
3-70 68P02900W22-Q
09-Sep-2004
System Information: DataGen Converting a CM database object file to a script file
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 may
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.
Revgen can only be run successfully 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-34) is divided into four areas as follows:
• File menu
• Information area
• Data area
• Toolbar
68P02900W22-Q 3-71
09-Sep-2004
Converting a CM database object file to a script file Chapter 3: Operating DataGen
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 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.
3-72 68P02900W22-Q
09-Sep-2004
Activating Revgen
If the setenv DG_AUTO_REVGEN environment variable is not set to yes, run Revgen as follows:
1. Select the REVGEN button or select Revgen from the Services menu.
The Revgen window is displayed as in Figure 3-34.
Figure 3-34 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.
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.
68P02900W22-Q 3-73
09-Sep-2004
Converting a CM database object file to a script file Chapter 3: Operating DataGen
8. Click Run Revgen. The information and data areas display the details and progress of the
object conversion. An example is shown in Figure 3-35.
Figure 3-35 Running Revgen
9. Click Exit to return to the Service window when the process is complete.
If the Exit button is selected before Revgen is complete, the actual conversion of
the 002 object will NOT be 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. Figure 3-35 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.
3-74 68P02900W22-Q
09-Sep-2004
If the Exit button is selected before Revgen is complete, the actual conversion of the .002
object will NOT be 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.
If the prompt BSS Area is locked appears when trying to open a BSS area, refer to the section
Lock/Unlock BSS area in Chapter 5 - Command Line Tools for more information. Alternatively,
use the Remove Lock File option in the File menu of the Watch window.
68P02900W22-Q 3-75
09-Sep-2004
Generating a database script file Chapter 3: Operating DataGen
Generating a database script file

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of database script files
After the Revgen process has successfully completed, it produces a database script file in the DataGen
output file directory.
The system also issues a report stating that the database tables have been populated.
Running the script file generator
Generating a database script can be performed from the Services window (refer to Figure 3-30) 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 No.) to identify the correct file. The user is informed when the script has been
successfully created.
The database script file is stored in the output file directory of DataGen.
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 to be compared against the new script.
Individual site files are created for example; SITE<XXX> where XXX is
replaced by the site number.
3-76 68P02900W22-Q
09-Sep-2004
System Information: DataGen Generating a database script file
If the Options Object file is found to be missing or corrupt, an error message as shown in
Figure 3-36 is displayed. Refer to "Administration tasks" on page 3-11 for details of reinstalling
the Options object file.
Figure 3-36 Invalid Options Object message
Viewing a database script file
After a database script file has been created, it may be viewed by selecting the Script option in the Edit
menu of the Service Window.
The script file is displayed within an xedit window as shown in Figure 3-37. 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 have been made.
68P02900W22-Q 3-77
09-Sep-2004
To define which editor to launch when viewing scripts, refer to "Defining environment variables" on
page 3-4 for details.
Figure 3-37 Viewing a database script file
xedit window description
The xedit window comprises three main areas:

• Toolbars
• File information areas
• File display area
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.
3-78 68P02900W22-Q
09-Sep-2004
System Information: DataGen Generating a database script file
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.
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
The following procedure describes how to define a text editor to view MMI scripts or compilation logs
other than the standard editors.
When adding a new editor, verify that the editor runs on the system processor. This can be done
by entering the editor name from the command line and ensuring that it launches correctly.
1. Log on to the DataGen processor as user root.
2. Copy the selected editor to the /usr/bin directory using the following commands:
cp <text_editor> /usr/bin
Where: is:
text_editor 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>
4. If all users wish 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: is:
text editor the name of the text editor
68P02900W22-Q 3-79
09-Sep-2004
If only specific users wish to use the editor, edit the .cshrc in the user’s home
directory.
For example, setenv DG_EDITOR vi. Therefore, when the script file is invoked from the
Edit menu, it is displayed with the vi editor, refer to Figure 3-38.
Figure 3-38 Viewing an MMI script with vi
3-80 68P02900W22-Q
09-Sep-2004
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.
Upgrader
The Upgrader is a window-based tool which is invoked by selecting the UPG button from the DataGen
main menu.
68P02900W22-Q 3-81
09-Sep-2004
Viewing and editing DataGen files Chapter 3: Operating DataGen
The Upgrader creates a new 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.
If any parameters in the BSS area are to be changed prior to the upgrade they should be done
by altering the MCDF files. Refer to "Using the Generic Table Editor (GTE)" on page
3-94 for details.
3-82 68P02900W22-Q
09-Sep-2004
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-39) from the Service window, either select the Table
Control option from the Services menu or click the Table Controller button.
Figure 3-39 Partial view of typical Table Controller display
68P02900W22-Q 3-83
09-Sep-2004
Using the Table Controller Chapter 3: Operating DataGen
Table Controller functions
The Table Controller has two functions:

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

• Menu bar
• Command buttons
• File select buttons
• File status display
Menu bar
The menu bar provides the following options to manipulate DataGen input files as described in Table 3-5
below:
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 Files Clears all file types in the Table Controller window.
Command buttons
The command buttons are used to perform File, Validate, Insert, Export and Report functions on the
files imported into the Table Controller.
3-84 68P02900W22-Q
09-Sep-2004
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.
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 appears 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. Figure 3-41 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.
For more detailed information, refer to Chapter 6 - MCDF tables.
68P02900W22-Q 3-85
09-Sep-2004
• BSS (bss) - This table is at the top of the MCDF hierarchy and contains BSS specific
information.
• SITE (bts) - This table contains specific information regarding each site in the BSS area.
• Hardware (hw) - This 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, noting the site, cabinet, cage and slot in which the device resides.
The cabinets and cages are not explicitly noted in the table; further information is
included within the details of the cards.
• Cabinet (cab) - This (optional) table contains information about all the non-default type
cabinets throughout the BSS area.
• Generics (gene) - This 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 may 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 via the Generics Table.
• Timer (time) - 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 may be overridden for a site or cell by values in the Specifics table.
• Circuit (acct) - This table contains all MTL, LMTL and OML signalling links. It also contains
the terrestrial circuits to time slots at the BSC for radio traffic channels.
• Channel (chan) - This table is only required for Remote Transcoders and contains the OML
and MTL signalling 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 detailed in the Hardware table.
• Link (link) - This 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 detailed in the Hardware table.
• Modify Value (modv) - This table details all the modify_value commands related to
MMS/LCF device functions within the area.
• PATHs (path) - This table details all the paths within the BSS area (providing signalling 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-86 68P02900W22-Q
09-Sep-2004
• LAPD (lapd) - This table 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.
• Cell (cell) - This table details all the cells across the OMC or network and also the external
neighbours used by the specified cells. The optional fields in this table contain information
which override the defaults specified in the Generics table.
• RTF (rtf) - This table contains details of the RTFs contained in the BSS area.
• DRI (dri) - This 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) - This 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.
• 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.
Elements that can exist in the Cell table are not shown in the Specifics table.
• Neighbour (ngbr) - This 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) - This 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) - This 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 a NS-VCI and DLCI to a specific GBL.
68P02900W22-Q 3-87
09-Sep-2004
• {4322} ACS (acs) - The Active Codec Set (ACS) table is used to specify the parameters for
any chg_acs_params commands.
• {3723} Hop (hop) - The Hop table is used to specify the parameters of the chg_hop_params
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.
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 1.6.0.0 MCDF tables.
Warning messages may appear during the Export process; these can be safely ignored as the
Export will continue successfully.
To create MCDF files, perform the following steps:
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 have been exported, click the OK button.
Each file, when correctly exported, is indicated by a check mark in the File column.
3-88 68P02900W22-Q
09-Sep-2004
File validation procedure

After the files have been 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 steps:

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 "Administration tasks" on page 3-11 for details.
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 have been validated, click OK.
Each correctly validated file is indicated by a check mark in the File column.
File insertion procedure

After successful validation, the files must be inserted back into the Informix database. To insert the files,
perform the following steps:
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 "Administration tasks" on page 3-11 for details.
2. In the Table Controller window, choose Select All Files from the Select menu.
68P02900W22-Q 3-89
09-Sep-2004
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.
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 new 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 input files also means that a file can only be validated if all its dependent files have
been validated and inserted or are currently selected.
MCDF table editing
After the MCDF files have been created from the Informix database, they can be edited using the Generic
Table Editor (GTE). The following procedure uses as an example of table editing a Generics table, which
requires a change to the Generics parameter ber_loss_daily.
Table editing procedure - example

To edit an MCDF table, perform the following steps:
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-40.
3. Highlight the data field containing the value for ber_loss_daily.
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 (*).
3-90 68P02900W22-Q
09-Sep-2004
6. In the Table Controller window, click the Insert button.

The edited value is automatically validated before being inserted back into the database and a
message window is displayed, showing the progress of the Insert function.
Figure 3-40 Generics table
7. Click OK in the message window, and a check mark is displayed in the relevant Validate
and Insert columns.
8. Select the Generics file select button. A Report window displays the message that the
ber_loss_daily value was successfully updated in the database.
68P02900W22-Q 3-91
09-Sep-2004
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 has been 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
problems as they occur.
File status icons
The File Status icons on the Table Controller window are defined as follows (refer to Figure 3-41):
3-92 68P02900W22-Q
09-Sep-2004
Figure 3-41 File status icons
$"

#

&

& & & &

&

$ $
& & &

#

#

& &

& & & &

& !

&

"

"
"

"
"

& %
%
& &

68P02900W22-Q 3-93
09-Sep-2004
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-6 describes the File menu options.
Table 3-6 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-94 68P02900W22-Q
09-Sep-2004
System Information: DataGen Using the Generic Table Editor (GTE)
New option
To create a new (empty) MCDF input file, use the following procedure:
In the MCDF input (.mcd) file, select New from File menu. A New message window is displayed as
in Figure 3-42.
Figure 3-42 New MCDF input file message
Click OK to create a new (empty) MCDF input file.
Open option
Selecting the Open option from the File menu in the MCDF input file window displays an Open File window
as shown in Figure 3-43.
Figure 3-43 MCDF Input File - Open option
68P02900W22-Q 3-95
09-Sep-2004
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 * may be used to display ALL files in a directory.
• Directories
This scrolled list box displays directories and sub-directories 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, OLM On-Line help is available via the OLM GUI’
Store in DDS option

After editing an MCDF Input file, perform the following steps to store the file in the DataGen Directory
Structure (DDS):
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-96 68P02900W22-Q
09-Sep-2004
Save As option
Figure 3-44 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-44 Save To File window
Print Setup option

Figure 3-45 shows the Printer Setup window which is displayed when Print Setup is selected from the
File menu.
68P02900W22-Q 3-97
09-Sep-2004
The default page size is A4.
Figure 3-45 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-7, Table 3-8 and Table 3-9:
Table 3-7 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.
3-98 68P02900W22-Q
09-Sep-2004
Table 3-8 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.
Table 3-9 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:’For DataGen Help please
refer to the DataGen manual supplied, OLM On-Line help is
available via the OLM GUI’ .
Print option
The Print Table window is displayed when the Print option is selected from the File menu.
Figure 3-46 Print Table window
The print command selects the appropriate command for postscript or text only printer as in
Figure 3-46. If no printer is set up, then none is displayed in the printer list.
68P02900W22-Q 3-99
09-Sep-2004
The Print Table window allows the user to specify printer output parameters. This window has:
• Two option buttons allowing 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.
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, OLM On-Line help is available via the OLM GUI’.
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-10 describes the Edit menu options.
Before Copying and Pasting cells, create the requisite number of columns and/or rows needed
to contain the data.
3-100 68P02900W22-Q
09-Sep-2004
Table 3-10 Edit menu options
Select To
Cut Cut the contents of the currently selected cell(s) with the data being retained in
a buffer. However, subsequent cut operations will overwrite the contents of the
buffer. The cut cells are left empty.
Copy Copy the contents of the currently selected cell(s) into a buffer.
Paste Copy the contents of the buffer into the currently selected cell(s).
Clear Delete the contents of the currently selected cell(s). Note that 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.
There is a single buffer for Cut/Copy operations. Only the last Cut/Copy operation is retained
in the buffer.
68P02900W22-Q 3-101
09-Sep-2004
Fill Cells window
Figure 3-47 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-47 Fill Cells window
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-11).
• Four option buttons in a Calculate area (refer to Table 3-12).
• Three action buttons (refer to Table 3-13).
Table 3-11 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.
3-102 68P02900W22-Q
09-Sep-2004
Table 3-12 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-13 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: ’For DataGen Help please refer to
the DataGen manual supplied, OLM On-Line help is available
via the OLM GUI’.
Procedure for filling cells

To modify a MCDF input file using the Fill Cells window, perform the following steps:
1. Highlight the first cell to be filled.
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,
Start and End for example.
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.
68P02900W22-Q 3-103
09-Sep-2004
Format menu
The Format menu enables the user to perform general search and replace operations. Table 3-14 shows the
definitions of the Format menu options.
Table 3-14 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.
Find option
Enter the string to search for and select the appropriate search criteria (Exact match or Case sensitive) for the
search. Figure 3-48 shows the Format Find window.
Figure 3-48 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-15 and Table 3-16 describe the Enable buttons and the Action buttons.
3-104 68P02900W22-Q
09-Sep-2004
Table 3-15 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-16 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.
via the OLM GUI’.
Goto option
Figure 3-49 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-49 Goto Cell window
The Goto Cell window has:

• Two data fields (refer to Table 3-17)
• Three action buttons (refer to Table 3-18)
68P02900W22-Q 3-105
09-Sep-2004
Table 3-17 Goto Cell - data fields
Field Enter
Column Column number
Row Row number
Table 3-18 Goto Cell - action buttons
Select To
OK Confirm the displayed parameters and close the Goto Cell window
Cancel Cancel the operation and close the Fill Cell window.
via the 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-50.
Figure 3-50 Replace window
The Replace window has:

• Two data fields (refer to Table 3-19)
• Two enable buttons (refer to Table 3-20)
• Three option buttons (refer to Table 3-21)
• Three action buttons (refer to Table 3-22)
3-106 68P02900W22-Q
09-Sep-2004
Table 3-19 Replace window - data fields
Field Enter
Search for The specific character string to search for.
Replace with The replacement character string.
Table 3-20 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-21 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-22 Replace window - actions
Select To
OK Confirm the displayed parameters and close the Replace window.
Cancel Cancel the operation and close the Replace window.
via the OLM GUI’.
Sort option
The contents of some tables can be sorted. If a table cannot be sorted, this option is greyed 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 do this.
The Unlock button enables the user to unlock a table and change the locked values. The user is presented with
a warning of the effects of this action.
68P02900W22-Q 3-107
09-Sep-2004
MCDF key equivalents
Table 3-23 describes the key equivalents that are available when working on MCDF tables.
Table 3-23 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-108 68P02900W22-Q
09-Sep-2004
System Information: DataGen Using the Topology Viewer
Using the Topology Viewer

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to the Topology Viewer
Selecting the Topology option causes the DataGen GUI to core if the GMS licence
(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 an Exit option only.
68P02900W22-Q 3-109
09-Sep-2004
Using the Topology Viewer Chapter 3: Operating DataGen
Invoking the Topology Viewer
To display the Topology Viewer (as in Figure 3-51), either select Topology from the Services menu or
click the Topology icon on the Services window.
Figure 3-51 Topology Viewer
3-110 68P02900W22-Q
09-Sep-2004
Using the Topology Viewer
Use the buttons on the menu bar shown in Figure 3-52 to access the topology viewer options.
Figure 3-52 Topology Viewer menu bar
The topology viewer options are described in greater detail below.
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.
68P02900W22-Q 3-111
09-Sep-2004
To display a cage configuration, perform the following steps:

1. Click the Cage Hardware Configuration button on the Topology Viewer window. Refer to
Figure 3-52.
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-53.
4. A Cage Description window is displayed as shown in Figure 3-54.
Figure 3-53 The Cage Number window
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 required, this main section can be cut and printed, enabling users to produce 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.
3-112 68P02900W22-Q
09-Sep-2004
Selecting Exit from the File menu closes the window.
Figure 3-54 The Cage Description window
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-62.
68P02900W22-Q 3-113
09-Sep-2004
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 already
exists, a backup of the original file will be 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.
3-114 68P02900W22-Q
09-Sep-2004
System Information: DataGen Generating a hardware report
Generating a hardware report

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of hardware reports
Users 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 steps:

1. Open the Service window (refer to "Opening a BSS area" on page 3-38 for details).
2. From the Service window (refer to Figure 3-30), select Generate Hardware Report from
the Services menu.
There must be data in the BSS area. Otherwise, the Generate Hardware Report
option will not be available.
3. The message Generating Hardware Report for Base Station System is displayed in a status
window. When complete, a confirmation window is displayed. Click OK to continue.
68P02900W22-Q 3-115
09-Sep-2004
Generating a hardware report Chapter 3: Operating DataGen
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-55. Refer to
"Administration tasks" on page 3-11 for details on how to define a default editor.
Figure 3-55 Viewing a hardware report
5. Close the report by using the appropriate command for the text editor in use.
3-116 68P02900W22-Q
09-Sep-2004
System Information: DataGen Converting a database script file to a CM database object file
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 has been done, the Database Script
File can be downloaded to the BSS via 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
The Binary Object Compiler is used by DataGen to convert a script file into a CM database object. If the
software version is 1.6.0.0, then the CM database object is automatically compressed. As a secondary
function of compiling the object, the compiler also validates the database.
As a requirement for running the binary object compiler, the user must have installed 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 Window menu, or by clicking the Compile
icon shown in Figure 3-56.
68P02900W22-Q 3-117
09-Sep-2004
Converting a database script file to a CM database object file Chapter 3: Operating DataGen
Figure 3-56 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 via the MMI Script Generate command does not update the Informix database, as it
is in an output file directory.
3-118 68P02900W22-Q
09-Sep-2004
System Information: DataGen Converting a database script file to a CM database object file
The Binary Object Compiler window has two data fields which display the BSS Area information 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
From GSR4 all binary object files (.002) are compressed. Refer to Command
Line tools, Compress /uncompress 16xx Binary object files for details on how
to uncompress files.
To activate the compiler, click the Compile button or select the Compile option from the File menu.
68P02900W22-Q 3-119
09-Sep-2004
Exporting object files to the OMC Chapter 3: Operating DataGen
Exporting object files to the OMC

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of exporting object files
After a binary object has been 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.
For more information about the requirements for this type of operation,
refer to DataGen-OMC Integration in Software Release Notes: DataGen
(68P02900W76).
3-120 68P02900W22-Q
09-Sep-2004
System Information: DataGen Exporting object files to the OMC
Exporting multiple binary object files
To export multiple binary object files to the OMC, perform the following steps:
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-11, customizing parameters for details on
how to define a path to an export directory.
2. From the Service window (refer to Figure 3-29) within each area, select Export 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>
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>
The setenv COUNTRY and COUNTRY_CODE variables must 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.
68P02900W22-Q 3-121
09-Sep-2004
Exporting object files to the OMC Chapter 3: Operating DataGen
Exporting a single binary object file
To export one object file that has been created via the DataGen GUI to the OMC, perform the following steps:
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: is:
n replaced by the configuration
number.
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 one 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.
source options.
4. Select option 2 (DataGen), then input the requested information.
the specified BSS Area name.
The setenv COUNTRY and COUNTRY_CODE variables must 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.
3-122 68P02900W22-Q
09-Sep-2004
System Information: DataGen Exporting object files to the OMC
Exporting OLM binary object files to the OMC
To export multiple binary object files to the OMC from the Offline MIB, perform the following steps:
1. At the OMC, invoke Utilities - OMC Database Utility.
2. Select the Load Database option.

source options.
3. Select option 3 (Off-Line MIB), then input the requested information.
the specified BSS Area name.
For example:
/usr/omc/ne_data/dbroot/databases/<BSS Area Name>/<db_load name>
68P02900W22-Q 3-123
09-Sep-2004
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 3-1).
Two different BSS Areas are chosen and a comparison of both started. A viewable report is generated in
which sites common to both areas are listed. Differences between the two BSS Areas for each site are also
listed. In addition, the report indicates where no differences between 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-57.
Figure 3-57 Difference Reporter window
The Difference Reporter window displays the details of two BSS areas which may be selected for comparison
using the BSS Area Details window.
3-124 68P02900W22-Q
09-Sep-2004
System Information: DataGen Difference Reporter
Using the Difference Reporter window

The Difference Reporter main window has two sets of four user input areas labelled:
• Country
• BSS Name
• Version
• Config
The action buttons on the Difference Reporter window may be 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 on the Difference Reporter
window. The Select BSS Area Details window is then displayed. Refer to Figure 3-58.
Figure 3-58 Select BSS Area Details window
Note that when the window is first displayed, the BSS Name, Software Version, and Config Version list boxes
are blank. Only the Country Name list box contains a list of countries.
68P02900W22-Q 3-125
09-Sep-2004
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 may 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 may be used as follows:
Use To
Done Enter the selected details into the Difference Reporter window for BSS Area 1
and Area 2.
Cancel Cancel the operation and close the window.
3-126 68P02900W22-Q
09-Sep-2004
System Information: DataGen Difference Reporter
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-59.
Figure 3-59 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 may be used as follows:
Use To
View Report Display an Information window.
Close Close the Information window.
68P02900W22-Q 3-127
09-Sep-2004
Difference Reporter Report window
The results of the Difference Reporter process are displayed in a Report window as shown in Figure 3-60.
Figure 3-60 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 may be used to view different parts of a report.
3-128 68P02900W22-Q
09-Sep-2004
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 3-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.6.7.0 to 1.7.4.0
• 1.6.7.0 to 1.7.6.0
• 1.7.4.0 to 1.7.6.0
Refer to Software Release Notes: DataGen (68P02900W76) for more information about 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-61. This allows the user to select the BSS Area characteristics to be upgraded. The Target Version
is entered automatically by DataGen.
68P02900W22-Q 3-129
09-Sep-2004
Upgrader Chapter 3: Operating DataGen
To change parameters in the BSS area prior to the upgrade, modify the MCDF files. Refer to
"Using the Generic Table Editor (GTE)" on page 3-94 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.
Figure 3-61 Upgrade BSS Area window
The Upgrade BSS Area window has:

• Six list boxes (refer to Table 3-24)
• Two action buttons (refer to Table 3-25)
Table 3-24 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 No. Display a list of Configuration numbers for the software versions.
Target Version Display the available target versions automatically.
Target Config. Display a list of target Configuration numbers.
Table 3-25 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.
3-130 68P02900W22-Q
09-Sep-2004
Area Comment field

By default, the area comment field contains the following information:
Copied from <BSS Area> <Configuration NO>
Where: is:
BSS area the name of the original BSS area.
Configuration No the configuration number of the
original BSS area.
Upgrade BSS Area
To upgrade a BSS Area, perform the following steps:

1. Select the UPG from the DataGen Main menu (refer to Figure 3-1). This displays the Upgrade
BSS Area window (refer to Figure 3-61).
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 displays 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.
To overwrite an existing configuration, select the number from the Target

Config. list.
68P02900W22-Q 3-131
09-Sep-2004
7. If the information displayed in the list box data fields is correct, click Upgrade.
If the BSS area is locked by another user, an information window is displayed as shown in
Figure 3-62. If this message is not displayed, proceed to Step 9.
Figure 3-62 Locked information window
8. Click OK to override the lock or Cancel to return to the Upgrade BSS Area window.
Information on the user holding the lock may be found in the DataGen.log file.
A Status window is displayed as shown in Figure 3-63.
Figure 3-63 Successful upgrade Status window
The following message is displayed in the Status window if the upgrade was successful:
3-132 68P02900W22-Q
09-Sep-2004
REPORT :- Upgrade completed successfully.
REPORT :- Starting gcmd for <Country:BSS_Area:Configuration_No>.
REPORT :- Gcmd completed without error.
Wait until Gcmd has completed before closing the window.
9. Click Close to return to the Upgrade BSS Area window when Gcmd has 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 following section Resolving upgrade problems 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 Upgrade BSS Area and carry
out Step 3 to Step 9.
Resolving upgrade problems
During the upgrade process, problems may be identified with the BSS area that prevent the success of the
upgrade. The Status window identifies any problems found.
Depending on the nature of the problem(s), modifications may be made in one of two ways:
• Modify MCDF files
• Modify MMI scripts
68P02900W22-Q 3-133
09-Sep-2004
To solve the problem(s), use the following procedures:

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 3-1).
Wait until Gcmd has completed before closing the window.
Modify MCDF files

Use the following steps to modify the MCDF files:
1. Open the target BSS area from the DataGen main menu. Refer to "Opening a BSS area" on
page 3-38, 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-83 for 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-76 for 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-117 for details.
3-134 68P02900W22-Q
09-Sep-2004
Modify MMI script

Use the following steps to modify the MMI script:
1. Open the target BSS area from the DataGen main menu. Refer to "Opening a BSS area"
on page 3-38 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-76 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-117
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-11 for more details. From the Service
window, select File - Export Object.
5. From the Service window, select File - Exit.
6. Create a new BSS area and overwrite the existing configuration number. Refer to "Creating a
new BSS area" on page 3-34 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-62 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-71 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, see Technical Description: BSS Implementation (68P02901W36).
68P02900W22-Q 3-135
09-Sep-2004
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 may be 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 GSR7 version 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.
A default BSS Area name is derived from the binary object name minus the .002
extension. For example, BSS12.002 will become BSS area BSS12. It is advisable
to use meaningful binary names.
3-136 68P02900W22-Q
09-Sep-2004
System Information: DataGen Batch processing of binary object files
Revgen multiple binary object files
To Revgen multiple binary object files, carry out the following procedure:
1. Start DataGen from an Xterm window and select BATCH
from the DataGen main menu, (refer to Figure 3-1).
The Batch Tool window is displayed.
2. Select the Revgen option (refer to Figure 3-64).
Figure 3-64 Batch Tool window with Revgen selected
3. To export the Revgened areas automatically, click Export MCDF Files; otherwise proceed to
Step 4.
4. To copy the Revgened areas automatically, click Copy Area; otherwise 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.
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 Network Expansion - Defining environment variables for details.
6. Click OK.
68P02900W22-Q 3-137
09-Sep-2004
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.
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-65. Click OK to continue.
Figure 3-65 Revgen batch confirmation window
If all the essential fields have not been completed, an error window is displayed
stating: All fields have not been filled in. Click OK to return to the Batch Tools
window.
9. The Batch monitor window is displayed as Figure 3-66. The Batch window may be left open
to monitor the batch processing.
3-138 68P02900W22-Q
09-Sep-2004
Figure 3-66 Revgen Batch monitor window
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.
Upgrade multiple binary object files
To upgrade multiple binary object files carry out the following procedure:
1. Refer to the earlier procedure Revgen multiple binary object files and repeat Step 1. This
displays the Batch Tool window (refer to Figure 3-64).
2. Select the Upgrade option.
3. To export the upgraded areas automatically, click Export MCDF Files; otherwise proceed to
Step 4.
4. To copy the upgraded areas automatically, click Copy Area; otherwise proceed to Step 5.
68P02900W22-Q 3-139
09-Sep-2004
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.
If files other than binary object files exist in the directory, then
an error message is generated in the Batch monitoring window.
A default import path can be defined. Refer to Network Expansion - Defining
environment variables 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).
All the binary object files in the directory must be the same software version
for the upgrade to be successful.
8. Select the target version to upgrade to from the Target Version list.
9. Enter the starting configuration number in the Start Config: field and click Execute.
To obtain a configuration number automatically, do not enter a number and

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-62, Edit menu for details.
3-140 68P02900W22-Q
09-Sep-2004
Compile multiple MMI scripts
To compile multiple MMI scripts, carry out the following procedure:

1. Refer to the procedure Revgen multiple binary object files and repeat Step 1. This displays
the Batch Tool window (refer to Figure 3-64).
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.
If files other than script files (ASCII text) exist in the directory, then
a warning message is generated in the Batch monitoring window.
A default import path may be defined. Refer to Network Expansion - Defining
environment variables for details.
4. Click OK.
All script files must be the same software version and the correct compiler version
must be selected, otherwise errors will be generated.
68P02900W22-Q 3-141
09-Sep-2004
7. Click Execute. A confirmation window is displayed stating:

Compiling ALL files from selection:
/fanned/user43/users/mcdermjo/dev/scripts/1600c/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-67. This batch window may be
left open to monitor the batch processing.
Figure 3-67 Compile Batch monitor window
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.
3-142 68P02900W22-Q
09-Sep-2004
If any of the scripts fail to compile, then only a report file is generated. This may be used
to identify the problem
68P02900W22-Q 3-143
09-Sep-2004
3-144 68P02900W22-Q
09-Sep-2004
Chapter
4
Operating the Offline MIB
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02900W22-Q 4-1
09-Sep-2004
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
only possible to create a binary file by downloading an ASCII format script file to a BSS in SYSGEN mode.
Prior to GSR4 it was possible, using DataGen, to modify a single BSS binary file via MCDF tables or to
modify MMI scripts. Currently, DataGen allows the user to modify and carry out Radio Frequency (RF)
planning on multiple BSS binary files via the Offline MIB (OLM) which has a graphical user interface (GUI).
Users can only run one Offline MIB at a time. However, multiple GUIs for the same MIB may 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.
Parameters such as circuits, channels, statistics (enabling/disabling/thresholds) and time slot

reservations may not be modified via the OLM GUI.
Task list prior to 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 Software Release Notes: DataGen (68P02900W76).
• Upgrade function is carried out from the front panel DataGen window, not from the OLM GUI.
Refer to Upgrader in Chapter 3, Operating DataGen for details.
• Circuits, channels, statistics (enabling/disabling/thresholds), time slot reservations must be

modified via MCDF tables or MMI scripts. The scripts are compiled to create BSS binary
object files. Refer to Chapter 3, Operating DataGen for details.
4-2 68P02900W22-Q
09-Sep-2004
System Information: DataGen Introduction to the Offline MIB
Task list
The following lists in sequence the procedures which are normally performed using the OLM GUI:
• Start OLM from DataGen front panel.
• Create a network configuration.
• From the Navigation Tree of the OLM, import BSS binary files from DataGen into the network.
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 BSSs via the Navigation Tree and Detail Views.
• Carry out CellXchange and implement 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 features
To carry out additional functions such as importing Binary files from tape into the OLM directory (ReAlign
Network), refer to this section.
These functions are not routine functions and should only be carried out by the administrator or
creator of the Offline MIB network.
68P02900W22-Q 4-3
09-Sep-2004
Introduction to the Offline MIB 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 Reinitialise 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 the OLM
If problems are encountered when operating the Offline MIB, refer to this section 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).
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-40
for details on this procedure.
4-4 68P02900W22-Q
09-Sep-2004
System Information: DataGen Introduction to the Offline MIB
To enable the environment variable, use the following steps:

1. Edit the file olmProcConfig.csh by executing the following commands:
cd /usr/omc/current/config
vi olmProcConfig.csh
2. Insert the following line:

setenv OLM_VERIFY_DB_LOGGING ON
3. Save the file, then 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 as opposed to cmutil on the OMC. 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-Q 4-5
09-Sep-2004
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 how 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, click the OLM button (refer to DataGen - startup and
shutdown in the Chapter 3, Operating DataGen). A status message is displayed. Click OK to continue. The
OLM Network Configurations window then opens as shown in Figure 4-1.
Creating a network configuration
To create a new network configuration, perform the following steps:

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 displayed as in Figure 4-2.
Figure 4-1 OLM Network Configurations window
4-6 68P02900W22-Q
09-Sep-2004
System Information: DataGen Starting/creating a network configuration in the OLM
Figure 4-2 OLM Network configuration creation window
2. Enter the name of the new network configuration and press the Tab key.
The name may not start with a number or include a dash.
3. Enter the Mobile Country Code (MCC) and press the Tab key.
4. Enter the Mobile Network Code (MNC).
5. Click in Additional Information and enter a brief description of the network. It is not
mandatory to enter this information.
6. Select File - Create from the menu bar to create the network configuration.
68P02900W22-Q 4-7
09-Sep-2004
Starting/creating a network configuration in the OLM Chapter 4: Operating the Offline MIB
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.
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-32 for more details.
4-8 68P02900W22-Q
09-Sep-2004
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
Perform the following procedure to 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.
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.
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.
68P02900W22-Q 4-9
09-Sep-2004
Starting/exiting the OLM GUI Chapter 4: Operating the Offline MIB
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...
It is only possible to open 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).
Figure 4-4 Opening a network configuration - status window
4-10 68P02900W22-Q
09-Sep-2004
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-14 for more information about the OLM front panel.
Figure 4-5 Offline MIB front panel
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. Click OK to exit the GUI and return to the OLM Network Configurations window.
Figure 4-6 GUI exit - confirmation window
The message shown in Figure 4-6 is displayed if the network configuration GUI is opened
by more than one user.
68P02900W22-Q 4-11
09-Sep-2004
Starting/exiting the OLM GUI Chapter 4: Operating the Offline MIB
Shutting down the OLM
Use the following steps to exit and shut down the OLM:
The last user to exit the GUI shuts down the Offline MIB.
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.
4-12 68P02900W22-Q
09-Sep-2004
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 Error and warning window for a Network element
4. Click the Save NE button to save the Network element with the reported errors or go to Step 5.
If no more Network element errors are present, the OLM shuts down.
5. Click Don’t Save NE. If no more errors are present, the OLM shuts down.
This may result in inconsistencies between the Offline MIB and the specific NE
database within the network configuration directory.
68P02900W22-Q 4-13
09-Sep-2004
Front panel icons Chapter 4: Operating the Offline MIB
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 logged in operator 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-22 for details.
Administration
Select the Admin icon to view the Admin Options window. Administration is related to the audit functions,
all BSSs, RXCDRs must be audited before it is possible to alter their BSS Binary database files.
4-14 68P02900W22-Q
09-Sep-2004
System Information: DataGen Front panel icons
Find
Select the Find icon to invoke a search facility to locate a Network Entity, Site or Cell within a network.
Once the item has been 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.
A 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.
68P02900W22-Q 4-15
09-Sep-2004
Front panel icons Chapter 4: Operating the Offline MIB
Expert Offline MIB front panel
The OLM front panel may 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.
4-16 68P02900W22-Q
09-Sep-2004
System Information: DataGen Finding a Network Element or Site or Cell
Finding a Network Element or Site or Cell

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of Find function
The Find function is used to locate an NE, site or cell within the network. From the Offline MIB front panel,
select the Find icon to display a Find window. Search for NEs, sites or cells by entering completely or
partially the following details:
• NE Name
• Site Name
• Site Id
• Cell Name
• GSM Cell Id
Once the required item 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.
Locating an NE, Site or Cell
To locate an NE or Site or Cell, carry out the following procedure:
68P02900W22-Q 4-17
09-Sep-2004
Finding a Network Element or Site or Cell Chapter 4: Operating the Offline MIB
1. Select the Find button from the Offline MIB front panel. This displays the Find window
as in Figure 4-10.
Figure 4-10 Find window - selecting Find NE(s).
2. Enter the name of the NE, 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.
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.
4-18 68P02900W22-Q
09-Sep-2004
3. Click the Find NE(s) or 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 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.
If no text is entered, the search display all NEs or Sites or Cells in the network.
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 or Sites or Cells.
If no match is found, an information window is displayed stating:

No matching <object> was found.
Where <object> is the Network Element or Site or
Cell.
5. Click the required <object> in the Find Results box. The selection is highlighted in inverse text.
Where: is:
object Network Element
Site
Cell
6. For a Cell or Site, to obtain the parent view, click the Find Parent button; otherwise, skip to
Step 7.
68P02900W22-Q 4-19
09-Sep-2004
Finding a Network Element or Site or Cell Chapter 4: Operating the Offline MIB
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
Objects found
Search Criteria
Open
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.
Examples of using Find
Below are typical examples of where an operator might 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, use the following procedure:
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, 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.
4-20 68P02900W22-Q
09-Sep-2004
Finding a BSS parent of a Cell

To find the BSS parent of a Cell, use the following procedure:
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 is 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.
Finding a Cell with a LAC

To search for Cells with a particular Location Area Code (LAC), use the following procedure:
2. Enter the LAC in the third field of the GSM Cell Id.
3. Click Find Cell(s).

All Cell(s) with the specified LAC are displayed in the Find Results box.
Additional information about GSM cell ids can be found in Technical Description:
BSS Command Reference (68P02903W18) and Installation & Configuration: GSM
System Configuration (68P02901W17).
68P02900W22-Q 4-21
09-Sep-2004
Using the Navigation Tree: overview Chapter 4: Operating the Offline MIB
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-23.
• "Moving levels on a Navigation Tree" on page 4-25.
• "Creating a BSS/RXCDR from the Navigation Tree" on page 4-27.
Further information
Further information on using the Navigation Tree can be found in 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, Fault Mgt are not present in the menu bar.
4-22 68P02900W22-Q
09-Sep-2004
System Information: DataGen Opening and closing a Navigation Tree
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-12.
Figure 4-12 Navigation Tree window
68P02900W22-Q 4-23
09-Sep-2004
Opening and closing a Navigation Tree Chapter 4: Operating the Offline MIB
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-13.
Figure 4-13 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-66
and carry out Step 5 to Step 8.
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-50 for details.
Closing the Navigation Tree
To close a Navigation Tree:

Select File - Close from the menu bar.
4-24 68P02900W22-Q
09-Sep-2004
System Information: DataGen Moving levels on a Navigation Tree
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-23.
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 for
details on how to create BSSs or RXCDRs.
Procedure for moving levels
Assuming the Navigation Tree is in the form shown in Figure 4-14, use the following procedure for moving
levels:
To expand the Navigation Tree to the second level, click the folder icon next to the Network object.
The various class buttons are displayed.
To open the branch of a tree under a button, click the folder icon beside the button.
To close the branch of a tree under a button, click again on the folder icon beside the button.
68P02900W22-Q 4-25
09-Sep-2004
Moving levels on a Navigation Tree Chapter 4: Operating the Offline MIB
Figure 4-14 Navigation Tree window - showing panner
Panner region
Panner and porthole
When the Navigation Tree diagram becomes larger in size than the display area of the Navigation Tree
window (Figure 4-14), a panner/porthole arrangement is used to control what is being displayed. The tree is
displayed in the porthole region, and what is displayed is controlled by means of a panner.
To display different portions of the tree, move the panner. To do this:
Click and hold the left mouse button within the panner region, and move the mouse until the required area is
in view within the porthole. Then, release the mouse button.
4-26 68P02900W22-Q
09-Sep-2004
System Information: DataGen Creating a BSS/RXCDR from the Navigation Tree
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, proceed as follows:
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-15.
Figure 4-15 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.
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.
68P02900W22-Q 4-27
09-Sep-2004
Creating a BSS/RXCDR from the Navigation Tree Chapter 4: Operating the Offline MIB
7. An information window is displayed as shown in Figure 4-16. Click OK to continue.
8. Repeat Step 2 to Step 6 to import the required number of BSS binary files into the network
configuration.
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-30.
4-28 68P02900W22-Q
09-Sep-2004
System Information: DataGen Audit: overview
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-30 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 may be better to schedule the audit. Refer
to "Scheduling an audit" on page 4-51 for more information.
The preferred way of using audit is on a per NE basis. Networkwide 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 & Configuration: GSM System Configuration
(68P02901W17).
68P02900W22-Q 4-29
09-Sep-2004
Running an audit from the Navigation Tree Chapter 4: Operating the Offline MIB
Running an audit from the Navigation Tree

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to auditing from the Navigation Tree
It is possible to carry out an audit from the Navigation Tree and then, once the audit is complete, perform
the function Apply to OMC.
Audit from the Navigation Tree
To carry out an audit from the Navigation Tree, use the following procedure:
1. From the Navigation Tree (refer to Figure 4-12), click the network node.
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 finished.
5. Select the Audited Item (highlighted in inverse text).
4-30 68P02900W22-Q
09-Sep-2004
System Information: DataGen Running an audit from the Navigation Tree
6. Select File - Open from the menu bar or double-click on the highlighted row.
An Audit Inconsistency List window is displayed as in Figure 4-17.
Figure 4-17 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 of the procedure 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 are displayed.
68P02900W22-Q 4-31
09-Sep-2004
Modifying the network configuration from the Navigation Tree Chapter 4: Operating the Offline MIB
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 & Configuration: GSM System Configuration
(68P02901W17).
Creating or editing circuits, channels, statistics (enabling/disabling/threshold), and time slot reservations are
not supported from the Navigation Tree.
When required, use the Offline MIB pulldown menu to verify and save the new configuration.
From the Navigation Tree, saving a detailed view of a device will 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" on page 4-37 for details.
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 neighbour commands of the surrounding
cells automatically.
The procedures for carrying out these tasks are documented in Installation & Configuration: GSM System
Configuration (68P02901W17).
When required, use the Offline MIB pulldown menu to verify and save the new configuration.
From the Navigation Tree, saving a detailed view of a device will 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" on page 4-37 for details.
4-32 68P02900W22-Q
09-Sep-2004
System Information: DataGen CellXchange: overview
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 & Configuration: GSM System Configuration
(68P02901W17) for more information on performing CellXchange from the OLM.
68P02900W22-Q 4-33
09-Sep-2004
Overwrite a BSS/RXCDR binary object file Chapter 4: Operating the Offline MIB
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.
This feature overwrites the existing NEs and any changes made via the OLM are lost.
Procedure for overwriting
To overwrite an existing BSS Binary object file, use the following procedure:
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-23 for details.
3. Select the BSS or RXCDR from the Navigation Tree.
4. Select Offline MIB - Import NE Database from the menu bar.

The BSS Binary configurations window is displayed as in Figure 4-18.
Figure 4-18 BSS Binary configurations window
4-34 68P02900W22-Q
09-Sep-2004
System Information: DataGen Overwrite a BSS/RXCDR binary object file
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-19. Click OK to continue.
7. Click Cancel to close the selection 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-Q 4-35
09-Sep-2004
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, the information is saved in the OLM. To apply the
changes to the BSS databases (binary files) on disk, the following procedures must be carried out:
• Verify - this ensures that all the parameters are correct in accordance to 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 - this saves the BSS database file to disk and should be carried out regularly. Exiting
the OLM without saving, will result in changes being lost. This option is available under the
Offline MIB pull-down menu.
Do not deploy a saved BSS database without first carrying out a verify procedure.
It is possible to carry out in one step, a verify and save for the entire network 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 a verify and save operation can be applied.
By default all NEs are selected. It is possible to deselect NEs from the list before carrying out
a verify and save.
4-36 68P02900W22-Q
09-Sep-2004
System Information: DataGen Verify and save NE database
Verify and save NE database

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Verify a network element
If the environment variable OLM_VERIFY_DB_LOGGING is set to

ON, then a detailed error file will 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 a network element (NE), use the following procedure:
2. Select Config Mgt from the Front Panel to display the Navigation Tree. Refer to "Opening
and closing a Navigation Tree" on page 4-23 for details.
3. Select the NE from the Navigation Tree.
68P02900W22-Q 4-37
09-Sep-2004
Verify and save NE database Chapter 4: Operating the Offline MIB
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-20.
Figure 4-20 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-32 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.
Do not deploy a saved NE database without first carrying out a verify procedure.
Save a network element
To save a NE, first refer to the previous procedure 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.
4-38 68P02900W22-Q
09-Sep-2004
System Information: DataGen Verify and save NE database
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.
It is recommended to carry out this procedure at regular intervals.
68P02900W22-Q 4-39
09-Sep-2004
Verify and save network Chapter 4: Operating the Offline MIB
Verify and save network

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Verify network
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, use the following procedures:
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.
4-40 68P02900W22-Q
09-Sep-2004
System Information: DataGen Verify and save network
5. Click the button Verify NE Database on the Offline MIB Database Operations window.
The Offline MIB Verify Operation Monitor window is displayed as in Figure 4-22. 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-21 Offline MIB Database Operations window
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.
Figure 4-22 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
subsequent windows to return to the Navigation Tree window.
If the operation failed, select the Network Element. The selected NE is then highlighted.
68P02900W22-Q 4-41
09-Sep-2004
7. Click Show Errors/Warnings. This displays the Binary Database error and warnings window,
detailing the location and errors found as in Figure 4-23.
Figure 4-23 Binary Database error and warnings window
8. Click Close to return to the Offline MIB Verify Operation Monitor window.
Writing errors to a file

To write the errors to a file, use the following steps:
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.
4-42 68P02900W22-Q
09-Sep-2004
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-32.
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 Navigation Tree
window.
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 in progress, use the following procedure:
1. Refer to the Verify network procedure and follow Step 1 to Step 5. The Offline MIB Verify
Operation Monitor window is then displayed (refer to Figure 4-22).
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.
window.
68P02900W22-Q 4-43
09-Sep-2004
Saving a network
To save the entire network, use the following procedure:

1. Refer to the procedure Verify network and repeat Step 1 to Step 4. The Offline MIB Database
Operations window is displayed. Refer to Figure 4-21.
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-24. This contains
a list of all the NE names and the status of the saved NE(s).
Figure 4-24 Offline MIB Save Operation Monitor window
window.
Do not deploy a saved network without first carrying out a verify procedure.
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.
4-44 68P02900W22-Q
09-Sep-2004
To abort a save operation in progress, use the following procedure:

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-24.
2. Click the Abort button.

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.
For NEs that have been saved, aborting does not rollback the saves already
carried out.
window.
68P02900W22-Q 4-45
09-Sep-2004
Deleting a network configuration in the OLM Chapter 4: Operating the Offline MIB
Deleting a network configuration in the OLM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to deleting a network
It is recommended to archive and delete the network configuration, once the binary files are transferred to the
OMC. Refer to Chapter 3, Operating DataGenExporting object files to the OMC for details.
Delete network configuration
To delete a network configuration, use the following procedure:

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.
A network configuration can only be deleted by the owner or the system

administrator.
3. Click Delete. A confirmation window is displayed as shown in Figure 4-25.
Figure 4-25 Delete network Confirmation window
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-46 68P02900W22-Q
09-Sep-2004
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 being able to:
• Create a new BTS SITE by copying and pasting an existing BTS into a BSS configuration.
• Reparent a BTS within the same Intra-BSS or a different Inter-BSS.
• Delete 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.
• Review transaction logs and maintain 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 & Configuration: GSM System Configuration
(68P02901W17) for more information on performing Network Expansion from the OLM.
68P02900W22-Q 4-47
09-Sep-2004
Additional OLM features Chapter 4: Operating the Offline MIB
Additional OLM features

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
List of additional tasks
Additional tasks that may be carried out from the Offline MIB are:
• "Using the autoclose function" on page 4-49
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-50

It is possible to hierarchically delete a BSS or RXCDR from the Navigation Tree.
• "Scheduling an audit" on page 4-51

To carry out an audit takes a considerable amount of time and
where possible it may be better to schedule an audit.
• "Auditing logs" on page 4-57

Audit logs provide a method of monitoring audits and also
provide an audit history.
• "Audit log management" on page 4-62

Audit log management can be used to automatically delete logs
after a predefined period.
• "Reload NE database" on page 4-64

It is possible to roll back to the previous saved version of an NE
database.
• "Realign a network" on page 4-66

BSS binary files may be copied to the appropriate directory in the
OLM. The realign function will ensure 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-68

It is possible from the Network configuration window under the Admin options to compress
or uncompress an offline MIB network.
4-48 68P02900W22-Q
09-Sep-2004
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, then 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 might be open.
Prerequisite
A Navigation Tree must be open and displayed on the user terminal before setting autoclose. Refer to
"Opening and closing a Navigation Tree" on page 4-23 for details.
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.
The autoclose function is a menu option. When selected, the alternate state will be shown in the
menu window, that is, with Autoclose On selected. Autoclose Off will display in the View menu.
68P02900W22-Q 4-49
09-Sep-2004
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
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.
Procedure
To delete a BSS or RXCDR, use the following steps:

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-12).
A Confirmation window as shown in Figure 4-26 is displayed.
Figure 4-26 Deleting a BSS or RXCDR - Confirmation window
Since the OLM is performing a hierarchical delete of the NE, a considerable

delay may be experienced.
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.
An information window is displayed stating that the operation was completed successfully.
4. Click OK to return to the Navigation Tree.
4-50 68P02900W22-Q
09-Sep-2004
System Information: DataGen Scheduling an audit
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, follow these steps:

1. Select the Admin icon from the Front Panel to display the Admin Options window
(Figure 4-27).
Figure 4-27 Admin Options window
2. Select the Audit Scheduler option. The selection is highlighted in black.
68P02900W22-Q 4-51
09-Sep-2004
Scheduling an audit Chapter 4: Operating the Offline MIB
3. Click OK.
The Audit scheduler window, as shown in Figure 4-28, opens. This contains a list of all
scheduled audits, detailing their Name, Status, Start Time, End Time, Interval, Execute
Mode, Update Mode and Operator.
Figure 4-28 Audit Scheduler window
4. To create a new audit, select Edit - Create from the Audit Scheduler window. The auSchedule
Detailed View <create> window is displayed as in Figure 4-29.
5. To insert the elements to be audited, click the Scheduled Element button. The network
Navigation Tree window is displayed.
4-52 68P02900W22-Q
09-Sep-2004
6. Select the Network Element 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-25.
It is valid to select either BSS, RXCDR, SITE, PCU or the entire network
to be audited.
7. Double click on the NE to be audited.

The Navigation Tree window closes and the selected Network name is displayed in the
Scheduled Element Name field.
Figure 4-29 auSchedule Detailed View <create> window
68P02900W22-Q 4-53
09-Sep-2004
Entering schedule information

Enter schedule information in the Detailed View window as follows:
1. Only the Start Time field needs to be specified for Oneshot auditing. Click on the parameter
that requires changing. The selected parameter is highlighted in black.
The parameters are ordered as follows:
Month/Day/Year Hour:Minute:Second
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 on the Detailed View.
3. Once all the above information has been entered into the
Detailed View, select File - Create from the menu bar.
The new Scheduled Audit is then created and can be viewed in the Audit Scheduler window.
4. Close the Detailed View window by selecting File - Close from the menu bar.
5. Close the Audit Scheduler window by selecting File - Close from the menu bar.
4-54 68P02900W22-Q
09-Sep-2004
Modifying a scheduled audit
All the limitations that apply to auditing also apply when modifying a scheduled audit. For more information,
refer to the earlier procedure for Creating a scheduled audit.
To modify a scheduled audit, use the following procedure:
1. Open an Audit Scheduler window. The Audit Scheduler window is displayed as in Figure 4-30.
2. Select the audit to be modified. The selection is highlighted in black.
Figure 4-30 Audit Scheduler window
3. To open this audit for modification, select Edit - Modify from the Audit Scheduler window.
The auSchedule Detailed View window is displayed as in Figure 4-29.
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.
It is not possible to revert to a previous version after an edited version has been
saved.
5. When all the required fields have been 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.
68P02900W22-Q 4-55
09-Sep-2004
Deleting a scheduled audit
Expired Scheduled Audits must be deleted from time to time to avoid using excess memory.
To delete a scheduled audit, use the following procedure:
1. Refer to the earlier procedure for Creating a scheduled audit and follow Step 1 to Step 3.
The Audit Scheduler window is displayed as in Figure 4-30.
2. Select the audit to be deleted.
3. Select Edit - Delete from the Audit Scheduler window.

4. Click OK.
The Scheduled Audit closes and the message Element Deleted is displayed in the status bar.
4-56 68P02900W22-Q
09-Sep-2004
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, use the following steps:
1. Select the Admin icon on the Front Panel to display the Admin Options window (Figure 4-27).
It is also possible to view the audit logs from the Navigation Tree by selecting
Config Mgt - Audit Logs from the menu bar.
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.
68P02900W22-Q 4-57
09-Sep-2004
Auditing logs Chapter 4: Operating the Offline MIB
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-51), progress details are
displayed in the Audit log list.
To abort an audit in progress, use the following procedure:
1. Refer to the Viewing an audit log procedure and follow Step 1 to Step 2 to open the Audit
Logs window.
2. From the Audit Log list, select the audit to be aborted.
The Status of an audit in progress is displayed as Active in the Audit Log list.
3. Select Options - Abort from the menu bar.

A confirmation window is displayed as in Figure 4-32.
4-58 68P02900W22-Q
09-Sep-2004
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.
68P02900W22-Q 4-59
09-Sep-2004
Auditing logs Chapter 4: Operating the Offline MIB
Viewing an audit inconsistency report
To view an Audit Inconsistency report for a particular Scheduled Audit, use the following procedure:
1. Refer to the Viewing an audit log procedure and follow Step 1 to Step 2. The Audit Logs
window is displayed as in Figure 4-31.
2. From the Audit Log list, select the audit from which any inconsistencies should be viewed.
The selected audit is highlighted.
An Audit Inconsistency report is only completely valid 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-17), detailing all
elements where inconsistencies were found during the audit.
The following information is displayed for each reported inconsistency or error:
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.
4-60 68P02900W22-Q
09-Sep-2004
Column Identifies
Apply Status The status of an attempted update to the system to remove an
inconsistency, or indicates the error detected by the audit.
If an inconsistency is being reported and an Apply to OMC
or Apply to NE operation has been performed, this column
indicates the result of the operation. This can be Success or
Failure. If an apply operation has not been attempted, this
field is blank.
If an error is being reported, this column describes the error.
Warning for NE Apply The type of warning given when inconsistencies applied to a
network element fail.
Attribute Name The name of the attribute that is inconsistent, if applicable.
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.
4. Select File - Close from the menu bar to close the Audit Inconsistency report.
Deleting an audit log
To delete an audit log, use the following procedure:

1. Refer to the Viewing an audit log procedure and follow Step 1 to 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-Q 4-61
09-Sep-2004
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 may also be deleted manually. Refer to the procedure Deleting an audit log for more information.
Setting the delete period
The operator should set the number of days for retaining the audit log files, after which interval the OMC
automatically deletes the files. If set to zero all the audit logs, except the current one, are deleted.
4-62 68P02900W22-Q
09-Sep-2004
System Information: DataGen Audit log management
To set the delete period, use the following procedure:

1. Select the Admin icon on the Front Panel to open the Admin Options window as in Figure 4-27.
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
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
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-Q 4-63
09-Sep-2004
Reload NE database Chapter 4: Operating the Offline MIB
Reload NE database
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to reloading an NE database
If changes have been 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 may be carried out.
Procedure to reload an NE database
If multiple NEs are changed, for example if an RF import, Cell or neighbour propagation has been
carried out, then all the affected NEs must be included in the roll back.
4-64 68P02900W22-Q
09-Sep-2004
System Information: DataGen Reload NE database
To reload a previous saved version of an NE database, do the following:

1. Refer to the procedure "Verify and save NE database" on page 4-37 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
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 stating:
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 status of finished.
68P02900W22-Q 4-65
09-Sep-2004
Realign a network Chapter 4: Operating the Offline MIB
Realign a network
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to realigning a network
The realign function is a short-cut method of putting BSSs and RXCDRs into a network configuration.
Normally, this is done from the Navigation Tree. Refer to "Creating a BSS/RXCDR from the Navigation
Tree" on page 4-27 for details. However, it is possible to copy NE binary files from a tar tape or via 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 may apply (refer to Table 4-2):
Table 4-2 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
It is not possible to continue working on network when a realign is in progress.
Procedure for realigning a network
To realign a network, use the following procedure:

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-23 for details.
4-66 68P02900W22-Q
09-Sep-2004
System Information: DataGen Realign a network
4. Open an Xterm window and copy the BSS binary files to:
/usr/omc/DataGen/olm/<network configuration name>
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-30 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 pulldown menu. Refer to "Reload NE
database" on page 4-64Reload NE database for details.
68P02900W22-Q 4-67
09-Sep-2004
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 may be used when disk space is an issue.
It is better to archive and delete old network configurations when the binary files are transferred
to the OMC.
Compress procedure
To compress a network, use the following procedure:

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.
4-68 68P02900W22-Q
09-Sep-2004
System Information: DataGen Compress or uncompress an OLM network
3. Select Admin - Compress from the menu bar.

Figure 4-36 Compress from the OLM Network Configurations window
4. Click OK to continue or Cancel to abort.
Uncompress procedure
To uncompress a network without restarting the OLM from the DataGen front panel, use the following
procedure:
1. Refer to the Compress procedure and follow Step 1 to Step 2.
2. Select Admin - Uncompress from the menu bar.

3. Click OK to continue or Cancel to abort.
68P02900W22-Q 4-69
09-Sep-2004
Troubleshooting the OLM Chapter 4: Operating the Offline MIB
Troubleshooting the OLM

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to troubleshooting the OLM
If the OLM does not appear to be functioning normally, refer to the information in Table 4-3 to Table 4-7
which details errors that can occur and how to resolve them.
To investigate potential problems, carry out the following steps:
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-3 to Table 4-7 for information on error messages and the appropriate action
to take.
Error OLM fails to start
If the OLM fails to start, Table 4-3 shows the possible error messages that may appear and the appropriate
action to take.
4-70 68P02900W22-Q
09-Sep-2004
System Information: DataGen Troubleshooting the OLM
Table 4-3 OLM fails to start
Error/Warning Explanation Action

msgctl call failed with The maximum message size and Check using sysdef -i to
main message queuemsgget maximum bytes per queue is verify value. Put in original
call failed with main specified during the DataGen values. Reboot and open network.
message queue 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 BSS file is not specified in: and contact your local support
Binary file <BSS_Name /usr/omc/config/OLM.CNFG office.
is>.
All copies of the ported If there is a heavy load on the Edit OLM.CNFG file and
BSS software have system it may be necessary to increase the number for
not started up in the increase the start up time in NMASECM_WAIT_SECS
allotted time. /usr/omc/config/OLM.CNFG parameter. Exit and restart the
or OLM. Refer to the procedure
BSS binary file is corrupt. "Starting/exiting the OLM
GUI" on page 4-9.
Recompile to create a new BSS
binary file and replace the existing
one.
Open the network.
Failed fork to run The maximum number of Check using sysdef -i to
NmaseCm code. processes that can be run is verify value. Put in original value.
specified during the DataGen Reboot and open network.
install. This kernel parameter
should not be altered.
Problem accessing DataGen The administrator must grant the Log on as omcadmin. From the
INFORMIX database sql user connect permission. command line invoke DGAdmin
code -387: no connect by typing DGAdmin and enter
permission the following command tp -u
<username>
68P02900W22-Q 4-71
09-Sep-2004
Database errors
Table 4-4 shows the error messages that may appear and the appropriate action to take.
Table 4-4 Database Errors
Error/Warning Action
Invalid NE To correct the errors carry out the following:
failed to open database
1. Reinitialise the database. Refer to the procedure
<Network name> sql error
"Reinitialise database" on page 4-75.
<Number>
Network name is <Name> it 2. Audit the network. Refer to the procedure "Running an
should be <Network Name> audit from the Navigation Tree" on page 4-30
There is more than one
Network in this database
Rose message received from
an NE when only start up
messages expected
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. Refer
and in MIB do not have to "Reload NE database" on page 4-64 for details.
the 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.
Cont.
4-72 68P02900W22-Q
09-Sep-2004
Table 4-4 Database Errors (Continued)

NE %s is in MIB, not in Contact your local support office.
BSS Binary directory
NE %s is in BSS Binary Contact your local support office.
directory, not in MIB
General errors
Table 4-5 shows the error messages that may appear and the appropriate action to take.
Table 4-5 General operating errors
The number of Users in the To correct the errors carry out the following:
Network Configurations list
is set to non-zero even 1. Reset the number of users to zero. Refer to the procedure
though there is no OLM GUI Force shutdown OLM in this section.
open.
The GUI hangs 2. Audit the network. Refer to the procedure "Running an
audit from the Navigation Tree" on page 4-30
SMASE channel has been To correct the errors carry out the following:
deleted.
1. Force shutdown the OLM. Refer to the procedureForce
OlmOmcInit channel has been
shutdown OLM in this section.
deleted
Unable to read from IPC 2. Open the network. Refer to the procedure "Starting/exiting
channels the OLM GUI" on page 4-9
Specific operation fails
If a specific task fails, Table 4-6 shows the error messages that may appear and the appropriate action to take.
Table 4-6 Specific operation error
Fatal Off-Line MIB To correct the error carry out the following:
Operation Error
1. View the audit log. Refer to the procedure "Auditing
logs" on page 4-57.
2. Exit and restart the OLM. Refer to the procedure

"Starting/exiting the OLM GUI" on page 4-9
68P02900W22-Q 4-73
09-Sep-2004
Import errors
While importing NE binary files Table 4-7 shows the possible error that may occur and the appropriate
action to take.
Table 4-7 Importing NE software errors
Transaction timeout To correct the errors carry out the following:
Link OOS
• Revert to the previously saved version of the NE database.
Ported BSS S/W for <BSS Refer to the procedure "Reload NE database" on page
Name> has not started 4-64
or
msgsnd call failed for NE
<BSS Name>.
msgrcv call failed for msg • Exit and restart the OLM. Refer to the procedure
Q "Starting/exiting the OLM GUI" on page 4-9
msgget call failed with
key <number> for BSS <BSS
Name>.
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 behaving abnormally. This
function will shut down the Offline MIB and reset the number of users to zero for the network configuration.
Any changes that have been made 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.
4-74 68P02900W22-Q
09-Sep-2004
Force shutdown OLM procedure
To shut down the OLM and reset the number of users to zero for the network configuration, use the following
procedure:
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 message Database operation successfully completed is displayed in an
Information window.
5. Click OK.
The column Users in the Network configuration window is reset to zero for the network.
On opening the network, carry out an audit. Refer to "Running an audit from the
Navigation Tree" on page 4-30 for details.
Reinitialise database
The reinitialise 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.
68P02900W22-Q 4-75
09-Sep-2004
Only the person that created the network configuration or the system administrator can carry
out this task.
To reinitialise the network database, use the following procedure:
1. Refer to the earlier procedure Force shutdown OLM and follow Step 1 to Step 2.
The OLM Network Configurations window opens and the network is selected.
2. Select Admin - Reinitialise Database from the menu bar.

A confirmation window is displayed as in Figure 4-38.
Figure 4-38 Reinitialise 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.
On opening the network, it will be seen that all the information that was audited
has been 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-30 for details.
4-76 68P02900W22-Q
09-Sep-2004
Chapter
5
Command line tools
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02900W22-Q 5-1
09-Sep-2004
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) or can be accessed either from the GUI or the command line.
Table 5-1 shows the user tools available for command line operation:
5-2 68P02900W22-Q
09-Sep-2004
System Information: DataGen Overview of command line tools
Table 5-1 Command line tools
Command line tools

Command name Invoked with Use Command line or
GUI
Auto-compile MMI auto_compile Compile a number of Both
scripts MMI scripts
Auto-revgen binary files auto_revgen Revgen a number of Both
binary files
Auto-upgrade binary auto_upgrade Upgrade a number of Both
files binary files
Copy Area ca Copies a BSS area to a Both
new 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 Both
area
MCDF filters filter Export or import or Both
validate MCDF files.
MMI Command gcmd Generates BSS Both
Generator command file(s)
Dbaccess command dbaccess Optimise DataGen Command line
database
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
68P02900W22-Q 5-3
09-Sep-2004
Overview of command line tools Chapter 5: Command line tools
General information
Most command line tools require that DGAdmin be run before they can be invoked, using the following
command:
DGAdmin
The DGAdmin command sets the user environment for DataGen. DGAdmin sets system variables in the
current environment to allow DataGen tools to function correctly.
DGAdmin 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.
Prior to 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
5-4 68P02900W22-Q
09-Sep-2004
System Information: DataGen Copy Area (ca) command
Copy Area (ca) command

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Name
ca - copy 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.
68P02900W22-Q 5-5
09-Sep-2004
Copy Area (ca) command Chapter 5: Command line tools
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 number> Define a new configuration.
-title <new configuration title string> The comment entered when creating the BSS area.
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
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>
5-6 68P02900W22-Q
09-Sep-2004
System Information: DataGen Copy Area (ca) command
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"
The next free configuration number in Area 11 is used and, if Area 11 does not exist, it will be
created.
68P02900W22-Q 5-7
09-Sep-2004
MMI Combiner (combine) command Chapter 5: Command line tools
MMI Combiner (combine) command

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Name
combine - combine 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 a MMI script file, run the following command:
cd \<country>\<bss area>\<config no>\command combine

This generates an MMI script file called COMBINED
Each time a combined script is generated the original script is backed up with a Date and Time
stamp. For example, COMBINED.BACKUP072498123425.
5-8 68P02900W22-Q
09-Sep-2004
System Information: DataGen MMI Combiner (combine) command
Requirements
Run DGAdmin before executing the compile command.
68P02900W22-Q 5-9
09-Sep-2004
Compile MMI script (compile) command Chapter 5: Command line tools
Compile MMI script (compile) command

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Name
compile - compile 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.6.7.0 or 1.7.4.0 or 1.7.6.0)
filename name of script file to compile
Description
This utility allows a 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 how to use the compile command:
compile -C Austria -v 1.7.6.0 BSS_scr

This example produces two files on successful compilation:
• BSS_scr.002
• BSS_scr.rep
If the compilation fails, only the report file (.rep) is generated and this may be used to determine the error.
5-10 68P02900W22-Q
09-Sep-2004
System Information: DataGen Compile MMI script (compile) command
Requirements
Run DGAdmin before executing the compile command.
68P02900W22-Q 5-11
09-Sep-2004
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 to compile with.
<filename or *> Define a directory where the scripts reside or a single MMI script.
Requirements
Run DGAdmin before executing the auto_compile command.

5-12 68P02900W22-Q
09-Sep-2004
System Information: DataGen Auto-compile MMI script command
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.7.6.0 ~/scr_objs/1760x/*
This compiles all existing MMI scripts in the specified directory using the corresponding 1760 compiler. On
successful completion, the report files and binaries will 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.7.6.0 -c 0 /usr/omc/test/1760x/objects/*
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-Q 5-13
09-Sep-2004
Compress/uncompress 16xx binary object files Chapter 5: Command line tools
Compress/uncompress 16xx binary object files

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Name
cpdb -c - compress 1613, 1620 or 1650 binary object (.002) files.

cpdb -u - uncompress 1613, 1620 or 1650 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 16xx 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
or uncompressed binary object files.
Example
The following are two examples of how to use the compress and uncompress command:
5-14 68P02900W22-Q
09-Sep-2004
System Information: DataGen Compress/uncompress 16xx binary object files
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-Q 5-15
09-Sep-2004
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.
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 may 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-16 68P02900W22-Q
09-Sep-2004
System Information: DataGen Delete database object (del) command
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.
If the BSS area is deleted, the related files in the DDS are also deleted.
68P02900W22-Q 5-17
09-Sep-2004
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 may also be used to validate files.
5-18 68P02900W22-Q
09-Sep-2004
System Information: DataGen MCDF filter command
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 inserted or 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.
Table 5-6 Valid file names
FileName Table
bss BSS
site Site
cab Cabinet
hware Hardware
gene Generics
timer Timer
modv Modify Value
acct Circuits
Cont.
68P02900W22-Q 5-19
09-Sep-2004
MCDF filter command Chapter 5: Command line tools
Table 5-6 Valid file names (Continued)

FileName Table
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 Neighbours
thro Throttles
eas EAS
dgtr Daughters
pix PIX
ksw KSW
nsvc Nsvc
hop Hop
acs ACS
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. Refer to the MCDF BSS and RXCDR tables in Chapter 6, MCDF
tables for further details.
5-20 68P02900W22-Q
09-Sep-2004
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 a MMI script for Austria BSS Area10, configuration number 0.
68P02900W22-Q 5-21
09-Sep-2004
MMI command generator (gcmd) command Chapter 5: Command line tools
gcmd Austria:Area10:0:1
This example produces a MMI script for site 1 only in Austria BSS Area10, configuration number 0.
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-22 68P02900W22-Q
09-Sep-2004
System Information: DataGen Optimise DataGen database (dbaccess) command
Optimise DataGen database (dbaccess) command

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Name
dbaccess - optimise the DataGen database.
Synopsis
dbaccess db_dg clusters.sql
Description
In order to maximise free disk space, it is advisable to optimise the DataGen database. This can be performed
by running the script named clusters.sql.
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-Q 5-23
09-Sep-2004
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, or
• 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.
5-24 68P02900W22-Q
09-Sep-2004
System Information: DataGen Lock/unlock BSS area (lock_adm) command
Table 5-8 Command Line options (lock_adm command)
Option Description
<country name> The country name of the configuration.
<BSS area name> The BSS name of the configuration.
<config_no> The configuration number.
–who query about lock status.
–lock lock a configuration.
–unlock unlock a configuration.
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
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 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 in the following example:
68P02900W22-Q 5-25
09-Sep-2004
Lock/unlock BSS area (lock_adm) command Chapter 5: Command line tools
omcadmin kiran>DGAdmin lock_adm -area Austria:182188:0 -lock

DATAGEN DATABASE LOCK ADMINISTRATION TOOL
BSS Area is already locked
Area: Austria, 182188, 0
5-26 68P02900W22-Q
09-Sep-2004
System Information: DataGen Revgen command
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.
68P02900W22-Q 5-27
09-Sep-2004
Revgen command Chapter 5: Command line tools
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.
-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 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 number> The -r option takes a further parameter and identifies the reference
configuration number. This number identifies a similar BSS which
the revgen utility uses to look up 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.
5-28 68P02900W22-Q
09-Sep-2004
System Information: DataGen Revgen command
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.7.4.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.
If the DDS directory does not exist for the configuration, the command
will fail. 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.
68P02900W22-Q 5-29
09-Sep-2004
Auto-Revgen command Chapter 5: Command line tools
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 new
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.
5-30 68P02900W22-Q
09-Sep-2004
System Information: DataGen Auto-Revgen command
Table 5-10 Command line options (auto_revgen command)
Option Description
-m Specifies that MCDF tables, should be exported after Revgen
(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 to (optional).
-v <Version> The software version to Revgen the binaries to.
<filename or *> Defines a directory where the binary or binaries reside.
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.7.6.0 ~/option_object/1760x/*
This Revgens all existing binaries in the specified directory to the corresponding 1740 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.7.6.0 ~/option_object/1760x/*
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.
68P02900W22-Q 5-31
09-Sep-2004
Toggle permissions (tp) command Chapter 5: Command line tools
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 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.
5-32 68P02900W22-Q
09-Sep-2004
System Information: DataGen Toggle permissions (tp) command
Requirements
Run DGAdmin before executing the tp command.
68P02900W22-Q 5-33
09-Sep-2004
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 to.
-t <target Config > Target configuration number to upgrade to.
5-34 68P02900W22-Q
09-Sep-2004
System Information: DataGen Version upgrader (upg) command
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.
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.7.6.0 -t 5
Where: is:
Country UK
BSS area BSS area
Configuration No. 0 to version 1.7.6.0
Configuration No. 5
If the specified target configuration exists, the upgrade is aborted.
68P02900W22-Q 5-35
09-Sep-2004
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. The binary files must all be of the 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.
5-36 68P02900W22-Q
09-Sep-2004
System Information: DataGen Auto-upgrader command
Table 5-13 Command line options (auto_upgrade command)
Option Description
–m Specifies that MCDF tables, should be exported after revgen
(optional).
–d Specifies that a copy of the new area should be made after revgen
(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 to (optional).
–v <Version> The software version of the binary files.
–u <Upgrade Version> The software version to which the resultant areas should all be
upgraded to.
<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 will be 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.6.7.0 -u 1.7.6.0 ~/scr_objs/1670x/*
This Revgens all existing binaries in the specified directory to corresponding 1670 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 1670 area will then be upgraded to
1760.
68P02900W22-Q 5-37
09-Sep-2004
Auto-upgrader command Chapter 5: Command line tools
auto_upgrade -m -d -C Austria -c 25 -v 1.6.7.0 -u 1.7.6.0

~/scr_objs/1670x/*
This command Revgens all existing binaries as before. After each Revgen process, each area is upgraded
to 1760 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 will be selected.
5-38 68P02900W22-Q
09-Sep-2004
System Information: DataGen Country administration
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 enable 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.
The 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.
68P02900W22-Q 5-39
09-Sep-2004
Country administration Chapter 5: Command line tools
Invoking xcadm
To invoke the Country Administration tool, execute the following procedure:

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.
Figure 5-1 Country Admin in use confirmation window
Using the xcadm GUI
The xcadm GUI (Figure 5-2) is organised into three functional areas:
• Menu bar
• Data fields
• Action buttons
5-40 68P02900W22-Q
09-Sep-2004
Figure 5-2 The xcadm GUI
The menus
The menu bar enables the DataGen user to create, update, and edit Country and Network Administration
files as follows:
File menu
The following option is available:
• Exit
Use the Exit option 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.
Country and Network menu options may be greyed out, according to which
operations are permitted at the time.
68P02900W22-Q 5-41
09-Sep-2004
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.
For NEW users where no country.std file exists, select Generate from
the Country menu to automatically generate a country.std file in the
/omcadmin/dg/ADMIN/country 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.
5-42 68P02900W22-Q
09-Sep-2004
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.
68P02900W22-Q 5-43
09-Sep-2004
5-44 68P02900W22-Q
09-Sep-2004
Chapter
6
MCDF tables
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02900W22-Q 6-1
09-Sep-2004
Overview of MCDF tables Chapter 6: MCDF tables
Overview of MCDF tables

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Scope of MCDF tables
This specification details the format of each of the files within the MCDF file set for use in BSS versions
1.6.5.0 and beyond.
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.
Due to MCDF supporting BSS versions 1.6.5.0, 1.6.7.0, 1.7.4.0 and 1.7.6.0, it is important that users
adhere to all ranges defined in the subsequent tables. The ranges may change from one load to the next.
Refer to Technical Description: BSS Command Reference (68P02901W23) for a detailed

description of the parameters in the MCDF tables.
Refer to the appropriate DataGen manual Software Release Notes: DataGen (68P02900W76)
for enhancements specific to the software release installed.
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-Q
09-Sep-2004
System Information: DataGen Overview of MCDF tables
Figure 6-1 Non-collocated BSS hierarchy
BSS Table
EAS Table
KSW Table Site Table
Cabinet
Table
Hardware
Table
MMS Table Daughter

Table
PIX Table
Circuits Table Cell Table Timers Table Throttles

NSVC Table Table
Generics Neighbour
Table Links Table Stats Table Table
Specifics Algorithm
Paths Table Table Table
LAPD Table RTF Table KEY

MCDF Table
DRI Table
Optional Table
File dependency,
RTC Table predecessor must exist
File dependency
if predecessor exists.
68P02900W22-Q 6-3
09-Sep-2004
Overview of MCDF 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 Circuits Table Channel Stats Table Throttles

Table Table Table
Timers Table LAPD Table Links Table Specifics

Table
KEY
MCDF Table
Optional Table
File dependency,
predecessor must exist
File dependency
if predecessor exists.
6-4 68P02900W22-Q
09-Sep-2004
System Information: DataGen BSS table
BSS table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of BSS table
This table is 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 is a list file laid out as follows: <field name><field width><range><status>
Default filename bss.mcd
Table 6-1 BSS specific table
Field
Field Name Range Status
Width
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 ID 50 0 to 255 Mandatory
Used for element bss_id.
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
a RXCDR (see Site Type)
otherwise not used.
Used for element opc.
Cont.
68P02900W22-Q 6-5
09-Sep-2004
BSS table Chapter 6: MCDF tables
Table 6-1 BSS specific table (Continued)

Field
Width
MSC Name 50 Text Optional.
The name of the MSC the BSS is connected to.
SPC MSC 50 0 to 16777215 Mandatory if the BSS area is
not a RXCDR (see Site Type)
otherwise unused.
Used for element dpc.
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
a RXCDR (see 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.
A5 Encryption Order 50 0 to 7 for each Optional.
of the entered
fields, with a
maximum of 8
fields.
Cont.
6-6 68P02900W22-Q
09-Sep-2004
Table 6-1 BSS specific table (Continued)

Field
Width
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 Means the ciphering algorithms are in the order A5/5, A5/3,A5/1
1,2,3,4,5,6,7,0 Means the order 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).
Have BSS area (in SYSGEN mode) perform a dynamic reconfigure of GPROCs to CSFPs.
Frequency Types Allowed 50 1-15 Mandatory. Only applicable
from 1510.
Used for the frequency_type parameter of the freq_types_allowed command. This defines the valid
frequency types for the current BSS area.
For 1510 loads the valid frequency types are defined within Table 6-2 below:
PCS1900 was formerly known as DCS2000
68P02900W22-Q 6-7
09-Sep-2004
BSS table Chapter 6: MCDF tables
Table 6-2 Frequency Types Allowed
Frequency Type Numeric 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
Field Name Field Width Range Status

PCS1900 Frequency Blocks 50 A, B, C, D, E, Optional. (Only applicable from
F, ALL 1510).
(see note
below).
Used to define the valid frequency blocks for PCS1900. Valid blocks are detailed in Table 6-3 below:
Note: For a subset of blocks, a space character is required.
Table 6-3 Valid Frequency Blocks
Frequency Block Parameter Channels

ALL 512-810
A 512-585
D 587-610
B 612-685
E 687-710
F 712-735
C 737-810
6-8 68P02900W22-Q
09-Sep-2004
All entries into this field must be space separated, for example: the blocks allowed are A, B, D only, so the
user must type:
A B D
It is very important that the information is entered this way when a subset of frequency blocks is required.
68P02900W22-Q 6-9
09-Sep-2004
Site (BTS specific) table Chapter 6: MCDF tables
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-4).
Default filename bts.mcd
Table 6-4 BTS specific table

Site Name 50 Text Mandatory
The Unique Site Name.
Site Number 3 0 to 120 Mandatory
The Site Number within the BSS.
Site Configuration 5 Text Mandatory
The type of site: BSC, BSS, BTS, M_BTS (MCell family) or L_BTS (Horizonoffice sites).
Horizonoffice is not supported in the 1650 release.

Frequency Type 1 0 to 3 Optional, defaults to 0 (only
applicable for pre-1510, refer to
Cabinet table frequency type from
1510 onwards).
Defines the frequency range to use at this site.
Pre-BSSGSM 1510:
0 GSM 900 or EGSM 900
1 DCS 1800
2 DCS 2000
Cont.
6-10 68P02900W22-Q
09-Sep-2004
System Information: DataGen Site (BTS specific) table

BTS Type 1 0 to 2 Mandatory if site number not 0
and Site Configuration is a BTS,
otherwise unused.
Used for element bts_type,
0 only BTP
1 only BTP and DHP
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.
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-16 LCF ( Pre-1510 )
0-24 LCF (1510 onwards)
Range Device
0-16 BSP
0-16 LCF (Pre-1510)
0-24 LCF (1510 onwards)
RSL Rate 2 16 or 64 Mandatory. Applicable from 1510
only.
Used to determine the data rate of the RSL on BTSs.
CSFP algorithm 10 See below. Optional.
Used for determining:
i The algorithm for dynamic configuration of CSFP.
ii The CSFP download flow control percentage.
Entries are made in the following format:
Site 0: ALG
Sites other than 0: ALG_Pctg
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
Cont.
68P02900W22-Q 6-11
09-Sep-2004
Site (BTS specific) table Chapter 6: MCDF tables

Dynamic Allocation 3 no/yes Optional. Applicable from 1600
Default is no. for In Cell sites only.
Used to indicate whether the site uses dynamic allocation of terrestrial backing resources.
6-12 68P02900W22-Q
09-Sep-2004
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-5. The default cabinet type is type 0 (BTS4).
Default filename cab.mcd
Table 6-5 Cabinet table

Site Number 3 0 to 120 Mandatory
The site number at which the cabinet is located (refer to the description in Table 6-4).
Cabinet ID 2 0 to 19 Mandatory
The CAB ID for the cabinet.
Cabinet Type 2 Text or Numeric in the Mandatory
range set out 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
14 M_CELL_MICRO
15 M_CELLCITY
16 M_CELLARENA
Cont.
68P02900W22-Q 6-13
09-Sep-2004
Cabinet table Chapter 6: MCDF tables
Table 6-5 Cabinet table (Continued)

17 LIBRA
18 HORIZONMACRO (THOR)
19 HORIZONMACRO_EXT (THOR_EXT)
20 M_CELLARENA_MACRO
21 PCU_CAB
22 HORIZONMICRO
23 HORIZONCOMPACT
24 HORIZONMACRO2
25 HORIZONMACRO2_EXT
Frequency Type 2 1 to 15 Mandatory.
The valid frequency types are defined in Table 6-6.
Note that 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.
6-14 68P02900W22-Q
09-Sep-2004
System Information: DataGen Cabinet table
Table 6-6 Frequency Types

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
PCS1900 was formerly known as DCS2000

Option Dependencies
Table 6-7 Option dependencies
If Then
Both Infrastructure Sharing Homogeneous Cabinet Each cabinet (within any given site) can support
and Infrastructure Sharing Heterogeneous Cabinet multiple frequency types.
options have been purchased: Valid Range: 1 to 15
Cont.
68P02900W22-Q 6-15
09-Sep-2004
Cabinet table Chapter 6: MCDF tables
Table 6-7 Option dependencies (Continued)

If Then
Both Infrastructure Sharing Homogeneous Cabinet Only the first cabinet for any given site need have
and Infrastructure Sharing Heterogeneous Cabinet this field set. Multiple frequency types within a
options have not been purchased: single cabinet, 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 Cabinet Each cabinet for any given site may be configured
has been purchased and Infrastructure Sharing to support a different frequency type.
Heterogeneous Cabinet options has not been Valid Range: 1, 2, 4 or 8.
purchased:

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 Antenna 3 yes/no Optional. Used only for
Default is no. cabinet type 15/16.
Used for the prompted parameter: Is Integrated Antenna allowed?
6-16 68P02900W22-Q
09-Sep-2004
System Information: DataGen Hardware table
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-8).
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-8 Hardware table

Site Number 3 0 to 120 Mandatory.
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 non-M-
Cell/Horizon sites, otherwise
unused.
The slot number for this device/function.
Not applicable for Horizonoffice DRIs. Refer to the DRI table (Table 6-29).
68P02900W22-Q 6-17
09-Sep-2004
Hardware table Chapter 6: MCDF tables

Device Name 7 Text Optional.
The name of this device at a BSS area:
BSS
AXCDR
The name of this device at an RXCDR area:
RXCDR
ABSS
The name of this device at a non-M-Cell site:
DRI
GPROC
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 is
range is device filled in.
dependant).
The first device ID for this device.
Second Device ID 3 0 to 255 (valid Optional.
range is device
dependant).
This field is only used 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).
MSI Type
255 MSI2 (non-MCell sites only)
21 MSI_NIU2 (Horizon II macrosites only)
Cont.
6-18 68P02900W22-Q
09-Sep-2004

12 RF Unit (Horizonoffice 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 (is supported in 1.6.5.0 for non-MCell sites)
1 XCDR (non-MCell sites only)
0 MSI (non-MCell sites only)
Manual equipage of MSI is not allowed on Horizon II and Horizon II_ext cabinets.

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
feature purchased and MMS0
Protocol Type is HDSL).
Used for the Enter the number of time slots supported on MMS0 prompt in the equip MSI command.
Cont.
68P02900W22-Q 6-19
09-Sep-2004

MMS0 Modem Setting 6 TEXT (MASTER Optional. (Mandatory if
or SLAVE) Integrated MCell HDSL
Protocol Type is 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
feature purchased and
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
Protocol Type is 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
Protocol Type is 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 only valid for a GPROC device entry.)
BTP
The name of this function at a PCU.
PICP (for a PCU DPROC)
PRP (for a PCU DPROC)
DPROC (mandatory for a PICP MSI at the PCU)
Cont.
6-20 68P02900W22-Q
09-Sep-2004

Function ID 3 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 from
1.5.0.0.
NONE Not Used
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
Note: 0 to 16 for pre-1.5.1.0
and 0 to 24 from 1.5.1.0.
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:
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{4040} 0 to 65535 Used for nsei. Note that older
binaries (1650, 1670) contain
the NSEI parameter in the
Generics table.
Cont.
68P02900W22-Q 6-21
09-Sep-2004

Used as follows for BSS area specific devices:
AXCDR yes/no Used to specify use of CIC
validation.
Second Function ID 3 0 to 99 Optional.
(Allow for
expansion)
The second ID of this function valid for GPROC and PCU entries, BSS or RXCDR area entries. Used
as follows:
1.5.0.0
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
Note that the applicable range for an LCF Maximum number of MTLs is 0-1 in pre-1.5.1.0 and 0-2 from
1.5.1.0 onwards (2 indicates a GPROC2 card is being used for this purpose). The applicable range for an
LCF Maximum number of LMTLs is 0-2 in 1.6.5.0 onwards.
Used as follows for M-Cell devices:
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.
Cont.
6-22 68P02900W22-Q
09-Sep-2004

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).
Third Function ID 3 0 to 99 Optional.
The third ID of this function - valid in GPROC and PCU entries, BSS or RXCDR area entries.
Used as follows:
1.5.0.0
NONE Not Used
BSP Not Used
BTP Not Used
CSFP Not Used
DHP Not Used
LCF 0-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.
Cont.
68P02900W22-Q 6-23
09-Sep-2004

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:
GPROC LCF 06 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 for the Enter the T391 timer prompt in the equip GBL command.
GBL T392 Timer 2 6 to 30 Used only with the PCU GBL
device - optional.
Used for the Enter the T392 timer prompt in the equip GBL command.
GBL N391 Counter 3 1 to 255 Used only with the PCU GBL
device - optional.
Used for the Enter the N391 counter prompt in the equip GBL command.
Cont.
6-24 68P02900W22-Q
09-Sep-2004

device - optional.
device - optional.
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 PSP
device - optional
Specifies the subnet mask of the PSP.
Router IP address 15 0 to 255 per byte Used only with the PCU PSP
device - optional
Specifies the router address of the PSP.
MSC MSI ID 3 0 to 123 Only used 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 Only used when MSI type is
GDP.
Always set to zero, because MSIs cannot be used to provide MSC MMSs.
Transcoding Capability 8 0 or 1 Only used when MSI type is
GDP.
Specifies the transcoding functionality of the GDP board.
68P02900W22-Q 6-25
09-Sep-2004
Generics table Chapter 6: MCDF tables
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 may be overridden for a site or cell by
values in the Specifics and Cell tables.
Table 6-9 outlines the parameters of the Generics table.
Default filename gene.mcd
Table 6-9 Generics table

Element Name 50 <element Mandatory.
name>[,<index>]
Name of the element optionally followed by an index.
Recommended Value 11 -2,147,483,647 to Mandatory.
+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.
Layout of elements in the MCDF Generics table
The following are the elements in the Generics table (refer to Table 6-10):
6-26 68P02900W22-Q
09-Sep-2004
System Information: DataGen Generics table
Table 6-10 Generics table - elements
Element name Recommended value

aci_error_clr_thresh 0
aci_error_gen_thresh 6
aci_error_inc 1
adap_ho_alt_trigger_rxqual 0
adap_ho_pbgt 0
adap_ho_rxlev 0
adap_ho_rxqual 0
adap_trigger_pbgt 0
adap_trigger_rxlev_dl 0
adap_trigger_rxlev_ul 0
adap_trigger_rxqual_dl 0
adap_trigger_rxqual_ul 0
adap_trigger_hop_rxqual_dl 0
adap_trigger_hop_rxqual_ul 0
addr_ind_bit_8 0
alt_qual_proc 0
{4322}amr_fr_dl_la_enabled 1
{4322}amr_fr_ul_la_enabled 1
{4322}amr_hr_dl_la_enabled 1
{4322}amr_hr_ul_la_enabled 1
{4322}amr_hr_res_ts 2
{4322}amr_hr_intracell_ho_allowed 3
{4322}amr_hop_count 1
{4322}amr_inner_hr_usage_thres 101
{4322} amr_bss_half_rate_enabled 0
{4322} amr_half_rate_enabled 0
{4322} amr_bss_full_rate_enabled 0
{4322} amr_full_rate_enabled 0
{4322} amr_new_calls_hr 101
{4322} amr_reconfig_fr_to_hr 101
{4322} amr_ms_monitor_period 40
{4322} amr_ms_high_cmr 95
Cont.
68P02900W22-Q 6-27
09-Sep-2004
Table 6-10 Generics table - elements (Continued)

{4322} amr_ms_low_cmr 99
{4322} amr_ms_high_rxqual 4
{4322} amr_ms_low_rxqual 2
{4322} amr_dl_thresh_adjust 3
{4322} amr_dl_la_mode_chg_min 5
{4322} amr_force_hr_usage 0
attach_detach 0
auto_dl_dur 50
auto_rf_loss_trace 0
ba_alloc_proc 0
band_preference None
band_preference_mode 0
bcch_power_level 3
{23658} bep_period 0
{23658} bep_period2 15
ber_loss_daily 4
ber_loss_hourly 6
bounce_protect_margin 0
bs_ag_blks_res 0
bs_pa_mfrms 0
{3723} bs_pag_blks_res 3
{3723} bs_pbcch_blks 2
{3723} bs_pcc_chans 1
{3723} bs_prach_blks 4
bssap_ss 254
bssqp block retries 3
{4449} bssgp_cbl_bit 0
bssgp_fc_period_c 10
bssgp_flow_control 2
bssgp_recap_retries 3
bssgp_reset_retries 3
bssgp_scheduling 1
bssgp_unblock_retries 3
Cont.
6-28 68P02900W22-Q
09-Sep-2004
Table 6-10 Generics table - elements (Continued)

bss_egsm_alm_allowed 0
bss_msc_overload_allowed 0
bts_escalation 60
bts_p_con_ack 1
bts_p_con_interval 2
bts_power_control_allowed 0
bts_txpwr_max_inner None
The bts_txpwr_max_inner parameter has a range from -1 to 21.

bvci None
{3723} c31_hyst 0
{3723} c32_qual 0
call_trace_options 0
called_pci 0
calling_pci 0
carrier_disable_time 120
carriers_ins_pwr_fail 30
cbc_fast_select 1
cbc_intface_vers 0
cbc_vbind_cntr 0
cbs_outage_cntr 0
cbch_enabled 0
ccch_conf 0
ccch_load_period 40
cell_bar_access_class 0
cell_bar_access_switch 0
cell_bar_qualify 0
cell_reselect_hysteresis 4
cell_reselect_offset 0
Cont.
68P02900W22-Q 6-29
09-Sep-2004

cell_reselect_param_ind 0
channel_reconfiguration_switch 0
cic_error_clr_thresh 0
cic_error_gen_thresh 6
cic_error_inc 1
cic_error_decrement 1
ciph_mode_rej_allowed 0
clk_src_fail_reset_period 24
coincident_offset 0
confusion_msg_allowed 0
congest_at_source None
congest_at_target None
cp_option_reset_ckt 1
cp_option_rr_status 1
cr_calling 0
cs34_enabled 0
{4445} ddtr_ctrl_enabled 0
decision_1_dl_rxlev_av_h 0
decision_1_dl_rxlev_av_ih 0
decision_1_dl_rxlev_av_p 0
decision_1_dl_rxqual_av_h 0
decision_1_dl_rxqual_av_p 0
decision_1_n1 1
decision_1_n2 1
decision_1_n3 1
decision_1_n4 1
decision_1_n5 1
decision_1_n6 1
decision_1_n7 1
decision_1_n8 1
decision_1_ncell_rxlev_av_h_calc 0
decision_1_p1 1
decision_1_p2 1
decision_1_p3 1
Cont.
6-30 68P02900W22-Q
09-Sep-2004

decision_1_p4 1
decision_1_p5 1
decision_1_p6 1
decision_1_p7 1
decision_1_p8 1
decision_1_p_bgt_rxlev_av_h 0
decision_1_tim_adv_av_alg 0
decision_1_ul_rxlev_av_h 0
decision_1_ul_rxlev_av_ih 0
decision_1_ul_rxlev_av_p 0
decision_1_ul_rxqual_av_h 0
decision_1_ul_rxqual_av_p 0
decision_alg_num 0
decision_alg_type 0
delay_dl_rel_dur 50
{4445} delay_ul_rel_dur 18
direct_inner_zone_threshold 63
disuse_cnt_hreqave 0
dl_audio_lev_offset 0
dl_dtx_voice_data 0
dl_rxlev_ho_allowed 1
dl_rxqual_ho_allowed 1
dnlk_vad_dtx 0
dr_chan_mode_modify 0
dr_ho_during_assign 0
dr_preference 0
dr_standard_congest 0
dtx_required 2
dual_band_offset 0
dyn_step_adj 0
dyn_step_adj_fmpr 10
dynet_tchs_reserved 0
early_classmark_sending 0
efr_enabled 0
Cont.
68P02900W22-Q 6-31
09-Sep-2004

{23658} egprs_init_dl_cs 2
{23658} egprs_init_ul_cs 2
egsm_handover_threshold 0
eop_enabled 0
emergency_class_switch 0
en_incom_ho 1
enhanced_relief 1
erc_ta_priority 50
extended_paging_active 0
full_pwr_rfloss 0
{3723} fdd_gprs_qoffset 0
gbl_thrput_period 50
gci_error_clr_thresh 0
gci_error_gen_thresh 6
gci_error_inc 1
gclk_qwarm_flag 0
global_reset_repetitions 0
gproc_slots 16
gprs_alarm_time 60
gprs_bs_cv_max 6
{3723} gprs_cell_reselect_hysteresis 0
{4441} gprs_com_ms_class 8
gprs_dl_pwr_mode 1
gprs_drx_timer_max 0
gprs_intraho_allwd 1
gprs_mac_mode 1
{4441} gprs_max_ul_ts 2
{4441} gprs_min_prr_blks 0
gprs_ms_pan_dec 1
gprs_ms_pan_inc 1
gprs_ms_pan_max 3
gprs_ms_txpwr_max_cch None
gprs_network_operation_mode 3
gprs_pb 1
Cont.
6-32 68P02900W22-Q
09-Sep-2004

gprs_pc_alpha 10
gprs_pc_meas_chan 0
{3723} gprs_penalty_time 0
gprs_reconfig_thresh_idle_tch 1
{3723} gprs_reselect_offset 16
gprs_rxlev_access_min 0
gprs_sched_beta 1
The gprs_sched_beta parameter has the following range: 0, 1, and 2.

gprs_sig_bvci 0
gprs_t3168 4000
gprs_t3192 500
{3723} gprs_temporary_offset 0
gprs_ts_config_alg 0
gprs_smg30_t3192 500
{4441} gprs_ul_dl_bias 1
group_block_unblock_allowed 0
{4040} gsl_lcf_mapping 1
gsm_cell_id_format 1
handover_power_level 2
handover_recognized_period 2
handover_required_curr_ch 0
handover_required_reject_switch 1
handover_required_sp_ver_used 0
{3723} hcs_thr 0
ho_exist_congest 0
ho_margin_def 8
ho_margin_usage_flag 0
ho_only_max_pwr 0
ho_pwr_level_inner 2
Cont.
68P02900W22-Q 6-33
09-Sep-2004

hop_count 255
hopping_support 0
hopping_systems_enabled,0 0
hopping_systems_hsn,0 0
Cont.
6-34 68P02900W22-Q
09-Sep-2004

illegal_circuit_id 0
immediate_assign_mode 0
inact_cont_allow 1
{4441} inc_prp_cap_ena 0
intave 8
{4445} init_dl_cs 1
{4445} init_ul_cs 1
interband_ho_allowed None
inter_cell_handover_allowed 1
interfer_bands,0 63
interfer_bands,1 63
interfer_bands,2 63
interfer_bands,3 63
interfer_bands,4 63
interfer_ho_allowed 1
intra_cell_handover_allowed 1
l_rxlev_dl_h 10
l_rxlev_dl_p 30
l_rxlev_ul_h 10
l_rxlev_ul_p 30
l_rxqual_dl_h 5
l_rxqual_dl_h_data None
l_rxqual_dl_h_hopping None
l_rxqual_dl_p 4
l_rxqual_dl_p_data None
l_rxqual_dl_p_hopping None
l_rxqual_ul_h 5
l_rxqual_ul_h_data None
l_rxqual_ul_h_hopping None
l_rxqual_ul_p 5
l_rxqual_ul_p_data None
l_rxqual_ul_p_hopping None
{4322} l_rxqual_ul_p_amr_fr None
{4322} l_rxqual_ul_p_amr_hr None
Cont.
68P02900W22-Q 6-35
09-Sep-2004

{4322} l_rxqual_ul_h_amr_fr None
{4322} l_rxqual_ul_h_amr_hr None
{4322} l_rxqual_ul_h_hopping_amr_fr None
{4322} l_rxqual_ul_h_hopping_amr_hr None
{4322} l_rxqual_ul_p_hopping_amr_fr None
{4322} l_rxqual_ul_p_hopping_amr_hr None
{4322} l_rxqual_dl_p_amr_fr None
{4322} l_rxqual_dl_p_amr_hr None
{4322} l_rxqual_dl_h_amr_fr None
{4322} l_rxqual_dl_h_amr_hr None
{4322} l_rxqual_dl_h_hopping_amr_fr None
{4322} l_rxqual_dl_h_hopping_amr_hr None
{4322} l_rxqual_dl_p_hopping_amr_fr None
{4322} l_rxqual_dl_p_hopping_amr_hr None
land_layer1_mode 0
layer_number 0
lcs_mode 0
link_about_to_fail 2
link_fail 4
local_maintenance 1
low_sig_thresh 0
lta_alarm_range 7
ltu_fw_auto_download 1
max_gprs_ts_per_carrier 8
max_ms_dl_buffer 12000
max_ms_dl_rate 900
max_number_of_sdcchs 48
max_q_length_full_rate_channel 0
max_q_length_immediate_assignments 0
max_q_length_sdcch 0
max_retran 0
max_rst_ckt_timer_exps 0
max_tx_bts 0
max_tx_ms 30
Cont.
6-36 68P02900W22-Q
09-Sep-2004

mb_preference 0
mb_tch_congest_thres 100
min_gprs_ts_per_carrier 0
The parameter min_gprs_ts_per_carrier is not available if the EGPRS option is purchased.

missing_rpt 0
mmi_cell_id_format 0
mms_cat_enable 0
mms_config_type 0
msc_preference 0
msc_qt 84
msc_release 0
ms_distance_allowed 0
ms_max_range 0
ms_p_con_ack 2
ms_p_con_interval 2
ms_power_control_allowed 1
ms_power_offset 0
ms_txpwr_max_cch 2
ms_txpwr_max_def 30
ms_txpwr_max_inner None
mspwr_alg 0
mtl_loadshare_granularity 1
multiband_reporting 0
n_avg 2
n_avg_i 2
ncc_of_plmn_allowed 255
nccr_enabled 0
nc_non_drx_period 2
nc_reporting_period_i 6
Cont.
68P02900W22-Q 6-37
09-Sep-2004

nc_reporting_period_t 2
ncell_proc 0
neighbor_journal 0
ns_alive_retries 3
ns_block_retries 3
ns_unblock_retries 3
nsei None
From release 1740 onwards, the NSEI parameter is located in the Hardware table.

num_audit_retries 1
num_gbl_dl_thrput_samples 10
num_gbl_ul_thrput_samples 10
number_of_preferred_cells 16
number_sdcchs_preferred 8
option_alg_a5_1 0
option_alg_a5_2 0
option_alg_a5_3 0
option_alg_a5_4 0
option_alg_a5_5 0
option_alg_a5_6 0
option_alg_a5_7 0
option_emergency_preempt 0
outer_zone_usage_level 0
override_intra_bss_pre_transfer 0
override_speech_version 0
pbgt_mode 0
pccch_alloc 0
{3723} pccch_drx_timer_max 3
{3723} pccch_enabled 0
pcr_enable 0
Cont.
6-38 68P02900W22-Q
09-Sep-2004

pcr_n1 127
pcr_n2 3750
{4040} pcu_redundancy 1
{4040} pcu_red_map_01 -1
{4040} pcu_red_map_02 -1
{4040} pcu_red_map_11 -1
{4040} pcu_red_map_12 -1
{4040} pcu_red_map_21 -1
{4040} pcu_red_map_22 -1
penalty_time 0
{4441} percent_traf_cf 55
phase2_classmark_allowed 0
phase2_resource_ind_allowed 0
phase_lock_gclk 0
phase_lock_retry 255
pic_error_clr_thresh 0
pic_error_gen_thresh 6
pic_error_inc 1
poor_initial_assignment 0
pool_gproc_preemption 1
pow_inc_step_size 2
pow_inc_step_size_dl 2
pow_inc_step_size_ul 2
pow_red_step_size 2
pow_red_step_size_dl 2
pow_red_step_size_ul 2
{3723} prach_s 8
{3723} prach_tx_int 14
{4040} primary_pcu -1
prioritize_microcell 1
{3723} priority_class 0
protect_last_ts 0
prr_agg_factor 3
psil_repeat_period 5
Cont.
68P02900W22-Q 6-39
09-Sep-2004

pwr_handover_allowed 1
pwrc 1
{3723}qsearch_p 0
queue_management_information 50
rac None
ra_colour None
{3723} ra_reselect_hysteresis 0
rach_load_period 16
rach_load_threshold 1000
rach_load_type 0
radio_link_timeout 4
rapid_pwr_down 0
rci_error_clr_thresh 0
rci_error_gen_thresh 6
rci_error_inc 1
rci_error_decrement 1
red_loss_daily 16
red_loss_hourly 20
red_loss_oos 511
red_loss_restore 6000
red_time_oos 25
red_time_restore 150
reestablish_allowed 0
remote_loss_daily 20
remote_loss_daily_pcu 16
remote_loss_hourly 16
remote_loss_hourly_pcu 20
remote_loss_oos 511
remote_loss_oos_pcu 511
remote_loss_restore 6000
remote_time_oos 5
remote_time_oos_pcu 5
remote_time_restore 5
remote_time_restore_pcu 5
Cont.
6-40 68P02900W22-Q
09-Sep-2004

report_resource_tch_f_high_water_mark 2
report_resource_tch_f_low_water_mark 12
res_gprs_pdchs 0
res_ts_less_one_carrier 0
rf_res_ind_period 10
rpd_offset 8
rpd_period 2
rpd_trigger 45
rpt_bad_qual_no_mr 0
rtf_path_enable 0
rxlev_access_min 0
rxlev_dl_zone 63
rxlev_min_def 15
rxlev_ul_zone 63
sccp_bssap_mgt 1
{4449} scr_enabled 0
sdcch_ho 1
sdcch_need_high_water_mark 2
sdcch_need_low_water_mark 12
sdcch_timer_ho 1
sdcch_tch_band_reassign_delay 0
{3723} search_prio_3g 1
second_asgnmnt 0
secondary_freq_type 1
second_asgnmnt 0
{3723}sgsn_release 0
sig_lnk_tst_allow 1
slip_loss_daily 10
slip_loss_hourly 4
slip_loss_oos 255
slip_loss_restore 6000
smg_gb_vers 29
smg_um_vers 29
sms_dl_allowed 0
Cont.
68P02900W22-Q 6-41
09-Sep-2004

sms_tch_chan 2
sms_ul_allowed 0
ssp_burst_delay 200
ssp_burst_limit 10
ss7_mode 0
ssm_critical_overload_threshold 80
ssm_normal_overload_threshold 70
static_sync_timer 12000
stat_interval 30
stp_pc None
stp_pc_enabled 0
sw_ts_less_one_carrier 0
switch_gprs_pdchs 0
sync_loss_daily 20
sync_loss_daily_pcu 20
sync_loss_hourly 16
sync_loss_hourly_pcu 16
sync_loss_oos 511
sync_loss_oos_pcu 511
sync_loss_restore 6000
sync_time_oos 90
sync_time_oos_pcu 25
sync_time_restore 30
sync_time_restore_pcu 150
t_avg_t 10
t_avg_w 10
tch_busy_critical_threshold 100
tch_busy_norm_threshold 100
tch_congest_prevent_thres 100
tch_flow_control 0
tch_full_need_low_water_mark 255
temporary_offset 0
threshold 7
timing_advance_period 4
Cont.
6-42 68P02900W22-Q
09-Sep-2004

{23658} tlli_blk_coding 0
trace_msgs_after_ho 5
trace_msgs_before_ho 5
trunk_critical_threshold 50
trunk_major_threshold 10
ts_alloc_flag 0
tsc_update_method 0
tx_integer 4
tx_power_cap 0
u_rxlev_dl_ih 45
All DCS1800 DRI devices in a Horizon II macro and Horizon II macro_ext cabinet are forced
to operate in high power mode (32 Watts).

u_rxlev_dl_p 40
u_rxlev_ul_ih 45
u_rxlev_ul_p 40
u_rxqual_dl_p 1
{4322} u_rxqual_dl_p_amr_hr None.
u_rxqual_ul_p 1
{4322} u_rxqual_ul_p_amr_hr None.
ul_audio_lev_offset 0
ul_rxlev_ho_allowed 1
ul_rxqual_ho_allowed 1
unequipped_circuit_allowed 0
update_c 0
use_bcch_for_gprs 1
68P02900W22-Q 6-43
09-Sep-2004
The element use_bcch_for_gprs is not available if the EGPRS option is purchased.

use_derived_ho_power 0
use_neighbor_pbgt_hreqave 0
volume_control_type 0
wait_for_reselection 10
wait_indication_parameters 5
worse_neighbor_ho 0
zone_ho_hyst 0
zone_pingpong_enable_win 30
zone_pingpong_disable_win 30
zone_pingpong_preferred_zone 255
zone_pingpong_count 3
Generics table elements for GSM Half Rate
{22064}
Table 6-11 shows the new and modified Generics table elements for GSM Half Rate and their recommended
values.
Table 6-11 Generics table elements for GSM Half Rate

{22064} hr_res_ts 2
{22064} hr_intracell_ho_allowed 3
{22064} hop_count 1
{22064} inner_hr_usage_thres 101
{22064} new_calls_hr 101
{22064} reconfig_fr_to_hr 101
{22064} force_hr_usage 0
{22064} l_rxqual_ul_p_hr None
{22064} l_rxqual_ul_h_hr None
{22064} l_rxqual_ul_h_hopping_hr None
Cont.
6-44 68P02900W22-Q
09-Sep-2004
Table 6-11 Generics table elements for GSM Half Rate (Continued)
{22064} l_rxqual_ul_p_hopping_hr None
{22064} l_rxqual_dl_p_hr None
{22064} l_rxqual_dl_h_hr None
{22064} l_rxqual_dl_h_hopping_hr None
{22064} l_rxqual_dl_p_hopping_hr None
{22064} u_rxqual_dl_p_hr None
{22064} u_rxqual_ul_p_hr None
{22064} gsm_bss_half_rate_enabled 0
{22064} gsm_half_rate_enabled 0
The parameter handover_required_sp_ver_used cannot be disabled if {22064} GSM Half

Rate is enabled.
68P02900W22-Q 6-45
09-Sep-2004
Timer table Chapter 6: MCDF tables
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 may be overridden for a site
or cell by values in the Specifics table.
Table 6-12 outlines the parameters of the Timer table.
Default filename time.mcd
Table 6-12 Timer table

Element Name 50 <element Mandatory
name>[,<index>]
Name of the timer element optionally followed by an index.
Recommended Value 11 -2,147,483,648 to Mandatory
+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.
Layout of timer elements in the MCDF Timer table
Table 6-13 shows the layout of the timer element parameters in the Timer table.
6-46 68P02900W22-Q
09-Sep-2004
System Information: DataGen Timer table
Table 6-13 Timer table - elements
# Element name Recommended value

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_t1_timer 3
9 bssgp_t2_timer 60
10 bssmap_t1 30000
11 bssmap_t4 50000
12 bssmap_t7 30000
13 bssmap_t8 28000
14 bssmap_t10 28000
15 bssmap_t11 28000
16 bssmap_t13 40000
17 bssmap_t19 30000
18 bssmap_t20 30000
19 bssmap_tqho 30000
20 bts_audit 60000
21 bts_audit_response 30000
22 carrier_free_immediate 120000
23 cbch_1 30000
24 cbch_2 30000
25 cbch_3 35000
26 channel_act 10000
27 channel_teardown 28000
28 cipher_comp_ms 28000
29 ciphering_successful 30000
30 circuit_reset_ack 70000
31 clear_cmd_ext_ho 30000
32 clear_command 30000
Cont.
68P02900W22-Q 6-47
09-Sep-2004
Table 6-13 Timer table - elements (Continued)

33 dealloc_inact 10000
34 downlink_sync_timer 1000
35 dynet_retry_time 1000
36 early_classmark_delay 0
37 emerg_reserved 120000
38 ext_rtry_cand_prd 4000
39 ext_ho_allocation 30000
40 flow_control_t1 20000
41 flow_control_t2 30000
42 ho_ack 5000
43 ho_allocation 30000
44 ho_complete 28000
45 ho_request 28000
46 ho_successful 30000
47 hop_count_timer 0
48 initial_sync_timer 4000
49 lb_int_bssmap_t4 50000
50 lb_int_bssmap_t13 40000
51 lb_int_called_pci 0
52 llb_int_calling_pci 0
53 lb_int_clear_command 30000
54 lb_int_cr_calling 0
55 lb_int_dpc 0
56 lb_int_global_reset_repetitions 0
57 lb_int_sccp_released 30000
58 lb_int_sccp_tconn_est 30000
59 lb_int_sccp_tiar 30000
60 lb_int_sccp_tias 30000
61 lb_int_sccp_trel 10000
62 lb_int_spi 60000
63 lb_int_ss7_l2_t1 50000
64 lb_int_ss7_l2_t2 25000
65 lb_int_ss7_l2_t3 1400
Cont.
6-48 68P02900W22-Q
09-Sep-2004

66 lb_int_ss7_l2_t4 600
67 lb_int_ss7_l2_t5 100
68 lb_int_ss7_l2_t6 5000
69 lb_int_ss7_l2_t7 1000
70 lb_int_ss7_l3_t1 850
71 lb_int_ss7_l3_t2 1400
72 lb_int_ss7_l3_t4 850
73 lb_int_ss7_l3_t5 850
74 lb_int_ss7_l3_t12 1150
75 lb_int_ss7_l3_t13 1150
76 lb_int_ss7_l3_t14 2500
77 lb_int_ss7_l3_t17 1150
78 lb_int_ss7_l3_t22 270000
79 lb_int_ss7_l3_t23 270000
80 lb_int_ss7_slt_t1 8000
81 lb_int_t_stat_info 90000
82 lcs_perf_location 300000
83 lcs_segmentation 10000
84 lcs_supervision 30000
85 lmtl_loadshare_granularity 0
86 mode_modify 10000
87 mode_rr_modify_ack 28000
88 ms_sapi3_est 28000
89 neighbor_report_timer 10
90 ns_alive_timer 3
91 ns_block_timer 3
92 ns_reset_period 125
93 ns_reset_timer 40
94 ns_test_timer 30
95 radio_chan_released 30000
96 register_exp 120000
97 rf_chan_rel_ack 10000
98 rr_ny1_rep 20
Cont.
68P02900W22-Q 6-49
09-Sep-2004

99 rr_T3101 5000
100 rr_T3103 30000
101 rr_T3105 60
102 rr_T3109 14400
103 rr_T3111 1500
104 rr_T3111_sd 1500
105 rr_T3111_tch 1500
106 rr_T3212 10
107 rtry_cand_prd 4000
108 sacch_info 2000
109 sccp_released 30000
110 sccp_tconn_est 30000
111 sccp_tiar 30000
112 sccp_tias 30000
113 sccp_trel 10000
114 send_circuit_blocks 30000
115 sm_audit_response 30000
116 spi 60000
117 ss7_l2_t1 50000
118 ss7_l2_t2 25000
119 ss7_l2_t3 1400
120 ss7_l2_t4 600
121 ss7_l2_t5 100
122 ss7_l2_t6 5000
123 ss7_l2_t7 1000
124 ss7_l3_t1 850
125 ss7_l3_t2 1400
126 ss7_l3_t3 850
127 ss7_l3_t4 850
128 ss7_l3_t5 850
129 ss7_l3_t12 1150
130 ss7_l3_t13 1150
131 ss7_l3_t14 2500
Cont.
6-50 68P02900W22-Q
09-Sep-2004

132 ss7_l3_t17 1150
133 ss7_l3_t21 30000
134 ss7_l3_t22 270000
135 ss7_l3_t23 270000
136 ss7_l3_t24 500
137 ss7_slt_t1 8000
138 ss7_slt_t2 60000
139 start_ack 30000
140 t_stat_info 90000
141 ts_free_immediate 50000
142 uplink_sync_timer 1000
143 valid_candidate_period 4000
68P02900W22-Q 6-51
09-Sep-2004
Modify Value table Chapter 6: MCDF tables
Modify Value table

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Modify Value table
This table contains the modify_value commands. The table is only applicable for MMS and LCF device
functions currently as DataGen only supports these devices within the modify_value command.
Default filename modv.mcd
Table 6-14 shows the MMS element parameters:
Table 6-14 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 See Applicable Names Mandatory.
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 See Range Table below. Mandatory.
The applicable ranges are shown in the following table:
Value Name Min Value Max Value
nbit 0 1
ber_oos_mon_period 1 60
ber_restore_mon_period 1 18000
Cont.
6-52 68P02900W22-Q
09-Sep-2004
System Information: DataGen Modify Value table
Table 6-14 Modify Value table (Continued)

phase_lock_duration 0 3600
mms_priority 0 255
max_opls 0 1
hdsl_oos_mon_period 0 3598
hdsl_restore_mon_pe- 0 65534
riod
shared_timeslots 0 32
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 below: Mandatory.
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
Device Fn ID2 2 0 or 1 Mandatory.
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)
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 has been added so as to allow support of further modify_value
commands as and when required.
68P02900W22-Q 6-53
09-Sep-2004
Circuit table Chapter 6: MCDF tables
Circuit table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Circuit table
Table 6-15 contains all MTL, LMTL and OML signalling 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).
The MSIs and MMSs required are detailed in the hardware file.
Default filename acct.mcd
Table 6-15 Circuit table

Site Number 3 0 to120 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 0 to 56 Mandatory.
(0 to 71 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 3 String width 3 Mandatory.
The type of entry being referred to as follows:
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)
Cont.
6-54 68P02900W22-Q
09-Sep-2004
System Information: DataGen Circuit table
Table 6-15 Circuit table (Continued)

Device ID 3 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 is as follows:
CBL 0
OPL 0
OML 0 to 3
MTL 0 to 15
LMTL5 0 to 15
XBL 0 to 31 (Pre 1600), 0 to 9 (From 1600)
Associated Device ID 3 1 to 128 Mandatory if not used for signalling
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.
End Group 1 0 to 3 Mandatory if Type = TCH,
otherwise unused.
The ending group number for the end timeslot.
MSC MSI 2 0 to 71 Mandatory if Type = TCH,
otherwise unused.
MSI used to the MSC (valid only for local transcoding BSC and RXCDR sites).
Cont.
68P02900W22-Q 6-55
09-Sep-2004
Circuit table Chapter 6: MCDF tables
Table 6-15 Circuit table (Continued)

MSC MMS 2 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.
6-56 68P02900W22-Q
09-Sep-2004
System Information: DataGen Channel table
Channel table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Channel table
Table 6-16 is only required for Remote Transcoders. This table contains the OML and MTL signalling 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.
Default filename chan.mcd

Table 6-16 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 2 0 to 71 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 2 0 to 71 Mandatory.
This field refers to the MSI ID of the B side.
MMS B 1 0 to 1 Mandatory.
This field refers to the MMS ID of the B side.
Cont.
68P02900W22-Q 6-57
09-Sep-2004
Channel table Chapter 6: MCDF tables
Table 6-16 Channel table (Continued)

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-Q
09-Sep-2004
System Information: DataGen Links table
Links table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Links table
This table is used for two different tasks (refer to Table 6-17):
• 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 from 1620).
• RXCDR area
Contains details of the links between the RXCDR and its BSCs used by the XBL feature
(add_conn from 1620, add_bss_conn from 1510 and add_xbl_conn for pre-1510).
In both cases, the MSIs and MMSs required are detailed in the Hardware table.
Default filename link.mcd
Table 6-17 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 a 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 0 to 120,254 Mandatory
This field is used as the A end site identifier. Value must be 0 in the case of a RXCDR area.
TS_SWITCH/Marker Sites
From 1510, 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.
68P02900W22-Q 6-59
09-Sep-2004
Links table Chapter 6: MCDF tables
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 56,254 Mandatory.
This field is used as the A end MSI identifier.
From 1510 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.
From 1510 if Site Number A is a TS_SWITCH (marker site), 254 must be entered as the MMS A value.
Site Number B 3 0 to 120,254 Mandatory
This field is used as the B end site identifier.
From 1510 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.
MSI B 3 0 to 56,254 Mandatory.
This field is used as the B end MSI identifier.
From 1510 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.
From 1510 if Site Number B is a TS_SWITCH (marker site), 254 must be entered as the MMS A value.
6-60 68P02900W22-Q
09-Sep-2004
System Information: DataGen Paths table
Paths table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Paths table
Table 6-18 contains details of all the paths/Dynets within the BSS area (providing signalling 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-18 Paths table

Terminating Site 3 1 to 120 Mandatory
Number
This field is used as the SITE at which the PATH terminates.
For a DYNET device this site MUST 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 120 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.
Cont.
68P02900W22-Q 6-61
09-Sep-2004
Paths table Chapter 6: MCDF tables
Table 6-18 Paths table (Continued)

RSL Second ID 1 0 to 7 (dependent on Mandatory if the first
type of equipment - see RSL id is present, see
below) RSL First ID.
This field is used as the second device ID for the RSL device.
The range is as follows:
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-Q
09-Sep-2004
System Information: DataGen LAPD table
LAPD table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of LAPD table
Table 6-19 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-19 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 (for 1620 onwards).
Type Range Usage
RSL 0 to 7 First Device ID
XBL 1 to 254 Refer to 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.
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.
Cont.
68P02900W22-Q 6-63
09-Sep-2004
LAPD table Chapter 6: MCDF tables
Table 6-19 LAPD table (Continued)

T200 timer value 4 See below. Optional
Range Min Max Step Size
Pre-1500 200 5000 50
1500 onwards 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.
Range Min Max
Pre-1500 1 127
1500 onwards 1 10
Used for the LAPD K value.
6-64 68P02900W22-Q
09-Sep-2004
System Information: DataGen Cell table
Cell table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Cell table
Table 6-20 can detail all the cells across the OMC or network and also the external neighbours 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-26.
Default filename cell.mcd
Table 6-20 Cell table

BSS ID 3 0 to 255 or X Mandatory.
The bss_id of the BSS this cell is in.
X being a cell external to the BSS area that is a neighbour of a cell inside this BSS area.
Site Number 3 0 to 120 or X Mandatory.
The Site number, within the BSS, of the Site this cell is in.
X being a cell external to the BSS area that is a neighbour of a cell inside this BSS area.
LAC 6 6 digit numeric Mandatory.
The Location Area Code.
Digits to be entered in decimal or hex. Hex numbers 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 in decimal or hex form. Hex numbers to be followed by h or preceded by 0x; for
example: 1234h or 0x1234
Cell Name 31 31 character string Optional.
The cell name.
Frequency Type 1 0, 1, 2, 4, 6 or 8 (See below) Mandatory
External Neighbours:
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:
PGSM 1
EGSM 2
DCS1800 4
Cont.
68P02900W22-Q 6-65
09-Sep-2004
Cell table Chapter 6: MCDF tables
Table 6-20 Cell table (Continued)

PGSM and DCS1800 5
EGSM and DCS1800 6
PCS1900 8
bsic 4 0 to 63 (hexadecimal) Mandatory.
Used for the bsic parameter of the add_neighbor command, when this cell is identified as a neighbour 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 See Frequency Type Channel Mandatory.
Groupings below:
Used for the bcch_freq_num parameter of the add_neighbor command, when this cell is identified as a
neighbour to another cell.
Verified also by the RTF table when 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
PCS1900 was formerly known as DCS2000.

ho_margin_cell 3 -63 to 63 Optional.
This value is purely 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.
Cont.
6-66 68P02900W22-Q
09-Sep-2004

ms_txpwr_max_cell 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 "Neighbour table" on page 6-155. Used for element
ms_txpwr_max_cell.
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-26).
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. Optional, only used if
Range:
if ccch_conf = 1: range 0 to 2
if ccch_conf not 1: range 0 to 7
Used for element bs_ag_blks_res.

number_sdcchs_ 2 See below. Optional, only used if
preferred not an external cell.
Range:
if ccch_conf = 1: range 4, 12, 20, 28, 36, 42
if ccch_conf not 1: range 8, 16, 24, 32, 40, 48
number_sdcchs_preferred must be <= max_number_of_sdcchs.
Used for element number_sdcchs_preferred.
max_number_of_ 2 16 to 48 Optional, only used if
sdcchs 12 to 48 (From 1600) not an external cell.
Cont.
68P02900W22-Q 6-67
09-Sep-2004

Value should be greater than that of number_sdcchs_preferred.
If ext_range_cell is set then the range is 16 to 20. If ccch_conf = 1, then the max_number_of_sdcchs default
is 44.
If ccch_conf = 1, then the max_number_of_sdcchs default is 48.
Used for element max_number_of_sdcchs.

sdcch_need_high_ 2 1 to 38 Optional, only used if
water_mark not an external cell.
sdcch_need_high_water_mark must be:
<= sdcch_need_low_water_mark - 10.
Used for element sdcch_need_high_water_mark.
sdcch_need_low_ 2 11 to 48 Optional, only used if
water_mark not an external cell.
sdcch_need_low_water_mark must be: <= max_number_of_sdcchs.
Used for element sdcch_need_low_water_mark.
max_tx_ms 2 0 to 39 Optional, only used if
Used for element max_tx_ms.
ms_txpwr_max_cch 2 0 to 19 Optional, only used if
Used for element ms_txpwr_max_cch.
ms_max_range 3 0 to 630 to 219 (if Optional, only used if
ext_range_cell is not an external cell.
enabled*)
Used for element ms_max_range.
ho_margin_def 3 -63 to 63 Optional, only used if
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
Used for element handover_power_level.
Cont.
6-68 68P02900W22-Q
09-Sep-2004

cell_reselect_hysteresis 2 0 to 7 Optional, only used if
Used for element cell_reselect_hysteresis.
max_tx_bts 2 0 to 21 (for PCS1900 Optional, only used if
cells) not an external cell.
-1 to 21 (for
PGSM/EGSM and
DCS1800 cells)
Used for element max_tx_bts.
bcch_power_level 2 0 to 21 Optional, only used if
Used for element bcch_power_level
inner_zone_alg 1 0 to 3 (3 is only valid Optional.
when the Dual Band Cell
Opt is purchased.)
Note that multi band must be enabled for inner_zone_alg to be modified.
This attribute is not valid at Horizonoffice sites.
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-26 or the "Specifics table" on page
6-102.
Used for chg_cell_element inner_zone_alg.

ext_range_cell 1 0 to 2 Optional.
There is one parameter associated with ext_range_cell as follows:
ms_max_range
(if ext_range 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.
Cont.
68P02900W22-Q 6-69
09-Sep-2004

hop_qual_enabled 1 0 to 1 Optional, only applicable to
1601 loads or later.
There are four parameters 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
6-102.
Used for chg_cell_element hop_qual_enabled.
data_qual_enabled 1 0 to 1 Optional, only applicable to
There are four parameters 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
6-102.
Used for chg_cell_element data_qual_enabled.
gprs_enabled 1 0 to 1 Optional, only applicable to
There are two parameters associated with gprs_enabled as follows:
rac
ra_colour
6-102.
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. Only applicable to
1650 loads and later.
The default value is 0.
qsearch_i 2 0 to 15 Optional. Only applicable to
qsearch_c_initial 1 0 to 1 Optional. Only applicable to
fdd_qoffset 2 0 to 15 Optional. Only applicable to
Cont.
6-70 68P02900W22-Q
09-Sep-2004

fdd_qmin 1 0 to 7 Optional. Only applicable to
{4449} gprs_cell_cgt_thr 1 1 to 4 Optional.
{4449} gprs_num_pmrs 2 1 to 10 Optional.
{4449} gprs_cr_margin 2 5 to 40 Optional.
{3723} persistence_level,0 2 0 to 15 Optional.
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.
{3723}prach_max_re- 1 0 to 3 Optional.
tran,0
Maximum number of retransmissions allowed for each radio priority level on a per cell basis. The default
value is 2.
tran,1
value is 2.
tran,2
value is 2.
tran,3
value is 2.
68P02900W22-Q 6-71
09-Sep-2004
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 will override this. If this were not so, the add_cell command
would fail to compile with the new range.
6-72 68P02900W22-Q
09-Sep-2004
System Information: DataGen Statistics table
Statistics table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Statistics table
Table 6-21, 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-21 Statistics table

Element Name 50 Text: Mandatory.
<element name>
[,<index>]
Name of the statistics element, optionally followed by an index.
Recommended Value 11 -2, 147, 483, 648 Mandatory.
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-Q 6-73
09-Sep-2004
Statistics table Chapter 6: MCDF tables
Layout of the elements in the MCDF Statistics table
Table 6-22 shows the statistics elements and their recommended values.
Table 6-22 Statistics table - elements

access_per_agch,0 0
access_per_pch,0 1
access_per_pch_cs,0 1
access_per_pch_ps,0 1
access_per_pch_cs_ps,0 1
{3723} access_per_ppch,0 0
access_per_rach,0 0
air_dl_control_blks,0 0
air_ul_control_blks,0 0
air_dl_data_blks,0 0
air_ul_data_blks,0 0
The statistics air_dl_data_blks and air_ul_data_blks are not available if the EGPRS option
is purchased.

{4445} air_dl_tbf_failures,0 0
{4445} air_ul_tbf_failures,0 0
alloc_sdcch,0 1
alloc_sdcch_fail,0 1
alloc_sdcch_fail,2 2147483647
alloc_sdcch_carr,0 0
alloc_tch,0 1
alloc_tch_carr,0 0
alloc_tch_fail,0 1
alloc_tch_fail,2 2147483647
{4322} alloc_tch_fail_hr_amr,0 0
Cont.
6-74 68P02900W22-Q
09-Sep-2004

alloc_tch_fail_inner_zone,0 1
{4322} alloc_tch_hr_amr,0 0
alloc_tch_inner_zone,0 1
{4322} amr_fr_dl_codec_mode_usage,0 0
{4322} amr_fr_ul_codec_mode_usage,0 0
{4322} amr_hr_dl_codec_mode_usage,0 0
{4322} amr_hr_ul_codec_mode_usage,0 0
{4322} amr_fr_dl_ adaptation,0 0
{4322} amr_fr_ul_ adaptation,0 0
{4322} amr_hr_dl_ adaptation,0 0
{4322} amr_hr_dl_ adaptation,0 0
{4322} amr_increase_thresh_adjust,0 0
{4322} amr_decrease_thresh_adjust,0 0
ater_chanel_status 0
ater_emerg_preempt_status 0
available_pdtch,0 0
available_sdcch,0 0
available_tch,0 0
available_tch,4,0 0
available_tch,4,1 1
available_tch,4,2 3
available_tch,4,3 5
available_tch,4,4 7
available_tch,4,5 9
available_tch,4,6 11
available_tch,5,0 0
available_tch,5,1 2
available_tch,5,2 4
available_tch,5,3 6
available_tch,5,4 8
Cont.
68P02900W22-Q 6-75
09-Sep-2004

{4322} available_tch_hr_amr,0 0
bad_ho_refnum_ms,0 0
bad_ho_refnum_ms,2 2147483647
ber,0 0
bsslap_abort_rcv,0 0
bsslap_abort_sent,0 0
bsslap_ms_pos_cmd,0 0
bsslap_ms_pos_resp,0 0
bsslap_rej,0 0
bsslap_reset,0 0
bsslap_ta_req,0 0
bsslap_ta_resp,0 0
bsslap_toa_req,0 0
bssmap_conless_info_rcv,0 0
bssmap_conless_info_sent,0 0
bssmap_perf_loc_abort_msgs,0 0
bssmap_perf_loc_req_msgs,0 0
bssmap_perf_loc_resp_msgs,0 0
bssmaple_conless_info_rcv,0 0
bssmaple_conless_info_sent,0 0
bssmaple_perf_loc_abort_msgs,0 0
bssmaple_perf_loc_req_msgs,0 0
bssmaple_perf_loc_resp_msgs,0 0
busy_cics,0 0
busy_cics,4,0 0
busy_cics,4,1 10
busy_cics,4,2 50
busy_cics,4,3 100
busy_cics,4,4 200
busy_cics,4,5 400
Cont.
6-76 68P02900W22-Q
09-Sep-2004

busy_cics,4,6 800
busy_cics,4,7 1200
busy_cics,4,8 1600
busy_cics,4,9 2200
busy_cics,5,0 9
busy_cics,5,1 49
busy_cics,5,2 99
busy_cics,5,3 199
busy_cics,5,4 399
busy_cics,5,5 799
busy_cics,5,6 1199
busy_cics,5,7 1599
busy_cics,5,8 2199
busy_cics,5,9 3200
busy_sdcch,0 1
busy_sdcch,4,0 0
busy_sdcch,4,1 1
busy_sdcch,4,2 3
busy_sdcch,4,3 5
busy_sdcch,4,4 7
busy_sdcch,4,5 9
busy_sdcch,4,6 11
busy_sdcch,4,7 13
busy_sdcch,4,8 15
busy_sdcch,4,9 17
busy_sdcch,5,0 0
busy_sdcch,5,1 2
busy_sdcch,5,2 4
busy_sdcch,5,3 6
busy_sdcch,5,4 8
busy_sdcch,5,5 10
busy_sdcch,5,6 12
busy_sdcch,5,7 14
busy_sdcch,5,8 16
Cont.
68P02900W22-Q 6-77
09-Sep-2004

busy_sdcch,5,9 400
busy_tch,0 1
busy_tch,4,0 0
busy_tch,4,1 1
busy_tch,4,2 3
busy_tch,4,3 5
busy_tch,4,4 7
busy_tch,4,5 9
busy_tch,4,6 11
busy_tch,4,7 13
busy_tch,4,8 15
busy_tch,4,9 17
busy_tch,5,0 0
busy_tch,5,1 2
busy_tch,5,2 4
busy_tch,5,3 6
busy_tch,5,4 8
busy_tch,5,5 10
busy_tch,5,6 12
busy_tch,5,7 14
busy_tch,5,8 16
busy_tch,5,9 400
busy_tch_carr,0 1
{4322} busy_tch_hr_amr,0 0
{4322} busy_tch_hr_amr,4,0 0
Cont.
6-78 68P02900W22-Q
09-Sep-2004

{4322} busy_tch_carr_hr_amr,0 0
{4322} call_sp_vers_downgrade_monitor,0 0
calls_queued,0 0
calls_queued,2 2147483647
cell_flush_reqs,0 0
{4441} ch_req_unsvcd_pcu,0 0
chan_dl_tx_pwr_lvl,0 0
chan_dl_tx_pwr_lvl,4,0 0
Cont.
68P02900W22-Q 6-79
09-Sep-2004

chan_req_cause_atmpt,0 0
chan_ul_tx_pwr_lvl,0 0
chan_ul_tx_pwr_lvl,4,0 0
chan_req_ms_blk,0 0
chan_req_ms_blk,2 2147483647
chan_req_ms_fail,0 0
chan_req_ms_fail,2 2147483647
channel_reqs_rec,0 0
channel_reqs_reject,0 0
channel_reqs_success,0 0
cipher_mode_fail,0 0
cipher_mode_fail,2 2147483647
Cont.
6-80 68P02900W22-Q
09-Sep-2004

classmk_update_fail,0 0
classmk_update_fail,2 2147483647
clr_cmd_from_msc,0 0
clr_req_to_msc,0 0
coding_scheme_change,0 0
congest_exist_ho_atmpt,0 0
congest_stand_ho_atmpt,0 0
congestion_lost_msu,0 0
congestion_lost_msu,2 2147483647
{4445} cong_rel_dl_scts,0 0
conn_refused,0 0
conn_req_to_msc,0 0
cpu_usage,0 0
cpu_usage,4,0 0
cpu_usage,4,1 11
cpu_usage,4,2 21
cpu_usage,4,3 31
cpu_usage,4,4 41
cpu_usage,4,5 51
cpu_usage,4,6 61
cpu_usage,4,7 71
cpu_usage,4,8 81
cpu_usage,4,9 91
cpu_usage,5,0 10
cpu_usage,5,1 20
cpu_usage,5,2 30
cpu_usage,5,3 40
cpu_usage,5,4 50
cpu_usage,5,5 60
cpu_usage,5,6 70
cpu_usage,5,7 80
cpu_usage,5,8 90
cpu_usage,5,9 100
cs12_on_32k_chan,0 0
Cont.
68P02900W22-Q 6-81
09-Sep-2004

dl_busy_pdtch,0 0
dl_busy_pdtch,4,0 0
dl_busy_pdtch,4,1 1
dl_busy_pdtch,4,2 3
dl_busy_pdtch,4,3 5
dl_busy_pdtch,4,4 7
dl_busy_pdtch,4,5 9
dl_busy_pdtch,4,6 11
dl_busy_pdtch,5,0 0
dl_busy_pdtch,5,1 2
dl_busy_pdtch,5,2 4
dl_busy_pdtch,5,3 6
dl_busy_pdtch,5,4 8
dl_pdtch_congestion,0 0
dl_pdtch_q_length,0 0
dl_pdtch_seizure,0 0
{23658} dl_radio_blks_1_ts,0 0
{23658} dl_rlc_ack_new_blks,0 0
{23658} dl_rlc_ddtr_blks,0 0
{23658} dl_rlc_nack_blks,0 0
{23658} dl_rlc_retx_blks,0 0
{23658} dl_rlc_stalled _blks,0 0
{23658} dl_rlc_unack_new_blks,0 0
Cont.
6-82 68P02900W22-Q
09-Sep-2004

{23658} dl_tbf_time_1_ts,0 0
{23658} dl_tbf_time_2_ts,0 0
{23658} dl_tbf_time_3_ts,0 0
{23658} dl_tbf_time_4_ts,0 0
dynet_assign_fail,0 0
dynet_call_rejects,0 0
efr_req_from_msc,0 0
{23658} egprs_64k_channels_switched,0 0
{23658} egprs_64k_not_avail,0 0
{23658} egprs_dl_asgn_pccch,0 0
{23658} egprs_avail_pdtch,0 0
er_intra_cell_ho_atmpt,0 0
er_intra_cell_ho_suc,0 0
fer,0 0
{4322} fer_amr_fr,0 0
{4322} fer_amr_hr,0 0
flow_control_barred,0 0
frmr,0 0
frmr,2 2147483647
gbl_link_ins,0 0
gbl_dl_data_thrput,0 0
gbl_flow_ctrl_sent,0 0
gbl_paging_reqs,0 0
gbl_dl_data_thrput_hist,0 0
gbl_dl_data_thrput_hist,4,0 0
Cont.
68P02900W22-Q 6-83
09-Sep-2004

gbl_ul_data_thrput_hist,0 0
gbl_ul_data_thrput_hist,4,0 0
gbl_ul_data_thrput,0 0
gbl_unavailable,0 0
gprs_access_per_agch,0 0
Cont.
6-84 68P02900W22-Q
09-Sep-2004

gprs_access_per_rach,0 0
gprs_avail_pdtch,0 0
gprs_cell_reselect_attmpt,0 0
gprs_cell_reselect_fail,0 0
gprs_channels_switched,0 0
gprs_32k_channels_switched,0 0
gprs_32k_dl_not_avail,0 0
gprs_32k_ul_not_avail,0 0
{3723} gprs_dl_asgn_pccch,0 0
gprs_dynet_failures,0 0
gprs_dynet_res_reqs,0 0
gprs_dynet_swi_reqs,0 0
gprs_dynet_res_reqs,4,0 0
gprs_dynet_swi_reqs,4,0 0
Cont.
68P02900W22-Q 6-85
09-Sep-2004

gprs_ms_neighbor_strong,0 0
gprs_pch_agch_q_length,0 0
{3723} gprs_ppch_pagch_q_length,0 0
{4441} gprs_prr_blk_usg,0 0
{4441} gprs_prr_blk_usg,4,0 0
Cont.
6-86 68P02900W22-Q
09-Sep-2004

{4441} gprs_rach_arrival,0 0
{4441}gprs_rach_arrival,4,0 0
{4441} gprs_rach_arrival,4,1 3
{4441}gprs_rach_arrival,4,8 101
{4441} g_rach_unsvcd_bts,0 0
ho_fail_no_resources,0 0
{4322} ho_req_from_msc,0 0
ho_req_msc_fail,0 0
ho_req_msc_fail,2 2147483647
Cont.
68P02900W22-Q 6-87
09-Sep-2004

ho_req_msc_ok,0 0
ho_req_msc_proto,0 0
ho_req_msc_proto,2 2147483647
i_frames_rx,0 0
i_frames_tx,0 0
idle_pdtch_intf_band0,0 0
idle_tch_intf_band0,0 0
imm_assgn_cause,0 0
in_inter_bss_ho,0 1
in_intra_bss_ho,0 1
in_intra_bss_nc_atmpt,0 0
in_intra_bss_nc_suc,0 0
interband_activity,0 0
intf_on_idle,0 0
intf_on_idle,4,0 0
intf_on_idle,4,1 6
intf_on_idle,4,2 11
intf_on_idle,4,3 16
intf_on_idle,4,4 21
intf_on_idle,4,5 26
intf_on_idle,4,6 31
intf_on_idle,4,7 36
intf_on_idle,4,8 41
intf_on_idle,4,9 46
intf_on_idle,5,0 5
intf_on_idle,5,1 10
Cont.
6-88 68P02900W22-Q
09-Sep-2004

intf_on_idle,5,2 15
intf_on_idle,5,3 20
intf_on_idle,5,4 25
intf_on_idle,5,5 30
intf_on_idle,5,6 35
intf_on_idle,5,7 40
intf_on_idle,5,8 45
intf_on_idle,5,9 65
intra_bss_ho,0 0
intra_bss_ho_cause_suc,0 0
intra_cell_ho,0 1
inv_est_cause_on_rach,0 0
invalid_frames_rx,0 0
invalid_frames_rx,2 2147483647
l_routing_syntax,0 0
l_routing_syntax,2 2147483647
l_routing_unknown,0 0
l_routing_unknown,2 2147483647
l_sccp_msgs,0 0
l_sccp_msgs_rx,0 0
l_sccp_msgs_tx,0 0
l_sif_sio_rx_opc,0 0
l_sif_sio_tx_dpc,0 0
l_sif_sio_type,0 0
l_sl_stop_congestion,0 0
lmtp_changeback,0 0
lmtp_changeover,0 0
lmtp_congestion,0 0
lmtp_congestion_lost_msu,0 0
lmtp_congestion_lost_msu,2 2147483647
lmtp_link_ins,0 0
lmtp_linkfail,0 0
lmtp_local_busy,0 0
lmtp_local_mgt,0 0
Cont.
68P02900W22-Q 6-89
09-Sep-2004

lmtp_local_sl_congestion,0 0
lmtp_local_sl_congestion,2 2147483647
lmtp_mgt_inhibit,0 0
lmtp_mgt_uninhibit,0 0
lmtp_msu_discarded,0 0
lmtp_msu_discarded,2 2147483647
lmtp_msu_rx,0 0
lmtp_msu_tx,0 0
lmtp_neg_acks,0 0
lmtp_neg_acks,2 2147483647
lmtp_re_tx,0 0
lmtp_re_tx,2 2147483647
lmtp_remote_mgt,0 0
lmtp_remote_proc,0 0
lmtp_remote_sl_congestion,0 0
lmtp_remote_sl_congestion,2 2147483647
lmtp_restoration,0 0
lmtp_sib_rx,0 0
lmtp_sib_tx,0 0
lmtp_sif_sio_rx,0 0
lmtp_sif_sio_tx,0 0
lmtp_sl_ack,0 0
lmtp_sl_ack,2 2147483647
lmtp_sl_alignment,0 0
lmtp_sl_alignment,2 2147483647
lmtp_sl_error_rate,0 0
lmtp_sl_error_rate,2 2147483647
lmtp_sl_fail,0 0
lmtp_sl_fail,2 2147483647
lmtp_sl_fibr,0 0
lmtp_sl_fibr,2 2147483647
lmtp_start_rpo,0 0
lmtp_start_rpo,2 2147483647
lmtp_stop_rpo,0 0
Cont.
6-90 68P02900W22-Q
09-Sep-2004

lmtp_su_error,0 0
lmtp_lmtp_su_error,2 2147483647
lmtp_unavailable,0 0
ma_cmd_to_ms,0 0
ma_cmd_to_ms_blkd,0 1
ma_cmd_to_ms_blkd,2 2147483647
ma_complete_from_ms,0 0
ma_complete_to_msc,0 0
ma_fail_from_ms,0 0
ma_fail_from_ms,2 2147483647
ma_req_from_msc,0 1
ma_req_from_msc_fail,0 0
ma_req_from_msc_fail,2 2147483647
ms_access_by_type,0 0
ms_class_1_10_req,0 0
The statistics ms_class_1_10_req,0, ms_class_11_20_req,0 and ms_class_21_29_req,0 are not

available if the EGPRS option is purchased.

ms_tch_usage_by_type,0 0
msu_discarded,0 0
msu_discarded,2 2147483647
mt_lts_on_sdcch,0 0
mtp_changeback,0 0
mtp_changeover,0 0
mtp_congestion,0 0
mtp_link_ins,0 0
mtp_linkfail,0 0
mtp_local_busy,0 0
Cont.
68P02900W22-Q 6-91
09-Sep-2004

mtp_local_mgt,0 0
mtp_mgt_inhibit,0 0
mtp_mgt_uninhibit,0 0
mtp_msu_rx,0 0
mtp_msu_tx,0 0
mtp_neg_acks,0 0
mtp_neg_acks,2 2147483647
mtp_re_tx,0 0
mtp_re_tx,2 2147483647
mtp_remote_mgt,0 0
mtp_remote_proc,0 0
mtp_restoration,0 0
mtp_sif_sio_rx,0 0
mtp_sif_sio_tx,0 0
mtp_sl_ack,0 0
mtp_sl_ack,2 2147483647
mtp_sl_alignment,0 0
mtp_sl_alignment,2 2147483647
mtp_sl_congestion,0 0
mtp_sl_congestion,2 2147483647
mtp_sl_error_rate,0 0
mtp_sl_error_rate,2 2147483647
mtp_sl_fail,0 0
mtp_sl_fail,2 2147483647
mtp_sl_fibr,0 0
mtp_sl_fibr,2 2147483647
mtp_start_rpo,0 0
mtp_start_rpo,2 2147483647
mtp_stop_rpo,0 0
mtp_su_error,0 0
mtp_su_error,2 2147483647
mtp_unavailable,0 0
n2_expiry,0 0
n2_expiry,2 2147483647
Cont.
6-92 68P02900W22-Q
09-Sep-2004

no_pdtch_avail 0
no_pdtch_avail_time 0
num_emerg_access,0 0
num_emerg_rejected,0 0
num_emerg_tch_kill,0 0
num_emerg_term_sdcch,0 0
ok_acc_proc,0 1
ok_acc_proc_suc_rach,0 0
out_ho_cause_atmpt,0 0
out_inter_bss_ho,0 1
out_inter_ho,0 0
out_intra_bss_ho,0 1
out_intra_bss_nc_atmpt,0 0
out_intra_bss_nc_suc,0 0
page_req_from_msc,0 0
page_req_from_msc_fail,0 0
page_req_from_msc_fail,2 2147483647
page_req_from_smlc_fail,0 0
page_req_from_smlc_fail,2 2147483647
paging_requests,0 0
path_balance,0 0
path_balance,4,0 0
path_balance,4,1 30
path_balance,4,2 50
path_balance,4,3 70
path_balance,4,4 90
path_balance,4,5 110
path_balance,5,0 29
path_balance,5,1 49
path_balance,5,2 69
Cont.
68P02900W22-Q 6-93
09-Sep-2004

path_balance,5,3 89
pch_agch_q_length,0 0
pch_q_page_discard,0 0
{3723} ppch_q_page_discard,0 0
prp_load,0 0
prp_load,4,0 0
prp_load,4,1 3
prp_load,4,2 6
prp_load,4,3 11
prp_load,4,4 21
prp_load,4,5 41
prp_load,4,6 61
prp_load,4,7 101
prp_load,4,8 161
prp_load,4,9 261
prp_load,5,0 2
prp_load,5,1 5
prp_load,5,2 10
prp_load,5,3 20
prp_load,5,4 40
prp_load,5,5 60
prp_load,5,6 100
prp_load,5,7 160
prp_load,5,8 260
prp_load,5,9 400
rber,0 0
rf_losses_sd,0 1
rf_losses_sd,2 2147483647
Cont.
6-94 68P02900W22-Q
09-Sep-2004

rf_losses_tch,0 1
rf_losses_tch,2 2147483647
{4322} rf_losses_tch_hr_amr,0 0
roc,0 0
roc,4,0 0
roc,4,1 7
roc,4,2 14
roc,4,3 21
roc,4,4 28
roc,4,5 35
roc,4,6 42
roc,4,7 49
roc,4,8 55
roc,4,9 64
roc,5,0 6
roc,5,1 13
roc,5,2 20
roc,5,3 27
roc,5,4 34
roc,5,5 41
roc,5,6 48
roc,5,7 54
roc,5,8 63
roc,5,9 219
routing_syntax,0 0
routing_syntax,2 2147483647
routing_unknown,0 0
routing_unknown,2 2147483647
sabm_tx,0 0
sccp_msgs,0 0
sccp_msgs_rx,0 0
sccp_msgs_tx,0 0
sdcch_congestion,0 0
second_assign_atmpt,0 0
Cont.
68P02900W22-Q 6-95
09-Sep-2004

second_assign_suc,0 0
sif_sio_rx_opc,0 0
sif_sio_tx_dpc,0 0
sif_sio_type,0 0
sl_congestion,0 0
sl_congestion,2 2147483647
sl_stop_congestion,0 0
sms_init_on_sdcch,0 0
sms_init_on_tch,0 0
sms_no_bcast_msg,0 0
tch_cong_inner_zone,0 0
tch_congestion,0 0
{4322} tch_congestion_hr_amr,0 0
{4322} tch_cong_inner_zone_hr_amr,0 0
tch_delay,0 0
tch_delay,4,0 0
tch_delay,4,1 10001
tch_delay,4,2 20001
tch_delay,4,3 30001
tch_delay,4,4 40001
tch_delay,4,5 50001
tch_delay,4,6 60001
tch_delay,4,7 70001
tch_delay,4,8 80001
tch_delay,4,9 90001
tch_delay,5,0 10000
tch_delay,5,1 20000
tch_delay,5,2 30000
tch_delay,5,3 40000
tch_delay,5,4 50000
tch_delay,5,5 60000
tch_delay,5,6 70000
tch_delay,5,7 80000
tch_delay,5,8 90000
Cont.
6-96 68P02900W22-Q
09-Sep-2004

tch_delay,5,9 100000
tch_q_length,0 0
tch_q_length,4,0 0
tch_q_length,4,1 1
tch_q_length,4,2 2
tch_q_length,4,3 3
tch_q_length,4,4 4
tch_q_length,4,5 5
tch_q_length,4,6 6
tch_q_length,4,7 7
tch_q_length,4,8 8
tch_q_length,4,9 9
tch_q_length,5,0 0
tch_q_length,5,1 1
tch_q_length,5,2 2
tch_q_length,5,3 3
tch_q_length,5,4 4
tch_q_length,5,5 5
tch_q_length,5,6 6
tch_q_length,5,7 7
tch_q_length,5,8 8
tch_q_length,5,9 255
tch_q_removed,0 1
tch_usage,0 0
tch_usage_ext_range,0 0
tch_usage_inner_zone,0 0
total_calls,0 1
u_ber,0 0
u_ber,4,0 0
u_ber,4,1 1
u_ber,4,2 2
u_ber,4,3 3
u_ber,4,4 4
u_ber,4,5 5
Cont.
68P02900W22-Q 6-97
09-Sep-2004

u_ber,4,6 6
u_ber,4,7 7
u_ber,4,8 8
u_ber,4,9 9
u_ber,5,0 0
u_ber,5,1 1
u_ber,5,2 2
u_ber,5,3 3
u_ber,5,4 4
u_ber,5,5 5
u_ber,5,6 6
u_ber,5,7 7
u_ber,5,8 8
u_ber,5,9 9
ul_busy_pdtch,0 0
ul_busy_pdtch,4,0 0
ul_busy_pdtch,4,1 1
ul_busy_pdtch,4,2 3
ul_busy_pdtch,4,3 5
ul_busy_pdtch,4,4 7
ul_busy_pdtch,4,5 9
ul_busy_pdtch,4,6 11
ul_busy_pdtch,5,0 0
ul_busy_pdtch,5,1 2
ul_busy_pdtch,5,2 4
ul_busy_pdtch,5,3 6
ul_busy_pdtch,5,4 8
Cont.
6-98 68P02900W22-Q
09-Sep-2004

ul_pdtch_congestion,0 0
ul_pdtch_q_length,0 0
ul_pdtch_seizure,0 0
{23658} ul_radio_blks_gmsk_1_ts,0 0
{23658} ul_radio_blks_gmsk_2_ts,0 0
{23658} ul_radio_blks_8psk_1_ts,0 0
{23658} ul_radio_blks_8psk_2_ts,0 0
{23658} ul_rlc_ack_new_blks,0 0
{23658} ul_rlc_retx_blks,0 0
{23658} ul_rlc_unack_new_blks,0 0
{23658} ul_tbf_time_gmsk_1_ts,0 0
{23658} ul_tbf_time_gmsk_2_ts,0 0
{23658} ul_tbf_time_8psk_1_ts,0 0
{23658} ul_tbf_time_8psk_2_ts,0 0
uplink_path_loss,0 0
uplink_path_loss,4,0 47
Cont.
68P02900W22-Q 6-99
09-Sep-2004

zone_change_atmpt,0 0
zone_change_suc,0 0
Statistics table elements for GSM Half Rate
{22064}
Table 6-23 shows the new and modified Statistics table elements for GSM Half Rate and their recommended
values.
Table 6-23 Statistics table - elements for GSM Half Rate

{22064} alloc_tch_fail_hr,0 0
{22064} alloc_tch_hr,0 0
{22064} available_tch_hr,0 0
{22064} busy_tch_hr,0 0
{22064} busy_tch_hr,4,0 0
{22064} busy_tch_hr,4,1 1
{22064} busy_tch_hr,4,2 3
{22064} busy_tch_hr,4,3 5
{22064} busy_tch_hr,4,4 7
{22064} busy_tch_hr,4,5 9
{22064} busy_tch_hr,4,6 11
{22064} busy_tch_hr,4,7 13
{22064} busy_tch_hr,4,8 15
{22064} busy_tch_hr,4,9 17
{22064} busy_tch_hr,5,0 0
{22064} busy_tch_hr,5,1 2
{22064} busy_tch_hr,5,2 4
Cont.
6-100 68P02900W22-Q
09-Sep-2004
Table 6-23 Statistics table - elements for GSM Half Rate (Continued)
{22064} busy_tch_hr,5,3 6
{22064} busy_tch_hr,5,4 8
{22064} busy_tch_hr,5,5 10
{22064} busy_tch_hr,5,6 12
{22064} busy_tch_hr,5,7 14
{22064} busy_tch_hr,5,8 16
{22064} busy_tch_hr,5,9 400
{22064} busy_tch_carr_hr,0 1
{22064} rf_losses_tch_hr,0 0
{22064} tch_congestion_hr,0 0
{22064} tch_cong_inner_zone_hr,0 0
{22064} fer_gsm_hr 0
{22064} ho_req_ack_to_msc 0
68P02900W22-Q 6-101
09-Sep-2004
Specifics table Chapter 6: MCDF tables
Specifics table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Specifics table
The Specifics table (Table 6-24) 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.
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, Timers, or Statistics table because
of restrictions such as the following: elements that have no specific default value, or elements
that are specific to particular site/cell configurations, for example, elements only supported at
Horizonoffice.
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
6-102 68P02900W22-Q
09-Sep-2004
System Information: DataGen Specifics table
Table 6-24 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.
Site Number 3 0-120, 251, 252 and 253. Mandatory.
This field is used to identify the site at which the specific value is required.
* From 1515 and prior to 1620 RXCDR areas:
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-Q 6-103
09-Sep-2004
Table 6-25 lists the parameters supported in the Specifics table:

Table 6-25 Specifics table - elements
access_per_agch,0
access_per_pch,0
{3723} access_per_ppch,0
access_per_rach,0
air_dl_control_blks,0
air_ul_control_blks,0
air_dl_data_blks,0
air_ul_data_blks,0
The statistics air_dl_data_blks and air_ul_data_blks are not available if the EGPRS option
is purchased.
{4445} air_dl_tbf_failures,0
{4445} air_ul_tbf_failures,0
adap_ho_alt_trigger_rxqual
adap_ho_pbgt
adap_ho_rxlev
adap_ho_rxqual
adap_trigger_hop_rxqual_dl
adap_trigger_hop_rxqual_ul
adap_trigger_pbgt
adap_trigger_rxlev_dl
adap_trigger_rxlev_ul
adap_trigger_rxqual_dl
adap_trigger_rxqual_ul
alloc_sdcch,0
alloc_sdcch_fail,0
alloc_sdcch_fail,2
alloc_sdcch_carr,0
alloc_tch,0
alloc_tch_carr,0
Cont.
6-104 68P02900W22-Q
09-Sep-2004
alloc_tch_fail,0
alloc_tch_fail,2
{4322} alloc_tch_fail_hr_amr,0
alloc_tch_fail_inner_zone,0
alloc_tch_inner_zone,0
{4322} alloc_tch_hr_amr,0
alt_qual_proc
{4322} amr_fr_dl_codec_mode_usage,0
{4322} amr_fr_ul_codec_mode_usage,0
{4322} amr_hr_dl_codec_mode_usage,0
{4322} amr_hr_ul_codec_mode_usage,0
amr_fr_dl_adaption,0
amr_fr_ul_adaption,0
amr_hr_dl_adaption,0
amr_hr_ul_adaption,0
amr_increase_thresh_adjust,0
amr_decrease_thresh_adjust,0
{4322} amr_fr_dl_la_enabled
{4322} amr_fr_ul_la_enabled
{4322} amr_hr_dl_la_enabled
{4322} amr_hr_ul_la_enabled
{4322} amr_hr_res_ts
{4322} amr_hr_intracell_ho_allowed
{4322} amr_hop_count
{4322} amr_inner_hr_usage_thres
{4322} amr_half_rate_enabled
{4322} amr_full_rate_enabled
{4322} amr_new_calls_hr
{4322} amr_reconfig_fr_to_hr
{4415} ater_channel_status,0
{4415} ater_emerg_preempt_status,0
attach_detach
available_pdtch,0
auto_rf_loss_trace
available_sdcch,0
Cont.
68P02900W22-Q 6-105
09-Sep-2004
available_tch,0
available_tch,4,0
available_tch,4,1
available_tch,4,2
available_tch,4,3
available_tch,4,4
available_tch,4,5
available_tch,4,6
available_tch,4,7
available_tch,4,8
available_tch,4,9
available_tch,5,0
available_tch,5,1
available_tch,5,2
available_tch,5,3
available_tch,5,4
available_tch,5,5
available_tch,5,6
available_tch,5,7
available_tch,5,8
available_tch,5,9
{4322} available_tch_hr_amr,0
bad_ho_refnum_ms,0
bad_ho_refnum_ms,2
band_preference
band_preference_mode
{23658} bep_period
{23658} bep_period2
ber,0
ber_loss_daily
ber_loss_hourly
bounce_protect_margin
bounce_protect_cong_tmr
bounce_protect_qual_tmr
bs_pa_mfrms
Cont.
6-106 68P02900W22-Q
09-Sep-2004
{3723} bs_pag_blks_res
{3723} bs_pbcch_blks
{3723}bs_pcc_chans
{3723} bs_prach_blks
bssgp_block_retries
bssgp_fc_period_c
bssgp_flow_control
bssgp_racap_retries
bssgp_reset_retries
bssgp_scheduling
bssgp_t1_timer
bssgp_t2_timer
bssgp_t2_timer
bss_msc_overload_allowed
bts_escalation
bts_p_con_ack
bts_p_con_interval
bts_power_control_allowed
bts_txpwr_max_inner
busy_sdcch,0
busy_sdcch,4,0
busy_sdcch,4,1
busy_sdcch,4,2
busy_sdcch,4,3
busy_sdcch,4,4
busy_sdcch,4,5
busy_sdcch,4,6
busy_sdcch,4,7
busy_sdcch,4,8
busy_sdcch,4,9
busy_sdcch,5,0
busy_sdcch,5,1
busy_sdcch,5,2
busy_sdcch,5,3
busy_sdcch,5,4
Cont.
68P02900W22-Q 6-107
09-Sep-2004
busy_sdcch,5,5
busy_sdcch,5,6
busy_sdcch,5,7
busy_sdcch,5,8
busy_sdcch,5,9
{4322} busy_tch_hr_amr,0
{4322} busy_tch_hr_amr,4,0
{4322} busy_tch_carr_hr_amr,0
busy_tch,0
busy_tch,4,0
busy_tch,4,1
busy_tch,4,2
busy_tch,4,3
busy_tch,4,4
busy_tch,4,5
busy_tch,4,6
Cont.
6-108 68P02900W22-Q
09-Sep-2004
busy_tch,4,7
busy_tch,4,8
busy_tch,4,9
busy_tch,5,0
busy_tch,5,1
busy_tch,5,2
busy_tch,5,3
busy_tch,5,4
busy_tch,5,5
busy_tch,5,6
busy_tch,5,7
busy_tch,5,8
busy_tch,5,9
bvci
{3723} c31_hyst
{3723} c32_qual
call_trace_options
called_pci
calling_pci
calls_queued,0
calls_queued,2
carrier_disable_time
carriers_ins_pwr_fail
cbc_fast_select
cbc_intface_vers
cbc_vbind_cntr
cbs_outage_cntr
cbch_enabled
ccch_load_period
cell_bar_access_class
cell_bar_access_switch
cell_bar_qualify
cell_flush_reqs,0
cell_reselect_offset
cell_reselect_param_ind
Cont.
68P02900W22-Q 6-109
09-Sep-2004
{4441} ch_req_unsvcd_pcu,0
chan_dl_tx_pwr_lvl,0
chan_dl_tx_pwr_lvl,4,0
chan_req_cause_atmpt,0
chan_ul_tx_pwr_lvl,0
chan_ul_tx_pwr_lvl,4,0
Cont.
6-110 68P02900W22-Q
09-Sep-2004
chan_req_ms_blk,0
chan_req_ms_blk,2
chan_req_ms_fail,0
chan_req_ms_fail,2
channel_reconfiguration_switch
channel_reqs_rec,0
channel_reqs_reject,0
channel_reqs_success,0
cipher_mode_fail,0
cipher_mode_fail,2
ciph_mode_rej_allowed
classmk_update_fail,0
classmk_update_fail,2
clk_src_fail_reset_period
clr_cmd_from_msc,0
clr_req_to_msc,0
coding_scheme_change,0
coincident_offset
confusion_msg_allowed
congest_at_source
congest_at_target
congest_exist_ho_atmpt,0
congest_stand_ho_atmpt,0
congestion_lost_msu,0
congestion_lost_msu,2
{4445} cong_rel_dl_scts
Cont.
68P02900W22-Q 6-111
09-Sep-2004
conn_refused,0
conn_req_to_msc,0
cp_option_reset_ckt
cp_option_rr_status
cpu_usage,0
cpu_usage,4,0
cpu_usage,4,1
cpu_usage,4,2
cpu_usage,4,3
cpu_usage,4,4
cpu_usage,4,5
cpu_usage,4,6
cpu_usage,4,7
cpu_usage,4,8
cpu_usage,4,9
cpu_usage,5,0
cpu_usage,5,1
cpu_usage,5,2
cpu_usage,5,3
cpu_usage,5,4
cpu_usage,5,5
cpu_usage,5,6
cpu_usage,5,7
cpu_usage,5,8
cpu_usage,5,9
cr_calling
cs34_enabled
crm_timer_value,0
crm_timer_value,1
crm_timer_value,2
crm_timer_value,3
crm_timer_value,4
crm_timer_value,5
crm_timer_value,6
crm_timer_value,7
Cont.
6-112 68P02900W22-Q
09-Sep-2004
crm_timer_value,8
crm_timer_value,9
crm_timer_value,10
crm_timer_value,11
crm_timer_value,12
crmpc_timer_value,0
crmpc_timer_value,1
crmpc_timer_value,2
crmpc_timer_value,3
crmpc_timer_value,4
crmpc_timer_value,5
crmpc_timer_value,6
crmpc_timer_value,7
crmpc_timer_value,8
cs12_on_32k_chan,0
d1_ba_alloc_proc
d1_missing_report
d1_ncell_proc
d1_sdcch_ho
d1_sdcch_timer_ho
decision_1_dl_rxlev_av_h
decision_1_dl_rxlev_av_ih
decision_1_dl_rxlev_av_p
decision_1_dl_rxqual_av_h
decision_1_dl_rxqual_av_p
decision_1_n1
decision_1_n2
decision_1_n3
decision_1_n4
decision_1_n5
decision_1_n6
decision_1_n7
decision_1_n8
decision_1_ncell_rxlev_av_h_calc
decision_1_p1
Cont.
68P02900W22-Q 6-113
09-Sep-2004
decision_1_p2
decision_1_p3
decision_1_p4
decision_1_p5
decision_1_p6
decision_1_p7
decision_1_p8
decision_1_p_bgt_rxlev_av_h
decision_1_tim_adv_av_alg
decision_1_ul_rxlev_av_h
decision_1_ul_rxlev_av_ih
decision_1_ul_rxlev_av_p
decision_1_ul_rxqual_av_h
decision_1_ul_rxqual_av_p
decision_alg_num
decision_alg_type
direct_inner_zone_threshold
disuse_cnt_hreqave
dl_audio_lev_offset
dl_busy_pdtch,0
dl_busy_pdtch,4,0
dl_busy_pdtch,4,1
dl_busy_pdtch,4,2
dl_busy_pdtch,4,3
dl_busy_pdtch,4,4
dl_busy_pdtch,4,5
dl_busy_pdtch,4,6
dl_busy_pdtch,4,7
dl_busy_pdtch,4,8
dl_busy_pdtch,4,9
dl_busy_pdtch,5,0
dl_busy_pdtch,5,1
dl_busy_pdtch,5,2
dl_busy_pdtch,5,3
dl_busy_pdtch,5,4
Cont.
6-114 68P02900W22-Q
09-Sep-2004
dl_busy_pdtch,5,5
dl_busy_pdtch,5,6
dl_busy_pdtch,5,7
dl_busy_pdtch,5,8
dl_busy_pdtch,5,9
dl_dtx_voice_data
dl_pdtch_congestion,0
dl_pdtch_q_length,0
dl_pdtch_seizure,0
{23658} dl_radio_blks_1_ts
{23658} dl_rlc_ack_new_blks
{23658} dl_rlc_ddtr_blks
{23658} dl_rlc_nack_blks
{23658} dl_rlc_retx_blks
{23658} dl_rlc_stalled _blks
{23658} dl_rlc_unack_new_blks
dl_rxlev_ho_allowed
dl_rxqual_ho_allowed
{23658} dl_tbf_time_1_ts
downlink_sync_timer
dr_chan_mode_modify
dr_ho_during_assign
dr_msc_preference
dr_preference
dr_standard_congest
dtx_required
dual_band_offset
dyn_step_adj
dyn_step_adj_fmpr
Cont.
68P02900W22-Q 6-115
09-Sep-2004
dynet_assign_fail,0
dynet_call_rejects,0
dynet_retry_time
dynet_tchs_reserved
efr_enabled
efr_req_from_msc,0
{23658} egprs_avail_pdtch
{23658} egprs_64k_channels_switched
{23658} egprs_64k_not_avail
{23658} egprs_dl_asgn_pccch
{23658} egprs_init_dl_cs
{23658} egprs_init_ul_cs
egsm_handover_threshold
emergency_class_switch
en_incom_ho
enhanced_relief
enh_ter_cic_mgt_ena_val
er_intra_cell_ho_atmpt,0
er_intra_cell_ho_suc,0
erc_ta_priority
extended_paging_active
fer,0
{4322} fer_amr_fr,0
{4322} ffer_amr_hr,0
flow_control_barred,0
frmr,0
frmr,2
full_pwr_rfloss
{4441} g_rach_unsvcd_bts,0
gbl_link_ins,0
gbl_dl_data_thrput,0
gbl_flow_ctrl_sent,0
gbl_paging_reqs,0
gbl_dl_data_thrput_hist,0
gbl_dl_data_thrput_hist,4,0
Cont.
6-116 68P02900W22-Q
09-Sep-2004
gbl_ul_data_thrput_hist_0
gbl_ul_data_thrput_hist,4,0
Cont.
68P02900W22-Q 6-117
09-Sep-2004
gbl_ul_data_thrput,0
gbl_unavailable,0
gprs_access_per_agch,0
gprs_access_per_rach,0
gprs_cell_reselect_attmpt,0
gprs_cell_reselect_fail,0
gprs_cell_reselect_hysteresis
gprs_channels_switched,0
gprs_32K_channels_switched,0
gprs_32K_dl_not_avail,0
gprs_32K_ul_not_avail,0
gprs_dl_asgn_pccch,0
gprs_dynet_failures,0
gprs_dynet_res_reqs,0
gprs_dynet_swi_reqs,0
gprs_dynet_res_reqs,4,0
Cont.
6-118 68P02900W22-Q
09-Sep-2004
gprs_dynet_swi_reqs,4,0
gprs_ms_neighbor_strong,0
gprs_pch_agch_q_length,0
gbl_thrput_period
gclk_qwarm_flag
global_reset_repetitions
gproc_slots
gprs_bs_cv_max
gprs_drx_timer_max
gprs_intraho_allwd
gprs_min_prr_blks
Cont.
68P02900W22-Q 6-119
09-Sep-2004
gprs_ms_pan_dec
gprs_ms_pan_inc
gprs_ms_pan_max
gprs_ms_txpwr_max_cch
gprs_pb
gprs_pc_alpha
gprs_pc_meas_chan
{3723} gprs_penalty_time
{3723} gprs_ppch_pagch__q_length,0
{4441} gprs_prr_blk_usg,0
{4441} gprs_prr_blk_usg,4,0
{4441} gprs_rach_arrival,0
{4441} gprs_rach_arrival,4,0
Cont.
6-120 68P02900W22-Q
09-Sep-2004
gprs_reconfig_thresh_idle_tch
{3723} gprs_reselect_offset
{3723} gprs_rxlev_access_min
gprs_sig_bvci
gprs_t3168
gprs_t3192
{3723} gprs_temporary_offset
gprs_ts_config_alg
gprs_smg30_t3192
group_block_unblock_allowed
gsm_cell_id_format
handover_recognized_period
handover_required_curr_ch
handover_required_reject_switch
{3723} hcs_thr
hdsl_losw_oos
hdsl_losw_restore
hdsl_snr_daily
hdsl_snr_daily_mon_period
Cont.
68P02900W22-Q 6-121
09-Sep-2004
hdsl_snr_hourly
hdsl_snr_hourly_mon_period
hdsl_snr_oos
hdsl_snr_restore
ho_ack
ho_complete
ho_exist_congest
ho_fail_no_resources,0
ho_margin_usage_flag
ho_only_max_pwr
ho_pwr_level_inner
{4322} ho_req_from_msc,0
ho_req_msc_fail,0
ho_req_msc_fail,2
ho_req_msc_ok,0
ho_req_msc_proto,0
ho_req_msc_proto,2
hop_count
hop_count_timer
hopping_support
hopping_systems_enabled,0
Cont.
6-122 68P02900W22-Q
09-Sep-2004
hopping_systems_hsn,0
i_frames_rx,0
i_frames_tx,0
idle_pdtch_intf_band,0,0
idle_tch_intf_band0,0
illegal_circuit_id
immediate_assign_mode
imm_assgn_cause
in_inter_bss_ho,0
in_intra_bss_ho,0
in_intra_bss_nc_atmpt,0
Cont.
68P02900W22-Q 6-123
09-Sep-2004
in_intra_bss_nc_suc,0
initial_sync_timer
intave
{4445} init_dl_cs
{4445} init_ul_cs
inter_cell_handover_allowed
interband_activity,0
interband_ho_allowed
interfer_bands,0
interfer_bands,1
interfer_bands,2
interfer_bands,3
interfer_bands,4
interfer_ho_allowed
intf_on_idle,0
intf_on_idle,4,0
intf_on_idle,4,1
intf_on_idle,4,2
intf_on_idle,4,3
intf_on_idle,4,4
intf_on_idle,4,5
intf_on_idle,4,6
intf_on_idle,4,7
intf_on_idle,4,8
intf_on_idle,4,9
intf_on_idle,5,0
intf_on_idle,5,1
intf_on_idle,5,2
intf_on_idle,5,3
intf_on_idle,5,4
intf_on_idle,5,5
intf_on_idle,5,6
intf_on_idle,5,7
intf_on_idle,5,8
intf_on_idle,5,9
Cont.
6-124 68P02900W22-Q
09-Sep-2004
intra_bss_ho,0
intra_bss_ho_cause_suc,0
intra_cell_handover_allowed
intra_cell_ho,0
inv_est_cause_on_rach,0
invalid_frames_rx,0
invalid_frames_rx,2
l_rxlev_dl_h
l_rxlev_dl_p
l_rxlev_ul_h
l_rxlev_ul_p
l_rxqual_dl_h
l_rxqual_dl_h_data
l_rxqual_dl_h_hopping
l_rxqual_dl_p
l_rxqual_dl_p_data
l_rxqual_dl_p_hopping
l_rxqual_ul_h
l_rxqual_ul_h_data
l_rxqual_ul_h_hopping
l_rxqual_ul_p
l_rxqual_ul_p_data
l_rxqual_ul_p_hopping
{4322} l_rxqual_ul_p_amr_fr
{4322} l_rxqual_ul_p_amr_hr
{4322} l_rxqual_ul_h_amr_fr
{4322} l_rxqual_ul_h_amr_hr
{4322} u_rxqual_ul_p_amr_hr
{4322} l_rxqual_ul_h_hopping_amr_fr
{4322} l_rxqual_ul_h_hopping_amr_hr
{4322} l_rxqual_ul_p_hopping_amr_fr
{4322} l_rxqual_ul_p_hopping_amr_hr
{4322} l_rxqual_dl_p_amr_fr
{4322} l_rxqual_dl_p_amr_hr
{4322} l_rxqual_dl_h_amr_fr
Cont.
68P02900W22-Q 6-125
09-Sep-2004
{4322} l_rxqual_dl_h_amr_hr
{4322} u_rxqual_dl_p_amr_hr
{4322} l_rxqual_dl_h_hopping_amr_fr
{4322} l_rxqual_dl_h_hopping_amr_hr
{4322} l_rxqual_dl_p_hopping_amr_fr
{4322} l_rxqual_dl_p_hopping_amr_hr
layer_number
link_about_to_fail
link_fail
local_maintenance
low_sig_thresh
lta_alarm_range
ltu_fw_auto_download
ma_cmd_to_ms,0
ma_cmd_to_ms_blkd,0
ma_cmd_to_ms_blkd,2
ma_complete_to_msc,0
ma_fail_from_ms,0
ma_fail_from_ms,2
ma_req_from_msc,0
ma_req_from_msc_fail,0
ma_req_from_msc_fail,2
max_gprs_ts_per_carrier
max_ms_dl_buffer
max_ms_dl_rate
max_q_length_full_rate_channel
max_q_length_immediate_assignments
max_q_length_sdcch
max_retran
max_rst_ckt_timer_exps
mb_tch_congest_thres
min_gprs_ts_per_carrier
6-126 68P02900W22-Q
09-Sep-2004
The parameter min_gprs_ts_per_carrier is not available if the EGPRS option is purchased.
mms_cat_enable
mms_config_type
ms_access_by_type,0
ms_class_1_10_req,0
ms_class_11,20_req,0
ms_class,21_29_req,0
The statistics ms_class_1_10_req,0, ms_class_11_20_req,0 and ms_class_21_29_req,0 are not

available if the EGPRS option is purchased.
ms_distance_allowed
ms_p_con_ack
ms_power_control_allowed
ms_power_level_period
ms_power_offset
ms_tch_usage_by_type,0
ms_txpwr_max_def
ms_txpwr_max_inner
mspwr_alg
mtl_loadshare_granularity
msu_discarded,0
msu_discarded,2
mt_lcs_on_sdcch,0
mtp_changeback,0
mtp_changeover,0
mtp_congestion,0
mtp_link_ins,0
mtp_linkfail,0
mtp_local_busy,0
mtp_local_mgt,0
Cont.
68P02900W22-Q 6-127
09-Sep-2004
mtp_mgt_inhibit,0
mtp_mgt_uninhibit,0
mtp_msu_rx,0
mtp_msu_tx,0
mtp_neg_acks,0
mtp_neg_acks,2
mtp_re_tx,0
mtp_re_tx,2
mtp_remote_mgt,0
mtp_remote_proc,0
mtp_restoration,0
mtp_sif_sio_rx,0
mtp_sif_sio_tx,0
mtp_sl_ack,0
mtp_sl_ack,2
mtp_sl_alignment,0
mtp_sl_alignment,2
mtp_sl_congestion,0
mtp_sl_congestion,2
mtp_sl_error_rate,0
mtp_sl_error_rate,2
mtp_sl_fail,0
mtp_sl_fail,2
mtp_sl_fibr,0
mtp_sl_fibr,2
mtp_start_rpo,0
mtp_start_rpo,2
mtp_stop_rpo,0
mtp_su_error,0
mtp_su_error,2
mtp_unavailable,0
multiband_reporting
n_avg
n_avg_i
n2_expiry,0
Cont.
6-128 68P02900W22-Q
09-Sep-2004
n2_expiry,2
no_pdtch_avail,0
no_pdtch_avail_time,0
ncc_of_plmn_allowed
neighbor_journal
neighbor_report_timer
ns_alive_retries
ns_alive_timer
ns_block_retries
ns_block_timer
ns_reset_period
ns_reset_timer
ns_test_timer
ns_unblock_retries
num_audit_retries
num_emerg_access,0
num_emerg_rejected,0
num_emerg_tch_kill,0
num_emerg_term_sdcch,0
num_gbl_dl_thrput_samples
num_gbl_ul_thrput_samples
number_of_preferred_cells
ok_acc_proc,0
ok_acc_proc_suc_rach,0
option_alg_a5_1
option_alg_a5_2
option_alg_a5_3
option_alg_a5_4
option_alg_a5_5
option_alg_a5_6
option_alg_a5_7
option_cbsms
option_emergency_preempt
out_ho_cause_atmpt,0
out_inter_bss_ho,0
Cont.
68P02900W22-Q 6-129
09-Sep-2004
out_intra_bss_ho,0
out_intra_bss_nc_atmpt,0
out_intra_bss_nc_suc,0
outer_zone_usage_level
override_intra_bss_pre_transfer
page_req_from_msc,0
page_req_from_msc_fail,0
page_req_from_msc_fail,2
paging_requests,0
path_balance,0
path_balance,4,0
path_balance,4,1
path_balance,4,2
path_balance,4,3
path_balance,4,4
path_balance,4,5
path_balance,4,6
path_balance,4,7
path_balance,4,8
path_balance,4,9
path_balance,5,0
path_balance,5,1
path_balance,5,2
path_balance,5,3
path_balance,5,4
path_balance,5,5
path_balance,5,6
path_balance,5,7
path_balance,5,8
path_balance,5,9
pbgt_mode
{3723} pccch_drx_timer_max
{3723} pccch_enabled
pch_agch_q_length,0
pch_q_page_discard,0
Cont.
6-130 68P02900W22-Q
09-Sep-2004
pcr_enable
pcr_n1
pcr_n2
penalty_time
{4441} percent_traf_cs
phase2_classmark_allowed
phase2_resource_ind_allowed
phase_lock_gclk
poor_initial_assignment
pool_gproc_preemption
pow_inc_step_size
pow_inc_step_size_dl
pow_inc_step_size_ul
pow_red_step_size
pow_red_step_size_dl
pow_red_step_size_ul
{3723} ppch_q_page_discard,0
{3723} prach_s
{3723} prach_tx_int
{4040} primary_pcu
prioritize_microcell
{3723} priority_class
protect_last_ts
prp_load,0
prp_load,4,0
prp_load,4,1
prp_load,4,2
prp_load,4,3
prp_load,4,4
prp_load,4,5
prp_load,4,6
prp_load,4,7
prp_load,4,8
prp_load,4,9
prp_load,5,0
Cont.
68P02900W22-Q 6-131
09-Sep-2004
prp_load,5,1
prp_load,5,2
prp_load,5,3
prp_load,5,4
prp_load,5,5
prp_load,5,6
prp_load,5,7
prp_load,5,8
prp_load,5,9
{3723} psi1_repeat_period
pwr_handover_allowed
pwrc
{3723} qsearch_p
queue_management_information
rac
ra_colour
{3723} ra_reselect_hysteresis
rach_load_period
rach_load_threshold
rach_load_type
radio_link_timeout
rapid_pwr_down
red_loss_daily
red_loss_hourly
red_loss_oos
red_loss_restore
red_time_oos
red_time_restore
reestablish_allowed
remote_loss_daily
remote_loss_daily_pcu
remote_loss_hourly
remote_loss_hourly_pcu
remote_loss_oos
remote_loss_oos_pcu
Cont.
6-132 68P02900W22-Q
09-Sep-2004
remote_loss_restore
remote_time_oos
remote_time_oos_pcu
remote_time_restore
remote_time_restore_pcu
report_resource_tch_f_high_water_mark
report_resource_tch_f_low_water_mark
res_gprs_pdchs
res_ts_less_one_carrier
rber,0
rf_losses_sd,0
rf_losses_sd,2
rf_losses_tch,0
rf_losses_tch,2
{4322} rf_losses_tch_hr_amr,0
rf_res_ind_period
roc,0
roc,4,0
roc,4,1
roc,4,2
roc,4,3
roc,4,4
roc,4,5
roc,4,6
roc,4,7
roc,4,8
roc,4,9
roc,5,0
roc,5,1
roc,5,2
roc,5,3
roc,5,4
roc,5,5
roc,5,6
roc,5,7
Cont.
68P02900W22-Q 6-133
09-Sep-2004
roc,5,8
roc,5,9
routing_syntax,0
routing_syntax,2
routing_unknown,0
routing_unknown,2
rpd_offset
rpd_period
rpd_trigger
rpt_bad_qual_no_mr
rrsm_timer_value,0
rrsm_timer_value,3
rrsm_timer_value,5
rrsm_timer_value,8
rrsm_timer_value,9
rrsm_timer_value,10
rrsm_timer_value,11
rrsm_timer_value,12
rrsm_timer_value,13
rrsm_timer_value,14
rrsm_timer_value,15
rrsm_timer_value,16
rrsm_timer_value,18
rrsmpc_timer_value,0
rrsmpc_timer_value,1
rrs_timer_values,0
rrs_timer_values,1
rrs_timer_values,2
rrs_timer_values,3
rrspc_timer_values,0
rrspc_timer_values,1
rxlev_dl_zone
rxlev_ul_zone
sabm_tx,0
sccp_bssap_mgt
Cont.
6-134 68P02900W22-Q
09-Sep-2004
sccp_msgs,0
sccp_msgs_rx,0
sccp_msgs_tx,0
sdcch_congestion,0
secondary_freq_type
sdcch_tch_band_reassign_delay
{3723} search_prio_3g
second_assign_atmpt,0
second_assign_suc,0
sif_sio_rx_opc,0
sif_sio_tx_dpc,0
sif_sio_type,0
sl_congestion,0
sl_congestion,2
sl_stop_congestion,0
slip_loss_daily
slip_loss_hourly
slip_loss_oos
slip_loss_restore
smg_gb_vers
smg_um_vers
sms_dl_allowed
sms_init_on_sdcch,0
sms_init_on_tch,0
sms_no_bcast_msg,0
sms_tch_chan
sms_ul_allowed
ss7_mode
ssm_critical_overload_threshold
ssm_normal_overload_threshold
ssmpc_timer_value
ssp_burst_delay
ssp_burst_limit
static_sync_timer
stat_interval
Cont.
68P02900W22-Q 6-135
09-Sep-2004
sw_ts_less_one_carrier
switch_gprs_pdchs
sync_loss_daily
sync_loss_daily_pcu
sync_loss_hourly
sync_loss_hourly_pcu
sync_loss_oos
sync_loss_oos_pcu
sync_loss_restore
sync_time_oos
sync_time_oos_pcu
sync_time_restore
sync_time_restore_pcu
t_avg_t
t_avg_w
tch_busy_critical_threshold
tch_busy_norm_threshold
tch_cong_inner_zone,0
tch_congestion,0
{4322} tch_congestion_hr_amr,0
{4322} tch_cong_inner_zone_hr_amr,
tch_congest_prevent_thres
tch_delay,0
tch_delay,4,0
tch_delay,4,1
tch_delay,4,2
tch_delay,4,3
tch_delay,4,4
tch_delay,4,5
tch_delay,4,6
tch_delay,4,7
tch_delay,4,8
tch_delay,4,9
tch_delay,5,0
tch_delay,5,1
Cont.
6-136 68P02900W22-Q
09-Sep-2004
tch_delay,5,2
tch_delay,5,3
tch_delay,5,4
tch_delay,5,5
tch_delay,5,6
tch_delay,5,7
tch_delay,5,8
tch_delay,5,9
tch_flow_control
tch_full_need_low_water_mark
tch_q_length,0
tch_q_length,4,0
tch_q_length,4,1
tch_q_length,4,2
tch_q_length,4,3
tch_q_length,4,4
tch_q_length,4,5
tch_q_length,4,6
tch_q_length,4,7
tch_q_length,4,8
tch_q_length,4,9
tch_q_length,5,0
tch_q_length,5,1
tch_q_length,5,2
tch_q_length,5,3
tch_q_length,5,4
tch_q_length,5,5
tch_q_length,5,6
tch_q_length,5,7
tch_q_length,5,8
tch_q_length,5,9
tch_usage,0
tch_usage_ext_range,0
tch_usage_inner_zone,0
temporary_offset
Cont.
68P02900W22-Q 6-137
09-Sep-2004
threshold
timing_advance_period
{23658} tlli_blk_coding
total_calls,0
trunk_critical_threshold
trunk_major_threshold
ts_alloc_flag
tsc_update_method
tx_integer
tx_power_cap
u_ber,0
u_ber,4,0
u_ber,4,1
u_ber,4,2
u_ber,4,3
u_ber,4,4
u_ber,4,5
u_ber,4,6
u_ber,4,7
u_ber,4,8
u_ber,4,9
u_ber,5,0
u_ber,5,1
u_ber,5,2
u_ber,5,3
u_ber,5,4
u_ber,5,5
u_ber,5,6
u_ber,5,7
u_ber,5,8
u_ber,5,9
u_rxlev_dl_ih
u_rxlev_dl_p
u_rxlev_ul_ih
u_rxlev_ul_p
Cont.
6-138 68P02900W22-Q
09-Sep-2004
u_rxqual_dl_p
u_rxqual_ul_p
ul_audio_lev_offset
ul_busy_pdtch,0
ul_busy_pdtch,4,0
ul_busy_pdtch,4,1
ul_busy_pdtch,4,2
ul_busy_pdtch,4,3
ul_busy_pdtch,4,4
ul_busy_pdtch,4,5
ul_busy_pdtch,4,6
ul_busy_pdtch,4,7
ul_busy_pdtch,4,8
ul_busy_pdtch,4,9
ul_busy_pdtch,5,0
ul_busy_pdtch,5,1
ul_busy_pdtch,5,2
ul_busy_pdtch,5,3
ul_busy_pdtch,5,4
ul_busy_pdtch,5,5
ul_busy_pdtch,5,6
ul_busy_pdtch,5,7
ul_busy_pdtch,5,8
ul_busy_pdtch,5,9
ul_pdtch_congestion,0
ul_pdtch_q_length,0
ul_pdtch_seizure,0
{23658} ul_radio_blks_gmsk_1_ts,0
{23658} ul_radio_blks_gmsk_2_ts,0
{23658} ul_radio_blks_8psk_1_ts,0
{23658} ul_radio_blks_8psk_2_ts,0
{23658} ul_rlc_ack_new_blks,0
{23658} ul_rlc_retx_blks,0
{23658} ul_rlc_unack_new_blks,0
{23658} ul_tbf_time_gmsk_1_ts,0
Cont.
68P02900W22-Q 6-139
09-Sep-2004
{23658} ul_tbf_time_gmsk_2_ts,0
{23658} ul_tbf_time_8psk_1_ts,0
{23658} ul_tbf_time_8psk_2_ts,0
ul_rxlev_ho_allowed
ul_rxqual_ho_allowed
unequipped_circuit_allowed
update_c
uplink_path_loss,0
uplink_path_loss,4,0
uplink_sync_timer
use_bcch_for_gprs
6-140 68P02900W22-Q
09-Sep-2004
The element use_bcch_for_gprs is not available if the EGPRS option is purchased.
use_derived_ho_power
use_neighbor_pbgt_hreqave
volume_control_type
wait_for_reselection
wait_indication_parameters
worse_neighbor_ho
zone_change_atmpt,0
zone_change_suc,0
zone_ho_hyst
Description of Specifics table for GSM Half Rate
{22064}
Table 6-26 lists the new and modified parameters supported in the Specifics table for GSM Half Rate.
Table 6-26 Specifics table - elements for GSM Half Rate
{22064} alloc_tch_hr,0
{22064} alloc_tch_fail_hr,0
{22064} available_tch_hr,0
{22064} busy_tch_carr_hr,0
{22064} busy_tch_hr,0
{22064} busy_tch_hr,4,0
{22064} busy_tch_hr,4,1
{22064} busy_tch_hr,4,2
{22064} busy_tch_hr,4,3
{22064} busy_tch_hr,4,4
{22064} busy_tch_hr,4,5
{22064} busy_tch_hr,4,6
{22064} busy_tch_hr,4,7
{22064} busy_tch_hr,4,8
Cont.
68P02900W22-Q 6-141
09-Sep-2004
Table 6-26 Specifics table - elements for GSM Half Rate (Continued)
{22064} busy_tch_hr,4,9
{22064} busy_tch_hr,5,0
{22064} busy_tch_hr,5,1
{22064} busy_tch_hr,5,2
{22064} busy_tch_hr,5,3
{22064} busy_tch_hr,5,4
{22064} busy_tch_hr,5,5
{22064} busy_tch_hr,5,6
{22064} busy_tch_hr,5,7
{22064} busy_tch_hr,5,8
{22064} busy_tch_hr,5,9
{22064} fer_gsm_hr
{22064} force_hr_usage
{22064} ho_req_ack_to_msc
{22064} hr_fr_hop_count
{22064} hr_intracell_ho_allowed
{22064} hr_res_ts
{22064} inner_hr_usage_thres
{22064} l_rxqual_dl_h_hopping_hr
{22064} l_rxqual_dl_h_hr
{22064} l_rxqual_dl_p_hopping_hr
{22064} l_rxqual_dl_p_hr
{22064} l_rxqual_ul_h_hopping_hr
{22064} l_rxqual_ul_h_hr
{22064} l_rxqual_ul_p_hopping_hr
{22064} l_rxqual_ul_p_hr
{22064} new_calls_hr
{22064} reconfig_fr_to_hr
{22064} rf_losses_tch_hr,0
{22064} tch_cong_inner_zone_hr,0
{22064} tch_congestion_hr,0
{22064} u_rxqual_dl_p_hr
{22064} u_rxqual_ul_p_hr
6-142 68P02900W22-Q
09-Sep-2004
System Information: DataGen RTF table
RTF table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of RTF table
This table contains details of the RTFs contained within the BSS area (refer to Table 6-27).
Default filename rtf.mcd
Table 6-27 RTF table

This field can be entered in decimal or hex. Hex numbers are to be followed by h or preceded by 0x;
The Site number, within the BSS, of the Site where this RTF is located.
First ID 2 0 to 50 to 23 Mandatory.
Horizonoffice
First device ID of the RTF.

Second ID 2 0 to 110 to 3 Mandatory.
Horizonoffice
Second device ID of the RTF.
68P02900W22-Q 6-143
09-Sep-2004
RTF table Chapter 6: MCDF tables

Primary Path ID 1 0 to 9 Mandatory. (If Site no.
is not 0 and DRI is not
redundant, otherwise
unused. Not required
for RTFs using Dynamic
Allocation.)
The Primary Path ID used in the associated RTF function.
Redundant Path ID 1 0 to 9 Optional.
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 See Frequency Type Mandatory if not a
Table below: 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 freq. 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.)
* From 1600, BCCH Frequency may be in extension band if egsm_bcch_sd is enabled in the Cell table.
KSW pair 1 0 to 3 Optional. (Mandatory
at non-M-Cell/non-
Horizonoffice sites,
otherwise unused.)
Used for the Managing KSW Pair prompt within the RTF equipage command.
6-144 68P02900W22-Q
09-Sep-2004

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 Reduction 2 -1 to 21 Optional. (Mandatory if
(trx_pwr_red) Cell Zone = 1.)
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 16Kbps 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 2 Optional. (Only valid if
Cell Zone = 0.)
Used for the Enter SDCCH load prompt within the RTF equipage command.
SDCCH Placement 3 0 to 250 Optional. (Only valid
Priority if SDCCH load is non
zero.)
Used for the Enter SDCCH placement priority prompt within the RTF equipage command.
Channel Allocation 3 0 to 250 Mandatory parameter in
Priority 1600.
Used for the Enter channel allocation priority prompt within the RTF equipage command.
Cont.
68P02900W22-Q 6-145
09-Sep-2004
RTF table Chapter 6: MCDF tables

Maximum GPRS 1 0 to 8 Optional.
PDCHs
Specifies the maximum number of PDCHs configured on the carrier. Only one GPRS carrier is allowed per
cell. res_gprs_pdch may not exceed max_pdch_gprs.
Reserve GPRS PDCHs 1 0 to 8 Optional.
Specifies the number of PDCHs for GPRS use only. These are never switched to circuit use except for
emergency calls.
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.
Allow 32k Trau 1 0 to 1 Optional - only prompted
for if the GPRS feature is
unrestricted, the carrier is
in the outer zone (that is,
call_zone set to 0), and
if the value entered for
the maximum number of
PDCHs is greater than
0. Not prompted for if
the RTF is sub-equipped
or dynamic allocation of
terrestrial resources is
enabled at the site.
Used for the prompt Is 32k kbps GPRS TRAU allowed (yes/no) within the RTF equipage command.
Allow 32k Trau is visible but not available if the EGPRS option is purchased. Refer to
pkt_radio_type for more information.

{23658}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.
Cont.
6-146 68P02900W22-Q
09-Sep-2004

{4322}
amr_half_rate_ 1 0 to 1 Optional.
enabled
Used to enable/disable AMR Half Rate at an RTF:
0 = disabled
1 = enabled.
{4415}Allow 8k Trau
1 0 to 1 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.
Description for GSM Half Rate
{22064}
Table 6-28 contains the parameters prompted for during the equipage of an RTF if both/either the AMR Half
Rate feature and/or GSM Half Rate feature is unrestricted.
Table 6-28 RTF table for GSM Half Rate

{22064} 1 0 to 1 Optional.
half_rate_enabled
Used to enable/disable GSM Half Rate at an RTF:
0 = disabled
1 = enabled.
68P02900W22-Q 6-147
09-Sep-2004
DRI table Chapter 6: MCDF tables
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-29).
The DRI must have its Cage and Slot number detailed in the Hardware table.
Default filename dri.mcd
Table 6-29 DRI table

The Site number, within the BSS, of the Site where this DRI is located.
First ID 2 0 to 50 to 23 Mandatory.
Horizonoffice
First device ID of the DRI.
6-148 68P02900W22-Q
09-Sep-2004
System Information: DataGen DRI table

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 MCELL/Horizonmacro site:
0 FOX
1 FMUX0
2 FMUX1
3 FMUX2
4 DIRECT
Note: Must be DIRECT for an M-Cellmicro site.

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 (MCell) Optional, only used for
1 to 24 (Horizonoffice) M-Cell/Horizonoffice
sites.
M-Cell: Transceiver Control Unit Port identifier.
Horizonoffice: LTU Connector number (range 1 to 24 )
68P02900W22-Q 6-149
09-Sep-2004

fm_cell_type 1 0 to 4 (depends on Mandatory (Not required
diversity_flag) at Horizonoffice sites).
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

Diversity 1 Boolean Mandatory (Not required
at Horizonoffice sites).
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 (Not required
at Horizonoffice sites).
Used for the antenna select number prompt within the RTF equipage command.
6-150 68P02900W22-Q
09-Sep-2004
System Information: DataGen DRI table

Assigned RTF first ID 1 0 to 5 Optional.
First device ID of the RTF to assign to this DRI.
Assigned RTF second 2 0 to 24 Optional.
ID
Second device ID of the RTF to assign to this DRI.
Opto Alarm State 2 0 to 1 Mandatory at
Horizonoffice sites.
Specifies the number alarm state for the optocoupler:
0 Normally closed
1 Normally open.

Opto Alarm Reporting 2 0 to 1 Optional.
Only valid at
Indicates whether or not the alarm is reported when the Optocoupler enters the alarm state.

Opto Alarm Index 2 0 to 33 Mandatory at
Specifies the alarm string displayed when an alarm is reported for the Optocoupler.
68P02900W22-Q 6-151
09-Sep-2004

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.
Valid for 1620 onwards and used to reference the associated combiner for this DRI.
Cavity Number 2 0 to 5 Optional.
Valid for 1620 onwards and used to reference the associated combiner for this DRI.
dri_density 1 1 to 2 Optional.
DRI density 2 is allowed only for HORIZON, HORIZON_MACRO, HORIZONMACRO2,
HORIZONMACRO2_EXT cabinets.
Assoc_dri_id 3 0 to 11 Mandatory when
dri_density is 2.
DRI density 2 is allowed only for HORIZON, HORIZON_MACRO, HORIZONMACRO2,
HORIZONMACRO2_EXT cabinets.
6-152 68P02900W22-Q
09-Sep-2004
System Information: DataGen Algorithm data table
Algorithm data table

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Algorithm data table
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-30 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
Cont.
68P02900W22-Q 6-153
09-Sep-2004
Algorithm data table Chapter 6: MCDF tables
Table 6-30 Algorithm data table (Continued)

Algorithm ID 1 0 to 3 Mandatory if
Algorithm Name is
not interfer_alg, unused
if it is.
This field gives the value for the algorithm ID/bin number field.
Algorithm Number 3 0 to 255. Mandatory.
This field gives the value for the algorithm number field.
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.
Only valid for 1.6.5.0.
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.
6-154 68P02900W22-Q
09-Sep-2004
System Information: DataGen Neighbour table
Neighbour table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Neighbour 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-31. 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-31 Neighbour table

BSS ID 3 0 to 255 Mandatory.
The bss_id of the BSS the source cell is in.
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 numbers will be
followed by h or preceded by 0x, for example, 1234h or 0x1234.
Neighbour LAC 6 6 digit numeric Mandatory.
The location area code of the neighbour. 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.
Neighbour RNC Id 5 4 digit numeric Mandatory, if a UMTS neighbour.
Neighbour CI 6 6 digit numeric Mandatory.

The location area code of the neighbour. 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.
Cont.
68P02900W22-Q 6-155
09-Sep-2004
Neighbour table Chapter 6: MCDF tables
Table 6-31 Neighbour table (Continued)

UTRAN Neighbor 4 3 digit numeric Mandatory, if a UMTS neighbour.
MNC
Sync 3 Boolean
Used to determine if the handovers between the cells is synchronized or not.
Pre 1.5.0.0 0 - Not synchronized
1 - Synchronized
From BSS 1.5.0.0 no - Not synchronized
yes - Synchronized
Coincident Cell 1 0 to 2 Optional. Only applies to internal
neighbours.
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 neighbouring cell.
Note that both neighbours 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 neighbours of one another.
ho_margin_cell 3 -24 to 31 Optional for both external and
internal neighbours.
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 neighbours.
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 neighbour cell
is external to BSS ID, not used if
neighbour 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.
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 neighbour on the ba_bcch list
ba_sacch Place the neighbour on the ba_sacch list.
Cont.
6-156 68P02900W22-Q
09-Sep-2004

both Place the neighbour on both the ba_bcch and ba_sacch lists.
empty field Place the neighbour on 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.
Note that 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_neighbour prompt: Add neighbour to the BA BCCH List (yes/no)?
BA SACCH List Type 3 Yes or No Optional.
Note that BA SACCH List Type must be set to Yes if the BA BCCH and BA GPRS List Types are set to
Used for the add_neighbour prompt: Add neighbour to the BA SACCH List (yes/no)?
BA GPRS List Type 3 Yes or No Optional.
Note that BA GPRS List Type must be set to Yes if the BA BCCH and BA SACCH List Types are set to
Used for the add_neighbour prompt: Add neighbour to the BA GPRS List (yes/no)?
Power Budget hreqave 2 1 to 31 Optional. BSS Microcellular option
purchased.
Used for the add_neighbor prompted parameter: Power budget surround cell hreqave.
Power Budget 2 1 to 7 Optional. BSS Microcellular option
Algorithm Type purchased.
Used for the add_neighbor prompted parameter: Power budget algorithm type.
Interfering Frequency 3 Boolean Optional. Only applicable where
Concentric Cells option purchased
AND inner_zone_alg is set to
interference for source cell
AND the neighbour 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 Handover 2 0 to 63 Optional. Only applicable if
Threshold Interfering Frequency is yes.
Used for the add_neighbor prompt: Enter the threshold for inner zone handover.
Inner Zone Handover 2 0 to 63 Optional. Only applicable if
Margin Interfering Frequency is yes.
Used for the add_neighbor prompt: Enter the margin for inner zone handover.
Uplink rxlev (serving 3 See below Optional. BSS Microcellular option
cell) purchased AND power budget
algorithm type is 3.
Range: Pre 1600: 0-63
Cont.
68P02900W22-Q 6-157
09-Sep-2004

From 1600: 0-255
Used for the add_neighbor prompted parameter: Uplink rxlev of serving cell.
Downlink rxlev 3 See below Optional. BSS Microcellular option
(serving cell) purchased AND power budget
Range: Pre 1600: 0-63
From 1600: 0-255
Used for the add_neighbor prompted parameter: Downlink rxlev of serving cell.
Qualifying Time 3 0 to 255 Optional. BSS Microcellular option
purchased AND power budget
Used for the add_neighbor prompted parameter: Qualifying time.
Qualifying Delay Time 3 0 to 255 Optional. BSS Microcellular option
Used for the add_neighbor prompted parameter: Qualifying delay time.
Neighbor Cell rxlev 2 0 to 63 Optional. BSS Microcellular option
Threshold purchased AND power budget
Used for the add_neighbor prompted parameter: Neighbor cell rxlev threshold.
Delay Time 3 0 to 255 Optional. BSS Microcellular option
Used for the add_neighbor prompted parameter: Delay time.
Handover Static Offset 3 0 to 127 Optional. BSS Microcellular option
Used for the add_neighbor prompted parameter: Handover static offset.
Handover Dynamic 3 0 to 127 Optional. BSS Microcellular option
Offset purchased AND power budget
Used for the add_neighbor prompted parameter: Handover dynamic offset.
Congestion Handover 3 -63 to 63 Optional. BSS Directed Retry
Margin option OR Alternate Congestion
Relief option purchased AND
neighbour is placed on a SACCH
list.
Used for the add_neighbor prompted parameter: Neighbor congestion handover margin.
Cont.
6-158 68P02900W22-Q
09-Sep-2004

Directed Retry Allowed 3 yes or no Optional. BSS Directed Retry
option purchased AND neighbour
is placed on a SACCH list AND
neighbour 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. From 1500 AND BSS
Directed Retry option purchased.
Used for the add_neighbor prompt: Enable channel interference avoidance test.
Rxlev Diff Adj Chan 3 -63 to 63 Optional. From 1500 AND
Intf Avoid Micro-Cellular option purchased
AND Channel Interference
Avoidance has a value of 1.
Used for the add_neighbor prompt: Rxlev difference for channel interference avoidance
test.
Adj Channel Intf HO 3 -63 to 63 Optional. From 1500 AND
Det Margin Micro-Cellular option purchased
AND Power Budget Algorithm
Type has a value of 7).
Used for the add_neighbor prompted parameter: Adjacent channel interference handover
detection margin.
Neighbour Range 8 Text EXTENDED or Optional. Only applicable when
NORMAL extended range cell option
purchased AND ext_range_cell is
enabled.
Used for the neighbour_range element of the add_neighbor command to allow the range to be extended or
normal range per neighbour.
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.
Neighbour 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.
Cont.
68P02900W22-Q 6-159
09-Sep-2004

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.

PCS1900 was formerly known as DCS2000.
6-160 68P02900W22-Q
09-Sep-2004
System Information: DataGen Throttles table
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-32.
Default filename thro.mcd
Table 6-32 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 3 0 to 254 Mandatory.
Specifies the throttle value.
68P02900W22-Q 6-161
09-Sep-2004
EAS table Chapter 6: MCDF tables
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-33.
Default filename eas.mcd
Table 6-33 EAS table

Alarm Index 2 0 to 33 Mandatory.
This field is used to identify the alarm number to give the string.
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.
6-162 68P02900W22-Q
09-Sep-2004
System Information: DataGen Daughter table
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 specifies
the full height cards at a site. Refer to Table 6-34.
Default filename dgtr.mcd
Table 6-34 Daughter table

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
non-M-Cell/Horizon sites,
otherwise unused).
The CAGE ID of the device.

Slot Number 2 0 to 28 Optional (Mandatory
at non-M-Cell/Horizon
sites, otherwise unused).
The slot number of the device.
68P02900W22-Q 6-163
09-Sep-2004
Daughter table Chapter 6: MCDF tables

Device Name 7 Text Mandatory.
The name of this device.
Device ID 3 0 to 255 (Valid range Mandatory.
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-164 68P02900W22-Q
09-Sep-2004
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-35.
Default filename pix.mcd
Table 6-35 PIX table

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 (opto coupler).
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 [N]o) Mandatory.
This field is used to decide whether to report the state changes (send alarm) for the specified Opto Number.
68P02900W22-Q 6-165
09-Sep-2004
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-36.
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).
Note that this command is invalid at M-Cell sites and will not be generated for these sites.
Default filename ksw.mcd
Table 6-36 KSW table

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)
Cont.
6-166 68P02900W22-Q
09-Sep-2004
System Information: DataGen KSW table
Table 6-36 KSW table (Continued)

for Highway 1)
for Highway 2)
68P02900W22-Q 6-167
09-Sep-2004
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-37.
Default filename nsvc.mcd
Table 6-37 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 1 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-168 68P02900W22-Q
09-Sep-2004
System Information: DataGen Hop table
Hop table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{3723}
Description of Hop table
The Hop table is used to specify the parameters of the chhg_hop_params command as in Table 6-38.
Default filename: hop.mcd
Table 6-38 Hop table

Site Number 6 6 digit Mandatory.
number
Used to identify the site at which the specific value is required.
LAC 6 6 digit Mandatory.
number
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.
CI 6 6 digit Mandatory.
number
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
Hopping Frequency 0 4 0 to 1023 Mandatory.
Mobile allocation ARFCN for FHI.
Hopping Frequency 1 4 0 to 1023 Optional.
Cont.
68P02900W22-Q 6-169
09-Sep-2004
Hop table Chapter 6: MCDF tables
Table 6-38 Hop table (Continued)

Cont.
6-170 68P02900W22-Q
09-Sep-2004

Cont.
68P02900W22-Q 6-171
09-Sep-2004
Hop table Chapter 6: MCDF tables

Cont.
6-172 68P02900W22-Q
09-Sep-2004

68P02900W22-Q 6-173
09-Sep-2004
ACS table Chapter 6: MCDF tables
ACS table
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{4322}
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-39.
Default filename: acs.mcd
Table 6-39 ACS table

Site Number 6 0–120 Mandatory.
This field is used to identify the site at which the specific value is required.
value.
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.
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
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.
Cont.
6-174 68P02900W22-Q
09-Sep-2004
System Information: DataGen ACS table
Table 6-39 ACS table (Continued)

line is 0 or 2.
line is 0 or 2.
line is 0 or 2.
AMR FR Init Codec Mode 3 0 to 6. Mandatory. Prompted for if the
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 to this (if valid).
AMR FR Uplink 3 0 to 63. Mandatory. Prompted for if the ACS
Threshold,1 contains more than one codec mode.
Lower Full-Rate uplink decision threshold for switching from one mode to another.
Hystersis,1 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.
the codec mode.
Cont.
68P02900W22-Q 6-175
09-Sep-2004

the codec mode.
AMR FR Downlink 3 0 to 63. Mandatory. Prompted for if the ACS
Lower Full-Rate downlink decision threshold for switching from one mode to another.
the codec mode.
the codec mode.
the codec mode.
AMR FR Uplink Thresh 3 0 to 63. Mandatory. Prompted for if the ACS
Hop,1 contains more than one codec mode.
Uplink switching threshold applied to frequency hopping channels.
Hop2 contains more than one codec mode.
AMR FR Uplink Hyst 3 0 to 15. Mandatory. Prompted for if the ACS
Uplink hysteresis applied to frequency hopping channels.
Cont.
6-176 68P02900W22-Q
09-Sep-2004

AMR FR Downlink Thresh 3 0 to 63. Mandatory. Prompted for if the ACS
Downlink switching threshold applied to frequency hopping channels.
AMR FR Downlink Thresh 3 0 to 63 Mandatory. Prompted for if the ACS
AMR FR Downlink Thresh 3 0 to 63 Mandatory. Prompted for if the ACS
AMR FR Downlink Hyst 3 0 to 15. Mandatory. Prompted for if the ACS
Downlink hysteresis applied to frequency hopping channels.
AMR HR ACS,1 3 2 to 6. Mandatory. Prompted for if the
line is 0 or 2.
line is 0 or 2.
Cont.
68P02900W22-Q 6-177
09-Sep-2004

line is 0 or 2.
line is 0 or 2.
AMR HR Init Codec Mode 3 2 to 6. Mandatory. Prompted for if the ACS
contains more than one codec mode.
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 (if valid).
AMR HR Uplink 3 0 to 63. Mandatory. Prompted for if the ACS
Lower half rate decision threshold for switching from one mode to another.
the codec mode.
the codec mode.
the codec mode.
AMR HR Downlink 3 0 to 63. Mandatory. Prompted for if the ACS
Cont.
6-178 68P02900W22-Q
09-Sep-2004

the codec mode.
the codec mode.
the codec mode.
AMR HR Uplink Thresh 3 0 to 63. Mandatory. Prompted for if the ACS
AMR HR Uplink Hyst 3 0 to 15. Mandatory. Prompted for if the ACS
Cont.
68P02900W22-Q 6-179
09-Sep-2004

AMR HR Downlink Thresh 3 0 to 63. Mandatory. Prompted for if the ACS
AMR HR Downlink Hyst 3 0 to 15. Mandatory. Prompted for if the ACS
6-180 68P02900W22-Q
09-Sep-2004
Index
Index
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
A
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Admin option Admintool, using (contd.)

scheduling an audit. . . . . . . . . . . . . . 4-51 modify group information . . . . . . . . . . 2-16
Administration . . . . . . . . . . . . . . . . . 3-11 modify user account . . . . . . . . . . . . . 2-11
changing permissions. . . . . . . . . . . . . 3-12 user administration utilities . . . . . . . . . . 2-7
country admin . . . . . . . . . . . . . . . . 3-27 user management . . . . . . . . . . . . . . 2-4
customising parameters. . . . . . . . . . . . 3-16 user management parameters . . . . . . . . . 2-5
database administration tasks . . . . . . . . . 3-20 user password parameters. . . . . . . . . . . 2-6
importing CM database objects . . . . . . . . 3-26 Audit . . . . . . . . . . . . . . . . . . . . . 4-29
installing the Options Object . . . . . . . . . 3-18 aborting while in progress . . . . . . . . . . 4-58
optimising the database . . . . . . . . . . . . 3-14 audit logs . . . . . . . . . . . . . . . . . . 4-57
viewing the log file. . . . . . . . . . . . . . 3-15 from Navigation Tree. . . . . . . . . . . . . 4-30
Administration - CADM . . . . . . . . . . . . 5-39 inconsistency report . . . . . . . . . . . . . 4-59
Administration icon scheduling . . . . . . . . . . . . . . . . . . 4-51
use of . . . . . . . . . . . . . . . . . . . . 4-14 Audit inconsistency report . . . . . . . . . . . 4-60
Admintool, using . . . . . . . . . . . . . . . . 2-2 viewing . . . . . . . . . . . . . . . . . . . 4-60
add a group . . . . . . . . . . . . . . . . . 2-15 Audit log management . . . . . . . . . . . . . 4-62
add new user account. . . . . . . . . . . . . 2-9 Audit logs
change user password . . . . . . . . . . . . 2-11 deleting . . . . . . . . . . . . . . . . . . . 4-61
delete a group . . . . . . . . . . . . . . . . 2-17 viewing . . . . . . . . . . . . . . . . . . . 4-57
display group account information . . . . . . 2-14 Auto-compile MMI script command . . . . . . . 5-12
display user account information . . . . . . . 2-8 Auto-Revgen command . . . . . . . . . . . . . 5-30
group administration utilities . . . . . . . . . 2-14 Auto-upgrader command . . . . . . . . . . . . 5-36
group management parameters . . . . . . . . 2-13
B
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Basic BSS with TS switch . . . . . . . . . . . 3-46 BSS area (contd.)

Batch processing creating . . . . . . . . . . . . . . . . . . . 3-34
compile . . . . . . . . . . . . . . . . . . 3-136 deleting . . . . . . . . . . . . . . . . . . . 3-42
BSS area opening . . . . . . . . . . . . . . . . . . . 3-38
configuring . . . . . . . . . . . . . . . . . 3-44 Service window . . . . . . . . . . . . . . . 3-34
copying . . . . . . . . . . . . . . . . . . . 3-40
68P02900W22-Q IX-1
09-Sep-2004
Index
C
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Cell Compile MMI script (compile) command . . . . 5-10

find . . . . . . . . . . . . . . . . . . . . . 4-21 Compile multiple binary object files . . . . . . 3-136
CellXchange Compress OLM network . . . . . . . . . . . . 4-68
introduction . . . . . . . . . . . . . . . . . 4-33 Compress/uncompress binary object files
Radio Frequency planning . . . . . . . . . . 4-33 command . . . . . . . . . . . . . . . . . . . 5-14
CM database objects . . . . . . . . . . . . . . 3-26 Configuration management icon
converting to a database script file. . . . . . . 3-71 use of . . . . . . . . . . . . . . . . . . . . 4-14
cmutil.olm command . . . . . . . . . . . . . . 4-5 Configuring BSS area(s) . . . . . . . . . . . . 3-44
Command line tools . . . . . . . . . . . . . . 5-2 basic BSS with TS switch. . . . . . . . . . . 3-46
auto compile MMI Script (auto_compile) . . . 5-12 basic BSS with TS switch - expansion . . . . . 3-54
auto_revgen . . . . . . . . . . . . . . . . . 5-30 daisy chain configuration with TS switch . . . 3-58
auto_upgrade . . . . . . . . . . . . . . . . 5-36 functions and MCDF table relationships . . . . 3-44
compile MMI script (compile) . . . . . . . . 5-10 Converting a script file . . . . . . . . . . . . 3-117
compress binary object files (cpdb -c) . . . . . 5-14 binary object compiler . . . . . . . . . . . 3-117
copy area (ca) . . . . . . . . . . . . . . . . 5-5 Sysgen mode . . . . . . . . . . . . . . . 3-117
delete database object (del) . . . . . . . . . . 5-16 Copy area (ca) command . . . . . . . . . . . . 5-5
general information . . . . . . . . . . . . . 5-4 Copy BSS binary files into OLM . . . . . . . . 4-66
lock/unlock BSS area (lock_adm) . . . . . . . 5-24 Copying a BSS area from the GUI . . . . . . . . 3-40
MCDF filter (filter) . . . . . . . . . . . . . 5-18 Country administration (CADM) . . . . . . . . 5-39
MMI combiner (combine) . . . . . . . . . . 5-8 administration files . . . . . . . . . . . . . . 5-43
MMI command generator (gcmd) . . . . . . . 5-21 menus . . . . . . . . . . . . . . . . . . . . 5-41
optimise DataGen database (dbaccess). . . . . 5-23 using the xcadm GUI . . . . . . . . . . . . . 5-40
revgen. . . . . . . . . . . . . . . . . . . . 5-27 Creating a BSS area . . . . . . . . . . . . . . 3-34
toggle permissions (tp) . . . . . . . . . . . . 5-32 Creating a BSS from Navigation Tree . . . . . . 4-27
uncompress binary object files (cpdb -u) . . . . 5-14 Creating a network
user options . . . . . . . . . . . . . . . . . 5-4 Saving a network. . . . . . . . . . . . . . . 4-6
version upgrader (upg) . . . . . . . . . . . . 5-34 Creating a RXCDR from Navigation Tree . . . . 4-27
D
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Daisy chain configuration with TS switch . . . . 3-58 DataGen database structure (contd.)
Database DataGen - OMC integration. . . . . . . . . . 1-7
dropping/recreating the db_dg Informix DataGen directory structure . . . . . . . . . . . 1-11
database . . . . . . . . . . . . . . . . . . . 3-22 main structure . . . . . . . . . . . . . . . . 1-12
reloading the Informix database . . . . . . . . 3-21 sub-structure. . . . . . . . . . . . . . . . . 1-13
save . . . . . . . . . . . . . . . . . . . . . 4-36 DataGen files . . . . . . . . . . . . . . . . . 3-81
system performance . . . . . . . . . . . . . 3-20 tools for editing . . . . . . . . . . . . . . . 3-81
usage scripts . . . . . . . . . . . . . . . . . 3-20 DataGen functions . . . . . . . . . . . . . . . 1-2
verify . . . . . . . . . . . . . . . . . . . . 4-36 Defragmenting the database . . . . . . . . . . . 3-14
warning messages . . . . . . . . . . . . . . 3-21 Delete database object (del) command . . . . . . 5-16
Database script files . . . . . . . . . . . . . . 3-76 Deleting a BSS area . . . . . . . . . . . . . . 3-42
alternative text editor . . . . . . . . . . . . . 3-79 Deleting a network . . . . . . . . . . . . . . . 4-46
producing . . . . . . . . . . . . . . . . . . 3-76 Deleting a network/country . . . . . . . . . . . 3-32
viewing . . . . . . . . . . . . . . . . . . . 3-77 Device management
xedit window . . . . . . . . . . . . . . . . 3-78 from navigation tree . . . . . . . . . . . . . 4-32
DataGen and OLM platform . . . . . . . . . . 1-5 Difference reporter . . . . . . . . . . . . . . 3-124
DataGen database structure . . . . . . . . . . . 1-7 menu option . . . . . . . . . . . . . . . . . 3-10
BSS database . . . . . . . . . . . . . . . . 1-7 selecting BSS area details. . . . . . . . . . 3-125
CM database object . . . . . . . . . . . . 1-7
database script file . . . . . . . . . . . . . 1-7
IX-2 68P02900W22-Q
09-Sep-2004
Index
Difference reporter (contd.) Difference reporter (contd.)

using the information window. . . . . . . . 3-127 using the report window . . . . . . . . . . 3-128
E
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Environment variables Environment variables (contd.)

automate RevGen . . . . . . . . . . . . . . 3-5 text editor . . . . . . . . . . . . . . . . . . 3-7
defining . . . . . . . . . . . . . . . . . . . 3-4 time slot order . . . . . . . . . . . . . . . . 3-5
export path . . . . . . . . . . . . . . . . . 3-6 version order . . . . . . . . . . . . . . . . 3-5
import path . . . . . . . . . . . . . . . . . 3-6 Exiting the OLM GUI . . . . . . . . . . . . . 4-11
output to script. . . . . . . . . . . . . . . . 3-7 Expanded BSS with TS . . . . . . . . . . . . . 3-54
override lock . . . . . . . . . . . . . . . . 3-7 Expanding the network . . . . . . . . . . . . . 4-47
setenv command . . . . . . . . . . . . . . . 3-4 Expert desktop option. . . . . . . . . . . . . . 4-16
setting from the GUI . . . . . . . . . . . . . 3-11 Exporting object files . . . . . . . . . . . . . 3-120
F
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
feature feature (contd.)

22064 . . . . . . . . . . . . . . . . 6-44 to 6-45, 4441 . . . . 6-32 to 6-33, 6-35, 6-39, 6-79, 6-86 to
6-100 to 6-101, 6-141 to 6-142, 6-147 6-87, 6-110, 6-116, 6-120 to 6-121, 6-131
23658 . . . . . 6-28, 6-32, 6-43, 6-82 to 6-83, 6-99, 4445 . . . . . . . . . . . . . . . . 6-30 to 6-31,
6-106, 6-115 to 6-116, 6-138 to 6-140, 6-146 6-35, 6-74, 6-81, 6-104, 6-111, 6-124
3723 . . . . 3-88, 6-28 to 6-29, 6-32 to 6-33, 6-38 4449 . . . . . . . . . . . . . . 6-28, 6-41, 6-71
to 6-41, 6-71, 6-74, 6-85 to 6-86, 6-94, 6-104, 6-107, Find icon
6-109, 6-120 to 6-121, 6-130 to 6-132, 6-135, 6-169 use of . . . . . . . . . . . . . . . . . . . . 4-15
4040 . . . . . . . . . . . 6-21, 6-33, 6-39, 6-131 Find, using . . . . . . . . . . . . . . . . . . . 4-17
4322 . . . . . . . 3-88, 6-27 to 6-28, 6-35 to 6-36, examples
6-43, 6-74 to 6-76, 6-78 to 6-79, 6-83, 6-87, 6-95 to BSS parent of a Cell . . . . . . . . . . . . 4-21
6-96, 6-105 to 6-106, 6-108, 6-116, 6-122, 6-125 to cell with LAC . . . . . . . . . . . . . . . 4-21
6-126, 6-133, 6-136, 6-147, 6-174 site with BSS name and Site Id . . . . . . . 4-20
4415 . . . . . . . . . . . . . . . . 6-105, 6-147 Functions - command line. . . . . . . . . . . . 5-2
G
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Generic Table Editor (GTE) . . . . . . . . . . . 3-94 Generic Table Editor (GTE) (contd.)
edit menu . . . . . . . . . . . . . . . . . 3-100 hot keys for MCDF . . . . . . . . . . . . 3-108
file menu . . . . . . . . . . . . . . . . . . 3-94 Group management. . . . . . . . . . . . . . . 2-13
fill cells . . . . . . . . . . . . . . . . . . 3-102 group parameters. . . . . . . . . . . . . . . 2-13
format menu . . . . . . . . . . . . . . . . 3-104
H
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Hardware configurations supported . . . . . . . 1-14 Help icon

Hardware reports, generating . . . . . . . . . 3-115 OLM GUI . . . . . . . . . . . . . . . . . . 4-15
Help button, DataGen. . . . . . . . . . . . . . 3-10
68P02900W22-Q IX-3
09-Sep-2004
Index
I
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Importing/exporting objects . . . . . . . . . . . 3-64 Invalid NE . . . . . . . . . . . . . . . . . . . 4-24

Installing the Options Object . . . . . . . . . . 3-18
L
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Loading network information . . . . . . . . . . 1-9 Lock/Unlock BSS area (lock_adm) command . . 5-24
gathering network information . . . . . . . . 1-10 Log files
Locate NE, site or cell . . . . . . . . . . . . . 4-17 viewing audit logs . . . . . . . . . . . . . . 4-57
M
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
MCDF files MCDF tables (contd.)

creating . . . . . . . . . . . . . . . . . . . 3-88 Hardware table. . . . . . . . . . . . . . . . 6-17
editing tables . . . . . . . . . . . . . . . . 3-90 Hop table . . . . . . . . . . . . . . . . . 6-169
inserting . . . . . . . . . . . . . . . . . . . 3-89 KSW table. . . . . . . . . . . . . . . . . 6-166
invalid data entry. . . . . . . . . . . . . . . 3-92 Lapd table . . . . . . . . . . . . . . . . . . 6-63
validating . . . . . . . . . . . . . . . . . . 3-89 Links table . . . . . . . . . . . . . . . . . 6-59
MCDF filter (filter) command . . . . . . . . . . 5-18 Modify Value table . . . . . . . . . . . . . . 6-52
MCDF table hierarchy . . . . . . . . . . . . . 6-2 Neighbour table . . . . . . . . . . . . . . 6-155
MCDF tables NSVC table . . . . . . . . . . . . . . . . 6-168
ACS table . . . . . . . . . . . . . . . . . 6-174 Paths table. . . . . . . . . . . . . . . . . . 6-61
Algorithm data table . . . . . . . . . . . . 6-153 PIX table . . . . . . . . . . . . . . . . . 6-165
BSS table . . . . . . . . . . . . . . . . . . 6-5 RTF table . . . . . . . . . . . . . . . . . 6-143
Cabinet table . . . . . . . . . . . . . . . . 6-13 Site table . . . . . . . . . . . . . . . . . . 6-10
Cell table . . . . . . . . . . . . . . . . . . 6-65 Specifics table . . . . . . . . . . . . . . . 6-102
Channel table . . . . . . . . . . . . . . . . 6-57 Statistics table . . . . . . . . . . . . . . . . 6-73
Circuit table . . . . . . . . . . . . . . . . . 6-54 Throttles table . . . . . . . . . . . . . . . 6-161
Daughter table . . . . . . . . . . . . . . . 6-163 Timer table . . . . . . . . . . . . . . . . . 6-46
DRI table . . . . . . . . . . . . . . . . . 6-148 MMI combiner (combine) command . . . . . . . 5-8
EAS table . . . . . . . . . . . . . . . . . 6-162 MMI command generator (gcmd) command . . . 5-21
Generics table . . . . . . . . . . . . . . . . 6-26
N
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Navigation tree Navigation Tree (contd.)

autoclose . . . . . . . . . . . . . . . . . . 4-49 opening . . . . . . . . . . . . . . . . . . . 4-23
Navigation Tree overwrite a BSS/RXCDR binary object file . . 4-34
audit . . . . . . . . . . . . . . . . . . . . 4-30 panner. . . . . . . . . . . . . . . . . . . . 4-26
closing . . . . . . . . . . . . . . . . . . . 4-24 porthole . . . . . . . . . . . . . . . . . . . 4-26
create BSS or RXCDR . . . . . . . . . . . . 4-27 Network
deleting a BSS/RXCDR . . . . . . . . . . . 4-50 create . . . . . . . . . . . . . . . . . . . . 4-6
device management . . . . . . . . . . . . . 4-32 delete . . . . . . . . . . . . . . . . . . . . 4-46
introduction . . . . . . . . . . . . . . . . . 4-22 Network Expansion. . . . . . . . . . . . . . . 4-47
moving levels . . . . . . . . . . . . . . . . 4-25
IX-4 68P02900W22-Q
09-Sep-2004
Index
O
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Offline MIB (OLM) OLM GUI, using (contd.)

integration with DataGen . . . . . . . . . . . 1-4 task list . . . . . . . . . . . . . . . . . . . 4-3
overview . . . . . . . . . . . . . . . . . . 1-3 troubleshooting . . . . . . . . . . . . . . . 4-4
Offline MIB directory structure . . . . . . . . . 1-13 database errors . . . . . . . . . . . . . . 4-72
main structure . . . . . . . . . . . . . . . . 1-14 fails to start . . . . . . . . . . . . . . . . 4-70
OLM file structure . . . . . . . . . . . . . . 1-13 force shutdown . . . . . . . . . . . . . . 4-74
OLM GUI, using . . . . . . . . . . . . . . . . 4-2 general operating errors . . . . . . . . . . 4-73
additional features . . . . . . . . . . . . . . 4-48 import errors . . . . . . . . . . . . . . . 4-74
auditing logs . . . . . . . . . . . . . . . 4-57 reinitialise database . . . . . . . . . . . . 4-75
autoclose . . . . . . . . . . . . . . . . . 4-49 specific operation fails . . . . . . . . . . . 4-73
compress/uncompress an OLM network . . . 4-68 verify and save network . . . . . . . . . . . 4-36
deleting a NE database . . . . . . . . . . . 4-50 OLM online Help . . . . . . . . . . . . . . . 4-15
deleting a scheduled audit . . . . . . . . . 4-56 OMC
managing audit logs . . . . . . . . . . . . 4-62 exporting object files to the OMC . . . . . . 3-120
modifying a scheduled audit . . . . . . . . 4-55 importing binary object files from the OMC . . 3-64
realigning a network . . . . . . . . . . . . 4-66 Opening a BSS area . . . . . . . . . . . . . . 3-38
scheduling an audit . . . . . . . . . . . . 4-51 Operating DataGen . . . . . . . . . . . . . . . 3-2
cmutil.olm command . . . . . . . . . . . . . 4-5 overview . . . . . . . . . . . . . . . . . . 3-2
deleting a network configuration . . . . . . . 4-46 procedures. . . . . . . . . . . . . . . . . . 3-2
environment variables . . . . . . . . . . . . 4-4 shutdown . . . . . . . . . . . . . . . . . . 3-10
exiting the OLM GUI . . . . . . . . . . . . 4-11 startup. . . . . . . . . . . . . . . . . . . . 3-9
expert desktop . . . . . . . . . . . . . . . . 4-16 Optimise DataGen database (dbaccess)
front panel icons . . . . . . . . . . . . . . . 4-14 command . . . . . . . . . . . . . . . . . . . 5-23
levels of users . . . . . . . . . . . . . . . . 4-4 Optimising the database. . . . . . . . . . . . . 3-14
shutting down the OLM . . . . . . . . . . . 4-12 Overview - DataGen . . . . . . . . . . . . . . 1-2
standard desktop . . . . . . . . . . . . . . . 4-16 Overwriting a BSS/RXCDR binary object file . . 4-34
starting the OLM GUI . . . . . . . . . . . . 4-9
P
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Panner . . . . . . . . . . . . . . . . . . . . . 4-26 Porthole . . . . . . . . . . . . . . . . . . . . 4-26
R
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Radio Frequency planning Revgen (contd.)

overview . . . . . . . . . . . . . . . . . . 4-33 auto-Revgen . . . . . . . . . . . . . . . . . 3-74
Realign a network . . . . . . . . . . . . . . . 4-66 converting object files . . . . . . . . . . . . 3-71
Reload an NE database . . . . . . . . . . . . . 4-64 menu options . . . . . . . . . . . . . . . . 3-71
Revert to saved network . . . . . . . . . . . . 4-40 toolbar . . . . . . . . . . . . . . . . . . . 3-72
Revgen . . . . . . . . . . . . . . . . . . . . 3-71 Revgen command . . . . . . . . . . . . . . . 5-27
activating . . . . . . . . . . . . . . . . . . 3-73 Revgen multiple binary object files . . . . . . 3-136
S
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Save NE database Save network . . . . . . . . . . . . . . . . . 4-40

Save NE. . . . . . . . . . . . . . . . . . . 4-37 aborting a save operation . . . . . . . . . . . 4-44
68P02900W22-Q IX-5
09-Sep-2004
Index
Scheduling an audit. . . . . . . . . . . . . . . 4-51 Service window (contd.)

deleting . . . . . . . . . . . . . . . . . . . 4-56 Services menu . . . . . . . . . . . . . . . . 3-69
modifying . . . . . . . . . . . . . . . . . . 4-55 toolbar . . . . . . . . . . . . . . . . . . . 3-62
Script file generator. . . . . . . . . . . . . . . 3-76 Shutting down DataGen. . . . . . . . . . . . . 3-10
Service window Shutting down the OLM . . . . . . . . . . . . 4-12
BSS area . . . . . . . . . . . . . . . . . . 3-62 Starting DataGen . . . . . . . . . . . . . . . . 3-9
Edit menu . . . . . . . . . . . . . . . . . . 3-68 Starting the OLM GUI . . . . . . . . . . . . . 4-9
File menu . . . . . . . . . . . . . . . . . . 3-64 Supported platforms . . . . . . . . . . . . . . 1-14
menu bar . . . . . . . . . . . . . . . . . . 3-64
T
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Table Controller . . . . . . . . . . . . . . . . 3-83 Tools - overview . . . . . . . . . . . . . . . . 5-2

command buttons . . . . . . . . . . . . . . 3-84 Troubleshooting OLM
controls . . . . . . . . . . . . . . . . . . . 3-84 database errors . . . . . . . . . . . . . . . . 4-72
creating MCDF files . . . . . . . . . . . . . 3-88 fails to start . . . . . . . . . . . . . . . . . 4-70
file select buttons . . . . . . . . . . . . . . 3-85 force shutdown . . . . . . . . . . . . . . . 4-74
file status display. . . . . . . . . . . . . . . 3-85 general errors . . . . . . . . . . . . . . . . 4-73
files status icons . . . . . . . . . . . . . . . 3-92 import errors. . . . . . . . . . . . . . . . . 4-74
functions . . . . . . . . . . . . . . . . . . 3-84 reinitialise database . . . . . . . . . . . . . 4-75
menu bar . . . . . . . . . . . . . . . . . . 3-84 specific operation fails . . . . . . . . . . . . 4-73
Toggle permissions (tp) command . . . . . . . . 5-32
U
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Uncompress OLM network . . . . . . . . . . . 4-68 Using the CADM tool (contd.)

Upgrade multiple binary object files . . . . . . 3-136 creating a new country . . . . . . . . . . . . 3-29
Upgrader . . . . . . . . . . . . . . . . . . 3-129 creating a new network . . . . . . . . . . . . 3-31
Upgrading a BSS area . . . . . . . . . . . . 3-129 deleting a country/network . . . . . . . . . . 3-32
DARBC and EXBL . . . . . . . . . . . . 3-135 Using the Generic Table Editor
multiple BSS areas . . . . . . . . . . . . . 3-133 Generic Table Editor (GTE). . . . . . . . . . 3-94
resolving problems . . . . . . . . . . . . . 3-133 Using the Table Controller
upgrade procedure . . . . . . . . . . . . . 3-131 editing MCDF tables . . . . . . . . . . . . . 3-90
Usage scripts. . . . . . . . . . . . . . . . . . 3-20 MCDF files . . . . . . . . . . . . . . . . . 3-88
User and group management . . . . . . . . . . 2-2 MCDF tables . . . . . . . . . . . . . . . . 3-85
Using the CADM tool Using the Topology Viewer . . . . . . . . . . 3-109
country administration . . . . . . . . . . . . 3-27 hardware configuration . . . . . . . . . . . 3-111
V
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Verify NE database . . . . . . . . . . . . . . . 4-37 Verify network . . . . . . . . . . . . . . . . . 4-40

aborting a verify operation . . . . . . . . . . 4-43
Version upgrader (upg) command . . . . . . . . 5-34
X
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Xterm icon. . . . . . . . . . . . . . . . . . . 4-15
IX-6 68P02900W22-Q
09-Sep-2004

Gsr7 Half Rate: System Information Datagen

Uploaded by

Document Information

Original Title

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

Gsr7 Half Rate: System Information Datagen

Uploaded by

Copyright:

Available Formats

SYSTEM INFORMATION

© 1996 -2004 Motorola, Inc. 68P02900W22-Q

All Rights Reserved 09-Sep-2004

System Information: DataGen

Chapter 1: Overview of DataGen

The DataGen and OLM platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Chapter 2: User and Group management using the Admintool

Chapter 3: Operating DataGen

Define default text editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Configuration of MCDF tables for a basic BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51

File status icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-92

Chapter 4: Operating the Offline MIB

Additional OLM features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Overwrite a BSS/RXCDR binary object file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34

Error OLM fails to start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-70

Chapter 5: Command line tools

Command line options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16

Chapter 6: MCDF tables

Paths table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-61

This page intentionally left blank.

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

Figure 3-22: Basic BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46

Figure 4-9: Expert desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16

This page intentionally left blank.

Table 1: Manual version history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Table 5-7: Command line options (gcmd command) . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21

System Information: DataGen

What is Covered In This Manual?

Issue status of this manual

Table 1 Manual version history

Resolution of service requests

The following Service Requests are now resolved in this manual:

Table 2 Service requests resolved in this manual

Failure to comply with Motorola’s operation, installation and maintenance

The tags have the format: {nnnn} or {nnnnn}

The tags are positioned in text as follows:

New and amended feature information Tag position in text

• Full sections under a main heading • Main heading

• Full paragraphs under subheadings • Subheading

Special key sequences

CTRL-c Press the Control and c keys at the same time.

Reporting safety issues

Whenever a safety issue arises:

Procedure 1 Safety issue reporting

1 Make the equipment concerned safe, for example by removing power.

Warnings and cautions

A definition and example follow below:

Example and format

Failure to comply with warnings

A definition and example follow below:

Example and format

• Potentially hazardous voltage.

Potentially hazardous voltage

Motorola GSM equipment does not utilise high voltages.

High RF potentials and electromagnetic fields are present in this equipment

When dismantling heavy assemblies, or removing or replacing equipment, a

Do not install substitute parts or perform any unauthorized modification of

Lithium batteries, if subjected to mistreatment, may burst and ignite. Defective

Motorola equipment contains CMOS devices. These metal oxide semiconductor

Devices sensitive to static

Special handling techniques

Motorola manual set

• Electronic, as fully navigable PDF files on:

"$