|
Buck, AHA! Me too (live and learn that is) the operative keyword must be EXTFMT(P). i also tried changing the table record len to 5 (as it should be) using this keyword and it compiled and ran fine. the PERRCD(1) keyword is unnecessary, whether you use 5 or 10. 1 is the default for that keyword. Are you getting all of this Sunil? btw, when was the last time anyone actually designed for table files? I know it's quicker to do a lookup, but I just chain anymore. This, i'm pretty sure was a 'feature' that was introduced before the chain opcode, and used after chain, only because random disk access used to be so resource expensive. it's so nice to rarely have to count cycles anymore.... Rick ----Buck's original message------- Live and learn. (me that is) I did it in RPG III like this: FPF1 IT F 10 EDISK E PF1 ARE 1 1 9P0 C ARE,1 DSPLY C SETON LR Then I did a CVTRPGSRC and got this: FPF1 IT F 10 DISK D ARE S 9 0 DIM(1) EXTFMT(P) FROMFILE(PF1) D PERRCD(1) C ARE(1) DSPLY C SETON LR
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.