>From what we've gleaned so far, EREP is just 'holding the mirror' and some
sort of WAIT is causing the CATALOG REDRIVE and is symptomatic of a tuning
opportunity. From a sysprog perspective I'm going to review WLM, DB2
buffer use and device busy. Craig Mullins DB/2 series is great and sugge
It's been a few years (retired / consulting now) since I had the duty of
looking at EREP records but as with what many others have said, it's about what
seems "normal" in your environment, although I've had instances of 0C4 that was
occuring regularly, though handled by the piece of software in
Most likely cause is SYSZTIOT or SYSZVVDS contention -- so the abend 91A
are symptoms of that latent problem (which affects your SLA potentially).
Catalog added contention management enhancement in z/OS 1.12 which causes
abend 91A for excessive wait and when the wait time threshold is reached
the a
>Catalog processing is not my area of expertise, but I think that this symptom
>record is the result of a catalog service task being ABTERMed with code 91A,
>possibly by a catalog analysis task. I don't remember offhand if a 91A is
>also used to terminate a service task when the suspended requ
: Turner Cheryl L
> To: IBM-MAIN@LISTSERV.UA.EDU
> Date: 06/15/2017 11:03 PM
> Subject: Re: EREP Symptom and/or Software Records
> Sent by: IBM Mainframe Discussion List
>
> I understand why you may have thought that but no I understand it is
> not the slip that spawns the
PM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: EREP Symptom and/or Software Records
>
>I understand why you may have thought that but no I understand it is not the
>slip that spawns the records. But couldn't it be said that the slip parms are
>indicating IBM's view of th
as I can.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@listserv.ua.edu] On Behalf
Of Peter Hunkeler
Sent: Thursday, June 15, 2017 4:20 PM
To: IBM-MAIN@listserv.ua.edu
Subject: AW: Re: EREP Symptom and/or Software Records
>But I still can't get my head around,
>But I still can't get my head around, why cut 100's of symptom/software
>records a day at all for a particular problem, if we're just going to ignore
>them - abend or not. But I'll try to let that not keep me awake at night.
I may well be wrong with my interpretation of the above statement an
> On Jun 14, 2017, at 8:47 AM, Turner Cheryl L wrote:
>
> was hoping you'd chime in John (and I appreciate the responses from Skip,
> Lizette and EdG, as well). Since I am the person that does the maintenance
> and OS upgrades now, I was taking it upon myself to be a bit proactive (or
> creat
ssion List [mailto:IBM-MAIN@listserv.ua.edu] On Behalf
Of Bruce Hewson
Sent: Thursday, June 15, 2017 1:20 AM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: EREP Symptom and/or Software Records
Hello Cheryl,
check out the Logrec Viewer exec -
https://www.ibm.com/systems/z/os/zos/tools/downloads/l
Hello Cheryl,
check out the Logrec Viewer exec -
https://www.ibm.com/systems/z/os/zos/tools/downloads/logrec-viewer.html
also you can monitor the PFA_LOGREC_ARRIVAl_RATE healthcheck to tell you when
you get a burst of LOGREC events.
Regards
Bruce
On Tue, 13 Jun 2017 16:24:34 -0500, Turner
Hopefully DAE has kicked in and you are just getting symptom records. IPCS
DAE(3.5) you can get a little insight into who's waving their hands.
http://www-01.ibm.com/support/docview.wss?uid=isg1OA08663
In a message dated 6/14/2017 8:47:57 A.M. Central Daylight Time,
cheryl.l.tur...@irs.g
Turner Cheryl L wrote:
I was hoping you'd chime in John (and I appreciate the responses from Skip,
Lizette and EdG, as well). Since I am the person that does the maintenance and
OS upgrades now, I was taking it upon myself to be a bit proactive (or creating
busy work?) and looking at the EREP
Wednesday, June 14, 2017 9:10 AM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: EREP Symptom and/or Software Records
Turner Cheryl L wrote:
> Greetings.
> Our former sysprog, who paid attention to the more finer system details, has
> left the building for greener pastures. So now we seem t
Turner Cheryl L wrote:
Greetings.
Our former sysprog, who paid attention to the more finer system details, has
left the building for greener pastures. So now we seem to have to step up our
game. However, I'm not sure what to do or how.
We are running several EREP reports to see what software
l L
>Sent: Jun 13, 2017 2:24 PM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: EREP Symptom and/or Software Records
>
>Greetings.
>Our former sysprog, who paid attention to the more finer system details, has
>left the building for greener pastures. So now we seem to have to step up our
> On Jun 13, 2017, at 4:24 PM, Turner Cheryl L wrote:
>
> Greetings.
> Our former sysprog, who paid attention to the more finer system details, has
> left the building for greener pastures. So now we seem to have to step up
> our game. However, I'm not sure what to do or how.
>
> We are runn
626-543-6132 Office ⇐=== NEW
robin...@sce.com
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Turner Cheryl L
Sent: Tuesday, June 13, 2017 2:25 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):EREP Symptom and/or Software Rec
Greetings.
Our former sysprog, who paid attention to the more finer system details, has
left the building for greener pastures. So now we seem to have to step up our
game. However, I'm not sure what to do or how.
We are running several EREP reports to see what software or symptom records are
19 matches
Mail list logo
