RRN 00037 CREATE/REMOVE ROUTING FOR MAINTENANCE REPORT

LQSQAY02

Message Triggering Condition

Response in case of successful / unsuccessful result of the execution, on operator request, of one of the following MMC-commands:
CRN 04262 CREATE-MAIREP-ROUTING
CRN 04264 REMOVE-MAIREP-ROUTING

Report Layout

SWA-EXCHANGE DEFENCE
   |
   |(A).......................                   (B).................
   |                             (C)........................... (D) (E)
   |-----------------------------------------------------------------
        (1)...
        SBLTYPE = (2).....
        DEVTYPE = (3).....
        ERRTYPE = (4)-(5).............
        REPREF  = (6)..
        SPEC    = (7).........
        OUTSET  = (8)..
        ==> (9)...................... (10).
        REL-ID = (11).
        DB MAIN STATUS = (12)
        DB SUBSTATUS = (13)
        ERROR POINT = (14)
  REPORT REFERENCE NUMBER = 0037

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) Requested option to remove the maintenance report routing for all device / error / SBL types
ALLDEV all device types
ALLERR all error types
ALLSBL all security block types
(2) Security block type see SI 006
(3) Device type see SI 009
(4) Error type value
(5) Error type mnemonic see SI 008
(6) Report reference number
(7) Specification (additional properties of the routed report)
CALNSUC calendar scheduled and not
successful
CALSUC calendar scheduled and successful
EXT external
INT internal
OPER operator
(8) Output set identity
(9) Comments on the execution result / error indication
(10) If applicable, indication of the output set identity to which the specified report is already routed
(11) Relation identity
(12) Database main status
(13) Database sub-status
(14) Error point

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(9) ALREADY ROUTED TO OUTPUTSET . . . . . . . . . . . A
(9) BUFFER OVERFLOW . . . . . . . . . . . . . . . . . C
(9) DATABASE ERROR . . . . . . . . . . . . . . . . . . C
(9) NO ROUTING APPLICABLE . . . . . . . . . . . . . . B
(9) NO SPACE IN ROUTING TABLE . . . . . . . . . . . . C

Action Description

Action Meaning
A The result data is given in case of the specified report is already routed to any other output set indicated on parameter (10). Check the input data, correct and enter the MMC-command again.
B The result data is given as an error message, when an inconsistent data is detected during the check of the operation, which is specified by the specific input parameters, whether is valid and in conflict with the existing data. Routing can be done on three different items : - for a security block type ; RRN 00052 or RRN 00154, - for a device type ; RRN 00154 or RRN 00156, - for an error type ; RRN 00048 or RRN 07439. Correct the input data and enter the MMC-command again. See also Restrictions part of the corresponding MMC-command. If the result is still unsuccessful, special fault clearing will be necessary. In that case continue with the Action C.
C Repeat the command after some time. If the result is still unsuccessful, special fault clearing will be necessary. See fault reporting procedures. Refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide. See also relation identity (parameter 11), database main status (parameter 12) and sub-status (parameter 13) to identify the problem and if any error point indication (parameter 14) 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.