To All,

Below is the Image DB schema that I used to 'scrub' the disk drives of a
retired HP3000.  It turns out that the database that I used consisted of
only a 'stand alone' detail set.

Regards
Paul Christidis

========================= Start Cut *+1
$CONTROL NOLIST,ROOT,TABLE,LINES=60,jumbo

<<This assumes that a volclass has been created that contains
  the specific disc drive.  For this specific case (LDEV=41) the
  following commands were used:
  :VOLUTIL
  Volume Utility A.02.00, (C) Hewlett-Packard Co., 1987. All Rights
Reserved.
  volutil: NEWCLASS MPEXL_SYSTEM_VOLUME_SET:disc41 (member41)
  ....
  ....
  exit

Where 'member41' is the volume name that corresponds to LDEV 41.  If
multiple
'members' were to be used then the syntax would have been:
volutil: NEWCLASS MPEXL_SYSTEM_VOLUME_SET:dummy41
(member41,member4x,etc...)

Then the capacity line below would be changed to correspond to the combined
disc space of the 'involved' members.  When the database will be created by
DBUTIL the required space would be 'allocated' and initialized to binary
zeros
thus 'over-writing' the existing data on the corresponding disc/discs.  One
could repeat the process a number of times to assure multiple
'over-writes'>>


BEGIN DATA BASE dumy41;

PASSWORDS:
    10 XXXXX;
    20 YYYYY;

ITEMS:
   Dummy-Item       ,   2 x128;

SETS:
   NAME:   Dummy-Set,      DETAIL (10/20), disc41; <<DummyDevClass>>
   ENTRY:
             dummy-item      ;

<< CAPACITY:   3050000;>> <<Capacity corr to ~1GB>>   << Dummy-Set >>
<< CAPACITY:   6100000;>> <<Capacity corr to ~2GB>>   << Dummy-Set >>
<< CAPACITY:  27450000;   <<Capacity corr to ~9GB>>   << Dummy-Set >>
   CAPACITY:  12200000;   <<Capacity corr to ~4GB>>   << Dummy-Set >>


END.
==================== End Cut *-1

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *