RRN 05228 SUBROUTEBLOCK CONTROL ASSIGNMENT: BAD RESULTS REPORT

BNL1XJ11

Message Triggering Condition

Response in case of unsuccessful result of the execution, on operator request, of one the following MMC-command:
CRN 07676 ASSIGN-SRTGBLK-CONTROL

Report Layout

SWA-NETW MNGR COM HNDLR
   |
   |(A).......................                   (B).................
   |                             (C)........................... (D) (E)
   |-----------------------------------------------------------------
      (1)AD RESULTS REPORT
      -----------------------------------------------------------------------
      RESULT = (2)
      REASON (3) (4) (5) (6) (7) (8) (9) (10)
      RELATION         = (11)
      DATABASE COMMAND = (12)
      DATABASE STATUS  = (13)
      POSSIBLE ACTIONS = (14)
  REPORT REFERENCE NUMBER = 5228

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) Title
(2) Result of the subrouteblock control action
(3) Title
(4) RTGBLK reason for failure see Evaluation
(5) DISTGRP reason for failure see Evaluation
(6) TKGCOM reason for failure see Evaluation
(7) TKGCOML reason for failure see Evaluation
(8) SRTGBLK reason for failure see Evaluation
(9) SRTGBLK reason for failure see Evaluation
(10) NM reason for failure see Evaluation
(11) Relation name (identity)
(12) Database command type
(13) Database status see Evaluation
(14) Possible actions that should be performed see Evaluation

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(4) BLOCK SEQUENCE ERROR IN BUFFER . . . . . . . . . . C
(4) BOTH ACTIVE AND PASSIVE IS NOT ALLOWED . . . . . . B
(4) BUFFER ERROR . . . . . . . . . . . . . . . . . . . C
(4) DEPENDENCY COMBINATION BARRED . . . . . . . . . . B
(4) DEPENDENCY COMBINATION IS BARRED . . . . . . . . . B
(4) ERROR WHILE CLOSING A SUB-DUT . . . . . . . . . . C
(4) ERROR WHILE CLOSING THE MAIN-DUT . . . . . . . . . C
(4) ERROR WHILE OPENING A SUB-DUT . . . . . . . . . . C
(4) ERROR WHILE OPENING THE MAIN-DUT . . . . . . . . . C
(4) ERROR WHILE ROLLING-BACK A SUB-DUT . . . . . . . . C
(4) ERROR WHILE ROLLING-BACK THE MAIN-DUT . . . . . . C
(4) ILLEGAL DEPENDENCY COMBINATION RESULT . . . . . . B
(4) ILLEGAL FUNCTION IDENTIFICATION . . . . . . . . . B
(4) ILLEGAL OBJECT TYPE FOR THIS FUNCTION & SUB-FUNCTION B
(4) ILLEGAL SUB-FUNCTION IDENTIFICATION . . . . . . . B
(4) MODULATION ERROR . . . . . . . . . . . . . . . . . B
(4) NEW MNEMONIC ALREADY USED . . . . . . . . . . . . B
(4) NO SPACE FOR BEARER DEPENDENCIES . . . . . . . . . B
(4) NO SPACE FOR CDE DEPENDENCIES . . . . . . . . . . B
(4) NO SPACE FOR NEW RTGBLK . . . . . . . . . . . . . C
(4) NO SPACE FOR SIGNALLING DEPENDENCIES . . . . . . . B
(4) OTHER FMM DID NOT ACKNOWLEDGE HIS ACTIVATION MSG . C
(4) OTHER FMM NOT ACTIVE ANYMORE . . . . . . . . . . . C
(4) REFERENCED OBJECT IDENTIFICATION NOT ALLOWED . . . B
(4) RTGBLK IS STILL USED BY CONTROL KEYS . . . . . . . B
(4) RTGBLK IS STILL USED FOR BROADBAND . . . . . . . . B
(4) RTGBLK IS STILL USED FOR PABX OVERFLOW . . . . . . B
(4) RTGBLK IS STILL USED IN PATED . . . . . . . . . . B
(4) THE REFERENCED OBJECT DOES NOT EXIST . . . . . . . B
(4) TONE NOT ALLOWED FOR THE USED RTGBLK TYPE . . . . B
(4) WRONG RESULT IN BEARER DEPENDENCIES . . . . . . . B
(4) WRONG RESULT IN CDE DEPENDENCIES . . . . . . . . . B
(4) WRONG RESULT IN SIGNALLING DEPENDENCIES . . . . . B
(5) BUFFER ERROR . . . . . . . . . . . . . . . . . . . C
(5) BUFFER INCOMPLETE . . . . . . . . . . . . . . . . C
(5) DISTGRP STILL USED . . . . . . . . . . . . . . . . B
(5) ERROR WHILE CLOSING A SUB-DUT . . . . . . . . . . C
(5) ERROR WHILE CLOSING THE MAIN-DUT . . . . . . . . . C
(5) ERROR WHILE OPENING A SUB-DUT . . . . . . . . . . C
(5) ERROR WHILE OPENING THE MAIN-DUT . . . . . . . . . C
(5) ERROR WHILE ROLLING-BACK A SUB-DUT . . . . . . . . C
(5) ERROR WHILE ROLLING-BACK THE MAIN-DUT . . . . . . C
(5) ILLEGAL FUNCTION IDENTIFICATION . . . . . . . . . B
(5) ILLEGAL OBJECT TYPE . . . . . . . . . . . . . . . B
(5) ILLEGAL SUB FUNCTION IDENTIFICATION . . . . . . . B
(5) INVALID HUNTING TYPE . . . . . . . . . . . . . . . B
(5) INVALID NUMBER SKIP VALUES . . . . . . . . . . . . B
(5) INVALID REFERENCE . . . . . . . . . . . . . . . . B
(5) NEW MNEMONIC ALREADY USED . . . . . . . . . . . . B
(5) NO ACKNOWLEDGE FROM OTHER DATA HANDLER . . . . . . C
(5) NO DISTGRP FOUND . . . . . . . . . . . . . . . . . B
(5) NO EMPTY SRTGBLK CHN CHAIN ALLOWED . . . . . . . . B
(5) NO MORE SPACE IN FUNC BUFFER . . . . . . . . . . . C
(5) NO SPACE FOR A NEW DISTGRP . . . . . . . . . . . . B
(5) NO SPACE FOR NEW SRTGBLK CHAIN . . . . . . . . . . B
(5) NO SPACE IN RANDOM NUMBER RELATION . . . . . . . . B
(5) NO SPACE IN TRAF DIST CHAIN RELATION . . . . . . . B
(5) NO SPACE IN TRAF DIST RELATION . . . . . . . . . . B
(5) NOT EXISTING DISTGRP . . . . . . . . . . . . . . . B
(5) OTHER DATA HANDLER NOT ACTIVE . . . . . . . . . . C
(5) POSITION NOT EXISTING IN SRTGBLK CHAIN . . . . . . B
(5) REFERENCE NOT ALLOWED . . . . . . . . . . . . . . B
(5) SRTGBLK CHAIN TOO LARGE . . . . . . . . . . . . . B
(6) CARRIER NOT APPLICABLE . . . . . . . . . . . . . . B
(6) COMPANY NOT APPLICABLE . . . . . . . . . . . . . . B
(6) DEPENDENCY COMBINATION CANNOT BE HANDLED BY TKG . B
(6) ERROR WHILE CLOSING A SUB-DUT . . . . . . . . . . C
(6) ERROR WHILE CLOSING THE MAIN-DUT . . . . . . . . . C
(6) ERROR WHILE OPENING A SUB-DUT . . . . . . . . . . C
(6) ERROR WHILE OPENING THE MAIN-DUT . . . . . . . . . C
(6) ERROR WHILE ROLLING-BACK A SUB-DUT . . . . . . . . C
(6) ERROR WHILE ROLLING-BACK THE MAIN-DUT . . . . . . C
(6) ILLEGAL FUNCTION IDENTIFICATION . . . . . . . . . B
(6) ILLEGAL OBJECT TYPE . . . . . . . . . . . . . . . C
(6) ILLEGAL SUB FUNCTION IDENTIFICATION . . . . . . . C
(6) INVALID REFERENCE . . . . . . . . . . . . . . . . B
(6) NEW MNEMONIC ALREADY USED . . . . . . . . . . . . B
(6) NO ACKNOWLEDGE FROM OTHER DATA HANDLER . . . . . . C
(6) NO EMPTY TKG CHAIN ALLOWED . . . . . . . . . . . . B
(6) NO INTEROFFICE TKG . . . . . . . . . . . . . . . . B
(6) NO MORE SPACE IN FUNC BUFFER . . . . . . . . . . . C
(6) NO SPACE FOR NEW TKG CHAIN . . . . . . . . . . . . B
(6) NO SPACE FOR NEW TKGCOM . . . . . . . . . . . . . B
(6) NO TKGCOM FOUND . . . . . . . . . . . . . . . . . B
(6) NOT EXISTING TKGCOM . . . . . . . . . . . . . . . B
(6) OTHER DATA HANDLER NOT ACTIVE . . . . . . . . . . C
(6) POSITION NOT EXISTING IN TKG CHAIN . . . . . . . . B
(6) REFERENCE NOT ALLOWED . . . . . . . . . . . . . . B
(6) ROUTE NOT APPLICABLE . . . . . . . . . . . . . . . B
(6) TKG CHAIN TOO LARGE . . . . . . . . . . . . . . . B
(6) TKG NOT IN CORRECT ROUTE . . . . . . . . . . . . . B
(6) TKGCOM STILL USED . . . . . . . . . . . . . . . . B
(6) TKGCOML LAYER NOT EXISTING . . . . . . . . . . . . B
(7) BUFFER ERROR . . . . . . . . . . . . . . . . . . . C
(7) BUFFER INCOMPLETE . . . . . . . . . . . . . . . . C
(7) ERROR WHILE CLOSING A SUB-DUT . . . . . . . . . . C
(7) ERROR WHILE CLOSING THE MAIN-DUT . . . . . . . . . C
(7) ERROR WHILE OPENING A SUB-DUT . . . . . . . . . . C
(7) ERROR WHILE OPENING THE MAIN-DUT . . . . . . . . . C
(7) ERROR WHILE ROLLING-BACK A SUB-DUT . . . . . . . . C
(7) ERROR WHILE ROLLING-BACK THE MAIN-DUT . . . . . . C
(7) ILLEGAL FUNCTION IDENTIFICATION . . . . . . . . . B
(7) ILLEGAL OBJECT TYPE . . . . . . . . . . . . . . . B
(7) ILLEGAL SUB FUNCTION IDENTIFICATION . . . . . . . B
(7) INVALID NUMBER SKIP VALUES . . . . . . . . . . . . B
(7) INVALID REFERENCE . . . . . . . . . . . . . . . . B
(7) NEW MNEMONIC ALREADY USED . . . . . . . . . . . . B
(7) NO ACK FROM OTHER DATA HANDLER . . . . . . . . . . B
(7) NO EMPTY TKGCOM CHAIN ALLOWED . . . . . . . . . . B
(7) NO FUNCTION BUFFER SPACE . . . . . . . . . . . . . B
(7) NO SPACE FOR A NEW TKGCOML . . . . . . . . . . . . B
(7) NO SPACE FOR NEW TKGCOM CHAIN . . . . . . . . . . B
(7) NO SPACE IN RANDOM NUMBER RELATION . . . . . . . . B
(7) NO SPACE IN TRAF DIST CHAIN RELATION . . . . . . . B
(7) NO SPACE IN TRAF DIST RELATION . . . . . . . . . . B
(7) NO TKGCOML FOUND . . . . . . . . . . . . . . . . . B
(7) NOT EXISTING TKGCOML . . . . . . . . . . . . . . . B
(7) OTHER DATA HANDLER NOT ACTIVE . . . . . . . . . . C
(7) POSITION NOT EXISTING IN TKGCOM CHAIN . . . . . . B
(7) REFERENCE NOT ALLOWED . . . . . . . . . . . . . . B
(7) TAR TYPE INCONSISTENT . . . . . . . . . . . . . . B
(7) TKGCOM CHAIN TOO LARGE . . . . . . . . . . . . . . B
(7) TKGCOML STILL USED . . . . . . . . . . . . . . . . B
(8) ASSIGNING NM CONTROL DATA TO TAR SRTGBLK NALLWD . B
(8) BUFFER INCOMPLETE . . . . . . . . . . . . . . . . C
(8) BUFFER NOT FILLED IN CORRECTLY . . . . . . . . . . C
(8) CALL GAPPING PERIODS NOT EXISTING . . . . . . . . B
(8) CLOSING A SUB-DUT . . . . . . . . . . . . . . . . C
(8) CLOSING THE MAIN-DUT . . . . . . . . . . . . . . . C
(8) CONFLICT BETWEEN HUNTING MECHANISM AND SKIP VALUES B
(8) DISTGRP LAYER NOT EXISTING . . . . . . . . . . . . B
(8) HUNTING MECHANISM NALLWD . . . . . . . . . . . . . B
(8) ILLEGAL FUNCTION IDENTIFICATION . . . . . . . . . B
(8) ILLEGAL NM CONTROL TYPE . . . . . . . . . . . . . B
(8) ILLEGAL OBJECT TYPE . . . . . . . . . . . . . . . B
(8) ILLEGAL SUB FUNCTION IDENTIFICATION . . . . . . . B
(8) INVALID NUMBER OF SKIP VALUES . . . . . . . . . . B
(8) INVALID REFERENCE . . . . . . . . . . . . . . . . B
(8) NEW CHAIN NALLWD BECAUSE SRTGBLK WITH NM . . . . . B
(8) NEW MNEMONIC ALREADY USED . . . . . . . . . . . . B
(8) NEW NEXT LAYER TKGCOM, BUT NO TKGCOM CHAIN SPECIFIED B
(8) NEW NEXT LAYER TKGCOM: REMOVE ACTION IS NALLWD . . B
(8) NEW NEXT LAYER TKGCOML, BUT NO TKGCOML CHAIN SPECIFIED B
(8) NEW NEXT LAYER TKGCOML: REMOVE ACTION IS NALLWD . B
(8) NM CONTROL DATA ASSIGNED ALREADY . . . . . . . . . B
(8) NO ACK FROM OTHER DATA HANDLER . . . . . . . . . . C
(8) NO COMPANY INFO FOUND . . . . . . . . . . . . . . B
(8) NO DEPENDENCY COMBINATIONS FOUND FOR SRTGBLK . . . B
(8) NO EMPTY TKGCOM CHAIN ALLWD . . . . . . . . . . . B
(8) NO EMPTY TKGCOML CHAIN ALLWD . . . . . . . . . . . B
(8) NO MORE SPACE IN FUNC BUFFER . . . . . . . . . . . C
(8) NO NM CONTROL DATA ASSIGNED . . . . . . . . . . . B
(8) NO NM CONTROL DATA FOUND . . . . . . . . . . . . . B
(8) NO SPACE FOR NEW SRTGBLK . . . . . . . . . . . . . C
(8) NO SRTGBLK FOUND . . . . . . . . . . . . . . . . . B
(8) NOT EXISTING SRTGBLK . . . . . . . . . . . . . . . B
(8) OPENING A SUB-DUT . . . . . . . . . . . . . . . . C
(8) OPENING THE MAIN-DUT . . . . . . . . . . . . . . . C
(8) OTHER DATA HANDLER NOT ACTIVE . . . . . . . . . . C
(8) POSITION NOT EXISTING IN CHAIN . . . . . . . . . . B
(8) REFERENCE NALLWD . . . . . . . . . . . . . . . . . B
(8) RESPONSE CATEGORY MUST BE SPECIFIED . . . . . . . B
(8) ROLLING-BACK A SUB-DUT . . . . . . . . . . . . . . C
(8) ROLLING-BACK THE MAIN-DUT . . . . . . . . . . . . C
(8) SPECIFIED SRTGBLK IS NOT A TAR SRTGBLK . . . . . . B
(8) SRTGBLK CANNOT BE REPLACED BY SRTGBLK WITH DIFFERENT TYPE B
(8) SRTGBLK USED IN DISTGRP LAYER . . . . . . . . . . B
(8) SRTGBLK USED IN RTGBLK LAYER . . . . . . . . . . . B
(8) TAR SRTGBLK IS STILL USED BY A NORMAL SRTGBLK . . B
(8) TKGCOM CHAIN TOO LARGE . . . . . . . . . . . . . . B
(8) TKGCOML CHAIN TOO LARGE . . . . . . . . . . . . . B
(8) WRONG REFERENCE TO SRTGBLK SPECIFIED . . . . . . . B
(9) . . . . . . . . . . . . . . . . . . . . . . . . . B
(9) A PARENT SRTGBLK MUST REMAIN A PARENT . . . . . . B
(9) MODIFY REFERENCED IDENTIFIED PARENT SRTGBLK NALLWD B
(9) MODIFY REFERENCED IDENTIFIED SRTGBLK WITH NM NALLWD B
(9) NALLWD TO MOD SRTGBLK WITH NM WHEN ANOTHER SRTGBLK USED AS REF B
(9) NM TO PARENT SRTGBLK NALLWD . . . . . . . . . . . B
(9) NO NORMAL SRTGBLK SPECIFIED . . . . . . . . . . . B
(9) NO SPACE FOR NEW CALL GAPPING PERIODS . . . . . . B
(9) NO SPACE FOR NEW TKGCOM CHAIN . . . . . . . . . . B
(9) NO SPACE FOR NEW TKGCOML CHAIN . . . . . . . . . . B
(9) NO SPACE IN NM RELATION . . . . . . . . . . . . . B
(9) NO SPACE IN RANDOM NUMBER RELATION . . . . . . . . B
(9) NO SPACE IN TRAF DIST CHAIN RELATION . . . . . . . B
(9) NO SPACE IN TRAF DIST RELATION . . . . . . . . . . B
(9) REMOVE A PARENT SRTGBLK NALLWD . . . . . . . . . . B
(9) RENAME A SRTGBLK WITH NM NALLWD . . . . . . . . . B
(9) RENAME A TAR-SRTGBLK NALLWD . . . . . . . . . . . B
(9) SOME CALL GAPPING PERIODS MISSING . . . . . . . . B
(9) SPECIFIED SRTGBLK IS A CHILD . . . . . . . . . . . B
(9) SPECIFIED SRTGBLK IS NOT A CHILD . . . . . . . . . B
(9) SPECIFIED SRTGBLK WITH NM BECOME A PARENT IS NALLWD B
(9) SRTGBLK HAS TKGCOM CHAIN . . . . . . . . . . . . . B
(9) SRTGBLK HAS TKGCOML CHAIN . . . . . . . . . . . . B
(9) SRTGBLK, USED AS REFERENCE, WITH NM NALLWD . . . . B
(9) TAR SRTGBLK MISSING . . . . . . . . . . . . . . . B
(9) TAR-SRTGBLK CAN NOT BE USED IN DISTGRP OR RTGBLK . B
(9) TKGCOM AS NM APPL POINT NOT IN CHAIN . . . . . . . B
(9) TKGCOML AS NM APPL POINT NOT IN CHAIN . . . . . . B
(9) TO CHILD SRTGBLK NM IS ASSIGNED . . . . . . . . . B
(10) DATABASE ERROR . . . . . . . . . . . . . . . . . . C
(10) INTERFACE ERROR WITH HANDLE-SRTGBLK-DATA FMM . . . B
(10) MESSAGE TOWARDS HANDLE-SRTGBLK-DATA FMM RANKED OUT B
(10) NO ACKNOWLEDGE OF HANDLE-SRTGBLK-DATA FMM . . . . B
(10) NO CHANGE . . . . . . . . . . . . . . . . . . . . B
(10) NO NM CONTROL ACTIVE . . . . . . . . . . . . . . . B
(10) NO RESULT RECEIVED FROM HANDLE-SRTGBLK-DATA FMM . B
(10) TAR WITH CALL GAPPING IS NOT ALLOWED . . . . . . . B

Action Description

Action Meaning
B Check input data:
  • if correct: given result data can be taken as information only.
  • if faulty : correct your input data and repeat MMC-command.
  • see also possible actions (parameter 6) about the next action

that should be performed.

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

In case of a database error, check the contents of the given relation (paramter 3), see database status (parameter 5) and see possible actions (parameter 6) about the next action that should be performed.