Had second thoughts and thought this forum to be more appropriate
Thanks
J
Begin forwarded message:
> From: Joseph Reichman
> Date: April 22, 2019 at 9:25:10 AM EDT
> To: ibm-m...@listserv.ua.edu
> Subject: Sysadata symbol and literal cross reference record type x’44’
>
> Hi
>
> For progr
Using RSECT instead of CSECT would result in your example being flagged
as non-reentrant (self modifying) but it wouldn’t catch any indirect
modification such as: LA R5,LABEL MVI 0(R5),0LABEL DS
0H B. THERE The example would also
On 4/22/19, Keven wrote:
> There’s almost no
> reason to use self-modifying code that makes sense anymore...
My impression was that the original poster was hoping to use the
assembler's facilities to root out instances of self-modifying code in
existing programs.
--
Bob Netzlof a/k/a Sweet Old
I am trying to determine what instructions are self modifying using sysadata
wondering if there is any way to determine that
-Original Message-
From: IBM Mainframe Assembler List On Behalf
Of Keven
Sent: Monday, April 22, 2019 5:18 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: S
To be more clear this goes back to the original problem of tracing a 14 cesct
huge piece of code I am wondering if I can identify what instructions are
modified
Thanks
-Original Message-
From: IBM Mainframe Assembler List On Behalf
Of Keven
Sent: Monday, April 22, 2019 5:18 PM
To: A
Yes
> On Apr 22, 2019, at 5:25 PM, Robert Netzlof wrote:
>
>> On 4/22/19, Keven wrote:
>>
>> There’s almost no
>> reason to use self-modifying code that makes sense anymore...
>
> My impression was that the original poster was hoping to use the
> assembler's facilities to root out instanc
On 2019-04-22, at 15:38:03, Joseph Reichman wrote:
> To be more clear this goes back to the original problem of tracing a 14 cesct
> huge piece of code I am wondering if I can identify what instructions are
> modified
>
There's the empirical approach: Save a copy as REFR; run it; see what brea
Sysadata type 44 will catch most
> On Apr 22, 2019, at 5:54 PM, Paul Gilmartin
> <0014e0e4a59b-dmarc-requ...@listserv.uga.edu> wrote:
>
>> On 2019-04-22, at 15:38:03, Joseph Reichman wrote:
>>
>> To be more clear this goes back to the original problem of tracing a 14
>> cesct huge piec
