General Error Messages of System.pdf

8/17/2019 General Error Messages of System.pdf

1/667

GSM/EDGE BSS, Rel.

RG20(BSS), Operating

Documentation, Issue 12

General Error Messages of System

DN987378

Issue 27-0

Confidential

Nokia Siemens Networks is continually striving to reduce the adverse environmental effects of

its products and services. We would like to encourage you as our customers and users to join

us in working towards a cleaner, safer environment. Please recycle product packaging and

follow the recommendations for power use and proper disposal of our products and their compo-

nents.

If you should have questions regarding our Environmental Policy or any of the environmental

services we offer, please contact us at Nokia Siemens Networks for any additional information.


2/667

2 DN987378


Id:0900d8058098a8bf

Confidential

The information in this document is subject to change without notice and describes only the

product defined in the introduction of this documentation. This documentation is intended for the

use of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted

in any form or means without the prior written permission of Nokia Siemens Networks. The

documentation has been prepared to be used by professional and properly trained personnel,

and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes

customer comments as part of the process of continuous development and improvement of the

documentation.

The information or statements given in this documentation concerning the suitability, capacity,

or performance of the mentioned hardware or software products are given "as is" and all liability

arising in connection with such hardware or software products shall be defined conclusively and

finally in a separate agreement between Nokia Siemens Networks and the customer. However,

Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions

contained in the document are adequate and free of material errors and omissions. Nokia

Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which

may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO

EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-

TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-

RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED

TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY

OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION

IN IT.

This documentation and the product it describes are considered protected by copyrights and

other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark

of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respectiveowners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2013. All rights reserved

f Important Notice on Product SafetyThis product may present safety risks due to laser, electricity, heat, and other sources

of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle

this product and only after having carefully read the safety information applicable to this

product.

The safety information is provided in the Safety Information section in the “Legal, Safety

and Environmental Information” part of this document or documentation set.

The same text in German:

f Wichtiger Hinweis zur ProduktsicherheitVon diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder

andere Gefahrenquellen ausgehen.

Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch

geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-

anforderungen erfolgen.

Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal,

Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentations-

satzes.


3/667

DN987378 3


Id:0900d8058098a8bf

Confidential

Table of contentsThis document has 669 pages.

1 General error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 DX error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.1 Error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6


4/667

4 DN987378


Id:0900d8058098a8bf

Confidential


5/667

DN987378 5

General Error Messages of System General error messages

Id:0900d8058098a8e9

Confidential

1 General error messagesThe general error messages are listed here in numerical order.

During an MML session, the user can see the explanation of an error that has occurred,together with instructions (if any) how to proceed, by pressing the character combination

CTRL-7. In addition, the user can search for the explanation of an error message by

means of the service terminal extension MRSTRE.

As this list contains the general execution error messages of all applications, it is

possible that it will also include messages that do not belong to the configuration of a

particular customer.

Error code values greater than 0x7fffffff = 2147483647 are application specific. They are

described in the application specific documents. The user cannot see the explanation of

these codes by using CTRL-7 or MRSTRE as given above.


6/667

6 DN987378


Id:0900d8058098a8ed

Confidential

DX error messages

2 DX error messages

2.1 Error messages0 SUCCESS

The operation succeeded completely.

1 NO SUCH FILE

The file does not exist.

2 FILE READ PROTECTED

The file is read protected.

3 OFFSET OUT OF FILE

The offset points out of the file.

4 OFFSET OUT OF RECORD

The offset points out of the record.

5 RECORD NUMBER OUT OF FILE

The number of the record is equal to or greater than the number of

records in the file.

6 SUBRECORD NUMBER OUT OF RECORD

The number of the subrecord is equal to or greater than the number of

subrecords in the file.

7 SEARCH KEY NOT FOUND

The search key is not found in the file.

8 FILE ALREADY EXISTS

The file already exists.

9 NOT IMPLEMENTED

The feature has not been implemented.

10 INCORRECT FILE HANDLE

The file handle is incorrect.

11 INCORRECT FILE TYPE

The type of the file is unknown, or it does not fit in the situation.

12 FILE HAS NO BITMAP

The file has no bitmap.

13 POINTER TO FILE DEFINITION STRUCTURE IS NULL

The pointer to the structure defining the characteristics of a file is null.

14 INCORRECT FILE DEFINITION STRUCTURE

The structure defining the characteristics of a file is incorrect.

15 INCORRECT ACCESS MODE

The access mode is forbidden or unknown.

16 FILE CATALOG FULL

The file catalog is full.


7/667

DN987378 7

General Error Messages of System DX error messages

Id:0900d8058098a8ed

Confidential

17 PROCESS LDT FULL

The LDT (local description table) of the process is full.

18 MEMORY ALLOCATION ERROR

An error has occurred in the allocation of memory space.

19 FILE WRITE PROTECTED

The file is write protected.

20 INCORRECT FILE BLOCK NUMBER

The number of the file block is incorrect.

21 NO BLOCK CHECK SUM IN FILE

The file has no block-specific check sums.

22 NULL POINTER TO PARAMETER

The pointer to the parameter is null.

23 ARRAY REALLOCATION ERROR

An error has occurred in the array reallocation.

24 RECORD IS FREE

The record is free.

25 RECORD IS NOT FREE

The record is not free.

26 END OF FILE CATALOG

The file catalog has ended.

27 CHECK SUM CALCULATION FAILUREThe calculation of the check sum failed (file was updated during the cal-

culation).

28 PCMCON GSW ERROR

The PCMCON file of the group switch is incorrect.

29 FILE DISTRIBUTION TIME-OUT

The time limit of file distribution has expired.

30 FILE DISTRIBUTION ERROR

An error has occurred in file distribution.

31 UNIT TYPE ACCESS ERROR An error has occurred in conversions between the unit type, logical

address and message bus address.

32 FLOPPY DISK CONTROLLER BUSY

The floppy disk controller has not returned to its original state after the

previous disk operation. The floppy disk controller is faulty. Restart the

EDISKD program block. Replace the DMADI plug-in unit.

33 FLOPPY DISK CONTROLLER IN RESULT PHASE

The floppy disk controller is in result phase. A new command is given

when the previous command is still in result phase. There is a distur-

bance in the EDISKD program block or the floppy disk controller is


8/667

8 DN987378


Id:0900d8058098a8ed

Confidential

DX error messages

faulty. Restart the program block EDISKD. Replace the DMADI plug-in

unit.

34 FLOPPY DISK CONTROLLER IN COMMAND PHASE

The floppy disk controller is in the command phase. The floppy disk con-troller waits for a new command while an attempt is made to read the

result of the previous command from it. There is a disturbance in the

EDISKD or the floppy disk controller is faulty. Initialize the floppy disk

controller again. Replace the DMADI plug-in unit.

35 EQUIPMENT CHECK ERROR

The disk drive has given an error signal or the 0 cylinder is not reached

in the recalibration command after 77 step pulses. The disk drive or the

floppy disk controller is faulty. Replace the disk drive. Replace the

DMADI plug-in unit.

36 DRIVE NOT READY

The disk drive is not capable of executing a new disk operation. The

operator tries to read the empty side of a single-sided disk or write on

an empty side of a single-sided disk. The disk type is not correct, the

disk does not exist, the door of the disk drive is open, there is no power

in the disk drive, the disk drive does not exist, the disk drive is faulty or

the floppy disk controller is faulty. Check the disk. Close the door of the

disk drive. Check the disk drive and change it if necessary. Replace the

DMADI plug-in unit.

37 RECALIBRATE ERROR

The transfer of the read/write head of the disk drive to the 0 track has

failed. Replace the disk drive. Replace the DMADI plug-in unit.

38 SEEK ERROR

The search for a track or a sector has failed. The disk drive or the floppy

disk controller is faulty. Replace the disk drive. Replace the DMADI

plug-in unit.

39 END OF TRACK ERROR

The floppy disk tries to direct a command to a sector whose number is

higher than that of the last sector of the track. There is a disturbance in

the EDISKD program block or the floppy disk controller is faulty. Restart

the EDISKD process. Replace the DMADI plug-in unit.

40 CRC ERROR IN DATA

There is a CRC error in the data field of the sector. The disk is faulty.

Replace the disk.

41 CRC ERROR IN ID

There is a CRC error in the ID field of the sector. The disk is faulty.

Replace the disk.

42 LATE DMA

The DMA controller does not receive permission for DMA transfer in

time. The DMA controller is faulty or the administration logic of the bus

is faulty. Replace the DMADI plug-in unit. Replace the CPU386 plug-in

unit.


9/667

DN987378 9


Id:0900d8058098a8ed

Confidential

43 SECTOR NOT FOUND

The floppy disk controller does not find the sector required. The disk is

faulty or the floppy disk controller is faulty. Replace the disk. Replace

the DMADI plug-in unit.44 DISK WRITE PROTECTED

The disk is write protected. Remove write protection.

45 MISSING DATA ADDRESS MARK

The floppy disk controller does not find the data address mark on the

required track. The disk or the floppy disk controller is faulty. Replace

the disk. Replace the DMADI plug-in unit.

46 MISSING ID ADDRESS MARK

The floppy disk controller does not find the ID address mark on the

required track. The disk or the floppy disk controller is faulty. Replace

the disk. Replace the DMADI plug-in unit.

47 CONTROL MARK

A deleted data address mark has been read during a reading operation.

The disk is faulty. Replace the disk.

48 CYLINDER ADDRESS ERROR

The cylinder address of the ID field of the sector differs from the current

