No integrity violation at all.
Simply bad coding.
While one could suggest a bi-address mode OPEN, I doubt that anyone other than
you would be interested.
Finally, IBM-MAIN would be much more appropriate.
On Fri, 11 Jun 2021 21:36:20 +0100 MELVYN MALTZ
om: "Seymour J Metz"
To:
Sent: Sunday, June 13, 2021 3:29 PM
Subject: Re: A problem with OPEN and CLOSE macros
Using an operand with the wrong length is a basic error, not limited to OPEN
or even to macros. Further, your code would fail even if you corrected
HERE24O to OPEN
13, 2021 3:29 PM
Subject: Re: A problem with OPEN and CLOSE macros
Using an operand with the wrong length is a basic error, not limited to OPEN
or even to macros. Further, your code would fail even if you corrected
HERE24O to OPEN (DCB1,INPUT,*,),MF=L; R5 doesn't contain a DCB address.
From: IBM Mainframe Assembler List [ASSEMBLER-LIST@LISTSERV.UGA.EDU] on behalf
of MELVYN MALTZ [072265160664-dmarc-requ...@listserv.uga.edu]
Sent: Friday, June 11, 2021 4:36 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: A problem with OPEN and CLOSE macros
1
I think there are many better uses of IBM development time.
-Original Message-
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On
Behalf Of MELVYN MALTZ
Sent: Friday, June 11, 2021 4:36 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: A problem with OPEN
Of Charles Mills
Sent: Friday, June 11, 2021 4:22 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: A problem with OPEN and CLOSE macros
OK, I kind of get your point. The OPEN will store the new R5 into the
executed MVC, which will cause it to move 256 bytes, regardless of the value
in R2.
But so
, your
bullet, your foot.
Charles
-Original Message-
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU]
On Behalf Of Charles Mills
Sent: Friday, June 11, 2021 3:53 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: A problem with OPEN and CLOSE macros
I think
IST@LISTSERV.UGA.EDU]
On Behalf Of MELVYN MALTZ
Sent: Friday, June 11, 2021 1:36 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: A problem with OPEN and CLOSE macros
1) An OPEN/CLOSE with MF=L,MODE=24 can be overlayed with an
MF=E,MODE=31 (and vice-versa). This results in destruction of the lis
No.
On Fri, Jun 11, 2021 at 4:36 PM MELVYN MALTZ <
072265160664-dmarc-requ...@listserv.uga.edu> wrote:
> 1) An OPEN/CLOSE with MF=L,MODE=24 can be overlayed with an
> MF=E,MODE=31 (and vice-versa). This results in destruction of the
> list,
> abends would occur
>
> 2) An OPEN/CLOSE
1) An OPEN/CLOSE with MF=L,MODE=24 can be overlayed with an
MF=E,MODE=31 (and vice-versa). This results in destruction of the list,
abends would occur
2) An OPEN/CLOSE with MF=L with (say) 2 entries can be overlayed with an
MF=E with 3 entries. The end-of-list bit isn't touched, but
10 matches
Mail list logo
