Re: 6.1 - READY?

Speaking from a vendor's perspective, Mark Waterbury had the right idea in
an earlier post. It is a fact of life that vendors do have to support
multiple OS release levels and objects that don't pass muster with IBM's
tool may, in fact, be not in use for a 6.1 customer.

In all cases with third party software, check with the vendor. If the
vendor tells you that their code is 6.1 compliant, then why not just
believe them.

Rich Loeber
Kisco Information Systems
http://www.kisco.com

--------------------------------------------------------------------------

Pete Massiello wrote:

Rob,

You are right, but how are we the community to know if this is a
program that isn't required or one that is required just in some certain
instances (like every time the OS release changes). I think vendors should
clean up their crap and not leave a mess behind, otherwise all the System
Admins are scratching their heads wondering how I have a 6.1 compliant
version with programs that have no observability or creation data.

Pete

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, May 20, 2008 2:21 PM
To: Midrange Systems Technical Discussion
Subject: RE: 6.1 - READY?

As others have pointed out, some vendor programs are of the "not used
anymore" variety. For example, Turnover had 3 modes: 5250, original C/S,
and WDSC. original C/S is not ported over to V6R1 as people have migrated
over to WDSC. They don't remove those programs automatically but will
tell you that you can delete programs with certain naming conventions. (I
always verified with the Last Used date from DSPOBJD.)
Other vendors may have the same issues and handle it the same. I've even
heard of "reference" objects that aren't called but only used for "set the
authority on this new program like this one reference program" support.

Rob Berendt