RRN 06718 RECONFIGURE-RACK

KELYKA04

Message Triggering Condition

Response in case of successful / unsuccessful result of the execution, on operator request, of the following MMC-command:
CRN 03405 ADD-RACK

Report Layout

 SWA-BB DEFENCE
    (A).......................                   (B).................
                                 (C)........................... (D) (E)
    -----------------------------------------------------------------
        PHYSICAL ROW      = (1)
        PHYSICAL RACK     = (2)
        RACK TYPE         = (3)
        RACK TYPE VERSION = (4)
        LOGICAL RACK      = (5)
        CLOCK ROW         = (6)
        CLOCK RACK        = (7)
        ==> (8)
            (9) (10) (11)/(12)
        DUT RESULT  = (13)
        DEBUG INFORMATION :
        FMM ID      = (14)
        ERROR POINT = (15)
        DB COM ID = (16)
        DB COM OP = (17)
        DB REL ID = (18) - (19)
        DB LCE ID = (20)
        DBCS-ERROR = (21)
        IO-ERROR = (22)
        DBSS-ERR/WARN = (23)
        DBCS-WARNING = (24)
        DB STATUS ED2 = (25)/(26)
        => CANCEL OR CONFIRM VIA THE GO COMMAND
           FOR SEQUENCE NUMBER = (27)
  REPORT REFERENCE NUMBER = 6718

Parameter Identification

Par. No. Meaning Remarks
(A) Command name
(B) Main execution result
(C) Result part type
(D) Result part number
(E) Continuation indicator
(1) Physical row number of the BB rack
(2) Physical rack number of the BB rack A, B, C, D, E, F, G, H, J, K, L,
M, P, R, S, T, U, V, W, Z
(3) Rack type of the BB rack
(4) Rack type version of the BB rack
(5) Logical rack number of the BB rack
(6) Clock row number of the BB rack
(7) Clock rack number of the BB rack
(8) Global result message see Evaluation
(9) Additional error info see Evaluation
(10) Row/Rack indication for clock position see Evaluation
(11) Minimum value that is expected see Evaluation
(12) Maximum value that is expected see Evaluation
(13) Database Update Transaction result message see Evaluation
(14) FMM identity where error occured
(15) Error point indicator where fault occurred in
the code
(16) Database data manipulation language command type
DELETE delete
GET get
MODIFY modify
STORE store
(17) Database data manipulation language option type
IN SEQUENCE in sequence
NO OPTION no option
(18) Database relation identity
(19) Database relation name
(20) Database logical control element identity
(21) Database error specification
(22) Input/output error specification
(23) Database security system error/warning specification
(24) Database warning specification
(25) Database status edition 2 main code see SI 057
(26) Database status edition 2 sub code see SI 057
(27) Sequence number

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(8) A BB RACK CAN NOT BE ADDED IN A NB ROW . . . . . . A
(8) ADDITION OF THIS TYPE OF BB RACK IS NOT SUPPORTED A
(8) COMMAND CANCELLED BY THE OPERATOR . . . . . . . . A
(8) DATA UPDATE TRANSACTION (DUT) IS NOT ACCEPTED . . A
(8) DB ERROR . . . . . . . . . . . . . . . . . . . . . B
(8) FOR THIS TYPE OF RACK A CLOCK POSITION MUST BE GIVEN A
(8) FOR THIS TYPE OF RACK NO CLOCK POSITION SHOULD BE GIVEN A
(8) MIXING OF XLK_GSN AND XLK_PSN RACKS IS NOT ALLOWED A
(8) NO MESSAGE RECEIVED FROM ICF-FMM TO CONFIRM THE ACTION A
(8) SW INCONSISTENCY . . . . . . . . . . . . . . . . . B
(8) THE CLOCK PROVIDING RACK IS MISSING . . . . . . . A
(8) THE CLOCK ROW/RACK POSITION IS ALREADY OCCUPIED . A
(8) THE GIVEN CLOCK RACK POSITION IS WRONG . . . . . . A
(8) THE GIVEN CLOCK ROW POSITION IS WRONG . . . . . . A
(8) THE GIVEN CLOCK ROW/RACK POSITION IS WRONG . . . . A
(8) THE LOGICAL RACK NUMBERING IS NOT ACCORDING THE RULES A
(8) THE LOGICAL RACK NUMBERING IS NOT UNIQUE . . . . . A
(8) THE PHYSICAL POSITION IS OCCUPIED BY ANOTHER BB RACK A
(8) THE VALUE FOR THE LOGICAL RACK NUMBER IS OUT OF RANGE A
(8) THIS ROW NUMBER IS RESERVED BY A PERIPHERAL RACK . A
(8) TIMEOUT OCCURED BEFORE THE OPERATOR CONFIRMED THE ACTION A
(13) DUT ABNORMAL END . . . . . . . . . . . . . . . . . B

Action Description

Action Meaning
A Check input data: if the input data is correct:
  • then the given result data can either be regarded as information only or
  • special fault clearing may be needed, if this is the case then repeat the command

if the input data is incorrect: correct your input data and repeat MMC-command.

B Inconsistencies in the system require special fault clearing. Refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide.