|
Rick.Chevalier@xxxxxxxxxxxxxxx wrote: > > Now it works. I don't know what I did but it's pulling in the field > lists for my output files now. > Just a guess, but you probably added some WRITE statements to the output records. Either of those would causing the O specs to get generated for your files, which would cause the output fields to be extracted. (The outline view does a verify under the covers, and the verifier (like the compiler), doesn't generate the O specs for any output records that aren't used in the program.) Or you might have added a subprocedure. The verifier/compiler will also generate the O specs for all output-capable files when it finds a P spec. It does that in case the subprocedures have any output operations that need the O specs. So, if you want the output fields in the outline view, but you don't want to add WRITE statements to your files yet, you can just code a blank P spec at the end of your source; it doesn't matter whether you actually have any procedures.
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.