|
I have two object, both are *FILE and attribute of LF. One is created using DDS to create the LF and one is created in SQL using CREATE INDEX. I found that there is a difference in the attributes of the objects depending on what method was used to create the object. The DDS compiler default sets the Access Path Maintenance to *IMMED and Access Path Recovery to *NO. CREATE INDEX also sets the Access Path Maintenance to *IMMED --- but Access Path Recovery to *AFTIPL. I found this during a cpyf, where I tried to change the access path maint to *DLY (on the index) and found that if access path recovery is *AFTIPL, you cannot change access path maint to *DLY. So I changed *AFTIPL to *NO. Should I expect there be a problem with changing *AFTIPL to *NO on the indexes? Since they are both *FILE/LF's is there any reason why the default is different for this attribute? And as an aside, we always noticed significant performance degradation (user response time complaints) the day after an IPL - and I'm thinking this attribute may have been somewhat responsible. (And the only other difference I can see via DSPFD is that there is no file level id with the object created via create index.) Comments welcome. Regards, Jerry Gerald Kern MIS Project Leader, Lotus Notes/Domino Administrator IBM Certified RPG IV Developer, RPG IV Programmer The Toledo Clinic, Inc. 4235 Secor Road Toledo, OH 43623-4299 Phone 419-479-5535 gkern@xxxxxxxxxxxxxxxx ***** This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
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.