hi: On 07/04/2025 16:31, Charles Mills wrote:
Right, your example is almost exactly what is said in the doc of the org
instructiion
With the ORG statement, you can give two instructions the same location counter values. In such a
case, the second instruction does not always eliminate the effects of the first instruction.
Consider the following example:
|ADDR DC A(ADDR) ||ORG *-4 ||B DC C'BETA' |
In this example, the value of |B ('BETA')| is destroyed by the relocation of |ADDR| during linkage
editing.
Thanks for motivating rtfm seems a "compatibility" problem. ;-)
The reason for asking is:
i had ome disasembled code of a PUTGET MACRO, to seee whether a reaL call does something
different, I orGed and called the macro. surprise. so be it.
/P
With regard to the first one, I don' think it will generate any ESDs unless
you code EXTRN (or similar) for each of your whatevers.
If you do so, then I think HLASM generates an ESD even in cases where a human
could tell it was problematic coding. For example
EXTRN FOO
DC A(FOO)
ORG *-4
X DC F'1'
What will X contain at runtime? I don't know, but I know you would be foolish
to count on it containing anything in particular.
Charles
-----Original Message-----
From: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> On Behalf
Of Peter Sylvester
Sent: Monday, April 7, 2025 6:56 AM
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
