Agreed. I haven't noticed any problems in my unsupported CM configuration 
either.

I did notice some strange effects with a 5.5 library manager and mixed 6.2 and 
5.5 clients, where the 5.5 clients were unable to access the drives that are 
also used by the 6.2 clients, even though the LM has no problems and the LM and 
the 5.5 LC are on the same LPAR....

On 10 jun. 2012, at 02:00, Skylar Thompson wrote:

> Yeah, I intended to do it first, but as it turns out, I haven't run into
> any problems in the two years or so we've been running like this.
> At this point I figure once v5.5 is EOL'd I'll upgrade. What ain't broke...
> 
> On 6/8/2012 10:43 AM, Remco Post wrote:
>> The manual says that you must upgrade the CM first, I believe. Of course, if 
>> it's a designated CM, the size of the db may make it a good candidate to go 
>> first anyway...
> 
> 
> --
> -- Skylar Thompson (skylar2 AT u.washington DOT edu)
> -- Genome Sciences Department, System Administrator
> -- Foege Building S048, (206)-685-7354
> -- University of Washington School of Medicine

-- 
Met vriendelijke groeten/Kind Regards,

Remco Post
r.post AT plcs DOT nl
+31 6 248 21 622