401-610-055v1

Lucent Technologies—ProprietaryThis document contains proprietary information of

Lucent Technologies and is not to be disclosed or usedexcept in accordance with applicable agreements.

Copyright © 2005 Lucent TechnologiesUnpublished and Not for Publication

All Rights Reserved

401-610-055Issue 28August 2005

Flexent®/AUTOPLEX®

Wireless NetworksExecutive Cellular Processor (ECP)Release 25.0Input MessagesVolume 1ABT—HELP

Copyright © 2005 Lucent Technologies

This material is protected by the copyright and trade secret laws of the United States and other countries. Itmay not be reproduced, distributed, or altered in any fashion by any entity (either internal or external to LucentTechnologies), except in accordance with applicable agreements, contracts or licensing, without the expresswritten consent of Lucent Technologies and the business management owner of the material.

NoticeEvery effort was made to ensure that the information in this document was complete and accurate at the timeof printing. However, information is subject to change.

Mandatory Customer InformationNOTE: This equipment has been tested and found to comply with the limits for a Class A digital device,pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection againstharmful interference when the equipment is operated in a commercial environment. This equipment generates,uses, and can radiate radio frequency energy, and if not installed and used in accordance with the instructionmanual, may cause harmful interference to radio communications. Operation of this equipment in a residentialarea is likely to cause harmful interference in which case the user will be required to correct the interference athis/her own expense.

Security StatementIn rare instances, unauthorized individuals make connections to the telecomunications network through theuse of remote access features. In such events, applicable tariffs require that the customer pay all network chargesfor traffic. Lucent Technologies cannot be responsible for such charges and will not make any allowence or giveany credit for charges that result from unauthorized access.

TrademarksAll trademarks and service marks specified herein are owned by their respective companies.

Lucent Technologies—ProprietarySee notice on first page

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 TABLE OF CONTENTS

ID............. TABLE-OF-CONTENTSTYPE .......... Input

Table of Contents

1. About This Document

1.1 Introduction ..................................................................................... 1

1.2 Prerequisite Skills ............................................................................ 1

1.3 Documentation on the Web ........................................................... 1

1.4 To obtain documentation, training, and technicalsupport or submit feedback ......................................................... 2

1.5 Technical Support ........................................................................... 2

1.6 Reason for Reissue .......................................................................... 2

1.7 Description of Table Information ................................................. 21.7.1 Feature ID Column ........................................................... 21.7.2 Feature Name Column ..................................................... 31.7.3 Message ID Column ......................................................... 31.7.4 Format Impact Column .................................................... 3

1.8 ECP 25.0 New and Changed Input Messages by Feature ......... 5

1.9 Index by Message ID of changes for Current Generic ............... 11

1.10 ECP 24.0 New and Changed Input Messages by Feature ....... 15

1.11 ECP 23.0 New and Changed Input Messages by Feature ....... 21

2. Getting Started

2.1 Introduction ..................................................................................... 1

2.2 Message Purpose ............................................................................. 1

2.3 Message Organization .................................................................... 2

2.4 Message Format .............................................................................. 2

2.5 Message Syntax ............................................................................... 32.5.1 Input Message Fields ........................................................ 52.5.2 Keywords ........................................................................... 52.5.3 Pathnames .......................................................................... 62.5.4 Format Notation ................................................................ 62.5.5 Format Examples .............................................................. 72.5.6 Use of Spaces ..................................................................... 82.5.7 Rules for Keying in Messages ......................................... 10

SEE PROPRIETARY NOTICE ON COVER PAGE

Issue 28 TABLE-OF-CONTENTS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksTABLE OF CONTENTS August 2005

2.6 System Acknowledgements .......................................................... 10

2.7 List of Acronyms ............................................................................. 13

3. Input Indexes

3.1 Input Messages Index ..................................................................... 1

3.2 Functional Index.............................................................................. 31

Input Message Descriptions


TABLE-OF-CONTENTS-ii Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ABOUT THIS DOCUMENT

CONTENTS

1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.2 Prerequisite Skills . . . . . . . . . . . . . . . . . . . . . . . 1

1.3 Documentation on the Web . . . . . . . . . . . . . . . . . . . . 1

1.4 To obtain documentation, training, and technical support or submitfeedback . . . . . . . . . . . . . . . . . . . . . . . . . . 2

1.5 For technical support . . . . . . . . . . . . . . . . . . . . . . 2

1.6 Reason For Reissue . . . . . . . . . . . . . . . . . . . . . . 2

1.7 Description of Table Information . . . . . . . . . . . . . . . . . . 21.7.1 Feature ID Column . . . . . . . . . . . . . . . . . . . . 21.7.2 Feature Name Column . . . . . . . . . . . . . . . . . . . 31.7.3 Message ID Column . . . . . . . . . . . . . . . . . . . . 31.7.4 Format Impact Column . . . . . . . . . . . . . . . . . . . 3

1.8 ECP 25.0 New and Changed Input Messages by Feature . . . . . . . . . . 5

1.9 Index by Message ID of changes for Current Generic . . . . . . . . . . . 11




Issue 28 ABOUT-THIS-DOCUMENT-i

401-610-055 Flexent /AUTOPLEX Wireless NetworksABOUT THIS DOCUMENT August 2005

This page intentionally left blank.


ABOUT-THIS-DOCUMENT-ii Issue 28


ID............. ABOUT-THIS-DOCUMENT

TYPE .......... Input

Chapter 1

About This Document

1.1 Introduction

The Flexent /AUTOPLEX Wireless Networks Input Messages document describes the inputmessages available for use on the Flexent /AUTOPLEX Wireless Networks systems.

The messages included in this document represent complete documentation for the current issue.Only certain "recent change" messages associated with updating the generic program are notincluded.

This document is organized into three major tab-divided sections:

• Overview contains three chapters: "About This Document," "Getting Started," and "InputIndexes." "About This Document" describes the purpose, prerequisite skills, error reportingprocedures, and related documents that pertain to this document. "Getting Started" describesthe purpose, organization, and format for the input messages. Also, a list ofFlexent /AUTOPLEX Wireless Networks acronyms is included. "Input Indexes" containstwo indexes. The first one is an alphabetical list of all the input messages. The second listgroups the input messages by unit and/or function.

• Flexent Input Message Descriptions contains the message documentation presented inalphabetical order by message name for all Flexent - specific input messages. Each messagebegins on a right-hand page with the individual descriptions grouped according to themessage name prefix.

• Input Message Descriptions contains the message documentation presented in alphabeticalorder by message name. Each message begins on a right-hand page with the individualdescriptions grouped according to the message name prefix.

1.2 Prerequisite Skills

To derive maximum benefit from the information presented in this document, you should befamiliar with the Flexent /AUTOPLEX Wireless Networks systems.

1.3 Documentation on the Web

The current release of the Flexent /AUTOPLEX Wireless Networks documentation is providedon the Lucent Technologies Wireless Networks customer technical support web site to allcustomers, free of charge. To access the site, please visit:

http://wireless.support.lucent.com

To provide the most current, complete, and technically accurate documentation to customers asquickly as possible, revisions and updates of information products on the current release of the401-010-001 Flexent /AUTOPLEX Wireless Networks Electronic Documentation CD-ROM are


Issue 28 ABOUT-THIS-DOCUMENT-1


also provided on the site for all customers, free of charge. In some cases, new informationproducts, or preliminary drafts of new information products are also posted on the site prior torelease on the CD-ROM. For information on how to access the documentation on the web, see"Accessing documentation on the web" on the current CD-ROM.

1.4 To obtain documentation, training, and technical support or submit feedback

The 401-010-001 Flexent /AUTOPLEX Wireless Networks Documentation CD-ROM and website provide a "To obtain documentation, training, and technical support, or send feedback"document. That document explains how to:

• obtain technical support

• register as an authorized user of the Lucent Technologies customer technical support web site

• access the most current AMPS/PCS and related 5ESS Digital Cellular Switch (DCS)documentation on the site

• order system and product documentation

• order training products or register for classroom training courses

• submit comments and feedback about documentation and training.

1.5 For technical support

Lucent Technologies customer technical support provides technical support for allFlexent /AUTOPLEX Wireless Networks systems and products. For technical support, pleasecall the following numbers:

From the USA:1-866-LUCENT8 (1-866-582-3688)

From all other countries:1-630-224-4672

Please be prepared to describe the specific problem in your Flexent /AUTOPLEX WirelessNetworks systems. An operator will either transfer your call directly to a customer technicalsupport representative or forward your request to a representative, who will return your call assoon as possible. Service-affecting situations are always handled immediately.

1.6 Reason For Reissue

Table 1-1 provides the reason for reissue for each new or changed input message by feature.

1.7 Description of Table Information

1.7.1 Feature ID Column

Lists the feature numbers responsible for changes to the message listed. Also to save space, thiscolumn indicates if the message is NEW, DELETE or RENAME.

• NEW MESSAGE means that this is a new message.

• DELETE MESSAGE means that this message has been either deleted from the manual entirelyor has been renamed, and that the old Message ID is no longer being used and has beendeleted.


ABOUT-THIS-DOCUMENT-2 Issue 28


• RENAME MESSAGE means that a Message ID was changed to a new Message ID. To do thisthe old ID is deleted, and a new ID is created. The message is marked RENAME to minimizethe impact on customers. This way the user knows that the message itself has NOT changed,but the manual page name has changed. If the message has changed the information in theother columns will indicate this.

• Changed messages with no Message ID change have no entry in this column.

1.7.2 Feature Name Column

Lists the features associated with changes to the message.

1.7.3 Message ID Column

The Message ID is a unique identifier that can be found in the key block in the upper right cornerof the first page of every message. Messages are alphabetized in the document according to theMessage ID.

1.7.4 Format Impact Column

Lists a "Y" if the changes have impacted the format. A "Y" in this column indicates that either theFormat section itself has changed or one of the variables listed in the Format section has hadadditional parameters added or deleted.

Sample table:

Table x-xECP xx.x New and Changed Input Messages by Feature

_ ____________________________________________________________________________________Feature Feature Name Message ID FormatID Impact_ ____________________________________________________________________________________xxxx.x Feature Name

AUD:TCS-NAME Y(NEW MESSAGE) GET:RNC-ALARM Y(DELETE MESSAGE) TEST:BTS-RNC Y(RENAME MESSAGE) TST:BTS-RNC Y_ ____________________________________________________________________________________







1.8 ECP 25.0 New and Changed Input Messages by Feature

Table 1-1ECP 25.0 New and Changed Input Messages by Feature

_ ____________________________________________________________________________________Feature Feature Name Message ID FormatID Impact_ _____________________________________________________________________________________ ____________________________________________________________________________________4263.0 Migrating DLN/SS7 Ring

Nodes to the AP PlatformMON:APSLK Y_ ____________________________________________________________________________________

4566.1 AMA Migration to AP -Stage 2

COPY:AMATAPE Y(RENAME MESSAGE) COPY:AMATAPE-ECP Y

LABEL:AMATAPE Y(RENAME MESSAGE) LABEL:AMATAPE-ECP Y(NEW MESSAGE) OP:AMA-METADATA Y

OP:AMA-SESSION Y(RENAME MESSAGE) OP:AMA-SESSION-ECP Y

OP:AMA-TELEPRO Y(RENAME MESSAGE) OP:AMA-TELEPRO-ECP Y

VER:AMATAPE Y(RENAME MESSAGE) VER:AMATAPE-ECP Y_ ____________________________________________________________________________________

4566.2 AMA Migration - Stage 3(NEW MESSAGE) RMV:AP-AMA Y(NEW MESSAGE) RMV:AP-AMATPS Y(NEW MESSAGE) RST:AP-AMA Y(NEW MESSAGE) RST:AP-AMATPS Y(NEW MESSAGE) SWITCHOVER:AMA Y(NEW MESSAGE) SWITCHOVER:AMATPS Y_ ____________________________________________________________________________________

4566.3 AMA Migration - Stage 4ABT:AMATAPE Y

(RENAME MESSAGE) ABT:AMATAPE-ECP Y(DELETE MESSAGE) ALW:AMA-AUTOST Y(RENAME MESSAGE) ALW:AMA-AUTOST-ECP Y(DELETE MESSAGE) ALW:AMA-SESSION Y(RENAME MESSAGE) ALW:AMA-SESSION-ECP Y

BKUP:DATABASE YCOPY:AMATAPE

(DELETE MESSAGE) INH:AMA-AUTOST Y(RENAME MESSAGE) INH:AMA-AUTOST-ECP Y(DELETE MESSAGE) INH:AMA-SESSION Y(RENAME MESSAGE) INH:AMA-SESSION-ECP Y_ ____________________________________________________________________________________




Table 1-1ECP 25.0 New and Changed Input Messages by Feature (Continued)

_ __________________________________________________________________________________________Feature Feature Name Message ID FormatID Impact_ ___________________________________________________________________________________________ __________________________________________________________________________________________4566.3 AMA Migration - Stage 4

(DELETE MESSAGE) INIT:AMA-DW Y(RENAME MESSAGE) INIT:AMA-DW-ECP Y

LABEL:AMATAPE Y(RENAME MESSAGE) LABEL:AMATAPE-ECP(DELETE MESSAGE) OP:AMA-CONFIG Y(RENAME MESSAGE) OP:AMA-CONFIG-ECP Y(DELETE MESSAGE) OP:AMA-CONTROL Y(RENAME MESSAGE) OP:AMA-CONTROL-ECP Y(DELETE MESSAGE) OP:AMA-DISK Y(RENAME MESSAGE) OP:AMA-DISK-ECP Y(DELETE MESSAGE) OP:AMA-MAPS Y(RENAME MESSAGE) OP:AMA-MAPS-ECP Y

OP:AMA-SESSION(DELETE MESSAGE) SET:AMA-CONFIG Y(DELETE MESSAGE) SET:AMA-CONFIG-BSN Y(RENAME MESSAGE) SET:AMA-CONFIG-BSN-ECP Y(RENAME MESSAGE) SET:AMA-CONFIG-ECP Y(DELETE MESSAGE) SET:AMA-CONTROL Y(RENAME MESSAGE) SET:AMA-CONTROL-ECP Y

STOP:AMATAPE Y(RENAME MESSAGE) STOP:AMATAPE-ECP Y

VER:AMATAPE(DELETE MESSAGE) WRITE:AMA-DATA Y(RENAME MESSAGE) WRITE:AMA-DATA-ECP Y_ __________________________________________________________________________________________

6015.13 Support of 1.2MSubscribers on aFlexent /AUTOPLEX

SystemCOPY:DBOP:ECP-AUD_ __________________________________________________________________________________________

8002.6 RNC Release 23 OAMSoftware feature.

TST:PSU-RNC_ __________________________________________________________________________________________8002.7 RNC Release 24 OAM

Software featureCOPY:RNCDB Y_ __________________________________________________________________________________________





_ __________________________________________________________________________________________Feature Feature Name Message ID FormatID Impact_ __________________________________________________________________________________________8168.1 Abutting Switch List (ASL)

Alternative for ExpandedMaximum SHO Universeon the 1X RNC

ABT:ECP-AUD YALW:ECP-AUD YAUD:ECP-NAME YINH:ECP-AUD Y_ __________________________________________________________________________________________

9021.0 TI Support for OMC-RANALW:RCMSINH:RCMS_ __________________________________________________________________________________________

9054.1 Optional EIN -R23 Phase(NEW MESSAGE) OP:EIN-ROUTEPOOL Y_ __________________________________________________________________________________________

9054.3 AP EINE as Optional Equipagefor RCS-APs and DNFS Hosts(NEW MESSAGE) OP:EIN-ROUTEPOOL Y_ __________________________________________________________________________________________

9999.21 CDMA Unknown FeatureOP:CTRC Y_ __________________________________________________________________________________________

9999.24 Network UnknownFeature

ALW:CELL YAUD:CELL YINH:CELL Y

(RENAME MESSAGE) OP:AMA-SESSION-ECPOP:AMA-TELEPRO

(RENAME MESSAGE) OP:AMA-TELEPRO-ECP_ __________________________________________________________________________________________9999.33 IMOM Cleanup

ALW:CELL YAUD:CELL YEXC:CELL-RTDIAG YINH:CELL Y_ __________________________________________________________________________________________

9999.8 1XEV DO FeatureUnknown

RST:BTS-TFU_ __________________________________________________________________________________________9999.99 Verification FID with

No Associated FeatureINIT:CDN-DBOP:DCS-MRAQ_ __________________________________________________________________________________________





_ __________________________________________________________________________________________Feature Feature Name Message ID FormatID Impact_ __________________________________________________________________________________________10444.7 RNC Integrity Monitor

(RIM) Phase 2(NEW MESSAGE) ALW:RNC-ABREVC Y(NEW MESSAGE) GET:RNC-ABREVC Y(NEW MESSAGE) INH:RNC-ABREVC Y(NEW MESSAGE) SWITCH:RNC Y_ __________________________________________________________________________________________

10615.0 Automatic ProtectionSwitching on the RNC(NEW MESSAGE) CLEAR:RNC-GICC Y(NEW MESSAGE) GET:RNC-GICC Y(NEW MESSAGE) LOCKOUT:RNC-GICC Y(NEW MESSAGE) SWITCH:TOMATE-RNC-TPU Y_ __________________________________________________________________________________________

10666.1 IP Backhaul for CDMA(Modcells 1, 2, 3 and 4)

ABT:VCA-AUD Y(NEW MESSAGE) ALW:CELL-MLG Y

ALW:VCA-AUD YAUD:VCA-NAME YCREATE:RCSDELETE:RCS

(NEW MESSAGE) DUMP:CELL-AUTH-FAIL Y(NEW MESSAGE) INH:CELL-MLG Y

INH:VCA-AUD YINIT:VCA YLABEL:AMATAPE Y

(NEW MESSAGE) OP:AP-IPBHINFO Y(Modcells 1, 2, 3 and 4)(NEW MESSAGE) OP:BHS-CELL Y

OP:CELL Y(NEW MESSAGE) OP:CELL-CSB Y(NEW MESSAGE) OP:DCS-BHSSTAT Y(NEW MESSAGE) OP:RNC-BHSSTAT Y

RESTART:RCSSHUTDOWN:RNC-TPUUNLOCK:RNC-TPU

(NEW MESSAGE) UPDATE:AP-BPSN Y(NEW MESSAGE) UPDATE:CELL-BPSN Y

VER:AMATAPE Y_ __________________________________________________________________________________________





_ __________________________________________________________________________________________Feature Feature Name Message ID FormatID Impact_ __________________________________________________________________________________________10674.2 IP Back Haul on

the CDMA RNCGET:RNC-ABREVC YGET:RNC-TPU-STATE YLOCK:RNC-TPU YSHUTDOWN:RNC-TPU YUNLOCK:RNC-TPU Y_ __________________________________________________________________________________________

11003.1 EV-DO Cell OA&MConvergence forMixed Networks(NEW MESSAGE) CFR:CELL Y(NEW MESSAGE) FLUS:CELL Y(NEW MESSAGE) OP:CELL-FLUS Y(NEW MESSAGE) STOP:FLUS-CELL Y_ __________________________________________________________________________________________

12064.0 Adaptive PagingBKUP:DATABASE YCOPY:DB Y_ __________________________________________________________________________________________

12084.0 1xEV-DO KTF RDAF 706301 -Session Status Command(NEW MESSAGE) OP:AP-IMSI-STATUS Y_ __________________________________________________________________________________________

12618.0 Idle Mobile SubscriberLocation Trace(NEW MESSAGE) ALW:LSLTRC Y(NEW MESSAGE) INH:LSLTRC Y(NEW MESSAGE) OP:LTRC Y_ __________________________________________________________________________________________








1.9 Index by Message ID of changes for Current Generic

Table 1-2Index by Message ID of changes for Current Generic

_ _______________________________________________________________________________________Message ID Changes Description_ _______________________________________________________________________________________

ABT:AMATAPE Notes in PURPOSE section updated.Variable a now MT0 and MT1 instead of ST1 and ST2.System Response section redone.

ABT:AMATAPE-ECP RENAMED - ECP version of ABT:AMATAPE-ECPABT:ECP-AUD Added to the Audit name list "RUESID2P".ABT:VCA-AUD BHMDB added to variable a.ALW:AMA-AUTOST DELETED - Renamed ALW:AMA-AUTOST-ECPALW:AMA-AUTOST-ECP RENAMED from ALW:AMA-AUTOSTALW:AMA-SESSION DELETED - Renamed ALW:AMA-SESSION-ECPALW:AMA-SESSION-ECP RENAMED from ALW:AMA-SESSIONALW:CELL Values in the audit name table changed for: ARDCCH,

CPAVAIL, CSCP, CSDL, FLCA, INTRPROC, OCQMICRO,OCQCCC, TURCUD, TUTRANS, TUUNEQ.

ALW:CELL-MLG NEWALW:ECP-AUD Added to the Audit name list "RUESID2P".ALW:LSLTRC NEWALW:RCMS Added RL to System Response section.ALW:RNC-ABREVC NEWALW:VCA-AUD BHMDB added to variable a.AUD:CELL Values in the audit name table changed for: ARDCCH,

CPAVAIL, CSCP, CSDL, FLCA, INTRPROC, OCQMICRO,OCQCCC, TURCUD, TUTRANS, TUUNEQ.

AUD:ECP-NAME Added to the Audit name list "RUESID2P".AUD:VCA-NAME BHMDB added to variable a.BKUP:DATABASE New value for variable a "ADAPTPGDB", delete AMAMDDB.CFR:CELL NEWCLEAR:RNC-GICC NEWCOPY:AMATAPE Message totally redone, consider NEW.COPY:AMATAPE-ECP RENAMED - ECP version of COPY:AMATAPECOPY:DB New value for variable a "ADAPTPGDB".

Warning section almost completely redone,second paragraph in the Purpose section also rewritten.In Warning section changed the a/b/c list. Also addedOP:ECD-AUD to the Input Message References section.

COPY:RNCDB RNC number or ALL added to the format.Purpose section redone.

CREATE:RCS Last paragraph in Purpose section added.DELETE:RCS Last paragraph in Purpose section added.DUMP:CELL-AUTH-FAIL NEWEXC:CELL-RTDIAG Variable b listing redone for different cell types.FLUS:CELL NEWGET:RNC-ABREVC NEW




Table 1-2Index by Message ID of changes for Current Generic (continued)

_ _________________________________________________________________________________________Message ID Changes Description_ _________________________________________________________________________________________

GET:RNC-GICC NEWGET:RNC-TPU-STATE Format 9 new.INH:AMA-AUTOST DELETED - Renamed INH:AMA-AUTOST-ECPINH:AMA-AUTOST-ECP RENAMED from INH:AMA-AUTOSTINH:AMA-SESSION DELETED - Renamed INH:AMA-SESSION-ECPINH:AMA-SESSION-ECP RENAMED from INH:AMA-SESSIONINH:CELL Values in the audit name table changed for: ARDCCH, CPAVAIL,

CSCP, CSDL, FLCA, INTRPROC, OCQMICRO, OCQCCC,TURCUD, TUTRANS, TUUNEQ.

INH:CELL-MLG NEWINH:ECP-AUD Added to the Audit name list "RUESID2P".INH:LSLTRC NEWINH:RCMS Added RL to System Response section.INH:RNC-ABREVC NEWINH:VCA-AUD BHMDB added to variable a.INIT:AMA-DW DELETED - Renamed INIT:AMA-DW-ECPINIT:AMA-DW-ECP RENAMED from INIT:AMA-DWINIT:CDN-DB Added additional information under descriptions

for PRTLTDB and VLRCSTDB values.INIT:VCA For variable a "bhm" value and description added

to the list.LABEL:AMATAPE Message totally redone, consider NEW.LABEL:AMATAPE-ECP RENAMED - ECP version of LABEL:AMATAPE

Variable d - DAT value added.LOCK:RNC-TPU Format 5 new.LOCKOUT:RNC-GICC NEWMON:APSLK Remove square brackets in format 1

Replace square brackets with curly brackets in format 4.OP:AMA-CONFIG DELETED - Renamed OP:AMA-CONFIG-ECPOP:AMA-CONFIG-ECP RENAMED from OP:AMA-CONFIGOP:AMA-CONTROL DELETED - Renamed OP:AMA-CONTROL-ECPOP:AMA-CONTROL-ECP RENAMED from OP:AMA-CONTROLOP:AMA-DISK DELETED - Renamed OP:AMA-DISK-ECPOP:AMA-DISK-ECP RENAMED from OP:AMA-DISKOP:AMA-MAPS DELETED - Renamed OP:AMA-MAPS-ECPOP:AMA-MAPS-ECP RENAMED from OP:AMA-MAPSOP:AMA-METADATA NEWOP:AMA-SESSION Message totally redone, consider NEW.OP:AMA-SESSION-ECP RENAMED - ECP version of OP:AMA-SESSION

Reference to the REPT-AMA-X25-DCI output message changed tothe new REPT-AMA-TELE-SUM-ECP output message.






OP:AMA-TELEPRO Message totally redone, consider NEWChange wording in the purpose to clarify that the summary isfor the current day.

OP:AMA-TELEPRO-ECP RENAMED - ECP version of OP:AMA-TELEPROReference to the REPT-AMA-X25-DCI output message changed tothe new REPT-AMA-TELE-SUM-ECP output messageChange wording in the purpose to clarify that the summary isfor the current day.

OP:AP-IMSI-STATUS NEWOP:AP-IPBHINFO NEWOP:BHS-CELL NEWOP:CELL New value added to variable c - MLG.

Minor descriptive text change.OP:CELL-CSB NEWOP:CELL-FLUS NEWOP:CTRC Remove format 6 and affected variables.OP:DCS-BHSSTAT NEWOP:DCS-MRAQ Changes the information found under the OK System Response.OP:ECP-AUD Added a Note to the EXPLANATION section and added COPY:DB

to the Input Message Reference on the page.OP:EIN-ROUTEPOOL NEWOP:LTRC NEWOP:RNC-BHSSTAT NEWRESTART:RCS Formatting problem in Warning fixed.RMV:AP-AMA NEWRMV:AP-AMATPS NEWRST:AP-AMA NEWRST:AP-AMATPS NEWRST:BTS-TFU Remove lines in Note about if GPS and 1xEV-DO only

used from APCLI, not true in 25.0.SET:AMA-CONFIG DELETED - Renamed SET:AMA-CONFIG-ECPSET:AMA-CONFIG-BSN DELETED - Renamed SET:AMA-CONFIG-BSN-ECPSET:AMA-CONFIG-BSN-ECP RENAMED from SET:AMA-CONFIG-BSNSET:AMA-CONFIG-ECP RENAMED from SET:AMA-CONFIGSET:AMA-CONTROL DELETED - Renamed SET:AMA-CONTROL-ECPSET:AMA-CONTROL-ECP RENAMED from SET:AMA-CONTROLSHUTDOWN:RNC-TPU Format 5 new.STOP:AMATAPE Notes in PURPOSE section updated Variable a now MT0 and MT1

instead of ST1 and ST2. System Response section redone.STOP:AMATAPE-ECP RENAMED - ECP version of STOP:AMATAPESTOP:FLUS-CELL NEWSWITCH:RNC NEW






SWITCH:TOMATE-RNC-TPU NEWSWITCHOVER:AMA NEWSWITCHOVER:AMATPS NEWTST:PSU-RNC Additional paragraph added to the Purpose section.UNLOCK:RNC-TPU Format 5 new.UPDATE:AP-BPSN NEWUPDATE:CELL-BPSN NEWVER:AMATAPE Message totally redone, consider NEW.VER:AMATAPE-ECP RENAMED - ECP version of VER:AMATAPEWRITE:AMA-DATA DELETED - Renamed WRITE:AMA-DATA-ECPWRITE:AMA-DATA-ECP RENAMED from WRITE:AMA-DATA_ _________________________________________________________________________________________




Tables 1-3 through 1-4 provide the reasons for reissue for earlier generics. These tables are forhistorical reference only.



_ ____________________________________________________________________________________Feature Feature Name Message ID FormatID Impact_ ____________________________________________________________________________________3756.1 3G Operational Fault

Detection (OFD) for BasicAccess Overhead Channels

ALW:CELL Y(NEW MESSAGE) CLR:CELL-OFD Y

CLR:CELL-OFD YINH:CELL YINIT:CDN-DBOP:CELL-OFD Y_ ____________________________________________________________________________________

4566.2 AMA Migration - Stage 3SET:AMA-CONFIGSET:AMA-CONFIG-BSN_ ____________________________________________________________________________________

6015.5 HVLR-AP Master DB’sConversion to ALX, Stage 2

ALW:MSCDBMS-AUDAUD:MSCDBMSINH:MSCDBMS-AUD_ ____________________________________________________________________________________

8002.6 RNC Release 23 OAMSoftware feature(NEW MESSAGE) EXPORT:RNC-CONFIG Y(NEW MESSAGE) IMPORT:RNC-CONFIG Y_ _____________________________________________________________________________________

8002.7 RNC Release 24 OAMSoftware feature

ALW:RNC-TPU-DGN Y(NEW MESSAGE) BKUP:RNCDB Y(NEW MESSAGE) COPY:RNCDB Y(NEW MESSAGE) DELBKUP:RNCDB Y

GET:RNC-INSTALL(RENAMED MESSAGE) GET:RNC-PDSNLIST Y(NEW MESSAGE) GET:RNC-PSPCF Y

GET:RNC-TPU-DGNRES YGET:RNC-TPU-INFO

(DELETE MESSAGE) GET:RNC-TPU-PDSNLIST YGET:RNC-TPU-STATE YGET:RNC-TPU-VER-CON YGET:RNC-TPU-VERSION Y_ _____________________________________________________________________________________





_ _____________________________________________________________________________________Feature Feature Name Message ID FormatID Impact_ _____________________________________________________________________________________8002.7 RNC Release 24 OAM

Software featureHALT:RNC-TPUINH:RNC-TPU-DGN YINSTALL:RNC-TPULOCK:RNC-TPU Y

(NEW MESSAGE) OP:RNCDB Y(NEW MESSAGE) OP:TCS-AUD Y

RESET:RNC-TPU YSHUTDOWN:RNC-TPU YUNLOCK:RNC-TPU Y_ _____________________________________________________________________________________

8880.5 MCR - Phase 2 DeliveriesOP:CELL Y_ _____________________________________________________________________________________

9021.0 TI Support for OMC-RANALW:AP-HVLRALW:AP-MMAALW:CELL-DLALW:MSCDBMS-AUDALW:MSCDBMS-RCVAUD:MSCDBMSCFR:AP-DS1CFR:AP-SS7CFR:SS7COMMIT:APCREATE:MMACREATE:RCSDELETE:MMADELETE:RCSDGN:AP-DS1DGN:SS7INH:AP-HVLRINH:AP-MMAINH:CELL-DLINH:MSCDBMS-AUDINH:MSCDBMS-RCVINIT:AMA-DWINIT:APOCNS:CELL Y_ _____________________________________________________________________________________





_ _____________________________________________________________________________________Feature Feature Name Message ID FormatID Impact_ _____________________________________________________________________________________9021.0 TI Support for OMC-RAN

OP:AP-ALARMOP:AP-CMDSOP:AP-DS1-STATOP:AP-DS1x-STATOP:AP-INFOOP:AP-MMA-STATOP:AP-MMAx-STATOP:AP-RCS-STATOP:AP-RCSx-STATOP:AP-STATUSOP:AP-VERSIONOP:CELL-DL YOP:SS7x-STATRESTART:MMARESTART:RCSRMV:APRMV:AP-DS1RMV:AP-HVLRRMV:AP-HVLRIMRMV:AP-MMARMV:AP-MSCDBMSRMV:AP-OAMPROXYRMV:AP-RNCDBMSRMV:AP-RNCMRMV:AP-ROPRMV:AP-SPRMV:AP-SS7MMRMV:AP-TCSRMV:AP-TPUGUIRMV:AP-VCARMV:RCSRMV:SS7RST:APRST:AP-DS1RST:AP-HVLRRST:AP-HVLRIMRST:AP-MMARST:AP-MSCDBMSRST:AP-OAMPROXYRST:AP-RNCDBMS_ _____________________________________________________________________________________





_ _____________________________________________________________________________________Feature Feature Name Message ID FormatID Impact_ _____________________________________________________________________________________9021.0 TI Support for OMC-RAN

RST:AP-RNCMRST:AP-ROPRST:AP-SPRST:AP-SS7MMRST:AP-TCSRST:AP-TPUGUIRST:AP-VCARST:CELLRST:RCSRST:SS7SELECT:APSTOP:MSCDBMSSTOP:SS7SWITCHBACK:FROMAPSWITCHOVER:APSWITCHOVER:HVLRIMSWITCHOVER:MSCDBMSSWITCHOVER:OAMPROXYSWITCHOVER:RCSSWITCHOVER:RNCDBMSSWITCHOVER:RNCMSWITCHOVER:ROPSWITCHOVER:SPSWITCHOVER:TCSSWITCHOVER:TPUGUISWITCHOVER:VCA_ _____________________________________________________________________________________

9216.0 Tone/AnnouncementExpansion

BKUP:DATABASE YCOPY:DB YINIT:CDN-DB Y_ _____________________________________________________________________________________





_ _____________________________________________________________________________________Feature Feature Name Message ID FormatID Impact_ _____________________________________________________________________________________9999.33 IMOM Cleanup

ABT:ECP-AUD YALW:CELL YALW:ECP-AUD YAUD:ECP-NAME YAUD:MSCDBMSCLR:CELL-OFD YINH:CELL YINH:ECP-AUD YMON:AP-SLKSET:AMA-CONTROL_ _____________________________________________________________________________________

9999.8 1XEV DO Feature UnknownINIT:BTSRST:BTS-TFU Y_ _____________________________________________________________________________________

10394.2 FMM AP Support forSatellite CPU

OP:AP-INFO Y(NEW MESSAGE) OP:AP-INV Y_ _____________________________________________________________________________________

10444.1 RNC Integrity Monitor(RIM) - Phase 1(NEW MESSAGE) GET:RNC-STATUS Y_ _____________________________________________________________________________________

10621.0 OAM&P to support CDMAPacket Core Blade PCF

TST:PSU-RNC Y_ _____________________________________________________________________________________10870.0 Remote T1 Monitoring

EXC:CELL-CDM-DS1(NEW MESSAGE) EXC:CELL-CDM-DS1 Y_ _____________________________________________________________________________________

10880.0 Network Integration Testingfor ECP Migration

AUD:ECP-NAME_ _____________________________________________________________________________________12048.2 Optical GIGE interface

on the GICC for the1x RNC application

GET:RNC-INSTALLGET:RNC-TPU-FAILEDPVC YGET:RNC-TPU-STATE YLOCK:RNC-TPU YSHUTDOWN:RNC-TPU YTST:BTS-RNC YTST:PSU-RNC YUNLOCK:RNC-TPU Y_ _____________________________________________________________________________________





_ _____________________________________________________________________________________Feature Feature Name Message ID FormatID Impact_ _____________________________________________________________________________________12157.0 MSC to pass on display

text to MS when receivedfrom ANSI41 messages

ABT:CDN-AUD YALW:CDN-AUD YAUD:CDN-NAME YINH:CDN-AUD Y_ _____________________________________________________________________________________

RTR Real Time Reliablemessage changes

CLR:PTN-MHD YCOPY:BKDISK Y

(NEW MESSAGE) COPY:BKTAPE YCOPY:TAPE-TOPDUMP:BKTAPE YOP:DFC-INFO YOP:MHD-INFO Y

(NEW MESSAGE) OP:MSGCLS YOP:MT-INFO YVFY:FILE_ _____________________________________________________________________________________






_____________________________________________________________________________________Feature Feature Name Message ID FormatID Impact_____________________________________________________________________________________4263.12 SS7-AP BERT test

DGN:SS7_____________________________________________________________________________________4263.17 SS7-AP Performance/

Capacity/ReliabilityImprovements - phase 2

CLR:SS7SRST YOP:SS7APNET Y_____________________________________________________________________________________

5088.2 SDB Transport over SpecialBearer Path (Base Station only)

OP:CELL Y_____________________________________________________________________________________6020.2 HVLR Enhancements

(NEW MESSAGE) ALW:AP-HVLR Y(NEW MESSAGE) INH:AP-HVLR Y

OP:AP-STATUS(DELETE MESSAGE) RESTART:AP-HVLRIM Y(NEW MESSAGE) RMV:AP-HVLRIM Y(NEW MESSAGE) RST:AP-HVLRIM Y(NEW MESSAGE) SWITCHOVER:HVLRIM Y_____________________________________________________________________________________

8002.6 RNC Release 23 OAMSoftware feature.

ALW:RNC-TPU-DGN YALW:TCS-AUD YGET:RNC-ALARMGET:RNC-INVENTORYGET:RNC-TPU-DGNRES Y

(NEW MESSAGE) GET:RNC-TPU-FAILEDPVC YGET:RNC-TPU-INVENTGET:RNC-VERSION

(NEW MESSAGE) HALT:RNC-TPU YINH:RNC-TPU-DGN YINH:TCS-AUD YTST:BTS-RNCTST:PSU-RNC_ ____________________________________________________________________________________

8124.2 1xEV-DO OA&M EnhancementsOP:BTS_ ____________________________________________________________________________________





_ ____________________________________________________________________________________Feature Feature Name Message ID FormatID Impact_ ____________________________________________________________________________________9054.1 Optional EIN - R23 Phase

INIT:ECP Y_ ____________________________________________________________________________________9103.1 Integration of AP

Commands with TI Stage 2(NEW MESSAGE) HELP Y

RST:CDN YSELECT:AP Y_ ____________________________________________________________________________________

9137.0 Base Configuration Required(mandatory migration features)for Retrofit to ECP R23.0.

RST:CDN Y_ ____________________________________________________________________________________9999.24 Network Unknown Feature

DGN:AP-DS1 YRMV:AP-DS1 YRST:AP-DS1 Y_ ____________________________________________________________________________________

9999.33 IMOM CleanupABT:CDN-AUD YALW:CDN-AUD YAUD:CDN-NAME YINH:CDN-AUD YSELECT:AP YSET:DB-SU YSW:CELL_ ____________________________________________________________________________________

9999.99 Verification FID withNo Associated Feature

DGN:SS7 YEXC:CELL-RTDIAG Y_ ____________________________________________________________________________________

10221.3 IOS BSC: Supportfor A3/A7

BKUP:DATABASE YCOPY:DB YINIT:ECP-DB Y_ ____________________________________________________________________________________

10621.0 OAM&P to support CDMAPacket Core Blade PCF

GET:RNC-INSTALL Y(NEW MESSAGE) GET:RNC-TPU-INFO Y(NEW MESSAGE) GET:RNC-TPU-PDSNLIST Y

GET:RNC-TPU-STATE Y_ ____________________________________________________________________________________





_ ____________________________________________________________________________________Feature Feature Name Message ID FormatID Impact_ ____________________________________________________________________________________10621.0 OAM&P to support CDMA

Packet Core Blade PCFGET:RNC-TPU-VER-CON YGET:RNC-TPU-VERSION YINSTALL:RNC-TPU YLOCK:RNC-TPU YRESET:RNC-TPU YSHUTDOWN:RNC-TPU YUNLOCK:RNC-TPU Y_ ____________________________________________________________________________________

10680.0 Enhancements to failoverand failback Capabilities(NEW MESSAGE) ALW:TP-AUD Y(NEW MESSAGE) INH:TP-AUD Y(NEW MESSAGE) OP:AP-PROCCFG Y(NEW MESSAGE) SWITCHBACK:AP Y

SWITCHOVER:AP Y_ ____________________________________________________________________________________







Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 GETTING STARTED

CONTENTS

2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 1

2.2 Message Purpose . . . . . . . . . . . . . . . . . . . . . . . 1

2.3 Message Organization . . . . . . . . . . . . . . . . . . . . . . 2

2.4 Message Format . . . . . . . . . . . . . . . . . . . . . . . . 2

2.5 Message Syntax . . . . . . . . . . . . . . . . . . . . . . . . 32.5.1 Input Message Fields . . . . . . . . . . . . . . . . . . . . 52.5.2 Keywords . . . . . . . . . . . . . . . . . . . . . . . . 52.5.3 Pathnames . . . . . . . . . . . . . . . . . . . . . . . . 62.5.4 Format Notation . . . . . . . . . . . . . . . . . . . . . . 62.5.5 Format Examples . . . . . . . . . . . . . . . . . . . . . 72.5.6 Use of Spaces . . . . . . . . . . . . . . . . . . . . . . . 82.5.7 Rules for Keying In Messages . . . . . . . . . . . . . . . . . 10

2.6 System Acknowledgements . . . . . . . . . . . . . . . . . . . . 10

2.7 List of Acronyms . . . . . . . . . . . . . . . . . . . . . . . 13


Issue 28 GETTING-STARTED-i

401-610-055 Flexent /AUTOPLEX Wireless NetworksGETTING STARTED August 2005



GETTING-STARTED-ii Issue 28


ID............. GETTING-STARTEDTYPE .......... Input

Chapter 2

Getting Started

2.1 Introduction

This chapter describes the input messages available for the Flexent /AUTOPLEX WirelessNetworks.

The messages included in this document represent complete documentation for the currentgeneric issue. Only certain "recent change" messages associated with updating the genericprogram are not included.

This section is divided into the following major sections:

Section 2.2 discusses the purpose of the input messages.

Section 2.3 discusses the organization of the input messages within the document.

Section 2.4 discusses the format of the input messages.

Section 2.5 discusses the syntax of the input messages.

Section 2.6 explains the system acknowledgements to the input messages.

Section 2.7 contains a list of acronyms and their meanings.

2.2 Message Purpose

The Flexent /AUTOPLEX Wireless Networks input messages documented here control,maintain, and administer the switching and control systems. They provide variable data typeinputs for functions that require a series of actions to be performed or reported. Examples offunctions the system is requested to perform by input messages are:

• Executing diagnostic and exercise programs, and reporting the results.

• Performing tests and reporting the results.

• Reporting the status of various subsystems.

• Reporting traffic information.

• Entering translation information into memory.

• Restoring units to service, or removing units from service.


Issue 28 GETTING-STARTED-1


Because several variables or options are inherent in these functions, many of the input messagesare complex and have several valid forms or executable paths. Some messages can affect service;these should be used only during periods of light traffic.

2.3 Message Organization

The messages are arranged alphabetically by message ID. The message ID appears on the bottomof each page with the page number. The message ID and message name are closely related, butthe message ID is unique to that message. Many messages start with the same or similar messagenames. The message name appears in the upper right hand corner of the page.

The message name consists of the action field ( a verb such as COPY, LOAD, or INH) and anidentification field (such as CELL, AMA, or STATUS). These fields are discussed in section 2.5.1.

2.4 Message Format

The descriptive material is presented under these headings:

• Key Block — Block of text in the upper right-hand corner on the first page of every messagedescription, below the message name.

Message ID — Unique ID for the message. Closely follows the message name, butlimited in characters and MUST be unique to that message. The message ID also appearson the bottom of each page with the page number.

Release — Generic release the message is associated with.

Type — Specifies that this is an Input message.

• Service-Affecting Messages - Input messages that may be service-affecting are flagged with acaution statement adjacent to the key block on the first page. An explanation of theconditions under which the message may be service-affecting is included.

• Purpose — Gives a complete statement of the message purpose.

• Format — Presents the message format. See Table 2-1 for a summary of rules.

• Explanation of Message — Defines the variables used in the message. It may also definekeywords. It includes any additional notes or tables needed to clarify message use.

• System Response — Explains the system response to each input message. This section of themessage documentation describes responses that are not self-explanatory. Typical systemacknowledgments are shown in Table 2-4.

Acknowledgments may be followed by text explaining any special conditions or errorsencountered while interpreting the message.

• References — Gives references to other input messages, output messages, or relateddocuments.


GETTING-STARTED-2 Issue 28


2.5 Message Syntax

Flexent /AUTOPLEX Wireless Networks messages follow a specific syntax. These conventionsare used throughout this document:

• Constant width typeface is used for:

— system generated responses

— output messages/reports

— literals in text including path and filenames.

• Constant width bold type face is used for keyboard input, (that is, input messageformat).

• Italic typeface is used for:

— place holders for user specified input; for example, OP:AMA;SESSION; a

— titles of other documents

• Roman typeface is used for punctuation that is for documentation purposes only; for example,the brackets shown at [;UCL].

Input messages are structured as described in Table 2-1.




Table 2-1Summary of Input Message Format

_ _______________________________________________________________________________________Term or Item Definition_ ________________________________________________________________________________________ _______________________________________________________________________________________

Field Basic structural unit of a message. Contains no more than threefields of variable length, separated by colons. Action field isrequired first. Identification field is required second; it containskeyword unit(s). Data field is optional; it contains keywordunit(s).

Subfield Optional breakdown of identification field. No more than threesubfields, separated by semicolons; contains keyword unit(s).

Keyword Mnemonic identifier of a unit, function, or condition. Input asgiven. May have argument(s) associated with it. Shown inconstant width bold for input.

Argument Variable information supplied by user. Input as a single entry, alist of up to 15 entries in the form (a,b,c...), or a range in the formx-y. Shown in italics.

Keyword unit Keyword and its associated argument(s), if any. Two or morekeyword units are separated by commas.

Message length Up to 255 characters, including spaces.

Lowercase entry Variable (argument). Replace with user-supplied information.Shown in italics.

Space Optional throughout message; required between keyword andits argument. Not permitted within keyword. See Section 2.5.6,"Use of Spaces."

[ ] Brackets Optional entries. Not input. Shown in roman.

{ } Braces Two or more entries for which the user must input one. Notinput.

OR bar Separates entries within braces or brackets. Not input.

" Quotation Mark Part of pathname of a file, directory, or device, and shown inconstant width bold. Input as given.

All other punctuation Part of message. Input as given._ _______________________________________________________________________________________




2.5.1 Input Message Fields

Input messages consist of either two or three fields, separated by colons, and terminated by anexclamation mark as shown below:

Action Field (verb): Identification Field: Data Field!

The action and identification fields are required for all input messages. Use of the data fielddepends on the structure of each input message.

The identification field may be divided into two or three subfields, separated by semicolons. Forexample:

STOP:AMATAPE! 2 fields, no subfields

OP:CELL;GENERIC! 2 fields, 2 subfields

DUMP:CELL a:MRAQ! 3 fields, no subfields

CFR:CELL a,b;c d:CHANL e! 3 fields, 2 subfields

The action field is a keyword that identifies a function. It is a verb, such as COPY, LOAD, STOP,or a verb abbreviation, such as ALW (allow), DGN (diagnose), or INH (inhibit). Theidentification field (or subfields), and the data field consist of one or more keyword units,separated by commas.

Currently most input commands have an option to specify CLASS at the end of each command.This CLASS option is only valid for input commands entered from CRAFT platforms (Example:Executive Cellular Processor Command Line Interface [ECP-CLI]). The CLASS option is not validfor input commands entered on migrated Technician Interface Command Line Interface (TICLI)platforms (Example: Operations Maintenance Platform [OMP] or Application Processor [AP]).

TICLI supports both Technician Interface (TI) and AP commands. TI commands that weresupported from the Executive Cellular Processor (ECP) Craft Shell and AP commands that weresupported from the Application Processor Command Line Interface (APCLI) or from the ElementManagement System Command Line Interface (EMSCLI) are supported from TICLI if the TIMigration feature is enabled. See document 401-710-210 Flexent Mobility Manager TechnicianInterface Implementation Guide for more information.

2.5.2 Keywords

A keyword, shown in constant width bold type in the input message documentation, is amnemonic identifier of a unit, function, or condition. It is constant information, and is inputexactly as given.




A keyword unit consists of a keyword with or without one or more variables, called arguments.Arguments, shown in italics print, represent variable information that must be supplied. Certainarguments are shown in boldface type. They are to be entered exactly as shown. Thefollowing are examples of keyword units.

DUMP:CELL a, ADRS b! is a message with two keyword units in the identificationfield.

INH:AMA;AUTOST! is a message with one keyword unit in the firstidentification subfield and one keyword unit in thesecond identification subfield.

LOAD:CELL a,ADRS b:DATA c! is a message with two keyword units in the identificationfield, and one keyword unit in the data field.

A keyword unit may have a single argument, a list, or a range of arguments. Arguments in a listare separated by commas, and enclosed in parentheses. A list can contain up to 15 arguments.The two arguments showing a range are separated by a hyphen. For example:

DUMP:CELL a:MRAQ! a represents the cell number.

DUMP:CELL 6:MRAQ! Specifies cell 6.

2.5.3 Pathnames

When referring to specific files, directories, and devices, such as tape drives,Flexent /AUTOPLEX Wireless Networks requires a special identifier, called a pathname.

Files are stored in a hierarchical manner; therefore, a device or filename is preceded by one ormore directory names. For example,

DISK /dev/vtoc, TAPE /dev/mt08

indicates that the DISK name is /vtoc and that it is located in the /dev directory. The TAPEdrive named /mt08 is also located in the /dev directory.

Again, to illustrate the hierarchical arrangement,

FN /user/a8/smo/test

shows the full pathname for the test file located in the /smo directory. /smo is a subdirectory of/a8, and /a8 is a subdirectory of /user.

Pathnames are used in many messages.

2.5.4 Format Notation

The input message formats shown in this document include, where necessary, three types ofnotation that are not part of the message itself. The purpose of this notation is to show thechoices available in constructing the message. The notation is for purposes of documentationonly; it is not input. (This notation is shown in roman font to indicate that it should not be input.)

[ ] Brackets enclose optional entries, that is, entries that may be included or omitted in themessage.




{ } Braces enclose two or more entries where one, and only one, must be included in themessage.

OR bars separate entries within braces and brackets.

The following is an example of using brackets, braces, and OR bars:

[ENTRY a][ENTRY b] None, one or both entries may be included in themessage.

{ENTRY a ENTRY b} One of ENTRY a or ENTRY b, must be included in themessage.

[ENTRY a ENTRY b] Neither entry, or just one entry, may be included in themessage.

Note that the OR bars in the second and third examples must not be entered; they indicate theformat options available.

2.5.5 Format Examples

The following examples show the difference between the input message as it is documented, andas it is input.

Entries Within Braces

Message format: ALW:SCSD {a,b c,d,e}!

Valid forms: ALW:SCSD 1,38!ALW:SCSD PTSWMCR, 1,12!

Braced Entries With and Without A Bracketed Entry

Message format: DUMP:CELL a; ADRS b [,L c][,{ONL OFL}]!

Valid forms: DUMP:CELL 3; ADRS 64!DUMP:CELL 7,8; ADRS X’7FF,L20,OFL!DUMP:CELL(10-20); ADRS 0’3777, ONL!

Entries Within Brackets

Message format: EXC:CELL a, RTDIAG [b][;RAW]!

Valid forms: EXC:CELL 12, RTDIAG!EXC:CELL 12, RTDIAG 3;RAW!EXC:CELL 12, RTDIAG 3-20!

Braced and Bracketed Entries

Message format: OP:STATUS:PROCESS,{ALLTERMS ALLKERNS ALL}[,OPL a]!

Valid forms: OP:STATUS:PROCESS,ALLTERMS!OP:STATUS:PROCESS,ALLTERMS,OPL 112!




OP:STATUS:PROCESS,ALLKERNS!OP:STATUS:PROCESS,ALLKERNS,OPL 800!OP:STATUS:PROCESS,ALL!OP:STATUS:PROCESS,ALL,OPL 57!

Bracketed Entries Within Brackets

Message format: RST:MTC a[;UCL[:CONT] :TLP[,CONT] :CONT]!

Valid forms: RST:MTC 4!RST:MTC 2:UCL!RST:MTC 7:UCL:CONT!RST:MTC 10:TLP!RST:MTC 1:TLP,CONT!RST:MTC 3:CONT!

2.5.6 Use of Spaces

2.5.6.1 Rules for use of spaces

Use spaces in your APX input command as follows:

• to separate a keyword from its variable

• to separate one keyword from another keyword

Do not use spaces

• within a keyword

You may enter extra spaces

• anywhere a single space is allowed, as long as you do not exceed 255 characters per inputcommand

• before or after punctuation, such as a colon, semicolon, comma, parenthesis, or exclamationmark

2.5.6.2 Use of spaces in conjunction with PDS input field delimiters

If a PDS input field delimiter appears between two parts of a format, a space is not required.

For example, in input format CHG:GEN!, a space is not required before or after the colon (butmay legally be included).

PDS input field separators are listed in Table 2-2.




Table 2-2PDS Input Field Separators

_ _________________________________________________________________________Separator Name_ __________________________________________________________________________ _________________________________________________________________________

! Exclamation mark. Used to end an input command. Optionalwhen keyed in from a terminal; required when input commandis used in a script._ _________________________________________________________________________

, Comma._ _________________________________________________________________________: Colon._ _________________________________________________________________________; Semi-colon._ _________________________________________________________________________" Quotation marks. Used to pass a file name to the switch. For

example:

EXC:ENVIR:UPROC,FN="/updtmp/site/vfytools"_ _________________________________________________________________________( Left parenthesis._ _________________________________________________________________________) Right parenthesis._ _________________________________________________________________________

NOTE: You may not use a PDS input field separator between a keyword and its variable. In thatparticular case, a space is required. Use of a PDS input field separator between a keyword and itsvariable would cause the input command to fail.

2.5.6.3 Generalization

The following generalization may help.

Use a space (if a PDS input field separator is not present) to set apart distinct pieces of information to bepassed separately to the software.

2.5.6.4 Examples

The following examples (Table 2-3) show these rules:

Table 2-3Usage Examples

________________________________________________________________________________________________________________Right Usage Wrong Usage Extra Spacing (permitted

but not required)________________________________________________________________________________________________________________________________________________________________________________________________________________________________EX;PAUSE;HSDC! EX;PA USE;HSDC! EX;PAUSE; HSDC!________________________________________________________________________________________________________________DGN:DCS a,TRKGRP b! DGN:DCSa,TRKGRPb! DGN: DCS a, TRKGRP b!________________________________________________________________________________________________________________CHG:GEN! C HG:GEN! CHG: GEN!________________________________________________________________________________________________________________DGN:DCS a,DL b;c,[,d][,RPT e][,UCL][ CLASS f]!

DGN:DCSa,DL b;c,[,d][,RPT e][,UCL][ CLASS f]!

DGN:DCS a,DL b;c ,[,d][,RPT e] [,UCL] [ CLASS f] !________________________________________________________________________________________________________________

EXC:ENVIR:UPROC,

FN="/updtmp/site/vfytools"

EXC:ENVIR:UPROC,

F N="/updtmp/site/vfytools"

EXC:ENVIR:UPROC,

FN= "/updtmp/site/vfytools"________________________________________________________________________________________________________________ALW:SCSD;UNIT a:PT(b,b,b)! ALW:SC SD;UNITa:PT(b,b,b)! ALW:SCSD; UNIT a: PT (b, b, b)!________________________________________________________________________________________________________________




2.5.7 Rules for Keying In Messages

When keying in messages, observe the following rules:

• A message may consist of up to 255 characters (including spaces) and may extend over severallines.

• The final character of a message is an exclamation mark (!) as shown in the messagedescription. The 255-character limit includes this final character. Messages typed at aterminal may be terminated with a carriage return (<return>) rather than an exclamationmark (!).

• One or more spaces may be used to separate an argument from its keyword. One exception isa list of arguments within parentheses; the left parenthesis serves as a separator, and no spaceis required.

• Except for values within double quotes (such as filenames), a message may be entered inupper or lower case.

2.6 System Acknowledgements

The system responds to each input message with an acknowledgment, and possibly one or moreoutput messages. For detailed information on acknowledgments for a particular message, seesection 4 of that message. The acknowledgment is always printed immediately. Outputmessages may occur following the output of other messages and data.

The format of all acknowledgments is:

aa[t[CODExxx]]

where aa = Two characters indicating status of requested input message. Table 2-4lists possible characters and their definitions.

t = Explanatory text for two character status (9 characters or less). Section 4 ofthe input message description lists definitions of explanatory text.

xxx = Decimal number (001-999) representing specific reason for two-characterstatus. Section 4 of the message description lists definitions of allapplicable numbers.




Table 2-4Input Message Acknowledgments

__________________________________________________________________________________________Acknowledgment Meaning____________________________________________________________________________________________________________________________________________________________________________________

?A Action field contains an error. The verb may have been typed incorrectlyor a field delimiter may have been omitted.

?D Data field contains an error. An item may have been incorrectly typed;improper data may have been entered; or a keyword or execute symbolmay have been omitted.

?E Error exists in the message but cannot be resolved to the proper field.

?I Identification field contains an error. An item may have been incorrectlytyped; an out-of-range number may have been used; or a requiredkeyword may have been omitted.

?T Time-out has occurred on the channel. Input has not been receivedwithin the allotted time, and processing of the message has been aborted.

IP In Progress. Request received and initiated. Further output will follow.

NA No Acknowledgment. Normally, the system acknowledges an inputrequest within two seconds. If control of the message processing hasbeen lost, NA is output to indicate an acknowledgment failure.

NG No Good. The message was received; the appropriate process wasinitiated; but the request conflicts with the current system or equipmentstatus. For example, action was requested for a unit that is beingdiagnosed.

OK Good. The message was received; the appropriate process was initiated;and work was completed.

PF Printout Follows. The request was received, and action will be taken. Aprintout will follow sometime later to explain, in detail, the results of thework initiated by the input message. This printout will be a terminationreport that may include the result of the work initiated by the inputmessage.

RL Retry Later. Request cannot be executed now because of unavailablesystem resources, such as system overload, excessive queue lengths, orthe requested process is busy.__________________________________________________________________________________________







2.7 List of Acronyms

2G Second Generation3G Third Generation Code Division Multiple Access3G-1X Third Generation Single Carrier5EGW 5ESS Gateway

A AccessAAA Authentication, Authorization, and AccountingAB After BootABD Alternate Boot DiskAC Alarm CardAC Authentication CenterACB Alarm Control BoardACC Analog Control ChannelACDN Administrative Call Processing/Database NodeACK AcknowledgmentACL Audit Control LibraryACNR Application Critical Node RecoveryACS Alarm Card SlotACS Alarm Control ShelfACT ActiveACTRC Automatic Call TraceACU Alarm Control UnitACU Analog Conversion UnitADF Alarm Definition FileADP Automatic Diagnostic ProcessAENC Asynchronous Event Notification CapabilityAERM Alignment Error Rate MonitorAFAC AUTOPLEX FacilityAGC Automatic Gain ControlAHVLR Administrative Home Visitor Location RegisterAIM Application Integrity MonitorAIS Alarm Indication SignalAM Administrative ModuleAMA Automatic Message AccountingAMATPS Automatic Message Accounting Teleprocessing SystemAMI Advanced Mobile Phone System Miscellaneous InformationAMI Alternate Mark InversionAML Automatic Maintenance LimitAMP AmplifierAMPS Advanced Mobile Phone SystemAMSS AUTOPLEX Message Storage SystemAN AuthenticationANI Automatic Number IdentificationANT AntennaAOADR Answer Only Automatic Message Accounting Dump for Roamers




AP Application ProcessorAP Argument PointerAP Attached ProcessorAPC Application Processor ClusterAPCC Application Processor Cluster ControllerAPCLI Application Processor Command Line InterfaceAPN Application Processor NodeAPS Automatic Protection SwitchingAR Autonomous RegistrationARCNET Attached Resource Computer NetworkARG Automatic Roamer GreetingARGR Autonomous Registration Glare ReportingARR Automatic Radio ReconfigurationARR Automatic Ring RecoveryARREGTRACE Autonomous Registration Glare ReportingAS Alarm ScanningASC Additional Sense CodeASCII American Standard Code for Information InterchangeASCQ Additional Sense Code QualifierASIC Application Specific Integrated CircuitASP Alarm Summary PrintASW All Seems WellAT Access TerminalATB Address Translation BufferATCC Auto-Tuned Cavity CombinerATM Asynchronous Transfer ModeATMOC3 Asynchronous Transfer Mode Optical Carrier Level 3ATMS Automatic Transmission Measurement SystemATP All Tests PassedATT Application Task TripperAV Analog VoiceAV-DRM Analog Voice Digital Radio ModuleAVL AvailableAWS Administrative Work StationAWTC Area Wide Test Channel

B8ZS Bipolar with 8 Zero SubstitutionBBA Bus Interface Unit [BIU]-Baseband Combiner/Radio [BCR]-

Analog Conversion Unit [ACU]BBU Baseband UnitBC BeaconBCCH Broadcast Control ChannelBCR Baseband Combiner/RadioBDU Bus Display UnitBEC Basic Error CorrectionBER Bit Error RateBERT Bit Error Rate TestBFM Blocking From Mobile Switching Center




BGMS Back Ground Music ServiceBGR Bi-directional Gating RegisterBHCA Busy Hour Call AttemptsBHCS Backhaul Connection ServerBHM Backhaul ManagerBHS Backhaul ServerBIC Bus Interface ControllerBID Billing IdentificationBISO Beginning of IsolationBIU Bus Interface UnitBKPRT Backup PartitionBLK BlockedBLOCK-AID Blocked Trunk IdentificationBLST Board Level Self TestBOLO Back Out Last OfficialBPCF Blade Packet Control FunctionBPH Beginning PhaseBPI Bytes Per InchBPSN Back Plane Serial NumberBSC Base Station ControllerBSN Block Sequence NumberBTL Bell Telephone LaboratoriesBTS Base Transceiver StationBTS Base Transceiver SystemBTS-FMS Base Transceiver System - Flexent Mobility ServerBUD Backlog Update DatabaseBWM Broadcast Warning Message

C/D Control/DisplayCA Community AddressCALGC Calibration and Gain ControlCAP CapacityCAS Channel Associated SignalingCAT Clock and ToneCATP Conditional All Tests PassedCBA Changeback AcknowledgementCBR Code Division Multiple Access Baseband RadioCC Central ControlCC Channel ConditionCCC Code Division Multiple Access Cluster ControllerCCC-2G Code Division Multiple Access Cluster Controller Second GenerationCCC-3G Code Division Multiple Access Cluster Controller Third GenerationCCF Conditional Call ForwardingCCF Custom Calling FeatureCCIO Central Control Input/OutputCCIS Common Channel Interoffice SignalingCCO Customer Controlled OperationCCS Common Channel Signaling




CCS Common Command SetCCS6 Common Channel Signaling System 6CCS7 Common Channel Signaling System 7CCU Code Division Multiple Access Channel UnitCCU Channel Control UnitCCU-2G Code Division Multiple Access Channel Unit Second GenerationCCU-32 Enhanced Code Division Multiple Access Channel UnitCCU-3G Code Division Multiple Access Channel Unit Third GenerationCDB Command Descriptor BlockCDBS Code Division Multiple Access Distributed Base StationCDM Code Division Multiple Access Digital ModuleCDMA Code Division Multiple AccessCDN Call Processing/Database NodeCDN-II Call Processing/Database Node IICDN3 Ring Call Processing/Database NodeCDNI Call Processing/Database Node IntegrityCDPD Cellular Digital Packet DataCDR Channel Data RegisterCE Channel ElementCE Critical EventCEM Channel Element ModemCEPT Conference on European Postal and Telecommunications AdministrationsCF Call ForwardingCFR Configure Flexible RatingCFT CraftCGSA Cellular Geographic Service AreaCH ChannelCHN ChannelCHPAM Cellular High Power Amplifier ModuleCI Control InterfaceCIA Critical Indicator AdministratorCIC Circuit Identification CodeCICC Common Intelligent Carrier CardCIM Channel Initialization and MonitorCIN Circuit Identification NumberCIP Command In ProgressCLAC Code Division Multiple Access Linear Amplifier CircuitCLAN Cluster Local Area NetworkCLEI Common Language Equipment IdentifierCLGC Closed Loop Gain ControlCLI Command Line InterfaceCLLI Common Language Location IdentifierCLP Cluster ProcessorCLSI Cell Site IntegrityCM Communication ModuleCMDPSG Command Programmable Serial GatewayCMLT Code Division Multiple Access Mobile Loopback Test




CMMCEQP Code Division Multiple Access Flexent CodeDivision Multiple Access Distributed Base Station Equipage

CMRFTG Connection Manager Reference Frequency Timing GeneratorCMSCT Connection Manager Synchronous Clock and ToneCN Cellular NetworkingCNAM Calling Party NameCNAT Changeable No Answer TimerCNC Central Node ControlCNCE Common Channel Signaling Network Critical EventCNI Common Network InterfaceCNID Control Network IdentificationCNR Critical Node RecoveryCOACC Code Division Multiple Access mobile originated Short Message

Service Over Access ChannelCOB Call ObservationCOMB CombinedCOMGR Command GroupCONDITIONAL ConditionalCONF ConferenceCONFIG ConfigurationCONT ControllerCOO Change-Over OrderCORBA Common Object Request Broker ArchitectureCOT ContinuityCP Call ProcessingCP Central ProcessorCP Command PresentCP Communications ProcessorCPB Call Processing BurstCPC Common Power ConverterCPC Concerned Point CodeCPI Central Processor InterventionCPI Communications Processor InterfaceCPM Call Processing MainCPN Calling Party NumberCPREGTRACE Call Processing Registration Glare for Active Call ReportingCPSECOND Call Processing Second Page Response Reporting FlagCPSG Call Processing Setup Glare ReportingCPU Central Processor UnitCQT Circuit Query TestCRC Code Division Multiple Access Radio ControllerCRC Cyclic Redundancy CheckCRT Cathode Ray TerminalCRTU Code Division Multiple Access Radio Test UnitCS Cell SiteCSB Carrier Service Option Class [SOC] Backhaul Server [BHS]CSC Cell Site ControllerCSC0 Cell Site Controller 0




CSC1 Cell Site Controller 1CSCANS Customer Service Computer Access Network StandardsCSDIP Character Special Device Interface ProcessCSN Cell Site NodeCSNE Cell Site Node EnhancedCSOP Coordinator of Spooler Output ProcessesCSP Cell Site ProcessorCSPC Cell Site Processor ControllerCSU Cache Store UnitCTRC Call TraceCTRM Code Division Multiple Access Test Radio ModuleCTU Code Division Multiple Access Transmit UnitCTU Clock and Timing UnitCU Control UnitCUMEM Control Unit MemoryCURSTRMV Control Unit Restore or RemoveCUSTAT Control Unit Hardware StatusCVT Circuit Validation TestCW Call Waiting

DA Dynamic AssignmentDACS Digital Access and Cross-Connect SystemDAP Display Administration ProcessDAT Digital Audio TapeDAT Disconnect Acknowledgement TimerDB DatabaseDBDM Database Download MechanismDBMS Database Management SystemDBS Duplex Bus SelectorDC Digital Control ChannelDCCH Digital Control ChannelDCF Defensive Check FailureDCHN D-Channel NodeDCI Dual Serial Channel/Computer InterconnectDCIS Direct Signaling MessagesDCIU Dual Serial Channel Computer Interconnect UnitDCS Digital Cellular SwitchDCSID Digital Cellular Switch IdentificationDCT Dispatch Control TableDCTE Dispatch Control Table EntryDCTEXT Dispatch Control Table ExtendedDDSBS Duplex Dual Serial Bus SelectorDEX Demand ExerciseDFC Disk File ControllerDFI Digital Facility InterfaceDFSA Data File System AccessDFU Digital Facility UnitDGN Diagnose




DGTSEND Digit SenderDHCP Dynamic Host Configuration ProtocolDIA Direct Internet AccessDIAGC Diagnostic Control ProgramDIAMON Diagnostic MonitorDICLA Dual-Individual Carrier Linear AmplifierDIO Direct Input/OutputDIOP Disk Independent OperationDIVBRIND Diversity Imbalance ErrorDKDRV Disk DriverDL Data LinkDLGSHL Dialogue ShellDLI Data Link InterfaceDLN Direct Link NodeDM Disconnected ModeDMA Direct Memory AccessDMAC Direct Memory Access ControllerDMEMBER Dynamic MemberDMH Data Message HandlerDMQ Deferred Maintenance QueueDN Directory NumberDNFS Dedicated Network File ServiceDNMOD Directory Number ModificationDOCR Dynamic Outgoing Call RestrictionDPC Destination Point CodeDPD Digital Pre-DistortionDPT Diagnostic Phase TableDRC Data Rate ChannelDRM Digital Radio ModuleDRS Data Replication ServiceDRU Digital Radio UnitDS0 Digital Signal Level 0DS0-A Digital Signal Level 0 ADS0s Digital Signal Level 0DS1 Digital Signal Level 1DSC Dedicated Switch ConnectionDSCH Dual Serial ChannelDSM Disk Suite MirroringDSN Digital Switch NodeDTR Data Terminal ReadyDUI Direct User InterfaceDUIC Direct User Interface ControllerDV Digital VoiceDV-DRM Digital Voice Digital Radio ModuleDVCC Digital Verification Color Code




EAI Emergency Action InterfaceEAIINT Emergency Action Interface Error InterruptEAR Error Analysis and RecoveryECD Equipment Configuration DatabaseECDA Equipment Configuration Database AccessECDLIB Equipment Configuration Database LibraryECDMAN Equipment Configuration Database ManagerECI Equipment Catalog IndexECID Executive Cellular Processor Call IdentificationECMA European Computer ManufacturersECP Executive Cellular ProcessorECP-AMA Executive Cellular Processor - Automatic Message AccountingECPC Executive Cellular Processor ComplexECPID Executive Cellular Processor IdentificationECU Enhanced Channel UnitECU-32 Enhanced Code Division Multiple Access Channel UnitEDI Engineering Design InformationEDPD Enhanced Digital Pre-DistortionEDRU Enhanced Digital Radio UnitEESN Easy Electronic Serial NumberEGRASP Enhanced Generic Access PackageEGSF Expanded General System FailureEIH Error Interrupt HandlerEIN Ethernet Interface NodeEINE Application Processor Ethernet Interface Node - EnhancedEINLINK Ethernet Interface Node LinkEIR Enhanced Information ReportEISO End of IsolationEKCC Enhanced Kill Call CapabilityEKILLCALL Enhanced Kill Call CapabilityEMDN Empty Mobile Directory NumberEMM Expanded Main MemoryEMS Element Management SystemEMSCLI Element Management System Command Line InterfaceEOF End Of FileEOH End Of HeaderEOM End Of MediumEOP End Of PartitionEOP/M End Of Partition/MediumEPCF Ethernet Packet Control FunctionEPH Ending PhaseEQL Equipment LocationER Error RegisterERRINT Error InterruptESC Ethernet Switch CardESD Extended Sense DataESID Extended System/Switch IdentificationESN Electronic Serial Number




ET Electronic TransferETNN Expanded Trunk Network NumberETOM Enhanced Time Division Multiple Access Oscillator ModuleEVC 1xEV-DO ControllerEVM 1xEV-DO ModemEVOL EvolutionEXIT-R Extended Information Product Tandem Signaling for Non-Home

SubscriberEXP ExpansionEXT ExtendedEXT External Test

FACIL Facility Access TypeFAF Feature Activation FileFANALM Fan AlarmFAP Feature Activation ProcessFARCA Far End Community AddressFBO First Block OffsetFBS First Block SequenceFCCCH Fundamental Common Control ChannelFCI Forward Call IndicatorFDBMS Flexent Database Management SystemFEPC Far End Point CodeFESS Far End Signaling ServerFFER Forward Frame Error RateFFS Flash File SystemFIFO First-In, First-OutFITS Factory Installation Test SystemFLCA Flexible Channel AllocationFLM Forward Link ModuleFLOW Flow Analysis ModuleFLUS Forward Link User SimulationFM FilemarkFMGR File ManagerFMM Flexent Mobility ManagerFMM-AMA Flexent Mobility Manager - Automatic Message AccountingFMMTR Flexent Mobility Manager TranslationsFMP Fraudulent Mobile PrintFMS Flexent Mobility ServerFOM Fiber Optic ModuleFOMP Fiber Optic Module PortFP Filter PanelFP Frame PointerFPCR Full Point Code RoutingFPGA Field Programmable Gate ArrayFPI Full Process InitializationFPO First Primary OffsetFPS First Primary Sequence




FRBC Frame Relay Bearer ChannelFRBCD Frame Relay Bearer Channel DaemonFREQ FrequencyFRMR Frame Reject ResponseFRSVCD Frame Relay Switched Virtual Circuit DaemonFS Frame SelectorFSC Forward Setup ChannelFSNAME File System NameFSO First Secondary OffsetFSRM Frame Selector Resource MonitorFSS First Secondary SequenceFSU Forward SetupFT Fault TolerantFT Functional TestFT-LAN Fault Tolerant Local Area NetworkFTAP Forward Test Access ProtocolFTC Forward Traffic ChannelFTM Front Transition ModuleFTP File Transfer ProtocolFTS Field Test SetFUDBERRNO Field Update Database ErrorsFX Flexent

G3 Growth Frame 3G4 Growth Frame 4G5 Growth Frame 5GCSL Global Call Status ListGDF Generic Description FileGI Group InterfaceGICC Gateway Intelligent Carrier CardGLS Global Location ServiceGOOS Go Out Of ServiceGPS Global Positioning SystemGRASP Generic Access PackageGRE Generic Routing EncapsulationGSF Generic Specification FileGT Global TitleGTT Global Title TranslationGUI Graphical User InterfaceGW Gateway

HA Host AdapterHCPU High Capacity Core Processing UnitHDB3 High Density BipolarHDR HeaderHEH Hardware Error HandlerHEHMSG Hardware Error Handler ReportsHFDT History File Table




HLR Home Location RegisterHOBIT Hand-off Based on InterferenceHOC Host CollectorHP-UX Hewlett Packard UNIX

HPCA High Power Personal Communication Service Code DivisionMultiple Access Amplifier

HROC High Data Rate Reverse Overload ControlHSD High-Speed Synchronous Data LinkHSDC High-Speed Synchronous Data Link ControllerHSL High Speed Signaling System 7 LinkHSR Hardware Status RegisterHTTP Hyper Text Transfer ProtocolHV Hardware VersionHVLR Home Visitor Location RegisterHVLR-IM Home Visitor Location Register Integrity ManagerHW Hardware

I IndexI/O Input/OutputIBLM Inter-Band Load ManagementICF Immediate Call ForwardingICMP Internet Control Message ProtocolICOS Increased Court-Ordered SurveillanceICRT Incoming Call Response TimerICTRC Immediate Call TraceID IdentificationIDENT IdentityIFB Interframe BufferIHLR Integrated Home Location RegisterILCD Immediate Long Call DetectionILI Incorrect Length IndicatorIM Input MessageIM Integrity ManagerIM Integrity MonitorIM Interrupt MaskIMDCA Mobile Switching Center Dynamic Channel AllocationIMS Interprocessor Message SwitchIMSDRV Interprocessor Message Switch DriverIMSI International Mobile Station IdentityIMSLT Idle Mobile Subscriber Location TraceINIT InitializationINLA Interference Look AheadIODRV Input/Output Processor DriverIOP Input/Output ProcessorIOS Inter-Operability SpecificationIOU Input/Output UnitIP Information ProductIP Internet Protocol




IP-RCS Internet Protocol - Radio Cluster ServerIPBH Internet Protocol BackhaulIPBTSGW Internet Protocol Base Transceiver Station GatewayIPGW Internet Protocol GatewayIPL Interrupt Priority LevelIRN Integrated Ring NodeIRN2 Integrated Ring Node 2IS In ServiceIS Interrupt SourceIS41 Interim Standard 41ISC Initialization Sequence ControlISC Intelligent Serial ControllerISDN Integrated Services Digital NetworkISO International Standards OrganizationISPage Inter-System PageISR Integrated Services Digital Network User Part RegisterISR Interprocessor Message Switch User Node Soak RestoreISUP Integrated Services Digital Network User PartITU International Telecommunication UnionIUN Interprocessor Message Switch User NodeIVT Intervendor TrunkIWF Interworking FunctionIWFA Interworking Function ApplicationIWFACCT Interworking Function AccountingIWFAUTH Interworking Function AuthenticationIWFCC Interworking Function Call ControlIWFDIA Interworking Function Direct Internet AccessIWFL2TP Interworking Function Level 2 Tunneling ProtocolIWFMAINT Interworking Function MaintenanceIWFMBI Interworking Function Modem Bank InterfaceIWFPE Interworking Function Protocol Engine

JIP Jurisdiction Information Parameter

KOP Kernel Overwrite ProcessKTF Korea Telecom FreetelKW Keyword

L LocateL-DRM Locate Digital Radio ModuleL-DRU Locate Digital Radio UnitL-RCU Locate Radio Channel UnitL2TP Level 2 Tunneling ProtocolLAC Linear Amplifier CircuitLAC Location Area ClusterLACID Logical Link IdentificationLAES Lawfully Authorized Electronic SurveillanceLAF Linear Amplifier Frame




LAF Logical Antenna FaceLAG Link Aggregation GroupLAN Local Area NetworkLAPD Link Access Procedure D-ChannelLAUN Linear Amplifier Unit NumberLBC Loopback ClearLBO Last Block OffsetLBS Last Block SequenceLC Locate ChannelLCD Long Call DetectionLCP Lost Call Call ProcessingLCSL Local Call Status ListLDFT Load Disk From TapeLDI Laboratory Design IssueLFS Link Fault SectionalizationLI Length IndicatorLI Link InterfaceLI4 Link InterfaceLIB LibraryLID0 Link Interface Digital Signal Level 0LIMA Location Independent Message AddressingLIU Line Interface UnitLLC Link Layer ConnectionLLI Linked List IndexedLMT Lightguide Microcell/Modular Cell TransceiverLN Link NodeLNA Low Noise Receive AmplifierLPG Logical Processor GroupLPO Last Primary OffsetLPS Last Primary SequenceLRN Location Routing NumberLS Link SetLSA Limited Service AreaLSB Error valueLSCMLT Last Seen Cell Mobile Location TraceLSL Low Speed Signaling System 7 LinkLSO Last Secondary OffsetLSS Last Secondary SequenceLSS Lucent Soft SwitchLSSU Link Status Signal UnitLTI Lucent Technologies InfrastructureLU Logical Unit

MAC Media Access ControlMAEC Media Access Error CounterMAN ManualMAS Main StoreMAS Mobile Activity Supervision




MASA Main Store ArrayMASC Main Store ControllerMAX Medium Access LayerMB Modem BankMBD Message Buffer DumpMC Main ControllerMC MicrocodeMCA Multi-Carrier AmplifierMCAT Manual and Cell Configuration and Cell TestMCB Message Control BlockMCC Maintenance Control CenterMCCPE Multiple Units with the Same Directory Number Customer Changeable

Primary Electronic Serial NumberMCH Maintenance ChannelMCO Manual Change OverMCR Mobile Call RegisterMCR Multiple Carrier RadioMCRT Maintenance Console Request TerminalMCS Message Communication SubsystemMCT Malicious Call TraceMDCT Minor Device Chain TableMDN Mobile Directory NumberMF Multi-FrequencyMFC Multi-Frequency CompelledMFFU Modular Fuse / Filter UnitMFGR ManufacturerMHD Moving Head DiskMHD0 Moving Head Disk 0MHD1 Moving Head Disk 1MIN Mobile Identification NumberMIRA Maintenance Input Request AdministratorMLAC Multiple Linear Amplifier CircuitMLG Multi-Link GroupMLTS Micro Level Test SetMM Measurement ModuleMM Mobility ManagerMM-AP Mobility Manager Application ProcessorMM-APC Mobility Manager Application Processor ClusterMM-DLN Mobility Manager Direct Link NodeMM-HVLR Mobility Manager Home Visitor Location RegisterMM-RCS Mobility Manager Radio Cluster ServerMM-ROP Mobility Manager Read Only PrinterMM-SS7 Mobility Manager Signaling System 7MM-VCA Mobility Manager Voice Channel AdministrationMMA Message Mapping ApplicationMMSA Multiple Microcell Shared AntennaMO Managed ObjectMOC Measurement Output Control




MOCT Measurement Output Control TableMOH Managed Object HandleMOOS Manual Out Of ServiceMOP Mount Off Line PartitionMOST Mobile Station TestMPC Mobile Positioning CenterMPSC Managed Purchased System CapacityMRA Maintenance Request AdministratorMRAQ Maintenance Request Administrator QueueMRF Maintenance Reset FunctionMRS Message Recording ServiceMRS Message Recording/Retrieval ServiceMRS Message Retrieval ServiceMRVA Message Transfer Part Routing Verification AcknowledgementMRVR Message Routing Verification ResultMRVT Message Routing Verification TestMS Message SegmenterMS Mobile SubscriberMS Multi-SectorMSC Mobile Switching CenterMSCDBMS Mobile Switching Center Database Management SystemMSCID Mobile Switching Center IdentificationMSGBUF Message BufferMSID Mobile Station IdentificationMSO Multiple Size OptionMSRE Mobile Status Report EnhancementMSU Message Signal UnitMT Magnetic TapeMT0 Magnetic Tape 0MT1 Magnetic Tape 1MTC Magnetic Tape ControllerMTCE MaintenanceMTM Master Timing ModuleMTP Message Transfer PartMTSO Mobile Telephone Switching OfficeMTTY Maintenance TeletypewriterMTTYC Maintenance Teletypewriter ControllerMULTI Multiple ConfigurationsMUSDN Multiple Units with the Same Directory NumberMV Maintenance ValueMV Model VersionMWI Message Waiting IndicatorMb Megabytes

N/A Not AvailableNA Not ApplicableNA Not AvailableNAK Negative Acknowledgment




NAT Network Access IdentifierNAUD Node AuditNCC Network Cross ConnectNCI Network Control InterfaceNCID Network Connection IdentifierND Non-Volatile Memory DriverNE Network ElementsNE Not EquippedNEARCA Near End Community AddressNEWSFX New SuffixNFS Network File SystemNGN Next Generation NetworkNGN-AP Next Generation Network - Application ProcessorNI Node IntegrityNIASRT Node Integrity AssertNIC Network Interface CardNID Network IdentifierNIP Network Interface PointNM Network ManagementNNBRDB Network NeighborNODEST Node StateNON-ATCC Non-Auto-Tune Cavity CombinerNO_RTE No RouteNP Node ProcessorNP Number PortabilityNP-LI Node Processor Link InterfaceNP-SCP Number Portability Service Control PointNPA Numbering Plan AreaNSD Network Services DivisionNSN National Significant NumberNSNL Network Serial Number ListNTB Network Test BeaconNTP Network Time ProtocolNTWK NetworkNTWK_O Network OnlyNVM Non-Volatile Memory

OA&M Operations, Administration, and MaintenanceOAI Open Air InterfaceOAI-AP Open Air Interface Application ProcessorOAMPROXY Operations, Administration and Maintenance ProxyOBGC On Board Gain ControlOC Overhead ChannelOC Overload ControlOC3 Optical Carrier Level 3OCNS Orthogonal Channel Noise SimulatorODD Office Dependent DataODIN On Line Data Integrity




ODPC On-Demand Pilot Strength Measurement Message CollectionODPCD On-Demand Pilot Strength Measurement Message Collection DaemonOFC OfficialOFD Operational Fault DetectionOFD-A Operational Fault Detection AccessOFD-ACCESS Operational Fault Detection ACCESSOFD-CAP Operational Fault Detection CapacityOFD-MS Operational Fault Detection Multi-SectorOFD-PG Operational Fault Detection PagingOFL Off LineOFLBOOT Off Line BootOFLDISK Off Line DiskOHM Over Head ManagerOIF Optical Interface FrameOKP Operational Kernel ProcessOLDSFX Old SuffixOLGC Open Loop Gain ControlOLMP On Line Mount PointOM Oscillator ModuleOM Output MessageRAN Operations and Maintenance CenterOMC-RAN Operations and Maintenance Center - Radio Access NetworkOMDB Output Message DatabaseOMP Operations Maintenance PlatformOMP-FX Operations Maintenance Platform for Flexent

OOF Out Of FrameOOS Out Of ServiceOOS-M Out Of Service ManualOOSL Out Of Service LimitOPC Origination Point CodeORCA Operations and Maintenance Center - Radio Access Network

Common Object Request Broker Architecture AgentOS Operating SystemOSDS Operating System for Distributed SwitchingOST Operating System TrapOTA Over-The-Air ActivationOTL Originating Test LineOTU Optical Transceiver UnitOVRWT Overwrite

PA Page/AccessPA Program AddressPAC Peripheral Alarm CardPACA Priority Access and Channel AssignmentPAF Physical Antenna FacePAS Project Accounting ServicePAS Protected Application SegmentPASA Project Accounting Service Authorization




PASV Project Accounting Service ValidationPAUTH Personal AuthorityPBI Peripheral Bus InterfacePC Peripheral ControlPC Point CodePCA Personal Communication Service Code Division Multiple Access

AmplifierPCB Process Control BlockPCBR Pre-Distortion Code Division Multiple Access Baseband RadioPCF Packet Control FunctionPCFCC Packet Control Function Call ControlPCFMAINT Packet Control Function MaintenancePCGRP Person Command GroupPCPAUD Processor Control Process AuditPCPEIH Processor Control Process Error Interrupt HandlerPCPMD Processor Control Process Maintenance DriverPCR Preventative Cyclic Redundancy Error CorrectionPCRID Processor IdentificationPCS Packet Core SwitchPCS Personal Communication ServicePCSD Peripheral Control SubdevicePCT Processor Configuration TablePCU Power Converter UnitPDC Periodic Data Collection PeriodPDSN Packet Data Serving NodePDT Page Descriptor TablePDT Physical Disk-to-TapePE Protocol EnginePG PagingPGT Page TablePH Protocol HandlerPHGRP Protocol Handler GroupPHPAM Personal Communication Service High Power Amplifier ModulePIC Peripheral Interface ControllerPIC Primary Interexchange CarrierPICB Peripheral Interface Control BusPICL Platform Information and Control LibraryPID Process IdentificationPIN Personal Identification NumberPIO Peripheral Input/OutputPIO Processor Input/OutputPIO Programmed Input/OutputPL Pilot LevelPLIB Public LibraryPLM Power Level MeasurementPMCR Plant Measurement Common ReportPMDB Process Message Data BlockPMGR Process Manager




PMS Plant Measurements SystemPMUX Point-to-Point Protocol MultiplexorPO Percent OccupancyPO Processor OccupancyPOPCLU Populated ClusterPOST Power On Self TestPP Packet PipePPM Parts Per MillionPPP Point-to-Point ProtocolPPS Packets Per SecondPPS Pulse Per SecondPPU Partial Parameter UpdatePR Periodic ResetPRI Primary Rate InterfacePRM Processor Recovery MessagePROFL ProfilePS Pilot/SyncPSA Pilot/Sync/AccessPSAX PacketStar Access GatewayPSBR Primary Segment Base RegisterPSC Processor Signaling CongestionPSLT Periodic Signaling Link TestPSM Power Switch MonitorPSMM Pilot Strength Measurement MessagePSSWDPFX Password PrefixPSSWDSFX Password SuffixPSTN Public Switched Telephone NetworkPSU Packet Switching UnitPSW Program Status WordPTR Programmable Treatment RoutingPVC Permanent Virtual CircuitPVSI Positive Verification System InterfacePZID Packet Zone Identifier

QBC QUICC Bus ClearQFAF Feature Activation File with QualificationQFE Quad Fast Ethernet

R-P Radio PacketR-P Radio ProtocolRA RadioRAC Ring Access CircuitRADIUS Remote Authentication Dial In User ServiceRAID Redundant Array of Independent DisksRAM Random Access MemoryRAN Radio Access NetworkRAO Regional Accounting OfficeRAP Ring Application Processor




RATI Random Access Terminal IdentifierRC/V Recent Change / VerifyRCC Radio Control ComplexRCC-OA&M Radio Control Complex/Operations, Administration and MaintenanceRCG Reference Calibration GeneratorRCMS Read Only Printer Client Message ServiceRCS Radio Cluster ServerRCS-IP Radio Cluster Server - Internet ProtocolRCT Route Set Congestion TestRCU Radio Channel UnitRDBU Ring Database UpdateRDI Remote Defect IndicationREACH Reverse Enhanced Access ChannelREGCANC Registration CancellationREGNOT Registration NotificationREJ RejectREMACS Remote Access SystemREX Routine ExerciseRF Radio FrequencyRFER Reverse Frame Error RateRFS Recent Change / Verify Form SecurityRFTG Reference Frequency Timing GeneratorRFU Radio Frequency UnitRG Reference GeneratorRG Roamer GreetingRGDB Roamer Greeting DatabaseRGRASP Ring Generic Access PackageRI0 Ring Interface 0RI1 Ring Interface 1RID Record IdentificationRIM Radio Network Controller Integrity MonitorRIMAST Radio Network Controller Integrity Monitor Assert BrevityRLM Reverse Link ModuleRLOOK Receiver Look-UpRLP Radio Link ProtocolRM Ring MonitorRMB Removable MediumRMF Recovery Message FormatterRMS Routine Maintenance SchedulerRN Ring NodeRNA Ring Node AddressRNC Radio Network ControllerRNC-AP Radio Network Controller Application ProcessorRNCDB Radio Network Controller DatabaseRNCDBMS Radio Network Controller Database Update ManagerRNCM Radio Network Controller ManagerRNR Receive Not ReadyROM Read Only Memory




ROP Read Only PrinterROS Request Out Of ServiceRPC Ring Peripheral ControllerRPCD Ring Peripheral Controller DeviceRPCN Ring Peripheral Controller NodeRPI Return to the Point of InterruptRPI Routing Priority IndexRSP Radio Test Unit Switch PanelRSPFAIL Radio Test Unit Switch Panel Comm FailureRSSI Received Signal Strength IndicatorRSU Reverse SetupRSUFIRST Reverse Setup FIRST ErrorRTAP Reverse Test Access ProtocolRTC Real Time ClockRTR Real Time ReliableRTS Real Time StatusRTU Radio Test UnitRTX Real Time ExecutiveRU Receiver UnitRUBRIM Ring Database Update Bridge Process MonitorRXAMP Receive AmplifierRXAUD Receive AudioRXBER Receive Bit Error RateRXGAIN Receive GainRXPWR Receive PowerRelAdr Relative Addressing

S SetupS StatementS-DRM Setup Digital Radio ModuleS-RCU Setup Radio Channel UnitS7 System 7SAAL Signaling Asynchronous Transfer Mode Adaptation LayerSABM Set Asynchronous Balanced ModeSADC Special Access Data ChannelSAR Store Address RegisterSAT Store Address TranslatorSAT Supervisory Audio ToneSBP Special Bearer PathSBR0 Segment Base Register 0SBR1 Segment Base Register 1SBR2 Segment Base Register 2SBR3 Segment Base Register 3SBR4 Segment Base Register 4SBR5 Segment Base Register 5SBR6 Segment Base Register 6SBR7 Segment Base Register 7SBSP Simple Base Transceiver System Startup Protocol




SBUS Small Computer System Interface BusSC Shelf ControllerSC Stable ClearSC-GICC Shelf Controller Gateway Intelligent Carrier CardSCANS Software Change Administration and Notification SystemSCANS-2 Software Change Administration and Notification SystemSCB System Controller BoardSCC Switching Control CenterSCC Synchronous Communications ControllerSCCP Signaling Connection Control PartSCHD ScheduleSCID Switch Call IdentificationSCM Station Class MarkSCMG Signaling Connection Control Part ManagementSCN Special Cellular NetworkingSCOC Signal Connection Control Point Oriented ControlSCP Service Control PointSCR Store Control RegisterSCS Sound Call ServiceSCSD Scanner Signal DistributorSCSDA Scanner Signal Distributor AdministratorSCSDC Scanner Signal Distributor ControllerSCSDH Scanner Signal Distributor HandlerSCSI Small Computer System InterfaceSCSM Selectable Cell Site MessagingSCT Synchronous Clock and ToneSDC Store Data ControlSDCA Short Distance Charging AreaSDD Subscriber Dialed DigitsSDE Segment Descriptor EntrieSDL Synchronous Data LinkSDLC Synchronous Data Link ControllerSDLRTC Synchronous Data Link Restore Tool Communications Protocol

HandlerSDLRTN Synchronous Data Link Restore Tool Network Protocol HandlerSDP Software Demand PagingSDP Status Display PageSDR Store Data RegisterSDS Shared Data SegmentSDT Segment Descriptor TableSFAP Subscriber Form Activity PrintSFM Selector Function MainSFW SoftwareSG Server GroupSG System GenerationSGEN System GenerationSH Speech HandlerSHLR Standalone Home Location Register




SI System IntegritySIB Status Indicator BusySID System IdentificationSIE Status Indication EmergencySII Series IISII-CS Series II Cell SiteSIM System Integrity MonitorSIMCNTL System Integrity Monitor ControlSIN Status Indication NormalSIO Status of Out-of-AlignmentSIO System Integrity OutputSIOF System Integrity Output FormatterSIOS Status Indication Out-of-ServiceSIP Simple-Internet ProtocolSJB Small Computer System Interface Job BlockSJR Small Computer System Interface Job ResponseSLC Signaling Link CodeSLK Signaling LinkSLM Signaling Link ManagementSLMK Signaling Link Maintenance KernelSLPO Signal Link Processor OccupancySLS Signaling Link SelectionSLT Signaling Link TestSM Service MeasurementsSM Switching ModuleSMD Storage Module DeviceSMEMBER Static MemberSMM Standard Main MemorySMP Sub-Mobile Switching Center PagingSMPA Sub-Mobile Switching Center Paging AreaSMS Short Message ServiceSMTC Serving Mobile Switching Center LucentSMV Selectable Mode VocoderSN Serial NumberSNAT Current Network Administration TimeSNMP Simple Network Management ProtocolSOF Spooler Output FunctionSOP Spooler Output ProcessSOPC Source Origination Point CodeSP Signaling ProcessorSP Stack PointerSP Status Display ProcessSPC Small Computer System Interface Protocol ControllerSPI Security Parameter IndexSPINA Subscriber Personal Identification Number AccessSPINI Subscriber Personal Identification Number InterceptSPINNIPIN Subscriber Personal Identification Number Intercept Personal

Identification Number




SPINNITRIGGERS Subscriber Personal Identification Number InterceptTrigger

SPM Signal Processing ModuleSPP Single Process PurgeSRAM Static Random Access MemorySRCU Setup Radio Channel UnitSRST Signaling Route Set TestSRV ServerSRVA Signaling Connection Control Part Routing Verification

AcknowledgementSRVR Signaling Connection Control Part Routing Verification ResultSRVT Signaling Connection Control Part Routing Verification TestSS7 Signaling System 7SS7-LINK Signaling System 7 LinkSS7HSL Signaling System 7 High Speed LinkSS7LSL Signaling System 7 Low Speed LinkSS7MM Signaling System 7 Message ManagerSS7MMA Signaling System 7 Message Manager ApplicationSSBR Secondary Segment Base RegisterSSD Shared Secret DataSSDW Second Start Dial WinkSSN Subsystem NumberSSR System Status RegisterST Signaling ToneST1 Stream 1ST2 Stream 2STBY StandbySTF Some Tests FailedSTOP StoppedSTP Signal Transfer PointSU SetupSU Software UpdateSUERM Signal Unit Error Rate MonitorSUGR Software Update Generic RetrofitSVC Switched Virtual CircuitSWI Switch IntegritySWNO Switch NumberSYSGEN System GenerationSaR Segmentation and Reassembly

T1FA T1 Facility AccessTA Test ApplicationTAR0 Trapped Address Register 0TAR1 Trapped Address Register 1TAUTH Terminal AuthorityTC Transient ClearTCAP Transaction Capabilities Application PartTCGRP Terminal Command Group




TCN T1 Facility Access Control NodeTCP Transmission Control ProtocolTCRI Task Control Register IndexTCS Traffic Control ServerTCU Thirteen-Kilo-bit Code Division Multiple Access Channel UnitTD Time Division Multiplex DriverTDM Time Division MultiplexTDMA Time Division Multiple AccessTDU Test and Diagnostic UnitTE Traffic EngineeringTELEPRO1 Teleprocessing Process 1TELEPRO2 Teleprocessing Process 2TEMP TemporaryTERM TerminalTFA Transfer AllowedTFU Time Frequency UnitTG Trunk GroupTGL Trunk Group ListTI Technician InterfaceTIA Telecommunications Industry AssociationTICC Traffic Intelligent Carrier CardTICLI Technician Interface Command Line InterfaceTID Transaction IdentificationTIOP Technician Interface Output ProcessorTISSUE Technician Interface Shell Security User EnhancementTLDB Trouble Location DatabaseTLDN Temporary Local Directory NumberTLP Trouble Locating ProcedureTM TimerTM Trunk Group MemberTM Trunk MaintenanceTMP TemporaryTMR Timer RegisterTOD Time of DayTOP Task Oriented PracticeTP Traffic ProcessorTPC Translation Point CodeTPS Teleprocessing SystemTPU Traffic Processing UnitTPU Transaction Processing UnitTPUCLI Traffic Processing Unit Command Line InterfaceTPUGUI Traffic Processing Unit Graphical User InterfaceTPUL Traffic Processing Unit LoggerTRBL TroubleTRC Time Division Multiple Access Radio ControllerTRKGRP Trunk GroupTRN Temporary Reference NumberTRSP Test Radio Switch Panel




TRTU Time Division Multiple Access Radio Test UnitTSP Translation Signaling PointTSS Time Stamp ServiceTT Traffic TypeTT Translation TypeTTL Terminating Test LineTTLNA Tower Top Low Noise AmplifierTTY TeletypewriterTTYC Teletypewriter ControllerTWC Three Way CallingTX TransmitTXAMP Transmit AmplifierTXOUTLOCK Transceiver Out of LockTXPORT Transmit PortTXWATTS Transmit WattageTrmIOP Terminate Input/Output Process

UA Unconditional AcknowledgementUART Universal Asynchronous Receiver/TransmitterUARTFAIL Universal Asynchronous Receiver/Transmitter self-test FailureUATI Universal Access Terminal IdentifierUC Unique ChallengeUC User ChannelUC Utility CircuitUCB Unit Control BlockUCL UnconditionalUCS User Control StringUDA User Defined Cell Site AlarmsUDP User Datagram ProtocolUDPC Unknown Destination Point CodeUER Microinterrupt Error RegisterUID Unit IdentificationUID User IdentificationUID Utility IdentificationULAM Ultralinear Amplifier ModuleULARP UNIX Level Automatic Restart ProcessUNA UnavailableUNAV UnavailableUPOPCLU Unpopulated ClusterUPS Uninterrupted Power SupplyURC Universal Radio ControllerURC2 Universal Radio Controller 2UTMOST User Talk MostUUCP UNIX to UNIX Copy ProgramUVDT User View Descriptor TableUX UNIX

UZ User Zone




V VoiceV-DRU Voice Digital Radio UnitV-RCU Voice Radio Channel UnitVC Virtual ChannelVC Virtual ClusterVC Voice ChannelVCA Voice Channel AdministrationVCAap Voice Channel Administration on the Application ProcessorVCC Virtual Channel ConnectionVCI Verify Charge IndicatorVCI Virtual Channel IdentifierVCSA Voice Channel Selection ActivityVCVM Virtual Cluster Virtual MachineVDRU Voice Digital Radio UnitVFL Voice Frequency LinkVFLA Voice Frequency Link AccessVFLAG Video FlagVHA Virtual Home AgentVIC Vocoder is In the CellVIOP Virtual Input/Output ProcessorVIS Vocoder is In the SwitchVL Virtual LinkVLMM Very Large Main MemoryVLR Visitor Location RegisterVM Virtual MachineVMS Voice Mail SystemVMSS Vendor Message Storage SystemVOLT VoltageVP Virtual PathVPC Virtual Path ConnectionVPI Virtual Path IdentifierVPN Virtual Private NetworkVRAL Voice Radio Attenuation LevelVRCU Voice Radio Channel UnitVTOC Volume Table Of ContentsVTTY Virtual TeletypewriterVTTYC Virtual Teletypewriter ControllerVTTYDRV Virtual Teletypewriter Driver

WAP Wireless Application ProtocolWER Write Enable RingWFI Wait For IdleWIN Wireless Intelligent NetworkWNP Wireless Number PortabilityWNPWLINE Wireless Number Portability WirelineWRONGCLK Wrong Decoder ClockWTIME Wait Time




XID Exchange IdentifierXLA TranslationXML Extended Markup LanguageXTA X-Band Tracking AntennaZCS Zero Code SuppressionZOT Zone Office Trunk



Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 IM INDEX

CONTENTS

3.1 INPUT MESSAGES INDEX . . . . . . . . . . . . . . . . . . . . 1

0.2 FUNCTIONAL INDEX . . . . . . . . . . . . . . . . . . . . . 31


Issue 28 IM:INDEX-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksIM INDEX August 2005



IM:INDEX-2 Issue 28


ID............. IM:INDEXTYPE .......... Input

CHAPTER 3

INPUT MESSAGE INDEXES

3.1 INPUT MESSAGES INDEX

Table 1 lists the input messages alphabetically by message name. This index also gives themessage ID and release information.

Table 2 groups the input messages by related unit or function. A list of the units and functions bywhich messages are indexed is listed at the beginning of Table 2.


Issue 28 IM:INDEX-1



IM:INDEX-2 Issue 28


Table 1Alphabetical Index of Input Messages

Volume 11X RNC INPUT MESSAGE DESCRIPTIONS

_ ____________________________________________________________________________________________Message Name Message ID Release_ ____________________________________________________________________________________________

ALW:RNC TPU DGN ALW:RNC-TPU-DGN 24.0 and laterALW:RNC ABREVC ALW:RNC-ABREVC 25.0 and later

BKUP:RNCDB BKUP:RNCDB 24.0 and later

CLEAR:RNC GICC CLEAR:RNC-GICC 25.0 and later

COPY:RNCDB RNC COPY:RNCDB 25.0 and later

DELBKUP:RNCDB RNC DELBKUP:RNCDB 24.0 and later

EXPORT:RNC CONFIG EXPORT:RNC-CONFIG 23.0 and later

GET:RNC ABREVC GET:RNC-ABREVC 25.0 and laterGET:RNC ALARM GET:RNC-ALARM 22.0 and laterGET:RNC GICC GET:RNC-GICC 25.0 and laterGET:RNC INSTALL GET:RNC-INSTALL 24.0 and laterGET:RNC INVENTORY GET:RNC-INVENTORY 22.0 and laterGET:RNC PDSNLIST GET:RNC-PDSNLIST 24.0 and laterGET:RNC PSPCF GET:RNC-PSPCF 24.0 and laterGET:RNC STATUS GET:RNC-STATUS 24.0 and laterGET:RNC TPU DGNRESULT GET:RNC-TPU-DGNRES 24.0 and laterGET:RNC TPU FAILEDPVC GET:RNC-TPU-FAILEDPVC 23.0 and laterGET:RNC TPU INFO GET:RNC-TPU-INFO 24.0 and laterGET:RNC TPU INVENTORY GET:RNC-TPU-INVENT 22.0 and laterGET:RNC TPU STATE GET:RNC-TPU-STATE 24.0 and laterGET:RNC TPU VER CON GET:RNC-TPU-VER-CON 24.0 and laterGET:RNC TPU VERSION GET:RNC-TPU-VERSION 24.0 and laterGET:RNC VERSION GET:RNC-VERSION 22.0 and later

HALT:RNC TPU HALT:RNC-TPU 24.0 and later

IMPORT:RNC CONFIG IMPORT:RNC-CONFIG 23.0 and later

INH:RNC ABREVC INH:RNC-ABREVC 25.0 and laterINH:RNC TPU DGN INH:RNC-TPU-DGN 24.0 and later

INSTALL:RNC TPU INSTALL:RNC-TPU 24.0 and later

LOCK:RNC TPU LOCK:RNC-TPU 24.0 and later


Issue 28 IM:INDEX-3



Volume 11X RNC INPUT MESSAGE DESCRIPTIONS


LOCKOUT:RNC GICC LOCKOUT:RNC-GICC 25.0 and later

OP RNC OP:RNC 22.0 and laterOP:RNCDB RNC OP:RNCDB 24.0 and laterOP RNC TRKGRP OP:RNC-TRKGRP 22.0 and later

RESET:RNC TPU RESET:RNC-TPU 24.0 and later

RMV:AP-RNCDBMS RMV:AP-RNCDBMS 24.0 and laterRMV:AP-RNCM RMV:AP-RNCM 24.0 and laterRMV RNC TRKGRP RMV:RNC-TRKGRP 22.0 and later

RST AP-RNCDBMS RST:AP-RNCDBMS 24.0 and laterRST AP-RNCM RST:AP-RNCM 24.0 and laterRST RNC TRKGRP RST:RNC-TRKGRP 22.0 and later

SHUTDOWN:RNC TPU SHUTDOWN:RNC-TPU 24.0 and later

SWITCH:RNC SWITCH:RNC 25.0 and laterSWITCH:TOMATE RNC TPU SWITCH:TOMATE-RNC-TPU 25.0 and later

SWITCHOVER RNCDBMS SWITCHOVER:RNCDBMS 24.0 and laterSWITCHOVER RNCM SWITCHOVER:RNCM 24.0 and later

TST:BTS RNC TST:BTS-RNC 22.0 and laterTST:PSU RNC TST:PSU-RNC 23.0 and later

UNLOCK:RNC TPU UNLOCK:RNC-TPU 24.0 and later_ ____________________________________________________________________________________________


IM:INDEX-4 Issue 28



Volume 1 (Continued)1xEV-DO INPUT MESSAGE DESCRIPTIONS


ALW BTS AUD ALW:BTS-AUD 22.0 and laterALW TP AUD ALW:TP-AUD 23.0 and later

COMMIT AP COMMIT:AP 24.0 and later

DEL BTS GENERIC DEL:BTS-GENERIC 22.0 and later

DGN:BTS ASMB TXAMP DGN:BTS-ASMB-TXAMP 22.0 and laterDGN BTS CDM DGN:BTS-CDM 22.0 and laterDGN BTS-TFU DGN:BTS-TFU 22.0 and later

EXC:BTS FLUS EXC:BTS-FLUS 22.0 and later

FLUS CELL FLUS:CELL 25.0 and later

INH BTS AUD INH:BTS-AUD 22.0 and laterINH TP AUD INH:TP-AUD 23.0 and later

INIT AP INIT:AP 24.0 and laterINIT BTS INIT:BTS 22.0 and laterINIT TP INIT:TP 20.0 and later

OP:AP-IMSI-STATUS OP:AP-IMSI-STATUS 24.0 and laterOP AP OOS OP:AP-OOS 21.0 and laterOP AP-PROCCFG OP:AP-PROCCFG 23.0 and laterOP AP-VERSION OP:AP-VERSION 24.0 and laterOP BTS OP:BTS 23.0 and laterOP BTS ALARM OP:BTS-ALARM 22.0 and laterOP:BTS AMP OP:BTS-AMP 22.0 and laterOP:BTS ASMB TXAMP OP:BTS-ASMB-TXAMP 22.0 and laterOP BTS CDM OP:BTS-CDM 22.0 and laterOP BTS CDM INVENTORY OP:BTS-CDM-INVENT 22.0 and laterOP BTS FLUS OP:BTS-FLUS 22.0 and laterOP BTS GENERIC OP:BTS-GENERIC 22.0 and laterOP:BTS OOS OP:BTS-OOS 21.0 and laterOP BTS-TDU OP:BTS-TDU 22.0 and laterOP BTS-TFU OP:BTS-TFU 22.0 and laterOP CELL FLUS OP:CELL-FLUS 25.0 and laterOP OOS OP:OOS 21.0 and laterOP TP-ALARM OP:TP-ALARM 20.0 and later


Issue 28 IM:INDEX-5



Volume 1 (Continued)1xEV-DO INPUT MESSAGE DESCRIPTIONS


OP TP OOS OP:TP-OOS 21.0 and laterOP TP-STATUS OP:TP-STATUS 20.0 and laterOP TP-VERSION OP:TP-VERSION 20.0 and later

RMV AP RMV:AP 24.0 and laterRMV:BTS ASMB TXAMP RMV:BTS-ASMB-TXAMP 22.0 and laterRMV BTS CDM RMV:BTS-CDM 22.0 and laterRMV BTS-TDU RMV:BTS-TDU 22.0 and laterRMV BTS-TFU RMV:BTS-TFU 22.0 and laterRMV TP RMV:TP 20.0 and later

RST AP RST:AP 24.0 and laterRST:BTS ASMB TXAMP RST:BTS-ASMB-TXAMP 22.0 and laterRST BTS CDM RST:BTS-CDM 22.0 and laterRST BTS-TDU RST:BTS-TDU 22.0 and laterRST BTS-TFU RST:BTS-TFU 24.0 and laterRST TP RST:TP 20.0 and later

SELECT AP SELECT:AP 24.0 and later

SEND BTS GENERIC SEND:BTS-GENERIC 22.0 and later

START TAA UATI START:TAA-UATI 22.0 and laterSTART TAF UATI START:TAF-UATI 22.0 and laterSTART TAR UATI START:TAR-UATI 21.0 and later

STOP:BTS ASMB TXAMP STOP:BTS-ASMB-TXAMP 22.0 and laterSTOP BTS CDM STOP:BTS-CDM 22.0 and laterSTOP BTS-TDU STOP:BTS-TDU 22.0 and laterSTOP BTS-TFU STOP:BTS-TFU 22.0 and laterSTOP:EXC BTS FLUS STOP:EXC-BTS-FLUS 22.0 and laterSTOP FLUS CELL STOP:FLUS-CELL 25.0 and laterSTOP SEND BTS GENERIC STOP:SEND-BTS-GENERIC 22.0 and laterSTOP:TAx UATI STOP:TAx-UATI 20.1 and later

SWITCHBACK AP SWITCHBACK:AP 23.0 and later

SWITCHOVER AP SWITCHOVER:AP 24.0 and later_ ____________________________________________________________________________________________


IM:INDEX-6 Issue 28



Volume 1 (Continued)FLEXENT/EMS INPUT MESSAGE DESCRIPTIONS


ALW AP HVLR ALW:AP-HVLR 24.0 and laterALW AP-MMA ALW:AP-MMA 24.0 and laterALW CELL-DL ALW:CELL-DL 24.0 and laterALW MSCDBMS-AUD ALW:MSCDBMS-AUD 24.0 and laterALW MSCDBMS-RCV ALW:MSCDBMS-RCV 24.0 and later

AUD MSCDBMS AUD:MSCDBMS 24.0 and later

BKUP:RNCDB BKUP:RNCDB 24.0 and later

CFR AP-DS1 CFR:AP-DS1 24.0 and laterCFR:AP-SS7 CFR:AP-SS7 24.0 and laterCFR SS7 CFR:SS7 24.0 and later

COMMIT AP COMMIT:AP 24.0 and later

COPY:RNCDB RNC COPY:RNCDB 25.0 and later

CREATE MMA CREATE:MMA 24.0 and laterCREATE RCS CREATE:RCS 25.0 and later

DELBKUP:RNCDB RNC DELBKUP:RNCDB 24.0 and later

DELETE MMA DELETE:MMA 24.0 and laterDELETE RCS DELETE:RCS 25.0 and later

DGN AP-DS1 DGN:AP-DS1 24.0 and laterDGN SS7 DGN:SS7 24.0 and later

INH AP HVLR INH:AP-HVLR 24.0 and laterINH AP-MMA INH:AP-MMA 24.0 and laterINH CELL-DL INH:CELL-DL 24.0 and laterINH MSCDBMS-AUD INH:MSCDBMS-AUD 24.0 and laterINH MSCDBMS-RCV INH:MSCDBMS-RCV 24.0 and later

INIT AP INIT:AP 24.0 and later

OP ALARM OP:ALARM-EMS 14.0 and laterOP AP-ALARM OP:AP-ALARM 24.0 and laterOP AP-CMDS OP:AP-CMDS 24.0 and later


Issue 28 IM:INDEX-7





OP AP-DS1-STATUS OP:AP-DS1-STAT 24.0 and laterOP AP-DS1x-STATUS OP:AP-DS1x-STAT 15.0 and laterOP AP-INFO OP:AP-INFO 24.0 and laterOP AP-INV OP:AP-INV 24.0 and laterOP AP-IPBHINFO OP:AP-IPBHINFO 25.0 and laterOP AP-MMA-STATUS OP:AP-MMA-STAT 24.0 and laterOP AP-MMAx-STATUS OP:AP-MMAx-STAT 24.0 and laterOP AP-RCS-STATUS OP:AP-RCS-STAT 24.0 and laterOP AP-RCSx-STATUS OP:AP-RCSx-STAT 15.0 and laterOP AP-STATUS OP:AP-STATUS 24.0 and laterOP AP-VERSION OP:AP-VERSION 24.0 and laterOP:RNCDB RNC OP:RNCDB 24.0 and laterOP SS7APNET OP:SS7APNET 23.0 and laterOP SS7x-STATUS OP:SS7x-STAT 24.0 and later

RESTART MMA RESTART:MMA 24.0 and laterRESTART RCS RESTART:RCS 24.0 and later

RMV AP RMV:AP 24.0 and laterRMV:AP-AMA RMV:AP-AMA 25.0 and laterRMV:AP-AMATPS RMV:AP-AMATPS 25.0 and laterRMV AP-DS1 RMV:AP-DS1 24.0 and laterRMV:AP-HVLR RMV:AP-HVLR 24.0 and laterRMV:AP-HVLRIM RMV:AP-HVLRIM 24.0 and laterRMV AP-MMA RMV:AP-MMA 14.0 and laterRMV AP-MSCDBMS RMV:AP-MSCDBMS 24.0 and laterRMV:AP-OAMPROXY RMV:AP-OAMPROXY 24.0 and laterRMV:AP-SP RMV:AP-SP 24.0 and laterRMV AP SS7MM RMV:AP-SS7MM 24.0 and laterRMV:AP-TCS RMV:AP-TCS 24.0 and laterRMV:AP-TPUGUI RMV:AP-TPUGUI 24.0 and laterRMV:AP-VCA RMV:AP-VCA 24.0 and laterRMV RCS RMV:RCS 24.0 and laterRMV SS7 RMV:SS7 24.0 and later

RST AP RST:AP 24.0 and laterRST:AP-AMA RST:AP-AMA 25.0 and laterRST:AP-AMATPS RST:AP-AMATPS 25.0 and laterRST AP-DS1 RST:AP-DS1 24.0 and laterRST:AP-HVLR RST:AP-HVLR 24.0 and later


IM:INDEX-8 Issue 28





RST:AP-HVLRIM RST:AP-HVLRIM 24.0 and laterRST AP-MMA RST:AP-MMA 24.0 and laterRST AP-MSCDBMS RST:AP-MSCDBMS 24.0 and laterRST AP-OAMPROXY RST:AP-OAMPROXY 24.0 and laterRST:AP-SP RST:AP-SP 24.0 and laterRST AP-SS7MM RST:AP-SS7MM 24.0 and laterRST AP-TCS RST:AP-TCS 24.0 and laterRST AP-TPUGUI RST:AP-TPUGUI 24.0 and laterRST:AP-VCA RST:AP-VCA 24.0 and laterRST RCS RST:RCS 24.0 and laterRST SS7 RST:SS7 24.0 and later

SELECT AP SELECT:AP 24.0 and later

STOP MSCDBMS STOP:MSCDBMS 24.0 and laterSTOP SS7 STOP:SS7 24.0 and later

SWITCHBACK FROMAP SWITCHBACK:FROMAP 13.0 and later

SWITCHOVER:AMA SWITCHOVER:AMA 25.0 and laterSWITCHOVER:AMATPS SWITCHOVER:AMATPS 25.0 and laterSWITCHOVER AP SWITCHOVER:AP 24.0 and laterSWITCHOVER:HVLRIM SWITCHOVER:HVLRIM 24.0 and laterSWITCHOVER MSCDBMS SWITCHOVER:MSCDBMS 24.0 and laterSWITCHOVER:OAMPROXY SWITCHOVER:OAMPROXY 24.0 and laterSWITCHOVER RCS SWITCHOVER:RCS 24.0 and laterSWITCHOVER:SP SWITCHOVER:SP 24.0 and laterSWITCHOVER TCS SWITCHOVER:TCS 24.0 and laterSWITCHOVER:TPUGUI SWITCHOVER:TPUGUI 24.0 and laterSWITCHOVER:VCA SWITCHOVER:VCA 24.0 and later_ ____________________________________________________________________________________________


Issue 28 IM:INDEX-9



Volume 1 (Continued)ECP INPUT MESSAGE DESCRIPTIONS


ABT AMATAPE ABT:AMATAPE 25.0 and laterABT AMATAPE ECP ABT:AMATAPE-ECP 6.1 and laterABT CDN AUD ABT:CDN-AUD 23.0 and laterABT DLN AUD ABT:DLN-AUD 6.0 and laterABT ECP AUD ABT:ECP-AUD 25.0 and laterABT VCA AUD ABT:VCA-AUD 25.0 and later

ACTV OMDB ACTV:OMDB 8.0 and later

ADD PAUTH ADD:PAUTH 8.0 and laterADD PCGRP ADD:PCGRP 8.0 and laterADD PROFL ADD:PROFL 8.0 and laterADD TAUTH ADD:TAUTH 8.0 and laterADD TCGRP ADD:TCGRP 8.0 and later

ALW ABREVC ALW:ABREVC 22.0 and laterALW AMA AUTOST ECP ALW:AMA-AUTOST-ECP 6.1 and laterALW AMADUMP ALW:AMADUMP 17.0 and laterALW AMA SESSION ECP ALW:AMA-SESSION-ECP 6.1 and laterALW ARGR ALW:ARGR 6.1 and laterALW ARREGTRACE ALW:ARREGTRACE 8.0 and laterALW ARUNSET ALW:ARUNSET 6.1 and laterALW AUD ALW:AUD 8.0 and laterALW CDN AUD ALW:CDN-AUD 23.0 and laterALW CDN CP ALW:CDN-CP 17.0 and laterALW CDN PRINT AUD ALW:CDN-PRINT-AUD 17.0 and laterALW CELL ALW:CELL 25.0 and laterALW CELL CP FAIL ALW:CELL-CP-FAIL 7.0 and laterALW CELL EXTERN FLASH ALW:CELL-EXTERN 20.0 and laterALW CELL MLG ALW:CELL-MLG 25.0 and laterALW CONFLOG ALW:CONFLOG 8.0 and laterALW CPREGTRACE ALW:CPREGTRACE 8.0 and laterALW CPSECOND ALW:CPSECOND 8.0 and laterALW CPSG ALW:CPSG 6.1 and laterALW DLN AUD ALW:DLN-AUD 7.0 and laterALW DLN PRINT AUD ALW:DLN-PRINT-AU 6.0 and laterALW DMQ ALW:DMQ 8.0 and laterALW DMQ ALW:DMQ-RTR 8.0 and laterALW EAIINT ALW:EAIINT 8.0 and laterALW ECP AUD ALW:ECP-AUD 25.0 and later


IM:INDEX-10 Issue 28





ALW ECP PRINT AUD ALW:ECP-PRINT 19.0 and laterALW EGSF ALW:EGSF 6.1 and laterALW ERRCHK ALW:ERRCHK 8.0 and laterALW ERRINT ALW:ERRINT 8.0 and laterALW ERRSRC ALW:ERRSRC 8.0 and laterALW FILESYS ACCESS ALW:FILESYS-ACCES 8.0 and laterALW FILESYS MOUNT ALW:FILESYS-MOUNT 8.0 and laterALW FILESYS OWNER ALW:FILESYS-OWNER 8.0 and laterALW FMP ALW:FMP 2.0 and laterALW HDWCHK ALW:HDWCHK 8.0 and laterALW LCP ALW:LCP 2.2 and laterALW LSLTRC ALW:LSLTRC 25.0 and laterALW RCMS ALW:RCMS 22.0 and laterALW REX ALW:REX 8.0 and laterALW REX RPCD ALW:REX-RPCD 8.0 and laterALW REX RPCN ALW:REX-RPCN 8.0 and laterALW RUTIL ALW:RUTIL 7.0 and laterALW RUTILFLAG ALW:RUTILFLAG 7.0 and laterALW SCSD ALW:SCSD 8.0 and laterALW SFTCHK ALW:SFTCHK 8.0 and laterALW TCS AUD ALW:TCS-AUD 23.0 and laterALW TRACE ALW:TRACE 7.0 and laterALW TRAP ALW:TRAP 7.0 and laterALW UMEM ALW:UMEM 8.0 and laterALW UTIL ALW:UTIL 8.0 and laterALW UTILFLAG ALW:UTILFLAG 8.0 and laterALW VCA AUD ALW:VCA-AUD 25.0 and laterALW VCA PRINT AUD ALW:VCA-PRINT 19.0 and later

APPLY OMDB APPLY:OMDB 8.0 and later

AUD CDN NAME AUD:CDN-NAME 23.0 and laterAUD CELL AUD:CELL 25.0 and laterAUD CNC AUD:CNC 7.0 and laterAUD CUMEM AUD:CUMEM 8.0 and laterAUD CUSTAT AUD:CUSTAT 8.0 and laterAUD DLN NAME AUD:DLN-NAME 6.0 and laterAUD ECD AUD:ECD 8.0 and laterAUD ECDOWN AUD:ECDOWN 8.0 and laterAUD ECP NAME AUD:ECP-NAME 25.0 and later


Issue 28 IM:INDEX-11





AUD FMGR AUD:FMGR 8.0 and laterAUD FSBLK AUD:FSBLK 8.0 and laterAUD FSCMPT AUD:FSCMPT 8.0 and laterAUD FSLINK AUD:FSLINK 8.0 and laterAUD MMGR AUD:MMGR 8.0 and laterAUD MSGBUF AUD:MSGBUF 8.0 and laterAUD NIDATA AUD:NIDATA 8.0 and laterAUD NMDATA AUD:NMDATA 7.0 and laterAUD NODEST AUD:NODEST 7.0 and laterAUD PMS AUD:PMS 8.0 and laterAUD PROAD AUD:PROAD 8.0 and laterAUD REMACS AUD:REMACS 7.0 and laterAUD TCS NAME AUD:TCS-NAME 20.0 and laterAUD VCA NAME AUD:VCA-NAME 25.0 and later

BKUP DATABASE DB BKUP:DATABASE 25.0 and later

CFR CELL CFR:CELL 25.0 and laterCFR RING CFR:RING 7.0 and later

CHG GEN CHG:GEN 7.0 and laterCHG MRVT CHG:MRVT 7.0 and laterCHG PAUTH CHG:PAUTH 8.0 and laterCHG PROFL CHG:PROFL 8.0 and laterCHG SLK CHG:SLK 8.0 and laterCHG SRVT CHG:SRVT 7.0 and later

CLR ACKDB CLR:ACKDB 8.0 and laterCLR APPSLT CLR:APPSLT 20.0 and laterCLR CELL CLR:CELL-SYNC 22.0 and laterCLR DB DNLD CLR:DB-DNLD 19.0 and laterCLR DB SU CLR:DB-SU 17.0 and laterCLR EMERDMP CLR:EMERDMP 8.0 and laterCLR FANALM CLR:FANALM 8.0 and laterCLR FILESYS DIR CLR:FILESYS-DIR 8.0 and laterCLR FILESYS FILE CLR:FILESYS-FILE 8.0 and laterCLR IMCAT CLR:IMCAT 8.0 and laterCLR IODRV CLR:IODRV 8.0 and laterCLR MHD MAEC CLR:MHD-MAEC 8.0 and laterCLR PTN MHD CLR:PTN-MHD 8.0 and later







CLR RUTIL CLR:RUTIL 7.0 and laterCLR RUTILFLAG CLR:RUTILFLAG 7.0 and laterCLR SRST CLR:SRST 7.0 and laterCLR SS7SRST CLR:SS7SRST 23.0 and laterCLR UMEM CLR:UMEM 8.0 and laterCLR UTIL CLR:UTIL 8.0 and laterCLR UTILFLAG CLR:UTILFLAG 8.0 and later

CMPR DISK CORE CMPR:DISK-CORE 8.0 and laterCMPR MHD CMPR:MHD 13.0 and later

COPY ACTDISK COPY:ACTDISK 8.0 and laterCOPY ADDR COPY:ADDR 8.0 and laterCOPY AMATAPE COPY:AMATAPE 25.0 and laterCOPY AMATAPE ECP COPY:AMATAPE-ECP 14.0 and laterCOPY BKDISK COPY:BKDISK 23.0 and laterCOPY BKTAPE COPY:BKTAPE 20.0 and laterCOPY CELL COPY:CELL 22.0 and laterCOPY DB COPY:DB 25.0 and laterCOPY DIFF SRC MHD COPY:DIFF-SRC-MHD 13.0 and laterCOPY OOSDISK COPY:OOSDISK 8.0 and laterCOPY PID COPY:PID 8.0 and laterCOPY PTN ALL COPY:PTN-ALL 13.0 and laterCOPY REG COPY:REG 8.0 and laterCOPY SPDISK COPY:SPDISK 8.0 and laterCOPY TAPE EMERDMP COPY:TAPE-EMERDMP 8.0 and laterCOPY TAPE IN COPY:TAPE-IN 8.0 and laterCOPY TAPE OUT COPY:TAPE-OUT 8.0 and laterCOPY TAPE TEST COPY:TAPE-TEST 8.0 and laterCOPY TAPE TOP COPY:TAPE-TOP 23.0 and laterCOPY UID COPY:UID 8.0 and laterCOPY UVAR COPY:UVAR 8.0 and later

DEL CELL GENERIC DEL:CELL-GENERIC 22.0 and laterDEL LOG DEL:LOG 8.0 and laterDEL PAUTH DEL:PAUTH 8.0 and laterDEL PCGRP DEL:PCGRP 8.0 and laterDEL PROFL DEL:PROFL 8.0 and later







DEL TAUTH DEL:TAUTH 8.0 and laterDEL TCGRP DEL:TCGRP 8.0 and laterDEL:VLR:DCS DEL:VLR-DCS 17.0 and later

DGN CELL DGN:CELL 22.0 and laterDGN CELL DL DGN:CELL-DL 22.0 and laterDGN CELL SG DGN:CELL-SG 22.0 and laterDGN CU DGN:CU 8.0 and laterDGN DCI DGN:DCI 8.0 and laterDGN DCS DL DGN:DCS-DL 6.0 and laterDGN DCS TRKGRP DGN:DCS-TRKGRP 17.0 and laterDGN DFC DGN:DFC 8.0 and laterDGN DUIC DGN:DUIC 8.0 and laterDGN ECP DL DGN:ECP-DL 2.0 and laterDGN HSDC DGN:HSDC 8.0 and laterDGN IOP DGN:IOP 8.0 and laterDGN LN DGN:LN 8.0 and laterDGN MHD DGN:MHD 8.0 and laterDGN MT DGN:MT 8.0 and laterDGN MTC DGN:MTC 8.0 and laterDGN MTTYC DGN:MTTYC 8.0 and laterDGN RPCN DGN:RPCN 8.0 and laterDGN SCSDC DGN:SCSDC 8.0 and laterDGN SDLC DGN:SDLC 8.0 and laterDGN TTYC DGN:TTYC 8.0 and later

DNLD CELL DNLD:CELL 22.0 and laterDNLD CELL DLOPTS DNLD:CELL-DLOPTS 22.0 and later

DUMP ADDR DUMP:ADDR 8.0 and laterDUMP BKTAPE DUMP:BKTAPE 23.0 and laterDUMP CACHE DUMP:CACHE 8.0 and laterDUMP CELL DUMP:CELL 22.0 and laterDUMP CELL AUTH FAIL DUMP:CELL-AUTH-FAIL 25.0 and laterDUMP CELL MRA DUMP:CELL-MRA 22.0 and laterDUMP CELL MRAQ DUMP:CELL-MRAQ 22.0 and laterDUMP CELL PLM DUMP:CELL-PLM 22.0 and laterDUMP CELL SG DUMP:CELL-SG 22.0 and laterDUMP FILE ALL DUMP:FILE-ALL 8.0 and laterDUMP FILE DATA DUMP:FILE-DATA 8.0 and later







DUMP FILE FORMAT DUMP:FILE-FORMAT 8.0 and laterDUMP FILE PARTL DUMP:FILE-PARTL 13.0 and laterDUMP ISR DUMP:ISR 17.0 and laterDUMP KERN DUMP:KERN 8.0 and laterDUMP MCR DUMP:MCR 17.0 and laterDUMP MHD BLOCK DUMP:MHD-BLOCK 8.0 and laterDUMP MHD DEFECT DUMP:MHD-DEFECT 13.0 and laterDUMP MHD VTOC DUMP:MHD-VTOC 8.0 and laterDUMP PID DUMP:PID 8.0 and laterDUMP PMEM DUMP:PMEM 8.0 and laterDUMP REG DUMP:REG 8.0 and laterDUMP RUTIL DUMP:RUTIL 7.0 and laterDUMP SMEAS DUMP:SMEAS 15.0 and laterDUMP TRK DATA DUMP:TRK-DATA 8.0 and laterDUMP UID DUMP:UID 8.0 and laterDUMP UVAR DUMP:UVAR 8.0 and later

END WHEN END:WHEN 8.0 and later

EX CU EX:CU 8.0 and laterEX DCI EX:DCI 8.0 and laterEX DFC EX:DFC 8.0 and laterEX DUIC EX:DUIC 8.0 and laterEX HSDC EX:HSDC 8.0 and laterEX IOP EX:IOP 8.0 and laterEX LDPARM EX:LDPARM 8.0 and laterEX LN EX:LN 7.0 and laterEX LOOP EX:LOOP 8.0 and laterEX MHD EX:MHD 8.0 and laterEX MT EX:MT 8.0 and laterEX MTC EX:MTC 8.0 and laterEX MTTYC EX:MTTYC 8.0 and laterEX PAUSE EX:PAUSE 8.0 and laterEX RPCN EX:RPCN 7.0 and laterEX SCSDC EX:SCSDC 8.0 and laterEX SDLC EX:SDLC 8.0 and laterEX STEP EX:STEP 8.0 and laterEX STOP EX:STOP 8.0 and laterEX TTYC EX:TTYC 8.0 and later







EXC CELL CDM DS1 EXC:CELL-CDM-DS1 24.0 and laterEXC CELL FT EXC:CELL-FT 22.0 and laterEXC CELL ODPC EXC:CELL-ODPC 22.0 and laterEXC CELL RTDIAG EXC:CELL-RTDIAG 22.0 and laterEXC CELL TRKGRP LPBK EXC:CELL-TRKGRP-LPBK 22.0 and laterEXC ENVIR PROC EXC:ENVIR-PROC 8.0 and laterEXC ENVIR UPROC EXC:ENVIR-UPROC 8.0 and laterEXC KILLCALL EXC:KILLCALL 14.0 and laterEXC LAESREQ EXC:LAESREQ 13.0 and laterEXC MRVT EXC:MRVT 7.0 and laterEXC OFLBOOT EXC:OFLBOOT 8.0 and laterEXC SRVT EXC:SRVT 7.0 and laterEXC SSDUPD EXC:SSDUPD 14.0 and laterEXC UCHALL EXC:UCHALL 14.0 and laterEXC UCL EXC:UCL 8.0 and later

FRCHO CELL RA FRCHO:CELL-RA 22.0 and laterFRCHO DCS TRKGRP FRCHO:DCS-TRKGRP 14.0 and later

FRMV LN FRMV:LN 8.0 and later

HELP HELP 23.0 and later_ ____________________________________________________________________________________________





Volume 2ECP INPUT MESSAGE DESCRIPTIONS


IN DTIME IN:DTIME 8.0 and laterIN FILE APND IN:FILE-APND 8.0 and laterIN FILE DEL IN:FILE-DEL 8.0 and laterIN FILE REPL IN:FILE-REPL 8.0 and laterIN FILESYS DIR IN:FILESYS-DIR 8.0 and laterIN REMOTE REPT IN:REMOTE-REPT 8.0 and laterIN REMOTE START IN:REMOTE-START 8.0 and laterIN REMOTE STOP IN:REMOTE-STOP 8.0 and laterIN XFER IN:XFER 8.0 and later

INH ABREVC INH:ABREVC 22.0 and laterINH AMA AUTOST ECP INH:AMA-AUTOST-ECP 6.1 and laterINH AMADUMP INH:AMADUMP 17.0 and laterINH AMA SESSION ECP INH:AMA-SESSION-ECP 6.1 and laterINH ARGR INH:ARGR 6.1 and laterINH ARREGTRACE INH:ARREGTRACE 8.0 and laterINH ARUNSET INH:ARUNSET 6.1 and laterINH AUD INH:AUD 8.0 and laterINH CDN AUD INH:CDN-AUD 23.0 and laterINH CDN CP INH:CDN-CP 17.0 and laterINH CDN PRINT AUD INH:CDN-PRINT 17.0 and laterINH CELL INH:CELL 25.0 and laterINH CELL CP FAIL INH:CELL-CP-FAIL 7.0 and laterINH CELL EXTERN FLASH INH:CELL-EXTERN 20.0 and laterINH CELL MLG INH:CELL-MLG 25.0 and laterINH CONFLOG INH:CONFLOG 8.0 and laterINH CPREGTRACE INH:CPREGTRACE 8.0 and laterINH CPSECOND INH:CPSECOND 8.0 and laterINH CPSG INH:CPSG 6.1 and laterINH DLN AUD INH:DLN-AUD 7.0 and laterINH DLN PRINT AUD INH:DLN-PRINT 6.0 and laterINH DMQ INH:DMQ 7.0 and laterINH DMQ INH:DMQ-RTR 8.0 and laterINH EAIINT INH:EAIINT 8.0 and laterINH ECP AUDIT INH:ECP-AUD 25.0 and laterINH ECP PRINT AUDIT INH:ECP-PRINT 19.0 and laterINH EGSF INH:EGSF 6.1 and laterINH ERRCHK INH:ERRCHK 8.0 and laterINH ERRINT INH:ERRINT 8.0 and laterINH ERRSRC INH:ERRSRC 8.0 and later





Volume 2 (Continued)_ ____________________________________________________________________________________________Message Name Message ID Release_ ____________________________________________________________________________________________

INH FILESYS UMOUNT INH:FILESYS-UMOUN 8.0 and laterINH FMP INH:FMP 2.0 and laterINH HDWCHK INH:HDWCHK 8.0 and laterINH IMSMEAS INH:IMSMEAS 8.0 and laterINH LCP INH:LCP 2.2 and laterINH LSLTRC INH:LSLTRC 25.0 and laterINH PSLT INH:PSLT 7.0 and laterINH RCMS INH:RCMS 22.0 and laterINH REPORT INH:REPORT 7.0 and laterINH REX INH:REX 8.0 and laterINH REX RPCD INH:REX-RPCD 7.0 and laterINH REX RPCN INH:REX-RPCN 7.0 and laterINH RMV INH:RMV 7.0 and laterINH RUTIL INH:RUTIL 7.0 and laterINH RUTILFLAG INH:RUTILFLAG 7.0 and laterINH SCSD INH:SCSD 8.0 and laterINH SFTCHK INH:SFTCHK 8.0 and laterINH SLK INH:SLK 7.0 and laterINH TCS AUD INH:TCS-AUD 23.0 and laterINH TRACE INH:TRACE 7.0 and laterINH TRAP INH:TRAP 7.0 and laterINH UMEM INH:UMEM 8.0 and laterINH UTIL INH:UTIL 8.0 and laterINH UTILFLAG INH:UTILFLAG 8.0 and laterINH VCA AUD INH:VCA-AUD 25.0 and laterINH VCA PRINT AUDIT INH:VCA-PRINT 19.0 and later

INIT AMA DW ECP INIT:AMA-DW-ECP 6.1 and laterINIT CDN INIT:CDN 22.0 and laterINIT CDN DB INIT:CDN-DB 25.0 and laterINIT CELL INIT:CELL 22.0 and laterINIT CNI INIT:CNI 5.1 and laterINIT DLN SPP INIT:DLN-SPP 4.1 and laterINIT ECP INIT:ECP 23.0 and laterINIT ECP DB INIT:ECP-DB 21.0 and laterINIT ISR CDN INIT:ISR-CDN 6.1 and laterINIT MCR CDN INIT:MCR-CDN 3.0 and laterINIT MHD INIT:MHD 8.0 and laterINIT UC INIT:UC 8.0 and later






INIT ULARP INIT:ULARP 8.0 and laterINIT UMEM INIT:UMEM 8.0 and laterINIT VCA INIT:VCA 25.0 and later

LABEL AMATAPE LABEL:AMATAPE 25.0 and laterLABEL AMATAPE ECP LABEL:AMATAPE-ECP 14.0 and later

LOAD ADDR LOAD:ADDR 8.0 and laterLOAD CELL LOAD:CELL 22.0 and laterLOAD DFC PUMP LOAD:DFC-PUMP 13.0 and laterLOAD DFC RAM LOAD:DFC-RAM 8.0 and laterLOAD MHD DEFECT LOAD:MHD-DEFECT 8.0 and laterLOAD MHD FIRMWARE LOAD:MHD-FIRMWARE 8.0 and laterLOAD PMEM LOAD:PMEM 8.0 and laterLOAD REG LOAD:REG 8.0 and laterLOAD RUTIL LOAD:RUTIL 8.0 and laterLOAD UVAR LOAD:UVAR 8.0 and later

LOGN SHL LOGN:SHL 14.0 and later

MEAS CELL MEAS:CELL 21.0 and later

MON APSLK MON:APSLK 20.0 and laterMON SLK MON:SLK 8.0 and later

MOVE CELL MOVE:CELL 17.0 and laterMOVE CELL OC MOVE:CELL-OC 22.0 and laterMOVE DN CELL MOVE:DN-CELL 22.0 and laterMOVE IMSI CELL MOVE:IMSI-CELL 22.0 and laterMOVE MIN CELL MOVE:MIN-CELL 22.0 and later

OCNS CELL OCNS:CELL 22.0 and later

OP ABREVC OP:ABREVC 22.0 and laterOP ACT OP:ACT 8.0 and laterOP ALARM OP:ALARM 5.1 and laterOP AMA CONFIG ECP OP:AMA-CONFIG-ECP 6.1 and laterOP AMA CONTROLFILE ECP OP:AMA-CONTROL-ECP 6.1 and laterOP AMA DISK ECP OP:AMA-DISK-ECP 6.1 and laterOP AMADUMP OP:AMADUMP 17.0 and laterOP AMA MAPS ECP OP:AMA-MAPS-ECP 6.1 and later






OP AMA METADATA OP:AMA-METADATA 25.0 and laterOP AMA SESSION OP:AMA-SESSION 25.0 and laterOP AMA SESSION ECP OP:AMA-SESSION-ECP 6.1 and laterOP AMA TELEPROCESSING OP:AMA-TELEPRO 25.0 and laterOP AMA TELEPROCESSING ECP OP:AMA-TELEPRO-ECP 6.1 and laterOP APPSLT OP:APPSLT 20.0 and laterOP AUD OP:AUD 8.0 and laterOP AUDERR OP:AUDERR 8.0 and laterOP BHS CELL OP:BHS-CELL 25.0 and laterOP C7NET OP:C7NET 8.0 and laterOP CDN OP:CDN 17.0 and laterOP CDN AUD OP:CDN-AUD 17.0 and laterOP CDN CP OP:CDN-CP 17.0 and laterOP CDN OVLD OP:CDN-OVLD 3.0 and laterOP CELL OP:CELL 24.0 and laterOP CELL CDM PPSUM OP:CELL-CDM-PPSUM 22.0 and laterOP CELL CENB OP:CELL-CENB 21.0 and laterOP CELL CSB OP:CELL-CSB 25.0 and laterOP CELL DL OP:CELL-DL 24.0 and laterOP CELL DLOPTS OP:CELL-DLOPTS 22.0 and laterOP CELL EXTERN OP:CELL-EXTERN 22.0 and laterOP CELL GENERIC OP:CELL-GENERIC 22.0 and laterOP CELL INVENT OP:CELL-INVENT 22.0 and laterOP CELL OVLD OP:CELL-OVLD 22.0 and laterOP CELL SCSM OP:CELL-SCSM 5.1 and laterOP CELL SG OP:CELLSG 22.0 and laterOP CELL TXWATTS OP:CELL-TXWATTS 22.0 and laterOP CELL VERSION OP:CELL-VERS 22.0 and laterOP CELL VOC OP:CELL-VOC 12.0 and laterOP CFGSTAT OP:CFGSTAT 8.0 and laterOP CLK OP:CLK 8.0 and laterOP COB CTRC OP:COB-CTRC 17.0 and laterOP CTRC OP:CTRC 25.0 and laterOP DCS OP:DCS 3.0 and laterOP DCS BHSSTAT OP:DCS-BHSSTAT 25.0 and laterOP DCS DL OP:DCS-DL 6.0 and laterOP DCS DS1 OP:DCS-DS1 16.0 and laterOP DCS MRAQ OP:DCS-MRAQ 12.0 and laterOP DCS TRKALM OP:DCS-TRKALM 5.1 and laterOP DCS TRKGRP OP:DCS-TRKGRP 9.0 and laterOP DFCELOG OP:DFCELOG 8.0 and later






OP DFC INFO OP:DFC-INFO 24.0 and laterOP DL OP:DL 2.0 and laterOP DLN OP:DLN 4.1 and laterOP DLN AUD OP:DLN-AUD 6.0 and laterOP DMQ OP:DMQ 8.0 and laterOP DN OP:DN 17.0 and laterOP ECP OP:ECP 6.1 and laterOP ECP AUD OP:ECP-AUD 25.0 and laterOP ECP CENB OP:ECP-CENB 21.0 and laterOP ECP DL OP:ECP-DL 2.0 and laterOP ECP OVLD OP:ECP-OVLD 2.0 and laterOP EIN ROUTEPOOL OP:EIN-ROUTEPOOL 25.0 and laterOP EMERSTAT OP:EMERSTAT 8.0 and laterOP ERRCHK OP:ERRCHK 8.0 and laterOP FNAME OP:FNAME 8.0 and laterOP GEN READLOG OP:GEN-READLOG 8.0 and laterOP GROW OP:GROW 8.0 and laterOP HSDC INFO OP:HSDC-INFO 17.0 and laterOP HSD INFO OP:HSD-INFO 17.0 and laterOP IMSI OP:IMSI 17.0 and laterOP INFO EESN OP:INFO-EESN 6.1 and laterOP INFO NPACOUNT OP:INFO-NPACOUNT 13.0 and laterOP INIT OP:INIT 8.0 and laterOP IODRV OP:IODRV 8.0 and laterOP ISR CDN OP:ISR-CDN 6.1 and laterOP LN DL OP:LN-DL 2.0 and laterOP LNSTAT OP:LNSTAT 7.0 and laterOP LOG OP:LOG 8.0 and laterOP LTRC OP:LTRC 25.0 and laterOP MCR CDN OP:MCR-CDN 3.0 and laterOP MEMERRS OP:MEMERRS 8.0 and laterOP MHD INFO OP:MHD-INFO 24.0 and laterOP MIN OP:MIN 17.0 and laterOP MSGCLS OP:MSGCLS 20.0 and laterOP MSG CTRC OP:MSG-CTRC 17.0 and laterOP MT INFO OP:MT-INFO 24.0 and laterOP MTTYC INFO OP:MTTYC-INFO 17.0 and laterOP MTTY INFO OP:MTTY-INFO 17.0 and laterOP NPMEM OP:NPMEM 8.0 and laterOP OC CELL OP:OC-CELL 22.0 and laterOP ODPC OP:ODPC 19.0 and later






OP OFFICE AL OP:OFFICE-AL 22.0 and laterOP OFL OP:OFL 8.0 and laterOP OMDB OP:OMDB 8.0 and laterOP OOS OP:OOS-RTR 8.0 and laterOP OUTCLS OP:OUTCLS 7.0 and laterOP PERMS OP:PERMS 20.0 and laterOP PM CELL OP:PM-CELL 22.0 and laterOP PMCR OP:PMCR 8.0 and laterOP REXINH OP:REXINH 8.0 and laterOP RING OP:RING 7.0 and laterOP RNC BHSSTAT OP:RNC-BHSSTAT 25.0 and laterOP ROP INFO OP:ROP-INFO 17.0 and laterOP RUTIL OP:RUTIL 7.0 and laterOP RUTILFLAG OP:RUTILFLAG 7.0 and laterOP SCC INFO OP:SCC-INFO 17.0 and laterOP SCHD OP:SCHD 7.0 and laterOP SCSD OP:SCSD 8.0 and laterOP SDLC INFO OP:SDLC-INFO 17.0 and laterOP SDL INFO OP:SDL-INFO 17.0 and laterOP:SESSIONS OP:SESSIONS 22.0 and laterOP SLK OP:SLK 8.0 and laterOP SMR OP:SMR 7.0 and laterOP SNAT OP:SNAT 7.0 and laterOP SPECTRUM OP:SPECTRUM 7.0 and laterOP STBY OP:STBY 8.0 and laterOP STATUS DISKUSE OP:ST-DISKUSE 8.0 and laterOP STATUS FILESYS OP:ST-FILESYS 8.0 and laterOP STATUS FREEDISK OP:ST-FREEDISK 8.0 and laterOP STATUS LISTDIR OP:ST-LISTDIR 8.0 and laterOP STATUS PORTS OP:ST-PORTS 8.0 and laterOP STATUS PROCESS OP:ST-PROCESS 8.0 and laterOP STATUS SUM OP:ST-SUM 8.0 and laterOP SUAUDIOPDFC OP:SUAUDIOPDFC 23.0 and laterOP:TCS AUD OP:TCS-AUD 24.0 and laterOP TPC OP:TPC 7.0 and laterOP TRACE OP:TRACE 7.0 and laterOP TRAP OP:TRAP 7.0 and laterOP TTYC INFO OP:TTYC-INFO 17.0 and laterOP TTY INFO OP:TTY-INFO 17.0 and laterOP ULARP COMMAND OP:ULARP-COMMAND 8.0 and laterOP ULARP EXECSEQ OP:ULARP-EXECSEQ 8.0 and later






OP ULARP PROCESS OP:ULARP-PROCESS 8.0 and laterOP UMEM OP:UMEM 8.0 and laterOP UNAV OP:UNAV 8.0 and laterOP UNEQIP OP:UNEQIP 8.0 and laterOP UTIL OP:UTIL 8.0 and laterOP VCA AUD OP:VCA-AUD 19.0 and later

ORD SCSD ORD:SCSD 8.0 and later

RCV DMTECD RC RCV:DMTECD-RC 8.0 and laterRCV DMTECD VFY RCV:DMTECD-VFY 8.0 and laterRCV DMTSG RC RCV:DMTSG-RC 8.0 and laterRCV DMTSG VFY RCV:DMTSG-VFY 8.0 and laterRCV MENU BROWSE RCV:M-BROWSE 8.0 and laterRCV MENU COMPAREDB RCV:M-COMPAREDB 8.0 and laterRCV MENU CREATEECD RCV:M-CREATEECD 8.0 and laterRCV MENU CREATESG RCV:M-CREATESG 8.0 and laterRCV MENU EVOL RCV:M-EVOL 8.0 and laterRCV MENU FDIFF RCV:M-FDIFF 8.0 and laterRCV MENU KEYCMP RCV:M-KEYCMP 8.0 and laterRCV MENU KEYCOMM RCV:M-KEYCOMM 8.0 and laterRCV MENU KEYS RCV:M-KEYS 8.0 and laterRCV MENU LOADF3B RCV:M-LOADF3B 8.0 and laterRCV MENU NEWDB RCV:M-NEWDB 8.0 and laterRCV MENU PRINTDB RCV:M-PRINTDB 8.0 and laterRCV MENU PRINTFRM RCV:M-PRINTFRM 8.0 and laterRCV MENU RCVECD RCV:M-RCVECD 8.0 and laterRCV MENU RCVSG RCV:M-RCVSG 8.0 and laterRCV MENU TRANSGEN RCV:M-TRANSGEN 8.0 and laterRCV MENU TREEBLD RCV:M-TREEBLD 8.0 and laterRCV MENU VFYDFLT RCV:M-VFYDFLT 8.0 and later

REPT SLK REPT:SLK 7.0 and later

RESET CELL RESET:CELL 22.0 and later

RFT ABORT RFT:ABORT 8.0 and laterRFT BEGINPOST RFT:BEGINPOST 8.0 and laterRFT FDUMP RFT:FDUMP 8.0 and laterRFT PRINT RFT:PRINT 8.0 and later






RMV AP ROP RMV:AP-ROP 24.0 and laterRMV CDN RMV:CDN 20.0 and laterRMV CELL RMV:CELL 22.0 and laterRMV CELL SG RMV:CELL-SG 22.0 and laterRMV CU RMV:CU 8.0 and laterRMV DCI RMV:DCI 8.0 and laterRMV DCS DL RMV:DCS-DL 6.0 and laterRMV DCS TRKGRP RMV:DCS-TRKGRP 20.0 and laterRMV DFC RMV:DFC 8.0 and laterRMV DUI RMV:DUI 8.0 and laterRMV DUIC RMV:DUIC 8.0 and laterRMV ECP DL RMV:ECP-DL 2.0 and laterRMV HSD RMV:HSD 8.0 and laterRMV HSDC RMV:HSDC 8.0 and laterRMV IOP RMV:IOP 8.0 and laterRMV LN RMV:LN 7.0 and laterRMV LN DL RMV:LN-DL 2.2 and laterRMV LN UCL RMV:LN-UCL 3.0 and laterRMV MHD RMV:MHD 8.0 and laterRMV MT RMV:MT 8.0 and laterRMV MTC RMV:MTC 8.0 and laterRMV MTTY RMV:MTTY 8.0 and laterRMV MTTYC RMV:MTTYC 8.0 and laterRMV ROP RMV:ROP 8.0 and laterRMV RPCN RMV:RPCN 7.0 and laterRMV SBUS RMV:SBUS 8.0 and laterRMV SCC RMV:SCC 8.0 and laterRMV SCSDC RMV:SCSDC 8.0 and laterRMV SDL RMV:SDL 8.0 and laterRMV SDLC RMV:SDLC 8.0 and laterRMV TTY RMV:TTY 8.0 and laterRMV TTYC RMV:TTYC 8.0 and laterRMV VIOP RMV:VIOP 9.0 and laterRMV VTTY RMV:VTTY 9.0 and laterRMV VTTYC RMV:VTTYC 9.0 and later

RNM PSSWD RNM:PSSWD 8.0 and later

RST AP ROP RST:AP-ROP 24.0 and laterRST CDN RST:CDN 23.0 and laterRST CELL RST:CELL 22.0 and later






RST CELL SG RST:CELL-SG 22.0 and laterRST CU RST:CU 8.0 and laterRST DCI RST:DCI 8.0 and laterRST DCS DL RST:DCS-DL 6.0 and laterRST DCS TRKGRP RST:DCS-TRKGRP 9.0 and laterRST DFC RST:DFC 8.0 and laterRST DUI RST:DUI 8.0 and laterRST DUIC RST:DUIC 8.0 and laterRST ECP DL RST:ECP-DL 2.0 and laterRST HSD RST:HSD 8.0 and laterRST HSDC RST:HSDC 8.0 and laterRST IOP RST:IOP 8.0 and laterRST LN RST:LN 8.0 and laterRST LN DL RST:LN-DL 2.2 and laterRST MHD RST:MHD 8.0 and laterRST MT RST:MT 8.0 and laterRST MTC RST:MTC 8.0 and laterRST MTTY RST:MTTY 8.0 and laterRST MTTYC RST:MTTYC 8.0 and laterRST ROP RST:ROP 8.0 and laterRST RPCN RST:RPCN 7.0 and laterRST SBUS RST:SBUS 8.0 and laterRST SCC RST:SCC 8.0 and laterRST SCSDC RST:SCSDC 8.0 and laterRST SDL RST:SDL 8.0 and laterRST SDLC RST:SDLC 8.0 and laterRST TTY RST:TTY 8.0 and laterRST TTYC RST:TTYC 8.0 and laterRST VIOP RST:VIOP 9.0 and laterRST VTTY RST:VTTY 9.0 and laterRST VTTYC RST:VTTYC 9.0 and later

SCHED VCSA SCHED:VCSA 17.0 and later

SEND CELL GENERIC SEND:CELL-GENERIC 22.0 and later

SET AMA CONFIG ECP SET:AMA-CONFIG-ECP 19.0 and laterSET AMA CONFIG BSN ECP SET:AMA-CONFIG-BSN-ECP 19.0 and laterSET AMA CONTROL ECP SET:AMA-CONTROL-ECP 14.0 and laterSET APPSLT SET:APPSLT 20.0 and laterSET CLK SET:CLK 15.0 and later






SET CLK SET:CLK-RTR 15.0 and laterSET CP SET:CP 16.0 and laterSET DB DNLD SET:DB-DNLD 19.0 and laterSET DB SU SET:DB-SU 17.0 and laterSET IODRV SET:IODRV 8.0 and laterSET TRACE SET:TRACE 7.0 and laterSET TRAP SET:TRAP 8.0 and later

STOP AMATAPE STOP:AMATAPE 25.0 and laterSTOP AMATAPE ECP STOP:AMATAPE-ECP 6.1 and laterSTOP AUD STOP:AUD 8.0 and laterSTOP BKDISK STOP:BKDISK 8.0 and laterSTOP CELL STOP:CELL 22.0 and laterSTOP CFR CELL STOP:CFR-CELL 22.0 and laterSTOP CMPR MHD STOP:CMPR-MHD 8.0 and laterSTOP COPY DIFF STOP:COPY-DIFF 8.0 and laterSTOP DCI STOP:DCI 8.0 and laterSTOP DCS MRAQ STOP:DCS-MRAQ 3.0 and laterSTOP DGN CELL STOP:DGN-CELL 22.0 and laterSTOP DGN CELL DL STOP:DGN-CELL-DL 22.0 and laterSTOP DGN CELL SG STOP:DGN-CELL-SG 22.0 and laterSTOP DGN DCS DL STOP:DGN-DCS-DL 6.0 and laterSTOP DGN DCS TRK STOP:DGN-DCS-TRK 9.0 and laterSTOP DGN ECP DL STOP:DGN-ECP-DL 2.0 and laterSTOP DMQ STOP:DMQ 8.0 and laterSTOP DNLD STOP:DNLD 4.0 and laterSTOP EXC ANY STOP:EXC-ANY 8.0 and laterSTOP EXC FT STOP:EXC-CELL-FT 22.0 and laterSTOP EXC CELL RTDIAG STOP:EXC-CELL-RTDIAG 22.0 and laterSTOP EXC ODPC STOP:EXC-ODPC 19.0 and laterSTOP EXC USER STOP:EXC-USER 8.0 and laterSTOP GEN STOP:GEN 8.0 and laterSTOP MEAS CELL STOP:MEAS-CELL 17.0 and laterSTOP MOVE CELL STOP:MOVE-CELL 22.0 and laterSTOP OCNS CELL STOP:OCNS-CELL 22.0 and laterSTOP OFLBOOT STOP:OFLBOOT 8.0 and laterSTOP OP CELL INVENT STOP:OP-CELL-INVENT 22.0 and laterSTOP OP COB CTRC STOP:OP-COB-CTRC 17.0 and laterSTOP OP MSG CTRC STOP:OP-MSG-CTRC 17.0 and later






STOP SEND CELL GENERIC STOP:SEND-CELL-GENERIC 22.0 and laterSTOP TRAP STOP:TRAP 7.0 and laterSTOP VCSA STOP:VCSA 17.0 and later

SW ACDN SW:ACDN 17.0 and laterSW CELL SW:CELL 22.0 and laterSW CLOCK SW:CLOCK 8.0 and laterSW CU SW:CU 8.0 and laterSW DLN SW:DLN 4.1 and laterSW OFLBOOT SW:OFLBOOT 8.0 and laterSW PORTSW SW:PORTSW 8.0 and laterSW SPECTRUM SW:SPECTRUM 7.0 and later

SWITCHOVER ROP SWITCHOVER:ROP 24.0 and later

UPD APPLY BYTER UPD:APPLY-BYTER 8.0 and laterUPD APPLY FILER UPD:APPLY-FILER 8.0 and laterUPD APPLY FUNCR UPD:APPLY-FUNCR 8.0 and laterUPD APPLY UNIXCMD UPD:APPLY-UNIXCMD 8.0 and laterUPD AUTO UPD:AUTO 8.0 and laterUPD AUTOCHK UPD:AUTOCHK 8.0 and laterUPD AUTOPROFILE UPD:AUTOPROFILE 8.0 and laterUPD AUTOSCHED UPD:AUTOSCHED 8.0 and laterUPD BKOUT UPD:BKOUT 8.0 and laterUPD BLDBOOT UPD:BLDBOOT 8.0 and laterUPD BLOCK UPD:BLOCK 8.0 and laterUPD BOLO UPD:BOLO 8.0 and laterUPD CELL GENERIC ABT UPD:CELL-ABT 1.0 and laterUPD CELL GENERIC ADD UPD:CELL-ADD 5.0 and laterUPD CELL GENERIC DLT UPD:CELL-DLT 2.0 and laterUPD CHG APPLY UPD:CHG-APPLY 8.0 and laterUPD CHG BKOUT UPD:CHG-BKOUT 8.0 and laterUPD CHG INST UPD:CHG-INST 8.0 and laterUPD CHG SKTM UPD:CHG-SKTM 8.0 and laterUPD CLR UPD:CLR 8.0 and laterUPD CLRBWM UPD:CLRBWM 8.0 and laterUPD CSCANS REPORT UPD:CSCANS-REPORT 8.0 and laterUPD CSCANS STOP UPD:CSCANS-STOP 8.0 and laterUPD DISPLAY UPD:DISPLAY 8.0 and laterUPD DISPLYUPD UPD:DISPLYUPD 8.0 and laterUPD EXALL UPD:EXALL 8.0 and later






UPD EXNXT UPD:EXNXT 8.0 and laterUPD EXPAND UPD:EXPAND 8.0 and laterUPD FLASH UPD:FLASH 13.0 and laterUPD FLASH DFC UPD:FLASH-DFC 8.0 and laterUPD FTRC UPD:FTRC 8.0 and laterUPD GEN APPLPROC UPD:GEN-APPLPROC 8.0 and laterUPD GEN BACKOUT UPD:GEN-BACKOUT 8.0 and laterUPD GEN COMMIT UPD:GEN-COMMIT 8.0 and laterUPD GEN CONTINUE UPD:GEN-CONTINUE 8.0 and laterUPD GEN ENTER UPD:GEN-ENTER 8.0 and laterUPD GENP UPD:GENP 8.0 and laterUPD GEN PROCEED UPD:GEN-PROCEED 8.0 and laterUPD GEN RESTORE UPD:GEN-RESTORE 8.0 and laterUPD INITPW UPD:INITPW 8.0 and laterUPD NXTWNDW UPD:NXTWNDW 8.0 and laterUPD OFC UPD:OFC 8.0 and laterUPD OMDB UPD:OMDB 8.0 and laterUPD PRINT UPD:PRINT 8.0 and laterUPD PRINT BWMFILE UPD:PRINT-BWMFILE 8.0 and laterUPD PRINT SKTM UPD:PRINT-SKTM 8.0 and laterUPD PRVWNDW UPD:PRVWNDW 8.0 and laterUPD RCVRY UPD:RCVRY 8.0 and laterUPD REBOOT UPD:REBOOT 8.0 and laterUPD RECOVERY UPD:RECOVERY 8.0 and laterUPD REDUCE UPD:REDUCE 8.0 and laterUPD RESET UPD:RESET 8.0 and laterUPD START EASYBWM UPD:START-EASYBWM 8.0 and laterUPD STOP EXC UPD:STOP-EXC 8.0 and laterUPD STOP SOAK UPD:STOP-SOAK 8.0 and laterUPD UPDCON UPD:UPDCON 8.0 and laterUPD UPDDSPLY UPD:UPDDSPLY 8.0 and laterUPD UPNAME UPD:UPNAME 8.0 and laterUPD VERSION UPD:VERSION 8.0 and laterUPD VFY UPD:VFY 8.0 and laterUPD VFYBWM UPD:VFYBWM 8.0 and laterUPD VFYCON UPD:VFYCON 8.0 and laterUPD VLR QUALREQ UPD:VLR-QUALREQ 17.0 and laterUPD VLR REGNOT UPD:VLR-REGNOT 17.0 and later

UPDATE AP BPSN UPDATE:AP-BPSN 25.0 and laterUPDATE CELL BPSN UPDATE:CELL-BPSN 25.0 and later






VER AMATAPE VER:AMATAPE 25.0 and laterVER AMATAPE ECP VER:AMATAPE-ECP 14.0 and laterVER PLM VER:PLM 22.0 and laterVER VCSA VER:VCSA 17.0 and later

VFY FILE VFY:FILE 20.0 and laterVFY MHD VFY:MHD 8.0 and laterVFY PAUTH VFY:PAUTH 8.0 and laterVFY PCGRP VFY:PCGRP 8.0 and laterVFY PROFL VFY:PROFL 8.0 and laterVFY TAPE VFY:TAPE 13.0 and laterVFY TAUTH VFY:TAUTH 8.0 and laterVFY TCGRP VFY:TCGRP 8.0 and later

WHEN COND WHEN:COND 8.0 and laterWHEN PID WHEN:PID 8.0 and laterWHEN RUTIL WHEN:RUTIL 8.0 and laterWHEN UID WHEN:UID 8.0 and later

WRITE AMA DATA ECP WRITE:AMA-DATA-ECP 6.1 and later

APPENDIX AUDIT APP:AUD 8.0 and laterAPPENDIX MEMBER NUMBERS B APP:MEM-NUM-B 8.0 and laterAPPENDIX MEMBER NUMBERS C APP:MEM-NUM-C 8.0 and laterAPPENDIX MEMBER NUMBERS D APP:MEM-NUM-D 8.0 and later_ ____________________________________________________________________________________________







0.2 FUNCTIONAL INDEX

The following is a list of the units and functions by which the messages are indexed.

AlarmsAuthenticationAuditsAuthority RelationsAutomatic Message Accounting (AMA)BreakpointsCall Processing Database Node (CDN)Cell HardwareCell Software GenericsClock (CLK)Control Unit (CU)Database (DB)DiagnosticsDigital Cellular Switch (DCS)Disk File System (DFS)Executive Cellular Processor (ECP)Expanded General System Failure (EGSF)Field Update (FU) SystemFile System MaintenanceGeneric Access Package (GRASP)Generic UpdateInhibitsInitializationInput/Output Devices and LogsInput/Output Processor (IOP)Interprocessor Message Switch (IMS)InterruptsLine UnitsMaintenance Control (MC)Overload ControlPlant Measurements System (PMS)Power Level Measurements (PLM)Process ControlProcessor Initialization and RecoveryRecent Change (RC)Retrofit ProcessRing UnitsScan and Signal Distributor (SC/SD) PointsSignaling Link (SLK)Tape ManipulationTrunk UnitsUser Level Automatic RestartVoice Channel Selection Activities (VCSA)

The messages in Table 2 are presented in alphabetical order within each unit or function.







Table 2 Index of Input Messages by Function_ _______________________________________________________________________________________________

Function Purpose Message ID_ _______________________________________________________________________________________________

CLR:FANALMALARMS Performs a remote reset of the 3B21D Computerfan alarm.

OP:ALARM Request a list of all alarmed ECP, CDN, cell, andDCS equipment.

OP:DCS-TRKALM Request a report of all trunk groups in alarm fora DCS.

OP:ECP-AL Request a survey of all off normal scan points.

ABT:CDN-AUDAUDITS Terminates a CDN OSDS audit.

ABT:ECP-AUD Terminates an ECP OSDS audit.

ALW:AUD Allows the routine running of one or moreaudits by the System Integrity Monitor.

ALW:CDN-AUD Allows the routine execution of one or all CDNOSDS audits.

ALW:CDN-PRINT-AUD Allows the printing of CDN OSDS audit results.

ALW:ECP-AUD Allows the routine execution of one or all ECPOSDS audits.

ALW:ECP-PRINT Allows the printing of ECP OSDS audit results.

AUD:CDN-NAME Requests a CDN OSDS audit.

AUD:CELL Requests an audit in one or more cell sites.

AUD:CNC Initiates the Central Node Control (CNC) audit.

AUD:CUMEM Runs the memory audit in the standby CU.

AUD:CUSTAT Runs the CU hardware status audit in themanual mode.

AUD:ECD Audits the Equipment Configuration Database(ECD).




Table 2 Index of Input Messages by Function (Continued)_ _______________________________________________________________________________________________


AUD:ECDOWNAUDITS Runs the Equipment Configuration DatabaseManager (ECDMAN) audit of record ownership.

AUD:ECP-NAME Requests an ECP OSDS audit.

AUD:FMGR Audits the File Manager’s (FMGR) resources.

Runs the file system block audit. AUD:FSBLK

Runs the file system compaction audit. AUD:FSCMPT

Runs the file system link audit. AUD:FSLINK

Runs the link and band status audit. AUD:LKBDST

Runs the memory manager audit. AUD:MMGR

Audits the message buffer resources. AUD:MSGBUF

Runs the network data audit. AUD:NIDATA

Runs the network management audit. AUD:NMDATA

Initiates ring node state audits. AUD:NODEST

AUD:PMS Runs the Equipment Configuration DatabaseManager (ECDMAN) audit of record ownership.

AUD:PROAD Audits the DCT Extended (DCTEXT), searchingfor suspended process creations (includingforks) and terminations.

AUD:REMACS Audits the remote access system.

INH:AUD Inhibits the routine running of one or moreaudits.

INH:CDN-AUD Inhibits the routine execution of one or all CDNOSDS audits.

INH:CDN-PRINT Inhibits the printing of CDN OSDS audit results.






INH:ECP-AUDAUDITS Inhibits the routine execution of one or all ECPOSDS audits.

INH:ECP-PRINT Inhibits the printing of ECP OSDS audit results.

OP:AUD Reports the status of an audit or auditscontrolled by the System Integrity Monitor(SIM).

OP:AUDERR Reports the error counts of one or more auditscontrolled by the SIM.

OP:CDN-AUD Requests audit statistics and queuing data.

OP:ECP-AUD Requests audit statistics and queuing data.

Stops a currently active audit. STOP:AUD

EXC:SSDUPDAUTHENTICATION Requests a Shared Secret Data (SSD) update of aparticular mobile for the AuthenticationCapability.

EXC:UCHALL Requests a Unique Challenge of a particularmobile for the Authentication Capability.

ADD:PAUTHAUTHORITYRELATIONS

Allows the addition of a new password with itsrelated identity to the Person Authority Relation(PAUTH).

ADD:PCGRP Allows the Command Groups (COMGR) to beassociated with a Person Identity (IDENT), thusallowing a craftsperson to access only certaingroups of commands.

ADD:PROFL Adds a new profile to the list of user profiles.

ADD:TAUTH Allows the addition of a new terminal to theTerminal Authority (TAUTH) relation.






ADD:TCGRPAUTHORITYRELATIONS

Allows the Command Groups (COMGR) to beassociated with a Terminal (TERM) Identity,thus allowing a craftsperson to access onlycertain groups of commands from that terminal.

CHG:PAUTH Allows changes to the password prefix and/orsuffix.

CHG:PROFL Add or remove a command group from a profileidentity.

DEL:PAUTH Allows deletion of person authority.

DEL:PCGRP Delete a command group from a personalidentity.

DEL:PROFL Delete a profile from a list of user profiles.

DEL:TAUTH Allows the deletion of a terminal identity fromthe Terminal Authority (TAUTH) relation.

DEL:TCGRP Allows a Command Group (COMGR) to bedisassociated from a Terminal (TERM) Identity,thus preventing a craftsperson from accessingthis group of commands from that terminal.

RNM:PSSWD Allows a user to change the password suffix.

VFY:PAUTH Allows verification of a person or grouppassword prefix and suffix.

VFY:PCGRP Allows the retrieval of entries from the PersonCommand Group (PCGRP) table.

VFY:PROFL Verify profile names or command groups.

VFY:TAUTH Allows verification of all terminal identities inthe Terminal Authority (TAUTH) relation.

VFY:TCGRP Allows the retrieval of entries from the TerminalCommand Group (TCGRP) table.






ABT:AMATAPEAUTOMATIC MESSAGEACCOUNTING (AMA)

Aborts the current AMA tape writing session.

ALW:AMA-AUTOST Allows auto-start of AMA tape writing.

ALW:AMA-SESSION Stops manual blocking of AMA tape writingoperations.

CLR:PTN-MHD Clears (initializes with zeroes) partitions on aspecified disk.

COPY:AMATAPE Writes primary or secondary AMA data ontotape.

INH:AMA-AUTOST Blocks auto-start of AMA tape writingoperations.

INH:AMA-SESSION Blocks all AMA tape writing sessions.

INIT:AMA-DW Initialize the AMA disk writer.

LABEL:AMATAPE Writes header labels for an AMA tape.

OP:AMA-CONFIG Provides status of the AMA configuration files.

OP:AMA-CONTROL Obtains the current state of the AMA controlfile.

OP:AMA-DISK Requests current AMA disk space occupancydata.

OP:AMA-MAPS Displays the disk maps and global maps foreach AMA stream.

OP:AMA-SESSION Obtains the status of the current or most recentAMA tape or teleprocessing session.

OP:AMA-TELEPRO Obtains a summary of AMA teleprocessing.






SET:AMA-CONFIGAUTOMATIC MESSAGEACCOUNTING (AMA)

Equips or unequips an AMA partition for thedata stream.

SET:AMA-CONTROL Changes one or more of the AMA control fileparameters.

Stops the tape writing process manually. STOP:AMATAPE

Verifies a tape for AMA use. VER:AMATAPE

WRITE:AMA-DATA Causes all AMA data stored in main memory tobe written to disk.

ALW:RUTILBREAKPOINTS Allows all RGRASP breakpoints in the specifiednode.

ALW:RUTILFLAG Allows specific RGRASP breakpoints in thespecified node.

ALW:UTIL Enables all currently defined 3B21D ComputerGeneric Access Package (GRASP) breakpoints sothat the associated actions are executed whenthe breakpoint conditions occur.

ALW:UTILFLAG Enables a specific 3B21D Computer GenericAccess Package (GRASP) breakpoint so that theassociated actions are executed when thebreakpoint condition occurs.

CLR:RUTIL Clears all RGRASP breakpoints in the specifiednode.

CLR:RUTILFLAG Clears specific RGRASP breakpoints in thespecified node.






CLR:UTILBREAKPOINTS Removes all currently defined 3B21D ComputerGeneric Access Package (GRASP) breakpoints;clears definitions.

CLR:UTILFLAG Removes the specified 3B21D Computer GenericAccess Package (GRASP) breakpoint and clearsthe definition.

DUMP:RUTIL Dumps the contents of memory at the givennode.

INH:RUTIL Inhibits all RGRASP breakpoints in the specifiednode.

INH:RUTILFLAG Inhibits specific RGRASP breakpoints in thespecified node.

INH:UTIL Disables (but leaves defined) all 3B21DComputer Generic Access Package (GRASP)breakpoints.

INH:UTILFLAG Disables (but leaves defined) a specific 3B21DComputer Generic Access Package (GRASP)breakpoint.

LOAD:RUTIL Load the contents of memory at the given nodewith the specified data.

OP:RUTIL Request the current status of all RGRASPbreakpoints in the specified node.

OP:RUTILFLAG Request the current status of specific RGRASPbreakpoints in the specified node.

OP:UTIL Lists currently defined 3B21D ComputerGeneric Access Package (GRASP) breakpoints,their status and trace status.

WHEN:RUTIL Sets an RGRASP breakpoint in the specifiednode.






ABT:CDN-AUDCALL PROCESSINGDATABASE NODE(CDN)

Terminates a CDN OSDS audit.

ALW:CDN-AUD Allows the routine execution of one or all CDNOSDS audits.

ALW:CDN-CP Restores call processing to this CDN.

ALW:CDN-PRINT-AUD Allows the printing of CDN OSDS audit results.

AUD:CDN-NAME Requests a CDN OSDS audit.

INH:CDN-AUD Inhibits the routine execution of one or all CDNOSDS audits.

INH:CDN-CP Inhibits call processing from this CDN.

INH:CDN-PRINT Inhibits the printing of CDN OSDS audit results.

INIT:CDN Requests a CDN OSDS initialization phase.

INIT:CDN-DB Causes an initialization of one or all data basemembers in a specified CDN.

INIT:MCR-CDN Reinitializes the Mobile Call Register (MCR)associated with an ECID that has been reportedas being up for more than 24 hours.

OP:CDN Requests the status of one or all CDNs.

OP:CDN-AUD Requests audit statistics and queuing data.

OP:CDN-CP Requests the status of a camped-on CDN.

OP:CDN-OVLD Requests CDN overload status information.

OP:MCR-CDN Reports the long duration call data for a MCRassociated with an ECID that has been reportedas being up for more than 24 hours.






SW:ACDNCALL PROCESSINGDATABASE NODE(CDN)

Requests that the Administrative CDN (ACDN)function be switched to another CDN.

ALW:CELLCELL HARDWARE Allow a software or hardware action at a cellsite.

AUD:CELL Request an audit in one or more cell sites.

CFR:CELL Requests Manual and Cell Configuration andCell Test (MCAT).

COPY:CELL Copies the data link information from the activeCSC to the offline CSC.

DGN:CELL Diagnoses the specified cell site unit.

DGN:CELL-DL Diagnoses the specified cell site data link.

DGN:CELL-SG Requests that diagnostics be run on all trunksassociated with a specific cell, server group, andantenna face.

DNLD:CELL Requests a non-volatile memory update of thespecified unit(s) at the specified cell(s).

DNLD:CELL-DLOPTS Request an NVM update of the data linkoptioning fields.

DUMP:CELL Dumps a block of text or data memory from acell.

DUMP:CELL-MRAQ Finds out which devices are being diagnosed ata cell, and which devices are waiting to bediagnosed in the high and low priority testequipment queues.






DUMP:CELL-SGCELL HARDWARE Requests an aggregate service measurementcount for each voice radio of appropriatetechnology type on the specified cell, servergroup, and antenna face.

EXC:CELL-FT Begins execution of a functional test at a cell site.

EXC:CELL-RTDIAG Begins execution of a routine diagnosticsequence at a cell site.

INH:CELL Inhibits a software or hardware action at cellsites.

INIT:CELL Request a cell site initialization or cell memoryboot.

LOAD:CELL Loads one to four bytes of data into a cell sitecontroller.

MEAS:CELL Performs measurements on Series II cell siteunits.

OP:CELL-SG Requests the status of all trunks associated witha specified cell, server group, and antenna face.

OP:CELL-VERS Finds out version of firmware and/or softwareinstalled on one or more devices at the cell site.

RMV:CELL Removes the specified unit from service.

RMV:CELL-SG Removes all trunks associated with a specifiedcell, server group and antenna face from service.

Returns cell unit to service. RST:CELL

RST:CELL-SG Restores all trunks associated with a specifiedcell, server group and antenna face to service.

STOP:CFR-CELL Requests exit from Manual and CellConfiguration and Cell Test (MCAT).

STOP:DGN-CELL Terminates a previously-requested diagnostic ata cell site.






STOP:DGN-CELL-DLCELL HARDWARE Terminates a previously requested diagnostic ofthe Cell Site (CS) Data Link (DL).

STOP:DGN-CELL-SG Requests that diagnostics being run on aspecified cell, server group, and antenna face beaborted immediately.

STOP:DNLD Requests that a non-volatile memory update beaborted at the specified cells.

INIT:CELLCELL SOFTWAREGENERICS

Requests a cell site initialization phase.

MOVE:CELL Moves the functionality of a setup, location, orbeacon radio to a voice radio.

OP:CELL-GENERIC Lists the cell generics on the ECP’s disk, the cellsites dependent on those generics, and a list ofcell sites with no available generic.

RMV:CELL Removes the specified unit from service.

SW:CELL Switches the active and standby roles ofduplicated equipment, for example: the cell sitecontrollers and reference generators.

UPD:CELL-ABT Terminates the loading of a cell generic tape.

UPD:CELL-ADD Loads a cell generic tape onto the ECP’s diskdrives.

UPD:CELL-DLT Deletes a cell generic from the ECP’s disk drives.

OP:CLKCLOCK (CLK) Reports the current date and time.

Sets or adjusts the system clock. SET:CLK






ALW:ERRCHKCONTROL UNIT (CU) Allows the logging and processing of all 3B21DComputer error sources.

ALW:ERRINT Allows the logging and processing of 3B21DComputer error interrupts attached to the unitspecified in the identification field.

ALW:ERRSRC Allows the logging and processing of errorsspecific to the pseudo-nodes representing the3B21D Computer CU communities.

ALW:HDWCHK Sets the system status register such that a CUswitch can be implemented as a normal faultrecovery procedure, thereby allowing a switchto the standby 3B21D Computer control unitwhen a fault occurs in the active 3B21DComputer control unit.

ALW:SFTCHK Allows the software error handling routines toincorporate system initialization into their errorrecovery procedures as a means of handling3B21D Computer software sanity problems.

AUD:CUMEM Runs the CUMEM 1 audit, comparing thecontents of the online and off-line main storeswhen in the ACT/ACT or ACT/STBY modes.

AUD:CUSTAT Runs the CU hardware status audit in themanual mode.

DGN:CU Diagnoses the specified control unit complex.

DUMP:CACHE Dumps the contents of the offline cache into3B21D Computer processor main memory.

DUMP:REG Dumps the contents of one or more registers,either as an immediate action, or as an actionassociated with a breakpoint.

EX:CU Exercises a control unit in an interactivediagnostic mode.






INH:ERRCHKCONTROL UNIT (CU) Inhibits the logging and processing of all 3B21DComputer error sources.

INH:ERRINT Inhibits the logging and processing of errorinterrupts attached to the 3B21D Computer unitspecified in the identification field.

INH:ERRSRC Inhibits the logging and processing of errorsspecific to the pseudo-nodes representing the3B21D Computer CU communities.

INH:HDWCHK Sets the system status register so that a CUswitch is not implemented as a normal faultrecovery action.

INH:SFTCHK Alters the manner in which software errors arehandled by precluding the use of systeminitialization when handling 3B21D Computersoftware errors.

LOAD:ADDR Loads a virtual address with specified data as anaction associated with a breakpoint.

LOAD:PMEM Loads a physical byte address with specifieddata as an immediate operation or as abreakpoint action.

LOAD:REG Loads a register with specified data as animmediate action or as a breakpoint action.

LOAD:UVAR Loads a Generic Access Package (GRASP) utilityvariable with specified data as an immediateoperation or as an action associated with abreakpoint.

OP:ERRCHK Formats and outputs a list of all inhibited 3B21DComputer error conditions, including ERRINT,ERRSRC, HDWCHK, and SFTCHK.






RMV:CUCONTROL UNIT (CU) Removes the specified control unit from service,for example: from the standby state to the out-of-service state.

RST:CU Restores a CU to standby status.

SW:CU Causes a non-forced switch of theactive/standby status of the two half systems.

ACTV:OMDBDATABASE (DB) Refreshes the active (incore) Output MessageDatabase from the OMDB disk file.

APPLY:OMDB Applies previous updates to the new copy of theOMDB disk file during field update.

BKUP:DATABASE Backs up the master copy of the member(s)database onto backup disk drives.

COPY:DB Overwrites the master copy of a data basemember with the backup copy.

INIT:CDN-DB Initializes data base members in a specifiedCDN.

INIT:ECP-DB Causes an initialization in main memory of adata base member at the ECP.

OP:OMDB Output the message text, message class, andalarm level from an OMDB entry for the givenkey or keys.

RCV:M-COMPAREDB Compares the Equipment ConfigurationDatabase (ECD) and the System Generation (SG)database.

RCV:M-NEWDB Creates a sorted list of keys for all form types inthe Equipment Configuration Database (ECD)and the System Generation (SG) database.






RCV:M-PRINTDBDATABASE (DB) Creates files of form instances when specifieddata form type(s) from the EquipmentConfiguration Database (ECD) and the SystemGeneration (SG) database are given.

UPD:BLDBOOT Calls ISGEN to rebuild the 3B21D Computerminimum-configuration or full-configurationboot image.

DGN:CELLDIAGNOSTICS Diagnoses the specified cell site unit.

DGN:CELL-DL Diagnoses the specified cell site data link.

DGN:CELL-SG Requests that diagnostics be run on all trunksassociated with a specific cell, server group, andantenna face.

DGN:CU Diagnoses the specified 3B21D ComputerControl Unit (CU) complex or a specified unitwithin the CU complex.

DGN:DCI Diagnoses the specified Dual SerialChannel/Computer Interconnect (DCI).

DGN:DCS-DL Diagnoses the specified Digital Cellular Switch(DCS) data link.

DGN:DCS-TRKGRP Diagnoses a trunk.

DGN:DFC Diagnoses the specified Disk File Controller(DFC).

DGN:DUIC Diagnoses the specified Direct User InterfaceController (DUIC).

DGN:ECP-DL Diagnoses the specified inter-ECP data link.

DGN:HSDC Diagnoses the High-Speed SpecifiedSynchronous Data Link Controller (HSDC).






DGN:IOPDIAGNOSTICS Diagnoses the specified Input/Output Processor(IOP).

DGN:LN Diagnoses the specified Link Nodes (LNs).

DGN:MHD Diagnoses the specified Moving Head Disk(MHD).

DGN:MT Diagnoses the specified Magnetic Tape (MT).

DGN:MTC Diagnoses the specified Magnetic TapeController (MTC).

DGN:MTTYC Diagnoses the specified MaintenanceTeletypewriter Controller (MTTYC).

DGN:RPCN Diagnoses the specified Ring PeripheralController Node (RPCN).

DGN:SCSDC Diagnoses the specified Scanner and SignalDistributor Controller (SCSDC).

DGN:SDLC Diagnoses the specified Synchronous Data LinkController (SDLC).

DGN:TTYC Diagnoses the specified TeletypewriterController (TTYC).

STOP:DGN-CELL Terminates a previously requested diagnostic ata cell site.

STOP:DGN-CELL-DL Terminates a previously requested diagnostic ofthe Cell Site (CS) Data Link (DL).

STOP:DGN-CELL-SG Requests that diagnostics being run on aspecified cell, server group, and antenna face beaborted immediately.

STOP:DGN-DCS-DL Terminates a previously requested diagnostic ofthe DCS Data Link (DL).

STOP:DGN-DCS-TRK Aborts a trunk diagnostic in progress.






STOP:DGN-ECP-DLDIAGNOSTICS Terminates a previously requested diagnostic ofan inter-ECP Data Link (DL).

DGN:DCS-DLDIGITAL CELLULARSWITCH (DCS)

Diagnoses the specified Digital Cellular Switch(DCS) data link.

DGN:DCS-TRKGRP Diagnoses a trunk.

OP:DCS Requests the status of a digital cellular switch.

OP:DCS-DL Requests the current status of the specifiedDigital Cellular Switch (DCS) Data Link (DL).

OP:DCS-DS1 Requests the status of DS-1 units at the DCS.

OP:DCS-MRAQ Prints which trunk is being diagnosed by ATMSat a DCS, and which trunks are waiting to bediagnosed in the ATMS trunk diagnostic queue.

OP:DCS-TRKGRP Requests the status of Cell Site (CS) voicechannels.

RMV:DCS-DL Removes DCS datalink from service.

RMV:DCS-TRKGRP Removes a trunk from service.

RST:DCS-DL Restores DCS datalink to service.

RST:DCS-TRKGRP Restores a trunk member to service.

STOP:DCS-MRAQ Aborts an ATMS trunk diagnostic if in progress,and removes all requests waiting in the ATMStrunk diagnostic queue.

STOP:DGN-DCS-DL Terminates a previously requested diagnostic ofthe DCS Data Link (DL).







CMPR:DISK-COREDISK FILE SYSTEM(DFS)

Compares the text portions of the disk and coreimages of a non-killable process.

CMPR:MHD Compares the contents of two disks or diskpartitions.

COPY:ACTDISK Copies a file from an active disk to an OFL orOOS disk.

COPY:BKDISK Copies selected on-line disk partitions to tape inthe Load Disk from Tape (LDFT) format.

COPY:OOSDISK Copies a specific file from an out-of-service diskto an active system disk.

COPY:SPDISK Copies a specific partition, or a list of partitions,from one of the system disks to an active sparedisk.

DGN:DFC Diagnoses the specified Disk File Controller(DFC).

DGN:MHD Diagnoses the specified Moving Head Disk(MHD).

DUMP:MHD-BLOCK Dumps the contents of a specified single diskblock or a range of blocks, in hexadecimal.

DUMP:MHD-DEFECT Dumps defect management information for aMoving Head Disk (MHD).

DUMP:MHD-VTOC Formats and prints the contents of a disk pack’sVolume Table Of Contents (VTOC).

EX:DFC Exercises a disk file controller in an interactivediagnostic mode.

EX:MHD Exercises a moving head disk in an interactivediagnostic mode.

INIT:MHD Formats all or specific disk tracks of the diskpack with initialized sectors.






LOAD:MHD-DEFECTDISK FILE SYSTEM(DFS)

Loads new defect data onto a Moving HeadDisk (MHD).

OP:AMA-DISK Requests current Automatic MessageAccounting (AMA) disk space occupancy data.

OP:DFC-INFO Outputs information on the specified Disk FileController (DFC) and its associated MovingHead Disks (MHD).

OP:MHD-INFO Outputs information regarding the specifiedMoving Head Disk (MHD).

OP:ST-DISKUSE Outputs the number of blocks contained in allfiles and directories within each specifieddirectory or filename.

OP:ST-FREEDISK Reports the number of free blocks and freei-nodes available for on-line file systems.

RMV:DFC Removes the specified disk file controller andany associated moving head disks from service.

RMV:MHD Removes the specified MHD from service.

RST:DFC Conditionally or unconditionally restores a DFCto service.

RST:MHD Conditionally or unconditionally restores anMHD to service.

STOP:BKDISK Stops the copying of the boot disk to tape.

STOP:CMPR-MHD Stops any CMPR MHD commands that arecurrently executing.

VFY:MHD Reads all or specific disk tracks or blocks andverifies the header and error-correction code ofeach sector of the tracks or blocks read.






ABT:ECP-AUDEXECUTIVE CELLULARPROCESSOR (ECP)

Terminates an ECP OSDS audit.

ALW:ECP-AUD Allows the routine execution of one or all ECPOSDS audits.

ALW:ECP-PRINT Allows the printing of ECP OSDS audit results.

AUD:ECP-NAME Requests an ECP OSDS audit.


INH:ECP-AUD Inhibits the routine execution of one or all ECPOSDS audits.

INH:ECP-PRINT Inhibits the printing of ECP OSDS audit results.

INIT:ECP Requests an ECP OKP initialization phase.

INIT:ECP-DB Causes an initialization in main memory of adata base member at the ECP.

OP:ECP Requests the status of a networked MobileTelephone Switching Office (MTSO) ExecutiveCellular Processor (ECP).

OP:ECP-AL Requests a survey of all off-normal alarm scanpoints, or requests the status of an individualscan point.

OP:ECP-AUD Requests audit statistics and queuing data.

OP:ECP-DL Requests the current status of the specifiedinter-ECP Data Link (DL).

OP:ECP-OVLD Requests ECP and cell overload statusinformation.

RMV:ECP-DL Removes the specified inter-ECP Data Link (DL)from service.






RST:ECP-DLEXECUTIVE CELLULARPROCESSOR (ECP)

Restores the specified inter-ECP Data Link (DL)to service.

STOP:DGN-ECP-DL Terminates a previously requested diagnostic ofan inter-ECP Data Link (DL).

ALW:EGSFEXPANDED GENERALSYSTEM FAILURE(EGSF)

Allows printing of the REPT-GENERAL outputmessage.

INH:EGSF Inhibits printing of the REPT-GENERAL outputmessage.

ALW:FILESYS-ACCESFIELD UPDATE (FU)SYSTEM

Changes the access permissions of a specific file.

ALW:FILESYS-MOUNT Allows a removable file system to be mounted.

ALW:FILESYS-OWNER Changes the owner and group of a specific file.

CLR:FILESYS-DIR Removes a directory from the file system.

Removes a file from a directory. CLR:FILESYS-FILE

CLR:IMCAT Invalidates the memory segments of the oldinput message catalog, forcing the new one to beloaded into main memory.

COPY:PTN-ALL Copies one set of partitions into a correspondingset of partitions.

IN:REMOTE-REPT Requests a report about the current status of theactive process.

IN:REMOTE-START Puts the file receiving computer into theremote-file-receive mode.






IN:REMOTE-STOPFIELD UPDATE (FU)SYSTEM

Terminates the input of update files from aremote source.

UPD:DISPLAY Displays information (from the field updatedatabase) about computer field updates.

DUMP:FILE-FORMATFILE SYSTEMMAINTENANCE

Dumps the contents of a file in the specifiedformat.

DUMP:FILE-ALL Dumps the contents of an ASCII file.

DUMP:FILE-PARTL Prints one or more lines of an ASCII file.

IN:FILE-DEL Deletes one or more lines from an ASCII file.

IN:FILE-APND Appends one line of user-supplied text after aspecified line in an ASCII file.

IN:FILE-REPL Replaces one or more lines of an ASCII file withone line of user-supplied text.

IN:FILESYS-DIR Creates a specified directory with read, write,and execute permissions for the owner, groupand others (mode 777).

OP:DN Requests output of the mobile serial number fora specified mobile directory number.

OP:FNAME Reports the full pathname of a file in a mountedfile system.

OP:ST-FILESYS Reports information about all mounted filesystems.

OP:ST-FREEDISK Reports the number of free blocks and freei-nodes available for on-line file systems.






OP:ST-LISTDIRFILE SYSTEMMAINTENANCE

Reports the contents of a specific directory orfile.

OP:ST-SUM Calculates and prints a 16-bit checksum for aspecified file, and prints the number of blocks inthe file.

ALW:UMEMGENERIC ACCESSPACKAGE (GRASP)

Causes the computer Generic Access Package(GRASP) transfer trace to start monitoring theflow of execution, as previously set up with anINIT UMEM command.

ALW:UTIL Enables all currently defined GRASPbreakpoints so that the associated actions areexecuted when the breakpoint conditions occur.

ALW:UTILFLAG Enables a specific GRASP breakpoint so that theassociated actions are executed when thebreakpoint condition occurs.

CLR:UMEM Removes the definition of a GRASP transfertrace to be removed.

CLR:UTIL Removes all currently defined GRASPbreakpoints; clears definitions.

CLR:UTILFLAG Removes the specified breakpoint and clears thedefinition.

COPY:ADDR Copies data from virtual addresses in mainmemory to other virtual addresses, registers, orGRASP utility variables as a response to abreakpoint.

COPY:PID Copies data from virtual addresses in mainmemory to GRASP utility variables.

COPY:REG Copies data from registers to virtual addressesin main memory or registers as an actionassociated with a breakpoint.






COPY:UIDGENERIC ACCESSPACKAGE (GRASP)

Copies data from virtual addresses in mainmemory to GRASP utility variables as animmediate action.

COPY:UVAR Copies data from a GRASP utility variable tovirtual addresses in main memory and inregisters as an action associated with abreakpoint.

DUMP:ADDR Dumps the contents of a specified range ofvirtual addresses in main memory as an actionassociated with a breakpoint.

DUMP:KERN Dumps the contents of a specified range ofvirtual addresses in the kernel as an immediateaction.

DUMP:PID Dumps the contents of a specified range ofvirtual addresses in main memory in theaddress space of a process with the specifiedprocess identifier.

DUMP:PMEM Dumps the contents of a specified range ofphysical addresses in main memory.

DUMP:REG Dumps the contents of one or more registers,either as an immediate action, or an actionassociated with a breakpoint.

DUMP:UID Dumps the contents of a specified range ofvirtual addresses in main memory in theaddress space of a process with the specifiedutility identifier.

DUMP:UVAR Dumps the contents of one or more specifiedGRASP utility variables either as an immediateaction, or an action associated with a breakpoint.

END:WHEN Marks the end of a list of GRASP commands tobe performed when a specified breakpointcondition exists.






IN:DTIMEGENERIC ACCESSPACKAGE (GRASP)

Overrides the default GRASP dynamic real-timelimit with a specified limit until the specifiedclock time or the end of the debugging session,whichever occurs first.

INH:UMEM Causes the GRASP transfer trace to stopmonitoring the flow of execution.

INH:UTIL Disables all GRASP breakpoints.

INH:UTILFLAG Disables a specific GRASP breakpoint.

INIT:UC Informs GRASP that a working utility circuit hasbeen installed causing GRASP to accept traceand hardware breakpoints, reset the utilitycircuit if an error occurred, or end the GRASPsession.

INIT:UMEM Specifies the definition of a GRASP transfertrace to be set up.

LOAD:ADDR Loads a virtual address with specified data as anaction associated with a breakpoint.

LOAD:REG Loads a register with specified data as abreakpoint action.

LOAD:UVAR Loads a GRASP utility variable with specifieddata as an immediate operation or as an actionassociated with a breakpoint.

OP:UMEM Dumps the contents of the GRASP trace to a file.

OP:UTIL Lists currently defined GRASP breakpoints,their status and trace status.






WHEN:PIDGENERIC ACCESSPACKAGE (GRASP)

Starts a list of GRASP commands that areperformed when a specified breakpointcondition exists.

WHEN:UID Starts a list of GRASP commands that areperformed when a specified breakpointcondition exists.

OP:GEN-READLOGGENERIC UPDATE Requests output of the system update event log.

STOP:GEN Stops the system-update command in progress.

UPD:BKOUT Removes temporary updates still active in thesystem.

UPD:GEN-BACKOUT Prepares system for booting from the oldgeneric if it is necessary to back out of the newgeneric.

UPD:GEN-COMMIT Commits to the new generic.

UPD:GEN-ENTER Enters the new generic data into the system.

UPD:GEN-PROCEED Prepares the system for booting from the newgeneric.

UPD:GEN-RESTORE Restores the old generic by removing the newgeneric from the system.






ALW:AUDINHIBITS Allows the running of audits managed by thesystem integrity monitor that were previouslyinhibited.

ALW:CONFLOG Allows error logging on the CONFIG errorlogfile of all errors reported to CONFIG for thespecified unit.

ALW:FILESYS-ACCES Changes the access permissions of a specific file.

ALW:FILESYS-MOUNT Allows a removable file system to be mounted.

ALW:FILESYS-OWNER Changes the owner and group of a specific file.

ALW:REX Allows Routine Exercises (REX) by clearing theREX temporary inhibits for one or morehardware communities.

ALW:SCSD Allows transitions of a scanner and signaldistributor scan point to be reported.

ALW:UTIL Enables all currently defined GRASPbreakpoints so that the associated actions areexecuted when the breakpoint conditions occur.

ALW:UTILFLAG Enables a specific GRASP breakpoint so that theassociated actions are executed when thebreakpoint condition occurs.

CLR:IODRV Allows option setting in the input/outputprocessor driver to suppress IOP Drivermessages.

INH:AUD Inhibits the routine execution of one or moreaudits that are controlled by the system integritymonitor.

INH:CONFLOG Inhibits error logging on the CONFIG errorlogfile for all specified computer units.






INH:FILESYS-UMOUNINHIBITS Inhibits the use of a previously mounted filesystem.

INH:REX Inhibits Routine Exercises (REX) for one or morehardware communities by setting the REXtemporary inhibit(s).

INH:SCSD Inhibits reporting of transitions of a scanner andsignal distributor scan point.

INH:UTIL Disables (but leaves defined) all GRASPbreakpoints.

INH:UTILFLAG Disables (but leaves defined) a specific GRASPbreakpoint.

SET:IODRVIODRV Allows option setting in the Input/OutputProcessor (IOP) Driver (IODRV) to printmessages.

INIT:CDNINITIALIZATION Requests a CDN OSDS initialization phase.

INIT:CDN-DB Initializes one or all data base members in aspecified CDN.

INIT:CELL Requests a cell site initialization phase or a cellmemory boot.

INIT:CNI Requests the initialization of the CommonNetwork Interface (CNI) ring.

INIT:ECP Requests an ECP OKP initialization phase.

INIT:ECP-DB Causes an initialization in main memory of adata base at the ECP.

INIT:MCR-CDN Reinitializes the Mobile Call Register (MCR)associated with an ECID that has been reportedas being up for more than 24 hours.






INIT:MHDINITIALIZATION Formats all or specific disk tracks of the diskpack with initialized sectors.

INIT:UC Informs the 3B21D Computer Generic AccessPackage (GRASP) that a working utility circuithas been installed so that GRASP will againaccept trace and hardware breakpointdefinitions, reset the utility circuit if an erroroccurred, or end the GRASP session.

INIT:ULARP Initializes the UNIX Level Automatic RestartProcess (ULARP).

INIT:UMEM Specifies the definition of a GRASP transfertrace to be set up.

OP:INIT Lists all currently initializing computerhardware units.

OP:MCR-CDN Reports the long duration call data for a MobileCall Register (MCR) associated with an ECIDthat has been reported as being up for more than24 hours.

ALW:CONFLOGINPUT/OUTPUTDEVICES AND LOGS

Allows error logging on the CONFIG errorlogfile of all errors reported to CONFIG for aspecified unit.

DEL:LOG Deletes the selected contents of a logfile andcleans corrupt entries from the file.

INH:CONFLOG Inhibits error logging on the CONFIG errorlogfile for all specified units.

OP:GEN-READLOG Requests output of the system update event log.

OP:LOG Reports the selected contents of a logfile.






OP:MEMERRSINPUT/OUTPUTDEVICES AND LOGS

Reports an interpreted version of selectedMEMLOG entries.

OP:REXINH Lists the hardware communities for whichroutine exercises are currently inhibited bymeans of the INH REX command.

SW:PORTSW Requests a switch of the MTTYC’s ROP and/orMTTY to the alternate MTTYC and a switch ofthe active/standby status of the MTTY and/orROP.

DGN:DUICINPUT/OUTPUTPROCESSOR

Diagnoses the specified Direct User InterfaceController (DUIC).

DGN:HSDC Diagnoses the high-speed specified synchronousdata link controller (HSDC).

DGN:IOP Diagnoses the specified Input/Output Processor(IOP).

DGN:MTC Diagnoses the specified Magnetic TapeController (MTC).

DGN:MTTYC Diagnoses the specified MaintenanceTeletypewriter Controller (MTTYC).

DGN:SCSDC Diagnoses the specified Scanner and SignalDistributor Controller (SCSDC).

DGN:SDLC Diagnoses the specified Synchronous Data LinkController (SDLC).

DGN:TTYC Diagnoses the specified TeletypewriterController (TTYC).

EX:DUIC Exercises a Direct User Interface Controller(DUIC) in an interactive diagnostic mode.






EX:HSDCINPUT/OUTPUTPROCESSOR

Exercises a High-Speed Synchronous DatalinkController (HSDC) in an interactive diagnosticmode.

EX:IOP Exercises an Input/Output Processor (IOP) in aninteractive diagnostic mode.

EX:MTC Exercises a Magnetic Tape Controller (MTC) inan interactive diagnostic mode.

EX:MTTYC Exercises a Maintenance TeletypewriterController (MTTYC) in an interactive diagnosticmode.

EX:SDLC Exercises a Synchronous Data Link Controller(SDLC) in an interactive diagnostic mode.

EX:TTYC Exercises a Teletypewriter Controller (TTYC) inan interactive diagnostic mode.

OP:IODRV Reports the current options set for theinput/output processor driver messages.

RMV:DUI Removes the specified Direct UserInterface (DUI) device from service.

RMV:DUIC Removes the specified Direct User InterfaceController (DUIC) from service.

RMV:HSD Removes the specified high-speed synchronousdata link subdevice from service.

RMV:HSDC Removes the specified High-Speed SynchronousData-Link Controller (HSDC) from service.

RMV:IOP Removes the specified input/output processorand any associated peripheral controllers fromservice.






RMV:MTINPUT/OUTPUTPROCESSOR

Removes the specified magnetic tape devicefrom service.

RMV:MTC Removes the specified Magnetic TapeController (MTC) and any associated magnetictape drives from service.

RMV:MTTY Removes the specified MaintenanceTeletypewriter (MTTY) from service.

RMV:MTTYC Removes the specified MaintenanceTeletypewriter Controller (MTTYC) and allassociated MTTYs, ROPs, and SCCs fromservice.

RMV:ROP Removes the specified Receive-Only Printer(ROP) from service.

RMV:SCC Removes the specified Switching Control Center(SCC) data-link subdevice from service.

RMV:SDL Removes the specified Synchronous Data Link(SDL) subdevice from service.

RMV:SDLC Removes the specified Synchronous Data LinkController (SDLC) from service.

RMV:TTY Removes the specified Teletypewriter (TTY)from service.

RMV:TTYC Removes the specified TeletypewriterController (TTYC) and any associatedteletypewriters from service.

RST:DUI Restores a Direct User Interface (DUI) device toservice.

RST:DUIC Restores a Direct User Interface Controller(DUIC) to service.

RST:HSD Restores a High-Speed Synchronous Data-Link(HSD) subdevice to service.






RST:HSDCINPUT/OUTPUTPROCESSOR

Restores a High-Speed Synchronous Data-LinkController (HSDC) to service.

RST:IOP Restores an Input/Output Processor (IOP) toservice.

RST:MT Restores the specified Magnetic Tape (MT)device to service.

RST:MTC Restores a Magnetic Tape Controller (MTC) toservice.

RST:MTTY Restores the specified MaintenanceTeletypewriter (MTTY) to service.

RST:MTTYC Restores a Maintenance TeletypewriterController (MTTYC) to service.

RST:ROP Restores the ROP to service.

RST:SCC Restores the Switching Control Center (SCC)data-link subdevice to service.

RST:SDL Restores the specified Synchronous Data Link(SDL) subdevice to service.

RST:SDLC Restores a Synchronous Data Link Controller(SDLC) to service.

RST:TTY Unconditionally restores the specified TTY toservice.

RST:TTYC Restores a TTYC to service.






ALW:DMQINTERPROCESSORMESSAGE SWITCH(IMS)

Allows previously inhibited or suspendedsources to send maintenance requests to the3B21D maintenance inhibit requestadministrator.

ALW:TRACE Allows tracing to occur according to previouslyinput trace parameter settings.

CFR:RING Configures the ring to include or exclude ringnode(s) from the active ring segment, or--if thering is down--to initialize it.

DGN:LN Diagnoses the specified Link Nodes (LN).

DGN:RPCN Diagnoses the specified Ring PeripheralController Node (RPCN).

EX:LN Exercises a link node in an interactive,diagnostic mode.

EX:RPCN Exercises a ring peripheral controller node in aninteractive, diagnostic mode.

INH:DMQ Inhibits the specified source of diagnosticrequests.

INH:TRACE Forms the basic on/off mechanism for TRACEwhen used with ALW TRACE.

OP:LN-DL Requests a report of the status of all data linkson a node.

OP:NPMEM Allows reading and reporting of specified NodeProcessor (NP) memory or port locations.

OP:RING Obtains the status or generic information abouta particular node, group of nodes, or particulargroup.






OP:TRACEINTERPROCESSORMESSAGE SWITCH(IMS)

Prints the status of tracing and the setting of thetrace detail flags for subsystems.

RMV:LN Removes the link node from service.

RMV:RPCN Removes the ring peripheral controller nodefrom service.

RST:LN Restores the specified link node to service.

RST:RPCN Restores the specified ring peripheral controllernode to service.

SET:TRACE Changes the operational characteristics of atrace.

ALW:CELLINTERRUPTS Allows a specific software or hardware action atspecified cell site(s).

INH:CELL Inhibits a specific software or hardware action atspecified cell site(s).

OP:CELL Prints the status of cell site equipment.

DGN:LNLINE UNITS Diagnoses the specified Link Nodes (LNs).

EX:LN Exercises a LN in an interactive diagnosticmode.

RMV:LN Removes the specified Link Node (LN) fromservice.

RMV:LN-DL Remove all data links on a particular Link Node(LN) from service.

RMV:LN-UCL Removes a specified Link Node (LN) fromservice.






RST:LNLINE UNITS Restores the Link Node (LN) to service.

RST:LN-DL Restore all data links on a particular Link Node(LN) to service.

DGN:DCS-TRKGRPMAINTENANCECONTROL (MC)

Diagnoses a trunk.


Requests log trunk test data. DUMP:TRK-DATA

OP:ACT Lists all currently active computer hardwareunits.

OP:ALARM Lists all alarmed ECP, CDN, cell, and DCSequipment.

OP:CFGSTAT Requests output configuration statusinformation for computer hardware units.

OP:DCS-DL Requests the current status of the specified DCSDL.

OP:DCS-DS1 Requests the status of DS-1 units at the DCS.

OP:DCS-MRAQ Tells which trunk is being diagnosed by ATMSat a DCS, and which trunks (if any) are waitingto be diagnosed in the ATMS trunk diagnosticqueue.

OP:DL Requests the current status of all equipped cell,DCS, and inter-ECP data links.

OP:DLN Requests the status of all Direct Link Nodes(DLNs).






OP:DMQMAINTENANCECONTROL (MC)

Outputs a list of the queue from the computermaintenance input request administrator.

OP:ECP-AL Requests a survey of all off-normal alarm scanpoints, or requests the status of an individualscan point.

OP:GROW Lists all computer hardware units currently inthe growth maintenance state.

OP:OFL Lists all offline computer hardware units.

OP:OOS Lists all out-of-service computer hardware units.

OP:ST-PORTS Reports the status of each connected computermessage port.

OP:STBY Provides a list of all standby computer hardwareunits.

RMV:CELL-SG Removes all trunks associated with a specifiedcell, server group and antenna face from service.



ALW:CELLOVERLOAD CONTROL Allows a specific software or hardware action atspecified cell site(s).

INH:CELL Inhibits a specific software or hardware action atspecified cell site(s).

OP:CDN-OVLD Requests CDN overload status information.

OP:CELL-OVLD Requests a printout of cell overload and forwardsetup channel control status for specified cells.

OP:ECP-OVLD Requests ECP and cell overload statusinformation.






OP:PMCRPLANTMEASUREMENTS

Outputs the plant measurements commonreports.

OP:PM-CELL Requests output of plant measurement data forone or more cell site(s).

VER:PLMPOWER LEVELMEASUREMENTS (PLM)

Determines which Power Level Measurement(PLM) requests are active.

EXC:ENVIR-PROCPROCESS CONTROL Executes a task as either a kernel or supervisorprocess.

EXC:ENVIR-UPROC Executes a task as a user process.

OP:ST-PROCESS Reports the status of active processes by specificclass.

Stops any process. STOP:EXC-ANY

STOP:EXC-USER Stops a user process specified either by IDnumber or by pathname.

STOP:GEN Stops the system-update command in progress.

CLR:EMERDMPPROCESSORINITIALIZATIONAND RECOVERY

Clears the emergency dump partition statusflag.

COPY:TAPE-EMERDMP Copies data from the emergency dump partitionon a disk to a magnetic tape.

INIT:ULARP Initializes the User Level Automatic RestartProcess (ULARP).

OP:EMERSTAT Reports the status of the emergency dumppartition on the disk: full or empty.

OP:ULARP-COMMAND Requests the status of run commands.






OP:ULARP-EXECSEQPROCESSORINITIALIZATIONAND RECOVERY

Outputs the execution sequence of childprocesses and run commands during abootstrap or user initialization procedure.

OP:ULARP-PROCESS Outputs the status of ULARP child processes.

RCV:M-BROWSERECENT CHANGE(RC)

Reads or patches a central processor data baseusing the "browse" tool.

RCV:M-COMPAREDB Compares the ECD and the SG database.

Generates a skeleton ECD. RCV:M-CREATEECD

Generates a skeleton SG database. RCV:M-CREATESG

RCV:M-EVOL Invokes a specified recent change activity; thisformat is used to evolve a new data base froman old one.

RCV:M-FDIFF Performs a comparison of two form types.

RCV:M-KEYCMP Performs a comparison of two sorted keyfiles.

RCV:M-KEYCOMM Creates a list of all keys that are common to twosorted keyfiles.

RCV:M-KEYS Creates a sorted list of form keys for all theinstances of a given form type found in the ECDand the SG databases.

RCV:M-LOADF3B Create a data base in loadfile format from a setof data base files.

RCV:M-NEWDB Creates a sorted list of keys for all form types inthe ECD and the SG databases.

RCV:M-PRINTDB Creates files of form instances when specifieddata form type(s) from the ECD and the SGdatabases are given.






RCV:M-PRINTFRMRECENT CHANGE(RC)

Creates a file of all form instances, given a list ofform keys, found in the ECD and the SGdatabase.

RCV:M-RCVECD Reviews or modifies an ECD through recentchange.

RCV:M-RCVSG Reviews or modifies a SG database throughrecent change.

RCV:M-TRANSGEN Creates a translation data base when a treeaddress space and translation specifications aregiven.

RCV:M-TREEBLD Builds a tree address space given the old andnew form specifications.

RCV:M-VFYDFLT Checks the syntax of the specified default fileand verifies that the low level field names andvalues contained therein are legal.

RFT:ABORTRETROFIT PROCESS Aborts the current generic retrofit proceduralprocess.

RFT:BEGINPOST Invokes the generic retrofit process from theending generic.

RFT:FDUMP Dumps the contents of a file.

RFT:PRINT Prints the named step or supplementalinstruction file of the generic retrofit proceduralprocess.






CFR:RINGRING UNITS Configures the ring to include or exclude RNsfrom the active ring segment or, if the ring isdown, to initialize it.

Diagnoses the specified RPCN. DGN:RPCN

EX:RPCN Exercises a RPCN in an interactive diagnosticmode.

INIT:CNI Initialize the Common Network Interface (CNI)ring.

OP:RING Obtain status or generic information about oneor more nodes.

Removes the specified RPCN from service. RMV:RPCN

Restores the RPCN to service. RST:RPCN

CLR:FANALMSCAN AND SIGNALDISTRIBUTOR(SCSD) POINTS

Performs a remote reset of the computer fanalarm.

EX:SCSDC Exercises an SCSDC in an interactive diagnosticmode.

OP:SCSD Reports the inhibit status and the state of SCSDscan points.

ORD:SCSD Performs one of four distribution operations onan SCSD distribute point.

RMV:SCSDC Removes the specified SCSDC from service.

RST:SCSDC Restores an SCSDC to service.






INH:SLKSIGNALING LINK Sets, resets, or requests the status of the alarminhibit flag of a Signaling Link (SLK).

COPY:TAPE-INTAPE MANIPULATION Copies files from a magnetic tape containing fullor relative pathnames and header information,and places them in their respective directories.

COPY:TAPE-OUT Copies one or more files to a magnetic tape,along with full or relative pathnames andheader (status) information.

COPY:TAPE-TEST Writes the diagnostic test tape header onto amagnetic tape.

STOP:BKDISK Stops the copying of the boot disk to tape.

VFY:TAPE Verifies the readability of information on systemtapes and the consistency of corresponding hashsums.

DGN:DCS-TRKGRPTRUNK UNITS Diagnoses a trunk.

DUMP:TRK-DATA Requests logged trunk test data; the resultingdata will appear in tabular form on the ROPwith explanatory headers.

OP:DCS-TRKALM Requests a report of all trunk groups in a DCSalarm.

OP:DCS-TRKGRP Requests the status of trunks.


RST:DCS-TRKGRP Restores a trunk member to service.





Table 2 Index of Input Messages by Function (Continued)_ ________________________________________________________________________________________________

Function Purpose Message ID_ ________________________________________________________________________________________________

INIT:ULARPUSER LEVELAUTOMATIC RESTART

Initializes the UNIX Level Automatic RestartProcess (ULARP).

OP:ULARP-COMMAND Requests the status of run commands.

OP:ULARP-EXECSEQ Requests a listing of the execution sequence ofchild processes and run commands during abootstrap or user initialization procedure.

OP:ULARP-PROCESS Requests the status of ULARP child processes.

SCHED:VCSAVOICE CHANNELSELECTIONACTIVITIES (VCSA)

Schedules Voice Channel Selection Activity(VCSA) measurements for the events requestedat the specified Cell Site (CS).

STOP:VCSA Cancels an active or a pending request formeasurement of Voice Channel SelectionActivity (VCSA).

VER:VCSA Determines which VCSA measurement requestsare currently scheduled or active.







Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW:RNC TPU DGN

ID............. ALW:RNC-TPU-DGNRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

NOTE: This command may be entered only from a Radio Network Controller (RNC)Application Processor (AP) or Operations, Administration, and Maintenance(OA&M) Proxy AP by invoking the Traffic Processing Unit Command LineInterface (TPUCLI) command.

Allow all Traffic Processing Unit (TPU) board Power On Self Test (POST) diagnostic test.

Format 1: Allow POST diagnostic test for the equipped TPU card on the specified TPUand RNC.

Format 2: Allow POST diagnostic test for the Common Intelligent Carrier Card (CICC) onthe specified TPU and RNC.

Format 3: Allow POST diagnostic test for the Gateway Intelligent Carrier Card (GICC) onthe specified TPU and RNC.

2. FORMAT

[1] ALW:RNC a, TPU b, DGN

[2] ALW:RNC a, TPU b, CICC c, DGN

[3] ALW:RNC a, TPU b, GICC d, DGN

3. EXPLANATION OF MESSAGE

a = RNC number (1-15).

b = TPU shelf number (1-2).

c = CICC slot number (5-18).

NOTE: Slots 5,6,17,18 are multipurpose slots, which may or may not beprovisioned for CICC.

d = GICC slot number (3,4,19,20).

4. SYSTEM RESPONSE

IN PROGRESS = Command is being executed by the system. The input command haspassed syntax checking and is being executed by the system. Outputmessage will follow.

PARAMETER ERROR = Invalid input parameters were specified.

REJECTED = The input command was rejected because it is not supported by thesystem.

SYNTAX ERROR = Invalid input syntax was specified.

UNEXPECTED ERROR = A software error occurred.


Issue 28 ALW:RNC-TPU-DGN-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW:RNC TPU DGN August 2005

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesALW-RNC-TPU-DGN

Other References:

401-710-082 Radio Network Controller (RNC) Operations, Administration, and Maintenance(OA&M) Guide


ALW:RNC-TPU-DGN-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW:RNC ABREVC

ID............. ALW:RNC-ABREVCRELEASE ....... 25.0 and laterTYPE .......... Input

WARNINGThis message may be service-affecting.Read purpose carefully.

**WARNING**This command may cause active calls to drop.

1. PURPOSE


This command Allow assert brevity control on the specified RNC.

2. FORMAT

ALW:RNC a, ABREVC



4. SYSTEM RESPONSE






5. REFERENCES

IM/OM References:

Input MessagesNone

Output MessagesALW-RNC-ABREVC


Issue 28 ALW:RNC-ABREVC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW:RNC ABREVC August 2005

Other References:



ALW:RNC-ABREVC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 BKUP:RNCDB

ID............. BKUP:RNCDBRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

This command requests that a backup occur for the active Radio Network Controller(RNC) application database on the pre-specified Operations, Administration, andMaintenance (OA&M) proxy server archive directory.

2. FORMAT

BKUP:RNCDB, RNC [a ALL]



4. SYSTEM RESPONSE

NG = No Good. Indicates that invalid input parameters were specified or anunrecoverable software error occurred.

PF = Printout Follows. Followed by a BKUP-RNCDB output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the BKUP-RNCDB commandwill be delayed.

RL = Retry Later. One of the following reasons may be specified:

— Command was rejected because it conflicts with anactive command.

The requested command would cause a problem if it were to runbecause of an already running or queued command.

— Managed object TYPE [NUMBER] is busy.

The managed object indicated by TYPE [and NUMBER] already has acommand running or queued, and it may only have one activecommand associated with it at a time.

— Maximum number of commands already running.

The system allows only a certain number of commands to runsimultaneously; running the requested command would exceed thelimit.


Issue 28 BKUP:RNCDB-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksBKUP:RNCDB August 2005

5. REFERENCES

IM/OM References:

Input MessagesCOPY:RNCDBDELBKUP:RNCDBOP:RNCDB

Output MessagesBKUP-RNCDBCOPY-RNCDBDELBKUP-RNCDBOP-RNCDB

Other References:

401-710-201 Mobility Manager Application Processor Cluster (MM-APC) Operations,Administration, and Maintenance Guide


BKUP:RNCDB-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CLEAR:RNC GICC

ID............. CLEAR:RNC-GICCRELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE


To request the clearing of an existing lockout, force switch or manual switch condition onthe specified Automatic Protection Switching (APS) mated Asynchronous Transfer Mode(ATM) pair. This command can only be successfully executed when the APS capability isenabled on the RNC.

2. FORMAT

CLEAR:RNC a, GICC b, ATM c



b = Gateway Intelligent Carrier Card (GICC) slot number (3,4,19,20).

c = ATM port number (1-2, the ATM ports are number 1 and 2 from the bottomup).

4. SYSTEM RESPONSE


PARAMETER ERROR = Out of range value was specified.



5. REFERENCES

IM/OM References:

Input MessagesNone

Output MessagesCLEAR-RNC-GICCGET-RNC-GICC


Issue 28 CLEAR:RNC-GICC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCLEAR:RNC GICC August 2005

Other References:



CLEAR:RNC-GICC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COPY:RNCDB RNC

ID............. COPY:RNCDBRELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE

This command requests a restore (a copy) of the Radio Network Controller (RNC)application database. The request can be for an individual RNC or for all RNCs using themost recent backup file from the $CDMA_OAM_ROOT/rncdbbackups directory, thebackup file is specified by the system user.

2. FORMAT

COPY:RNCDB, RNC [a ALL], DIRNAME "b"



b = The backup directory/filename entered inside quotes (For example:"rnc24_12.0").

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a COPY-RNCDB output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the COPY-RNCDB commandwill be delayed.









Issue 28 COPY:RNCDB-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOPY:RNCDB RNC August 2005

5. REFERENCES

IM/OM References:

Input MessagesBKUP:RNCDBDELBKUP:RNCDBOP:RNCDB


Other References:



COPY:RNCDB-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DELBKUP:RNCDB RNC

ID............. DELBKUP:RNCDBRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

This command requests that a specified Radio Network Controller (RNC) applicationdatabase on the pre-specified Operations, Administration, and Maintenance (OA&M)proxy server archive directory, be deleted.

2. FORMAT

DELBKUP:RNCDB, DIRNAME "a"


a = The backup directory/filename entered inside quotes (For example:"rnc24_12.0").

4. SYSTEM RESPONSE











Issue 28 DELBKUP:RNCDB-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDELBKUP:RNCDB RNC August 2005

5. REFERENCES

IM/OM References:

Input MessagesBKUP:RNCDBCOPY:RNCDBOP:RNCDB


Other References:



DELBKUP:RNCDB-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EXPORT:RNC CONFIG

ID............. EXPORT:RNC-CONFIGRELEASE ....... 23.0 and laterTYPE .......... Input

1. PURPOSE


Export the configuration values in Radio Network Controller Database (RNCDB) to aspecified file in format compatible with config.ini which is used by the TrafficProcessing Unit (TPU) software. This command may be used for remote configurationchanges.

2. FORMAT

EXPORT:RNC a, CONFIG, b



b = A valid file name including the full path or relative path name, for example:/temp/config.ini or ./config-file.ini.

4. SYSTEM RESPONSE






5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesEXPORT-RNC-CONFIG


Issue 28 EXPORT:RNC-CONFIG-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEXPORT:RNC CONFIG August 2005

Other References:



EXPORT:RNC-CONFIG-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 GET:RNC ABREVC

ID............. GET:RNC-ABREVCRELEASE ....... 25.0 and laterTYPE .......... Input



1. PURPOSE


This command gets the current assert brevity control state on the specified RNC.

2. FORMAT

GET:RNC a, ABREVC



4. SYSTEM RESPONSE






5. REFERENCES

IM/OM References:

Input MessagesNone

Output MessagesGET-RNC-ABREVC


Issue 28 GET:RNC-ABREVC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksGET:RNC ABREVC August 2005

Other References:



GET:RNC-ABREVC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 GET:RNC ALARM

ID............. GET:RNC-ALARMRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE


Format 1: Report the alarm details that have been generated autonomously for thespecified Traffic Processing Unit (TPU) on the specified RNC.

Format 2: Report summary of all alarms (total number of alarms, and number of alarmsin each severity category) that have been generated autonomously on thespecified RNC.

2. FORMAT

[1] GET:RNC a, TPU b, ALARM

[2] GET:RNC a, [TPU b], ALARM [;SUMMARY]




SUMMARY = Summary will be displayed instead of detailed alarms.

4. SYSTEM RESPONSE






5. REFERENCES

IM/OM References:

Input MessagesNone


Issue 28 GET:RNC-ALARM-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksGET:RNC ALARM August 2005

Output MessagesGET-RNC-ALARM-SUMGET-RNC-TPU-ALARM

Other References:



GET:RNC-ALARM-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 GET:RNC GICC

ID............. GET:RNC-GICCRELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE


To report Automatic Protection Switching (APS) related information available for the5ESS Gateways (GWs) resident on the specified Gateway Intelligent Carrier Card (GICC).This command can only be successfully executed when the APS capability is enabled onthe RNC.

2. FORMAT

GET:RNC a, GICC b, 5EGW, INFO



b = GICC slot number (3,4,19,20).

4. SYSTEM RESPONSE





5. REFERENCES

IM/OM References:

Input MessagesNone

Output MessagesGET-RNC-GICC

Other References:



Issue 28 GET:RNC-GICC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksGET:RNC GICC August 2005



GET:RNC-GICC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 GET:RNC INSTALL

ID............. GET:RNC-INSTALLRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE


Report the installation software and hardware versions of the specified RNC or report theinstallation status for the specified Gateway Intelligent Carrier Card (GICC) or BladePacket Control Function (BPCF) of the specified RNC.

NOTE: It may take approximately sixty seconds after a GICC initializes or a GICC isremoved from a Traffic Processing Unit (TPU) shelf for the GICC’s hardwareversion to be accurately reflected in this command’s output.

Format 1: Report the installation software and hardware versions of the specified RNC.

Format 2: Report the installation status for the specified GICC of the specified RNC.

Format 3: Report the installation status for the specified BPCF of the specified RNC.

2. FORMAT

[1] GET:RNC a, INSTALL, VERSION

[2] GET:RNC a, TPU b, GICC c, INSTALL, STATUS

[3] GET:RNC a, TPU b, BPCF d, INSTALL, STATUS




c = GICC slot number (3).

d = BPCF slot number (5,6,17,18).

NOTE: Slots 5,6,17,18 are multipurpose slots, which may or may not beprovisioned for BPCF.

4. SYSTEM RESPONSE





Issue 28 GET:RNC-INSTALL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksGET:RNC INSTALL August 2005



5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesGET-RNC-INSTALL

Other References:



GET:RNC-INSTALL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 GET:RNC INVENTORY

ID............. GET:RNC-INVENTORYRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE


Report the equipped Traffic Processing Units (TPUs) on the specified RNC.

2. FORMAT

GET:RNC a, INVENTORY



4. SYSTEM RESPONSE






5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesGET-RNC-INVENTORY

Other References:



Issue 28 GET:RNC-INVENTORY-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksGET:RNC INVENTORY August 2005



GET:RNC-INVENTORY-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 GET:RNC PDSNLIST

ID............. GET:RNC-PDSNLISTRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE


Report the Packet Data Serving Node (PDSN) list for the specific RNC, the TrafficProcessing Unit (TPU) shelf, or a specific Blade Packet Control Function (BPCF) in an RNC.

Format 1: Report the PDSN List for both TPUs on the specified RNC.

Format 2: Report the PDSN List on the specified TPU and RNC.

Format 3: Report the PDSN List on the specified BPCF card, TPU and RNC.

2. FORMAT

[1] GET:RNC a, PDSNLIST

[2] GET:RNC a, TPU b, PDSNLIST

[3] GET:RNC a, TPU b, BPCF c, PDSNLIST




c = BPCF card number (5,6,17,18).


4. SYSTEM RESPONSE







Issue 28 GET:RNC-PDSNLIST-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksGET:RNC PDSNLIST August 2005

5. REFERENCES

IM/OM References:

Input MessagesNone

Output MessagesGET-RNC-PDSNLIST

Other References:



GET:RNC-PDSNLIST-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 GET:RNC PSPCF

ID............. GET:RNC-PSPCFRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE


Report the Process Status on the Blade Packet Control Function (BPCF) for the specifiedelement.

Format 1: Report the Process Status of all BPCF cards on both Traffic Processing Units(TPUs) of the specified RNC.

Format 2: Report the Process Status of all BPCF cards for the specified TPU and RNC.

Format 3: Report the Process Status on the specified BPCF card, TPU and RNC.

2. FORMAT

[1] GET:RNC a, PSPCF

[2] GET:RNC a, TPU b, PSPCF

[3] GET:RNC a, TPU b, BPCF c, PSPCF






4. SYSTEM RESPONSE







Issue 28 GET:RNC-PSPCF-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksGET:RNC PSPCF August 2005

5. REFERENCES

IM/OM References:

Input MessagesNone

Output MessagesGET-RNC-PSPCF

Other References:



GET:RNC-PSPCF-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 GET:RNC STATUS

ID............. GET:RNC-STATUSRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE


Report the call processing status for the specified RNC.

2. FORMAT

GET:RNC a, STATUS



4. SYSTEM RESPONSE






5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesGET-RNC-STATUS

Other References:



Issue 28 GET:RNC-STATUS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksGET:RNC STATUS August 2005



GET:RNC-STATUS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 GET:RNC TPU DGNRESULT

ID............. GET:RNC-TPU-DGNRESRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE


Report the available results of Power On Self Test (POST) diagnostics test(s) for thespecified Traffic Processing Unit (TPU) managed resource of the specified RNC and reportthe current status of the POST diagnostics test.

Format 1: Report the available results of POST diagnostics test(s) for the equipped TPUcards (CICC and GICC) on the specified TPU and RNC.

Format 2: Report the available results of POST diagnostics test(s) for the specifiedGateway Intelligent Carrier Card (GICC) on the specified TPU and RNC.

Format 3: Report the available results of POST diagnostics test(s) for the specifiedCommon Intelligent Carrier Card (CICC) on the specified TPU and RNC.

2. FORMAT

[1] GET:RNC a, TPU b, DGNRESULT

[2] GET:RNC a, TPU b, GICC c, DGNRESULT

[3] GET:RNC a, TPU b, CICC d, DGNRESULT




c = GICC slot number (3,4,19,20).

d = CICC slot number (5-18).


4. SYSTEM RESPONSE





Issue 28 GET:RNC-TPU-DGNRES-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksGET:RNC TPU DGNRESULT August 2005



5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesGET-RNC-TPU-DGNRES

Other References:



GET:RNC-TPU-DGNRES-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 GET:RNC TPU FAILEDPVC

ID............. GET:RNC-TPU-FAILEDPVC

RELEASE ....... 23.0 and laterTYPE .......... Input

1. PURPOSE


Report the available failed Permanent Virtual Circuit (PVC) for the specified TrafficProcessing Unit (TPU) managed resource of the specified RNC.

Format 1: Report the list of failed PVC for the equipped TPU cards (Gateway IntelligentCarrier Card [GICC]) on the specified TPU and RNC.

Format 2: Report the list of failed PVC for the specified GICC on the specified TPU andRNC.

Format 3: Report the list of failed PVC for the specified Asynchronous Transfer Mode(ATM) port on the specified GICC, TPU and RNC.

2. FORMAT

[1] GET:RNC a, TPU b, FAILEDPVC

[2] GET:RNC a, TPU b, GICC c, FAILEDPVC

[3] GET:RNC a, TPU b, GICC c, ATM d, FAILEDPVC





d = ATM port number (1-2, the ATM ports are number 1 and 2 from the bottomup).

4. SYSTEM RESPONSE







Issue 28 GET:RNC-TPU-FAILEDPVC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksGET:RNC TPU FAILEDPVC August 2005

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesGET-RNC-TPU-FAILEDPVC

Other References:



GET:RNC-TPU-FAILEDPVC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 GET:RNC TPU INFO

ID............. GET:RNC-TPU-INFORELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE


Report the administrative information, operational information and usage information forthe specified Blade Packet Control Function (BPCF) card and Traffic Processing Unit(TPU).

2. FORMAT

[1] GET:RNC a, TPU b, BPCF c, INFO






4. SYSTEM RESPONSE






5. REFERENCES

IM/OM References:

Input MessagesNone


Issue 28 GET:RNC-TPU-INFO-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksGET:RNC TPU INFO August 2005

Output MessagesGET-RNC-TPU-INFO

Other References:



GET:RNC-TPU-INFO-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 GET:RNC TPU INVENTORY

ID............. GET:RNC-TPU-INVENTRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE


Report the equipped Traffic Processing Unit (TPU) cards on the specified TPU and RNC.

2. FORMAT

GET:RNC a, TPU b, INVENTORY




4. SYSTEM RESPONSE






5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesGET-RNC-TPU-INVENT

Other References:



Issue 28 GET:RNC-TPU-INVENT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksGET:RNC TPU INVENTORY August 2005



GET:RNC-TPU-INVENT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 GET:RNC TPU STATE

ID............. GET:RNC-TPU-STATERELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE


Report the Administrative State, Operational State and Usage State for the specified TrafficProcessing Unit (TPU) cards.

Format 1: Report the states for the equipped TPU cards on the specified TPU and RNC.

Format 2: Report the states for the specified Ethernet Switch Card (ESC) on the specifiedTPU and RNC.

Format 3: Report the states for the specified Gateway Intelligent Carrier Card (GICC) onthe specified TPU and RNC.

Format 4: Report the states for the specified Common Intelligent Carrier Card (CICC) onthe specified TPU and RNC.

Format 5: Report the states for the specified Alarm Card (AC) number of a specifiedAlarm Card Slot (ACS) on the specified TPU and RNC.

Format 6: Report the states for the specified ATM of the specified GICC on the specifiedTPU and RNC.

Format 7: Report the states for the specified SC GICC on the specified TPU and RNC.

Format 8: Report the states for the specified Blade Packet Control Function (BPCF) on thespecified TPU and RNC.

Format 9: Report the state of Internet Protocol Base Transceiver Station Gateway(IPBTSGW).

2. FORMAT

[1] GET:RNC a, TPU b, STATE

[2] GET:RNC a, TPU b, ESC c, STATE

[3] GET:RNC a, TPU b, GICC d, STATE

[4] GET:RNC a, TPU b, CICC e, STATE

[5] GET:RNC a, TPU b, ACS f, AC g, STATE

[6] GET:RNC a, TPU b, GICC d, ATM h, STATE

[7] GET:RNC a, TPU b, GICC i, SC, STATE

[8] GET:RNC a, TPU b, BPCF j, STATE


Issue 28 GET:RNC-TPU-STATE-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksGET:RNC TPU STATE August 2005

[9] GET:RNC a, TPU b, GICC i, IPBTSGW, STATE




c = ESC slot number (2,21).


e = CICC slot number (5-18).


f = ACS number (1).

g = AC number (1-2).

h = ATM port number (1-2, the ATM ports are number 1 and 2 from the bottomup).

i = Shelf Controller (SC) GICC slot number (3).

j = BPCF card number (5,6,17,18).


4. SYSTEM RESPONSE






5. REFERENCES

IM/OM References:

Input MessagesNone

Output MessagesGET-RNC-TPU-STATE


GET:RNC-TPU-STATE-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 GET:RNC TPU STATE

Other References:



Issue 28 GET:RNC-TPU-STATE-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksGET:RNC TPU STATE August 2005



GET:RNC-TPU-STATE-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 GET:RNC TPU VER CON

ID............. GET:RNC-TPU-VER-CONRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE


Report the running configuration file version and configured configuration file versions forthe specified Traffic Processing Unit (TPU) managed resource of the specified RNC.

Format 1: Report the configured application software version and for the equipped TPUcards on the specified TPU and RNC.

Format 2: Report the configured application software version and for the specifiedGateway Intelligent Carrier Card (GICC) on the specified TPU and RNC.

Format 3: Report the configured application software version and for the specifiedCommon Intelligent Carrier Card (CICC) on the specified TPU and RNC.

Format 4: Report the configured application software version and for the specified BladePacket Control Function (BPCF) on the specified TPU and RNC.

2. FORMAT

[1] GET:RNC a, TPU b, VERSION, CONFIG

[2] GET:RNC a, TPU b, GICC c, VERSION, CONFIG

[3] GET:RNC a, TPU b, CICC d, VERSION, CONFIG

[4] GET:RNC a, TPU b, BPCF e, VERSION, CONFIG







e = BPCF card number (5,6,17,18).



Issue 28 GET:RNC-TPU-VER-CON-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksGET:RNC TPU VER CON August 2005

4. SYSTEM RESPONSE






5. REFERENCES

IM/OM References:

Input MessagesNone

Output MessagesGET-RNC-TPU-VER-CON

Other References:



GET:RNC-TPU-VER-CON-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 GET:RNC TPU VERSION

ID............. GET:RNC-TPU-VERSIONRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE


Report active application software version and configured application software version forthe specified Traffic Processing Unit (TPU) managed resource of the specified RNC.

Format 1: Report the application software version for the equipped TPU cards on thespecified TPU and RNC.

Format 2: Report the application software version for the specified Ethernet Switch Card(ESC) on the specified TPU and RNC.

Format 3: Report the application software version for the specified Gateway IntelligentCarrier Card (GICC) on the specified TPU and RNC.

Format 4: Report the application software version for the specified Common IntelligentCarrier Card (CICC) on the specified TPU and RNC.

Format 5: Report the application software version for the specified Alarm Card (AC)number of a specified Alarm Card Slot (ACS) on the specified TPU and RNC.

Format 6: Report the application software version for the specified Blade Packet ControlFunction (BPCF) on the specified TPU and RNC.

2. FORMAT

[1] GET:RNC a, TPU b, VERSION

[2] GET:RNC a, TPU b, ESC c, VERSION

[3] GET:RNC a, TPU b, GICC d, VERSION

[4] GET:RNC a, TPU b, CICC e, VERSION

[5] GET:RNC a, TPU b, ACS f, AC g, VERSION

[6] GET:RNC a, TPU b, BPCF h, VERSION




c = ESC slot number (2,21).



Issue 28 GET:RNC-TPU-VERSION-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksGET:RNC TPU VERSION August 2005

e = CICC slot number (5-18).


f = ACS number (1).

g = AC number (1-2).

h = BPCF card number (5,6,17,18).


4. SYSTEM RESPONSE






5. REFERENCES

IM/OM References:

Input MessagesNone

Output MessagesGET-RNC-TPU-VERSION

Other References:



GET:RNC-TPU-VERSION-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 GET:RNC VERSION

ID............. GET:RNC-VERSIONRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE


Report the application software version for the specified RNC.

2. FORMAT

GET:RNC a, VERSION



4. SYSTEM RESPONSE






5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesGET-RNC-VERSION

Other References:



Issue 28 GET:RNC-VERSION-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksGET:RNC VERSION August 2005



GET:RNC-VERSION-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 HALT:RNC TPU

ID............. HALT:RNC-TPURELEASE ....... 24.0 and laterTYPE .......... Input


**WARNING**This command will result in Radio Network Controller (RNC) losingCommunication with Blade Packet Control Function (BPCF) card.

1. PURPOSE

NOTE: This command may be entered only from an RNC Application Processor (AP) orOperations, Administration, and Maintenance (OA&M) Proxy AP by invokingthe Traffic Processing Unit Command Line Interface (TPUCLI) command.

Halt the specified BPCF card on the specified Traffic Processing Unit (TPU) and RNC.

2. FORMAT

HALT:RNC a, TPU b, BPCF c




c = BPCF card slot number (5,6,17,18).


4. SYSTEM RESPONSE






5. REFERENCES

IM/OM References:

Input MessagesNone


Issue 28 HALT:RNC-TPU-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksHALT:RNC TPU August 2005

Output MessagesGET-RNC-TPU-STATEHALT-RNC-TPU

Other References:



HALT:RNC-TPU-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 IMPORT:RNC CONFIG

ID............. IMPORT:RNC-CONFIGRELEASE ....... 23.0 and laterTYPE .......... Input

1. PURPOSE


Import the configuration values from a specified file in format compatible withconfig.ini which is used by the Traffic Processing Unit (TPU) software, into RadioNetwork Controller Database (RNCDB). This command may be used for remoteconfiguration changes.

2. FORMAT

IMPORT:RNC a, CONFIG, b



b = A valid file name including the full path or relative path name, for example:/temp/config.ini or ./config-file.ini.

4. SYSTEM RESPONSE






5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesIMPORT-RNC-CONFIG


Issue 28 IMPORT:RNC-CONFIG-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksIMPORT:RNC CONFIG August 2005

Other References:



IMPORT:RNC-CONFIG-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 INH:RNC ABREVC

ID............. INH:RNC-ABREVCRELEASE ....... 25.0 and laterTYPE .......... Input



1. PURPOSE


This command inhibits the assert brevity control on the specified RNC.

2. FORMAT

INH:RNC a, ABREVC



4. SYSTEM RESPONSE






5. REFERENCES

IM/OM References:

Input MessagesNone

Output MessagesINH-RNC-ABREVC


Issue 28 INH:RNC-ABREVC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksINH:RNC ABREVC August 2005

Other References:



INH:RNC-ABREVC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 INH:RNC TPU DGN

ID............. INH:RNC-TPU-DGNRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE


Inhibit the Power On Self Test (POST) diagnostic on the specified Traffic Processing Unit(TPU) board(s). The inhibition will take effect the next time the TPU board is reset.

Format 1: Inhibit POST diagnostic test for all TPU cards (CICC and GICC) for thespecified RNC.

Format 2: Inhibit POST diagnostic test for the specified Common Intelligent Carrier Card(CICC) of the specified TPU and RNC.

Format 3: Inhibit POST diagnostic test for the specified Gateway Intelligent Carrier Card(GICC) of the specified TPU and RNC.

2. FORMAT

[1] INH:RNC a, TPU b, DGN

[2] INH:RNC a, TPU b, CICC c, DGN

[3] INH:RNC a, TPU b, GICC d, DGN




c = CICC slot number (5-18).



4. SYSTEM RESPONSE





Issue 28 INH:RNC-TPU-DGN-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksINH:RNC TPU DGN August 2005



5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesINH-RNC-TPU-DGN

Other References:



INH:RNC-TPU-DGN-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 INSTALL:RNC TPU

ID............. INSTALL:RNC-TPURELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE


Install the software and configuration file on the specified Gateway Intelligent CarrierCard (GICC) or Blade Packet Control Function (BPCF) card.

Format 1: Install the software and configuration file for all hardware types on thespecified GICC. All binary and configuration files are copied to the GICC.

Format 2: Install only configuration data on the specified GICC. All configuration filesare copied to the GICC.

Format 3: Install the software and configuration file for the specified hardware type onthe specified GICC. Binary and configuration files of specified hardware onlyis copied to the GICC.

Format 4: Install the software and configuration file for the specified slot on the specifiedBPCF. The newly installed software is activated after installation. Thiscommand may involve a shutdown of BPCF, if the card was in the unlockedstate. The command may take anywhere between 10-90 minutes.

2. FORMAT

[1] INSTALL:RNC a, TPU b, GICC c, VERSION d, ALL

[2] INSTALL:RNC a, TPU b, GICC c, VERSION d, CONFIG

[3] INSTALL:RNC a, TPU b, GICC c, VERSION d, HWTYPE e

[4] INSTALL:RNC a, TPU b, BPCF f, VERSION d



b = Traffic Processing Unit (TPU) shelf number (1-2).

c = GICC slot number (3).

d = Version string. This is the BPCF version string of the software package thatwill be copied to the specified GICC on the specified TPU. The version canbe found by using the GET:RNC-INSTALL input command.

e = Hardware type:

ATM — Asynchronous Transfer Mode (ATM).BPCF — Blade Packet Control Function (BPCF).


Issue 28 INSTALL:RNC-TPU-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksINSTALL:RNC TPU August 2005

CICC — Common Intelligent Carrier Card (CICC).GICC — Gateway Intelligent Carrier Card (GICC).

f = BPCF slot number (5,6,17,18).


4. SYSTEM RESPONSE


INSTALLATION ERROR = An installation error occurred.

PARAMETER RANGE ERROR = Invalid input parameters were specified.


TPU MANAGER UNAVAILABLE = The TPU Manager is not available.

5. REFERENCES

IM/OM References:

Input MessagesGET:RNC-INSTALL

Output MessagesGET-RNC-INSTALLINSTALL-RNC-TPU

Other References:



INSTALL:RNC-TPU-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 LOCK:RNC TPU

ID............. LOCK:RNC-TPURELEASE ....... 24.0 and laterTYPE .......... Input



1. PURPOSE


Lock the specified Traffic Processing Unit (TPU) cards on the specified TPU and RNC.

Format 1: Lock the specified Gateway Intelligent Carrier Card (GICC) on the specifiedTPU and RNC.

Format 2: Lock the specified Common Intelligent Carrier Card (CICC) on the specifiedTPU and RNC.

Format 3: Lock the specified Asynchronous Transfer Mode (ATM) port for the specifiedGICC on the specified TPU and RNC.

Format 4: Lock the specified Blade Packet Control Function (BPCF) card on the specifiedTPU and RNC.

Format 5: Locks the Internet Protocol Base Transceiver Station Gateway (IPBTSGW).gateway on the specified RNC.

2. FORMAT

[1] LOCK:RNC a, TPU b, GICC c

[2] LOCK:RNC a, TPU b, CICC d

[3] LOCK:RNC a, TPU b, GICC c, ATM e

[4] LOCK:RNC a, TPU b, BPCF f

[5] LOCK:RNC a, TPU b, GICC c, IPBTSGW






Issue 28 LOCK:RNC-TPU-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksLOCK:RNC TPU August 2005



e = ATM port number (1-2, the ATM ports are number 1 and 2 from the bottomup).

f = BPCF card slot number (5,6,17,18).


4. SYSTEM RESPONSE






5. REFERENCES

IM/OM References:

Input MessagesNone

Output MessagesGET-RNC-TPU-STATELOCK-RNC-TPU

Other References:



LOCK:RNC-TPU-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 LOCKOUT:RNC GICC

ID............. LOCKOUT:RNC-GICCRELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE


To prevent Automatic Protection Switching (APS) to the protection 5ESS Gateway(5EGW) in the specified APS mated pair. The protection 5EGW always resides onTransaction Processing Unit (TPU) shelf 2 (bottom TPU shelf). This command can only besuccessfully executed when the APS capability is enabled on the RNC.

2. FORMAT

LOCKOUT:RNC a, GICC b, ATM c



b = GICC slot number (3,4,19,20).

c = ATM port number (1-2, the ATM ports are number 1 and 2 from the bottomup).

4. SYSTEM RESPONSE





5. REFERENCES

IM/OM References:

Input MessagesNone

Output MessagesGET-RNC-GICCLOCKOUT-RNC-GICC


Issue 28 LOCKOUT:RNC-GICC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksLOCKOUT:RNC GICC August 2005

Other References:



LOCKOUT:RNC-GICC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP RNC

ID............. OP:RNCRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Requests the status of a Radio Network Controller (RNC).

2. FORMAT

OP:RNC [a]


a = RNC number (1-15). If no RNC number is specified, the status of each RNCwill be printed.

4. SYSTEM RESPONSE

?E = Particular information entered is invalid:

— RNC number out of range.

— RNC value must be numeric.

— Single RNC number expected.

— No equipped RNC.

NG = No Good. The RNC Feature is not active.

PF = Printout Follows. Request has been processed. Output message(s) willfollow.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesOP-RNC

Other References:None.


Issue 28 OP:RNC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP RNC August 2005



OP:RNC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP:RNCDB RNC

ID............. OP:RNCDBRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

This command requests a list of all Radio Network Controller (RNC) application databasebackup files for a specified RNC or all.

2. FORMAT

OP:RNCDB, RNC [a ALL]



4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a OP-RNCDB output message. If the PF isfollowed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the OP-RNCDB command willbe delayed.









Issue 28 OP:RNCDB-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP:RNCDB RNC August 2005

5. REFERENCES

IM/OM References:

Input MessagesBKUP:RNCDBCOPY:RNCDBDELBKUP:RNCDB


Other References:



OP:RNCDB-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP RNC TRKGRP

ID............. OP:RNC-TRKGRPRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Request the status Packet Pipe (PP) trunk group or member, homed on a Radio NetworkController (RNC).

2. FORMAT

OP:RNC a, TRKGRP b[, {c MEMBER d}]



b = Packet Pipe Trunk Group (TRKGRP) number (1-2000).

c = State of the requested trunk group:

ALL — All states.ACTIVE — Active.BLOCKED — Remotely blocked.EQP — Equipped (default).OOS — Out of service.UNEQP — Unequipped.

d = Packet Pipe trunk member number (1-96).

4. SYSTEM RESPONSE




— TRKGRP number out of range for RNC Packet Pipe.

— Single numeric TRKGRP number expected.

— Member number out of range for RNC Packet Pipe.

— Single member number expected.

— Unknown TRKGRP state.

— Single state identifier expected.

— Member number not expected when state specified.

IP = In Progress. Request is being processed. Output message(s) will follow.

NG = No Good. The RNC Feature is not active.


Issue 28 OP:RNC-TRKGRP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP RNC TRKGRP August 2005


RL = Retry Later. Unable to execute command for provided reason.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesOP-RNC-TRKGRP



OP:RNC-TRKGRP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RESET:RNC TPU

ID............. RESET:RNC-TPURELEASE ....... 24.0 and laterTYPE .......... Input



Reset of the Blade Packet Control Function (BPCF) slot without halting thedisk may cause disk damage!

1. PURPOSE


Reset the specified Traffic Processing Unit (TPU) cards on the specified TPU and RNC.

Format 1: Reset the specified Gateway Intelligent Carrier Card (GICC) on the specifiedTPU and RNC. A software reset will be performed on the specified unit.

Format 2: Reset the specified Common Intelligent Carrier Card (CICC) on the specifiedTPU and RNC. A software reset will be performed on the specified unit.

Format 3: Reset the specified TPU cards on the specified TPU slot on the specified TPUand RNC. A hardware reset will be performed on the specified slot.

Format 4: Reset the specified BPCF card on the specified TPU and RNC. A software resetwill be performed on the specified unit.

2. FORMAT

[1] RESET:RNC a, TPU b, GICC c

[2] RESET:RNC a, TPU b, CICC d

[3] RESET:RNC a, TPU b, SLOT e

[4] RESET:RNC a, TPU b, BPCF f








Issue 28 RESET:RNC-TPU-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRESET:RNC TPU August 2005

e = Slot number (3-20).

f = BPCF card slot number (5,6,17,18).


4. SYSTEM RESPONSE






5. REFERENCES

IM/OM References:

Input MessagesNone

Output MessagesRESET-RNC-TPU

Other References:



RESET:RNC-TPU-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RMV:AP-RNCDBMS

ID............. RMV:AP-RNCDBMSRELEASE ....... 24.0 and laterTYPE .......... Input


**WARNING**If UCL is specified, the Radio Network Controller Database Update Manager(RNCDBMS) application will be removed from service even if it cannot bemade ACTIVE on the mate Application Processor (AP). This could result ina complete loss of the ability to complete new calls.

1. PURPOSE

Removes the Application Processor (AP) Radio Network Controller Database UpdateManager (RNCDBMS) application from service.

On successful completion of this command the RNCDBMS application will be in the OOS-MANUAL state. An attempt to switchover the RNCDBMS application running in an activestate will be made for both conditional or unconditional removes. If RNCDBMS cannot beswitched over to the mate AP and the UCL parameter is not specified, this command willfail. If UCL is specified, the RNCDBMS application will be removed from service even ifthe RNCDBMS cannot be switched over to the mate AP.

2. FORMAT

RMV:AP a,RNCDBMS [;UCL]


a = AP number.

UCL = Unconditional remove request.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RMV-AP-RNCDBMS output message. Ifthe PF is followed by the word QUEUED, the command was queued toallow a running command to complete. Therefore, the RMV-AP-RNCDBMScommand will be delayed.





Issue 28 RMV:AP-RNCDBMS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRMV:AP-RNCDBMS August 2005





5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RST:AP-RNCDBMS (Flexent EMS/AP)SWITCHOVER:RNCDBMS (Flexent EMS/AP)

Output MessagesOP-AP-STATUSRMV-AP-RNCDBMSRST-AP-RNCDBMSSWITCHOVER-RNCDBMS

Other References:



RMV:AP-RNCDBMS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RMV:AP-RNCM

ID............. RMV:AP-RNCMRELEASE ....... 24.0 and laterTYPE .......... Input


**WARNING**If UCL is specified, the Radio Network Controller Manager (RNCM)application will be removed from service even if it cannot be made ACTIVEon the mate Application Processor (AP). This could result in a complete lossof the ability to complete new calls.

1. PURPOSE

Removes the Application Processor (AP) Radio Network Controller Manager (RNCM)application from service.

On successful completion of this command the RNCM application will be in the OOS-MANUAL state. An attempt to switchover the RNCM application running in an active statewill be made for both conditional or unconditional removes. If RNCM cannot be switchedover to the mate AP and the UCL parameter is not specified, this command will fail. If UCLis specified, the RNCM application will be removed from service even if the RNCM cannotbe switched over to the mate AP.

2. FORMAT

RMV:AP a,RNCM b [;UCL]


a = AP number.

b = RNCM number.


4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RMV-AP-RNCM output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RMV-AP-RNCM commandwill be delayed.





Issue 28 RMV:AP-RNCM-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRMV:AP-RNCM August 2005





5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RST:AP-RNCM (Flexent EMS/AP)SWITCHOVER:RNCM (Flexent EMS/AP)

Output MessagesOP-AP-STATUSRMV-AP-RNCMRST-AP-RNCMSWITCHOVER-RNCM

Other References:



RMV:AP-RNCM-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RMV RNC TRKGRP

ID............. RMV:RNC-TRKGRPRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Removes a Packet Pipe (PP) trunk, homed on a Radio Network Controller (RNC), fromservice. This input message permits the technician to use the RNC trunk representation toidentify the trunk for removal.

The system response will vary depending upon whether the removal request wasconditional or unconditional.

• For Conditional Removal. If the removal of the packet pipe would cause the CodeDivision Multiple Access (CDMA) Out Of Service (OOS) threshold to be exceeded, therequest will fail. If OOS limits would not be exceeded, new call attempts will beblocked on the CDMA Cluster Controller (CCC) served by this packet pipe. If anyexisting calls on the packet pipe remain after five minutes have elapsed, the packet pipewill be unblocked and the remove will fail.

• For Unconditional Removal. If the unconditional option is specified, OOS limits are notchecked. New call attempts will be blocked on the CCC served by this packet pipe, andall calls present on the packet pipe will be given five minutes to terminate.

2. FORMAT

RMV:RNC a, TRKGRP b, MEMBER c[;UCL]




c = Packet Pipe trunk member number (1-96).

UCL = Unconditionally remove the trunk from service. OOS limits are ignored andcalls will be terminated after a five-minute campon interval.

4. SYSTEM RESPONSE




— TRKGRP number out of range be for RNC Packet Pipe.

— Single numeric TRKGRP number expected.

— Member number out of range for RNC Packet Pipe.

— Single member number expected.

— UCL option expected.


Issue 28 RMV:RNC-TRKGRP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRMV RNC TRKGRP August 2005


NG = No Good. Necessary condition for execution of request not met.

NG = No Good. RNC Feature is not active.



5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesRMV-RNC-TRKGRP



RMV:RNC-TRKGRP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RST AP-RNCDBMS

ID............. RST:AP-RNCDBMSRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Restores the Application Processor (AP) Radio Network Controller Database UpdateManager (RNCDBMS) application to service.

On successful completion of this command, the RNCDBMS managed object will be in theACTIVE or STBY maintenance state depending on the state of the application on the mateAP. If the application is ACTIVE on the mate AP, it will be brought to the STBY state onthis AP. If the application is not ACTIVE on the mate AP, the application will be broughtto the ACTIVE state on this AP.

2. FORMAT

RST:AP a, RNCDBMS


a = AP number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RST-AP-RNCDBMS output message. Ifthe PF is followed by the word QUEUED, the command was queued toallow a running command to complete. Therefore, the RST-AP-RNCDBMScommand will be delayed.









Issue 28 RST:AP-RNCDBMS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRST AP-RNCDBMS August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RMV:AP-RNCDBMS (Flexent EMS/AP)RST-AP-RNCDBMS (Flexent EMS/AP)SWITCHOVER-RNCDBMS (Flexent EMS/AP)


Other References:



RST:AP-RNCDBMS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RST AP-RNCM

ID............. RST:AP-RNCMRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Restores the Application Processor (AP) Radio Network Controller Manager (RNCM)application to service.

On successful completion of this command, the specified RNCM managed object will be inthe ACTIVE state.

2. FORMAT

RST:AP a, RNCM b


a = AP number.

b = RNCM number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RST-AP-RNCM output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RST-AP-RNCM commandwill be delayed.









Issue 28 RST:AP-RNCM-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRST AP-RNCM August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RMV:AP-RNCM (Flexent EMS/AP)RST-AP-RNCM (Flexent EMS/AP)SWITCHOVER-RNCM (Flexent EMS/AP)


Other References:



RST:AP-RNCM-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RST RNC TRKGRP

ID............. RST:RNC-TRKGRPRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Restores a Packet Pipe (PP) trunk, homed on a Radio Network Controller (RNC), intoservice. This input message permits the technician to use the RNC trunk representation toidentify the trunk for restoral.

2. FORMAT

RST:RNC a, TRKGRP b, MEMBER c




c = Packet Pipe trunk member number (1-96).

4. SYSTEM RESPONSE

?E = Error. Particular information entered is invalid:

— Member number out of range for RNC Packet Pipe

— RNC number out of range

— Single MEMBER number expected

— Single numeric TRKGRP number expected

— Single RNC Number expected

— TRKGRP number must be in 1 .. x for RNC Packet Pipe


NG = No Good. One of the following:

— Bad TM action: x

— Necessary condition for execution of request not met

— Optional parameter <string> is not valid for RNC

— RNC Feature is not active




Issue 28 RST:RNC-TRKGRP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRST RNC TRKGRP August 2005

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesRST-RNC-TRKGRP



RST:RNC-TRKGRP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 SHUTDOWN:RNC TPU

ID............. SHUTDOWN:RNC-TPURELEASE ....... 24.0 and laterTYPE .......... Input



1. PURPOSE


Shutdown the specified Traffic Processing Unit (TPU) cards on the specified TPU andRNC.

Format 1: Shutdown the specified Gateway Intelligent Carrier Card (GICC) on thespecified TPU and RNC.

Format 2: Shutdown the specified Common Intelligent Carrier Card (CICC) on thespecified TPU and RNC.

Format 3: Shutdown the specified Asynchronous Transfer Mode (ATM) port on thespecified GICC, TPU and RNC.

Format 4: Shutdown the specified Blade Packet Control Function (BPCF) card on thespecified TPU and RNC.

Format 5: Shutdown the Internet Protocol Base Transceiver Station Gateway (IPBTSGW)on the specified RNC.

NOTE: Shutdown differs from lock in that it allows active calls to be drained beforedoing the lock.

The SHUTDOWN command will transition the TPU card from UNLOCKED toSHUTTINGDOWN state, drain the calls, and eventually transition the TPU card to LOCKEDstate.

2. FORMAT

[1] SHUTDOWN:RNC a, TPU b, GICC c

[2] SHUTDOWN:RNC a, TPU b, CICC d

[3] SHUTDOWN:RNC a, TPU b, GICC c, ATM e

[4] SHUTDOWN:RNC a, TPU b, BPCF f

[5] SHUTDOWN:RNC a, TPU b, GICC c, IPBTSGW


Issue 28 SHUTDOWN:RNC-TPU-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSHUTDOWN:RNC TPU August 2005




c = GICC slot number (3, 4, 19, 20).


NOTE: Slots 5, 6, 17, and 18 are multipurpose slots, which may or may notbe provisioned for CICC.


f = BPCF card slot number (5, 6, 17, 18).

NOTE: Slots 5, 6, 17, and 18 are multipurpose slots, which may or may notbe provisioned for BPCF.

4. SYSTEM RESPONSE






5. REFERENCES

IM/OM References:

Input MessagesNone

Output MessagesSHUTDOWN-RNC-TPU

Other References:



SHUTDOWN:RNC-TPU-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 SWITCH:RNC

ID............. SWITCH:RNCRELEASE ....... 25.0 and laterTYPE .......... Input



1. PURPOSE


Switch the A8A9 and A10A11 IP Gateways for the specified RNC.

2. FORMAT

[1] SWITCH:RNC a, A8A9

[2] SWITCH:RNC a, A10A11



4. SYSTEM RESPONSE






5. REFERENCES

IM/OM References:

Input MessagesNone

Output MessagesSWITCH-RNC


Issue 28 SWITCH:RNC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSWITCH:RNC August 2005

Other References:



SWITCH:RNC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 SWITCH:TOMATE RNC TPU

ID............. SWITCH:TOMATE-RNC-TPU




1. PURPOSE


To request a manual or forced protection switch from the specified 5ESS Gateway(5EGW) to its designated Automatic Protection Switching (APS) mate. This command canonly be successfully executed when the APS capability is enabled on the RNC.

2. FORMAT

SWITCH:TOMATE, RNC a, TPU b, GICC c, ATM d [FORCE]



b = Traffic Processing Unit (TPU) shelf number (1-2).

c = Gateway Intelligent Carrier Card (GICC) slot number (3,4,19,20).

d = Asynchronous Transfer Mode (ATM) port number (1-2).

4. SYSTEM RESPONSE





5. REFERENCES

IM/OM References:

Input MessagesNone


Issue 28 SWITCH:TOMATE-RNC-TPU-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSWITCH:TOMATE RNC TPU August 2005

Output MessagesGET-RNC-GICCSWITCH-TOMATE-RNC-TPU

Other References:



SWITCH:TOMATE-RNC-TPU-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 SWITCHOVER RNCDBMS

ID............. SWITCHOVER:RNCDBMSRELEASE ....... 24.0 and laterTYPE .......... Input


**WARNING**An unconditional switchover may result in the loss of OOS MANUALremoved state information on trunks. Recovery operations in progress at thetime of the UCL switchover may be delayed.

1. PURPOSE

Switches over an ACTIVE Application Processor (AP) Radio Network Controller DatabaseUpdate Manager (RNCDBMS) application to its standby instance on the mate AP.

On successful completion of this command the state of the RNCDBMS application will beswitched from ACTIVE on this AP, STBY on the mate AP to STBY on this AP and ACTIVEon the mate AP. All stable calls will be preserved.

2. FORMAT

SWITCHOVER:RNCDBMS [;UCL]


UCL = Unconditional request.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a SWITCHOVER-RNCDBMS output message.If the PF is followed by the word QUEUED, the command was queued toallow a running command to complete. Therefore, the SWITCHOVER-RNCDBMS command will be delayed.







Issue 28 SWITCHOVER:RNCDBMS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSWITCHOVER RNCDBMS August 2005



5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RMV:AP-RNCDBMS (Flexent EMS/AP)RST:AP-RNCDBMS (Flexent EMS/AP)SWITCHOVER-RNCDBMS (Flexent EMS/AP)


Other References:



SWITCHOVER:RNCDBMS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 SWITCHOVER RNCM

ID............. SWITCHOVER:RNCMRELEASE ....... 24.0 and laterTYPE .......... Input



1. PURPOSE

Switches over an ACTIVE Application Processor (AP) Radio Network Controller Manager(RNCM) application to its STBY instance on the mate Application Processor (AP).

On successful completion of this command the state of the RNCM application will beswitched from ACTIVE on this AP, STBY on the mate AP to STBY on this AP and ACTIVEon the mate AP. All stable calls will be preserved.

2. FORMAT

SWITCHOVER:RNCM a [;UCL]


a = Radio Network Controller Manager (RNCM) number.


4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a SWITCHOVER-RNCM output message. Ifthe PF is followed by the word QUEUED, the command was queued toallow a running command to complete. Therefore, the SWITCHOVER-RNCM command will be delayed.







Issue 28 SWITCHOVER:RNCM-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSWITCHOVER RNCM August 2005



5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RMV:AP-RNCM (Flexent EMS/AP)RST:AP-RNCM (Flexent EMS/AP)SWITCHOVER-RNCM (Flexent EMS/AP)


Other References:



SWITCHOVER:RNCM-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 TST:BTS RNC

ID............. TST:BTS-RNCRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE


Perform Asynchronous Transfer Mode (ATM) loop back test to Base Transceiver System(BTS) on the specified trunk resource(s) on the specified ATM processor, GatewayIntelligent Carrier Card (GICC), Traffic Processing Unit (TPU) and RNC.

Although this command goes from the RNC "toward" the BTS, the loop back actuallyoccurs at the first PacketStar Access Gateway (PSAX) that the RNC’s ATM link terminatesat. Thus, the PSAX performs the loop back to the RNC and the loop back does not go allthe way to the BTS.

2. FORMAT

TST:BTS, RNC a, TPU b, GICC c, ATM d, TG e, [TM f]






e = Trunk Group (TG) number (1-2000).

f = Trunk Group Member (TM) number (1-96). Without the TM parameter thecommand will be issued on all (TG, TM) Permanent Virtual Circuit (PVC)pairs that match the specified TG number.

4. SYSTEM RESPONSE







Issue 28 TST:BTS-RNC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksTST:BTS RNC August 2005

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesTST-BTS-RNC

Other References:



TST:BTS-RNC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 TST:PSU RNC

ID............. TST:PSU-RNCRELEASE ....... 23.0 and laterTYPE .......... Input

1. PURPOSE


Perform Asynchronous Transfer Mode (ATM) loop back test to Packet Switching Unit(PSU) on the specified network resource(s); on the specified ATM processor, GatewayIntelligent Carrier Card (GICC), Traffic Processing Unit (TPU), and RNC.

If Virtual Channel Connection (VCC) or Virtual Path Connection (VPC) is not provided aspart of the command, provisioned outgoing connection type will be used for intra-subnetloopbacks. All inter-subnet loopbacks utilize VCC connectivity. A Virtual Path Identifier(VPI) must be provisioned for the local subnet when requesting an intra-subnet VCCloopback. A VPI must be provisioned for the remote subnet when requesting an inter-subnet loopback.

If the Automatic Protection Switching (APS) capability is enabled on the RNC, the 5ESS

Gateway (GW) must be the active 5ESS GW in the mated pair for the test to pass. Pleasebrowse to the TPU Graphical User Interface (GUI) APS status page (or use the GET:RNCa,GICC b, 5EGW, INFO CLI input command) to determine if the port to be tested is theactive port in the pair. You may execute the TPU GUI Network Elements (NE) status pagebased ATM port SWITCH TO MATE command (or the SWITCH:TOMATE CLI inputcommand) to activate the port, if necessary. In addition, if the operational mode for thatport (see the GUI APS status page or CLI GET:RNC a,GICC b, 5EGW, INFO outputmessage) is unidirectional, the ATM switch Optical Carrier Level 3 (OC3) port that isphysically connected to the port under test must be also be active for the test to pass.Please refer to your ATM switch manual to determine which OC3 port on the ATM switchis active.

2. FORMAT

TST:PSU, RNC a, TPU b, GICC c, ATM d, FARCA {e ALL} [,SUBNET f][,VCC VPC] [;ENH]






e = Far End Community Address (FARCA) (1-254).

ALL = The command will be issued on all FARCA (1-254) excluding the Near EndCommunity Address (NEARCA).


Issue 28 TST:PSU-RNC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksTST:PSU RNC August 2005

VCC = VCC connection type.

VPC = VPC connection type.

f = Far End Subnet (0-3).

ENH = Proprietary enhanced option. An enhanced loop back test is the same as astandard loop back test except that the far end inserts their actual VPI andVirtual Channel Identifier (VCI) into the looped back message therebyallowing the user to verify exactly who it is they are communicating with.

4. SYSTEM RESPONSE






5. REFERENCES

IM/OM References:

Input MessagesSWITCH:TOMATE-RNC-TPU

Output MessagesTST-PSU-RNC

Other References:



TST:PSU-RNC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 UNLOCK:RNC TPU

ID............. UNLOCK:RNC-TPURELEASE ....... 24.0 and laterTYPE .......... Input


**WARNING**Command may affect service.

1. PURPOSE


Unlock the specified Traffic Processing Unit (TPU) cards on the specified TPU and RNC.

Format 1: Unlock the specified Gateway Intelligent Carrier Card (GICC) on the specifiedTPU and RNC.

Format 2: Unlock the specified Common Intelligent Carrier Card (CICC) on the specifiedTPU and RNC.

Format 3: Unlock the specified GICC Asynchronous Transfer Mode (ATM) processor onthe specified TPU and RNC.

Format 4: Unlock the specified Blade Packet Control Function (BPCF) card on thespecified TPU and RNC.

Format 5: Unlocks the Internet Protocol Base Transceiver Station Gateway (IPBTSGW) onthe specified RNC.

2. FORMAT

[1] UNLOCK:RNC a, TPU b, GICC c

[2] UNLOCK:RNC a, TPU b, CICC d

[3] UNLOCK:RNC a, TPU b, GICC c, ATM e

[4] UNLOCK:RNC a, TPU b, BPCF f

[5] UNLOCK:RNC a, TPU b, GICC c, IPBTSGW




c = GICC slot number (3, 4, 19, 20).


Issue 28 UNLOCK:RNC-TPU-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksUNLOCK:RNC TPU August 2005


NOTE: Slots 5, 6, 17, and 18 are multipurpose slots, which may or may notbe provisioned for CICC.


f = BPCF card slot number (5, 6, 17, 18)

NOTE: Slots 5, 6, 17, and 18 are multipurpose slots, which may or may notbe provisioned for BPCF.

4. SYSTEM RESPONSE






5. REFERENCES

IM/OM References:

Input MessagesNone

Output MessagesUNLOCK-RNC-TPU

Other References:



UNLOCK:RNC-TPU-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW BTS AUD

ID............. ALW:BTS-AUDRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Format 1: Enable the execution of the audit of the maintenance state information of allCell components.

Format 2: Enable the execution of the audit of the configuration information associatewith all Cell components.

NOTE: This command may be entered only from the Flexent Element ManagementSystem (EMS).

2. FORMAT

[1] ALW:BTS a, AUD MAINT

[2] ALW:BTS a, AUD CONFIG


a = Base Transceiver System (BTS) number (1-600).

4. SYSTEM RESPONSE

IP = In Progress. Request has been sent to the cell site. Output message(s) willfollow.

NA = No Acknowledgement.


PF = Printout Follows. Request has been executed. Followed by a ALW-BTS-AUD output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesINH:BTS-AUD

Output MessagesALW-BTS-AUD



Issue 28 ALW:BTS-AUD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW BTS AUD August 2005



ALW:BTS-AUD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW TP AUD

ID............. ALW:TP-AUDRELEASE ....... 23.0 and laterTYPE .......... Input

1. PURPOSE

Enable the execution of the audit of the maintenance state information of Traffic Processor(TP).


2. FORMAT

ALW:TP a, AUD MAINT


a = TP number (1-448).

4. SYSTEM RESPONSE

IP = In Progress. Request has been sent to the AP. Output message(s) willfollow.



PF = Printout Follows. Request has been executed. Followed by a ALW-TP-AUD output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesINH:TP-AUD

Output MessagesALW-TP-AUDINH-TP-AUD



Issue 28 ALW:TP-AUD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW TP AUD August 2005



ALW:TP-AUD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COMMIT AP

ID............. COMMIT:APRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Commits the Application Processor (AP) to the version of platform software currentlyrunning.

NOTE: If the Application Processor (AP), is a 1xEV-DO AP, then the command can onlybe entered from the Element Management System (EMS).

Format 1: This command commits the AP to the version of platform software currentlyrunning on the AP. A commit removes the "backout" version of AP platformsoftware if it exists. A commit also removes the "new" version of AP platformsoftware if a new version (different from the currently running version) of APplatform software exists.

COMMIT is done only as part of a software update or generic retrofit procedure,after the new software has stabilized on the system for some time interval. Seethe Application Processor Cluster Operations, Administration, andMaintenance Guide to follow the software update or generic retrofit procedure.

The COMMIT will fail if the selected version of AP platform software differsfrom the currently running version of AP platform software.

This command can be run only from the EMS.

Format 2: This is a 1xEV-DO message. Commits the current sets of software versions sothat they cannot be backed out or removed.

2. FORMAT

[1] COMMIT:AP a, SOFTWARE b

[2] COMMIT:AP a, SOFTWARE


a = AP number (1-278).

b = Software type: platform is the only type of software supported.

4. SYSTEM RESPONSE

IP = In Progress.



PF = Printout Follows. Followed by a COMMIT-AP output message. If the PF isfollowed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the COMMIT:AP command willbe delayed.


Issue 28 COMMIT:AP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOMMIT AP August 2005

RL = Retry Later. One of the following reasons:



— Managed object TYPE NUMBER is busy.

The managed object indicated by TYPE and NUMBER already has acommand running or queued, and it may only have one activecommand associated with it at a time.



5. REFERENCES

IM/OM References:

Input MessagesOP:AP-VERSIONSELECT:AP

Output MessagesCOMMIT-APOP-AP-VERSIONSELECT-AP

Other References:

401-710-101 Application Processor Cluster (APC) Operations, Administration, and Maintenance(OA&M)

401-710-110 Element Management System (EMS) Users Guide


COMMIT:AP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DEL BTS GENERIC

ID............. DEL:BTS-GENERICRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Deletes the requested generic from a Base Transceiver System (BTS).


2. FORMAT

DEL:BTS a[, CDM b], GENERIC c


a = BTS number (1-600).

b = Code Division Multiple Access (CDMA) Digital Module (CDM)number (1-16).

c = Name of the Generic Description File (GDF). A string of 12 characters.

For Flexent Modular Cell 4.0, the generic name should follow the namingconvention: For example: F2000DDAA.60

1st character — Software type:

F — Functional software (Cell and Radio Cluster Server [RCS]).

2nd-3rd character — Release level of the load.

4th character — Base/Package release number:

0 — Base release.1 — Package release.

5th character — Incremented for maintenance release.

6th character — Technology type:

E — 1xEV-DO

7th character — Cell type:

A — Flexent Microcell.B — Flexent Modular Cell 4.0.D — Flexent Modular & CDBS Cells.

8th character — Type of load:

E — Experimental loads.F — FOA loads.G — GA loads.P — Private loads.

Other names are used for internal alpha, beta, etc loads.


Issue 28 DEL:BTS-GENERIC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDEL BTS GENERIC August 2005

9th character — Radio Cluster Server (RCS) to cell compatibility indicator.Always D.

10th character — Decimal point.

11th-12th character — Load sequence number.

4. SYSTEM RESPONSE



NG = No Good. Necessary conditions for message execution (including apossibly unequipped cell site) were not met.

PF = Printout Follows. Request has been executed. Followed by a OP-BTS-GENERIC output message.

RL = Retry Later. Data links to cell site are down.

5. REFERENCES

IM/OM References:

Input MessagesOP:BTS-GENERICSEND:BTS-GENERICSTOP:SEND-BTS-GENERIC

Output MessagesDEL-BTS-GENERIC



DEL:BTS-GENERIC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN:BTS ASMB TXAMP

ID............. DGN:BTS-ASMB-TXAMPRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Diagnose a Transmit Amplifier (TXAMP) for a specified cabinet of a specific BaseTransceiver System (BTS).

NOTE: This command is not supported in a mixed cell mode.

NOTE: This command may only be entered from the Flexent Element ManagementSystem (EMS), but for 1xEV-DO it may also be entered from the ApplicationProcessor (AP) Command Line Interface (CLI).

2. FORMAT

DGN:BTS a, ASMB b, TXAMP c



b = Assemblage (cabinet) number (1-4).

c = TXAMP number (1-36).

4. SYSTEM RESPONSE




PF = Printout Follows. Followed by a DGN-BTS-ASMB-TXAMP output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesDGN-BTS-ASMB-TXAMP



Issue 28 DGN:BTS-ASMB-TXAMP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN:BTS ASMB TXAMP August 2005



DGN:BTS-ASMB-TXAMP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN BTS CDM

ID............. DGN:BTS-CDMRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Diagnoses a Base Transceiver System (BTS) for a particular unit.


2. FORMAT

[1] DGN:BTS a, CDM b, CBR c

[2] DGN:BTS a, CDM b, CRC

[3] DGN:BTS a, CDM b, EVM d




CBR = CDMA Baseband Radio (CBR).

c = CBR number (1-3).

CRC = CDMA Radio Controller (CRC).

d = 1xEV-DO Modem (EVM) number (0-11).

4. SYSTEM RESPONSE




PF = Printout Follows. Followed by a DGN-BTS-CDM output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.


Issue 28 DGN:BTS-CDM-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN BTS CDM August 2005

Output MessagesDGN-BTS-CDM



DGN:BTS-CDM-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN BTS-TFU

ID............. DGN:BTS-TFURELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Diagnoses a Base Transceiver System (BTS) for a specified Time Frequency Unit (TFU).


NOTE: This command is not supported on the active TFU.


2. FORMAT

DGN:BTS a, TFU b



b = TFU number (1-8).

4. SYSTEM RESPONSE




PF = Printout Follows. Followed by a DGN-BTS-TFU output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesDGN-BTS-TFU



Issue 28 DGN:BTS-TFU-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN BTS-TFU August 2005



DGN:BTS-TFU-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EXC:BTS FLUS

ID............. EXC:BTS-FLUSRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Initiate a Forward Link User Simulation (FLUS) on a given carrier.


2. FORMAT

EXC:BTS a, FLUS CDM b, SECTOR c, USER d, TT e, CC f, LOC g



b = Code Division Multiple Access (CDMA) Digital Module (CDM) number (1-14).

c = Sector number within the CDM (1-3).

d = FLUS user number (1-25).

e = FLUS Traffic Type (TT):

1 — A high traffic intensity user such as a ftp session.2 — A medium traffic such as a HTTP application session.3 — A low traffic such as a Wireless Application Protocol (WAP) session.

f = Channel Condition (CC):

1 — A model derived from the International Telecommunication Union(ITU) pedestrian A model with one antenna.

2 — A model derived from the ITU pedestrian A model with two antennas.3 — A model derived from the ITU vehicular B model with one antenna.4 — A model derived from the ITU vehicular B Model with two antennas.

g = Location:

1 — A 25 percentile for average served rate.2 — A 50 percentile for average served rate.3 — A 80 percentile for average served rate.

4. SYSTEM RESPONSE





Issue 28 EXC:BTS-FLUS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEXC:BTS FLUS August 2005

PF = Printout Follows. Followed by a EXC-BTS-FLUS output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesEXC-BTS-FLUS



EXC:BTS-FLUS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 FLUS CELL

ID............. FLUS:CELLRELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE

Requests setup and control of Forward Link User Simulation (FLUS) at a specified cell.

NOTE: This command only applies for converged cells supporting 1x Evolution - DataOnly (1xEV-DO) carrier.

Format 1 Requests initialization of FLUS at the cell.

Format 2 Sets FLUS parameters for a session.

Format 3 Requests that a FLUS session be stopped.

Use an initial request before entering any secondary request. As many secondary requestsas needed can be used to adjust the FLUS activity level. After a secondary request hasbeen entered, the FLUS supervisor will remain active until terminated by a STOP:FLUS-CELL input command.

2. FORMAT

[1] FLUS:CELL a; START

[2] FLUS:CELL a, SECTOR b, CARRIER c, USER d, TT e, CC f, LOC g

[3] FLUS:CELL a [, CARRIER c [, USER d] ]; STOP


a = Cell site number (1-600):

• A single cell site.• A list of cell sites separated by commas and enclosed in parentheses.

b = Sector number (0-6).

c = Carrier number (1-18). For Format 3, if user is omitted, all users on thespecified carrier are terminated. If carrier and user are omitted, the entireFLUS session (all carriers/users) are terminated.

d = Simulated user number (1-25) for the FLUS session.

e = FLUS user traffic type number:

1 — High traffic intensity user such as a File Transfer Protocol (FTP) user.2 — Medium traffic intensity user such as a Hyper Text Transfer Protocol

(HTTP) user.3 — Low traffic intensity user such as a Wireless Application Protocol

(WAP) user.

f = FLUS user channel condition type number:

1 — A model derived from the ITU Pedestrian "A" model with oneantenna.


Issue 28 FLUS:CELL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksFLUS CELL August 2005

2 — A model derived from the ITU Pedestrian "A" model with twoantennas.

3 — A model derived from the ITU Vehicular model with one antenna.4 — A model derived from the ITU Vehicular model with two antennas.

g = FLUS user location type number:

1 — At 25 percentile for average served rate.2 — At 50 percentile for average served rate.3 — At 80 percentile for average served rate.

4. SYSTEM RESPONSE


NG = No Good. Necessary conditions for message execution were not met.PF = Printout Follows. Request has been executed. Output message(s) will

follow.RL = Retry Later. Data links to cell site are down.

5. REFERENCES

IM/OM References:

Input MessagesOP:CELL-FLUSSTOP:FLUS-CELL

Output MessagesFLUS-CELLOP-CELLOP-CELL-FLUS



FLUS:CELL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 INH BTS AUD

ID............. INH:BTS-AUDRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Format 1: Inhibits an audit of the maintenance state information of all cell components.

Format 2: Inhibits an audit of the configuration information associate with all cellcomponents.


2. FORMAT

[1] INH:BTS a, AUD MAINT

[2] INH:BTS a, AUD CONFIG



4. SYSTEM RESPONSE




PF = Printout Follows. Request has been executed. Followed by an INH-BTS-AUD output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesALW:BTS-AUD

Output MessagesINH-BTS-AUD



Issue 28 INH:BTS-AUD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksINH BTS AUD August 2005



INH:BTS-AUD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 INH TP AUD

ID............. INH:TP-AUDRELEASE ....... 23.0 and laterTYPE .......... Input

1. PURPOSE

Inhibits the execution of the audit of the maintenance state information of Traffic Processor(TP).


2. FORMAT

INH:TP a, AUD MAINT



4. SYSTEM RESPONSE

IP = In Progress. Request has been sent to the TP. Output message(s) willfollow.



PF = Printout Follows. Request has been executed. Followed by a INH-TP-AUD output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesALW:TP-AUD

Output MessagesALW-TP-AUDINH-TP-AUD



Issue 28 INH:TP-AUD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksINH TP AUD August 2005



INH:TP-AUD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 INIT AP

ID............. INIT:APRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Initialize an Application Processor (AP) at a specific initialization level.


Format 1: INIT:AP-FULL takes several minutes longer than INIT:AP-APPL but is morethorough. Note that no output messages will be displayed when the INIT:APFULL or INIT:AP APPL commands run successfully.

The AP must be in the OOS MANUAL state before running either INIT:AP-APPL or INIT:AP-FULL. After the AP is initialized, it is returned to the OOSMANUAL state.

INIT:AP-FULL is primarily used for software update. Both forms of INIT:APmay be used for certain rare errors when a reinitialization is required to recoveran AP.

Format 2: This is a 1xEV-DO message. Initialize a specified unit. This will reboot theplatform software on the AP.

2. FORMAT

[1] INIT:AP a, b

[2] INIT:AP a



b = Initialization level:

APPL — Only the Flexent /AUTOPLEX software will be reinitialized.

FULL — The entire AP, including the operating system, will beimmediately rebooted.

4. SYSTEM RESPONSE

IP = In Progress.




Issue 28 INIT:AP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksINIT AP August 2005

PF = Printout Follows. Followed by a INIT-AP output message. If the PF isfollowed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the INIT:AP command will bedelayed.








5. REFERENCES

IM/OM References:

Input MessagesRMV:APRST:APSELECT:AP

Output MessagesINIT-APRMV-APRST-APSELECT-AP

Other References:



INIT:AP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 INIT BTS

ID............. INIT:BTSRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Initializes a Base Transceiver System (BTS) in Stable Clear (SC) mode.

NOTE: Only Stable Clear is supported. The 1xEV modular Cell does not supportTransient Clear (TC).


2. FORMAT

INIT:BTS a:SC



4. SYSTEM RESPONSE




PF = Printout Follows. Followed by an INIT-BTS output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesINIT-BTSREPT-EVDO-BTS



Issue 28 INIT:BTS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksINIT BTS August 2005



INIT:BTS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 INIT TP

ID............. INIT:TPRELEASE ....... 20.0 and laterTYPE .......... Input

1. PURPOSE

Initialize a Traffic Processor (TP).

NOTE: This command is not supported on the active TP.


2. FORMAT

INIT:TP a



4. SYSTEM RESPONSE




PF = Printout Follows. Followed by a INIT-TP output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesINIT-TP



Issue 28 INIT:TP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksINIT TP August 2005



INIT:TP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP:AP-IMSI-STATUS

ID............. OP:AP-IMSI-STATUSRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Report the status of an 1xEV-DO user session using the International Mobile StationIdentity (IMSI) and Application Processor (AP) ID. The operator can find out where themobile is located in the Network and whether it is Active or Dormant. Other sessionrelated information are also provided by this command.

NOTE: This command may only be entered from the Flexent Element ManagementSystem (EMS) Command Line Interface (CLI), for 1xEV-DO ApplicationProcessors (APs).

2. FORMAT

OP:AP a, IMSI b, STATUS


a = AP number.

b = 15 digit IMSI number.

4. SYSTEM RESPONSE

Command not supported on this AP = AP specified in command is a non 1xEV-DOAP.

COMMAND ACKNOWLEDGMENT TIMEOUT = Command Acknowledgement not received byEMS from the Controller.

IP = In Progress. Command Accepted and is in progress. Followed by a OP-AP-IMSI-STATUS output message.

NA = No Acknowledgement. Command is not accepted. Reason will follow.

NG = No Good. Necessary conditions for message execution were not met.

syntax error:[echoed input command], IMSI must be a 15 digit numeric value =Invalid IMSI in the command.

syntax error:[echoed input command] = Error in syntax of the message. The reasoncould be one of the following:

— Invalid AP in the command.

— Wrong use of reserved words in the command.

5. REFERENCES

IM/OM References:

Input MessagesNone.


Issue 28 OP:AP-IMSI-STATUS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP:AP-IMSI-STATUS August 2005

Output MessagesOP-AP-IMSI-STATUS

Other References:

401-614-102 CDMA2000 1xEV-DO Radio Networks Controller Application ProcessorOperations, Administration, and Maintenance (OA&M)


OP:AP-IMSI-STATUS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP AP OOS

ID............. OP:AP-OOSRELEASE ....... 21.0 and laterTYPE .......... Input

1. PURPOSE

This is a 1xEV-DO message. It reports all the Application Processor (AP) components thatare Out Of Service (OOS) for the system. (Either in Out of Service Manual [OOS-MAN] orOut of Service Fault [OOS-FLT] state.)

NOTE: When issued from AP Command Line Interface (CLI), this commands reports foronly the frame from which the AP CLI is invoked. The Output message displaysthe status of all OOS AP components for that particular frame. Output from theAP CLI version of this command is not displayed on the Read Only Printer(ROP).

NOTE: When issued from the Element Management System (EMS) CLI, this commandreports for all frames connected to the EMS. The output message displays thestatus of all OOS AP components for all frames connected to that OperationsMaintenance Platform (OMP).

2. FORMAT

OP:AP, OOS


See Purpose.

4. SYSTEM RESPONSE

IP = In Progress.


NG = No Good. Indicates that an invalid input parameter was specified or anunrecoverable software error occurred.

PF = Printout Follows.

5. REFERENCES

IM/OM References:

Input MessagesOP:OOSOP:BTS-OOSOP:TP-OOS


Issue 28 OP:AP-OOS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP AP OOS August 2005

Output MessagesOP-AP-OOSOP-BTS-OOSOP-OOSOP-TP-OOS



OP:AP-OOS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP AP-PROCCFG

ID............. OP:AP-PROCCFGRELEASE ....... 23.0 and laterTYPE .......... Input

1. PURPOSE

Report the status of all the 1xEV-DO processes in an Application Processor (AP). (Includesthe process groups FDBMS, HOC, HWSERVER, LOGSERVER, OHM, and TPAGENT).


2. FORMAT

OP:AP a, PROCCFG


a = AP number. Must be an odd number (1-277).

4. SYSTEM RESPONSE

IP = In Progress.



PF = Printout Follows. Followed by an OP-AP-PROCCFG output message.

RL = Retry Later. The following reason may be specified:



5. REFERENCES

IM/OM References:

Input MessagesSWITCHBACK:AP (Flexent EMS/AP)SWITCHOVER:AP (Flexent EMS/AP)

Output MessagesOP-AP-PROCCFGSWITCHBACK-APSWITCHOVER-AP



Issue 28 OP:AP-PROCCFG-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP AP-PROCCFG August 2005



OP:AP-PROCCFG-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP AP-VERSION

ID............. OP:AP-VERSIONRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Lists the version(s) of the software on the Application Processor (AP).


This command displays:

— The version of AP platform software running on the AP.

— The new version of AP platform software on the AP (if it exists), or the backout versionof AP platform software on the AP (if it exists). The new or backout version will existonly if a version has been installed since the last COMMIT:AP.

— The version of AP platform software selected on the AP (SELECT:AP).

— The available versions of Radio Cluster Server (RCS) software installed on the AP.

— The available versions of cell software installed on the AP.

— The selected version and running version for each RCS configured on the AP.

This is also a 1xEV-DO message. The 1xEV-DO AP provides application software versioninformation. This command displays the following application versions:

• The 1xEV-DO Controller (EVC) Application version(s) installed on the AP.

• Cell software versions installed on this AP.

• EVC Application versions, from the list of installed software, which are Selected (thenext to be activated), Current (running at the time the OP:AP-VERSION command isexecuted), and Committed.

2. FORMAT

OP:AP a, VERSION



4. SYSTEM RESPONSE

IP = In Progress.



PF = Printout Follows. Followed by an OP-AP-VERSION output message.


Issue 28 OP:AP-VERSION-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP AP-VERSION August 2005


— Maximum number of commands already running


5. REFERENCES

IM/OM References:

Input MessagesCOMMIT:APSELECT:AP


Other References:



OP:AP-VERSION-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP BTS

ID............. OP:BTSRELEASE ....... 23.0 and laterTYPE .......... Input

1. PURPOSE

Reports the status of all equipped components on a particular Base Transceiver System(BTS).

The response from this command lists the summary state of the BTS and the status of itsTime Frequency Unit (TFU), if applicable. Other than this information, it will only list theother elements from the BTS if they exhibit some abnormal characteristic (For example:alarm, out-of-service, and so forth.). To see the state of any particular element (Forexample: for the CDM, AMP, and so forth.), use the OP command for that particularelement.

NOTE: This command may only be entered from the Flexent Element ManagementSystem (EMS), but for 1x EV-DO it may also be entered from the ApplicationProcessor (AP) Command Line Interface (CLI).

2. FORMAT

OP:BTS a



4. SYSTEM RESPONSE




PF = Printout Follows. Followed by an OP-BTS output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.


Issue 28 OP:BTS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP BTS August 2005

Output MessagesOP-BTS



OP:BTS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP BTS ALARM

ID............. OP:BTS-ALARMRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Reports all active alarms on a particular Base Transceiver System (BTS).


2. FORMAT

OP:BTS a, ALARM



4. SYSTEM RESPONSE




PF = Printout Follows. Followed by an OP-BTS-ALARM output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesOP-BTS-ALARM



Issue 28 OP:BTS-ALARM-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP BTS ALARM August 2005



OP:BTS-ALARM-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP:BTS AMP

ID............. OP:BTS-AMPRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Reports the status of all equipped Amplifiers (AMPs) on a particular Base TransceiverSystem (BTS).


2. FORMAT

OP:BTS a, AMP



4. SYSTEM RESPONSE




PF = Printout Follows. Followed by a OP-BTS-AMP output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesOP:BTS-TXAMP

Output MessagesOP-BTS-AMP



Issue 28 OP:BTS-AMP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP:BTS AMP August 2005



OP:BTS-AMP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP:BTS ASMB TXAMP

ID............. OP:BTS-ASMB-TXAMPRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Reports the status of a specified Transmit Amplifier (TXAMP) in a given cabinet of aspecific Base Transceiver System (BTS).

NOTE: This command is supported in a mixed cell mode.


2. FORMAT

OP:BTS a, ASMB b, TXAMP c





4. SYSTEM RESPONSE




PF = Printout Follows. Followed by a OP-BTS-ASMB-TXAMP output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesOP-BTS-AMP

Output MessagesOP-BTS-ASMB-TXAMP



Issue 28 OP:BTS-ASMB-TXAMP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP:BTS ASMB TXAMP August 2005



OP:BTS-ASMB-TXAMP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP BTS CDM

ID............. OP:BTS-CDMRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Format 1: Reports the status of a specified Code Division Multiple Access (CDMA)Digital Module (CDM) on a particular Base Transceiver System (BTS).

Format 2: Reports the status of a specified CDMA Baseband Radio (CBR) on a particularCDM for a specified BTS.

Format 3: Reports the status of a specified CDMA Radio Controller (CRC) on a particularCDM for a specified BTS.

Format 4: Reports the status of a specified 1xEV-DO Modem (EVM) on a particular CDMfor a specified BTS.


2. FORMAT

[1] OP:BTS a, CDM b

[2] OP:BTS a, CDM b, CBR c

[3] OP:BTS a, CDM b, CRC

[4] OP:BTS a, CDM b, EVM d



b = CDM number (1-16).


d = EVM number (0-11).

4. SYSTEM RESPONSE




PF = Printout Follows. Followed by an OP-BTS-CDM output message.

RL = Retry Later.


Issue 28 OP:BTS-CDM-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP BTS CDM August 2005

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesOP-BTS-CDM



OP:BTS-CDM-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP BTS CDM INVENTORY

ID............. OP:BTS-CDM-INVENTRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Reports a cell sites equipment inventory.


2. FORMAT

OP:BTS a [, CDM b ], INVENTORY




4. SYSTEM RESPONSE




PF = Printout Follows. Followed by an OP-BTS-CDM-INVENT output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesOP-BTS-CDM-INVENT



Issue 28 OP:BTS-CDM-INVENT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP BTS CDM INVENTORY August 2005



OP:BTS-CDM-INVENT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP BTS FLUS

ID............. OP:BTS-FLUSRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Format 1: Reports the status of a single Forward Link User Simulation (FLUS) user on aspecified carrier in a given Base Transceiver System (BTS).

Format 2: Reports the status of all FLUS users on a specified carrier in a given BTS.


2. FORMAT

[1] OP:BTS a, FLUS CDM b, USER c

[2] OP:BTS a, FLUS CDM b



b = CDM number (1-14).

c = FLUS user number (1-25).

4. SYSTEM RESPONSE




PF = Printout Follows. Followed by an OP-BTS-FLUS output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesOP-BTS-FLUS



Issue 28 OP:BTS-FLUS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP BTS FLUS August 2005



OP:BTS-FLUS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP BTS GENERIC

ID............. OP:BTS-GENERICRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Requests a list of cell generics on a Base Transceiver System (BTS).

Format 1: If no generic is specified, the output lists all software generics present for thatmodular cell and indicates which, if any, is the active generic and which, ifany, is being downloaded to the respective Code Division Multiple Access(CDMA) Digital Module (CDM).

If a generic is specified, the output indicates if that generic is currently beingdownloaded. The output also includes a list of image files associated withthat generic and their states.

Format 2: If the BTS number, CDM number, nor generic is specified, the output lists theprovisioned CDM generic and cell type.


2. FORMAT

[1] OP:BTS a [, CDM b ], GENERIC [c]

[2] OP:BTS, GENERIC



b = CDMA Digital Module (CDM) number (1-16).










E — 1xEV-DO


Issue 28 OP:BTS-GENERIC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP BTS GENERIC August 2005









4. SYSTEM RESPONSE



NG = No Good. Information could not be retrieved, or other necessaryconditions for message execution were not met.

PF = Printout Follows. Request has been executed. Output message(s) willfollow.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesDEL:BTS-GENERICSEND:BTS-GENERICSTOP:SEND-BTS-GENERIC

Output MessagesOP-BTS-GENERIC



OP:BTS-GENERIC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP:BTS OOS

ID............. OP:BTS-OOSRELEASE ....... 21.0 and laterTYPE .......... Input

1. PURPOSE

This is a 1xEV-DO message. It reports all the Base Transceiver System (BTS) componentsthat are Out Of Service (OOS) for the system. (Either in Out of Service Manual [OOS-MAN] or Out of Service Fault [OOS-FLT] state.)

NOTE: This command is not supported from the Application Processor (AP) CommandLine Interface (CLI).

NOTE: When issued from the Element Management System (EMS) CLI, this commandreports for all frames connected to the EMS. The output message displays thestatus of all OOS BTS components for all frames connected to that OperationsMaintenance Platform (OMP).

2. FORMAT

OP:BTS, OOS


See Purpose.

4. SYSTEM RESPONSE

IP = In Progress.




5. REFERENCES

IM/OM References:

Input MessagesOP:AP-OOSOP:OOSOP:TP-OOS


Issue 28 OP:BTS-OOS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP:BTS OOS August 2005




OP:BTS-OOS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP BTS-TDU

ID............. OP:BTS-TDURELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Reports the status of a specified Test and Diagnostic Unit (TDU) in a given BaseTransceiver System (BTS).


NOTE: This command is not supported for BTSs of type Modular Cell 1, Modular Cell 2,or Modular Cell 3.


2. FORMAT

OP:BTS a, TDU b



b = TDU number (1-14).

4. SYSTEM RESPONSE




PF = Printout Follows. Followed by a OP-BTS-TDU output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesOP-BTS-TDU



Issue 28 OP:BTS-TDU-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP BTS-TDU August 2005



OP:BTS-TDU-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP BTS-TFU

ID............. OP:BTS-TFURELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Reports the status of a specified Time Frequency Unit (TFU) in a given Base TransceiverSystem (BTS).



2. FORMAT

OP:BTS a, TFU b




4. SYSTEM RESPONSE




PF = Printout Follows. Followed by a OP-BTS-TFU output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesOP-BTS-TFU



Issue 28 OP:BTS-TFU-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP BTS-TFU August 2005



OP:BTS-TFU-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP CELL FLUS

ID............. OP:CELL-FLUSRELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE

Requests the status of all Forward Link User Simulation (FLUS) users at a specified cell.


2. FORMAT

OP:CELL a, FLUS [, CARRIER b]


a = Cell site number (1-600).

b = Carrier number (1-18). If carrier is omitted, the status of all users on allcarriers are shown.

4. SYSTEM RESPONSE





Other responses have their standard meanings.

5. REFERENCES

IM/OM References:

Input MessagesFLUS:CELLSTOP:FLUS-CELL

Output MessagesFLUS-CELLOP-CELL-FLUS



Issue 28 OP:CELL-FLUS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP CELL FLUS August 2005



OP:CELL-FLUS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP OOS

ID............. OP:OOSRELEASE ....... 21.0 and laterTYPE .......... Input

1. PURPOSE

This is a 1xEV-DO message. Reports all the Application Processor (AP), Base TransceiverSystem (BTS) and Traffic Processor (TP) components that are Out Of Service (OOS) for thesystem. (Either in Out of Service Manual [OOS-MAN] or Out of Service Fault [OOS-FLT]state.)

NOTE: When issued from AP Command Line Interface (CLI), this command reports foronly the frame from which AP CLI is invoked. The Output message displays thestatus of all OOS AP and TP (but not BTS) components for that particular frame.Output from the AP CLI version of this command is not displayed on the ReadOnly Printer (ROP).

NOTE: When issued from the Element Management System (EMS) CLI, this commandreports all OOS AP, TP, and BTS elements for all frames connected to the EMS.

2. FORMAT

OP:OOS


See Purpose.

4. SYSTEM RESPONSE

IP = In Progress.




5. REFERENCES

IM/OM References:

Input MessagesOP:AP-OOSOP:BTS-OOSOP:TP-OOS



Issue 28 OP:OOS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP OOS August 2005



OP:OOS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP TP-ALARM

ID............. OP:TP-ALARMRELEASE ....... 20.0 and laterTYPE .......... Input

1. PURPOSE

Reports the alarms that have been generated autonomously for the specified TrafficProcessor (TP).


2. FORMAT

OP:TP a, ALARM



4. SYSTEM RESPONSE




PF = Printout Follows. Followed by an OP-TP-ALARM output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesOP-BTS-ALARMOP-TP-ALARMOP-TP-STATUSOP-TP-VERSION



Issue 28 OP:TP-ALARM-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP TP-ALARM August 2005



OP:TP-ALARM-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP TP OOS

ID............. OP:TP-OOSRELEASE ....... 21.0 and laterTYPE .......... Input

1. PURPOSE

This is a 1xEV-DO message. It reports all the Traffic Processor (TP) components that areOut Of Service (OOS) for the system. (Either in Out of Service Manual [OOS-MAN] or Outof Service Fault [OOS-FLT] state.)

NOTE: When issued from Application Processor (AP) Command Line Interface (CLI),this command reports for only the frame from which the AP CLI is invoked. TheOutput message displays the status of all OOS TP components for that particularframe. Output from the AP CLI version of this command is not displayed on theRead Only Printer (ROP).

NOTE: When issued from the Element Management System (EMS) CLI, this commandreports for all frames connected to the EMS. The output message displays thestatus of all OOS TP components for all frames connected to that OperationsMaintenance Platform (OMP).

2. FORMAT

OP:TP, OOS


See Purpose.

4. SYSTEM RESPONSE

IP = In Progress.




5. REFERENCES

IM/OM References:

Input MessagesOP:AP-OOSOP:BTS-OOSOP:OOS


Issue 28 OP:TP-OOS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP TP OOS August 2005




OP:TP-OOS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP TP-STATUS

ID............. OP:TP-STATUSRELEASE ....... 20.0 and laterTYPE .......... Input

1. PURPOSE

Reports the maintenance status of an Traffic Processor (TP).


2. FORMAT

OP:TP a, STATUS



4. SYSTEM RESPONSE




PF = Printout Follows. Followed by an OP-TP-STATUS output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesOP:TP-ALARMOP:TP-VERSION

Output MessagesOP-BTS-ALARMOP-TP-ALARMOP-TP-STATUSOP-TP-VERSION



Issue 28 OP:TP-STATUS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP TP-STATUS August 2005



OP:TP-STATUS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP TP-VERSION

ID............. OP:TP-VERSIONRELEASE ....... 20.0 and laterTYPE .......... Input

1. PURPOSE

Lists the version(s) of the software on the Traffic Processor (TP).


2. FORMAT

OP:TP a, VERSION



4. SYSTEM RESPONSE




PF = Printout Follows. Followed by an OP-TP-VERSION output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesOP-TP-VERSION



Issue 28 OP:TP-VERSION-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP TP-VERSION August 2005



OP:TP-VERSION-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RMV AP

ID............. RMV:APRELEASE ....... 24.0 and laterTYPE .......... Input


**WARNING**Radio Cluster Server (RCS) transient calls may be lost. If the UCL option isused, an attempt to save RCS stable calls will be made, but they may also belost.

If UCL is specified, the database update application will be removed fromservice even if it cannot be made primary elsewhere. This could result in acomplete loss of the ability to perform database Recent Changes.

If the UCL option is used and Voice Channel Administration (VCA) cannotbe switched over to the mate Application Processor (AP), execution of thiscommand will result in the loss of the ability to complete new calls.

If the UCL option is used and this AP has the last ACTIVE Home VisitorLocation Register (HVLR), the removal of this application will result in aloss of call processing.

If the UCL option is used and this AP hosts the last ACTIVE HVLR IntegrityManager (HVLR-

IM), the removal of this application will prevent HVLRfrom successfully reinitializing. Also the Technician Interface (TI)commands backup:db and copy:db cannot be run.

If the UCL option is used and the last ACTIVE Signaling System 7 (SS7) linkin a linkset is removed, all calls for the IS634 base station associated with thelinkset will be lost.

If the UCL option is used and this AP has the last active Signaling System 7High Speed Link (SS7HSL) in a link set, the SS7HSL will become OOSMANUAL and the linkset will become OOS FAULT resulting in the loss of allservice to the associated base station.

If the last active Signaling System 7 Message Manager (SS7MM) applicationis running on this AP, the use of the UCL option will result in the removal ofthe SS7MM application from service and the complete loss of the ability toprocess SS7 messages.

1. PURPOSE

Remove the specified Application Processor (AP), including any applications andresources associated with the AP, from service. Successful completion of this commandresults in the AP and its associated applications and resources transitioning to the OOSMANUAL state. A list of the resources and applications associated with an AP can bedetermined by executing the OP:AP-STATUS command.


Issue 28 RMV:AP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRMV AP August 2005


Applications and resources are removed from service in turn. Attempts to switchovermated applications running in an active state or with a primary update role will be madefor both conditional or unconditional removes. If the remove is conditional, a failure toremove or successfully switchover any application or the failure to remove a singleresource will result in the failure of the AP remove command. Any component that isremoved before the command fails will remain OOS MANUAL and will need to be restoredmanually. If the AP remove command is unconditional (UCL option) it will not be failed ifany application or resource fails to be removed.

Attempts will be made to switchover stable calls on each RCS to the mate RCS, but the UCLoption doesn’t require that the mate RCS be ACTIVE so that stable calls are not guaranteedto be maintained for unconditional AP removes.

Message Mapping Applications (MMAs) must be in the inhibited state (OP:AP-STATUS,INH:AP-MMA) before they may be removed under a conditional AP remove command.There must be an active SS7 link on the mate AP before the links may be removed under aconditional AP remove command.

While the AP is OOS MANUAL, some commands may still be accepted (such as RST:AP).

This is also a 1xEV-DO message. Remove a specified AP from service. Adding theoptional argument UCL has the same effect as if no argument is supplied. That is, there isno conditional remove.

2. FORMAT

[1] RMV:AP a [;UCL]

[2] RMV:AP a




4. SYSTEM RESPONSE

IP = In Progress.



PF = Printout Follows. Followed by a RMV-AP output message. If the PF isfollowed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RMV-AP command will bedelayed.


RMV:AP-2 Issue 28









5. REFERENCES

IM/OM References:

Input MessagesALW:AP-MMA (Flexent EMS/AP)INH:AP-MMA (Flexent EMS/AP)INIT:APOP:ALARM-EMS (Flexent EMS/AP)OP:AP-ALARM (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)OP:CELLOP:CELL-GENERICRESTART:AP-HVLRIM (Flexent EMS/AP)RMV:AP-DS1 (Flexent EMS/AP)RMV:AP-HVLR (Flexent EMS/AP)RMV:AP-MMA (Flexent EMS/AP)RMV:AP-MSCDBMS (Flexent EMS/AP)RMV:AP-ROP (Flexent EMS/AP)RMV:AP-SP (Flexent EMS/AP)RMV:AP-SS7 (Flexent EMS/AP)RMV:AP-SS7MM (Flexent EMS/AP)RMV:AP-VCA (Flexent EMS/AP)RMV:RCS (Flexent EMS/AP)RMV:SS7 (Flexent EMS/AP)RST:APRST:AP-DS1 (Flexent EMS/AP)RST:AP-HVLR (Flexent EMS/AP)RST:AP-MMA (Flexent EMS/AP)RST:AP-MSCDBMS (Flexent EMS/AP)RST:AP-ROP (Flexent EMS/AP)RST:AP-SP (Flexent EMS/AP)RST:AP-SS7 (Flexent EMS/AP)


Issue 28 RMV:AP-3


RST:AP-SS7MM (Flexent EMS/AP)RST:AP-VCA (Flexent EMS/AP)RST:RCS (Flexent EMS/AP)RST:SS7 (Flexent EMS/AP)

Output MessagesALW-AP-MMAINH-AP-MMAINIT-APOP-ALARMOP-AP-ALARMOP-AP-STATUSOP-CELLOP-CELL-GENERICRESTART:AP-HVLRIMRMV-APRMV-AP-DS1RMV-AP-HVLRRMV-AP-MMARMV-AP-MSCDBMSRMV-AP-ROPRMV-AP-SPRMV-AP-SS7RMV-AP-SS7MMRMV-AP-VCARMV-RCSRMV-SS7RST-APRST-AP-DS1RST-AP-HVLRRST-AP-MMARST-AP-MSCDBMSRST-AP-ROPRST-AP-SPRST-AP-SS7RST-AP-SS7MMRST-AP-VCARST-RCSRST-SS7

Other References:

401-710-080 MSC Support for IS-634 Base Stations Feature Guide




RMV:AP-4 Issue 28


401-710-202 Mobility Manager (MM) Read Only Printer (ROP) Operations, Administration, andMaintenance (OA&M) Guide

apoffline (invoked from AP UNIX login)aponline (invoked from AP UNIX login)


Issue 28 RMV:AP-5




RMV:AP-6 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RMV:BTS ASMB TXAMP

ID............. RMV:BTS-ASMB-TXAMPRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Removes a Transmit Amplifier (TXAMP) for a specified cabinet of a specific BaseTransceiver System (BTS).

NOTE: This command is not supported in a mixed mode cell.


2. FORMAT

RMV:BTS a, ASMB b, TXAMP c [;UCL]





UCL = Unconditional.

4. SYSTEM RESPONSE




PF = Printout Follows. Followed by a RMV-BTS-ASMB-TXAMP output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesRMV-BTS-ASMB-TXAMP



Issue 28 RMV:BTS-ASMB-TXAMP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRMV:BTS ASMB TXAMP August 2005



RMV:BTS-ASMB-TXAMP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RMV BTS CDM

ID............. RMV:BTS-CDMRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Removes a specified unit on a particular Base Transceiver System (BTS).


2. FORMAT

[1] RMV:BTS a, CDM b, CBR c [;UCL]

[2] RMV:BTS a, CDM b, CRC [;UCL]

[3] RMV:BTS a, CDM b, EVM d [;UCL]









4. SYSTEM RESPONSE




PF = Printout Follows. Followed by a RMV-BTS-CDM output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.


Issue 28 RMV:BTS-CDM-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRMV BTS CDM August 2005

Output MessagesRMV-BTS-CDM



RMV:BTS-CDM-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RMV BTS-TDU

ID............. RMV:BTS-TDURELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Removes a Test and Diagnostic Unit (TDU) on a particular Base Transceiver System (BTS).

NOTE: This command is not supported for BTSs of type Modular Cell 1, Modular Cell 2,Modular Cell 3 or in a mixed mode cell.


2. FORMAT

RMV:BTS a, TDU b [;UCL]





4. SYSTEM RESPONSE




PF = Printout Follows. Followed by a RMV-BTS-TDU output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesRMV-BTS-TDU



Issue 28 RMV:BTS-TDU-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRMV BTS-TDU August 2005



RMV:BTS-TDU-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RMV BTS-TFU

ID............. RMV:BTS-TFURELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Removes a Time Frequency Unit (TFU) on a particular Base Transceiver System (BTS).

NOTE: This command is not supported in a mixed mode cell.


2. FORMAT

RMV:BTS a, TFU b [;UCL]





4. SYSTEM RESPONSE




PF = Printout Follows. Followed by a RMV-BTS-TFU output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesRMV-BTS-TFU



Issue 28 RMV:BTS-TFU-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRMV BTS-TFU August 2005



RMV:BTS-TFU-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RMV TP

ID............. RMV:TPRELEASE ....... 20.0 and laterTYPE .......... Input

1. PURPOSE

Removes the specified Traffic Processor (TP). This command is always unconditional.

NOTE: This command cannot remove a TP that is already Out Of Service (OOS).


2. FORMAT

RMV:TP a



4. SYSTEM RESPONSE




PF = Printout Follows. Followed by a RMV-TP output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesRST:TP

Output MessagesRMV-TPRST-TP



Issue 28 RMV:TP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRMV TP August 2005



RMV:TP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RST AP

ID............. RST:APRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Restores an Application Processor (AP) and any resources and applications associated withthat AP to service.


On successful completion of the command, the AP and all its associated resources andapplications will be ACTIVE. A list of the resources and applications associated with anAP can be determined by executing the OP:AP-STATUS command. Each matedapplication will be brought to the ACTIVE or STBY state depending on the state of theapplication on the mate AP. If the application is ACTIVE on the mate AP, it will bebrought to the STBY state on this AP. If the application is not ACTIVE on the mate AP, theapplication will be brought to the ACTIVE state on this AP.

Each non-mated (simplex) application will be brought to the active state.

Each Radio Cluster Server (RCS) that is made ACTIVE will begin stable clearing the cells,and it will be a few minutes before the cells can process calls. If an RCS is OOS MANUAL onboth of its associated APs before the AP restore command is issued, that RCS will not berestored to service since it is assumed that the technician manually removed that RCS fromservice (RMV:RCS) and it should not be automatically restored. The RCS should bemanually restored to service if desired (RST:RCS).

The Mobile Switching Center Database Management System (MSCDBMS) updateapplication is restored to the ACTIVE maintenance state on each AP where it is running.The MSCDBMS update role is assigned to be primary and secondary on the AP pair whereit is executing. The MSCDBMS update application will be assigned the primary updaterole if the MSCDBMS update role is not primary on the mate AP. The MSCDBMS updateapplication will be assigned the secondary update role if the MSCDBMS update role isprimary on the mate AP.

The Message Mapping Application (MMA) is a mated application that runsACTIVE/ACTIVE on the AP pair. Each MMA application instance will be brought to theACTIVE state as a result of the successful execution of this command.

This is also a 1xEV-DO message.

2. FORMAT

RST:AP a




Issue 28 RST:AP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRST AP August 2005

4. SYSTEM RESPONSE

IP = In Progress.



PF = Printout Follows. Followed by a RST-AP output message. If the PF isfollowed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RST-AP command will bedelayed.








5. REFERENCES

IM/OM References:

Input MessagesINIT:APOP:ALARM-EMS (Flexent EMS/AP)OP:AP-ALARM (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)OP:CELLOP:CELL-GENERICRESTART:AP-HVLRIM (Flexent EMS/AP)RMV:APRMV:AP-DS1 (Flexent EMS/AP)RMV:AP-HVLR (Flexent EMS/AP)RMV:AP-MMA (Flexent EMS/AP)RMV:AP-MSCDBMS (Flexent EMS/AP)RMV:AP-ROP (Flexent EMS/AP)RMV:AP-SP (Flexent EMS/AP)RMV:AP-SS7 (Flexent EMS/AP)RMV:AP-SS7MM (Flexent EMS/AP)


RST:AP-2 Issue 28


RMV:AP-VCA (Flexent EMS/AP)RMV:RCS (Flexent EMS/AP)RMV:SS7 (Flexent EMS/AP)RST:AP-DS1 (Flexent EMS/AP)RST:AP-HVLR (Flexent EMS/AP)RST:AP-MMA (Flexent EMS/AP)RST:AP-MSCDBMS (Flexent EMS/AP)RST:AP-ROP (Flexent EMS/AP)RST:AP-SP (Flexent EMS/AP)RST:AP-SS7 (Flexent EMS/AP)RST:AP-SS7MM (Flexent EMS/AP)RST:AP-VCA (Flexent EMS/AP)RST:RCS (Flexent EMS/AP)RST:SS7 (Flexent EMS/AP)

Output MessagesINIT-APOP-ALARMOP-AP-ALARMOP-AP-STATUSOP-CELLOP-CELL-GENERICRESTART-AP-HVLRIMRMV-APRMV-AP-DS1RMV-AP-HVLRRMV-AP-MMARMV-AP-MSCDBMSRMV-AP-ROPRMV-AP-SPRMV-AP-SS7RMV-AP-SS7MMRMV-AP-VCARMV-RCSRMV-SS7RST-APRST-AP-DS1RST-AP-HVLRRST-AP-MMARST-AP-MSCDBMSRST-AP-ROPRST-AP-SPRST-AP-SS7RST-AP-SS7MMRST-AP-VCARST-RCSRST-SS7


Issue 28 RST:AP-3


Other References:





401-710-205 Mobility Manager Signaling System 7 / Direct Link Node (MM-SS7/MM-DLN)Operations, Administration, and Maintenance (OA&M)


RST:AP-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RST:BTS ASMB TXAMP

ID............. RST:BTS-ASMB-TXAMPRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Restores a Transmit Amplifier (TXAMP) for a specified cabinet of a specific BaseTransceiver System (BTS).

Specifying UCL is required for the TXAMP.



2. FORMAT

RST:BTS a, ASMB b, TXAMP c ;UCL






4. SYSTEM RESPONSE




PF = Printout Follows. Followed by a RST-BTS-ASMB-TXAMP output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.


Issue 28 RST:BTS-ASMB-TXAMP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRST:BTS ASMB TXAMP August 2005

Output MessagesRST-BTS-ASMB-TXAMP



RST:BTS-ASMB-TXAMP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RST BTS CDM

ID............. RST:BTS-CDMRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Restores a specified unit on a particular Base Transceiver System (BTS).


2. FORMAT

[1] RST:BTS a, CDM b, CBR c [;UCL]

[2] RST:BTS a, CDM b, CRC [;UCL]

[3] RST:BTS a, CDM b, EVM d [;UCL]









4. SYSTEM RESPONSE




PF = Printout Follows. Followed by a RST-BTS-CDM output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.


Issue 28 RST:BTS-CDM-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRST BTS CDM August 2005

Output MessagesRST-BTS-CDM



RST:BTS-CDM-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RST BTS-TDU

ID............. RST:BTS-TDURELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Restores a Test and Diagnostic Unit (TDU) on a particular Base Transceiver System (BTS).

NOTE: This command is not supported for BTSs of type Modular Cell 1, Modular Cell 2,Modular Cell 3 or in a mixed cell mode.


2. FORMAT

RST:BTS a, TDU b [;UCL]





4. SYSTEM RESPONSE




PF = Printout Follows. Followed by a RST-BTS-TDU output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesRST-BTS-TDU



Issue 28 RST:BTS-TDU-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRST BTS-TDU August 2005



RST:BTS-TDU-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RST BTS-TFU

ID............. RST:BTS-TFURELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Restores a Time Frequency Unit (TFU) on a particular Base Transceiver System (BTS).



2. FORMAT

RST:BTS a, TFU[:GPS] b [;UCL]



GPS = Requests the restore of the GPS.



4. SYSTEM RESPONSE




PF = Printout Follows. Followed by a RST-BTS-TFU output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesRST-BTS-TFU



Issue 28 RST:BTS-TFU-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRST BTS-TFU August 2005



RST:BTS-TFU-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RST TP

ID............. RST:TPRELEASE ....... 20.0 and laterTYPE .......... Input

1. PURPOSE

Restores a Traffic Processor (TP) from the Out Of Service (OOS) state to the active state.This command is used to put a TP back into service after maintenance activities arecomplete.


2. FORMAT

RST:TP a



4. SYSTEM RESPONSE




PF = Printout Follows. Followed by a RST-TP output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesRMV:TP

Output MessagesRMV-TPRST-TP



Issue 28 RST:TP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRST TP August 2005



RST:TP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 SELECT AP

ID............. SELECT:APRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Selects the Application Processor (AP) platform software version for a software update orgeneric retrofit procedure.

Format 1: The AP will initialize to the selected version of AP platform software on eitherof the following events:

• An initialization of the AP in response to INIT:AP-FULL (during asoftware update).

• An initialization of the AP in response to a "42 r, 50, 54" sequence at the ECPEmergency Action Interface (during a generic retrofit).

NOTE: This command can only be run from the Technician InterfaceCommand Line Interface (TICLI).

Format 2: This is a 1xEV-DO message. The 1xEV-DO command selects the APApplication Software Version to activate. The 1xEV-DO command does notselect platform software; a single platform version may be present. Beforeactivating the software, all the APs in the same frame must select the sameapplication version. The compatible platform version also needs to be installedand activated beforehand.

NOTE: This command can only be run from the Element ManagementSystem (EMS).

2. FORMAT

[1] SELECT:AP a, SOFTWARE b, VERSION "c"

[2] SELECT:AP a, APPLICATION SOFTWARE, VERSION d



b = Software type. "platform" is the only supported software type.

c = Software version. A string of characters within double quotes.

d = AP Application Software version identifier. A string of 12 characters.







Issue 28 SELECT:AP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSELECT AP August 2005



E — 1xEV-DO


D — Flexent Modular & CDBS Cells and APs.


F — FOA loads.G — GA loads.P — Private loads.


9th character — Compatibility indicator. Always D.



4. SYSTEM RESPONSE

IP = In Progress.



PF = Printout Follows. Followed by a SELECT:AP output message. If the PF isfollowed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the SELECT:AP command willbe delayed.









SELECT:AP-2 Issue 28


5. REFERENCES

IM/OM References:

Input MessagesCOMMIT:APINIT:APOP:AP-VERSION

Output MessagesCOMMIT-APINIT-APOP-AP-VERSIONSELECT-AP

Other References:








Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 SEND BTS GENERIC

ID............. SEND:BTS-GENERICRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Requests a download of specified generic software at the specified Base TransceiverSystem (BTS).


2. FORMAT

SEND:BTS a[, CDM b], GENERIC c













E — 1xEV-DO




Issue 28 SEND:BTS-GENERIC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSEND BTS GENERIC August 2005







4. SYSTEM RESPONSE





RL = Retry Later. Data links to the cell are down.

5. REFERENCES

IM/OM References:

Input MessagesSTOP:SEND-BTS-GENERIC

Output MessagesSEND-BTS-GENERIC



SEND:BTS-GENERIC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 START TAA UATI

ID............. START:TAA-UATIRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Starts both forward and reverse link test application tests.


2. FORMAT

START:TAA:UATI 0xa [, BTS b, SECTOR c] [, DRCRATE d] [, ACK e][, NOLOOPBACK] [, DATAPKTS] [, MINRATE f, MAXRATE g][, DURATION h] [, INTERVAL i] [,TAI j]


a = Universal Access Terminal Identifier (UATI) ID in hexadecimal format.

b = Base Transceiver System (BTS) number (1-600).

c = Sector number (1-3).

d = Fixed Data Rate Channel (DRC) (0-12). If not specified, test will use variableDRC rate.

e = Fixed ACK bit indicator:

0 — Indicates that the test does not use a fix ACK bit.1 — Indicates that the test makes use of a fix ACK bit.

NOLOOPBACK = Requests that no loopback related packets will be generated/processed.Otherwise, loopback related packets will be generated/processed.

DATAPKTS = Requests that data packets will be generated. Otherwise, no data packets willbe generated during the test.

f = Minimum data rate throughout the reverse test:

0 — 0 kbps1 — 9.6 kbps2 — 19.2 kbps3 — 38.4 kbps4 — 76.2 kbps5 — 153.6 kbps

g = Maximum data rate throughout the reverse test:



Issue 28 START:TAA-UATI-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSTART TAA UATI August 2005

NOTE: The MINRATE value must be less than or equal to the MAXRATEvalue. If the MINRATE value is equal to the MAXRATE value, then theMAXRATE value cannot be equal to zero. If one value is specifiedthen the other must also be specified.

h = Test duration. If not specified, 30 minutes will be used. Test duration:

1 — 15 minutes.2 — 30 minutes.3 — 45 minutes.4 — 60 minutes.5 — 75 minutes.6 — 90 minutes.7 — 105 minutes.8 — 120 minutes.9 — 135 minutes.10 — 150 minutes.11 — 165 minutes.12 — 180 minutes.13 — 195 minutes.14 — 210 minutes.15 — 225 minutes.16 — 240 minutes.

i = Data collection interval in seconds (2-5). If not specified, 2 seconds will beused.

j = Idle state timer for collecting data for UATI in minutes (1-15). If notspecified, no idle states data will be collected.

4. SYSTEM RESPONSE




PF = Printout Follows. Followed by an START-TAA-UATI output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesSTART:TAF-UATISTART:TAR-UATI


START:TAA-UATI-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 START TAA UATI

Output MessagesSTART-TAA-UATISTOP-TAx-UATI



Issue 28 START:TAA-UATI-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksSTART TAA UATI August 2005



START:TAA-UATI-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 START TAF UATI

ID............. START:TAF-UATIRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Starts forward link test application tests.


2. FORMAT

START:TAF:UATI 0xa [, BTS b, SECTOR c] [, DRCRATE d] [, ACK e][, NOLOOPBACK] [, DATAPKTS] [, DURATION f][, INTERVAL g] [,TAI h]



b = Base Transceiver System (BTS) number (1-600).

c = Sector number (1-3).

d = Fixed Data Rate Channel (DRC) (0-12). If not specified, test will use variableDRC rate.

e = Fixed ACK bit indicator:

0 — Indicates that the test does not use a fix ACK bit.1 — Indicates that the test makes use of a fix ACK bit.

NOLOOPBACK = Requests that no loopback related packets will be generated/processed.Otherwise, loopback related packets will be generated/processed.

DATAPKTS = Requests that data packets will be generated. Otherwise, no data packets willbe generated during the test.

f = Test duration. If not specified, 30 minutes will be used. Test duration:

1 — 15 minutes.2 — 30 minutes.3 — 45 minutes.4 — 60 minutes.5 — 75 minutes.6 — 90 minutes.7 — 105 minutes.8 — 120 minutes.9 — 135 minutes.10 — 150 minutes.11 — 165 minutes.12 — 180 minutes.13 — 195 minutes.


Issue 28 START:TAF-UATI-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSTART TAF UATI August 2005

14 — 210 minutes.15 — 225 minutes.16 — 240 minutes.

g = Data collection interval in seconds (2-5). If not specified, 2 seconds will beused.

h = Idle state timer for collecting data for UATI in minutes (1-15). If notspecified, no idle states data will be collected.

4. SYSTEM RESPONSE




PF = Printout Follows. Followed by an START-TAF-UATI output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesSTART:TAA-UATISTART:TAR-UATI

Output MessagesSTART-TAF-UATISTOP-TAx-UATI



START:TAF-UATI-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 START TAR UATI

ID............. START:TAR-UATIRELEASE ....... 21.0 and laterTYPE .......... Input

1. PURPOSE

Starts reverse link test application tests.


2. FORMAT

START:TAR:UATI 0xa [, MINRATE b, MAXRATE c] [, DURATION d][, INTERVAL e]



b = Minimum data rate throughout the reverse test:


c = Maximum data rate throughout the reverse test:


NOTE: The MINRATE value must be less than or equal to the MAXRATEvalue. If the MINRATE value is equal to the MAXRATE value, then theMAXRATE value cannot be equal to zero. If one value is specifiedthen the other must also be specified.

d = Test duration. If not specified, 30 minutes will be used. Test duration:

1 — 15 minutes.2 — 30 minutes.3 — 45 minutes.4 — 60 minutes.5 — 75 minutes.6 — 90 minutes.7 — 105 minutes.8 — 120 minutes.9 — 135 minutes.


Issue 28 START:TAR-UATI-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSTART TAR UATI August 2005

10 — 150 minutes.11 — 165 minutes.12 — 180 minutes.13 — 195 minutes.14 — 210 minutes.15 — 225 minutes.16 — 240 minutes.

e = Data collection interval in seconds (2-5). If not specified, 2 seconds will beused.

4. SYSTEM RESPONSE




PF = Printout Follows. Followed by an START-TAR-UATI output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesSTART:TAA-UATISTART:TAF-UATI

Output MessagesSTART-TAR-UATISTOP-TAx-UATI



START:TAR-UATI-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 STOP:BTS ASMB TXAMP

ID............. STOP:BTS-ASMB-TXAMPRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Stops an initiated but not yet executed maintenance activity on a Transmit Amplifier(TXAMP) for a specified Base Transceiver System (BTS).



2. FORMAT

STOP:BTS a, ASMB b, TXAMP c





4. SYSTEM RESPONSE




PF = Printout Follows. Followed by a STOP-BTS-ASMB-TXAMP outputmessage.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesSTOP-BTS-ASMB-TXAMP



Issue 28 STOP:BTS-ASMB-TXAMP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSTOP:BTS ASMB TXAMP August 2005



STOP:BTS-ASMB-TXAMP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 STOP BTS CDM

ID............. STOP:BTS-CDMRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Stops an initiated but not yet executed maintenance activity on a specified unit on aparticular Base Transceiver System (BTS).


2. FORMAT

[1] STOP:BTS a, CDM b, CBR c

[2] STOP:BTS a, CDM b, CRC

[3] STOP:BTS a, CDM b, EVM d








4. SYSTEM RESPONSE




PF = Printout Follows. Followed by a STOP-BTS-CDM output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.


Issue 28 STOP:BTS-CDM-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSTOP BTS CDM August 2005

Output MessagesSTOP-BTS-CDM



STOP:BTS-CDM-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 STOP BTS-TDU

ID............. STOP:BTS-TDURELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Stops an initiated but not yet executed maintenance activity on a Test and Diagnostic Unit(TDU) on a particular Base Transceiver System (BTS).

NOTE: This command is not supported for BTSs of type Modular Cell 1, Modular Cell 2,Modular Cell 3 or in a mixed cell mode.


2. FORMAT

STOP:BTS a, TDU b




4. SYSTEM RESPONSE




PF = Printout Follows. Followed by a STOP-BTS-TDU output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesSTOP-BTS-TDU



Issue 28 STOP:BTS-TDU-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSTOP BTS-TDU August 2005



STOP:BTS-TDU-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 STOP BTS-TFU

ID............. STOP:BTS-TFURELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Stops an initiated but not yet executed maintenance activity on a Time Frequency Unit(TFU) on a particular Base Transceiver System (BTS).



2. FORMAT

STOP:BTS a, TFU b




4. SYSTEM RESPONSE




PF = Printout Follows. Followed by a STOP-BTS-TFU output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesSTOP-BTS-TFU



Issue 28 STOP:BTS-TFU-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSTOP BTS-TFU August 2005



STOP:BTS-TFU-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 STOP:EXC BTS FLUS

ID............. STOP:EXC-BTS-FLUSRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Format 1: Terminates a single Forward Link User Simulation (FLUS) user on a specifiedcarrier in a given Base Transceiver System (BTS).

Format 2: Terminates all FLUS users on a specified carrier in a given BTS.


2. FORMAT

[1] STOP:EXC;BTS a, FLUS CDM b, USER c

[2] STOP:EXC;BTS a, FLUS CDM b




c = FLUS user number (1-25).

4. SYSTEM RESPONSE




PF = Printout Follows. Followed by a STOP-EXC-BTS-FLUS output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesSTOP-EXC-BTS-FLUS



Issue 28 STOP:EXC-BTS-FLUS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSTOP:EXC BTS FLUS August 2005



STOP:EXC-BTS-FLUS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 STOP FLUS CELL

ID............. STOP:FLUS-CELLRELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE

Ends the Forward Link User Simulation (FLUS) session at a specified cell.


2. FORMAT

STOP:FLUS;CELL a



• A single cell site.• A list of cell sites separated by commas and enclosed in parentheses.

4. SYSTEM RESPONSE






5. REFERENCES

IM/OM References:

Input MessagesFLUS:CELL

Output MessagesFLUS-CELL



Issue 28 STOP:FLUS-CELL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSTOP FLUS CELL August 2005



STOP:FLUS-CELL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 STOP SEND BTS GENERIC

ID............. STOP:SEND-BTS-GENERIC


1. PURPOSE

Stops a download of software to a specified Base Transceiver System (BTS).


2. FORMAT

STOP:SEND;BTS a[, CDM b], GENERIC




4. SYSTEM RESPONSE






5. REFERENCES

IM/OM References:

Input MessagesSEND:BTS-GENERIC

Output MessagesSTOP-SEND-BTS-GENERIC



Issue 28 STOP:SEND-BTS-GENERIC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSTOP SEND BTS GENERIC August 2005



STOP:SEND-BTS-GENERIC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 STOP:TAx UATI

ID............. STOP:TAx-UATIRELEASE ....... 20.1 and laterTYPE .......... Input

1. PURPOSE

Terminates a specified test application test.


2. FORMAT

STOP:{TAA TAF TAR}; UATI 0xa


TAA = Test application both forward and reverse.

TAF = Test application forward.

TAR = Test application reverse.


4. SYSTEM RESPONSE




PF = Printout Follows. Followed by a STOP:TAx-UATI output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesSTART:TAA-UATISTART:TAF-UATISTART:TAR-UATI

Output MessagesSTOP-TAx-UATI



Issue 28 STOP:TAx-UATI-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSTOP:TAx UATI August 2005



STOP:TAx-UATI-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 SWITCHBACK AP

ID............. SWITCHBACK:APRELEASE ....... 23.0 and laterTYPE .......... Input

1. PURPOSE

Switchback all server processes from the specified Application Processor (AP) to theoriginal position.


2. FORMAT

SWITCHBACK:AP a


a = AP number. Must be an odd number (1-277).

4. SYSTEM RESPONSE

IP = In Progress.



PF = Printout Follows. Followed by a SWITCHBACK-AP output message. If thePF is followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the SWITCHBACK:FROMAPcommand will be delayed.









Issue 28 SWITCHBACK:AP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSWITCHBACK AP August 2005

5. REFERENCES

IM/OM References:

Input MessagesSWITCHOVER:AP (Flexent EMS/AP)

Output MessagesSWITCHOVER-APSWITCHBACK-AP



SWITCHBACK:AP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 SWITCHOVER AP

ID............. SWITCHOVER:APRELEASE ....... 24.0 and laterTYPE .......... Input


**WARNING**If Voice Channel Administration (VCA) is switched over unconditionally asa result of this command, this may result in the loss of OOS MANUALinformation on trunks. Some maintenance operations in progress may beterminated.

1. PURPOSE


Switchover all applications in the ACTIVE state or primary role on the specifiedApplication Processor (AP) to their mate APs.

Switchover all ACTIVE applications on the specified AP to their STDBY mates on otherAPs. If the MSCDBMS update application is executing on the specified AP with an updaterole of primary, the primary update role will be switched over to the mate AP.

During a conditional AP switchover, switchovers will be attempted only on RCSs who areSTBY on their mate AP. During an unconditional AP switchover, RCS gracefulswitchovers will first be attempted. If an RCS fails to be switched over gracefully, it will beforced to switchover to its mate RCS, dropping all calls as well as denying new callattempts.

Format 1 Switchover for non 1xEV-DO AP.

Format 2 Switchover for 1xEV-DO AP. For a 1xEV-DO AP, there is an option toswitchover one server process or all the server processes. To switch over allserver process, type the AP number only without the server process name.

2. FORMAT

[1] SWITCHOVER:AP a [;UCL]

[2] SWITCHOVER:AP a [,b]


a = AP number.



Issue 28 SWITCHOVER:AP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSWITCHOVER AP August 2005

b = Server name. Only one server process can be specified:

FDBMSHOCHWSERVERLOGSERVEROHMTPAGENT

4. SYSTEM RESPONSE

IP = In Progress.



PF = Printout Follows. Followed by a SWITCHOVER-AP output message. If thePF is followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the SWITCHOVER-APcommand will be delayed.








5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)SWITCHBACK:AP (Flexent EMS/AP)SWITCHBACK:FROMAP (Flexent EMS/AP)SWITCHOVER:MSCDBMS (Flexent EMS/AP)


SWITCHOVER:AP-2 Issue 28


SWITCHOVER:RCS (Flexent EMS/AP)SWITCHOVER:ROP (Flexent EMS/AP)SWITCHOVER:SP (Flexent EMS/AP)SWITCHOVER:VCA (Flexent EMS/AP)

Output MessagesOP-AP-STATUSSWITCHBACK-FROMAPSWITCHOVER-APSWITCHOVER-MSCDBMSSWITCHOVER-RCSSWITCHOVER-ROPSWITCHOVER-SPSWITCHOVER-VCA

Other References:










Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW AP HVLR

ID............. ALW:AP-HVLRRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Changes the state of the Application Processor (AP) Home Visitor Location Register(HVLR) to allow access to the Home Location Register (HLR) or the Visitor LocationRegister (VLR) from the specified AP.

The INH:HVLR command may be used to inhibit access to the HVLR.

2. FORMAT

ALW:AP a, HVLR


a = AP number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a ALW-HVLR output message. If the PF isfollowed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the ALW-HVLR command willbe delayed.









Issue 28 ALW:AP-HVLR-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW AP HVLR August 2005

5. REFERENCES

IM/OM References:

Input MessagesINH:AP-HVLR (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)RMV:AP-HVLR (Flexent EMS/AP)RST:AP-HVLR (Flexent EMS/AP)SWITCHOVER:HVLR (Flexent EMS/AP)

Output MessagesALW-AP-HVLRINH-AP-HVLROP-AP-STATUSRMV-AP-HVLRRST-AP-HVLRSWITCHOVER-HVLR

Other References:



ALW:AP-HVLR-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW AP-MMA

ID............. ALW:AP-MMARELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Allow call processing on a Message Mapping Application (MMA)

This command re-enables call processing on an MMA that may have had call processinginhibited using the INH:AP-MMA input command. If the MMA is in either the CAMP-ON orINHIBIT call processing state (OP:AP-STATUS), its state will be returned to NORMAL andthe MMA will resume processing calls for its associated IS634 Base Station.

2. FORMAT

ALW:AP a,MMA b


a = Application Processor (AP) number.

b = MMA number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a ALW-AP-MMA output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the ALW:AP-MMA commandwill be delayed.









Issue 28 ALW:AP-MMA-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW AP-MMA August 2005

5. REFERENCES

IM/OM References:

Input MessagesINH:AP-MMA (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)RMV:AP (Flexent EMS/AP)RMV:AP-MMA (Flexent EMS/AP)RST:AP (Flexent EMS/AP)RST:AP-MMA (Flexent EMS/AP)

Output MessagesALW-AP-MMAINH-AP-MMAOP-AP-STATUSRMV-APRMV-AP-MMARST-APRST-AP-MMA

Other References:




ALW:AP-MMA-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW CELL-DL

ID............. ALW:CELL-DLRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Allow the virtual data links between the Executive Cellular Processor (ECP) complex andthe Message Mapping Application (MMA) for a particular IS634 Cell, thus allowing callprocessing for that cell within the Mobile Switching Center (MSC).

This command restores the virtual data links for an IS634 cell, thus allowing call processingfor that cell within the MSC.

A virtual data link for an IS634 cell is the "logical" connection between the ECP complexand the Message Mapping Application (MMA) that runs on an Open Air InterfaceApplication Processor (OAI-AP). There are two virtual data links for each IS634 cell, oneto each OAI-AP where the MMA application is hosted. An MMA processes messages foran IS634 Base Station, which has particular IS634 cells associated with it. This commandallows both virtual data links for an individual IS634 cell.

This command allows the technician to undo the inhibit function performed by theINH:CELL-DL command.

2. FORMAT

ALW:CELL a, DL


a = Cell number.

DL = Data link. Specifies that the virtual data links for the IS-634 cell are beingallowed.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a ALW-CELL-DL output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the ALW:CELL-DL commandwill be delayed.





Issue 28 ALW:CELL-DL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW CELL-DL August 2005





5. REFERENCES

IM/OM References:

Input MessagesALW:AP-MMA (Flexent EMS/AP)INH:AP-MMA (Flexent EMS/AP)INH:CELL-DL (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)RST:AP-MMA (Flexent EMS/AP)

Output MessagesALW-AP-MMAINH-AP-MMAINH-CELL-DLOP-AP-STATUS

Other References:



ALW:CELL-DL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW MSCDBMS-AUD

ID............. ALW:MSCDBMS-AUDRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Allow Application Processor (AP) based AUTOPLEX daily comprehensive databaseaudits.

This command allows daily comprehensive database audits between AP and ExecutiveCellular Processor (ECP) databases. On successful completion of this command, the dailycomprehensive audits will be resumed. If the TIME parameter is specified, then the auditswill begin at the specified time. If the TIME parameter is not specified, the previouslyspecified audit time will be used; if no time has ever been specified, the default audit timeof 03:00 will be used.

This command also allows the mufdb and ccfdb key crosscheck audit.

2. FORMAT

ALW:MSCDBMS,AUD[,TIME a]


a = Time at which to run daily comprehensive audits (in format hh:mm, wherehh represents the hour of the day in military time at which the audits shouldbe run, and mm represents the minute within the hour).

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a SWITCHOVER-AP output message. If thePF is followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the SWITCHOVER:APcommand will be delayed.







Issue 28 ALW:MSCDBMS-AUD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW MSCDBMS-AUD August 2005



5. REFERENCES

IM/OM References:

Input MessagesAUD:MSCDBMS (Flexent EMS/AP)INH:MSCDBMS-AUD (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)STOP:MSCDBMS (Flexent EMS/AP)

Output MessagesALW-MSCDBMS-AUDAUD-MSCDBMSINH-MSCDBMS-AUDOP-AP-STATUSSTOP-MSCDBMS-AUD

Other References:



ALW:MSCDBMS-AUD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW MSCDBMS-RCV

ID............. ALW:MSCDBMS-RCVRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Allow Application Processor (AP) based Recent Change / Verify (RC/V).

This command allows recent change processing to take place on the APs. On successfulcompletion of this command, new recent change sessions will be allowed to be initiated(apxrcv) and changes to the AUTOPLEX database will be allowed within existingsessions in which they had been inhibited.

2. FORMAT

ALW:MSCDBMS,RCV


See Purpose.

4. SYSTEM RESPONSE











Issue 28 ALW:MSCDBMS-RCV-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW MSCDBMS-RCV August 2005

5. REFERENCES

IM/OM References:

Input MessagesINH:MSCDBMS-RCV (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)

Output MessagesALW-MSCDBMS-RCVINH-MSCDBMS-RCVOP-AP-STATUS

Other References:


apxrcv (invoked from ECP or OMP)


ALW:MSCDBMS-RCV-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD MSCDBMS

ID............. AUD:MSCDBMSRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Audits Application Processor (AP) and Executive Cellular Processor (ECP) database tablesand synchronizes them if necessary.

This command runs a comprehensive audit on a specified table or on all tables if no table isspecified with the TABLE parameter. The audit will compare the AP and ECP versions ofthe table(s) and if discrepancies are detected the AP table will be modified to match theECP table.

When Home Visitor Location Register (HVLR) is enabled and the table specified is ccfdb,the audit will compare the master mufdb keys to each instance of ccfdb keys and willcorrect any discrepancies.

The output of the command will indicate which tables have been modified and whetheralarms were generated as a result of the audit, because audit mismatches could not becorrected. The output of the command will also indicate if the audit finds a Linked ListIndexed (LLI) record marked for deletion. Note that this command should not be runwhile a COPY:DB command is in progress.

2. FORMAT

AUD:MSCDBMS[,TABLE a]


a = Name of the table to be audited.

4. SYSTEM RESPONSE







Issue 28 AUD:MSCDBMS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD MSCDBMS August 2005





5. REFERENCES

IM/OM References:

Input MessagesALW:MSCDBMS-AUD (Flexent EMS/AP)COPY:DBINH:MSCDBMS-AUD (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)STOP:MSCDBMS (Flexent EMS/AP)


Other References:



AUD:MSCDBMS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 BKUP:RNCDB

ID............. BKUP:RNCDBRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

This command requests that a backup occur for the active Radio Network Controller(RNC) application database on the pre-specified Operations, Administration, andMaintenance (OA&M) proxy server archive directory.

2. FORMAT

BKUP:RNCDB, RNC [a ALL]



4. SYSTEM RESPONSE











Issue 28 BKUP:RNCDB-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksBKUP:RNCDB August 2005

5. REFERENCES

IM/OM References:

Input MessagesCOPY:RNCDBDELBKUP:RNCDBOP:RNCDB


Other References:



BKUP:RNCDB-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CFR AP-DS1

ID............. CFR:AP-DS1RELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Configures the loopback state of a Digital Signal Level 1 (DS1) in order to prepare it fortesting or operation. This command puts the specified DS1 into and out of "externalloopback" mode. The DS1 must be manually removed from service (RMV:AP-DS1) beforethe CFR:AP-DS1-EXT command can be performed. Once the CFR:AP-DS1-EXTcommand has successfully completed the DS1 has been placed into "external loopback"mode. The DS1 can then be tested with external DS1 test equipment. When testing hascompleted, the DS1 must be manually put back into "normal mode" (no loopback) usingthe CFR:AP-DS1-NORM command or the DS1 can be restored to service directly(RST:AP-DS1).

Note that a DS1 may not be configured in "external loopback" mode while it is beingdiagnosed (DGN:AP-DS1). The current mode of a DS1 can be determined by displaying itsstatus (OP:AP-STATUS).

2. FORMAT

CFR:AP a,DS1 b,c



b = DS1 number.

c = Mode keyword:

EXT — Configure the DS1 into "external loopback" mode, which means thatan external loopback test with external DS1 test equipment can nowbe performed.

NORM — Configure the DS1 back into "normal mode" (no loopback), whichmeans the DS1 can now be diagnosed (DGN:AP-DS1) or restored(RST:AP-DS1).

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a CFR-AP-DS1 output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the CFR:AP-DS1 commandwill be delayed.


Issue 28 CFR:AP-DS1-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCFR AP-DS1 August 2005








5. REFERENCES

IM/OM References:

Input MessagesDGN:AP-DS1 (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)RMV:AP-DS1 (Flexent EMS/AP)RST:AP-DS1 (Flexent EMS/AP)

Output MessagesCFR-AP-DS1DGN-AP-DS1OP-AP-STATUSRMV-AP-DS1RST-AP-DS1

Other References:



CFR:AP-DS1-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CFR:AP-SS7

ID............. CFR:AP-SS7RELEASE ....... 24.0 and laterTYPE .......... Input


**WARNING**If the Signaling System 7 Message Manager Application (SS7MMA) link isin the EXTERNAL LOOP mode and the remote end attempts to restore thelink, the link will appear to become active but fail at higher levels of the SS7protocol. Use the EXTERNAL LOOP mode only when both ends agree thatthe link is in the test state.

1. PURPOSE

Toggles the Signaling System 7 Message Manager Application (SS7MMA) link between thenormal (NO LOOP) mode and the EXTERNAL LOOP mode.

Use the CFR:AP-DS1-EXT and CFR:AP-DS1-NORM command to toggle a SignalingSystem 7 High Speed Link (SS7HSL) between normal (NO LOOP) and EXTERNAL LOOPmode.

The SS7MMA link must be manually removed from service (RMV:AP-SS7) before theCFR:AP-SS7-EXT command can be performed. When the CFR:AP-SS7-EXT commandhas successfully completed, the link has been placed into EXTERNAL LOOP mode. Theexternal loopback mode can be used to facilitate pattern (For example: Bit Error Rate Test[BERT]) testing from the remote end. Examples of BERT patterns are qrss and 511.

NOTE: The remote end must be able to perform the BERT test at a single Digital SignalLevel 0 (DS0) level. The BERT tests can be used to verify the quality of thetransmission facility, troubleshoot SS7 connection problems, and verify some ofthe circuitry in the Application Processors (APs) Digital Signal Level 1 (DS1)interface.

To remove the external loopback, execute the CFR:AP-SS7-NORM command or theRST:AP-SS7 command.

The mode an SS7MMA link can be determined by displaying its status by using theOP:AP-STATUS or OP:AP-DS1-STATUS command.

2. FORMAT

CFR:AP a,SS7 b,c


a = AP number

b = SS7 link number


Issue 28 CFR:AP-SS7-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCFR:AP-SS7 August 2005

c = Mode keyword:

EXT — Configure the SS7 link into "external loopback" mode, which meansthat an external loopback test with external test equipment can nowbe performed.

NORM — Configure the SS7 link back into "normal mode" (no loopback)which means the link can now be restored (RST:AP-SS7).

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a CFR-AP-SS7 output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the CFR-AP-SS7 commandwill be delayed.








5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RMV:AP-SS7 (Flexent EMS/AP)RST:AP-SS7 (Flexent EMS/AP)

Output MessagesCFR-AP-SS7OP-AP-STATUSRMV-AP-SS7RST-AP-SS7


CFR:AP-SS7-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CFR:AP-SS7

Other References:




Issue 28 CFR:AP-SS7-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksCFR:AP-SS7 August 2005



CFR:AP-SS7-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CFR SS7

ID............. CFR:SS7RELEASE ....... 24.0 and laterTYPE .......... Input


**WARNING**If the Signaling System 7 Low Speed Link (SS7LSL) is in the EXTERNALLOOP mode and the remote end attempts to restore the link, the link willappear to become active but fail at higher levels of the SS7 protocol. Use theEXTERNAL LOOP mode only when both ends agree that the link is in thetest state.

1. PURPOSE

Toggles the Signaling System 7 Low Speed Link (SS7LSL) between the normal (NO LOOP)mode and the EXTERNAL LOOP mode.

Use the CFR:AP-DS1-EXT and CFR:AP-DS1-NORM command to toggle a SignalingSystem 7 High Speed Link (SS7HSL) between normal (NO LOOP) and EXTERNAL LOOPmode.

The SS7LSL must be manually removed from service (RMV:SS7) before the CFR:SS7-EXTcommand can be performed. When the CFR:SS7-EXT command has successfullycompleted, the link has been placed into EXTERNAL LOOP mode. The external loopbackmode can be used to facilitate pattern (For example: Bit Error Rate Test [BERT]) testingfrom the remote end. Examples of BERT patterns are qrss and 511.

NOTE: The remote end must be able to perform the BERT test at a single Digital SignalLevel 0 (DS0) level. The BERT tests can be used to verify the quality of thetransmission facility, troubleshoot SS7 connection problems, and verify some ofthe circuitry in the Application Processors (APs) Digital Signal Level 1 (DS1)interface.

To remove the external loopback, execute the CFR:SS7-NORM command or the RST:SS7command.

The mode of an SS7LSL can be determined by displaying its status by using theOP:AP-STATUS or OP:AP-DS1-STATUS input command.

2. FORMAT

CFR:SS7 a,b


a = Signaling System 7 Low Speed Link (SS7LSL) number.


Issue 28 CFR:SS7-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCFR SS7 August 2005

b = Mode keyword:

EXT — Configure the SS7LSL into EXTERNAL LOOP mode, which meansthat an external loopback test with external test equipment can nowbe performed.

NORM — Configure the SS7LSL back into normal mode (NO LOOPBACK)which means the link can now be restored (RST:SS7).

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a CFR-SS7 output message. If the PF isfollowed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the CFR-SS7 command will bedelayed.








5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RST:SS7 (Flexent EMS/AP)RMV:SS7 (Flexent EMS/AP)

Output MessagesCFR-SS7OP-AP-STATUSRST-SS7RMV-SS7


CFR:SS7-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CFR SS7

Other References:




Issue 28 CFR:SS7-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksCFR SS7 August 2005



CFR:SS7-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COMMIT AP

ID............. COMMIT:APRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Commits the Application Processor (AP) to the version of platform software currentlyrunning.


Format 1: This command commits the AP to the version of platform software currentlyrunning on the AP. A commit removes the "backout" version of AP platformsoftware if it exists. A commit also removes the "new" version of AP platformsoftware if a new version (different from the currently running version) of APplatform software exists.

COMMIT is done only as part of a software update or generic retrofit procedure,after the new software has stabilized on the system for some time interval. Seethe Application Processor Cluster Operations, Administration, andMaintenance Guide to follow the software update or generic retrofit procedure.

The COMMIT will fail if the selected version of AP platform software differsfrom the currently running version of AP platform software.

This command can be run only from the EMS.

Format 2: This is a 1xEV-DO message. Commits the current sets of software versions sothat they cannot be backed out or removed.

2. FORMAT

[1] COMMIT:AP a, SOFTWARE b

[2] COMMIT:AP a, SOFTWARE



b = Software type: platform is the only type of software supported.

4. SYSTEM RESPONSE

IP = In Progress.



PF = Printout Follows. Followed by a COMMIT-AP output message. If the PF isfollowed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the COMMIT:AP command willbe delayed.


Issue 28 COMMIT:AP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOMMIT AP August 2005








5. REFERENCES

IM/OM References:

Input MessagesOP:AP-VERSIONSELECT:AP


Other References:




COMMIT:AP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COPY:RNCDB RNC

ID............. COPY:RNCDBRELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE

This command requests a restore (a copy) of the Radio Network Controller (RNC)application database. The request can be for an individual RNC or for all RNCs using themost recent backup file from the $CDMA_OAM_ROOT/rncdbbackups directory, thebackup file is specified by the system user.

2. FORMAT

COPY:RNCDB, RNC [a ALL], DIRNAME "b"



b = The backup directory/filename entered inside quotes (For example:"rnc24_12.0").

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a COPY-RNCDB output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the COPY-RNCDB commandwill be delayed.









Issue 28 COPY:RNCDB-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOPY:RNCDB RNC August 2005

5. REFERENCES

IM/OM References:

Input MessagesBKUP:RNCDBDELBKUP:RNCDBOP:RNCDB


Other References:



COPY:RNCDB-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CREATE MMA

ID............. CREATE:MMARELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Create a new Message Mapping Application (MMA) instance.

Create new instances of the MMA on both Application Processors (APs) in the configuredAP pair. Before issuing this command, the MMA must be configured in the Recent Change/ Verify (RC/V) bsconfig form. After the MMA has been created, it may be placed inservice using the RST:AP-MMA command. The CREATE:MMA command is used as part ofthe MMA growth procedure as described in the 401-710-080 MSC Support for IS-634 BaseStations Feature Guide document.

2. FORMAT

CREATE:MMA a


a = MMA number.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by a CREATE-MMA output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the CREATE:MMA commandwill be delayed.










Issue 28 CREATE:MMA-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCREATE MMA August 2005

5. REFERENCES

IM/OM References:

Input MessagesDELETE:MMA (Flexent EMS/AP)

Output MessagesCREATE-MMADELETE-MMA

Other References:


401-610-036 Database Update Manual



CREATE:MMA-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CREATE RCS

ID............. CREATE:RCSRELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE

Create a new Radio Cluster Server (RCS) instance.

Create a new instance of an RCS. Before issuing this command, the RCS must beconfigured in the Recent Change / Verify (RC/V) rcslink form. This command is usedas part of the RCS growth procedure as described in the 401-710-101 Application ProcessorCluster (APC) Operations, Administration, and Maintenance (OA&M)

This command is not required or supported for RCSs with Internet Protocol Backhaul(IPBH) enabled. RCSs that are configured for IP Backhaul will be in the Out Of ServiceManual (OOS-M) state after the cmodeqp form is inserted for the RCS.

2. FORMAT

CREATE:RCS a


a = RCS number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a CREATE-RCS output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the CREATE:RCS commandwill be delayed.









Issue 28 CREATE:RCS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCREATE RCS August 2005

5. REFERENCES

IM/OM References:

Input MessagesDELETE:RCS (Flexent EMS/AP)

Output MessagesCREATE-RCSDELETE-RCS

Other References:




CREATE:RCS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DELBKUP:RNCDB RNC

ID............. DELBKUP:RNCDBRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

This command requests that a specified Radio Network Controller (RNC) applicationdatabase on the pre-specified Operations, Administration, and Maintenance (OA&M)proxy server archive directory, be deleted.

2. FORMAT

DELBKUP:RNCDB, DIRNAME "a"


a = The backup directory/filename entered inside quotes (For example:"rnc24_12.0").

4. SYSTEM RESPONSE











Issue 28 DELBKUP:RNCDB-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDELBKUP:RNCDB RNC August 2005

5. REFERENCES

IM/OM References:

Input MessagesBKUP:RNCDBCOPY:RNCDBOP:RNCDB


Other References:



DELBKUP:RNCDB-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DELETE MMA

ID............. DELETE:MMARELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Delete a Message Mapping Application (MMA) from the Application Processor (AP)cluster.

This command deletes MMA instances from both APs where the MMA is configured. TheMMA instances must be in either the OOS MANUAL (RMV:AP-MMA) or OOS FAULT state.The MMA must first be deleted with this command before the associated Recent Change /Verify (RC/V) bsconfig form is deleted or before the AP designations are changed inthe RC/V bsconfig form. This command is used as part of the MMA degrowthprocedure as described in 401-710-080 MSC Support for IS-634 Base Stations Feature Guide.

Once the MMA is deleted, it appears as "configured" in the OP:AP-STATUS command.The "configured" state indicates that the MMA is in the process of being grown or de-grown.

2. FORMAT

DELETE:MMA a


a = MMA number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a DELETE-MMA output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the DELETE:MMA commandwill be delayed.







Issue 28 DELETE:MMA-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDELETE MMA August 2005



5. REFERENCES

IM/OM References:

Input MessagesCREATE:MMA (Flexent EMS/AP)

Output MessagesCREATE-MMADELETE-MMAOP-AP-STATUS

Other References:





DELETE:MMA-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DELETE RCS

ID............. DELETE:RCSRELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE

Delete a Radio Cluster Server (RCS) from the AP Application Processor (AP) cluster.

This command deletes the RCS from both the primary and alternate APs where it isequipped. The RCS must first be deleted with this command before the associated RecentChange / Verify (RC/V) rcslink form is deleted or before the primary or alternate APdesignations are changed in the RC/V rcslink form.

Once the RCS is deleted, it appears as configured in the OP:AP-STATUS command.

This command is not required or supported for RCSs with Internet Protocol Backhaul(IPBH) enabled.

2. FORMAT

DELETE:RCS a


a = RCS number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a DELETE-RCS output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the DELETE:RCS commandwill be delayed.









Issue 28 DELETE:RCS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDELETE RCS August 2005

5. REFERENCES

IM/OM References:

Input MessagesCREATE:RCS (Flexent EMS/AP)

Output MessagesCREATE-RCSDELETE-RCSOP-AP-STATUS

Other References:




DELETE:RCS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN AP-DS1

ID............. DGN:AP-DS1RELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Diagnoses a Digital Signal Level 1 (DS1) that is configured for the Link Access ProcedureD-Channel (LAPD) or Asynchronous Transfer Mode (ATM) protocol using an internalloopback test. This command puts the specified DS1 in "internal loopback" mode and thentests the DS1. The results of the test are displayed in output messages. The test shouldtake less than 75 seconds for a T1 link test to complete and 120 seconds for an E1 link.Once the test is completed, the DS1 is put back into "normal mode" (no loopback). TheDS1 must then be manually restored to service (RST:AP-DS1).

Note that only one DS1 may be diagnosed at a time. A second request on the same DS1will be rejected. A second request on a different DS1 will be queued until the first onefinishes. The DS1 must be in "normal mode" (no loopback) (CFR:AP-DS1) when thiscommand is executed. The mode a DS1 is currently in can be determined by displaying itsstatus (OP:AP-STATUS). The DS1 must also be manually removed from service before thiscommand can be performed (RMV:AP-DS1).

2. FORMAT

DGN:AP a, DS1 b [, DS0 c, CONNECT ]



b = DS1 number.

c = Digital Signal Level 0 (DS0) number (1-24).

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a DGN-AP-DS1 output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the DGN:AP-DS1 commandwill be delayed.







Issue 28 DGN:AP-DS1-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN AP-DS1 August 2005



5. REFERENCES

IM/OM References:

Input MessagesCFR:AP-DS1 (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)RMV:AP-DS1 (Flexent EMS/AP)RST:AP-DS1 (Flexent EMS/AP)

Output MessagesCFR-AP-DS1DGN-AP-DS1OP-AP-STATUSRMV-AP-DS1RST-AP-DS1

Other References:



DGN:AP-DS1-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN SS7

ID............. DGN:SS7RELEASE ....... 24.0 and laterTYPE .......... Input


**WARNING**If this Signaling System 7 (SS7) link is on a preferred referenced DigitalSignal Level 1 (DS1), the recommendation is to place the DS1 loopback atthe other end of the Digital Access and Cross–Connect System (DACS),5ESS Digital Cellular Switch (DCS), and so forth, otherwise links on otherDS1s might bounce.

1. PURPOSE

Diagnose a Signaling System 7 (SS7) link using Bit Error Rate Test (BERT). The results ofthe test are displayed to the Read Only Printer (ROP) and the Application Processor (AP)Admin log. (See the 401-710-101 Application Processor Cluster [APC] Operations,Administration, and Maintenance (OA&M) for information on AP Admin log files and how touse them.)

This command will run a BERT test on the specified SS7 Link. If no DURATION or CONToption is entered, the default duration of the test will be set to two minutes. The minimumduration for the test is two minutes and the maximum allowed duration is 24 hours. Notethat in order to successfully run a BERT command the following conditions must be met:

— At most one BERT test may be running for a single SS7 link at any one time. A secondrequest on the same SS7 link will be rejected.

— A maximum of three BERT tests may be running on any one AP at any one time.— The Digital Signal Level 1 (DS1) associated with the SS7 link must be equipped and

active.— The SS7 link must also be either in the growth state or in the available state.— The SS7 link must be manually out of service (RMV:SS7).

2. FORMAT

DGN:SS7 a [, CONT DURATION b:cc ]


a = SS7 number (1-512).

CONT = Continuous test. This keyword denotes that the BERT will run for themaximum amount of time allowable.

DURATION = Duration of the test.

b = The number of hours the test is set to run (0-24).

cc = The number of minutes the test is set to run (00-59). This must be 00 if b isset to 24. This must not be 00 or 01 if b is set to 00.


Issue 28 DGN:SS7-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN SS7 August 2005

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a DGN-AP-SS7 output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the DGN-AP-SS7 commandwill be delayed.








5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RMV:SS7 (Flexent EMS/AP)RST:SS7 (Flexent EMS/AP)

Output MessagesDGN-SS7OP-AP-STATUSRMV-SS7RST-SS7

Other References:



DGN:SS7-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 INH AP HVLR

ID............. INH:AP-HVLRRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Changes the state of the Application Processor (AP) Home Visitor Location Register(HVLR) to inhibit access to the Home Location Register (HLR) or the Visitor LocationRegister (VLR) from the specified AP.

The ALW:HVLR command may be used to allow access to the HVLR.

2. FORMAT

INH:AP a, HVLR


a = AP number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a INH-AP-HVLR output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the INH-HVLR command willbe delayed.









Issue 28 INH:AP-HVLR-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksINH AP HVLR August 2005

5. REFERENCES

IM/OM References:

Input MessagesALW:AP-HVLR (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)RMV:AP-HVLR (Flexent EMS/AP)RST:AP-HVLR (Flexent EMS/AP)SWITCHOVER:HVLR (Flexent EMS/AP)

Output MessagesALW-AP-HVLRINH-AP-HVLROP-AP-STATUSRMV-AP-HVLRRST-AP-HVLRSWITCHOVER-HVLR

Other References:



INH:AP-HVLR-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 INH AP-MMA

ID............. INH:AP-MMARELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Inhibit call processing on a Message Mapping Application (MMA).

This command inhibits call processing on an ACTIVE MMA instance. The state of the mateMMA instance is not affected; however, the mate MMA must be ACTIVE and in theNORMAL call processing state in order for this command to succeed. If calls are in progresson the MMA when this command is issued, the MMA is placed in the CAMP-ON callprocessing state while calls are allowed to drain from the MMA. No new calls are acceptedwhile the MMA is in the CAMP-ON state. The MMA will automatically leave the CAMP-ONstate and enter the INHIBIT state when the following conditions are satisfied:

— No emergency-911 calls are in progress

— The number of normal calls in progress on the MMA is below the threshold set for theMMA on the bsconfig Recent Change / Verify (RC/V) form.

If the MMA is in either the CAMP-ON or INHIBIT call processing state when the mateMMA fails or is unconditionally removed, it will automatically return to the NORMAL callprocessing state so that service to the IS634 Base Station is not lost. This command isintended to be used to gracefully remove an MMA from service without affecting serviceto the associated IS634 Base Station. The conditional RMV:AP-MMA command requires thatan ACTIVE MMA be in the INHIBIT call processing state.

2. FORMAT

INH:AP a,MMA b



a = MMA number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a INH-AP-MMA output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the INH:AP-MMA commandwill be delayed.


Issue 28 INH:AP-MMA-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksINH AP-MMA August 2005








5. REFERENCES

IM/OM References:

Input MessagesALW:AP-MMA (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)RMV:AP (Flexent EMS/AP)RMV:AP-MMA (Flexent EMS/AP)RST:AP (Flexent EMS/AP)RST:AP-MMA (Flexent EMS/AP)

Output MessagesALW-AP-MMAINH-AP-MMAOP-AP-STATUSRMV-APRMV-AP-MMARST-APRST-AP-MMA

Other References:





INH:AP-MMA-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 INH CELL-DL

ID............. INH:CELL-DLRELEASE ....... 24.0 and laterTYPE .......... Input


**WARNING**If the UCL option is used, the IS–634 cell virtual data links are inhibitedregardless of whether there are calls in progress (including emergency 911calls) for that IS–634 cell. This will result in any existing calls beingterminated and will prevent any new calls between that IS–634 cell and theMobile Switching Center (MSC).

1. PURPOSE

Inhibit the virtual data links between the Executive Cellular Processor (ECP) complex andthe Message Mapping Application (MMA) for a particular IS-634 cell, thus preventing callprocessing for that cell within the MSC.

This command inhibits the virtual data links for an IS-634 cell, thus preventing callprocessing for that IS-634 cell within the MSC. Without the UCL option, the virtual datalinks will only be inhibited if there are no calls currently being processed for that IS-634cell. Without UCL, the Message Mapping Application (MMA) instances on bothApplication Processors (APs) will be queried for the number of calls in progress for thespecified IS-634 cell; if there are any calls up, the command will fail.

The Data Link (DL) specified in the command signifies data link. The DL option is added tospecify that the virtual data links for the IS-634 cell are being inhibited. Currently, INH-CELL only supports the DL option. In the future the command might support otheroptions.

If the UCL option is specified, the virtual data links will be inhibited regardless of thenumber of calls. Any calls up between the Base Station and the MSC for the particular IS-634 cell will be terminated and no new calls will be allowed.

A virtual data link for an IS-634 cell is the "logical" connection between the ECP complexand the Message Mapping Application (MMA) that runs on an Open Air InterfaceApplication Processor (OAI-AP). There are two virtual data links for each IS-634 cell, oneto each OAI-AP where the MMA application is hosted. The MMA application processesmessages for a particular IS-634 cell Base Station, which has IS-634 cells associated with it.This command inhibits both virtual data links for an individual IS-634 cell withoutaffecting any of the other IS-634 cells associated with the Base Station.

This command is intended to be used during IS-634 cell de-growth procedures. It allowsthe technician to inhibit service for a particular IS-634 cell so that the IS-634 cell can bedeleted from Recent Change / Verify (RC/V) using the is634cell form.

The ALW:CELL-DL command may be used to allow the IS-634 cell virtual data links.

2. FORMAT

INH:CELL a, DL [;UCL]


Issue 28 INH:CELL-DL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksINH CELL-DL August 2005


a = Cell number

DL = Virtual Data Link.


4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a INH-CELL-DL output message. If thePF1 is followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the INH:CELL-DL commandwill be delayed.








5. REFERENCES

IM/OM References:

Input MessagesALW:AP-MMA (Flexent EMS/AP)ALW:CELL-DL (Flexent EMS/AP)INH:AP-MMA (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)

Output MessagesALW-AP-MMAINH-AP-MMAOP-AP-STATUS


INH:CELL-DL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 INH CELL-DL

Other References:




Issue 28 INH:CELL-DL-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksINH CELL-DL August 2005



INH:CELL-DL-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 INH MSCDBMS-AUD

ID............. INH:MSCDBMS-AUDRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Inhibits Application Processor (AP) based AUTOPLEX daily comprehensive databaseaudits.

This command inhibits the daily comprehensive database audits between AP andExecutive Cellular Processor (ECP) databases. On successful completion of this command,the daily comprehensive audits will be discontinued until the ALW:MSCDBMS-AUDcommand is run.

This command also inhibits the mufdb and ccfdb key crosscheck audit.

2. FORMAT

INH:MSCDBMS,AUD


See Purpose.

4. SYSTEM RESPONSE











Issue 28 INH:MSCDBMS-AUD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksINH MSCDBMS-AUD August 2005

5. REFERENCES

IM/OM References:

Input MessagesALW:MSCDBMS-AUD (Flexent EMS/AP)AUD:MSCDBMS (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)STOP:MSCDBMS (Flexent EMS/AP)


Other References:



INH:MSCDBMS-AUD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 INH MSCDBMS-RCV

ID............. INH:MSCDBMS-RCVRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Inhibits Application Processor (AP) based Recent Change / Verify (RC/V).

This command inhibits recent change processing on the APs. On successful completion ofthis command, recent change sessions will be prohibited from starting (apxrcv) andchanges to the AUTOPLEX database will be disallowed within existing sessions.Changes to the database through the Recent Change interface will be disallowed until theALW:MSCDBMS-RCV command is run successfully. Note that this command affectsapxrcv, but does not affect other database tools such as apxsub.

2. FORMAT

INH:MSCDBMS,RCV


See Purpose.

4. SYSTEM RESPONSE











Issue 28 INH:MSCDBMS-RCV-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksINH MSCDBMS-RCV August 2005

5. REFERENCES

IM/OM References:

Input MessagesALW:MSCDBMS-RCV (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)

Output MessagesINH-MSCDBMS-RCVALW-MSCDBMS-RCVOP-AP-STATUS

Other References:


apxrcv (invoked from ECP or OMP)apxsub (invoked from OMP)


INH:MSCDBMS-RCV-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 INIT AP

ID............. INIT:APRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Initialize an Application Processor (AP) at a specific initialization level.


Format 1: INIT:AP-FULL takes several minutes longer than INIT:AP-APPL but is morethorough. Note that no output messages will be displayed when the INIT:APFULL or INIT:AP APPL commands run successfully.

The AP must be in the OOS MANUAL state before running either INIT:AP-APPL or INIT:AP-FULL. After the AP is initialized, it is returned to the OOSMANUAL state.

INIT:AP-FULL is primarily used for software update. Both forms of INIT:APmay be used for certain rare errors when a reinitialization is required to recoveran AP.

Format 2: This is a 1xEV-DO message. Initialize a specified unit. This will reboot theplatform software on the AP.

2. FORMAT

[1] INIT:AP a, b

[2] INIT:AP a



b = Initialization level:

APPL — Only the Flexent /AUTOPLEX software will be reinitialized.

FULL — The entire AP, including the operating system, will beimmediately rebooted.

4. SYSTEM RESPONSE

IP = In Progress.




Issue 28 INIT:AP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksINIT AP August 2005

PF = Printout Follows. Followed by a INIT-AP output message. If the PF isfollowed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the INIT:AP command will bedelayed.








5. REFERENCES

IM/OM References:

Input MessagesRMV:APRST:APSELECT:AP

Output MessagesINIT-APRMV-APRST-APSELECT-AP

Other References:



INIT:AP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP ALARM

ID............. OP:ALARM-EMSRELEASE ....... 14.0 and laterTYPE .......... Input

1. PURPOSE

Reports alarms for all Application Processors (APs) and for the Radio Cluster Servers(RCSs), Message Mapping Applications (MMAs), Digital Signal Level 1s (DS1s), SignalingSystem 7 (SS7) links, Ethernet Interface Node Link (EINLINK), and Local Area Networks(LANs) associated with each AP.


2. FORMAT

OP:ALARM


Report the alarms that have been generated autonomously for the APs and for the RCSs,MMAs, DS1s, SS7 links, EINLINK, and LANs on each AP.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by an OP-ALARM output message.

5. REFERENCES

IM/OM References:

Input MessagesOP:AP-ALARM (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)OP:AP-VERSION (Flexent EMS/AP)OP:CELLOP:CELL-GENERIC

Output MessagesOP-ALARMOP-AP-ALARMOP-AP-STATUSOP-AP-VERSIONOP-CELLOP-CELL-GENERIC


Issue 28 OP:ALARM-EMS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP ALARM August 2005

Other References:





OP:ALARM-EMS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP AP-ALARM

ID............. OP:AP-ALARMRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Report the alarms that have been generated autonomously for the specified ApplicationProcessor (AP) and for the Radio Cluster Servers (RCSs), Message Mapping Applications(MMAs), Digital Signal Level 1s (DS1s), Signaling System 7 (SS7) links, Ethernet InterfaceNode Link (EINLINK), and Local Area Networks (LANs) associated with that AP.

2. FORMAT

OP:AP a, ALARM


a = AP number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by an OP-AP-ALARM output message.




5. REFERENCES

IM/OM References:

Input MessagesOP:ALARM-EMS (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)OP:AP-VERSION (Flexent EMS/AP)OP:CELLOP:CELL-GENERIC



Issue 28 OP:AP-ALARM-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP AP-ALARM August 2005

Other References:




OP:AP-ALARM-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP AP-CMDS

ID............. OP:AP-CMDSRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Outputs running and queued commands.

This command outputs a list of running commands and queued commands. Queuedcommands have been entered, but cannot be run until a running command completes.

2. FORMAT

OP:AP a, CMDS


a = Application Processor (AP) number (1-278).

4. SYSTEM RESPONSE











Issue 28 OP:AP-CMDS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP AP-CMDS August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)

Output MessagesOP-AP-CMDSOP-AP-STATUS

Other References:




OP:AP-CMDS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP AP-DS1-STATUS

ID............. OP:AP-DS1-STATRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Report the maintenance status of all the Digital Signal Level 1s (DS1s) on the specifiedApplication Processor (AP).

2. FORMAT

OP:AP a, DS1, STATUS


a = AP number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by an OP-AP-DS1-STAT output message.




5. REFERENCES

IM/OM References:

Input MessagesOP:ALARM-EMS (Flexent EMS/AP)OP:AP-ALARM (Flexent EMS/AP)OP:AP-DS1x-STAT (Flexent EMS/AP)OP:AP-MMA-STAT (Flexent EMS/AP)OP:AP-MMAx-STAT (Flexent EMS/AP)OP:AP-RCS-STAT (Flexent EMS/AP)OP:AP-RCSx-STAT (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)OP:AP-VERSION (Flexent EMS/AP)OP:CELL

Output MessagesOP-ALARMOP-AP-ALARMOP-AP-DS1-STATOP-AP-DS1x-STATOP-AP-MMA-STATOP-AP-MMAx-STAT


Issue 28 OP:AP-DS1-STAT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP AP-DS1-STATUS August 2005

OP-AP-RCS-STATOP-AP-RCSx-STATOP-AP-STATUSOP-AP-VERSIONOP-CELL

Other References:




OP:AP-DS1-STAT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP AP-DS1x-STATUS

ID............. OP:AP-DS1x-STATRELEASE ....... 15.0 and laterTYPE .......... Input

1. PURPOSE

Report the maintenance status of a Digital Signal Level 1s (DS1s), and the Digital SignalLevel 0s (DS0s) or Signaling System 7 (SS7) links on that DS1.

2. FORMAT

OP:AP a, DS1 b, STATUS



b = DS1 number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by OP-AP-DS1x-STAT output message.




5. REFERENCES

IM/OM References:

Input MessagesOP:ALARM-EMS (Flexent EMS/AP)OP:AP-ALARM (Flexent EMS/AP)OP:AP-DS1-STAT (Flexent EMS/AP)OP:AP-MMA-STAT (Flexent EMS/AP)OP:AP-MMAx-STAT (Flexent EMS/AP)OP:AP-RCS-STAT (Flexent EMS/AP)OP:AP-RCSx-STAT (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)OP:AP-VERSION (Flexent EMS/AP)OP:CELL

Output MessagesOP-ALARMOP-AP-ALARMOP-AP-DS1-STATOP-AP-DS1x-STATOP-AP-RCS-STAT


Issue 28 OP:AP-DS1x-STAT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP AP-DS1x-STATUS August 2005

OP-AP-RCSx-STATOP-AP-MMA-STATOP-AP-MMAx-STATOP-AP-STATUSOP-AP-VERSIONOP-CELL

Other References:




OP:AP-DS1x-STAT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP AP-INFO

ID............. OP:AP-INFORELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

This command outputs information about the Application Processor (AP) hardware type, alist of applications that can be supported on the AP and the features that are enabled onthe AP. The information is listed for the AP specified on the command line, or for all APsin the system if no AP number is entered.

2. FORMAT

OP:AP [a], INFO



4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a OP-AP-INFO output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the OP-AP-INFO commandwill be delayed.








?E = Error. The AP entered is not configured in the database.


Issue 28 OP:AP-INFO-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP AP-INFO August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)

Output MessagesOP-AP-INFOOP-AP-STATUS

Other References:



OP:AP-INFO-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP AP-INV

ID............. OP:AP-INVRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

This command outputs location information about the Application Processor (AP) whichincludes: hardware type, frame type, Ethernet Interface Node (EIN) group and member,and frame / drawer / slot numbers. If the AP is a Dedicated Network File Service (DNFS)Host AP, its satellite APs will be listed. For a satellite AP, its DNFS host and drawer hostwill be listed. If the AP is a Drawer Host, its Satellite APs will be listed. The information islisted for the AP specified on the command line, or for all APs in the system if no APnumber is entered. This information can also be requested on a per frame basis.

2. FORMAT

OP:AP [a , FRAME b], INV



b = Frame number (1-28).

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a OP-AP-INV output message. If the PF isfollowed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the OP-AP-INV command willbe delayed.










Issue 28 OP:AP-INV-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP AP-INV August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUSOP:AP-INFO

Output MessagesOP-AP-INFOOP-AP-INVOP-AP-STATUS

Other References:



OP:AP-INV-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP AP-IPBHINFO

ID............. OP:AP-IPBHINFORELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE

This command requests that the Internet Protocol Backhaul (IPBH) information bedisplayed if the Application Processor (AP) has Radio Cluster Server (RCS) InternetProtocol (IP) services enabled. This information will be for a single AP only. Therequested result will contain the IP addresses for the interfaces and for the gateways.Furthermore, a listing of each RCS that is IPBH feature enabled will be shown.

2. FORMAT

OP:AP a, IPBHINFO



4. SYSTEM RESPONSE



PF = Printout Follows. Followed by a OP-AP-IPBHINFO output message. Ifthe PF is followed by the word QUEUED, the command was queued toallow a running command to complete. Therefore, the OP-AP-IPBHINFOcommand will be delayed.









Issue 28 OP:AP-IPBHINFO-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP AP-IPBHINFO August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:AP-INFO (Flexent EMS/AP)

Output MessagesOP-AP-INFOOP-AP-IPBHINFO

Other References:



OP:AP-IPBHINFO-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP AP-MMA-STATUS

ID............. OP:AP-MMA-STATRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Report the maintenance status of all the Message Mapping Applications (MMAs) on thespecified Application Processor (AP).

2. FORMAT

OP:AP a, MMA, STATUS


a = AP number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a OP-AP-AMA-STAT output message.




5. REFERENCES

IM/OM References:

Input MessagesOP:ALARM-EMS (Flexent EMS/AP)OP:AP-ALARM (Flexent EMS/AP)OP:AP-DS1-STAT (Flexent EMS/AP)OP:AP-DS1x-STAT (Flexent EMS/AP)OP:AP-MMA-STAT (Flexent EMS/AP)OP:AP-MMAx-STAT (Flexent EMS/AP)OP:AP-RCS-STAT (Flexent EMS/AP)OP:AP-RCSx-STAT (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)OP:AP-VERSION (Flexent EMS/AP)OP:CELL

Output MessagesOP-ALARMOP-AP-ALARMOP-AP-DS1-STATOP-AP-DS1x-STATOP-AP-RCS-STAT


Issue 28 OP:AP-MMA-STAT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP AP-MMA-STATUS August 2005

OP-AP-RCSx-STATOP-AP-MMA-STATOP-AP-MMAx-STATOP-AP-STATUSOP-AP-VERSIONOP-CELL

Other References:




OP:AP-MMA-STAT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP AP-MMAx-STATUS

ID............. OP:AP-MMAx-STATRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Report the maintenance status of a Message Mapping Application (MMA), and the DigitalSignal Level 1s (DS1s) and Signaling System 7 (SS7) links on that MMA.

2. FORMAT

OP:AP a, MMA b, STATUS



b = MMA number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by OP-AP-MMAx-STAT output message.




5. REFERENCES

IM/OM References:

Input MessagesOP:ALARM-EMS (Flexent EMS/AP)OP:AP-ALARM (Flexent EMS/AP)OP:AP-DS1-STAT (Flexent EMS/AP)OP:AP-DS1x-STAT (Flexent EMS/AP)OP:AP-MMA-STAT (Flexent EMS/AP)OP:AP-RCS-STAT (Flexent EMS/AP)OP:AP-RCSx-STAT (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)OP:AP-VERSION (Flexent EMS/AP)OP:CELL


Issue 28 OP:AP-MMAx-STAT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP AP-MMAx-STATUS August 2005

Output MessagesOP-ALARMOP-AP-ALARMOP-AP-DS1-STATOP-AP-DS1x-STATOP-AP-MMA-STATOP-AP-MMAx-STATOP-AP-RCS-STATOP-AP-RCSx-STATOP-AP-STATUSOP-AP-VERSIONOP-CELL

Other References:




OP:AP-MMAx-STAT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP AP-RCS-STATUS

ID............. OP:AP-RCS-STATRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Report the maintenance status of all the Radio Cluster Servers (RCSs) on the specifiedApplication Processor (AP).

2. FORMAT

OP:AP a, RCS, STATUS


a = AP number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by an OP-AP-RCS-STAT output message.




5. REFERENCES

IM/OM References:

Input MessagesOP:ALARM-EMS (Flexent EMS/AP)OP:AP-ALARM (Flexent EMS/AP)OP:AP-DS1-STAT (Flexent EMS/AP)OP:AP-DS1x-STAT (Flexent EMS/AP)OP:AP-MMA-STAT (Flexent EMS/AP)OP:AP-MMAx-STAT (Flexent EMS/AP)OP:AP-RCSx-STAT (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)OP:AP-VERSION (Flexent EMS/AP)OP:CELL

Output MessagesOP-ALARMOP-AP-ALARMOP-AP-DS1-STATOP-AP-DS1x-STATOP-AP-MMA-STATOP-AP-MMAx-STAT


Issue 28 OP:AP-RCS-STAT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP AP-RCS-STATUS August 2005

OP-AP-RCS-STATOP-AP-RCSx-STATOP-AP-STATUSOP-AP-VERSIONOP-CELL

Other References:




OP:AP-RCS-STAT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP AP-RCSx-STATUS

ID............. OP:AP-RCSx-STATRELEASE ....... 15.0 and laterTYPE .......... Input

1. PURPOSE

Report the maintenance status of a Radio Cluster Servers (RCSs), and the Digital SignalLevel 1s (DS1s) and Digital Signal Level 0s (DS0s) on that RCS.

2. FORMAT

OP:AP a, RCS b, STATUS



b = RCS number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by an OP-AP-RCSx-STAT output message.




5. REFERENCES

IM/OM References:

Input MessagesOP:ALARM-EMS (Flexent EMS/AP)OP:AP-ALARM (Flexent EMS/AP)OP:AP-DS1-STAT (Flexent EMS/AP)OP:AP-DS1x-STAT (Flexent EMS/AP)OP:AP-MMA-STAT (Flexent EMS/AP)OP:AP-MMAx-STAT (Flexent EMS/AP)OP:AP-RCS-STAT (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)OP:AP-VERSION (Flexent EMS/AP)OP:CELL

Output MessagesOP-ALARMOP-AP-ALARMOP-AP-DS1-STATOP-AP-DS1x-STATOP-AP-MMA-STAT


Issue 28 OP:AP-RCSx-STAT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP AP-RCSx-STATUS August 2005

OP-AP-MMAx-STATOP-AP-RCS-STATOP-AP-RCSx-STATOP-AP-STATUSOP-AP-VERSIONOP-CELL

Other References:




OP:AP-RCSx-STAT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP AP-STATUS

ID............. OP:AP-STATUSRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Report the maintenance status of an Application Processor (AP), and the Home VisitorLocation Register (HVLR), Radio Cluster Servers (RCSs), Message Mapping Applications(MMAs), Digital Signal Level 1s (DS1s), Signaling System 7 (SS7) links, Ethernet InterfaceNode Link (EINLINK) and Local Area Networks (LANs) on that AP.

2. FORMAT

OP:AP a, STATUS


a = AP number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by an OP-AP-STATUS output message.




5. REFERENCES

IM/OM References:

Input MessagesOP:ALARM-EMS (Flexent EMS/AP)OP:AP-ALARM (Flexent EMS/AP)OP:AP-VERSION (Flexent EMS/AP)OP:CELLOP:CELL-GENERIC



Issue 28 OP:AP-STATUS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP AP-STATUS August 2005

Other References:




OP:AP-STATUS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP AP-VERSION

ID............. OP:AP-VERSIONRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Lists the version(s) of the software on the Application Processor (AP).


This command displays:

— The version of AP platform software running on the AP.

— The new version of AP platform software on the AP (if it exists), or the backout versionof AP platform software on the AP (if it exists). The new or backout version will existonly if a version has been installed since the last COMMIT:AP.

— The version of AP platform software selected on the AP (SELECT:AP).

— The available versions of Radio Cluster Server (RCS) software installed on the AP.

— The available versions of cell software installed on the AP.

— The selected version and running version for each RCS configured on the AP.

This is also a 1xEV-DO message. The 1xEV-DO AP provides application software versioninformation. This command displays the following application versions:

• The 1xEV-DO Controller (EVC) Application version(s) installed on the AP.

• Cell software versions installed on this AP.

• EVC Application versions, from the list of installed software, which are Selected (thenext to be activated), Current (running at the time the OP:AP-VERSION command isexecuted), and Committed.

2. FORMAT

OP:AP a, VERSION



4. SYSTEM RESPONSE

IP = In Progress.



PF = Printout Follows. Followed by an OP-AP-VERSION output message.


Issue 28 OP:AP-VERSION-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP AP-VERSION August 2005


— Maximum number of commands already running


5. REFERENCES

IM/OM References:

Input MessagesCOMMIT:APSELECT:AP


Other References:



OP:AP-VERSION-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP:RNCDB RNC

ID............. OP:RNCDBRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

This command requests a list of all Radio Network Controller (RNC) application databasebackup files for a specified RNC or all.

2. FORMAT

OP:RNCDB, RNC [a ALL]



4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a OP-RNCDB output message. If the PF isfollowed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the OP-RNCDB command willbe delayed.









Issue 28 OP:RNCDB-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP:RNCDB RNC August 2005

5. REFERENCES

IM/OM References:

Input MessagesBKUP:RNCDBCOPY:RNCDBDELBKUP:RNCDB


Other References:



OP:RNCDB-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP SS7APNET

ID............. OP:SS7APNETRELEASE ....... 23.0 and laterTYPE .......... Input

1. PURPOSE

Reports the Signaling System 7 (SS7) network level point code and subsystem status.

Use of this input command is only allowed when the High Speed SS7 Link (HSL) or LowSpeed SS7 Link (LSL) feature is activated in the Feature Activation File (FAF).

2. FORMAT

[1] OP:SS7APNET,PRTE

[2] OP:SS7APNET,ABNORM

[3] OP:SS7APNET,PRN "aaa"

[4] OP:SS7APNET,PCLU "aaabbb"

[5] OP:SS7APNET,PMEM ["aaabbbccc" "fffff"]

[6] OP:SS7APNET,STATES ["aaabbbccc" "fffff"]

[7] OP:SS7APNET,SSINFO "d"

[8] OP:SS7APNET,SSINFO ALL

[9] OP:SS7APNET,CONCERNED

[10] OP:SS7APNET,LOCPC

[11] OP:SS7APNET,SLK ["e"]


aaabbbccc = Far-End Point Code - 9-character string.

aaa = Network identifier (3 digits from 001-254).

bbb = Cluster (3 digits from 000-255).

ccc = Member number (3 digits from 000-255).

d = Subsystem number (1-254).

e = Signaling link number (3 digits, each digit 0-9).

fffff = 5-digit point code.


Issue 28 OP:SS7APNET-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP SS7APNET August 2005

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by OP-SS7APNET output message.




5. REFERENCES

IM/OM References:

Input MessagesOP:ALARM-EMS (Flexent EMS/AP)OP:AP-ALARM (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)OP:AP-VERSION (Flexent EMS/AP)OP:CELLOP:SS7x-STAT (Flexent EMS/AP)

Output MessagesOP-ALARMOP-AP-ALARMOP-AP-STATUSOP-AP-VERSIONOP-SS7x-STATOP-CELLOP-SS7APNET



OP:SS7APNET-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 OP SS7x-STATUS

ID............. OP:SS7x-STATRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Report the maintenance status of the specified Signaling System 7 High Speed Link(SS7HSL) link on that Application Processor (AP).

2. FORMAT

OP:SS7 a, STATUS


a = SS7 link number (1-384). Use the OP:AP-STATUS input message to obtainthe SS7 link number for this AP.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by OP-SS7x-STAT output message.




5. REFERENCES

IM/OM References:

Input MessagesOP:ALARM-EMS (Flexent EMS/AP)OP:AP-ALARM (Flexent EMS/AP)OP:AP-DS1-STAT (Flexent EMS/AP)OP:AP-DS1x-STAT (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)OP:AP-VERSION (Flexent EMS/AP)OP:CELL (Flexent EMS/AP)OP:SS7APNET (Flexent EMS/AP)

Output MessagesOP-ALARMOP-AP-ALARMOP-AP-DS1-STATOP-AP-DS1x-STATOP-AP-STATUSOP-AP-VERSION


Issue 28 OP:SS7x-STAT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksOP SS7x-STATUS August 2005

OP-CELLOP-SS7APNETOP-SS7x-STAT

Other References:



OP:SS7x-STAT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RESTART MMA

ID............. RESTART:MMARELEASE ....... 24.0 and laterTYPE .......... Input


**WARNING**This command will result in a loss of all calls for the IS–634 base stationassociated with the Message Mapping Application (MMA) number.

1. PURPOSE

Restart the Message Mapping Application (MMA) on both Application Processors (APs)that the MMA is associated with.

The UCL qualifier is required since this command will be service impacting.

2. FORMAT

RESTART:MMA a;UCL


a = MMA number.


4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RESTART-MMA output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RESTART:MMA commandwill be delayed.









Issue 28 RESTART:MMA-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRESTART MMA August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RST:AP (Flexent EMS/AP)RST:AP-MMA (Flexent EMS/AP)

Output MessagesOP-AP-STATUSRESTART-MMARST-APRST-AP-MMA

Other References:





RESTART:MMA-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RESTART RCS

ID............. RESTART:RCSRELEASE ....... 24.0 and laterTYPE .......... Input


**WARNING**This command always results in a stable clear of the associated cells. Allcalls on the cells will be lost. This command should be used in off–peakhours to minimize service impact.

1. PURPOSE

Restart the Radio Cluster Server (RCS) on both its primary and alternate ApplicationProcessors (APs).

This command restarts the RCS on both its primary and alternate APs. It is used duringthe Cell generic retrofit procedure to cause the RCS to restart on the version of RCSsoftware specified on the Recent Change / Verify (RC/V) cell2 form (and, if applicable,the RC/V crcseq or trcseq forms). It can also be used independently of the Cellgeneric retrofit procedure to force the RCS to stop, and then restart.

This command does not cause a switchover of the ACTIVE and STDBY RCS instances.That is, if the RCS has an ACTIVE instance on AP x and a STDBY instance on AP y beforethe command is issued, the RCS will remain ACTIVE on AP x, and STDBY on AP y afterrestarting.

If this command is invoked from the AP, it must be invoked from the AP hosting theACTIVE instance of the RCS.

2. FORMAT

RESTART:RCS a


a = RCS number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RESTART-RCS output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RESTART:RCS commandwill be delayed.


Issue 28 RESTART:RCS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRESTART RCS August 2005








5. REFERENCES

IM/OM References:

Input MessagesOP:AP-VERSION (Flexent EMS/AP)RST:AP (Flexent EMS/AP)RST:RCS (Flexent EMS/AP)

Output MessagesOP-AP-VERSIONREPT-AP-GRRCSAUDRESTART-RCSRST-APRST-RCS

Other References:




RESTART:RCS-2 Issue 28


ID............. RMV:APRELEASE ....... 24.0 and laterTYPE .......... Input


**WARNING**Radio Cluster Server (RCS) transient calls may be lost. If the UCL option isused, an attempt to save RCS stable calls will be made, but they may also belost.

If UCL is specified, the database update application will be removed fromservice even if it cannot be made primary elsewhere. This could result in acomplete loss of the ability to perform database Recent Changes.

If the UCL option is used and Voice Channel Administration (VCA) cannotbe switched over to the mate Application Processor (AP), execution of thiscommand will result in the loss of the ability to complete new calls.

If the UCL option is used and this AP has the last ACTIVE Home VisitorLocation Register (HVLR), the removal of this application will result in aloss of call processing.

If the UCL option is used and this AP hosts the last ACTIVE HVLR IntegrityManager (HVLR-

IM), the removal of this application will prevent HVLRfrom successfully reinitializing. Also the Technician Interface (TI)commands backup:db and copy:db cannot be run.

If the UCL option is used and the last ACTIVE Signaling System 7 (SS7) linkin a linkset is removed, all calls for the IS634 base station associated with thelinkset will be lost.

If the UCL option is used and this AP has the last active Signaling System 7High Speed Link (SS7HSL) in a link set, the SS7HSL will become OOSMANUAL and the linkset will become OOS FAULT resulting in the loss of allservice to the associated base station.

If the last active Signaling System 7 Message Manager (SS7MM) applicationis running on this AP, the use of the UCL option will result in the removal ofthe SS7MM application from service and the complete loss of the ability toprocess SS7 messages.

1. PURPOSE

Remove the specified Application Processor (AP), including any applications andresources associated with the AP, from service. Successful completion of this commandresults in the AP and its associated applications and resources transitioning to the OOSMANUAL state. A list of the resources and applications associated with an AP can bedetermined by executing the OP:AP-STATUS command.


Issue 28 RMV:AP-1



Applications and resources are removed from service in turn. Attempts to switchovermated applications running in an active state or with a primary update role will be madefor both conditional or unconditional removes. If the remove is conditional, a failure toremove or successfully switchover any application or the failure to remove a singleresource will result in the failure of the AP remove command. Any component that isremoved before the command fails will remain OOS MANUAL and will need to be restoredmanually. If the AP remove command is unconditional (UCL option) it will not be failed ifany application or resource fails to be removed.

Attempts will be made to switchover stable calls on each RCS to the mate RCS, but the UCLoption doesn’t require that the mate RCS be ACTIVE so that stable calls are not guaranteedto be maintained for unconditional AP removes.

Message Mapping Applications (MMAs) must be in the inhibited state (OP:AP-STATUS,INH:AP-MMA) before they may be removed under a conditional AP remove command.There must be an active SS7 link on the mate AP before the links may be removed under aconditional AP remove command.

While the AP is OOS MANUAL, some commands may still be accepted (such as RST:AP).

This is also a 1xEV-DO message. Remove a specified AP from service. Adding theoptional argument UCL has the same effect as if no argument is supplied. That is, there isno conditional remove.

2. FORMAT

[1] RMV:AP a [;UCL]

[2] RMV:AP a




4. SYSTEM RESPONSE

IP = In Progress.



PF = Printout Follows. Followed by a RMV-AP output message. If the PF isfollowed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RMV-AP command will bedelayed.


RMV:AP-2 Issue 28









5. REFERENCES

IM/OM References:

Input MessagesALW:AP-MMA (Flexent EMS/AP)INH:AP-MMA (Flexent EMS/AP)INIT:APOP:ALARM-EMS (Flexent EMS/AP)OP:AP-ALARM (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)OP:CELLOP:CELL-GENERICRESTART:AP-HVLRIM (Flexent EMS/AP)RMV:AP-DS1 (Flexent EMS/AP)RMV:AP-HVLR (Flexent EMS/AP)RMV:AP-MMA (Flexent EMS/AP)RMV:AP-MSCDBMS (Flexent EMS/AP)RMV:AP-ROP (Flexent EMS/AP)RMV:AP-SP (Flexent EMS/AP)RMV:AP-SS7 (Flexent EMS/AP)RMV:AP-SS7MM (Flexent EMS/AP)RMV:AP-VCA (Flexent EMS/AP)RMV:RCS (Flexent EMS/AP)RMV:SS7 (Flexent EMS/AP)RST:APRST:AP-DS1 (Flexent EMS/AP)RST:AP-HVLR (Flexent EMS/AP)RST:AP-MMA (Flexent EMS/AP)RST:AP-MSCDBMS (Flexent EMS/AP)RST:AP-ROP (Flexent EMS/AP)RST:AP-SP (Flexent EMS/AP)RST:AP-SS7 (Flexent EMS/AP)


Issue 28 RMV:AP-3


RST:AP-SS7MM (Flexent EMS/AP)RST:AP-VCA (Flexent EMS/AP)RST:RCS (Flexent EMS/AP)RST:SS7 (Flexent EMS/AP)

Output MessagesALW-AP-MMAINH-AP-MMAINIT-APOP-ALARMOP-AP-ALARMOP-AP-STATUSOP-CELLOP-CELL-GENERICRESTART:AP-HVLRIMRMV-APRMV-AP-DS1RMV-AP-HVLRRMV-AP-MMARMV-AP-MSCDBMSRMV-AP-ROPRMV-AP-SPRMV-AP-SS7RMV-AP-SS7MMRMV-AP-VCARMV-RCSRMV-SS7RST-APRST-AP-DS1RST-AP-HVLRRST-AP-MMARST-AP-MSCDBMSRST-AP-ROPRST-AP-SPRST-AP-SS7RST-AP-SS7MMRST-AP-VCARST-RCSRST-SS7

Other References:





RMV:AP-4 Issue 28



apoffline (invoked from AP UNIX login)aponline (invoked from AP UNIX login)


Issue 28 RMV:AP-5




RMV:AP-6 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RMV:AP-AMA

ID............. RMV:AP-AMARELEASE ....... 25.0 and laterTYPE .......... Input


**WARNING**Use of the UCL option on this command may result in a loss of AutomaticMessage Accounting information.

1. PURPOSE

This command removes the Application Processor (AP) Automatic Message Accounting(AMA) application from service. If this is the last active AP AMA application in thesystem and the UCL parameter is not specified, this command will fail. If UCL is specified,the AMA application will be removed from service even if there are no other active AMAapplications in the system. This will result in loss of AMA call records. On successfulcompletion of this command, AMA will be in the OOS-MANUAL state.

2. FORMAT

RMV:AP a,AMA [;UCL]


a = AP number.


4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RMV-AP-AMA output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RMV-AP-AMA commandwill be delayed.







Issue 28 RMV:AP-AMA-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRMV:AP-AMA August 2005



5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUSRST:AP-AMASWITCHOVER:AMA

Output MessagesOP-AP-STATUSRMV-AP-AMARST-AP-AMASWITCHOVER-AP-AMA

Other References:



RMV:AP-AMA-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RMV:AP-AMATPS

ID............. RMV:AP-AMATPSRELEASE ....... 25.0 and laterTYPE .......... Input


**WARNING**Use of the UCL option on this command may result in a loss of AutomaticMessage Accounting information.

1. PURPOSE

This command removes the Application Processor (AP) Automatic Message AccountingTeleprocessing System (AMATPS) application from service. If this is the last active APAMATPS application in the system and the UCL parameter is not specified, this commandwill fail. If UCL is specified, the AMATPS application will be removed from service even ifthere are no other active AMATPS applications in the system. This will result in loss ofAMA call records. On successful completion of this command, AMATPS will be in theOOS-MANUAL state.

2. FORMAT

RMV:AP a,AMATPS [;UCL]


a = AP number.


4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RMV-AP-AMATPS output message. If thePF is followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RMV-AP-AMATPScommand will be delayed.







Issue 28 RMV:AP-AMATPS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRMV:AP-AMATPS August 2005



5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUSRST:AP-AMATPSSWITCHOVER:AMATPS

Output MessagesOP-AP-STATUSRMV-AP-AMATPSRST-AP-AMATPSSWITCHOVER-AP-AMATPS

Other References:



RMV:AP-AMATPS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RMV AP-DS1

ID............. RMV:AP-DS1RELEASE ....... 24.0 and laterTYPE .......... Input


**WARNING**Use of the UCL option may result in loss of calls. If the Digital Signal Level 1(DS1) is configured with the Link Access Procedure D–Channel (LAPD) orAsynchronous Transfer Mode (ATM) protocol and has RCSs associated withit, transient calls may be lost. An attempt will be made to save stable callson the Radio Cluster Servers (RCSs), but they may also be lost.

If the DS1 is configured with the Signaling System 7 (SS7) protocol, all of itsassociated SS7 links will be removed from service. If any of the removedSS7 links were the last active link in their linkset, the linkset and the MMAson both Application Processors (APs) associated with the linkset will betaken out of service, resulting in loss of all calls.

If the DS1 is configured with the Signaling System 7 High Speed Link(SS7HSL) or Signaling System 7 Low Speed Link (SS7LSL) protocol, all of itsassociated SS7 links will be removed from service. If any of the removedSS7 links were the last active link in their linkset, the linkset will be takenout of service, resulting in loss of all messaging to the signaling end point.

1. PURPOSE

Format 1: Removes the DS1 from service.

Format 2: Removes the Digital Signal Level 0 (DS0) from service.

If the DS1 is configured with the LAPD or ATM protocol, any RCSs associated with it areremoved from service. If the DS1 is configured with the SS7, SS7HSL, or SS7LSL protocol,any SS7 links associated with it are removed from service.

If the specified DS1 is configured with the LAPD or ATM protocol, the DS1 will beremoved from service, and attempts will be made to gracefully switchover its associatedRCSs before removing the RCSs and the DS1 from service. Successful completion of thecommand results in the DS1 and all of its associated RCSs being placed in the OOSMANUAL state.

If any RCSs fail to be removed during the conditional removal of a LAPD or ATM DS1, theDS1 will not be removed and removal of subsequent RCSs will not be attempted. AnyRCSs already removed before the command fails will remain OOS MANUAL.

If an RCS cannot be removed during the unconditional removal of a LAPD or ATM DS1,the command will continue with the next RCS associated with the DS1, removing as manyRCSs as possible. The DS1 will then be removed, and RCSs that were not successfullyremoved will be placed in the OOS FAULT state. Although attempts are made toswitchover stable calls to the mate RCS, the calls are not guaranteed to be maintained. TheUCL option does not require that the mate RCS be in service.


Issue 28 RMV:AP-DS1-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRMV AP-DS1 August 2005

If the DS1 is configured with the SS7, SS7HSL, or SS7LSL protocol, the DS1 will beremoved from service and attempts will be made to remove the SS7 links associated withthe DS1. Successful completion of the command results in the DS1 and all of its associatedSS7 links being placed in the OOS MANUAL state. All SS7 links that were already OOSMANUAL will not be affected.

If any SS7 link fails to be removed during the conditional removal of a SS7 DS1, the DS1will not be removed, and the remaining links on the DS1 will not be removed. Theconditional removal will be failed if an attempt is made to remove a SS7 link that is the lastlink in service in a linkset. Any SS7 links already removed before the command fails willremain OOS MANUAL.

If a SS7 link cannot be removed during the unconditional removal of a SS7 DS1, thecommand will continue with the next SS7 link associated with the DS1, removing as manylinks as possible and finally removing the DS1 itself. The UCL option will force theremoval of any SS7 links on the DS1 that are the last links in service in a linkset.

If the DS1 is configured with the SS7 protocol and the SS7 link is the last link in the linkset,MMAs on both APs associated with the linkset will be placed in the OOS FAULT state andall calls will be lost.

2. FORMAT

[1] RMV:AP a, DS1 b [; UCL ]

[2] RMV:AP a, DS1 b, DS0 c


a = AP number.

b = DS1 number.



4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RMV-AP-DS1 output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RMV-AP-DS1 message willbe delayed.





RMV:AP-DS1-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RMV AP-DS1





5. REFERENCES

IM/OM References:

Input MessagesCFR:AP-DS1 (Flexent EMS/AP)CFR:AP-SS7 (Flexent EMS/AP)CFR:SS7 (Flexent EMS/AP)DGN:AP-DS1 (Flexent EMS/AP)OP:ALARM-EMS (Flexent EMS/AP)OP:ALARM (Flexent EMS/AP)OP:AP-ALARM (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)OP:CELLOP:CELL-GENERICOP:CELL-MICRORMV:AP (Flexent EMS/AP)RMV:AP-SS7 (Flexent EMS/AP)RMV:RCS (Flexent EMS/AP)RST:AP (Flexent EMS/AP)RST:AP-DS1 (Flexent EMS/AP)RST:AP-MMA (Flexent EMS/AP)RST:AP-SS7 (Flexent EMS/AP)RST:RCS (Flexent EMS/AP)

Output MessagesCFR-AP-DS1CFR-AP-SS7CFR-SS7DGN-AP-DS1OP-ALARMOP-AP-ALARMOP-AP-STATUSOP-CELLOP-CELL-GENERICOP-CELL-MICRORMV-APRMV-AP-DS1RMV-AP-SS7RMV-RCS


Issue 28 RMV:AP-DS1-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksRMV AP-DS1 August 2005

RST-APRST-AP-DS1RST-AP-SS7RST-RCS

Other References:





RMV:AP-DS1-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RMV:AP-HVLR

ID............. RMV:AP-HVLRRELEASE ....... 24.0 and laterTYPE .......... Input


**WARNING**Use of the UCL option on this command may result in a loss of callprocessing.

1. PURPOSE

This command removes the Application Processor (AP) Home Visitor Location Register(HVLR) from service. If this is the last active AP HVLR application in the system and theUCL parameter is not specified, this command will fail. If UCL is specified, the HVLRapplication will be removed from service even if there are no other active HVLRapplications in the system. This could result in a loss of call processing. On successfulcompletion of this command, HVLR will be in the OOS-MANUAL state.

2. FORMAT

RMV:AP a,HVLR [;UCL]


a = AP number.


4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RMV-AP-HVLR output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RMV-AP-HVLR commandwill be delayed.







Issue 28 RMV:AP-HVLR-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRMV:AP-HVLR August 2005



5. REFERENCES

IM/OM References:

Input MessagesALW:AP-HVLR (Flexent EMS/AP)INH:AP-HVLR (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)RST:AP-HVLR (Flexent EMS/AP)

Output MessagesALW-AP-HVLRINH-AP-HVLROP-AP-STATUSRMV-AP-HVLRRST-AP-HVLR

Other References:


401-710-204 Mobility Manager Home Visitor Location Register (MM-HVLR) Operations,Administration, and Maintenance (OA&M) Guide


RMV:AP-HVLR-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RMV:AP-HVLRIM

ID............. RMV:AP-HVLRIMRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

This command removes the Application Processor (AP) Home Visitor Location RegisterIntegrity Manager (HVLR-IM) application from service. If the AP HVLR-IM applicationon the specified AP is in the ACTIVE state and the mate AP HVLR-IM application is not inthe STBY state and the UCL parameter is not specified, this command will fail. If UCL isspecified, the AP HVLR-IM application will be removed from service even if there are noother active AP HVLR-IM applications in the system. On successful completion of thiscommand, the AP HVLR-IM application will be in the OOS-MANUAL state.

2. FORMAT

RMV:AP a, HVLRIM [;UCL]


a = AP number.


4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RMV-AP-HVLRIM output message. If thePF is followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RMV-AP-HVLRIMcommand will be delayed.









Issue 28 RMV:AP-HVLRIM-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRMV:AP-HVLRIM August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RMV:AP (Flexent EMS/AP)RST:AP (Flexent EMS/AP)RST:AP-HVLRIM (Flexent EMS/AP)SWITCHOVER:HVLRIM (Flexent EMS/AP)

Output MessagesOP-AP-STATUSRMV-APRMV-AP-HVLRIMRST-APRST-AP-HVLRIMSWITCHOVER-HVLRIM

Other References:




RMV:AP-HVLRIM-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RMV AP-MMA

ID............. RMV:AP-MMARELEASE ....... 14.0 and laterTYPE .......... Input


**WARNING**If the UCL option is used, the Message Mapping Application (MMA)instance is removed from service on the Application Processor (AP)regardless of whether it has calls in progress (including emergency 911 calls)or the mate MMA is in service. Use of the UCL option when the mate MMAis not in service will result in the loss of all calls to the IS634 Base Station.

1. PURPOSE

Removes the specified Message Mapping Application (MMA) from service on thedesignated Application Processor (AP).

This command removes the MMA instance to the OOS MANUAL state on the designatedAP. Without the UCL option, the MMA will only be removed if it is in the inhibited state(OP:AP-STATUS, INH:AP-MMA, ALW:AP-MMA). The MMA will be in the inhibited stateafter:

— an INH:AP-MMA command has been executed

— there are no emergency 911 calls active for this MMA instance

— the number of non-emergency calls has dropped below the threshold specified on theRC/V bsconfig form.

If the UCL option is used, the MMA instance is removed from service on the AP regardlessof whether it has calls in progress (including emergency 911 calls) or the mate MMA is inservice.

2. FORMAT

RMV:AP a, MMA b[; UCL]


a = AP number.

b = MMA number.


4. SYSTEM RESPONSE



Issue 28 RMV:AP-MMA-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRMV AP-MMA August 2005

PF = Printout Follows. Followed by a RMV-AP-MMA output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RMV:AP-MMA commandwill be delayed.








5. REFERENCES

IM/OM References:

Input MessagesALW:AP-MMA (Flexent EMS/AP)INH:AP-MMA (Flexent EMS/AP)RMV:AP (Flexent EMS/AP)RST:AP-MMA (Flexent EMS/AP)

Output MessagesALW-AP-MMAINH-AP-MMARMV-APRMV-AP-MMARST-AP-MMA

Other References:





RMV:AP-MMA-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RMV AP-MSCDBMS

ID............. RMV:AP-MSCDBMSRELEASE ....... 24.0 and laterTYPE .......... Input


**WARNING**Use of the UCL option on this command may result in a complete loss of theability to perform database Recent Changes.

1. PURPOSE

Removes Application Processor (AP) database update application from service.

This command removes the AP database update application from service. If the databaseupdate role is primary on the specified AP, then the update application will be switchedover to another AP (The equivalent of SWITCHOVER:MSCDBMS will be performed) whereits role will become primary. If the database update application cannot become primaryon another AP and the UCL parameter is not specified, this command will fail. If UCL isspecified, the database update application will be removed from service even if it cannot bemade primary elsewhere. This could result in a complete loss of the ability to performdatabase Recent Changes. On successful completion of this command the MobileSwitching Center Database Management System (MSCDBMS) managed object will be inthe OOS-MANUAL state and the database update role will be none.

2. FORMAT

RMV:AP a,MSCDBMS[;UCL]


a = AP number.


4. SYSTEM RESPONSE







Issue 28 RMV:AP-MSCDBMS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRMV AP-MSCDBMS August 2005





5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RST:AP-MSCDBMS (Flexent EMS/AP)SWITCHOVER:MSCDBMS (Flexent EMS/AP)

Output MessagesOP-AP-STATUSRMV-AP-MSCDBMSRST-AP-MSCDBMSSWITCHOVER-MSCDBMS

Other References:



RMV:AP-MSCDBMS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RMV:AP-OAMPROXY

ID............. RMV:AP-OAMPROXYRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Removes an Application Processor (AP) Operations, Administration and MaintenanceProxy (OAMPROXY) application from service.

If this is the last active AP OAMPROXY application in the system and the UCL parameter isnot specified, this command will fail. If UCL is specified, the OAMPROXY application willbe removed from service even if there are no other active OAMPROXY applications in thesystem. On successful completion of this command, OAMPROXY will be in the OOS-MANUAL state.

2. FORMAT

RMV:AP a,OAMPROXY [;UCL]


a = AP number.


4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RMV-AP-OAMPROXY output message. Ifthe PF is followed by the word QUEUED, the command was queued toallow a running command to complete. Therefore, the RMV-AP-OAMPROXY command will be delayed.







Issue 28 RMV:AP-OAMPROXY-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRMV:AP-OAMPROXY August 2005



5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RST:AP-OAMPROXY (Flexent EMS/AP)SWITCHOVER:OAMPROXY (Flexent EMS/AP)

Output MessagesOP-AP-STATUSRMV-AP-OAMPROXYRST-AP-OAMPROXYSWITCHOVER-OAMPROXY

Other References:



RMV:AP-OAMPROXY-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RMV:AP-SP

ID............. RMV:AP-SPRELEASE ....... 24.0 and laterTYPE .......... Input


**WARNING**Use of the UCL option on this command may result in a complete loss ofStatus Display Pages in the system.

1. PURPOSE

Removes an Application Processor (AP) Status Display Process (SP) application fromservice.

This command removes the AP SP application from service. An attempt to switchover theSP application running in an active state will be made for both conditional orunconditional removes. If SP cannot be switched over to the mate AP and the UCLparameter is not specified, this command will fail. If UCL is specified, the SP applicationwill be removed from service even if the SP cannot be switched over to the mate AP. Onsuccessful completion of this command, SP will be in the OOS-MANUAL state on thespecified AP.

2. FORMAT

RMV:AP a,SP [;UCL]


a = AP number.


4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RMV-AP-SP output message. If the PF isfollowed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RMV-AP-SP command willbe delayed.





Issue 28 RMV:AP-SP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRMV:AP-SP August 2005





5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RST:AP-SP (Flexent EMS/AP)SWITCHOVER:SP (Flexent EMS/AP)

Output MessagesOP-AP-STATUSRMV-AP-SPRST-AP-SPSWITCHOVER-SP

Other References:



RMV:AP-SP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RMV AP SS7MM

ID............. RMV:AP-SS7MMRELEASE ....... 24.0 and laterTYPE .......... Input


**WARNING**Use of the UCL option on this command may result in a complete loss of theability to process Signaling System 7 (SS7) messages.

1. PURPOSE

Remove Application Processor (AP) Signaling System 7 Message Manager (SS7MM)application from service.

This command removes the AP SS7MM application from service. If this is the last activeAP SS7 message manager application in the system and the UCL parameter is not specified,this command will fail. If UCL is specified, the SS7MM application will be removed fromservice even if there are no other active SS7MM applications in the system. This couldresult in a complete loss of the ability to process SS7 messages. On successful completionof this command, SS7MM will be in the OOS-MANUAL state.

2. FORMAT

RMV:AP a,SS7MM[;UCL]


a = AP number.


4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RMV-AP-SS7MM output message. If thePF is followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RMV-AP-SS7MM commandwill be delayed.





Issue 28 RMV:AP-SS7MM-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRMV AP SS7MM August 2005





5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RMV:AP-SS7MM (Flexent EMS/AP)RST:AP-SS7MM (Flexent EMS/AP)

Output MessagesOP-AP-STATUSRMV-AP-SS7MMRST-AP-SS7MM

Other References:



RMV:AP-SS7MM-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RMV:AP-TCS

ID............. RMV:AP-TCSRELEASE ....... 24.0 and laterTYPE .......... Input


**WARNING**If UCL is specified, the Traffic Control Server (TCS) application will beremoved from service even if it cannot be made ACTIVE on the mateApplication Processor (AP). This could result in a complete loss of theability to complete new calls.

1. PURPOSE

Removes the Application Processor (AP) Traffic Control Server (TCS) application fromservice.

On successful completion of this command the TCS application will be in the OOS-MANUALstate. An attempt to switchover the TCS application running in an active state will bemade for both conditional or unconditional removes. If TCS cannot be switched over tothe mate AP and the UCL parameter is not specified, this command will fail. If UCL isspecified, the TCS application will be removed from service even if the TCS cannot beswitched over to the mate AP.

2. FORMAT

RMV:AP a,TCS b [;UCL]


a = AP number.

b = TCS number.


4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RMV-AP-TCS output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RMV-AP-TCS commandwill be delayed.





Issue 28 RMV:AP-TCS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRMV:AP-TCS August 2005





5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RST:AP-TCS (Flexent EMS/AP)SWITCHOVER:TCS (Flexent EMS/AP)

Output MessagesOP-AP-STATUSRMV-AP-TCSRST-AP-TCSSWITCHOVER-TCS

Other References:



RMV:AP-TCS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RMV:AP-TPUGUI

ID............. RMV:AP-TPUGUIRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Removes an Application Processor (AP) Traffic Processing Unit Graphical User Interface(TPUGUI) application from service.

If this is the last active AP TPUGUI application in the system and the UCL parameter is notspecified, this command will fail. If UCL is specified, the TPUGUI application will beremoved from service even if there are no other active TPUGUI applications in the system.On successful completion of this command, TPUGUI will be in the OOS-MANUAL state.

2. FORMAT

RMV:AP a,TPUGUI [;UCL]


a = AP number.


4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RMV-AP-TPUGUI output message. If thePF is followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RMV-AP-TPUGUIcommand will be delayed.







Issue 28 RMV:AP-TPUGUI-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRMV:AP-TPUGUI August 2005



5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RST:AP-TPUGUI (Flexent EMS/AP)SWITCHOVER:TPUGUI (Flexent EMS/AP)

Output MessagesOP-AP-STATUSRMV-AP-TPUGUIRST-AP-TPUGUISWITCHOVER-TPUGUI

Other References:



RMV:AP-TPUGUI-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RMV:AP-VCA

ID............. RMV:AP-VCARELEASE ....... 24.0 and laterTYPE .......... Input


**WARNING**If UCL is specified, the Voice Channel Administration (VCA) application willbe removed from service even if it cannot be made ACTIVE on the mate AP.This could result in a complete loss of the ability to complete new calls.

1. PURPOSE

Removes the Application Processor (AP) Voice Channel Administration (VCA) applicationfrom service.

This command removes the Application Processor (AP) Voice Channel Administration(VCA) application from service. On successful completion of this command the VCAapplication will be in the OOS-MANUAL state. An attempt to switchover the VCAapplication running in an active state will be made for both conditional or unconditionalremoves. If VCA cannot be switched over to the mate AP and the UCL parameter is notspecified, this command will fail. If UCL is specified, the VCA application will be removedfrom service even if the VCA cannot be switched over to the mate AP.

2. FORMAT

RMV:AP a,VCA [;UCL]


a = AP number.


4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RMV-AP-VCA output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RMV-AP-VCA commandwill be delayed.





Issue 28 RMV:AP-VCA-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRMV:AP-VCA August 2005





5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RST:AP-VCA (Flexent EMS/AP)SWITCHOVER:VCA (Flexent EMS/AP)

Output MessagesOP-AP-STATUSRMV-AP-VCARST-AP-VCASWITCHOVER-VCA

Other References:



RMV:AP-VCA-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RMV RCS

ID............. RMV:RCSRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Removes the specified Radio Cluster Server (RCS) from service.

This command removes the RCS from service on both the primary and alternateApplication Processors (APs) assigned to this RCS along with its associated signaling links.This command can only be executed in the unconditional mode.

2. FORMAT

RMV:RCS a; UCL


a = RCS number.


4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RMV-RCS output message. If the PF isfollowed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RMV:RCS command will bedelayed.









Issue 28 RMV:RCS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRMV RCS August 2005

5. REFERENCES

IM/OM References:

Input MessagesRMV:AP (Flexent EMS/AP)RMV:AP-DS1 (Flexent EMS/AP)RMV:CELLRST:RCS (Flexent EMS/AP)

Output MessagesREPT-AP-APPLNKURMV-APRMV-AP-DS1RMV-CELLRMV-RCSRST-RCS

Other References:



RMV:RCS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RMV SS7

ID............. RMV:SS7RELEASE ....... 24.0 and laterTYPE .......... Input


**WARNING**If the UCL option is used to unconditionally remove the last ACTIVESignaling System 7 Link (SS7–LINK) or Signaling System 7 MessageManager Application (SS7MMA) in a linkset, the linkset will become OOSFAULT resulting in loss of all messaging to the associated signaling endpoint.

1. PURPOSE

Removes the specified high speed or low speed SS7-LINK or SS7MMA link from service.

Remove the specified high speed or low speed SS7-LINK or SS7MMA link from service onthe Application Processor (AP). If the link is the last ACTIVE link in its linkset, thecommand will fail unless the UCL option is specified. If a linkset’s last ACTIVE link isremoved, the linkset will become OOS FAULT resulting in loss of all messaging to theassociated signaling end point. Removing an SS7-LINK or SS7MMA from service does notaffect the state of the Digital Signal Level 1 (DS1) it is associated with.

2. FORMAT

RMV:SS7 a[; UCL]


a = SS7-LINK or SS7MMA number (1-512).


4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RMV-SS7 output message. If the PF isfollowed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RMV:SS7 command will bedelayed.





Issue 28 RMV:SS7-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRMV SS7 August 2005





5. REFERENCES

IM/OM References:

Input MessagesOP:ALARM-EMS (Flexent EMS/AP)OP:AP-ALARM (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)OP:SS7x-STAT (Flexent EMS/AP)OP:SS7APNETRMV:AP (Flexent EMS/AP)RMV:AP-DS1 (Flexent EMS/AP)RST:AP (Flexent EMS/AP)RST:AP-DS1 (Flexent EMS/AP)RST:SS7 (Flexent EMS/AP)

Output MessagesOP-ALARMOP-AP-ALARMOP-AP-STATUSOP-SS7x-STATOP-SS7APNETRMV-APRMV-AP-DS1RMV-SS7RST-APRST-AP-DS1RST-SS7

Other References:



RMV:SS7-2 Issue 28


ID............. RST:APRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Restores an Application Processor (AP) and any resources and applications associated withthat AP to service.


On successful completion of the command, the AP and all its associated resources andapplications will be ACTIVE. A list of the resources and applications associated with anAP can be determined by executing the OP:AP-STATUS command. Each matedapplication will be brought to the ACTIVE or STBY state depending on the state of theapplication on the mate AP. If the application is ACTIVE on the mate AP, it will bebrought to the STBY state on this AP. If the application is not ACTIVE on the mate AP, theapplication will be brought to the ACTIVE state on this AP.

Each non-mated (simplex) application will be brought to the active state.

Each Radio Cluster Server (RCS) that is made ACTIVE will begin stable clearing the cells,and it will be a few minutes before the cells can process calls. If an RCS is OOS MANUAL onboth of its associated APs before the AP restore command is issued, that RCS will not berestored to service since it is assumed that the technician manually removed that RCS fromservice (RMV:RCS) and it should not be automatically restored. The RCS should bemanually restored to service if desired (RST:RCS).

The Mobile Switching Center Database Management System (MSCDBMS) updateapplication is restored to the ACTIVE maintenance state on each AP where it is running.The MSCDBMS update role is assigned to be primary and secondary on the AP pair whereit is executing. The MSCDBMS update application will be assigned the primary updaterole if the MSCDBMS update role is not primary on the mate AP. The MSCDBMS updateapplication will be assigned the secondary update role if the MSCDBMS update role isprimary on the mate AP.

The Message Mapping Application (MMA) is a mated application that runsACTIVE/ACTIVE on the AP pair. Each MMA application instance will be brought to theACTIVE state as a result of the successful execution of this command.

This is also a 1xEV-DO message.

2. FORMAT

RST:AP a




Issue 28 RST:AP-1


4. SYSTEM RESPONSE

IP = In Progress.



PF = Printout Follows. Followed by a RST-AP output message. If the PF isfollowed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RST-AP command will bedelayed.








5. REFERENCES

IM/OM References:

Input MessagesINIT:APOP:ALARM-EMS (Flexent EMS/AP)OP:AP-ALARM (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)OP:CELLOP:CELL-GENERICRESTART:AP-HVLRIM (Flexent EMS/AP)RMV:APRMV:AP-DS1 (Flexent EMS/AP)RMV:AP-HVLR (Flexent EMS/AP)RMV:AP-MMA (Flexent EMS/AP)RMV:AP-MSCDBMS (Flexent EMS/AP)RMV:AP-ROP (Flexent EMS/AP)RMV:AP-SP (Flexent EMS/AP)RMV:AP-SS7 (Flexent EMS/AP)RMV:AP-SS7MM (Flexent EMS/AP)


RST:AP-2 Issue 28


RMV:AP-VCA (Flexent EMS/AP)RMV:RCS (Flexent EMS/AP)RMV:SS7 (Flexent EMS/AP)RST:AP-DS1 (Flexent EMS/AP)RST:AP-HVLR (Flexent EMS/AP)RST:AP-MMA (Flexent EMS/AP)RST:AP-MSCDBMS (Flexent EMS/AP)RST:AP-ROP (Flexent EMS/AP)RST:AP-SP (Flexent EMS/AP)RST:AP-SS7 (Flexent EMS/AP)RST:AP-SS7MM (Flexent EMS/AP)RST:AP-VCA (Flexent EMS/AP)RST:RCS (Flexent EMS/AP)RST:SS7 (Flexent EMS/AP)

Output MessagesINIT-APOP-ALARMOP-AP-ALARMOP-AP-STATUSOP-CELLOP-CELL-GENERICRESTART-AP-HVLRIMRMV-APRMV-AP-DS1RMV-AP-HVLRRMV-AP-MMARMV-AP-MSCDBMSRMV-AP-ROPRMV-AP-SPRMV-AP-SS7RMV-AP-SS7MMRMV-AP-VCARMV-RCSRMV-SS7RST-APRST-AP-DS1RST-AP-HVLRRST-AP-MMARST-AP-MSCDBMSRST-AP-ROPRST-AP-SPRST-AP-SS7RST-AP-SS7MMRST-AP-VCARST-RCSRST-SS7


Issue 28 RST:AP-3


Other References:







RST:AP-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RST:AP-AMA

ID............. RST:AP-AMARELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE

This command restores an Application Processor (AP) Automatic Message Accounting(AMA) application to service. On successful completion of this command, AMAapplication will be in the ACTIVE maintenance state.

2. FORMAT

RST:AP a, AMA


a = AP number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RST-AP-AMA output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RST-AP-AMA commandwill be delayed.









Issue 28 RST:AP-AMA-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRST:AP-AMA August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUSRMV:AP-AMASWITCHOVER:AMA

Output MessagesRMV-AP-AMARST-AP-AMASWITCHOVER-AP-AMA

Other References:



RST:AP-AMA-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RST:AP-AMATPS

ID............. RST:AP-AMATPSRELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE

This command restores an Application Processor (AP) Automatic Message AccountingTeleprocessing System (AMATPS) application to service. On successful completion of thiscommand, AMATPS application will be in the ACTIVE maintenance state.

2. FORMAT

RST:AP a, AMATPS


a = AP number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RST-AP-AMATPS output message. If thePF is followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RST-AP-AMATPScommand will be delayed.









Issue 28 RST:AP-AMATPS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRST:AP-AMATPS August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUSRMV:AP-AMATPSSWITCHOVER:AMATPS

Output MessagesOP-AP-STATUSRMV-AP-AMATPSRST-AP-AMATPSSWITCHOVER-AP-AMATPS

Other References:



RST:AP-AMATPS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RST AP-DS1

ID............. RST:AP-DS1RELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Restores a Digital Signal Level 1 (DS1) to the ACTIVE state. If the DS1 is configured for theLink Access Procedure D–Channel (LAPD) or Asynchronous Transfer Mode (ATM)protocol, its associated Radio Cluster Servers (RCSs), Digital Signal Level 0 (DS0s), andsignaling links will also be restored to the ACTIVE state. If the DS1 is configured for theSignaling System 7 (SS7), Signaling System 7 High Speed Link (SS7HSL) or SignalingSystem 7 Low Speed Link (SS7LSL) protocol, its associated SS7 link(s) will also be restoredto the ACTIVE state.

If the specified DS1 is configured for the LAPD or ATM protocol, the DS1 will be madeACTIVE. RCSs associated with the DS1 are restored to ACTIVE if their mate RCS is notACTIVE; otherwise they are restored to STBY. The DS0s and signaling links associatedwith the DS1 are also restored to ACTIVE, and the ACTIVE RCSs begin stable clearing thecells. A few minutes afterwards the cells can process calls. If both an RCS and its mate arein the OOS MANUAL state as a result of a RMV-RCS;UCL command, they will remain OOSMANUAL when the DS1 is restored and must be manually restored using the RST:RCScommand.

If the specified DS1 is configured for the SS7 protocol, the DS1 will be made ACTIVE, andits associated SS7 links will be restored to the ACTIVE state. SS7 links in loopback willhave their loopback state cleared before being made ACTIVE. If a restored SS7 link is thefirst link in its linkset to be made ACTIVE, and if the associated Message MappingApplication (MMA) on either or both Application Processors (APs) are OOS FAULT, anattempt will be made to bring the MMA(s) to the ACTIVE state.

If the specified DS1 is configured for the SS7HSL or SS7LSL protocol, the DS1 will be madeACTIVE, and its associated SS7 links will be restored to the ACTIVE state. SS7 links inloopback will have their loopback state cleared before being made ACTIVE.

2. FORMAT

RST:AP a, DS1 b [, DS0 c ] [; UCL ]


a = AP number.

b = DS1 number.


4. SYSTEM RESPONSE



Issue 28 RST:AP-DS1-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRST AP-DS1 August 2005

PF = Printout Follows. Followed by a RST-AP-DS1 output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RST-AP-DS1 message willbe delayed.








5. REFERENCES

IM/OM References:

Input MessagesCFR:AP-DS1 (Flexent EMS/AP)DGN:AP-DS1 (Flexent EMS/AP)OP:ALARM (Flexent EMS/AP)OP:AP-ALARM (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)OP:CELLOP:CELL-GENERICOP:CELL-MICRORMV:AP (Flexent EMS/AP)RMV:AP-DS1 (Flexent EMS/AP)RMV:AP-SS7 (Flexent EMS/AP)RMV:RCS (Flexent EMS/AP)RMV:SS7 (Flexent EMS/AP)RST:AP (Flexent EMS/AP)RST:AP-SS7 (Flexent EMS/AP)RST:RCS (Flexent EMS/AP)RST:SS7 (Flexent EMS/AP)


RST:AP-DS1-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RST AP-DS1

Output MessagesCFR-AP-DS1DGN-AP-DS1OP-ALARMOP-AP-ALARMOP-AP-STATUSOP-CELLOP-CELL-GENERICOP-CELL-MICRORMV-APRMV-AP-DS1RMV-AP-SS7RMV-RCSRMV-SS7RST-APRST-APRST-AP-DS1RST-AP-SS7RST-RCSRST-SS7

Other References:





Issue 28 RST:AP-DS1-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksRST AP-DS1 August 2005



RST:AP-DS1-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RST:AP-HVLR

ID............. RST:AP-HVLRRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

This command restores an Application Processor (AP) Home Visitor Location Register(HVLR) application to service. On successful completion of this command, HVLR will bein the ACTIVE maintenance state.

2. FORMAT

RST:AP a, HVLR


a = AP number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RST-AP-HVLR output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RST-AP-HVLR commandwill be delayed.









Issue 28 RST:AP-HVLR-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRST:AP-HVLR August 2005

5. REFERENCES

IM/OM References:

Input MessagesALW:AP-HVLR (Flexent EMS/AP)INH:AP-HVLR (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)RMV:AP-HVLR (Flexent EMS/AP)

Output MessagesALW-AP-HVLRINH-AP-HVLROP-AP-STATUSRMV-AP-HVLRRST-AP-HVLR

Other References:




RST:AP-HVLR-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RST:AP-HVLRIM

ID............. RST:AP-HVLRIMRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

On successful completion of this command, the Application Processor (AP) Home VisitorLocation Register Integrity Manager (HVLR-IM) application will be restored to theACTIVE or STBY maintenance state depending on the state of the application on the mateAP. If the application is ACTIVE on the mate AP, it will be brought to the STBY state onthis AP. If the application is not ACTIVE on the mate AP, the application will be broughtto the ACTIVE state on this AP.

2. FORMAT

RST:AP a, HVLRIM


a = AP number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RST-AP-HVLRIM output message. If thePF is followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RST-AP-HVLRIMcommand will be delayed.









Issue 28 RST:AP-HVLRIM-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRST:AP-HVLRIM August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RMV:AP (Flexent EMS/AP)RMV:AP-HVLRIM (Flexent EMS/AP)RST:AP (Flexent EMS/AP)SWITCHOVER:HVLRIM (Flexent EMS/AP)

Output MessagesOP-AP-STATUSRMV-APRMV-AP-HVLRIMRST-APRST-AP-HVLRIMSWITCHOVER-HVLRIM

Other References:




RST:AP-HVLRIM-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RST AP-MMA

ID............. RST:AP-MMARELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Restores the specified Message Mapping Application (MMA) to the ACTIVE state on thedesignated Application Processor (AP).

After the MMA is restored, it will initialize and begin processing calls.

2. FORMAT

RST:AP a, MMA b


a = AP number.

b = MMA number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RST-AP-MMA output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RST:AP-MMA commandwill be delayed.









Issue 28 RST:AP-MMA-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRST AP-MMA August 2005

5. REFERENCES

IM/OM References:

Input MessagesRST:AP (Flexent EMS/AP)RST:AP-MMA (Flexent EMS/AP)

Output MessagesRST-APRST-AP-MMA

Other References:




RST:AP-MMA-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RST AP-MSCDBMS

ID............. RST:AP-MSCDBMSRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Restores Application Processor (AP) database update application to service.

This command restores the AP database update application to service. On successfulcompletion of this command the Mobile Switching Center Database Management System(MSCDBMS) managed object will be in the ACTIVE maintenance state and the databaseupdate role will be secondary if it is primary on another AP or primary otherwise.

2. FORMAT

RST:AP a,MSCDBMS


a = AP number.

4. SYSTEM RESPONSE











Issue 28 RST:AP-MSCDBMS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRST AP-MSCDBMS August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RMV:AP-MSCDBMS (Flexent EMS/AP)SWITCHOVER:MSCDBMS (Flexent EMS/AP)


Other References:



RST:AP-MSCDBMS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RST AP-OAMPROXY

ID............. RST:AP-OAMPROXYRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Restores the Application Processor (AP) Operations, Administration and MaintenanceProxy (OAMPROXY) application to service.

On successful completion of this command, OAMPROXY will be in the ACTIVEmaintenance state.

2. FORMAT

RST:AP a, OAMPROXY


a = AP number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RST-AP-OAMPROXY output message. Ifthe PF is followed by the word QUEUED, the command was queued toallow a running command to complete. Therefore, the RST-AP-OAMPROXY command will be delayed.









Issue 28 RST:AP-OAMPROXY-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRST AP-OAMPROXY August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RMV:AP-OAMPROXY (Flexent EMS/AP)SWITCHOVER:OAMPROXY (Flexent EMS/AP)


Other References:



RST:AP-OAMPROXY-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RST:AP-SP

ID............. RST:AP-SPRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

This command restores the Application Processor (AP) Status Display Process (SP)application to service. On successful completion of this command, the SP managed objectwill be in the ACTIVE or STBY maintenance state depending on the state of the applicationon the mate AP. If the application is ACTIVE on the mate AP, it will be brought to theSTBY state on this AP. If the application is not ACTIVE on the mate AP, the applicationwill be brought to the ACTIVE state on this AP.

2. FORMAT

RST:AP a, SP


a = AP number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RST-AP-SP output message. If the PF isfollowed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RST-AP-SP command willbe delayed.









Issue 28 RST:AP-SP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRST:AP-SP August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RMV:AP-SP (Flexent EMS/AP)SWITCHOVER:SP (Flexent EMS/AP)


Other References:



RST:AP-SP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RST AP-SS7MM

ID............. RST:AP-SS7MMRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Restore Application Processor (AP) Signaling System 7 Message Manager (SS7MM)application to service.

On successful completion of this command, SS7MM will be in the ACTIVE maintenancestate.

2. FORMAT

RST:AP a, SS7MM


a = AP number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RST-AP-SS7MM output message. If thePF is followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RST-AP-SS7MM commandwill be delayed.









Issue 28 RST:AP-SS7MM-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRST AP-SS7MM August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RMV:AP-SS7MM (Flexent EMS/AP)RST-AP-SS7MM (Flexent EMS/AP)

Output MessagesOP-AP-STATUSRMV-AP-SS7MMRST-AP-SS7MM

Other References:



RST:AP-SS7MM-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RST AP-TCS

ID............. RST:AP-TCSRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Restores the Application Processor (AP) Traffic Control Server (TCS) application to service.

On successful completion of this command, the specified TCS managed object will be inthe ACTIVE state.

2. FORMAT

RST:AP a, TCS b


a = AP number.

b = TCS number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RST-AP-TCS output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RST-AP-TCS commandwill be delayed.









Issue 28 RST:AP-TCS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRST AP-TCS August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RMV:AP-TCS (Flexent EMS/AP)RST-AP-TCS (Flexent EMS/AP)SWITCHOVER-TCS (Flexent EMS/AP)


Other References:



RST:AP-TCS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RST AP-TPUGUI

ID............. RST:AP-TPUGUIRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Restores the Application Processor (AP) Traffic Processing Unit Graphical User Interface(TPUGUI) application to service.

On successful completion of this command, TPUGUI will be in the ACTIVE maintenancestate.

2. FORMAT

RST:AP a, TPUGUI


a = AP number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RST-AP-TPUGUI output message. If thePF is followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RST-AP-TPUGUIcommand will be delayed.









Issue 28 RST:AP-TPUGUI-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRST AP-TPUGUI August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RMV:AP-TPUGUI (Flexent EMS/AP)SWITCHOVER:TPUGUI (Flexent EMS/AP)


Other References:



RST:AP-TPUGUI-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RST:AP-VCA

ID............. RST:AP-VCARELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

This command restores the Application Processor (AP) Voice Channel Administration(VCA) application to service. On successful completion of this command, the VCAmanaged object will be in the ACTIVE or STBY maintenance state depending on the stateof the application on the mate AP. If the application is ACTIVE on the mate AP, it will bebrought to the STBY state on this AP. If the application is not ACTIVE on the mate AP, theapplication will be brought to the ACTIVE state on this AP.

2. FORMAT

RST:AP a, VCA


a = AP number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RST-AP-VCA output message. If the PFis followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RST-AP-VCA commandwill be delayed.









Issue 28 RST:AP-VCA-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRST:AP-VCA August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RMV:AP-VCA (Flexent EMS/AP)SWITCHOVER:VCA (Flexent EMS/AP)


Other References:


401-710-206 Mobility Manager Voice Channel Administration (MM-VCA)Operations, Administration, and Maintenance (OA&M)


RST:AP-VCA-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RST RCS

ID............. RST:RCSRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Restores the specified Radio Cluster Server (RCS) to service.

The RCS will be restored with this command on the primary and alternate ApplicationProcessors (APs) along with its assigned signaling links. This command is consideredsuccessful if the RCS is restored on at least one AP, at that point however, the RCS willbegin stable clearing the cells and it will be a few minutes before the cells can process calls.

This command may be used when the RCS is UNAVAILABLE on one AP and ACTIVE onanother AP (or UNAVAILABLE on both APs) to restore the UNAVAILABLE RCS.

This command will first attempt to restore the RCS on the primary AP then the alternateAP.

2. FORMAT

RST:RCS a


a = RCS number.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RST-RCS output message. If the PF isfollowed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RCS:RCS command will bedelayed.









Issue 28 RST:RCS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRST RCS August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:CELLRESTART:RCS (Flexent EMS/AP)RMV:RCS (Flexent EMS/AP)

Output MessagesOP-CELLREPT-AP-APPLNKURESTART-RCSRMV-RCSRST-RCS

Other References:



RST:RCS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 RST SS7

ID............. RST:SS7RELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Restores a high speed or low speed Signaling System 7 Link (SS7-LINK) or SignalingSystem 7 Message Manager Application (SS7MMA) link to the ACTIVE state on theApplication Processor (AP).

2. FORMAT

RST:SS7 a


a = SS7-LINK or SS7MMA number (1-512).

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a RST-SS7 output message. If the PF isfollowed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the RST:SS7 command will bedelayed.









Issue 28 RST:SS7-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksRST SS7 August 2005

5. REFERENCES

IM/OM References:

Input MessagesCFR:SS7 (Flexent EMS/AP)OP:ALARM-EMS (Flexent EMS/AP)OP:AP-ALARM (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)OP:SS7x-STAT (Flexent EMS/AP)OP:SS7APNETRMV:AP (Flexent EMS/AP)RMV:AP-DS1 (Flexent EMS/AP)RMV:SS7 (Flexent EMS/AP)RST:AP (Flexent EMS/AP)RST:AP-DS1 (Flexent EMS/AP)

Output MessagesCFR-SS7OP-ALARMOP-AP-ALARMOP-AP-STATUSOP-SS7x-STATOP-SS7APNETRMV-APRMV-AP-DS1RMV-SS7RST-APRST-AP-DS1RST-SS7

Other References:



RST:SS7-2 Issue 28


ID............. SELECT:APRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Selects the Application Processor (AP) platform software version for a software update orgeneric retrofit procedure.

Format 1: The AP will initialize to the selected version of AP platform software on eitherof the following events:

• An initialization of the AP in response to INIT:AP-FULL (during asoftware update).

• An initialization of the AP in response to a "42 r, 50, 54" sequence at the ECPEmergency Action Interface (during a generic retrofit).

NOTE: This command can only be run from the Technician InterfaceCommand Line Interface (TICLI).

Format 2: This is a 1xEV-DO message. The 1xEV-DO command selects the APApplication Software Version to activate. The 1xEV-DO command does notselect platform software; a single platform version may be present. Beforeactivating the software, all the APs in the same frame must select the sameapplication version. The compatible platform version also needs to be installedand activated beforehand.

NOTE: This command can only be run from the Element ManagementSystem (EMS).

2. FORMAT

[1] SELECT:AP a, SOFTWARE b, VERSION "c"

[2] SELECT:AP a, APPLICATION SOFTWARE, VERSION d



b = Software type. "platform" is the only supported software type.

c = Software version. A string of characters within double quotes.

d = AP Application Software version identifier. A string of 12 characters.











E — 1xEV-DO


D — Flexent Modular & CDBS Cells and APs.


F — FOA loads.G — GA loads.P — Private loads.


9th character — Compatibility indicator. Always D.



4. SYSTEM RESPONSE

IP = In Progress.



PF = Printout Follows. Followed by a SELECT:AP output message. If the PF isfollowed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the SELECT:AP command willbe delayed.











5. REFERENCES

IM/OM References:

Input MessagesCOMMIT:APINIT:APOP:AP-VERSION

Output MessagesCOMMIT-APINIT-APOP-AP-VERSIONSELECT-AP

Other References:








Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 STOP MSCDBMS

ID............. STOP:MSCDBMSRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Stops in-progress and queued comprehensive database audits.

Stops all in progress and queued comprehensive audits (if any) which may have beenstarted manually (AUD:MSCDBMS) or automatically. Audits are run automatically once perday at 3:00 AM or at a time chosen by the technician (ALW:MSCDBMS-AUD).

2. FORMAT

STOP:MSCDBMS,AUD


See Purpose.

4. SYSTEM RESPONSE











Issue 28 STOP:MSCDBMS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSTOP MSCDBMS August 2005

5. REFERENCES

IM/OM References:

Input MessagesALW:MSCDBMS-AUD (Flexent EMS/AP)AUD:MSCDBMS (Flexent EMS/AP)INH:MSCDBMS-AUD (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)


Other References:



STOP:MSCDBMS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 STOP SS7

ID............. STOP:SS7RELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Stop in-progress Bit Error Rate Test (BERT) on an Signaling System 7 (SS7) link.

Stops an in progress BERT running on an SS7 link. The OP:AP-STATUS command may berun to verify if there is a BERT in progress for that particular link.

2. FORMAT

STOP:SS7 a, DGN


a = SS7 number (1-512).

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a STOP-SS7 output message. If the PF isfollowed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the STOP-SS7 command willbe delayed.









Issue 28 STOP:SS7-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSTOP SS7 August 2005

5. REFERENCES

IM/OM References:

Input MessagesDGN:SS7 (Flexent EMS/AP)OP:AP-STATUS (Flexent EMS/AP)

Output MessagesDGN-SS7OP-AP-STATUSSTOP-SS7

Other References:



STOP:SS7-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 SWITCHBACK FROMAP

ID............. SWITCHBACK:FROMAPRELEASE ....... 13.0 and laterTYPE .......... Input

1. PURPOSE

Switchback all Radio Cluster Servers (RCSs) that are ACTIVE on the "from" ApplicationProcessor (AP) which have the "to" AP assigned as their primary AP.

This command will switchover all ACTIVE RCSs on the "from" AP back to the "to" AP asequipped on the Recent Change / Verify (RC/V) rcslink form. For an RCS to beswitched back, the "to" AP must be configured as primary AP for the RCS. If a gracefulswitchover is not possible for a given RCS (for example: the RCS on the mate AP is notSTBY) that RCS will not be switched back.

2. FORMAT

SWITCHBACK:FROMAP a, TOAP b


a = The AP number of where to switchback the RCSs "from".

b = The AP number of where to switchback the RCSs "to".

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a SWITCHBACK-FROMAP output message.If the PF is followed by the word QUEUED, the command was queued toallow a running command to complete. Therefore, theSWITCHBACK:FROMAP command will be delayed.









Issue 28 SWITCHBACK:FROMAP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSWITCHBACK FROMAP August 2005

5. REFERENCES

IM/OM References:

Input MessagesSWITCHOVER:AP (Flexent EMS/AP)SWITCHOVER:RCS (Flexent EMS/AP)

Output MessagesSWITCHOVER-APSWITCHBACK-FROMAPSWITCHOVER-RCS

Other References:



SWITCHBACK:FROMAP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 SWITCHOVER:AMA

ID............. SWITCHOVER:AMARELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE

This command switches the Application Processor (AP) Automatic Message Accounting(AMA) application to the mate AP. On successful completion of this command the state ofthe AMA application will be switched from ACTIVE to STBY on this AP, and on the mate APfrom STBY to ACTIVE.

2. FORMAT

SWITCHOVER:AMA[;UCL]


UCL = Unconditional switchover request.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a SWITCHOVER-AMA output message. Ifthe PF is followed by the word QUEUED, the command was queued toallow a running command to complete. Therefore, the SWITCHOVER-AMAcommand will be delayed.









Issue 28 SWITCHOVER:AMA-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSWITCHOVER:AMA August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUSRMV:AP-AMARST:AP-AMA

Output MessagesOP-AP-STATUSRMV-AP-AMARST-AP-AMASWITCHOVER-AMA

Other References:



SWITCHOVER:AMA-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 SWITCHOVER:AMATPS

ID............. SWITCHOVER:AMATPSRELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE

This command switches the Application Processor (AP) Automatic Message AccountingTeleprocessing System (AMATPS) application to the mate AP. On successful completionof this command the state of the AMATPS application will be switched from ACTIVE toSTBY on this AP, and on the mate AP from STBY to ACTIVE.

2. FORMAT

SWITCHOVER:AMATPS[;UCL]



4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a SWITCHOVER-AMATPS output message.If the PF is followed by the word QUEUED, the command was queued toallow a running command to complete. Therefore, the SWITCHOVER-AMATPS command will be delayed.









Issue 28 SWITCHOVER:AMATPS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSWITCHOVER:AMATPS August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUSRMV:AP-AMATPSRST:AP-AMATPS

Output MessagesOP-AP-STATUSRMV-AP-AMATPSRST-AP-AMATPSSWITCHOVER-AMATPS

Other References:



SWITCHOVER:AMATPS-2 Issue 28


ID............. SWITCHOVER:APRELEASE ....... 24.0 and laterTYPE .......... Input


**WARNING**If Voice Channel Administration (VCA) is switched over unconditionally asa result of this command, this may result in the loss of OOS MANUALinformation on trunks. Some maintenance operations in progress may beterminated.

1. PURPOSE


Switchover all applications in the ACTIVE state or primary role on the specifiedApplication Processor (AP) to their mate APs.

Switchover all ACTIVE applications on the specified AP to their STDBY mates on otherAPs. If the MSCDBMS update application is executing on the specified AP with an updaterole of primary, the primary update role will be switched over to the mate AP.

During a conditional AP switchover, switchovers will be attempted only on RCSs who areSTBY on their mate AP. During an unconditional AP switchover, RCS gracefulswitchovers will first be attempted. If an RCS fails to be switched over gracefully, it will beforced to switchover to its mate RCS, dropping all calls as well as denying new callattempts.

Format 1 Switchover for non 1xEV-DO AP.

Format 2 Switchover for 1xEV-DO AP. For a 1xEV-DO AP, there is an option toswitchover one server process or all the server processes. To switch over allserver process, type the AP number only without the server process name.

2. FORMAT

[1] SWITCHOVER:AP a [;UCL]

[2] SWITCHOVER:AP a [,b]


a = AP number.





b = Server name. Only one server process can be specified:

FDBMSHOCHWSERVERLOGSERVEROHMTPAGENT

4. SYSTEM RESPONSE

IP = In Progress.



PF = Printout Follows. Followed by a SWITCHOVER-AP output message. If thePF is followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the SWITCHOVER-APcommand will be delayed.








5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)SWITCHBACK:AP (Flexent EMS/AP)SWITCHBACK:FROMAP (Flexent EMS/AP)SWITCHOVER:MSCDBMS (Flexent EMS/AP)




SWITCHOVER:RCS (Flexent EMS/AP)SWITCHOVER:ROP (Flexent EMS/AP)SWITCHOVER:SP (Flexent EMS/AP)SWITCHOVER:VCA (Flexent EMS/AP)

Output MessagesOP-AP-STATUSSWITCHBACK-FROMAPSWITCHOVER-APSWITCHOVER-MSCDBMSSWITCHOVER-RCSSWITCHOVER-ROPSWITCHOVER-SPSWITCHOVER-VCA

Other References:










Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 SWITCHOVER:HVLRIM

ID............. SWITCHOVER:HVLRIMRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

This command switches the Application Processor (AP) Home Visitor Location RegisterIntegrity Manager (HVLR-IM) application to the mate AP. On successful completion ofthis command the state of the HVLR-IM application will be switched from ACTIVE on thisAP, STBY on the mate AP to STBY on this AP and ACTIVE on the mate AP.

2. FORMAT

SWITCHOVER:HVLRIM[;UCL]



4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a SWITCHOVER-HVLRIM output message.If the PF is followed by the word QUEUED, the command was queued toallow a running command to complete. Therefore, the SWITCHOVER-HVLRIM command will be delayed.









Issue 28 SWITCHOVER:HVLRIM-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSWITCHOVER:HVLRIM August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RMV:AP-HVLRIM (Flexent EMS/AP)RST:AP-HVLRIM (Flexent EMS/AP)

Output MessagesOP-AP-STATUSRMV-AP-HVLRIMRST-AP-HVLRIMSWITCHOVER-HVLRIM

Other References:



SWITCHOVER:HVLRIM-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 SWITCHOVER MSCDBMS

ID............. SWITCHOVER:MSCDBMSRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Switches Application Processor (AP) database update application to another AP.

This command switches the AP database update application to another AP. On successfulcompletion of this command, the values of the database update role on the two APs will beswitched. (A role of primary becomes secondary and vice versa.) This command doesnot affect the maintenance state of the Mobile Switching Center Database ManagementSystem (MSCDBMS) managed object. When executed from the AP, this command must berun on the AP on which the update role is primary.

2. FORMAT

SWITCHOVER:MSCDBMS


See Purpose.

4. SYSTEM RESPONSE











Issue 28 SWITCHOVER:MSCDBMS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSWITCHOVER MSCDBMS August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RMV:AP-MSCDBMS (Flexent EMS/AP)RST:AP-MSCDBMS (Flexent EMS/AP)


Other References:



SWITCHOVER:MSCDBMS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 SWITCHOVER:OAMPROXY

ID............. SWITCHOVER:OAMPROXYRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Performs switchover of the ACTIVE Application Processor (AP) Operations,Administration and Maintenance Proxy (OAMPROXY) application to its STBY instance onthe mate AP.

2. FORMAT

SWITCHOVER:OAMPROXY


This command switches the AP OAMPROXY application to the mate AP. On successfulcompletion of this command, the state of the OAMPROXY application will be switched fromACTIVE on this AP, STBY on the mate AP to STBY on this AP and ACTIVE on the mateAP.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a SWITCHOVER-OAMPROXY outputmessage. If the PF is followed by the word QUEUED, the command wasqueued to allow a running command to complete. Therefore, theSWITCHOVER-OAMPROXY command will be delayed.









Issue 28 SWITCHOVER:OAMPROXY-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSWITCHOVER:OAMPROXY August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RMV:AP-OAMPROXY (Flexent EMS/AP)RST:AP-OAMPROXY (Flexent EMS/AP)


Other References:



SWITCHOVER:OAMPROXY-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 SWITCHOVER RCS

ID............. SWITCHOVER:RCSRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Switchover an ACTIVE Radio Cluster Server (RCS) to its STBY instance on the mateApplication Processor (AP).

This command attempts either a conditional or unconditional switchover of an ACTIVERCS to its STBY instance on the mate AP.

During a conditional RCS switchover, only a graceful switchover is attempted.

During an unconditional RCS switchover, a graceful switchover is first attempted. If theRCS fails the graceful switchover, it is forced to switchover to its mate RCS dropping allcalls as well as denying new call attempts.

2. FORMAT

SWITCHOVER:RCS a [;UCL]


a = RCS number.


4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a SWITCHOVER-RCS output message. Ifthe PF is followed by the word QUEUED, the command was queued toallow a running command to complete. Therefore, the SWITCHOVER:RCScommand will be delayed.









Issue 28 SWITCHOVER:RCS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSWITCHOVER RCS August 2005

5. REFERENCES

IM/OM References:

Input MessagesSWITCHBACK:FROMAP (Flexent EMS/AP)SWITCHOVER:AP (Flexent EMS/AP)

Output MessagesSWITCHBACK-FROMAPSWITCHOVER-APSWITCHOVER-RCS

Other References:



SWITCHOVER:RCS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 SWITCHOVER:SP

ID............. SWITCHOVER:SPRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Performs switchover of the ACTIVE Application Processor (AP) Status Display Process(SP) application to its STBY instance on the mate AP.

2. FORMAT

SWITCHOVER:SP


This command switches the AP SP application to the mate AP. On successful completionof this command the state of the SP application will be switched from ACTIVE on this AP,STBY on the mate AP to STBY on this AP and ACTIVE on the mate AP.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a SWITCHOVER-SP output message. If thePF is followed by the word QUEUED, the command was queued to allow arunning command to complete. Therefore, the SWITCHOVER-SPcommand will be delayed.









Issue 28 SWITCHOVER:SP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSWITCHOVER:SP August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RMV:AP-SP (Flexent EMS/AP)RST:AP-SP (Flexent EMS/AP)


Other References:



SWITCHOVER:SP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 SWITCHOVER TCS

ID............. SWITCHOVER:TCSRELEASE ....... 24.0 and laterTYPE .......... Input



1. PURPOSE

Switches over an ACTIVE Application Processor (AP) Traffic Control Server (TCS)application to its STBY instance on the mate Application Processor (AP).

On successful completion of this command the state of the TCS application will beswitched from ACTIVE on this AP, STBY on the mate AP to STBY on this AP and ACTIVEon the mate AP. All stable calls will be preserved.

2. FORMAT

SWITCHOVER:TCS a [;UCL]


a = Traffic Control Server (TCS) number.


4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a SWITCHOVER-TCS output message. Ifthe PF is followed by the word QUEUED, the command was queued toallow a running command to complete. Therefore, the SWITCHOVER-TCScommand will be delayed.







Issue 28 SWITCHOVER:TCS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSWITCHOVER TCS August 2005



5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RMV:AP-TCS (Flexent EMS/AP)RST:AP-TCS (Flexent EMS/AP)SWITCHOVER-TCS (Flexent EMS/AP)


Other References:



SWITCHOVER:TCS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 SWITCHOVER:TPUGUI

ID............. SWITCHOVER:TPUGUIRELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Performs switchover of the ACTIVE Application Processor (AP) Traffic Processing UnitGraphical User Interface (TPUGUI) application to its STBY instance on the mate AP.

This command switches the AP TPUGUI application to the mate AP. On successfulcompletion of this command the state of the TPUGUI application will be switched fromACTIVE on this AP, STBY on the mate AP to STBY on this AP and ACTIVE on the mateAP.

2. FORMAT

SWITCHOVER:TPUGUI[; UCL]



4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a SWITCHOVER-TPUGUI output message.If the PF is followed by the word QUEUED, the command was queued toallow a running command to complete. Therefore, the SWITCHOVER-TPUGUI command will be delayed.









Issue 28 SWITCHOVER:TPUGUI-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSWITCHOVER:TPUGUI August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RMV:AP-TPUGUI (Flexent EMS/AP)RST:AP-TPUGUI (Flexent EMS/AP)


Other References:



SWITCHOVER:TPUGUI-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 SWITCHOVER:VCA

ID............. SWITCHOVER:VCARELEASE ....... 24.0 and laterTYPE .......... Input


**WARNING**An unconditional switchover may result in the loss of OOS MANUALremoved state information on trunks. Recovery operations in progress at thetime of the UCL switchover may be delayed (for example, CDN stable clearor cell stable clear).

1. PURPOSE

Performs switchover of an ACTIVE Application Processor (AP) Voice ChannelAdministration (VCA) application to its STBY instance on the mate AP.

This command switches the AP VCA application to the mate AP. On successfulcompletion of this command the state of the VCA application will be switched fromACTIVE on this AP, STBY on the mate AP to STBY on this AP and ACTIVE on the mateAP. All stable calls will be preserved.

2. FORMAT

SWITCHOVER:VCA[;UCL]



4. SYSTEM RESPONSE


PF = Printout Follows. Followed by a SWITCHOVER-VCA output message. Ifthe PF is followed by the word QUEUED, the command was queued toallow a running command to complete. Therefore, the SWITCHOVER-VCAcommand will be delayed.







Issue 28 SWITCHOVER:VCA-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksSWITCHOVER:VCA August 2005



5. REFERENCES

IM/OM References:

Input MessagesOP:AP-STATUS (Flexent EMS/AP)RMV:AP-VCA (Flexent EMS/AP)RST:AP-VCA (Flexent EMS/AP)


Other References:



SWITCHOVER:VCA-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ABT AMATAPE

ID............. ABT:AMATAPERELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE

Aborts the current Automatic Message Accounting (AMA) tape writing session.

Aborted tape information should not be used for billing purposes. The next primarysession picks up the aborted tape’s data.

NOTE: Either MT0 or MT1 has to be specified.

NOTE: This command is supported for Flexent Mobility Manager - AMA (FMM-AMA)only. For Executive Cellular Processor - AMA (ECP-AMA), please refer to theinput message ABT:AMATAPE-ECP.

2. FORMAT

ABT:AMATAPE;a!


a = Session type:

MT0 — Used if AMA data goes to the Magnetic Tape 0 (MT0).MT1 — Used if AMA data goes to the Magnetic Tape 1 (MT1).

4. SYSTEM RESPONSE

NG = No Good. Tape writing is not in progress.

OK = Good. Request has been accepted.

RL 5 = Retry Later. Unable to send message to Tape Process.

5. REFERENCES

IM/OM References:

Input MessagesABT:AMATAPE-ECPCOPY:AMATAPESTOP:AMATAPE

Output MessagesREPT-AMATAPE-ER



Issue 28 ABT:AMATAPE-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksABT AMATAPE August 2005



ABT:AMATAPE-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ABT AMATAPE ECP

ID............. ABT:AMATAPE-ECPRELEASE ....... 6.1 and laterTYPE .......... Input

1. PURPOSE

Aborts the current Automatic Message Accounting (AMA) tape writing session.

Aborted tape information should not be used for billing purposes. The next primarysession picks up the aborted tape’s data.

NOTE: Either ST1 or ST2 has to be specified.

NOTE: This command is supported for Executive Cellular Processor - AMA (ECP-AMA)only. For Flexent Mobility Manager - AMA (FMM-AMA), please refer to theinput message ABT:AMATAPE.

2. FORMAT

ABT:AMATAPE;a!


a = Data stream:

ST1 — Used if AMA data goes to the Stream 1 (ST1) data stream.ST2 — Used if AMA data goes to the Stream 2 (ST2) data stream.

4. SYSTEM RESPONSE

NG = No Good. Tape writing is not in progress.

PF = Printout Follows. Followed by a REPT:AMATAPE-ER output message.

RL CODE 2 = Retry Later. Internal audit triggered.

RL CODE 5 = Retry Later. No abort message can be sent to the AMA tape writer at thistime.

5. REFERENCES

IM/OM References:

Input MessagesABT:AMATAPECOPY:AMATAPE-ECPSTOP:AMATAPE-ECP

Output MessagesREPT-AMATAPE-ER-ECP



Issue 28 ABT:AMATAPE-ECP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksABT AMATAPE ECP August 2005



ABT:AMATAPE-ECP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ABT CDN AUD

ID............. ABT:CDN-AUDRELEASE ....... 23.0 and laterTYPE .......... Input

1. PURPOSE

Aborts a Call Processing/Database Node (CDN) Operating System for DistributedSwitching (OSDS) audit.

2. FORMAT

ABT:CDN a,AUD b!


a = CDN number (1-24).

b = Name or index number of audit to be aborted:

ACCNTL — Administrative Call Processing/Database Node (ACDN)cellular networking trunk list audit. (Index number for thisaudit is 20.)

ANOPO — Over-The-Air Activation (OTA) table and Head index arrayaudit. (Index number for this audit is 29.)

CCNID — Control Network Identification (CNID) database recordsaudit. (Index number for this audit is 36.)

CNLIST — Call Processing (CP) cellular networking linked list audit.(Index number for this audit is 12.)

CNNET — CP network entity table audit. (Index number for this auditis 13.)

CNTKML — CP trunk Mobile Call Register (MCR) list audit. (Indexnumber for this audit is 15.)

CPARG — CP automatic roamer greeting audit. (Index number for thisaudit is 23.)

CPGCSL — CP global call status list audit. (Index number for this auditis 17.)

CPIWFDATA — CP Interworking Function (IWF) database audit. (Indexnumber for this audit is 30.)

CPLCSL — CP local call status list audit. (Index number for this audit is18.)

CPMCST — CP mobile call status table audit. (Index number for thisaudit is 8.)

CPMPC — CP Meter Pulse Call audit. (Index number for this audit is34.)

CPMSG — CP mobile call register segmented audit. (Index number forthis audit is 10.)

CPREG — CP tear-down MCR list servicing audit. (Index number forthis audit is 11.)

CPSCN — CP special cellular networking audit. (Index number for thisaudit is 14.)

CPTDML — CP tear-down MCR list integrity audit. (Index number forthis audit is 9.)


Issue 28 ABT:CDN-AUD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksABT CDN AUD August 2005

GLB — Node Integrity global data audit. (Index number for thisaudit is 24.)

IABZOT — Interprocessor busy zone office trunks audit. (Index numberfor this audit is 16.)

IACPMMA — CP Message Mapping Application (MMA) audit. (Indexnumber for this audit is 32.)

IARMCR — Interprocessor remote mobile call register audit. (Indexnumber for this audit is 25.)

LAES — Lawfully authorized electronic surveillance data audit.(Index number for this audit is 33.)

LCSLCHK — CP Local Call Status List (LCSL) /MCR consistency checkaudit. (Index number for this audit is 19.)

LPG — Logical processor group audit. (Index number for this auditis 21.)

MDTXT — CP global data array audit. (Index number for this audit is37.)

OS — Operating System for Distributed Switching (OSDS) audit.(Index number for this audit is 1.)

OSCLCK — OSDS clock audit. (Index number for this audit is 2.)OTAESN — Over-The-Air Activation (OTA) Electronic Serial Number

(ESN) audit. (Index number for this audit is 28.)OTATRN — Over-The-Air Activation (OTA) Temporary Reference

Number (TRN) audit. (Index number for this audit is 27.)PGMA — CP page message area audit. (Index number for this audit is

6.)PGOPL — CP outstanding page list audit. (Index number for this audit

is 7.)PRLISTS — Periodic Reset (PR) link lists audit. (Index number for this

audit is 5.)RUCDNAUD — Ring Database Update (RDBU) table checksum request audit.

(Index number for this audit is 22.)SMP — Sub-Mobile Switching Center (MSC) Paging (SMP) audit.

(Index number for this audit is 31.)UZDATA — User zone data audit. (Index number for this audit is 26.)WTRGDATA — WINTRIG database entry verify audit. (Index number for

this audit is 35.)

4. SYSTEM RESPONSE

OK = Good. Audit has been aborted or was not running.

5. REFERENCES

IM/OM References:

Input MessagesAUD:CDN-NAME


ABT:CDN-AUD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ABT CDN AUD

Output MessagesNone.



Issue 28 ABT:CDN-AUD-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksABT CDN AUD August 2005



ABT:CDN-AUD-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ABT DLN AUD

ID............. ABT:DLN-AUDRELEASE ....... 6.0 and laterTYPE .......... Input

1. PURPOSE

Aborts a Direct Link Node (DLN) Operating System for Distributed Switching (OSDS)audit.

2. FORMAT

ABT:DLN a, AUD b!


a = DLN number (1-2).

b = Name of audit to be aborted:

LPG — Logical Processor Group (LPG) audit.

RUXTBLS — Ring Database Update (RDBU) table checksum request audit.

SS7HDR — SS7 header audit for 5ESS Digital Cellular Switch (DCS).

4. SYSTEM RESPONSE


5. REFERENCES

IM/OM References:

Input MessagesAUD:DLN-NAME




Issue 28 ABT:DLN-AUD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksABT DLN AUD August 2005



ABT:DLN-AUD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ABT ECP AUD

ID............. ABT:ECP-AUDRELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE

Aborts an Executive Cellular Processor (ECP) Operating System for Distributed Switching(OSDS) audit.

2. FORMAT

ABT:ECP, AUD a!


a = Name of audit to be aborted:

ASTAPT — Active packet/session layer table integrity audit.CDNI — Call Processing/Database Node (CDN) integrity audit.CICELL — Cell Site Integrity (CLSI) audit.CMCSXBUF — Message Communication Subsystem (MCS) cell site

transmit buffers audit.DLDLT — Data link maintenance data link table audit.DLDSC — Data link maintenance dedicated switch connection audit.DLNI — direct link node integrity audit.IIMAUD — Interprocessor Message Switch (IMS) integrity module

logical number range check audit.OS — Operating System for Distributed Switching (OSDS) audit.OSCLCK — OSDS clock audit.RMLNSTAT — Ring monitor link node status audit.RUAPEQP — Ring Database Update (RDBU) application processor

equipment table audit.RUAPGTT — ruapgett table versus apgett database audit.RUAPLINK — ruaplink table versus aplink database audit.RUAPOFID — ruapofic table versus apofic database audit.RUAPPC2LS — ruappc2ls table versus appc2ls database audit.RUAPSUBSYS — ruapsubsys table versus apsubsys database audit.RUBSCONF — RDBU base station configuration table audit.RUCCO — rucco table versus rucco database audit.RUCELL — Cell database cell type and call processing status field

audit.RUCIDATA — cicelldata() versus RDBU table audit.RUDLT — RDBU data link configuration tables audit.RUECP — RDBU executive cellular processor audit.RUESID2P — RDBU Extended System/Switch Identification (ESID) to

pcrid lookup table audit.RUGEN — RDBU general audit.RULNTBL — RDBU link node checksum audit.RUNET — RDBU network entity table audit.RUNLMP — network link maintenance processRUOPT — RDBU output message disposition table audit.RUPCT — RDBU processor configuration table audit.


Issue 28 ABT:ECP-AUD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksABT ECP AUD August 2005

RURCSLNK — RDBU Radio Cluster Server (RCS) to channel table audit.RUSS7LS — RDBU Signaling System 7 (SS7) linkset table audit.RUTGI — RDBU trunk group index table audit.RUXIDATA — xissar, xigssr and xissr2 versus RDBU table audit.XISS — System integrity switch status audit.

4. SYSTEM RESPONSE

NG = No Good. Audit inactive.


5. REFERENCES

IM/OM References:

Input MessagesAUD:ECP-NAME




ABT:ECP-AUD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ABT VCA AUD

ID............. ABT:VCA-AUDRELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE

Aborts an Application Processor (AP) Operating System for Distributed Switching (OSDS)audit.

2. FORMAT

ABT:VCA, AUD a!


a = Name of audit to be aborted:

BHMDB — Backhaul Manager (BHM) database audit.DCASTATE — Dynamic Call Assignment State audit.IACELL — Voice Channel Administration (VCA) cell interprocessor

audit.IACST — VCA cell site trunk interprocessor audit.IAIZOT — VCA idle zone office trunk interprocessor audit.OS — Operating System for Distributed Switching (OSDS) audit.OSCLCK — OSDS clock audit.PPBLK — Packet pipe blocking bit (Blocking From DCS [BFD] and

Blocking From MSC [BFM]) status audit.TMPPS — VCA Time Division Multiple Access (TDMA) packet pipe

structure audit.VCAS — Inter-vendor trunk state audit.VCDB — VCA database audit.VCFINFO — VCA Interfering neighbor list in fin_info table audit.VCLISTS — VCA list audit.VCMPT — VCA packet pipe member pointer table audit.VCMS — VCA member structure audit.VCPAFID — VCA paf2indx/indx2paf and Digital Control Channel

(DCCH) channels in chan_usage table audit.VCSTATE — VCA state validation audit.VCTGI — VCA trunk group index table audit.VCTMR — VCA timer structures audit.VCTP — VCA terminal process table audit.

4. SYSTEM RESPONSE

NG = No Good.

— Audit inactive or Voice Channel Administration (VCA) is active on theExecutive Cellular Processor (ECP) and not on the AP. Try again withthe ABT:ECP-AUD input command.

OK = Good.

— Audit has been aborted or was not running.


Issue 28 ABT:VCA-AUD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksABT VCA AUD August 2005

RL = Retry Later.

— Voice Channel Administration on the Application Processor (VCAap)will come up shortly or when it is restored.

?E = Error.

5. REFERENCES

IM/OM References:

Input MessagesABT:ECP-AUDAUD:VCA-NAME




ABT:VCA-AUD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ACTV OMDB

ID............. ACTV:OMDBRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Refreshes the active (incore) Output Message Database (OMDB) from the OMDB disk file.

2. FORMAT

ACTV:OMDB!


See Purpose.

4. SYSTEM RESPONSE

IP = In Progress. Followed by the ACTV-OMDB output message.

5. REFERENCES

IM/OM References:

Input MessagesOP:OMDBUPD:OMDB

Output MessagesACTV-OMDB

Other References:

254-341-230 Craft Interface Software Subsystem Description 3B20D Computer


Issue 28 ACTV:OMDB-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksACTV OMDB August 2005



ACTV:OMDB-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ADD PAUTH

ID............. ADD:PAUTHRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Adds a new user with its related password to the Personal Authority (PAUTH) database.It embeds the password into the authority record and links the password to its useridentity.

2. FORMAT

ADD:PAUTH:IDENT "a",PSSWDPFX "b",PSSWDSFX "c"!


a = Identity of the person or group that uses the password prefix and suffix, inone to eight letters and/or digits.

b = Password Prefix (PSSWDPFX) in three letters and/or digits.

c = Password Suffix (PSSWDSFX) in six to 13 characters.

4. SYSTEM RESPONSE

NG = No Good.

— PASSWORD PREFIX ILLEGAL LENGTHThe given password prefix is not equal to three characters in length.

— PASSWORD PREFIX NOT UNIQUEThe given password prefix already exists in the password authorityadministration.

— PASSWORD SUFFIX ILLEGAL LENGTHThe given password suffix is less than six characters or greater than 13characters in length.

— PERSON IDENTITY NOT UNIQUEThe given person identity already exists in the personal authorityadministration.

— UNABLE TO ACCESS AUTHORITY ADMINISTRATIONPassword or personal authority information is inaccessible.

OK = Good. Password and identity added to database.

RL = Retry Later.

— AUTHORITY ADMINISTRATION UNDER UPDATEAuthority information is currently being updated.


Issue 28 ADD:PAUTH-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksADD PAUTH August 2005

5. REFERENCES

IM/OM References:

Input MessagesCHG:PAUTHDEL:PAUTHRNM:PSSWDVFY:PAUTH

Output MessagesVFY-PAUTH



ADD:PAUTH-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ADD PCGRP

ID............. ADD:PCGRPRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Format 1: Associates the Command Groups (COMGRs) with a person Identity (IDENT),thus allowing a user to access specific groups of commands. The IDENT mustalready exist in the Personal Authority (PAUTH) database.

Format 2: Associates a Profile (PROFL) with an IDENT, thus allowing a user access to allthe commands associated with a set of command groups. The IDENT mustalready exist in the PAUTH database.

2. FORMAT

[1] ADD:PCGRP:IDENT "a", COMGR b!

[2] ADD:PCGRP:IDENT "a", PROFL "c"!


a = Identity of the person or group in one to eight letters and/or digits.

b = Command group.

c = A profile name which has been previously created, but not assigned to thisuser.

4. SYSTEM RESPONSE

NG = No Good.

— COMMAND GROUP ALREADY ASSIGNED TO THIS PERSONThe given command group has already been assigned to this personidentity.

— NON-EXISTENT PERSON IDENTITYThe given person identity does not exist in the personal authorityadministration.

— NON-EXISTENT PROFILE IDENTITYThe given profile does not exist in the personal authorityadministration.

— PASSWORD ENHANCEMENT NOT ACTIVATEDThe PROFL option with this command is valid only for applicationsrunning with the password enhancement feature.

— UNABLE TO ACCESS AUTHORITY ADMINISTRATIONPerson authority information is inaccessible.

OK = Good. Command group added to database.

RL = Retry Later.



Issue 28 ADD:PCGRP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksADD PCGRP August 2005

5. REFERENCES

IM/OM References:

Input MessagesADD:PAUTHCHG:PAUTHDEL:PAUTHDEL:PCGRPRNM:PSSWDVFY:PAUTHVFY:PCGRP

Output MessagesVFY-PAUTHVFY-PCGRP



ADD:PCGRP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ADD PROFL

ID............. ADD:PROFLRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Adds a new profile to the list of user profiles. A profile is a set of command groups. Amaximum of 64 profiles are allowed. These profiles can later be assigned to individualusers.

2. FORMAT

ADD:PROFL,IDENT "a"!


a = Identifying name of the profile to be added to the database. A maximum ofeight characters may be used.

4. SYSTEM RESPONSE

NG = No Good.

— MAXIMUM NUMBER OF PROFILES EXCEEDED— PASSWORD ENHANCEMENT NOT ACTIVATED

This command is valid only for applications running with the passwordenhancement feature enabled.

— PROFILE IDENTITY NOT UNIQUE— UNABLE TO ACCESS PROFILE ADMINISTRATION

OK = Good. Profile successfully added to the database.

RL = Retry Later.

— PROFILE ADMINISTRATION UNDER UPDATE

5. REFERENCES

IM/OM References:

Input MessagesADD:PCGRPCHG:PROFLDEL:PCGRPDEL:PROFLVFY:PCGRPVFY:PROFL


Issue 28 ADD:PROFL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksADD PROFL August 2005

Output MessagesVFY-PCGRPVFY-PROFL



ADD:PROFL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ADD TAUTH

ID............. ADD:TAUTHRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Adds a terminal to the Terminal Authority (TAUTH) database.

2. FORMAT

ADD:TAUTH:TERM "a"!


a = Terminal identity in four characters, starting with tty.

4. SYSTEM RESPONSE

NG = No Good.

— INVALID TERMINAL IDENTITYThe given terminal identity is either not four characters in length ordoes not start with "tty".

— TERMINAL IDENTITY ALREADY EXISTSThe given terminal identity already exists in the terminal authorityadministration.


OK = Good. Terminal identity added to database.

RL = Retry Later.


5. REFERENCES

IM/OM References:

Input MessagesDEL:TAUTHVFY:TAUTH

Output MessagesVFY-TAUTH



Issue 28 ADD:TAUTH-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksADD TAUTH August 2005



ADD:TAUTH-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ADD TCGRP

ID............. ADD:TCGRPRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Associates a Command Group (COMGR) with a terminal Identity (IDENT), thus allowinga user to access only specific groups of commands from that terminal. The IDENT mustalready exist for the Terminal Command Group (TCGRP) in the Terminal Authority(TAUTH) database.

2. FORMAT

ADD:TCGRP:IDENT "a", COMGR b!



b = Command group.

4. SYSTEM RESPONSE

NG = No Good.

— COMMAND GROUP ALREADY ASSIGNED TO THIS TERMINALThe given command group has already been assigned to this terminalidentity.

— INVALID TERMINAL IDENTITYThe given terminal identity is either not four characters in length ordoes not start with "tty".

— NON-EXISTING TERMINAL IDENTITYThe given terminal identity does not exist in the terminal authorityadministration.

— UNABLE TO ACCESS AUTHORITY ADMINISTRATIONTerminal authority information is inaccessible.

OK = Good. Command group added to database.

RL = Retry Later.


5. REFERENCES

IM/OM References:

Input MessagesADD:TAUTHDEL:TAUTHDEL:TCGRPVFY:TAUTHVFY:TCGRP


Issue 28 ADD:TCGRP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksADD TCGRP August 2005

Output MessagesVFY-TAUTHVFY-TCGRP



ADD:TCGRP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW ABREVC

ID............. ALW:ABREVCRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Requests that assert brevity control be allowed.

NOTE: The following assumes that Format Type destinations associated withREPT-DCF-RECOVERY follow the Lucent Technologies recommended values(either Option 1 or Option 2). Refer to 401-710-202, Mobility Manager (MM) ReadOnly Printer (ROP) Operations, Administration, and Maintenance (OA&M) Guide fordetails.

When assert brevity control is allowed, if more than two of the same assert occur in thesame Executive Cellular Processor Complex (ECPC) processor during a 15-minute interval,only the first two asserts (REPT-DCF-RECOVERY) are sent to all the designateddestinations. The remaining asserts in the 15-minute interval are logged:

ECP-ROP — asserts are logged in the /omp-data/logs/rm directory on the OperationsMaintenance Platform (OMP) and not sent to the rop0 destination.

MM-ROP — asserts are logged in the /omp-data/logs/OMPROP1 directory (theOMPLOG destination) on the OMP and are not sent to the RS232 destination.

At the end of the 15-minute interval, a single summary message (REPT-DCF-SUMMARY)reports the assert information for the processor for the interval.

NOTE: The REPT-DCF-SUMMARY message is not subject to assert brevitycontrol.

When assert brevity control is inhibited, all ECPC assert messages are sent to alldesignated ROP destinations.

Additionally, if more than two of the same assert occur in the same ECPC processor duringa 15-minute interval, a single summary message (REPT-DCF-SUMMARY) reports the assertinformation for the processor for the interval.

2. FORMAT

ALW:ABREVC!


See Purpose.

4. SYSTEM RESPONSE

IP = In Progress. The request was received; the ALW-ABREVC output messagewill follow.


Issue 28 ALW:ABREVC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW ABREVC August 2005

5. REFERENCES

IM/OM References:

Input MessagesINH:ABREVCOP:ABREVC

Output MessagesALW-ABREVCINH-ABREVCOP-ABREVCREPT-DCF-RECOVERYREPT-DCF-SUMMARY

Other References:

401-610-160 ECP Operations, Administration, and Maintenance (OA&M) Guide



ALW:ABREVC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW AMA AUTOST ECP

ID............. ALW:AMA-AUTOST-ECPRELEASE ....... 6.1 and laterTYPE .......... Input

1. PURPOSE

Allows auto-start of Automatic Message Accounting (AMA) tape writing.

Allows an AMA tape writing session to be started once a day at a designated time. Use theSET:AMA-CONTRL-ECP input message to set the starting and stopping times for thesession.


NOTE: This command is supported for Executive Cellular Processor - AMA (ECP-AMA)only. For Flexent Mobility Manager - AMA (FMM-AMA), please refer to theRecent Change / Verify (RC/V) automated message accounting configurationand control information (amacc) form.

2. FORMAT

ALW:AMA;AUTOST[:DAYS {(a[,a]) a-a}];b!


a = Days of the week to be allowed (unit, list, or range). One of:

sun — Sundaymon — Mondaytue — Tuesdaywed — Wednesdaythu — Thursdayfri — Fridaysat — Saturday

If DAYS is specified, a must be listed.If DAYS is not specified, all days are allowed.

b = Data stream:


4. SYSTEM RESPONSE

IP = In Progress. Request accepted. The AMA monitor process has been calledto cancel manual blocking of automatic AMA tape writing sessions.

RL CODE 0 = Retry Later. Tape session is currently in progress. Reissue command aftersession completes.


Issue 28 ALW:AMA-AUTOST-ECP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW AMA AUTOST ECP August 2005

5. REFERENCES

IM/OM References:

Input MessagesINH:AMA-AUTOST-ECPOP:AMA-CONTROL-ECPSET:AMA-CONTROL-ECP

Output MessagesREPT-AMA-MON-CONT-F-A-ECPREPT-AMA-MON-CONT-F-B-ECP



ALW:AMA-AUTOST-ECP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW AMADUMP

ID............. ALW:AMADUMPRELEASE ....... 17.0 and laterTYPE .......... Input

1. PURPOSE

Requests activation of the Charge Verify feature for the specified roaming mobile unit.

Use of this input command is only allowed when the Charge Verify feature is activated inthe Feature Activation File (FAF).

Activation of the Charge Verify feature for a mobile allows the REPT-CP-IMMEDIATEoutput report to be generated each time the mobile completes a call. The INH:AMADUMPcommand may be used to deactivate Charge Verify for a given mobile.

The mobile unit’s Directory Number (DN), Mobile Identification Number (MIN), orInternational Mobile Station Identity (IMSI) must be entered as a string of digits withindouble quotes. For example, for a DN of 6309790001234, the command would be enteredas:ALW:AMADUMP, DN "6309790001234"!

2. FORMAT

ALW:AMADUMP,{ DN "a" MIN "b" IMSI "c" }!


a = Variable-length DN 1-14 digits.

b = 10-digit MIN.

c = 8- to 15-digit IMSI.

4. SYSTEM RESPONSE

OK = Good. The request has completed. The Charge Verify feature is activatedfor the specified mobile.

NG = No Good. Followed by one of the following error messages:

— Charge Verify FAF is off

— VLR for this MSID does not exist.

— Maximum number of allowed mobiles has been reached


Issue 28 ALW:AMADUMP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW AMADUMP August 2005

5. REFERENCES

IM/OM References:

Input MessagesINH:AMADUMP


Other References:

401-612-436 Charge Verify


ALW:AMADUMP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW AMA SESSION ECP

ID............. ALW:AMA-SESSION-ECPRELEASE ....... 6.1 and laterTYPE .......... Input

1. PURPOSE

Stops manual blocking of Automatic Message Accounting (AMA) operations.


NOTE: This command is supported for Executive Cellular Processor - AMA (ECP-AMA)only. For Flexent Mobility Manager - AMA (FMM-AMA), please refer to theRecent Change / Verify (RC/V) automated message accounting configurationand control information (amacc) form.

2. FORMAT

ALW:AMA;SESSION;a!


a = Data stream:


4. SYSTEM RESPONSE

OK = Good. Request accepted. The AMA monitor process has been called tocancel manual blocking of AMA tape sessions.

RL CODE 0 = Retry Later. AMA session is currently in progress. Reissue commandafter session completes.

5. REFERENCES

IM/OM References:

Input MessagesINH:AMA-SESSION-ECPOP:AMA-CONTROL-ECP

Output MessagesREPT-AMA-MON-CONT-F-A-ECPREPT-AMA-MON-CONT-F-B-ECP



Issue 28 ALW:AMA-SESSION-ECP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW AMA SESSION ECP August 2005



ALW:AMA-SESSION-ECP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW ARGR

ID............. ALW:ARGRRELEASE ....... 6.1 and laterTYPE .......... Input


**WARNING**Allowing printing of Autonomous Registration Glare Reporting could floodthe Read Only Printer (ROP).

1. PURPOSE

Allows printing of the REPT:PAGE RSP TO FLOOD PAGE - ARGR output message aspart of the Autonomous Registration Glare Reporting (ARGR) feature.

Printing of this message is inhibited by default.

2. FORMAT

ALW:ARGR!


See Purpose.

4. SYSTEM RESPONSE

OK = Good. The request has been executed and the REPT:PAGE-RSP outputmessages are allowed to print autonomously.

5. REFERENCES

IM/OM References:

Input MessagesINH:ARGR

Output MessagesREPT-PAGE-RSP



Issue 28 ALW:ARGR-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW ARGR August 2005



ALW:ARGR-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW ARREGTRACE

ID............. ALW:ARREGTRACERELEASE ....... 8.0 and laterTYPE .......... Input


**WARNING**Allowing REPT–REGTRACE output message printing could flood the ReadOnly Printer (ROP).

1. PURPOSE

Allows printing of the REPT-REGTRACE output message as part of the AutonomousRegistration (AR) Inter Mobile Switching Center (MSC) Autonomous Registration GlareReporting (ARREGTRACE) feature.


2. FORMAT

ALW:ARREGTRACE!


See Purpose.

4. SYSTEM RESPONSE

OK = Good. The request has been executed and the REPT-REGTRACE outputmessages are allowed to print autonomously.

5. REFERENCES

IM/OM References:

Input MessagesINH:ARREGTRACE

Output MessagesREPT-REGTRACE



Issue 28 ALW:ARREGTRACE-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW ARREGTRACE August 2005



ALW:ARREGTRACE-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW ARUNSET

ID............. ALW:ARUNSETRELEASE ....... 6.1 and laterTYPE .......... Input


**WARNING**Allowing REPT–AR–UNSET output message printing could flood the ReadOnly Printer (ROP).

1. PURPOSE

Allows printing of the REPT-AR-UNSET output message. This message indicates theproblem of multiple locations reporting Autonomous Registration (AR) for a single mobile.This problem often reflects a need to reconfigure cell site boundaries.


2. FORMAT

ALW:ARUNSET!


See Purpose.

4. SYSTEM RESPONSE

OK = Good. The request has been executed and the REPT:AR-UNSET outputmessages are allowed to print autonomously.

5. REFERENCES

IM/OM References:

Input MessagesINH:ARUNSET

Output MessagesREPT-AR-UNSET



Issue 28 ALW:ARUNSET-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW ARUNSET August 2005



ALW:ARUNSET-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW AUD

ID............. ALW:AUDRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Allows the routine execution of one or more audits controlled by the System IntegrityMonitor (SIM) that were previously inhibited. Entering the ALW:AUD input message clearsone or more audit inhibits previously set to the manually inhibited or automaticallyinhibited state.

Separate inhibit states are provided for:

— All audits. When the inhibit state for ALL audits is set, routine audit scheduling iscompletely turned off. Entering the ALW:AUD input message with the ALL optionreinitializes the audit control subsystem and turns on routine audit scheduling, but ithas no effect on the inhibit states of individual audits.

— Each audit, identified by audit name and member number. When an audit is inhibitedeither manually or automatically, it is not scheduled to run routinely or in response to asoftware request.

— Each instance of an audit. One instance of an audit may be inhibited while otherinstances are allowed to run routinely.

Audit inhibit states may be displayed by entering the OP:AUD input message.

2. FORMAT

ALW:AUD:{ALL a[ b] a c,INS "d"}!


ALL = Specifies all audits controlled by SIM.

Clears a master inhibit state which is independent of the inhibit states forindividual audits. Causes SIM to attempt to initialize the audit controlsystem if it has not been successfully initialized.

If the control record in the equipment configuration database for SIM hasbeen modified, ALL causes SIM to reinitialize its internal control parametersaccording to the new content of the control record.

a = Audit name. Computer audit names are listed in the input MemberNumbers Appendix, APP:MEM-NUM-B.

If a is specified without b, all members of the audit will be allowed.

b = Member number (see the input Member Numbers Appendix,APP:MEM-NUM-B). May be specified as a single number or a list of numbers.See the User Guidelines in this manual for instructions on entering lists ofnumbers.


Issue 28 ALW:AUD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW AUD August 2005

c = Single member number (see the input Member Numbers Appendix,APP:MEM-NUM-B).

d = Instance name.

4. SYSTEM RESPONSE

See the appendix, System Responses for Audit System Input Messages, APP:AUD.

5. REFERENCES

IM/OM References:

Input MessagesINH:AUDOP:AUD

Output MessagesALW-AUDOP-AUD

Input AppendicesAPP:AUDAPP:MEM-NUM-B

Other References:

254-303-106 3B20D and 3B21D Computers UNIX RTR Operating System System MaintenanceManual


ALW:AUD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW CDN AUD

ID............. ALW:CDN-AUDRELEASE ....... 23.0 and laterTYPE .......... Input

1. PURPOSE

Allows the routine execution of one or all Call Processing/Database Node (CDN)Operating System for Distributed Switching (OSDS) audits.

Format 1: Allows all CDN audits.

Format 2: Allows one CDN audit.

2. FORMAT

[1] ALW:CDN a, AUD!

[2] ALW:CDN a, AUD b!



b = Name or index number of audit to be allowed:
















Issue 28 ALW:CDN-AUD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW CDN AUD August 2005




















this audit is 35.)

4. SYSTEM RESPONSE

OK = Good. Audit prints have been allowed.


ALW:CDN-AUD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW CDN AUD

5. REFERENCES

IM/OM References:

Input MessagesAUD:CDN-NAMEINH:CDN-AUD




Issue 28 ALW:CDN-AUD-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW CDN AUD August 2005



ALW:CDN-AUD-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW CDN CP

ID............. ALW:CDN-CPRELEASE ....... 17.0 and laterTYPE .......... Input

1. PURPOSE

Restores call processing to the specified Call Processing/Database Node (CDN).

2. FORMAT

ALW:CDN a,CP!



4. SYSTEM RESPONSE

OK = Good. Request accepted and the CDN will be restored.

NG = No Good. Request not accepted. The CDN is not in the proper state forthis request.

5. REFERENCES

IM/OM References:

Input MessagesINH:CDN-CPSW:ACDNRMV:LN-UCL




Issue 28 ALW:CDN-CP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW CDN CP August 2005



ALW:CDN-CP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW CDN PRINT AUD

ID............. ALW:CDN-PRINT-AUDRELEASE ....... 17.0 and laterTYPE .......... Input

1. PURPOSE

Allows the printing of Call Processing/Database Node (CDN) Operating System forDistributed Switching (OSDS) audit results.

2. FORMAT

ALW:CDN a, PRINT AUD!



4. SYSTEM RESPONSE


5. REFERENCES

IM/OM References:

Input MessagesINH:CDN-PRINT




Issue 28 ALW:CDN-PRINT-AUD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW CDN PRINT AUD August 2005



ALW:CDN-PRINT-AUD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW CELL

ID............. ALW:CELLRELEASE ....... 25.0 and laterTYPE .......... Input


**WARNING**Most messages of this type merely return the cell site to its normal state asfar as a particular function is concerned, and are not service–affecting. Twoexceptions are:

a) The CP option generates a cell site transient clear phase. If callprocessing was previously inhibited on this cell site, no calls shouldhave been transient anyway.

b) The FWDSCHCL option causes a cell to reject requests for service fromany except class 0 mobiles. This is considered a manual overloadcontrol.

1. PURPOSE

Allows a specific software or hardware action at specified cell site(s).

Software and hardware actions covered by this message ordinarily are allowed.Exceptions are as noted. Depending on the function inhibited, a stable clear, transientclear, or even a single process purge may erase an inhibit condition.

Format 1: Allows a software function.

Format 2: Allows automatic running of a particular audit. The audit will be run in itsregular place in the routine audit cycle. To request the immediate schedulingof an audit, use input message AUD:CELL.

Format 3: Allows printing of various categories of messages.

Format 4: Allows a hardware reset or interrupt. This format is invalid Series II cells.

2. FORMAT

[1] ALW:CELL a, b [ CLASS c]!

[2] ALW:CELL a, AUD d [ CLASS c]!

[3] ALW:CELL a, PRINT e [ CLASS c]!

[4] ALW:CELL a, CSC f; INTR g [ CLASS c]!


Issue 28 ALW:CELL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW CELL August 2005



• A single cell site.

• A range (maximum number of cells in a range is 32).

• A list of cell sites separated by commas and enclosed in parentheses.

If b is FWDSCHCL, a must be a single cell site number.

b = Function to be allowed:

BOOT — Automatic cell boots. To request a boot manually, useINIT:CELL.

CP — Call processing. Originations, terminations, paging, location,and handoff are allowed. The status of the cell becomesACTIVE.

FT ANT — Automatic antenna Functional Tests (FTs) (CDMA).

FT DCCH — Digital control channel FTs (TDMA).

FT LC — Automatic location radio FTs. An FT is also run immediatelyfollowing a manually-requested conditional restoral. See inputmessage RST:CELL.

FT OC — Overhead Channel FTs (CDMA). Not valid for Flexent

Modular Cell 4.0.

FT PL — Pilot Level FTs (CDMA). Not valid for Flexent Modular Cell4.0.

FT SU — Automatic setup radio FTs.

FT TP — Traffic Path FTs (CDMA). Not valid for Flexent Modular Cell4.0.

FWDSCHCL — Forward setup channel controls. Only subscribers in mobileclass 0 will be allowed originating access to the specified cellsite(s). A mobile unit can be in any one of 16 classes. Forwardsetup controls are normally inhibited; see input messageINH:CELL.

INVENTORY — Automatic execution of routine inventory. Cell site inventoryautomatically begins 5 seconds after the time specified by "Timeof Day for Routine Diagnostics" in translations. To execute aroutine inventory sequence manually, use input messageOP:CELL-INVENT. The INVENTORY option is for Series IITDMA and all CDMA cells, however on TDMA, the cell siteinventory is not scheduled to begin automatically with the"Time of Day Routine" as with CDMA. Rather, with TDMA, theroutine inventory begins only when TRC, AMP, or radio is reset.

NOTE: The INVENTORY option is not valid for TDMA Flexent

cells.


ALW:CELL-2 Issue 28


OFD ACCESS — Allows the Operational Fault Detection ACCESS (OFD-ACCESS) software functionality at the cell site. The OFD-ACCESS option is for CDMA cell Release 20.0 and later.

OFD CAP — Allow the Operational Fault Detection Capacity (OFD-CAP)software functionality at the cell site. This OFD CAP option isonly for CDMA cells.

OFD MS — Allow the Operational Fault Detection Multi-Sector (OFD-MS)software functionality at the cell site. The OFD MS option isonly for CDMA cells.

OFD PG — Allow the Operational Fault Detection Paging (OFD-PG)software functionality at the cell site. The OFD PG option isonly for CDMA cells.

PHMON — Phase monitoring. Repeated phasing will prompt the MobileTelephone Switching Office (MTSO) to remove the cell site fromservice.

RTDIAG — Automatic execution of routine diagnostics. Cell site routinediagnostics automatically begin at 5 seconds after the timespecified by "Time of Day for Routine Diagnostics" intranslations. To execute a routine diagnostic sequencemanually, use input message EXC:CELL.

SCSM — Selectable Cell Site Messaging (SCSM). All output reportsassociated with the specified cell will be reported to the inputdevice that issued this command. For a list of cells beingmonitored by SCSM, see the OP:SCSM input command.

c = Overriding output message class (151-213). This option may be used onlyif the Virtual System Output Message Routing feature is supported.

d = Audit to be allowed. See Table 1 for details.

e = Category of prints to be allowed.

AUD — Individual audit error messages, plus informational postmortem messages.

DIVERR — Hardware Error Handler (HEH) error reports for Series II andTDMA Flexent concerning diversity branch imbalance (see theDIVIMB error keyword in output message REPT-CELL-HEH-1).

HEHMSG — Hardware error handler reports.

f = Cell Site Controller (CSC) (0-1) on which a specified interrupt is to beallowed.

g = Type of reset or interrupt to be allowed:

ALL — All interrupts.

CPIMS — Communications Processor Interface (CPI) flow controlmessage.


Issue 28 ALW:CELL-3


CPIST — CPI board status.

CPUADRV — User address violation.

CPUMISC — High Capacity Core Processing Unit (HCPU) misc interrupt.

CPUMTX — Interrupt from mate (exception on mate side).

MPARF — Memory board parity failure.

MWPER — Write protect violation.

NCI0CF — Network Control Interface (NCI) 0 TDM clock failure.

NCI1CF — NCI 1 TDM clock failure.

NCI2CF — NCI 2 TDM clock failure.

4. SYSTEM RESPONSE


NG = No Good. Some necessary precondition(s) for the execution of themessage were not met. This includes the case where the cell site is notequipped. If b is FWDSCHCL, NG indicates that the read control filler bit inthe AUTOPLEX database must be on.

NG - VIRTUAL SYSTEM OUTPUT MESSAGE ROUTING FEATURE NOT ACTIVE =No Good. The CLASS option was used but its Virtual System OutputMessage Routing feature had not been turned on.


RL = Retry Later Data links to the cell are down.

5. REFERENCES

IM/OM References:

Input MessagesAUD:CELLEXC:CELL-FTINH:CELLINIT:CELLOP:CELL-INVENTOP:CELL-SCSMRST:CELL

Output MessagesALW-CELLALW-CELL-AUDALW-CELL-AUDPRINTALW-CELL-PRINT


ALW:CELL-4 Issue 28


REPT-CELL-ANT-TESTREPT-CELL-HEH-1REPT-CELL-HEH-2

Other References:

401-612-021 Virtual System Output Message Routing


Issue 28 ALW:CELL-5


Table 1 shows the audits within the cell. Audit names range from two to ten alphabeticcharacters, the first two characters being the name of the subsystem and the last charactersbeing a mnemonic of the data structure being audited.

The numbers 1 through 4 indicate to which cell type the specified audit applies.

1 — Series II cell

2 — CDMA Flexent Microcell

3 — TDMA Flexent Microcell

4 — CDMA Flexent Modular cell, Flexent Modular Cell 4.0, Flexent Modular Cell 3.0and Flexent Modular Cell 4.0 Mixed Frame, and Flexent CDMA Distributed BaseStation (CDBS) cell.

Table 1. Audit Table_ ______________________________________________________________________________________

Cell type

_ _______________Audit1 2 3 4 Name Description_ _______________________________________________________________________________________ ______________________________________________________________________________________

x x - x ARCCC Audits all CDMA Cluster Controllers (CCCs).x - - - ARDCCH Audits all voice radios that support DCCH.x - - - ARLRCU All locate radios.x - - - ARRTU Radio test unit.x - - - ARSRCU All setup radios.x - - - ARVRCU All voice radios.- x x x AS Alarm scanning.x x - x AUWCACCC Walsh code administration CDMA Cluster Controller

(CCC).x x - x CCPCCC CDMA call processing/ CDMA Cluster Controller (CCC).x x - x CCPCCIDMGR CDMA Call Processing CAMSHO/AHO Call ID Managerx x - x CCPECP CDMA call processing/ Executive Cellular Processor (ECP).x x - x CCPINT CDMA call processing internal.x x - x CCPNLMGR RCC call process of Neighbor List Manager.x x - x CCPOAM CDMA call processing/ Radio Control

Complex/Operations, Administration and Maintenance(RCC-OA&M) structures.

x x - x CCPSEC CDMA call processing secondary cell.x - x - CPAVAIL Channels available for call processing.x - x - CSCP Call processing software.x - - - CSDL Data link connections.x - - - CSTDM TDM bus connection map.- - x - FLCA Flexible Channel Allocation.x x x x HHTPKILL Hardware error handler process cleanup.x - - - IIA Cell site controller interrupt inhibit administration.x x x x INTRPROC Request for Mobile Telephone Switching Office (MTSO) to

run interprocessor audit._ ______________________________________________________________________________________


ALW:CELL-6 Issue 28


Table 1. Continued_ ____________________________________________________________________________________

Cell type

_ _______________Audit1 2 3 4 Name Description_ _____________________________________________________________________________________ ____________________________________________________________________________________

x x x x MECHKSUM Audits checksummed memory (which includes mostprotected data and text) against boot sum table.

x - - - MEMATE Compares the standby mate controller’s memory againstthat of the active controller.

x x x x MEWRPROT Audit master and per-block write protection.x x x x NVMVER Non-volatile memory versions.- - x - OCQMICRO Microcell overload control.x x - - OCQCCC CCC overload status.x x x x OS Audits Operating System for Distributed Switching (OSDS)

data structures.x x x x OSCLCK Audits OSDS timing.x x x x RASP Cleans up when Maintenance Request Administrator

(MRA) is purged.x x x x RATP Audits equipment status table and other data maintained

by the MRA.x x x x RMCLNP Cleans up when Routine Maintenance Scheduler (RMS) is

purged.x x x x RMTPID RMS global data.x x x x TEER Audits data structures for traffic event recording.x x x x TEHR Audits data structures for hourly traffic reports.x - x - TEPL Audits data structures and decoder information pertaining

to power level measurements. Not applicable for CDMA.x x x x TESPINMS Kills terminal processes created by traffic engineering.x x x x TPCLNP Audits terminal process clean-up.x x - x TUCDMA CDMA translation update.x - x - TURCUD Translation download radio parameters.x x x x TUTRANS Audits translation hash sums.x - x - TUUNEQ Audits translation unit unequipped._ ____________________________________________________________________________________


Issue 28 ALW:CELL-7




ALW:CELL-8 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW CELL CP FAIL

ID............. ALW:CELL-CP-FAILRELEASE ....... 7.0 and laterTYPE .......... Input

1. PURPOSE

Allows the throttling of the REPT:CELL-CP-FAIL output message.

Cell Call Processing (CP) failures are reported in the REPT-CELL-CP-FAIL outputmessage and are normally throttled to ten messages per Call Processing/Database Node(CDN) per minute.

This message is throttled by default.

2. FORMAT

ALW:CELL, CP, FAIL, THROTTLE!


See Purpose.

4. SYSTEM RESPONSE

OK = Good. The request has been executed and REPT:CELL-CP-FAIL outputmessage throttling is allowed.

5. REFERENCES

IM/OM References:

Input MessagesINH:CELL-CP-FAIL

Output MessagesREPT-CELL-CP-FAIL



Issue 28 ALW:CELL-CP-FAIL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW CELL CP FAIL August 2005



ALW:CELL-CP-FAIL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW CELL EXTERN FLASH

ID............. ALW:CELL-EXTERNRELEASE ....... 20.0 and laterTYPE .......... Input

1. PURPOSE

Allows the cell indicators on the 2121 — System Equipage Summary, 2122 — Off-Normal Cells, and 2130 — Cell Site Status Summary pages to blink when an externalalarm is present at the cell site.

These cell indicators will only blink when an external alarm is present at the cell site andwhen all other alarm conditions are normal (that is, no other kinds of alarms are present atthe cell site).

NOTE: The default state is blinking of these cell indicators. If you do not wish to seethese cell indicators blinking, you will have to turn them off, using theINH:CELL-EXTERN input command. If blinking has been turned off manually,use the ALW:CELL-EXTERN input command to turn the blinking back on again.

2. FORMAT

ALW:CELL,EXTERN,FLASH!


See Purpose.

4. SYSTEM RESPONSE

OK = Good. The request has been executed and the cell indicators on the2121 — System Equipage Summary, 2122 — Off-Normal Cells, and2130 — Cell Site Status Summary pages are allowed to blink.

5. REFERENCES

IM/OM References:

Input MessagesINH:CELL-EXTERN




Issue 28 ALW:CELL-EXTERN-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW CELL EXTERN FLASH August 2005



ALW:CELL-EXTERN-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW CELL MLG

ID............. ALW:CELL-MLGRELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE

Allow the specified Multi-Link Group (MLG) to resume handling traffic.

2. FORMAT

ALW:CELL a, CP, CDM b, MLG c




c = MLG number (1-2).

4. SYSTEM RESPONSE






5. REFERENCES

IM/OM References:

Input MessagesINH:CELL-MLG

Output MessagesALW-CELL-MLG

Other References:



Issue 28 ALW:CELL-MLG-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW CELL MLG August 2005



ALW:CELL-MLG-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW CONFLOG

ID............. ALW:CONFLOGRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Allows logging of all errors for a specified computer unit and any units beneath it that arereported to CONFIG. Error logging continues until the INH:CONFLOG input message isexecuted.

2. FORMAT

ALW:CONFLOG;a b!


a = Unit name, as specified in the Unit Control Block (UCB). Computer unitnames are listed in the Input Member Numbers Appendix, APP:MEM-NUM-C, Table C.

b = Unit number, as specified in the UCB. See the Input Member NumbersAppendix, APP:MEM-NUM-C, Table C.

4. SYSTEM RESPONSE

IP = In Progress. Message syntax is invalid or the unit name or number doesnot exist in the Equipment Configuration Database (ECD).

OK = Good. Request completed.

PF = Printout Follows. Followed by an ALW-CONFLOG output message.

RL = Retry Later. ECD access failure.

5. REFERENCES

IM/OM References:

Input MessagesINH:CONFLOG

Output MessagesALW-CONFLOG

Input AppendicesAPP:MEM-NUM-C

Other References:

254-341-100 SPCS File System Software Subsystem Description 3B20D Computer


Issue 28 ALW:CONFLOG-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW CONFLOG August 2005



ALW:CONFLOG-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW CPREGTRACE

ID............. ALW:CPREGTRACERELEASE ....... 8.0 and laterTYPE .......... Input



1. PURPOSE

Allows printing of the REPT-REGTRACE output message as part of the CP RegistrationGlare for Active Call Reporting (CPREGTRACE) feature.

Printing of this output message is inhibited by default.

2. FORMAT

ALW:CPREGTRACE!


See Purpose.

4. SYSTEM RESPONSE

OK = Good. The request has been executed and REPT-REGTRACE outputmessages are allowed to print autonomously.

5. REFERENCES

IM/OM References:

Input MessagesINH:CPREGTRACE




Issue 28 ALW:CPREGTRACE-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW CPREGTRACE August 2005



ALW:CPREGTRACE-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW CPSECOND

ID............. ALW:CPSECONDRELEASE ....... 8.0 and laterTYPE .......... Input



1. PURPOSE

Allows printing of the REPT-REGTRACE output message as part of the CP Second PageResponse Reporting Flag (CPSECOND) feature.

Printing of this output message is inhibited by default.

2. FORMAT

ALW:CPSECOND!


See Purpose.

4. SYSTEM RESPONSE

OK = Good. The request has been executed and REPT-REGTRACE outputmessages are allowed to print autonomously.

5. REFERENCES

IM/OM References:

Input MessagesINH:CPSECOND




Issue 28 ALW:CPSECOND-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW CPSECOND August 2005



ALW:CPSECOND-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW CPSG

ID............. ALW:CPSGRELEASE ....... 6.1 and laterTYPE .......... Input


**WARNING**Allowing REPT–CP–SETUP output message printing could flood the ReadOnly Printer (ROP).

1. PURPOSE

Allows printing of the REPT-CP-SETUP output message as part of the CP Setup GlareReporting (CPSG) feature.


2. FORMAT

ALW:CPSG!


See Purpose.

4. SYSTEM RESPONSE

OK = Good. The request has been executed and REPT-CP-SETUP outputmessages are allowed to print autonomously.

5. REFERENCES

IM/OM References:

Input MessagesINH:CPSG

Output MessagesREPT-CP-SETUP



Issue 28 ALW:CPSG-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW CPSG August 2005



ALW:CPSG-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW DLN AUD

ID............. ALW:DLN-AUDRELEASE ....... 7.0 and laterTYPE .......... Input

1. PURPOSE

Allows the routine execution of one or all Direct Link Node (DLN) Operating System forDistributed Switching (OSDS) audits.

Format 1: Allows all DLN audits.

Format 2: Allows one DLN audit.

2. FORMAT

[1] ALW:DLN a, AUD!

[2] ALW:DLN a, AUD b!



b = Name of audit to be allowed:

LPG — Logical processor group audit.


SS7HDR — SS7 header audit for 5ESS Digital Cellular Switch (DCS).

4. SYSTEM RESPONSE

OK = Good. Routine execution of audits has been allowed.

5. REFERENCES

IM/OM References:

Input MessagesAUD:DLN-NAMEINH:DLN-AUD




Issue 28 ALW:DLN-AUD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW DLN AUD August 2005



ALW:DLN-AUD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW DLN PRINT AUD

ID............. ALW:DLN-PRINT-AURELEASE ....... 6.0 and laterTYPE .......... Input

1. PURPOSE

Allows the printing of Direct Link Node (DLN) Operating System for DistributedSwitching (OSDS) audit results.

2. FORMAT

ALW:DLN a, PRINT AUD!



4. SYSTEM RESPONSE

OK = Good. Printing of audit errors has been allowed.

5. REFERENCES

IM/OM References:

Input MessagesINH:DLN-PRINT




Issue 28 ALW:DLN-PRINT-AU-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW DLN PRINT AUD August 2005



ALW:DLN-PRINT-AU-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW DMQ

ID............. ALW:DMQRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Allows previously inhibited or suspended sources to send maintenance requests to the 3BMaintenance Input Request Administrator (MIRA).

2. FORMAT

ALW:DMQ;{SRC a RUN}!


SRC = Reverses the effect of an inhibit diagnostic source input command (INH:DMQ)for a specified source of requests.

a = Three character process name:ADP — Automatic Diagnostic Process.ALL — All nonmanual requests.ARR — Automatic Ring Recovery.CNR — Critical Node Restore (EISO/BISO restore).ISR — Interprocessor Message Switch User Node Soak Restore (ISR).REX — Routine Exerciser.

RUN = Restart normal execution of all diagnostic request sources after suspension bya system recovery.

4. SYSTEM RESPONSE

None.

5. REFERENCES

IM/OM References:

Input MessagesINH:DMQ

Output MessagesOP-DMQ


Issue 28 ALW:DMQ-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW DMQ August 2005

Other References:


254-303-110 3B20D and 3B21D PDS Input Messages Manual

254-341-220 3B20D Computer Operating System Diagnostics Software Subsystem Description- 3B Processor Section

401-661-045 Common Network Interface (CNI) Ring Maintenance- Diagnostics User’s Guide Section


ALW:DMQ-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW DMQ

ID............. ALW:DMQ-RTRRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Allows previously inhibited or suspended sources to send automatic maintenance requeststo the computer Maintenance Input Request Administrator (MIRA).

Format 1: Reverses the effect of an inhibit source message (INH:DMQ) for a specifiedsource of automatic maintenance requests.

Format 2: Valid only while execution of deferred maintenance requests is suspendedduring system recovery. It allows execution of deferred maintenance requestsduring system recovery.

2. FORMAT

[1] ALW:DMQ;SRC a!

[2] ALW:DMQ;RUN!


a = Three-character source name. Computer source names are:

ADP — Automatic diagnostic process.ALL — Allows all automatic maintenance requests by clearing the

inhibited sources.REX — Routine exerciser.

4. SYSTEM RESPONSE

?D = Data field contains an error. General syntax error in the data field,followed by the parameter position and one of the following reasons:

— INVALID KEYWORDThe keyword in the stated parameter is not a valid keyword.

?E = Error. Input error of undetermined type.

?I = Identification Field contains an error. General syntax error, followed bythe parameter position and one of the following reasons:

— EXTRA KEYWORDDuplicate or extraneous keywords were input.

— INVALID KEYWORDThe keyword in the stated parameter position is not a valid keyword.

— MISSING KEYWORDA required keyword is missing from the input.

PF = Printout Follows. Followed by an ALW-DMQ output message.

RL = Retry Later. The system is in an overload condition.


Issue 28 ALW:DMQ-RTR-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW DMQ August 2005

5. REFERENCES

IM/OM References:

Input MessagesINH:DMQOP:DMQ

Output MessagesALW-DMQOP-DMQ

Other References:



ALW:DMQ-RTR-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW EAIINT

ID............. ALW:EAIINTRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Allows the logging and processing of Emergency Action Interface (EAI) error interruptsfrom the 3B21D computer Control Unit (CU) specified in the identification field. If a CU isnot specified with the input command, EAI error interrupts for both CUs are allowed.

NOTE: The 3B21D computer CUs do not have EAI error interrupts.

2. FORMAT

[1] ALW:EAIINT!

[2] ALW:EAIINT;CU a!


a = CU number (0-1).

4. SYSTEM RESPONSE

?I = Identification Field contains an error. One of these messages may follow:

INPUT ERROR Identification field error.

PF = Printout Follows. Followed by the ALW-EAIINT output message.

5. REFERENCES

IM/OM References:

Input MessagesALW:ERRCHKINH:EAIINTOP:ERRCHK

Output MessagesALW-EAIINTINH-EAIINTOP-ERRCHK



Issue 28 ALW:EAIINT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW EAIINT August 2005



ALW:EAIINT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW ECP AUD

ID............. ALW:ECP-AUDRELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE

Allows the routine execution of one or all Executive Cellular Processor (ECP) OperatingSystem for Distributed Switching (OSDS) audits.

Format 1: Allows all ECP audits.

Format 2: Allows one ECP audit.

2. FORMAT

[1] ALW:ECP, AUD!

[2] ALW:ECP, AUD a!


a = Name of audit to be allowed:






pcrid lookup table audit.RUGEN — RDBU general audit.


Issue 28 ALW:ECP-AUD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW ECP AUD August 2005

RULNTBL — RDBU link node checksum audit.RUNET — RDBU network entity table audit.RUNLMP — network link maintenance processRUOPT — RDBU output message disposition table audit.RUPCT — RDBU processor configuration table audit.RURCSLNK — RDBU Radio Cluster Server (RCS) to channel table audit.RUSS7LS — RDBU Signaling System 7 (SS7) linkset table audit.RUTGI — RDBU trunk group index table audit.RUXIDATA — xissar, xigssr and xissr2 versus RDBU table audit.XISS — System integrity switch status audit.

4. SYSTEM RESPONSE



5. REFERENCES

IM/OM References:





ALW:ECP-AUD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW ECP PRINT AUD

ID............. ALW:ECP-PRINTRELEASE ....... 19.0 and laterTYPE .......... Input

1. PURPOSE

Allows the printing of Executive Cellular Processor (ECP) Operating System forDistributed Switching (OSDS) audit results.

2. FORMAT

ALW:ECP, PRINT AUD!


See Purpose.

4. SYSTEM RESPONSE


5. REFERENCES

IM/OM References:

Input MessagesINH:ECP-PRINT




Issue 28 ALW:ECP-PRINT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW ECP PRINT AUD August 2005



ALW:ECP-PRINT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW EGSF

ID............. ALW:EGSFRELEASE ....... 6.1 and laterTYPE .......... Input


**WARNING**Allowing general system Call Processing (CP) failure printing could floodthe Read Only Printer (ROP).

1. PURPOSE

Allows printing of the REPT GENERAL SYSTEM CP FAILURE output message as part ofthe Expanded General System Failure (EGSF) feature.


2. FORMAT

ALW:EGSF!


See Purpose.

4. SYSTEM RESPONSE

NG = No Good. The EGSF feature is not available.

OK = Good. The request has been executed and the REPT-GENERAL outputmessages are allowed to print autonomously.

5. REFERENCES

IM/OM References:

Input MessagesINH:EGSF

Output MessagesREPT-GENERAL



Issue 28 ALW:EGSF-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW EGSF August 2005



ALW:EGSF-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW ERRCHK

ID............. ALW:ERRCHKRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Allows the logging and processing of all computer error sources. This message causes theinhibit administrator to set the inhibit status to allow for all computer inhibit sources.These include HDWCHK, SFTCHK, EAIINT, ERRINT, and the ERRSRC representing theControl Unit (CU) complexes.

NOTE: The 3B21D computer CUs do not have Emergency Action Interface (EAI) ErrorInterrupts (EAIINTs).

2. FORMAT

ALW:ERRCHK!


See Purpose.

4. SYSTEM RESPONSE

?I = Identification Field contains an error.

PF = Printout Follows. Followed by the ALW-ERRCHK output message.

5. REFERENCES

IM/OM References:

Input MessagesALW:EAIINTALW:ERRINTALW:ERRSRCALW:HDWCHKALW:SFTCHKINH:ERRCHKOP:ERRCHK

Output MessagesALW-ERRCHKINH-ERRCHKOP-ERRCHK



Issue 28 ALW:ERRCHK-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW ERRCHK August 2005



ALW:ERRCHK-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW ERRINT

ID............. ALW:ERRINTRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Requests that the logging and processing of error interrupts attached to the unit specifiedin the identification field be allowed. If a unit name is not specified with the inputcommand, then error interrupts for all computer units are allowed.

2. FORMAT

ALW:ERRINT[;{a b[,c d]}]!


a = Unit name. Computer unit names are listed in the Member NumbersAppendix, APP:MEM-NUM-C, Table C.

NOTE: Allowing a Control Unit (CU) in an active/standby duplex configurationallows both CUs since they must be kept in identical states.

b = Unit number. (See Member Numbers Appendix, APP:MEM-NUM-C, Table C.)

c = Subunit name, if a=CU. Subunit names are listed in the Member NumbersAppendix, APP:MEM-NUM-D, Table D.

d = Subunit number. (See the Member Numbers Appendix, APP:MEM-NUM-D,Table D.)

4. SYSTEM RESPONSE


INPUT ERROR Possibly indicates the unit name and number specified.

NG = No Good. One of these messages may follow:

UNEQUIPPED UNIT Indicates unit name and number specified wasfound in the database, but is unequipped.

PF = Printout Follows. Followed by ALW-ERRINT output message. cannot befound in the database.

5. REFERENCES

IM/OM References:

Input MessagesALW:ERRCHKINH:ERRINTOP:ERRCHK

Output MessagesALW-ERRINTINH-ERRINTOP-ERRCHK


Issue 28 ALW:ERRINT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW ERRINT August 2005

Input AppendicesAPP:MEM-NUM-CAPP:MEM-NUM-D



ALW:ERRINT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW ERRSRC

ID............. ALW:ERRSRCRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Requests that the logging and processing of errors specific to the pseudo-nodesrepresenting the computer Control Unit (CU) communities be allowed.

This message causes the inhibit administrator to set the inhibit status to allowed for the CUpseudo-nodes.

2. FORMAT

ALW:ERRSRC [AM]!


See Purpose.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by ALW-ERRSRC output message.

5. REFERENCES

IM/OM References:

Input MessagesALW:ERRCHKINH:ERRSRCOP:ERRCHK

Output MessagesALW-ERRSRCINH-ERRSRCOP-ERRCHK



Issue 28 ALW:ERRSRC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW ERRSRC August 2005



ALW:ERRSRC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW FILESYS ACCESS

ID............. ALW:FILESYS-ACCESRELEASE ....... 8.0 and laterTYPE .......... Input


**WARNING**Incorrect permission values can prevent the system from accessing neededfiles or executing commands and processes.

1. PURPOSE

Changes the access permissions of a specific file. Permissions allow the owner, group, andothers to read, write, and execute a file.

2. FORMAT

ALW:FILESYS:ACCESS a, FN "b"!


a = A three-digit number giving access permissions for owner, group and others,in that order.

1 — Execute (search in directory) only.2 — Write only.3 — Write and execute (search).4 — Read only.5 — Read and execute (search).6 — Read and write.7 — Read, write, and execute (search).

b = Full pathname of the file or directory. See the User Guidelines section of thismanual for definitions of pathname, file, and directory.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by the ALW-FILESYS-ACCESS outputmessage.

5. REFERENCES

IM/OM References:

Input MessagesALW:FILESYS-OWNEROP:ST-LISTDIR

Output MessagesALW-FILESYS-ACCESSOP-ST-LISTDIR


Issue 28 ALW:FILESYS-ACCES-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW FILESYS ACCESS August 2005

Other References:


Display/Menu Page Name:CRAFT FM 01


ALW:FILESYS-ACCES-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW FILESYS MOUNT

ID............. ALW:FILESYS-MOUNTRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Allows a removable file system to be mounted.

2. FORMAT

ALW:FILESYS:MOUNT,FN "a",BSDIR "b"[,RO][,AUD]!


a = Special device filename of the file system to be mounted. See the UserGuidelines in this manual for definitions of special device name and filesystem.

b = The base directory of the mounted file system, from which all file names inthat file system must descend.

RO = File system is to be mounted read only.

AUD = File manager is to audit the file system prior to mounting it.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by the ALW-FILESYS-MOUNT output messageand a PRM output message.

5. REFERENCES

IM/OM References:

Input MessagesINH:FILESYS-UMOUNOP:ST-FILESYS

Output MessagesALW-FILESYS-MOUNTOP-ST-FILESYS

Other References:




Issue 28 ALW:FILESYS-MOUNT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW FILESYS MOUNT August 2005



ALW:FILESYS-MOUNT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW FILESYS OWNER

ID............. ALW:FILESYS-OWNERRELEASE ....... 8.0 and laterTYPE .......... Input


**WARNING**Incorrect owner specifications can prevent the system from accessingneeded files.

1. PURPOSE

Changes the owner and group of a specific file.

2. FORMAT

ALW:FILESYS:OWNER "a", FN "b"!


a = User ID of the new owner of the file.

b = Pathname of the file. See the User Guidelines section in this manual fordefinitions of pathname, file and directory.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by the ALW-FILESYS-OWNER outputmessage.

5. REFERENCES

IM/OM References:

Input MessagesALW:FILESYS-ACCES

Output MessagesALW-FILESYS-OWNER

Other References:




Issue 28 ALW:FILESYS-OWNER-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW FILESYS OWNER August 2005



ALW:FILESYS-OWNER-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW FMP

ID............. ALW:FMPRELEASE ....... 2.0 and laterTYPE .......... Input

1. PURPOSE

Allows printing of the REPT-FMP-MOBILE output message, which contains directorynumber and serial number information for fraudulent home, roamer, tumbling, or ANSI-41 roamer mobiles.

This input message is valid only if the Fraudulent Mobile Print (FMP) optional feature isactive in the system.

2. FORMAT

ALW:FMP!


See Purpose.

4. SYSTEM RESPONSE

NG = No Good. FMP feature is not active.

PF = Printout Follows. Request has been executed. A REPT-FMP outputmessage will follow.

5. REFERENCES

IM/OM References:

Input MessagesINH:FMP

Output MessagesREPT-FMPREPT-FMP-MOBILE



Issue 28 ALW:FMP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW FMP August 2005



ALW:FMP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW HDWCHK

ID............. ALW:HDWCHKRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Sets the system status register such that a Control Unit (CU) switch can be implemented asa normal fault recovery procedure, thereby allowing a switch to the standby computercontrol unit when a fault occurs in the active computer control unit.

2. FORMAT

ALW:HDWCHK!


See Purpose.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by the ALW-HDWCHK output message.

5. REFERENCES

IM/OM References:

Input MessagesALW:ERRCHKINH:HDWCHKOP:ERRCHK

Output MessagesALW-HDWCHKINH-HDWCHKOP-ERRCHK

Other References:



Issue 28 ALW:HDWCHK-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW HDWCHK August 2005



ALW:HDWCHK-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW LCP

ID............. ALW:LCPRELEASE ....... 2.2 and laterTYPE .......... Input


**WARNING**Allowing lost call printing could flood the Read Only Printer (ROP).

1. PURPOSE

Lost Call printing is ordinarily inhibited. When allowed via this message, lost calls fromall cells are reported in the REPT-CELL-CP-FAIL output message.

If a call is lost due to radio transmitter failure, then the lost call message is always printed.

2. FORMAT

ALW:LCP [ CLASS a]!


a = Overriding output message class (151-213). This option may be used onlyif the Virtual System Output Message Routing feature is supported.

4. SYSTEM RESPONSE

OK = Good. Indicates that the request has been executed.


5. REFERENCES

IM/OM References:

Input MessagesINH:LCP

Output MessagesREPT-CELL-CP-FAIL

Other References:



Issue 28 ALW:LCP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW LCP August 2005



ALW:LCP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW LSLTRC

ID............. ALW:LSLTRCRELEASE ....... 25.0 and laterTYPE .......... Input


**WARNING**Activating the Last Seen Cell Mobile Location Trace (LSCMLT) for too manyMobile Subscribers (MS) could result in some impact on systemperformance as well as location reports congestion at the Read Only Printer(ROP).

1. PURPOSE

If the Idle Mobile Subscriber Location Trace (IMSLT) at Serving Mobile Switching Center(MSC) optional feature is active in the Feature Activation File (FAF), this commandrequests to activate the LSCMLT on an idle MS after reporting the mobile’s currentlocation. The command is valid only at serving MSC using Standalone Home LocationRegisters (SHLR).

NOTE: This command does not work at the serving MSC using Integrated HomeLocation Register (IHLR).

The LSCMLT, once activated for the specified MS, will provide:

— The last seen cell mobile location display and autonomous updates on the vlrltRecent Change / Verify (RC/V) form.

— Report at the ROP when location changed.

NOTE: This kind of trace invocation could generate multiple mobile location reports. Itshould be deactivated using the INH:LSLTRC input command.

Users could get better trace resolution on the LSCMLT by periodically invoking theOP:LTRC command.

2. FORMAT

ALW:LSLTRC, {DN "a" MIN "b" IMSI "c" }!


a = Variable length Directory Number (DN) 1-14 digits.

b = 10-digit Mobile Identification Number (MIN).

c = 8-15 digit International Mobile Station Identity (IMSI).

4. SYSTEM RESPONSE

?E = Error. One of the following additional strings may print:

— IMSI feature inactive, check FAF

— IMSLT feature inactive, check FAF


Issue 28 ALW:LSLTRC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW LSLTRC August 2005

— Single string value expected for mobile number

— the Last Seen Cell Location Trace is not active

IP = In Progress. Output messages will follow.

NG = No Good. The MS has already been active in the location trace.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesINH:LSLTRCOP:LTRC

Output MessagesREPT-LTRC



ALW:LSLTRC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW RCMS

ID............. ALW:RCMSRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Allows the Read Only Printer (ROP) Client Message Service (RCMS) feature to be enabled.Enabling this service, routes informational error ROP messages to Operations andMaintenance Center - Radio Access Network (OMC-RAN) Common Object RequestBroker Architecture (CORBA) Agent (ORCA), in addition to being displayed on the ROP.This command can be used from Technician Interface Command Line Interface (TICLI)when Technician Interface (TI) is enabled on the Application Processor (AP) and whenORCA is active on the system.

2. FORMAT

ALW:RCMS


See Purpose.

4. SYSTEM RESPONSE

PF = Good. The request has been executed and the Read Only Printer (ROP)Client Message Service (RCMS) feature is allowed.

RL = Retry Later. ORCA is not active now.

5. REFERENCES

IM/OM References:

Input MessagesALW:RCMSINH:RCMS

Output MessagesALW-RCMS



Issue 28 ALW:RCMS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW RCMS August 2005



ALW:RCMS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW REX

ID............. ALW:REXRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Allows Routine Exercise (REX) for one or more hardware communities by clearing theREX temporary inhibit(s). A hardware community consists of a major device controllerand its associated subdevices. If a hardware community has REX permanently inhibited,its REX temporary inhibit is not available.

2. FORMAT

ALW:REX:{a[ b] ALL}!


a = Unit name of a major community controller. Applications may addadditional major controllers which may be allowed by this command. Thecomputer controllers are:

CU — Control unit.DCI — Dual serial channel/computer interconnect.IOP — Input/output processor.

b = Unit number (see the Input Member Numbers Appendix, APP:MEM-NUM-C,Table C). If not specified, then all controllers with the specified unit name areallowed.

ALL = Clear the temporary REX inhibits for all major community controllers thatare not permanently inhibited from REX.

4. SYSTEM RESPONSE

?D = Data field contains an error.

NG = No Good. REX is permanently inhibited for the unit specified, or for allthe units specified.

OK = Good. REX is allowed for the unit specified, or for at least one of the unitsspecified.

PF = Printout Follows. Followed by an ALW-REX output message.

RL = Retry Later. The database manager or a database record could not beopened, try again at a later time. If this persists, seek technical assistance.


Issue 28 ALW:REX-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW REX August 2005

5. REFERENCES

IM/OM References:

Input MessagesALW:DMQINH:DMQINH:REXOP:DMQOP:REXINH

Output MessagesALW-REXOP-DMQOP-REXINH

Input AppendicesAPP:MEM-NUM-C



ALW:REX-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW REX RPCD

ID............. ALW:REX-RPCDRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Allow Routine Exercise (REX) of Ring Peripheral Controller Device (RPCD) nodes [DirectLink Nodes (DLNs)].

2. FORMAT

ALW:REX:RPCD a b!


a = Group number (0-63).

b = Member number (1-15).

4. SYSTEM RESPONSE

?D = Data field contains an error. Data field error, usually invalid unit name.

OK = Good. Routine exercises are allowed for the RPCD (DLNs) specified.

RL = Retry later.

5. REFERENCES

IM/OM References:

Input MessagesINH:REX-RPCD

Output MessagesOP-DMQ

Other References:



254-341-220 3B20D Computer Operating System Diagnostics Software Subsystem Description



Issue 28 ALW:REX-RPCD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW REX RPCD August 2005



ALW:REX-RPCD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW REX RPCN

ID............. ALW:REX-RPCNRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Allows Routine Exercise (REX) of Ring Peripheral Controller Nodes (RPCNs).

2. FORMAT

ALW:REX:RPCN a b!



b = Member number (0).

4. SYSTEM RESPONSE

?D = Data field contains an error. Usually invalid unit name.

OK = Good. Routine exercises are allowed for the RPCN specified.

RL = Retry later.

5. REFERENCES

IM/OM References:

Input MessagesINH:REX-RPCN


Other References:



254-341-220 3B20D Computer Operating System Diagnostics Software Subsystem Description


Issue 28 ALW:REX-RPCN-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW REX RPCN August 2005



ALW:REX-RPCN-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW RUTIL

ID............. ALW:RUTILRELEASE ....... 7.0 and laterTYPE .......... Input


**WARNING**Incorrect use of this command may interrupt operation of a node on the ringor the whole ring.

1. PURPOSE

Allows all Ring Generic Access Package (RGRASP) breakpoints in the specified node.

An attempt will be made to allow all breakpoints in the specified node. The user will beinformed about the result of this operation.

When a breakpoint has fired MHIT times, it will automatically become inhibited (disabled).

2. FORMAT

ALW:RUTIL (a, b), {AP NP} [; MHIT c]!




c = Maximum number of hits to be allowed for that breakpoint. (If not specifiedMHIT is set to 10.)

4. SYSTEM RESPONSE

None.

5. REFERENCES

IM/OM References:

Input MessagesCLR:RUTILINH:RUTILOP:RUTILWHEN:RUTIL

Output MessagesALW-RUTIL



Issue 28 ALW:RUTIL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW RUTIL August 2005



ALW:RUTIL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW RUTILFLAG

ID............. ALW:RUTILFLAGRELEASE ....... 7.0 and laterTYPE .......... Input



1. PURPOSE

Allows specific Ring Generic Access Package (RGRASP) breakpoints in the specified node.

An attempt will be made to allow the specified breakpoint in the specified node. The userwill be informed about the result of this operation.

When this breakpoint has fired MHIT times it will automatically become inhibited(disabled).

2. FORMAT

ALW:RUTILFLAG (a, b), {AP NP} ; BP c [, MHIT d]!




c = Specific breakpoint to be allowed.

d = Maximum number of hits to be allowed for that breakpoint. (If not specifiedMHIT is set to 10.)

4. SYSTEM RESPONSE

None.

5. REFERENCES

IM/OM References:

Input MessagesCLR:RUTILFLAGINH:RUTILFLAG

Output MessagesALW-RUTILFLAG



Issue 28 ALW:RUTILFLAG-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW RUTILFLAG August 2005



ALW:RUTILFLAG-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW SCSD

ID............. ALW:SCSDRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Allows transitions of a Scanner Signal Distributor (SCSD) scan point to be reported. Scanpoints can be identified by physical location (as in Format 1) or by logical address (as inFormat 2).

2. FORMAT

[1] ALW:SCSD;UNIT a: PT {b (b,b[,b,b,b,b,b,b...])}!

[2] ALW:SCSD;GRPN "c", DUPID d: PT {e (e,e[e,e,e,e])}!


a = SCSD unit member number (0-16).

b = Physical scan point number on an SCSD (0-47).

c = Name of the logical SCSD group. Examples are:FANALM0, FANALM1, FANACU0, FANACU1, PDF0, PRSWCU0,PRSWCU1, PRSWIOP0, PRSWIOP1, PRSWDFC0, PRSWDFC1,PRSWMHD0, PRSWMHD1, PRSWPD0, PTSWROP, PTSWMCR.

d = Duplex point ID (0-1).

e = Number of a point within a logical group (0-5).

4. SYSTEM RESPONSE

NG = No Good. The SCSD administrator process is not active; nocommunication with SCSD points is possible.

PF = Printout Follows. Followed by an ALW-SCSD output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesINH:SCSDOP:SCSD

Output MessagesALW-SCSDREPT-FAN-INHIBITREPT-FAN-MULTIPLEREPT-FAN-SINGLEREPT-SCSDC


Issue 28 ALW:SCSD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW SCSD August 2005

Other References:



ALW:SCSD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW SFTCHK

ID............. ALW:SFTCHKRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Allows the software error handling routines to incorporate system initialization into theirerror recovery procedures as a means of handling computer software sanity problems.

2. FORMAT

ALW:SFTCHK!


See Purpose.

4. SYSTEM RESPONSE


PF = Printout Follows. Followed by an ALW-SFTCHK output message.

5. REFERENCES

IM/OM References:

Input MessagesALW:ERRCHKINH:SFTCHKOP:ERRCHK

Output MessagesALW-SFTCHKINH-SFTCHKOP-ERRCHK

Other References:



Issue 28 ALW:SFTCHK-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW SFTCHK August 2005



ALW:SFTCHK-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW TCS AUD

ID............. ALW:TCS-AUDRELEASE ....... 23.0 and laterTYPE .......... Input

1. PURPOSE

Allows the routine execution of one or all Traffic Control Server (TCS) audits.

Format 1: Allows all TCS audits.

Format 2: Allows one TCS audit.

2. FORMAT

[1] ALW:TCS a, AUD ALL[; PRINT]!

[2] ALW:TCS a, AUD b[; PRINT]!


a = TCS number (1-15).

PRINT = Will allow the user to see error(s) found during an audit if and only if thePRINT option had previously been entered with an INH:TCS-AUD inputcommand.

b = Name of audit to be allowed:

AUCMCR — Audit TCS Call Manager call records.AURMINT — Audit TCS Resource Manager internal data.

4. SYSTEM RESPONSE


5. REFERENCES

IM/OM References:

Input MessagesAUD:TCS-NAMEINH:TCS-AUD

Output MessagesALW-TCS-AUDINH-TCS-AUDAUD-TCS-NAMEAUD-TCS-NAME-ERR



Issue 28 ALW:TCS-AUD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW TCS AUD August 2005



ALW:TCS-AUD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW TRACE

ID............. ALW:TRACERELEASE ....... 7.0 and laterTYPE .......... Input

1. PURPOSE

This command, along with INH:TRACE command, forms the basic on/off mechanism fortrace. Until this command is issued, no trace report will be attempted (although it willconsume a certain amount of fixed overhead). After this command is entered, tracing willtake place according to the previously input trace parameter settings. The parametersettings may be changed at any time with the SET:TRACE command (whether tracing isallowed or inhibited).

2. FORMAT

ALW:TRACE!


See Purpose.

4. SYSTEM RESPONSE

The TRACE craft process ALW:TRACE joins the terminate class associated with TRACEprocess tdcp.p. This means that the craft process will be aborted whenever tdcp.p isaborted by its owner which may be either Interprocessor Message Switch (IMS) or anapplication.

The 3B21D copies the system-detail-flag structure into the user-detail-flag structure andsets the global trace-activity flag.

Sends an updated Local Trace Control Block structure to Node Processors (NPs).

NOTE: The IMS driver process must be running before trace updates can be sent to thenode processors.

5. REFERENCES

IM/OM References:

Input MessagesINH:TRACEOP:TRACESET:TRACE

Output MessagesALW-TRACEINH-TRACEOP-TRACEREPT-TRACESET-TRACE


Issue 28 ALW:TRACE-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW TRACE August 2005



ALW:TRACE-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW TRAP

ID............. ALW:TRAPRELEASE ....... 7.0 and laterTYPE .......... Input

1. PURPOSE

Requests activation of a pending trap that was entered by the SET:TRAP command. Inaddition, this command will allow a trap to be resumed that was temporarilysuspended/inhibited or a trap that has completed due to duration or message countcriterion being satisfied. Traps that have been aborted before completing can be restartedwith an ALW:TRAP command. Traps that have been stopped by a STOP:TRAP commandcannot be reactivated with an ALW:TRAP command. These traps can only be activated byentering a new SET:TRAP command.

2. FORMAT

ALW:TRAP;ID {a (a,a,a) ALL}!


a = Trap identification number or numbers. This can be specified as a single ID, alist of IDs or all IDs.

ALL = All applicable trap identification numbers.

4. SYSTEM RESPONSE

Traps will be activated for the specified identification numbers. Appropriateerror/diagnostic messages will be printed.

5. REFERENCES

IM/OM References:

Input MessagesALW:TRAPINH:TRAPSET:TRAPSTOP:TRAP

Output MessagesALW-TRAP



Issue 28 ALW:TRAP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW TRAP August 2005



ALW:TRAP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW UMEM

ID............. ALW:UMEMRELEASE ....... 8.0 and laterTYPE .......... Input


**WARNING**Use of this GRASP capability can degrade system performance. It shouldnot be used without expert technical assistance.

1. PURPOSE

Causes the computer Generic Access Package (GRASP) transfer trace to start monitoringthe flow of execution, as previously set up with an INIT:UMEM message. The transfertrace goes into the running state with successful completion of the message. This messagecan be used either as an immediate action, or it can be used in the action list of a WHENcommand.

2. FORMAT

ALW:UMEM{/ !}


See Purpose.

4. SYSTEM RESPONSE

?I = Identification Field contains an error. General syntax error.

IP = In Progress. The message has been added to the WHEN action list.

NG = No Good. No trace is defined.

PF = Printout Follows. Followed by an ALW-UMEM output message.

RL = Retry Later. Or wait for the previous OP:UMEM or OP:UMEM;MLH tocomplete. The system is in an overload condition.

5. REFERENCES

IM/OM References:

Input MessagesINH:UMEMINIT:UMEMOP:UMEMOP:UTILWHEN:PIDWHEN:UID

Output MessagesALW-UMEMOP-UTIL


Issue 28 ALW:UMEM-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW UMEM August 2005



ALW:UMEM-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW UTIL

ID............. ALW:UTILRELEASE ....... 8.0 and laterTYPE .......... Input


**WARNING**Use of this GRASP capability can degrade system performance. It shouldnot be used without expert technical assistance.

1. PURPOSE

Enables all currently defined computer Generic Access Package (GRASP) breakpoints sothat the associated actions are executed when the breakpoint conditions occur.

2. FORMAT

ALW:UTIL{! /}


See Purpose.

4. SYSTEM RESPONSE


NG = No Good. No GRASP breakpoints are currently defined.

PF = Printout Follows. Followed by an ALW-UTIL output message.

RL = Retry Later. The system is in an overload condition, or wait for previousOP:UMEM or OP:UMEM;MCH to complete.

5. REFERENCES

IM/OM References:

Input MessagesALW:UTILFLAGINH:UTILOP:UMEMOP:UTILWHEN:PIDWHEN:UID

Output MessagesALW-UTILOP-UTIL


Issue 28 ALW:UTIL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW UTIL August 2005

Other References:

254-341-115 3B20D Computer Generic Access Package (GRASP) and Enhanced Generic AccessPackage (EGRASP) Software Subsystem Description


ALW:UTIL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW UTILFLAG

ID............. ALW:UTILFLAGRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Enables a specific computer Generic Access Package (GRASP) breakpoint so that theassociated actions are executed when the breakpoint condition occurs. TheALW:UTILFLAG message can be used to enable a breakpoint immediately, or as an actionassociated with a breakpoint.

2. FORMAT

ALW:UTILFLAG a{! /}


a = Numeric identifier (one or more decimal digits) for the breakpoint to beenabled.

4. SYSTEM RESPONSE

IP = In Progress. The message was added to the WHEN action list.

NG = No Good. Identifier does not correspond to a currently definedbreakpoint.

PF = Printout Follows. Followed by the ALW-UTILFLAG output message.


5. REFERENCES

IM/OM References:

Input MessagesALW:UTILINH:UTILFLAGOP:UMEMOP:UTILWHEN:PIDWHEN:UID

Output MessagesALW-UTILFLAGOP-UTILWHEN-PIDWHEN-UID


Issue 28 ALW:UTILFLAG-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW UTILFLAG August 2005

Other References:



ALW:UTILFLAG-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW VCA AUD

ID............. ALW:VCA-AUDRELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE

Allows the routine execution of one or all Application Processor (AP) Operating Systemfor Distributed Switching (OSDS) audits.

Format 1: Allows all AP audits.

Format 2: Allows one AP audit.

2. FORMAT

[1] ALW:VCA, AUD!

[2] ALW:VCA, AUD a!


a = Name of audit to be allowed:






4. SYSTEM RESPONSE

NG = No Good.

— Audit inactive or Voice Channel Administration (VCA) is active on theExecutive Cellular Processor (ECP) and not on the AP. Try again withthe ALW:ECP-AUD input command.


Issue 28 ALW:VCA-AUD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW VCA AUD August 2005

OK = Good.


RL = Retry Later.


?E = Error.

5. REFERENCES

IM/OM References:

Input MessagesALW:ECP-AUDAUD:VCA-NAME




ALW:VCA-AUD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 ALW VCA PRINT AUD

ID............. ALW:VCA-PRINTRELEASE ....... 19.0 and laterTYPE .......... Input

1. PURPOSE

Allows the printing of the Application Processor (AP) Operating System for DistributedSwitching (OSDS) audit results.

2. FORMAT

ALW:VCA, PRINT AUD!


See Purpose.

4. SYSTEM RESPONSE

NG = No Good.

— Audit inactive or Voice Channel Administration (VCA) is active on theExecutive Cellular Processor (ECP) and not on the AP. Try again withthe ALW:ECP-PRINT input command.

OK = Good.


RL = Retry Later.


?E = Error.

5. REFERENCES

IM/OM References:

Input MessagesALW:ECP-PRINTINH:VCA-PRINT




Issue 28 ALW:VCA-PRINT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksALW VCA PRINT AUD August 2005



ALW:VCA-PRINT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 APPLY OMDB

ID............. APPLY:OMDBRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Applies previous updates to the new copy of the Output Message Database (OMDB) diskfile during field update.

2. FORMAT

APPLY:OMDB!


See Purpose.

4. SYSTEM RESPONSE

IP = In Progress. Followed by an APPLY-OMDB output message.

5. REFERENCES

IM/OM References:

Input MessagesACTV:OMDBOP:OMDBUPD:OMDB

Output MessagesAPPLY-OMDB

Other References:



Issue 28 APPLY:OMDB-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksAPPLY OMDB August 2005



APPLY:OMDB-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD CDN NAME

ID............. AUD:CDN-NAMERELEASE ....... 23.0 and laterTYPE .......... Input

1. PURPOSE

Requests a Call Processing/Database Node (CDN) Operating System for DistributedSwitching (OSDS) audit.

2. FORMAT

AUD:CDN a, NAME b!



b = Name or index number of audit requested. Please note that audits LPG andRUCDNAUD are not supported for all Application Processor (AP) - basedCDN’s. List of audits:

















Issue 28 AUD:CDN-NAME-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD CDN NAME August 2005



















this audit is 35.)

4. SYSTEM RESPONSE

OK = Good. Audit was already scheduled.

PF = Printout Follows. Audit has been scheduled to run.

5. REFERENCES

IM/OM References:

Input MessagesNone.


AUD:CDN-NAME-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD CDN NAME

Output MessagesAUD-CDN-OSDS-N-E-C



Issue 28 AUD:CDN-NAME-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD CDN NAME August 2005



AUD:CDN-NAME-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD CELL

ID............. AUD:CELLRELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE

Requests an audit in one or more cell sites.

2. FORMAT

AUD:CELL a, NAME b [ CLASS c]!



• A single cell site.• A range (maximum number of cells in range is 32).• A list of cell sites separated by commas and enclosed in parentheses.

b = Audit requested. See Table 1 for details.


4. SYSTEM RESPONSE




PF = Printout Follows. Request has been executed.



5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesAUD-CELL-AUDNAME-CAUD-CELL-AUDNAME-N


Issue 28 AUD:CELL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD CELL August 2005

Other References:



AUD:CELL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD CELL

Table 1 shows the audits within the cell. Audit names range from two to ten alphabeticcharacters, the first two characters being the name of the subsystem and the last charactersbeing a mnemonic of the data structure being audited.

The numbers 1 through 4 indicate to which cell type the specified audit applies.

1 — Series II cell

2 — CDMA Flexent Microcell

3 — TDMA Flexent Microcell

4 — CDMA Flexent Modular cell, Flexent Modular Cell 4.0, Flexent Modular Cell 3.0and Flexent Modular Cell 4.0 Mixed Frame, and Flexent CDMA Distributed BaseStation (CDBS) cell.

Table 1. Audit Table_ ______________________________________________________________________________________

Cell type

_ _______________Audit1 2 3 4 Name Description_ _______________________________________________________________________________________ ______________________________________________________________________________________

x x - x ARCCC Audits all CDMA Cluster Controllers (CCCs).x - - - ARDCCH Audits all voice radios that support DCCH.x - - - ARLRCU All locate radios.x - - - ARRTU Radio test unit.x - - - ARSRCU All setup radios.x - - - ARVRCU All voice radios.- x x x AS Alarm scanning.x x - x AUWCACCC Walsh code administration CDMA Cluster Controller

(CCC).x x - x CCPCCC CDMA call processing/ CDMA Cluster Controller (CCC).x x - x CCPCCIDMGR CDMA Call Processing CAMSHO/AHO Call ID Managerx x - x CCPECP CDMA call processing/ Executive Cellular Processor (ECP).x x - x CCPINT CDMA call processing internal.x x - x CCPNLMGR RCC call process of Neighbor List Manager.x x - x CCPOAM CDMA call processing/ Radio Control

Complex/Operations, Administration and Maintenance(RCC-OA&M) structures.

x x - x CCPSEC CDMA call processing secondary cell.x - x - CPAVAIL Channels available for call processing.x - x - CSCP Call processing software.x - - - CSDL Data link connections.x - - - CSTDM TDM bus connection map.- - x - FLCA Flexible Channel Allocation.x x x x HHTPKILL Hardware error handler process cleanup.x - - - IIA Cell site controller interrupt inhibit administration.x x x x INTRPROC Request for Mobile Telephone Switching Office (MTSO) to

run interprocessor audit._ ______________________________________________________________________________________


Issue 28 AUD:CELL-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD CELL August 2005

Table 1. Continued_ ____________________________________________________________________________________

Cell type

_ _______________Audit1 2 3 4 Name Description_ _____________________________________________________________________________________ ____________________________________________________________________________________

x x x x MECHKSUM Audits checksummed memory (which includes mostprotected data and text) against boot sum table.

x - - - MEMATE Compares the standby mate controller’s memory againstthat of the active controller.

x x x x MEWRPROT Audit master and per-block write protection.x x x x NVMVER Non-volatile memory versions.- - x - OCQMICRO Microcell overload control.x x - - OCQCCC CCC overload status.x x x x OS Audits Operating System for Distributed Switching (OSDS)

data structures.x x x x OSCLCK Audits OSDS timing.x x x x RASP Cleans up when Maintenance Request Administrator

(MRA) is purged.x x x x RATP Audits equipment status table and other data maintained

by the MRA.x x x x RMCLNP Cleans up when Routine Maintenance Scheduler (RMS) is

purged.x x x x RMTPID RMS global data.x x x x TEER Audits data structures for traffic event recording.x x x x TEHR Audits data structures for hourly traffic reports.x - x - TEPL Audits data structures and decoder information pertaining

to power level measurements. Not applicable for CDMA.x x x x TESPINMS Kills terminal processes created by traffic engineering.x x x x TPCLNP Audits terminal process clean-up.x x - x TUCDMA CDMA translation update.x - x - TURCUD Translation download radio parameters.x x x x TUTRANS Audits translation hash sums.x - x - TUUNEQ Audits translation unit unequipped._ ____________________________________________________________________________________


AUD:CELL-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD CNC

ID............. AUD:CNCRELEASE ....... 7.0 and laterTYPE .......... Input

1. PURPOSE

Initiates the central node control audit. (This audit is also routinely executed.)

NOTE: Routine execution of this audit may be inhibited by UNIX RTR during outagesof the Interprocessor Message Switch (IMS) subsystem. This can be checked byusing the OP:AUD command and routine execution can be resumed by using theALW:AUD command.

Internal ring node maintenance records are audited for inconsistencies which couldprevent jobs (such as RST:LN) from progressing or cause jobs to be unnecessarily aborted.

2. FORMAT

AUD:CNC 1 [;{ a b a,b}]!


a = Specifies whether the audit should correct errors:

CORR — Indicates correction should occur. This is the default value.

NCG — Inhibits error correction.

b = Specifies the level of detail of error reporting:

DETL — Generate a raw data report for each error found. This is the defaultvalue.

SUM — Generate only an audit completion message when the auditterminates.

4. SYSTEM RESPONSE

See Purpose.

5. REFERENCES

IM/OM References:

Input MessagesALW:AUDINH:AUDOP:AUDOP:AUDERRSTOP:AUD

Output MessagesAUD-CNC

Output AppendicesAPP:AUD


Issue 28 AUD:CNC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD CNC August 2005

Other References:



AUD:CNC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD CUMEM

ID............. AUD:CUMEMRELEASE ....... 8.0 and laterTYPE .......... Input


**WARNING**This audit can take more than 180 minutes to run and can degrade theperformance of other UNIX RTR system audits. Excessive audit errorsmay result in a hardware reconfiguration with one CU being left out ofservice.

1. PURPOSE

Runs the standby Control Unit Memory (CUMEM) 1 audit in the standby Control Unit(CU), comparing the contents of the online and off-line main stores when in the ACT/ACTor ACT/STBY modes.

2. FORMAT

AUD:CUMEM 1 [;a ;b ;a,b] !


a = CORR or NCG.

CORR — Audit should correct errors (default).NCG — Audit does not correct errors.

b = DETL or SUM.

DETL — Generate a raw data report for each error found followed by anaudit completion message (default). (A limited number of reportsis generated.)

SUM — Generate only an audit completion message when the auditterminates. Raw data reports are not created for any errors thatare found.

4. SYSTEM RESPONSE

See the Audit Appendix, APP:AUD.

5. REFERENCES

IM/OM References:

Input MessagesOP:AUDRST:CUSTOP:AUD


Issue 28 AUD:CUMEM-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD CUMEM August 2005

Output MessagesAUD-CUMEMOP-AUDOP-OOS

Input AppendicesAPP:AUD

Other References:


254-341-235 SPCS Audit Facilities Description 3B20D Model 2 Processor


AUD:CUMEM-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD CUSTAT

ID............. AUD:CUSTATRELEASE ....... 8.0 and laterTYPE .......... Input


**WARNING**Excessive audit errors may result in a hardware reconfiguration with oneControl Unit (CU) being left out of service.

1. PURPOSE

Runs the Control Unit Hardware Status (CUSTAT) audit in the manual mode.

2. FORMAT

AUD:CUSTAT 1 [;a ;b ;a,b] !


a = CORR or NCG.


b = DETL or SUM.



4. SYSTEM RESPONSE


5. REFERENCES

IM/OM References:

Input MessagesOP:AUDSTOP:AUD

Output MessagesAUD-CUSTATOP-AUD


Issue 28 AUD:CUSTAT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD CUSTAT August 2005


Other References:




AUD:CUSTAT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD DLN NAME

ID............. AUD:DLN-NAMERELEASE ....... 6.0 and laterTYPE .......... Input

1. PURPOSE

Requests that a Direct Link Node (DLN) Operating System for Distributed Switching(OSDS) audit be run.

2. FORMAT

AUD:DLN a, NAME b!



b = Name of audit requested:


SS7HDR — Signaling System 7 (SS7) header audit for 5ESS Digital CellularSwitch (DCS)

LPG — Logical processor group audit.

4. SYSTEM RESPONSE


PF = Printout Follows. Audit has been scheduled to run. A printout willfollow.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesAUD-DLN-OSDS-N-E-C



Issue 28 AUD:DLN-NAME-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD DLN NAME August 2005



AUD:DLN-NAME-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD ECD

ID............. AUD:ECDRELEASE ....... 8.0 and laterTYPE .......... Input


**WARNING**Running ECD audit 1 or 3 while diagnostics are running can result inmutilation of database records.

1. PURPOSE

Audits the Equipment Configuration Database (ECD).

Format 1: Audits the incore ECD.

Format 2: Runs a structural audit of the minimum configuration ECD.

Format 3: Runs a structural audit of the full configuration ECD.

2. FORMAT

[1] AUD:ECD a [;b ;c ;b,c] !

[2] AUD:ECD 2,INS "ecd" [;b ;c ;b,c] !

[3] AUD:ECD 2,INS "appecd" [;b ;c ;b,c] !


a = Specifies the type of incore ECD audit (1-3):

1 — Structural audit.3 — Raw data audit.

b = CORR or NCG.


c = DETL or SUM.



4. SYSTEM RESPONSE



Issue 28 AUD:ECD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD ECD August 2005

5. REFERENCES

IM/OM References:


Output MessagesAUD-ECDOP-AUD


Other References:




AUD:ECD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD ECDOWN

ID............. AUD:ECDOWNRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Runs the Equipment Configuration Database Manager (ECDMAN) audit of recordownership. This audit releases reserved records for processes that have died.

2. FORMAT

AUD:ECDOWN 1 [;a ;b ;a,b] !


a = CORR or NCG.


b = DETL or SUM.



4. SYSTEM RESPONSE


5. REFERENCES

IM/OM References:


Output MessagesAUD-ECDOWNOP-AUD



Issue 28 AUD:ECDOWN-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD ECDOWN August 2005

Other References:




AUD:ECDOWN-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD ECP NAME

ID............. AUD:ECP-NAMERELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE

Requests an Executive Cellular Processor (ECP) Operating System for DistributedSwitching (OSDS) audit. This command can only be executed from the ECP CRAFTplatform.

2. FORMAT

AUD:ECP, NAME a!


a = Name of audit requested:






pcrid lookup table audit.RUGEN — RDBU general audit.RULNTBL — RDBU link node checksum audit.RUNET — RDBU network entity table audit.RUNLMP — network link maintenance processRUOPT — RDBU output message disposition table audit.


Issue 28 AUD:ECP-NAME-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD ECP NAME August 2005

RUPCT — RDBU processor configuration table audit.RURCSLNK — RDBU Radio Cluster Server (RCS) to channel table audit.RUSS7LS — RDBU Signaling System 7 (SS7) linkset table audit.RUTGI — RDBU trunk group index table audit.RUXIDATA — xissar, xigssr and xissr2 versus RDBU table audit.XISS — System integrity switch status audit.

4. SYSTEM RESPONSE



PF = Printout Follows. Audit has been scheduled to run.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesAUD-ECP-NAME-E-C



AUD:ECP-NAME-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD FMGR

ID............. AUD:FMGRRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Audits the resources of the File Manager (FMGR).

2. FORMAT

AUD:FMGR a [;b ;c ;b,c] !


a = Specifies the member number (1-9) of the FMGR audit.

1 — Task queue audit.2 — Internal inode table audit.3 — Hash table and internal inode pointer table audit.4 — File table audit.5 — Internal capability table audit.6 — Buffer audit.7 — Mount table audit.8 — Delayed queue audit.9 — Message queue audit.

b = CORR or NCG.


c = DETL or SUM.



4. SYSTEM RESPONSE



Issue 28 AUD:FMGR-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD FMGR August 2005

5. REFERENCES

IM/OM References:


Output MessagesAUD-FMGR1AUD-FMGR2AUD-FMGR3AUD-FMGR4AUD-FMGR5AUD-FMGR6AUD-FMGR7AUD-FMGR8AUD-FMGR9OP-AUD


Other References:




AUD:FMGR-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD FSBLK

ID............. AUD:FSBLKRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Requests that the file system block audit be run. This audit can be run on a mounted orunmounted file system.

2. FORMAT

AUD:FSBLK a,INS "b"[;c ;d ;c,d][:PARAM "e"]!


a = Member number of the FSBLK audit. The computer audit member number is1.

b = Instance to be audited. Computer instance names are:

/dev/bdb/dev/betc/dev/broot/dev/db/dev/etc/dev/root/dev/tmp

c = CORR or NCG.

CORR — Audit should correct errors.NCG — Audit does not correct errors (default).

d = DETL or SUM.



e = Parameter BACKUP is specified if it is desired that the audit check thefilesystem for the appropriateness of generating a backup tape. If this isspecified, the audit may report, as errors, conditions that normally would notbe considered errors, but could result in the creation of an improper backuptape. These errors are not correctable.

4. SYSTEM RESPONSE



Issue 28 AUD:FSBLK-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD FSBLK August 2005

5. REFERENCES

IM/OM References:

Input MessagesAUD:FSLINKOP:AUDOP:FNAMESTOP:AUD

Output MessagesAUD-FSBLKOP-AUD


Other References:





AUD:FSBLK-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD FSCMPT

ID............. AUD:FSCMPTRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Requests that the file system compaction audit be run. This audit can be run on a mountedor unmounted file system.

2. FORMAT

AUD:FSCMPT a,INS "b"[;c ;d ;c,d][:PARAM "{e f e,f}"]!


a = Member number of the FSCMPT audit. The computer audit member numberis 1.

b = Instance to be audited. Instance names are the special device filescorresponding to the file system audited.

c = CORR or NCG.

CORR — Audit should correct errors, and complete the compaction(default).

NCG — Audit should not correct errors, and should not do thecompaction.

d = DETL or SUM.



e = MIN or MAX.

MIN — Perform or report for a minimum effort compaction (default).MAX — Perform or report for a maximum effort compaction.

f = COND or UCL.

COND — Limit number of regular file blocks relocated to achievecompaction (default).

UCL — An unlimited number of regular file blocks may be relocated toachieve compaction.

4. SYSTEM RESPONSE

See the appendix, System Responses for Audit System Input Messages, APP:AUD.


Issue 28 AUD:FSCMPT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD FSCMPT August 2005

5. REFERENCES

IM/OM References:

Input MessagesAUD:FSBLKAUD:FSLINKOP:AUDOP:FNAME

Output MessagesAUD-FSCMPTOP-AUD


Other References:





AUD:FSCMPT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD FSLINK

ID............. AUD:FSLINKRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Requests that the file system link audit be run. This audit can be run on a mounted orunmounted file system.

2. FORMAT

AUD:FSLINK a,INS "b"[;c ;d ;c,d][:PARAM "e"]!


a = Member number of the FSLINK audit. The computer audit member numberis 1.

b = Instance to be audited. Computer instance names are:

/dev/bdb/dev/betc/dev/broot/dev/db/dev/etc/dev/root/dev/tmp

c = CORR or NCG.

CORR — Audit should correct errors.NCG — Audit does not correct errors (default).

d = DETL or SUM.



e = Parameter BACKUP is specified if it is desired that the audit check thefilesystem for the appropriateness of generating a backup tape. If this isspecified, the audit may report as errors conditions that would not normallybe considered errors, but could result in the creation of an improper backuptape. These errors are not correctable.

4. SYSTEM RESPONSE



Issue 28 AUD:FSLINK-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD FSLINK August 2005

5. REFERENCES

IM/OM References:

Input MessagesAUD:FSBLKOP:AUDOP:FNAMESTOP:AUD

Output MessagesOP-AUDAUD-FSLINK


Other References:





AUD:FSLINK-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD MMGR

ID............. AUD:MMGRRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Runs the memory manager audits. The first three audits validate the segment descriptortable, page tables and the page descriptor table, and recover lost pages and page tables.The segment release audit completes an interrupted segment breakdown procedure. Thesegment unlock audit releases old iolocked segments.

The swap space compaction audit runs a complete swap disk space compaction. It shouldbe run, load permitting, in response to repeated REPT-MMGR004 output messages.

NOTE: While the swap space compaction is running, the memory manager will not beable to swap supervisor processes into memory. As a result, the onlysupervisor processes that will run during this interval will be those already inmemory. The real-time interval depends on the level of kernel process activity,or unpredictable things such as the type and number of supervisor segmentsthat are in memory at the time.

2. FORMAT

AUD:MMGR a [;b ;c ;b,c] !


a = Member number of the audit.

1 — Segment descriptor table audit.2 — Page table audit.3 — Page descriptor table audit.4 — Segment release audit.5 — Segment unlock audit.9 — Swap space compaction audit.

b = CORR or NCG.


c = DETL or SUM.


SUM — Generate only an audit completion message when the auditterminates. Raw data reports are not created for any errors that arefound.

4. SYSTEM RESPONSE



Issue 28 AUD:MMGR-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD MMGR August 2005

5. REFERENCES

IM/OM References:


Output MessagesAUD-MMGROP-AUDREPT-MMGR004


Other References:




AUD:MMGR-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD MSGBUF

ID............. AUD:MSGBUFRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Audits the Message Buffer (MSGBUF) resources.

2. FORMAT

AUD:MSGBUF a [;b ;c ;b,c] !


a = Member number of the audit:

1 — Message buffer queue audit.2 — Message buffer extender block audit.

b = CORR or NCG.


c = DETL or SUM.



4. SYSTEM RESPONSE


5. REFERENCES

IM/OM References:


Output MessagesAUD-MSGBUFOP-AUDREPT-KAUDPRC


Issue 28 AUD:MSGBUF-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD MSGBUF August 2005


Other References:




AUD:MSGBUF-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD NIDATA

ID............. AUD:NIDATARELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Runs the internal data audits on the recent changeable tables.

NOTE: Routine execution of this audit may be inhibited by the UNIX - Real TimeReliable (RTR) system during outages of the Common Network Interface (CNI)subsystem. This may be verified by using the OP:AUD command. Routineexecution may be resumed by using the ALW:AUD command.

These audits will compare the 3B21D computer and disk copy of the tables and report anymismatches. The tables will also be checked for invalid data within a table, andinconsistencies across tables. If any errors are uncovered that cannot be corrected withrecent change, then the audit will correct the error as necessary.

2. FORMAT

AUD:NIDATA a [;b]!


a = Data table to be audited:

1 — Office Identification Data.

2 — Link Configuration Data.

3 — Logical-Physical Translation Data.

4 — CCS7 Routing Data.

5 — Subsystem Information Data.

6 — Permanent Relations Data.

8 — Global Title Translator Data.

9 — Invalid.

10 — Protocol Timer/Parameter Data.

b = Specifies the level of detail of error reporting:

DETL — Generates a raw data report for each error found. (A limited numberof reports are generated.) (Default)

SUM — Generates an audit completion message when the audit terminates.Raw data reports are not created for any errors that are found.

4. SYSTEM RESPONSE

See Purpose.


Issue 28 AUD:NIDATA-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD NIDATA August 2005

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesAUD-NIDATA

Other References:



AUD:NIDATA-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD NMDATA

ID............. AUD:NMDATARELEASE ....... 7.0 and laterTYPE .......... Input


**WARNING**Common Network Interface (CNI) does not recommend running this auditin error correction mode. Error correction mode should only be used underthe guidance of CNI Customer Support because of the critical nature of thedata being audited. CNI Customer Support should always be notified in theevent of an error.

1. PURPOSE

NMDATA is the audit family name for the group of audits concerned with the integrity ofnetwork management dynamic data.

NOTE: Routine execution of this audit may be inhibited by the UNIX - Real TimeReliable (RTR) system during outages of the Common Network Interface (CNI)subsystem. This may be verified by using the OP:AUD command. Routineexecution may be resumed by using the ALW:AUD command.

NMDATA 1 audits the routing tables. The routing tables consist of the network table,cluster table, page access table, the member table, the link set translation table, the RoutingPriority Index (RPI) status table, and the director index to network table. One aspect of therouting tables structure is the dynamic allocation and deallocation of slots in the pageaccess table and the member table (those tables are also referred to as the paging tables) asdifferent network events (such as remote link failures or congestion) occur. CNI processesand maintains status information for the point code affected by those events. Thosepaging tables that are used in the allocation/deallocation of slots are audited to ensure thatpointers connecting the tables are valid. The free entries for the paging tables are auditedas well as the used entries.

The fields in the routing tables that are used when routing or updating status informationabout a point code are also audited by NMDATA 1. The audit will look at inconsistenciesbetween the different fields and among the different routing tables.

A copy of the data being audited is also found in the Direct Link Node (DLN). Whenchanges are made to the 3B21D computer master copy as a result of error correction, theremote node copy is updated with REMACS.

WARNING

The application is not notified of the change to the data as a result of error correction. Forthis reason it is recommended that NMDATA 1 always run in error detection mode only.

NMDATA 2 audits the loadshare tables in the 3B21D computer. The loadshare tables areused for message routing. Note that NMDATA 2 is different than NMDATA 1 in that errorcorrection results in any changes to the master copy of the tables.


Issue 28 AUD:NMDATA-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD NMDATA August 2005

2. FORMAT

AUD:NMDATA a[;b ;c ;b,c]!


a = Specifies the audit member to be run:

1 — Routing Tables Linked List and Consistency Check Audit.

2 — Loadshare Tables Audit.

b = Specifies whether the audit should correct errors. The default value iscontained within the Equipment Configuration Database (ECD) record forthis audit (audrec).

CORR — Indicates error-correction should occur.

NCG — Inhibits error-detection mode.

c = Specifies the level of detail of error reporting.

DETL — Indicates a raw data report for each error found should begenerated. The raw data report(s) are followed by an auditcompletion message. A limited number of reports is generated.(Default value.)

SUM — Indicates only an audit completion message is generated when theaudit terminates and in that case raw data reports are not created forany errors that are found.

4. SYSTEM RESPONSE

See Purpose.

5. REFERENCES

IM/OM References:


Output MessagesAUD-NMDATA-1AUD-NMDATA-2



AUD:NMDATA-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD NMDATA

Other References:



Issue 28 AUD:NMDATA-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD NMDATA August 2005



AUD:NMDATA-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD NODEST

ID............. AUD:NODESTRELEASE ....... 7.0 and laterTYPE .......... Input

1. PURPOSE

Initiates ring node state audits.

NOTE: Routine execution of these audits may be inhibited by UNIX Real Time Reliable(RTR) during outages of the Interprocessor Message Switch (IMS) subsystem.This can be checked by using the OP:AUD command and routine execution can beresumed by using the ALW:AUD command.

The node availability map audit compares the two principal records within the IMS driverprocess of the states of ring nodes. It does not check the major state in the EquipmentConfiguration Database (ECD).

This map contains for each ring node a flag indicating whether the node is an IMS UserNode (IUN) in the ACTIVE state. It is used primarily in sending state updates afterchanges in ring configuration and after initializations.

The audit compares the map to the major states of the nodes recorded in the IMS driverprocess.

When errors are detected the map is corrected to agree with the major states.

2. FORMAT

AUD:NODEST a[;{ b c b,c}]!


a = Specifies a particular member of the NODEST family of audits.

1 — The node availability map audit. (This audit is also routinelyscheduled.)

b = Specifies whether the audit should correct errors:

CORR — Indicates correction should occur. This is the default value.

NCG — Inhibits error correction.

c = Specifies the level of detail of error reporting:

DETL — Generate a raw data report for each error found. This is the defaultvalue.

SUM — Generate only an audit completion message when the auditterminates.

4. SYSTEM RESPONSE

See Purpose.


Issue 28 AUD:NODEST-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD NODEST August 2005

5. REFERENCES

IM/OM References:


Output MessagesAUD-NODEST


Other References:



AUD:NODEST-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD PMS

ID............. AUD:PMSRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Runs the Plant Measurements System (PMS) database audit.

2. FORMAT

AUD:PMS 1 [;a ;b ;a,b] !


a = CORR or NCG.


b = DETL or SUM.



4. SYSTEM RESPONSE


5. REFERENCES

IM/OM References:


Output MessagesAUD-PMSOP-AUD



Issue 28 AUD:PMS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD PMS August 2005

Other References:




AUD:PMS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD PROAD

ID............. AUD:PROADRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Audits the Dispatch Control Table (DCT) Extended (DCTEXT), searching for suspendedprocess creations (including forks) and terminations. It also searches for processes whichhave been suspended from execution for over 30 minutes and terminates them.

2. FORMAT

AUD:PROAD 1 [;a ;b ;a,b] !


a = CORR or NCG.


b = DETL or SUM.



4. SYSTEM RESPONSE


5. REFERENCES

IM/OM References:


Output MessagesAUD-PROADOP-AUD



Issue 28 AUD:PROAD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD PROAD August 2005

Other References:




AUD:PROAD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD REMACS

ID............. AUD:REMACSRELEASE ....... 7.0 and laterTYPE .......... Input

1. PURPOSE

Performs control operations on, or requests status of, the REMACS Data Audit.

2. FORMAT

AUD:REMACS: {INH ALW STATUS CYCLE a FREQ b}!


INH = Inhibits the running of the REMACS Data Audit. Aborts any previouslyrequested cycle(s) that may be running. This inhibit will remain in effect aslong as CNI does not perform a level 4 initialization; once this occurs theinhibit will have to be reentered.

ALW = Allows the running of the REMACS Data Audit. This is the default state of theREMACS Data Audit.

STATUS = Displays the current status of the REMACS Data Audit. If the audit is runningor is cycling, the current frequency of invocation is also displayed. If theaudit is cycling, the current cycle count will be displayed.

CYCLE = Cycles the REMACS Data Audit for the number of cycles entered. the auditmust already be inhibited and currently not cycling for this command to behonored by REMACS.

a = Number of cycles.

FREQ = Changes the frequency of invocation of the REMACS Data Audit to thenumber entered. Each time REMACS is invoked, REMACS runs the DataAudit on a portion of REMACS data; this command modifies the frequency ofData Audit invocation each time REMACS itself is invoked. For example ifREMACS is invoked every 200 milliseconds and the Data Audit frequency ofinvocation is 3, then the Data Audit will be run once every 600 milliseconds.

b = Data audit frequency. The Data Audit frequency of invocation is initially setto 1 (Data Audit invoked each time REMACS itself is invoked).

4. SYSTEM RESPONSE

See Explanation of Message.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesAUD-REMACS


Issue 28 AUD:REMACS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD REMACS August 2005



AUD:REMACS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD TCS NAME

ID............. AUD:TCS-NAMERELEASE ....... 20.0 and laterTYPE .......... Input

1. PURPOSE

Requests one or all Traffic Control Server (TCS) audits.

Format 1: Requests all TCS audits.

Format 2: Requests one TCS audit.

For additional information about the TCS audits see the Audit Tables at the end of AUD-TCS-NAME-ERR output manual page.

2. FORMAT

[1] AUD:TCS a, NAME ALL

[2] AUD:TCS a, NAME b


a = TCS number (1-15).

b = Name of audit requested:

AUCMCR — Audit TCS Call Manager call records.AURMINT — Audit TCS Resource Manager internal data.

4. SYSTEM RESPONSE


5. REFERENCES

IM/OM References:

Input MessagesALW:TCS-AUDINH:TCS_AUD

Output MessagesALW-TCS-AUDINH-TCS-AUDAUD-TCS-NAMEAUD-TCS-NAME-ERR



Issue 28 AUD:TCS-NAME-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD TCS NAME August 2005



AUD:TCS-NAME-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 AUD VCA NAME

ID............. AUD:VCA-NAMERELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE

Requests an Application Processor (AP) Operating System for Distributed Switching(OSDS) audit.

2. FORMAT

AUD:VCA, NAME a!


a = Name of audit requested:






4. SYSTEM RESPONSE

NG = No Good.

— Audit inactive or Voice Channel Administration (VCA) is active on theExecutive Cellular Processor (ECP) and not on the AP. Try again withthe AUD:ECP-NAME input command.

OK = Good.



Issue 28 AUD:VCA-NAME-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksAUD VCA NAME August 2005

RL = Retry Later.


?E = Error.

5. REFERENCES

IM/OM References:


Output MessagesAUD-VCA-NAME-E-C



AUD:VCA-NAME-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 BKUP DATABASE DB

ID............. BKUP:DATABASERELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE

Requests the master copy of the specified database be backed up to disk in the dbbackupdirectory.

All changes made to the databases are made to the master copy in /1apx10/dbdata orthe Administrative Call Processing/Database Node (ACDN) copy for ACDN masterdatabases. A backup causes the master copy of one or all databases to be backed up intothe /1apx10/dbbackup directory.

The LAESDB, LAESTKDB, LLCDB, PRTLTDB, RGDB, VDN2PDB, VLRCSTDB, VLRDB,VLRUZDB, VS2PDB, and WINTRIGDB databases do not have full backup copies. Althoughthe BKUP:DATABASE command may be executed on these databases, the resulting file inthe /1apx10/dbbackup directory contains only the basic structure of the databasewithout any records.

When one member of a database dependency group is backed up, all databases in thatgroup will be backed up to maintain consistency. The dependency groups are:

1. MUFDB, CCFDB, SUBAUXDB, AUDB, SUBUZDB, UZDB, CNIDDB, DN2PDB, P2LDNDB,S2PDB, WINCRDDB, WINSRVDB, WINTDADB, SUBMBRDB, SUBPLTDB.

2. ATDB, RTDB, REDB, PDTDB.

3. IUNDB, APCDNDB, RDTKDB, CEQDB, TRUNKDB, FCIDB, CGSADB, FCAUXDB, MCADB,PCTNDB, RESELDB, DCSDB, IWFDB, RSAUXDB, DLCDB, APDB, APGTTDB, APOFIDDB,APPC2LSDB, APSS7LKDB, APSS7SSDB, RCSLINKDB, APFRMDB, BSDB, CICDB,SS7LSDB, LACLDB, FCSDB, CDMEQPDB, CELLDB, FINDB, IOSFACEDB,MODCELLDB, NID2SECDB, RNCTRKDB, ZID2SECDB.

4. OPCLASSDB, OPTYPEDB.

5. APOPDSTDB, APOPMSGDB.

6. ECPDB, FSCODEDB.

7. VLRDB, VDN2PDB, VLRUZDB, VS2PDB, WINTRIG.

8. CDHFLDB, CDHNLDB.

9. TELSGRPDB, TELSCRNDB.

10. CHRATEDB, TARIFFDB, DAYPGDB, EXCDAYDB, CIEXPDB, TREATDB.

11. LAESDB, LAESTKDB.

12. TONEDB, TAMAPDB.


Issue 28 BKUP:DATABASE-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksBKUP DATABASE DB August 2005

The dependency groups specific to the Inter-Operability Specification (IOS) Base StationController (BSC) configuration are:

1. APCDNDB, APDB, APFRMDB, APGTTDB, APOFIDDB, APPC2LSDB, APSS7LKDB,BSDB, CDMEQPDB, CELLDB, CEQDB, CGSADB, DCSDB, DLCDB, FCAUXDB, FCIDB,IUNDB, IWFDB, LACLDB, MCADB, MODCELLDB, PCTNDB, RCSLINKDB, RDTKDB,RESELDB, RNCTRKDB, RSAUXDB, SS7LSDB, TRUNKDB, APSS7SSDB, CICDB,FCSDB, FINDB.




5. ECPDB, FSCODEDB.

6. BSLKDB, IOSCELLDB, IOSHODB, LUBSCDB, OVBSDB SHICCDB, SHODB.

2. FORMAT

BKUP:DATABASE;DB a!


a = Database name:ALL — All database members.ADAPTPGDB — Adaptive Paging.AMACCDB — Automated Message Accounting Configuration and Control.APCDNDB — AP Call Processing/Database Node (CDN).APDB — Application processor equipage.APFRMDB — Application processor frame equipage.APGTTDB — Application processor global title translation.APOFIDDB — Application processor office identification.APOPDSTDB — Application processor output message destination.APOPMSGDB — Application processor output message formats.APPC2LSDB — Application processor point code to link set routing.APSS7LKDB — Application processor Signaling System 7 (SS7) link

information.APSS7SSDB — Application processor subsystem number translation.ARGDB — Authorized roaming group.ATDB — Ambiguous tables.AUDB — Authentication center.BSDB — Base station configuration.BSLKDB — Base station A3/A7 link.CALDB — Dynamic routing calendar.CCODB — Customer controlled options.CCFDB — Custom calling features.CDHFLDB — Code Division Multiple Access (CDMA) Directed Handoff

Frequency List.CDHNLDB — CDMA Directed Handoff Neighbor List.CDMEQPDB — CDMA Digital Module (CDM) Equipage code.CELLDB — Cell site information.CEQDB — Cell equipage.


BKUP:DATABASE-2 Issue 28


CGSADB — Cellular geographic service area.CHRATEDB — Charge rate.CICDB — Circuit identification code.CIEXPDB — Charge index expansion.CIRNLDB — CDMA Inter-Band Load Management (IBLM) redirection

neighbor list.CNIDDB — CDMA Network ID.DAYPGDB — Day program definition.DCSDB — Digital cellular switch.DLCDB — Data link configuration.DN2EDB — Directory Number to Extended System ID.DN2PDB — Directory Number to Primary.DNMODDB — Dialed number modification.DPLANDB — Dialing plan.DXDRTEDB — Digit by digit routing.ECPDB — Executive cellular processor.EXCDAYDB — Exception day definition.FCAUXDB — Face code auxiliary.FCIDB — Face code information.FCSDB — Flexible channel allocation channel set.FINDB — Flexible channel allocation interfering neighbors.FLTRDB — Filter.FRMDB — Fraudulent serial numbers.FSCODEDB — Feature/service code.I3DDB — International direct distance dial.ICDB — Carrier information.IMRDB — Input message routing.IOSCELLDB — Inter-Operability Specification (IOS) cell.IOSFACEDB — IS634 cell site sector equipped information.IOSHODB — IOS cell handoff information.IUNDB — Inter-process message switch user node.IVCDB — Inter-vendor cell.IVTDB — Inter-vendor trunk.IWFDB — Inter-working function.LACLDB — Local area cluster information.LUBSCDB — IOS cell list under abutting BSC.MCADB — Multiple component assignment.MMCMDNDB — Mobile directory number on multiple message center.MMCSRDB — Special routing on multiple message center.MODCELLDB — CDMA Modular Cell Equipage.MRDB — Message routing.MSIDMPCDB — Mobile Identification Number (MIN) - based point code

routing for Mobile Positioning Center (MPC).MUFDB — Subscriber.NETDB — Cellular networking.NETMSCDB — Network Mobile Switching Center (MSC).NID2SECDB — IS634 cell site sector equipped information for provisioned

Network IDs.NNBRDB — Network neighbor.OAMPRXYDB — Operations, Administration, and Maintenance (OA&M)

proxy.




OPCLASSDB — Output message class.OPTYPEDB — Output message type.ORBDB — Object Request Broker.OVBSDB — Other Vender Base Station.P2LDNDB — Primary Mobile Station Identification (MSID) to local

Directory Number (DN).PCTNDB — Point code to trunk member.PDTDB — Primary digit tables.PNDB — Ported numbers list.RCSLINKDB — Radio Cluster Server (RCS)/ Microcell signaling link.RDTKDB — Radio-to-trunk translator.REDB — Resolution entries.RESELDB — Reselection control channel list.RLSDB — Route list selector.RLSTODDB — Route list selector time of day.RNCTRKDB — Radio Network Controller (RNC) Trunk Database (DB) used

for Packet Core.ROMDB — Roamer service list.RSAUXDB — Auxiliary reselection control channel list.RTDB — Resolution tables.S2PDB — Secondary Mobile Station Identification (MSID) to primary

MSID.SACDB — Service access code.SHICCDB — IOS soft handoff Common Intelligent Carrier Card (CICC)

configuration.SHODB — IOS soft handoff application configuration.SS7LSDB — SS7 link set.STARTDB — Start tables.STDLDB — Standard list.SUBAUXDB — Subscriber auxiliary.SUBMBRDB — Subscriber flexible alerting member.SUBPLTDB — Subscriber flexible alerting pilot.SUBUZDB — Subscriber user zones.TAMAPDB — External Tone/Announcement Mapping.TARIFFDB — Tariff ID.TELSCRNDB — Teleservice screening treatment.TELSGRPDB — Teleservice screening group.TGLDB — Trunk group list.TISECURDB — Technician Interface Security Database.TONEDB — Tones and announcements.TREATDB — Call treatment.TRUNKDB — Trunk group and member.USERDB — Operations and Maintenance Center - Radio Access Network

(OMC-RAN) user.UZDB — User zones.WINCRDDB — Wireless Intelligent Network (WIN) Critical Restriction

Digits Database.




WINSRVDB — WIN Service Database.WINTDADB — WIN Trigger Destination Address Database.ZID2SECDB — IS634 cell site sector equipped information for provisioned

Zone Area IDs.

4. SYSTEM RESPONSE

IP = In Progress. Database backup has begun.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesREPT-DATABASE-NAME








Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CFR CELL

ID............. CFR:CELLRELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE

Requests Manual and Cell Configuration and Cell Test (MCAT).

Format 1: Requests initial MCAT.

Format 2: Requests secondary MCAT session. It also indicates the radio configurationused.

Format 3: Requests cleanup of MCAT session.

Format 4: Requests a secondary stop and normal cleanup of MCAT session.

Format 5: Requests a secondary stop or cleanup of MCAT messages. This format is onlyvalid for TDMA RCS cells only. This format has the same functionality asSTOP:CFR-CELL.

Format 6: Requests a secondary MCAT session for Flexent Modular Cell 4.0 andFlexent Modular Cell 3.0 / Flexent Modular Cell 4.0 Mixed Frame.

Use an initial request before entering any secondary request. As many secondary requestsas needed can be used to configure a test path. After a secondary request has been entered,an initial request cannot be entered until a STOP:CFR (see input message STOP:CFR-CELL) or CFR:CELL a, MULTI; MSTOP is used.

2. FORMAT

[1] CFR:CELL a, c; START [ CLASS h]!

[2] CFR:CELL a[, b] , c; d e[: CHANL f][ RC g][ CLASS h]!

[3] CFR:CELL a,c[ CLASS h]!

[4] CFR:CELL a, MULTI; MSTOP!

[5] CFR:CELL a[; STOP]!

[6] CFR:CELL a, b, c [, TXPORT j ] [, CARRIER i ]; d e[ RC g ] [ CLASS h ]!


START = Start the MCAT on the specified unit. The MCAT mode will be active untilterminated by a STOP:CFR-CELL or CFR:CELL a, MULTI; MSTOP inputmessage.

a = Cell site number (1-600):• A single cell site.• A range (1-32).• A list of cell sites separated by commas and enclosed in parentheses.


Issue 28 CFR:CELL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCFR CELL August 2005

b = Flexent identifier: This field is required for all actions except for "XMIT" and"CONFIG", where it is optional. If b is not specified the action is specified toall Code Division Multiple Access Baseband Radio (CBR)/ Pre-DistortionCode Division Multiple Access Baseband Radios (PCBRs) (Flexent CDBS) inthe session. For Format 6, only CDM x is applicable.

BBU x where x = 1 - 3. Baseband Unit (BBU) is applicable to Flexent

CDMA Distributed Base Station (CDBS) cells.

CDM x where x = 1 - 16. CDMA Digital Module (CDM) is applicable toFlexent Modular cells and Flexent Modular Cell 4.0.

MICRO x where x = 1 - 6. MICRO is applicable to TDMA and CDMAFlexent Microcells.

NOTE: a must be a single cell site number if c is any of the following:

BBA xRA x [,UC y]RA x ORIG [,UC y]SUSU x ORIG

c = Cell site unit:NOTE: MULTI is an option that allows you to issue the same command to

multiple radios at the same time.

Flexent Modular Cell 4.0 assemblages only:

MULTI CBR x — Flexent Modular Cell / Flexent Modular Cell 4.0Code Division Multiple Access (CDMA) baseband radio(Message Format 6 only). x = (1-3) (Flexent Modular cell)x = (1-6) (Flexent Modular Cell 4.0).

Series II/Flexent only:

MULTIMULTI ANT x — Physical Transmit face (Message Format 2 only).

x = (0-6) (Series II and modular cell) x = (optional )(Flexent only).

MULTI BBA x — BBA numbers NOTE: You may enter only oneBBA number at a time. (Message Format 2 only). x = (1-42).

MULTI CBR — Flexent Microcell CDMA baseband radio (MessageFormat 2 only).

MULTI CBR x — Flexent Modular Cell / Flexent Modular Cell4.0. baseband radio (Message Format 2 only, for modularcells only). x = (1-3) for Flexent Modular cell, x = (1-6) forFlexent Modular Cell 4.0.

Where x can be one of the following:

• A single CBR.


CFR:CELL-2 Issue 28


• A range (1-6).• A list of CBRs separated by commas and enclosed in

parentheses.

MULTI PCBR x — Pre-distortion CDMA baseband radio (MessageFormat 2 only, for Flexent CDMA Distributed Base Stationonly). x = (1-3).

MULTI RA x — Radio numbers (Up to 16 (non-RCS) or 5 (RCS)comma separated numbers enclosed in parentheses)(Message Format 2 only). x = (0-191) (non-RCS) x = (1-5)RCS only.

Flexible Channel Allocation (FLCA), affects the following change associatedwith the CFR and MULTI RA commands.

NOTE: If the RA is an FLCA RA, then the cell needs to have its QFAF forFLCA Dynamic Assignment (DA) set or the CFR request will berejected.

RA x [,UC y] — Radio (User Channel [UC] is valid only with theTRKREQ or RATDS actions for a TDMA RA. If the RA isassociated with Packet-Pipe then the technician can only useUC #3.) x = (0-191) y = (1-3).

RA x ,CARRIER y — Radio Carrier number (TDMA RCS cell only).x = (1-5) y = (1-2).

RA x ORIG — Original Radio [,UC y] (UC is valid only with theTRKREQ or RATDS actions for a TDMA RA. If the RA isassociated with Packet-Pipe then the technician can only useUC #3.) x = (0-191) y = (1-3).

NOTE: The SU option is not supported in Flexent TDMA.

SU x — Setup radioT{ x = (0-7) or x = (0-35) with DirectionalSetup.

SU x ORIG — Original Setup radioT{ x = (0-7) or x = (0-35) withDirectional Setup.

TRTU — TDMA Test EDRU (Can’t be used with MULTI).

d,e = The action d and option e requested:

The following table lists the configuration actions for Series II MultipleConfigurations (MULTI) and CDMA Modular cells and Flexent CDMADistributed Base Stations. It also applies to Flexent Modular Cell 4.0assemblages.


Issue 28 CFR:CELL-3


Cell Configuration Command Actions For Series II_ ________________________________________________________________

ACTIONS_ _________________________________________________________________ ________________________________________________________________BBA only BBA & Voice Radios Voice Radios only_ ________________________________________________________________ADDCE n CONFIG n VRADPC n (for Series II only).CDMADPC n XMITC nDELCE nPNOFFSET n_ ________________________________________________________________

where n is the option to be entered after each action.

NOTE: All other SII actions are used for single radio processing, includingCONFIG, VRADPC and XMITC.

NOTE: For Flexent Modular Cell 4.0 assemblages the following actionsare applicable: CONFIG, CDMADPC, ADDCE, DELCE.

NOTE: For converged cell the following actions are applicable to a 1xEvolution - Data Only (1xEV-DO) carrier: CONFIG, CDMADPC,XMITC.

ADDCE: — Number of CEs to add:

1-55 — Non-Flexent

1-40 — Flexent and Flexent Modular Cell 4.0

BASEB: — BASEBAND MODULE CONTROL

NOTE: Options 105-115 apply to Analog in Flexent TDMAmicrocells. Options 110-115 are not valid if c is a TDMARA.

100 — Connect Clock and Tone (CAT) Board / turn on 1004Hz toneat 0 dBm.

101 — Connect CAT/turn on 1004Hz tone at -16 dBm.102 — Disconnect CAT/turn off tone.105 — Enable muting.106 — Disable muting.110 — Turn on SAT 0 (5970 Hz).111 — Turn off SAT 0.112 — Turn on SAT 1 (6000 Hz).113 — Turn off SAT 1.114 — Turn on SAT 2 (6030 Hz).115 — Turn off SAT 2.


CFR:CELL-4 Issue 28


CDMADPC: — CBR Power Control (Microcell).

800 — Select 20.5 dB RF power level.801 — Select 20.0 dB RF power level.802 — Select 19.5 dB RF power level.803 — Select 19.0 dB RF power level.804 — Select 18.5 dB RF power level.805 — Select 18.0 dB RF power level.806 — Select 17.5 dB RF power level.807 — Select 17.0 dB RF power level.808 — Select 16.5 dB RF power level.809 — Select 16.0 dB RF power level.810 — Select 15.5 dB RF power level.811 — Select 15.0 dB RF power level.812 — Select 14.5 dB RF power level.813 — Select 14.0 dB RF power level.814 — Select 13.5 dB RF power level.815 — Select 13.0 dB RF power level.816 — Select 12.5 dB RF power level.817 — Select 12.0 dB RF power level.818 — Select 11.5 dB RF power level.819 — Select 11.0 dB RF power level.820 — Select 10.5 dB RF power level.821 — Select 10.0 dB RF power level.822 — Select 9.5 dB RF power level.823 — Select 9.0 dB RF power level.824 — Select 8.5 dB RF power level.825 — Select 8.0 dB RF power level.826 — Select 7.5 dB RF power level.827 — Select 7.0 dB RF power level.828 — Select 6.5 dB RF power level.829 — Select 6.0 dB RF power level.830 — Select 5.5 dB RF power level.831 — Select 5.0 dB RF power level.832 — Select 4.5 dB RF power level.833 — Select 4.0 dB RF power level.834 — Select 3.5 dB RF power level.

CDMADPC: — CBR Power Control (Flexent ).

55 — Select -5.5 db RF power level.60 — Select -6.0 db RF power level.65 — Select -6.5 db RF power level..... Increment of 5 (0.5dB)...290 — Select -29.0 db RF power level.295 — Select -29.5 db RF power level.300 — Select -30.0 db RF power level.


Issue 28 CFR:CELL-5


CDMADPC: — CBR Power Control (Flexent Modular Cell 4.0).

00 — Select -0.0 db RF power level.05 — Select -0.5 db RF power level.10 — Select -1.0 db RF power level..... Increment of 5 (0.5dB)...290 — Select -29.0 db RF power level.295 — Select -29.5 db RF power level.300 — Select -30.0 db RF power level.

CDMADPC: — PCBR Power Control (Flexent CDMA Distributed BaseStation).

20 — Select -2.0 db RF power level.21 — Select -2.1 db RF power level..... Increment of 1 (0.1dB)...55 — Select -5.5 db RF power level.56 — Select -5.6 db RF power level.57 — Select -5.7 db RF power level..... Increment of 1 (0.1dB)...249 — Select -24.9 db RF power level.250 — Select -25.0 db RF power level.

CDMADPC: — BBA Power Control (Series II).

.. Increment of 5 (0.5dB).700 — Select -30 dB RF power level.701 — Select -28 dB RF power level.702 — Select -26 dB RF power level.703 — Select -24 dB RF power level.704 — Select -22 dB RF power level.705 — Select -20 dB RF power level.706 — Select -18 dB RF power level.707 — Select -16 dB RF power level.708 — Select -14 dB RF power level.709 — Select -12 dB RF power level.710 — Select -10 dB RF power level.711 — Select -8 dB RF power level.712 — Select -6 dB RF power level.713 — Select -4 dB RF power level.714 — Select -2 dB RF power level.715 — Select full power level.

NOTE: The allowable BBA power control values for the PCSCDMA minicell are:


CFR:CELL-6 Issue 28


705 — Select -20 dB RF power level.706 — Select -18 dB RF power level.707 — Select -16 dB RF power level.708 — Select -14 dB RF power level.709 — Select -12 dB RF power level.710 — Select -10 dB RF power level.711 — Select -8 dB RF power level.

CHANL: — SELECT CHANNEL NUMBER

NOTE: d must be configured to run the CHANL option.

chan# — 1-799 or 990-1023.chan# — 1-1999 (for TDMA PCS mini-cells).

NOTE: For TDMA PCS mini-cells only, the upper limit of the rangehas been extended to 1999.

CONFIG: — CONFIGURE A VOICE RADIO/BBA

149 — Disassociate a radio or group of radios (CDMA pilots only)or CDMA BBAs.

150 — Send configuration message to radios (set up CDMA pilotsonly) or CDMA BBAs.

151 — Select antenna face Omni (SII).152 — Select antenna face Alpha (SII).153 — Select antenna face Beta (SII).154 — Select antenna face Gamma (SII).155 — Select antenna face Delta (SII).156 — Select antenna face Epsilon (SII).157 — Select antenna face Zeta (SII).159 — Disassociate a radio or group of radios (both CDMA and

1xEV-DO pilots).160 — Send configuration message to radios (set up both CDMA

and 1xEV-DO pilots).

DELCE: — Number of CEs to delete:

1-55 — No-RCS1-40 — Flexent Micro and Flexent Modular Cell 4.0.

ECODC: — ENCODER CONTROL

NOTE: This choice is not valid if c is a TDMA RA.

201 — Request to send 10kHz tone.202 — Request to stop sending 10kHz tone.


Issue 28 CFR:CELL-7


PNOFFSET: — PN offset number (0-511).

RATDS: — RADIO TO DS0/DS1

NOTE: When c is an RCS, this option only applies to Analogradios.

500 — Connect RA to DS0.501 — Connect RA to DS0 1.502 — Connect RA to DS0 2.503 — Connect RA to DS0 3.504 — Connect RA to DS0 4.505 — Connect RA to DS0 5.506 — Connect RA to DS0 6.507 — Connect RA to DS0 7.508 — Connect RA to DS0 8.509 — Connect RA to DS0 9.510 — Connect RA to DS0 10.511 — Connect RA to DS0 11.512 — Connect RA to DS0 12.513 — Connect RA to DS0 13.514 — Connect RA to DS0 14.515 — Connect RA to DS0 15.516 — Connect RA to DS0 16.517 — Connect RA to DS0 17.518 — Connect RA to DS0 18.519 — Connect RA to DS0 19.520 — Connect RA to DS0 20.521 — Connect RA to DS0 21.522 — Connect RA to DS0 22.523 — Connect RA to DS0 23.524 — Connect RA to DS0 24.525 — Connect RA to DS0 25 (for E1 mode only).526 — Connect RA to DS0 26 (for E1 mode only).527 — Connect RA to DS0 27 (for E1 mode only).528 — Connect RA to DS0 28 (for E1 mode only).529 — Connect RA to DS0 29 (for E1 mode only).530 — Disconnect RA from DS0/DS1.540 — Connect RA to DS0 30 (for E1 mode only).541 — Connect RA to DS0 31 (for E1 mode only).600 — Connect RA to DS1 0.601 — Connect RA to DS1 1.602 — Connect RA to DS1 2.603 — Connect RA to DS1 3.604 — Connect RA to DS1 4.605 — Connect RA to DS1 5.606 — Connect RA to DS1 6.607 — Connect RA to DS1 7.608 — Connect RA to DS1 8.609 — Connect RA to DS1 9.


CFR:CELL-8 Issue 28


610 — Connect RA to DS1 10.611 — Connect RA to DS1 11.612 — Connect RA to DS1 12.613 — Connect RA to DS1 13.

TRKREQ: TRUNK LOOPBACK CONTROL

NOTE: If c is a non-RCS TDMA RA, UC must be specified.However, if the RA is associated with Packet-pipe then thetechnician can only use UC #3. When c is RCS, then thisoption applies only to Analog radios.

400 — Set trunk loopback.401 — Remove trunk loopback.

VRADPC: — VOICE RADIO POWER CONTROL

350 — Select -28 dB RF power level.351 — Select -24 dB RF power level.352 — Select -20 dB RF power level.353 — Select -16 dB RF power level.354 — Select -12 dB RF power level.355 — Select -8 dB RF power level.356 — Select -4 dB RF power level.357 — One of the following:

For a single radio only.Select 0 dB RF power level (0 attenuation level).

For use with the MULTI option only.Select full power level, at the maximum allowed bythe Voice Radio Attenuation Level (VRAL) setting.(The VRAL setting is configurable and is shown infields 8 and 9 of the ceqface form.)

NOTE: Use of the VRAL setting as the upper limitwith the MULTI option protects the LinearAmplifier Frame (LAF) from overload.

XMITC: — TRANSMITTER CONTROL

300 — Turn the radio transmitter on.301 — Turn the radio transmitter off.

f = Channel number (1-666). Must be used with multi-BBA and TRTU.

g = Radio Configuration:

1 — Default value.3

h = Overriding output message class (151-213). This option may be used onlyif the Virtual System Output Message Routing feature is supported.


Issue 28 CFR:CELL-9


i = Radio Carrier number — applies to Flexent Modular Cell 4.0 assemblages.CDMA carrier is required for ADDCE and DELCE. Carrier is optional forCONFIG and CDMADPC. If omitted, action applies to all carriers.

1-10 — for pre-R22.0 cells.1-18 — for R22.0 and later cells.

j = CBR Transmit Port (TXPORT) number (1-2). Flexent Modular Cell 4.0assemblages only. TXPORT is optional for XMITC. If omitted, action appliesto the first active TXPORT.

4. SYSTEM RESPONSE


NG = No Good. Necessary conditions for message execution where not met.




5. REFERENCES

IM/OM References:

Input MessagesSTOP:CFR-CELL

Output MessagesCFR-CELLOP-CELL

Other References:



CFR:CELL-10 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CFR RING

ID............. CFR:RINGRELEASE ....... 7.0 and laterTYPE .......... Input


**WARNING**If the ring initialization is successful any subsequent problems which causeit to go down will probably cause an IMS level 3 or higher initializationunless Manual Ring Mode is in effect. See the REPT MANUAL RING MODEoutput message for details.

**WARNING**

Use of this command with option LEVEL may be service–affecting andshould only be used after consulting with the appropriate customertechnical support group.

1. PURPOSE

Configures the ring to include or exclude ring node(s) from the active ring segment or, ifthe ring is down, initialize it. In addition, a level [0 3 4 5] ring recovery and a clearing ofring Error Analysis and Recovery (EAR) history can be executed.

2. FORMAT

CFR:RING [,a [,b] ,a [,b];EXCLUDE ,a [,b];INCLUDE] ,a;MOVFLT ,ZEROCNTS ,LEVEL c]!


a = Specifies a ring node or, if b is present, the first of a range of ring nodes (inthe direction of flow of ring 0).

a is of the form {RPCNx 0 LNx y}

RPCN — Indicates a ring peripheral controller node.

LN — Indicates a link node.

x — A Ring Node (RN) group number (00-63) with explicit leading zerofor group numbers less than 10.

y — The node’s position in the RN group (1-15).

b = Specifies the last node in the range begun by a.

b is of the form {RPCNx 0 LNx y}

c = Specifies the level of ring EAR recovery requested.

c is of the form {0 3 4 5}


Issue 28 CFR:RING-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCFR RING August 2005

INCLUDE = This is a request to make ring nodes part of the active ring segment. This isthe default state for this command.

If node(s) are specified, only those nodes will be added to the active ringsegment in response to this command.

If no nodes are specified, the new configuration will include as many nodesas possible. If the ring is down, it will be initialized.

If an isolated ring segment currently exists, the requested node or nodesmust include the BISO’s and/or EISO’s nearest isolated neighbor node, orsegment, so as not to fragment the existing isolated segment.

EXCLUDE = This is a request to isolate specified node(s) from the active ring segment.This may cause inclusion or isolation of other nodes to form a workable ring.

Active ring nodes cannot be isolated.

A section of the ring cannot be isolated such that the remaining active ringsegment is too short. That is, the active ring segment must contain aminimum combination of ring nodes and interframe buffers to allowsimultaneous propagation of long messages plus the token message. Notethat when the system attempts to choose active BISO and EISO ring nodes toisolate a given requested range of node(s), this threshold could be crossed.

If an isolated segment currently exists, the node or nodes requested musteither include the BISO and/or EISO node(s) or must already be excludedfrom the active ring segment.

MOVFLT = This is a request to move an indication of a faulty ring interface from thecurrently isolated ring node to the adjacent ring node, a, and to reconfigurethe ring so that a becomes the isolated node.

Automatic ring error analysis cannot always determine which of twoadjacent nodes is at fault. When manual maintenance indicates that thewrong ring node has been isolated, this command is used to correct the ringconfiguration. Such correction may not be possible using other methodsbecause it may be essential to have an isolated node adjacent to the fault andthe ring may be too small to allow both nodes to be isolated, eventemporarily.

This form of the command is accepted only when a single node is currentlyisolated and the specified node, a is adjacent (for example: a is the BISO orEISO ring node) and is not undergoing restoral.

ZEROCNTS = This is a request to clear the history of past level 0, level 3, level 4 and level 5ring recoveries. Also, ring EAR’s mode will be set to the stable mode.


CFR:RING-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CFR RING

If this request is typed when the ring status is unstable, the request will berejected.

If this request is typed within the confidence interval associated with asuccessful ring restoration, approximately 5 seconds, the request will berejected.

If ring EAR’s mode is the quasi-instable mode, then after this request iscompleted, ring EAR’s mode will be switched to the stable mode and theinformation "RING ERROR THRESHOLD EXCEEDED" will be removedfrom 1105 display page.

The key idea of this request is to clear the ring EAR recovery history and setring EAR’s mode to the stable state. Consequently, when the next ringcommunication failure occurs, ring EAR will first try to execute the lowestlevel ring EAR recovery.

LEVEL c = Use of this option may be service-affecting. See the WARNING on the firstpage of this message.

This is a request to execute a specific level ring recovery and clear therecovery history of ring EAR.

If this request is typed when the ring status unstable, this request will berejected.

If this request is typed within the confidence interval associated with asuccessful ring restoration, approximately 5 seconds, the request will berejected.

If ring EAR’s mode is the quasi-instable mode, then after this request iscompleted, ring EAR’s mode will be switched to the stable mode and theinformation "RING ERROR THRESHOLD EXCEEDED" will be removed fromthe 1105 display page.

This command will first zero the ring recovery history and then execute therequested level of ring recovery. This ring recovery will not be counted inring EAR’s recovery history. If a ring communication failure occurs duringthe manual level [0 3 4 5] ring recovery, ring EAR will trigger a level 3 ringrecovery.

Ring configurations established by this command have no special permanence. They arenot remembered as having been requested manually and they do not change the ringinterface hardware maintenance states of the nodes. For example, a ring segment isolatedby this command and not containing a ring fault may be included back into the active ringsegment by any subsequent ring configuration change, such as by a fault recovery,diagnostic, restore or subsequent CFR:RING command. An exception is that nodes in theGROW major state will always be kept isolated to prevent installation from causing ringrecoveries.


Issue 28 CFR:RING-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksCFR RING August 2005

The ring can not be reconfigured using the INCLUDE or EXCLUDE options if either thecurrent BISO and/or EISO ring node is not active. A ring with an inactive BISO and/orEISO node is in a transient state, restoral of this node(s) will be given top priority. TheMOVFLT option may be used subject to limitations described above.

When the ring is down, the CFR:RING command (without options) will attempt toinitialize the ring. This requires at least one RPCN node in the STBY state. (A successfulRST:RPCN input command will leave the RPCN node in the STBY state when the ring isdown). The ring initialization will not, in itself, restore any IUNs to service.

Ring initializations are much slower than ring reconfigurations. Allow several minutes perone hundred nodes equipped in the office.

4. SYSTEM RESPONSE

NG = No Good. The request was not accepted, reason to follow.

RL = Retry Later. The CFR:RING command can not execute at this time, reason tofollow.

The ring is reconfigured or initialized as per the INCLUDE or EXCLUDE or MOVFLT orLEVEL c keyword explanation above.

NOTE: Ring reconfigurations abort diagnostics of ring nodes.

5. REFERENCES

IM/OM References:

Input MessagesEXC:OFLBOOTSTOP:OFLBOOT

Output MessagesCFR-RINGEXC-OFLBOOTREPT-MANUALSTOP-OFLBOOT

Other References:


254-303-111 3B20D and 3B21D PDS Output Messages Manual

401-661-045 Common Network Interface (CNI) Ring Maintenance- International Link Node Signaling Link Operating Procedures Section


CFR:RING-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CHG GEN

ID............. CHG:GENRELEASE ....... 7.0 and laterTYPE .......... Input

1. PURPOSE

Changes the Common Network Interface (CNI) incore view of the CNI Generic ID. It is tobe used once at the completion of Broadcast Warning Message (BWM) additions or genericupdates.

2. FORMAT

CHG:GEN!


See Purpose.

4. SYSTEM RESPONSE

None.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesCHG-GEN



Issue 28 CHG:GEN-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCHG GEN August 2005



CHG:GEN-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CHG MRVT

ID............. CHG:MRVTRELEASE ....... 7.0 and laterTYPE .......... Input

1. PURPOSE

Changes or displays the Message Routing Verification Test (MRVT) Delay (D) parameterwhich is used in the calculation of the T1 timer.

2. FORMAT

CHG:MRVT[ a]!


a = New value of the delay parameter (8-15 seconds).

NOTE: If this argument is not present on the command line, the currentvalue of the delay parameter is displayed.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by a CHG-MRVT output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesEXC:MRVT

Output MessagesCHG-MRVTEXC-MRVTREPT-MRVR



Issue 28 CHG:MRVT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCHG MRVT August 2005



CHG:MRVT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CHG PAUTH

ID............. CHG:PAUTHRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Changes the password for a given user Identity (IDENT). Either password prefix orpassword suffix or both must be entered.

2. FORMAT

[1] CHG:PAUTH:IDENT "a",{PSSWDPFX "b" PSSWDSFX "c"}!

[2] CHG:PAUTH:IDENT "a",PSSWDPFX "b",PSSWDSFX "c"!



b = Password Prefix (PSSWDPFX) in three letters and/or digits.

c = Password Suffix (PSSWDSFX) in six to 13 characters.

4. SYSTEM RESPONSE



— PARAMETER(S) MISSINGNecessary parameters are missing. Either a password prefix orpassword suffix or both must be entered.

— PASSWORD PREFIX ILLEGAL LENGTHThe given password prefix is not equal to three characters in length.

— PASSWORD PREFIX NOT UNIQUEThe given password prefix already exists in the password authorityadministration.

— PASSWORD SUFFIX ILLEGAL LENGTHThe given password suffix is greater than 13 characters in length.


OK = Good. Password and identity has been changed in the database.

RL = Retry Later. One of these messages may follow:



Issue 28 CHG:PAUTH-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCHG PAUTH August 2005

5. REFERENCES

IM/OM References:

Input MessagesADD:PAUTHDEL:PAUTHVFY:PAUTHRNM:PSSWD




CHG:PAUTH-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CHG PROFL

ID............. CHG:PROFLRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Adds or removes a Command Group (COMGR) from a profile Identity (IDENT). Thisallows a profile to contain a set of command groups. The IDENT must already exist in theProfile (PROFL) database.

2. FORMAT

CHG:PROFL:IDENT "a",ACTION b,COMGR c,[-d],[-e],[-f],[-g],[-h],[-i],[-j],[-k][-l],[-m],[-n],[-o],[-p],[-q,][-r]!


a = Identity of the profile in one to eight letters and/or digits.

b = The action to perform on the profile, either INCLUDE or EXCLUDE thegiven command group(s).

c-r = Command group.

4. SYSTEM RESPONSE

NG = No Good.

— PASSWORD ENHANCEMENT NOT ACTIVATEDThis command is valid only for applications running with the PasswordEnhancement feature enabled.

— PROFILE IDENTITY DOES NOT EXISTThe given profile identity does not exist in the profile authorityadministration.

— UNABLE TO ACCESS PROFILE ADMINISTRATIONProfile authority information is inaccessible.

OK = Good. Command group successfully added to or removed from profile.

RL = Retry Later.

— PROFILE ADMINISTRATION UNDER UPDATEProfile information is currently being updated.

5. REFERENCES

IM/OM References:

Input MessagesADD:PCGRPADD:PROFLDEL:PCGRPDEL:PROFLVFY:PCGRPVFY:PROFL


Issue 28 CHG:PROFL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCHG PROFL August 2005

Output MessagesVFY-PROFL



CHG:PROFL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CHG SLK

ID............. CHG:SLKRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Requests a change in the minor state of a Signaling Link (SLK).

A request is made to change the minor state of the particular SLK to the specified state orto request the transfer of the SLK from the active to the standby Voice Frequency Link(VFL). It should be noted that entering either of these requests does not guarantee thespecified action. Successful SLK prove-in is required to accomplish either of theserequested actions. For example, when a request is made to change a link that is in theMOOS state to the IS state, the link is first moved from MOOS to OOS. Once the link is in theOOS state, automatic link prove-in can begin. It is not until successful prove-in has beenreached that the link is moved to the IS state.

The minor states TEST and MOOS are maintained by the system during a node removal andrestoral. However, these states are lost during a system initialization. After a systeminitialization, links in the UNAVAILABLE major state will be set to the GROW minor state.Links in the AVAILABLE major state will start in the OOS minor state after initialization,and will attempt to move to the IS minor state automatically.

2. FORMAT

CHG:SLK(a,b); c!




c = Requested minor state:

ARST — Auto restore service. Return a signaling link to service from theMOOS state. The link will attempt to move to the IS state. Valid formajor state AVL, minor state MOOS.

NOTE: ARST and IS are equivalent commands.

FIS — This option may be used to force manual out-of-service restrictionsoff of a CCS7 link. Valid for CCS7 signaling links with major stateAVL, MINOR state MOOS or OOS.

GROW — Growth. This state is used during link installation and de-installation. Valid for signaling links with major state UNA.

IS — In service. Return a signaling link to service from the MOOS state.The link will attempt to move to the IS state. Valid for major stateAVL, minor state MOOS.

NOTE: ARST and IS are equivalent commands.


Issue 28 CHG:SLK-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCHG SLK August 2005

MOOS — Manual out-of-service. Signaling link cannot handle traffic.Typically, when performing maintenance on the link. Valid forsignaling links with major state AVL. The following minor statetransitions are allowed, depending on link type:

For CC7 or CCIS6 links:

OOS — MOOS, if alternate links are IS.IS — MOOS, if alternate links are IS.

NOTE: MOOS state may be automatically removed by the system ifall alternate links are lost.

TEST — Test. This state is used during link installation and de-installation.Valid for signaling links with major state UNA.

4. SYSTEM RESPONSE

None.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesCHG-SLK

Other References:

401-661-045 Common Network Interface (CNI) Ring Maintenance- Ring and Ring Node Maintenance Procedures Section


CHG:SLK-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CHG SRVT

ID............. CHG:SRVTRELEASE ....... 7.0 and laterTYPE .......... Input

1. PURPOSE

Requests that the SCCP Routing Verification Test (SRVT) delay parameter, which is usedin the calculation of the T2 timer, be changed or displayed. The expiration of the T2 timersignifies the end of the waiting period for the reception and processing of all expectedSCCP Routing Verification Acknowledgement (SRVA) messages.

If a request is made to change the delay parameter, and the requested value is withinrange, it is written onto disk and the delay parameter is updated to the new value. Thisnew value becomes the new "default" that will be read in on initializations. The initialdefault is 12.

2. FORMAT

CHG:SRVT[ a]!


a = New value of the delay parameter (8-16).

NOTE: If this argument is not present on the command line, the currentvalue of the delay parameter is displayed to the maintenanceoutput class.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by a CHG-SRVT output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesEXC:SRVTOP:TPC

Output MessagesCHG-SRVTEXC-SRVTOP-TPC



Issue 28 CHG:SRVT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCHG SRVT August 2005



CHG:SRVT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CLR ACKDB

ID............. CLR:ACKDBRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Invalidates the segment name of the ACKDB so that the next invocation of either the craftshell or Display Administration Process reinitializes it. Current running process willcontinue to use the old copy of the ACKDB until they are terminated.

2. FORMAT

CLR:ACKDB!


See Purpose.

4. SYSTEM RESPONSE

IP = In Progress.

5. REFERENCES

IM/OM References:

Input MessagesSTOP:EXC-ANYSTOP:EXC-USER


Other References:




Issue 28 CLR:ACKDB-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCLR ACKDB August 2005



CLR:ACKDB-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CLR APPSLT

ID............. CLR:APPSLTRELEASE ....... 20.0 and laterTYPE .......... Input

1. PURPOSE

Requests the reset of the Periodic Signaling Link Test (PSLT) inhibit flag of one or allApplication Processor (AP) signaling links.

2. FORMAT

CLR:APPSLT, SS7 ["a" ALL]


a = Signaling System 7 (SS7) link number (1-512).

ALL = Resets the PSLT inhibit flag of all AP signaling links.

4. SYSTEM RESPONSE

?E = Error. An invalid value was entered.


5. REFERENCES

IM/OM References:

Input MessagesMON:APSLKOP:APPSLTSET:APPSLT

Output MessagesMON-APSLKREPT-SET-APPSLT



Issue 28 CLR:APPSLT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCLR APPSLT August 2005



CLR:APPSLT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CLR CELL

ID............. CLR:CELL-SYNCRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Clears all Reference Frequency Timing Generator (RFTG) count buffers.

2. FORMAT

CLR:CELL a, CELLSYNC [ CLASS b ]



b = Overriding output message class (151-213). This option may be used onlyif the Virtual System Output Message Routing feature is supported.

4. SYSTEM RESPONSE



The CLASS option was used but its Virtual System Output MessageRouting feature had not been turned on.




5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesCLR-CELLSYNC

Other References:



Issue 28 CLR:CELL-SYNC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCLR CELL August 2005



CLR:CELL-SYNC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CLR DB DNLD

ID............. CLR:DB-DNLDRELEASE ....... 19.0 and laterTYPE .......... Input


**WARNING**This command should only be used at the direction of technical supportpersonnel. The improper use of this command could result in databasecorruption in the Call Processing/Database Nodes (CDNs) and severelyimpact call delivery.

1. PURPOSE

Places the database download process into the normal operation mode.

Clears the effects of the SET:DB-DNLD input command if the the first group of CDNshave not completed a database download using the new database sizes.

The unconditional option can be used to return the database download process to normaloperation mode regardless of the success or failure of any previous CDN databasedownload attempts.

2. FORMAT

CLR:DB DNLD[;UCL]!



4. SYSTEM RESPONSE

OK = Good. Places DBcdninit process in normal operation mode if a CLRDBRESIZE message is present in /etc/log/DBIBLOG1. If message is notpresent, contact Lucent Technologies Customer Technical AssistanceManagement for support.

5. REFERENCES

IM/OM References:

Input MessagesSET:DB-DNLD




Issue 28 CLR:DB-DNLD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCLR DB DNLD August 2005



CLR:DB-DNLD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CLR DB SU

ID............. CLR:DB-SURELEASE ....... 17.0 and laterTYPE .......... Input

1. PURPOSE

Places the database download process into the normal operation mode.

Clears the effects of the SET:DB-SU command if the software update apply is aborted andthe Call Processing/Database Nodes (CDNs) are not to be removed and restored. Note,DBcdninit places itself back into normal operation mode after all CDNs on the systemhave been removed and restored following a SET:DB-SU command.

2. FORMAT

CLR:DB SU!


See Purpose.

4. SYSTEM RESPONSE

OK = Good. Places DBcdninit process in normal operation mode.

5. REFERENCES

IM/OM References:

Input MessagesSET:DB-SU




Issue 28 CLR:DB-SU-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCLR DB SU August 2005



CLR:DB-SU-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CLR EMERDMP

ID............. CLR:EMERDMPRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Clears the emergency dump partition status flag. The flag is set whenever an emergencydump is written to disk. Until the flag is cleared, it causes the REPT EMERGENCY DUMPPARTITION FULL output message to be printed periodically and prevents a newemergency dump being written to disk until 12 hours later. The user is thus providedsufficient time to copy out the partition contents onto a tape.

2. FORMAT

CLR:EMERDMP!


See Purpose.

4. SYSTEM RESPONSE

OK = Good. Emergency dump partition is marked empty.

PF = Printout Follows. Followed by a CLR-EMERDMP output message.

5. REFERENCES

IM/OM References:

Input MessagesCOPY:TAPE-EMERDMPOP:EMERSTAT

Output MessagesCLR-EMERDMPREPT-EMERGENCY

Other References:



Issue 28 CLR:EMERDMP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCLR EMERDMP August 2005



CLR:EMERDMP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CLR FANALM

ID............. CLR:FANALMRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Performs a remote reset of the computer Fan Alarm (FANALM). The points are identifiedby physical location (as in Format 1) or by logical address (as in Format 2).

2. FORMAT

[1] CLR:FANALM;UNIT a:PT {b (b,b[,b,b...])}!

[2] CLR:FANALM;GRPN "c",DUPID d: PT{e (e,e[e,e])}!


a = Scanner Signal Distributor (SCSD) unit number (0-16).

b = Physical point number on SCSD (0-31).

c = Name of the logical SCSD group. Logical SCSD group names for fan alarmsbegin with the prefix FANA. Examples are:

FANACU0FANACU1

d = Duplex identifier (0-1).

e = Logical point number (0-5).

4. SYSTEM RESPONSE

NG = No Good. SCSD administrator process is not active; no communicationwith SD points is possible.

PF = Printout Follows. Followed by a CLR-FANALM output message.

RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesALW:SCSDINH:SCSDOP:SCSD


Issue 28 CLR:FANALM-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCLR FANALM August 2005

Output MessagesCLR-FANALMREPT-FAN-SINGLEREPT-FAN-MULTIPLEREPT-SCSDC

Other References:


254-341-110 3B20D Computer Kernel and Basic Services Software Subsystem Description


CLR:FANALM-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CLR FILESYS DIR

ID............. CLR:FILESYS-DIRRELEASE ....... 8.0 and laterTYPE .......... Input


**WARNING**Incorrect use of this command can result in the removal of needed filesystem directories.

1. PURPOSE

Removes a directory from the file system. The directory must be empty (no files orsubdirectories stored under the directory name) before it can be removed.

2. FORMAT

CLR:FILESYS:DIR, FN "a"!


a = Pathname of the directory to be removed. See the User Guidelines in thismanual for definitions of pathname and directory.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by a CLR-FILESYS-DIR output message.

5. REFERENCES

IM/OM References:

Input MessagesCLR:FILESYS-FILEIN:FILESYS-DIROP:ST-LISTDIR

Output MessagesCLR-FILESYS-DIR

Other References:




Issue 28 CLR:FILESYS-DIR-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCLR FILESYS DIR August 2005



CLR:FILESYS-DIR-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CLR FILESYS FILE

ID............. CLR:FILESYS-FILERELEASE ....... 8.0 and laterTYPE .......... Input


**WARNING**Incorrect use of this command can result in the removal of needed files andprocesses.

1. PURPOSE

Removes a file from a directory.

2. FORMAT

CLR:FILESYS:FILE, FN "a"!


a = Pathname of the file. See the User Guidelines section in this manual fordefinitions of pathname and file.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by a CLR-FILESYS-FILE output message.

5. REFERENCES

IM/OM References:

Input MessagesOP:ST-LISTDIR

Output MessagesCLR-FILESYS-FILEOP-ST-LISTDIR

Other References:




Issue 28 CLR:FILESYS-FILE-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCLR FILESYS FILE August 2005



CLR:FILESYS-FILE-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CLR IMCAT

ID............. CLR:IMCATRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Invalidates the memory segments of the old input message catalog, forcing the new one tobe loaded into the main memory. This message is used during a field update of the inputmessage catalog.

2. FORMAT

CLR:IMCAT!


See Purpose.

4. SYSTEM RESPONSE


— FILE INACCESSIBLEFile did not open.

— SEGCODE CANNOT BE DETERMINEDNo segment names.

— SEGMENT NAME CANNOT BE CLEAREDSegments not marked invalid.

OK = Good. Segments are marked invalid.

PF = Printout Follows. Followed by a CLR-IMCAT output message.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesCLR-IMCAT

Other References:



Issue 28 CLR:IMCAT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCLR IMCAT August 2005



CLR:IMCAT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CLR IODRV

ID............. CLR:IODRVRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Allows option setting in the Input/Output Processor (IOP) driver to suppress IOP drivermessages.

NOTE: Entering this command without the options turns off all severity levels,handler IDs and classes, but leaves the MSGSAVE flag as is.

2. FORMAT

CLR:IODRV[;LVL a (a,a[,a])][,ID b (b,b[,b...])][,CLASS c (c,c[,c...])] [,MSGSAVE]!


a = Severity level (1-3), where one is the most severe setting and three is theleast severe.

b = Administrative Module (AM) handler identification:

ALL — Turns on all IDs.APH — Application protocol handler.APPL1-APPL5 — Reserved for application handlers.CIH — Craft interface handler.DUIH — Direct user interface handler.IOP — Input/output driver.MAINT — Maintenance handler.MTH — Magnetic tape handler.NPH — Network protocol handler.SCSDH — Scanner and signal distributor handler.SDLH — Synchronous data link handler.SPH — Session protocol handler.TPH — Transport protocol handler.PPH — Presentation protocol handler.

c = Thirty-two classes available.

MSGSAVE = IOP error messages will not be saved in the IODRVLOG logfile.

4. SYSTEM RESPONSE

NG = No Good. Conflict with system status.

PF = Printout Follows. Followed by a CLR-IODRV output message.


Issue 28 CLR:IODRV-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCLR IODRV August 2005

5. REFERENCES

IM/OM References:

Input MessagesOP:IODRVSET:IODRV

Output MessagesCLR-IODRVOP-IODRV



CLR:IODRV-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CLR MHD MAEC

ID............. CLR:MHD-MAECRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Clears a given MHD’s Media Access Error Counter (MAEC). The MAEC for a given MHDis set to zero.

A MAEC counts all errors which could be classified as bad disk blocks (media defects). Ifupon investigation some or all of these errors are attributed to specific bad disk blocks, thebad disk blocks should be mapped out using the LOAD:MHD;DEFECT and INIT:MHDcommands. This procedure will reset the specified MHD’s MAEC back to zero.

If upon further investigation none of these errors are attributed to media defects, thenmapping bad blocks and formatting the disk is not necessary. In this case, theCLR:MHD;MAEC command is used to reset the specified MHD’s MAEC back to zero.

2. FORMAT

CLR:MHD a;MAEC!


a = MHD member number.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by a CLR-MHD-MAEC output message.

5. REFERENCES

IM/OM References:

Input MessagesINIT:MHDLOAD:MHD-DEFECTVFY:MHD

Output MessagesCLR-MHD-MAECREPT-DKDRV

Other References:

254-303-106 3B20D and 3B21D Computers UNIX RTR Operating System System MaintenanceManual - File System Maintenance, Procedure for Handling Disk Errors


Issue 28 CLR:MHD-MAEC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCLR MHD MAEC August 2005



CLR:MHD-MAEC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CLR PTN MHD

ID............. CLR:PTN-MHDRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Clears (initializes with zeroes) partitions on a specified disk. The partitions to be clearedare determined from a specfile (default /etc/clearspec). Both the disk specified and itsmate should be active before this message is entered.

This command will be used by the applications that have Automatic Message Accounting(AMA) partitions (on removable media disk packs) which need to be cleared whenever adisk copy is generated.

2. FORMAT

CLR:PTN;MHD a [;SPECF "b"]!


a = Identifies of disk unit to be initialized with zeroes.

b = Pathname of specification file containing list of partition names that will beinitialized with zeroes. Default will be /etc/clearspec. See the UserGuidelines section of this manual for definitions of pathnames and files.

4. SYSTEM RESPONSE

NG = No Good. Process not initiated.

PF = Printout Follows. Followed by an INIT-PTN output message.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesCLR-PTN



Issue 28 CLR:PTN-MHD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCLR PTN MHD August 2005



CLR:PTN-MHD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CLR RUTIL

ID............. CLR:RUTILRELEASE ....... 7.0 and laterTYPE .......... Input



1. PURPOSE

Clears all Ring Generic Access Package (RGRASP) breakpoints in the specified node.

2. FORMAT

CLR:RUTIL(a, b), {AP NP}!




4. SYSTEM RESPONSE

PF = Printout Follows. Followed by a CLR-RUTIL output message.

5. REFERENCES

IM/OM References:

Input MessagesALW:RUTILINH:RUTILOP:RUTILWHEN:RUTIL

Output MessagesCLR-RUTIL



Issue 28 CLR:RUTIL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCLR RUTIL August 2005



CLR:RUTIL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CLR RUTILFLAG

ID............. CLR:RUTILFLAGRELEASE ....... 7.0 and laterTYPE .......... Input



1. PURPOSE

Clears specific Ring Generic Access Package (RGRASP) breakpoints in a specified node.

2. FORMAT

CLR:RUTILFLAG(a, b), {AP NP}; BP c!




c = Specific breakpoint to be cleared.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by a CLR-RUTILFLAG output message.

5. REFERENCES

IM/OM References:

Input MessagesALW:RUTILFLAGINH:RUTILFLAG

Output MessagesCLR-RUTILFLAG



Issue 28 CLR:RUTILFLAG-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCLR RUTILFLAG August 2005



CLR:RUTILFLAG-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CLR SRST

ID............. CLR:SRSTRELEASE ....... 7.0 and laterTYPE .......... Input


**WARNING**Use of this command can be service affecting.

1. PURPOSE

Clears the status of a route making it available, and stops the Signaling Route Set Test(SRST) for the route. This is used to reduce the amount of unnecessary signaling networkmanagement message traffic for primary or alternate routes.

Format 1: ANSI Standard Format.

Format 2: Lucent Format.

2. FORMAT

[1] CLR:SRST;DPC (a,b[,c])[;LS d]!

[2] CLR:SRST;DPC (a,e,f[,c])[;LS d]!


a = Destination Point Code (DPC) network identifier (1-254).

b = DPC network cluster (0-255).

c = DPC member identifier (0-255). Include this field if you want to stop theSRST for a single member of a cluster. Do not include this field if you wantto stop the SRST for an entire cluster.

d = Link set (1-511). Include this field if you want to stop the SRST for one linkset. Do not include this field if you want to stop the SRST for all the link setsused by the DPC.

e = Region identifier (0-31).

f = Cluster identifier (0-7).

4. SYSTEM RESPONSE

NG = No Good. The message was not recognized. Repeat the request.

PF = Printout Follows. The request was received and will be acted on. Aprintout will follow later to explain in detail the results of the workinitiated.

RL = Retry Later. System resources are unavailable to execute command now.


Issue 28 CLR:SRST-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCLR SRST August 2005

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesCLR-SRST



CLR:SRST-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CLR SS7SRST

ID............. CLR:SS7SRSTRELEASE ....... 23.0 and laterTYPE .......... Input

1. PURPOSE

Clears the route status for the specified point code.

If the POPCLU keyword is used the command will clear the route status for the specifiedpoint code and if the given point code is a Populated Cluster (POPCLU), then the routestatus will be cleared for all other members in the same POPCLU whose configured routeis the same as the populated cluster.

Hexadecimal 24 bit point code is used for the ANSI or China point code format, and 14 bitpoint code is used for ITU-T (International Telecommunication Union TelecommunicationStandardization Sector) point code format. No matter which point code format is used insystem, if ALL keyword is used, the command will clear all point codes (for any point codeformat) with an abnormal status.

NOTE: If there are static members in the populated cluster which use a different routethan the populated cluster, then those routes will NOT be cleared.

This input command will allow the technician to clear the status of the route making itavailable for use, and will stop the Signaling Route Set Test (SRST) for the route.

Use of this input command is only allowed when the High Speed SS7 Link (HSL) or LowSpeed SS7 Link (LSL) feature is activated in the Feature Activation File (FAF).

2. FORMAT

[1] CLR:SS7SRST "aaaaaa"[, POPCLU]

[2] CLR:SS7SRST "bbbbb"

[3] CLR:SS7SRST ALL


aaaaaa = Point code value (6 digit hex number, for example: "e61000").

bbbbb = Point code value (5 digit decimal number, for example: "61000").

4. SYSTEM RESPONSE

?E = Error. Error in input command format.


PF = Printout Follows. Followed by a CLR-SS7SRST output message.

RL = Retry Later.


Issue 28 CLR:SS7SRST-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCLR SS7SRST August 2005

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesCLR-SS7SRST



CLR:SS7SRST-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CLR UMEM

ID............. CLR:UMEMRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Causes the definition of an computer Generic Access Package (GRASP) transfer trace to beremoved. The trace goes into the UNDEF state with successful completion of the message.

2. FORMAT

CLR:UMEM [;UCL]!


UCL = Unconditional execution.

4. SYSTEM RESPONSE

?A = Action field contains an error. INVALID KEYWORDMessage not allowed in a WHEN action list.

?I = Identification Field contains an error. General syntax error.

NG = No Good. Includes one of the following:

— TRACE NOT DEFINEDThe trace is not defined.

— UCERRThe circuit is unavailable.

PF = Printout Follows. Followed by a CLR-UMEM output message.

RL = Retry Later. Or wait for previous OP:UMEM or OP:UMEM;MCH to complete.The system is in an overload condition.

5. REFERENCES

IM/OM References:

Input MessagesINIT:UMEMOP:UMEMOP:UTIL

Output MessagesCLR-UMEMOP-UTIL

Other References:



Issue 28 CLR:UMEM-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCLR UMEM August 2005



CLR:UMEM-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CLR UTIL

ID............. CLR:UTILRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Removes all currently defined computer Generic Access Package (GRASP) breakpoints;clears definitions.

2. FORMAT

CLR:UTIL[;RESET]!


RESET = The RESET option causes breakpoint numbering to be reinitialized; the nextbreakpoint defined will be given the number 1.

4. SYSTEM RESPONSE

?A = Action field contains an error.

INVALID KEYWORDCommand not allowed in a WHEN action list.

NG = No Good. No GRASP breakpoints are currently defined.

PF = Printout Follows. Followed by a CLR-UTIL output message.


5. REFERENCES

IM/OM References:

Input MessagesCLR:UTILFLAGOP:UMEMOP:UTILWHEN:PIDWHEN:UID

Output MessagesCLR-UTILOP-UTIL

Other References:



Issue 28 CLR:UTIL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCLR UTIL August 2005



CLR:UTIL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CLR UTILFLAG

ID............. CLR:UTILFLAGRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Removes the specified computer Generic Access Package (GRASP) breakpoint and clearsthe definition.

2. FORMAT

CLR:UTILFLAG a[;RESET]!


a = Numeric identifier (one or more decimal digits) for the breakpoint to becleared.

RESET = If a is the last remaining defined breakpoint, then the RESET option causesbreakpoint numbering to be reinitialized; the next defined breakpoint will begiven the number 1. If a is not the last defined breakpoint, then the RESETkeyword is ignored.

4. SYSTEM RESPONSE

NG = No Good. Identifier does not correspond to a currently definedbreakpoint.

PF = Printout Follows. Followed by a CLR-UTILFLAG output message.


5. REFERENCES

IM/OM References:

Input MessagesCLR:UTILOP:UMEMOP:UTILWHEN:PIDWHEN:UID

Output MessagesCLR-UTILFLAGOP-UTILWHEN-PIDWHEN-UID


Issue 28 CLR:UTILFLAG-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCLR UTILFLAG August 2005

Other References:



CLR:UTILFLAG-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CMPR DISK CORE

ID............. CMPR:DISK-CORERELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Compares the text portions of the disk and core images of a non-killable process.Equipment Configuration Database Library (ECDLIB), Public Library (PLIB), and3bsgen.kern can also be compared.

2. FORMAT

CMPR:DISK,CORE,FN "a"; [, OPTNM "b",MPT "c",MHDNUM "d"]!


a = Pathname of the file. See the User Guidelines in this manual for definitionsof pathname and file.

b = Special device file name on offline partition (for example: /dev/root).

c = Pathname of mount point.

d = MHD number.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by a CMPR-DISK-CORE output message.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesCMPR-DISK-CORE

Other References:




Issue 28 CMPR:DISK-CORE-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCMPR DISK CORE August 2005



CMPR:DISK-CORE-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 CMPR MHD

ID............. CMPR:MHDRELEASE ....... 13.0 and laterTYPE .......... Input


**WARNING**Incorrect use of this command can degrade system performance. Thiscommand should not be used without expert technical assistance.

1. PURPOSE

Compares the contents of two disks or two disk partitions. A disk partition may reside onthe disk of its duplex mate, or on an arbitrary disk. Also, both disk partitions may resideon the same disk.

Only one CMPR:MHD or COPY:DIFF command is allowed to run at one time. If more thanone is attempted, the DFC driver will deny the request and output an error code to thateffect.

2. FORMAT

CMPR:MHD a [,PTN {b c-d}];[MATE MHD e] [,PTN {f g-h}][:BLOCKS i,RO]!


a = First member number.

b and f = Partition numbers within a range of (0 to 63), or list of partitions (r1, r2, r3,..., rn) where the list may include 64 entries.

Default will be all but the FREE, UNASGN, DIAG, SWAP, and PDUMPpartitions.

c-d = A range of partition numbers where a list of up to 32 ranges (p0-p1, p2-p3,p4-p5, ..., pm-pn) may be specified. A range has the format c-d where dmust be greater than c.

e = Second member number. If MHD e or MATE is not specified, MATE is thedefault.

g-h = A range of partition numbers where a list of up to 32 ranges (p0-p1, p2-p3,p4-p5, ..., pm-pn) may be specified. A range has the format g-h where hmust be greater than g.


Issue 28 CMPR:MHD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCMPR MHD August 2005

i = An integer value indicating the size of the Input/Output (I/O) buffers as amultiple of disk blocks. The legal values are 1-256. If BLOCKS is notspecified, the default is 256. However, if BLOCKS is not specified, and the ROoption is used, then the default is 128.

RO = All blocks on specified Moving Head Disks (MHDs) or partitions will be readinto memory, but no comparison will be performed. If MHD e or MATE is notspecified, the reads will only be performed on MHD a.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by a CMPR-MHD output message.

5. REFERENCES

IM/OM References:

Input MessagesCMPR:MHDCOPY:DIFF-SRC-MHDDUMP:MHD-BLOCKSTOP:CMPR-MHD

Output MessagesCMPR-MHD

Other References:



CMPR:MHD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COPY ACTDISK

ID............. COPY:ACTDISKRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Copies a file from an active disk to an Off Line (OFL) or Out Of Service (OOS) disk. Thefile can be a regular file, a contiguous file (type "C" or "x"), or a block device (type "b",partition or file system). For a regular or contiguous file, the destination file will be createdwith type, owner, and permission flags similar to those of the source file.

2. FORMAT

COPY:ACTDISK :MHD a ,SRC "b" ,PTN "c" [,DEST "d"]!


a = Specifies destination disk unit (0-255). This disk should not be active.

b = Full pathname of the file to be copied. This file should exist on an active disk.See the User Guidelines in this manual for definitions of pathname and file.

c = Special device filename or number of the destination partition on thenon-active disk. If a name is specified, then this partition should exist on theactive disk.

d = A pathname where the file is to be written, on the non-active file system. Ifthis name is not specified, the path name of the source file will be used. If thename starts with a /, then the mount point will be excluded. This nameshould not be specified if the source is a partition or file system.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by a COPY-ACTDISK output message.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesCOPY-ACTDISK



Issue 28 COPY:ACTDISK-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOPY ACTDISK August 2005



COPY:ACTDISK-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COPY ADDR

ID............. COPY:ADDRRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Copies data from virtual addresses in main memory to other virtual addresses, registers,or computer Generic Access Package (GRASP) utility variables as a response to abreakpoint.

Indirect addressing may be specified. The first listed offset is added to the value of thesource address and the result is used as a virtual address of a location in main memory.The number of offsets specified defines the length of the chain of virtual addresses to beaccessed in this way before accessing the desired range of source locations. For example, asingle offset with value 0 uses the virtual address found in the source for the location to becopied.

2. FORMAT

COPY:ADDR a [,OFF b] [,L c ,NL c] {;ADDR d ;UVAR e ;REG f} [;WORD]!


a = The starting virtual address for the source data in decimal, octal, orhexadecimal notation.

b = A single offset or list of up to five offsets. Omission of the keyword impliesno indirect addressing. Offsets are in bytes unless the WORD option isspecified.

L c = The length of the copy in bytes unless the WORD option is specified. Themaximum is 128 bytes or 32 words. The default is 1 word or byte.

NL c = The operation will use the locations beginning c lower than the calculatedaddress and ending at the address. The locations are used in ascendingorder.

d = The virtual address of the destination for the data in decimal, octal, orhexadecimal notation.

e = A GRASP utility variable (1-50), in decimal, to be written as the destinationcopy. Utility variable values are reset to zero at the end of a debuggingsession.

f = The name of the register to be written as the destination copy. Valid registernames are as follows:AP, ATBBGR, ATBPSW, ATBQ, ATBSAR, ATBSCR, ATBSDR, BGR,CAR, CDR, ERC, FP, HG, HSR, HSRBGC, IM, ISC, ISS, PA,PPR, PSW, R10, R11, R8, R9, RNULL, RTC, SBR0, SBR1, SBR2,SBR3, SBR4, SBR5, SBR6, SBR7, SCRATCH0, SCRATCH1, SDR,SM, SP, SSRC, SSRS, SYSBASE, T0, T1, T2, T3, T4, T5, T6,T7, TIMERS, TOPIS, UINT0, UINT1, UINT2, UINT3, UINTER.

WORD = All addresses, offsets, and lengths are interpreted in terms of words(including addresses derived in address chains). If this option is omitted,values given are in bytes.


Issue 28 COPY:ADDR-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOPY ADDR August 2005

4. SYSTEM RESPONSE

?I = Identification Field contains an error. General syntax error or one of thefollowing errors:

— INCONSISTENT KEYWORDS (NL-OFF)Negative length not allowed without OFF.

— INVALID KEYWORDADDR is invalid in an immediate action.

— RANGE ERROR (L or NL)Length specified is too long.

— INPUT ERROR (OFF COUNT)Too many offsets listed.

— RANGE ERROR (UVAR)Invalid utility variable number was specified.


NG = No Good.

— BAD REG NAMEA named register is not a valid destination.

PF = Printout Follows. Followed by a COPY-ADDR output message.


5. REFERENCES

IM/OM References:

Input MessagesCOPY:PIDCOPY:UIDDUMP:ADDRLOAD:ADDRWHEN:PIDWHEN:UID

Output MessagesCOPY-ADDRCOPY-PIDCOPY-REGCOPY-UIDCOPY-UVAR

Other References:



COPY:ADDR-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COPY AMATAPE

ID............. COPY:AMATAPERELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE

Writes primary or secondary Automatic Message Accounting (AMA) data onto tape.

NOTE: Either MT0 or MT1 has to be specified.

Format 1: Copies primary data.

Format 2: Copies secondary data.

NOTE: This command is supported for Flexent Mobility Manager - AMA (FMM-AMA)only. For Executive Cellular Processor - AMA (ECP-AMA), please refer to theinput message COPY:AMATAPE-ECP.

2. FORMAT

[1] COPY:AMATAPE;PRIM [;DENS a];b!

[2] COPY:AMATAPE;SEC, SBLK c, EBLK d [;DENS a];b!


a = AMA tape density:

DDS2 — Length 120m, native capacity 4.0 Gbytes.DDS2C — Length 120m, compressed capacity 8.0 Gbytes.DDS3 — Length 125m, native capacity 12.0 Gbytes.DDS3C — Length 125m, compressed capacity 24.0 Gbytes.DDS4 — Length 150m, native capacity 20.0 Gbytes.DDS4C — Length 150m, compressed capacity 40.0 Gbytes.

b = Session type:

MT0 — Used if AMA data goes to the Magnetic Tape 0 (MT0).MT1 — Used if AMA data goes to the Magnetic Tape 1 (MT1).

c = Sequence number of the first block of secondary data required.

d = Sequence number of the last block of secondary data required.

4. SYSTEM RESPONSE

NG 0 = No Good. Tape session in progress.

NG 5 = No Good. Unable to send message to Tape process.

NG 10 = No Good. Tape sessions are inhibited.

NG 18 = No Good. Session type invalid.

NG 19 = No Good. New session not allowed.


Issue 28 COPY:AMATAPE-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOPY AMATAPE August 2005

NG 20 = No Good. New primary session not allowed.

OK = Good. Request has been accepted.

5. REFERENCES

IM/OM References:

Input MessagesABT:AMATAPECOPY:AMATAPE-ECPSTOP:AMATAPE

Output MessagesREPT-AMA-SESSION-EREPT-AMATAPE-ERREPT-AMATAPE-SESS-C



COPY:AMATAPE-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COPY AMATAPE ECP

ID............. COPY:AMATAPE-ECPRELEASE ....... 14.0 and laterTYPE .......... Input

1. PURPOSE

Writes primary or secondary Automatic Message Accounting (AMA) data onto tape.


Format 1: Copies primary data.

Format 2: Copies secondary data.

NOTE: This command is supported for Executive Cellular Processor - AMA (ECP-AMA)only. For Flexent Mobility Manager - AMA (FMM-AMA), please refer toCOPY:AMATAPE.

2. FORMAT

[1] COPY:AMATAPE;PRIM, MT a [;DENS d];e!

[2] COPY:AMATAPE;SEC, MT a, SBLK b, EBLK c [;DENS d];e!


a = Tape drive number.

b = Sequence number of the first block of secondary data required.

c = Sequence number of the last block of secondary data required.

d = AMA tape density. The control file holds the default option (see SET:AMA-CONTROL-ECP).

DAT — 600,000 AMA Blocks to (60/90m) DAT.HIGH — 6250 BPI operation.MED — 1600 BPI operation.

e = Data stream:


4. SYSTEM RESPONSE

NG CODE 1 = No Good. Tape sessions are manually inhibited, or other necessaryconditions for command execution were not met.

PF = Printout Follows. Tape writing is allowed and session will be started.REPT-AMATAPE-SESS-C-ECP or REPT-AMATAPE-ER-ECP will beoutput when tape writing is complete. REPT-AMA-SESS-ECP will beoutput when session is started.


Issue 28 COPY:AMATAPE-ECP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOPY AMATAPE ECP August 2005

NOTE: The number of AMA records written depends upon the densityspecified (high density writes more records).

RL CODE 0 = Retry Later. Tape session already in progress.

RL CODE 2 = Retry Later. Internal audit invoked.

5. REFERENCES

IM/OM References:

Input MessagesABT:AMATAPE-ECPCOPY:AMATAPESTOP:AMATAPE-ECP

Output MessagesREPT-AMATAPE-ER-ECPREPT-AMATAPE-SESS-C-ECP



COPY:AMATAPE-ECP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COPY BKDISK

ID............. COPY:BKDISKRELEASE ....... 23.0 and laterTYPE .......... Input

1. PURPOSE

Copies selected on-line disk partitions to tape in the Load Disk From Tape (LDFT) format.The partitions must be specified in a specification file. The default for the specification filename is /etc/pdtspec. The full pathname must be given for each partition, and onlyone partition can appear on each line.

If the system is booted on the primary root file system, for those partitions having backuppartitions, the backup partitions are written to tape. If the system is booted on the backuproot file system, the primary disk partitions are written to tape. Partitions without backuppartitions are written from the primary partitions in both cases. Collectively the partitionsmake up one logical volume.

Format 1: Copies the partitions to magnetic tape in single volume format.

Format 2: Acknowledges the mounting of a new tape by the user. Format 2 is only usedin conjunction with Format 1.

Format 3: Copies partitions to a Digital Audio Tape (DAT) in multi-volume format.

On a 3B21D Computer with a Digital Audio Tape (DAT) drive, Format 3 isused to format the DAT with multiple logical volumes, provided the tapealready contains the TOP file at the beginning of tape. (The TOP file isconsidered to be Session 1 Volume 0 and is written by the COPY:TAPE:TOPcommand.) One or more of these logical volumes form a backup session. ADAT may be formatted with no more than nine (1-9) backup sessions insequential order. A backup session may contain any combination of logicalvolumes meeting the following criterion: the logical volumes within a sessionmust be ordered such that any given volume identified by its logical volumenumber has a greater number than the previous volume in the session.

See section 3 for the mapping of logical volume numbers to the volume namesthey represent.

By default, Format 3 will try to append logical volumes to the current end ofdata mark. There are optional parameters for session and volume position torequest that a logical volume be appended to the end of a specific logicalvolume on the DAT for the purpose of overwriting the DAT from that pointforward. This option is only valid for overwriting logical volumes within themost recent backup session or for appending a logical volume for the nextsession to the last logical volume of the specified positioning session.

NOTE: When specifying a DAT as the tape device, COPY:BKDISK will always use aDAT device which writes low density (uncompressed) data to satisfy arequirement of LDFT processing. In the event that the specified DAT devicewrites high density (compressed) data, COPY:BKDISK will override the selectionand use the equivalent low density DAT device. For example, if the high density


Issue 28 COPY:BKDISK-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOPY BKDISK August 2005

rewind DAT device (/dev/mt00) is specified, COPY:BKDISK will override theselection and use the low density rewind DAT device (/dev/mt08).

2. FORMAT

[1] COPY:BKDISK;START:SRC "a",TD "b",TPSIZE c[,FN "d"][,MRG] [,EXT] [,SKP] [,NODMTMSG] [,COM]!

[2] COPY:BKDISK;ACK:TPSIZE c!

[3] COPY:BKDISK;MULTI:SRC"a",TD "b",SESS e,VOL f[,PSESS g, PVOL h] [,FN "d"][,MRG] [,EXT] [,SKP][,NODMTMSG] [,COM]!


a = Pathname that specifies the boot disk. See the User Guidelines in this manualfor a description of special device file names.

b = Special device file name of the tape drive to be used. See NOTE in thePURPOSE section for additional information. Also, see the User Guidelinesin this manual for definitions and examples of tape device names.

c = Specifies the size of the tape mounted. The tape size is in meters for DigitalAudio Tapes (DATs). The acceptable range for a DAT tape size is 30 to 150.The format requires entry of the tape size separated from the keyword by aspace.

d = Specification file name that contains a set of partitions to be written to tape.The full pathname of the file is required.

e = Backup session number which is used to group one or more logical volumestogether. The first backup session on tape must be numbered backupsession 1 and increased sequentially thereafter with a maximum value of 9.

f = Logical volume number which identifies the group of partitions beingwritten to tape. The logical volume numbers have a range from 1 to 9 withthe following association to logical volume names:

1 — AMTEXT2 — AMODD3 — SMTEXT4 — SMODD15 — SMODD26 — SMODD37 — SMODD48 — SMODD59 — SMODD6


COPY:BKDISK-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COPY BKDISK

g = Positioning backup session number which identifies a backup session ontape. The range of positioning backup session numbers is 1 to 9. Thisnumber is used along with the positioning logical volume number to locate aspecific logical volume on tape to which to append the new logical volume.The absence of the positioning fields will result in the logical volume beingappended to the current end of data mark on tape.

h = Positioning logical volume number. The range of positioning logical volumenumbers is 0 to 9. Note that 0 is included in this range to allow forappending to the TOP file. Refer to the explanation of field g for moreinformation.

MRG = Writes generic and database partitions as one generic sequence. With thisoption, the specification file should contain both database and genericpartitions. As the default, if the specification file contains generic anddatabase partitions, then two sequences will be created. Note that the defaultaction is not supported for a multi-volume LDFT tape. The user must specifythis option when the specification file contains both database and genericpartitions and input command Format 3 is being used.

EXT = LDFT extended format tapes where the data blocks can be up to 6K bytes.This option cannot be used on a Kennedy tape drive controlled by a UN134PC.

SKP = Skip block usage bitmap and unused data blocks when writing file systemsto tape. Use of this option is generally recommended, because it willconserve tape, if possible. This will usually save time also. Note, however,that tape reading and writing time may double when this option is used withstreaming tape drives (drives without mechanical tensioners or vacuumcolumns) in a worst-case data scattering scenario.

NODMTMSG = Upon completion, the DISMOUNT TAPE AND LABEL message will not beprinted.

COM = This option must be used when creating an RTR disk image that contains acommon VTOC (a VTOC containing both the 3B21D lboot partitions) orwhen creating other generic text tapes that will be shared among 3B21Dprocessors.

4. SYSTEM RESPONSE


NG = No Good. A fatal error was encountered because the actual disk writer orthe user acknowledgement program (invoked by COPY:BKDISK;ACK)could not be initiated. Try the command again. If the process fails again,seek technical assistance.

PF = Printout Follows. Followed by a COPY-BKDISK output message.


Issue 28 COPY:BKDISK-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOPY BKDISK August 2005

5. REFERENCES

IM/OM References:

Input MessagesSTOP:BKDISKCOPY:TAPE-TOPDUMP:BKTAPE

Output MessagesCOPY-BKDISK

Other References:

254-341-114 Field Operations Tools Software System Description 3B20D Computer


COPY:BKDISK-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COPY BKTAPE

ID............. COPY:BKTAPERELEASE ....... 20.0 and laterTYPE .......... Input

1. PURPOSE

Copies the contents of a multi-volume formatted Digital Audio Tape (DAT) from a sourceDAT drive to a destination DAT drive. The default action is to make a complete copy ofthe source DAT. If the optional session number is specified, then the multi-volumeformatted data is copied from the beginning of the specified session on the source DATand appended to the end of the previous session on the destination DAT.

NOTE: COPY:BKTAPE will always use a destination DAT device which writes lowdensity (uncompressed) data to satisfy a requirement of Load Disk From Tape(LDFT) processing. In the event that the specified destination DAT device writeshigh density (compressed) data, COPY:BKTAPE will override the selection anduse the equivalent low density DAT device. For example, if the high densityrewind DAT device (/dev/mt10) is specified, COPY:BKTAPE will override theselection and use the low density rewind DAT device (/dev/mt18). It is un-necessary to override the source DAT device since data is always returneduncompressed, regardless of format, on read operations.

2. FORMAT

COPY:BKTAPE:SRC "a", DEST "b" [,SESS c]!


a = Device filename of the source DAT drive. See NOTE in the PURPOSEsection for additional information. Also, see the User Guidelines in thismanual for definitions and examples of tape device names.

b = Device filename of the destination DAT drive. See NOTE in the PURPOSEsection for additional information. Also, see the User Guidelines in thismanual for definitions and examples of tape device names.

c = Session number on the source DAT. This session is the starting point for thecopy from the source DAT (1-9).

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by a COPY-BKTAPE output message.

5. REFERENCES

IM/OM References:

Input MessagesCOPY-BKDISKDUMP-BKTAPE


Issue 28 COPY:BKTAPE-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOPY BKTAPE August 2005

Output MessagesCOPY-BKTAPE



COPY:BKTAPE-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COPY CELL

ID............. COPY:CELLRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Copies the data link information stored in the Non-Volatile Memory (NVM) of the activeCell Site Controller (CSC)) to the NVM of the offline CSC.

2. FORMAT

COPY:CELL a,CPYNVM!



4. SYSTEM RESPONSE

IP = In Progress. Request accepted - output message COPY-CELL-NVMCOPYwill follow.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesCOPY-CELL-NVMCOPYREPT-CELL-NVM



Issue 28 COPY:CELL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOPY CELL August 2005



COPY:CELL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COPY DB

ID............. COPY:DBRELEASE ....... 25.0 and laterTYPE .......... Input


**WARNING**

1 Only use this command when absolutely necessary because allRecent Changes to the database since the last backup are lost.

2 To ensure proper execution, COPY:DB command will automaticallydo the following:

a Verify there is no Mobile Switching Center DatabaseManagement System (MSCDBMS) audits in progress or queued.

b Block all periodic and on–demand Executive Cellular Processor(ECP) audits from executing. All ECP audit counters will remainconstant while COPY:DB is in progress. Refer to theOP:ECP–AUD input message for more details on audit counters.

c Inhibit all Mobile Switching Center Database ManagementSystem (MSCDBMS) audits unless the are already foundinhibited. If MSCDBMS audits are found inhibited, COPY:DBwill ensure they remain inhibited while executing.

3 Once the COPY:DB is completed, all ECP audits will no longer beblocked from executing, and all MSCDBMS audits will be restoredto the original state from the time when COPY:DB was requested.

NOTE: If MSCDBMS audits are allowed at the time COPY:DB isrequested, they will be restored to the allowed state.

If MSCDBMS audits are inhibited at the time COPY:DB isrequested, they will be left in the inhibited state.

4 After COPY:DB completes, a download to the Ring CDNs (CDN3s)for the databases modified by COPY:DB will take place.

**READ PURPOSE CAREFULLY**

1. PURPOSE

Overwrites the master copy of a database with the backup copy. Sends a message to theMobility Manager Application Processor (MM-AP) to synchronize databases with theExecutive Cellular Processor (ECP) Linked List Indexed (LLI) databases.


Issue 28 COPY:DB-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOPY DB August 2005

This message requests the master copy be overwritten with the backup copy of thedatabase. All other instances of the database including the ECP, ring CDNs, CDN4s,HVLR MM-APs are also updated to maintain consistency.

The LAESDB, LAESTKDB, LLCDB, PRTLTDB, RGDB, VDN2PDB, VLRCSTDB, VLRDB,VLRUZDB, VS2PDB, and WINTRIGDB databases do not have full backup copies. Althoughthe COPY:DB command may be executed on these databases, all records in the masterdatabase will be removed.

When any member of a database dependency group is copied, all members of thedependency group will have their master copies overwritten to maintain consistency. Thedatabase dependency groups are:

1. MUFDB, CCFDB, SUBAUXDB, AUDB, SUBUZDB, UZDB, CNIDDB, DN2PDB, P2LDNDB,S2PDB, WINCRDDB, WINSRVDB, WINTDADB, SUBMBRDB, SUBPLTDB.

2. ATDB, RTDB, REDB, PDTDB.

3. IUNDB, APCDNDB, RDTKDB, CEQDB, TRUNKDB, FCIDB, CGSADB, FCAUXDB, MCADB,PCTNDB, RESELDB, DCSDB, IWFDB, RSAUXDB, DLCDB, APDB, APGTTDB, APOFIDDB,APPC2LSDB, APSS7LKDB, APSS7SSDB, RCSLINKDB, APFRMDB, BSDB, CICDB,SS7LSDB, LACLDB, FCSDB, CDMEQPDB, CELLDB, FINDB, IOSFACEDB,MODCELLDB, NID2SECDB, RNCTRKDB, ZID2SECDB.



6. ECPDB, FSCODEDB.

7. VLRDB, VDN2PDB, VLRUZDB, VS2PDB, WINTRIGDB.


9. TELSGRPDB, TELSCRNDB.

10. CHRATEDB, TARIFFDB, DAYPGDB, EXCDAYDB, CIEXPDB, TREATDB.

11. LAESDB, LAESTKDB.

12. TONEDB, TAMAPDB.

The database dependency groups specific to the Inter-Operability Specification (IOS) BaseStation Controller (BSC) configuration are:

1. APCDNDB, APDB, APFRMDB, APGTTDB, APOFIDDB, APPC2LSDB, APSS7LKDB,BSDB, CDMEQPDB, CELLDB, CEQDB, CGSADB, DCSDB, DLCDB, FCAUXDB, FCIDB,IUNDB, IWFDB, LACLDB, MCADB, MODCELLDB, PCTNDB, RCSLINKDB, RDTKDB,RESELDB, RNCTRKDB, RSAUXDB, SS7LSDB, TRUNKDB, APSS7SSDB, CICDB,FCSDB, FINDB.




5. ECPDB, FSCODEDB.


COPY:DB-2 Issue 28


6. BSLKDB, IOSCELLDB, IOSHODB, LUBSCDB, OVBSDB SHICCDB, SHODB.

NOTE: Offices using ISDN User Part (ISUP) signaling must verify that the correct ISUPdata is still present in DLCDB and TGLDB after the COPY:DB command is run.

If ISUP trunk information changed because of the COPY:DB, it might be necessary tochange the LINK and/or the Trunk Group List (TGL) form to reflect the new ISUP trunkinformation. The following ISUP rules should be applied:

RULE: Offices using ISUP signaling on the 5ESS Digital Cellular Switch (DCS) must havean instance of the LINK form for each 5ESS DCS connected to the ECP via SignalingSystem 7 (SS7) links. The Send Calling Party Number field on the TGL form only appliesto ISUP trunks on the 5ESS DCS.

2. FORMAT

COPY:DB a[; UCL]!


a = Database name:ALL — All database members. This option is only valid for Inter-

Operability Specification (IOS) Base Station Controller (BSC)configuration.

ADAPTPGDB — Adaptive Paging.AMACCDB — Automated Message Accounting Configuration and Control.AMAMDDB — Automated Message Accounting Meta Data.APCDNDB — AP Call Processing/Database Node (CDN).APDB — Application Processor Equipage.APFRMDB — Application processor frame equipage.APGTTDB — Application processor global title translation.APOFIDDB — Application processor office identification.APOPDSTDB — Application processor output message destination.APOPMSGDB — Application processor output message formats.APPC2LSDB — Application processor point code to link set routing.APSS7LKDB — Application processor SS7 link information.APSS7SSDB — Application processor subsystem number translation.ARGDB — Authorized roaming group.ATDB — Ambiguous tables.AUDB — Authentication center.BSDB — Base station configuration.BSLKDB — Base station A3/A7 link.CALDB — Dynamic routing calendar.CCFDB — Custom calling features.CCNID — Custom control network identification.CCODB — Customer controlled options.CDHFLDB — Code Division Multiple Access (CDMA) directed handoff

frequency list.CDHNLDB — CDMA directed handoff neighbor list.CDMEQPDB — CDMA Digital Module (CDM) equipage.CELLDB — Cell site information.CEQDB — Cell equipage.


Issue 28 COPY:DB-3


CGSADB — Cellular geographic service area.CHRATEDB — Charge rate.CICDB — Circuit identification code.CIEXPDB — Charge index expansion.CIRNLDB — CDMA Inter-Band Load Management (IBLM) redirection

neighbor list.CNIDDB — CDMA network ID.DAYPGDB — Day program definition.DCSDB — Digital cellular switch.DLCDB — Data link configuration.DN2EDB — Directory number to extended System ID.DN2PDB — Directory number to primary Mobile Station Identification

(MSID).DNMODDB — Dialed number modification.DPLANDB — Dialing plan.DXDRTEDB — Digit by digit routing.ECPDB — Executive cellular processor.EXCDAYDB — Exception day definition.FCAUXDB — Face code auxiliary.FCIDB — Face code information.FCSDB — Flexible channel allocation channel set.FINDB — Flexible channel allocation interfering neighbors.FLTRDB — Filter.FRMDB — Fraudulent serial numbers.FSCODEDB — Feature/service code.I3DDB — International direct distance dial.ICDB — Carrier information.IMRDB — Input message routing.IOSCELLDB — Inter-Operability Specification (IOS) cell.IOSFACEDB — IS634 cell site sector equipped information.IOSHODB — IOS cell handoff information.IUNDB — Inter-process message switch user node.IVCDB — Inter-vendor cell.IVTDB — Inter-vendor trunk.IWFDB — Inter-working function.LACLDB — Local area cluster information.LAESDB — Lawfully authorized electronic surveillance.LAESTKDB — Lawfully authorized electronic surveillance trunk.LLCDB — Link layer connection.LUBSCDB — IOS cell list under abutting BSC.MCADB — Multiple component assignment.MMCMDNDB — Mobile directory number on multiple message center.MMCSRDB — Special routing on multiple message center.MODCELLDB — CDMA Modular Cell equipage.MRDB — Message routing.MSIDMPCDB — Mobile Identification Number (MIN) - based point code

routing for Mobile Positioning Center (MPC).MUFDB — Subscriber.NETDB — Cellular networking.NETMSCDB — Network Mobile Switching Center (MSC).


COPY:DB-4 Issue 28


NID2SECDB — IS634 cell site sector equipped information for provisionedNetwork IDs.

NNBRDB — Network neighbor.OAMPRXYDB — Operations, Administration, and Maintenance (OA&M)

proxy.OPCLASSDB — Output message class.OPTYPEDB — Output message type.ORBDB — Object Request Broker.OVBSDB — Other Vender Base Station.P2LDNDB — Primary Mobile Station Identification (MSID) to local

Directory Number (DN).PCTNDB — Point code to trunk member.PDTDB — Primary digit tables.PNDB — Ported numbers list.PRTLTDB — Period location trace.RCSLINKDB — Radio Cluster Server (RCS)/ Microcell signaling link.RDTKDB — Radio-to-trunk translator.REDB — Resolution entries.RESELDB — Reselection control channel list.RGDB — Roamer greeting.RLSDB — Route list selector.RLSTODDB — Route list selector time of day.RNCTRKDB — Radio Network Controller (RNC) Trunk Database (DB) used

for Packet Core.ROMDB — Roamer service list.RSAUXDB — Auxiliary reselection control channel list.RTDB — Resolution tables.S2PDB — Secondary MSID to primary MSID.SACDB — Service access code.SHICCDB — IOS soft handoff Common Intelligent Carrier Card (CICC)

configuration.SHODB — IOS soft handoff application configuration.SS7LSDB — SS7 link set.TAMAPDB — External Tone/Announcement Mapping.STARTDB — Start tables.STDLDB — Standard list.SUBAUXDB — Subscriber auxiliary.SUBMBRDB — Subscriber flexible alerting member.SUBPLTDB — Subscriber flexible alerting pilot.SUBUZDB — Subscriber user zones.TARIFFDB — Tariff ID.TELSCRNDB — Teleservice screening treatment.TELSGRPDB — Teleservice screening group.TGLDB — Trunk group list.TISECURDB — Technician Interface Security Database.TONEDB — Tones and announcements.TREATDB — Call treatment.TRUNKDB — Trunk group and member.UZDB — User zones.VDN2PDB — Visitor Directory Number to Primary Mobile Station

Identification (MSID).


Issue 28 COPY:DB-5


VLRCSTDB — Visitor Location Register (VLR) call status trace.VLRDB — Visitor Location Register (VLR).VLRUZDB — VLR user zones.VS2PDB — Visitor secondary MSID to primary MSID.WINCRDDB — Wireless Intelligent Network (WIN) Critical Restriction

Digits Database.WINSCFDB — WIN Service Control Function Database.WINSRVDB — WIN Service Database.WINTDADB — WIN Trigger Destination Address Database.WINTRIGDB — WIN Trigger database.ZID2SECDB — IS634 cell site sector equipped information for provisioned

Zone Area IDs.

4. SYSTEM RESPONSE

IP = In Progress. Database copy has begun.

5. REFERENCES

IM/OM References:

Input MessagesOP:ECP-AUD

Output MessagesREPT-AP-COPY-DBREPT-COPY-DBREPT-DATABASE-NAME



COPY:DB-6 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COPY DIFF SRC MHD

ID............. COPY:DIFF-SRC-MHDRELEASE ....... 13.0 and laterTYPE .......... Input


**WARNING**Incorrect use of this input message can degrade system performance andresult in disk data mutilation. This command should not be used withoutexpert technical assistance.

1. PURPOSE

Compares disk partitions in order to detect differences. When a difference is found, data iscopied from the source partition to the destination partition. The input arguments canspecify disks or specific partitions. A disk partition may reside on the disk of its duplexmate, or on an arbitrary disk. Also, both partitions may reside on the same disk.

A difference generates a message which identifies the location of the difference. A copywill then be performed to correct the difference. The source argument is considered tocontain the correct disk data. The mismatch messages provide an audit trail of correcteddisk blocks.

Only one COPY:DIFF or CMPR:MHD command is allowed to run at one time. If more thanone is attempted, the DFC driver will deny the request and output an error code to thateffect.

2. FORMAT

COPY:DIFF;SRC,MHD a[,PTN {b c-d}];DEST,{MATE MHD e},[PTN {f g-h}][:BLOCKS i]!


a = Source member number.

b and f = Partition number within a range of (0 to 63), or list of partitions (r1, r2, r3,..., rn) where the list may include 64 entries.

Default will be all but the FREE, UNASGN, DIAG, SWAP, and PDUMPpartitions.

c-d = A range of partition numbers where a list of up to 32 ranges (p0-p1, p2-p3,p4-p5, ..., pm-pn) may be specified. A range has the format c-d where dmust be greater than c.

e = Destination member number.

g-h = A range of partition numbers where a list of up to 32 ranges (p0-p1,4p2-p3, p4-p5, ..., pm-pn) may be specified. A range has the format g-hwhere h must be greater than g.

i = An integer value indicating the size of the Input/Output (I/O) buffers as amultiple of disk blocks. The legal values are 1-256. If BLOCKS is notspecified, the default number of 128 will be used.


Issue 28 COPY:DIFF-SRC-MHD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOPY DIFF SRC MHD August 2005

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by a COPY-DIFF-SRC output message.

5. REFERENCES

IM/OM References:

Input MessagesCMPR:MHDSTOP:COPY-DIFF


Other References:



COPY:DIFF-SRC-MHD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COPY OOSDISK

ID............. COPY:OOSDISKRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Copies a specific file from an out-of-service disk to an active system disk. This message istypically used for retrieving a file from a software backup maintained on a spare disk.

2. FORMAT

COPY:OOSDISK;MHD a, SRC "b", DEST "c"[,PTN d]!


a = Specifies a non-active disk containing the source file (0-255).

b = Full pathname that specifies the file to be copied. See the User Guidelines inthis manual for definition of pathname and file.

c = Pathname of the destination file.

d = Specifies partition number, where the source file resides in the out-of-servicedisk. If not specified, the partition corresponding to the file on the active diskwill be used.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by the COPY-OOSDISK output message.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesCOPY-OOSDISK



Issue 28 COPY:OOSDISK-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOPY OOSDISK August 2005



COPY:OOSDISK-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COPY PID

ID............. COPY:PIDRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Copies data from virtual addresses in main memory to the computer Generic AccessPackage (GRASP) utility variables.


2. FORMAT

COPY:PID a, ADDR b [,OFF c] [,L d ,NL d] ;UVAR e [;WORD] !


a = Process ID of the target process.

b = The starting virtual address for the source data in decimal, octal, orhexadecimal notation.

c = A single offset or list of up to five offsets. Omission of the keyword impliesno indirect addressing. Offsets are in bytes unless the WORD option isspecified.

L d = The length of the file to be copied in bytes unless the WORD option isspecified. The maximum is 128 bytes or 32 words. The default is 1 byte or 1word.

NL d = Indicates that the operation should use the locations beginning d lower thanthe calculated address and ending at the address. The locations are used inascending order. Usage and limitations are the same as for the L option.

e = A GRASP utility variable (1-50), in decimal, to be written as the address ofthe destination of the copy. Utility variable values are reset to zero at the endof a debugging session.

WORD = All addresses, offsets, and lengths are to be interpreted in words, includingaddresses derived in address chains. If this option is omitted, values givenare assumed to be in bytes.

4. SYSTEM RESPONSE


— EXTRA KEYWORD (PID)PID is invalid in a breakpoint.



Issue 28 COPY:PID-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOPY PID August 2005


— INVALID KEYWORDDestination of ADDR or REG not valid outside of a WHEN action list.


— RANGE ERROR (PID)Process ID is out of range.


NG = No Good.

— BAD PIDThe PID specified is for a process for which copies are not allowed.

PF = Printout Follows. Followed by a COPY-PID output message.


5. REFERENCES

IM/OM References:

Input MessagesCOPY:ADDRCOPY:REGCOPY:UIDCOPY:UVARDUMP:PIDLOAD:ADDRLOAD:PMEMLOAD:REGLOAD:UVAROP:ST-PROCESSOP:UMEM


Other References:



COPY:PID-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COPY PTN ALL

ID............. COPY:PTN-ALLRELEASE ....... 13.0 and laterTYPE .......... Input


**WARNING**All existing data in the destination partitions will be destroyed.

1. PURPOSE

Copies one set of disk partitions into a corresponding set of partitions.

A duplex disk configuration is a prerequisite for the command to work properly. Toensure data consistency, one of the Moving Head Disks (MHDs) of the duplex pair will beremoved from service and the data from its copy of the source partition will be copied tothe destination partition on the disk which is left active. After the copy is complete, theMHD which was removed from service will be restored.

2. FORMAT

COPY:PTN:ALL, SRC "a", DEST "b" [,ACT]!


a = Full pathname of a file that specifies a list of partitions, or a special devicefilename of a partition to be copied. Refer to the 235-600-31x 7R/E 5ESSSwitch ECD/SG Data Base Manual - Where ’x’ is the release-specific version ofthe specified document.

b = Full pathname of a file that contains the corresponding list of destinationpartitions, or the special device filename for a destination partition.

ACT = Leaves the system in a duplex disk configuration as it copies the partitions.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by a COPY-PTN-ALL output message.

5. REFERENCES

IM/OM References:

Input MessagesCLR:FILESYS-FILE

Output MessagesCOPY-PTN-ALL


Issue 28 COPY:PTN-ALL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOPY PTN ALL August 2005

Other References:

235-600-31x 7R/E 5ESS Switch ECD/SG Data Base Manual - Where ’x’ is the release-specificversion of the specified document.




COPY:PTN-ALL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COPY REG

ID............. COPY:REGRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Copies data from computer registers to virtual addresses in main memory and in registersas an action associated with a breakpoint. Copies data from registers to computer GenericAccess Package (GRASP) utility variables as either an immediate action or as an actionassociated with a breakpoint.


Format 1: Executed as an action associated with a breakpoint.

Format 2: Executed as either an immediate action or as an action associated with abreakpoint.

2. FORMAT

[1] COPY:REG a [,OFF b] [,L c] {;ADDR d ;REG f ;UVAR=e} [;WORD]!

[2] COPY:REG a [,L c];UVAR e [;WORD]!


a = Specifies a register to be read as the source for the copy. Valid register namesare as follows:

AP — Argument Pointer (AP).ATBBGR — Register used by the Address Translation Buffer (ATB)

miss routine to temporarily store the Bi-directionalGating Register (BGR).

ATBPSW — Register used by the ATB miss routine to temporarilystore the Program Status Word (PSW) register.

ATBQ — Register used by the ATB miss routine to temporarilystore the q register.

ATBSAR — Register used by the ATB miss routine to temporarilystore the Store Address Register (SAR) contents.

ATBSCR — Register used by the ATB miss routine to temporarilystore the Store Control Register (SCR) contents.

ATBSDR — Register used by the ATB miss routine to temporarilystore the Store Data Register (SDR) contents.

BGR — Bi-directional gating register.CAR — Channel address register.CDR — Channel data register.ERC — Error Register (ER) clear.FP — Frame Pointer (FP).


Issue 28 COPY:REG-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOPY REG August 2005

HG — Reserved register HG.HSRBGC — Bi-directional gating control bits of the Hardware Status

Register (HSR).HSR — Hardware status register.IM — Interrupt Mask (IM) register.ISC — Interrupt Source (IS) register clear.ISS — Interrupt Source (IS) register set.PA — Program address register.PPR — Pulse point register.PSW — Program status word.R0 — General register R0.R10 — Frame Pointer (FP).R11 — Stack Pointer (SP).R1 — General register R1.R2 — General register R2.R3 — General register R3.R4 — General register R4.R5 — General register R5.R6 — General register R6.R7 — General register R7.R8 — General register R8.R9 — Argument Pointer (AP).RNULL — Null register.RTC — Real time clock.SBR0 — Segment Base Register 0 (SBR0).SBR1 — Segment Base Register 1 (SBR1).SBR2 — Segment Base Register 2 (SBR2).SBR3 — Segment Base Register 3 (SBR3).SBR4 — Segment Base Register 4 (SBR4).SBR5 — Segment Base Register 5 (SBR5).SBR6 — Segment Base Register 6 (SBR6).SBR7 — Segment Base Register 7 (SBR7).SCRATCH0 — JE group temp subgroup scratch register SCRATCH0.SCRATCH1 — JE group temp subgroup scratch register SCRATCH1.SDR — Store data register.SP — Stack pointer SP.SSRC — System Status Register (SSR) clear.SSRS — System Status Register (SSR) set.SYSBASE — Beginning address of UNIX RTR Operating System tab.T0 — JE group temp subgroup scratch register T0.T1 — JE group temp subgroup scratch register T1.T2 — JE group temp subgroup scratch register T2.T3 — JE group temp subgroup scratch register T3.T4 — JE group temp subgroup scratch register T4.T5 — JE group temp subgroup scratch register T5.T6 — JE group temp subgroup scratch register T6.T7 — JE group temp subgroup scratch register T7.TIMERS — Timing circuit.TOPIS — Interrupt stack pointer.UINT0 — Error microinterrupt hander register UINT0.UINT1 — Error microinterrupt hander register UINT1.


COPY:REG-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COPY REG

UINT2 — Error microinterrupt hander register UINT2.UINT3 — Error microinterrupt hander register UINT3.UINTER — Shadow error register (uint_er) loaded during an error

microinterrupt.

b = A single offset or list of up to five offsets. Omission of the keyword impliesno indirect addressing. Offsets are in bytes unless the WORD option isspecified. (Used as an action associated with a breakpoint.)

L c = The length of the copy assumed to be in bytes unless the WORD option isspecified. The maximum is 128 bytes or 32 words. The default for anomitted or zero length is 1.

d = Specifies the destination virtual address for the data in decimal, octal, orhexadecimal notation. (Used as an action associated with a breakpoint.)

e = Specifies a GRASP utility variable (1-50), in decimal, to be written as thedestination copy. Utility variable values are reset to 0 at the end of adebugging session. (Can be used as an immediate action or associated with abreakpoint.)

f = Specifies the register to be written as the destination copy. (Used as an actionassociated with a breakpoint.) Valid register names are as follows:AP, ATBBGR, ATBPSW, ATBQ, ATBSAR, ATBSCR, ATBSDR, BGR,CAR, CDR, ERC, FP, HG, HSR, HSRBGC, IM, ISC, ISS, PA,PPR, PSW, R0, R1, R10, R11, R2, R3, R4, R5, R6, R7, R8,R9, RNULL, RTC, SBR0, SBR1, SBR2, SBR3, SBR4, SBR5, SBR6,SBR7, SCRATCH0, SCRATCH1, SDR, SP, SSRC, SSRS, SYSBASE,T0, T1, T2, T3, T4, T5, T6, T7, TIMERS, TOPIS, UINT0,UINT1, UINT2, UINT3, UINTER.

WORD = All addresses and lengths are in terms of words. If this option is omitted,values given are assumed to be in bytes.

4. SYSTEM RESPONSE


— EXTRA KEYWORD (OFF) Indirection not allowed except as action of aWHEN.

— INCONSISTENT KEYWORDS (NL-OFF) Negative length not allowedwithout OFF.

—INVALID KEYWORD Destination of ADDR or REG not valid outside of aWHEN action list.

— RANGE ERROR (L or NL) Length specified is too long.— RANGE ERROR (UVAR) Invalid utility variable number was specified.


NG = No Good.

— BAD REG NAMEA named register is not a valid source or destination.


Issue 28 COPY:REG-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOPY REG August 2005

PF = Printout Follows. Followed by a COPY-REG output message.


5. REFERENCES

IM/OM References:

Input MessagesCOPY:ADDRCOPY:PIDCOPY:UIDCOPY:UVARDUMP:REGLOAD:ADDRLOAD:REGLOAD:UVAROP:UMEMWHEN:PIDWHEN:UID


Other References:



COPY:REG-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COPY SPDISK

ID............. COPY:SPDISKRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Copies a specific partition, or a list of partitions, from one of the system disks to an activespare disk. This command is typically used for generating a backup copy of the softwareon a system disk. The system disk pair must be duplexed to use this input message.

2. FORMAT

COPY:SPDISK;SRC "a", DEST "b"!


a = Full pathname of a file that contains a list of partitions, or a special device filename of a partition, to be copied. See the User Guidelines in this manual fordefinitions of full pathname and special device file name.

b = Filename for the corresponding list of destination partitions, or the specialdevice filename for a destination partition.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by a COPY-SPDISK output message.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesCOPY-SPDISK



Issue 28 COPY:SPDISK-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOPY SPDISK August 2005



COPY:SPDISK-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COPY TAPE EMERDMP

ID............. COPY:TAPE-EMERDMPRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Copies data from the emergency dump partition on a disk to a magnetic tape.

NOTE: If the resulting tape is to be read on a UNIX system, it must be read using thedd command.

2. FORMAT

COPY:TAPE:EMERDMP, TD "a"!


a = Tape special device file name. See the User Guidelines in this manual fordefinition and examples of tape device names.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by a COPY-TAPE-EMERDMP output message.

5. REFERENCES

IM/OM References:

Input MessagesCLR:EMERDMPOP:EMERSTATOP:ST-FILESYS

Output MessagesCOPY-TAPE-EMERDMPREPT-EMERGENCY

Other References:





Issue 28 COPY:TAPE-EMERDMP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOPY TAPE EMERDMP August 2005



COPY:TAPE-EMERDMP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COPY TAPE IN

ID............. COPY:TAPE-INRELEASE ....... 8.0 and laterTYPE .......... Input


**WARNING**If a full pathname is specified on the COPY:TAPE;OUT command line,directory information is retained and the file will be placed in the samedirectory it was copied from, overwriting any existing version.

1. PURPOSE

Copies files from a magnetic tape containing full or relative pathnames and headerinformation, and places them in their respective directories. This command can also printa table of contents of the tape.

NOTE: If the tape to be read was written on a UNIX system, it must have been writtenusing the cpio message with the -c option.

2. FORMAT

COPY:TAPE:IN, TD "a"[,TOC] [,BSDIR "b"]!


a = Tape special device file name. See the User Guidelines in this manual fordefinitions and examples of tape device names.

TOC = Table of contents. Prints a list of the files on the tape with their statusinformation. No files are created.

b = Pathname of the base directory into which the files on the tape will be copied.See the User Guidelines in this manual for definitions of pathname anddirectory.

NOTE: If the relative path is specified on the COPY:TAPE;OUT command line, thedefault base directory is /cft/shl/cmds. Use the BSDIR option to specifyan alternate base directory.

Remember, the BSDIR option does not apply if the full pathname wasspecified on the COPY:TAPE;OUT command line. Use the TOC option ofCOPY:TAPE;IN to determine how a file or list of files were copied to tape,that is whether copied by relative pathnames or by full pathnames.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by a COPY-TAPE-IN output message.


Issue 28 COPY:TAPE-IN-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOPY TAPE IN August 2005

5. REFERENCES

IM/OM References:

Input MessagesCOPY:TAPE-OUT

Output MessagesCOPY-TAPE-INCOPY-TAPE-OUT

Other References:




COPY:TAPE-IN-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COPY TAPE OUT

ID............. COPY:TAPE-OUTRELEASE ....... 8.0 and laterTYPE .......... Input


**WARNING**Use extreme caution when invoking this command with full pathnames.Reading a tape that contains full pathnames may destroy existing data.

1. PURPOSE

Copies one or more files to a magnetic tape, along with full or relative pathnames andheader (status) information.

Format 1: Used to copy one or more files with full pathnames. See the User Guidelines inthis manual for a definition of full pathnames.

Format 2: Used to copy one or more files with relative pathnames. See the UserGuidelines in this manual for a definition of relative pathnames.

NOTE: If the resulting tape is to be read on a UNIX system, it must be read using thecpio command with the -c options.

2. FORMAT

[1] COPY:TAPE:OUT, TD "a" {,FN "b" ,FLIST "c"}!

[2] COPY:TAPE:OUT, TD "a" {,FN "d" ,FLIST "e"} ,BSDIR "f"!


a = Tape special device file name. See the User Guidelines in this manual fordefinitions and examples of tape device names.

b = Full pathname of the single file to be written to the tape. See the UserGuidelines in this manual for a definition of full pathname.

c = Pathname of a file that contains a list of full pathnames of the files to bewritten to the tape. Used if two or more files are to be written.

d = Relative pathname of the single file to be written to the tape. Specify the basedirectory via the BSDIR option. See the User Guidelines in this manual for adefinition of relative pathname.

e = Pathname of a file that contains a list of relative pathnames of the files to bewritten to the tape. Used if two or more files are to be written. Specify thebase directory via the BSDIR option.


Issue 28 COPY:TAPE-OUT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOPY TAPE OUT August 2005

f = Pathname of the base directory where the file to be copied to tape is located.Relative pathnames are relative to this directory. See the User Guidelines inthis manual for definitions of pathname and directory.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by a COPY-TAPE-OUT output message.

5. REFERENCES

IM/OM References:

Input MessagesCOPY:TAPE-IN

Output MessagesCOPY-TAPE-INCOPY-TAPE-OUT

Other References:




COPY:TAPE-OUT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COPY TAPE TEST

ID............. COPY:TAPE-TESTRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Writes the diagnostic test tape header block onto a magnetic tape. A demand diagnosticphase for the tape unit verifies the tape has this header block (in low density) before usingthe tape for testing.

2. FORMAT

COPY:TAPE:TEST,TD "a"!


a = Tape special device file name. See User Guidelines for definition andexamples of tape device names. Select low density and rewind. Thediagnostic phase will not accept the tape if the header block is written in highdensity.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by the COPY-TAPE-TEST output message.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesCOPY-TAPE-TEST

Other References:




Issue 28 COPY:TAPE-TEST-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOPY TAPE TEST August 2005



COPY:TAPE-TEST-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COPY TAPE TOP

ID............. COPY:TAPE-TOPRELEASE ....... 23.0 and laterTYPE .......... Input

1. PURPOSE

Copies a Task Oriented Practice (TOP) file(s) from disk to tape. A TOP file containswritable microcode and the Load Disk From Tape (LDFT) program used for a "deadstart."If the COM option is specified, the Very Large Main Memory (VLMM) TOP file and 3B21DTOP file are copied from disk to tape, strictly in that order. Otherwise, ahardware-platform-specific TOP file is copied. For example, if the current hardwareplatform is VLMM, /etc/topfile64 or /etc/topfile is copied to tape.

NOTE: When specifying a Digital Audio Tape (DAT) as the tape device,COPY:TAPE:TOP will always use a DAT device which writes low density(uncompressed) data to satisfy a requirement of LDFT processing. In the eventthat the specified DAT device writes high density (compressed) data,COPY:TAPE:TOP will override the selection and use the equivalent low densityDAT device. For example, if the high density rewind DAT device (/dev/mt00) isspecified, COPY:TAPE:TOP will override the selection and use the low densityrewind DAT device (/dev/mt08).

2. FORMAT

COPY:TAPE:TOP,TD "a",[COM]!


a = Tape special device file name. See NOTE in the PURPOSE section foradditional information. Also, see the User Guidelines, in Section 2 of thismanual, for definition and examples of tape device names.

COM = Option used to create a common TOP tape which consists of both the VLMMTOP file and the 3B21D TOP file.

NOTE: The input message with the COM option does not copy the Standard MainMemory (SMM) or Expanded Main Memory (EMM) TOP file. If this optionis not specified, the TOP file copied to tape will be the one for the currenthardware platform. See the example in the PURPOSE section.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by the COPY-TAPE-TOP output message.

5. REFERENCES

IM/OM References:

Input MessagesNone.


Issue 28 COPY:TAPE-TOP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOPY TAPE TOP August 2005

Output MessagesCOPY-TAPE-TOP



COPY:TAPE-TOP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COPY UID

ID............. COPY:UIDRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Copies data from virtual addresses in main memory to computer Generic Access Package(GRASP) utility variables as an immediate action.


2. FORMAT

COPY:UID a, ADDR b [,OFF c] [,L d ,NL d] ;UVAR e [;WORD] !


a = The utility ID of the process from which the source data will be copied.

b = The starting virtual address for the data in decimal, octal, or hexadecimalnotation.

c = A single offset or list of up to five offsets. Omission of the keyword impliesno indirect addressing. Offsets are in bytes unless the WORD option isspecified.

L d = The length of the copy in bytes unless the WORD option is specified. Themaximum is 128 bytes or 32 words. The default is 1 byte or 1 word.

NL d = The operation will use the locations beginning d lower than the calculatedaddress and ending at the address. The locations are used in ascendingorder.

e = A GRASP utility variable (1-50), in decimal, to be written as the destinationcopy. Utility variable values are reset to zero at the end of a debuggingsession.

WORD = All addresses, offsets, and lengths are to be interpreted in words, includingaddresses derived in address chains. If this option is omitted, values givenare assumed to be in bytes.

4. SYSTEM RESPONSE


— EXTRA KEYWORD (UID)UID is not valid in a WHEN action list.

— EXTRA KEYWORD (UID)UID is invalid in a breakpoint.



Issue 28 COPY:UID-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOPY UID August 2005




— RANGE ERROR (UID)Utility ID is out of range.



BAD UIDThe UID specified is for a process for which copies are notallowed.

PF = Printout Follows. Followed by the COPY-UID output message.


5. REFERENCES

IM/OM References:

Input MessagesCOPY:ADDRCOPY:PIDCOPY:REGCOPY:UVARDUMP:UIDLOAD:UVAROP:UMEM


Other References:



COPY:UID-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COPY UVAR

ID............. COPY:UVARRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Copies data from a computer Generic Access Package (GRASP) in utility variable to virtualaddresses in main memory and in registers as an action associated with a breakpoint.Copies data from another GRASP utility variable as an immediate action or as an actiontriggered by a breakpoint.


Format 1: Required by action to be triggered by a breakpoint.

Format 2: Either executed immediately or triggered by a breakpoint.

2. FORMAT

[1] COPY:UVAR a [,OFF b] [,L c ,NL c] {;ADDR d ;REG f} [;WORD]!

[2] COPY:UVAR a [,L c ,NL c] ;UVAR e [;WORD]!


a = A GRASP utility variable (1-50), in decimal, as the source for the copy.Utility variable values are reset to zero at the end of a debugging session.

b = A single offset or list of up to five offsets. Omission of the keyword impliesno indirect addressing. Offsets are in bytes unless the WORD option isspecified. (Used as an action associated with a breakpoint.)

L c = The length of the copy in bytes unless the WORD option is specified. Themaximum is 128 bytes or 32 words. The default is 1.

NL c = The operation should use the locations beginning c lower than the calculatedaddress and ending at the address. The locations are used in ascendingorder.

d = The destination virtual address for the data in decimal, octal, or hexadecimalnotation. (Used as an action associated with a breakpoint.)

e = A GRASP utility variable (1-50), in decimal, to be written as the destinationcopy. Utility variable values are reset to zero at the end of a debuggingsession. (Can be used as an immediate action or associated with abreakpoint.)


Issue 28 COPY:UVAR-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOPY UVAR August 2005

f = The register to be written as the destination of the copy. (Used as an actionassociated with a breakpoint.) Valid register names are as follows:

AP — Argument Pointer (AP)ATBBGR — Register used by the ATB miss routine to temporarily store

the Bi-directional Gating Register (BGR).ATBPSW — Register used by the ATB miss routine to temporarily store

the Program Status Word (PSW) register.ATBQ — Register used by the ATB miss routine to temporarily store

the q register.ATBSAR — Register used by the ATB miss routine to temporarily store

the Store Address Register (SAR) contents.ATBSCR — Register used by the ATB miss routine to temporarily store

the Store Control Register (SCR) contents.ATBSDR — Register used by the ATB miss routine to temporarily store

the Store Data Register (SDR) contents.BGR — Bi-directional gating register.CAR — Channel address register.CDR — Channel data register.ERC — Error Register (ER) clear.FP — Frame Pointer (FP).HG — Reserved register HG.HSRBGC — Bi-directional gating control bits of the Hardware Status

Register (HSR).HSR — Hardware status register.IM — Interrupt Mask (IM) register.ISC — Interrupt Source (IS) register clear.ISS — IS register set.PA — Program address register.PPR — Pulse point register.PSW — Program status word.R0 — General register R0.R10 — Frame pointer.R11 — Stack Pointer (SP).R1 — General register R1.R2 — General register R2.R3 — General register R3.R4 — General register R4.R5 — General register R5.R6 — General register R6.R7 — General register R7.R8 — General register R8.R9 — Argument pointer.RNULL — Null register.RTC — Real time clock.SBR0 — Segment base register SBR0.SBR1 — Segment base register SBR1.SBR2 — Segment base register SBR2.SBR3 — Segment base register SBR3.SBR4 — Segment base register SBR4.SBR5 — Segment base register SBR5.


COPY:UVAR-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 COPY UVAR

SBR6 — Segment base register SBR6.SBR7 — Segment base register SBR7.SCRATCH0 — JE group temp subgroup scratch register SCRATCH0.SCRATCH1 — JE group temp subgroup scratch register SCRATCH1.SDR — Store data register.SP — Stack pointer.SSRC — System Status Register (SSR) clear.SSRS — SSR set.SYSBASE — Beginning address of UNIX RTR Operating System tab.T0 — JE group temp subgroup scratch register T0.T1 — JE group temp subgroup scratch register T1.T2 — JE group temp subgroup scratch register T2.T3 — JE group temp subgroup scratch register T3.T4 — JE group temp subgroup scratch register T4.T5 — JE group temp subgroup scratch register T5.T6 — JE group temp subgroup scratch register T6.T7 — JE group temp subgroup scratch register T7.TIMERS — Timing circuit.TOPIS — Interrupt stack pointer.UINT0 — Error microinterrupt hander register UINT0.UINT1 — Error microinterrupt hander register UINT1.UINT2 — Error microinterrupt hander register UINT2.UINT3 — Error microinterrupt hander register UINT3.UINTER — Shadow error register (uint_er) loaded during an error

microinterrupt.

WORD = Indicates that all addresses, offsets, and lengths are to be interpreted in termsof words, including addresses derived in address chains. If this option isomitted, values given are assumed to be in bytes.

4. SYSTEM RESPONSE


— EXTRA KEYWORD (OFF)Indirection not allowed except as action of a WHEN.







— BAD REG NAME 1A named register is not a valid destination.


Issue 28 COPY:UVAR-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksCOPY UVAR August 2005

PF = Printout Follows. Followed by a COPY-UVAR output message.

RL = Retry Later. The system is in an overload condition, or wait for previousOP:UMEM or OP:UMEM;MCH to complete. Printout Follows.

5. REFERENCES

IM/OM References:

Input MessagesCOPY:ADDRCOPY:PIDCOPY:REGCOPY:UIDDUMP:UVARLOAD:ADDRLOAD:REGLOAD:UVAROP:UMEMWHEN:PIDWHEN:UID


Other References:



COPY:UVAR-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DEL CELL GENERIC

ID............. DEL:CELL-GENERICRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Deletes requested generic from an Non-Volatile Memory (NVM) at the specified Flexent

or Flexent Modular Cell 4.0.

2. FORMAT

DEL:CELL a[, b], GENERIC c[ CLASS d]!


a = Flexent or Flexent Modular Cell 4.0 site number (1-600).

• A single cell site.• A range (maximum number of cells in a range is 32).• A list of cell sites separated by commas and enclosed in parentheses.

b = Flexent identifier:


CDMA Distributed Base Station (CDBS) Cells.

CDM x where x = 1 - 16. CDMA Digital Module (CDM) is applicable toFlexent Modular Cells and Flexent Modular Cell 4.0.


x can be:

• A single number.• A range of numbers.• A list of numbers separated by commas and enclosed in parentheses.

c = Name of the Generic Description File (GDF). A string of 12 characters withindouble quotes.

For Flexent Modular Cell 4.0, the generic name should follow the namingconvention when a range of CDM is entered or all CDMs are implied(variable b is not entered): For example: F2000DDAA.60


B — Cell boot software (releases prior to 17.0 only).D — Cell diagnostic software. (Microcell all releases; Flexent

Modular prior to 17.0 only.)F — Functional software (Cell and Radio Cluster Server [RCS]).



Issue 28 DEL:CELL-GENERIC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDEL CELL GENERIC August 2005





B — TDMAD — CDMA


A — Flexent Microcell.B — Flexent Modular Cell 4.0.D — Flexent Modular and CDBS Cells.U — Flexent Modular 1.0-3.0 with Universal Radio Controller

(URC) controller board.




9th character — Radio Cluster Server (RCS) to cell compatibility indicator.Usually A.



NOTE: If a single CDM is specified, the generic requested will bedownloaded regardless of the cell type.

For Flexent Modular Cell 3.0 / Flexent Modular Cell 4.0 Mixed Frame,configuration only, when a list or range of CDMs is specified, or no CDMsare specified, then:

• If the specified generic is a Flexent Modular Cell generic, the Flexent

Modular Cell generic will be deleted from the CDMs in the Flexent

Modular Cell assemblage(s) and the Flexent Modular Cell 4.0 equivalentgeneric will be deleted from the CDMs in the Flexent Modular Cell 4.0assemblage(s).

• If the specified generic is a Flexent Modular Cell 4.0 generic, theFlexent Modular Cell 4.0 generic will be deleted from the CDMs in theFlexent Modular Cell 4.0 assemblage(s) and the Flexent Modular Cellequivalent generic will be deleted from the CDMs in the Flexent

Modular Cell assemblage(s).

d = Overriding output message class (151-213). This option may be used onlyif the Virtual System Output Message Routing feature is supported.


DEL:CELL-GENERIC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DEL CELL GENERIC

4. SYSTEM RESPONSE




PF = Printout Follows. Request has been executed. Followed by a OP-CELL-GENERIC output message.



5. REFERENCES

IM/OM References:

Input MessagesOP:CELL-GENERICSEND:CELL-GENERICSTOP:SEND-CELL-GENERIC

Output MessagesDEL-CELL-GENERICOP-CELL-GENERIC

Other References:



Issue 28 DEL:CELL-GENERIC-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksDEL CELL GENERIC August 2005



DEL:CELL-GENERIC-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DEL LOG

ID............. DEL:LOGRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Deletes the selected contents of a logfile and cleans corrupt entries from the file. If thefilename is the only criterion entered, only corrupt entries are deleted. Otherwise, onlyentries in the logfile that meet all of the specified criteria are deleted.

2. FORMAT

DEL:LOG;LG "a"[:[DATE b[-c],][TIME d[-e],][KW "f",][ID g,][TYPE h]];


a = Name of the logfile. Any valid logfile name; for example, ULARP.

b = Start date as six-digit format (mmddyy) or ten-digit format (mmddyyhhmm).For example, 100257 = October 2, 1957; 0102571000 = January 2, 1957, at10:00 a.m.

c = End date as six-digit format (mmddyy) or ten-digit format (mmddyyhhmm).The default is the start date. If supplied, this date must be in the same format(six or ten digits) as the start date.

d = Start time in hours and minutes format (hhmm). For example, 0110 = 1:10a.m.

e = End time in hours and minutes format (hhmm). For example, 1530 = 3:30p.m.The default is the start time.

NOTE: When the six-digit date range is used in conjunction with a time range, thelog entries will be deleted from start time to end time for each day in therange of start date through end date.The ten-digit date allows the user to delete log entries from the start time onstart date until end time on end date. Specifying the start time (variable d)and end time (variable e) with the ten-digit date range is invalid.

f = A keyword that appears in all entries that are to be deleted.

g = An optional decimal number (0-9999) which is used to link an item in alogfile with an entry in another file. The ID is filled in by the process thatmade the logfile entry.

h = An optional decimal number (0-9999) that specifies the type of entry on alogfile. This TYPE is filled in by the process that made the logfile entry.


Issue 28 DEL:LOG-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDEL LOG August 2005

4. SYSTEM RESPONSE

IP = In Progress.

NG = No Good.

— CANNOT ATTACH TO ECD. Could not attach to the EquipmentConfiguration Database (ECD).

5. REFERENCES

IM/OM References:

Input MessagesOP:LOG

Output MessagesDEL-LOGOP-LOG

Other References:




DEL:LOG-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DEL PAUTH

ID............. DEL:PAUTHRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Deletes a person Identity (IDENT) from the Personal Authority (PAUTH) database.

2. FORMAT

DEL:PAUTH:IDENT "a"!



4. SYSTEM RESPONSE

NG = No Good.

— NON_EXISTENT PERSON IDENTITYThe given person identity does not exist in the personal authorityadministration.

— UNABLE TO ACCESS AUTHORITY ADMINISTRATIONPersonal authority information is inaccessible.

OK = Good. Personal authority deleted.

RL = Retry Later.


5. REFERENCES

IM/OM References:

Input MessagesADD:PAUTHCHG:PAUTHVFY:PAUTH




Issue 28 DEL:PAUTH-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDEL PAUTH August 2005



DEL:PAUTH-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DEL PCGRP

ID............. DEL:PCGRPRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Format 1: Disassociates the Command Group (COMGR) from a personal Identity(IDENT), thus preventing a user from accessing this group of commands. TheIDENT for the Person Command Group (PCGRP) must already exist in thePersonal Authority (PAUTH) database.

Format 2: Disassociates a profile from a personal identity. It prevents a user fromaccessing this group of commands.

2. FORMAT

[1] DEL:PCGRP:DATA,IDENT "a",COMGR b;

[2] DEL:PCGRP:IDENT "a",PROFL "c";


a = Identity of the person or group in one to eight letters and/or digits.

b = Command group.

c = A profile name which has been previously created and assigned to this user.The name is one to eight letters and/or digits.

4. SYSTEM RESPONSE

NG = No Good.

— COMMAND GROUP NOT ASSIGNED TO THIS PERSONThe given command group was never assigned to this person identity.


— NON-EXISTENT PROFILE IDENTITYProfile does not exist in the database.

— PASSWORD ENHANCEMENT NOT ACTIVATEDThe PROFL option with this command is valid only for applicationsrunning with the password enhancement feature.

— PROFILE NOT ASSIGNEDProfile not assigned to the identity.

— UNABLE TO ACCESS AUTHORITY ADMINISTRATIONPersonal authority information is inaccessible.

OK = Good. Command group deleted from database.

RL = Retry Later.



Issue 28 DEL:PCGRP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDEL PCGRP August 2005

5. REFERENCES

IM/OM References:

Input MessagesADD:PAUTHADD:PCGRPCHG:PAUTHDEL:PAUTHVFY:PAUTHVFY:PCGRP

Output MessagesVFY-PAUTHVFY-PCGRP



DEL:PCGRP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DEL PROFL

ID............. DEL:PROFLRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Deletes an existing profile from the list of user profiles. A profile is a set of commandgroups. The profile is also deleted from any user to which it is assigned.

2. FORMAT

DEL:PROFL:IDENT "a"!


a = Identifying name of the profile to be deleted from the database. A maximumof eight characters may be used.

4. SYSTEM RESPONSE


PASSWORD ENHANCEMENT NOT ACTIVATED — This command is validonly for applications running with the password enhancementfeature enabled.

PROFILE IDENTITY DOES NOT EXIST

UNABLE TO ACCESS PROFILE ADMINISTRATION

OK = Good. Profile successfully deleted from the database.


AUTHORITY ADMINISTRATION UNDER UPDATE

PROFILE ADMINISTRATION UNDER UPDATE

5. REFERENCES

IM/OM References:

Input MessagesADD:PCGRPADD:PROFLCHG:PROFLDEL:PCGRPVFY:PCGRPVFY:PROFL

Output MessagesVFY-PROFL



Issue 28 DEL:PROFL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDEL PROFL August 2005



DEL:PROFL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DEL TAUTH

ID............. DEL:TAUTHRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Deletes a terminal identity from the Terminal Authority (TAUTH) database.

2. FORMAT

DEL:TAUTH:TERM "a"!



4. SYSTEM RESPONSE


— INVALID TERMINAL IDENTITYThe given terminal identity is either not four characters in length ordoes not start with tty.

— NON-EXISTENT TERMINAL IDENTITYThe given terminal identity does not exist in the terminal authorityadministration.


OK = Good. Terminal identity deleted from the database.



5. REFERENCES

IM/OM References:

Input MessagesADD:TAUTHVFY:TAUTH




Issue 28 DEL:TAUTH-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDEL TAUTH August 2005



DEL:TAUTH-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DEL TCGRP

ID............. DEL:TCGRPRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Disassociates the Command Group (COMGR) from a Terminal (TERM) identity, thuspreventing a user from accessing this group of commands from that terminal. The TERMmust already exist in the Terminal Authority (TAUTH) database.

2. FORMAT

[1] DEL:TCGRP:TERM "a",COMGR b;

[2] DEL:TCGRP:TERM "a",PROFL "c";



b = Command group.

c = A profile name which has been previously created and assigned to thisterminal. The name is one to eight letters and/or digits.

4. SYSTEM RESPONSE

NG = No Good.

— COMMAND GROUP NOT ASSIGNED TO THIS TERMINALThe given command group has not been assigned to this terminalidentity.

— INVALID TERMINAL IDENTITYThe given terminal identity is either not four characters in length ordoes not start with tty.

— NON-EXISTENT PROFILE IDENTITYProfile does not exist in the database.

— NON-EXISTENT TERMINAL IDENTITYThe given terminal identity does not exist in the terminal authorityadministration.


OK = Good. Command group deleted from the database.

RL = Retry Later.



Issue 28 DEL:TCGRP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDEL TCGRP August 2005

5. REFERENCES

IM/OM References:

Input MessagesADD:TAUTHADD:TCGRPDEL:TAUTHVFY:TAUTHVFY:TCGRP

Output MessagesVFY-TAUTHVFY-TCGRP



DEL:TCGRP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DEL:VLR:DCS

ID............. DEL:VLR-DCSRELEASE ....... 17.0 and laterTYPE .......... Input

1. PURPOSE

This input command will allow technician to erase all Visitor Location Registers (VLRs) ata serving Mobile Switching Center (MSC) for roamers subscribed to a particular homeMobile Switching Center Identification (MSCID). All the parameters of the commandmust be entered.

2. FORMAT

DEL:VLR:DCS a, ECP b, SI c!


a = Home Digital Cellular Switch (DCS) ID (0-16 in decimal).

b = Home Executive Cellular Processor (ECP) ID (0-15 in decimal).

c = Home System Identifier (1-32767 in decimal).

4. SYSTEM RESPONSE

?E = Error. Error in input command format.

IP = In Progress. The request has been received and has been initiated.Printout will follow.

NG = No Good. Input command format is correct but some necessary conditionfor message execution was not met.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesDEL-VLR-DCS

Other References:

401-612-493 Visitor Location Register (VLR) Erasure for a Mobile Switching Center Identification(MSCID)


Issue 28 DEL:VLR-DCS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDEL:VLR:DCS August 2005



DEL:VLR-DCS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN CELL

ID............. DGN:CELLRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Diagnoses the specified cell site unit.

NOTE: For the PH, TLP and CHANL options, the comma is used to separate the multipleoptions. The comma is not needed if only one option is chosen. The option c isalways required if option b is not specified.

2. FORMAT

DGN:CELL a, [ b ] [ ,c ] [ ; [ RPT d ] [ ,RAW ] [ ,UCL ] ][ : [ PH e ] [ ,TLP ] [ ,CHANL f ] ] [ , BOTH ] [ CLASS g ]!


Except for voice radios, the unit is left in the out-of-service state on completion of thediagnostic. Voice radios are returned to the state they were in before the diagnosticrequest. If Automatic Radio Reconfiguration (ARR) is in effect and a diagnostic isrequested on a voice radio that is being used by ARR to replace a faulty unit, thediagnostic will be rejected. A message will be printed, stating that the voice radio has beenreconfigured and therefore is unavailable for diagnostics.


• A single cell site.• A range (maximum number of cells in a range is 32).• A list of cell sites separated by commas and enclosed in parentheses.

NOTE: a must be a single cell site number if c is any of the following:

AMPBBA xCAT xCBRCBR xCCU xCRCDL xLC xLC x ORIGORIGPCBR xRA xSU xTRC


Issue 28 DGN:CELL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN CELL August 2005

b = Series II or Flexent identifier:



CDM x where x = 1 - 16. CDMA Digital Module (CDM) is applicable toFlexent Modular Cells and Flexent Modular Cell 4.0.

CCC x where x = 1 - 42. CDMA Cluster Controller (CCC) is applicableCDMA Series II cells.


c = Cell site unit (required for Flexent Modular Cells and Flexent CDBS Cells).

NOTE: The following units cannot be diagnosed in Series II: ReferenceGenerator (RG), Reference Calibration Generator (RCG), LinearAmplifier Circuit (LAC), Lightguide Microcell/Modular CellTransceiver (LMT), Optical Transceiver Unit (OTU) and MultipleLinear Amplifier Circuit (MLAC).

Cell unit is not required if option b is specified.

If the cell unit is not specified for Microcells, then diagnostics arerun on all Microcell units.

AMP — TDMA or CDMA amplifier. Applicable to TMDA Microcell,CDMA Microcell, Flexent Modular Cell, Flexent CDBS Cell, andFlexent Modular Cell 4.0.

BBA x — CDMA BIU-BCR-ACU (BBA) set for Series II cells.

x = 1-42

CAT x — Clock and tone

x = 10-11 for 13.1 CDMA Personal Communication Service (PCS)minicell, with growth frame 5 frame technology.

x = 8-9 for 13.1 CDMA PCS minicell, with growth frame 4 frametechnology.

x = 6-7 for 12.1 CDMA PCS minicell.

x = 4-5 for CDMA.

x = 2-3 for CDMA or non-CDMA.

x = 0-1 for non-CDMA.

CBR — CDMA Baseband Radio (CBR) for CDMA Flexent Microcell.


DGN:CELL-2 Issue 28


CBR x — CDMA Baseband Radio (CBR)

x = 1-3 for Flexent Modular Cells and Flexent Modular Cell 4.0assemblages.

x = 1-6 for Flexent Modular Cell 4.0 assemblages.

CCU x — CDMA Channel Unit (CCU)

x = 1-2 for CDMA Flexent Microcells.

x = 1-7 for CDMA Series II cells.

x = 1-6 for Flexent Modular Cells, Flexent Modular Cell 4.0assemblages, and Flexent CDBS Cells.

x = 1-12 for Flexent Modular Cell 4.0 assemblages.

CRC — CDMA Radio Controller (CRC).

CRTU — CDMA Radio Test Unit (CRTU).

CSC x — Cell Site Controller (CSC).

x = 0-1

CSC x, AL — CSC alarm interface

x = 0-1

CSC x, CPI — CSC communications processor interface.

x = 0-1

CSC x, CPU — CSC central processor unit.

x = 0-1

CSC x, MEM — CSC memory.

x = 0-1

CSC x, NCI y — CSC network control interface.

x = 0-1

y = 0-2

DL x — Data links.

x = 0-1

EDRU — Enhanced Digital Radio Unit.

LC x — Locate Channel (LC) radio.

x = 0-39

LC x ORIG — Original LC radio, that is, radio that was being used in LCradio prior to reconfiguration by ARR.

x = 0-39

LEDRU — Locate Enhanced Digital Radio Unit.


Issue 28 DGN:CELL-3


PCBR x — Pre-distortion CDMA baseband radio.

x = 1-3 for CDBS cells.

PCBR x, MMA — amplifier.

x = 1-3 for CDBS cells.

RA x — Radio.

x = 0-191 for Series II cells. NOTE: If the RA is a Flexible ChannelAllocation (FLCA) RA, then the cell needs to have its FeatureActivation File with Qualification (QFAF) for FLCADynamic Assignment (DA) set or the Diagnose (DGN)request will be rejected.

x = 1-5 for Flexent Microcells, Flexent Modular Cells, Flexent

CDBS Cells, and Flexent Modular Cell 4.0.

RA x ORIG — Original voice radio, that is, radio that was being used as avoice radio prior to reconfiguration by ARR.

x = 0-191

RTU — Radio test unit (AMPS).

SU x — Setup (SU) radio

x = 0-7without Directional Setup.

x = 0-35 with Directional Setup.

SU x ORIG — Original Setup (SU) radio, that is, radio that was being usedas SU radio prior to reconfiguration by ARR.

x = 0-7without Directional Setup.

x = 0-35 with Directional Setup.

TFU — CDMA Time Frequency Unit (TFU) is applicable for CDMAFlexent Microcells and Flexent CDBS Cells.

TFU x — CDMA Time Frequency Unit (TFU).

x = 1-8 for Flexent Modular Cells and Flexent Modular Cell 4.0.

TRC — Radio controller.

TRTU — Radio test unit (TDMA).

d = Number of times the diagnostic is to be repeated. Default is one time.Maximum is 32,767. If the unit is Data Link (DL), the maximum is 256.

RAW = Prints expected and observed values during the diagnostic of every phase,and only the first failure of any failing phase.


DGN:CELL-4 Issue 28


UCL = Unconditionally execute the diagnostic and print all failures. Normal modestops on first failure.

In Flexent Cells, when running diagnostics without specifying the unit bydefault the request is run with the UCL option. So regardless or not the UCLoption is specified, the request is taken as UCL. The request will run tocompletion regardless of the number of problems encounter by the request.

PH = Execute only the specified phase number(s).

This option is for SII Digital Signal Level 1 (DS1) only. When specified,diagnosis will be carried out on both DS1 units of the Digital FacilityInterface (DFI) board.

e = Phase number in decimal. May be a single number or a range. Phasenumbers per unit are as follows:

AMP — Amplifier. Phase number: 1.BBA — CDMA BIU-BCR-ACU (BBA) set. Phase number: 1.CAT — Clock and tone. NOTE: Phase 2 is a CDMA-only diagnostic.

Phase number: 1-2.CBR — CDMA baseband radio. Phase number: 1.CCC — CDMA cluster controller. Phase number: 1.CCC, CCU — CDMA channel unit. Phase number: 1.CCU — CDMA channel unit (Flexent Microcell). Phase number: 1.CCU — CDMA channel unit (Flexent and Flexent Modular Cell

4.0). Phase number: 1.CRC — CDMA radio controller. Phase number: 1.CRTU — CDMA Radio test unit (CDMA). Phase number: 1.CSC — Cell site controller. Phase number: 1-17.CSC, AL — Cell site controller, alarm interface. Phase number: 1.CSC, CPI — Cell site controller, communications process interface. Phase

number: 1.CSC, MEM — Cell site controller, memory. Phase number: 1.CSC, NCI — Cell site controller, network control interface. Phase

number: 1.DL — Data links. Phase number: 2.LAC — Linear amplifier circuit. Cannot be diagnosed.LC — Locate radio. Phase number: 1.RA — Radio CDMA-only diagnostic (non-Flexent ). Phase

number: 2.RA — Radio (Flexent Microcell). Phase number: 1-4.RA — Radio (Flexent and Flexent Modular Cell 4.0). Phase

number: 1-4.RCG — Reference calibration generator. Cannot be diagnosed.RG — Reference generator Cannot be diagnosed.RTU — Radio test unit (AMPS). Phase number: 1.SU — Setup radio. Phase number: 1.


Issue 28 DGN:CELL-5


TFU — CDMA Time Frequency Unit (TFU). Phase number: 1.TRC — TDMA radio controller. Phase number: 1.TRTU — Radio test unit (TDMA). Phase number: 1.

TLP = Print the trouble locating procedure for all failures.

f = Channel number:

1-799 or 990-1023 — Used to diagnose LC, SU, or Radio Frequency (RF)test unit.

2-1998 — Used for TDMA PCS mini-cells and Flexent TDMA PCS only.

NOTES: For TDMA PCS mini-cells only, the upper limit of the range hasbeen extended to 1999.If CHANL is not specified, the diagnostic supervisor will pick anyavailable channel. If the specified channel is not available at thecell site, the request will be denied.

TDMA Flexible Channel Allocation (FLCA), introduced in R14.0,affects the following changes associated with the DGN commandFor R14.0, TDMA FLCA feature applies to non-Flexent Cells.

1. The CHANL option can apply to a FLCA RA but only if theFeature Activation File (FAF) for FLCA DA is set. Otherwise,the command will be rejected as before when using theCHANL option on RAs. The channel cannot be a channel for afixed channel radio in the same sector.

2. If CHANL option is not used for a FLCA RA, but an AreaWide Test Channel (AWTC) is defined in Translations, thenthe cell will use AWTC.

3. If CHANL option is not used for a FLCA, and an AWTC is notdefined in Translations, then the cell will search for anavailable FLCA channel. If no FLCA channel is available,then a message will display indicating no FLCA channelwas available as part of the normal output for the DGNcommand.

g = Overriding output message class (151-213). This option may be used onlyif the Virtual System Output Message Routing feature is supported.

4. SYSTEM RESPONSE





DGN:CELL-6 Issue 28





5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesDGN-CELLRMV-CELL-DLRMV-CELL-RANGERMV-CELL-SG-ANTRMV-CELL-RARST-CELL

Other References:



Issue 28 DGN:CELL-7




DGN:CELL-8 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN CELL DL

ID............. DGN:CELL-DLRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Diagnoses the specified Cell Site (CS) data link. The loopback option tests the associateddata transmission facility.

2. FORMAT

DGN:CELL a, DL b; c [;ERR] [,RPT d] [,UCL][,CLASS e]!



b = Data Link (DL) number (0-1).

c = One of the following:

CELLLB — Place the CELL end of the data line in the loopback mode.Remove the loopback mode by RST:CELL DL.

DSCLB — Place the Dedicated Switch Connection (DSC) associated withCELL a, DL b in the loopback mode. This action will causethe DSC to be looped back toward the Link Node (LN) andtoward the CELL. Remove the loopback connection by usingRST:CELL or RMV:CELL.

ECHO — Put the specified link node data link controller in the echomode. All data received from the data facility are echoedback. Use this mode when external test equipment requires aloopback mode. Remove the echo mode by restoring the datalink.

LOCALLB — Perform near-end data facility loopback test. The testautomatically places the near-end data facility in the near-endloopback mode. Only applicable with an RS-449 interface.

LOOPBACK — Perform data facility loopback test from the linknode. Thistest requires a manually placed loopback in the data facility.

ERR = Dump the protocol error registers at the conclusion of the loopback test.

Valid only if c = LOOPBACK or LOCALLB (with RS-449) for Series II.

d = Number of times the diagnostic is to be repeated. (1-256).

UCL = Unconditionally execute the cell resident diagnostic with no earlytermination and prints all failures. Normal mode stops on first failure.

NOTE: The UCL mode can flood the Teletypewriter (TTY) with outputmessages.

e = Overriding output message class (151-213). This option may be used onlyif the Virtual System Output Message Routing feature is supported.


Issue 28 DGN:CELL-DL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN CELL DL August 2005

4. SYSTEM RESPONSE


NG = No Good. Necessary conditions for message execution (including apossibly unequipped inter-ECP data link) were not met.




5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesDGN-CELL-DLSTOP-DGN-CELL

Other References:



DGN:CELL-DL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN CELL SG

ID............. DGN:CELL-SGRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Run diagnostics on all trunks associated with a specified cell, server group and antennaface.

2. FORMAT

DGN:CELL a, SG b, ANT c[,ALL]!



b = Server group number (0-1).

c = Antenna face number:(0-6 for Series II cells).

ALL = Request all measurement data, regardless of diagnostic passage or failure.Without this option selected, measurement data is provided only ondiagnostic failure.

4. SYSTEM RESPONSE

IP = In Progress. Request has been accepted. Output message(s) will follow.


5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesDGN-DCS-TRKGRP



Issue 28 DGN:CELL-SG-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN CELL SG August 2005



DGN:CELL-SG-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN CU

ID............. DGN:CURELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Diagnoses the specified computer Control Unit (CU) complex or a specified unit within theCU complex.

Format 1: Diagnoses the specified CU complex.

Format 2: Diagnoses the Central Control (CC) unit.

Format 3: Diagnoses the specified Channel (CH).

Format 4: Diagnoses the Cache Store Unit (CSU).

Format 5: Diagnoses the specified Direct Memory Access (DMA) unit.

Format 6: Diagnoses the specified Main Store Controller (MASC) unit.

Format 7: Diagnoses the Store Address Translator (SAT) circuit pack.

Format 8: Diagnoses the Utility Circuit (UC) circuit pack.

2. FORMAT

[1] DGN:CU a [;[RAW] [,UCL] [,REX ,DEX ]] [:TLP]!

[2] DGN:CU a,CC 0[;[RPT c][,RAW][,UCL][,REX ,DEX]][:[PH d[-e]][,TLP]]!

[3] DGN:CU a,CH b[;[RPT c][,RAW][,UCL][,REX ,DEX]][:[PH d[-e]][,TLP][,{DFC IOP}f]]!

[4] DGN:CU a,CSU 0[;[RPT c][,RAW][,UCL][,REX ,DEX]][:[PH d[-e]][,TLP]]!

[5] DGN:CU a,DMA b[;[RPT c][,RAW][,UCL][,REX ,DEX]][:[PH d[-e]][,CONT][,TLP]]!

[6] DGN:CU a,MASC b[;[RPT c][,RAW][,UCL][,REX ,DEX]][:[PH d[-e]][,TLP]]!

[7] DGN:CU a,SAT 0[;[RPT c][,RAW][,UCL][,REX ,DEX]][:[PH d[-e]][,TLP]]!

[8] DGN:CU a,UC 0[;[RPT c][,RAW][,UCL][,REX ,DEX]][:[PH d[-e]][,TLP]]!


Issue 28 DGN:CU-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN CU August 2005


a = Member number (0-1).

b = Subunit number. See the Member Numbers Appendix, APP:MEM-NUM-D,Table D.

c = Number of times diagnostic is repeated. Maximum is 256; default is one.

NOTE: This option does not override early terminations. UCL should also bespecified if the diagnostic terminates.

RAW = Print the diagnostic results of every phase. Default is the first five failures ofeach failing phase.


NOTE: This option does not override forced early terminations.

REX = Run routine exercise phases in addition to the normal (automatic) phases.This option will not allow demand exercise phases to be run even if the rangeof phases specified includes such a phase.

DEX = Run demand exercise phases in addition to routine exercise and normal(automatic) phases. This option will not allow special demand exercisephases which require user interaction to be run even if the range of phasesspecified includes such a phase.

d = The number of the first phase to be executed.

e = The number of the last phase to be executed.

PH = Protocol handler.

TLP = Executes the Trouble Locating Procedure (TLP) at the conclusion of thediagnostic. This process generates a list of suspected faulty equipment.

NOTE: It is recommended that the TLP and UCL parameters not be specifiedtogether because it may produce an improper TLP listing.

f = Member number of the DFC (0-7) or IOP (0-15) that is to be used as ahelper unit. When a helper unit is required but the specified helper unit isinappropriate or unavailable, the helper unit dependent tests are skipped.

CONT = Include only the specified unit (controller). Units attached to the specifiedunit will not be included. If the specified unit has no attached units, CONT isignored. Format 5 is currently used by the DMA. If this parameter is notspecified, the DMA controller and all channels connected to it are diagnosed.


DGN:CU-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN CU

4. SYSTEM RESPONSE



— INCONSISTENT KEYWORDThe combination of keywords is not a valid combination.

— INVALID DATANot a valid value for the phase option.






— MISSING DATAData required for a keyword in the stated parameter block was notfound.

— MISSING KEYWORDA required keyword is missing from the input. Unit to diagnose mustbe specified.

— RANGE ERRORInput is out of the valid range.

PF = Printout Follows. Followed by a DGN-CU output message.


5. REFERENCES

IM/OM References:

Input MessagesOP:DMQRMV:CURST:CUSTOP:DMQ

Output MessagesANALY-TLPFILEDGN-CUOP-DMQ


Issue 28 DGN:CU-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN CU August 2005

Input AppendicesAPP:MEM-NUM-D

Other References:


Display/Menu Page Name:COMMON PROCESSOR DISPLAY


DGN:CU-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN DCI

ID............. DGN:DCIRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Diagnoses the specified Dual Serial Channel/Computer Interconnect (DCI).

2. FORMAT

DGN:DCI a[;[RPT b][,RAW][,UCL][,REX ,DEX]][:[PH c[-d]][,TLP]]!



b = Number of times diagnostic is repeated. The maximum is 256. The default isone.


RAW = Prints the diagnostic results of every phase. The default is the first fivefailures of each failing phase.



REX = Runs routine exercise phases in addition to the normal (automatic) phases.This option will not allow demand exercise phases to be run even if the rangeof phases specified includes such a phase.

DEX = Runs demand exercise phases in addition to routine exercise and normal(automatic) phases. This option will not allow special demand exercisephases that require user interaction to be run even if the range of phasesspecified includes such a phase.

c = The number of the first phase to be executed.

d = The number of the last phase to be executed.


NOTE: The TLP and UCL parameters should not be used together because additionaltest results may adversely affect the TLP listing.

4. SYSTEM RESPONSE





Issue 28 DGN:DCI-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN DCI August 2005










PF = Printout Follows. Followed by a DGN-DCI output message.


5. REFERENCES

IM/OM References:

Input MessagesOP:DMQRMV:DCIRST:DCISTOP:DMQ

Output MessagesANALY-TLPFILEDGN-DCIOP-DMQ

Other References:




DGN:DCI-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN DCS DL

ID............. DGN:DCS-DLRELEASE ....... 6.0 and laterTYPE .......... Input

1. PURPOSE

Diagnoses the specified Digital Cellular Switch (DCS) data link. The loopback option teststhe associated data transmission facility.

This command is not applicable for a DCS switch with Signaling System 7 (SS7) data linkconnections.

2. FORMAT

DGN:DCS a, DL b; c [,ERR] [,RPT d][,UCL] [ CLASS e]!


a = DCS number (1-16).



DSCLB — Place the Dedicated Switch Connection (DSC) associated withDCS a, DL b in the loopback mode. This action will cause theDSC to be looped back toward the Link Node (LN) andtoward the DCS. Remove the loopback connection by usingRST:DCS-DL or RMV:DCS-DL.

ECHO — Puts the specified linknode data link controller in the echomode. All data received from the data facility are echoedback. Use this mode when external test equipment requires aloopback mode. Remove the echo mode by restoring the datalink.

LOCALLB — Perform near-end data facility loopback test. The testautomatically places the near-end data facility in the near-endloopback mode. Only applicable with an RS-449 interface.

LOOPBACK — Performs data facility loopback test from the linknode. Thistest requires a manually placed loopback in the data facility.

REMOTELB — Perform far-end data facility loopback test. This automaticallyplaces the far-end data facility in the far-end loopback mode.Only applicable with an RS-449 interface.

ERR = Dumps the protocol error registers at the conclusion of the loopback test.Valid only if c = LOOPBACK, LOCALLB or REMOTELB.


UCL = Unconditionally executes the diagnostic with no early termination and printsall failures. Normal mode stops on first failure.



Issue 28 DGN:DCS-DL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN DCS DL August 2005

4. SYSTEM RESPONSE


NG = No Good. Necessary conditions for message execution (including apossibly unequipped DCS data link) were not met. Requested DCS is aswitch with SS7 data link connections.




5. REFERENCES

IM/OM References:

Input MessagesRMV:DCS-DLRST:DCS-DL

Output MessagesDGN-DCS-DLSTOP-DGN-CELL

Other References:



DGN:DCS-DL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN DCS TRKGRP

ID............. DGN:DCS-TRKGRPRELEASE ....... 17.0 and laterTYPE .......... Input

1. PURPOSE

Diagnoses a trunk. This input message permits use of the Digital Cellular Switch (DCS)trunk representation to identify the trunk for diagnosis. A trunk that has failed adiagnostic will be removed from service; otherwise, the trunk will be returned to its statebefore the diagnostic.

2. FORMAT

DGN:DCS a, TRKGRP b [, MEMBER c][, LBC][, ALL] [ CLASS d]!



b = Trunk group number:

1-2000 — for 5ESS DCS.

c = Trunk member number:


If a trunk member is not specified, the entire trunk group will be diagnosed.

LBC = Request the Loopback Clear (LBC) test.

ALL = Request all measurement data, regardless of diagnostic passage or failure.Without this option selected, measurement data is provided only ondiagnostic failure.


4. SYSTEM RESPONSE


NG = No Good. Necessary condition for execution of request not met. DCS ortrunk identification likely not valid.

NG = No Good.

NG - CDMA feature not on for cell n No Good. The packet pipe is associatedwith cell n which does not have the CDMA feature activated.

NG - REQUEST NOT ALLOWED No Good. For packet pipe trunks, the diagnostic is notcurrently supported.



Issue 28 DGN:DCS-TRKGRP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN DCS TRKGRP August 2005

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesDGN-DCS-TRKGRP

Other References:



DGN:DCS-TRKGRP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN DFC

ID............. DGN:DFCRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Diagnoses the specified Disk File Controller (DFC).

NOTE: The Moving Head Disk (MHD) cannot be diagnosed if the DFC is not in service.Therefore, a controller and its associated disk units cannot be diagnosed with oneinput message.

2. FORMAT

DGN:DFC a[;[RPT b][,RAW][,UCL][,REX ,DEX]][:[PH c[-d]][,CONT][,TLP][,CU e]]!












CONT = Includes only the specified unit (controller). Units attached to the specifiedunit will not be included. Default is diagnose DFC variable a only.




Issue 28 DGN:DFC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN DFC August 2005

e = Member number of the Control Unit (CU) helper unit (0-1). When a helperunit is not required, the specified helper unit is not used. When a helper unitis required but the specified helper unit is inappropriate or unavailable, thehelper unit dependent tests are skipped. The off-line CU is required as ahelper unit when demand phase 15 is executed.

NOTE: The helper CU must be Out Of Service (OOS) and must be diagnosed as AllTests Passed (ATP) before it is used as a helper unit.

4. SYSTEM RESPONSE













PF = Printout Follows. Followed by a DGN-DFC output message.



DGN:DFC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN DFC

5. REFERENCES

IM/OM References:

Input MessagesOP:DMQRMV:DFCRST:DFCSTOP:DMQ

Output MessagesANALY-TLPFILEDGN-DFCOP-DMQ

Other References:




Issue 28 DGN:DFC-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN DFC August 2005



DGN:DFC-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN DUIC

ID............. DGN:DUICRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Diagnoses the specified Direct User Interface Controller (DUIC).

NOTE: The Input/Output Processor (IOP) must be in service before the DUIC can bediagnosed.

2. FORMAT

DGN:DUIC a[;[RPT b][,RAW][,UCL][,REX ,DEX]][:[PH c[-d]][,TLP][,CONT]]!



b = Number of times the diagnostic is repeated. The maximum is 256. Thedefault is one.




NOTE: This option does not override a forced early termination.



c = Number of the phase to be executed, or the first number in a range of phases.

d = Specifies the last phase to be executed.



CONT = Includes only the specified unit (controller). Units attached to the specifiedunit will not be included. If the specified unit has no attached units, CONT isignored.


Issue 28 DGN:DUIC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN DUIC August 2005

4. SYSTEM RESPONSE













PF = Printout Follows. Followed by a DGN-DUIC output message.


5. REFERENCES

IM/OM References:

Input MessagesOP:DMQRMV:DUICRST:DUICSTOP:DMQ


DGN:DUIC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN DUIC

Output MessagesANALY-TLPFILEDGN-DUICOP-DMQ

Other References:



Issue 28 DGN:DUIC-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN DUIC August 2005



DGN:DUIC-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN ECP DL

ID............. DGN:ECP-DLRELEASE ....... 2.0 and laterTYPE .......... Input

1. PURPOSE

Diagnoses the specified inter- Executive Cellular Processor (ECP) data link. The loopbackoption tests the associated data transmission facility.

2. FORMAT

DGN:ECP a, DL b; c [,ERR] [,RPT d][,UCL] [ CLASS e]!


a = ECP number (1-15).



DSCLB — Places the Dedicated Switch Connection (DSC) associated withECP a DL b in the loopback mode. This action will cause theDSC to be looped back toward the Link Node (LN) andtoward the ECP. Remove the loopback connection by usingRST:ECP a, DL b or RMV:ECP a, DL b.

ECHO — Puts the specified link node data link controller in the echomode. All data received from the data facility are echoedback. Use this mode when external test equipment requires aloopback mode. Remove the echo mode by restoring the datalink.

LOCALLB — Performs near-end data facility loopback test. The testautomatically places the near-end data facility in the near-endloopback mode. Only applicable with an RS-449 interface.

LOOPBACK — Performs data facility loopback test from the linknode. Thistest requires a manually placed loopback in the data facility.

REMOTELB — Performs far-end data facility loopback test. Thisautomatically places the far-end data facility in the far-endloopback mode. Only applicable with an RS-449 interface.

ERR = Dumps the protocol error registers at the conclusion of the loopback test.Valid only if c = LOOPBACK, LOCALLB or REMOTELB.


UCL = Unconditionally executes the diagnostic with no early termination and printsall failures. Normal mode stops on first failure.

NOTE: The UCL mode can flood the Teletypewriter (TTY) with outputmessages.

e = Overriding message class (151-213). This option may be used only if theVirtual System Output Message Routing feature is supported.


Issue 28 DGN:ECP-DL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN ECP DL August 2005

4. SYSTEM RESPONSE


NG = No Good. Necessary conditions for message execution (including apossibly unequipped inter-ECP data link) were not met.




5. REFERENCES

IM/OM References:

Input MessagesRMV:ECP-DLRST:ECP-DL

Output MessagesDGN-ECP-DLSTOP-DGN-CELL

Other References:



DGN:ECP-DL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN HSDC

ID............. DGN:HSDCRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Diagnoses the specified High-Speed Synchronous Data Link Controller (HSDC).

NOTE: The Input/Output Processor (IOP) must be in service before the HSDC can bediagnosed.

2. FORMAT

DGN:HSDC a[;[RPT b][,RAW][,UCL][,REX ,DEX]][:[PH c[-d]][,TLP][,CONT]]!








REX = Runs Routine Exercise (REX) phases in addition to the normal (automatic)phases. This option will not allow demand exercise phases to be run even ifthe range of phases specified includes such a phase.

DEX = Runs Demand Exercise (DEX) phases in addition to routine exercise andnormal (automatic) phases. This option will not allow special demandexercise phases that require user interaction to be run even if the range ofphases specified includes such a phase.

c = Specifies the first phase to be executed.



NOTE: The TLP and UCL parameters cannot be used together because additional testresults may adversely affect the TLP listing.



Issue 28 DGN:HSDC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN HSDC August 2005

4. SYSTEM RESPONSE













PF = Printout Follows. Followed by a DGN-HSDC output message.


5. REFERENCES

IM/OM References:

Input MessagesRMV:HSDCRST:HSDCRST:IOP


DGN:HSDC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN HSDC

Output MessagesANALY-TLPFILEDGN-HSDCRST-IOP

Other References:



Issue 28 DGN:HSDC-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN HSDC August 2005



DGN:HSDC-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN IOP

ID............. DGN:IOPRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Diagnoses the specified Input/Output Processor (IOP).

NOTE: The peripheral controllers cannot be diagnosed if the IOP is not in service.Therefore, an IOP and its associated peripheral controllers cannot be diagnosedwith one input message.

2. FORMAT

DGN:IOP a[;[RPT b][,RAW][,UCL][,REX ,DEX]][:[PH c[-d]][,CONT][,TLP][,CU e]]!












CONT = Includes only the specified unit (controller). Units attached to the specifiedunit will not be included. Default is diagnose IOP variable a only.




Issue 28 DGN:IOP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN IOP August 2005

e = Member number of the Control Unit (CU) helper unit (0-1). When a helperunit is not required, the specified helper unit is not used. When a helper unitis required but the specified helper unit is inappropriate or unavailable, thehelper unit dependent tests are skipped. The off-line CU is required as ahelper unit when demand phase 15 is executed.


4. SYSTEM RESPONSE













PF = Printout Follows. Followed by a DGN-IOP output message.



DGN:IOP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN IOP

5. REFERENCES

IM/OM References:

Input MessagesOP:DMQRMV:IOPRST:IOPSTOP:DMQ

Output MessagesANALY-TLPFILEDGN-IOPOP-DMQ

Other References:



Issue 28 DGN:IOP-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN IOP August 2005



DGN:IOP-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN LN

ID............. DGN:LNRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Diagnoses the specified Link Node (LN).

Options RPT and UCL can be used to change the system’s usual method of running adiagnostic, which is running the diagnostic once and adhering to early terminationinstructions in the diagnostic. An early termination instruction in a diagnostic causes thediagnostic to terminate when a test within the diagnostic phase fails. Option RPT requeststhe repetition of diagnostics. Option UCL requests that early termination instructions in adiagnostic be overridden and the diagnostic be allowed to continue when a test within thediagnostic phase fails.

There are two kinds of early termination instructions that may be contained in adiagnostic. One kind of early termination instruction is overridden when the DGN:LNinput command includes the UCL option. The other kind of early termination instruction isa "forced" early termination. The failure of a test that includes a "forced" early terminationinstruction is considered a significant enough failure that the early termination cannot beoverridden by the UCL option.

An early termination instruction can be identified in a diagnostic listing .l file bysearching for erlytrm. A "forced" early termination instruction can be identified bychecking for force as a part of the erlytrm instruction.

2. FORMAT

DGN:LNa b [;[RPT c] [,RAW] [,UCL]] [:PH d [,TLP :TLP]]!




c = Number of repetitions desired. Maximum = 256. Default = 1.

NOTE: This option does not override early termination. If it is desired tooverride early termination, the UCL option should also be specified.The UCL option, however will not override forced earlytermination.

RAW = Print the diagnostic results of every phase. Default = Print the first fivefailures of each phase.

UCL = Unconditional execution - overrides early terminations, but not forced earlyterminations.



Issue 28 DGN:LN-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN LN August 2005

d = Specifies the phase or phases to be executed. It may be a single decimalnumber or a range (for example, to execute phases 10 through 13, enter10-13). Default = All automatic phases.

TLP = Execute the Trouble Locating Procedure at the conclusion of the diagnostic.This generates a list of suspected faulty equipment.

NOTE: The UCL and TLP must not be used together.

4. SYSTEM RESPONSE

Four sequential system actions are performed in response to this input command.

1. The LN is removed from service following the rules for the RMV:LN input message.

2. If the resultant LN major state is any of OOS, GROW, OFL, or UNAV, an attempt is madeto isolate the LN (for other major states, the diagnostic is aborted by DiagnosticMonitor [DIAMON]).

3. The specified (or default) diagnostic phases are run.

4. If the LN was in the active ring prior to the start of the diagnostics and wassuccessfully isolated (in 2 above), then at the conclusion of the diagnostic execution anattempt is made to include the LN back into the active ring. Otherwise, the node is leftin its original ring configuration state.

NOTE: The LN remains in the OOS, GROW, OFL, or UNAV state.

5. REFERENCES

IM/OM References:

Input MessagesCHG:SLK

Output MessagesDGN-AUDITDGN-LNRMV-LN

Other References:



401-661-045 Common Network Interface (CNI) Ring Maintenance- Ring and Ring Node Maintenance Procedures Section,- Diagnostic User’s Guide Section


DGN:LN-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN MHD

ID............. DGN:MHDRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Diagnoses the specified Moving Head Disk (MHD).

NOTE: The Disk File Controller (DFC) must be in service before the MHD can bediagnosed.

2. FORMAT

DGN:MHD a[;[RPT b][,RAW][,UCL][,REX ,DEX]][:[PH c[-d]][,TLP][,CONT]]!








REX = Runs Routine Exercise (REX) phases in addition to the normal (automatic)phases. This option will not allow demand exercise phases to be run even ifthe range of phases specified includes such a phase.

DEX = Runs Demand Exercise (DEX) phases in addition to routine exercise andnormal (automatic) phases. This option will not allow special demandexercise phases which require craft interaction to be run even if the range ofphases specified includes such a phase.

c = Number of the first phase to be executed.

d = Number of the last phase to be executed.




Issue 28 DGN:MHD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN MHD August 2005


4. SYSTEM RESPONSE













PF = Printout Follows. Followed by a DGN-MHD output message.


5. REFERENCES

IM/OM References:

Input MessagesOP:DMQRMV:MHDRST:MHDSTOP:DMQ


DGN:MHD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN MHD

Output MessagesANALY-TLPFILEDGN-MHDOP-DMQ

Other References:




Issue 28 DGN:MHD-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN MHD August 2005



DGN:MHD-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN MT

ID............. DGN:MTRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Diagnoses the specified Magnetic Tape (MT).

NOTE: The Disk File Controller (DFC) must be in service before the MT can bediagnosed.

2. FORMAT

DGN:MT a[;[RPT b][,RAW][,UCL][,REX ,DEX]] [:[PH c [-d]] [,TLP] [,CONT]]!






UCL = Unconditional (UCL) execution.


REX = Runs Routine Exercise (REX) phases in addition to the normal (automatic)phases. This option will not allow Demand Exercise (DEX) phases to be runeven if the range of phases specified includes such a phase.

DEX = Runs DEX phases in addition to REX and normal (automatic) phases. Thisoption will not allow special DEX phases which require user interaction torun even if the range of phases specified includes such a phase.

c = Number of the first phase to be executed.

d = Number of the last phase to be executed.




Issue 28 DGN:MT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN MT August 2005

CONT = Includes only the specified unit Controller (CONT). Units attached to thespecified unit will not be included. If the specified unit has no attached units,CONT is ignored.

4. SYSTEM RESPONSE













PF = Printout Follows. Followed by a DGN-MT output message.


5. REFERENCES

IM/OM References:

Input MessagesOP:DMQRMV:MTRST:MT

Output MessagesANALY-TLPFILEDGN-MTOP-DMQ


DGN:MT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN MT

Other References:




Issue 28 DGN:MT-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN MT August 2005



DGN:MT-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN MTC

ID............. DGN:MTCRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Diagnoses the specified Magnetic Tape Controller (MTC).

NOTE: The Input/Output Processor (IOP) must be in service before the MTC can bediagnosed.

2. FORMAT

DGN:MTC a[;[RPT b][,RAW][,UCL][,REX ,DEX]][:[PH c[-d]][,TLP][,CONT][,MT e]]!



b = Number of times the diagnostic is to be repeated. The maximum is 256. Thedefault is one.






DEX = Runs DEX phases in addition to routine exercise and normal (automatic)phases. This option will not allow special demand exercise phases whichrequire craft interaction to be run even if the range of phases specifiedincludes such a phase.

c = Specifies the number of the first phase to be executed.


NOTE: Before phase 5 is executed, a diagnostic test tape with a write ring must bemounted on the specified Magnetic Tape (MT).


Issue 28 DGN:MTC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN MTC August 2005


NOTE: It is not recommended that the TLP and UCL parameters be specifiedtogether since it may produce an improper TLP listing.


e = Member number of the magnetic tape device that is to be used as a helperunit (0-255). When a helper unit is not required, the specified helper unit isignored. When a helper unit is required but the specified helper unit isinappropriate or unavailable, the helper unit dependent tests are skipped.Member number of the MT device helper unit is required when demandphase 5 is executed.

4. SYSTEM RESPONSE








— EXTRA-KEYWORDDuplicate or extraneous keywords were input.





PF = Printout Follows. Followed by a DGN-MTC output message.



DGN:MTC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN MTC

5. REFERENCES

IM/OM References:

Input MessagesOP:DMQRMV:MTCRST:MTCSTOP:DMQ

Output MessagesANALY-TLPFILEDGN-MTCOP-DMQ

Other References:



Issue 28 DGN:MTC-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN MTC August 2005



DGN:MTC-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN MTTYC

ID............. DGN:MTTYCRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Diagnoses the specified Maintenance Teletypewriter Controller (MTTYC).

NOTE: The Input/Output Processor (IOP) must be in service before the MTTYC can bediagnosed.

2. FORMAT

DGN:MTTYC a[;[RPT b][,RAW][,UCL][,REX ,DEX]][:[PH c[-d]][,TLP][,CONT]]!









DEX = Runs DEX phases in addition to routine exercise and normal (automatic)phases. This option will not allow special demand exercise phases whichrequire user interaction to be run even if the range of phases specifiedincludes such a phase.


d = Specifies the last phase to be entered.




Issue 28 DGN:MTTYC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN MTTYC August 2005


4. SYSTEM RESPONSE













PF = Printout Follows. Followed by a DGN-MTTYC output message.


5. REFERENCES

IM/OM References:

Input MessagesOP:DMQRMV:MTTYCRST:MTTYCSTOP:DMQ


DGN:MTTYC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN MTTYC

Output MessagesANALY-TLPFILEDGN-MTTYCOP-DMQ

Other References:




Issue 28 DGN:MTTYC-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN MTTYC August 2005



DGN:MTTYC-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN RPCN

ID............. DGN:RPCNRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Diagnoses the specified Ring Peripheral Controller Node (RPCN).

Options RPT and UCL can be used to change the system’s usual method of running adiagnostic, which is running the diagnostic once and adhering to early terminationinstructions in the diagnostic. An early termination instruction in a diagnostic causes thediagnostic to terminate when a test within the diagnostic phase fails. Option RPT requeststhe repetition of diagnostics. Option UCL requests that early termination instructions in adiagnostic be overridden and the diagnostic be allowed to continue when a test within thediagnostic phase fails.

There are two kinds of early termination instructions that may be contained in adiagnostic. One kind of early termination instruction is overridden when the DGN:RPCNinput command includes the UCL option. The other kind of early termination instruction isa "forced" early termination. The failure of a test that includes a "forced" early terminationinstruction is considered a significant enough failure that the early termination cannot beoverridden by the UCL option.

An early termination instruction can be identified in a diagnostic listing .l file bysearching for erlytrm. A "forced" early termination instruction can be identified bychecking for force as a part of the erlytrm instruction.

2. FORMAT

DGN:RPCNa 0[;[RPT b] [,RAW] [,UCL]] [:PH c [,CU d] [,TLP] :TLP]!


a = A Ring Node (RN) group number (00-63) with explicit leading zero forgroup numbers less than 10.

b = Number of repetitions desired. Maximum = 256. Default = 1.

NOTE: This option does not override early termination. If it is desired tooverride early termination, the UCL option should also be specified.The UCL option, however, will not override forced earlytermination.

RAW = Print the diagnostic results of every phase. Default = Print the first fivefailures of each phase.

UCL = Unconditional execution - overrides early terminations, but not forced earlyterminations.



Issue 28 DGN:RPCN-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN RPCN August 2005

c = Specifies the phase or phases to be executed. It may be a single decimalnumber or a range (for example, to execute phases 10 through 13, enter10-13). Default = All automatic phases.

d = Helper Control Unit number (0-1). Off-line CU required as a helper unitwhen demand phase 14 is specified. Default = All automatic phases.

NOTE: The helper CU must be out of service and All Tests Passed (ATP)before it can be used as a helper.

TLP = Execute the Trouble Locating Procedure at the conclusion of the diagnostic.This process generates a list of suspected faulty equipment.

NOTE: The UCL and TLP must not be used together.

4. SYSTEM RESPONSE

Four sequential system actions are performed in response to this input command.

1. The RPCN is removed from service following the rules for the RMV:RPCN inputmessage.

2. If the resultant RPCN major state is any of OOS, GROW, OFL, or UNAV, an attempt ismade to isolate the RPCN (for other major states, the diagnostic is aborted byDiagnostic Monitor [DIAMON]).

3. The specified (or default) diagnostic phases are run.

4. If the RPCN was in the active ring prior to the start of the diagnostics and has beensuccessfully isolated (in 2 above), an attempt is made to include the RPCN back intothe active ring at the conclusion of the diagnostic execution. Otherwise, the node is leftin its original ring configuration state.

NOTE: The RPCN remains in the OOS, GROW, OFL, or UNAV state.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesANALY-TLPFILEDGN-AUDITDGN-RPCNRMV-RPCN


DGN:RPCN-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN RPCN

Other References:



401-661-045 Common Network Interface (CNI) Ring Maintenance- Diagnostic User’s Guide Section


Issue 28 DGN:RPCN-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN RPCN August 2005



DGN:RPCN-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN SCSDC

ID............. DGN:SCSDCRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Diagnoses the specified Scanner Signal Distributor Controller (SCSDC).

NOTE: The Input/Output Processor (IOP) must be in service before the SCSDC can bediagnosed.

2. FORMAT

DGN:SCSDC a[;[RPT b][,RAW][,UCL][,REX ,DEX]][:[PH c[-d]] [,TLP][,CONT]]!









DEX = Runs DEX phases in addition to REX and normal (automatic) phases. Thisoption will not allow special demand exercise phases that require userinteraction to be run even if the range of phases specified includes such aphase.





CONT = Diagnoses only the specified controller. Units attached to the specifiedcontroller will not be diagnosed.


Issue 28 DGN:SCSDC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN SCSDC August 2005

4. SYSTEM RESPONSE













PF = Printout Follows. Followed by a DGN-SCSDC output message.


5. REFERENCES

IM/OM References:

Input MessagesOP:DMQRMV:SCSDCRST:IOPRST:SCSDCSTOP:DMQ

Output MessagesANALY-TLPFILEDGN-SCSDCOP-DMQRST-IOP


DGN:SCSDC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN SCSDC

Other References:



Issue 28 DGN:SCSDC-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN SCSDC August 2005



DGN:SCSDC-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN SDLC

ID............. DGN:SDLCRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Diagnoses the specified Synchronous Data Link Controller (SDLC).

NOTE: The Input/Output Processor (IOP) must be in service before the SDLC can bediagnosed.

2. FORMAT

DGN:SDLC a[;[RPT b][,RAW][,UCL][,REX ,DEX]][:[PH c[-d]][,TLP] [,CONT]]!









DEX = Runs DEX phases in addition to routine exercise and normal (automatic)phases. This option will not allow special demand exercise phases whichrequire user interaction to be run even if the range of phases specifiedincludes such a phase.





CONT = Diagnoses only the specified controller. Units attached to the specifiedcontroller will not be diagnosed.


Issue 28 DGN:SDLC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN SDLC August 2005

4. SYSTEM RESPONSE













PF = Printout Follows. Followed by a DGN-SDLC output message.


5. REFERENCES

IM/OM References:

Input MessagesOP:DMQRMV:SDLCRST:IOPRST:SDLCSTOP:DMQ

Output MessagesANALY-TLPFILEDGN-SDLCOP-DMQRST-IOP


DGN:SDLC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN SDLC

Other References:



Issue 28 DGN:SDLC-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN SDLC August 2005



DGN:SDLC-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN TTYC

ID............. DGN:TTYCRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Diagnoses the specified Teletypewriter Controller (TTYC).

NOTE: The Input/Output Processor (IOP) must be in service before the TTYC can bediagnosed.

2. FORMAT

DGN:TTYC a[;[RPT b][,RAW][,UCL][,REX ,DEX]][:[PH c[-d]][,TLP][,CONT]]!



b = Number of times the diagnostic is to be repeated. The maximum is 256. Thedefault is one.






DEX = Runs DEX phases in addition to routine exercise and normal (automatic)phases. This option will not allow special demand exercise phases thatrequire user interaction to be run even if the range of phases specifiedincludes such a phase.






Issue 28 DGN:TTYC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN TTYC August 2005

CONT 1 Includes only the specified unit (controller). Units attached to the specifiedunit will not be included. If the specified unit has no attached units, CONT isignored.

4. SYSTEM RESPONSE













PF = Printout Follows. Followed by a DGN-TTYC output message.


5. REFERENCES

IM/OM References:

Input MessagesOP:DMQRMV:TTYCRST:TTYCSTOP:DMQ


DGN:TTYC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DGN TTYC

Output MessagesANALY-TLPFILEDGN-TTYCOP-DMQ

Other References:



Issue 28 DGN:TTYC-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksDGN TTYC August 2005



DGN:TTYC-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DNLD CELL

ID............. DNLD:CELLRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Requests a Non-Volatile Memory (NVM) update of the specified unit(s) at the specifiedcell(s).

NOTE: Supported in Series II only.

2. FORMAT

DNLD:CELL a, b [ ;c ] [ CLASS d ]!



• A single cell site.• A range (with maximum in range being 32 cells).• A list of cell sites separated by commas and enclosed in parentheses

(maximum 32).

b = Downloadable Series II Cell Site (SII-CS) software/firmware unit types:

BBA { y z } — BCR-BIU-ACU units (CDMA only)CAT { w } — Clock and tone boardCCC { y z } — Code Division Multiple Access (CDMA) cluster controller

(CDMA only)CRTU — Radio test unit (CDMA)CSC x, CPI — Communications processor boardCSC x, CPU — Cell site controller core boardLC { y z } — Locate radioLC y ORIG — Original locate radio (before Automatic Radio

Reconfiguration [ARR])RA { y z } — Voice radioRA y ORIG — Original voice radio (before ARR)RCU [ z ] — All locate, setup and voice radiosRTU — Radio test unit (AMPS)RUPART — Partial radio unitsRUREST — Remaining radio unitsSU { y z } — Setup radioSU y ORIG — Original setup radio (before ARR)TRTU — Radio test unit (TDMA)

Key:

w = Depends on the technology:

0-11 — For CDMA radios in 13.1 CDMA PCS minicell with growthframe 5 frame technology.



Issue 28 DNLD:CELL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDNLD CELL August 2005


0-5 — For CDMA radios, At most 6 can be specified for CDMAradios.

0-3 — For non-CDMA radios. At most 4 can be specified for non-CDMA radios.

x = 0-1.

y = A single radio or a range or a list of radios. (At most 8 can be specified.)y must be a single radio if one of the following is specified: ORIG,ALLALT or ALLOFC.

z = One of the following:

ALL — All radios of that type at a cell site.ALLAMPS — All AMPS radios of that type at a cell site.ALLCDMA — Meaning all CDMA units of that type at a cell site.

ALLCDMA is only valid when b is BBA or CCC. If b is CCCand the cell is on APXD14.0 or later, then c may be CCCOFC,CCCALT, CCUOFC, CCUALT, or omitted which defaults toALLOFC. If b is BBA, then c does not apply.

ALLTDMA — All Time Division Multiple Access (TDMA) radios of thattype at a cell site.

CDMAREST — Used to update and restore the rest of the CDMA units(BBAs or CCCs) of that type with the correct NVM version.CDMAREST is valid for all values of c when: b is BBA or CCC,and c is ALLOFC or ALLALT The CDMAREST option is onlyvalid on R15.0 cells and beyond.

CAUTION: CCC CDMAREST must be used following the downloading ofone or more CCC(s) to complete downloading the rest of theCDMA Cluster Controller (CCC) maintenance units with thenew NVM image.

NOTES: 1. The combination of SU ALLTDMA is invalid.2. RUPART is used to update some of the idle radios before

doing switch and boot on the mate Cell Site Controller (CSC)in a Cell Software Update procedure.

3. RUREST is used to update and restore the rest of the radioand radio test units with the new NVM after doing switchand boot on the mate CSC in a Cell Software Updateprocedure.

CAUTION: RUREST must be used following RUPART to complete downloading therest of the radio and radio test units with the new NVM after doingswitch and boot on the mate CSC in a Cell Software Update procedure.


DNLD:CELL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DNLD CELL

c = Firmware specifications for Radio Channel Unit (RCU), Radio Test Unit(RTU)/ TDMA Radio Test Unit (TRTU)/ CDMA Radio Test Unit (CRTU),and CCC units:

ALLALT — Updates the given CCC and all its associated CDMA ChannelUnit (CCU)/ Channel Elements (CEs) with alternate version -CDMA only.

ALLOFC — Updates the given CCC and all its associated CCU/CEs withofficial version - CDMA only.

ALT — Both main controller and decoder alternate firmware.CCCALT — Updates CCC with alternate version. - CDMA only.CCCOFC — Updates CCC with official version. - CDMA only.CCUALT — Updates CCU image with alternate version. - CDMA only.CCUOFC — Updates CCU image with official version. - CDMA only.DCODALT — Decoder alternate firmware.DCODOFC — Decoder official firmware.MAINALT — Main controller alternate firmware.MAINOFC — Main controller official firmware.OFC — Both main controller and decoder official firmware.

NOTES: 1. ALT, MAINALT, and DCODALT are invalid for RTU and TRTUunits.

2. DCODALT, DCODOFC, MAINALT and MAINOFC are invalid forCRTU units.

3. DCODOFC and DCODALT are invalid for TDMA units.4. The combination of SU ALLTDMA is invalid.5. ALLCDMA is only valid when:

b is BBA or CCC, andc is CCCOFC, CCCALT, CCUOFC, CCUALT or ALLCDMA.The ALLCDMA option is only valid on R14.0 cells and beyond.

6. If you specify either ALLALT or ALLOFC, you must havespecified a single CCC at variable b.


4. SYSTEM RESPONSE

NG = No Good. Cell is doing either an NVM update or Random AccessMemory (RAM) download. Wait until the cell is done with either activitybefore issuing command again. If multiple cells are requested, the entirecommand fails if any of the specified cells are downloading.

NG = No Good. The technology of some unit does not match the technologyrequested.



Issue 28 DNLD:CELL-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksDNLD CELL August 2005


RL = Retry Later Too many NVM update commands have been enteredsimultaneously. Wait until an NVM update completes before entering theNVM update command again.

5. REFERENCES

IM/OM References:

Input MessagesINH:CELLINIT:CELLRMV:CELL

Output MessagesREPT-CELL-NVM

Other References:



DNLD:CELL-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DNLD CELL DLOPTS

ID............. DNLD:CELL-DLOPTSRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Requests a Non-Volatile Memory (NVM) update of the Data Link (DL) optioning fields atthe specified cell. The request works for an offline cell site controller only.

NOTE: You must enter all 7 parameters in the given order.

2. FORMAT

DNLD:CELL a, DLOPTS b c d e f g h!



b = Digital Signal Level 1 (DS1)/ DL configuration:0 = 2 DS1 boards and 2 datalinks1 = 1 DS1 board and 2 datalinks2 = 1 DS1 board and 1 datalink

c = Data rate:0 = 9.6 Kbps1 = 56 Kbps

d = Framing mode:0 = D4 frame (applies to T1 signaling type only)1 = Extended super frame (applies to T1 signaling type only)2 = Conference on European Postal and Telecommunications

Administrations (CEPT) with CRC4 framing (applies to all E1signaling options)

3 = CEPT without CRC4 framing (applies to all E1 signaling options)

NOTE: The meanings of these values may not correspond to the meaningsof the Recent Change / Verify (RC/V) ceqcom2 Form framingmode values. Refer to the 401-610-036 Database Update Manual forinformation on ceqcom2 Form framing mode values.

e = Type of zero suppression:0 = Zero Code Suppression (ZCS) (applies to T1 signaling type only)1 = Bipolar with 8 Zero Substitution (B8ZS) (applies to T1 signaling type

only)2 = High Density Bipolar (HDB3) (applies to all E1 signaling options)3 = Alternate Mark Inversion (AMI) (applies to all E1 signaling options)

NOTE: The meanings of these values may not correspond to the meaningsof the RC/V ceqcom2 Form code suppression method values.Refer to the 401-610-036 Database Update Manual for information onceqcom2 Form code suppression method values.


Issue 28 DNLD:CELL-DLOPTS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDNLD CELL DLOPTS August 2005

f = Line length compensation:0 = 0 - 133 feet.1 = 134 - 266 feet.2 = 267 - 399 feet.3 = 400 - 533 feet.4 = 534 - 655 feet.

g = Signaling type:0 = T1 signaling.1 = E1/CEPT channel associated signaling.2 = E1/CEPT common channel signaling.

h = Cell type:0 = 0 - Series II cell site.2 = Series IIe basic station.3 = Series IIe growth station.4 = Series IIm cell site.5 = Series IImm cell site.

4. SYSTEM RESPONSE

NG = No Good. Cell is doing either NVM update or Random Access Memory(RAM) download. Wait until the cell is done with either activity beforeissuing command again. If multiple cells are requested, the entirecommand fails if any of the specified cells are downloading.

PF = Printout Follows. Command was accepted.

RL = Retry Later. Too many NVM update commands have been enteredsimultaneously. Wait until an NVM update completes before enteringNVM update command again.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesDNLD-CELL-DLOPTS

Other References:



DNLD:CELL-DLOPTS-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP ADDR

ID............. DUMP:ADDRRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Dumps the contents of a specified range of virtual addresses in the computer mainmemory as an action associated with a breakpoint. The range is specified by twoaddresses or an address and a length. The length defaults to a value of one.

If only one address is given, indirect addressing may be specified. In this case, the firstoffset listed is added to the contents of the given address and the result is interpreted as avirtual address. The number of offsets specified defines the length of the chain of virtualaddresses to be accessed in this way before accessing the desired range of dump locations.For example, a single offset with value zero uses the virtual address found in the locationspecified in the DUMP:ADDR input message for the dump location.

2. FORMAT

DUMP:ADDR {a-b a [,OFF c] [,L ,NL d]} [;WORD] /


a = Starting virtual address of the dump in decimal, binary, octal, or hexadecimalnotation. Assumed to be a byte address unless the WORD option is used.

b = Ending virtual address of dump. Assumed to be a byte address unless theWORD option is used.

c = A single offset or list of up to five offsets. Omission of the keyword impliesno indirect addressing. Offsets are in bytes unless the WORD option is used.

L d = The length of the dump, assumed to be in bytes unless the WORD option isused. Maximum 128 bytes or 32 words. Default is one, unless a range isexplicitly specified. The actual range of addresses dumped will be roundedout to word address boundaries.

NL d = Indicator that the operation should use the locations beginning d lower thanthe calculated address and ending at the address. The locations are used inascending order. Usage and limitation are the same as for the L option.

WORD = Indicates that all addresses, offsets, and lengths are to be interpreted aswords, including addresses derived in address chains. If this option isomitted, they are assumed to be byte values.

e = Dump direction:

L — Indicator that the operation should add the length d to the startingaddress to calculate the ending address.

NL — Indicator that the operation should use the locations beginning dlower than the calculated address and ending at the address. Thelocations are used in ascending order. Usage and limitation are thesame as for the L option.


Issue 28 DUMP:ADDR-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP ADDR August 2005

f = Addressing increment:

WORD - Indicates that all addresses, offsets, and lengths are to be interpretedin terms of words, including addresses derived in address chains. If thisoption is omitted, they are assumed to be byte values.

4. SYSTEM RESPONSE

?I = Identification Field contains an error. General syntax error, or one of thefollowing errors:

— INCONSISTENT DATA (ADDR)Address range must be in ascending order.


— MISSING KEYWORDPID or UID must be specified except in a WHEN action list.

— RANGE ERROR (L or NL)Length specified is too long or zero.

IP = In Progress. The input message has been added to the WHEN action list.


5. REFERENCES

IM/OM References:

Input MessagesDUMP:PIDDUMP:PMEMDUMP:REGDUMP:UIDWHEN:PIDWHEN:UID

Output MessagesDUMP-ADDR

Other References:



DUMP:ADDR-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP BKTAPE

ID............. DUMP:BKTAPERELEASE ....... 23.0 and laterTYPE .......... Input

1. PURPOSE

Displays the contents of the multi-volume Digital Audio Tape (DAT) logical volumeheaders and optionally provides an estimate of how full the tape is.

2. FORMAT

DUMP:BKTAPE;TD "a" [,TPSIZE b]!


a = Device filename of the DAT drive. See the User Guidelines in this manual fordefinitions and examples of tape device names.

b = Length in meters of the DAT mounted on the specified drive. The length isused to estimate how full the tape is. Valid lengths are 30-150 meters.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by a DUMP-BKTAPE output message.

5. REFERENCES

IM/OM References:

Input MessagesCOPY:BKDISKCOPY:BKTAPE

Output MessagesDUMP-BKTAPE



Issue 28 DUMP:BKTAPE-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP BKTAPE August 2005



DUMP:BKTAPE-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP CACHE

ID............. DUMP:CACHERELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Dumps the contents of the offline cache into computer processor main memory. Theportions of cache dumped are the ones which map to the kernel and interrupt stacks. Thecommand will not be accepted if the other Control Unit (CU) is in the standby state.

The cache (1K bytes) is placed at virtual address 0x80000 for the interrupt stack portionand at virtual address 0x6a0000 for the kernel stack. In the case of the kernel stack, theaddress dumped to will not correspond to the actual start of the kernel stack. This offset isnecessary to preserve the portions of the kernel stack which are not resident in the cachebut which do map to the address range used for the cache kernel stack. Whether aparticular stack entry is in cache or main memory is dependent upon whether thehardware is present and enabled, and the state of the ISTK bit in the PSW of the runningprocess. The reconstruction of the kernel stack (both cache and main memory) is left to theuser.

2. FORMAT

DUMP:CACHE!


See Purpose.

4. SYSTEM RESPONSE

NG = No Good. Could not access or reserve the Unit Control Block (UCB)record of the mate CU, or the mate CU was not out of service.

PF = Printout Follows. Followed by a DUMP-CACHE output message.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesDUMP-CACHE



Issue 28 DUMP:CACHE-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP CACHE August 2005



DUMP:CACHE-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP CELL

ID............. DUMP:CELLRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Dump a block of text or data memory from a cell.

2. FORMAT

DUMP:CELL a, b; ADRS c [, L d] [ CLASS e]!



• A single cell site

• A range (maximum number of cells in range is 32)

• A list of cell sites separated by commas and enclosed in parentheses.

If b is RA, LC, CCC, CRTU, or SU, a must be a single cell site number.

b = Cell site unit (Series II only):

CCC x — Code Division Multiple Access (CDMA) cluster controller,x = (1-42).

CCC x, CCU y[,CE z] — CDMA cluster controller, x = (1-42), y = CCUunit number (CDMA only), z = CE subunit number (CDMAonly).

CSC x — Cell site controller, x = (0-1).CSC x, CPI — Cell site controller, communications processor interface.

x = (0-1).LC x — Location radio, x = (0-39).RA x — Radio for Series II (SII) cells only, x = (0-191).SU x — Setup radio, x = (0-7 or 0-35 with Directional Setup).RTU — Radio test unit (AMPS).TRTU — Radio test unit (TDMA).

c = One-to-eight digit memory address in hexadecimal. For each hardware unit,valid ranges are represented below, a valid address would be any addresswithin the represented range of values.

For informational purposes only the invalid ranges and the function in thatrange are also specified for the CCC and CCU units. These ranges representinvalid ranges and cannot be dumped.


Issue 28 DUMP:CELL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP CELL August 2005

CDMA Cluster Controller Third Generation (CCC-3G) Valid dumpablerange:

— (X’30000000 - X’3FFFFFFF)— (X’40000001 - X’401FFFFF)— (X’4020001D - X’600FFFFF)— (X’60100001 - X’601FFFFF)— (X’60200001 - X’602FFFFF)— (X’60300001 - X’6FFFFFFF)— (X’80000000 - X’800007FE)— (X’80000800 - X’C001FFF7)— (X’C001FFFA - X’C001FFFB)— (X’C0020000 - X’C003FFF7)— (X’C003FFFA - X’C003FFFB)— (X’C0040000 - X’C005FFF7)— (X’C005FFFA - X’C005FFFB)— (X’C0060000 - X’C007FFF7)— (X’C007FFFA - X’C007FFFB)— (X’C0080000 - X’E003FFFF)

The following represents the ranges associated with the CCC functions.NOTE - These ranges are not dumpable:

Angel interrupt — (X’800007FF - X’800007FF)

DUSART 0 — (X’40000000 - X’4000001C)

DUSART 1 — (X’40200000 - X’4020001C)

ECU 1 DPR left and right Port Mailbox —(X’C001FFFC - X’C001FFFF)

ECU 1 bypass Enable Interrupt Reset —(X’C001FFF8 - X’C001FFF9)







Empty region after EPROM — (X’E0040000 - X’FFFFFFF)

Hardware reset strobe — (X’70000000 - X’7FFFFFFF)

Internal cache, bad access int CLR, series port 0 —(X’00000000 - X’2FFFFFFF)


DUMP:CELL-2 Issue 28


SPYDER-T interrupt clear — (X’60100000 - X’60100000)

Timer0clr — (X’60300000 - X’60300000)

Write violation interrupt clear — (X’60200000 - X’60200000)

CDMA Channel Unit Third Generation (CCU-3G). Valid address range:

— (X’F0000100 - X’F000012F)— (X’F1C00000 - X’F1C0012F)— (X’F2000000 - X’F200026F)— (X’F2400000 - X’F28001FF)— (X’F2C00000 - X’F2C0001F)— (X’F4000000 - X’F401FFFB)— (X’F4020000 - X’F510020B)— (X’F5100220 - X’F5110007)— (X’F5110010 - X’F5110207)— (X’F5110220 - X’F5120207)— (X’F5120220 - X’F5130207)— (X’F5130220 - X’F5132FFF)— (X’F5140000 - X’F513FFFF)— (X’F5140004 - X’F514014F)— (X’F5140200 - X’F514020B)— (X’F5140220 - X’F5150207)— (X’F5150220 - X’F515FFFF)— (X’F5160004 - X’F5160207)— (X’F5160220 - X’F5170007)— (X’F5170009 - X’F517003F)— (X’F5170048 - X’F5170207)— (X’F5170220 - X’F5170FFB)— (X’F5171100 - X’F5171DFF)— (X’F5172000 - X’F51D0017)— (X’F51D0020 - X’F51D003B)— (X’F5800000 - X’F6400023)— (X’F6400028 - X’F640002B)— (X’F6400040 - X’F640007F)

CDMA Channel Unit Third Generation (CCU-3G). Invalid address range:

EXTIF_STATUS Host CSM0 only — (X’F51D0018 - X’F51D001F)

EXT_INT_CLEAR Host CSM0 addresses to the CSM1 end —(X’F51D003C - X’F57FFFFF)

Jupiter register reserved — (X’F6400024 - X’F6400027)

Jupiter registers which clears on read —(X’F640002C - X’F640003F)

Jupiter registers reserved — (X’F6400080 - X’F67FFFFF)

Last 4 bytes of DPRAM — (X’F401FFFC - X’F401FFFF)

Saturn registers not supported — (X’F0000080 - X’F00000FF)

Saturn registers not supported — (X’F0000130 - X’F1BFFFFF)




Saturn UART registers — (X’F1C00130 - X’F1FFFFFF)

Saturn registers not supported — (X’F2000270 - X’F23FFFFF)

Saturn registers not supported — (X’F2800200 - X’F2BFFFFF)

Saturn registers not supported — (X’F2C00020 - X’F3FFFFFF)

Unreadable PNGEN CSM0 only — (X’F510020C - X’F510021F)

Unreadable AIRAM CSM0 only — (X’F5110008 - X’F511000F)

Unreadable AIRAM CSM0 only — (X’F5110208 - X’F511021F)

Unreadable SEARCHER CSM0 only —(X’F5120208 - X’F512021F)

Unreadable DEMOD CSM0 only — (X’F5130208 - X’F513021F)

Unreadable DEMOD CSM0 only — (X’F5133000 - X’F513FFFF)

FRAME_STATUS_BUFFER CSM0 only —(X’F5140000 - X’F5140003)

Unreadable DEINT CSM0 only — (X’F5140150 - X’F51401FF)

Unreadable DEINT CSM0 only — (X’F514020C - X’F514021F)

Unreadable VD CSM0 only — (X’F5150208 - X’F515021F)

Unreadable TD registers CSM0 only —(X’F5160000 - X’F5160003)

Unreadable TD registers CSM0 only —(X’F5160208 - X’F516021F)

Unreadable TX_FIFO_RESET CSM0 —(X’F5170008 - X’F5170008)

Unreadable TX_PARITY_STATUS CSM0 only —(X’F5170040 - X’F5170047)

Unreadable TX registers CSM0 only —(X’F5170208 - X’F517021F)

Unreadable TX_FRAME_CNTL/DATA CSM0 —(X’F5170FFC - X’F51710FF)

Unreadable TX registers CSM0 only —(X’F5171E00 - X’F5171FFF)

CDMA Cluster Controller Second Generation (CCC-2G) Valid address range:

Angel interrupt — (X’800007FF - X’800007FF)

DUSART 0 — (X’40000000 - X’4000001C)

DUSART 1 — (X’40200000 - X’4020001C)

Empty region after EPROM — (X’E0040000 - X’FFFFFFFF)

Hardware reset strobe — (X’70000000 - X’7FFFFFFF)




HCU 1 DPRAM — (X’C0017FFE - X’C0017FFF)

HCU 1 bypass enable interrupt reset —(X’C0018003 - X’C0018004)













Internal cache, bad access interrupt CLR, series port 0 —(X’00000000 - X’2FFFFFFF)

SPYDER-T interrupt clear — (X’60100000 - X’60100000)

Timer0clr — (X’60300000 - X’60300000)

Write violation interrupt clear — (X’60200000 - X’60200000)

CDMA Channel Unit Second Generation (CCU-2G) Valid address range:

CCU x DPRAM — (X’E0007FFE - X’E0007FFF)

EPROM — (X’F0000000 - X’FFFFFFFF)

Internal cache — (X’00000000 - X’000003FF)

Series II only. Valid address range:

Cell Site Controller (CSC) CSC Core Board Non-Volatile Memory(NVM) — (X’0 - X’1FFFF)

CSC Core Board Random Access Memory (RAM) —(X’4000000 - X’5FFFFFF)

CSC Core Board Static Random Access Memory (SRAM) —(X’FFE00000 - X’FFFFFFFF)




Communications Processor Interface (CPI) NVM —(X’0 - X’1FFFF)

Communications Processor (CP) SRAM — (X’40000 - X’7FFFF)

CPI Dual Port RAM — (X’80000 - X’81FF7)

Locate Radio — (X’0 - X’FFFF)

Setup Radio — (X’0 - X’FFFF)

AMPS Radio Channel Unit (RCU) or Time Division Multiple Access(TDMA) Digital Radio Unit (DRU) — (X’0 - X’FFFF)

TDMA Enhanced Digital Radio Unit (EDRU) —(X’4000000 - X’41FFFFF)

AMPS Test Unit — (X’0 - X’FFFF)

TDMA Test Unit — (X’0 - X’FFFF)

d = Number of bytes (Length [L]) (1-160) of data to be dumped. The default is1. If a Series II LC, SU, RA, RTU, or TRTU is involved, the maximumnumber of bytes is 64. If a Series II CCC or CE is involved, the maximumnumber of bytes is 160.


4. SYSTEM RESPONSE




PF = Printout Follows. Request has been executed; output message(s) willfollow.



5. REFERENCES

IM/OM References:

Input MessagesNone.




Output MessagesDUMP-CELL-EVENT

Other References:








Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP CELL AUTH FAIL

ID............. DUMP:CELL-AUTH-FAILRELEASE ....... 25.0 and laterTYPE .......... Input

1. PURPOSE

Request the Backhaul Connection Server (BHCS) to generate a list of the Base TransceiverStations (BTSs) that have failed authentication.

2. FORMAT

DUMP:CELL,AUTH,FAIL


See Purpose.

4. SYSTEM RESPONSE

NG = No Good. Request could not be granted; explanation follows.

PF = Printout Follows. Message was received. A DUMP-CELL-AUTH-FAILoutput message will follow with a list of the BTSs which have failedauthentication.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesDUMP-CELL-AUTH-FAIL



Issue 28 DUMP:CELL-AUTH-FAIL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP CELL AUTH FAIL August 2005



DUMP:CELL-AUTH-FAIL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP CELL MRA

ID............. DUMP:CELL-MRARELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Determines which input actions (if any) are waiting in Maintenance Request Administrator(MRA) at a cell.

2. FORMAT

DUMP:CELL a:MRA [CLASS b]!




4. SYSTEM RESPONSE

IP = In Progress. Request has been sent to the cell site; output message(s) willfollow.






5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesDUMP-CELL-MRA

Other References:



Issue 28 DUMP:CELL-MRA-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP CELL MRA August 2005



DUMP:CELL-MRA-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP CELL MRAQ

ID............. DUMP:CELL-MRAQRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Determines which devices (if any) are being diagnosed at a cell, and which devices (if any)are waiting to be diagnosed in the high- and low-priority test equipment queues.

2. FORMAT

DUMP:CELL a:MRAQ [ CLASS b]!


a = Cell site number (1-600).• A single cell site.• A range (1-32).• A list of cell sites separated by commas and enclosed in parentheses.


4. SYSTEM RESPONSE







5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesDUMP-CELL-MRAQ


Issue 28 DUMP:CELL-MRAQ-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP CELL MRAQ August 2005

Other References:



DUMP:CELL-MRAQ-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP CELL PLM

ID............. DUMP:CELL-PLMRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Dumps a Power Level Measurement (PLM) for a cell. The first format is for Series II,Flexent Modular Cells and Flexent CDMA Distributed Base Station (CDBS) Cells, andFlexent Modular Cell 4.0. The second format is for Flexent Microcells.

NOTE: This command only applies to cells with CDMA equipment.

2. FORMAT

[1] DUMP:CELL a; PLM b; CARRIER c, SECTOR d!

[2] DUMP:CELL a, MICRO e; PLM b; CARRIER c!


a = Cell site number (1-600):• A single cell site.• A range (maximum number of cells in range is 32).• A list of cell sites separated by commas and enclosed in parentheses.

b = Power Level Measurement (PLM) mode:9 — Total Output Power on Forward Link.10 — Noise Rise (Median and Delta Rise)

c = Code Division Multiple Access (CDMA) cell carrier number:

1-10 — for pre-R22.0 cells.1-18 — for R22.0 and later cells.

d = CDMA sector number (0-6).

e = Flexent Microcell number (1-6).

4. SYSTEM RESPONSE

?E = Error.


NG = No Good. May be the following reason:

— The CDMA FER/PLM Feature is not active

5. REFERENCES

IM/OM References:

Input MessagesVER:PLM


Issue 28 DUMP:CELL-PLM-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP CELL PLM August 2005

Output MessagesDUMP-CELL-PLM



DUMP:CELL-PLM-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP CELL SG

ID............. DUMP:CELL-SGRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Requests an aggregate service measurement count for each voice radio of appropriatetechnology type on the specified cell, server group, and antenna face.

NOTE: This input command works for Series II cell sites only.

2. FORMAT

DUMP:CELL a,SG b,ANT c;d [ CLASS e]!


a = A single cell site number (1-600).

b = Server group number (0-1).

c = Antenna face number (0-6), specified in one of the following ways:• A single antenna face number.• A hyphen-separated range with a starting antenna face number and an

ending antenna face number (example: 2-5).0 = Omni1 = Alpha2 = Beta3 = Gamma4 = Delta5 = Epsilon6 = Zeta

d = Type of service measurement count to be requested:

HOBIT — Hand-off Based on Interference (HOBIT) for Time DivisionMultiple Access (TDMA). This option applies only to TDMAradios.

INLA — Interference Look Ahead. This option applies to AMPS andTDMA radios.


4. SYSTEM RESPONSE


NG = No Good. Specified parameters are out of range or other necessaryconditions for message execution were not met.



Issue 28 DUMP:CELL-SG-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP CELL SG August 2005

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesREPT-CELL-SG

Other References:



DUMP:CELL-SG-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP FILE ALL

ID............. DUMP:FILE-ALLRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Dumps the contents of an ASCII file.

2. FORMAT

DUMP:FILE:ALL, FN "a" [,OPL b]!


a = Pathname of the file. See User Guidelines for definitions of pathname andfile.

NOTE: Dumps of directories and/or non-ASCII files may produce unpredictableoutput.

b = Number of segments output, specified in decimal. Default is 10 segments.Maximum number of segments is 999. Each segment has a maximum size of1000 bytes or 20 lines.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by the DUMP-FILE-ALL output message.

5. REFERENCES

IM/OM References:

Input MessagesDUMP:FILE-DATADUMP:FILE-PARTL

Output MessagesDUMP-FILE-ALLDUMP-FILE-PARTL

Other References:




Issue 28 DUMP:FILE-ALL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP FILE ALL August 2005



DUMP:FILE-ALL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP FILE DATA

ID............. DUMP:FILE-DATARELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Dumps the contents of a file in the specified format. If no format is given, the dump isprinted in octal.

2. FORMAT

DUMP:FILE:DATA, FN "a" [,b] [,OPL c]!


a = Pathname of the file. The pathname is a list of the names of each directoryleading to the file, and ends with the name of the specific file. Each namebegins with a slash, and the entire pathname is enclosed in quotation marks.For example, /usr/a1/ssw/test means that /usr/a1/ssw representsthe list of directory names and /test represents the file name.

b = Specifies the output format (default = octal):

C — Interprets bytes in ASCII notation.D — Interprets words in decimal notation.O — Interprets words in octal notation.X — Interprets words in hexadecimal notation.

c = Number of segments to be output: specified in decimal. Default is 10segments. Maximum number is 999. Each segment has a maximum size of1000 bytes or 20 lines.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by DUMP-FILE-PARTL output message.

5. REFERENCES

IM/OM References:

Input MessagesDUMP:FILE-ALLDUMP:FILE-PARTL

Output MessagesDUMP-FILE-ALLDUMP-FILE-PARTL

Other References:



Issue 28 DUMP:FILE-DATA-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP FILE DATA August 2005



DUMP:FILE-DATA-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP FILE FORMAT

ID............. DUMP:FILE-FORMATRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Dumps the contents of a file in the specified format. If no format is given, the dump isprinted in octal.

2. FORMAT

DUMP:FILE:FORMAT, FN "a" [,b] [,OPL c]!


a = Pathname of the file. The pathname is a list of the names of each directoryleading to the file, and ends with the name of the specific file. Each namebegins with a slash, and the entire pathname is enclosed in quotation marks.For example, usr/a1/ssw/test means that /usr/a1/ssw/ representsthe list of directory names and /test represents the file name.

b = Specifies the output format (default = octal):

C - Interprets bytes in ASCII notation.D - Interprets words in decimal notation.O - Interprets words in octal notation.X - Interprets words in hexadecimal notation.

c = Number of segments output: specified in decimal. Default is 10 segments.Maximum is 999. Each segment has a maximum size of 1000 bytes or 20lines.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by the DUMP-FILE-FORMAT output message.

5. REFERENCES

IM/OM References:

Input MessagesDUMP:FILE-ALLDUMP:FILE-PARTL

Output MessagesDUMP-FILE-ALLDUMP-FILE-FORMATDUMP-FILE-PARTL


Issue 28 DUMP:FILE-FORMAT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP FILE FORMAT August 2005

Other References:




DUMP:FILE-FORMAT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP FILE PARTL

ID............. DUMP:FILE-PARTLRELEASE ....... 13.0 and laterTYPE .......... Input

1. PURPOSE

Prints one or more lines of an ASCII file.

NOTE: Specifying a non-ASCII file may produce unpredictable output.

2. FORMAT

DUMP:FILE:PARTL, FN "a", LINE b[-c][,OPL=d]!


a = Pathname of the file. See User Guidelines for the definition of a pathname.

b = Line number to be printed or first line of a range, specified in decimal. If theline number specified (limited to 1 through 131072 inclusive) is larger thanthe number of lines in the file, the last line of the file is assumed.

c = Last line number of a range (limited to 1 through 131072 inclusive). Iflarger then the number of lines in the file, the last line of the file is assumed.

d = Output is printed in segments to prevent a large dump from dominating theROP. The OPL option specifies the decimal number of segments to output(1-999) with the default at 10 segments. Each printed segment will containup to 800 bytes, which includes formatting space and line numbering.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by the DUMP-FILE-PARTL output message.

5. REFERENCES

IM/OM References:

Input MessagesDUMP:FILE-ALLDUMP:FILE-DATA

Output MessagesDUMP-FILE-ALLDUMP-FILE-FORMATDUMP-FILE-PARTL


Issue 28 DUMP:FILE-PARTL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP FILE PARTL August 2005

Other References:




DUMP:FILE-PARTL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP ISR

ID............. DUMP:ISRRELEASE ....... 17.0 and laterTYPE .......... Input

1. PURPOSE

Dump the contents of the ISDN User Part (ISUP) Register (ISR) associated with the inputISR index and Call Processing/Database Node (CDN). The contents of the specified ISRwill be output without disturbing any active calls even if the ISR is actually involved in anactive call.

This message is useful to technical support in the resolution of anomalous call scenarios.

Note that this input command only applies when an ISUP call is being serviced by aTraditional/Reduced Footprint Digital Cellular Switch (DCS); it does not apply to the5ESS DCS.

2. FORMAT

DUMP:ISR a,CDN b!


a = Single index number of the ISR to be dumped (0-1299).

b = Single CDN number of the ISR to be dumped (1-24).

4. SYSTEM RESPONSE


PF = Printout Follows. Message was received; dump output for the ISRspecified follows.

5. REFERENCES

IM/OM References:

Input MessagesINIT:ISR-CDN

Output MessagesAUD-CDN-OSDS-N-E-N



Issue 28 DUMP:ISR-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP ISR August 2005



DUMP:ISR-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP KERN

ID............. DUMP:KERNRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Dumps the contents of a specified range of virtual addresses in computer kernel as animmediate action. The range is specified by two addresses or an address and a length. Thelength defaults to a value of 1.

If only one address is given, indirect addressing may be specified. In this case, the firstoffset listed is added to the content of the given address and the result is interpreted as avirtual address. The number of offsets specified defines the length of the chain of virtualaddresses to be accessed in this way before accessing the desired range of dump locations.For example, a single offset with value 0 uses the virtual address found in the locationspecified in the DUMP:KERN input message for the dump location.

2. FORMAT

DUMP:KERN {a-b a [,OFF c][, {L NL} d]}!


a = Starting virtual byte address of the dump, in decimal, octal, or hexadecimal.

b = Ending virtual byte address of the dump.

c = A single offset or list of up to five offsets. Omission of the keyword impliesno indirect addressing.

L d = The length of the dump, assumed to be in bytes. The maximum is 128 bytes.The default is 1, unless a range is explicitly specified. The actual range ofaddresses to be dumped will be rounded out to word address boundaries.

NL d = Indicator that the operation should use the locations beginning d lower thanthe calculated address and ending at the address. The locations are used inascending order. Usage and limitations are the same as for the L option.

4. SYSTEM RESPONSE







Issue 28 DUMP:KERN-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP KERN August 2005


PF = Printout Follows. Followed by a WHEN output message.


5. REFERENCES

IM/OM References:

Input MessagesDUMP:PIDDUMP:PMEMDUMP:REGDUMP:UIDWHEN:PIDWHEN:UID

Output MessagesDUMP-ADDRWHEN-PIDWHEN-UID

Other References:



DUMP:KERN-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP MCR

ID............. DUMP:MCRRELEASE ....... 17.0 and laterTYPE .......... Input

1. PURPOSE

Dumps the contents of the Mobile Call Register (MCR) associated with the input MCRnumber, also known as the Executive Cellular Processor (ECP) Call Identification (ECID),and Call Processing/Database Node (CDN). The contents of the specified MCR will beoutput, whether or not the MCR is actually involved in an active call, without disturbingany active calls.

If the specified MCR is linked to other MCRs as part of an active call, those linked MCRswill also be output.

The data will be output via a CPHISTORY formatted MCR dump, (which is a special caseuse of the CDN audit error message) with an "ERROR" number of "99".

This message is useful to technical support in the resolution of anomalous call scenarios.

NOTE: A CP 977 assert occurs as a result of using this command.

2. FORMAT

DUMP:MCR a,CDN b!


a = Single ECID number of the MCR to be dumped (0-65535).

b = Single CDN number of the MCR to be dumped (1-24).

4. SYSTEM RESPONSE


PF = Printout Follows. Message was received; CPHISTORY output for theMCR specified follows.

5. REFERENCES

IM/OM References:

Input MessagesINIT:MCR-CDN


Issue 28 DUMP:MCR-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP MCR August 2005

Output MessagesREPT-CDN-OSDS-AUDREPT-CDN-OSDS-DATAREPT-CDN-OSDS-NAME



DUMP:MCR-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP MHD BLOCK

ID............. DUMP:MHD-BLOCKRELEASE ....... 8.0 and laterTYPE .......... Input


**WARNING**Do not input this request at the same time as another request for the sameMHD, because errors due to resource limitations may occur.

1. PURPOSE

Dumps the contents of a specified single disk block or a range of blocks, in hexadecimal.One disk block contains 512 bytes.

The Moving Head Disk (MHD) does not have to be in the active state for this command towork.

2. FORMAT

DUMP:MHD a;BLOCK b[-c][:DEST {ROP "d"}]!



b = Disk block offset from the start of the disk, specified in decimal(0-2147483646). May be the first block of a range of blocks. Block 0 is thefirst block of a disk.

c = Last block of a range of blocks (0-2147483646).

DEST = Destination of the output. Default is the inputing Teletypewriter (TTY).

ROP = Read Only Printer (ROP). A maximum of five disk blocks can be directed tothe ROP by a single input command.

d = Pathname of a file to receive the data. See User Guidelines for the definitionof pathname. There is no limit on the number of disk blocks that can bedirected to a file by a single input command.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by the DUMP-MHD-BLOCK output message.

5. REFERENCES

IM/OM References:

Input MessagesNone.


Issue 28 DUMP:MHD-BLOCK-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP MHD BLOCK August 2005

Output MessagesDUMP-MHD-BLOCK



DUMP:MHD-BLOCK-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP MHD DEFECT

ID............. DUMP:MHD-DEFECTRELEASE ....... 13.0 and laterTYPE .......... Input

1. PURPOSE

Dump defect management information for a Moving Head Disk (MHD).

This command is used to read the defect tables from an MHD. The tables specify thelocation of media defects. This information is used by the MHD’s controller to map arounddefective areas on the media.

— This command should only be used for disk drives that support defect management;otherwise, the command will abort.

— The MHD does not have to be in the active state to execute this command.

If no options are specified, the COMB (combined) defect table will be output.

2. FORMAT

DUMP:MHD a;DEFECT [ ;FN "b" { : [ [COMB] [,MFGR] ] ALL } ]!


MHD = Identifies the MHD used in the message.

a = MHD member number (0-255).

FN = Indicates the user is specifying a file to which the MFGR defect table will bewritten.

For Storage Module Device (SMD) MHD, the file is formatted in a way thatcan be used as input to the LOAD:MHD command.

For Small Computer System Interface (SCSI) MHD, the contents of the file ispurely informational and cannot be used as input to the LOAD:MHDcommand.

b = Full pathname that specifies the file to be written.

COMB = Requests the combined defect table.

For SMD MHD, this table represents the defect list currently being used by theMHD’s controller to map around defects. The COMB defect table can beupdated by using the INIT:MHD command with the NEW option. The updatecopies the current MFGR defect table to the COMB defect table.

For SCSI MHD, this table represents the GROWN defect list and contains onlythose defects added by the user. This list, in conjunction with the PRIMARYdefect list (see MFGR option below), is used by the MHD’s controller to maparound media defects.


Issue 28 DUMP:MHD-DEFECT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP MHD DEFECT August 2005

MFGR = Requests the manufacturer’s defect table.

For SMD MHD, this table represents the original defects supplied by the diskdrive vendor and defects added by the user. This table is used to update theCOMB defect table.

For SCSI MHD, this table represents the PRIMARY defect list and contains onlythose defects supplied by the disk drive vendor. This list, in conjunction withthe GROWN defect list (see COMB option above), is used by the MHD’s controllerto map around media defects.

ALL = Requests both defect tables: COMB and MFGR.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by the DUMP-MHD-DEF output message.

5. REFERENCES

IM/OM References:

Input MessagesLOAD:MHD-DEFECTINIT:MHD

Output MessagesDUMP-MHD-DEFECT

Other References:



DUMP:MHD-DEFECT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP MHD VTOC

ID............. DUMP:MHD-VTOCRELEASE ....... 8.0 and laterTYPE .......... Input


**WARNING**Do not input this request at the same time as another DUMP:MHD orVFY:MHD request, because errors may occur.

1. PURPOSE

Formats and prints the contents of a disk pack’s Volume Table Of Contents (VTOC). TheMoving Head Disk (MHD) does not have to be in the active state for this command towork.

2. FORMAT

DUMP:MHD a; VTOC [:SORT {B P}]!



SORT = Specifies the sort algorithm to be used in formatting the output data.

B — Sort by ascending disk block addresses (default).P — Sort by ascending logical partition numbers.

NOTE: Disk packs used in the UNIX RTR operating system must have a VTOCstarting at block number zero.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by the DUMP-MHD-VTOC output message.

5. REFERENCES

IM/OM References:

Input MessagesVFY:MHD

Output MessagesDUMP-MHD-VTOC



Issue 28 DUMP:MHD-VTOC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP MHD VTOC August 2005



DUMP:MHD-VTOC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP PID

ID............. DUMP:PIDRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Dumps the contents of the specified range of virtual addresses in computer main memoryin the address space of the process with the specified process identifier. This messagecannot be used as an action associated with a breakpoint. The range is specified by twoaddresses or as one address and a length. The length defaults to a value of 1.

If only one address is given, indirect addressing may be specified. In this case, the firstoffset listed is added to the value of the given address and the result is interpreted asanother address. The number of offsets specified defines the length of the chain of virtualaddresses to be accessed in this way before accessing the desired range of dump locations.For example, a single offset with value 0 uses the virtual address found in the locationspecified in the DUMP:PID input message for the dump location.

2. FORMAT

DUMP:PID a, ADDR {b-c b [, OFF d][, {L NL} e]} [; WORD] !


a = Process ID of the target process.

b = Starting virtual address of the dump in decimal, octal, or hexadecimalnotation. Assumed to be a byte address unless the WORD option is used.

c = Ending virtual address of the dump. Assumed to be a byte address unlessthe WORD option is used.

d = A single offset or list of up to five offsets. Omission of the keyword impliesno indirect addressing. Offsets are in bytes unless the WORD option is used.

L e = The length of the dump, assumed to be in bytes unless the WORD option isused. Maximum 128 bytes or 32 words. Default=1, unless a range isexplicitly specified. The actual range of addresses to be dumped will berounded out to word address boundaries.

NL e = Used to indicate that the operation should use the locations beginning elower than the calculated address and ending at the address. The locationsare used in ascending order. Usage and limitations are the same as for theL option.

WORD = Indicates that all addresses, offsets, and lengths are to be interpreted in termsof words including addresses derived in address chains. If this option isomitted, they are assumed to be byte values.


Issue 28 DUMP:PID-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP PID August 2005

4. SYSTEM RESPONSE


INVALID KEYWORD — Command not allowed in a WHEN action list.






NG = No Good. The PID is for a process for which dumps are not permitted.

PF = Printout Follows. Followed by the DUMP-PID output message.


5. REFERENCES

IM/OM References:

Input MessagesDUMP:ADDRDUMP:PMEMDUMP:REGDUMP:UIDOP:ST-PROCESSOP:UMEM

Output MessagesDUMP-PID

Other References:



DUMP:PID-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP PMEM

ID............. DUMP:PMEMRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Dumps the contents of a specified range of physical addresses in computer main memory.The range is specified by two addresses or by one address and an optional byte lengthcount. The default length is 4 bytes.

The output will contain formatted fullwords. If the addresses specified did not describe aset of fullwords, the addresses will be rounded out to fullword boundaries. For example,physical memory addresses X’4041-X’405D (in hexadecimal) would be treated ashexadecimal numbers X’4040-X’405F.

This message may be used either as an immediate command or in the action list of a WHEN.

2. FORMAT

DUMP:PMEM {a-b a [,{L NL} c]} {/ !}


a = Starting (if L is used) or ending (if NL is used) physical address dump indecimal, octal, or hexadecimal notation. Value will be rounded down to afullword address.

b = Ending physical address for dump in decimal, octal, or hexadecimal notation.Value will be rounded up to the next fullword boundary.

L c = Indicator that the ending address should be calculated by adding the bytelength c to the starting address a and then rounding up to the next fullwordboundary.

NL c = Byte length used to calculate the starting address. The byte length c issubtracted from the ending address a and then rounded down to a fullwordboundary. The address a is rounded up to the next fullword boundary and isused as the ending address.

4. SYSTEM RESPONSE

?I = Identification Field contains an error. General syntax error, or:



PF = Printout Follows. Followed by the DUMP-PMEM output message.



Issue 28 DUMP:PMEM-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP PMEM August 2005

5. REFERENCES

IM/OM References:

Input MessagesDUMP:PIDDUMP:UIDWHEN:PIDWHEN:UID

Output MessagesDUMP-PMEM

Other References:



DUMP:PMEM-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP REG

ID............. DUMP:REGRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Dumps the contents of one or more registers, either as an immediate action, or as an actionassociated with a breakpoint.

This message can also be used to dump an address range in main memory (by specifying asingle register and offsets), but only if the message is part of an action list for a WHENmessage.

If offsets are specified, the first offset is added to the contents of the specified register andthe result is interpreted as a virtual address. The number of offsets specified defines thelength of the chain of virtual addresses to be accessed in this way before accessing thedesired range of dump locations. For example, a single offset with value 0 uses the virtualaddress found in the register for the memory dump location.

NOTE: Offsets can only be used if the DUMP:REG message is used as an action associatedwith a breakpoint, since that defines a process address space for memoryaddressing.

2. FORMAT

DUMP:REG a [,OFF b] [,{L NL} c] [;WORD] {/ !}


a = Single register name or a list of registers to be dumped. See User Guidelinesfor instructions on entering a list of names. A maximum of five registers maybe listed.

The following is a list of acceptable register names:AP, ATBBGR, ATBPSW, ATBQ, ATBSAR, ATBSCR, ATBSDR, BGR,CDR, DSTBUS, ER, FP, HG, HM, HSR, IB, IM, IS, ONES, PA,PPR, PSW, R0, R1, R10, R11, R2, R3, R4, R5, R6, R7, R8,R9, RTC, SAR, SBR0, SBR1, SBR2, SBR3, SBR4, SBR5, SBR6,SBR7, SCR, SCRATCH0, SCRATCH1, SDR, SIR, SM, SP, SRCBUS,SSR, SYSBASE, T0, T1, T2, T3, T4, T5, T6, T7, TIMERS,TOPIS, UINT0, UINT1, UINT2, UINT3, UINTER.

b = Offset. Omission of the keyword implies no indirect addressing. Offsets areonly allowed if one register is specified. Offsets are in bytes unless the WORDoption is used.

L c = The length of the dump, in bytes unless the WORD option is used. Themaximum is 128 bytes or 32 words for memory dumps and 4 bytes forregister dumps. The default is 1 unless a range is explicitly specified. Theactual range of addresses to be dumped will be rounded out to word addressboundaries.


Issue 28 DUMP:REG-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP REG August 2005

NL c = Indicator that the operation should use the locations beginning c lower thanthe calculated address and ending at the address. The locations are used inascending order. Usage and limitations are the same as for the L option.

WORD = Indicates that all addresses, offsets, and lengths are to be interpreted in termsof words, including addresses derived in address chains. If this option isomitted they are assumed to be byte values.

4. SYSTEM RESPONSE


— EXTRA KEYWORDIndirection not allowed except as an action of a WHEN.

— INCONSISTENT DATA (REG LIST + OFF)No indirection permitted with more than one register listed.



— INPUT ERROR (REG COUNT)Too many registers listed.



NG = No Good.

— BAD REG NAME

PF = Printout Follows. Followed by the DUMP-REG output message.


5. REFERENCES

IM/OM References:

Input MessagesDUMP:ADDRDUMP:PIDDUMP:PMEMDUMP:UIDOP:UMEMWHEN:PIDWHEN:UID

Output MessagesDUMP-REG


DUMP:REG-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP REG

Other References:



Issue 28 DUMP:REG-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP REG August 2005



DUMP:REG-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP RUTIL

ID............. DUMP:RUTILRELEASE ....... 7.0 and laterTYPE .......... Input



1. PURPOSE

Dumps the contents of memory at the given node.

Format 1: memory at the address range given at the specified node.

Format 2: memory from the given address for the specified length.

2. FORMAT

[1] DUMP:RUTIL(a, b), {AP NP}; ADDR (X’c, X’d) !

[2] DUMP:RUTIL(a, b), {AP NP}; ADDR X’c, { L NL } e [;WORD] !




c = Start address of the dump in hexadecimal.

If L is given, then c is taken to be the beginning address to dump.

If NL is given, then c is the end address of the dump; the start address iscalculated by end address minus total number of bytes to dump.

d = End address of the dump in hexadecimal.

e = Length of the dump in decimal; if WORD is given, then e is the number offour-byte words to dump, otherwise e is the number of bytes to dump.

4. SYSTEM RESPONSE

An attempt will be made to dump the contents of the specified address at the given node.Currently a maximum length of 468 bytes is allowed for a single dump operation.

All addresses are to be provided in hexadecimal, for example, X’FE3402.

All lengths are to be provided in decimal, for example, 75.

A formatted output of the node’s memory contents will be printed.


Issue 28 DUMP:RUTIL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP RUTIL August 2005

5. REFERENCES

IM/OM References:

Input MessagesLOAD:RUTIL

Output MessagesDUMP-RUTIL

Other References:

401-661-045 Common Network Interface (CNI) Ring Maintenance


DUMP:RUTIL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP SMEAS

ID............. DUMP:SMEASRELEASE ....... 15.0 and laterTYPE .......... Input

1. PURPOSE

Dumps signaling system measurements from measurement history files in a nonpagedformat.

2. FORMAT

DUMP:SMEAS (a [, a]); HIST b; {SLK (c, d [, e, f]) NODE (c, d [, e, f]) CHN g[-g] LS h[-h] CLUSTER i[-i]} [: DEST j]!


a = Measurement identification in at most 12 characters.

b = Name of the history file. The history file name must agree with one of thenames in the HFDT table:

C30M — Current 30 minute data file.CDAY — Current day data file.CHRM — Current hour data file.L15M — Last 15 minute data file.L30M — Last 30 minute data file.LDAY — Last day data file.LHRM — Last hour data file.LPM — Last period measurement structure.

c = Group number (0-63), starting group number.

d = Member number (1-15), starting member number.

e = Group number (0-63), ending group number.

f = Member number (1-15), ending member number.

g = Starting and ending channel number.

h = Starting and ending link set number.

i = Starting and ending cluster number.

j = Destination class.

4. SYSTEM RESPONSE

User may specify as many measurement names as the command will allow. In addition tothose measurement names listed in the References section, these values will also bepermitted: ALL7LINK, ALLCHANNEL, ALLCLUSTER ALLIUN, ALLLINKSET,ALLOFFICE, ALLRPC, and FACPERF.

If ALLOFFICE is specified, then all of the nonzero office measurements will be output.


Issue 28 DUMP:SMEAS-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP SMEAS August 2005

If ALL7LINK is specified, all of the nonzero link measurements for the CCS7 link(s)specified will be output.

ALLIUN, ALLRPC, ALLCHANNEL, ALLLINKSET, and ALLCLUSTER will be handledsimilarly.

If FACPERF is specified, then the following nonzero CCS7 link facility relatedmeasurements will be output: CRCER, ERSEC, NCCLALOC, NCCMXOSY, NCCTOTRNCCTOTRT RABTER, and SEVERSEC.

5. REFERENCES

IM/OM References:

Input MessagesOP:OUTCLS

Output MessagesDUMP-SMEAS

Output AppendicesAppendix 10

Other References:None


DUMP:SMEAS-2 Issue 28


MEASUREMENTS RECOGNIZED BY THE COMMAND

IMS/CNI OFFICE MEASUREMENTS - DO NOT REQUIRE OPTIONS (SLK, ...)

ABOFL ABOFS ALSRO ALSROT BLKG0BLKG1 CINIT0 CINIT1 CINIT2 CINIT3CINIT4 CINIT0T CINIT1T CINIT2T CINIT3TCINIT4T CLFA CLFAT CLFSP CLFSPTCOFFDIF CUTOCUWDS CUTOCUMSG GTTPERFD GTTUNBCGTTUNNT GTTUNBT IMOFFDI INITBT INITBTTINIT1A INIT1AT INIT1B INIT1BT INIT0INIT2 INIT3 INIT4 INIT0T INIT2TINIT3T INIT4T MRBADRTG MRNIAU MRNIAUTMRRING MRSBCO7 MRSNTO7 MSINVSIO NOCMGNOCMGT ORMSUOCT ORIGMSUS RDWN RDWNTRGCNFG RGCNFGT RNIMN RNIMNT RTGAUDFLSCR SCRERPRO SCRERUA SCRERUATY SCRERUNESCRGTR SCRLNN SCRLSS SCRNATL SCSRTRSCSRTX SCSSTR SCSSTX SCUDSX SPISPSPISPT SPISPPO SPISPPOT SPIA SPIATSPIAPO SPIAPOT SRNIAU SRNIAUT THRSWMSUTRMSUOCT TSMSUOCT TRMDMSUS

MEASUREMENTS THAT REQUIRE NODE OPTION

ARRATT ARRFLR ARREXR BLK0 BLK1BUFSW CONFG CONFGT CUTORWDS CUTORMSGDMAFLT DMAMISS IDLE IFBPTER0 IFBPTER1ILLEGAL IMNPDIF INBOF IPFMTER0 IPFMTER1IPSM0 IPSM1 IUNOVLD0 IUNOVLD1 IUNOVLD2MINTRA MRINTCH MRNRING MRRGQ0 MRRGQ1MXRG0 MXRG1 NPPTER OOSCFG OOSCFGTOOSAU OOSAUT OOSMN OOSMNT PANICSPIOFLT PTERTE RACER0 RACER1 RCOPTER0RCOPTER1 RDFMTER0 RDFMTER1 RDINHER0 RDINHER1RIPTER0 RIPTER1 RPCBOF RRBOVFLW0 RRBOVFLW1RRBOVFLW2 RRBOVFLW3 RRBOVFLW1T RRBOVFLW2T RRBOVFLW3TRSTTRMT RTMSGSRC RTOCUWDS RTOCUMSG SFPTER0SFPTER1 TDPRCNG0 TDPRCNG1 TDPRCNG2 WRRGQ0WRRGQ1 WSMER0 WSMER1 WTFMTER0 WTFMTER1WXRG0 WXRG1




MEASUREMENTS THAT REQUIRE CHN OPTION

RBOF RBOFBLK RINTCH WBOFN WBOFNLWBOFO

MEASUREMENTS THAT REQUIRE LS OPTION

ALSR ALSRT CLF CLFT LSMSUTRANLSMSURECD LSOCTRECD LSOCTRETRN LSOCTTRAN

MEASUREMENTS THAT REQUIRE CLUSTER OPTION

RTESETUN RTESETUNT

CCS7 MEASUREMENTS THAT REQUIRE SLK OPTION

BYMSUX BYMSUR BYRX BYR BYSRBYSX BYX CRCER ERSEC L6MGXV0L6MGRV0 L6MGXV1 L6MGRV1 L6MGXV2 L6MGRV2L6MGXV3 L6MGRV3 L6MGXV4 L6MGRV4 L6MGXV5L6MGRV5 L6MGXV6 L6MGRV6 L6MGXV7 L6MGRV7L6SUPRV0 L6SUPRV1 L6SUPRV2 L6SUPRV3 L6SUPRV4L6SUPRV5 L6SUPRV6 L6SUPRV7 L6SUPXV0 L6SUPXV1L6SUPXV2 L6SUPXV3 L6SUPXV4 L6SUPXV5 L6SUPXV6L6SUPXV7 L7ACO L7ACOFE L7ACONE L7ACOTEL7AFLT L7BOLR L7BOLRT L7DIF L7EMRL7EMRPO L7EMRPOT L7EMRT L7FLALIGN L7FLDL7FLDT L7LCDIS1X L7LCDIS2X L7LCDIS3X L7LCDIS1XTL7LCDIS2XT L7LCDIS3XT L7LCON1X L7LCON2X L7LCON3XL7LCON1XT L7LCON2XT L7LCON3XT L7MCOFE L7MCONEL7MFLT L7MGSX L7MGSR L7POR L7PORTMGANSRV0 MGANSRV1 MGANSRV2 MGANSRV3 MGANSRV4MGANSRV5 MGANSRV6 MGANSRV7 MGANSXV0 MGANSXV1MGANSXV2 MGANSXV3 MGANSXV4 MGANSXV5 MGANSXV6MGANSXV7 MGIAMRV0 MGIAMRV1 MGIAMRV2 MGIAMRV3MGIAMRV4 MGIAMRV5 MGIAMRV6 MGIAMRV7 MGIAMXV0MGIAMXV1 MGIAMXV2 MGIAMXV3 MGIAMXV4 MGIAMXV5MGIAMXV6 MGIAMXV7 MGMSUX MGMSUR NACRNACRTE SPI SPIPOC SPIPOT SPIT




CCS7 MEASUREMENTS THAT REQUIRE SLK OPTION (Contd)

BYRXTE CRCERTE DCFLABN DCFLABNT DCFLHWPDCFLHWPT DCFLSWP DCFLSWPT DCFLXDA DCFLXDATDCFLXDC DCFLXDCT DCFLXER DCFLXERT DRBSYLNKDRPEMSG1 DRPEMSG2 DRPEMSG3 DRP7MSG1 DRP7MSG2DRP7MSG3 ERSECTE FORRX FORRXBY LINKDLAYL7BADRTG L7BOFRT L7BYTO3B L7LNKACTT L7MRPBCL7MRPNT L7MSINVSIO L7ORIGMSUS L7ORMSUOCT L7POXL7POXT L7RBFOC L7RTGAUD L7THRSWMSU L7TRMDMSUSL7TRMSUOCT L7TSMSUOCT L7XBFLOOK L7XBFOC MSG7LOOPMSUDISC0 MSUDISC1 MSUDISC2 MSUSAMPL NBSYLINKNCCLALOC NCCMXOSY NCCTOTR NCCTOTRT OCCUPMSURABT RABTER SC7REASATT SC7REASSCSFL SC7SEGATTSC7SEGSCSFL SC7R SC7RERPRO SC7RERUA SC7RERUATYSC7RERUNE SC7RGTR SC7RLNN SC7RLSS SC7RNATLSC7UDSX SEVERSEC SQL TPROCOTG UNVLZPEAKOCC







Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP TRK DATA

ID............. DUMP:TRK-DATARELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Requests logged trunk test data. The data will appear in tabular form on the Read OnlyPrinter (ROP) with explanatory headers.

Test result data will be tabulated from the time specified to the present.

2. FORMAT

DUMP:TRK;DATA {XMIT MISC}:a ,b [ CLASS c] [;UCL] [;DCS d] [;DCS d,TRKGRP e]!


XMIT = This log contains transmission test data for completed but failing trunk tests.

MISC = This log contains data concerning trunk tests that terminated abnormally.

a = Month (01-12).

b = Day (01-31).

UCL = Retrieve data from the specific date requested.


DCS = Search for a specific Digital Cellular Switch (DCS) number. DCS must beused in conjunction with a TRKGRP number.

d = DCS number (01-16).

TRKGRP = Search for a specific trunk group within a specified DCS. Must be precededby the DCS option.

e = Trunk group number:


4. SYSTEM RESPONSE

IP = In Progress. Request has been received by UNIX -level process TMlog forhandling. Output message will follow.

NG = No Good. Necessary condition for execution of request not met.



Issue 28 DUMP:TRK-DATA-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP TRK DATA August 2005

5. REFERENCES

IM/OM References:

Input MessagesNone.


Other References:



DUMP:TRK-DATA-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP UID

ID............. DUMP:UIDRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Dumps the contents of a specified range of virtual addresses in computer main memory inthe address space of the process with the specified utility identifier. This message cannotbe used as an action associated with a breakpoint.

The range is specified by two addresses or by one address and a length. The lengthdefaults to a value of 1.

If only one address is given, indirect addressing may be specified. In this case, the firstoffset is added to the value of the given address and the result is interpreted as a virtualaddress. The number of offsets specified defines the length of the chain of virtualaddresses to be accessed in this way before accessing the desired range of dump locations.For example, a single offset with value 0 uses the virtual address found in the locationspecified in the DUMP:UID message for the dump location.

2. FORMAT

DUMP:UID a, ADDR {b-c b [,OFF d] [,{L NL} e]} [;WORD] !


a = Utility ID number of the target process.

b = Starting virtual address of the dump in decimal, binary, octal, or hexadecimalnotation. Assumed to be a byte address unless the WORD option is used.

c = Ending virtual address of dump. Assumed to be a byte address unless theWORD option is used.

d = Offset. Omission of the keyword implies no indirect addressing. Offsets arein bytes unless the WORD option is used.

L e = The length of the dump, in bytes unless the WORD option is used. Themaximum is 128 bytes or 32 words. The default is 1, unless a range isexplicitly specified. The actual range of addresses to be dumped will berounded out to word address boundaries.

NL e = Indicator that the operation should use the locations beginning e lower thanthe calculated address and ending at the address. The locations are used inascending order. Usage and limitations are the same as for the L option.

WORD = Indicates that all addresses, offsets, and lengths are to be interpreted in termsof words including addresses derived in address chains. If this option isomitted they are assumed to be byte values.


Issue 28 DUMP:UID-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP UID August 2005

4. SYSTEM RESPONSE

?A = Action field contains an error. One of these messages may follow:

INVALID KEYWORD Message not allowed in a WHEN action list.


— EXTRA KEYWORD (UID)UID is not valid in a WHEN action list.




— RANGE ERROR (UID)Utility ID is out of range.

NG = No Good. The UID is for a process for which dumps are not permitted.

PF = Printout Follows. Followed by the DUMP-UID output message.


5. REFERENCES

IM/OM References:

Input MessagesDUMP:ADDRDUMP:PIDDUMP:PMEMDUMP:REGOP:UMEM

Output MessagesDUMP-UID

Other References:



DUMP:UID-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 DUMP UVAR

ID............. DUMP:UVARRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Dumps the contents of one or more computer Generic Access Package (GRASP) utilityvariables either as an immediate message or as an action associated with a breakpoint.Utility variables are used to store data temporarily.

This message can also be used to dump an address range in main memory (by specifying asingle utility variable and offsets) but only if the message is part of the action list for aWHEN message.

If offsets are specified, the first offset is added to the value of the contents of the utilityvariable and the result is interpreted as a virtual address. The number of offsets specifieddefines the length of the chain of virtual addresses to be accessed in this way beforeaccessing the desired range of dump locations. For example, a single offset with value 0uses the virtual address found in the utility variable for the dump location.

NOTE: Offsets can only be used if the DUMP:UVAR message is used as an actionassociated with a breakpoint, since that defines a process address space formemory addressing.

2. FORMAT

DUMP:UVAR a [,OFF b][,{L NL}c][;WORD]{/ !}


a = Utility variable(s) (1-50) to be dumped. See User Guidelines for instructionson entering a list of variable numbers. A maximum of five utility variablesmay be listed.

b = A single offset or list of up to five offsets. Omission of the keyword impliesno indirect addressing. Offsets are in bytes unless the WORD option is used.

L c = The length of the dump, assumed to be in bytes unless the WORD option isused. The maximum is 128 bytes or 32 words for memory dumps, 4 bytes or1 word for utility variable dumps. The default is 1 unless a range is explicitlyspecified. The actual range of addresses to be dumped is rounded out toword address boundaries.

NL c = Used to indicate that the operation should use the locations beginning clower than the calculated address and ending at the address. The locationsare used in ascending order. Usage and limitations are the same as for the Loption.

WORD = Indicates that all addresses, offsets, and lengths are to be interpreted aswords including addresses derived in address chains. If this option isomitted they are assumed to be byte values.


Issue 28 DUMP:UVAR-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksDUMP UVAR August 2005

4. SYSTEM RESPONSE


— EXTRA KEYWORD (OFF)Indirection not allowed except as action of a WHEN.

— INCONSISTENT DATA (UVAR LIST + OFF)No indirection permitted with more than one utility variable listed.



— INPUT ERROR (UVAR COUNT)Too many utility variables listed.

— RANGE ERROR (L OR NL)Length specified too long or zero.



PF = Printout Follows. Followed by the DUMP-UVAR output message.


5. REFERENCES

IM/OM References:

Input MessagesDUMP:ADDRDUMP:PIDDUMP:PMEMDUMP:REGDUMP:UIDOP:UMEMWHEN:PIDWHEN:UID

Output MessagesDUMP-UVAR

Other References:



DUMP:UVAR-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 END WHEN

ID............. END:WHENRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Marks the end of a list of computer Generic Access Package (GRASP) messages to beperformed when a specified breakpoint condition exists.

2. FORMAT

END:WHEN!


See Purpose.

4. SYSTEM RESPONSE

?A = Action field contains an error. Only allowed in a WHEN action list.

?I = Identification Field contains an error. General syntax error or:

— PUNCTUATION ERRORExclamation point was expected.

PF = Printout Follows. Followed by a WHEN output message.


5. REFERENCES

IM/OM References:

Input MessagesOP:UMEMWHEN:PIDWHEN:UID

Output MessagesWHEN-PIDWHEN-UID

Other References:



Issue 28 END:WHEN-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEND WHEN August 2005



END:WHEN-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX CU

ID............. EX:CURELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Requests that a computer Control Unit (CU) be exercised in an interactive diagnosticmode.

Format 1: Starts the interactive diagnostic mode.

Format 2: Pauses or suspends the diagnostic execution at a specified statement numberwithin a diagnostic phase.

Format 3: Puts the diagnostic in a loop between the specified statement numbers.

Format 4: Steps the diagnostic and suspends at the specified statement number. It issimilar to Format 2, but also prints the command buffer contents being passedto the diagnostic driver.

Format 5: Can only be used with main store diagnostic phase 95 or 96. It executes themain store diagnostic phase with user-supplied address range, refresh rate,number of failures to be collected, data pattern (phase 95), words per array tocopy (phase 96), and refresh parity check time.

Format 6: Stops the looping started by EX:LOOP.

NOTE: To use Formats 2 through 6, first execute Format 1.

2. FORMAT

[1] EX:CU a,CH=b[;[RAW][,UCL]]:PH c[,TLP][,{DFC IOP} d]!

[2] EX:PAUSE;CU a,CH=b:ST e!

[3] EX:LOOP;CU a,CH=b:ST f-g!

[4] EX:STEP;CU a:ST e !

[5] EX:LDPARM;CU a,MASC a[:[SA h][,EA i][,REF j][,FNUM k][,PAT l][,WPA m][,TIME n]]!

[6] EX:STOP;CU a,b!



b = Unit type and member number of the subunit beneath the CU. Valid subunitnames and member numbers are listed in the Member Numbers Appendix,APP:MEM-NUM-D, Table D.


Issue 28 EX:CU-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX CU August 2005

RAW = Print all the diagnostic failures. Default is to print the first five failures.

UCL = Execute unconditionally.


c = Execute the specified phase

NOTE: The phase will not be executed until subsequent commands fromFormats 2 through 5 are input.

TLP = Execute the Trouble Locating Procedure (TLP) at the conclusion of thediagnostic. This process generates a list of suspected faulty equipment.

NOTE: It is not recommended that the TLP and UCL parameters bespecified together, as it may produce an improper TLP listing.

d = Member number of the DFC (0-7), IOP (0-15) or Ring Peripheral ControllerNode (RPCN) to be used as a helper unit. When a helper unit is not required,the specified helper unit is ignored. When a helper unit is required but thespecified helper unit is inappropriate or not available, the helper unitdependent tests are skipped.

e = Statement number that is the target of the action. This statement is notexecuted.

f = Lower statement boundary of an exercise loop.

g = Upper statement boundary of an exercise loop.

h = Starting address for the MAS exercise, in hexadecimal notation. Default is 0.

i = End address for the MAS exercise, in hexadecimal notation. Default is allequipped memory in controller under test.

j = Memory refresh rate in decimal.For 3B21D default is 16 ms. Possible values are 16, 18, 20, 22, 24,26, 28, 30 ms.

k = Number of failures for which data is to be collected. Default is 100.

l = 32-bit data pattern used in the MAS exercise (phase 95), in hexadecimalnotation. Default is Oxffffffff.

m = Number of words per memory array to copy from the online CU, inhexadecimal notation (phase 96). Default is all words in each array.

n = Duration of time, in seconds, for which refresh data parity checks should berun to scan for errors in the MASC under test (phase 96). Default = 34seconds for TN14 MASAs, 68 seconds for TN28, TN56, TN2012 MASAs, 136seconds for TN56 MASAs with either an extended main memory or verylarge main memory features, 136 seconds for TN2012 MASAs with anextended main memory feature, or 272 seconds for TN2012 MASAs with avery large main memory feature.This parameter is not used for 3B21D.


EX:CU-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX CU

4. SYSTEM RESPONSE




— MISSING DATAData required for the statement keyword was not found on the inputline.


— RANGE ERRORNot a valid value for the statement parameter.







PF = Printout Follows. Followed by the EX CU output message.


5. REFERENCES

IM/OM References:

Input MessagesDGN:CUEX:LOOPSTOP:DMQ


Issue 28 EX:CU-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX CU August 2005

Output MessagesANALY-TLPFILEDGN-CUEX-CU

Input AppendicesAPP:MEM-NUM-D

Other References:



EX:CU-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX DCI

ID............. EX:DCIRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Exercises a Dual Serial Channel/Computer Interconnect (DCI) in an interactive diagnosticmode.




Format 4: Steps the diagnostic and suspends at the specified statement number. It issimilar to Format 2.



2. FORMAT

[1] EX:DCI a [;[RAW] [,UCL]]: PH b [,TLP] !

[2] EX:PAUSE; DCI a: ST d !

[3] EX:LOOP; DCI a: ST e-f !

[4] EX:STEP; DCI a: ST d !

[5] EX:STOP; DCI a !



RAW = Prints all the diagnostic failures. Default is the first five failures.

UCL = Executes unconditionally.


PH = Executes the specified phase.

b = Number of the phase to be executed.

NOTE: The phase will not be executed until subsequent messages from Formats 2through 5 are input.


Issue 28 EX:DCI-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX DCI August 2005


NOTE: It is not recommended that the TLP and UCL parameters be specifiedtogether, as it may produce an improper TLP listing.

d = Statement number that is the target of the action. This statement is notexecuted.

e = Lower statement boundary of an exercise loop.

f = Upper statement boundary of an exercise loop.

4. SYSTEM RESPONSE












PF = Printout Follows. Followed by the EX-DCI output message.


5. REFERENCES

IM/OM References:

Input MessagesDGN:DCIEX:LOOPSTOP:DMQ


EX:DCI-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX DCI

Output MessagesANALY-TLPFILEDGN-DCIEX-DCI

Other References:



Issue 28 EX:DCI-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX DCI August 2005



EX:DCI-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX DFC

ID............. EX:DFCRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Exercises a Disk File Controller (DFC) in an interactive diagnostic mode.







2. FORMAT

[1] EX:DFC a [;[RAW] [,UCL]]: PH b [,TLP] [,CU c]!

[2] EX:PAUSE; DFC a: ST d !

[3] EX:LOOP; DFC a: ST e-f !

[4] EX:STEP; DFC a: ST d !

[5] EX:STOP;DFC a !



RAW = Prints all the diagnostic failures. Default is to print the first five failures.



b = Executes the specified phase.




Issue 28 EX:DFC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX DFC August 2005

NOTE: It is not recommended that the TLP and UCL parameters be specifiedtogether as it may produce an improper TLP listing.

c = (0 or 1) Member number of the CU helper unit. When a helper unit is notrequired, the specified helper unit is not used. When a helper unit isrequired but the specified helper unit is inappropriate or unavailable, thehelper unit dependent tests are skipped. The off-line CU is required as ahelper unit when demand phase 15 is executed.


d = Statement number that is target of the action. This statement is not executed.



4. SYSTEM RESPONSE












PF = Printout Follows. Followed by the EX-DFC output message.



EX:DFC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX DFC

5. REFERENCES

IM/OM References:

Input MessagesDGN:DFCEX:LOOPSTOP:DMQ

Output MessagesANALY-TLPFILEDGN-DFCEX-DFC

Other References:



Issue 28 EX:DFC-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX DFC August 2005



EX:DFC-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX DUIC

ID............. EX:DUICRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Exercises a Direct User Interface Controller (DUIC) in an interactive diagnostic mode.







2. FORMAT

[1] EX:DUIC a [;[RAW] [,UCL]]: PH b [,TLP] [,CONT]!

[2] EX:PAUSE; DUIC a: ST c!

[3] EX:LOOP; DUIC a: ST d-e!

[4] EX:STEP; DUIC a: ST c!

[5] EX:STOP; DUIC a!











Issue 28 EX:DUIC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX DUIC August 2005

c = Statement number that is the target of the action. This statement is notexecuted.

d = Lower statement boundary of an exercise loop.

e = Upper statement boundary of an exercise loop.

4. SYSTEM RESPONSE












PF = Printout Follows. Followed by the EX-DUIC output message.


5. REFERENCES

IM/OM References:

Input MessagesDGN:DUICEX:LOOPSTOP:DMQ

Output MessagesANALY-TLPFILEDGN-DUICEX-DUIC


EX:DUIC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX DUIC

Other References:



Issue 28 EX:DUIC-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX DUIC August 2005



EX:DUIC-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX HSDC

ID............. EX:HSDCRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Exercises a High-Speed Synchronous Data Link Controller (HSDC) in an interactivediagnostic mode.







2. FORMAT

[1] EX:HSDC a [;[RAW] [,UCL]]: PH b [,TLP]!

[2] EX:PAUSE; HSDC a: ST c!

[3] EX:LOOP; HSDC a: ST d-e!

[4] EX:STEP; HSDC a: ST c!

[5] EX:STOP; HSDC a!












Issue 28 EX:HSDC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX HSDC August 2005




4. SYSTEM RESPONSE












PF = Printout Follows. Followed by the EX-HSDC output message.


5. REFERENCES

IM/OM References:

Input MessagesDGN:HSDCEX:LOOPSTOP:DMQ


EX:HSDC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX HSDC

Output MessagesANALY-TLPFILEDGN-HSDCEX-HSDC

Other References:



Issue 28 EX:HSDC-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX HSDC August 2005



EX:HSDC-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX IOP

ID............. EX:IOPRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Exercises an Input/Output Processor (IOP) in an interactive diagnostic mode.







2. FORMAT

[1] EX:IOP a [;[RAW] [,UCL]]: PH b [,TLP] [,CU c]!

[2] EX:PAUSE; IOP a: ST d !

[3] EX:LOOP; IOP a: ST e-f !

[4] EX:STEP; IOP a: ST d !

[5] EX:STOP; IOP a !


a = Member number (0-15). Number (0-1).








Issue 28 EX:IOP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX IOP August 2005



c = Member number of the CU helper unit (0-1). When a helper unit is notrequired, the specified helper unit is not used. When a helper unit isrequired but the specified unit is inappropriate or unavailable, the helperunit dependent tests are skipped. The off-line CU is required as a helper unitwhen demand phase 15 is executed.





4. SYSTEM RESPONSE












PF = Printout Follows. Followed by the EX-IOP output message.



EX:IOP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX IOP

5. REFERENCES

IM/OM References:

Input MessagesDGN:IOPEX:LOOPSTOP:DMQ

Output MessagesANALY-TLPFILEDGN-IOPEX-IOP

Other References:



Issue 28 EX:IOP-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX IOP August 2005



EX:IOP-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX LDPARM

ID............. EX:LDPARMRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Inputs user-supplied parameters to main store phases 95 and 96.

NOTE: To use this input command, first invoke the interactive diagnostics. For example:

EX:CU a,MASC b:ph c!

This format can only be used with main store diagnostic phase 95 or 96. It executes theMain Store (MAS) diagnostic phase with user-supplied address range, refresh rate,number of failures to be collated, data pattern (phase 95), words per array to copy (phase96), and refresh parity check time (phase 96).

2. FORMAT

EX:LDPARM;CU a,MASC b[:[SA h][,EA i][,REF j][,FNUM k][,PAT l][,WPA m][,TIME n]]!



b = Member number of the Main Store Controller (MASC) beneath the CU (0-1).

c = Executes the specified phase.

h = Starting address for the MAS exercise, in hexadecimal notation. Default is 0.

i = End address for the MAS exercise, in hexadecimal notation. Default is allequipped memory in controller under test.

j = Memory refresh rate used in the MAS exercise, in decimal. Default is 4 ms.Possible values are 2, 4, 6, 8, 10, 12, 14, 16, 32, 36, 40, 44, 48, 52, 56,or 60 ms. Memory devices are guaranteed to work at a refresh rate of 4 msor less when the memory device case temperature is between 0°C and 85°C.

k = Number of failures for which data is to be collected. Default is 100.

l = 32-bit data pattern used in the MAS exercise (phase 95), in hexadecimalnotation. Default is 0xffffffff.

m = Number of words per memory array to copy from the on-line CU, inhexadecimal notation (phase 96). Default is all words in each array.

n = Duration of time, in seconds, for which refresh data parity checks should berun to scan for errors in the MASC under test (phase 96). Default is 34seconds for TN14 MASAs, 68 seconds for TN28, TN56, TN2012 MASAs,136 seconds for TN56 MASAs with either extended main memory or verylarge main memory features, 136 seconds for TN2012 MASAs with extendedmain memory feature, or 272 seconds for TN2012 MASAs with very largemain memory feature.


Issue 28 EX:LDPARM-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX LDPARM August 2005

4. SYSTEM RESPONSE












PF = Printout Follows. Followed by the EX-LDPARM output message.


5. REFERENCES

IM/OM References:

Input MessagesDGN:CUEX:CUSTOP:DMQ

Output MessagesANALY-TLPFILEDGN-CUEX-CUEX-LDPARM

Other References:



EX:LDPARM-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX LN

ID............. EX:LNRELEASE ....... 7.0 and laterTYPE .......... Input

1. PURPOSE

Exercises a Link Node (LN) in an interactive diagnostic mode.





Format 5: Stops the looping started by the EX:LOOP input command.

2. FORMAT

[1] EX:LNx y :PH a!

[2] EX:PAUSE;LNx y :ST b!

[3] EX:LOOP;LNx y :ST c-d!

[4] EX:STEP;LNx y :ST b!

[5] EX:STOP;LNx y!


x = A Ring Node (RN) group number (00-63) with explicit leading zero forgroup numbers less than 10.

y = The node’s position in the RN group (1-15).

a = Specifies the number of the phase to be executed.

NOTE: The phase will not be executed until subsequent commands fromFormats 2-5 are input.

b = Statement number that is the target of the action. This statement is notexecuted.

c-d = Statement boundaries for the loop command.

4. SYSTEM RESPONSE

Two sequential system actions are performed in response to the input command ofFormat 1.

1. The LN is removed from service following the rules for the RMV:LN input message.

2. If the resultant LN major state is either OOS, GROW, OFL, or UNAV, an attempt is madeto isolate the LN (for other major states, the diagnostic is aborted by DIAMON). When


Issue 28 EX:LN-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX LN August 2005

the system is ready to accept subsequent interactive commands of Formats 2-5, itresponds with an "EX: STARTED AT STATEMENT 1" output message.

Additional sequential system actions are then performed in response to the inputcommands of Formats 2-5.

3. The specified diagnostic phase is run.

4. If the LN was in the active ring prior to the start of the diagnostics and wassuccessfully isolated (in 2 above), an attempt is made to include the LN back into theactive ring at the conclusion of the diagnostic execution. Otherwise, the node is leftin its original ring configuration state.

NOTE: The LN remains in the OOS, GROW, OFL, or UNAV state.

5. REFERENCES

IM/OM References:

Input MessagesDGN:LNSTOP:DMQ

Output MessagesDGN-LNEX-LN

Other References:




EX:LN-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX LOOP

ID............. EX:LOOPRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Performs a specified group of diagnostic tasks repeatedly.


EX:a,[,b];ph c!

This format puts the diagnostic in a loop between the specified statement numbers.

2. FORMAT

EX:LOOP;a[,b]:ST f-g!


a = Unit type and member number of the unit on which interactive diagnosticswas started. Valid unit names and member numbers are listed in theMember Numbers Appendix, APP:MEM-NUM-C, Table C.

b = Unit type and member number of the subunit, if any. Valid subunit namesand member numbers are listed in the Member Numbers Appendix,APP:MEM-NUM-D, Table D.


f = Statement lower boundary of an exercise loop.

g = Statement upper boundary of an exercise loop.

4. SYSTEM RESPONSE









Issue 28 EX:LOOP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX LOOP August 2005





PF = Printout Follows. Followed by the EX-LOOP output message.


5. REFERENCES

IM/OM References:

Input MessagesEX:CUEX:DCIEX:DFCEX:DUICEX:HSDCEX:IOPEX:MHDEX:MTCEX:MTTYCEX:PAUSEEX:SCSDCEX:SDLCEX:STEPEX:STOPEX:TTYCSTOP:DMQ

Output MessagesANALY-TLPFILEEX-LOOP


Other References:



EX:LOOP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX MHD

ID............. EX:MHDRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Exercises a Moving Head Disk (MHD) in an interactive diagnostic mode.







2. FORMAT

[1] EX:MHD a[;[RAW][,UCL]]:PH b[,TLP]!

[2] EX:PAUSE;MHD a:ST c!

[3] EX:LOOP;MHD a:ST d-e!

[4] EX:STEP;MHD a:ST c!

[5] EX:STOP;MHD a!



RAW = Print all the diagnostic failures. Default is the first five failures.



b = Execute the specified phase.



NOTE: It is not recommended that the TLP and UCL parameters be specifiedtogether, as it may produce an improper TLP listing


Issue 28 EX:MHD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX MHD August 2005




4. SYSTEM RESPONSE












PF = Printout Follows. Followed by the EX-MHD output message.


5. REFERENCES

IM/OM References:

Input MessagesDGN:MHDEX:LOOPSTOP:DMQ


EX:MHD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX MHD

Output MessagesANALY-TLPFILEDGN-MHDEX-MHD

Other References:



Issue 28 EX:MHD-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX MHD August 2005



EX:MHD-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX MT

ID............. EX:MTRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Exercises a Magnetic Tape (MT) in an interactive diagnostic mode.




Format 4: Steps the diagnostic and suspends at the specified statement number.



2. FORMAT

[1] EX:MT a[;[RAW][,UCL]]:Ph b[,TLP]!

[2] EX:PAUSE;MT a:ST c!

[3] EX:LOOP;MT a:ST d-e!

[4] EX:STEP;MT a:ST c!

[5] EX:STOP;MT a!



RAW = Print all diagnostic failures. Default is the first five failures.




NOTE: The phase will not be executed until subsequent messages from Formats2 through 5 are input.


NOTE: It is not recommended that the TLP and UCL parameters be specifiedtogether, because it may produce an improper TLP listing.



Issue 28 EX:MT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX MT August 2005



4. SYSTEM RESPONSE












PF = Printout Follows. Followed by EX-MT output message.


5. REFERENCES

IM/OM References:

Input MessagesDGN:MTEX:LOOP

Output MessagesANALY-TLPFILEDGN-MTEX-MT


EX:MT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX MT

Other References:



Issue 28 EX:MT-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX MT August 2005



EX:MT-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX MTC

ID............. EX:MTCRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Exercises a Magnetic Tape Controller (MTC) in an interactive diagnostic mode.







2. FORMAT

[1] EX:MTC a [;[RAW] [,UCL]]:PH b[,TLP][,MT c]!

[2] EX:PAUSE;MTC a:ST d!

[3] EX:LOOP;MTC a:ST e-f!

[4] EX:STEP;MTC a:ST e!

[5] EX:STOP;MTC a!












Issue 28 EX:MTC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX MTC August 2005

c = Member number of the magnetic tape device that is to be used as a helperunit (0-255). When a helper unit is not required, the specified helper unit isignored. When a helper unit is required but the specified helper unit isinappropriate or unavailable, the helper unit dependent tests are skipped.




4. SYSTEM RESPONSE












PF = Printout Follows. Followed by the EX-MTC output message.


5. REFERENCES

IM/OM References:

Input MessagesDGN:MTCEX:LOOPSTOP:DMQ


EX:MTC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX MTC

Output MessagesANALY-TLPFILEDGN-MTCEX-MTC

Other References:



Issue 28 EX:MTC-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX MTC August 2005



EX:MTC-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX MTTYC

ID............. EX:MTTYCRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Exercises a Maintenance Teletypewriter Controller (MTTYC) in an interactive diagnosticmode.







2. FORMAT

[1] EX:MTTYC a[;[RAW][,UCL]]:PH b[,TLP]!

[2] EX:PAUSE;MTTYC a:ST c!

[3] EX:LOOP;MTTYC a:ST d-e!

[4] EX:STEP;MTTYC a:ST c!

[5] EX:STOP;MTTYC a!



RAW = Print all the diagnostic failures. The default is to print the first five failures.


b = Executes the specified phase.

NOTES: 1. This option does not override forced early terminations.

2. The phase will not be executed until subsequent messages fromFormats 2 through 5 are input.


NOTE: The TLP and UCL parameters should not be used together, as additional testresults may adversely affect the TLP listing.


Issue 28 EX:MTTYC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX MTTYC August 2005




4. SYSTEM RESPONSE












PF = Printout Follows. Followed by the EX-MTTYC output message.


5. REFERENCES

IM/OM References:

Input MessagesDGN:MTTYCEX:LOOPSTOP:DMQ

Output MessagesANALY-TLPFILEDGN-MTTYCEX-MTTYC


EX:MTTYC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX MTTYC

Other References:



Issue 28 EX:MTTYC-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX MTTYC August 2005



EX:MTTYC-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX PAUSE

ID............. EX:PAUSERELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Runs to a specified point in a diagnostic command, and then stops.


EX:a,[,b];ph c!

This format pauses or suspends the diagnostic execution at a specified statement numberwithin a diagnostic phase.

2. FORMAT

EX:PAUSE;a[,b]:ST e!






4. SYSTEM RESPONSE









Issue 28 EX:PAUSE-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX PAUSE August 2005





PF = Printout Follows. Followed by the EX-PAUSE output message.


5. REFERENCES

IM/OM References:

Input MessagesEX:CUEX:DCIEX:DFCEX:DUICEX:HSDCEX:IOPEX:MHDEX:MTCEX:MTTYCEX:SCSDCEX:SDLCEX:STEPEX:TTYCSTOP:DMQ

Output MessagesANALY-TLPFILEEX-PAUSE


Other References:



EX:PAUSE-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX RPCN

ID............. EX:RPCNRELEASE ....... 7.0 and laterTYPE .......... Input

1. PURPOSE

Exercises a Ring Peripheral Controller Node (RPCN) in an interactive diagnostic mode.




Format 4: Steps the diagnostic and suspends at the specified statement number. It issimilar to Format 2 but also dumps the command buffer contents being passedto the IMS driver. The contents are sent to the teletypewriter.


2. FORMAT

[1] EX:RPCNx 0:PH a [,b]!

[2] EX:PAUSE;RPCNx 0:ST c!

[3] EX:LOOP;RPCNx 0:ST d-e!

[4] EX:STEP;RPCNx 0:ST c!

[5] EX:STOP;RPCNx 0!


x = A Ring Node (RN) group number (00-63) with explicit leading zero forgroup numbers less than 10.

a = Specifies the number of the phase to be executed.

NOTE: The phase will not be executed until subsequent commands fromFormats 2 through 5 are input.

b = Helper unit to be used with this diagnostic request.


d-e = Statement boundaries for the loop command.

4. SYSTEM RESPONSE

Two sequential system actions are performed in response to the input command ofFormat 1.

1. The RPCN is removed from service following the rules for the RMV:RPCN inputmessage.


Issue 28 EX:RPCN-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX RPCN August 2005

2. If the resultant RPCN major state is any of OOS, GROW, OFL, or UNAV, an attemptis made to isolate the RPCN (for other major states, the diagnostic is aborted byDIAMON). When the system is ready to accept subsequent interactive commands ofFormats 2 through 5, it responds with an "EX: STARTED AT STATEMENT 1"output message.

Additional sequential system actions are then performed in response to the inputcommands of Formats 2 through 5.

1. The specified diagnostic phase is run.

2. If the RPCN was in the active ring prior to the start of the diagnostics and wassuccessfully isolated (in 2 above), an attempt is made to include the RPCN back intothe active ring at the conclusion of the diagnostic execution. Otherwise, the node isleft in its original ring configuration state.

NOTE: The RPCN remains in the OOS, GROW, OFL, or UNAV state.

5. REFERENCES

IM/OM References:

Input MessagesDGN:RPCNSTOP:DMQ

Output MessagesANALY-TLPFILEDGN-RPCNEX-RPCN

Other References:




EX:RPCN-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX SCSDC

ID............. EX:SCSDCRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Exercises a Scanner Signal Distributor Controller (SCSDC) in an interactive diagnosticmode.




Format 4: Steps the diagnostic and suspends at the specified statement number. Thisformat is similar to Format 2.



2. FORMAT

[1] EX:SCSDC a[;[RAW][UCL]]:PH b[,TLP]!

[2] EX:PAUSE;SCSDC a:ST c!

[3] EX:LOOP;SCSDC a:ST d-e!

[4] EX:STEP;SCSDC a:ST c!

[5] EX:STOP;SCSDC a!



RAW = Print all the diagnostic failures. Default is the first five failures.








Issue 28 EX:SCSDC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX SCSDC August 2005


d = Statement lower boundary of an exercise loop.

e = Statement upper boundary of an exercise loop.

4. SYSTEM RESPONSE












PF = Printout Follows. Followed by the EX-SCSDC output message.


5. REFERENCES

IM/OM References:

Input MessagesDGN:SCSDCEX:LOOPSTOP:DMQ


EX:SCSDC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX SCSDC

Output MessagesANALY-TLPFILEDGN-SCSDCEX-SCSDC

Other References:



Issue 28 EX:SCSDC-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX SCSDC August 2005



EX:SCSDC-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX SDLC

ID............. EX:SDLCRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Exercises a Synchronous Data Link Controller (SDLC) in an interactive diagnostic mode.



Format 3: Puts the diagnostic in a loop between the specified statement numbers. Thisformat is similar to Format 2 but also prints the message buffer contents beingpassed to the diagnostic driver.

Format 4: Steps the diagnostic and suspends at the specified statement number. Thisformat is similar to Format 2.



2. FORMAT

[1] EX:SDLC a[;[RAW][,UCL]]:PH b[,TLP]!

[2] EX:PAUSE;SDLC a:ST c!

[3] EX:LOOP;SDLC a:ST d-e!

[4] EX:STEP;SDLC a:ST c!

[5] EX:STOP;SDLC a!









Issue 28 EX:SDLC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX SDLC August 2005




d = Statement lower boundary of an exercise loop.

e = Statement upper boundary of an exercise loop.

4. SYSTEM RESPONSE












PF = Printout Follows. Followed by the EX-SDLC output message.


5. REFERENCES

IM/OM References:

Input MessagesDGN:SDLCEX:LOOPSTOP:DMQ


EX:SDLC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX SDLC

Output MessagesANALY-TLPFILEDGN-SDLCEX-SDLC

Other References:



Issue 28 EX:SDLC-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX SDLC August 2005



EX:SDLC-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX STEP

ID............. EX:STEPRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

This command steps the diagnostic and suspends at the specified statement number. It issimilar to the EX:PAUSE input command, but in the case of a CU diagnostic, it will alsoprint the command buffer contents being passed to the diagnostic driver.


EX:a[,b];ph c!

2. FORMAT

EX:STEP;a[,b]:ST e!






4. SYSTEM RESPONSE


— EXTRA KEYWORD 1Duplicate or extraneous keywords were input.

— INVALID KEYWORD 1The keyword in the stated parameter position is not a valid keyword.

— MISSING DATA 1Data required for the statement keyword was not found on the inputline.

— MISSING KEYWORD 1A required keyword is missing from the input.

— RANGE ERROR 1Not a valid value for the statement parameter.



Issue 28 EX:STEP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX STEP August 2005


— EXTRA KEYWORD 1Duplicate or extraneous keywords were input.

— INVALID KEYWORD 1The keyword in the stated parameter position is not a valid keyword.

— MISSING KEYWORD 1A required keyword is missing from the input.

PF = Printout Follows. Followed by an EX-STEP output message.


5. REFERENCES

IM/OM References:

Input MessagesEX:CUEX:DCIEX:DFCEX:DUICEX:HSDCEX:IOPEX:MHDEX:MTCEX:MTTYCEX:PAUSEEX:SCSDCEX:SDLCEX:TTYCSTOP:DMQ

Output MessagesANALY-TLPFILEEX-STEP


Other References:



EX:STEP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX STOP

ID............. EX:STOPRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Exits from the interactive diagnostics mode. This command stops the looping started byEX:LOOP. This input message only stops the EX:LOOP command.

NOTE: To use this input command, first invoke the interactive diagnostics and theEX:LOOP command. For example:

EX:a[,b];ph c!EX:LOOP;a[,b]:st f-g!

2. FORMAT

EX:STOP;a[,b]!





f = Statement lower boundary of an exercise loop.

g = Statement upper boundary of an exercise loop.

4. SYSTEM RESPONSE









Issue 28 EX:STOP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX STOP August 2005





PF = Printout Follows. Followed by an EX-STEP output message.


5. REFERENCES

IM/OM References:

Input MessagesEX:CUEX:DCIEX:DFCEX:DUICEX:HSDCEX:IOPEX:LOOPEX:MHDEX:MTCEX:MTTYCEX:SCSDCEX:SDLCEX:TTYCSTOP:DMQ

Output MessagesANALY-TLPFILEEX-STEP


Other References:



EX:STOP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX TTYC

ID............. EX:TTYCRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Exercises a Teletypewriter Controller (TTYC).







2. FORMAT

[1] EX:TTYC a[;[RAW][,UCL]]:PH b[,TLP]!

[2] EX:PAUSE;TTYC a:ST c!

[3] EX:LOOP;TTYC a:ST d-e!

[4] EX:STEP;TTYC a:ST c!

[5] EX:STOP;TTYC a!












Issue 28 EX:TTYC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX TTYC August 2005



4. SYSTEM RESPONSE












PF = Printout Follows. Followed by the EX-TTYC output message.


5. REFERENCES

IM/OM References:

Input MessagesDGN:TTYCEX:LOOPSTOP:DMQ

Output MessagesANALY-TLPFILEDGN-TTYCEX-TTYC


EX:TTYC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EX TTYC

Other References:



Issue 28 EX:TTYC-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksEX TTYC August 2005



EX:TTYC-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EXC CELL CDM DS1

ID............. EXC:CELL-CDM-DS1RELEASE ....... 24.0 and laterTYPE .......... Input

1. PURPOSE

Format 1: Obtain the performance measurement data collected by base-station, for eachT1 equipped.

Format 2: Clear the performance measurement data collected by base-station, for each T1equipped.

2. FORMAT

[1] EXC:CELL a, CDM b, DS1 c, REPORT d [,HOUR e]

[2] EXC:CELL a, CDM b, DS1 c, CLEAR


a = Cell site number (1-600). A single cell site number is allowed.

b = CDM number (1-16). A single CDM number is allowed.

c = Digital Signal Level 1 (DS1) number (1-8). Universal Radio Controller 2(URC2) can have up to 8.

d = Report number:

1 — Include only the current 15 minute, number of seconds into currentinterval, and 24 hour aggregate data.

2 — Include only the specified number-of-hour-shift in the past, in 15 minuteincrements.

3 — Include only the 24 hour data in 15 minute increments and 24 houraggregate data. The number of seconds into current 15 minute intervalshall also be specified.

4 — Current measured signal level, alarm, loop mode, state, substate, mode,framing, line coding, signaling, line build out, options, chain, clocksource, clock priority.

e = Hour number for REPORT 2 (1-24).

4. SYSTEM RESPONSE



RL = Retry Later. Data links to the cell site are down.

VERR = Validation Error. Input command has incorrect syntax or range.


Issue 28 EXC:CELL-CDM-DS1-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEXC CELL CDM DS1 August 2005

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesEXC-CDM-CELL-DS1



EXC:CELL-CDM-DS1-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EXC CELL FT

ID............. EXC:CELL-FTRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Begins execution of a functional test at a cell site.

Format 1: All functional tests except single channel functional test. This format is validfor CDMA Series II, Flexent Modular Cell, Flexent Modular Cell 4.0, andFlexent Modular Cell 3.0 / Flexent Modular Cell 4.0 Mixed Frame.

For Flexent Modular Cell 3.0 / Flexent Modular Cell 4.0 Mixed Frame, if theCDMA Test Radio Module (CTRM) is equipped all functional tests for thisformat are applicable; without CTRM equipped only the antenna function testis applicable.

Format 2: All functional tests except single channel functional test. This format is validfor Flexent Microcell.

Format 3: Single channel functional test only. This format is valid for Series II, Flexent

Modular Cell, and Flexent Modular Cell 3.0 / Flexent Modular Cell 4.0Mixed Frame when the CTRM is equipped.

Format 4: Single channel functional test only. This format is valid for CDMA Flexent

Microcell.

Format 5: Receive Gain (RXGAIN) functional test only. This format is valid for CDMAFlexent Modular Cell 4.0.

2. FORMAT

[1] EXC:CELL a, FT c [ CLASS j ]!

[2] EXC:CELL a [, MICRO b ], FT c [, CARRIER e ] [ CLASS j ]!

[3] EXC:CELL a, FT SC d, f, CCU g, CE h [, VORATE i ]!

[4] EXC:CELL a, MICRO b, FT SC, CCU g, CE h [, VORATE i ]!

[5] EXC:CELL a, CDM k, CBR l, FT RXGAIN


a = Cell site number (1-600):• A single cell site.• A range (maximum number of cells in range is 32).• A list of cell sites separated by commas and enclosed in parentheses.

For Format 3 and 4 only a single cell site number is allowed.

b = Flexent Microcell number (1-6):• A single microcell.• A range (For TDMA microcells only).

For Format 4, only a single microcell number is allowed.


Issue 28 EXC:CELL-FT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEXC CELL FT August 2005

NOTE: If not specified, test will be executed on entire range of microcells(For TDMA microcells only).

c = Functional test to be run:

TDMA Series II:

ANT [ d ] — Antenna functional test.

DCCH [ l ] — Digital control channel radio functional test.

l = Radio 0-191 (Single only).

TDMA Flexent Microcell:

ANT [ k ] — Antenna functional test.

DCCH [ k ] — Digital Control Channel (DCCH) functional test.

LC [ k ] — Locate Channel (LC) functional test.

LMT [ l ] — Lightguide Microcell/Modular Cell Transceiver (LMT)functional test.

NOTE: The Received Signal Strength Indicator (RSSI) levelis checked when the LMT functional test isexecuted.

SU [ k ] — Setup (SU) channel functional test.

k = Digital Radio Module Number (1-5):

• A single value.

• A range of values, if b is single value and e is not specified.

• If this field is not specified then the functional test will attempt toexecute on the entire range of microcells specified by b.

l = 0-20 (Single only).

CDMA Series II:


OC [ d ] — Overhead Channel functional test.

PL [ d ]— Pilot Level functional test.

TP [ d ]— Traffic Path functional test. Not valid for ThirdGeneration CDMA (3G) boards.

CDMA Flexent Microcell:

ANT — Antenna functional test.

OC — Overhead Channel functional test.


EXC:CELL-FT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EXC CELL FT

PL — Pilot Level functional test.

TP — Traffic Path functional test. Not valid for 3G boards.

CDMA Flexent Modular Cell and Flexent Modular Cell 3.0 / Flexent

Modular Cell 4.0 Mixed Frame:


NOTE: If sector [ d ] is not specified, the test will be run onall sectors.

OC [ d ] — Overhead Channel functional test.

PL [ d ] — Pilot Level functional test.

TP [ d ] — Traffic Path functional test. Not valid for 3G boards.

Flexent Modular Cell 4.0:


NOTE: If sector [ d ] is not specified, the test will be run onall sectors.

d = Sector number (0-6). Single value, or range if used with Format 1 or 2Functional Test (FT) option.

e = Carrier number (1-2). This option is valid only if option b is specified andsingle value of LC or SU is specified.

f = Flexent identifier:

CCC x where x = 1 - 42. CDMA Cluster Controller (CCC) is applicable toSeries II cells.

CDM x where x = 1 - 16. CDMA Digital Module (CDM) is applicable toFlexent Modular Cells and Flexent Modular Cell 3.0 / Flexent

Modular Cell 4.0 Mixed Frame when the CTRM is equipped.

g = The CDMA Channel Unit (CCU) number:

• (1-7) for Series II.• (1-2) for Flexent Microcell.• (1-6) for Flexent Modular Cell and Flexent Modular Cell 3.0 /

Flexent Modular Cell 4.0 Mixed Frame.

h = The CDMA Channel Element (CE) number:

For 2G cells:

• (0-9) for Series II.• (0-19) for Flexent Microcell and Modular Cell.


Issue 28 EXC:CELL-FT-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksEXC CELL FT August 2005

For 3G cells:

• (0-31) for Series II.• (0-63) for Flexent Microcell, Flexent Modular cell, and

Flexent / Flexent Modular Cell 4.0.

i = Optional Vocoder rate (8 or 13, default is 13).

j = Overriding output message class (151-213). This option may be used onlyif the Virtual System Output Message Routing feature is supported.

k = CDMA Digital Module (CDM) number (1-16).

l = Code Division Multiple Access Baseband Radio (CBR) number (1-6).

4. SYSTEM RESPONSE







5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesEXC-CELLEXC-CELL-ANT-TEST

Other References:



EXC:CELL-FT-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EXC CELL ODPC

ID............. EXC:CELL-ODPCRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Starts an On-Demand Pilot Strength Measurement Message Collection (ODPC) session.Please note that in order to start an ODPC session all of the targeted cells need to be on-line. This "starting" request will be rejected if and only if one or more cells are out-of-service. Furthermore, if at least one cell is going through an initialization the ODPCsession will not be started at the cell level, only at the Operations Maintenance Platform(OMP) level. Therefore, no data will be collected if this happens.

2. FORMAT

EXC:CELL {a a-a (a,a,...) (a,a,...,a-a)}, ODPC[, DUR b, PINT c]!


a = Cell site number (1-600):• A single cell site.• A range, with a maximum number of cells in the range of 20.• A list of up to 20 cells.• A list and range combination, totaling no more than 20 cells.

b = The duration of Pilot Strength Measurement Message (PSMM) collectionsession. It needs to be selectable within a range of 5 to 120 minutes. Thedefault value of the duration shall be 30 minutes if none is specified. Theduration shall be selectable in 5 minute increments.

c = The mobile polling interval for the session. The polling interval, which is thetime between pilot measurement requests to mobiles needs to be selectablewithin a range of 1 to 15 minutes. The default value of the polling intervalwill be 5 minutes if none is specified. The polling interval shall be selectablein 1 minute increments.

4. SYSTEM RESPONSE

NA - TIME OUT = No acknowledgement. The Operations Maintenance Platform (OMP)is not responding. Possibly the On-Demand Pilot Strength MeasurementMessage Collection Daemon (ODPCD) is not active on the OMP.

OK = Good. Request has been received by the Cell(s). Output message willfollow.

5. REFERENCES

IM/OM References:

Input MessagesOP:ODPCSTOP:EXC-ODPC


Issue 28 EXC:CELL-ODPC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEXC CELL ODPC August 2005

Output MessagesEXC-CELL-ODPC



EXC:CELL-ODPC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EXC CELL RTDIAG

ID............. EXC:CELL-RTDIAGRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Executes a routine diagnostic sequence at a cell site.

Format 1: For Series II cells only.

Format 2: For Flexent Microcell cells only.

Format 3: For Flexent Modular Cells, Flexent Modular Cell 4.0, Flexent Modular Cell3.0 / Flexent Modular Cell 4.0 Mixed Frame, and Flexent CDMA DistributedBase Station (CDBS) cells.

2. FORMAT

[1] EXC:CELL a, RTDIAG [ b ] [; RAW ] [ CLASS e ]!

[2] EXC:CELL a, c, RTDIAG [, d ] [; RAW ] [ CLASS e ]!

[3] EXC:CELL a, c, RTDIAG [ CLASS e ]!


a = Cell site number (1-600):• A single cell site• A range (maximum number of cells in range is 32)• A list of cell sites separated by commas and enclosed in parentheses.

b = Devices to be diagnosed. The default is all devices.

Series II cell only:

A decimal number or a range is valid in this field. The default is all devices.

To help in diagnosing a range of equipment, the starting and ending numberfor each range is shown in the following table. For example, to diagnose allVoice Radios, enter 136-327. To diagnose all Setup Radios (assuming thereare two sets of Setup Radios in the configuration) and Voice Radios, enter100-327.

For Series II cell with growth frame before Growth Frame 3 (G3):

1 — Cell Site Controller (CSC) 0, standby side.2 — CSC 1, active side.3 — Clock and Tone (CAT)/ Synchronous Clock and Tone (SCT) 04 — CAT/SCT 15 — CAT/SCT 26 — CAT/SCT 37 — CAT/SCT 48 — CAT/SCT 5


Issue 28 EXC:CELL-RTDIAG-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEXC CELL RTDIAG August 2005

9 — Radio Test Unit (RTU) 0.10 — RTU 1.11 — RTU 2.12 — CDMA Cluster Controller (CCC) 1.

• •• •

41 — CCC 30.42 — Locate radio 0.

• •• •

81 — Locate radio 39.82 — Setup radio 0.

• •• •

89 — Setup radio 7.90 — Setup radio 8 for Directional Setup only

• •• •

117 — Setup radio 35 for Directional Setup only118 — Voice radio 0.

• •• •

309 — Voice radio 191.310 — CCC 1, CDMA Channel Unit (CCU) 1.311 — CCC 1, CCU 2.

• •• •

316 — CCC 1, CCU 7.• •• •

519 — CCC 30, CCU 7.520 — Combination of Bus Interface Unit [BIU]-Baseband Combiner/Radio

[BCR]-Analog Conversion Unit [ACU] (BBA) 1.• •• •

549 — BBA 30.

For Series II cell with growth frame G3 or Rack Mount Growth Frame (Half):

1 — CSC 0, standby side.2 — CSC 1, active side.3 — CAT/SCT 04 — CAT/SCT 15 — CAT/SCT 26 — CAT/SCT 37 — CAT/SCT 48 — CAT/SCT 59 — CAT/SCT 610 — CAT/SCT 711 — RTU 0.


EXC:CELL-RTDIAG-2 Issue 28


12 — RTU 1.13 — RTU 2.14 — CCC 1.

• •• •


• •• •


• •• •


• •• •


• •• •

311 — Voice radio 191.312 — CCC 1, CCU 1.313 — CCC 1, CCU 2.

• •• •

318 — CCC 1, CCU 7.• •• •

521 — CCC 30, CCU 7.522 — BBA 1.

• •• •

551 — BBA 30.

For Series II cell with Growth Frame 4 (G4) or Rack Mount Growth Frame(Full):

1 — CSC 0, standby side.2 — CSC 1, active side.3 — CAT/SCT 04 — CAT/SCT 15 — CAT/SCT 26 — CAT/SCT 37 — CAT/SCT 48 — CAT/SCT 59 — CAT/SCT 610 — CAT/SCT 711 — CAT/SCT 812 — CAT/SCT 9




13 — RTU 0.14 — RTU 1.15 — RTU 2.16 — CCC 1.

• •• •


• •• •


• •• •


• •• •


• •• •


• •• •

326 — CCC 1, CCU 7.• •• •

571 — CCC 36, CCU 7.572 — BBA 1.

• •• •

607 — BBA 36.

For Series II cell with Growth Frame 5 (G5) or Double Density Frame:

1 — CSC 0, standby side.2 — CSC 1, active side.3 — CAT/SCT 04 — CAT/SCT 15 — CAT/SCT 26 — CAT/SCT 37 — CAT/SCT 48 — CAT/SCT 59 — CAT/SCT 610 — CAT/SCT 711 — CAT/SCT 812 — CAT/SCT 9




13 — CAT/SCT 1014 — CAT/SCT 1115 — RTU 0.16 — RTU 1.17 — RTU 2.18 — CCC 1.

• •• •


• •• •


• •• •


• •• •


• •• •


• •• •

334 — CCC 1, CCU 7.• •• •

621 — CCC 42, CCU 7.622 — BBA 1.

• •• •

663 — BBA 42.

c = Flexent identifier:



CDM x where x = 1 - 16. CDMA Digital Module (CDM) is applicable toFlexent Modular cells and Flexent Modular Cell 4.0.

MICRO x where x = 1 - 6. MICRO is applicable to Flexent Microcells. xcan be a range if d is not specified.

d = Cell site unit. If cell unit is not specified than all of the microcell units will bediagnosed.

NOTE: More than one Radio (RA) can be specified.




TDMA Flexent Microcell units only:

AMP — Amplifier.

RA x — RA, Range of radios or single value, x = (1-5).

TRC — TDMA radio controller.

NOTE: For Series II/TDMA: MLAC devices cannot be specified.

NOTE: For Series II/CDMA PCS Minicells, all devices: Only Active orStandby devices in the range specified will be restored. All otherswill be ignored (skipped).

NOTE: For Series II/CDMA PCS Minicells, duplexed devices: For allduplexed devices (those that have an ACT/STBY configuration),the restoral will be rejected if the device’s mate is not either activeor standby (to avoid outages). The request will be rejected if it is forthe active unit of the pair.

NOTE: For Series II/CDMA PCS Minicell all CATs Devices: Active CATswill be requested, but the restoral will always be rejected if the CATis providing CDMA timing, to avoid disrupting CDMA calls. Therequest will be rejected if it is for the active unit of the pair.

NOTE: For Series II/CDMA PCS Minicell, all CCCs Devices: First, CCCsin the specified range that are not supporting special purposechannels will be restored. The CCCs will be restored in increasingnumerical order (that is, from smaller numbers up to largernumbers). Then, CCCs in the specified range that are supportingspecial purpose channels will be restored. These CCCs will berestored in decreasing numerical order (that is, from largernumbers down to smaller ones). Two passes are used to minimizespecial purpose channel migration.

NOTE: For Series II CDMA PCS Minicell, all CCCs Devices: The order inwhich the CCUs in the specified range are restored is designed tominimize special purpose channel migration. The order iscalculated algorithmically at execution time and, therefore, theorder may appear random.

RAW = Include raw data in any diagnostic failure messages (RST-CELL) that may beprinted.





4. SYSTEM RESPONSE







5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesEXC-CELLRST-CELL

Other References:








Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EXC CELL TRKGRP LPBK

ID............. EXC:CELL-TRKGRP-LPBKRELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

Begins a cell initiated trunk group loopback test on an Asynchronous Transfer Mode(ATM) packet pipe.

2. FORMAT

EXC:CELL a, TRKGRPb, MEMBER c;LOOPBACK [,ENH]!


a = Cell site number (1-600):• A single cell site.

b = Trunk group number:


c = Trunk member number:


4. SYSTEM RESPONSE




VERR = Validation error. Input command has incorrect syntax or range.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesEXC-CELL-TRKGRP-LPBK



Issue 28 EXC:CELL-TRKGRP-LPBK-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEXC CELL TRKGRP LPBK August 2005



EXC:CELL-TRKGRP-LPBK-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EXC ENVIR PROC

ID............. EXC:ENVIR-PROCRELEASE ....... 8.0 and laterTYPE .......... Input


**WARNING**Incorrect use of this message can cause unpredictable system damage ordegradation. It should not be used without expert technical assistanceunless it is part of a prescribed procedure.

1. PURPOSE

Executes a task as either a kernel or supervisor process. Although this command canexecute user processes, EXC:ENVIR:UPROC.

2. FORMAT

EXC:ENVIR:PROC,FN "a"!


a = Pathname of the file to be executed. See User Guidelines for a description ofpathname.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by the EXC-ENVIR-PROC output message.

5. REFERENCES

IM/OM References:

Input MessagesEXC:ENVIR-UPROCOP:ST-PROCESS

Output MessagesEXC-ENVIR-PROCREPT-PMGR-ERROR

Other References:




Issue 28 EXC:ENVIR-PROC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEXC ENVIR PROC August 2005



EXC:ENVIR-PROC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EXC ENVIR UPROC

ID............. EXC:ENVIR-UPROCRELEASE ....... 8.0 and laterTYPE .......... Input


**WARNING**Incorrect use of this message can cause unpredictable system damage ordegradation. It should not be used without expert technical assistanceunless it is part of a prescribed procedure.

1. PURPOSE

Executes a task as a user process.

2. FORMAT

EXC:ENVIR:UPROC,FN "a"[,ARGS b][,BKG][,OPL c]!


a = Full pathname of the file to be executed. See the User Guidelines for adescription of pathnames.

b = A single argument or a list of up to six arguments for the user process. Seethe User Guidelines for instructions on entering a list of arguments. Anyargument containing lowercase letters or special characters must be enclosedin quotation marks.

BKG = Run the process in the background, freeing the terminal for further inputmessages. The default is foreground execution.

c = Number of segments to be output; specified in decimal. The default is 10segments; maximum is 999. Each segment has a maximum size of 1000bytes or 20 lines.

4. SYSTEM RESPONSE

PF = Printout Follows. Followed by the EXC-ENVIR-UPROC output message.

5. REFERENCES

IM/OM References:

Input MessagesEXC:ENVIR-PROCOP:ST-PROCESS

Output MessagesEXC-ENVIR-UPROC


Issue 28 EXC:ENVIR-UPROC-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEXC ENVIR UPROC August 2005

Other References:




EXC:ENVIR-UPROC-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EXC KILLCALL

ID............. EXC:KILLCALLRELEASE ....... 14.0 and laterTYPE .......... Input

1. PURPOSE

Request that calls for a particular mobile be killed using the Enhanced Kill Call Capability(EKILLCALL) optional feature.

The subscriber unit’s Mobile Identification Number (MIN) or International Mobile StationIdentity (IMSI) must be entered as a string of digits within double quotes. The commandmust be entered as a numeric value without quotes. For example the MIN 3125551234, thecommand would be entered as:EXC:KILLCALL;MIN "3125551234";CMD 1!

The IMSI feature must be active in order to use Format 2.

2. FORMAT

[1] EXC:KILLCALL;MIN "a";CMD c!

[2] EXC:KILLCALL;IMSI "b";CMD c!


a = 10-digit Mobile Identification Number (MIN).

b = 8- to 15-digit International Mobile Station Identity (IMSI).

c = The Enhanced Kill Call command. All of the commands will send a messageto the Read Only Printer (ROP). See the EXC-KILLCALL output message.Legal values and there meanings:

1 — Kill Call Without Automatic Message Accounting (AMA). Attempts totear down calls for the given MIN and if successful will generate aSecurity AMA record for the call.

2 — Kill Call With AMA. Attempts to tear down calls for the given MIN andif successful will generate a billable AMA record for the call.

3 — Alert Only. Will not attempt to tear down calls for the given MIN.

4. SYSTEM RESPONSE

?E = Error. Error in format of MIN or IMSI or CMD value.

NG = No Good.

PF = Printout Follows. Followed by a EXC-KILLCALL output message.


Issue 28 EXC:KILLCALL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEXC KILLCALL August 2005

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesEXC-KILLCALLREPT-KILLCALL

Other References:

401-612-146 Enhanced Kill Call Capability (EKCC)


EXC:KILLCALL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EXC LAESREQ

ID............. EXC:LAESREQRELEASE ....... 13.0 and laterTYPE .......... Input

1. PURPOSE

Request that an Lawfully Authorized Electronic Surveillance (LAES) action requestmessage be sent to the LAES delivery function.

The maximum length of the command line arguments is 60 characters, for example: thecombined length of (a + b + c <= 60). No argument can exceed 32 characters in length. Ifan argument exceeds 32 characters in length, an error message is returned. Digit stringarguments must be entered within double quotes. For example, the string 1234567890would be entered as:EXC:LAESREQ "1234567890"!

2. FORMAT

EXC:LAESREQ [a b c]!


a = Alphanumeric argument.

b = Alphanumeric argument.

c = Alphanumeric argument.

4. SYSTEM RESPONSE

?E = Error. Argument(s) exceeded maximum number of characters allowed perargument/ command line.

PF = Printout Follows. See output message REPT-LAESREQ.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesREPT-LAESREQ

Other References:

401-612-209 Lawfully Authorized Electronic Surveillance


Issue 28 EXC:LAESREQ-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEXC LAESREQ August 2005



EXC:LAESREQ-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EXC MRVT

ID............. EXC:MRVTRELEASE ....... 7.0 and laterTYPE .......... Input

1. PURPOSE

Initiates the Message Routing Verification Test (MRVT).

The requested test is run, and the report is written to the maintenance class and/or thestandard output.

Format 1: ANSI Standard.

NOTE: Non-local network point codes always use ANSI standard format.

Format 2: Lucent Technologies.

2. FORMAT

[1] EXC:MRVT;PC aaabbbccc [,STPS d] [,TRACE]!

[2] EXC:MRVT;PC aaaeefccc [,STPS d] [,TRACE]!


aaabbbccc = Point code of the terminating node for the test for the ANSI Standard.

aaaeefccc = Point code of the terminating node for the test for the Lucent TechnologiesStandard.

aaa = Network identifier.

bbb = Cluster identifier.

ccc = Member identifier.

d = Maximum number of Signal Transfer Points (STPs) the MRVT is allowed tocross (0-15). Default is 2.

ee = Region identifier.

f = Cluster identifier.

TRACE = Traces of STPs crossed during the test will be included in the output if thetest was a success or partial success. If a failure occurs, and this keyword ispresent the TRACE will not appear; however, some error messages docontain a listing of point codes which is similar to the TRACE.

4. SYSTEM RESPONSE

?D = Data Field contains an error. Questionable Data.

?I = Identification Field contains an error. Questionable Identifier (Keyword).


Issue 28 EXC:MRVT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEXC MRVT August 2005


RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesCHG:MRVT

Output MessagesCHG-MRVTEXC-MRVTREPT-MRVR



EXC:MRVT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EXC OFLBOOT

ID............. EXC:OFLBOOTRELEASE ....... 8.0 and laterTYPE .......... Input


**WARNING**Incorrect use of this command may interrupt operations of the system, ordegrade its performance or availability.

Off–line boot requires a logical split of the system during which one CU andall its subunits will not be available.

Note that the boot signal generated in the off–line side will result in theyellow CRITICAL alarm indicator being lit. This is the expected behavior ofthe indicator in all bootstraps (including offline boot). The indicator will becleared automatically within 30 seconds.

1. PURPOSE

Initiates the off-line boot procedure. This may be used to verify the integrity of boot filesand data, or as the prelude for the side switch.

There are some restrictions the user must follow for this input message to executesuccessfully:

• The primary or secondary disk must be selected manually.

• Both Input/Output Processors (IOPs) 0 and 1 cannot be selected for the off-line side.

• There should be no RCV activities running.

• There should be no diagnostic activities running.

• The MTTY and ROP port selector switches must be in the AUTO position and theportswitch controller must be powered on.

2. FORMAT

EXC:OFLBOOT: [, TTY a][, APARM b][, INITLVL c][, IOPx [MAX]][, HDWCHK][, SFTCHK][, ERRINT][, BROOT][, MINCONFIG][, UCL d][, MONITOR][, RETROFIT][, OOS][, TRACE]!


a = The TTY a option is used as a pseudo Read Only Printer (ROP) on the off-lineside. All of the off-line side output directed to the ROP is sent to this TTY.The valid range is 0 to 254.

If the selected TTY is a UNIX system TTY, the output sent to it may beunformatted until someone logs in.

The default is no TTY; the off-line ROP output will not be sent to any outputdevice.


Issue 28 EXC:OFLBOOT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEXC OFLBOOT August 2005

CAUTION:By selecting the Teletypewriter (TTY) option, the Input/Output Processor (IOP)associated with it is implicitly assigned to the off-line side.

b = The APARM b option is used as an application parameter for the off-line side.The range is a single alphanumeric character. This is equivalent to thefunction of poke 42 on the EAI page during normal boot.

The default is no APARM option set for off-line side.

c = The INITLVL c option is used as the UNIX RTR operating system bootstrapinitialization level for the off-line side.

2 — The initial CU system configuration must be ACT or STBY. The OOSoption will not override this requirement.

3 — Boot and load new ECD.4 — (default) Boot and load new ECD and clear Protected Application

Segment (PAS).

CAUTION:These levels apply to RTR initialization. Different applications may or may notsupport all of them.

IOPx = The IOP will be removed from service in the on-line side and remain on theoriginal off-line side until OFLBOOT is stopped. Side switching does notaffect this assignment. The range (x) can be 0 through 7.

If MAX is specified, all of the devices under this IOP will be equipped andmade available to the off-line side except the ROP, MaintenanceTeletypewriter (MTTY), and Switching Control Center (SCC). The ROP,MTTY, and SCC will be unequipped on the off-line side.

CAUTION:Even with the SCC unequipped, it may perform a link switch. In this case, all EAIcapabilities are functional.

If MAX is not specified, only peripheral controllers under this IOP will beequipped. Peripheral units under this IOP will not be equipped.If the default option and TTY a option are selected, only TTY a will beequipped under this IOP in addition to the peripheral controllers.

If oflboot is a prelude to the software release transition procedure, x has to beeither 0 or 1.

The default is IOPx without MAX.

HDWCHK = Hardware checks will be inhibited for the off-line side. The default is allowed.

SFTCHK = Software checks will be inhibited for the off-line side. The default is allowed.

ERRINT = Error interrupts will be inhibited for the off-line side. The default is allowed.

BROOT = Backup partitions will be used for the off-line side.

The default is the primary partitions.

CAUTION:If a side switch is done and then the oflboot procedure stopped, the system will berunning on the backup partitions. A boot will be needed afterward to return to theprimary (root) partition.


EXC:OFLBOOT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EXC OFLBOOT

MINCONFIG = Minimum configuration database will be used for the off-line side. Anysubsequent side switch will not be allowed.

The default is the full configuration database.

d = By selecting the UCL option some application prechecks will be overridden.The default enforces all prechecks.

CAUTION:Application initiated aborts will be ignored. Because the UCL option inhibits systemrecovery actions, it should be used only in a software release transition procedureunder technical guidance. Misuse can cause call processing downtime.

NOTE:Using the UCL option requires a password (d); to obtain it, seek technicalassistance. The value d will change every time the UCL option is entered;thus, using the UCL option always requires contacting technical assistance.

MONITOR = All off-line Processor Recovery Messages (PRMs) will be directed to the on-line ROP.

The default case will have only off-line PRMs up to Step 4 (KBOOT) directedto the on-line ROP.

RETROFIT = Recovery strategy will be modified to accommodate the software releasetransition.

The default is normal recovery strategy.

CAUTION:The RETROFIT option should be used only during a manual software releasetransition scenario. It has a strong impact during the side switch: allows the sideswitch to occur even if the switch precheck fails. This can result in a level 3 bootdepending on the nature of switch precheck failure. Misuse of this option can causecall processing downtime.

OOS = If specified, units selected for the off-line side may be initially Out Of Service(OOS). The default requires those units to be ACT or STBY.

TRACE = This option should be used by authorized technical personnel only. It is fortrouble shooting purposes, and will generate a significant amount ofundocumented trace messages.

The default is no trace message generated.

4. SYSTEM RESPONSE



?E = Error.


IP = In Progress.

NG = No Good.

RL = Retry Later. Some activity is running, that is incompatible withEXC:OFLBOOT; for example, rcvecd.


Issue 28 EXC:OFLBOOT-3

401-610-055 Flexent /AUTOPLEX Wireless NetworksEXC OFLBOOT August 2005

5. REFERENCES

IM/OM References:

Input MessagesSTOP:OFLBOOTSW:OFLBOOT

Output MessagesEXC-OFLBOOTREPT-OFLBOOTSTOP-OFLBOOTSW-OFLBOOT



EXC:OFLBOOT-4 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EXC SRVT

ID............. EXC:SRVTRELEASE ....... 7.0 and laterTYPE .......... Input

1. PURPOSE

Requests initiation of the Signaling Connection Control Part (SCCP) Routing VerificationTest (SRVT).

The requested test will be run, and the report written to the maintenance class and/or thestandard output.

Format 1: ANSI Standard.

Format 2: Lucent Technologies Standard.

2. FORMAT

[1] EXC:SRVT;TYPE a,DIGITS b[,TPC cccdddeee][,NTSP f][,TRACE]!

[2] EXC:SRVT;TYPE a,DIGITS b[,TPC cccggheee][,NTSP f][,TRACE]!


a = Translation type (0-254).

b = Digits in the global title, limited to 3, 6, 9, 10, or 12 digits. (for example, an800 number).

cccdddeee = ANSI Standard Translation Point Code (TPC) to which the initiator shouldaddress and send an SRVT message. If not included, the default is chosen byCommon Network Interface (CNI) based on the translation type. CNI willsend more than one SRVT message if more than one unique TPC is returned.

cccggheee = Lucent Technologies Standard TPC to which the initiator should address andsend an SRVT message. If not included, the default is chosen by CNI basedon the translation type. CNI will send more than one SRVT message if morethan one unique TPC is returned.

ccc = Network identifier

ddd = Cluster identifier

eee = Member identifier

f = Maximum number of Translation Signaling Points (TSPs) allowed to becrossed (1-15, default 1).

gg = Region identifier

h = Cluster identifier


Issue 28 EXC:SRVT-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEXC SRVT August 2005

TRACE = If this keyword is present, a list of TSPs crossed during the test will beincluded in the output. If this keyword is not present, a list of TSPs crossedwill be included only when an error occurs and one or more TSPs had beencrossed when the error occurred. No TRACE word will appear if notrequested.

4. SYSTEM RESPONSE


RL = Retry Later.

5. REFERENCES

IM/OM References:

Input MessagesCHG:SRVTOP:TPC

Output MessagesCHG-SRVTEXC-SRVTOP-TPC



EXC:SRVT-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EXC SSDUPD

ID............. EXC:SSDUPDRELEASE ....... 14.0 and laterTYPE .......... Input

1. PURPOSE

Requests a Shared Secret Data (SSD) update of a particular mobile for the AuthenticationCapability.

The Mobile Identification Number (MIN) or International Mobile Station Identity (IMSI)must be entered as a string of digits within double quotes. For example, for a MIN of3125551234, the command would be entered as:EXC:SSDUPD;MIN "3125551234"!

The IMSI feature must be active in order to use Format 2.

2. FORMAT

[1] EXC:SSDUPD;MIN "a"!

[2] EXC:SSDUPD;IMSI "b"!




4. SYSTEM RESPONSE

?E = Error. Error in format of Mobile number.

IP = In Progress. See output message REPT-SSDUPD.

NG = No Good. May be one of the following:— AUDB entry (AUTH form) not found for this MSID— Another Authentication for MSID in progress— Authentication inactive; check FAF— MSID not found in SUB form— Max. No. of Authentication requests in progress— Mobile handed off to another MSC— Mobile in state not allowed for Auth. Operation— Mobile on cell incapable of Authentication— Mobile on MSC incapable of Authentication— xxx Resource shortage — xxx is the resource in question.)

RL = Retry Later. May be one of the following:— AUDB entry (AUTH form) not found for this MSID— Another Authentication for MSID in progress— Authentication inactive; check FAF— MSID not found in SUB form— Max. No. of Authentication requests in progress— Mobile handed off to another MSC— Mobile in state not allowed for Auth. Operation


Issue 28 EXC:SSDUPD-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEXC SSDUPD August 2005

— Mobile on cell incapable of Authentication— Mobile on MSC incapable of Authentication— xxx Resource shortage — xxx is the resource in question.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesREPT-SSDUPD

Other References:

401-612-041 Authentication


EXC:SSDUPD-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EXC UCHALL

ID............. EXC:UCHALLRELEASE ....... 14.0 and laterTYPE .......... Input

1. PURPOSE

Requests a Unique Challenge of a particular mobile for the Authentication Capability.

The Mobile Identification Number (MIN) or International Mobile Station Identity (IMSI)must be entered as a string of digits within double quotes. For example, for a MIN of3125551234, the command would be entered as:EXC:UCHALL;MIN "3125551234"!

The IMSI feature must be active in order use Format 2.

2. FORMAT

[1] EXC:UCHALL;MIN "a"!

[2] EXC:UCHALL;IMSI "b"!




4. SYSTEM RESPONSE

?E = Error. Error in format of Mobile number.

IP = In Progress. See output message REPT-SSDUPD.

NG = No Good. May be one of the following:— AUDB entry (AUTH form) not found for this MSID— Another Authentication for MSID in progress— Authentication inactive; check FAF— IMSI inactive;check FAF— MSID not found in SUB or VLR form

— Max. No. of Authentication requests in progress— Mobile handed off to another MSC— Mobile in state not allowed for Auth. Operation— Mobile on cell incapable of Authentication— Mobile on MSC incapable of Authentication— xxx Resource shortage — xxx is the resource in question.)— SSD not shared for this MSID; cannot perform UC

RL = Retry Later. May be one of the following:— AUDB entry (AUTH form) not found for this MSID— Another Authentication for MSID in progress— Authentication inactive; check FAF— IMSI inactive;check FAF— MSID not found in SUB or VLR form

— Max. No. of Authentication requests in progress


Issue 28 EXC:UCHALL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEXC UCHALL August 2005

— Mobile handed off to another MSC— Mobile in state not allowed for Auth. Operation— Mobile on cell incapable of Authentication— Mobile on MSC incapable of Authentication— xxx Resource shortage — xxx is the resource in question.)— SSD not shared for this MSID; cannot perform UC

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesREPT-UCHALL

Other References:

401-612-041 Authentication


EXC:UCHALL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 EXC UCL

ID............. EXC:UCLRELEASE ....... 8.0 and laterTYPE .......... Input

1. PURPOSE

Causes the user shell to accept an input message that it previously rejected because it wasnot represented in the input message catalog database.

When operating in the full capability mode, the user shell will reject any input messagethat is not represented in the Input Message (IM) catalog database, with an erroracknowledgement. Consequently, a missing or erroneous entry in the IM catalog willcause the user shell to reject the associated input message, even if it is typed correctly. Ifthis should occur, the user can force the user shell to accept the message and attempt toexecute it by entering the EXC:UCL command immediately following the erroracknowledgement. This command affects only the message immediately preceding therejected input message. It will not cause the user shell to re-execute a successful messageor a message with a syntax error, and it has no effect on any subsequent message. If it isused to force the user shell to execute an invalid input message, the invalid message will berejected by the program that processes it.

This command may be used only when the shell is operating in the full capability mode. Itwill be rejected if the shell is operating in the partial capability mode or limp mode.

2. FORMAT

EXC:UCL!


See Purpose.

4. SYSTEM RESPONSE

NG = No Good. The command has been rejected for one of the followingreasons:

— ’EXC:UCL’ INVALID IN PART MODE— CFTSHL CANNOT EXECUTE ’EXC:UCL’ ITSELF— NO PREVIOUS COMMAND AVAILABLE— PREVIOUS COMMAND HAD A SYNTAX ERROR

OK = Good. Followed by the command to be executed, its acknowledgement,and any resulting output messages. Refer to the manual page for theprevious command.

5. REFERENCES

IM/OM References:

Input MessagesNone.


Issue 28 EXC:UCL-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksEXC UCL August 2005


Other References:



EXC:UCL-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 FRCHO CELL RA

ID............. FRCHO:CELL-RARELEASE ....... 22.0 and laterTYPE .......... Input

1. PURPOSE

This message is only valid for Radio Cluster Server (RCS) cells.

Force a call handoff to another free voice radio on the same logical cell face or to a specificvoice radio located either on the same cell or a different cell on the same Digital CellularSwitch (DCS). This message can free up a specific voice radio to perform diagnostics or tomove a call onto a voice radio which is suspected of being bad.

NOTE: This message is valid for a trunk group and member that is vocoder relocated(Vocoder is In the Switch [VIS]). You must use this message rather than theFRCHO:DCS-TRKGRP command.

This message moves a call which is active on a particular cell and voice radio (source radio)to any other free radio on the same logical cell face or to a specific radio (destination radio)on the same cell or a different cell on the same DCS. The UCL option can be allow or denysubsequent handoff requests.

If the destination radio is not specified, the call will be handed off to any other free radioon the same face. If the destination radio is specified and that radio is idle, the call will behanded off to that radio.

The handoff will be denied if:

1. No destination radio is given and all of the radios on the same logical face as thesource radio are busy.

2. The destination radio specified is not idle.

3. The source radio is already in the progress of performing a handoff or is any otherstate in which a handoff is normally not allowed.

2. FORMAT

FRCHO:CELL a[, MICRO b], RA c, CARRIER d [,UC e][; CELL f[, MICRO g], RA h, CARRIER i [,UC j] [;UCL]] [ CLASS k]!


a = Source cell site number (1-600).

b = Source microcell number (1-6).

c = Source cell site radio number:1-192 — for Series II (SII) cells.1-5 — for Radio Cluster Server (RCS) cells.

d = Source RCS cell site carrier number (1-2).

e = Source cell site user channel number (1-3). This option is required if c is adigital radio. This option is not allowed if c is an analog radio.


Issue 28 FRCHO:CELL-RA-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksFRCHO CELL RA August 2005

f = Destination cell site number (1-600).

g = Destination RCS microcell number (1-6).

h = Destination cell site radio number:1-192 — for SII cells.1-5 — for RCS cells.

i = Destination RCS cell site carrier number (1-2).

j = Destination cell site user channel number (1-3). This option is required if his a digital radio. This option is not allowed if h is an analog radio.

UCL = Deny all handoff requests until another forced handoff request without theUCL option is issued. UCL must be used with a destination argument.

k = Overriding output message class (151-213). This option may be used onlyif the Virtual System Output Message Routing feature is supported.

4. SYSTEM RESPONSE

?E = Error. Necessary condition for execution of request not met. DCS ortrunk identification likely not valid.

NG = No Good. May be one of the following reasons:

— Invalid input.

— Feature not active.

— Requested trunk not in use.

— Destination Trunk is not idle.

— Call is in an invalid state for handoff.


PF = Printout Follows. Request has been acknowledged. Output message willfollow.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesFRCHO-CELL-RA

Other References:



FRCHO:CELL-RA-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 FRCHO DCS TRKGRP

ID............. FRCHO:DCS-TRKGRPRELEASE ....... 14.0 and laterTYPE .......... Input

1. PURPOSE

Force a call handoff to another free voice radio on the same logical cell face or to a specificvoice radio located either on the same cell or a different cell on the same Digital CellularSwitch (DCS). This message can free up a specific voice radio to perform diagnostics or tomove a call onto a voice radio which is suspected of being bad.

NOTE: This message is not valid for a trunk group and member that is vocoder relocated(Vocoder is In the Switch [VIS]). You must use the FRCHO:CELL-RA command.

This message moves a call which is active on a particular cell and voice radio (source radio)to any other free radio on the same logical cell face or to a specific radio (destination radio)on the same cell or a different cell on the same DCS. The UCL option can be allow or denysubsequent handoff requests.

If the destination radio is not specified, the call will be handed off to any other free radioon the same face. If the destination radio is specified and that radio is idle, the call will behanded off to that radio.

The handoff will be denied if:

1. No destination radio is given and all of the radios on the same logical face as thesource radio are busy.

2. The destination radio specified is not idle.

3. The source radio is already in the progress of performing a handoff or is any otherstate in which a handoff is normally not allowed.

2. FORMAT

FRCHO:DCS a, TRKGRP b, MEMBER c[[; TRKGRP d, MEMBER e][;UCL]][ CLASS f]!



b = Source cell site trunk group number:

1-2000 — for 5ESS Digital Cellular Switch (DCS).

c = Source cell site trunk member number (1-192).

d = Destination cell site trunk group number:

1-2000 — for 5ESS Digital Cellular Switch (DCS).

e = Destination cell site trunk member number (1-192).

UCL = Deny all handoff requests until another forced handoff request without theUCL option is issued. UCL must be used with a destination argument.


Issue 28 FRCHO:DCS-TRKGRP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksFRCHO DCS TRKGRP August 2005

f = Overriding output message class (151-213). This option may be used onlyif the Virtual System Output Message Routing feature is supported.

4. SYSTEM RESPONSE

?E = Error. Necessary condition for execution of request not met. DCS ortrunk identification likely not valid.

NG = No Good. May be one of the following reasons:

— Invalid input.

— Feature not active.

— Requested trunk not in use.

— Destination Trunk is not idle.

— Call is in an invalid state for handoff.


PF = Printout Follows. Request has been acknowledged. Output message willfollow.

5. REFERENCES

IM/OM References:

Input MessagesNone.

Output MessagesFRCHO-DCS-SRC-TRKGRP

Other References:



FRCHO:DCS-TRKGRP-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 FRMV LN

ID............. FRMV:LNRELEASE ....... 8.0 and laterTYPE .......... Input


**WARNING**This command can cause signaling point isolation, isolating the office andinterrupting Common Channel Signaling (CCS) message processing, byremoving the last Link Node (LN) of a set. Use it only when it is necessaryto override the safety checks of the RMV:LN command.

1. PURPOSE

Forces removal of the specified node from service, regardless of the state of the link, mate,or of other nodes.

If the node (except Ring Peripheral Controller [RPC]) major state is ACT, the node (exceptRPC) is in the active ring segment, and the Interprocessor Message Switch (IMS)subsystem is not initializing at a level higher than 1A, then an attempt is made to removethe node (except RPC) from service. If successful, the LN major state is changed to OOSand the node itself is placed in the quarantine state.

When a node is manually removed, it becomes the responsibility of the craft to restore thenode to service.

This command does not use the Maintenance Input Request Administrator (MIRA) queue,so the OP:DMQ and STOP:DMQ commands do not apply to it and it may be executed aheadof previously entered commands in the MIRA queue.

Due to the nature of this command, Network Services Division (NSD) offices are requiredto confirm command execution. NSD offices will be prompted with an "ARE YOU SURE<Y/N>?" query. If an affirmative response ("Y" or "y") is entered within 10 seconds, thenthe command will be executed; otherwise, the command will not be executed.

2. FORMAT

FRMV:LNa b!


a = A Ring Node (RN) group number (00-63) with explicit leading zero forgroup numbers less than 10.

b = The node’s position in the RN group (1-15).

4. SYSTEM RESPONSE

NG = No Good. The request was not accepted; the reason will follow.

RL = Retry Later. The FRMV:LN command cannot execute at this time; thereason will follow.


Issue 28 FRMV:LN-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksFRMV LN August 2005

5. REFERENCES

IM/OM References:

Input MessagesDGN:LNRMV:LNRST:LN

Output MessagesDGN-LNFRMV-LNRMV-LNRST-LN

Other References:



401-661-045 Common Network Interface (CNI) Ring Maintenance- Diagnostic User’s Guide Section


FRMV:LN-2 Issue 28

Flexent /AUTOPLEX Wireless Networks 401-610-055August 2005 HELP

ID............. HELPRELEASE ....... 23.0 and laterTYPE .......... Input

1. PURPOSE

Displays list of all the commands that are valid on Technician Interface Command LineInterface (TICLI), with some syntax information. This command will either display a list ofall the commands or a set of commands, based on the option specified with the command.

2. FORMAT

[1] HELP ALL

[2] HELP a


a = One of following command verbs:

ABTALWAUDBKUPCFRCLRCOMMITCOPYCREATEDELDELETEDGNDNLDDUMPEXCFRCHOINHINITLABLELOADMONMOVEOCNSOPRESETRESTARTRMVRSTSELECTSENDSETSTOP


Issue 28 HELP-1

401-610-055 Flexent /AUTOPLEX Wireless NetworksHELP August 2005

SWSWITCHBACKSWITCHOVERUPDVERWRITE

4. SYSTEM RESPONSE

List of all commands or a list of commands for a specific verb.

5. REFERENCES

IM/OM References:

Input MessagesNone

Output MessagesNone



HELP-2 Issue 28

Documents

401-610-055v1