One of my pet peeves is when IPCS...
You know how the IPCS LIST command helpfully aligns the output where it starts
in the correct column for the starting address:
+0 00F9AB18. FCE0 E2D4C3C1 |.\..SMCA|
+8 00F9AB20. 0D69 807E3000 E7E7E7E7
From: Hall, Keven keh...@informatica.com
Sent: Friday, 8 October 2010 5:46 AM
One of my pet peeves is when IPCS (for example) does this:
40404040 40404040 40404040 ||
0010 ||
0020 Next X'0010' bytes same as
On Oct 8, 2010, at 04:43, robin wrote:
In fact, with some printers, printing would actually be
slowed down by having to print the alpha characters
of the message (compared to printing only numeric).
That's s Twentieth Century.
And I wonder even about the economic tradeoff between
printer
In general I am sympathetic to these musings. I also believe clarity is
very important. But I am compelled to add a few observations.
First, my experience has been that the maintenance of hand-coded finite
state machines is difficult. There are wonderful tools for building (and
rebuilding) FSMs
First time I saw this was in 1968 in some 'n'-inches thick stack
of fan-fold paper. It saved thousands of trees, millions of $$$ on
paper, ribbons and computer time from the IBM 1401 1960's to
the day a SYSUDUMP became too big to print and carry o one's
desk. Today it's mostly in the way and I
. Ramaekers
Sent: Monday, October 04, 2010 13:08
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: 16-bytes the same
Depends on the situation. I was writing my own DUMP routine (via email)
and needed to look for repeated blocks (16-bytes). If found (more than
once), than I could insert a Same
-Original Message-
From: IBM Mainframe Assembler List [mailto:assembler-l...@listserv.uga.edu] On
Behalf Of Hall, Keven
Sent: 07 October 2010 19:46
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: 16-bytes the same
One of my pet peeves is when IPCS (for example) does this:
40404040
On 10/7/2010 12:06 PM, Rob Scott wrote:
I agree - I would *love* to know how to override this behaviour in IPCS - I
find that it gets in the way much more than it helps.
It would be nice if the person analyzing the dump could tell IPCS that it would
take at least 256 equal bytes (for
On 10/7/2010 1:06 PM, Rob Scott wrote:
I agree - I would *love* to know how to override this behaviour in IPCS - I
find that it gets in the way much more than it helps.
Sometimes. I remember once entering a thoughtlessly composed operator
command,
perhaps d u, whatever and watching
My first post was remiss in not noting another important use of
blanks-substring detection, which is due originally to the late John Cocke.
The most important determinant of the performance of a translator--compiler,
interpreter, assembler, whatever--is the speed and efficiency with which it
At 02:51 + on 10/08/2010, john gilmore wrote about Re: 16 bytes the same:
Apart from its obvious usefulness in processing right-to-left text
like that of Arabic, Farsi, and Hebrew, the TRTR instruction is
valuable for locating the rightmost non-blank character in
left-to-right text
At 12:02 + on 10/06/2010, john gilmore wrote about levels of
abstraction (was: 16-bytes the same):
Why use a TRT, which requires a table of, usually, 256 bytes, when
something more compact can be put together for the special case of
16 blanks (or nuls)? The answer can be boiled down
, October 04, 2010 1:08 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: 16-bytes the same
Depends on the situation. I was writing my own DUMP routine (via email)
and needed to look for repeated blocks (16-bytes). If found (more than
once), than I could insert a Same as above
On Tue, Oct 5, 2010 at 3:29 PM, Bill Fairchild bi...@mainstar.com wrote:
I couldn't think of a useful reason for such code either, other than
perhaps as a teaching exercise. But I was going to reply Who cares what the
value of it is? Why not just answer the original question? A long time
On 10/5/2010 9:45 AM, Rob van der Heij wrote:
But that would involve comparing two strings, rather than a string
with a character? I would be pretty annoyed reading a dump and get
portions omitted with ... these 32 byte are all the same, guess what
they are...
Note that Bill did say ...or
From: McNeill,Cliff cmcn...@mdanderson.org
Sent: Wednesday, 6 October 2010 1:08 AM
If the check is to eliminate 16 duplicate bytes that follow, shouldn't the CLC
be checking for a length of 16 (17 less
1)?
I thought that this had been settled some time back --
with a detailed byte-byte
From: Frank M. Ramaekers framaek...@ailife.com
Sent: Friday, 1 October 2010 5:14 AM
Doesn't the following statement check to see that all 16-bytes are same?
00251A D50E 5001 5000 1 0 8688 CLC 1(15,R5),0(R5)
Useful if you know the value of one of the bytes.
Not quite so
-Original Message-
From: IBM Mainframe Assembler List
[mailto:assembler-l...@listserv.uga.edu] On Behalf Of Tony Thigpen
Sent: Friday, October 01, 2010 8:33 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: 16-bytes the same
Why would you say that? The code *will* check to see
On Oct 1, 2010, at 10:12, robin wrote:
From: Frank M. Ramaekers framaek...@ailife.com
Sent: Friday, 1 October 2010 5:14 AM
Doesn't the following statement check to see that all 16-bytes are same?
00251A D50E 5001 5000 1 0 8688 CLC 1(15,R5),0(R5)
Useful if you know
Yes, it does.
Although I'd apply the appropriate commentary in most circumstances (as a
memory jogger).
Mike.
-Original Message-
From: framaek...@ailife.com
Sent: Thu, 30 Sep 2010 14:14:10 -0500
To: assembler-list@listserv.uga.edu
Subject: Help jog my memory (16-bytes the same
. Ramaekers Jr.
-Original Message-
From: IBM Mainframe Assembler List
[mailto:assembler-l...@listserv.uga.edu] On Behalf Of Watkins, Douglas
Sent: Thursday, September 30, 2010 2:36 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Help jog my memory (16-bytes the same)
This statement
Sorry, I misunderstood what the OP must have been meant by the same --
thus, he's checking that the 16 bytes of a single area are all the same
as one another (or, each byte is the same as the next within it), right?
Not, as I first had read, as two collections, this operand's 16 bytes is
the same
@LISTSERV.UGA.EDU
Subject: Re: Help jog my memory (16-bytes the same)
Sorry, I misunderstood what the OP must have been meant by the same --
thus, he's checking that the 16 bytes of a single area are all the same
as one another (or, each byte is the same as the next within it), right?
Not, as I
23 matches
Mail list logo
