Re: Possible timing issue with IO -- 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.

yeah, actually everything related to IO was immaterial.

I knew that DB management should have got things done in good order - again, that contributed to my wonderment.

It was more a matter of putting one kind of process in the middle of another one and not seeing how the "individual" nature then went against the structure when run on its own.

Oh well, another conquered!

Vern

On 1/26/2014 3:46 PM, CRPence wrote:

On 26-Jan-2014 13:24 -0800, Vernon Hamberg wrote:

On 1/26/2014 12:08 PM, Mark S Waterbury wrote:

Do those logical files over this physical file have "Access path
maintenance" set to MAINT(*IMMED) or *DLY or *REBLD?

<<SNIP>>

Maintenance is *IMMED - we'd wondered about that.

<<SNIP>>

The MAINT() is immaterial, because the LF would have been opened by
the program by that key to do its lookups. Any open via a keyed access
path has that keyed AccPth maintained immediately, irrespective its
MAINT(). If delayed AccPth maintenance, then the open synchronously
awaits all delayed maintenance being applied. If rebuild access path
maintenance, then the open synchronously awaits the entire [re]build of
the AccPth.

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.