×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 30/05/2007, at 2:53 AM, Walden H. Leverich wrote:
I believe (but won't bet on it) that there's an API that will set
those
flags on a file too. Perhaps the APIs could be used on a table? I
would
think so.
If such an API existed then possibly but it doesn't (well I could
find no public API that exposes these attributes in the InfoCentre).
These attributes are set at CREATION and cannot be altered after
creation via CHGPF or similar.
Of course, there is always SST ...
I see other appenders have suggested:
1) OVRDBF INHWRT(*YES)
Respected by SQL INSERT, UPDATE, and DELETE but does not issue an
error--simply ignores the attempted write. This is different from
ALWUPD(*NO) ALWDLT(*NO) for which an UPDATE or DELETE operation will
fail with SQL0150. Interesting that this message refers to a VIEW or
LF ...
2) Use triggers to deny the operation
As I see it the major problem with these options is that they require
either action at run-time (i.e. OVRDBF) or reliance on a state that
can be changed (i.e., the trigger can be dropped by a suitably
authorised person). The ALWUPD and ALWDLT attributes can only be set
at creation and cannot be changed later except via deleting and
recreating the file (or judicious use of SST) which makes these
settings more secure.
Regards,
Simon Coulter.
------------------------------------------------------------------------
--------------
FlyByNight Software OS/400, i5/OS Technical Specialists
http://www.flybynight.com.au/
Phone: +61 3 9899 0985 Mobile: +61 0411 091 400 /"\
Fax: +61 3 9899
0985 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
------------------------------------------------------------------------
--------------
midrange.com
