|
I have no problems with KLISTs at this time, but moving them into the 'D' spec is a good Idea to keep them in a single place. I currently have two approaches to doing KLISTs. 1. I define them in the beginning of my C specs for all my files. My KLISTs name mimic the file name. ex. ITEMAS file will have a KLIST of KyItemas if I have to use multiple KLISTs for a file (Partial keys or what not), I normally will append a 'F' or 'P' for full or partial. 2. I define the KLISTs in the subroutine that uses the file. ex. CSR GETREC BEGSRC C KyITEMBL KList C KFld WWITNB Item Number C KFld WWWHID Warehouse ID * C Eval WWITNB = P1ITNB C Eval WWWHID = P1WHID * C KyITEMBL Chain ITEMBL 99 By doing this, I know exactly what the KLIST is and the values. Debugging is simple. I just check the fields that are for the KLIST and I know if they are right or not. Michael * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the RPG/400 Discussion Mailing List! To submit a new * * message, send your mail to "RPG400-L@midrange.com". To unsubscribe * * from this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe RPG400-L' in the body of your message. Questions should * * be directed to the list owner / operator: david@midrange.com * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
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.