On Wed, 9 Jul 1997 10:13:45 -0400, Gary Nolan
<[log in to unmask]> wrote:

>After two lost SR#''s  my third has arrived in the mail.

>KPR# 5003370999 Turboimage/xl

>Dbutil move corrupts the eof of dynamic data set expansion defined ds.

>Problem:
>When the 'MOVE set TO device' command issued through DBUTIL,
>the set on the target device has a different EOF.

>--------------------
>The short of this is, use dbutil to move data set with dynamic expansion
>and the set will become corrupt.

I ran into this bug/feature several years ago by accident and at the time
considered it a "feature" because it allowed me to "fix" datasets whose EOF
had become different then the LIMIT.  This was in the days before DDX when
a dataset had to have an EOF = LIMIT.  If the EOF was less than the LIMIT I
could use DBUTIL Move to move the dataset several times until the EOF
equaled the LIMIT.

With the advent of DDX this is indeed a problem and one that needs to be
fixed.

/PLUG ALERT

Adager contains a Move Dataset command which does not have this problem.

Adager also does a "Consistency Check" every time it opens a database and
looks for problems like the one that Gary points out.  If Adager finds such
a damaged dataset it will go into "Root File Therapy" and allow the user to
update the root file capacity to match the new EOF.

/END PLUG ALERT

Hope this helps,


+---------------+
|               |
|            r  |  Ken                             [log in to unmask]
|          e    |                           http://www.adager.com
|        g      |  Ken Paul                      Tel 208 726-9100
|      a        |  Customer Support              Fax 208 726-2822
|    d          |  Adager Corporation
|  A            |  Sun Valley, Idaho 83353-3000            U.S.A.
|               |
+---------------+