RRN 07721 <DOCUMENT TITLE>

AC9XXJ13

Message Triggering Condition

Response in case of unsuccessful result of the execution, on operator request, of one of the following MMC-commands : CRN 00082 CREATE-DID CRN 00083 MODIFY-DID
CRN 00084 DISPLAY-DID CRN 04075 REMOVE-DID

Report Layout

 SWA-SUBSEC DID
    (A).......................                   (B).................
                                 (C)........................... (D) (E)
    -----------------------------------------------------------------
        RESULT     = (1)....
        REASON     = (2)....
        ERRORPOINT = (3)....
        (4)
  REPORT REFERENCE NUMBER = 7721

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) Command execution result
(2) error reason
(3) error point
(4) comments on the execution result

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(1) COMMAND NOT EXECUTED . . . . . . . . . . . . . . . A
(1) CONSISTENCY ERROR . . . . . . . . . . . . . . . . A
(1) DB ERROR . . . . . . . . . . . . . . . . . . . . . B
(1) DB INCONSISTENCY . . . . . . . . . . . . . . . . . B
(1) DUT END OF TRANSACTION ERROR . . . . . . . . . . . B
(1) DUT START OF TRANSACTION ERROR . . . . . . . . . . B
(2) A REFERENCE, A TASK OR COMPRESS REQUIRED . . . . . A
(2) CLOSE MAIN-DUT . . . . . . . . . . . . . . . . . . B
(2) CLOSE SUB-DUT . . . . . . . . . . . . . . . . . . B
(2) COM DEST = 0 . . . . . . . . . . . . . . . . . . . A
(2) COMBINATION OF SPECIFIED TASKS NOT ALLOWED . . . . A
(2) CREATE OF REQUESTED COMBINATION NOT ALLOWED . . . A
(2) DID KEY COMBINATION ALREADY EXISTING . . . . . . . A
(2) DID REFERENCE COMBINATION ALREADY EXISTING . . . . A
(2) DISPLAY OPTION NOT FOUND . . . . . . . . . . . . . A
(2) ILLEGAL KEY-COMBINATION FOR CREATE-DID . . . . . . A
(2) ILLEGAL KEY-COMBINATION FOR MODIFY-DID . . . . . . A
(2) INCOMING COMBINATION NOT FOUND . . . . . . . . . . A
(2) INCOMING KEY COMBINATION ALREADY EXISTING . . . . A
(2) INCOMING REFERENCE COMBINATION ALREADY EXISTING . A
(2) ITEM TO REMOVE IS NOT UNIQUE . . . . . . . . . . . A
(2) KEY DID COMBINATION IS NOT EXISTING . . . . . . . A
(2) MAIN-DUT ROLL-BACK . . . . . . . . . . . . . . . . B
(2) NO COMBINATION FOUND . . . . . . . . . . . . . . . A
(2) NO FREE COMDEST(CD) FOUND . . . . . . . . . . . . A
(2) NO FREE COMORG(CO) FOUND . . . . . . . . . . . . . A
(2) NO ITEMS TO REMOVE FOUND . . . . . . . . . . . . . A
(2) OPEN MAIN-DUT . . . . . . . . . . . . . . . . . . B
(2) OPEN SUB-DUT . . . . . . . . . . . . . . . . . . . B
(2) OUTGOING COMBINATION NOT FOUND . . . . . . . . . . A
(2) OUTGOING KEY COMBINATION ALREADY EXISTING . . . . A
(2) OUTGOING REFERENCE COMBINATION ALREADY EXISTING . A
(2) PASSIVE GUARD NOT YET RELEASED . . . . . . . . . . C
(2) REF AND KEY HAVE DIFFERENT TOC RANGES . . . . . . A
(2) REFERENCE AND TASK NOT ALLOWED . . . . . . . . . . A
(2) REFERENCE REQUIRED FOR CREATE DID . . . . . . . . A
(2) REFERENCED DID COMBINATION IS NOT EXISTING . . . . A
(2) REFERENCED INCOMING COMBINATION NOT EXISTING . . . A
(2) REFERENCED INCOMING COMBINATION NOT FOUND . . . . A
(2) REFERENCED OUTGOING COMBINATION NOT EXISTING . . . A
(2) REMOVAL OF A DESTGRP IS NOT ALLOWED . . . . . . . A
(2) REMOVAL OF LAST COMB WITH THIS DESTGRP IS NOT ALLOWED A
(2) REMOVAL OF REQUESTED COMBINATION IS NOT ALLOWED . A
(2) REMOVE ALL DESTDID NOT ALLOWED . . . . . . . . . . A
(2) REMOVE INCOMING COMBINATION NOT ALLOWED . . . . . A
(2) REMOVE NOT ALLOWED . . . . . . . . . . . . . . . . A
(2) REQUESTED COMBINATION NOT EXISTING . . . . . . . . A
(2) SUB-DUT ROLL-BACK . . . . . . . . . . . . . . . . B
(4) COMPRESS ENDED WITH ERROR . . . . . . . . . . . . B
(4) MORE INFO IN DB-ERROR REPORT . . . . . . . . . . . D
(4) PLEASE CONFIRM/CANCEL (COMMAND + CONTROL = CONFIRM/CANCEL) E

Action Description

Action Meaning
A 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. Check input data, correct and enter the MMC-command again. See also the Restrictions part of the corresponding MMC-command. If the input data is correct, the given result data can be taken as an information only or it is possible that the commands, to be entered previously, are forgotten. In that case enter the necessary MMC-commands first. If the combination you typed in is not found, please consider the following: - the combination may may not be existing at all - maybe it is not existing for the DIDCASE you specified when you want to create or modify a DID-combination (or a task) then you must specify the exact DIDCASE. The default DIDCASE is BOTH. For instance, if you specified DIDCASE=ACTIVE but there is only a combination for DIDCASE=BOTH, then you will receive an error that the DID combiantion does not exist. Hint: Use the DISPLAY command to see which combinations (and their DIDCASEs) exist.
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. If any error point indication (parameter 3) is given, this error point refers in the source listing to a specific point where the database failure occurred.
C Repeat the command after some time. If the result is still unsuccessful, special fault clearing will be necessary. In case that 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.
D See the database error report triggered for the same failure. 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.
E Enter CONFIRM or CANCEL request by using the related the MMC-command.