RRN 05570 HANDLE ROUTING CALENDAR (UNSUCCESSFUL)

CJ1BXI03

Message Triggering Condition

Response in case of unsuccessful result of the execution, on operator request, of one of the following MMC-commands:
CRN 07475 CREATE-ROUTING-CALENDAR
CRN 07476 MODIFY-ROUTING-CALENDAR
CRN 07477 REMOVE-ROUTING-CALENDAR
CRN 07478 DISPLAY-ROUTING-CALENDAR

This report is also triggered as a last report after the display of the old data, to indicate that the remove is executed successfully, which is requested via the MMC-command:
CRN 07477 REMOVE-ROUTING-CALENDAR

Report Layout

 SWA-PATED COMMAND HDLR
    (A).......................                   (B).................
                                 (C)........................... (D) (E)
    -----------------------------------------------------------------
        (1)............................................... (2) (3) (4).
  REPORT REFERENCE NUMBER = 5570

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
numbered 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) Comments on the execution result/error indication
(2) Day If applicable
(3) Month indication of
APR April
AUG August
DEC December
FEB February
JAN January
JUL July
JUN June
MAR March
MAY May
NOV November
OCT October
SEP September
(4) Year the data

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(1) CURRENT DAY MAY NOT BE REMOVED . . . . . . . . . . A
(1) DATABASE ERROR . . . . . . . . . . . . . . . . . . B
(1) DATE ALREADY IN CALENDAR . . . . . . . . . . . . . A
(1) DATE NOT IN CALENDAR . . . . . . . . . . . . . . . A
(1) DATE NOT IN FUTURE . . . . . . . . . . . . . . . . A
(1) DUT EOT FAILURE . . . . . . . . . . . . . . . . . B
(1) DUT SOT FAILURE . . . . . . . . . . . . . . . . . B
(1) HOLIDAY CALENDAR DOES NOT EXIST . . . . . . . . . A
(1) PAST YEAR NOT ALLOWED . . . . . . . . . . . . . . A
(1) YEAR HAS TO BE REMOVED COMPLETELY . . . . . . . . A
(1) YEAR NOT IN CALENDAR . . . . . . . . . . . . . . . A
(1) YEAR NOT REMOVED COMPLETELY . . . . . . . . . . . A
(1) YEAR TOO FAR IN FUTURE . . . . . . . . . . . . . . A

Action Description

Action Meaning
A The result data is given as an error message, when an inconsistent data is detected during the check of the operation, which is specified by the specific input parameters, whether is valid and in conflict with the existing data. Correct the input data and enter the MMC-command again.If applicable, see also Restrictions part of the corresponding MC-command. If the input data is correct, the given result data can be taken as an information only or special fault clearing will be necessary. In that case, continue with the Action B.
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.