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

× 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.

Hi, Chuck:

Thanks for those added comments. I recalled this as well.

The OP's original post did not contain any specific error messages the OP said they received, nor any context to describe exactly what the circumstances were, or when those errors occurred,

So, I just responded to the last paragraph of the OP's post, since the method described (using RSTOBJ to replace a *PGM in "production") will destroy a *PGM (or *SRVPGM) while it is potentially "in use" by one or more other jobs, thus causing various failures in "production" jobs.

Mark

> On 10/23/2012 11:06 AM, CRPence wrote:

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.

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.