Ref: Your note of Fri, 20 Mar 2020 10:01:28 -0600
gil writes:
> On 2020-03-20, at 05:32:28, Jonathan Scott wrote:
> >
> > Further testing has revealed that this test case fails on every
> > release of HLASM we have here back to HLASM 1.2 from around 1995.
> > So the good news for us is that the c
On 2020-03-20, at 05:32:28, Jonathan Scott wrote:
>
> Further testing has revealed that this test case fails on every
> release of HLASM we have here back to HLASM 1.2 from around 1995.
> So the good news for us is that the current team did not break
> it, but the bad news is that the original imp
Thanks Jonathan, much appreciated.
Still waiting on access approval to raise an official report for you.
Ian
On Friday, March 20, 2020, 11:38:10 AM GMT, Jonathan Scott
wrote:
Ref: Your note of Wed, 18 Mar 2020 17:58:43 +
Jonathan Scott wrote:
> The problem occurs on the target ins
Ref: Your note of Wed, 18 Mar 2020 17:58:43 +
Jonathan Scott wrote:
> The problem occurs on the target instruction of a forward
> conditional assembly branch, and appears to suggest that the
> wrong ICTL setting is being used when lookahead processing is
> used in open code to skip ahead to f
Ref: Your note of Wed, 18 Mar 2020 15:47:13 +
Ian Worthington writes
> However, when I set an ICTL of 1,79,2 and COPY in a member
> which works perfectly well without the ICTL, all hell breaks
> loose, with parts of the seqno being inserted into the text
> body.
I think you lost the battle t
Source is properly formatted here: ictl confusion
|
|
|
| | |
|
|
|
| |
ictl confusion
The HLASM LangRef is very explicit and clear about the effect of the ICTL
instruction on the COPY members, viz: ...
|
|
|
On Wednesday, March 18, 2020, 03:54:38 PM GMT, Ian Worthingto
Curses. These have been line-wrapped into oblivion. How do I stop the
listserv doing that?
i
On Wednesday, March 18, 2020, 03:50:59 PM GMT, Ian Worthington
<0c9b78d54aea-dmarc-requ...@listserv.uga.edu> wrote:
LISTING:===- Loc Object Code Addr1 Addr2 Stmt Source Statement
HLASM R6.0 2020/03/18 13.41 0
1 ictl 1,79,2
... -
The HLASM LangRef is, as far as I can see, very explicit and clear about the
effect of the ICTL instruction on the COPY members, viz:
COPY Instruction: The ICTL instruction does not affect the format of statements
brought in by a COPY instruction or generated from a library macro definition.
T
