On Fri, 7 Sep 2012 18:19:07 -0700, Skip Robinson <[email protected]> wrote:
>We have followed a simple rule for a decade or so. Everything included in >ServerPac goes into one CSI. Period. Everything else goes into some other >CSI. Hence if we order a product separately in between ServerPacs but know >that it will later on come in the next ServerPac, we install in the >ServerPac CSI. Otherwise it goes somewhere else. > >The reason for this rule is the management of maintenance, which is far >easier, more consistent, and more reliable if all the blood cousins are >housed in the same bunkhouse. > >. Exactly the same rule I have followed. If it is Z038 Serverpac orderable, and I know we would order it with the next Serverpac, it goes into that CSI. The only exception I can think of was Java when we used to install new versions at the whim of the WAS team, before WAS starting coming with its own Java. But we also stopped maintaining Java with SMP/E around the same time because using SMP/E to keep track of Java maintenance buys you exactly nothing (IMO, there was a recent discussion about that here). At some other shops I have been at the same rule was followed with perhaps the additional exception of languages like COBOL and PL1 that also weren't ordered with a OS/390 or z/OS Serverpac either since they were maintained / upgraded separately. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:[email protected] Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
