R14-R1 or all?
All that the documentation says are supposed to be unaltered, assuming (1) the
documentation exists and (2) it discusses altering of caller's registers.
Where documented?
I don't know. I don't do VSE. We were talking about VSE in this thread. The
only doc I have is for z/OS. I
On 1/17/2011 12:12 PM, Tony Thigpen wrote:
We in z/VSE are just now really getting 64bit stuff so it's time to ask
a few question of those with more experience with 64bit stuff.
I write code for a vendor that is called by customer programs. As such,
I really don't have much control over how they
On Mon, 17 Jan 2011 22:08:15 + Bill Fairchild wrote:
:>The z/OS system service GETMAIN does not preserve the high-order half of GP
registers, and there are probably others in z/OS like that. Check the doc on
each VSE system service that you use. When in doubt, save all 16 GP regs with
a
On 1/17/2011 2:44 PM, Don Poitras wrote:
AMODE 64 in VSE? I didn't think that was supported yet. If you're
talking about z/OS, then you need to worry about more than save areas.
You'd most likely be called from LE in which case you would be called
from an XPLINK program.
Oh, wait. AMODE64. Hmmm
On 1/17/2011 2:44 PM, Don Poitras wrote:
AMODE 64 in VSE? I didn't think that was supported yet. If you're
talking about z/OS, then you need to worry about more than save areas.
You'd most likely be called from LE in which case you would be called
from an XPLINK program.
Wait! LE does not imply
The z/OS system service GETMAIN does not preserve the high-order half of GP
registers, and there are probably others in z/OS like that. Check the doc on
each VSE system service that you use. When in doubt, save all 16 GP regs with
a STMG before you call a system service and reload all of them,
AMODE 64 in VSE? I didn't think that was supported yet. If you're
talking about z/OS, then you need to worry about more than save areas.
You'd most likely be called from LE in which case you would be called
from an XPLINK program. The stack is different and the method of
parameter passing is differ
Tony,
>> ...OCEXIT
you are preparing stuff from a vendor point - right?
Why do you not use the stuff ported from z/OS to VSE to support CICS/TS
and some other subsystem?
I am 100% sure that ESTAE and ESPIE can be used- they might even be
available without OS390 on the EXEC-card.
--
Martin
Pi_
>> BAKR/PR need operating support, and I don't know
whether that's available in VSE.
BAKR can be used - The op-sys does prepare a linkage-stack in
CR15.
It is crippled, if you compare it to the functionality that comes in
z/OS- but you get 96 levels and you get 24 for recovery in a
recover-stack.
BAKR/PR is available in z/VSE, but has the restriction that it can't be
used in an OCEXIT is in place. Since I am a low-level program, I can't
take the chance and use BAKR/PR.
Also, I failed to mention that my routines work for both batch and under
CICS.
Tony Thigpen
-Original Message -
On 1/17/2011 3:12 PM, Tony Thigpen wrote:
It looks like we have to not only handle AMODE 64, but also multiple
save area formats, AMODE 24, 31, and 64.
I am looking for any pointers from those that been down this road before.
Under zOS, I handle that by using BAKR to save everything, which
all
On Mon, 17 Jan 2011 14:18:54 -0600 "McKown, John"
wrote:
:>First question: Does your code use 64-bit instructions? If not, then why
would you need to worry about saving the high word of the caller's registers?
If you don't modify it, then it doesn't need to be saved, does it? Since the
save ar
> I am looking for any pointers from those that been down this road before.
> Tony Thigpen
Take a look at the z/OS MVS Assembler Services Guide, Chapter 2: it has a
lot of information about the kinds of areas you're exploring.
On 17 January 2011 15:18, McKown, John wrote:
> First question: Does your code use 64-bit instructions? If not, then why
> would you need to worry about saving the high word of the caller's registers?
> If you don't modify it, then it doesn't need to be saved, does it?
Just don't issue a GETMAI
First question: Does your code use 64-bit instructions? If not, then why would
you need to worry about saving the high word of the caller's registers? If you
don't modify it, then it doesn't need to be saved, does it? Since the save
areas passed in are compatibily extended, then it shouldn't mat
15 matches
Mail list logo
