Re: Regarding RBINTCOD

2024-01-30 Thread Jim Mulder
. So maybe that will get into the next release after z/OS 3.1. Jim Mulder -Original Message- From: IBM Mainframe Discussion List On Behalf Of Jon Perryman Sent: Tuesday, January 30, 2024 3:06 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Regarding RBINTCOD On Tue, 30 Jan

Re: Regarding RBINTCOD

2024-01-30 Thread Jon Perryman
On Tue, 30 Jan 2024 20:05:50 +0200, Binyamin Dissen wrote: >:>Jon P did write what I meant. Answer: no, it just makes it a lot more likely >that the storage obtain for the SDWA will succeed. > >Sad. I believe abend recovery R0=12 is virtually unheard of when SDWA is above the line. Realize

Re: Regarding RBINTCOD

2024-01-30 Thread Binyamin Dissen
On Tue, 30 Jan 2024 13:17:15 + Peter Relson wrote: :> :>Are you implying that an ESTAE(X) routine with SDWALOC=31 is guaranteed an :>SDWA and there is no reason to check R0 for 12 and alternate code paths? :> :>Jon P did write what I meant. Answer: no, it just makes it a lot more likely

Re: Regarding RBINTCOD

2024-01-30 Thread Peter Relson
Are you implying that an ESTAE(X) routine with SDWALOC=31 is guaranteed an SDWA and there is no reason to check R0 for 12 and alternate code paths? Jon P did write what I meant. Answer: no, it just makes it a lot more likely that the storage obtain for the SDWA will succeed. Peter Relson z/OS

Re: Regarding RBINTCOD

2024-01-29 Thread Mike Schwab
REGION=(24,31,64) memory limits is available On Mon, Jan 29, 2024 at 12:27 PM Jon Perryman wrote: > On Mon, 29 Jan 2024 15:40:04 +0200, Binyamin Dissen < > bdis...@dissensoftware.com> wrote: > > >Are you implying that an ESTAE(X) routine with SSWALOC=31 is guaranteed an > >SDWA and there is no

Re: Regarding RBINTCOD

2024-01-29 Thread Mike Schwab
REGIONX=(24,31,53) memory limits is available. On Mon, Jan 29, 2024 at 12:27 PM Jon Perryman wrote: > On Mon, 29 Jan 2024 15:40:04 +0200, Binyamin Dissen < > bdis...@dissensoftware.com> wrote: > > >Are you implying that an ESTAE(X) routine with SSWALOC=31 is guaranteed an > >SDWA and there is

Re: Regarding RBINTCOD

2024-01-29 Thread Jon Perryman
On Mon, 29 Jan 2024 15:40:04 +0200, Binyamin Dissen wrote: >Are you implying that an ESTAE(X) routine with SSWALOC=31 is guaranteed an >SDWA and there is no reason to check R0 for 12 and alternate code paths? Obviously Peter is not making that guarantee but how many jobs run with REGION=0M or

Re: Regarding RBINTCOD

2024-01-29 Thread Binyamin Dissen
On Mon, 29 Jan 2024 12:57:53 + Peter Relson wrote: :>But none of this is appropriate to do within a recovery routine. That is why there is an SDWA. :>And if the system was unable to provide the ESTAE-type recovery routine with an SDWA, then too bad (and encourage the creator to use

Re: Regarding RBINTCOD

2024-01-29 Thread Joseph Reichman
Thanks > On Jan 29, 2024, at 7:58 AM, Peter Relson wrote: > >  > Is there any way to know whether this is an SVC or abend > > I mean I know for SVC the length must be 2 but that doesn't mean it cannot > be a abend > > > Abend is an SVC. So you could conceivably look at RBINTCOD for

Re: Regarding RBINTCOD

2024-01-29 Thread Peter Relson
Is there any way to know whether this is an SVC or abend I mean I know for SVC the length must be 2 but that doesn't mean it cannot be a abend Abend is an SVC. So you could conceivably look at RBINTCOD for x'000D'. A different question would be whether you can tell that the error was not