cylinder address maintained by the floppy disk controller. There is a dis-

turbance in the program block EDISKD, the disk is faulty or the floppy

disk controller is faulty. Initialize the floppy disk controller again.

Replace the disk. Replace the DMADI plug-in unit.

49 BAD SECTOR

Floppy disk: The cylinder address of the ID field of the sector is 0FFH.

The disk is faulty. Replace the disk. Winchester: The disk operation has

been directed to a track which has been marked bad.

50 INCORRECT TASK

Incorrect command. The program block EDISKD does not recognize

the task given. The application program is faulty. Check the application

program.

51 NO EQUIPMENT

There is no equipment. There are no disk drives connected to the

DMADI plug-in unit, or the cable between the DMADI and the disk drive

has been accidentally disconnected. Connect the cable.

52 INCORRECT PARAMETER IN TASK

The parameter is incorrect. One of the parameters of the parameter

block is incorrect. The application program is incorrect. Check the appli-

cation program.

53 END OF DISK FOUND

The last sector of the disk has been reached. An attempt is made to

read from the disk (absolute reading) or to write onto the disk (absolute

writing) past the end of the disk. The reading or writing is ended in the

last sector. An attempt is made to write outside the memory of the disk.


10/667

10 DN987378


Id:0900d8058098a8ed

Confidential

DX error messages

54 COMMAND NOT ALLOWED ON OLD FORMAT DISK

The command is not allowed on the disk of the old format. Do not give

this command.

55 FORMAT ERROR

Floppy disk: The formatting of the disk has failed. The disk is faulty.

Replace the disk. Winchester: The read/write head of the disk drive

stays on the track on which the formatting has failed. Mark the track bad

and format the alternative track.

56 NO SUCH FILE

The file specified by the parameter block is not found on the disk. The

disk is incorrect or the application program is faulty. Replace the disk.

Check the application program.

57 LABEL IS THE ONLY ONE

An attempt has been made to delete the only label of the disk file.

58 FILE WRITE PROTECTED

The file is write protected.

59 FILE ALREADY UNPROTECTED

The file is already unprotected through another label.

60 FILE ALREADY EXISTS

The file already exists.

61 END OF DATA FOUND

The last data sector of the file has been reached. An attempt is made to

read the file past the end of the data. The reading is ended in the last

data sector.

62 NO DATA TO READ

There is no data to read. The file is empty or the read pointer of the

parameter block points past the end sector of the file data.

63 END OF FILE FOUND

The last sector of the file has been reached. An attempt is made to write

past the end of the file. The writing is ended in the last sector.

64 FILE FULL

The file is full.65 FILE TOO BIG

An attempt has been made to create a file which requires too much

memory space. Pack the disk. Reduce the memory reservation of the

file.

66 DISK FULL

The disk is full. All file labels of the disk are in use.

67 TOO MANY CRC ERRORS

The CRC counter of the disk has reached the maximum value. Replace

the disk.

68 DMA TERMINATION ERROR


11/667

DN987378 11


Id:0900d8058098a8ed

Confidential

The DMA transfer has been shorter than expected. Replace the DMADI

plug-in unit.

69 TIME-OUT ERROR

The device has not responded within the given time. Carry out periodicmaintenance and replace the used media if necessary. If the problem

re-occurs, check the device, used media, cabling and controller.

70 INCORRECT COMMAND

The command code of the parameter block is unknown.

71 WRITE BLOCK TOO SHORT

The length of the block to be written is shorter than 4, and blocks shorter

than 4 cannot be written on the tape. Load the MML and try again.

72 MULTIFILE NOT ALLOWED

An attempt has been made to open a file on a one-file tape with a mul-

tifile opening command or quick file opening command. When neces-

sary, change the tape type into a one-file tape and try again.

73 TRACK WRITE PROTECTED

Reel-to-reel tape unit (MTU) is write protected. Remove the protection

unless there is a reason for it.

74 ONE FILE TAPE

An attempt has been made to direct to a one-file tape one of the follow-

ing commands which can be directed only to multifile tapes: premark

tape, close file quickly, close multifile, search for HDR1 block or search

for file. Replace the tape with a multifile tape and give the command

again.

75 CORRECTED ERROR

The formatter has detected an error in connection with a reading or

writing operation. The error has been corrected and data can be read

from the tape.

76 TAPE MARK READ

The block read was a tape mark. Repeat the MML command. If the error

occurs again, clean the read head of the drive and change the tape reel.

77 VERIFY ERROR

The data has not been written on the tape. The fault is either in the reel-to-reel tape unit or in the RAM. Locate and replace the faulty unit.

78 CRC ERROR

Despite repeated attempts writing fails due to a fault in the tape or in the

read head. Clean the read head of the reel-to-reel tape unit or replace

the tape with a new one.

79 LATE DMA

The DMA circuit of the DMADI has not transferred data between the

MTU and the RAM. The fault is either in the TAPI, DMADI or CPU386

plug-in units. Highest probability is that the fault is in the DMADI.

Replace the faulty unit.

80 DRIVE NOT READY


12/667

12 DN987378


Id:0900d8058098a8ed

Confidential

DX error messages

The reel-to-reel tape unit is not ready to receive commands. There is a

hardware fault in the drive. Try again in 3-4 minutes.

81 FORMATTER BUSY

The reel-to-reel tape unit is executing a command. A new command hasbeen given before the previous one has been acknowledged. The oper-

ating system is faulty. Locate the fault, initialize the TAPEDR program

block if necessary.

82 ACCESSED DRIVE OFF LINE

The reel-to-reel tape unit given in the MML command is in the OFF LINE

state. Press the ON LINE button on the front panel of the unit.

83 PHYSICAL END

The end mark of the tape has been detected. If the tape should not be

at the end, check the condition of the tape and, when necessary, clean

the read head and change the tape.84 WRITE SECTION NOT FOUND

No write section is found in the reel-to-reel tape unit specified in the

MML command. Open the tape.

85 FILE TRANSFER SYSTEM BUSY (PROGRAM BLOCK MEMDAT)

The program block MEMDAT is not capable of receiving new tasks. Try

again.

86 FILE TRANSFER SYSTEM BUSY (PROGRAM BLOCK DUMPER)

The program block DUMPER is not capable of receiving new tasks. Try

again.

87 FILE TRANSFER SYSTEM BUSY (PROGRAM BLOCK FULLER)

The program block FULLER is not capable of receiving new tasks. Try

again.

88 FILE TRANSFER SYSTEM BUSY (PROGRAM BLOCK LOADER)

The program block LOADER is not capable of receiving new tasks. Try

again.

89 FILE TRANSFER SYSTEM BUSY (PROGRAM BLOCK UPDATE)

The program block UPDATE is not capable of receiving new tasks. Try

again.

90 LOADING ABORTED

The program block DUMPER has interrupted the loading of the files due

to a loading error. Try again.

91 ERROR IN LOADING MESSAGE

There is an error in the loading message. The loading message has

been distorted on the message bus. Try again.

92 END OF FILE FOUND

The file is loaded up to the end mark. The file to be loaded is shorter

than indicated by the program block which has requested the loading.

The situation is normal if the MEMDAT program block has been

requested to update the whole file.


13/667

DN987378 13


Id:0900d8058098a8ed

Confidential

93 INCORRECT FILE NUMBER

The file number is incorrect. Check that the file number is correct and

that it belongs to the files of the source unit or the target unit.

94 NO RESPONSE

No acknowledgement is received from the LOADER program block to a

loading message. Check the operation of the ASS bus and the

LOADER program block.

95 LENGTH ERROR IN LOADING

Loading error. Check that the number of bytes to be updated which is

given to the MEMDAT program block is no larger than the file length.

96 NO MESSAGE

No message was received by the program block.

97 INCORRECT MESSAGE

The program block does not recognize the task identifier.

98 UNUSABLE STORE

Reading or writing on the disk is not possible. Check that the disk drive

is in order and in correct state.

99 DUMPING ABORTED

The sending of files has been interrupted.

100 BEGIN OF TAPE

The tape is at the beginning: A new tape has been inserted into the tape

unit or the tape unit has been set in the OFF LINE state with operating

switches although the unit should be in the ON LINE state.

101 TIME-OUT ERROR (2)

The TAPEDR program block has been waiting for an interrupt but it has

not arrived within the time limit. (The length of timeout supervision is 3-

15 seconds, 3 minutes in rewinding.) Cause for the error: 1. The cable

of the interrupt line between the TAPI and CPU386 plug-in unit is broken

or connected to a wrong pin. 2. The program block has set the address

of the interrupt service program incorrectly in the interrupt vector table.

3. The tape unit has moved into the OFF LINE state, possibly because

of a disturbance. 4. The tape unit is faulty. 5. The magnetic tape is

faulty. Check the items above.

102 WRITE BLOCK TOO LONG

An attempt has been made to write too long a data block on the I/O

device. Correct the error in the application process.

103 DUPLICATE PREFORMATTING

An attempt has been made to format a tape already formatted.

104 NOT AT BEGINNING OF TAPE

The tape is not at the beginning as it should be in connection of the for-

matting and opening commands. Rewind the tape to the beginning.

105 IDENTIFICATION FAILURE


14/667

14 DN987378


Id:0900d8058098a8ed

Confidential

DX error messages

An attempt is made to open a formatted tape with an incorrect identifier

(ID). Check the identifier.

106 PREFORMAT MISSING

The opening command has been given for a tape which has not beenformatted. Format the tape.

107 MULTIFILE TAPE

An error occurs when a command is given which is allowed only to one-

