No guarantees, but when I have seen this it is because the Recovery log
needs to be extended.

Basically what you do is:

        use dsmfmt to create a new recovery log volume, 10-20 mb is
usually enough
        run dsmserv extend specifying the new log
        restart your server again

The instructions below are copied from the README file for the ADSM V2
AIX server:
Good luck!
===============================================================
Wanda Prather
Johns Hopkins Applied Physics Lab
301-953-6000 X8769
wanda_prather AT jhuapl DOT edu

"Intelligence has much less practical application than you'd think."
              - Scott Adams/Dilbert
===============================================================



*************************************************
STAND-ALONE EXTENSION OF THE SERVER RECOVERY LOG
*************************************************

When running the Version 2 server with the logmode set to Rollforward,
it is possible the server will run out of recovery log space before
database backup operations can complete successfully.  This is usually
a result of recovery logs that are too small or database backup triggers
set so that the database backup log full percentage is set too high.

In this situation it is possible that you may have to halt the server
without sufficient recovery log space available for successful server
re-start.

To provide for extending the recovery log in this situation, ADSM has
provided the EXTEND LOG parameter for the dsmserv program.  You can use
this parameter to extend the recovery log using an additional recovery
log volume so that the server can be started with sufficient recovery
log space to initialize and perform the needed database backup.

The syntax for the EXTEND LOG command is as follows:

    dsmserv extend log <volname> <mb>

Where:

    <volname> specifies the name of a new, formatted recovery log
              volume that should be used for the extension of the
              recovery log.

    <mb> - specifies the size in megabytes that the recovery log should
           be extended.  This specification should be a multiple of 4
           and should be at least 1 megabyte less than the size of
           the volume specified with the <volname> parameter.

The dsmfmt program can be used to allocate and format the recovery log
volume.

As an example, lets assume that the server exhausted all recovery log
space and that because of this, a database backup operation could not
succeed.  When trying to restart the server program, you found that
insufficient recovery log space was available for start-up.

Using the dsmfmt program, you allocate a 21MB recovery log
volume named adsm.new.reclog.

You can start the server an extend the recovery log to use this new
volume with the following parameter;

    dsmserv extend log adsm.new.reclog 20

After the log extension job completes, your server can be brought up
normally.  You should adjust the size of the recovery log and/or the log
full percentage on your database trigger so that a database backup can
complete successfully the next time that one is needed.


        ----------
        From:   Ulrike Scharf[SMTP:Ulrike_Scharf AT kasten DOT de]
        Sent:   Wednesday, December 10, 1997 1:24 PM
        To:     ADSM-L AT vm.marist DOT edu
        Subject:        ANR7837S Internal error LOGSEG871 detected.

        I have a very big problem, my ADSM-Server hangs on start!
        Can anyone please explain me the following error messages:


         Starting Server
        ANR7800I DSMSERV generated at 09:27:38 on Oct 31 1997.

        ADSTAR Distributed Storage Manager for AIX-RS/6000
        Version 2, Release 1, Level 5.15/5.15

        Licensed Materials - Property of IBM

        5765-564 (C) Copyright IBM Corporation 1990, 1995. All rights
reserved.
        U.S. Government Users Restricted Rights - Use, duplication or
disclosure
        restricted by GSA ADP Schedule Contract with IBM Corporation.

        ANR7838S Server operation terminated.
        ANR7837S Internal error LOGSEG871 detected.
          0x10034ABC *UNKNOWN*
          0x10032F40 *UNKNOWN*
          0x100338A8 *UNKNOWN*
          0x100046FC *UNKNOWN*
          0xD06FCE08 _pthread_body
        ANR7833S ADSM thread 1 terminated in response to program abort.
        ANR7833S ADSM thread 2 terminated in response to program abort.
        ANR7833S ADSM thread 3 terminated in response to program abort.
        ANR7833S ADSM thread 4 terminated in response to program abort.
        ANR7833S ADSM thread 5 terminated in response to program abort.
        ANR7833S ADSM thread 6 terminated in response to program abort.
        ANR7833S ADSM thread 7 terminated in response to program abort.
        ANR7833S ADSM thread 8 terminated in response to program abort.
        ANR7833S ADSM thread 9 terminated in response to program abort.
        /usr/lpp/adsmserv/bin/rc.adsmserv[19]: 18884 IOT/Abort
trap(coredump)