We upgrade everything from 6.3.4.300 to 6.3.5.100 - only complication being
the Linux kernel semaphore issue which is highly aggravated due to the
change in DB2 levels that came in with 6.3.5 - still waiting for RedHat to
patch this.  RedHat just released a kernel update with 3-semaphore patches
but none have the Bugzilla ID that IBM (
http://www-01.ibm.com/support/docview.wss?uid=swg21691823) said is our
problem (and we don't pay enough for maintenance to be able to even look at
the *Bugzilla entry 1165277* ).  Can anyone out there help with getting
this info?

On Mon, Feb 2, 2015 at 12:37 PM, Skylar Thompson <skylar2 AT u.washington DOT 
edu>
wrote:

> Just to keep things confusing, IBM includes TSM server v6.3.4 in the v6.4
> release. AFAIK there is no true v6.4 server release. v6.3.4.300 has been
> working great for us on the server side.
>
> On Mon, Feb 02, 2015 at 05:31:48PM +0000, Lee, Gary wrote:
> > Looks like I won't be going to v7 for a while.  I have v5 clients still
> active with no end in site.
> >
> > I am upgrading from 6.2.5 on RHEL 6.1.  What is the wisdom of the group,
> go to 6.3.x or 6.4.x?
> >
> > We do no dedup here and have no plans for it.
> > However,we do use tsm for ve.
> >
> > Thankns for any help.
>
> --
> -- Skylar Thompson (skylar2 AT u.washington DOT edu)
> -- Genome Sciences Department, System Administrator
> -- Foege Building S046, (206)-685-7354
> -- University of Washington School of Medicine
>



--
*Zoltan Forray*
TSM Software & Hardware Administrator
BigBro / Hobbit / Xymon Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html