|
Thanks and sure Scott the section of code in question is below(ignore formatting issues caused by copy/paste).
I glanced over your code, and nothing jumped out at me that would cause an error about the statements being out of sequence.
Is it possible that the error is in the /include member? There were two other things that did jump out at me, however:a) You're setting *INLR in a NOMAIN module. (which won't have any effect, and may serve to confuse someone later)
b) You have fields that are defined in a subprocedure, but you're attempting to use them in your output specs. Since O-specs are global, fields that are in them also have to be global.
But, again, I don't see why this would cause an error about the statements being out of sequence.
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.
midrange.com
