One other ambiguity is that although the DSECT generated by the ASMADATA macro begins with the RDW, the offsets are against the byte following the RDW.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> on behalf of Peter Relson <rel...@us.ibm.com> Sent: Tuesday, November 5, 2024 8:23 AM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Offsets in ADATA Caution: This email did not originate from George Mason’s mail system. Do not click links or open attachments unless you recognize the sender and know the content is safe. The "source record" is what it says it is - your source. That is within an ADATA record (which is referred to in the documentation as "this record"). I do agree with you that "...in statement field" would seem much better as "...in source record" since there is no obvious other mention of a "statement field" (whereas there is a mention of a source record, and the length of it and the offset to it). It is not generally important what you "see". What is important is what you can rely on. Obviously the source record has to go "somewhere". With the current implementation it apparently goes right after the reserved fields. At least in the case you have. Maybe there are other cases where it doesn't to right there. The thing you can (and are expected to) rely on is that you can locate that source record by the provided offset field. You still did not share which web page you are looking at, but I expect that I am looking at what you're referring to. Peter Relson z/OS Core Technology Design
