Bruce writes:

> The problem with updating a non-critical item which is part of an extended
>  sort is a problem with DBUPDATE whether or not CIUPDATE is turned on. One
>  solution to this problem would be if IMAGE was able to recognize these
items
>  as critical in addition to the actual sort item and then drop into CIUPDATE
>  mode (if it is turned on), or disallow the update of the (extended)
critical
>  item if CIUPDATE is off.
>
>  Perhaps now we are talking about a third enhancement request.

Let me modify my request again, this time into three parts:

=======================================

Part A: Change the CIUPDATE setting in IMAGE to ON as the default. This is
the manner the setting should be set as IMAGE heads into the sunset (and
possibly a brighter future). Estimated lab effort: 3 minutes.

Part B: Modify the insertion procedure of the current CIUPDATE code to pay
strict attention to "extended sort" criteria, something CIUPDATE apparently
does not now do, thereby making it the functional equivalent of a
DBGET-DBDELETE-DBPUT sequence, only vastly more efficient. This is not a
difficult change. Estimated lab effort: 1 week.

Part C: Modify DBUPDATE so that it will honor the extended sort requirements
of the record if any item's value in the extended sort range is changed,
regardless of whether the item being modified is critical or not. This too is
not a difficult change. Estimated lab effort: 1 week, although this request
could easily be piggy-backed onto Part B's work.

======================================

There should be no ON or OFF flags for any of these items. This is either the
way that IMAGE should have operated from the beginning or is the manner that
IMAGE is described to work in the current manuals.

Wirt Atmar

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