RRN 08502 HANDLE SCCP TRACE FUNC (UNSUCCESSFUL)

AJ5MD903

Message Triggering Condition

This report will be triggered in case of unsuccessful result of the execution, on operator request, of one of the the following MMC-commands:
CRN 08501 START-SCCP-TRACE
CRN 08502 DISPLAY-SCCP-TRACE
CRN 08503 STOP-SCCP-TRACE
CRN 08504 DISPLAY-SCCP-TRACEPAR

Report Layout

 SWA-SUBSEC SCCP
    (A).......................                   (B).................
                                       (C)...........................
    -----------------------------------------------------------------
        OPERATOR INPUT :
        (1)
         TRACEID : (2)
         CONTYP  : (3).....
         CDGTI   : (4).......
         CDDEST  : (5)..... / (6)............. / (7).............
                 & (8)...
         CDSSN   : (9).....
         CDNTRADD: (10)....
         CDTRLTYP: (11).
         CDNBRPL : (12).....
         CDDN    : (13)..............
         CDENCOD : (14)...
         CDNATUSE: (15)...
         CDRTSSN : (16)...
         CGGTI   : (17)......
         CGDEST  : (18).... / (19)............ / (20)............
                 & (21)..
         CGSSN   : (22)....
         CGNTRADD: (23)....
         CGTRLTYP: (24).
         CGNBRPL : (25).....
         CGDN    : (26)..............
         CGENCOD : (27)...
         CGNATUSE: (28)...
         CGRTSSN : (29)...
         LOCREF  : (30)............
         POOL    : (31).... & (32)....
         LCE     : (33)..
         DETAIL  : (34)....
        ERROR INFORMATION :
         (36)..........................................................
  REPORT REFERENCE NUMBER = 8502

Parameter Identification

Par. No. Meaning Remarks
(A) Command name
(B) Main execution result
(C) Result part type
(1) Title operator input
(2) Trace identity (number) 1 to 5 : connectionless trace, 6
to 10 : connection-oriented trace
(3) Connection type
CLESSCCP connectionless trace
CORSCCP connection-oriented trace
(4) Called address global title indicator
(5) Called destination point code (hexadecimal)
(6) Called destination point code (split code)
(7) Called dest point code (exchange name)
(8) Called destination lognet
(9) Called subsystem number
ALL all possibilities
AUTHCENTRE authentication centre
BSSAP base station sub-system
application part
BSSOMAP base station sub-system O&M part
EIR equipment identity register
HLR home location register
INALSSF ALCATEL service switching
function (IN)
INERSCF ERICSSON service control function
(IN)
INERSSF ERICSSON service switching
function (IN)
ISUP ISDN user part
MAP mobile application part
MSC mobile service centre
MUP mobile user part
OMAP operation and maintenance
administration part
OMUP operation and maintenance user
part
Q3L4TO7 Q3 level interface 4 to 7 (TMN)
SCCPX25 signalling connection control
part X25 link
SCMG signalling connection part
management
SSNABS absentee
SSNIVPN individual virtual private
numbering
TAXAP taxation application part
UNCHG unchanged
UNKNOWN unknown number
USBS user signalling bearer service
VLR visitor location register
(10) Called nature of address
ADD add
ALL all natures of address
CHANGE change
INTAL international
NAT national
NATADDR nature of address
NOTAPPL NR_ABD not applicable
number of abbreviated dialling
NTWKSPEC network specification
REMOVE remove
SUBSC subscriber
UNCHG unchanged
UNKNOWN unknown
(11) Called translation type
(12) Called numbering plan
(13) Called directory number
(14) Called encoding scheme
EVEN even encoding
ODD odd encoding
(15) Called national used
(16) Called routing SSN
(17) Calling address global title indicator
(18) Calling destination point code (hexadecimal)
(19) Calling destination point code (split code)
(20) Calling dest point code (exchange name)
(21) Calling destination lognet
(22) Calling subsystem number
see param (9)
(23) Calling nature of address
see param (10)
(24) Calling translation type
(25) Calling numbering plan
(26) Calling directory number
(27) Calling encoding scheme
EVEN even encoding
ODD odd encoding
(28) Calling national used
(29) Calling routing SSN
(30) Local reference
(31) Pool identity 1
see param (9)
(32) Pool identity 2
see param (9)
(33) Logical control element
(34) Print report detail
NOPRINT do not print the trace
PRINT print the trace
(36) Error information

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(36) DB ACCESS ERROR . . . . . . . . . . . . . . . . . C
(36) DB INCONSISTENCY . . . . . . . . . . . . . . . . . C
(36) DISPLAYED TRACE IS NOT ACTIVE IN ANY CE . . . . . B
(36) DUT EOT ERROR . . . . . . . . . . . . . . . . . . C
(36) DUT SOT ERROR . . . . . . . . . . . . . . . . . . C
(36) INCONSISTENT CONNECTION TYPE . . . . . . . . . . . B
(36) INPUT POOL - FIRST ARGUMENT POOL DOES NOT EXIST . B
(36) INPUT POOL - SECOND ARGUMENT POOL DOES NOT EXIST . B
(36) INPUT TRACE ALREADY ACTIVE . . . . . . . . . . . . A
(36) INPUT TRACE ALREADY ACTIVE . . . . . . . . . . . . A
(36) INPUT TRACE NOT ACTIVE . . . . . . . . . . . . . . A
(36) INPUT TRACE NOT LOCATABLE . . . . . . . . . . . . A
(36) NO FREE TRACE CONTROL BLOCK . . . . . . . . . . . B
(36) NO TRACES ACTIVE FOR INPUT CONNECTION TYPE . . . . B
(36) STARTED TRACE WAS NOT ACTIVATED IN ANY CE . . . . B
(36) SYSTEM ERROR - DESTINATION PONT CODE UNKNOWN . . . B
(36) SYSTEM ERROR - INTERFACE ERROR 1 . . . . . . . . . B
(36) SYSTEM ERROR - INTERFACE ERROR 2 . . . . . . . . . B
(36) SYSTEM ERROR - INTERFACE ERROR 3 . . . . . . . . . B
(36) SYSTEM ERROR - NOT SUCCESSFUL RESULT FROM N7USRA . B
(36) SYSTEM ERROR - TIMEOUT EXPIRED . . . . . . . . . . B
(36) TRACEID HAS NO TRACEPAR . . . . . . . . . . . . . A
(36) TUPLE NOT FOUND IN R_N7_TRPAR . . . . . . . . . . A
(36) TUPLE NOT FOUND IN R_POOLTR . . . . . . . . . . . A
(36) WRONG DPC WAS GIVEN . . . . . . . . . . . . . . . A

Action Description

Action Meaning
A Check input data : - if correct : 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 unsuccessfulm special fault clearing will be necessary. See full reporting procedures.
C Special fault clearing is necessary. See fault reporting procedures. Refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide.