@LISTSERV.UGA.EDU
Subject: Re: Loading a VCON with as an immediate value
On Wed, Jun 19, 2019 at 3:11 PM Charles Mills wrote:
> Oh my gosh, @John, 4 bytes of virtual storage is NOTHING! Especially now
> that there is no effective 4K limit on easy addressability.
>
> OTOH, you have already sp
"There is no such thing as useless knowledge, however I admit there
are degrees of utility." - Samuel C. Woolvin
On 6/20/19, Tom Marchant
<00a69b48f3bb-dmarc-requ...@listserv.uga.edu> wrote:
> On Thu, 20 Jun 2019 06:46:45 -0500, John McKown wrote:
>
>>Time spent learning is never wasted. Even
On Thu, 20 Jun 2019 06:46:45 -0500, John McKown wrote:
>Time spent learning is never wasted. Even if the thing learned is not
>extremely important. At least, that is my philosophy.
I agree completely.
--
Tom Marchant
On Wed, Jun 19, 2019 at 5:24 PM Seymour J Metz wrote:
> IMHO it is cleaner and more readable to do
>
> L R15,=V(ENTRY)
>
> The other code is not only a Rube Goldberg, but it has a 50/50 chance of
> blowing up; V(ENTRY) has full word alignment.
>
{sigh} I guess I am loosing my ability to
On Wed, Jun 19, 2019 at 3:11 PM Charles Mills wrote:
> Oh my gosh, @John, 4 bytes of virtual storage is NOTHING! Especially now
> that there is no effective 4K limit on easy addressability.
>
> OTOH, you have already spent the most precious thing of all on it: your
> time.
>
Time spent learning
MBLER-LIST@LISTSERV.UGA.EDU
Subject: Loading a VCON with as an immediate value
To me, it seems silly to do the following, if I am only loading a VCON in a
single place.
L R15,=V(ENTRY)
When I can do:
LLILF R15,0
ORG *-4
DC V(ENTRY)
I am hoping that someone out there can tell me how I c
Notwithstanding the ASMA215W message (I have SUPR(215) in all my options
members), GOFF is not required on z/OS. I do not know about the other
platforms.
On a side note, I can't imagine any good reason for not using LIST(133).
Anyone got one?
sas
On Wed, Jun 19, 2019 at 5:43 PM Gord Tomlin
On 2019-06-19 16:06, Charles Mills wrote:
Believe it or not, the binder*will* resolve it. Requires the binder and
perhaps GOFF.
It does require GOFF, which in turn requires LIST(133).
--
Regards, Gord Tomlin
Action Software International
(a division of Mazda Computer Corporation)
Tel:
: Wednesday, June 19, 2019 10:31 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Loading a VCON with as an immediate value
To me, it seems silly to do the following, if I am only loading a VCON in a
single place.
L R15,=V(ENTRY)
When I can do:
LLILF R15,0
ORG *-4
DC V(ENTRY)
I am hoping
R-LIST@LISTSERV.UGA.EDU] On
Behalf Of Farley, Peter x23353
Sent: Wednesday, June 19, 2019 11:11 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Loading a VCON with as an immediate value
LARL is no help if it is truly an external (not in the current source) program
or entry point.
If it really external,
LARL does indeed work with "truly" external symbols. It does require an
explicit EXTRN declaration for the symbol.
One subtle advantage of this is that the binder finishes the relocation,
and program fetch doesn't have to adjust it (as it does A/V-cons).
sas
On Wed, Jun 19, 2019 at 2:11 PM
On Jun 19, 2019, at 11:31 AM, John McKown wrote:
>
> LLILH R15,ENTRY
> HLASM complains the ENTRY is either relocatable or unresolved. ..
>
I’ve encountered the complementary inconsistency:
LAR15,=D’3.14’works, but:
DCS(=D’3.14’)fails.
So it can resolve a
Ref: Your note of Wed, 19 Jun 2019 12:31:10 -0500
I assume that this is more like what was intended:
EXTRN ENTRY
IILF R15,ENTRY
We have already prototyped a HLASM change to allow any four-byte
immediate operand to be relocatable like this (in addition to
relative immediate
is a fullword (not halfword) instruction, to that would be the
right one to use.
Peter
-Original Message-
From: IBM Mainframe Assembler List On Behalf
Of John McKown
Sent: Wednesday, June 19, 2019 1:49 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Loading a VCON
On Wed, Jun 19, 2019 at 12:37 PM Steve Smith wrote:
> This was previously discussed; maybe on IBM-MAIN. I remember because I
> asked it myself. In any case, the bottom line is that the "preferred" way
> is to use LARL. This always works on z/OS as long as you use the binder.
>
Thanks. That's
This was previously discussed; maybe on IBM-MAIN. I remember because I
asked it myself. In any case, the bottom line is that the "preferred" way
is to use LARL. This always works on z/OS as long as you use the binder.
LLILH is a halfword immediate instruction; presumably a typo.
sas
On Wed,
macro
-Original Message-
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On
Behalf Of John McKown
Sent: Wednesday, June 19, 2019 1:31 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Loading a VCON with as an immediate value
To me, it seems silly to do
To me, it seems silly to do the following, if I am only loading a VCON in a
single place.
L R15,=V(ENTRY)
When I can do:
LLILF R15,0
ORG *-4
DC V(ENTRY)
I am hoping that someone out there can tell me how I can improve the
previous 3 instructions to be something like:
LLILH R15,ENTRY
18 matches
Mail list logo
