Take a look at increasing INITSQA in LOADxx. It's likely you were close to the 
limit before, and some environmental change pushed it over the limit. You 
shouldn't need much of an increase from the default, or if you're specifying it 
now to het you past this problem.

Mark Jacobs

Jesse Lynch<mailto:[email protected]>
February 11, 2018 at 2:04 PM
We got

IEA303W ABEND 878 REASON 00000004 DURING
INITIALIZATION UNDER RIM IEAVNP23
OSC Index 12 connected to CPC4100A via IP
Addr 10.216.182.225:3270<http://10.216.182.225:3270> **
LT Index=11 CSSID=00 MIFID=09 CU=0
UA=00 LUName=GMSTR **
Type=2965-N10 Mfg=IBM SN=0000000D2C07
message displayed during start up of GGGG.



at IPL over weekend on 2 of our LPARs.
For one, trying reipl worked fine. For the other we tried several times, no go.
RSU 1711 went into our 2.1 system. We searched on apars and found some old ones 
mentioning to increase
ESQA. There was some miscommunication and we increased ECSA from 570M to 650M 
for that one LPAR and it came
up just fine.

On further reading, it looks like if ESQA is exhausted, it might go to the ECSA.

So I have 2 questions

1). Anything we should look for on why this happened to us for the first time 
at IPL? Our maintenance?
or the fact because of the maintenance we stopped PPRC during the IPLs. Also we 
did update our ISV vendor software including CAs MIM. I know one of the old 
APARs mentioned GRS.

2). I am concerned that increasing ECSA might cost us in some way. Will this 
affect performance
or cause LPAR failure as we go along. I kind of looked at TMON for that LPAR 
and this is what I see:

CSA: 3068K( 34%) ECSA: 650M( 29%)
SQA: 800K( 56%) ESQA: 47076K( 61%)


We lost our senior Performance Guy to retirement recently which is why I am out 
here
asking for advice.

Thank you. Jess

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected]<mailto:[email protected]> with 
the message: INFO IBM-MAIN


Please be alert for any emails that may ask you for login information or 
directs you to login via a link. If you believe this message is a phish or 
aren't sure whether this message is trustworthy, please send the original 
message as an attachment to 
'[email protected]<mailto:[email protected]>'.


--

Mark Jacobs
Time Customer Service
Global Technology Services

The standard you walk past is the standard you accept.
Lt. Gen. David Morrison


This electronic message, including any attachments, may contain proprietary, 
confidential or privileged information for the sole use of the intended 
recipient(s). You are hereby notified that any unauthorized disclosure, 
copying, distribution, or use of this message is prohibited. If you have 
received this message in error, please immediately notify the sender by reply 
e-mail and delete it.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to