| CRN 04265 | DISPLAY-MAIREP-ROUTING |
SWA-EXCHANGE DEFENCE
|
|(A)....................... (B).................
| (C)........................... (D) (E)
|-----------------------------------------------------------------
(1)...
(2)...........................
(4). (5).. (6)..
(7)..... (8).. (9).. (10).....
(11). (12). (13).
==> (14).....................
REL-ID = (15).
DB MAIN STATUS = (16)
DB SUBSTATUS = (17)
ERROR POINT = (18)
REPORT REFERENCE NUMBER = 0038
| Par. No. | Meaning | Remarks |
|---|---|---|
| (A) | Command name | |
| (B) | Main execution result | |
| (C) | Result part type | |
| (D) | Result part number | |
| (E) | Continuation indicator | |
| (1) | Requested display option | |
| ALLDEV | all device types | |
| ALLERR | all error types | |
| ALLSBL | all security block types | |
| (2) | Header text | |
| DEVTYPE REPREF OUTSET SPEC | header 2 | |
| ERRTYPE REPREF OUTSET | header 3 | |
| SBLTYPE REPREF OUTSET | header 1 | |
| (4) | Security block type | see SI 006 |
| (5) | Report reference number | |
| (6) | Output set identity | |
| (7) | Device type | see SI 009 |
| (8) | Report reference number | |
| (9) | Output set identity | |
| (10) | Specification | |
| CALNSUC | calendar scheduled and not
successful | |
| CALSUC | calendar scheduled and successful | |
| EXT | external | |
| INT | internal | |
| OPER | operator | |
| (11) | Error type | see SI 008 |
| (12) | Report reference number | |
| (13) | Output set identity | |
| (14) | Comments on the execution result / error indication | |
| (15) | Relation identity | |
| (16) | Data base main status | |
| (17) | Data base sub-status | |
| (18) | Error point |
| Key Parameter | Contents / Meaning | Action | ||
|---|---|---|---|---|
| 1 | 2 | 3 | ||
| (14) | DATABASE ERROR . . . . . . . . . . . . . . . . . . | B | ||
| (14) | NO ROUTING APPLICABLE . . . . . . . . . . . . . . | A | ||
| Action | Meaning |
|---|---|
| A | Check input data: - if exact: given result data can be taken as information only. - if faulty: correct your input data and repeat MMC-command. |
| B | 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 15), database main status (parameter 16) and sub-status (parameter 17) to identify the problem and if any error point indication (parameter 18) 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. |