file tapes and there is a multifile tape in the tape unit. Check the tape

type and change it when necessary.

108 TAPI UNIT FAILURE

There is a fault in the TAPI plug-in unit. Change the TAPI plug-in unit.

109 DMA UNIT FAILURE

Before a reading or writing task is executed the TAPEDR program block

checks in the DMADI plug-in unit the DMA channels which have been

reserved for data transfer. If an error is detected, the command will not

be executed but a failure status will be returned. Change the DMADI

plug-in unit.

110 DATE NOT EXPIRED

An attempt has been made to format a tape with an HDR1 label whose

date has not expired. Release the tape or take another tape into use.

111 FORMAT ERROR

The start block is faulty on the track to be closed. The track close task

has been directed to a faulty track. Give a new command to the correct

track.

112 PRINTER FAILURE

The printer is out of order. Check the printer and the printer cable.

113 SERO BOARD MISSING

The SERO unit of the printer interface is missing or faulty. Check that

the SERO unit is in its place and functioning.

114 SERO BOARD FAILURE

The SERO unit of the printer interface is faulty. Check the functioning of

the SERO unit and replace it if necessary.

115 I/O DEVICE IN INCORRECT WORKING STATE

Operation has been directed to an I/O device that is not in the WO state.

Check the working state of the I/O device and set it into the WO state if

necessary.

116 TAPE CHANGE TIME-OUT

A tape change command has been given but the new tape has not been

installed quickly enough. Preformat and open the new tape.

117 INCORRECT PARAMETER IN TASK

The object data (tape unit number, tape reel, or file name) in the task is

incorrect. Correct the object data (application program or logical file

incorrect).


15/667

DN987378 15


Id:0900d8058098a8ed

Confidential

118 INCORRECT NUMBER OF DRIVE

The device corresponding to the tape unit index in the task has not been

included in the software package in question. Correct the tape unit index

or software package so that the required tape unit is included.119 INCORRECT NAME OF TAPE FILE (ALREADY IN USE)

The file name defined in the MML command is already in use in another

tape unit. Open the tape file with a name which is not yet in use.

120 INCORRECT NAME OF REEL (ALREADY IN USE)

The name of the tape reel given in the MML command is already in use

in another tape unit. Preformat the tape by using a name which is not

yet in use.

121 COMMAND NOT ALLOWED IN THIS TAPE STATE

The MML command is not allowed in the current state of the tape.

Correct the working state of the tape. If the tape unit is blocked, it mustbe set in the ON LINE state again.

122 CHECKSUM ERROR IN SYSTEM MONITORING MESSAGE

The checksum in the message between the OSMONI program block

and the application program is incorrect. Repeat the command.

123 WRONG MEMORY OR I/O ADDRESS

The program block OSMONI tries to handle an incorrect memory area.

(Write on ROM, no memory area, no input port, etc.) Change the

address.

124 MEMORY LACKING IN GIVEN ADDRESS

There is memory space only in part of the area to be filled.

125 PROCESS NOT IN DXPARA

The process identifier is incorrect. Check the process identifier.

126 ASS UNIT BUSY

An attempt is made to write on the memory of the ASS3 (DX 210). An

attempt is made to write on the active side of the ASS0-ASS2 memo-

ries. It is not possible to write on the memory of the ASS3. Perform swi-

tchover.

127 NO RESPONSE FROM PREPROCESSOR

The preprocessor does not respond within time limit. Check that theplug-in unit exists. Try again.

128 TIME LIMIT EXCEEDED IN LOADING

MMIMAN has not received a response to a link or load message from

IOMANA within the time limit when loading the MML program, in parts,

into the OMU or MSW memory. Try again.

129 UNKNOWN COMMAND

The requested MML program is not in the MCOMND file or MMIMAN

has not accepted MCOMND in its validity checks. Check the MCOMND

file. Restart MMIMAN.

130 UNKNOWN COMMAND CLASS


16/667

16 DN987378


Id:0900d8058098a8ed

Confidential

DX error messages

MMIMAN does not recognize the requested command class.

131 MML LOADING ERROR

The dynamic address data in the phased loading of the MML program

are not correct. Try again.

132 RESOURCE SHORTAGE

MMIMAN has been unable to reserve all necessary buffers in the

loading phase of an MML program. Try again.

133 MML LENGTH ERROR

The MML program on disk is too long for the area reserved for MML pro-

grams. Shorten the MML program on disk.

134 CURRENTLY NO SPACE FOR NEW MML

The RAM areas reserved for MML programs are being used by other

MML programs and it is not possible to load a new program. Try again.

135 TIME LIMIT EXCEEDED IN INQUIRY

MMIMAN has not received a response within the time limit from

IOMANA when inquiring about the MML program length data. Try again.

136 MESSAGE LENGTH ERROR

Message length error noticed by an individual process. NOTICE: THIS

IS NOT A DMX ERROR.

137 GIVEN BUFFER IS NOT DIVISIBLE BY EIGHT BYTES

The given buffer is not divisible by eight bytes that is required by algo-

rithm in use.

138 TQM still used by some WBTSs

The TQM is still used by some WBTSs.

139 THE COUNT OF IUB TRANSPORT QOS-ENABLED WBTS EXCEEDS

THE LICENSE IUB TRANSPORT QOS CAPACITY LIMIT

The count of Iub Transport QoS-enabled WBTS exceeds the license Iub

Transport QoS capacity limit.

140 THE STATE OF THE LICENSE IUB TRANSPORT QOS IS OFF

The state of the license Iub Transport QoS is off.

141 DCH&HSDPA, HSDPA OR HSUPA SHOULD NOT EXIST WHEN

DCH&HSPA EXISTSIf DCH & HSPA exists, DCH & HSDPA, HSDPA or HSUPA should not

exist.

142 HSDPA OR HSPA SHOULD NOT EXIST WHEN DCH&HSDPA

EXISTS

If DCH & HSDPA exists, HSDPA or HSPA should not exist.

143 ALLOCATE ERROR

An allocate error noticed by an individual process. For example,

process RAM area overflow: NOTICE: THIS IS NOT A DMX ERROR.

144 HSDPA OR HSUPA SHOULD NOT EXIST WHEN HSPA EXISTS

If HSPA exists, HSDPA or HSUPA should not exist.


17/667

DN987378 17


Id:0900d8058098a8ed

Confidential

145 STRINGENT SHOULD BE INCLUDED IN ONLY ONE PATH TYPE

FOR SAME AAL2 UP USAGE

For the same AAL2 up usage in a CoCo, stringent should be included

in only one path type.146 STRINGENT BI-LEVLE SHOULD BE INCLUDED IN ONLY ONE PATH

TYPE FOR SAME AAL2 UP USAGE

For the same AAL2 up usage in a CoCo, stringent bi-level should be

included in only one path type.

147 TOLERANT SHOULD BE INCLUDED IN ONLY ONE PATH TYPE FOR

SAME AAL2 UP USAGE

For the same AAL2 up usage in a CoCo, tolerant should be included in

only one path type.

148 STRINGENT OR STRINGENT BI-LEVEL DCH IS MISSING FROM

ROUTEStringent or stringent bi-level DCH is missing from route.

149 TOLERANT HSDPA IS MISSING IN BTS

Tolerant HSDPA is missing in BTS.

150 INVALID PARAMETER

A parameter noticed invalid by an individual process. NOTICE: THIS IS

NOT A DMX ERROR.

151 AAL2 UP USAGE AND AAL2 PATH TYPE COMBINATION IS ILLEGAL

AAL2UP usage and AAL2 PATH TYPE combination is illegal.

152 AAL2 PATH TYPES OF AN AAL2UPUSAGE ARE OVERLAPPED

Aal2 path types of an aal2upusage are overlapped.

153 LCS SUPPORT FOR ANCHORING CAN BE ENABLED ONLY WHEN

PARAMETER LCS FUNCTIONALITY IS ENABLED

LCS Support for Anchoring can be enabled only when parameter LCS

Functionality is enabled.

154 TIME LIMIT EXCEEDED IN MESSAGE WAITING

The time limit of message receiving has expired. Try again, check the

functioning of the partner program block.

155 LCS SUPPORT FOR ANCHORING CAN BE ENABLED ONLY WHEN

OPERATIONAL MODE IS RNC CENTRIC MODE

LCS Support for Anchoring can be enabled only when Operational

Mode of LCS is RNC Centric Mode.

156 SINTERSEARCHCONN PARAMETER SHOULD BE BETWEEN THE

SINTRASEARCHCONN AND SSEARCHRATCONN

The value of parameter SintersearchConn should be between the

parameters SintrasearchConn and SsearchRATConn.

157 LHOWINSIZEONINTERFERENCE MUST BE EQUAL TO OR

GREATER THAN RRINDPERIOD IN WBTS CELL

Window size for interference measurement to start LHOs must be equal

to or greater than Radio Resource Indication Period in WBTS cell.


18/667

18 DN987378


Id:0900d8058098a8ed

Confidential

DX error messages

158 LHOWINSIZEONINTERFERENCE CANNOT BE SHORTER THAN

PRX AND PTXTOTALREPORTPERIOD IN NB/RSXXX CELL

Window size for interference measurement to start LHOs must be equal

to or greater than reporting periods for the RTWP and the TCP mea-surements in NB/RSXXX cell.

159 MODIFICATIONS NOT ALLOWED

File modifications in the CMs are not allowed because either the active

or the passive CM is loading its files. Try again.

160 AAL2 UP USAGE AND PATH TYPE COVERAGE OVERLAPPED

AAL2 UP USAGE and Path Type Coverage overlapped.

