Nick , et al :
          Here's my crib notes on how to do a database change.
          the objective is NOT only to add MDISK space but to recover the old
          MDISK.

          The hardest part is to understand that ADSM is smart enough to know
          what to delete and what to keep and to trust it.  Because you have
          to use extend and reduce commands and ADSM knows what to use.

          Just remember to run the   DSMDISK  from some other userid and then
          link the disk to the server
                                   cheers .. joe.f.
*     example of adding more errlog space
*       can be used to add more DB space too. just substitue ?
*%* q db
*%* q dbvol
<dirmaint define a new disk>
<run DSMMDISK 'offline' from some other id>
<cp link to new disk here ie) send cp dsserv link * etc
*%* define  dbvolume 201
*%* q db
(find out who much extending possible )
*%* extend db  32
*%* q process
(process takes time for log and is not immediate but is for db)
for sync'd (mirror) volume you have to ... ?
      define dbcopy  201 301
to eliminate old volume
      q dbvol format=detailed
      reduce db 136
      delete dbvol 200