Ref: Your note of Sun, 1 Dec 2019 21:51:39 -
> Hi there,
>
> APAR PH00902 has this neat get-out clause...
>
>
> The presence of a mnemonic in the above lists does not necessarily mean that
> the corresponding instruction is available to use. The list may include
> mnemonics reserved for pos
Yep, serious, at least as far as a moot & hypothetical discussion of
history goes. There are (hypothetically) other ways to handle those issues.
Having R15 as the incoming EPA has never been more than a convenience
anyway. The first example program in my first assembler class (long before
MVS/XA,
On Mon, Dec 2, 2019 at 8:31 AM Steve Smith wrote:
> Yep, serious, at least as far as a moot & hypothetical discussion of
> history goes. There are (hypothetically) other ways to handle those
> issues.
>
> Having R15 as the incoming EPA has never been more than a convenience
> anyway. The first e
Or
LR 12,15
USING entrypointname,12
On Mon, 2 Dec 2019 at 10:03, John McKown
wrote:
> On Mon, Dec 2, 2019 at 8:31 AM Steve Smith wrote:
>
> > Yep, serious, at least as far as a moot & hypothetical discussion of
> > history goes. There are (hypothetically) other ways to handle thos
On 12/2/2019 7:58 AM, Kerry Liles wrote:
Or
LR 12,15
USING entrypointname,12
And, of course, R15 is not even loaded with the entry point address for
programs given control in AMODE(64) :-\
These days, one is expected to issue LARL/USING to your program
constants. There is gener
Point taken! Thanks for clarification and I agree about base registers in
general.
On Dec 2, 2019 11:48 AM, "Ed Jaffe" wrote:
> On 12/2/2019 7:58 AM, Kerry Liles wrote:
>
>> Or
>>
>> LR 12,15
>> USING entrypointname,12
>>
>
>
> And, of course, R15 is not even loaded with the entry poi
I just had that discussion on a different forum with a guy who converted a
program to AMODE 64 and got surprised by that. "Why was my program loaded
at x'FF02', and why do I get a S0C4?"
However, that really only applies to system-controlled linkage. Normal
linkage can be, and often is used
ObNit If you keep your CSECT to a reasonable size then there is no need for a
base register to address the code. But if you have an obscenely large
monolithic program you will still need a base register, plus a large bottle of
aspirins.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
Even when using "baseless" code, I like to keep ONE register as the base/entry
point of the module (plus what ever is needed for constant/data areas beyond
the first 4K). Having a register thus set makes looking at a dump easier as
this base register (90% of the time R12) points to the current
On Mon, 2 Dec 2019 19:27:42 +, Keith Moe wrote:
>Even when using "baseless" code, I like to keep ONE register
>as the base/entry point of the module (plus what ever is
>needed for constant/data areas beyond the first 4K).
Locating your constants at the beginning of the program allows
you t
On 12/2/2019 12:02 PM, Tom Marchant wrote:
Locating your constants at the beginning of the program allows
you to do that without sacrificing a register.
Prezactly! That's what we do (using LOCTRs)...
--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90
On 12/2/2019 12:02 PM, Tom Marchant wrote:
Locating your constants at the beginning of the program allows
you to do that without sacrificing a register.
Prezactly! That's what we do (using LOCTRs)...
--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 9
On 2019-12-02, at 09:48:39, Ed Jaffe wrote:
>
> On 12/2/2019 7:58 AM, Kerry Liles wrote:
>> Or
>>
>> LR 12,15
>> USING entrypointname,12
>
> And, of course, R15 is not even loaded with the entry point address for
> programs given control in AMODE(64) :-\
>
That strikes me as thoughtl
On 2019-12-02, at 13:02:39, Tom Marchant wrote:
>
> On Mon, 2 Dec 2019 19:27:42 +, Keith Moe wrote:
>
>> Even when using "baseless" code, I like to keep ONE register
>> as the base/entry point of the module (plus what ever is
>> needed for constant/data areas beyond the first 4K).
>
> Loca
For AMODE64 there is an inconsistency between CALL and supervisor-assisted
linkage. The register setup for PGM=foo is the same as for any other ATTACHX of
foo.
OS/360 loaded R15. DOS/360 did not.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
___
On Monday, December 2, 2019, 02:56:13 PM PST, Paul Gilmartin
<0014e0e4a59b-dmarc-requ...@listserv.uga.edu> wrote:
> In the source? Branch around them or use LOCTR? What difference
> does it make as long as instructions plus data do not exceed 4Ki?
For programs that don't use a base r
Some folks eschew the use of literals (I like them!) but if you use literals
you end up with data following instructions physically. LOCTR is your friend
for making the literals end up at the beginning of the CSECT.
Charles
-Original Message-
From: IBM Mainframe Assembler List [mailto:AS
If you begin each module with an eye-catcher then your base register instantly
identifies the module.
Charles
-Original Message-
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On
Behalf Of Keith Moe
Sent: Monday, December 2, 2019 11:28 AM
To: ASSEMBLER-LIST
What does CSECT size have to do with base registers? If I have constants in
my CSECT and use "traditional" base/offset branches then I need a base
register, no matter how small the CSECT. If I have neither of the above I do
not need a base register, no matter how large the CSECT.
No argument with
19 matches
Mail list logo