161 IF DIRECTEDRRCFORHSDPALAYERENHANC IS DISABLED,

THERE CANNOT BE MORE THAN TWO LAYERS

If DRRC connection setup for HSDPA layer enhancements is disabled,

there cannot be more than two layers in one sector.

162 MISSING PRIMARY SPARE BCSU UNIT

PCU track configuration is asymmetrical and primary spare BCSU unit

definition is missing.

163 INVALID PRIMARY SPARE BCSU UNIT CONFIGURATION

PCU track configuration is asymmetrical and primary spare BCSU unit

configuration is invalid.

164 WRONG PRIMARY SPARE BCSU UNIT STATE

Wrong primary spare BCSU unit state.

165 POSITION NUMBER RESERVED

The position number is already in use. Change the position number.

166 FILE ERROR

An error has been found in the CM files while a command is being exe-

cuted. See the alarm 2060 CENTRAL MEMORY FILE ERROR, /Failure

Print-Outs, Alarm Print-Out Manual, 2.5/.Repeat the command.

167 GROUP CALL NUMBER WITH POSITION NUMBER

The given subscriber number is a group call number. Check the sub-

scriber number and use hunting group MML commands if necessary.

168 EXTENSION OF HUNTING GROUP

The subscriber belongs to a hunting group. Check the subscriber

number and use hunting group MML commands if necessary.

169 VIRTUAL CHANNEL CONNECTION TABLE IS FULL

The Virtual Channel Connection table is full.

170 DISK NOT UPDATED

No communication with the program block handling disk update, or

some other failure in disk update. See the alarm 1065 DISK UPDATE

FAILURE, /Disturbance Print-Outs, Alarm Print-Out Manual, 2.5/.

171 SPARE CM UNIT NOT UPDATED


19/667

DN987378 19


Id:0900d8058098a8ed

Confidential

The spare CM is not updated. See the alarm 1064 UNIT UPDATE

FAILURE, /Disturbance Print-Outs, Alarm Print-Out Manual, 2.5/.

172 VIRTUAL CHANNEL CONNECTION TABLE ENTRY ALREADY

EXISTSThe Virtual Channel Connection table entry already exists.

173 POSITION NUMBER VACANT

Check the position number.

174 VIRTUAL CHANNEL CONNECTION TABLE IS EMPTY

The Virtual Channel Connection table is empty.

175 VIRTUAL CHANNEL CONNECTION TABLE ENTRY DOES NOT

EXIST

The Virtual Channel Connection table entry does not exist.

176 INCORRECT FILE NUMBERThere is an incorrect or illegal file number in the counter correction

message. Repeat the command, check the parameters.

177 FILE CATALOG ERROR

An error has been detected in file addressing. The file in question is not

found in the catalog or the addressing is outside the catalog.

178 NONEXISTENT METER

The STATCO program block has received an incorrect value for one of

the following parameters in the meter interrogation MML command:

incorrect subscriber number, incorrect circuit group number, incorrect

charging zone number, incorrect meter type or class. Repeat thecommand, check the parameters.

179 IF NEIGHBORINGRNWElEMENT IS SET TO IHSPA ADAPTER,

NRNCVERSION SHOULD BE SET TO REL6

If the value of NeighboringRNWElement is set to IHSPA Adapter, the

value of NRncVersion should be internally set to Rel6.

180 DLDC FEATURE IS NOT IN USE IN BSC

DLDC feature cannot be enabled due to that there is no license installed

in BSC or license has been expired or license is in wrong state.

181 DLDC CAPACITY LICENSE EXCEEDED

Capacity of the DLDC license exceeded.

182 DLDC CANNOT BE ENABLED WITHOUT EGPRS ENABLED IN BTS

DLDC cannot be enabled if EGPRS feature is not in use in the BTS.

183 DLDC REQUIRES THAT TRACK CAN ONLY CONTAIN PCU2-TYPE

PCUS

DLDC cannot be enabled if the serving PCU and the whole track

contains other than PCU2-type PCUs.

184 FILE MARKED BAD

Operation has been directed to a disk file marked bad.

185 FILE LOCKED BY ANOTHER USER


20/667

20 DN987378


Id:0900d8058098a8ed

Confidential

DX error messages

File is locked. The user has no authority to read the file or write in it.

186 DATA VERIFY ERROR

The data on disk does not correspond to the data in memory. Writing on

the disk has failed. The disk formatting has failed.

187 ALTERNATE TRACK ERROR

No alternate track can be found for a track marked bad. Format an alter-

nate track.

188 DISK FULL

The disk is full.

189 NO INDEX PULSES

The disk controller does not detect disk index pulses. The disk drive is

faulty or the disk controller is faulty. Replace the disk drive. Replace the

disk controller.

190 NO SEEK COMPLETE

The read/write head of the disk drive does not move correctly. The disk

drive or the disk controller is faulty. Replace the disk drive. Replace the

disk controller.

191 WRITE FAULT

Writing on the disk fails. The disk drive or the disk controller is faulty.

Replace the disk drive. Replace the disk controller.

192 DRIVE NOT SELECTED

The disk drive has not been specified in the command.

193 TRACK 0 NOT FOUND

The disk or the disk controller is faulty. Replace the disk drive. Replace

the disk controller.

194 ID FIELD READ ERROR

There is a disk ID field read error. If the error is repeated, the disk drive

or the disk controller is faulty. Mark the track bad and format an alter-

nate track. Replace the disk drive. Replace the disk controller.

195 UNCORRECTABLE DATA ERROR

An error has been detected in the data to be stored on disk. The error

cannot be corrected by the disk controller. Set the read/write head on

the track again. If the error does not disappear, mark the track bad and

format an alternate track.

196 TARGET SECTOR NOT FOUND

The required block cannot be found on the disk. Mark the track on which

the block is located bad and format an alternate track.

197 DATA TRANSFER TIME-OUT

Data transfer between the disk controller and EDISKD has exceeded

the time limit. Replace the disk drive. Replace the disk controller.

Replace the DMADI plug-in unit.

198 ERROR BURST CORRECTED

The disk controller has detected and corrected incorrect data.


21/667

DN987378 21


Id:0900d8058098a8ed

Confidential

199 ADJG GAN RELATED PARAMETERS NOT SAME WITH RNC

PARAMETERS GANetwARFCN, GANetwNCC AND GANetwBCC

ADJG GAN related parameters are not the same with RNC parameters

GANetwARFCN, GANetwNCC and GANetwBCC.200 INVALID COMMAND

The disk controller does not accept the command it has received from

EDISKD. Replace the disk controller.

201 INVALID SECTOR ADDRESS

Wrong block number. The disk controller has been given a block

number outside the memory. The disk has not been initialized or the

disk drive is faulty. Initialize the disk. Replace the disk drive.

202 VOLUME OVERFLOW

EDISKD has given the disk controller a command, and the value of the

parameters is too high.

203 RAM FAILURE

The RAM of the disk controller is faulty. Replace the disk controller.

204 ROM FAILURE

The ROM of the disk controller is faulty. Replace the disk controller.

205 ECC HARDWARE FAILURE

There is an error in the correction logic of the disk controller. Replace

the disk controller.

206 GAN ADJG CAN EXIST ONLY WHEN GSM NEIGHBOUR CELL IS

NOT INCLUDED IN THE SYSTEM INFORMATION

GAN ADJG can exist only when GSM neighbour cell is not included in

the system information.

207 SCSI BUS IS BUSY

The SCSI bus is busy.

208 NO RESPONSE FROM DMA

Writing on the DMA has failed. Replace the DMADI unit.

209 SENSE DATA TRANSFER FAILED

EDISKD has not received error status from the disk controller. Replace

the disk controller.210 RESET UNSUCCEEDED

The disk controller reset has failed. Replace the disk controller.

211 SCSI BUS ERROR

The cable between the DMADI plug-in unit and the winchester disk con-

troller is faulty. Faulty disk controller. Replace cable. Replace disk con-

troller.

212 PARITY ERROR

There is a parity error in the data transfer between the disk controller

and the DMADI plug-in unit. Try again.

213 ILLEGAL ALTERNATE TRACK ACCESS


22/667

22 DN987378


Id:0900d8058098a8ed

Confidential

DX error messages

The addressing of an alternate track is incorrect or the disk operation

has been directed to an alternate track directly (without being first

directed to a track marked bad).

214 INVALID ALTERNATE TRACKThe track has already been marked as an alternate track for another

track. Choose another alternate track.

215 ALTERNATE TRACK NOT ALTERNATE

An alternate track has been marked for a bad track but no bit of the alter-

nate track is found in the ID field of the alternate track. Format the alter-

nate track again.

216 BAD TRACK AS ALTERNATE

An attempt is made to mark a bad track as an alternate track. Choose

another alternate track.

217 WINCHESTER DISK CHECKSUM ERROR

There is an error in the checksum of the disk directory. Initialize the disk.

218 EDISKD PROGRAM BLOCK BUSY

EDISKD is copying the disk; other application processes cannot

operate on the disk. Wait till the copying ends.

219 SEGMENT READ ERROR

An error has occurred during an attempt to read a segment.

220 SEGMENT WRITE ERROR

An error has occurred during an attempt to write in a segment.

221 ATTEMPT TO ACCESS ABOVE SEGMENT

An attempt has been made to access above segment.

222 ADJG BCCH ARFCN VALUE OUT OF RANGE

ADJG BCCH ARFCN value is out of range.

223 NO AVAILABLE UDP PORT FOR RESERVATION

No available UDP port for reservation.

