Dave writes:

> Ciupdate can mess you up if you have extended sort keys (sorting by another
>  field immediately after the sort key), and your applications depend on it.
>  So our standard is to leave it 'allowed', and some applications that DON'T
>  go anywhere near extended sort keys do in fact do what Wirt thinks no one
>  has ever done......

I'm afraid that I don't understand. CIUPDATE is all about the easy and
efficient change of critical item fields (search and sort items) in a
dataset. It was put into IMAGE in part to replace the cumbersome
delete-and-reput procedure that was previously required, but it was primarily
implemented so that new keys could be added to underindexed datasets and not
affect any existing program.

If a key field's value is replaced, using either technique, it will of course
have an impact on an extended sort. But merely having CIUPDATE on will not
affect extended sorts by itself in any manner that I'm aware of.

Wirt Atmar

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