LP PARAMETER HAS BEEN INCREASED

Toda a vez que dois bancos de dados Adabas entrava no ar dava esta mensagem:

1                       J E S 2  J O B  L O G  --  S Y S T E M  C P A C  --  N O
0
00.54.32 STC02566 ---- FRIDAY,    13 MAY 2007 ----
00.54.32 STC02566  IEF695I START AAFAI072 WITH JOBNAME AAFAI110 IS ASSIGNED TO
00.54.32 STC02566  $HASP373 AAFAI072 STARTED
00.54.32 STC02566  IEF403I AAFAI110 - STARTED - TIME=00.54.32            
00.54.32 STC02566  ADAN02 001100 Nucleus run without protection log      
00.54.32 STC02566  ADAL01 00110 2007-05-13 00:54:32 CLOG not active      
00.54.32 STC02566  ADAN03 00110 ADABAS coming up
00.54.32 STC02566  ADAN84 00110 LP parameter has been increased
00.54.32 STC02566  ADAN84 00110 Additional protection area blocks
00.54.32 STC02566  ADAN84 00110 Are being formatted                        
00.54.32 STC02566  ADAN19 00110 Buffer flush is  a s y n c h r o n o u s
00.54.32 STC02566  ADAN01 00110 A D A B A S  V7.4.4  is active          
00.54.32 STC02566  ADAN01 00110 MODE = MULTI                            
00.54.32 STC02566  ADAN01 00110 Running without recovery log

Solução

O suporte (na época Consist) falou que algum utilitário estava passando este parâmetro em algum momento. Checando os backups desses dois bancos realmente tinha um parâmetro do backup que estava com o parâmetro LP/LWKP2 diferente;

MEMBER=PRGREPD  000003 REC SAVE:25.05.2007 13:52 BY   USERID AA99001  R=00000001
DSN=AAB.DIBD.ADAPARM                                    VOL=PRL303 UNIT=1024    
....+....1....+....2....+....3....+....4....+....5....+....6....
* MEMBER=PRGREPD                                                                
ADARUN PROG=ADAREP,DBID=230,MODE=SINGLE,PLOGRQ=NO                              
ADARUN LP=10000,LWKP2=1200,SVC=249,DEVICE=8391

Foi deixado o parâmetro do backup igual ao do banco;

Categories: Adabas