The difference becomes important when new code is given or testing. With the
option CIUPDATE=ALLOWED then your code would produce an error when
attempting to update a key item. This may indicate an error in your code.
Did you really want to change a key? If the setting was CIUPDATE=ON you
would not have an error but a corrupted database.
Now there are times in which you want to update the key item, and with the
setting of CIUPDATE=ALLOWED your program can thus set the flag at run-time
and update the key and then reset the flag. Thus accomplishing your task
with your full knowledge of what you were wanting. That is the reason for
the different settings. If you trust all your software and do not want to
mess with setting flags then turn the option on and away you go.

James

> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
> Behalf Of Leonard Berkowitz
> Sent: Monday, November 30, 1998 10:26 AM
> To: [log in to unmask]
> Subject: CIUPDATE
>
>
> I understand the difference between CIUPDATE=ON and
> CIUPDATE=ALLOWED (a call to
> DBCONTROL mode 5). Can someone provide a scenario where the distinction is
> significant? After all the same program[mer] can convert
> CIUPDATE=ALLOWED to
> CIUPDATE=ON.
>
> Thanks.
> ========================
> Leonard S. Berkowitz
> mailto:[log in to unmask]
> phone: (617) 972-9400 ext. 3250
> fax:   (617) 923-5555
>