Addition of LIM and functions with mutual exchange data 1

[GioBs]

Hi, I want to add LIM to a BC9 CNI82 system of beyond 11 LIMs.
I have made some tests in laboratory, adding LIM to a system of 3 LIMs, same release BC9. I have followed the indications in the dynatext and have used the LIM disposition table "LIM>11".
I have not redistributed the common functions program units, i.e. no common functions program units are loaded in the added lim 4 (like if it were lim number 18).

This i the procedure that I've followed:
Created on the disc REL1 and REL2 (DUSYI) (3LIMs exchange)
Create on disc also INL (DUSII)
Connected LIM 4 to GS
Switched on LIM controlling that display card goes to 3120
Sent the lim disposition table to new lim (CNLDI and CNLDT)
Verified the OK of CNLDT (Display Card 51)
Loaded the units with program with LAPUT
first message: LOADING INFORMATIONS (display card 6x)
LOADING WAS SUCCESFULL
third message: WAIT FOR START INFORMATION (display card 99, 100, 105, 101)
fourth message: SPONTANEOUS PRINTOUT
START PHASE 1, 1,3 AND PHASE 1,5 READY
STARTED LIM: S FAILED LIM: S PARTLY FAILED LIM: S FAILED PU: S
1
2
3
4

Initialized connection with GJLII
Date and time with CATII
then GJLCP, GJLSP, SCICP
then SFLII (DispCard 103)

DUSYI

Configurated extensions on LIM4 (EXTEI)

DUSYI

It seems all OK, but a strange phrase was in ambush in dyna: "Is there a function with mutual exchange data in all the LIMs, where the data for the functions is not initiated in the added LIM, at an initial start?"
and then
"example of functions:
- Traffic Measurement Data
- Call Diversion data
- Traffic group matrix data
- System Data
- Night service data
- Message waiting data
- Application system parameter data "

In fact:
I've prepared the 3 LIMs exchange with Night Service (NSCOI) and NASCS:ANS=801;
Well: the code 801 doesn't work for LIM4 extensions.

Dyna says "remove and reinitiate data for the function..", but NASCR doesn't work: FAULTY INTERRUPT, and the system reloads.

Perhaps i have to reinitialize these data before configure extension (EXTEI) on LIM4 (?).

I've also noted that CIL doesn't work for LIM4 extension.
Call diversion (CDINI) works after a RFEXI (but is not required for dyna procedure!)

argh!!

which are exactly "functions with mutual exchange data"?
I've noted B1 of parameter TYPE in CNPIP: it seems that B1=1 is equal to "program unit of function with mutual exchange data".
Is It True?
Can I use LADCI in this situation (addition of lim)?

My last questions are:
which is the correct procedure for addition of lim, where no common functions are loaded in the added lim (is it corrected what I have made)?
Which are exactly the functions with mutual exchange data?
Which it is the way in order to manage the functions with mutual exchange data?

Sorry for my english and thanks to all!

GioBs

 

[dstrang1]

Once you've added the LIM and done a successful dump, you need to poke the LIM twice ( or power cycle it) for a reload. I believe you're also *supposed* to send RFEXI, but that command has never brought anything but catastrophe for me in large systems so I haven't used it for a *long* time.

Good luck,

Dave Strang

 

[GioBs]

Thanks for your indication, Dave.
I'll try this procedure tomorrow, in lab.

GioBs

 

[zirafa]

Hello,

Have you succeeded? Does reload help?
I noticed that the added lim does not have number analysis data . You have to remove extensions to reinitiate this data
Hopefully reload helps.

Thanks for responce

 

[GioBs]

Yes, the reload (power cycle) of added LIM helps (Thank You, Dave), but it does not resolve all the problems.

I'll try to explain:
before Dave's replay, my procedure was:
1)CNLDI
2)CNLDT
3)LAPUT
4)GJLII
5)CATII
6)SFLII
7)DUSYI
8)Configuration of dirs, ecc.

In this case, for example, selecting Night Service Code (ANS=801) from an added LIM (LIM4) extension, it remained dumb, like if 801 does not exist.

Now my procedure is:
1)CNLDI
2)CNLDT
3)LAPUT
4)GJLII
5) (no catii)
6)SFLII
7)DUSYI
8)Power cycle added lim
9)Configuration of dirs, ecc.


Now 801 exist, but Night Service does not work (congestion tone). I have to do NSCOE and then NSCOI. In this way it goes OK.
Now NASCR works OK, before there was a "FAULTY INTERRUPT".
Also CIL it's OK.

BUT

