BC9 Lim removal 4

[cv8devil]

I had 2 remote LIMs from a 23 LIM system that were no longer required and had to be removed from the building. All extensions were removed from the LIMs, I CNBOE all the boards except for LPU,LSU,DSU,GJUL4. I followed ALEX and brought the 2 LIMs back to mag 0 only, then early one morning I followed ALEX and removed the LIMs. There were no common program units and everything went well with CNLIE and SFCEI. No alarms, dumps all work..
BUT, now in HIMDP I am getting H'34 errors from various LIMs referecing the 2 removed LIMS (19 and 20)

DIAGNOSTICS FROM LIM 001

TIME DATE ERROR CODE
03:18:50 28NOV06 H'34
RECEIVING LIM ADDRESS NOT AVAILABLE
LOGICAL PROGRAM ERROR ADDRESS = 02008D7C
ENTER
SWSW B-LEVEL SIGNAL TCSINFFETE (H'001F)
FROM DERS1 (H'184) EXE A IN LIM 003
TO RHH (H'25D) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL = 39
WITH 0 1 2 3 4 5 6 7 8 9
000 02 4C 03 BD 12 12 0F 0A A0 22
010 A1 0F 06 2D 03 00 01 00 01 02
020 75 01 CC 00 00 00 00 01 00 00
030 00 00 00 00 FF FF FF FF 00

SEND
SWSW B-LEVEL SIGNAL FETTCSNUME (H'0024)
FROM RHH (H'25D) EXE A IN LIM 001
TO DERS1 (H'184) EXE A IN LIM 020
NUMBER OF DATA BYTES IN SIGNAL = 10
WITH 0 1 2 3 4 5 6 7 8 9
000 02 4C 02 5D 01 02 01 02 02 0F

and

TIME DATE ERROR CODE
15:19:44 27NOV06 H'34
RECEIVING LIM ADDRESS NOT AVAILABLE
LOGICAL PROGRAM ERROR ADDRESS = 020011BA
ENTER
SWSW A-LEVEL SIGNAL RELQUERCD (H'0021)
FROM CMPS12 (H'2DD) EXE A IN LIM 016
TO GPP (H'168) EXE A IN LIM 010
NUMBER OF DATA BYTES IN SIGNAL = 7
WITH 0 1 2 3 4 5 6 7 8 9
000 01 C4 00 01 85 0A FF

SEND
SWSW A-LEVEL SIGNAL RELQUERCD (H'0021)
FROM GPP (H'168) EXE A IN LIM 010
TO GPP (H'168) EXE A IN LIM 019
NUMBER OF DATA BYTES IN SIGNAL = 7
WITH 0 1 2 3 4 5 6 7 8 9
000 01 C4 00 01 85 0A 0A

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 00 04 0C


there are others as well, but they all reference the 2 removed LIMs. Within the next 2 weeks I will be upgrading the group switch to GJUG5 cards (got the GSm ready to go) and soon after that we will be upgrading to BC13.
These H'34 erors though, have me concerned.
Any suggestions?

 

[fcpli]

OK. To get further, hirei; and key ksexe again. Print out himdp;
In which LIM is 3565?

 

[cv8devil]

<KSDDPIR=3565;
KEY SYSTEM DIRECTORY DATA
DIR CUST EQU CAT ADN ODN CALALT
3565 010-0-11-00 25 1

END

<HIREI;
WAIT
EXECUTED
<KSEXEIR=3565;
KSEXEIR=3565;
SURE? (YES/NO)
<Y;
WAIT
WAIT
FAULT INTERRUPT

MESSAGE FROM OPERATING SYSTEM:
RELOAD REQUESTED
RELOAD REQUESTED
SYSTEM INITIATED DATA
<HIMDP;

DIAGNOSTICS FROM OPERATING SYSTEM
TIME DATE
20:51:26 12DEC06
DIAGNOSTICS FROM LIM 001

TIME DATE ERROR CODE
20:50:19 12DEC06 H'34
RECEIVING LIM ADDRESS NOT AVAILABLE
LOGICAL PROGRAM ERROR ADDRESS = 02008BC8
ENTER
SWSW B-LEVEL SIGNAL GPMEMDATAFET (H'0027)
FROM GPP (H'168) EXE A IN LIM 010
TO KHHS2 (H'1D2) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL = 4
WITH 0 1 2 3 4 5 6 7 8 9
000 00 8D 0A 13

SEND
SWSW B-LEVEL SIGNAL FETGPGRPDATA (H'0045)
FROM KHHS2 (H'1D2) EXE A IN LIM 001
TO GPP (H'168) EXE A IN LIM 019
NUMBER OF DATA BYTES IN SIGNAL = 7
WITH 0 1 2 3 4 5 6 7 8 9
000 0A 00 00 8D 01 D2 01

NO INFORMATION STORED IN LIM 002
NO INFORMATION STORED IN LIM 003
NO INFORMATION STORED IN LIM 004
NO INFORMATION STORED IN LIM 005
NO INFORMATION STORED IN LIM 006
NO INFORMATION STORED IN LIM 007
NO INFORMATION STORED IN LIM 008
NO INFORMATION STORED IN LIM 009
NO INFORMATION STORED IN LIM 010
NO INFORMATION STORED IN LIM 011
NO INFORMATION STORED IN LIM 012
NO INFORMATION STORED IN LIM 013
NO INFORMATION STORED IN LIM 014
NO INFORMATION STORED IN LIM 015
NO INFORMATION STORED IN LIM 016
NO INFORMATION STORED IN LIM 017
NO INFORMATION STORED IN LIM 018
NO INFORMATION STORED IN LIM 021
NO INFORMATION STORED IN LIM 022
NO INFORMATION STORED IN LIM 023

END

 

[fcpli]

Try to sacop:unit=khhs2,lim=1,sector=rel,addr=1b7&237;
Check adresses 23A and 23B,they should be 00, if not, sacos them in all KHHS's. BTW, SUH seems to be OK.

 

[cv8devil]

ok..
<SACOP:UNIT=KHHS2,LIM=1,SECTOR=REL,ADDR=1B7&237;
MEMORY CONTENT ON ADDRESS POSITION
EXE A

ADDRESS 0 1 2 3 4 5 6 7 8 9 A B C D E F ISO
000001B0 BE 01 C5 FF FF 00 17 00 01 01 01 01 01 01 01 01 ................
00000230 00 00 00 00 00 00 00 02 4D 03 12 04 04 01 17 00 ........M.......
END
then
<SACOS:UNIT=KHHS2,LIM=1,SECTOR=REL,ADDR=23A,DATA=00;
SACOS:UNIT=KHHS2,LIM=1,SECTOR=REL,ADDR=23A,DATA=00;
SURE? (YES/NO)
< Y;
WAIT
EXECUTED
<SACOS:UNIT=KHHS2,LIM=1,SECTOR=REL,ADDR=23B,DATA=00;
SACOS:UNIT=KHHS2,LIM=1,SECTOR=REL,ADDR=23B,DATA=00;
SURE? (YES/NO)
<Y;
WAIT
EXECUTED

after
<SACOP:UNIT=KHHS2,LIM=1,SECTOR=REL,ADDR=1B7&237;
MEMORY CONTENT ON ADDRESS POSITION
EXE A

ADDRESS 0 1 2 3 4 5 6 7 8 9 A B C D E F ISO
000001B0 BE 01 C5 FF FF 00 17 00 01 01 01 01 01 01 01 01 ................
00000230 00 00 00 00 00 00 00 02 4D 03 00 00 04 01 17 00 ........M.......
END

I did sacos on khhs1,2,3,4 and when I did a <SUDIPIR=3565;
DIRECTORY INFORMATION AT 22:03:52 12DEC06
..snip..
GROUP DATA
COMMAND LOST

SO something still missing??

 

[fcpli]

Sorry, a mistake! The address should be 1CA&1CB, not those mentioned. Sacos back the original values to 23A&23B with sacos:unit=khhs2,lim=1,sector=rel,addr=23A,data=12&04;
And then sacop:sacos:unit=khhs2,lim=1,sector=rel,addr=1C0;
and here sacos:unit=khhs2,lim=1,sector=rel,addr=1CA,data=00&00; if not already set.
Too much thinking at the same time.....

fcpli

 

[cv8devil]

Ok, I put 23A back to original and SACOP as below. 1CA and 1CB are already 00 in KHHS1,2,3,4. I appreciate the thinking going on.

<SACOP:UNIT=KHHS2,LIM=1,SECTOR=REL,ADDR=1C0;
MEMORY CONTENT ON ADDRESS POSITION
EXE A

ADDRESS 0 1 2 3 4 5 6 7 8 9 A B C D E F ISO
000001C0 01 01 01 01 01 01 01 01 01 01 00 00 01 01 01 00 ................
END

 

[fcpli]

Okay, let's try something else: First of all, start a trace
stisr;
stuni:unit=khhs2,lim=1;
sttss:tri=1,size=500;
sttsi:tri=1;
ksexe:dir=3565;
y;
wait until the command stops (reload req)
sttse:tri=1;
stsap:signo=27,tri=1;
assume the result shows this signal on line 323, start printing, say from line 315
strap:tri=1,line=315&&500;
search for following signal:
16.21.32.620 00189 SWSW SIGNAL

16.21.32.620 00189 SWSW SIGNAL DELINEPNTFET (H'0044)
FROM DERS1 (H'0184) EXE IN LIM 002
TO KHHS2 (H'01D2) EXE A IN LIM 001
WITH 0 1 2 3 4 5 6 7 8 9
000 H'00 H'37 H'02 H'44 H'02 H'44 H'FF H'FF H'00 H'00
010 H'25 H'01 H'D2 H'01 H'00 H'00 H'00

Look at D4&D5 in the signal (in this example H'02 H'44).
This is the pointer (0244), which points to GPP.
Now, sacop GPP in the home LIM of the extension (ders1 is sending from that LIM, in the example LIM2):
sacop:unit=gpp,lim=2,reloff=0&1,filno=1,point=244;


<sacop:unit=gpp,lim=2,reloff=0&1,filno=1,point=244;
MEMORY CONTENT ON INDIVIDUAL POSITION
EXE A
FILE NUMBER RELOAD FILE START DS FILE START
1 0000009E
POINT RELOFF DSOFF ADDRESS DATA ISO
0244 0000 000009AE 00 .
0244 0001 000009AF 09 .
END

here we can see that in my example the group lim is 9, and the extension itself resides in LIM2.

<gpdap:grp=99;
GROUP CALL PICKUP DATA
GRP LIM DIR AGRP MGRP
99 9 2133

END

Now try to sacos the LIM away:

sacos:unit=gpp,lim=2,reloff=0,filno=1,point=244,data=ff&ff;

Then SUDIP. Your LIM is H'13

If this works, there is a simpler way to remove all GPP data concerning LIM19&20,but this is a longer example just trying to figure out (both of us), how it works.

Good luck

 

[cv8devil]

Success. SUDIPIR=3565; now works.

<STSAP:SIGNO=27,TRI=1;

TRACE IND SEARCH RESULT
TRACE INDIVIDUAL NO 1
20.02.21.480 00107 SWSW SIGNAL GPMEMDATAFET (H'0027)
FROM GPP (H'0168) EXE IN LIM 010
TO KHHS2 (H'01D2) EXE A IN LIM 001
WITH 0 1 2 3 4 5 6 7 8 9
000 H'00 H'B7 H'0A H'13 H'02 H'00 H'01 H'C5 H'0A H'00
010 H'25 H'01
SIGNAL FOUND IN:
LINE(S): 00107
END

then found this

20.02.21.400 00105 SWSW SIGNAL DELINEPNTFET (H'0044)
FROM DERS1 (H'0184) EXE IN LIM 010
TO KHHS2 (H'01D2) EXE A IN LIM 001
WITH 0 1 2 3 4 5 6 7 8 9
000 H'00 H'B7 H'01 H'C4 H'01 H'C4 H'FF H'FF H'00 H'00
010 H'28 H'D4 H'00 H'00 H'00 H'00

<SACOP:UNIT=GPP,LIM=10,RELOFF=0&1,FILNO=1,POINT=1C4;
MEMORY CONTENT ON INDIVIDUAL POSITION
EXE A
FILE NUMBER RELOAD FILE START DS FILE START
1 0000009E
POINT RELOFF DSOFF ADDRESS DATA ISO
01C4 0000 000007AE 0A .
01C4 0001 000007AF 13 .
END

<SACOS:UNIT=GPP,LIM=10,RELOFF=0,FILNO=1,POINT=1C4,DATA=FF&FF;

You said there is a simpler way to get the rest of the data, as causing a heap of reloads wont make the customer happy. lol
I'm fortunate in that I'm able to dial in and do all this after hours so no one notices any issues.

 

[fcpli]

The reload is only a data reload, and if your dump is up-to-date, it shouldn't bother anybody. Now I suppose you have also tried ksexe, ksddp etc. on this dir. If everything seems to be OK, you can clean rest of the GPP's.
sacop all lims one by one:

SACOP:UNIT=GPP,LIM=x,RELOFF=1,FILNO=1,POINT=0&&27F;

Locate in the data value 13 or 14 (LIM19&20). If found, remember the pointer and clean the data as you did in the example:

SACOS:UNIT=GPP,LIM=x,RELOFF=0,FILNO=1,POINT=yyy,DATA=FF&FF;

Then test again and again. If OK, make a dump.

Note that the printouts are 640 lines long, and in the beginning there are only FF's (setting of the pointers begins from the end). You can shorten the printout if you know approx. how many members you have in each LIM.
This does not cause any reloads!
Then hirei; and after some time himdp;

Good luck

 

[cv8devil]

It's looking good so far.removed around 26 entries so far which match the numbers per lim that were in the pickup group. I'll give a final update tomorrow after I put them in a new pickup group, and in a couple of days of watching himdp.

I appreciate the time you have put in, and have learned some valuable lessons, as well as what you have showed me in this thread.

 

[cv8devil]

fcpli, thanks for your assistance with this. No further H'34 errors in HIMDP. It is fixed.

 

[fcpli]

OK, hope you have learned something about LIM removal.
Note that there might be some other errors not seen yet, in the future. But they can be fixed one by one, the major task is (was) to get the printouts working properly.
Have a nice day!

fcpli

 

[whosrdaddy]

antoher star for you for excellent support fcpli!

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