78.10 Error Messages and Advisories

78.10.1 Error Messages

 
F01:
COMMUNICATION WITH DISPLAYER IN <xxxxx> IMPOSSIBLE
F02:
WRITING ACCESS FAILED (START ADDRESS = <xxxx>H:<xxxx>H)
F03:
NO TABLE DEFINITION EXISTS WITH THIS NAME
F04:
OVERFLOW OF DEFINITION TABLE IN AMO
F05:
OVERFLOW OF RESIDENT DEFINITION TABLE
F06:
INDEX ILLEGAL
F07:
DATABASE ACCESS FAILED
F08:
DEFINITION REJECTED
F09:
ADDRESS TABLE NOT FOUND
F10:
DISPLACEMENT ILLEGAL
F11:
INPUT FOR "UNIT", "NO", "VAL" INCONSISTENT
 
The number of values specified for "VAL" must be entered in the parameter "NO"; this helps detect input errors. The values specified for "VAL" may not exceed the maximum length defined by the parameter "UNIT".
F12:
DATABASE TABLE DOES NOT EXIST
F13:
LTG NUMBER EXCEEDS <xx>H
F14:
LTU NUMBER EXCEEDS <xx>H
F15:
INPUT FOR "TYPE" AND "SEL" INCONSISTENT
 
For example, the input TYPE=CPB is inconsistent with SEL=DTI
F16:
FILE "<xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>" ALREADY ASSIGNED
 
In order to assign a different file, the AMO must be terminated and restarted.
F17:
CREATION OF FILE FAILED WITH STATUS <xxxx>H
 
Status output is the same as FAM call.
F18:
OPENING OF FILE FAILED WITH STATUS <xxxx>H
 
Status output is the same as FAM call.
F19:
SEEKING IN FILE FAILED WITH STATUS <xxxx>H
 
Status output is the same as FAM call.
F20:
READING FROM FILE FAILED WITH STATUS <xxxx>H
 
Status output is the same as FAM call.
F21:
WRITING TO FILE FAILED WITH STATUS <xxxx>H
 
Status output is the same as FAM call.
F22:
CLOSING OF FILE FAILED WITH STATUS <xxxx>H
 
Status output is the same as FAM call.
F23:
NO FILE ASSIGNED
 
...therefore no hard disk backup area can be used.
F24:
NECESSARY PARAMETER VALUE MISSING
F25:
LINE NUMBER EXCEEDS <xxxx>H
F26:
CIRCUIT ADDRESS UNPLAUSIBLE OR LINE DOES NOT EXIST
 
The address used for addressing the memory was implausible / invalid.
F27:
FLEX-ADDR HIERARCHY NOT SUFFICIENT FOR ADDRESSING
 
Conversion error due to flexible addressing.
F28:
<xxxxx> INDEX EXCEEDS <xx>H
 
Access index to high for LINK or LINE paths
F29:
FILE "<xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>" ALREADY EXISTS
 
A file with the same name already exists on the hard disk and will NOT be overwritten.
Enter a new name.
F30:
ALLOCATION OF TEMPORARY SEGMENT FAILED; NOT ENOUGH MEMORY AVAILABLE
 
The temporary segment for intermediate storage of the BCASA- data could not be created in the system. There is not enough free main storage available.
OpenScape 4000 V10, Volume 1: AMO Descriptions, Service Documentation, Issue 5, ID: P31003H31A0S107057620
 © 09/2025 Mitel Networks Corporation. -  All rights reserved.
 Mitel and the Mitel logo are trademarks of Mitel Networks Corporation. Unify and associated marks are trademarks of Unify Software and Solutions GmbH&Co. KG. All other trademarks herein are the property of their respective owners.