RRN 00095 SBL MANAGEMENT: AUTONOMOUS RELOAD

LRTTAV03

Message Triggering Condition

This report is triggered to inform the operator about the results of the autonomous load.

Report Layout

SWA-ONLINE LOAD FUNCTION
   |
   |(A).......................                   (B).................
   |                             (C)........................... (D) (E)
   |-----------------------------------------------------------------
        AUTONOMOUS RELOAD
        (1)
        NA          = (2)...
        SBLTYPE     = (3).....
        NBR         = (4)..
        CE FUNCTION = (5).....              APT = (6).....
        ==> (7)...................
        ACTION RESULT = (8)
        FMM-ID = (9)..
        REL-ID = (10).
        DB MAIN STAT = (11)
        DB SUB-STAT = (12)
        ERROR POINT = (13)
        LOGICAL DEVICE = (14)
        FILE IDENTITY = (15)
        RECORD SEQUENCE NUMBER = (16)
        LOGICAL IO RECORD NUMBER = (17)
        OFFSET IN LOGICAL IO RECORD = (18)
        PHYSICAL IO RECORD NUMBER = (19)
  REPORT REFERENCE NUMBER = 0095

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) Autonomous reload
(2) Network address of the control alement in hexadecimal form
(3) Security block type see SI 006
(4) Security block number
(5) Control element function see SI 019
(6) Application processor type see SI 210
(7) Global result see ACTION DESCRIPTION
(8) Action result see ACTION DESCRIPTION
(9) FMM identity
(10) Relation identity
(11) Database main status see SI 058
(12) Database sub status see SI 058
(13) Error point
(14) Logical device identity
(15) File identity where the relation is situated
(16) Record sequence number
(17) Logical input/output record number within the file
(18) Offset in logical input/output record where the Core Image Record (CIR) of the relation starts
(19) Physical input/output record number

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(7) ACTION FAILED . . . . . . . . . . . . . . . . . . A
(8) BOOTPROM RELOAD . . . . . . . . . . . . . . . . . B
(8) CE LOADED WITH DUM PACKET . . . . . . . . . . . . B
(8) CONFIRMED NOT RESTARTED . . . . . . . . . . . . . B
(8) DATA BASE FAILURE . . . . . . . . . . . . . . . . B
(8) FAST TEST NOT OK . . . . . . . . . . . . . . . . . B
(8) GLSLMD FILE NOT CORRECT . . . . . . . . . . . . . B
(8) HDS LOADING NOK . . . . . . . . . . . . . . . . . B
(8) HDS LOADING TIMEOUT . . . . . . . . . . . . . . . B
(8) INCORRECT LOAD MODULE NAME . . . . . . . . . . . . B
(8) LOAD-SHEDDING FAILED . . . . . . . . . . . . . . . B
(8) NEW BOOTSTRAP . . . . . . . . . . . . . . . . . . B
(8) NO DELTA PLS . . . . . . . . . . . . . . . . . . . B
(8) NO END OF PROGRAM FOUND . . . . . . . . . . . . . B
(8) NO FREE PROCESS . . . . . . . . . . . . . . . . . B
(8) NO OBC FILE LIST BUILT . . . . . . . . . . . . . . B
(8) NO PATH . . . . . . . . . . . . . . . . . . . . . B
(8) NOT SUCCESSFUL . . . . . . . . . . . . . . . . . . B
(8) OPEN APLS FAILURE . . . . . . . . . . . . . . . . B
(8) OPEN DLS FAILURE . . . . . . . . . . . . . . . . . B
(8) OPEN GLS FAILURE . . . . . . . . . . . . . . . . . B
(8) OPEN UDLS FAILURE . . . . . . . . . . . . . . . . B
(8) OPEN UPLS FAILURE . . . . . . . . . . . . . . . . B
(8) PATH ABORT . . . . . . . . . . . . . . . . . . . . B
(8) READ APLS FAILURE . . . . . . . . . . . . . . . . B
(8) READ DLS FAILURE . . . . . . . . . . . . . . . . . B
(8) READ GLS FAILURE . . . . . . . . . . . . . . . . . B
(8) READ UDLS FAILURE . . . . . . . . . . . . . . . . B
(8) READ UPLS FAILURE . . . . . . . . . . . . . . . . B
(8) ROM HDS CHECK SKIPPED . . . . . . . . . . . . . . B
(8) SOFTWARE FAULT . . . . . . . . . . . . . . . . . . B
(8) TIME OUT, REMOTE CE . . . . . . . . . . . . . . . B
(8) WRONG APLS NAME . . . . . . . . . . . . . . . . . B
(8) WRONG UPLS NAME . . . . . . . . . . . . . . . . . B

Action Description

Action Meaning
A Action is failed. See action result (parameter 8) for additional information.
B Special fault clearing is necessary. See fault reporting procedures (refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide). See also FMM identity (parameter 9), relation identity (parameter 10) ,database main status (parameter 11) and sub-status (parameter 12) to identify the problem and if any error point indication (parameter 13) is given, this error point refers in the source listing to a specific point where the database failure occurred. See the error point and check the contents of the relation.