Re: ADSM for AS/400 - not starting

Greetings,

  If a machine goes down hard (we have also had this experience) it will
attempt to process the recovery log upon startup.  This may take some time.
 I am going to hazard a guess that ADSM is detecting a corrupted recovery
log.  You may have to reformat those files.  I would ask IBM if this is the
case before taking those steps.

Good Luck,
  Dan T.

----------
> From: AS Department <as400 AT HETNET.MSK DOT RU>
> From: AS Department <as400 AT HETNET.MSK DOT RU>
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: ADSM for AS/400 - not starting
> Date: Tuesday, October 14, 1997 8:03 AM
>
> Dear Coleague,
>
> I have a problem with ADSM on AS/400.
> After a feed at AS/400 was unexpectedly switched off.
> Now ADSM is not started.
>
> This is log:
>
> ANR0900I Procesing options file QOPTADSM(OPTIONS).
> ADSTAR Distributed Storage Manager for AS400
> Version 2, Release 1, Level 0.1/2.2
> Licensed Materials - Property of IBM
> 5716SV2 (C) Copyright IBM Corporation 1990, 1996. Al rights reserved.
> U.S. Government Users Restricted Rights - Use, duplication or disclosure
> restricted by GSA ADP Schedule Contract with IBM Corporation.
> ANR7800I QANRSERV generated at 15:23:5 on 05/2/96.
> ANR0990I ADSM server restart-recovery in progres.
> ANR0200I Recovery log asigned capacity is 24 megabytes.
> ANR0201I Database asigned capacity is 24 megabytes.
> ANR0306I Recovery log volume mount in progres.
> ANR0353I Recovery log analysis pas in progres.
> ANR0354I Recovery log redo pas in progres.
> ANR0355I Recovery log undo pas in progres.
> ANR9999D DSMSERV2/QCSRC/PKTHREAD(78): Run-time asertion failed:
> "CmpLsn( *pageLsnP, hdrP->updtLsn ) = GREATERTHAN", Thread 0, File
> DSMSERV2/QCSRC/DBLOG, Line 916.
>
> Thank,
> Alexander Klimanov,
> HETNET Consulting.