RRN 00197 HANDLE N7 EXCHANGE (UNSUCCESSFUL)

PLGHD928

Message Triggering Condition

Response in case of unsuccessful result of the execution, on operator request, of one of the following MMC-commands :
CRN 03265 CREATE-N7-DEST
CRN 03266 MODIFY-N7-DEST
CRN 03267 REMOVE-N7-DEST
CRN 03268 DISPLAY-N7-DEST

Report Layout

 SWA-SUBSEC MTP
    (A).......................                   (B).................
                                 (C)........................... (D) (E)
    -----------------------------------------------------------------
        OPERATOR INPUT:
        EXCHNAME  = (2)..
        EXCHNAME  = (3).............
        DESTTYPE  = (4).   (6)..
        CLUSTER     (7)
        NMMSG     = (8)
        XLIST     = (9)
        MOPCAPPL  = (10)
        NEWNAME   = (11)
        NEWRTES   = (12)
        DETAIL    = (13)
        OPCIND    = (14)
        CONTROL   = (15). & (16) & (17) & (18) & (19)
        (20)....  = (21).
        (22)....... (23)........... (24)....   (26)............ (27)....
        (28)....... (29). (30)............
         NCANAME  = (31)............
         EXCHNAME = (32)............
         (33)...... (34)............ (35)....
                    (37)............ (38)....
         RTESID   = (39)............
         LOGNET   = (40)............
         DETAIL   = (41)..
         CONTROL  = (42).... & (43) & (44) & (45) & (46)
         (47)..... (48)............ (49)....   (51)............ (52)....
         LOGNET  = (53)............
         NCANAME = (54)............
         RTES    = (55)............
         NCANAME = (56)............
         RTESID  = (57)............
         CONTROL = (58).... & (59) & (60) & (61) & (62)
        -----------------------------------------------------------------------
        ERROR:
          (64)
          (65)
          (66)
          (67)
  REPORT REFERENCE NUMBER = 0197

Parameter Identification

