I agree so much with what Peter says that I would do it manually before I would try to guess at how the assembler did things.
I don't see how modifying some macro to use AREAD is less effort than running the assembly and capturing the SYSADATA or SYSPRINT. You can easily "filter" ADATA on a particular DSECT name. (My program did that.) Probably the same would be true for SYSPRINT, but I have not thought about it. Charles -----Original Message----- From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On Behalf Of Joseph Reichman Sent: Monday, January 3, 2022 6:01 AM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Determining a group item Peter The data is the layout of a VB file it doesn’t have orgs for group items has 0 or nothing What I am trying and am not sure if I will succeed is read in the data via AREAD Using ADATA is not practical as there isn’t Production adata file of the record layout I could haphazardly take a production program and look for the esid of that copybook but it seems like overkill I’m in a testing group whose members know little assembler Rexx is used to validate data for instance when the government issues a stimulus payment The production record layout is VB with different sections What I am attempting is to generate and populate Rexx variables with the same name/symbols as that of assembler and corresponding value from the record Just had an idea for an RFE a debugger for the conditional assembly Thanks > On Jan 3, 2022, at 8:32 AM, Peter Relson <rel...@us.ibm.com> wrote: > > Joe, > > I can all but guarantee that trying to derive the offsets and lengths from > the source will miss edge cases that the assembler deals with. ORG is a > simple example of something that can be not overly straightforward. > > That is why looking at ADATA (or a listing) has a big advantage -- you are > utilizing information produced by the program responsible for dealing with > the subtleties. > > Peter Relson > z/OS Core Technology Design
