Peter, please change the thread subject when asking a different question. I've
done so now. And although I'm often around now (being retired) any new
question should be addressed to the list!
1. If you overlay a relocatable field with another relocatable field, you are
giving the assembler two conflicting definitions of the same storage location.
There will be more than one RLD (not ESD) entry and the results are likely to
be incorrect. I do not know what the binder and loader will do in this case,
but if they do not detect it, the result will probably be that relocation is
incorrectly applied twice.
2. The name operand on an END instruction specifies the default entry point for
the module. From what I remember, an undefined name (provided it is not part of
an expression) is assumed for historical reasons to be an external name to be
resolved at link-edit time. If it is not found at link-edit time, that is
therefore considered an error.
Jonathan Scott
-----Original Message-----
From: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> On Behalf
Of Peter Sylvester
Sent: 07 April 2025 14:56
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Object Record size
hi js,
i have two questions about hlasm
1 - which the following snippet in a csect
dc f'1'
x dc a(whatever)
org x
dc a(whatever)
it seem that one gets two esd entires ... that are supposed to treated by the
binder how?
(i may not use my personal eyeball utility correctly?)
2 - the END "card" inan object deck may have a name for a type 2 version.
the binder complains about the value, if the name is not in the module;
Why i this so?
You can add a " entry ep" just after the end instead, btw.
best
Peter Sylvester