224 NO SUCH I/O-DEVICE

An application program wants to operate on a device (process) which

does not exist on the given MSW level. Give the logical file an I/O device

that exists on the MSW level in question.

225 NO SUCH MSW CONNECTION

Application program wants the execution on a higher MSW level, which

does not belong to this branch of network (incorrect system identifier).

Check the system identifier of the I/O device and try again.

226 MSW TRANSMISSION ERROR

The NETCOM program block has failed to transmit data. Try again if

necessary.

227 LOGICAL FILE ALREADY EXISTS

Application program tries to create a logical file with a name which

already exists in the tables of IOMANA. Change the name of the logical


23/667

DN987378 23


Id:0900d8058098a8ed

Confidential

file to be created if you want to create a new file, or try to delete the old

one.

228 I/O-DEVICE CONNECTION FAILURE

Application program has chained too many logical files. Change the I/Odevice connection of the logical file.

229 LEG OF ONE OWNER ID EXCEEDED THE MAX NUMBER

Leg of one owner ID exceeded the max number.

230 NO SUCH LOGICAL FILE

Application program is trying to operate on a logical file that does not

exist. Give the right file number in the command.

231 NO FREE BUFFER

The system cannot provide a buffer needed to perform the task. Try

again after a while.

232 UNDEFINED COMMAND

Command has not been defined.

233 OVERLOAD IN I/O SYSTEM

There is currently no space available in the tables of IOMANA. Try again

after a while.

234 TOO DEEPLY NESTED

There are too many levels in the chain of logical file connections.

Change the connections.

235 OBJECT NOT FOUND

The object (usually another logical file) connected to the logical file is

not found.

236 LOGICAL FILE COUNT EXEEDED

An attempt has been made to create more logical files than the space

reserved for them allows. Remove unnecessary logical files.

237 PATTERN MATCH ENGINE OF AAL2 ACCELERATOR FPGA IS

BUSY

Pattern Match Engine of AAL2 Accelerator FPGA is busy.

238 ILLEGAL DEVICE

An attempt has been made to give a task to a device for which it is notallowed.

239 SPARE LOGICAL FILE ALREADY EXISTS

An attempt has been made to create a spare logical file for a logical file

which already has a spare logical file.

240 DEVICE NOT IN USE

The I/O device given in the task does not exist in the system or it is not

available. Check the working state of the I/O device.

241 PREVIOUS RESERVER INCORRECT


24/667

24 DN987378


Id:0900d8058098a8ed

Confidential

DX error messages

The reserver of the device has been given incorrectly in the command

used for releasing an I/O device or for changing the reserver. Check the

parameters of the MML command.

242 CHANGE IS NOT ALLOWEDChange is not allowed.

243 ILLEGAL COMMAND

The command cannot be executed because the device is in wrong

working state. Check the working state of the device and change it if

necessary.

244 DEVICE ALREADY RESERVED

An attempt was made to reserve a device that is already reserved. Try

again.

245 ILLEGAL UNIT

An attempt has been made to give the task to a computer unit which is

not found in the system.

246 CONTROLLED SWITCHOVER OF TBU NOT ALLOWED BECAUSE

TBU IS NOT SYNCHRONIZED TO ANY REFERENCE

CONTROLLED SWITCHOVER OF TBU NOT ALLOWED BECAUSE

TBU IS NOT SYNCHRONIZED TO ANY REFERENCE Controlled swi-

tchover of TBU is forbidden because TBUs are not synchronized to any

synchronization reference. Correct the situation before making switcho-

ver. You can do switchover using FCD parameter in switchover

command. Using FCD parameter under this circumstance may cause

significant disturbance in network element's internal message connec-tions. Worst case scenario is system restart.

247 NOT BIG ENOUGH BUFFER

An attempt to read from a device more data than the biggest possible

buffer can hold.

248 CONTROLLED TRANSITION TO SP-EX STATE NOT ALLOWED

BECAUSE REDUNDANT TBU IS NOT YET INITIALIZED

Controlled transition to SP-EX state is forbidden because redundant

TBU is not yet initialized. Typically, initialization takes only a few

seconds but under certain circumstances initialization can take up to

two minutes. You can execute state transition using FCD parameter in

state change command. Using FCD parameter shall cause issue where

redundant TBU is not ready for switchover and thus not fulfill definition

of 2N redundant unit. Under these circumstances, switchover of TBU

may cause significant disturbance in the network element's internal

message connections.

249 CONFIGURATION SET NOT ALLOWED

Disk configuration change is not allowed because e.g. both disks are

not in the normal working state.

250 NO PERMITTED

An attempt is made to delete a logical file created by another program-

block.


25/667

DN987378 25


Id:0900d8058098a8ed

Confidential

251 TIME-OUT ERROR IN I/O SYSTEM

Time limit set by the application program has expired before the I/O

program blocks have performed the task. Try again.

252 BUFFER ALLOCATION ERROR

The allocation of the buffer was not successful.

253 NO DATA TO WRITE

There is not data to write.

254 LOGICAL FILE RESERVED

The logical file is reserved. Try again.

255 UNSUCCESSFUL

A general negative response to an interrogation task. This is not an

actual error, but a negative answer to an interrogation, the alternative

being the status SUCCESS.256 PSN TUNNEL ALREADY EXISTS IN PSEUDO WIRE CONFIGURA-

TION

PSN tunnel already exists in Pseudo Wire Configuration.

257 INVALID SEMAPHORE NAME

The given semaphore name is not smaller than the number of sema-

phores defined by parameters.

258 SEMAPHORE PROTECTION VIOLATION

An attempt has been made to use the semaphore in a way that is not

allowed to the caller according to the protection parameters.

259 SEMAPHORE INITIALIZATION ERROR

An illegal attempt to initialize the semaphore. Only a non-negative value

can be initialized in the counter of the semaphore, and only when the

value already is non-negative.

260 ENTER REGION ERROR

The primitive ENTER_REGION is called in a situation in which there

already are calls in the critical region. The critical regions can not be

chained.

261 EXIT REGION ERROR

The primitive EXIT_REGION is called in a situation in which there areno calls in the critical region.

262 BUFFER SIZE ERROR

An attempt has been made to allocate a buffer of the size of zero or a

buffer bigger than the maximum theoretical buffer size.

263 BUFFER NOT AVAILABLE

Buffer allocation was not successful within the defined time limit.

264 NO FREE DESCRIPTOR SLOT

No free descriptor slot for the descriptor pointing to the buffer was found

in the area of the descriptor table reserved for the dynamic use of the

caller or defined process.


26/667

26 DN987378


Id:0900d8058098a8ed

Confidential

DX error messages

265 HANDLE ERROR

The buffer chain of the caller or defined process does not contain a

buffer with the defined handle.

266 ERROR IN MESSAGE LENGTH

The length of the message is not within the allowed range.

267 INVALID COMPUTER IDENTIFICATION ERROR

The logical address or preprocessor address in the computer field of the

message header is greater than the largest allowed address of this type.

268 COMPUTER DOES NOT EXIST

The combination of the index part in the logical address and the distri-

bution extent, in the computer field of the message header, the prepro-

cessor address or the physical computer corresponding to the relative

address referring to the pair of the own computer has not been defined.

269 NO MBIF

Message transmission requires a message bus, but the logical or

physical message bus that should be used in message transmission

according to the computer field in the header, has not been defined or

it does not exist.

270 HAND NOT REACHABLE

An incorrect message transmission attempt to a hand in a process

familyin which no error message transmission to the master is in use.

The hand is free or it has not been created (in a lightweight family), or

the focus in its message header and in the administration information

do not match (when the focus of process identifier is used in the family).

271 MESSAGE QUEUE OVERFLOW

An attempt has been made to send a message to a process the

message queue length of which, after the message transmission, would

exceed the maximum value defined when creating the process.

272 UNIT SEPARATED

The message transmission requires a message bus, but the message

bus interface unit used is not connected to the bus.

273 TRANSMIT FIFO NOT EMPTY

A message could not be sent to the message bus since the transmis-

sion buffer of the message bus interface unit is not empty. The reason

for the failure always is a hardware fault.

274 BUS SENDING FAILED

An attempt to send a message to the message bus has failed, e.g. since

the receiving computer does not exist or it is not connected to the

message bus. The reason for the failure can also be a hardware fault.

275 LAST BYTE FAIL

Message transmission to the message bus has failed at the point of the

last byte. The reason for the failure probably is a hardware fault.

276 TRANSMIT FIFO NOT EMPTIED, NO FAIL DETECTED


27/667

DN987378 27


Id:0900d8058098a8ed

Confidential

An attempt has been made to transmit a message to the message bus.

The transmission buffer of the message bus interface unit is not emptied

within the time limit, and no transmission fault has been detected.

277 BROADCAST FAILED An attempt has been made to send a message to the message bus with

a general group address. The transmission buffer of the message bus

interface unit has not been emptied within the time limit. When a general

group address is used, this error code is received instead of error codes

received in other transmission methods (BUS SENDING FAILED, LAST

BYTE FAIL and TRANSMIT FIFO NOT EMPTIED, NO FAIL

DETECTED).

278 NO ACKNOWLEDGEMENT TO REGISTERED MESSAGE

RECEIVED

No acknowledgement to a registered message is received from the

computer at the point of which this status appears in the acknowledge-

ment message.

279 REGISTERED MESSAGE NOT OK

A registered message has not reached the intended receiver in the

computer to which the message was addressed.

280 MESSAGE IS TOO LONG

The received message is longer than the defined size of the message

