RRN 04789 ROUTINE TEST

A2CHWT04

Message Triggering Condition

Result report for the following command, which has been caused by an operator input:
CRN 04909 DISPLAY-RT-REPORT

Report Layout

   ROUTINE TEST
      (A).......................                           (B).................
                                                 (C)...........................
      -------------------------------------------------------------------------
      CONTROL        =  (1).             DATE           = (2)/(3)
                                         TIME           =  (4):(5)
                                         PERIOD (H:MIN) =  (6):(7)
      STRDATE        = (8)../(9)/(10)      START TIME     =  (11):(12)
      STOP DATE      = (13)./(14)/(15)      STOP TIME      =  (16):(17)
      RANGE          =  (18)...
      REPTYPE        =  (19)....
      TESTCAT        =  (20).
      REPMODE        =  (21)..
      RESULT         =  (22)..
      TESTLIST       =  (23). & (24). & (25). & (26).
                        (27). & (28). & (29). & (30).
      DEVTYPE        =  (31).... & (32).... & (33).... & (34)....
                        (35).... & (36).... & (37).... & (38)....
      (39)....................................................
                                                NBR SUCC
      TESTNBR DEVTYPE T-DATE  T-START T-END     TESTED   TESTCAT  RESULT
      (41). (42).... (43).-   -     (46):     (48):     (50).    (51).  (52)..
                 CAUSE   :(53) (54).....................
                 TEST CONTINUES(55)
                 (56).......................................
                 (57)...........................
                 (58)..  (59). && (60).  (61)
                 (62)...........................
                 (63).   (64).           (65).....................
  REPORT REFERENCE NUMBER = 4789

Parameter Identification

Par. No. Meaning Remarks
(A) command name
(B) main execution result
(C) result part type
(1) Control parameter
(2) Start date Month: Starting with this date, a
periodic output of the results of
automatic routine tests has been
created.
(3) Start date Day: Starting with this date, a
periodic output of the results of
automatic routine tests has been
created.
(4) Start time Hour: Starting with this time, a
periodic output of the results of
automatic routine tests has been
created.
(5) Start time Minute: Starting with this time,
a periodic output of the results
of automatic routine tests has
been created.
(6) Period Hour: Period created to output
the results of automatic routine
tests.
(7) Period Minute: Period created to output
the results of automatic routine
tests.
(8) Start date Year: The results of automatic
routine tests stored after this
date are output.
(9) Start date Month: The results of automatic
routine tests stored after this
date are output.
(10) Start date Day: The results of automatic
routine tests stored after this
date are output.
(11) Start time Hour: The results of automatic
routine tests stored after this
time are output.
(12) Start time Minute: The results of automatic
routine tests stored after this
time are output.
(13) Stop date Year: The results of automatic
routine tests stored up to this
date are output.
(14) Stop date Month: The results of automatic
routine tests stored up to this
date are output.
(15) Stop date Day: The results of automatic
routine tests stored up to this
date are output.
(16) Stop time Hour: The results of automatic
routine tests stored up to this
time are output.
(17) Stop time Minute: The results of automatic
routine tests stored up to this
time are output.
(18) Range Retrospective to this range, the
results stored from automatic
routine tests are output.
PT1D Results of the last day
PT2D Results of the last 2 days
PT3D Results of the last 3 days
PT4D Results of the last 4 days
PT5D Results of the last 5 days
PT6D Results of the last 6 days
PT7D Results of the last 7 days
(19) Report type A comprehensive reproduction or a
summary of the results stored
from the routine tests is
provided.
(20) Test category The results of automatic device
and/or trunk tests are output.
(21) Report mode The output of test results or
detailed test results follows.
(22) Result Successful and/or unsuccessful
test results are output. In the
case of the FAIL parameter, only
reports whose result is
UNSUCCESSFUL or which contain a
list of non-tested or faulty
devices or trunks are output.
(23) Test Number Test numbers between 1 and 500.
(24) Test number
(25) Test number
(26) Test number
(27) Test number
(28) Test number
(29) Test number
(30) Test number
(31) Device type (see TABLE 009)
(32) Device type (see TABLE 009)
(33) Device type (see TABLE 009)
(34) Device type (see TABLE 009)
(35) Device type (see TABLE 009)
(36) Device type (see TABLE 009)
(37) Device type (see TABLE 009)
(38) Device type (see TABLE 009)
(39) Result Information on successful or
unsuccessful execution of the
command DISPLAY-RT-REPORT.
(41) Test number
(42) Device type (see TABLE 009)
(43) Test date Year, month, day
(46) Test start Hour, minute
(48) Test end Hour, minute
(50) Number Number of successfully tested
devices or trunks
(51) Test category
(52) Result Result of the routine test
(53)
(54) Cause Cause of the unsuccessful routine
test (see REPREFR 156)
(55) Continued Note: in the case of a test which
has been created with the PROCEED
option.
(56) Table header
(57) Header
(58) Network address
(59) Device number
(60) Device number
(61) Cause Cause of the unsuccessful routine
test (see REPREFR 156)
(62) Table header
(63) Trunk group identity
(64) Trunk number
(65) Cause Cause of the unsuccessful routine
test (see REPREF 1105)

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(39) COMMAND NOT ALLOWED NOW! . . . . . . . . . . . . . C
(39) DB ACCESS UNSUCCESSFUL . . . . . . . . . . . . . . A
(39) ERROR IN LDH: DB ACCESS UNSUCCESSFUL . . . . . . . A
(39) ERROR IN LDH: FILE ACCESS UNSUCCESSFUL . . . . . . A
(39) ERROR IN LDH: NO MORE USER BUFFER AVAILABLE . . . C
(39) ERROR IN LDH: TOO FEW WORK FILES . . . . . . . . . E
(39) ERROR IN LDH: TOO FEW WORK FILES DEFINED . . . . . E
(39) ERROR IN LDH: WORK FILES CANNOT BE DELETED . . . . A
(39) ERROR ON READING FROM THE HARD DISK . . . . . . . A
(39) FAULTY FILE DESCRIPTION . . . . . . . . . . . . . A
(39) LDH HAS NOT INITIALISED FILES . . . . . . . . . . F
(39) LOGDATA HANDLER BUSY . . . . . . . . . . . . . . . C
(39) LOGGER HAS CHANGED FILES . . . . . . . . . . . . . B
(39) NO REPORTS AVAILABLE . . . . . . . . . . . . . . . D
(39) NO RESPONSE FROM LOGDATA HANDLER . . . . . . . . . B
(39) OVERFLOW, SPECIFY REQUEST MORE EXACTLY . . . . . . B
(39) SOFTWARE ERROR . . . . . . . . . . . . . . . . . . A
(39) TIME TO REQUEST NEW FILE EXPIRED . . . . . . . . . A
(39) TOO MANY INTERMEDIATE REPORTS FOR ONE TEST NUMBER E

Action Description

Action Meaning
A Retry job, if unsuccessful, special fault clearance by system specialist.
B Verify input and retry job.
C Retry job at specified time.
D With job DISPLAY LOG FUNCTION, verify whether unsolicited reports are active. If yes, select other input values. If not, activate the parameter LOGTYPE = UNSOLREP with job CONTROL LOG FUNCTION, then restart delayed RT job and activate the command DISPLAY-RT-REPORT again.
E Select a smaller range as input value.
F Initiate the files for UNSOLICITED REPORTS with the job CONTROL LOG FUNCTION.