o: 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 buil
Of Charles Mills
Sent: Friday, February 01, 2019 6:27 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Cause of CsvdylpaRsnBadVersion?
Thanks all.
> Charles fell
> into the subtle case that specifying PLISTVER=MAX in effect is saying
> "I am using new function".
I p
inframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Peter Relson
Sent: Friday, February 1, 2019 4:59 AM
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 ex
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
Not for macros written in the base control program (and elsewhere) in the
past 30
sion 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 e
On 2019-02-01 11:59 AM, Charles Mills wrote:
Do others here agree with that advice? Eschew MF=(E,...,COMPLETE) ?
Numerous newer (in geological terms) macros simply define a storage area
with MF=L. For these I use PLISTVER=MAX with MF=L when it's available,
and in these cases I also use
iginal 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
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
...@sce.com
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Charles Mills
Sent: Thursday, January 31, 2019 3:37 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Cause of CsvdylpaRsnBadVersion?
And the answer is:
1. Don't code
: IBM-MAIN@LISTSERV.UA.EDU
Subject: Cause of CsvdylpaRsnBadVersion?
I've got CSVDYLPA code that has been working more or less unchanged for
eight years -- no idea what release of z/OS it was developed on. (The coding
has not changed but it is re-assembled from time to time -- the most recent
obj
Of Charles Mills
Sent: Thursday, January 31, 2019 11:04 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Cause of CsvdylpaRsnBadVersion?
I've got CSVDYLPA code that has been working more or less unchanged for
eight years -- no idea what release of z/OS it was developed on. (The coding
has not changed
I've got CSVDYLPA code that has been working more or less unchanged for
eight years -- no idea what release of z/OS it was developed on. (The coding
has not changed but it is re-assembled from time to time -- the most recent
object module was created on V2R2.)
All of a sudden I am getting return
12 matches
Mail list logo
