On 4/3/2022 2:38 PM, Charles Mills wrote:
HLASM always (?) chooses the smallest offset when it has multiple choices.
And when the offsets are equal, it chooses the higher-numbered register...
--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
On Sun, 3 Apr 2022 at 15:02, João Reginato wrote:
> Hi guys
> Take a look in these pieces of code compiled in z/OS V2R4: (use any
> proportional font like courier for better understanding)
>
> 000BCC D2A5 D100 8B94 00100 02B94 2107 MVC
> WKINFO(LINFO/2),LKINFO INITIALIZE DYNALLOC
>
I didn't realize it reading your answer, Abe, until after I wrote mine, but
yes, I think I am saying the same thing you said.
Charles
-Original Message-
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On
Behalf Of Abe Kornelis
Sent: Sunday, April 3, 2022
Ah! You said location counter. You meant offset. (Not criticizing; it's just
that I took you literally.)
You want to know why are the first 3 s-cons 8xxx and the remainder Dxxx?
** ASMA303W Multiple address resolutions may result is a hint. You got a whole
lotta USINGs there.
It was using R8 as the base register +displacement and suddenly changes to
R13 as you can see in 8A92D000, ie. R8+x'A92' and then R13(RD)+x'000'
Em dom., 3 de abr. de 2022 16:42, Charles Mills escreveu:
> 002A8E 5341+PATCH_AREA DS 0H PATCH AREA
> 002A8E
002A8E 5341+PATCH_AREA DS 0H PATCH AREA
002A8E 8A8E8A908A92D0005342+ DC64S(*) PATCH AREA
002A96 D002D004D006D008 ==> THE LOCATION COUNTER WAS CHANGED SUDDENLY
002A9E D00AD00CD00ED010
The location counter changed by 8, no? 8 bytes of
I don"t think so because it will just eject the page when printed
Em dom., 3 de abr. de 2022 16:29, Abe Kornelis escreveu:
> Joao,
>
> from what I see it appears that the assembler thinks you have an active
> USING
> with R13 pointing to the location where the S-con of D000 appears,
> offset
Joao,
from what I see it appears that the assembler thinks you have an active
USING
with R13 pointing to the location where the S-con of D000 appears,
offset 2AA4 in the listing.
I see you do have an ASMA303W indicating overlapping USING ranges.
You do have the active USINGS in the page header,
Hi guys
Take a look in these pieces of code compiled in z/OS V2R4: (use any
proportional font like courier for better understanding)
000BCC D2A5 D100 8B94 00100 02B94 2107 MVC
WKINFO(LINFO/2),LKINFO INITIALIZE DYNALLOC
000BD2 D2A5 D1A6 8C3A 001A6 02C3A 2108 MVC
On Sat, 2 Apr 2022 at 19:59, Tony Thigpen wrote:
> I have used ARs to get data from other VSE partitions (address spaces to
> you z/OS guys). I am looking at a program that needs to 'snap shot' a
> partition by copying a lot of data, then printing it.
>
> I have never used "move to primary" or
On Sun, 3 Apr 2022 at 12:30, Dan Greiner wrote:
[...]
> What you might want to consider is the cost of totally trashing your data
> cache with all of stuff you're copying.
> To minimize that cache trashing, read up on the special pad characters for
> MVCL and MVCLE. When these
> instructions
The only possible difference between using ARs versus MVCP/MVCS is that there
is the overhead of AR translation. However, if you're limited to only a single
source and destination address space, then this will happen once, and the
results will be cached in the ALB; so the issue is probably
I much prefer having eyecatchers show up in save area tracebacks, even if that
"wastes" space.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Assembler List [ASSEMBLER-LIST@LISTSERV.UGA.EDU] on behalf
of Martin Trübner
"Pro" ¬= "hacker". Obfuscated code contests are for amusement, not for
production code.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Assembler List [ASSEMBLER-LIST@LISTSERV.UGA.EDU] on behalf
of Martin Ward
Tony,
I assume it is for debugging problems at customerside.
I would do it verifyable --- issue a SUSPEND (via SVC 30) and then issue
the DUMP-commands (again via SVC 30) - that way you can easy check that
you have what you want and you would not need to debug corners of the
program that
Tony,
My tuppence, since I do not really know VSE I may be quite wrong ...
The fastest copy for a very large amount of data would probably be to
manipulate the page table entries
of your partition to map to the source partition's page frames of
interest into an available page range of your
On Sat, 2 Apr 2022 19:59:53 -0400 Tony Thigpen wrote:
:>I have used ARs to get data from other VSE partitions (address spaces to
:>you z/OS guys). I am looking at a program that needs to 'snap shot' a
:>partition by copying a lot of data, then printing it.
:>I have never used "move to
17 matches
Mail list logo
