Sam.
I think, that you are right... ( Perhaps you changed the size of CSA
or ECSA to a much larger size )
In a previous migracion another LPAR we had memory problems and for that
reason we changed the parameters of CSA and ECSA ... So we have regularized
the values of CSA and ECSA and we are waiting an opportunity to try again...
I'll tell you how we will ...
Thank you so match
Atte.,
Alvaro Quintupray Burgos
-Mensaje original-
De: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] En nombre de
Knutson, Sam
Enviado el: Miércoles, 04 de Febrero de 2009 23:40
Para: IBM-MAIN@bama.ua.edu
Asunto: Re: Abend 04E - Reason 00E20003 on BIND Job with DB2
The reason code points to a shortage of Private storage not common storage.
Check that you have the same REGION being assigned perhaps you dropped a
USERMOD or an IEFUSI exit that you had in place on your previous release.
Perhaps you changed the size of CSA or ECSA to a much larger size making
PVT/EPVT much smaller.
The CA-SYSVIEW PRIVATE and REGION commands will show you what your virtual
storage boundaries are and use within a given address space.
Consider to try coding REGION=nnnM or event REGIOn=0M on your step.
Not being a DB2 guy it's not obvious if the storage shortage is local in your
BIND job which is what it sounds like or in the DBxxMSTR or DBxxDBM1 address
spaces. I think it is the first case.
00E20003
Explanation: In order to satisfy an unconditional request for storage,
the get variable storage function needed to obtain storage (from GETMAIN)
to expand a storage pool. However, GETMAIN indicated that sufficient
storage in the private area was not available.
This abend reason code is issued by the following CSECT: DSNSVBK
System Action: The agent is abended.
Operator Response: Notify the system programmer.
System Programmer Response: Increase region size. If the region size is
already defined at the maximum, consider enabling the CONTSTOR system
initialization parameter. For more information, see DB2 Installation
Guide.
Good Luck!
LookAT is often a good place to start to find a message or code if you don't
have the exact book or link handy.
http://www-03.ibm.com/systems/z/os/zos/bkserv/lookat/
Best Regards,
Sam Knutson, GEICO
System z Performance and Availability Management
mailto:sknut...@geico.com
(office) 301.986.3574
(cell) 301.996.1318
"Think big, act bold, start simple, grow fast..."
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of
Alvaro Quintupray B.
Sent: Wednesday, February 04, 2009 5:47 PM
To: IBM-MAIN@bama.ua.edu
Subject: Abend 04E - Reason 00E20003 on BIND Job with DB2
Hi.
We are migrated from ZOS 1.6 to ZOS 1.8 with DB2 7.10 and we are
getting an abend 04E with Reason code 00E20003 at the BIND.
--
1READY
DSN SYSTEM
(DSNT)
DSN
BIND PACKAGE(CDDTCBAT)QUALIFIER(WDSIGADM)PATH
(HDSIGSTP,HDGRCSTP,HDCRMSTP)LIB('DDTCDB2.DBRMLIB') ACT(REP)
ISOLATION(CS) RELEASE(COMMIT)VALIDATE(BIND) MEMBER(
DTCLDCFE );
IKJ56641I DSN ENDED DUE TO
ERROR+
IKJ56641I SYSTEM ABEND CODE 04E REASON CODE 00E20003 PSW
077C10009DE825BC ASIDS: HOME = 0051 PRIMARY = 0048 SECONDARY =
0048
This problem not occurred with ZOS 1.6 ... I know that is a management
storage ( CSA, ECSA ) but I can see whith SYSVIEW and RMF/ISPF that
Do not have problem with CSA.
And can not find one similar report on the web...
anyone has any help for me?
Thanks
Alvaro.
This email/fax message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution of this
email/fax is prohibited. If you are not the intended recipient, please
destroy all paper and electronic copies of the original message.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
La información contenida en este correo electrónico, así como en cualquiera de
sus adjuntos, es confidencial y está dirigida exclusivamente a el o los
destinatarios indicados. Cualquier uso, reproducción, divulgación o
distribución por otras personas distintas de el o los destinatarios está
estrictamente prohibida. Si ha recibido este correo por error, por favor
notifíquelo inmediatamente al remitente y bórrelo de su sistema sin dejar copia
del mismo. BancoEstado no acepta responsabilidad alguna por cualquier perdida o