ADSM-L

Re: [ADSM-L] Trouble with Java GUI on Windows

2010-01-09 02:39:54
Subject: Re: [ADSM-L] Trouble with Java GUI on Windows
From: Grigori Solonovitch <G.Solonovitch AT BKME DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Sat, 9 Jan 2010 09:57:46 +0300
Hello Roger,
We were suffering a lot from TSM Client 6.1. We started from 6.1.0.0, then 
upgraded to 6.1.0.2 --> 6.1.2.0 --> 6.1.3.0.

I have seen a lot of different problems whith these versions, but I never have 
problems with Java. We have mainly 32/64 bit Windows 2003 R2 
Enterprise/Standard Edition and AIX. GUI in Windows is working fine with Java, 
provided on TSM Client CD. dsmj under AIX is definately slow, but I have 
recommended users to use WEB Client for the both Windows and AIX. Actually 
after upgrading TSM Client to 6.1.3 there are no complaints from users.

I do not know, maybe reported problems are visable for quite new Windows 2008 
and Windows 7. As far as I understand only TSM Client 6.1.3 is certified for 
these operating systems.

I do not think it will be easy to reduce TSM Client version from 6.1.X to 5.5.5.

So try to go forward.

Good luck!

Grigori

________________________________________
From: ADSM: Dist Stor Manager [ADSM-L AT VM.MARIST DOT EDU] On Behalf Of Roger 
Deschner [rogerd AT UIC DOT EDU]
Sent: Saturday, January 09, 2010 6:17 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Trouble with Java GUI on Windows

As people start installing Version 6.1 clients, we're starting to get a
lot of problems and complaints about the new Java GUI Client.

1. If you don't have your Java configuration just right, it won't work
at all. I've gotten quite tired of coaching users through untangling
their Java setups which were imposed upon them by some other Java app. I
thought the idea of Java was to make things less dependent on the
underlying environment of OS, drivers, and hardware, but it's the
opposite. It's really very delicate, and dependent on everything else.

2. It's sloooooow. So slow on many systems that you don't know if you
clicked on something or not, so you click again. Bad things can happen
when you do this. Even if nothing bad happens, it is still maddeningly
sluggish. Twice the time to go through a wizard, such as to set up a
scheduler. This is on a pretty fast new-ish machine running Vista Pro,
as well as on an older XP machine, and a brand-new Win7 netbook.

So I'm about to alter our installation scripts and documentation to
create shortcuts to dsmmfc.exe - the old native non-Java GUI. Until I
get this ironed out, we are only recommending the v6.1 client for
Windows 7 users. We eagerly await the promised availability in 1H2010 of
a v5.5 client that supports Windows 7. In the V6 client, IBM should
continue to support dsmmfc.exe and update it as new features are added,
perhaps even making it the default GUI client again. It just simply
works better.

Roger Deschner      University of Illinois at Chicago     rogerd AT uic DOT edu
====================== "Java" is a 4-letter word =======================

Please consider the environment before printing this Email.

________________________________
"This email message and any attachments transmitted with it may contain 
confidential and proprietary information, intended only for the named 
recipient(s). If you have received this message in error, or if you are not the 
named recipient(s), please delete this email after notifying the sender 
immediately. BKME cannot guarantee the integrity of this communication and 
accepts no liability for any damage caused by this email or its attachments due 
to viruses, any other defects, interception or unauthorized modification. The 
information, views, opinions and comments of this message are those of the 
individual and not necessarily endorsed by BKME."

<Prev in Thread] Current Thread [Next in Thread>