|
Interesting outcome. Does the old rule "Write records, read files" be relevant here? --------------------------------- Booth Martin http://www.martinvt.com --------------------------------- -------Original Message------- From: RPG programming on the AS400 / iSeries Date: 04/21/05 14:00:39 To: RPG programming on the AS400 / iSeries Subject: Re: %KDS Compile Problem Tony, Thanks for pointing that out! I changed the file name to the record format name on the SETLL in my test program, and it compiled fine! I'm still confused though (and it will bug me until I find the answer), why will the Filename work on one system, but not another? Do you know if a specific PTF addresses this issue? Unfortunately, even though your work-around fixed the problem, I would rather not modify the code if I don't have to (for maintenance reasons). Thanks for the help! Mike > I had the exact problem on my system, and I have had several experts on this > board review my code (the first time it was a simple DS definition error). I > stopped using %KDS, and use ad-hoc keylists exclusively, which ought to be > the technique everybody uses, along with using DSs to READ to and WRITE from > -- but I oughtn't preach ;-) > > The workaround is to always CHAIN, READE, SETLL, etc using the RECORD FORMAT > NAME, instead of the file name. Don't ask me why, but when you use the file > name, strange things go bump in the night at times. -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.