Re: 64 bit question
Robin, Man..that pretty small...probably when they came out it it was huge Scott ford www.identityforge.com from my IPAD 'Infinite wisdom through infinite means' On Jun 17, 2013, at 7:39 PM, robin wrote: > From: "Scott Ford" > Sent: Tuesday, June 18, 2013 2:47 AM > > >> God, I remember half word instructions because I only had 16k to work in >> ..probably the 1401 guys >> had less > > Many early machines had less. > > Pilot ACE and DEUCE had 384 words -- > and of those, only 256 words could be used for instructions.
Re: 64 bit question
From: "Scott Ford" Sent: Tuesday, June 18, 2013 2:47 AM God, I remember half word instructions because I only had 16k to work in ..probably the 1401 guys had less Many early machines had less. Pilot ACE and DEUCE had 384 words -- and of those, only 256 words could be used for instructions.
Re: 64 bit question
God, I remember half word instructions because I only had 16k to work in ..probably the 1401 guys had less Scott ford www.identityforge.com from my IPAD 'Infinite wisdom through infinite means' On Jun 17, 2013, at 11:04 AM, Martin Truebner wrote: > ZMan > > it took me some time to find an answer without "when I " > > here is one: > >>> I remember when we only had two bits. > > Still is- the condition-code in z-Series > > -- > Martin > > Pi_cap_CPU - all you ever need around MWLC/SCRT/CMT in z/VSE > more at http://www.picapcpu.de
Re: 64 bit question
ZMan it took me some time to find an answer without "when I " here is one: >> I remember when we only had two bits. Still is- the condition-code in z-Series -- Martin Pi_cap_CPU - all you ever need around MWLC/SCRT/CMT in z/VSE more at http://www.picapcpu.de
Re: 64 bit question
64 bits? I remember when we only had two bits.. (Howzat for nostalgica?) On Mon, Jun 17, 2013 at 10:32 AM, Martin Truebner wrote: > JR - we are far off the original point- and there is no point for being > sorry > > BTW: how are we doing? A long thread and it has not yet drifted into > nostalgica. > > -- > Martin > > Pi_cap_CPU - all you ever need around MWLC/SCRT/CMT in z/VSE > more at http://www.picapcpu.de > -- zMan -- "I've got a mainframe and I'm not afraid to use it"
Re: 64 bit question
JR - we are far off the original point- and there is no point for being sorry BTW: how are we doing? A long thread and it has not yet drifted into nostalgica. -- Martin Pi_cap_CPU - all you ever need around MWLC/SCRT/CMT in z/VSE more at http://www.picapcpu.de
Re: 64 bit question
My apologies to all concerned (especially Martin Truebner and Scott Ford) if I missed the original point of this thread! I'm very sorry. = > Date: Mon, 17 Jun 2013 09:48:49 -0400 > From: scott_j_f...@yahoo.com > Subject: Re: 64 bit question > To: ASSEMBLER-LIST@LISTSERV.UGA.EDU > > JR, > > I appreciate your input ..and of course error handling is second nature..the > question was really concerning how it worked . Peter and Lizette were kind > enough to explain how it worked ... > > Scott ford > www.identityforge.com > from my IPAD > > 'Infinite wisdom through infinite means' > > > On Jun 17, 2013, at 8:34 AM, J R wrote: > > > While Peter Relson's posts are always appreciated, was this not somewhat > > stating the obvious? > > > > I don't know what the percentage may be but a substantial amount of (esp. > > commercial) software development is devoted to exception handling, error > > recovery, etc. > > > > Also, we keep seeing comments like, "I don't like to assume ..." There is > > nothing wrong with making assumptions as long as you assume *and* verify. > > In this case, > > > > GET64 STORAGE /* ASSUME 64-BIT */ > > LTR R15,R15 /* DID IT WORK? */ > > BZ .../* YES, CONTINUE */ > > GET31 STORAGE /* FALL BACK TO 31-BIT */ > > > > I would expect this to be second nature to just about everybody on this > > list. > > > > = > > > > > > > >> Date: Mon, 17 Jun 2013 00:29:13 -0400 > >> From: scott_j_f...@yahoo.com > >> Subject: Re: 64 bit question > >> To: ASSEMBLER-LIST@LISTSERV.UGA.EDU > >> > >> Thanks Peter and Lizette ...the clarification is excellent much appreciated > >> > >> Scott ford > >> www.identityforge.com > >> from my IPAD > >> > >> 'Infinite wisdom through infinite means' > >> > >> > >> On Jun 16, 2013, at 8:17 PM, Lizette Koehler > >> wrote: > >> > >>> Thanks for the clarification > >>> > >>> Lizette > >>> > >>> -Original Message- > >>> From: IBM Mainframe Assembler List > >>> [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] > >>> On Behalf Of Peter Relson > >>> Sent: Sunday, June 16, 2013 3:39 PM > >>> To: ASSEMBLER-LIST@LISTSERV.UGA.EDU > >>> Subject: > >>> > >>>> System will always be able to answer a request for 64 bit - If you make > >>> it > >>>> conditional it will tell you that it resolved from below the bar (if > >>>> the area above the bar is exhausted). Scott, what would stop you using > >>>> z-arch-instructions to handle it? > >>> > >>> That is not the way 64-bit storage works in z/OS. You can request. If you > >>> request conditionally, you get a return code back if not available (such > >>> as > >>> by 'too small MEMLIMIT'). > >>> It is then up to you to request below-2G storage by the normal means. If > >>> you > >>> request unconditionally, you abend if not available. > >>> > >>>> My issue is more trying to allocate a 64 bit storage and it failing > >>> Just about any request for storage can "fail". It is up to you to decide > >>> what to do when it does, such as 'try something else'. > >>> > >>> Peter Relson > >>> z/OS Core Technology Design
Re: 64 bit question
JR, I appreciate your input ..and of course error handling is second nature..the question was really concerning how it worked . Peter and Lizette were kind enough to explain how it worked ... Scott ford www.identityforge.com from my IPAD 'Infinite wisdom through infinite means' On Jun 17, 2013, at 8:34 AM, J R wrote: > While Peter Relson's posts are always appreciated, was this not somewhat > stating the obvious? > > I don't know what the percentage may be but a substantial amount of (esp. > commercial) software development is devoted to exception handling, error > recovery, etc. > > Also, we keep seeing comments like, "I don't like to assume ..." There is > nothing wrong with making assumptions as long as you assume *and* verify. In > this case, > > GET64 STORAGE /* ASSUME 64-BIT */ > LTR R15,R15 /* DID IT WORK? */ > BZ .../* YES, CONTINUE */ > GET31 STORAGE /* FALL BACK TO 31-BIT */ > > I would expect this to be second nature to just about everybody on this list. > > = > > > >> Date: Mon, 17 Jun 2013 00:29:13 -0400 >> From: scott_j_f...@yahoo.com >> Subject: Re: 64 bit question >> To: ASSEMBLER-LIST@LISTSERV.UGA.EDU >> >> Thanks Peter and Lizette ...the clarification is excellent much appreciated >> >> Scott ford >> www.identityforge.com >> from my IPAD >> >> 'Infinite wisdom through infinite means' >> >> >> On Jun 16, 2013, at 8:17 PM, Lizette Koehler wrote: >> >>> Thanks for the clarification >>> >>> Lizette >>> >>> -Original Message- >>> From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] >>> On Behalf Of Peter Relson >>> Sent: Sunday, June 16, 2013 3:39 PM >>> To: ASSEMBLER-LIST@LISTSERV.UGA.EDU >>> Subject: >>> >>>> System will always be able to answer a request for 64 bit - If you make >>> it >>>> conditional it will tell you that it resolved from below the bar (if >>>> the area above the bar is exhausted). Scott, what would stop you using >>>> z-arch-instructions to handle it? >>> >>> That is not the way 64-bit storage works in z/OS. You can request. If you >>> request conditionally, you get a return code back if not available (such as >>> by 'too small MEMLIMIT'). >>> It is then up to you to request below-2G storage by the normal means. If you >>> request unconditionally, you abend if not available. >>> >>>> My issue is more trying to allocate a 64 bit storage and it failing >>> Just about any request for storage can "fail". It is up to you to decide >>> what to do when it does, such as 'try something else'. >>> >>> Peter Relson >>> z/OS Core Technology Design
Re: 64 bit question
J R, >> While Peter Relson's posts are always appreciated, was this not >> somewhat stating the obvious? I was the original cause by stating something wrong about VSE (Peter: and it is exactly the way you described it (for z/OS) in z/VSE as well). Since we are comparing notes already- the described behavior (not getting what you ask for and a return-code tells what was not satisfied) is the case for operand PAGEFRAMESIZE=MAX - if the system can't cope it gives a return-code (but still satisfies the request for storage). -- Martin Pi_cap_CPU - all you ever need around MWLC/SCRT/CMT in z/VSE more at http://www.picapcpu.de
Re: 64 bit question
While Peter Relson's posts are always appreciated, was this not somewhat stating the obvious? I don't know what the percentage may be but a substantial amount of (esp. commercial) software development is devoted to exception handling, error recovery, etc. Also, we keep seeing comments like, "I don't like to assume ..." There is nothing wrong with making assumptions as long as you assume *and* verify. In this case, GET64 STORAGE /* ASSUME 64-BIT */ LTR R15,R15 /* DID IT WORK? */ BZ .../* YES, CONTINUE */ GET31 STORAGE /* FALL BACK TO 31-BIT */ I would expect this to be second nature to just about everybody on this list. = > Date: Mon, 17 Jun 2013 00:29:13 -0400 > From: scott_j_f...@yahoo.com > Subject: Re: 64 bit question > To: ASSEMBLER-LIST@LISTSERV.UGA.EDU > > Thanks Peter and Lizette ...the clarification is excellent much appreciated > > Scott ford > www.identityforge.com > from my IPAD > > 'Infinite wisdom through infinite means' > > > On Jun 16, 2013, at 8:17 PM, Lizette Koehler wrote: > > > Thanks for the clarification > > > > Lizette > > > > -Original Message- > > From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] > > On Behalf Of Peter Relson > > Sent: Sunday, June 16, 2013 3:39 PM > > To: ASSEMBLER-LIST@LISTSERV.UGA.EDU > > Subject: > > > >> System will always be able to answer a request for 64 bit - If you make > > it > >> conditional it will tell you that it resolved from below the bar (if > >> the area above the bar is exhausted). Scott, what would stop you using > >> z-arch-instructions to handle it? > > > > That is not the way 64-bit storage works in z/OS. You can request. If you > > request conditionally, you get a return code back if not available (such as > > by 'too small MEMLIMIT'). > > It is then up to you to request below-2G storage by the normal means. If you > > request unconditionally, you abend if not available. > > > >> My issue is more trying to allocate a 64 bit storage and it failing > > Just about any request for storage can "fail". It is up to you to decide > > what to do when it does, such as 'try something else'. > > > > Peter Relson > > z/OS Core Technology Design
Re: 64 bit question
Thanks Peter and Lizette ...the clarification is excellent much appreciated Scott ford www.identityforge.com from my IPAD 'Infinite wisdom through infinite means' On Jun 16, 2013, at 8:17 PM, Lizette Koehler wrote: > Thanks for the clarification > > Lizette > > -Original Message- > From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] > On Behalf Of Peter Relson > Sent: Sunday, June 16, 2013 3:39 PM > To: ASSEMBLER-LIST@LISTSERV.UGA.EDU > Subject: > >> System will always be able to answer a request for 64 bit - If you make > it >> conditional it will tell you that it resolved from below the bar (if >> the area above the bar is exhausted). Scott, what would stop you using >> z-arch-instructions to handle it? > > That is not the way 64-bit storage works in z/OS. You can request. If you > request conditionally, you get a return code back if not available (such as > by 'too small MEMLIMIT'). > It is then up to you to request below-2G storage by the normal means. If you > request unconditionally, you abend if not available. > >> My issue is more trying to allocate a 64 bit storage and it failing > Just about any request for storage can "fail". It is up to you to decide > what to do when it does, such as 'try something else'. > > Peter Relson > z/OS Core Technology Design
Re: 64 bit question
Thanks for the clarification Lizette -Original Message- From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On Behalf Of Peter Relson Sent: Sunday, June 16, 2013 3:39 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: >System will always be able to answer a request for 64 bit - If you make it >conditional it will tell you that it resolved from below the bar (if >the area above the bar is exhausted). Scott, what would stop you using >z-arch-instructions to handle it? That is not the way 64-bit storage works in z/OS. You can request. If you request conditionally, you get a return code back if not available (such as by 'too small MEMLIMIT'). It is then up to you to request below-2G storage by the normal means. If you request unconditionally, you abend if not available. >My issue is more trying to allocate a 64 bit storage and it failing Just about any request for storage can "fail". It is up to you to decide what to do when it does, such as 'try something else'. Peter Relson z/OS Core Technology Design
Re: 64 bit question
Apologies for the post without subject. I hope anyone adding to it or responding to it supplies one. The intended subject was "Re: 64 bit question". Peter Relson z/OS Core Technology Design
Re: 64 bit question
Peter, This is my first adventure into the 64bit world. So I am sure you can understand my caution with customers z/os systems. I wasn't aware that the feature couldn't be turned off. My issue is more trying to allocate a 64 bit storage and it failing ...I appreciate everyone's help. Scott ford www.identityforge.com from my IPAD 'Infinite wisdom through infinite means' On Jun 14, 2013, at 7:24 AM, Peter Relson wrote: > As Tom Marchant pointed out, all supported z/OS releases (and those from > z/OS 1.6 onward) require z/Architecture and support 64-bit virtual. > Customers do not "enable" 64-bit functionality on such releases; it cannot > be (fully) disabled > > Peter Relson > z/OS Core Technology Design
Re: 64 bit question
John McKown wrote: >Why not just try to get memory above the line, using IARST64 REQUEST=GET, >and check the return code? What if the machine is out of memory above the line? (JOKE) >Hum, I really find bit 7 amusing. What does STFLE set that bit to when >STFLE is not available. No, wait, what? Right, we need the STFU instruction for that... ...phsiii
Re: 64 bit question
Scott mentions customers and 24-bit and yestedrday Paul Gilmartin mention 'during the transition from 370 to XA' and... I'm interested about what assembler code 'out there' (zOS,zVM or zVSE) still contained (probably as dual code path?) XA or 370 or 390 only code path/instructions - and why. I understand that not all would like to discuss that information on the forum, but if you do wish to share information/stories off list then please email me at smo...@uk.ibm.com Thanks Sharuff Sharuff Morsa - IBM Hursley Labs .. and a quick plug for... http://www.ibm.com/support/docview.wss?uid=swg21577670 - for HLASM requirements http://www.ibm.com/support/docview.wss?uid=swg21595123 - for HLASM readers comments > >Date:Thu, 13 Jun 2013 13:56:12 -0400 >.From: Scott Ford >Subject: Re: 64 bit question > >John, > >As a vendor I won't assume ..I have customers who still think we should write our code in 24 bit mode. So don't get me >started. I know your right from my experience , but I would rather be safe than sorry> > >Scott ford >www.identityforge.com >from my IPAD > Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Re: 64 bit question
As Tom Marchant pointed out, all supported z/OS releases (and those from z/OS 1.6 onward) require z/Architecture and support 64-bit virtual. Customers do not "enable" 64-bit functionality on such releases; it cannot be (fully) disabled Peter Relson z/OS Core Technology Design
Re: 64 bit question
On Thu, 13 Jun 2013 13:56:12 -0400 Scott Ford wrote: :>As a vendor I won't assume ..I have customers who still think we should write our code in 24 bit mode. So don't get me started. I know your right from my experience , but I would rather be safe than sorry Ah, the age-old ivory tower vs. real world debate. You mean your customers really won't accept your demand to buy new hardware??? ;) :>On Jun 13, 2013, at 1:46 PM, John Gilmore wrote: :> :>> Are we not talking about a rather small, even exiguous, population of :>> mainframes under z/OS that do not make AMODE(64) virtual storage :>> available? :>> :>> Its unmediated, direct use by applications may still be exiguous too, :>> but its mediated use by DB2 and the like is now substantial. :>> :>> John Gilmore, Ashland, MA 01721 - USA -- Binyamin Dissen http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies.
Re: 64 bit question
Yeah, I don't want to be using something I assume someone has enabled. Most customers do probably..but Murphy's law is always there Scott ford www.identityforge.com from my IPAD 'Infinite wisdom through infinite means' On Jun 13, 2013, at 12:53 PM, Larry lawler wrote: > CVTV64 EQU X'10' 64-bit virtual services are present. > *You should ensure FLCARCH (in IHAPSA) is > *non-zero before using > > > > > > -Original Message- > From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On > Behalf Of Scott Ford > Sent: Thursday, June 13, 2013 9:46 AM > To: ASSEMBLER-LIST@LISTSERV.UGA.EDU > Subject: 64 bit question > > All, > > After reading through the Extended Addressability Guide/ref I have a > question.. > How do I tell if a machine will support 64 bit storage above the "bar" ? I > mean > like a Assembler macro query ..I want to use 64bit storage but I don't know to > tell programmatically what the allocation is for the system. > > Regards, > > Scott ford > www.identityforge.com > from my IPAD > > 'Infinite wisdom through infinite means'
Re: 64 bit question
CVTV64 EQU X'10' 64-bit virtual services are present. *You should ensure FLCARCH (in IHAPSA) is *non-zero before using -Original Message- From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On Behalf Of Scott Ford Sent: Thursday, June 13, 2013 9:46 AM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: 64 bit question All, After reading through the Extended Addressability Guide/ref I have a question.. How do I tell if a machine will support 64 bit storage above the "bar" ? I mean like a Assembler macro query ..I want to use 64bit storage but I don't know to tell programmatically what the allocation is for the system. Regards, Scott ford www.identityforge.com from my IPAD 'Infinite wisdom through infinite means'
Re: 64 bit question
On Thu, 13 Jun 2013 17:14:25 +, Randy Schafer wrote: >STFLE FUNCTION That's no good. IIRC, STFLE became available on the z9. You can check those bits in the PSA. MVS issues STFL or STFLE to save the information at location 200 (X'C8') If you're running on a z9, the hardware supports 64-bit addressing. For that matter, if you are running any release of z/OS higher than 1.5, you have to be on a z/architecture processor. -- Tom Marchant
Re: 64 bit question
Scott, I find your comment on 24 bit interesting as I had a new client we were in talks with who wanted us to code in C because assembler programmers are few! So I called one of our current clients to see if they have the C run modules etc. and he said "Where do I look?" and I said "Don't bother, I've heard enough already!". So, you're right. Let's not get started! Duffy -Original Message- From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On Behalf Of Scott Ford Sent: Thursday, June 13, 2013 10:56 AM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: 64 bit question John, As a vendor I won't assume ..I have customers who still think we should write our code in 24 bit mode. So don't get me started. I know your right from my experience , but I would rather be safe than sorry Scott ford www.identityforge.com from my IPAD 'Infinite wisdom through infinite means' On Jun 13, 2013, at 1:46 PM, John Gilmore wrote: > Are we not talking about a rather small, even exiguous, population of > mainframes under z/OS that do not make AMODE(64) virtual storage > available? > > Its unmediated, direct use by applications may still be exiguous too, > but its mediated use by DB2 and the like is now substantial. > > John Gilmore, Ashland, MA 01721 - USA
Re: 64 bit question
John, As a vendor I won't assume ..I have customers who still think we should write our code in 24 bit mode. So don't get me started. I know your right from my experience , but I would rather be safe than sorry Scott ford www.identityforge.com from my IPAD 'Infinite wisdom through infinite means' On Jun 13, 2013, at 1:46 PM, John Gilmore wrote: > Are we not talking about a rather small, even exiguous, population of > mainframes under z/OS that do not make AMODE(64) virtual storage > available? > > Its unmediated, direct use by applications may still be exiguous too, > but its mediated use by DB2 and the like is now substantial. > > John Gilmore, Ashland, MA 01721 - USA
Re: 64 bit question
On 13 June 2013 13:19, John McKown wrote: > Hum, I really find bit 7 amusing. What does STFLE set that bit to when > STFLE is not available. No, wait, what? If you didn't get this message, please let us know immediately. Tony H.
Re: 64 bit question
Are we not talking about a rather small, even exiguous, population of mainframes under z/OS that do not make AMODE(64) virtual storage available? Its unmediated, direct use by applications may still be exiguous too, but its mediated use by DB2 and the like is now substantial. John Gilmore, Ashland, MA 01721 - USA
Re: 64 bit question
Guys, Your great I will dig through the data areas ...much much appreciated Scott ford www.identityforge.com from my IPAD 'Infinite wisdom through infinite means' On Jun 13, 2013, at 1:14 PM, Randy Schafer wrote: > You could also try > > STFLE FUNCTION > > Then check the first word: > > - Bits (0-7) > > 0 - N3 INSTRUCTIONS AVAILABLE > 1 - Z/ARCH MODE INSTALLED > 2 - Z/ARCH MODE ACTIVE > 3 - DAT ENHANCEMENT INSTALLED > 4 - IDTE DOES CLEARING (ASCE) > 6 - ASN AND LX REUSE INSTALLED > 7 - STFLE AVAILABLE > > > -Original Message- > From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] > On Behalf Of John McKown > Sent: Thursday, June 13, 2013 12:08 PM > To: ASSEMBLER-LIST@LISTSERV.UGA.EDU > Subject: Re: 64 bit question > > Why not just try to get memory above the line, using IARST64 REQUEST=GET, and > check the return code? > > http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2A9B0/4.1 > > Or, you might check the CVTV64 bit in the CVTOSLV2 flag field of the CVT (CVT > macro), after checking that FLCARCH is non-zero in the PSA (IHAPSA macro). > > USING PSA,0 > CLI FLCARCH,0 > BZ NO64BIT > L 1,FLCCVT > DROP 0 > USING CVT,1 > TM CVTOSLV2,CVTV64 > BZ NO64BIT > ... > IHAPSA DSECT=YES,LIST=YES > CVT DSECT=YES,LIST=YES > > > On Thu, Jun 13, 2013 at 11:45 AM, Scott Ford wrote: > >> All, >> >> After reading through the Extended Addressability Guide/ref I have a >> question.. >> How do I tell if a machine will support 64 bit storage above the "bar" >> ? I mean like a Assembler macro query ..I want to use 64bit storage >> but I don't know to tell programmatically what the allocation is for the >> system. >> >> Regards, >> >> Scott ford >> www.identityforge.com >> from my IPAD >> >> 'Infinite wisdom through infinite means' > > > > -- > This is a test of the Emergency Broadcast System. If this had been an actual > emergency, do you really think we'd stick around to tell you? > > Maranatha! <>< > John McKown
Re: 64 bit question
On 6/13/2013 10:19 AM, John McKown wrote: Hum, I really find bit 7 amusing. What does STFLE set that bit to when STFLE is not available. No, wait, what? That bit is set by STFL. -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/
Re: 64 bit question
On 6/13/2013 9:45 AM, Scott Ford wrote: After reading through the Extended Addressability Guide/ref I have a question.. How do I tell if a machine will support 64 bit storage above the "bar" ? I mean like a Assembler macro query ..I want to use 64bit storage but I don't know to tell programmatically what the allocation is for the system. TMCVTOSLV3,CVTV64 64-bit virtual supported? JZNo64Bit Branch if not -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/
Re: 64 bit question
Not sure I have a machine I can try that on. Looks like a trap. -Original Message- From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On Behalf Of John McKown Sent: Thursday, June 13, 2013 12:19 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: 64 bit question Hum, I really find bit 7 amusing. What does STFLE set that bit to when STFLE is not available. No, wait, what? On Thu, Jun 13, 2013 at 12:14 PM, Randy Schafer < randy.schafer.a...@statefarm.com> wrote: > You could also try > > STFLE FUNCTION > > Then check the first word: > > - Bits (0-7) > > 0 - N3 INSTRUCTIONS AVAILABLE > 1 - Z/ARCH MODE INSTALLED > 2 - Z/ARCH MODE ACTIVE > 3 - DAT ENHANCEMENT INSTALLED > 4 - IDTE DOES CLEARING (ASCE) > 6 - ASN AND LX REUSE INSTALLED > 7 - STFLE AVAILABLE > > > -Original Message- > From: IBM Mainframe Assembler List > [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] > On Behalf Of John McKown > Sent: Thursday, June 13, 2013 12:08 PM > To: ASSEMBLER-LIST@LISTSERV.UGA.EDU > Subject: Re: 64 bit question > > Why not just try to get memory above the line, using IARST64 > REQUEST=GET, and check the return code? > > http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2A9B0/4. > 1 > > Or, you might check the CVTV64 bit in the CVTOSLV2 flag field of the > CVT (CVT macro), after checking that FLCARCH is non-zero in the PSA > (IHAPSA macro). > > USING PSA,0 > CLI FLCARCH,0 > BZ NO64BIT > L 1,FLCCVT > DROP 0 > USING CVT,1 > TM CVTOSLV2,CVTV64 > BZ NO64BIT > ... > IHAPSA DSECT=YES,LIST=YES > CVT DSECT=YES,LIST=YES > > > On Thu, Jun 13, 2013 at 11:45 AM, Scott Ford > wrote: > > > All, > > > > After reading through the Extended Addressability Guide/ref I have a > > question.. > > How do I tell if a machine will support 64 bit storage above the "bar" > > ? I mean like a Assembler macro query ..I want to use 64bit storage > > but I don't know to tell programmatically what the allocation is for > > the > system. > > > > Regards, > > > > Scott ford > > www.identityforge.com > > from my IPAD > > > > 'Infinite wisdom through infinite means' > > > > > > -- > This is a test of the Emergency Broadcast System. If this had been an > actual emergency, do you really think we'd stick around to tell you? > > Maranatha! <>< > John McKown > -- This is a test of the Emergency Broadcast System. If this had been an actual emergency, do you really think we'd stick around to tell you? Maranatha! <>< John McKown
Re: 64 bit question
Hum, I really find bit 7 amusing. What does STFLE set that bit to when STFLE is not available. No, wait, what? On Thu, Jun 13, 2013 at 12:14 PM, Randy Schafer < randy.schafer.a...@statefarm.com> wrote: > You could also try > > STFLE FUNCTION > > Then check the first word: > > - Bits (0-7) > > 0 - N3 INSTRUCTIONS AVAILABLE > 1 - Z/ARCH MODE INSTALLED > 2 - Z/ARCH MODE ACTIVE > 3 - DAT ENHANCEMENT INSTALLED > 4 - IDTE DOES CLEARING (ASCE) > 6 - ASN AND LX REUSE INSTALLED > 7 - STFLE AVAILABLE > > > -Original Message- > From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] > On Behalf Of John McKown > Sent: Thursday, June 13, 2013 12:08 PM > To: ASSEMBLER-LIST@LISTSERV.UGA.EDU > Subject: Re: 64 bit question > > Why not just try to get memory above the line, using IARST64 REQUEST=GET, > and check the return code? > > http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2A9B0/4.1 > > Or, you might check the CVTV64 bit in the CVTOSLV2 flag field of the CVT > (CVT macro), after checking that FLCARCH is non-zero in the PSA (IHAPSA > macro). > > USING PSA,0 > CLI FLCARCH,0 > BZ NO64BIT > L 1,FLCCVT > DROP 0 > USING CVT,1 > TM CVTOSLV2,CVTV64 > BZ NO64BIT > ... > IHAPSA DSECT=YES,LIST=YES > CVT DSECT=YES,LIST=YES > > > On Thu, Jun 13, 2013 at 11:45 AM, Scott Ford > wrote: > > > All, > > > > After reading through the Extended Addressability Guide/ref I have a > > question.. > > How do I tell if a machine will support 64 bit storage above the "bar" > > ? I mean like a Assembler macro query ..I want to use 64bit storage > > but I don't know to tell programmatically what the allocation is for the > system. > > > > Regards, > > > > Scott ford > > www.identityforge.com > > from my IPAD > > > > 'Infinite wisdom through infinite means' > > > > > > -- > This is a test of the Emergency Broadcast System. If this had been an > actual emergency, do you really think we'd stick around to tell you? > > Maranatha! <>< > John McKown > -- This is a test of the Emergency Broadcast System. If this had been an actual emergency, do you really think we'd stick around to tell you? Maranatha! <>< John McKown
Re: 64 bit question
You could also try STFLE FUNCTION Then check the first word: - Bits (0-7) 0 - N3 INSTRUCTIONS AVAILABLE 1 - Z/ARCH MODE INSTALLED 2 - Z/ARCH MODE ACTIVE 3 - DAT ENHANCEMENT INSTALLED 4 - IDTE DOES CLEARING (ASCE) 6 - ASN AND LX REUSE INSTALLED 7 - STFLE AVAILABLE -Original Message- From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On Behalf Of John McKown Sent: Thursday, June 13, 2013 12:08 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: 64 bit question Why not just try to get memory above the line, using IARST64 REQUEST=GET, and check the return code? http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2A9B0/4.1 Or, you might check the CVTV64 bit in the CVTOSLV2 flag field of the CVT (CVT macro), after checking that FLCARCH is non-zero in the PSA (IHAPSA macro). USING PSA,0 CLI FLCARCH,0 BZ NO64BIT L 1,FLCCVT DROP 0 USING CVT,1 TM CVTOSLV2,CVTV64 BZ NO64BIT ... IHAPSA DSECT=YES,LIST=YES CVT DSECT=YES,LIST=YES On Thu, Jun 13, 2013 at 11:45 AM, Scott Ford wrote: > All, > > After reading through the Extended Addressability Guide/ref I have a > question.. > How do I tell if a machine will support 64 bit storage above the "bar" > ? I mean like a Assembler macro query ..I want to use 64bit storage > but I don't know to tell programmatically what the allocation is for the > system. > > Regards, > > Scott ford > www.identityforge.com > from my IPAD > > 'Infinite wisdom through infinite means' > -- This is a test of the Emergency Broadcast System. If this had been an actual emergency, do you really think we'd stick around to tell you? Maranatha! <>< John McKown
Re: 64 bit question
Why not just try to get memory above the line, using IARST64 REQUEST=GET, and check the return code? http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2A9B0/4.1 Or, you might check the CVTV64 bit in the CVTOSLV2 flag field of the CVT (CVT macro), after checking that FLCARCH is non-zero in the PSA (IHAPSA macro). USING PSA,0 CLI FLCARCH,0 BZ NO64BIT L 1,FLCCVT DROP 0 USING CVT,1 TM CVTOSLV2,CVTV64 BZ NO64BIT ... IHAPSA DSECT=YES,LIST=YES CVT DSECT=YES,LIST=YES On Thu, Jun 13, 2013 at 11:45 AM, Scott Ford wrote: > All, > > After reading through the Extended Addressability Guide/ref I have a > question.. > How do I tell if a machine will support 64 bit storage above the "bar" ? I > mean like a Assembler macro query ..I want to use 64bit storage but I don't > know to tell programmatically what the allocation is for the system. > > Regards, > > Scott ford > www.identityforge.com > from my IPAD > > 'Infinite wisdom through infinite means' > -- This is a test of the Emergency Broadcast System. If this had been an actual emergency, do you really think we'd stick around to tell you? Maranatha! <>< John McKown
