How can I erase generic extensions when the LIM where the data are stored is already ended.It was erased with out knowing that some generic extensions data are stored in this lim.Can anyone pls help me how to clear this problem. I can't erase & prints data for those generic extensions the system always response is command lost.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
How can I erase generic extensions 2
- Thread starter rokane
- Start date
rezal, summerdike:
Rokane wants to save the system as it is. SFEXI is only possible after first initial load, making a new system with INL, maybe not very clever in this case. If your opinion is
to just give advices, which are counted to zero, don't bother, it's only a waste of space. If he wants to try this, OK. The RO case can also be solved, but first the DE case, and there are some other things also, so let's begin with this one, OK?
Rokane wants to save the system as it is. SFEXI is only possible after first initial load, making a new system with INL, maybe not very clever in this case. If your opinion is
to just give advices, which are counted to zero, don't bother, it's only a waste of space. If he wants to try this, OK. The RO case can also be solved, but first the DE case, and there are some other things also, so let's begin with this one, OK?
fcpli:
It is NOT a good advice to leave the system like this.
I would certainly not do that to any of my customers. This kind of stuff will give You headaches for a long time.
The only sensible thing is to rescue as much data as
possible and then rebuild it. After this I will not waste
more space on this issue...
/rezal
It is NOT a good advice to leave the system like this.
I would certainly not do that to any of my customers. This kind of stuff will give You headaches for a long time.
The only sensible thing is to rescue as much data as
possible and then rebuild it. After this I will not waste
more space on this issue...
/rezal
- Thread starter
- #23
rokane!
Actually you can use the same SGSAI for the EL and KL, but
to be accurate, change byte 3 to 99 for EL and to c2 for KL (3-99 or 3-C2). After the extensions are OK, there remains RO (at least). A good idea is to use pcregen to print all data out, and check where you got "command lost".
Good luck
Actually you can use the same SGSAI for the EL and KL, but
to be accurate, change byte 3 to 99 for EL and to c2 for KL (3-99 or 3-C2). After the extensions are OK, there remains RO (at least). A good idea is to use pcregen to print all data out, and check where you got "command lost".
Good luck
- Thread starter
- #25
-
1
- #26
To erase the routes is a little bit tricky. What we need to know, is the reference pointer of the rou which is/was in the removed LIM. How to find it/them:
1) With CNPIP:UNIT=DTM;
check where the active unit resides.
2) Then SACOP:UNIT=DTM,LIM=x,RELOFF=9,FILNO=1,POINT=0&&9c3;
Where x is for the active DTM LIM. The printout is HUGE (2500 records), but don't care! Now, in the data, is the LIM number (in your case 12 -> 0C). Write down all the
pointers, which point to LIM 12.
3) Now, to be sure that you are on the right track, sacop those pointers mentioned above with
SACOP:UNIT=DTM,LIM=x,RELOFF=6&7,FILNO=1,POINT=xyzw;
This sacop results in route number (HEX). If you have the information of them somewhere, it is good to check that they are correct.
If OK, just a SGSAI remains. But first insert the sacops here (not the long one, just those pointers you need to "kill").
Have a "nice" weekend!
1) With CNPIP:UNIT=DTM;
check where the active unit resides.
2) Then SACOP:UNIT=DTM,LIM=x,RELOFF=9,FILNO=1,POINT=0&&9c3;
Where x is for the active DTM LIM. The printout is HUGE (2500 records), but don't care! Now, in the data, is the LIM number (in your case 12 -> 0C). Write down all the
pointers, which point to LIM 12.
3) Now, to be sure that you are on the right track, sacop those pointers mentioned above with
SACOP:UNIT=DTM,LIM=x,RELOFF=6&7,FILNO=1,POINT=xyzw;
This sacop results in route number (HEX). If you have the information of them somewhere, it is good to check that they are correct.
If OK, just a SGSAI remains. But first insert the sacops here (not the long one, just those pointers you need to "kill").
Have a "nice" weekend!
singhbrindisi
Technical User
I agree with Jazaya....
FCPLI is a busy magician moving all around the globe....
BR,
""The truth about action must be known and the truth of inaction also must be known; even so the truth about prohibited action must be known. For mysterious are the ways of action""
FCPLI is a busy magician moving all around the globe....
BR,
""The truth about action must be known and the truth of inaction also must be known; even so the truth about prohibited action must be known. For mysterious are the ways of action""
- Thread starter
- #29
rokane:
OK, you are almost lucky now!
So, what abot the RO part?
Also, in order to get the data completely OK (as some people were concerned about), just check with PCREGEN that you don't receive any "COMMAND LOST" messages. Also check from HIMDP that the history does not show any faults (unusual ones)
or lost LIMs. If all this seems to be OK, you are saved!
ps. There might also be GH or CH parts wrong here, check!
OK, you are almost lucky now!
So, what abot the RO part?
Also, in order to get the data completely OK (as some people were concerned about), just check with PCREGEN that you don't receive any "COMMAND LOST" messages. Also check from HIMDP that the history does not show any faults (unusual ones)
or lost LIMs. If all this seems to be OK, you are saved!
ps. There might also be GH or CH parts wrong here, check!
- Status
Similar threads