RRN 08344 ROUTING ADMINISTRATION

AJKY8FAA

Message Triggering Condition

Response to operator request in the case of successful or unsuccessful execution of the following commands:
CRN 3219 CREATE-BSCRTCD
CRN 8390 DISPLAY-BSCHGRP
CRN 8393 MODIFY-BSCHGRP
CRN 3218 MODIFY-BSCRTCD
CRN 5819 EXTEND-BSCHGRP
CRN 5820 REDUCE-BSCHGRP
CRN 5821 SEIZE-BSCHGRP
CRN 5822 RELEASE-BSCHGRP
CRN 3220 EXTEND-BSCRTCD
CRN 3221 REDUCE-BSCRTCD
CRN 3222 REMOVE-BSCRTCD

Report Layout

 SWA-ORJ-ROUTING LAYERS
    (A).......................                   (B).................
                                 (C)........................... (D) (E)
    -----------------------------------------------------------------
        (1).................... (2).......................
        BSCRTCD/TCP/DESCR : (3)............. / (4).. / (5).............
        FMM NAME   : (6).................   FMM VAR    : (7).....
        FMM ID     : (8)..                  GSM        : (9).....
        OWN LCE ID : (10)..                 OWN PCE    : (11)..
        ERROR      : (12).......................
        ERRORPOINT : (13)                    PGM DAT    : (14)
        ERROR IN BSTCE TREATMENT:           BSTCE INDEX:(15)..
        LCE-ID:(16)..                       PCE:        (17)..
        LAN:(18)..
        ASSIST TRUNK COMMAND HANDLER DATA:
        RESULT:(19)...............
        CONSISTENCY ERROR:
        (20)........................................ AT (21)..
  REPORT REFERENCE NUMBER = 8344

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) task description
(2) state
(3) BSC-channelgroup identity
(4) BSC-routecode identity
(5) BSC-channelgroup description additional comment
(6) fmm name
(7) fmm variant and pcs
(8) fmm id fmm identity
(9) gsm variant and pcs generic software module
(10) own LCE id logical control element identity
(11) own PCE networkadress of command handler
(12) error description
(13) errorpoint for error analysation by designer
(14) programmer data extra counter for loops
(15) BSTCE index internal information
(16) LCE id logical control element id
(17) PCE networkadress of BSTCE
(18) LAN Logical Access Number
(19) assist trunk command handler result from BSTCE
ACKNOWLEDGE
DB ERROR R_H7DST_N7
DB ERROR R_LI7N_CNF GLS_ERROR
request accepted support information only support information only
generic load segment wrong
INIT ERR support information only
INVALID ORDER LI_N7_CNF NFTUPLE support information only
support information only
NO LCG RESP no response from local charging
generator
ORD ERROR TTCE support information only
ORDER ERROR support information only
RELEASE IMPED OPERATION unsucessful execution
RELEASED channel released after operation
SEIZED channel seized for operation
SPEC COMB ERROR TR7N_SIG NFTUPLE support information only
support information only
WTC wait traffic clear
(20) consistency error
(21) error occurence networkadress or LCE

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(12) COMMAND HANDLER BUSY, TRY LATER . . . . . . . . . J
(12) END OF DATA UPDATE TRANSACTION NOT SUCCESSFUL . . J
(12) ERROR IN ASSIST TRUNK COMMAND HANDLER . . . . . .
(19) NO DH RESPONSE . . . . . . . . . . . . . . . . . . K
(12) NO BSTCE ADDED TO BASE STATION CHANNEL GROUP . . . L
(12) NO BSTCE REMAINING UNDER TREATMENT . . . . . . . . L
(12) NO CHANNEL IN READY STATE FOUND . . . . . . . . . D
(12) NO CHANNELS ADDED TO BSCHGP IN BSTCE . . . . . . . L
(12) NO CHANNELS OF BSCHGRP IN READY STATE FOUND . . . D
(12) NO CHANNELS OF THE BSCHGP FOUND . . . . . . . . . A
(12) NO FREE CHANNELS FOUND . . . . . . . . . . . . . . A
(12) NO FREE CHANNELS IN READY STATE FOUND . . . . . . D
(12) NO OTHER BSTCE IN BSCHGRP . . . . . . . . . . . . M
(12) NOT ALL CHANNELS COULD BE REMOVED OR SOME CHANNELS NOT RDY L
(12) REFUSING AT LTRA INITIALISATION . . . . . . . . . J
(12) START OF DATA UPDATE TRANSACTION NOT SUCCESSFUL . J
(12) THE ATCH DOESNOT SEND RESPONSE . . . . . . . . . . K
(12) THE CALL ATTEMPTS PER SECOND ARE OUT OF RANGE . . I
(12) TIMEOUT DURING INITIALISATION OF LTRA . . . . . . J
(12) TIMEOUT WAITING FOR CONFIRM OR CANCEL . . . . . . N
(12) TIMER_EXPIRED DURING (DE)REGISTRATION WITH N7 . . A
(12) TO MANY FAILURES IN INITIALISATION OF LTRA . . . . J
(12) TOO MANY BSTCES IN BSCHGP . . . . . . . . . . . . H
(12) TOO MANY BSTCES IN TRA . . . . . . . . . . . . . . O
(19) CLOSE DUT ERROR . . . . . . . . . . . . . . . . . J
(19) NO GLS FOUND . . . . . . . . . . . . . . . . . . . A
(19) NO TRUNKS TO HANDLE . . . . . . . . . . . . . . . A
(19) OPEN DUT ERROR . . . . . . . . . . . . . . . . . . J
(20) (DE)REGISTRATION FOR SPC/LN WITH N7 NOT SUCC . . . A
(20) BSCHGP WITH THIS DESTINATION POINT CODE ALREADY EXISTS A
(20) BSTCE IS ALLOCATED TO A BASESTATION CHANNEL GROUP A
(20) BSTCE IS NOT ALLOCATED TO A BASESTATION CHANNEL GROUP A
(20) DESTINATION POINT CODE NOT EXISTING . . . . . . . A
(20) DTTCE IS NO BSTCE . . . . . . . . . . . . . . . . A
(20) LN NOT IN USE IN THIS EXCHANGE . . . . . . . . . . A
(20) MISMATCH BETWEEN DPC OF BSCHGP AND BSTCE . . . . . A
(20) MTP ROUTING FOR N7 NOT DEFINED . . . . . . . . . . A
(20) MTP ROUTING FOR SPC/LN NOT DEFINED . . . . . . . . A
(20) NA DOES NOT EXIST . . . . . . . . . . . . . . . . A
(20) NEWBSRID EXISTS ALREADY . . . . . . . . . . . . . A
(20) NO N7 ROUTING EXISTS . . . . . . . . . . . . . . . A
(20) NO PCM ID WAS SPECIFIED FOR THE FIRST EXTEND OF A BSTCE G
(20) NOT ALL CHANNELS OF BSCHGRP ARE IN READY STATE . . P
(20) NUMBER OF RESERVED CHANNELS SMALLER THAN EQUIPPED CHANNELS G
(20) N7 DEST IS OWN EXCHANGE . . . . . . . . . . . . . A
(20) N7 DEST OUTSIDE RANGE . . . . . . . . . . . . . . A
(20) OBSERVATION ACTIVE ON BASESTATION CHANNELGROUP . . D
(20) PCM-ID USED FOR OTHER BSTCE IN BSCHGRP . . . . . . G
(20) SEIZE/RELEASE THE CCS-LINK WITH ENLIST AND CHANNEL GIVEN Q
(20) SPACE TO SMALL FOR EXTEND - USE MODIFY-BSCHGRP . . D
(20) SPLITTED N7PC INVALID . . . . . . . . . . . . . . A
(20) STILL CELLS LINKED TO BASESTATION CHANNEL GROUP . B
(20) TCE SEQUENCENUMBER USED FOR OTHER BSTCE IN BSCHGRP G
(20) THE LAST BASESTATION CHANNEL GROUP MAY NOT BE REMOVED C
(20) THE NEW BSRID ALREADY EXISTS . . . . . . . . . . . A
(20) THE REFBSGID DOES NOT EXIST . . . . . . . . . . . A
(20) THE SPECIFIED BSCHGRP ALREADY EXISTS . . . . . . . A
(20) THE SPECIFIED BSCHGRP DOES NOT EXIST . . . . . . . A
(20) TIMER_EXPIRED DURING (DE)REGISTRATION WITH N7 . . A
(20) TRA IS OUT OF SERVICE . . . . . . . . . . . . . . A
(20) TRA TO SMALL FOR EXTENTION OF CAPS . . . . . . . . E
(20) TRUNK RESOURCE ALLOCATOR IS UNKNOWN . . . . . . . A