TCMAP (for curiosity, I had verified TCMAP already to step 7) now is all 0 (except cat 15, obviously).
Dirs of pre existing LIMS respect the "old" and invisible TCMAP; extensions of LIM4 work with TCMAP all 0 (connections not permitted).
I have to use TCMAS, and it goes OK.

Woah!
Must I try all the services and timers of the system?

Have I made a mistake?
No? ...in this case which are the parameters that I have to rewrite in the system?
Yes?...where is my error?

Thanks to all!!

GioBs

 

[zirafa]

Hello,

It seems that
LIM add on procedure - procedure "looking for advetures" or "never ending".

 

[mdman]

Wenn you add a LIM, you add the program and data parts of the program units in the INL format. This means that these units do not have any customer data in them after they are loaded to the new lim.
In order to add this data you must send a number of commands again so that the data is programmed in all the lim's.
Normally I send these commands after I added a LIM. (Use PCregen to regenerate the commands).
I usually delete some data first when possible (NUTRE,CDCOE, RODNE, LCDDE, NSCOE, delete all call logging and delete all Traffic recording)

SYDAS
SYTDS
ASPAC
NUTRI
CDCOI
ICMWC
RODNI
LCDDI
LCTDI
TCMAS
NSCOI
All call logging
All Traffic Recording

 

[GioBs]

Thank You, mdman.
I'll add these infos to my procedure.
Do You reload added LIM as indicated from dstrang1?

Any other indication from anyone will be appreciated.

 

[mdman]

Reload is not necessary, RFEXI also not.

I usually do a SFCEI afterwards but that is only since sometimes the new LIM doesn't show all magazines.

It is good practice to power off and on the newly added LIM to see if it reloads correctly.

 

[mundus]

Hi,
use LADCI:LIM=1,LIMR=new lim,UNIT=x; where x is:
LADCI:UNIT=NAP,LIMS=1,LIMR= ; number analyse
LADCI:UNIT=ACP,LIMS=1,LIMR= ; Abbreviated dialling
LADCI:UNIT=EAP1,LIMS=1,LIMR= ; route dest
LADCI:UNIT=NUD,LIMS=1,LIMR= ; number conversion
LADCI:UNIT=CLOP,LIMS=1,LIMR= ; call logging
LADCI:UNIT=PNR,LIMS=1,LIMR= ; PNR
LADCI:UNIT=LRP1,LIMS=1,LIMR= ; LCR
LADCI:UNIT=LRP1,LIMS=1,LIMR= ; LCR
LADCI:UNIT=LRP2,LIMS=1,LIMR= ; LCR
LADCI:UNIT=LRP3,LIMS=1,LIMR= ; LCR
LADCI:UNIT=LRP4,LIMS=1,LIMR= ; LCR
LADCI:UNIT=LRP6,LIMS=1,LIMR= ; LCR
LADCI:UNIT=LRP7,LIMS=1,LIMR= ; LCR
LADCI:UNIT=NDBP,LIMS=1,LIMR= ; name Identity
LADCI:UNIT=DED,LIMS=1,LIMR= ; common directory
LADCI:UNIT=ELDP,LIMS=1,LIMR= ; text
and ( grenerated by PCREG ):
ASPAC, ACPAC, SYTDS, SYDAS, TCMAS, CDCOE - CDCOI, NSCOE -
NSCOI, GESPC ( Change GESPI to GESPC ), ACFUE - ACFUI &
ICMWC.
and if you have call logging activated:
CLTGE, CLGME, CLGMI & CLTGI.
If you use LCR then:
LCLDI:LIM= new lim, DEST= ,AC= ;

 

[GioBs]

Thank You mdman
Thank You mundus

it seems like in the film “Apollo 13”, when Ken Mattingly (interpreted by Gary Sinise) must find the correct procedure in order to permit coming back of shuttle on the earth

The program units of which LADCI copies the dbase are not directly involved from the commands you make after.
And this is a NEW in my procedure.
I had identified these program units thanks to the TYPE bit B1 of the CNPIP.
But LADCI is indeed necessary?
I think to have obtained an analogous result using recharges of the added LIM.
What do you think about this?

Thanks to all comments

 

[whosrdaddy]

if you follow mdman's lead, all is ok. I still prefer to make a new system though (costs me less time and headache afterward)

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!

 

[GioBs]

ThankYou Daddy, I am happy for having received one answer from you.
I am agree with you, but I do not have enough mags and cards in order to make this in laboratory, and therefore I must make the work in this way.

Thanks to all
(but the thread is not closed )