Hi:
What I was reporting is how it was coded in a program (in
production). Which was astonishing to me!! I'd never seen any one
attempt this before that I can remember.
We have discussed this also on/in IBM Main. It was pointed out by
someone else, that this could lead to a S0C6 -- which is what
bothered me about how HLASM dealt with this to start with.
In all the code I've written and/or worked on from the S/360-20
through z/16s, this was the first time I can recall someone
attempting to "branch" to a drop statement. Or any other
assembler directive.
Your example, if it was on an odd boundary would result in S0C6 -
Specification error (which someone demonstrated on/in IBM Main).
I certainly hope the HLASM folks will take another look at this
and realize how this could be even more confusing to newbie ALC
programmers who may do this and then have such a directive end up
being preceded with something like DS X that would put the next
byte on an odd byte boundary (the S0C6 problem).
Regards,
Steve Thompson
On 10/2/2024 5:49 AM, Валерий Мѵронѣнко wrote:
Hi,
Try to rewrite it like this:
DROPR EQU *
DROP R11
LA R1, xxxxx
С уважением / Best regards / Atentamente / Meilleures salutations /
تحياتي الحارة / Cordiali Saluti / Freundliche Grüß,
*Валерий Мироненко*
*--*
Russia|Direct:+7 966 019-02-20
È CarPhone:
☁ Email: [email protected] | Security Email: [email protected]
© 2023 Tenants Group LLC / IDS LLC | Skype:
*ValMironenko*
P *Please consider the environment before printing this e-mail*
*_________________________________________________________________________________*
