We used to do the stepped approach until zVM 4.4 or 5.1. Originally we did CP/GCS and TCPIP then did CMS later. That was until TCPIP became dependent on CMS. Now we're Big Bang believers. If you must do stepped -remember CMS BEFORE or AT SAME TIME as TCPIP.
-----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Schuh, Richard Sent: Thursday, October 30, 2008 2:03 PM To: [email protected] Subject: Re: TCPIP for z/VM 5.4 That brings up a question. Is there any known inconsistency that will be exposed if I upgrade the CP from 5.2 to 5.3 first? Big Bang is not to my liking at this time? Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark > Sent: Thursday, October 30, 2008 9:15 AM > To: [email protected] > Subject: Re: TCPIP for z/VM 5.4 > > On Thursday, 10/30/2008 at 10:13 EDT, Edward M Martin > <[EMAIL PROTECTED]> wrote: > > > But I thought that TCP/IP and CMS were tied to each other level > wise. > > They work on different levels but there could be inconsistencies. > > You are correct. A particular release may include a TCP/IP change > that depends on a new CMS function that depends on a new CP function. > Sometimes yes, sometimes no. If a service that TCP/IP or one of its > servers needs isn't present in CP and/or CMS, that app will typically > stop. We try to do it gracefully and it is our general rule to check > for the availability of a new service when the server starts - not > waiting until it is actually needed. This way the error appears right > away. > > If you don't do a big bang: > 1. Upgrade CP > 2. Upgrade CMS > 3. Upgrade TCP/IP with all of its attendent servers > > What is underneath needs to be newer than what rides on top. > We do our best to make this work if it's reasonable to do so, but > there are limits. > E.g. When the SSL support for z/VM 5.4 ships later this year, it will > not work with an old stack and the new stack will not work with the > old SSL server. The expense of making it work was prohibitive. > > Within reason we'll support a mixed configuration while you are > migrating. > > Alan Altmark > z/VM Development > IBM Endicott > ************************************************************ This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. ************************************************************
