Charles
I can subscript the setc symbol from the AREAD
I’m doing this in a call from the rexx
As long as I get the production copybook
Once this is done it’s done
Meaning I don’t have to change it every time the copybook(s) change
I am not really aware when those change take place and if they do I would have
to assemble a new sysadata file. As far as the Duplication factor
It always been 0 or nothing if it’s zero won’t bump it up
If not I can do &lenvar SETA L’FIELDA
And bump up the value by that
I really don’t know when the copybooks are changed mostly in the beginning of
year but not necessarily
Every time that happens I would have to reassemble to produce an adata of the
copybook(‘s)
It maybe easier with adata but necessarily more practical
Thanks
> On Jan 2, 2022, at 7:30 PM, Charles Mills <charl...@mcn.org> wrote:
>
> 1. Unless my recollection of AREAD is flawed, it will just give you the raw
> source code. It's not much different from reading the source file. In order
> to determine offsets and so forth you would have to write your own assembler:
> you will have to "know" what FOO DS 3PL8 "means." You will have to bump your
> internal location counter by 24 and read the next card image. You will have
> to understand the location counter implication of DS 0F and ORG FOO-7.
>
> 2. With regard to processing the listing rather than the ADATA, I have to say
> that "intellectually" I don't like it ("listings are for people; ADATA is for
> this sort of task") but practically it sounds like a fine idea. All of the
> offsets and symbol values are there and it is easy to figure out -- no trying
> to interpret some structure of binary data.
>
> (Is it clear whether a symbol is relocatable or not? Is the difference
> between FOO EQU * versus FOO EQU 126 clear from the listing?)
>
> 3. You might consider Rexx for the processing language, especially if you are
> going to process SYSPRINT.
>
> 4. Whichever route you go, I would divide the project up into two phases:
>
> i. Parse the input (SYSPRINT or ADATA). Build a big table with everything you
> think you might need to know about each symbol (name, offset, value, format,
> length, comment). Dump that table out to make sure it is right and you
> understand what you have done.
>
> ii. Turn it into the Rexx statements that you need.
>
> Charles
>
>
> -----Original Message-----
> From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU]
> On Behalf Of Joseph Reichman
> Sent: Sunday, January 2, 2022 1:31 PM
> To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
> Subject: Re: Determining a group item
>
> That’s what I thought not punching out but doing a number of SETC to generate
> dc’s
> That will help me define/populate Rexx variables
>
> Thanks
>
>> On Jan 2, 2022, at 4:27 PM, Steve Smith <sasd...@gmail.com> wrote:
>>
>> When I've done similar things, I just wrote a macro to replace DS, and it
>> punched out the appropriate line in whatever language I needed. Seemed to
>> be far easier than reprocessing source/listings/adata.
>>
>> sas
