HP3000-L Archives

November 1998, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Tony Furnivall <[log in to unmask]>
Reply To:
Tony Furnivall <[log in to unmask]>
Date:
Mon, 30 Nov 1998 10:06:56 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (15 lines)
At 10:26 AM 11/30/98 -0500, Leonard Berkowitz wrote:
>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.


I belive the primary difference is that CIUPDATE=ON is a system-wide
setting, while CIUPDATE=ALLOWED is a procss-by-process setting. IOW, if the
flag is set to ALLOWED, then you have to ENABLE it in your program; other
programs that do not enable it will not have access to the feature.
At any rate, that's what I recall from the dim and distant days of training
people on the capability!
Tony

ATOM RSS1 RSS2