Hi,

A possible reason can be the fragmentation that normally occurs.
It is possble to prevent it by coding VSM CHECKREGIONLOSS(xxxK,xM) on your 
DIAGxx member of PARMLST.

Atenciosamente / Regards / Saludos

Ituriel do Nascimento Neto
BANCO BRADESCO S.A.
4250 / DITI Engenharia de Software
Sistemas Operacionais Mainframes
Tel: +55 11 3684-9602 R: 49602 3-1404
Fax: +55 11 3684-4427



-----Mensagem original-----
De: IBM Mainframe Discussion List <[email protected]> Em nome de Jake 
Anderson
Enviada em: terça-feira, 8 de janeiro de 2019 04:16
Para: [email protected]
Assunto: Re: Generic query on Region allocation failure

Apology for being vague

IEF085I REGION NOT AVAILABLE ERROR CODE = 20 IEF187I NNNNNJJJ FAILED - SYSTEM 
ERROR IN INITIATOR IEF472I NNNNNJJJ NNNNNJJJ - COMPLETION CODE - SYSTEM = 822 
USER= 00000, REASON = 00000



On Tue 8 Jan, 2019, 8:20 AM Lizette Koehler <[email protected] wrote:

> As always, it is helpful to post the complete error message it
> received
>
> Was it an S878
>
> Was it an S40d? if yes, what is the sub codes?
>
> Did you put on any recent maintenance?
>
> Did you increase the number of devices in your IO GEN (Check if HSA
> has
> grown)
>
> How much physical memory did you have on z114 vs z14
>
>
> Lots of things to check into without seeing the exact and complete
> error messages.
>
> Did you ask the Vendor about the issue?  Did they suggest any analysis?
>
>
> Lizette
>
> > -----Original Message-----
> > From: IBM Mainframe Discussion List <[email protected]> On
> Behalf Of
> > Jake Anderson
> > Sent: Monday, January 07, 2019 9:11 PM
> > To: [email protected]
> > Subject: Generic query on Region allocation failure
> >
> > Hi
> >
> > After we have moved from z114 to z14. Some of our database(ISVs
> > database
> > product) started task failed with region allocation.( When I kept
> > 5m),
> but
> > after increasing the region size it came up .
> >
> > Not sure if z14 requires some task to move above the line ?
> >
> > Could someone please shed some light on the above ?
> >
> > We are at zOS 2.2.
> >
> > Jake
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to [email protected] with the message: INFO IBM-MAIN
>

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

AVISO LEGAL <br>...Esta mensagem é destinada exclusivamente para a(s) pessoa(s) 
a quem é dirigida, podendo conter informação confidencial e/ou legalmente 
privilegiada. Se você não for destinatário desta mensagem, desde já fica 
notificado de abster-se a divulgar, copiar, distribuir, examinar ou, de 
qualquer forma, utilizar a informação contida nesta mensagem, por ser ilegal. 
Caso você tenha recebido esta mensagem por engano, pedimos que nos retorne este 
E-Mail, promovendo, desde logo, a eliminação do seu conteúdo em sua base de 
dados, registros ou sistema de controle. Fica desprovida de eficácia e validade 
a mensagem que contiver vínculos obrigacionais, expedida por quem não detenha 
poderes de representação. 
LEGAL ADVICE<br>...This message is exclusively destined for the people to whom 
it is directed, and it can bear private and/or legally exceptional information. 
If you are not addressee of this message, since now you are advised to not 
release, copy, distribute, check or, otherwise, use the information contained 
in this message, because it is illegal. If you received this message by 
mistake, we ask you to return this email, making possible, as soon as possible, 
the elimination of its contents of your database, registrations or controls 
system. The message that bears any mandatory links, issued by someone who has 
no representation powers, shall be null or void.

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

Reply via email to