Anil, It depends on the size of your environment. If you have few lpars then it is possible the enhance the frequency of applying Maintenance. In our case it's almost impossible apply Maintenance more than twice a year, so we do apply RSUxx12 and RSUxx06 and critical PTFs, when it's the case.
For ISVs we try to do the same. Atenciosamente / Regards / Saludos BANCO BRADESCO S.A. 4250 / DITI 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 ANIL KUMAR Enviada em: quinta-feira, 7 de dezembro de 2017 02:56 Para: [email protected] Assunto: RSU maintenance strategy - Need expert suggestions Hi All, I needed expert suggestions on following the RSU maintenance strategy for z/OS , associated ISV products , DB2 etc. Could you please let me know 1) How many times in a year do we need to apply the maintenance to z/os , ISV products , DB2 etc. 2) How to decide which ones to be applied. (latest RSU) 3) Whether the HIPERs included also be applied , even though we have not encountered the specific issues in out shop. So far in the account I was working for , it was not a strict rule to apply maintenance be it z/OS or DB2 or associated ISV product. Infact I do not remember any maintenance being applied to DB2 unless it was a major upgrade for which the pre-req was needed. Even for ISV's if they are running fine, then no action was taken. However for a different shop , we have been asked to come up with the best approach on whats needs to be done. If we keep updating the maintenance then 1 FTE job will be consumed for the work for a year. Hence needed some advise on what strategy is being used by different shops and what is the best practice. Please advise. If any documents etc are available please point me to them and I shall read. Sincerely hoping to get some advise. Thanks. ---------------------------------------------------------------------- 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
