Hi Kyle,

ADSM Client PTFs and fixtests are, as a general rule, completely
self-contained. Even if you have *never* installed the client on
a particular system, you can install the fixtest. There is no
requirement to install the original PTF first.

Exceptions to this rule are very infrequent, and would be clearly
documented in the accompanying README files.

The 3.1.0.7f2 fixtest includes the fix the the sched log truncation
problem (IC24185/IC24236).

If the problem with "active object not found" is the one related
to international characters, and if you are seeing it at 3.1.0.6,
then you will still see it at 3.1.0.7. At 3.1.0.6, we fixed the
root cause, which prevents the problem from growing. There is a
clean-up utility available as a fixtest, IC21746L2 (this one is
an exception to the rule that I mentioned above, but the doc
that comes with it describes how to install and use the tool;
note that where it says to install 3.1.0.6, you should read it
as "3.1.0.7"; actually, I recommend 3.1.0.7f2).

IC23396 and IC24185/IC24236 (these two APARs are the same) will
both be included in the next official V3.1 PTF.

I recommend 3.1.0.7f2 over the original 3.1.0.7 code. It is
fully supported, despite the "fixtest" term.

Regards,

Andy

Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com
"The only dumb question is the one that goes unasked."

Just to clarify.  If we are having the problem we need to go to the 3.1.0.7
client and then add the fix test, right.  Or, is there a fix/fixtest for
3.1.0.6.  We are still nervous about going to 3.1.0.7.  We know of a
problem
where the sched log has the first 8 characters truncated on some of the
lines in it.  Also, there is an Active Object not found error/problem.  We
want to go to 3.1.0.7 once the General release has all of these known bugs
fixed.  Do you know when that will be?  This is because we can't use
fixtest
in production here.

Kyle