|
Hmmm! Does a keyed DELETE "include" a CHAIN or SETLL, hence the read? Would it behave differently if you SETLL by key and then DELETE without key? Would that work? Been too long! -------------- Original message -------------- > I would like to confirm something that was just discovered. I have a > trigger program (RPGILE) attached to a file that executes only when a read > event occurs. But it appears that a 'DELETE' operation on that file causes > the trigger to fire. This is not a situation where I read a record then > issue the 'Delete' operation. This is a 'delete' operation where the key > is specified. Can anyone confirm this? This particular application has a > series of program calls, that because of the 'read' trigger being executed > as a result of a 'delete' operation causes a recursive call. > > Thanks for any input. > > > Bill Greenfield > Senior Technical Consultant > Computer Applications Specialists, Inc. > 6201 Chevy Chase Drive > Laurel, MD 20707 > Voice: 301 776 3400 Fax: 301 776 3444 > BGreenfield@xxxxxxxxxxxxxx > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.