Reason code 00 is a storage key mismatch.
Joe
On Wed, Aug 24, 2022 at 3:19 PM Brian Westerman <
brian_wester...@syzygyinc.com> wrote:
> The "normal" reason this happens (at least to me) is because the task
> isn't authorized to issue the detach. It has nothing to do with whether or
> not the ta
The "normal" reason this happens (at least to me) is because the task isn't
authorized to issue the detach. It has nothing to do with whether or not the
task was able to start, because the task may not have needed to be authorized
when it started, but needs it to perform a specific function and
The application "got abended" because something running under that task
mis-issued DETACH.
The doc for completion code 23E reason 0 seems pretty clear.
The entry requirement for DETACH is:
R1 contains the address of a word which contains the address of the TCB of the
task to be detached.
If you
If was an APF issue then the started wouldn't have started at all
This online application has 7 region with X1 until X9
only X2 and X2 are having this issue
On Tue, Aug 23, 2022, 9:03 AM Brian Westerman
wrote:
> Since this is a DR test, I would be willing to bet that someone made an
> error in
Since this is a DR test, I would be willing to bet that someone made an error
in the PROGxx member and you have at lest one and probably several datasets
that are not authorized correctly. It could be that someone forgot a comma or
they specified the wrong volume (i.e it's on Z24RES on the prim
pering, amendment or viruses or any consequence thereof.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Seymour J Metz
Sent: Monday, August 22, 2022 11:47 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: S23E abend
ent: Monday, August 22, 2022 5:17 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: S23E abend
Look at the SVC 3E trace entry in the dump. It shows R1 and the PSW at the
time.
Look at the key of R1 storage.
The minidump indicates that the DETACH was issued in key8.
Not clear to me why DETACH requires
Look at the SVC 3E trace entry in the dump. It shows R1 and the PSW at the
time.
Look at the key of R1 storage.
The minidump indicates that the DETACH was issued in key8.
Not clear to me why DETACH requires R/W access to the passed R1, but so it is.
On Mon, 22 Aug 2022 12:43:28 +0400 Peter wr
This is what I can see
IEA995I SYMPTOM DUMP OUTPUT 416
SYSTEM COMPLETION CODE=23E REASON CODE=
TIME=13.40.32 SEQ=03035 CPU=4000 ASID=00C2
PSW AT TIME OF ERROR 078C3000 8132DC5C ILC 4 INTC 04
NO ACTIVE MODULE FOUND
NAME=UNKNOWN
DATA AT PSW 0132DC56 - 10005070 10
What is they key of the storage? Certainly doesn't look like a TCB.
What was the PSW key when the DETACH was issued?
On Mon, 22 Aug 2022 12:14:30 +0400 Peter wrote:
:>1B10A920 E6C1D7C1 D9D47A6C C8F84040 40404040D7D3C9E2 E37A6CC8 F8404040
:>40404040 *WAPARM:%H8 PLIST:%H8
:>
:>This is
1B10A920 E6C1D7C1 D9D47A6C C8F84040 40404040D7D3C9E2 E37A6CC8 F8404040
40404040 *WAPARM:%H8 PLIST:%H8
This is what I see in dump
On Mon, Aug 22, 2022, 11:57 AM Binyamin Dissen
wrote:
> On Mon, 22 Aug 2022 10:23:01 +0400 Peter wrote:
>
> :>One of our online application started task
On Mon, 22 Aug 2022 10:23:01 +0400 Peter wrote:
:>One of our online application started task got abended with S23E with
:>reason code 0.
:>Recently we swapped our production site with our DR site.
:>The person who supports that product believes that the system swap could be
:>a reason
:>Bu
Hello
One of our online application started task got abended with S23E with
reason code 0.
Recently we swapped our production site with our DR site.
The person who supports that product believes that the system swap could be
a reason
But during swap all we did was upgrading our DR machine t
13 matches
Mail list logo
