Re: RPGLE with embeded SQL cursor over file with *READ trigger -- RPG400-L

Subject: Re: RPGLE with embeded SQL cursor over file with *READ trigger
From: CRPence <CRPbottle@xxxxxxxxx>
Date: Tue, 23 Oct 2012 10:06:27 -0500
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the IBM i / System i <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

On 22 Oct 2012 22:16, Mark S Waterbury wrote:

The OS (IBM i or OS/400) does not "protect" *PGM objects (or
*SRVPGMs), e.g. by placing a *SHRRD (*USE) lock on them when
they are "in use" (e.g. called or activated in some jobs).

However as I recall, the OS, specifically the database component of the OS, *does* lock a "trigger" program when a database file, one which previously was associated with that program as a trigger [ADDPFTRG; or CREATE TRIGGER, but there is no *READ for SQL triggers], is opened for the type of I\O covered by that trigger.

Follow-Ups:

Re: RPGLE with embeded SQL cursor over file with *READ trigger , Mark S Waterbury
Re: RPGLE with embeded SQL cursor over file with *READ trigger , Mark S Waterbury

This mailing list archive is Copyright 1997-2026 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.