RRN 00367 ROUTINE TEST - HANDLE ROUTINE TEST

PKBLW002

Message Triggering Condition

This report will be triggered in case of successful / unsuccessful result of the execution, on Operator Request, of one of the following MMC-commands :
CRN 00452 START-RT
CRN 00453 STOP-RT
CRN 00454 CREATE-RT
CRN 00455 REMOVE-RT
CRN 00456 MODIFY-RT
CRN 00457 DISPLAY-RT-ELEMENTS (parameter (option) TESTNBR used)
CRN 00458 SUSPEND-RT
CRN 00459 RESUME-RT

Note: For Basic Accesses with multi-numbering and Operator requests with Directory Numbers, the output will contain all the Directory Numbers entered. Otherwise, only the first Directory Number, as reported by EN-DN Translation, will be used.

Report Layout

   SWA-CENTRAL ROUTINE TEST
      (A).......................                           (B).................
                                         (C)...........................(D).(E)
      -------------------------------------------------------------------------
        TESTNBR  = (1).
        (2)....
        TESTCAT  = (3).
        DEVTYPE  = (4).....
        EPM      = (5)
        REATMODE = (6)
        ITRCL    = (7).....
        ITRRTG   = (8).....
        ITRFM    = (9)... & (10).. & (11)..
        STRDATE  = (12)-(13)
        STRTIME  = (14):(15)
        STOPDATE = (16)-(17)
        STOPTIME = (18):(19)
        PERIOD   = (20)...
        PROCEED  = (21).
        SUSPEND  = (22).
        (23).... = (24).  &  (25).  &  (26).  &  (27).
                   (28).  &  (29).  &  (30).  &  (31).
        TKGPART  = (32).  &  (33).  &&  (34).
        (35)...... (36).  &  (37).  &  (38).  &  (39).
        (40)...... (41).  &  (42).  &  (43).  &  (44).
        (45)...... (46)  (47). &  (48)  (49). &  (50)  (51). &  (52)  (53).
        (54)...... (55)  &  (56)  &  (57)  &  (58)
        (59)...... (60) (61). & (62) (63). & (64) (65). & (66) (67).
        (68)...... (69)............  &  (70)............
                   (71)............  &  (72)............   (73)..............
        (74)...... (75).... & (76)    &    (77).... & (78)
                   (79).... & (80)    &    (81).... & (82)
        AREACODE = (83).
        ALLOCATED TESTNBR = (84)
        ==> (86) / (87)
            (89).... (90) (91) : (92)..........................
                         -->  REF (93)
                         -->  (94)..........................
            DETAILED DB-ERROR INFO :
               REF    FMM     REL     DB-STATUS    ERROR-POINT
               (96)   (97).   (98).     (99)/(100)         (101)
  REPORT REFERENCE NUMBER = 0367

Parameter Identification

