Have you tried allocating and formatting a new recovery log volume (with
dsmfmt) and running the command "dsmserv extend log"?

Example:

dsmfmt -log /adsmstg/newlogvol.dsm 101
dsmserv extend log /newlogvol.dsm 100

Once you're back up & running, you'll need to investigate why the recovery log
got full (check the activity log, dsmserv.err, etc.) and from there, determine
whether you really need to keep the additional log space you just added, or
whether you can remove it.

Andy

Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com



ADSM-L AT VM.MARIST DOT EDU on 06/22/98 08:03:54 AM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: error ANR9999D adminit.c(763)


Couldn't find this in the archives:

I had something go (apparently horribly) wrong with ADSM over the weekend.
Partial core dump (ran out of space for the dump :-<), the whole 9 yards.
Not entirely obvious what the problem is, but probably involved the tape
library.

When I try to restart the server, I get

        ANR0900I Processing options file dsmserv.opt.
        ANR0990I ADSM server restart-recovery in progress.
        ANR0200I Recovery log assigned capacity is 48 megabytes.
        ANR0201I Database assigned capacity is 1000 megabytes.
        ANR0306I Recovery log volume mount in progress.
        ANR0353I Recovery log analysis pass in progress.
        ANR0354I Recovery log redo pass in progress.
        ANR0355I Recovery log undo pass in progress.
        ANR0352I Transaction recovery complete.
        ANR9999D adminit.c(763): Insufficient log space to update table
Administrative.Attribute-s.

What do I need to do now?  ADSM v3.1.1.2 on AIX 4.2.1.

Thanks.

Pat Wilson
paw AT dartmouth DOT edu