User Manual

Siemens Building Technologies VISONIK DCS Functions and System Messages VVS18 CM2U8567E / 04.1999
Landis & Staefa Division System Messages --- DCS Messages 3-43
Ennn=vvvv! uuuu.xxxx, box@=zzzz
PNAM 00:00:00
Ennn=vvvv! uuuu.xxxx, box@=zzzz
->MSGDEV (M.xMER)
uuuu represents one of the following file names:
uuuu=IM Process image
uuuu=DM Data processing
uuuu=REA Reaction register
nnn is an error number.
vvvv is one of the error number's related texts.
xxxx specifies the segment number of the uuuu file in which the error
occurred.
zzzz specifies the relative offset in the segment xxxx where the error has
been detected.
All programs which have access to the process image IM, the data processing files DM
or the reaction register REA can initiate the above message if these files contain some
inconsistencies or errors.
The following errors can occur:
Error Error text group
number
-------------------------------------------------------------
1 RP too small! (RP lower than *M@) A
2 RP too large! (RP higher than WP) A
3 First backlink not zero A
4 Forward/Backwardlink wrong A
5 WP not at the end of last record A
6 forward record link behind EP A
7 odd record link A
8 BOX and recordlength not corresponding A
9 TA order wrong C
10 insert queue clutch failure A
11 index map clutch failure A
12 2 equal TA in sequence C
20 Illegal Seg# given by B$BSG C
21 Dataset full, generation not completed B
22 Dataset full, generation not completed B
23 Queue TA already in xM, Queue TA deleted BC
30 Delete BOX: BOX not found C
100 AP wrong, corrected A
101 RP wrong, corrected A
102 1st backlink unequal zero, corrected A
110 WP out of limits, segment cleared A
111 Negative link, segment partially cleared A
112 too large link, segment partially cleared A
113 link/backlink unequal, segment partially cleared A
120 WP not at end of chain, corrected A
130 Record twice in dataset, 2nd one deleted BC
131 Order of records wrong, segment partially cleared BC
Group A
All these errors indicate some serious DC Server problem (disk, memory fault, power
supplies, etc.). These errors are corrected automatically, but sometimes the corrections
cause a loss of data. This is noted in the associated message. Data are only lost from
segments whose numbers appear in the respective messages.
In other cases the system attempts to rectify an error through an automatic boot. Since
the above listed messages very often have a delayed printout after the boot, there is, in
this special case, an additional printout given BEFORE the automatic boot:
"uuuuxxxx corrupted, AAA2:VIMS$ Error (octal) = nnnn"
Explanation