Re: Dump in 64 bit mode "Storage around GPR2 is invalid."

On Tue, 30 Aug 2016 08:49:12 -0700, Charles Mills wrote: >> You cannot call a 31-bit LE program (XPLINK or non-XPLINK) from XPLINK-64 >> unless you establish a new LE environment. > >FWIW in my (by definition limited) experience many (all of mine, for example) >assembler modules are essentially

Re: Dump in 64 bit mode "Storage around GPR2 is invalid."

three environments in addressing it. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tom Marchant Sent: Tuesday, August 30, 2016 8:31 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Dump in 64 bit mode "Storage around GPR2 is invalid.&

Re: Dump in 64 bit mode "Storage around GPR2 is invalid."

On Tue, 30 Aug 2016 06:33:14 -0700, Charles Mills wrote: >@Janet, I have no personal experience with this exact problem, but from what I >do know and what others have written here, if you wish to market a >C/C++-callable API-type product in object or assembler source code

Re: Dump in 64 bit mode "Storage around GPR2 is invalid."

o:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Janet Graff Sent: Monday, August 29, 2016 8:46 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Dump in 64 bit mode "Storage around GPR2 is invalid." Charles, It doesn't appear that the register conventions for XPLINK and non-XPLINK are compatible. I

Re: Dump in 64 bit mode "Storage around GPR2 is invalid."

In article <9374213960550353.wa.m42tomibmmainyahoo@listserv.ua.edu> you wrote: > On Mon, 29 Aug 2016 07:51:19 -0700, Charles Mills wrote: > >Hmmm. To me, that strategy seems appropriate for a report program ("this > >field is not relevant to this type of transaction so

Re: Dump in 64 bit mode "Storage around GPR2 is invalid."

] On Behalf Of Edward Gould Sent: Monday, August 29, 2016 12:39 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Dump in 64 bit mode "Storage around GPR2 is invalid." > On Aug 29, 2016, at 9:51 AM, Charles Mills <charl...@mcn.org> wrote: > > Hmmm. To me, that strategy seems

Re: Dump in 64 bit mode "Storage around GPR2 is invalid."

On Mon, 29 Aug 2016 07:51:19 -0700, Charles Mills wrote: >Hmmm. To me, that strategy seems appropriate for a report program ("this >field is not relevant to this type of transaction so print blanks or >asterisks") but not for a dump program. Isn't a dump -- consider the name --

Re: Dump in 64 bit mode "Storage around GPR2 is invalid."

> On Aug 29, 2016, at 9:51 AM, Charles Mills wrote: > > Hmmm. To me, that strategy seems appropriate for a report program ("this > field is not relevant to this type of transaction so print blanks or > asterisks") but not for a dump program. Isn't a dump -- consider the name --

Re: Dump in 64 bit mode "Storage around GPR2 is invalid."

eed to consider that. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Janet Graff Sent: Monday, August 29, 2016 8:46 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Dump in 64 bit mode "Storage around GPR2 is invalid." Charl

Re: Dump in 64 bit mode "Storage around GPR2 is invalid."

Charles, It doesn't appear that the register conventions for XPLINK and non-XPLINK are compatible. If one were marketing an Assembler API would you have to deliver two versions? One XPLINK and one non-XPLINK? Janet >@Janet, it occurred to me that you are talking about both C and "XGR." That

Re: Dump in 64 bit mode "Storage around GPR2 is invalid."

l Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Peter Relson Sent: Sunday, August 28, 2016 5:27 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Dump in 64 bit mode "Storage around GPR2 is invalid." The LE folks indicate that the message r

Re: Dump in 64 bit mode "Storage around GPR2 is invalid."

The LE folks indicate that the message really does not have much to do with the display of asterisks for that register. For performance reasons, the C/C++ compiler may choose not to save specific registers. If register contents were not saved, then the data for that register is residual

Re: Dump in 64 bit mode "Storage around GPR2 is invalid."

ERV.UA.EDU Subject: Re: Dump in 64 bit mode "Storage around GPR2 is invalid." On 25 August 2016 at 17:52, Janet Graff <004dc9e91b6d-dmarc-requ...@listserv.ua.edu> wrote: > I don't know if I'm XPLINK or standard linkage. The fact that your dump says DOWNSTACK DSA al

Re: Dump in 64 bit mode "Storage around GPR2 is invalid."

On 25 August 2016 at 17:52, Janet Graff <004dc9e91b6d-dmarc-requ...@listserv.ua.edu> wrote: > I don't know if I'm XPLINK or standard linkage. The fact that your dump says DOWNSTACK DSA almost certainly implies XPLINK. In the LE Debugging guide where I went to verify this, there is this

Re: Dump in 64 bit mode "Storage around GPR2 is invalid."

Thanks Charles! >Why are you using the AIX compiler reference? There is a z/OS compiler >reference manual, you know. Covers USS as well as legacy MVS. >http://www-01.ibm.com/support/docview.wss?uid=swg27036892 >Charles -- For

Re: Dump in 64 bit mode "Storage around GPR2 is invalid."

://www-01.ibm.com/support/docview.wss?uid=swg27036892 Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Janet Graff Sent: Thursday, August 25, 2016 5:52 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Dump in 64 bit mode "St

Re: Dump in 64 bit mode "Storage around GPR2 is invalid."

I don't know if I'm XPLINK or standard linkage. I'm using the following command to link xlc -o MY64.exe -q64 VSHVOLTG.o VSHVOLT.o VSHMSG.o MY64.o where would I look to see if XPLINK is turned on? How would I turn it off? I can't find XPLINK mentioned in the Compiler Reference V10.1 IBM XL C

Re: Dump in 64 bit mode "Storage around GPR2 is invalid."

arles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tony Harminc Sent: Thursday, August 25, 2016 2:16 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Dump in 64 bit mode "Storage around GPR2 is invalid." On 25 Aug

Re: Dump in 64 bit mode "Storage around GPR2 is invalid."

f Of Tony Harminc Sent: Thursday, August 25, 2016 1:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Dump in 64 bit mode "Storage around GPR2 is invalid." On 25 August 2016 at 12:47, Charles Mills <charl...@mcn.org> wrote: > I am generally very happy with the CEEDUMP and fi

Re: Dump in 64 bit mode "Storage around GPR2 is invalid."

On 25 August 2016 at 12:11, Janet Graff <004dc9e91b6d-dmarc-requ...@listserv.ua.edu> wrote: > I have XGR'd GPR2 and GPR3 before the abend and GPR5 definitely does not > contain a bunch Beees. I'm not sure quite what you mean by this. Your own code (that you know has run not long before the

Re: Dump in 64 bit mode "Storage around GPR2 is invalid."

On 25 August 2016 at 12:47, Charles Mills wrote: > I am generally very happy with the CEEDUMP and find it quite satisfactory. My experience with CEEDUMP is that it's all just fine until it isn't. It seems not to cope at all well with anything other than a simple failure within

Re: Dump in 64 bit mode "Storage around GPR2 is invalid."

arles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Janet Graff Sent: Thursday, August 25, 2016 12:12 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Dump in 64 bit mode "Storage around GPR2 is invalid." Here's an ex

Re: Dump in 64 bit mode "Storage around GPR2 is invalid."

Here's an example Parameters, Registers, and Variables for Active Routines: main (DSA address 0048082FEA20): DOWNSTACK DSA Saved Registers:

Dump in 64 bit mode "Storage around GPR2 is invalid."

When I get a CEEDUMP while running in 64 bit mode some of the register summary shows things like "GPR2. ". Why does this happen and how do I get the value of the register? Janet -- For IBM-MAIN subscribe