Re: 6.1 - READY?

Because the vendors themselves may not have their change management ducks
in a row.

Customer: I have program ZYX321 in your library that doesn't pass
ANZOBJCVN.
Vendor: Oops, we missed that one. That one came out in a special fix.
Or, we forgot about that special tools library.

I've found vendor programs that even the vendor can't find the source for
anymore. Luckily it was one that had nothing in it's Last Used Date.

Sometimes, especially with change management systems, you may have a
difference between "source" machines and "target" machines. And the
vendor may have only tested their "source" machine.

Hey, after having to downgrade one system from V6R1 back to V5R4M5 because
crap blew up, NOTHING survives that doesn't pass ANZOBJCVN! No
exceptions.

Care to see the scars? I've went round and round with vendors. You have
to be quite specific. Break it up into bite size pieces. Like, open up
separate problems for each library. For example do not open this up as
one problem:

These don't pass ANZOBJCVN:
VNDLIB1
PGMA
PGMB
PGMC
VNDLIB2
PGMD
PGME
PGMF
VNDLIB3
PGMA again
PGMG
PGMH

Open it up as three problems or the vendor may work on one library and
forget the rest. Also makes it nice for the vendor to create their own
proper change management tickets. Trying to work WITH them and giving
yourself a little extra work helps to get you a higher quality solution.

Rob Berendt