receiving area. In this case a part of the message is copied into the

receiving area, the rest of the message will be lost.

281 DYNAMIC DESCRIPTOR SLOT RANGE DEFINITION ERROR

The definition of descriptor slots reserved for dynamic use of the pro-

cessor is incorrect (CREATE_FIRST, CREATE_PROCESS). The

descriptor slots reserved for dynamic use and defined in the loading

module of the extension program are not a subset of descriptor slots to

be used dynamically by the process (EXECUTE_PROGRAM).

282 PRIORITY ERROR

The priorities defined for the process are not in the right order, or the

higher priority exceeds the maximum priority of the family.

283 INVALID PROCESS IDENTIFICATION

The defined process identification is not smaller than the number of pro-

cesses in the family (lightweight processes in the lightweight family).

284 PROCESS DOES NOT EXIST

The process of the given process identification does not exist. The exis-

tence of the master, instead of the lightweight hand, will be checked.

The killing or restarting of the process is possible only by using the

creation name of the process.

285 PROCESS ALREADY EXISTS

The process of the given process identification does exist. The exis-

tence of the master, instead of the lightweight hand, will be checked.

286 INVALID FAMILY IDENTIFICATION


28/667

28 DN987378


Id:0900d8058098a8ed

Confidential

DX error messages

The given family identification is not smaller than the number of process

families defined by parameters.

287 FAMILY DOES NOT EXIST ERROR

The process family of the given family identification does not exist.

288 FAMILY ALREADY EXISTS

The process family of the given family identification already exists.

289 MODULE NOT FOUND

The loading module given in the family record is not found in the primary

chain. The module is not loaded into the computer, or its name field is

incorrect.

290 MODULE TYPE ERROR

The loading module is not of the right type.

291 HAND GROUP COUNT CONFLICTThe family record and the loading module contain contradictory data on

the number of hand groups in the family.

292 FAMILY ENVIRONMENT AREA SIZE ERROR

The size of the family environment, calculated according to the data in

the family record and loading module, is at least 4 giga bytes.

293 NO ROOM FOR FAMILY ENVIRONMENT AREA

In the computer, there is no big enough, uniform, free memory space for

family or extension environment.

294 PROCESS COUNT ERROR

The number of processes in the family (lightweight processes in a light-

weight family) counted according to the information in the family record

is at least 65535.

295 LDT SIZE ERROR

The number of LDT descriptor slots counted according to the informa-

tion in the family record and loading module is smaller than 8192.

296 INVALID SELECTOR

The LDT selector in the family record or the selector of the descriptor,

set according to the descriptor parts in the loading module, is illegal.

297 DESCRIPTOR SLOT IN USE An attempt has been made to set a descriptor to a descriptor slot

already in use. All the descriptor slots, reserved for dynamic use, must

be free, as well.

298 DESCRIPTOR TYPE ERROR

An attempt has been made to set the segment descriptor to IDT, or such

a segment descriptor that is not accepted in the DMX environment. The

granularity bit may not be set (the maximum size of a segment to be set

is 1 megabyte), and the data segment may not be downwards increas-

ing.

299 LOCAL AREA ALLOCATION ERROR


29/667

DN987378 29


Id:0900d8058098a8ed

Confidential

There is not enough space in the family or extension environment for a

segment, for which a memory space is allocated in connection with the

setting of a descriptor. This fault occurs only if an incomplete correction

has been made in order to change the size of a segment.

300 FAMILY NOT EMPTY

An attempt has been made to delete the environment of a family that is

not empty. The deletion of a family environment is not possible if there

are processes in the family, or if a process in another family has

changed its name to one belonging to the family that is being deleted.

301 ILLEGAL ATTEMPT TO MODIFY DMXRTE PROCESS FAMILY

An attempt has been made to delete a DMX family or to modify it.

302 PROCESS FROZEN

An attempt has been made to send a message to a process that is

frozen due to an exceptional interruption caused by it.303 FREE EXTENDED MEMORY CHAIN ALREADY INITIALIZED

Free extended memory chain was already initialized when initialization

was asked from the operating system.

304 NO FREE TIME LIMIT RECORDS

There are no free time limit records in the computer.

305 TIME LIMIT TO RESET NOT FOUND

The time limit to be reset was not found.

306 TIME LIMIT TO READ NOT FOUND

The time limit to be read was not found.

307 NO ROOM TO WRITE TIME LIMIT WARMING DATA

The defined area is not sufficient for copying the time limits to be

warmed up.

308 NO FREE TNSDL TIMER RECORDS

There are no free TNSDL timer records in the computer.

309 TNSDL TIMER TO RESET NOT FOUND

The TNSDL timer to be reset was not found.

310 TNSDL TIMER TO READ NOT FOUND

The TNSDL timer to be read was not found.

311 NO ROOM TO WRITE TNSDL TIMER WARMING DATA

The defined space is not sufficient for copying the TNSDL timers to be

warmed up.

312 NO FREE WAKE UP RECORDS

There are no free wake-up records in the computer.

313 WAKE UP TO RESET NOT FOUND

The wake-up to be reset was not found.

314 NO FREE TIMER SERVICE RECORDS

There are no free timer service records in the computer.


30/667

30 DN987378


Id:0900d8058098a8ed

Confidential

DX error messages

315 TIMER SERVICE TO RESET NOT FOUND

The timer service to be reset was not found.

316 LOGICAL BUS NOT DEFINED

The logical bus, required for message transfer, has not been defined.

317 SORTER NOT DEFINED

The sorter, required when transferring messages, has not been defined.

318 NO ROOM FOR ACKNOWLEDGEMENTS TO REGISTERED

MESSAGE

When sending a registered message, the space reserved for computer

unit-specific acknowledgements was insufficient. The message-

sending primitive is, therefore, not collecting any acknowledgements.

319 FAMILY SERVICES IN USE

The use of the given primitive is not allowed in the process using thefamily services of the General On-Line Library (LIBGEN).

320 SETTING OF MESSAGE TRAFFIC MONITORING FAILED

Both monitoring records are reserved.

321 RESETTING OF MESSAGE TRAFFIC MONITORING FAILED

The process attempting to remove message traffic monitoring had not

set message traffic monitoring.

322 DEBUGGING SERVICE SET BY OTHER PROCESS

Setting the debugging service failed because some other process

already has set the service.

323 NO DEBUGGING SERVICE SET BY PROCESS

The process attempting to remove the debugging service was not the

one that had set it.

324 THE COMPUTER IS ALREADY STOPPED

Setting of debugging service failed because the computer has already

been stopped.

325 A PROCESS IS ALREADY STOPPED

Setting of debugging service failed because a process has already

been stopped.

326 INCORRECT FULL PROCESS ID

The primitive is directed to a process which is identified with a concise

process id. However, the name which the process is using at the

moment differs from the name given, thus the primitive does not recog-

nize it.

327 COMPUTER GROUP NOT FOUND

The record representing the computer group, and the data of which the

operating system primitive was to read or modify, cannot be found in the

group address table.

328 COMPUTER NOT FOUND FROM GROUP


31/667

DN987378 31


Id:0900d8058098a8ed

Confidential

The computer cannot be found in the group the caller of the operating

system primitive had given.

329 NO ROOM FOR GROUP RECORD

There is no room for the group record in the memory space it was to becopied.

330 GROUP ADDRESS TABLE FULL

There is no room for a new or a bigger record in the group address table.

331 MESSAGE ROUTING TABLE FULL

There is no room for a new record in the message routing table.

332 NOT LOGICAL ADDRESS

A computer address that was to be logical is not logical.

333 NOT PHYSICAL ADDRESS

A computer address that was to be physical is not physical.

334 WRONG MESSAGE

The operating system primitive received a wrong message.

335 NO ANSWER

The operating system primitive received no answer.

336 NOT DONE

The service that was asked by a call of an operating system primitive

was not executed.

337 PSEUDO WIRE (PW) ALREADY EXISTS IN CONFIGURATION

Pseudo Wire (PW) already exists in Pseudo Wire Configuration.

339 ADDRESS RANGES OVERLAP

The address range defined by the post office overlaps with an address

range defined earlier.

340 INVALID POST DISTRICT INDEX

The district index of the post office is invalid.

341 GENERAL GROUP DEFINITION ERROR

Error in general group definition: both general groups have not been

defined or own computer cannot be found in either group.

342 ILLEGAL CALL PARAMETER USED IN SYNCHRONOUS OR ASYN-CHRONOUS INTERFACE

Illegal call parameter is used in synchronous or asynchronous interface.

343

Requested DSP service type is currently disabled in some or all DSP

service pools.

344 VMGW DATA CORRUPTION IN BC2PRB

VMGW data corruption in BC2PRB.

345 VMGW DATA CORRUPTION IN HTAPRB

VMGW data corruption in HTAPRB

346 SISU NOT FOUND


32/667

32 DN987378


Id:0900d8058098a8ed

Confidential

DX error messages

SISU is not found.

347 SISU IS ALREADY BLOCKED

SISU LB is already in blocked state.

348 SISU IS ALREADY WORKING

SISU LB is already in working state.

349 MDCR OR UBRSHARE CANNOT BE UNSPECIFIED FOR UBR PLUS

VP OR VC

MDCR or UBRSHARE cannot be unspecified for UBR plus VP or VC.

350 TARGET IS NOT A VIRTUAL UNIT

The target is not a virtual unit.

351 TARGET INDEX INVALID

The target index is invalid.

352 PARENT UNIT INVALID

The parent unit is invalid.

353 TARGET AND CHILD NOT MAPPED

