Wouldn't it be easier to make a global statement about R14 being altered
rather than that the top half (alone) is preserved when AMODE=24/31?
It would be easier, but it would be dangerous.
The case that is being protected against is this
- a program is using the high half of reg 14 for
Don,
This is a bit off-topic, but I figure that you are the guy that has maybe
thought about this with respect to your cool tool.
We do a lot of mixed Java / C++ / Assembler coding in Eclipse, and I've
thought that it would be very nice if there were an Assembler syntax editor
plugin for Eclipse
I'm wondering if the following is a good idea. I've been reading again. If I
have a routine which does the following:
...
CALL MYSUB,(PARMS,...),VL
L R13,4(,R13)
RETURN (14,12),T,RC=(15)
and I'm using standard calling conventions and save areas, is there any
I'm wondering if the following is a good idea. I've been reading again. If I
have a routine which does the following:
...
CALL MYSUB,(PARMS,...),VL
L R13,4(,R13)
RETURN (14,12),T,RC=(15)
and I'm using standard calling conventions and save areas, is
Bad idea if MYSUB abends. You've effectively lost the evidence that would have been in the back chain. Also, if you're in an LE environment, you have the danger that something your program is passing will be walked on by MYSUB, because you are now giving MYSUB your program's DSA to do with as he
One questions how there would be addressability to either the VCON or the
parms.
You're right of course. I wasn't bothering with the details. If it were me and
I wanted to do it this way, I'd get the parmlist address (R1) and branch
address (R15) set up inline and then restore R2-R14 and
There is interesting project on sourceforge related with z390:
http://sourceforge.net/projects/z390ide/
It's IDE with debugger for z390 emulator:-)
Unfortunately it has been written in C# so there is a problem on Linux
with Mono:/
PS. Youngins are interested in z/OS assembler development. I think
Most youngins would tolerate ISPF/PDF much better if the default profile
distribution had reasonable settings.
Whoever developed the CUA ISPF/PDF settings (command @ bottom, tab to
pull-down, etc.) certainly never used ISPF for better productivity.
I see great feature developments with each
On Jan 20, 2011, at 11:57, McKown, John wrote:
...
LR13,4(,R13)
LM R14,R12,12(R13)
CALL MYSUB,(PARAMS,...),LINKOP='15,15',LINKINST=BCR,VL
The above call replaces the normal BALR 14,15 with BCR 15,15 and so goes to
MYSUB, but removes the current program
