I have done a large amount of ADSM testing having the same "null database"
requirement.  Since the tests required complicated ADSM configurations that
I didn't want to recreate every time I reran the test, I did the following
on my Solaris 2.6 system:

1) Followed your procedure to create a null database.
2) Manually registered the admin from the server_console.
3) Logged on with the admin client.
4) Executed a MACRO containing all the ADSM configuration commands.
5) Halted the ADSM Server.
6) Copied the db.dsm to db.null.dsm
7) Copied the log.dsm to log.null.dsm

Then, before executing each test that required a null database, I would
copy the db.null.dsm and log.null.dsm files to replace the db.dsm and
log.dsm, then start the ADSM server.

I don't know if this will work on non-solaris systems.

Ajax Dempsey

At 10:38 AM 1/27/99 -0500, you wrote:
>In order to do some testing, I have tried the following:
>
>1) Started with a 3.1.2.0 level Server
>2) Formatted a small database and log file
>3) dsmserv format 1 logfile 1 dbfile
>4) start ADSM
>
>I do not want to load any existing database, but try some testing on this
>small ADSM system.  However, when I bring ADSM up, it has no admins defined
>and I cannot get into ADSM to do anything.  Even the default admin/admin is
>missing.  Is there some way to get into ADSM to set up the first admins?
>
>I could go the route and dig out my CD, install the base system and install
>the upgrades as necessary.  But, this seems like a lot of unnecessary work
>if I don't really have to.
>
>Any ideas out there?   Thanks.
>Bob Price
>
>Westinghouse Information Systems
>4350 Northern Pike
>Monroeville, PA 15146-2886
>
>Email:   pricerr AT westinghouse DOT com
>Voice:   (412) 374-3247, (WIN) 284-3247
>FAX:     (412) 374-3470, (WIN) 284-3470
>
>