Hi everyone.  ADSM has a fairly unique problem in defining what is supported
in V1 and V2, so when we say V1 is supported until ???, but we only take
apar's on V2 clients, let me explain.

The ADSM clients have a single code stream.  Each update is cumulative
on the previous code base.  Thus, we really have only one
"version" for our clients, and that is the latest one (we can do builds
backwards in emergencies, but prefer not to!).

So, here is the problem:  Since we only have one code stream for the clients,
we have decided to always give them the latest number so people do not think
they are back level.  Problem is, those who have older servers at a different
level get concerned.  Our direction is to always make our clients backward
compatible with all server levels that are still in service.  Some functions
may require new servers to run, but the older function will still operate.

Our servers are different, and they do have version numbers that relate
specifically to service periods.  But since we only have one set of clients
that operate to all server platforms, we chose the method above.  It may
be confusing at times, but it keeps costs down so that we can do more
things.

I hope this helps to explain the methodology.  If anyone has any suggestions
on how to we remove confusion, we are all ears!  Thanks,

Paul Bradshaw