Actually, we figured it out and it had nothing to do with Java.

It seems the new V6/all Java clients are very fragile when it comes to
errors in the DSM.OPT file.

When I had the user run the CLI, from the menu, it would flash and quit
immediately.  As soon as we ran DSMC manually, we saw the error (QUIET was
spelled QUITE).

Correcting this fixed everything.

I don't ever recall seeing this kind of failure in any of the preceding
client versions.



From:
"Clark, Margaret" <MClark AT SDDPC DOT ORG>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
10/26/2009 05:00 PM
Subject:
Re: [ADSM-L] Problems with new install of V6.1.0.2 client on Windows 2008
x64 system
Sent by:
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



I've seen the same thing, when the client had an old version of Java
loaded.

- Margaret Clark

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Zoltan Forray/AC/VCU
Sent: Monday, October 26, 2009 6:30 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Problems with new install of V6.1.0.2 client on Windows
2008 x64 system

Subject says almost "all of it".  The only additional info I can add is
the error he is seeing in the DSMJ error log:

10/26/2009 07:06:30: ANS1971E The remote client agent (dsmagent) could not
be started.Error executing dsmagent ! java.lang.NullPointerException
10/26/2009 07:31:59: ANS1971E The remote client agent (dsmagent) could not
be started.Error executing dsmagent ! java.lang.NullPointerException
10/26/2009 08:39:49: ANS1971E The remote client agent (dsmagent) could not
be started.

The only hit I see that is even close is:

http://www-01.ibm.com/support/docview.wss?rs=663&context=SSGSG7&dc=DB550&uid=swg1IC61768&loc=en_US&cs=UTF-8&lang=en&rss=ct663other


which does talk about a v6.1.1.1  (still looking for it),  eventhough this
is a NEW install, not an upgrade?

Your thoughts?