Target and child is not mapped.

354 CHILD INDEX INVALID

Child index is invalid.

355 LOCAL RELATED UNIT INVALID

Local related unit is invalid.

356 IP ADDRESS EXISTS IN VLAN INTERFACE

IP address exists in VLAN interface.

357 PSN TUNNEL CANNOT BE FOUND IN PSEUDO WIRE CONFIGURA-

TION

The Packet Switched Network (PSN) tunnel cannot be found in Pseudo

Wire Configuration.

358 PSEUDO WIRE CANNOT BE FOUND IN PSEUDO WIRE CONFIGU-

RATION

Pseudo Wire (PW) cannot be found in Pseudo Wire Configuration.

359 PSEUDO WIRE IS NOT IN DISABLED STATE AS IT SHOULD BE

Pseudo Wire (PW) is not in disabled state as it should be.

360 PSN TUNNEL IS NOT EMPTY AND INCLUDES PSEUDO WIRE(S)

The Packet Switched Network (PSN) tunnel is not empty and includes

Pseudo Wire(s).

361 ACTIVATE ASSOCIATION BY GIVING PRIO=YES WITH THE OYH

COMMAND

The state of an M3UA association in override mode can be changed

only if PRIO=YES for the association.

362 ILLEGAL AAL2 PATH TYPE COMBINATION FOR HSXPA VCC

UNDER ROUTE


33/667

DN987378 33


Id:0900d8058098a8ed

Confidential

Within one ATM route, HSxPA VCC which has either only tolerant type

or all AAL2 path types should be found.

363 VALUE OF FASTUETHRESHOLDBCC MUST BE HIGHER THAN

VALUE OF FASTUECANCELBCCThe value of the parameter FastUEThresholdBestCellChange must be

higher than the value of FastUECancelBestCellChange.

364 APS LOGIC INITIALIZATION ERROR

APS logic for protection group in interface unit cannot be initialized. This

can happen, if spare unit is removed from the configuration and created

back again while there is/are protection group(s) configured in the inter-

face unit. The spare interface unit is not allowed to start up in this case.

To initialize the protection group successfully, the working unit must

also be restarted. Also, if there is a protection group in interface unit and

spare unit is removed and created back again, the SET port is automat-

ically selected in creation of spare unit so that internal SET ports in pro-

tected interface units match with each other (first SET in WO unit - first

SET in SP unit and so on). If ports were not matching earlier, the SDH

fiber cable in spare unit must be reconnected to port which is matching

with working unit.

365 MISU IS NOT FOUND

MISU is not found.

366 LIBRARY PROGRAM IS NOT AVAILABLE

Library program is not available.

367 DSP BOOT FILE CONSISTENCY ERROR OR CRC CHECKSUM

FAILURE WAS DETECTED WHEN ATTEMPTING TO START UP THE

DSP

DSP boot file consistency error or CRC checksum failure was detected

when attempting to start up the DSP.

368 CONFIGURATION NOT ALLOWED TO PRIMARY SPARE UNIT

Configuration not allowed to primary spare unit.

369 DMPG SWITCH IS ONGOING

DMPG switch is ongoing.

370 ADVANCED IN SPEECH ANNOUNCEMENTS ARE NOT SUP-

PORTED, NO ENOUGH MEMORY EXISTS IN VANU UNIT(S) Advanced in speech announcements are not supported, no enough

memory exists in VANU unit(s).

371 PW PACKET PAYLOAD SIZE IS TOO BIG

PW packet payload size is too big, for example, the frame amount of

timeslots is more than 512.

372 THE LICENSE OF IBTS SHARING IS OFF

The license of IBTS Sharing is off.

373 IF MAXBITRATENRTMACDFLOW IS 13440KBPS, THERE MUST BE

ONE SPDSCHCODESET WHICH CONTAINS 15 CODE SET


34/667

34 DN987378


Id:0900d8058098a8ed

Confidential

DX error messages

If MaxBitRateNRTMACdflow is 13440kbps, there must be one SPD-

SCHCodeset which contains 15 code set.

374 HSDPA14MBPSPERUSER AND RELEVANT LICENSE MUST BE

ENABLED BEFORE SETTING MAXBITRATENRTMACDFLOW TO13440KBIT/S

Before setting MaxBitRateNRTMACdflow to 13440kbit/s,

HSDPA14MbpsPerUser and relevant license must be enabled.

375 RECEIVED BOOT MESSAGE WITH INCORRECT SEQUENCE

NUMBER FROM DSP

The sequence number in boot packet acknowledgement message from

DSP is not what is expected.

376 NO ANSWER RECEIVED FROM RRA MASTER IN TIME

Timer for waiting an answer from rra master has expired, and no answer

has been received.377 CELL SERVICE OR CCH SETUP FAILED IN L3; FAILURE SOURCE

COULD BE RRA, BRM, NBAP, NRM, RC3 or L2

Cell service or CCH setup failed in L3. Failure source could be RRA,

BRM, NBAP, NRM, RC3 or L2.

378 CELL STATE NOTIFICATION ERROR IN L3; FAILURE SOURCE

COULD BE RRA, BRM, RNC_RAB_COMMON OR L2

Cell state notification error in L3. Failure source could be RRA, BRM,

RNC_RAB_COMMON or L2.

379 ENCODING OF EXTERNAL INTERFACE MESSAGE FAILED IN L3

Encoding of external interface message failed in L3.

380 CCH RESERVATION RELATED BRM MESSAGE WAITING TIME

OUT IN L3 RRA PRB

CCH reservation related BRM message waiting time out in L3 RRA

PRB.

381 CELL/CCH RESOURCE RESERVATION RELATED MESSAGE

WAITING TIME OUT IN L3 RRA PRB

Cell/CCH resource reservation related message waiting time out in L3

RRA PRB.

382 CCH RESERVATION RELATED MESSAGE WAITING TIME OUT IN

L3 RRA PRB

CCH reservation related message waiting time out in L3 RRA PRB.

383 INTERNAL ERROR IN CELL/CCH HANDLING L3 RRA-CMA HAND

Internal error in Cell/CCH handling L3 RRA-CMA hand

384 CELL SETUP OR COMMON TRANSPORT CHANNEL RESERVA-

TION-RELATED ERROR NOTICED IN NBAP

Cell Setup or Common Transport Channel reservation-related error

noticed in NBAP.

385 CELL OR COMMON TRANSPORT CHANNEL RESERVATION-

RELATED ERROR NOTICED IN NBAP


35/667

DN987378 35


Id:0900d8058098a8ed

Confidential

Cell or Common Transport Channel reservation-related error noticed in

NBAP.

386 CELL OR COMMON TRANSPORT CHANNEL RESERVATION-

RELATED ERROR NOTICED IN NBAP PRBCell or Common Transport Channel reservation-related error noticed in

NBAP.

387 JITTER BUFFER SIZE IS TOO SMALL

Frame number of PW is bigger than jitter buffer size. Jitter buffer size

must be equal or more than frame number of the same PW.

388 PW CONFIGURATION IS NOT UPDATED TO ETIP PLUG-IN UNIT

The PW configuration is not updated to the ETIP plug-in unit due to that

the unit or connection to it is not working.

389 PW CONFIGURATION SAVED ON OMU FILE, BUT NOT IN ETIP

UNIT

The PW configuration is saved on the OMU file, but not in the ETIP unit

due to that the unit or LAPD connection to it is not working. The PW con-

figuration is uploaded to the unit automatically after the ETIP unit is

working.

390 NSVCS UNDER ONE NSE MUST HAVE SAME PORT NUMBER

Every NSVC created under one NSE shall have the same local UDP

port.

391 IBTS SHARING CAN BE ENABLED ONLY WHEN THE VALUE OF

NEIGHBOURINGRNWELEMENT IS ADA

IBTS Sharing can be enabled only when the value of NeighbouringRN-

WElement is ADA.

392 IBTS SHARING CAN BE SUPPORTED ONLY WHEN CELL DCH

RELOCATION IS SUPPORTED

IBTS Sharing can be supported only when cell DCH relocation is sup-

ported.

393 IPBASEDROUTEIDIUR MUST BE DEFINED IF NEIGHBOURINGRN-

WELEMENT IS ADA

If NeighbouringRNWElement is ADA, IPBasedRouteIdIur must be

defined.

394 ONLY ONE PLMN ID SHOULD BE CONFIGURED FOR THOSE IURS

WHICH SUPPORT IBTSSHARING

Only one PLMN ID should be configured for those IURs which support

IBTSSharing.

395 PLMNID OF IURS WHICH SUPPORT IBTS SHARING MUST BE THE

SAME

PLMNId of IURs which support IBTS Sharing must be the same.

396 THE MAX NUMBER OF IUR OBJECTS NEIGHBORING RNC IS 32

The number of IUR objects neighboring RNC exceeded the limit.

397 THE RELATION BETWEEN SRNC AND ADA CANNOT BE DEFINEDBOTH IN CONTROLLERIDPAIR AND IUR


36/667

36 DN987378


Id:0900d8058098a8ed

Confidential

DX error messages

The relation between SRNC and ADA cannot be defined both in Con-

trollerIdPair and IUR.

398 ONE ADA CAN BE USED BY ONLY ONE RNC FOR IBTS SHARING

One ADA can be used by only one RNC for IBTS Sharing.

399 MAXBITRATEDLPSNRT SHOULD BE BIGGER THAN OR EQUAL TO

INITIALBITRATEDL

MaxBitRateDLPSNRT should be bigger than or equal to InitialBitRat-

eDL.

