Linda,

What's the reason code of your S878 abend ?


Atenciosamente / Regards / Saludos

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



-----Mensagem original-----
De: IBM Mainframe Discussion List [mailto:[email protected]] Em nome de 
Elardus Engelbrecht
Enviada em: sexta-feira, 30 de setembro de 2016 09:27
Para: [email protected]
Assunto: Re: IEFUJI and REGION LIMIT - S878 abends in JES2

linda golding wrote:

>Apologize for the late response .

It is all right with me. ;-)


>*a)Ok, at what stage of JES2 initializing do you get the 878?*
>JES2 was getting S878 abends during IPL

Ok, what replies were given? $WARM? $S or so? Granted if you could go that far.

Could you see what automatic JES2 commands were given/handled? Do you see JES2 
Monitor starting up?
Can you see what last $HASP was shown?


>MEMLIMIT(00008G) -- PARMLIB

Could you try out NOLIMIT to see if that resolves your 878?


>This is a newly built system and we are planning to use as sandbox . There is 
>no maintenance put on these systems  No changes made to JES2PARM and nothing 
>changed with memory settings

Ok.


>*e)What else was running while getting those 878 abends?*
>Probably nothing apart from the system address spaces being a fresh IPL

Nothing? What about things like SMF, VLF, LLA, DLF, NET, OMVS, HSM and 
start/stop things like IRRDPTAB and IFGEDI? Where they also active and running?

It could be that one of these is consuming storage or one of them could using 
UJI eating up memory causing JES2 to die.


>*g)Can you see (source code) what are those two exits doing?*
>Its vanilla code.no changes to the exits as far as i remember . I'll take a 
>look again ...

Vanilla from where? From IBM or CBT or just setting RC=00 while doing nothing? 
Check if you have the RIGHT module with the RIGHT name.

I see 'vanilla' as something with size of x'20' or something.

Perhaps you should compare your system and JES2 and the exits with your other 
systems?

Perhaps you should ask IBM for assistance?

Good luck and all of the best for you!

Groete / Greetings
Elardus Engelbrecht

----------------------------------------------------------------------
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