Don't know, maybe some do. I would advise following the book, examining the code, and maybe experimenting to get the results that seem to work the best (fsvo best).
Your issue came up from assembling on a higher level than you executed on. Gotta be careful with that. I do think IBM might have produced a better error. Something that resolved to "I don't support parmlist version > 2, and you gave me a 3." sas On Thu, Jan 31, 2019 at 7:59 PM Charles Mills <charl...@mcn.org> wrote: > Do others here agree with that advice? Eschew MF=(E,...,COMPLETE) ? > > Charles > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Jesse 1 Robinson > Sent: Thursday, January 31, 2019 4:10 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Cause of CsvdylpaRsnBadVersion? > > As a general rule for LIST/EXECUTE form macros, avoid coding anything else > on the execute call except for E. The reason is that the LIST call > determines what data needs to be included in the generated code. Once that > is built, any parm that would require a different size or list format will > no longer fit properly in the area already generated. Setting flags is > usually OK on MF=E as long as the flag(s) already exist. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- sas ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
