On 07 Feb 2013 03:45, Raul A. Jager W. wrote:
I think I will use the triggers.
I will also look for an "exit point" on opening the file, maybe I
can limit the open to only read.
No reason to "look for". That is the Database Open exit. But as
with ALWDLT(*NO), the Database Open exit will not enable preventing
Clear because that method is not implemented using Data Management Open;
a delete trigger will still be desirable even if the exit prevents all
but read-only opens.
# Subject: Re: Exit Point When Opening a Source Member with RDP ?
# From: CRPence
# Date: Tue, 22 Jan 2013 11:19:39 -0800
"... QIBM_DB_OPEN exit enhancement ..."
even further refinement in the support; I did not search for any cross
reference to either v5r4 or v7r1, for an equivalent to this change:
APAR SE53671 v6r1 IBM i 6.1 R610 SI48461 1000 /* no cumulative */
Allow greater flexibility for defining when the Open Database File Exit
Program is called.
_i Open Database File Exit Program i_
" Required Parameter Group:
1 Open Database File Input Information Input Char(*)
2 Return Code Output Binary(4)
Exit Point Name: QIBM_QDB_OPEN
Exit Point Format Name: DBOP0100
QSYSINC Member Name: EDBOPNDB
The Open Database File exit program is called when a job is opening a
database file. This exit is called in the job that is attempting to open
the file. The exit program is passed a list of files referenced in the
open request and the open options. The exit program may set a return
code value to end the open request. When an open request is issued, the
operating system calls the user-written exit program through the
registration facility. For information about adding an exit program to
an exit point, see the Registration Facility APIs.
Exit program introduced: V5R3"