OMG. "RUN THE EXAMPLE". I asked you to run it 3 times now. It obviously
doesn't branch to the LBL00. Instead, it abends. Totally unacceptable except
for personal use.
> That is the biggest complaint I have had with the macro from my people.
You should be ashamed having others use this macro. This must be a nightmare
for your QA people. You couldn't be bothered to use AREAD correctly. Don't use
AREAD unless it's needed and you are willing to code it correctly.
I've never complained about all the things you keep saying are my complaints.
I'm complaining that a macro SHARED with us (and used in your production) has
blatantly obvious bad branches when a label is in the wrong column.
> Considering that the one that told me to use AREAD, including providing > the
> base examples, was John Ehrman, I think I will take his opinion over yours.
John would never recommend this as a correct use of AREAD. Apparently you never
asked when NOT to use AREAD. You never asked why IBM avoids using AREAD in
their macro's. I would expect his examples to be for data generation and very
rarely for code generation.
> so the OP had something of an example.
I don't expect examples to be flawless. However, I do expect them to be
presentable and something they can actually use as a model.
I've tried several times to help you understand so this is my last attempt.
Regards, Jon.
On Sunday, March 10, 2019, 3:50:15 AM PDT, Tony Thigpen <[email protected]>
wrote:
Jon,
If you are fussing about the fixed-format of the input, then WTF. It's
use, by design, requires a fixed format input deck. It's documented that
way and if someone uses it wrong, then they are responsible for the
outcome. I work with programmers that can follow direction and use thing
right.
But, even if they do it wrong, then the worse outcome, if the '-----'
line is wrong, is a message from the assembler that the loop count is
exceeded. No big problem. It get's fixed and they move forward.
If other lines are not in the correct position, they get assembler
errors. Again, not a big problem.
Just because you don't like a fixed format input deck, does not mean
that the design is flawed or wrong. It's just a style you would not
implement but I will.
Are you also going to complain that the branch labels are restricted to
24 characters? That is the biggest complaint I have had with the macro
from my people.
