forrest@LBL.GOV (06/27/88)
The Release Notes for CMS 3.0 state that is important to verify all CMS 2.x libraries before converting to CMS 3.0. This is because although CMS 3.0 can convert CMS 2.x libraries to the new format, it can only do so to CMS 2.x libraries that have no "structural problems". Thus, any such problem must be both recognized and fixed using CMS 2.x. I don't know about you but we have hundreds of CMS users, some of whom we don't even know. We're going to put an article in our newsletter warning of the need to verify existing CMS libraries and we'll also post various on-line messages, but I'm wondering if this will be enough. To conver ourselves I'm going to keep CMS 2.x on my Workstation which is connected through DFS to the central cluster on which CMS 3.0 will be brought up. This will allow me to fix and CMS 2.x libraries which might be overlooked after to conversion to 3.0. What have other sites done about the conversion to CMS 3.0. DEC changes internal structures from time to time but this is the first case I can recall where the program that uses the new structure can't handle the old structure in all cases. (I could be wrong on this.) Jon Forrest FORREST@LBL.GOV ucbvax!lbl-csam!ux1!forrest