× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Because when the sh1t hits the fan and the customer's application isn't
working, they are going to look to me to fix it. I don't want to say, well
the vendor said it was fine. Great, now the customer is down, the IT mgr is
getting crap from their management, what do we do? Wait a week while the
vendor sends us a CD? Some vendors are great, and others suck.

I don't wish to give that type of service to my customers. Also, at the end
of the day, they perceive that it was me who screwed up the upgrade, as
something that was working now isn't. It's the old "last straw on the
camel".

This is my opinion, and I understand that Kisco is a good vendor, but not
everyone is up to your standards Rich.

Pete

Pete Massiello
iTech Solutions
http://www.itechsol.com

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rich Loeber
Sent: Tuesday, May 20, 2008 3:08 PM
To: Midrange Systems Technical Discussion
Subject: 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




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.