Action Description

Action Meaning
A Correct the input values of the concerning parameters and start the command again. To SEIZE/RELEASE a CCS-LINK specify ENLIST1 with NA and CHANNEL (TN), a range is not allowed.
B Remove all cells and the start command again
C If the last BSC-channelgroup has to be removed then first create a dummy with CREATE-BSCHGRP and then remove the previous one
D Correct the data with other commands and then start command again
E Check whether the reserved space in the TRA for the other trunkgroups and BSC-channelgroups can be reduced. if possible do this, if not then a TRA with enough space has to be found using the DISPLAY-BSCHGRP command with LTRA=H'ffff. if neither a TRA with enough space left nor one that has unused space for other trunkgroups or BSC-channelgroups then the exchange needs a hardware extention with RSACEs. if there is an other TRA that could handle the number of trunks and caps the BSC-channelgroup has to be shifted to this TRA. the search for a TRA that can handle the needed caps/trunk can be automated by omitting the parameter LTRA at the create command.
G Modify the number of reserved channels in the TRA with the command MODIFY-BSCHGRP: SPACE= new_number_of_channels ; then start the command again
H A BSC-channelgroup can contain 16 BSTCES as a maximum
I correct the input of parameter LOAD (traffic or holdtime) and start the command again
J Only one data modifying command may be executed in the exchange in time so wait a few minutes and then start the command again
K The remote access to the BSTCE failed so check the SBL-status of the mentioned control element
L This error is only the information that the previously reported problems left nothing to do for the orj so correct the warning that have been reported in former reports and start the command again
M Use the command REMOVE-BSCRTCD i.s.o. REDUCE-BSCHGRP
N Start the command REMOVE-BSCRTCD again and confirm it when you are asked
O Check whether BSTCES from other BSC-channelgroups or dttces of other trunkgroups in this TRA can be reduced. if yes reduce them an do your extention afterwards, if no then the BSC-channelgroup has to be shifted to an other TRA by removing and re - creating it.
P Seize all channels for operation using the command: SZE-BSCHGRP and resubmit the MODIFY-BSCHGRP:LTRA=.. afterwards.
Q To SEIZE/RELEASE a CCS-LINK specify ENLIST1 with NA and CHANNEL (TN), a range is not allowed.