400 INITIALBITRATEDL SHOULD BE BIGGER THAN OR EQUAL TO

MINALLOWEDBITRATEDL

The value of InitialBitRateDL should be bigger than or equal to the value

of MinAllowedBitRateDL.

401 MAXBITRATEULPSNRT SHOULD BE BIGGER THAN OR EQUAL TO

INITIALBITRATEUL

MaxBitRateULPSNRT should be bigger than or equal to InitialBitRa-

teUL.

402 INITIALBITRATEUL SHOULD BE BIGGER THAN OR EQUAL TO

MINALLOWEDBITRATEUL

The value of InitialBitRateUL should be bigger than or equal to the value

of MinAllowedBitRateUL.

403 FMC IS STILL BEING USED BY THE VCEL

FMC is still being used by the VCEL.

404 HOP IS STILL BEING USED BY THE VCELHOP is still being used by the VCEL.

405 WRAB IS STILL USED BY THE VCEL

WRAB is still used by the VCEL.

406 NO ANSWER RECEIVED FROM RRA CMA IN TIME

Timer for waiting an answer from rra cma has expired, and no answer

has been received.

407 INVALID EPD VALUE

EPD value is invalid.

408 EACH WCDMA CELL CAN HAVE ONLY ONE GAN-SPECIFIC INTER-RAT NEIGHBOR CELL (ADJG)

Each WCDMA cell can have only one GAN-specific inter-RAT neighbor

cell (ADJG).

409 IBTSRNCMAPPING CAN ONLY BE SET TO NOT USED IF NEIGH-

BORINGRNWELEMENT IS 1 (3G-WCDMA RNC)

When NeighboringRNWElement is 1 (3G-WCDMA RNC), IBTSRNC-

Mapping can only be set to not used.

410 INVALID IBTS SHARING CONFIGURATION

IBTSSharingRncId or one IUR whose IBTSRNCMapping must be

defined. RelocationSupport of more than one IU CS and IU PS is sup-ported when the value of CSVoiceServiceSupport is IBTS Sharing.


37/667

DN987378 37


Id:0900d8058098a8ed

Confidential

411 UNIT POOL DATABASE ALREADY CONTAINS A POOL WITH THE

GIVEN POOL ID

Unit pool database already contains a pool with the given pool ID.

412 THE REQUESTED POOL DOES NOT EXIST IN THE UNIT POOLDATABASE

The requested pool does not exist in the unit pool database.

413 THE GIVEN UNIT IS ALREADY ASSIGNED TO THE POOL

The given unit is already assigned to the pool.

414 THE REQUESTED UNIT IS NOT ASSIGNED TO THE POOL

The requested unit is not assigned to the pool.

416 THE MAX COUNT OF IUR WHOSE NEIGHBOURINGRNWELEMENT

IS 1 SHOULD NOT EXCEED 1

The max count of IUR whose NeighbouringRNWElement is 1 (3GWCDMA RNC) should not exceed 1.

417 CALLER OF LIBGEN FUNCTION UNAUTHORIZED

The prioritized functions of LIBGEN are called by an unauthorized

process.

418 PARAMETERS OF LIBGEN FUNCTION ERRONEOUS

The parameters to be transmitted to the LIBGEN function are incorrect.

419 RESOURCES RESERVED BY LIBGEN FUNCTION INSUFFICIENT

The resources to be reserved in the LIBGEN function are insufficient.

420 USE OF LIBGEN FUNCTION ERRONEOUS

The LIBGEN function is called incorrectly.

421 MESSAGE USED BY LIBGEN FUNCTION INVALID

The message to be transmitted to the LIBGEN function is incorrect.

422 HAND USED BY LIBGEN FUNCTION IS FREE INSTEAD OF BEING

RESERVED

The hand to be transmitted as a parameter to the LIBGEN function is no

longer reserved although the function is for reserved hands.

423 NO REAL HAND RESERVATION TIME-OUTS

The LIBGEN function HAND_RESERVATION_TIMEOUT returns this

error code when the routine is called unnecessarily (=time limit of hand

reservation has not expired).

424 TIME-OUT IN ENTERING MESSAGE REMOTE PROCEDURE CALL

An error code returned by the call of the

MSG_RPC_THROUGH_WINDOW routine when the service is not

received at all within the defined period.

425 TIME-OUT IN RECEIVING ANSWER MESSAGE TO REMOTE PRO-

CEDURE CALL

An error code returned by the MSG_RPC_THROUGH_WINDOW

routine when in the routine, no answer message is received after the

message transmission within the defined time limit.


38/667

38 DN987378


Id:0900d8058098a8ed

Confidential

DX error messages

426 GIVEN WINDOW NOT FOUND IN MSG_RPC_THROUGH_WINDOW-

ROUTINE

The flow control window given as a parameter to the

MSG_RPC_THROUGH_WINDOW routine is not found.427 SERVICE NOT SUPPORTED

The service is not supported in this network element.

428 UNIT POOL WAS DELETED BECAUSE THERE ARE NO UNITS CON-

NECTED TO THIS POOL

Unit pool was deleted because there are no units connected to this pool.

429 FAILED TO GET RUNNING BUILD ID WITH BOSLIB

Failed to get running build ID. The BOSLIB library has returned error.

430 FAILED TO GET BUILD INFO FROM SOMAFI WITH SWFLIB

Failed to get build info from SOMAFI. The SWFLIB library has returnederror.

431 THE DEFAULT BUILD IN SOMAFI IS INVALID (NOT FOUND OR

CORRUPTED)

The default build in SOMAFI could not be found correctly. The reason

could be that SOMAFI is corrupted or patched wrongly etc.

432 FAILED TO SET DEFAULT BUILD IN SOMAFI

Failure when setting the default build in SOMAFI. The service has

returned the error.

433 CHANGING OF THE SW BUILD HAS FAILED

The changing of the SW build has failed. System is not running with the

requested SW build.

434 ILLEGAL MAC ADDRESS

The MAC address is illegal.

435 NE3S LOAD MODULE ERROR

Load module does not exist, or an error has occurred while loading load

module from disk.

436 LETGR UPDATE FAILURE

The update of a configuration change to the LETGR unit has failed.

Files in the other units have been updated.437 NPU UPDATE IS FAILED

The update of a configuration change to the NPU unit has failed. Files

in the other units have been updated.

438 MOCN CANNOT BE ACTIVATED BECAUSE THE MOCN LICENSE

STATE IS CONFIG/OFF INSTEAD OF ON

MOCN cannot be activated, because the MOCN license state is CON-

FIG/OFF instead of ON.

439 COMMON PLMN ID IS NOT ALLOWED TO BE MODIFIED IF

RELATION TO WCEL OBJECT EXISTS


39/667

DN987378 39


Id:0900d8058098a8ed

Confidential

Common PLMN ID is not allowed to be modified if relation to WCEL

object exists.

440 SUM OF OPERATORWEIGHT UNDER IUO OBJECTS MUST BE 0

OR 100Sum of OperatorWeight under IUO Objects must be 0 or 100.

441 NULLNRIFORCSPOOL OF IUOPERATOR MUST BE UNIQUE WITH

OTHERS WHEN FLEX IU OR MOCN IS ACTIVATED

NullNRIForCSPool of IuOperator must be unique with others, when

Flex IU or MOCN is activated.

442 NULLNRIFORPSPOOL OF IUOPERATOR MUST BE UNIQUE WITH

OTHERS WHEN FLEX IU OR MOCN IS ACTIVATED

NullNRIForPSPool of IuOperator must be unique with others, when Flex

IU or MOCN is activated.

443 NRILENGTHFORCSCN OF ALL IUOPERATOR MUST BE SAMEWHEN FLEX IU OR MOCN IS ACTIVATED

NRILengthForCSCN of all IuOperator must be same, when Flex IU or

MOCN is activated.

444 NRILENGTHFORPSCN OF ALL IUOPERATOR MUST BE SAME

WHEN FLEX IU OR MOCN IS ACTIVATED

NRILengthForPSCN of all IuOperator must be same, when Flex IU or

MOCN is activated.

445 IP ADDRESS OF IPD UNIT IS ALREADY USED BY OTHER POOL

IP address of IPD unit is already used by other pool.

446 PRIMARY UNIT ALREADY EXISTS IN THE POOL

Primary unit already exists in the pool.

447 SECONDARY UNIT ALREADY EXISTS IN THE POOL

Secondary unit already exists in the pool.

448 UNIT IS ALREADY ASSIGNED TO THE OTHER POOL

Unit is already assigned to the other pool.

449 ILLEGAL MODIFICATION OF PRIMARY OR SECONDARY UNIT

Illegal modification of primary or secondary unit.

450 UNIT DELETION IS DENIED DUE TO OTHER ONGOING DELETIONUnit deletion is denied due to other ongoing deletion.

451 SECONDARY UNIT HAS BEEN DELETED FROM THE POOL

Secondary unit has been deleted from the pool.

452 PRIMARY UNIT HAS BEEN DELETED FROM THE POOL

The primary unit has been deleted from the pool.

453 ORDINARY UNIT HAS BEEN DELETED FROM THE POOL

Ordinary unit has been deleted from the pool.

454 PRIMARY UNIT OF THE POOL HAS BEEN MODIFIED

The primary unit of the pool has been modified.


40/667

40 DN987378


Id:0900d8058098a8ed

Confidential

DX error messages

455 SECONDARY UNIT OF THE POOL HAS BEEN MODIFIED

Secondary unit of t

General Error Messages of System.pdf

Documents

Transcript of General Error Messages of System.pdf