Par. No. Meaning Remarks
(A) Command name
(B) Main execution result
(C) Result part type
(D) Result part number
(E) Continuation indicator
(2) Exchid mnemonic name translated via the
mnemonic relation(R_N7EXMNEM)
(3) Exchange name exchange name in ascii form
(4) Information about the exchange adjacency or non adjacency
information
ADJ adjacent exchange
NADJ non-adjacent exchange
(6) Destination type signalling point or signalling
transfer point information
SP signalling point (a terminating
traffic exchange)
STPSP signalling transfer point and
signalling point (a transit and
terminating exchange)
(7) Cluster cluster
(8) Treatment of network management messages nmmsgs
OFF treatment of NM messages - OFF
ON treatment of NM messages - ON
(9) X-list for routeset - maintain or exclude xlist
EXCLUDE exclude x-list for routeset
MAINTAIN maintain x-list for routeset
(10) Mopc application mopcappl
CAPCODE capability code
MT16LK more than 16 links
MT4096TK more than 4096 trunks
NETRES network restoration
NORM normal
RENUMBER renumbered OPC
(11) Newname of exchange new exchange name in ascii form
(12) Newname of routeset new routeset name in ascii form
(13) Destination detail details of the destination
ADJ adjacent exchange
DESTCA destination in concerned area
DESTNCA destination in non concerned area
NADJ non-adjacent exchange
NCANAME non-concerned area name
SP signalling point (a terminating
traffic exchange)
STPSP signalling transfer point and
signalling point (a transit and
terminating exchange)
(14) Opc indicator opc indicator
OPCSET1 OPC indicator1
OPCSET2 OPC indicator2
OPCSET3 OPC indicator3
OPCSET4 OPC indicator4
OPCSET5 OPC indicator5
OPCSET6 OPC indicator6
OPCSET7 OPC indicator7
(15) Control parameter control
CANCEL cancel
CONFIRM confirm
DELAY delay
DONTCARE dontcare
NONE none
SCHED schedule
(16) Scheduled month month
(17) Scheduled day day
(18) Scheduled hour hour
(19) Scheduled minute minute
(20) Logical network parameter lognet parameter
LOGNET1 lognet1 parameter
LOGNET2 lognet2 parameter
LOGNET3 lognet3 parameter
LOGNET4 lognet4 parameter
(21) Logical network mnemonic relation translated via
mnemonic relation(R_N7LNMNEM)
(22) Destination parameter dest parameter
DEST1 = dest1 parameter
DEST2 = dest1 parameter
DEST3 = dest1 parameter
DEST4 = dest1 parameter
NEWDEST1 = newdest1 parameter
NEWDEST2 = newdest1 parameter
NEWDEST3 = newdest1 parameter
NEWDEST4 = newdest1 parameter
(23) Splitted destination point code-low low range pointcode in splitted
format
(24) Hexadecimal destination point code-low low range pointcode in
hexadecimal format
(26) Splitted destination point code-high high range pointcode in splitted
format
(27) Hexadecimal destination point code-high high range pointcode in
hexadecimal format
(28) Routeset parameter routeset parameter
RTESID1 = rtesid1 parameter
RTESID2 = rtesid2 parameter
RTESID3 = rtesid3 parameter
RTESID4 = rtesid4 parameter
(29) Routesetid1 mnemonic name translated via
mnemonic relation(R_N7RSMNEM)
(30) Routeset name1 mnemonic name in ascii form
(31) Non-concerned area name in ASCII form
(32) Exchange name in ASCII form
(33) Header text
CLUSTER cluster
DESTS = destination
EXCHNAME = exchange name
NCANAME = non-concerned area name
(34) Splitted destination point code - low low range pointcode in splitted
format
(35) Hexadecimal destination point code - low low range pointcode in
hexadecimal format
ALL DESTS = ALL, all destinations
NCANAME = ALL, all non-concerned
areas
(37) Splitted destination point code - high high range pointcode in splitted
format
(38) Hexadecimal destination point code - high high range pointcode in
hexadecimal format
(39) Routeset identity mnemonic name translated via
mnemonic relation(R_N7RSMNEM)
(40) Logical network mnemonic name translated via
mnemonic relation(R_N7LNMNEM)
(41) Detailed display request display detail
ADJ adjacent exchanges
ALL all possible items
CLUSTER cluster exchanges
DESTCA destinations in the concerned
area
DESTNCA destinations in the non-concerned
area
NADJ non-adjacent exchanges
NCANAME non-concerned area names
SP signalling points
STPSP signalling transfer points and
signalling poi nts
(42) Command control
see param (15)
control
(43) Scheduled month month
(44) Scheduled day day
(45) Scheduled hour hour
(46) Scheduled minute minute
(47) Header for destination
DEST1 = Destination 1
DEST2 = Destination 2
DEST3 = Destination 3
DEST4 = Destination 4
(48) A single splitted destination point code, or the first splitted destination point code in the range of destination point codes low range pointcode in splitted
format
(49) A single hexadecimal destination point code, or the first hexadecimal destination point code in the range of the destination point codes low range pointcode in
hexadecimal format
(51) The last splitted destination point code in the range of the destination point codes (see also the explanation given for parameter(7) high range pointcode in splitted
format
(52) The last hexadecimal destination point code in the range of the destination point codes high range pointcode in
hexadecimal format
(53) Logical network mnemonic name translated via
mnemonic relation (R_N7LNMNEM)
(54) Non concerned area name mnemonic name translated into via
mnemonic relation(R_N7EAMNEM)
(55) Routeset name mnemonic name translated into via
mnemonic relation(R_N7RSMNEM)
(56) Non concerned area name in ASCII form
(57) Routeset name in ASCII form
(58) Command control
see param (15)
control
(59) Scheduled month month
(60) Scheduled day day
(61) Scheduled hour hour
(62) Scheduled minute minute
(64) Failure reason see Evaluation
(65) Additional failure reason see Evaluation
(66) Additional failure reason see Evaluation
(67) Invalid parameter / concerned point code identity
THE CONCERNED POINT CODE IDENTITY IS dest1
DEST1
THE CONCERNED POINT CODE IDENTITY IS dest2
DEST2
THE CONCERNED POINT CODE IDENTITY IS dest3
DEST3
THE CONCERNED POINT CODE IDENTITY IS dest4
DEST4

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(64) DB ACCESS ERROR . . . . . . . . . . . . . . . . . B
(64) DB INCONSISTENCY . . . . . . . . . . . . . . . . . B
(64) DEST IS ALREADY USED AS OWN POINT CODE . . . . . . A
(64) DESTINATION PC ALREADY PRESENT IN CONCERNED AREA . A
(64) DESTINATION PC ALREADY USED IN NCA . . . . . . . . A
(64) DISPLAY OF REPORT IS CANCELLED . . . . . . . . . . A
(64) DPC DOES NOT EXIST . . . . . . . . . . . . . . . . A
(64) DPC OF CLUSTER MAY NOT BE CHANGED, USE REMOVE CREATE A
(64) EXCHANGE IS ADJACENT . . . . . . . . . . . . . . . A
(64) EXCHANGE IS NOT A SIGNALLING POINT . . . . . . . . A
(64) EXCHANGE IS NOT A SIGNALLING TRANSFER POINT . . . A
(64) EXCHANGE IS NOT ADJACENT . . . . . . . . . . . . . A
(64) GIVEN DEST VALUE PRESENT AS OWN POINT CODE . . . . A
(64) GIVEN EXCH DOES NOT EXIST . . . . . . . . . . . . A
(64) GIVEN EXCHANGE DOES NOT EXIST . . . . . . . . . . A
(64) GIVEN EXCHANGE IS AN OWN EXCHANGE . . . . . . . . A
(64) GIVEN EXCHANGE IS PRESENT IN NON CONCERNED AREA . A
(64) GIVEN EXCHANGE NAME PRESENT IN CONCERNED AREA . . A
(64) INVALID POINT CODE FOR CLUSTER . . . . . . . . . . A
(64) LOGICAL NETWORK DOES NOT SUPPORT CLUSTER . . . . . A
(64) LOGICAL NETWORK DOES NOT SUPPORT NON CONCERNED AREA A
(64) NCANAME ALREADY EXISTS . . . . . . . . . . . . . . A
(64) NO DATA FOUND . . . . . . . . . . . . . . . . . . A
(64) NO NCA KNOWN TO OWN EXCHANGE . . . . . . . . . . . A
(64) NO OWN POINTCODE IN GIVEN LOGICAL NETWORK . . . . A
(64) NO REMOTE EXCHANGE NAME FOUND . . . . . . . . . . A
(64) NO ROUTESET DEFINED . . . . . . . . . . . . . . . A
(64) OPCIND UNKNOWN TO OWN NODE . . . . . . . . . . . . A
(64) POINT CODE ALREADY EXISTS AS DEST . . . . . . . . A
(65) ALL GIVEN ROUTESETS MUST BELONG TO SAME PHYS EXCH A
(65) ALREADY IN WANTED STATE . . . . . . . . . . . . . A
(65) DEST CANNOT BE REMOVED/MODIFIED,LKSET TO DEST EXISTS A
(65) DEST EXISTS AS OWN_PC . . . . . . . . . . . . . . A
(65) DEST IS ALREADY PRESENT . . . . . . . . . . . . . A
(65) DIRECT LKSET EXISTS . . . . . . . . . . . . . . . A
(65) EXCH IS RESTORED AT OWN . . . . . . . . . . . . . A
(65) EXCH MUST BE ADJ FOR_APPL . . . . . . . . . . . . A
(65) EXCH MUST BE ADJACENT . . . . . . . . . . . . . . A
(65) GIVEN DEST DOESNT BELONG TO SAME EXCH . . . . . . A
(65) GIVEN LOGNETS MUST BE DIFFERENT . . . . . . . . . A
(65) GIVEN RTESNAME DOESNT EXIST . . . . . . . . . . . A
(65) INDIRECT ROUTE EXISTS . . . . . . . . . . . . . . A
(65) INPUT DEST DOES NOT EXIST . . . . . . . . . . . . A
(65) LKSET DOES NOT SUPPORT NETWORK RESTORATION . . . . A
(65) LKSET DOESNT EXIST . . . . . . . . . . . . . . . . A
(65) LKSET USED BY OTHER EXCH . . . . . . . . . . . . . A
(65) LOGNET DOES NOT SUPPORT NETWORK RESTORATION . . . A
(65) MAX NUMBER OF EXCHANGES DEFINED . . . . . . . . . A
(65) NADJ DEST CAN NOT BE STPSP . . . . . . . . . . . . A
(65) NAME EXISTS AS EXCHANGE NAME IN CONCERNED AREA . . A
(65) NAME EXISTS AS NON CONCERNED AREA NAME . . . . . . A
(65) NAME NOT FOUND . . . . . . . . . . . . . . . . . . A
(65) NO LKSET DEFINED TO DEST . . . . . . . . . . . . . A
(65) NO MORE LOGID . . . . . . . . . . . . . . . . . . A
(65) NO NCA DEFINED FOR GIVEN LOGNET . . . . . . . . . A
(65) NO NCA DEFINED FOR OWN EXCHANGE . . . . . . . . . A
(65) NO PHY EXCH FOR APPL OTHER THAN NORMAL . . . . . . A
(65) OWN PHY EXCHANGE . . . . . . . . . . . . . . . . . A
(65) PC NOT VALID . . . . . . . . . . . . . . . . . . . A
(65) REMOVE OF NORMAL DEST NALWD, EXCH STILL HAS DEST FOR MOPC A
(65) ROUTE EXISTS FOR GIVEN DEST . . . . . . . . . . . A
(65) RTESNAME EXISTS . . . . . . . . . . . . . . . . . A
(65) SAME APPL EXISTS . . . . . . . . . . . . . . . . . A
(65) THESE APPL NOT ALLOWED . . . . . . . . . . . . . . A
(66) ANSI PC 00 XX XX NOT ALLOWED . . . . . . . . . . . A
(66) DEST ALREADY EXISTS FOR EXCH, LOGNET & OPCSET . . A
(66) DETAIL ARGUMENT NOT VALID FOR SPECIFIED DEST . . . A
(66) DPC IS A CLUSTER . . . . . . . . . . . . . . . . . A
(66) EXCHANGE IS NOT IN CONCERNED AREA . . . . . . . . A
(66) EXIT LOOP . . . . . . . . . . . . . . . . . . . . A
(66) GIVEN DEST CANNOT BE A RANGE FOR ANSI MEMBER . . . A
(66) GIVEN DEST CANNOT BE A RANGE FOR ITU CONCERNED AREA A
(66) GIVEN DEST DOES NOT EXIST IN NCA . . . . . . . . . A
(66) GIVEN EXCH HAS NO NORMAL DEST IN LOGNET . . . . . A
(66) GIVEN EXCH STILL HAS RTESID FOR MOPCAPPL . . . . . A
(66) INVALID CLUSTER PC, XX XX 00 EXPECTED . . . . . . A
(66) INVALID ITU PC LENGTH . . . . . . . . . . . . . . A
(66) LN DOES NOT SUPPORT XLIST . . . . . . . . . . . . A
(66) MODIFICATION OF DESTTYPE NOT ALWD FOR CLUSTER . . A
(66) MODIFY OR REMOVAL OF DEST NOT ALLWD WHEN REGISTERED A
(66) MODIFY OR REMOVE NOT ALLOWED,ROUTESET USED BY DTAX A
(66) MODIFY OR REMOVE NOT ALLOWED,ROUTESET USED BY OTAX A
(66) MODIFY OR REMOVE NOT ALLOWED,ROUTESET USED BY SCCP A
(66) MODIFY OR REMOVE NOT ALLOWED,ROUTESET USED BYISUP/TUP A
(66) NADJ STPSP NOT ALLOWED . . . . . . . . . . . . . . A
(66) NO DEST MATCHING OPERATOR INPUT FOUND . . . . . . A
(66) NO RESPONSE FROM MTP ACCOUNTING FMM . . . . . . . A
(66) NORMAL DEST ALREADY EXISTS FOR THIS EXCHANGE,LOGNET A
(66) REMOVE NOT ALLOWED,ROUTESET USED IN ACCOUNTING . . A
(66) RTESID EXISTS BUT NOT FOR THE SPECIFIED LOGNET . . A
(66) SPECIFIED DEST MOPCAPPL COMBINATION DOES NOT EXIST A
(66) SPECIFIED DEST UNKNOWN FOR SPECIFIED LOGNET . . . A
(66) SPECIFIED LOGNET IS WRONG FOR THE SPECIFIED EXCHANGE A
(66) SYSTEM ERROR OCCURRED IN MTP ACCOUNTING FMM . . . A
(66) TUPLE FOUND . . . . . . . . . . . . . . . . . . . A
(66) XLIST ONLY APPLICABLE FOR CLUSTER DEST . . . . . . A

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. Correct the input data and enter the MMC-command again. If applicable, see also the invalid parameter / concerned point code identity (parameter 18). If the input data is correct, the given result data can be taken as information only and it is quite possible that commands, to be entered previous to the command, are forgotten. In that case, enter the necessary MMC-commands first. See also the Restrictions part of the corresponding 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.