Par. No. Meaning Remarks
(A) command name
(B) main execution result
ABORTED execution terminated because of
operator abort request
ALARM STATE = OFF alarm was set off
ALARM STATE = ON alarm was set on
NOT SUCCESSFUL execution terminated because of
error
QUEUED job was accepted and queued for
execution
SUCCESSFUL execution terminated successfully
SUCCESSFULLY STARTED execution started, result follows
later
SYSTEM REPORT the report is generated by the
system without direct connection
to an MMC command
WAITS FOR CONFIRM job was accepted but execution
will be holded until a
confirmation is given
WARNING execution terminated with warning
(C) result part type
FINAL RESULT The report is a final result.
Interim result or result parts
were sent before.
INTERIM RESULT The report is only an interim
result. A final result will
follow.
MEASUREMENT RESULT The report is a measurement
protocol.
RESPONSE TO COMMAND ACTIVATE Used in the area of traffic
measurement.
RESPONSE TO JOB EXECUTION Used in the area of traffic
measurement.
RESULT PART The result must be split into
different result parts. The
different result parts are
numbred from 1 onwards. The sign
(M_CH_SIGN) indicates if another
result part will be sent
(E_CH_PART), or if it is the last
part (E_CH_LAST).
TEST RESULT The report is a test result, e.g.
for line testing.
(D) result part number
(E) continuation indicator
(1) Routine test number specific routine test number
ALL all routine test numbers
only applicable for the
MMC-commands STOP-RT, SUSPEND-LTM
and RESUME-LTM
(2) Global Request header (if applicable) Global Request indicates that the
test groups several other tests
which will run in parallel
GLBREQ header text
(3) Routine test category
LT line test
RT routine test
TESTBUS testbus test
TESTBUS1 testbus test, one by one
TT trunk test
(4) Device type see SI 009
(5) Execution progress mode
(6) Reattempt mode, indicating the number of reattempts
(7) Individual test report class
ATSTEET report with all devices except
those with early termination
ATSTRES report with all devices
NOTSTRES report no devices at all
NSTSTRES report with faulty devices and
devices with early termination
OFTSTRES report with only faulty devices
(8) Individual test report routing
NOREPORT no report routing
REPORT routing to user VDU
(9) Individual test report format (reporting summary and segment results or summary results only)
SUMRES reporting summary results
SUMSEG reporting summary and segment
results
(10) Individual Test report format (segment information)
ALLSEG reporting all segments
FAILSEG reporting faulty segments only
(11) Individual Test report format (reporting global or detailed results
DETRES reporting detailed results
GLBRES reporting global results
(12) Start date of the routine test month
(13) Start date of the routine test day
(14) Start time of the routine test hour
(15) Start time of the routine test minute
(16) Stop date of the routine test month
NONE if no stop date was specified
(17) Stop date of the routine test day
(18) Stop time of the routine test hour
NONE if no stop time was specified
(19) Stop time of the routine test minute
(20) Routine test period for scheduling
(21) Applicability of the option : Proceed, the next period, the routine test where it was stopped before Example :
A routine test is scheduled to
test all lines of the exchange
between 01.00 hour (AM) and 05.00
hour (AM). Suppose that the test
must run daily. If, on a
particular day, not all lines
could be tested during the
specified period, then the
remaining (not tested) lines will
be tested the day after.
FALSE Proceed Test option not
applicable
TRUE Proceed Test option applied
(22) Applicability of the option : Suspend routine test
FALSE Suspend Test option not
applicable
TRUE Suspend Test option applied
(23) Suppressed test segment or test segment header (if applicable)
SUPTSEG Suppressed test segment header
TSEGMENT Test segment header
(24) Suppressed test segment number or test segment number depending on the header indication of Para Nbr 23 specific test segment number :
see SI 015
= ALL : all test segment numbers
(25) Suppressed test segment number or test segment number depending on the header indication of Para Nbr 23 test Segment number : see SI 015
(26) Suppressed test segment number or test segment number depending on the header indication of Para Nbr 23 test segment number : see SI 015
(27) Suppressed test segment number or test segment number depending on the header indication of Para Nbr 23 test segment number : see SI 015
(28) Suppressed test segment number or test segment number depending on the header indication of Para Nbr 23 test Segment number : see SI 015
(29) Suppressed test segment number or test segment number depending on the header indication of Para Nbr 23 test segment number : see SI 015
(30) Suppressed test segment number or test segment number depending on the header indication of Para Nbr 23 test segment number : see SI 015
(31) Suppressed test segment number or test segment number depending on the header indication of Para Nbr 23 test segment number : see SI 015
(32) Identity of trunkgroup to which the trunks, specified in Para Nbr 33 and 34, belong
(33) Identity of trunk, being the first in the range of trunks, belonging to the trunkgroup (Para Nbr 32) involved
(34) Identity of trunk, being the last in the range of trunks, belonging to the trunkgroup (Para Nbr 32) involved
(35) Header which can specify:
DN = directory number (list)
EN = equipment number (list)
GDN = general directory number
LEN = line equipment number (list)
NA = network address (list)
TESTLIST = test number list
TK = trunk (list)
TKG = trunkgroup (list)
(36) Test number
(37) Test number
(38) Test number
(39) Test number
(40) Header which can specify:
(41) Trunkgroup identity (Part Number) belonging to a test number
(42) Trunkgroup identity (Part Number) belonging to a test number
(43) Trunkgroup identity (Part Number) belonging to a test number
(44) Trunkgroup identity (Part Number) belonging to a test number
(45) Header which can specify:
(46) Identity (Part Number) of trunkgroup to which the Trunk, specified in Para Nbr 47, belong
(47) Identity (number) of the trunk, which is part of the trunkgroup (Para Nbr 46), belonging to a test number
(48) Identity (Part Number) of trunkgroup to which the Trunk, specified in Para Nbr 49, belong
(49) Identity (number) of the trunk, which is part of the trunkgroup (Para Nbr 48), belonging to a test number
(50) Identity (Part Number) of trunkgroup to which the trunk, specified in Para Nbr 51, belong
(51) Identity (number) of the trunk, which is part of the trunkgroup (Para Nbr 50), belonging to a test number
(52) Identity (Part Number) of trunkgroup to which the trunk, specified in Para Nbr 53, belong
(53) Identity (number) of the trunk, which is part of the trunkgroup (Para Nbr 52), belonging to a test number
(54) Header which can specify:
(55) Network address of CE (Control Element) belonging to a test number in hexadecimal form (H'zyxw)
(56) Network address of CE (Control Element) belonging to a test number in hexadecimal form (H'zyxw)
(57) Network address of CE (Control Element) belonging to a test number in hexadecimal form (H'zyxw)
(58) Network address of CE (Control Element) belonging to a test number in hexadecimal form (H'zyxw)
(59) Header which can specify:
(60) Network address, part of equipment number, belonging to a test number in hexadecimal form (H'zyxw)
the equipment number consists of
network address and terminal
number
(61) Terminal number, part of equipment number, belonging to a test number the equipment number consists of
network address and terminal
number
(62) Network address, part of equipment number, belonging to a test number in hexadecimal form (H'zyxw)
the equipment number consists of
network address and terminal
number
(63) Terminal number, part of equipment number, belonging to a test number the equipment number consists of
network address and terminal
number
(64) Network address, part of equipment number, belonging to a test number in hexadecimal form (H'zyxw)
the equipment number consists of
network address and terminal
number
(65) Terminal number, part of equipment number, belonging to a test number the equipment number consists of
network address and terminal
number
(66) Network address, part of equipment number, belonging to a test number in hexadecimal form (H'zyxw)
the equipment number consists of
network address and terminal
number
(67) Terminal number, part of equipment number, belonging to a test number the equipment number consists of
network address and terminal
number
(68) Header which can specify:
(69) Directory number keyed numeral
(70) Directory number keyed numeral
(71) Directory number keyed numeral
(72) Directory number keyed numeral
(73) Completion result
*
case of multi-numbering, being
several Directory Numbers
assigned to the same Basic
Access; if no indication,
multi-numbering not present
INVALID DN invalid directory number
ROUTINE TEST STARTED STARTED, SEE MPX REPORT routine test started
started
TIME OUT O&M SACE time out
(74) Header which can specify:
(75) MDF (Main Distribution Frame) identity, being an up to 6-digit line number, part of the line equipment number the line equipment number
consists of an up to 6-digit line
number with optional Remote
Centre identification
appearance of the line equipment
number is CDE-dependent
(76) Position in MDF (Main Distribution Frame), being the Remote Centre identification, part of the line equipment number the line equipment number
consists of an up to 6-digit line
number with optional Remote
Centre identification
if the Remote Centre
identification value equals to
zero, it represents the host
exchange
appearance of the line equipment
number is CDE-dependent
(77) MDF (Main Distribution Frame) identity, being an up to 6-digit line number, part of the line equipment number the line equipment number
consists of an up to 6-digit line
number with optional Remote
Centre identification
appearance of the line equipment
number is CDE-dependent
(78) Position in MDF (Main Distribution Frame), being the Remote Centre identification, part of the line equipment number the line equipment number
consists of an up to 6-digit line
number with optional Remote
Centre identification
if the Remote Centre
identification value equals to
zero, it represents the host
exchange
appearance of the line equipment
number is CDE-dependent
(79) MDF (Main Distribution Frame) identity, being an up to 6-digit line number, part of the line equipment number the line equipment number
consists of an up to 6-digit line
number with optional Remote
Centre identification
appearance of the line equipment
number is CDE-dependent
(80) Position in MDF (Main Distribution Frame), being the Remote Centre identification, part of the line equipment number the line equipment number
consists of an up to 6-digit line
number with optional Remote
Centre identification
if the Remote Centre
identification value equals to
zero, it represents the host
exchange
appearance of the line equipment
number is CDE-dependent
(81) MDF (Main Distribution Frame) identity, being an up to 6-digit line number, part of the line equipment number the line equipment number
consists of an up to 6-digit line
number with optional Remote
Centre identification
appearance of the line equipment
number is CDE-dependent
(82) Position in MDF (Main Distribution Frame), being the Remote Centre identification, part of the line equipment number the line equipment number
consists of an up to 6-digit line
number with optional Remote
Centre identification
if the Remote Centre
identification value equals to
zero, it represents the host
exchange
appearance of the line equipment
number is CDE-dependent
(83) Area code identity keyed numeral
(84) Allocated test number
(86) Comment on execution result see Evaluation
(87) Additonal comment on execution result see Evaluation
(89) Parameter identification (mnemonic)
(90) Argument header (if applicable)
ARG header text
(91) Argument number
(92) Consistency check result see Evaluation
(93) Link
(94) Additional comment see Evaluation
(96) Reference (link)
(97) FMM identity
(98) Relation identity
(99) Data base status see SI 057
(100) Data base status see SI 057
(101) Error point an error point refers in the
source listing to a specific
point in the relation on which
the data base failure occured

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(86) CHANGE OF GROUPING NOT ALLOWED . . . . . . . . . . A
(86) CLEAN-UP IS RUNNING . . . . . . . . . . . . . . . A
(86) COMMAND NOT ALLOWED FOR REMOTE LINE . . . . . . . A
(86) DATA BASE ERROR . . . . . . . . . . . . . . . . . B
(86) DATA BASE ERROR . . . . . . . . . . . . . . . . . B
(86) ENVIRONMENT RELEASE ONGOING, TRY AGAIN AFTER 5 MIN C
(86) FAULT FOUND IN TRANSLATION . . . . . . . . . . . . B
(86) GLOBAL REQUEST SUCCESSFUL . . . . . . . . . . . . A
(86) GROUPING NOT ALLOWED . . . . . . . . . . . . . . . A
(86) HAS WRONG SYNTAX . . . . . . . . . . . . . . . . . A
(86) INCONSISTENT INPUT . . . . . . . . . . . . . . . . A
(86) INVALID DN . . . . . . . . . . . . . . . . . . . . A
(86) NO FREE TESTNBR FOUND . . . . . . . . . . . . . . C
(86) NO TEST AVAILABLE . . . . . . . . . . . . . . . . A
(86) NO TESTNBR FOUND . . . . . . . . . . . . . . . . . A
(86) PROCEED FUNCTION IS DEACTIVATED . . . . . . . . . A
(86) ROUTINE TEST ALREADY REQUESTED . . . . . . . . . . A
(86) ROUTINE TEST QUEUE BUSY . . . . . . . . . . . . . C
(86) ROUTINE TEST STARTED . . . . . . . . . . . . . . . A
(86) ROUTINE TEST STOPPED . . . . . . . . . . . . . . . A
(86) ROUTINE TEST SUSPENDED . . . . . . . . . . . . . . A
(86) ROUTINE TEST WAITING FOR EXECUTION . . . . . . . . A
(86) SYSTEM ERROR . . . . . . . . . . . . . . . . . . . B
(86) SYSTEM ERROR . . . . . . . . . . . . . . . . . . . B
(86) TEST CREATED . . . . . . . . . . . . . . . . . . . A
(86) TEST IS RUNNING . . . . . . . . . . . . . . . . . A
(86) TEST MODIFIED . . . . . . . . . . . . . . . . . . A
(86) TEST NOT EXECUTING . . . . . . . . . . . . . . . . C
(86) TEST NOT REMOVED . . . . . . . . . . . . . . . . . C
(86) TESTNBR MISSING . . . . . . . . . . . . . . . . . A
(86) TIME OUT O&M SACE . . . . . . . . . . . . . . . . C
(86) TRANSLATION ERROR . . . . . . . . . . . . . . . . B
(87) DB ERROR AFTER STOP-TIMER STARTED . . . . . . . . B
(87) DB ERROR AFTER TIMER CANCELLED . . . . . . . . . . B
(87) DB ERROR AFTER TIMER IMPLEMENTED . . . . . . . . . B
(87) NO TIMER CANCELLED . . . . . . . . . . . . . . . . C
(87) ONLY START-TIMER IMPLEMENTED . . . . . . . . . . . C
(87) ONLY STOP-TIMER CANCELLED . . . . . . . . . . . . C
(87) TIMER NOT CHANGED . . . . . . . . . . . . . . . . C
(87) TIMER NOT IMPLEMENTED . . . . . . . . . . . . . . C
(92) CORRESPONDING PLANE IN WRONG STATUS . . . . . . . A
(92) DATA BASE ERROR . . . . . . . . . . . . . . . . . B
(92) DEVTYPE NOT ALLOWED IN GLOBAL TEST . . . . . . . . A
(92) FAULT FOUND IN TRANSLATION . . . . . . . . . . . . B
(92) FIRST TKNBR NOT FOUND . . . . . . . . . . . . . . A
(92) HAS NO ALLOCATED TRUNK . . . . . . . . . . . . . . A
(92) HAS WRONG DEVTYPE . . . . . . . . . . . . . . . . A
(92) HAS WRONG SYNTAX . . . . . . . . . . . . . . . . . A
(92) HAS WRONG TESTCAT . . . . . . . . . . . . . . . . A
(92) IN CONFLICT WITH TESTCAT . . . . . . . . . . . . . A
(92) INVALID DN . . . . . . . . . . . . . . . . . . . . A
(92) INVALID GDN . . . . . . . . . . . . . . . . . . . A
(92) INVALID TESTSEGMENT . . . . . . . . . . . . . . . A
(92) INVALID TRUNK . . . . . . . . . . . . . . . . . . A
(92) IS NOT EQUIPPED . . . . . . . . . . . . . . . . . A
(92) IS NOT IN TRAFFIC . . . . . . . . . . . . . . . . A
(92) NO PROCEEDING TESTS ALLOWED . . . . . . . . . . . A
(92) NO STARTTIME PRESENT . . . . . . . . . . . . . . . A
(92) NO TEST APPLICABLE . . . . . . . . . . . . . . . . A
(92) NO TEST AVAILABLE . . . . . . . . . . . . . . . . A
(92) NO VALID DEVICE FOUND . . . . . . . . . . . . . . A
(92) NOT ALL PLANES IN SERVICE . . . . . . . . . . . . A
(92) NOT ALLOWED FOR CURRENT FOLDSTAGE . . . . . . . . A
(92) NOT CONSISTENT WITH DEVTYPE . . . . . . . . . . . A
(92) NOT CONSISTENT WITH FOLDSTAGE . . . . . . . . . . A
(92) NOT EXISTING . . . . . . . . . . . . . . . . . . . A
(92) NOT USED AS OUTGOING TRUNK GROUP . . . . . . . . . A
(92) SECOND TKNBR NOT FOUND . . . . . . . . . . . . . . A
(92) STOPTIME EARLIER THAN STARTTIME . . . . . . . . . A
(92) SYSTEM ERROR . . . . . . . . . . . . . . . . . . . B
(92) TRANSLATION ERROR . . . . . . . . . . . . . . . . B
(92) TRUNK GROUP NOT EXISTING . . . . . . . . . . . . . A
(92) TRUNK GROUP NOT USED IN A ROUTE . . . . . . . . . A
(94) AREACODE NOT IN PLAN . . . . . . . . . . . . . . . A
(94) DATABASE ERROR . . . . . . . . . . . . . . . . . . A
(94) DATABASE ERROR . . . . . . . . . . . . . . . . . . A
(94) DIALNUMBER IS FACILITY OR ANNOUNCEMENT . . . . . . A
(94) DIALNUMBER NOT IN PLAN . . . . . . . . . . . . . . A
(94) DIALNUMBER TOO LONG . . . . . . . . . . . . . . . A
(94) DIALNUMBER TOO SHORT . . . . . . . . . . . . . . . A
(94) INVALID DN . . . . . . . . . . . . . . . . . . . . A
(94) NETWORK ADDRESS N.O.K., NO SUBSCRIBER CE . . . . . A
(94) NETWORK ADDRESS NOT IN SYSTEM . . . . . . . . . . A
(94) NO FREE PROCESS . . . . . . . . . . . . . . . . . C
(94) NO SUBSCRIBER CONNECTED . . . . . . . . . . . . . A
(94) NOT OK : REMOTE LINE . . . . . . . . . . . . . . . A
(94) PABX . . . . . . . . . . . . . . . . . . . . . . . A
(94) PBX . . . . . . . . . . . . . . . . . . . . . . . A
(94) REQUEST NOT ALLOWED . . . . . . . . . . . . . . . A
(94) SOFTWARE FAULT . . . . . . . . . . . . . . . . . . B
(94) SUBSCRIBER NOT CREATED . . . . . . . . . . . . . . A
(94) SUBSCRIBER NOT CREATED . . . . . . . . . . . . . . A
(94) TERMINAL NUMBER OUT OF RANGE . . . . . . . . . . . A

Action Description

Action Meaning
A
  • The given result data can be taken as an information only.
  • The result data are given as an error message when inconsistent data

are detected during the check of the operation, which is specified by the specific input parameters.

Check input data. If applicable, see also Restrictions part of the corresponding MMC-command.

If input data are correct:

  • The given result data can be taken as information only.
  • The result data is given as an error message when inconsistent data are detected during the check of the operation, which is specified by the specific input parameters
    • Special fault clearing will be necessary.
    • If applicable, see fault reporting procedures (refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide).
  • If input data are not correct, repeat the MMC-command with corrected

data.

B Special fault clearing will be necessary.

If applicable, see fault reporting procedures (refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide).

C Repeat the command (maybe) 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.