Not sure if this helps:
/cisco-ar/usrbin/mcdadmin: [-c] -d {dbdirname|DEFAULT} -[r|R] DBPATH -p
DBPATH -i importfile -e exportfile [-z C=N]
where:
-c attempts to create database
-o when creating, overwrite pre-existing database
-T recopy database templates when creating database
-t DIR specifies directory from which to get database templates
-d DBNAME specifies the database name, or "DEFAULT"
-N NAME specifies username (will prompt if not given)
-P PASSWORD specifies password (will prompt if not given)
-s supplies default name and password
-i IMPORTFILE specifies file to import from. ("-" for stdin)
-l don't hold exclusive lock while importing (slower, but
friendly)
-e EXPORTFILE specifies file to export to. ("-" for stdout)
-f EXPORTFILE exports diffable file (not importable) to export
to. ("-" for stdout)
-a DBAREA specifies the "area" of the database to use
("config", "state", "altconfig", or "altstate",
defaults to "config"
-p DBPATH specifies (on export only) what to export
-r DBPATH specifies something to remove ("trims" table)
-R DBPATH removes recursively! (or "clobbers" table)
The use of DBPATH in -p, -r, and -R is as follows: either
it is an absolute pathname, starting with '/', in which
case it refers to that part of the MCD tree, or it is a
"server zone name" tuple, starting with ':'. The names
after
the ':' are whitespace separated, and the name or zone and
name may be left unspecified. example: -p "myserv azone
foo"
-G GENERATION specifies generation number for RR table export
-H says full table generational history should be dumped
-k kill the lockmgr, do nothing else
-z CCC=N sets debugging classes CCC to level N
-v, -V prints version information
