RRN 06756 <ACTIVATE N7 MTUP>

KKXCD906

Message Triggering Condition

Response in case of successful/unsuccessful result of the execution, on operator request, of the following MMC-command:
CRN 03654 ACTIVATE-N7-MTUP

Report Layout

 SWA-SUBSEC MTP
    (A).......................                   (B).................
                                 (C)........................... (D) (E)
    -----------------------------------------------------------------
     OPERATOR INPUT:
      (1)
      RTESID   = (2).............
      DEST     =(3) (4)........... (5)
      LOGNET   = (6).............
      TRAFLOAD = (7)
      CONGFLAG = (8)
      SLS      = (9)
      MSGLEN   = (10) & (11) & (12) & (13) & (14) & (15) & (16) & (17)
      NBRMSG   = (18)
      TIMER    = (19).
      REPORT   = (20)
      CONTROL  = (21).. & (22) & (23) & (24) & (25) & (26) & (27)
     ------------------------------------------------------------------
     RESULT: (28)
      RTESID      = (29)............
      DEST        = (30)..........  (31)......
      LOGNET      = (32)............
      OPERMODE    = (33).....
      TRAFLOAD    = (34)
      CONGFLAG    = (35)
      NBRSLS      = (36)
      SLS         = (37)
      MSGLEN      = (38) (39) (40) (41) (42) (43) (44) (45)
      NBRMSG      = (46)
      TIMER       = (47) * 30 MINUTES
      REPORT      = (48)
      MTUP STATUS = (49)
  REPORT REFERENCE NUMBER = 6756

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) Requested option
DISPCNT display the MTUP counters
DISPLAY display the present parameters
for the message transfer user
part (MTUP) testing
START start a message transfer user
part (MTUP) test session with the
old and/or new parameters
(2) Routeset name max.16 characters via R_N7RSMNEM
(3) DEST Parameter displayed
(4) Splitted point code in ASCII form (14 characters )
(5) Hexadecimal point code max.14 bits
(6) Logical network name max.16 characters via R_N7LNMNEM
(7) Input traffic load number of messages that must be
sent per second
(8) Input congestion flag flag value
(9) Input signalling link selection (SLS) value for which the test is to be done link number
(10) Input message length
(11) Input message length
(12) Input message length
(13) Input message length
(14) Input message length
(15) Input message length
(16) Input message length
(17) Input message length
(18) Input the total number of messages to be sent
(19) Input timer value time duration in steps of 30
minutes that MTUP has to work
(20) Requested report type
NO REPORTING no on-line reporting
REPORTING on-line reporting
(21) Command control
SCHED schedule request
(22) Start date for the scheduled request month
(23) Start date for the scheduled request day
(24) Start time for the scheduled request hour
(25) Start time for the scheduled request minute
(26) Period for the scheduled request number of hours
(27) Period for the scheduled request number of minutes
(28) Information about errors See EVALUATION
(29) Routeset name max.16 characters via R_N7RSMNEM
(30) Splitted point code max.16 characters via R_N7PCMNEM
(31) Hexadecimal point code max.14 bits
(32) Logical network name max.16 characters via R_N7LNMNEM
(33) Operator mode
ONE WAY one way
TURNROUND turn around
(34) Traffic load number of messages that must be
sent per second
(35) Congestion flag value
(36) Number of signalling link selections
(37) Signalling link selection (SLS) value
(38) Message length
(39) Message length
(40) Message length
(41) Message length
(42) Message length
(43) Message length
(44) Message length
(45) Message length
(46) Total number of messages to be sent
(47) Timer value indicates the time duration that MTUP has to work in steps of 30 minutes
(48) Report type
NO REPORTING no on-line reporting
REPORTING on-line reporting
(49) Message transfer user part (MTUP) status see EVALUATION

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(28) CONGFLAG EQUALS ZERO - NOT ALLOWED . . . . . . . . AC
(28) DEST SUPPORTS ANSI PROTOCOL - ITU EXPECTED . . . . AC
(28) INCORRECT PROTOOL- ITU EXPECTED . . . . . . . . . AC
(28) ITU PC VALUE OUT OF RANGE . . . . . . . . . . . . AC
(28) MODIFY ERROR , SRUR STOPPED . . . . . . . . . . . AC
(28) MTUP TESTING NOT APPL FOR DEST IN EXTERNAL AREA . AC
(28) NO MTUP ACTIVE . . . . . . . . . . . . . . . . . . AC
(28) NO ROUTING FOR DESTINATION . . . . . . . . . . . . AC
(28) SLS NOT SPECIFIED . . . . . . . . . . . . . . . . AC
(28) START NOT ACCEPTED BY SRUR ,OLD VALUES WILL BE RESTORED BC
(28) TIMER AND NO. OF MSG EQUALS ZERO - NOT ALLOWED . . AC
(28) TIMER EXPIRED , OLD VALUES WILL BE RESTORED . . . BC
(28) TIMER EXPIRED BEFORE RECEIVING MESSAGE FROM SRUR . BC
(28) TRAFLOAD EQUALS ZERO - NOT ALLOWED . . . . . . . . AC
(49) DESTINATION INACCESSIBLE . . . . . . . . . . . . . BC
(49) DPC SSF COMBINATION UNKNOWN . . . . . . . . . . . BC
(49) MTUP BUSY . . . . . . . . . . . . . . . . . . . . BC
(49) MTUP DISABLED . . . . . . . . . . . . . . . . . . AC
(49) MTUP LOAD TOO HIGH . . . . . . . . . . . . . . . . AC
(49) MTUP LOCAL BUSY . . . . . . . . . . . . . . . . . BC
(49) MTUP ONE WAY ONLY . . . . . . . . . . . . . . . . AC
(49) MTUP RECEIVE BUSY . . . . . . . . . . . . . . . . BC
(49) MTUP REDUCED ONLY . . . . . . . . . . . . . . . . AC
(49) MTUP REMOTE BUSY . . . . . . . . . . . . . . . . . BC
(49) MTUP TX BUSY . . . . . . . . . . . . . . . . . . . BC
(49) NO ANSWER FROM MTUP-CE . . . . . . . . . . . . . . BC
(49) NO ANSWER FROM REMOTE . . . . . . . . . . . . . . BC
(49) NO FREE CE . . . . . . . . . . . . . . . . . . . . AC
(49) NO USER BUFFER AVAILABLE . . . . . . . . . . . . . AC

Action Description

Action Meaning
AC Check input data:
  • if exact: given result data can be taken as information only,
  • if faulty: correct your input data and repeat the MMC-command.

Special fault clearing is necessary. See fault reporting procedures. Refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide.

BC Repeat the command after some time. If the result is still unsuccessful, special fault clearing will be necessary. See fault reporting procedures. Special fault clearing is necessary. See fault reporting procedures. Refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide.