| CRN 07614 | DISPLAY-N7MTP-HISTORY |
Note: Splitted point code value (1 up to 4 decimal digit strings seperated by 1 space character) depends on the network / sub-service field:
Report Layout Note:
SWA-ORJ-MTP
(A)....................... (B).................
(C)........................... (D) (E)
-----------------------------------------------------------------
OPERATOR INPUT :
TYPE = (2).....
LOGNET = (3)
RTES = (4)
DEST = (5)...... (6).............
LKSET = (7)..
SLC = (8)
CCSMEN = (9)... & (10)
MODE = (11)....
LKID = (12).
STRDATE = (13). & (14) & (15)
STRTIME = (16) & (17) & (18)
DETAIL = (19)
CONTROL = (20).... & (21) & (22) & (23) & (24)
-----------------------------------------------------------------------
RESULT :
ERROR = (26)...........................
REPORT REFERENCE NUMBER = 7492
| Par. No. | Meaning | Remarks |
|---|---|---|
| (A) | Command name | |
| (B) | Main execution result | |
| (C) | Result part type | |
| (D) | Result part number | |
| (E) | Continuation indicator | |
| (2) | Requested option | |
| ALL | display request for both link
events and routeset state chan ges | |
| LKHIST | display request for the
link-related events (link history) | |
| RTESHIST | display request for the routeset
state changes (routeset his tory) | |
| (3) | Logical Network | (0 to 32) |
| (4) | Routeset | |
| (5) | Hexadecimal destination point code | |
| ALL | display request for all
destinations | |
| (6) | Arguments of Destination-splitted pc | 1 to 16 characters |
| (7) | Linkset identity | external linkset number (1 to
512) |
| (8) | Signalling link code | a code (0 to 15), or |
| ALL | all codes | |
| (9) | Logical or physical control element identity of common channel signalling module (CCSM) equipment number | control element identity in
hexadecimal form, or |
| ALL | all control element identities | |
| (10) | Terminal number of the common channel signalling module (CCSM) equipment number | a terminal number |
| ALL | all terminal numbers | |
| (11) | Mode of the common channel signalling module (CCSM) which is either PHYSICAL/LOGICAL CE ID | |
| LOGICAL | Logical control element ID | |
| PHYSICAL | Pysical control element ID | |
| (12) | Link identity | an external link number (1 to
1024), or |
| (13) | Historical display start point date | year |
| (14) | month | |
| (15) | day | |
| (16) | Historical display start point time | hour |
| (17) | minute | |
| (18) | seconds | |
| (19) | Detail | |
| ALL | display all events | |
| SIGLK | display only the routeset state
changes due to signalling link events | |
| TFP | display only the routeset state
changes due to the transfer prohibition | |
| (20) | Command control | |
| CANCEL | cancel request | |
| SCHED | schedule request | |
| (21) | Start date and time for the scheduled request | month |
| (22) | day | |
| (23) | hour | |
| (24) | minutes | |
| (26) | Result / error information | see Evaluation |
| Key Parameter | Contents / Meaning | Action | ||
|---|---|---|---|---|
| 1 | 2 | 3 | ||
| (26) | COMMAND STATUS TERMINATE . . . . . . . . . . . . . | A | ||
| (26) | DATABASE ERROR . . . . . . . . . . . . . . . . . . | B | ||
| (26) | DATABASE INCONSISTENCY . . . . . . . . . . . . . . | B | ||
| (26) | FIRST TIMESTAMP NOT MOST ACTUAL . . . . . . . . . | A | ||
| (26) | INIT VALUE . . . . . . . . . . . . . . . . . . . . | A | ||
| (26) | LINK CAN NOT BE FOUND . . . . . . . . . . . . . . | B | ||
| (26) | LINKSET CONTAINS NO LINKS . . . . . . . . . . . . | A | ||
| (26) | MORE LINKS . . . . . . . . . . . . . . . . . . . . | A | ||
| (26) | NO EVENTS DISPLAYED DUE TO ERRORS OR DUE TO NO CORRECT EVENTS | B | ||
| (26) | NO LINKS TO CCSMEN . . . . . . . . . . . . . . . . | A | ||
| (26) | NO LINKS TO DESTINATION . . . . . . . . . . . . . | A | ||
| (26) | NO MORE EVENTS DISPLAYED DUE TO ERROR OR DUE TO NO CORRECT EVENTS | B | ||
| (26) | NO ROUTES AVAILABLE . . . . . . . . . . . . . . . | A | ||
| (26) | NOT EXISTING LINK . . . . . . . . . . . . . . . . | A | ||
| (26) | NOT EXISTING LKID . . . . . . . . . . . . . . . . | A | ||
| (26) | NOT EXISTING LKSET . . . . . . . . . . . . . . . . | A | ||
| (26) | NOT EXISTING MODULE . . . . . . . . . . . . . . . | A | ||
| (26) | NOT SUCCESSFUL DUT END . . . . . . . . . . . . . . | B | ||
| (26) | NOT SUCCESSFUL DUT START . . . . . . . . . . . . . | B | ||
| (26) | RECEIVED SNTM BUFFER IS EMPTY . . . . . . . . . . | B | ||
| (26) | ROUTE CAN NOT BE FOUND . . . . . . . . . . . . . . | B | ||
| (26) | SEMANTIC CHECK OK . . . . . . . . . . . . . . . . | A | ||
| (26) | SEMANTIC ERROR . . . . . . . . . . . . . . . . . . | B | ||
| (26) | TIMESTAMP FOUND IN BUFFER . . . . . . . . . . . . | A | ||
| (26) | TN OUT OF RANGE . . . . . . . . . . . . . . . . . | A | ||
| Action | Meaning |
|---|---|
| A | Check input data:
|
| 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. |