I have put together a series of PowerPoint files illustrating the operation of
the vector-facility instructions ... a sort of graphic-novel version of
Chapters 21-25 of the PoO. Since the Assembler List doesn't accept file
uploads, you can find the material on my Google drive:
Thank you, John!
This is a good solution, and it's a "doh" moment for me that I did
not think of it myself.
Your suggestion gives the equivalent functionality, So I'll adopt it,
but with a variation.
Ideally, I'd like to create your MNOP macro in my macro library, but
then OPSYN won't
Ref: Your note of Tue, 28 Sep 2021 07:47:02 -0400
Steve Smith writes:
> From reading the APAR, it seems HLASM thought it better to produce ASMA001E
> rather than (potentially) ASMA951U. I can't see it was worth breaking Dave
> Cole's scheme. It seems that ANOP is on the "restricted" list, and
>From reading the APAR, it seems HLASM thought it better to produce ASMA001E
rather than (potentially) ASMA951U. I can't see it was worth breaking Dave
Cole's scheme. It seems that ANOP is on the "restricted" list, and you'll
have to OPSYN to something that isn't. And hopefully that doesn't
Ref: Your note of Tue, 28 Sep 2021 06:53:32 -0400
The quick and safe solution to suppress PRINT instructions is to
define a dummy inline PRINT macro that does nothing.
PRINT OPSYN ANOP is legal if used before a macro is defined, but
it is not allowed to be used at generation time when it was
On 28/09/2021 11:53, David Cole wrote:
When print suppression is scattered all hither and yon throughout a
complex set of inner macros, debugging subtle problems can be seriously
hindered. So how do you easily get rid of print suppression?
I use the assembler option:
PCONTROL(GEN,MCALL,ON)
This is about debugging a complex mesh of macro calls when PRINT OFFs
and PRINT NOGENs are used by the macros.
When print suppression is scattered all hither and yon throughout a
complex set of inner macros, debugging subtle problems can be
seriously hindered. So how do you easily get rid of
