hi Scott,
Thank you for opening a case for this in our official support channel. We will
handle from there.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the messa
On Mon, 6 Jul 2020 14:55:39 -0500, Scott Fagen wrote:
With a great deal of online help from Steve Smith and Alex Brodsky, they
(independently) discovered that "above" the displayed code (generated within my
prolog), I had a DS statement that had a variable duplication factor that
relied on a v
Hi Scott,
It would be useful to see a more complete C snippet. IIRC, I've seen
this before where the __asm("":DS()) was not declared outside of the
main function.
On 2020-07-07 12:51 AM, Scott Fagen wrote:
I have a Metal C program where I am trying to add some static data via an
__asm(“…” :
On Mon, 6 Jul 2020 13:59:30 -0400, Steve Smith wrote:
>My guess is that something in your inserted prologue/epilogue code contains
>a forward-reference that causes HLASM to suspend the location counter in
>pre-assembly.
>
Steve - any idea of what I should be looking for. It's not clear to me how
My guess is that something in your inserted prologue/epilogue code contains
a forward-reference that causes HLASM to suspend the location counter in
pre-assembly.
The message (ASMA032E) is a prime example of the anti-pattern of issuing an
error message that makes you guess which of the listed poss
