Thanks Jim. We are on top of the MAINT disks and CMS level. It is more the relationship, if any, of SFS to NFS to TCP/IP levels that is of concern.
Big-bang seemed the only way to guarantee that we would be given the time to do the non-CP components. When we implemented the 4.4 CP, we were inundated with truly hot projects and never were able to find the time to do the rest. Regards, Richard Schuh -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Jim Bohnsack Sent: Friday, May 05, 2006 2:43 PM To: [email protected] Subject: Re: CMS Levels I had a problem when I first went to z/VM 4.4 because the SFS serves were still pointing to the MAINT ??? disk which was at the z/VM 4.3 level, so if you run SFS with a 5.2 CMS, make sure that whichever of the MAINT disks they, be default, access are at the 5.2 level. My preference is to update a service at a time rather than doing a "big bang" type of update. Jim At 04:14 PM 5/5/2006, you wrote: >Tomorrow will be our next (last, we hope) attempt to move to 5.2. In the = >event that we should have to regress to our current system, I was = >wondering if it is possible and prudent to leave some of our servers at = >the CMS22 level. Specifically, is it necessary to fallback the SFS and = >NFS servers? We know that TCP/IP and all of its friends will need to = >revert to their former selves. Does the NFS machine have to match the = >level of TCP/IP? If so, does SFS have to degress to match? We are = >back-level with SFS and have a problem that is fixed in V5, so we really = >would like to leave SFS at the CMS22 level if we go back. > >We have been running CMS22 in most of our other service and several = >individual user machines (80+ users in all) for over a month with = >absolutely zero release-related problems. > >Regards, >Richard Schuh Jim Bohnsack Cornell Univ. (607) 255-1760
