At work we were using debug tool to trace data the self modifying code had a EQAMODIN record of the form EQAMODIN LABEL where LABEL NOP LABEL1 Was the self modifying code. Since debug tool had issues we were going to use TEST to trace the records AT + (where;go) ADATA record type 36 had the offset and statement number However the EQAMODIN record doesn't generate neither a statement number or a offset of LABEL. Thing is debug tool uses EQALANGX records which are generated from SYSADATA input
Thought I could figure this out with just SYSADATA -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Charles Mills Sent: Monday, March 18, 2019 6:51 AM To: [email protected] Subject: Re: Sysadata record types for HLASM Not sure I understand your question perfectly but (a.) I don't think the ADATA makes any special distinction in the case of a self-modifying instruction and (b.) I suspect the ADATA has both the location and the number, but quite possibly in different records -- but my experience with parsing ADATA is with DS/DC, not executable instructions. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Joseph Reichman Sent: Sunday, March 17, 2019 9:36 PM To: [email protected] Subject: Re: Sysadata record types for HLASM Thanks Basically trying to determine from the eqamodin which specifies a self modifying instruction if the adata produced has a location or statement number of the self modified code ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
