Or you can download an amazing SOS IPL text... Available at http://www.cbttape.org/~jjaeger/zzsa.html
Atenciosamente / Regards / Saludos Ituriel do Nascimento Neto BANCO BRADESCO S.A. 4254 / DPCD Engenharia de Software Sistemas Operacionais Mainframes Tel: +55 11 3684-2177 R: 42177 3-1402 Fax: +55 11 4197-2814 -----Mensagem original----- De: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] Em nome de Doug Fuerst Enviada em: segunda-feira, 14 de maio de 2012 16:56 Para: IBM-MAIN@bama.ua.edu Assunto: Re: Early IPL problems I always found that your activity the day after you have a wait state and you have no other system to fix it is to create a small one or two pack system to save your butt next time it happens. Or create another LPAR and have the space system running all the time. You generally only have this happen once. Doug -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Martin, Larry D Sent: Monday, May 14, 2012 1:51 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Early IPL problems John, I have always found that the Wait States that I encounter are of my own doing. I have never done an SADUMP. The one occurrence that was problematic was after a POR and no LP would IPL. Had to make changes to SYS1.PARMLIB but had no system. We were saved by the "Jan Jeager's OS/390 System Utilities". Building that capability into the HMC would be a great addition. Thanks, .............Larry -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of John McDowell Sent: Monday, May 14, 2012 12:56 PM To: IBM-MAIN@bama.ua.edu Subject: Early IPL problems Thanks for all of the feedback thus far, both on and off the list, it has been useful. So far, there seems to be general agreement that the frequency of problems is low (at least in production LPARs), that some way of displaying what the Wait State Code (WSC) means would be useful and that recovery from these sort of problems is accomplished by using another running z/OS system. To help focus the feedback somewhat I would be interested to know: - What are the typical steps taken to identify/recover from a WSC ? For example, Step 1: Find the meaning of the WSC Step 2: SADUMP Step 3: Correct the source of the problem Step 4: Re-IPL Step 5: Open a PMR etc., etc. Steps 1 seems fairly certain, beyond that the remaining steps (both content and sequence) seem to be much less so. - Are the existing messages useful/sufficient for identifying the underlying cause and how to correct the WSC ? - Are there circumstances (e.g. console setup, etc.) that prevent the existing messages from being seen ? - Are additional/better/different messages needed to identify and/or correct the cause of the WSC ? - Is there any need to diagnose and/or correct problems without resorting to another running z/OS system ? - To what extent, if any, is it desirable to avoid the WSC by providing some means of error recovery ? Thanks. John McDowell - IBM ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN This E-mail and any of its attachments may contain Prince George's County Government or Prince George's County 7th Judicial Circuit Court proprietary information or Protected Health Information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited by federal law and may expose you to civil and/or criminal penalties. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: INFO IBM-MAIN
