Thanks Mark. I did get this already and have run it. Actually got it three (?) years ago when we wanted to go to V6R1 and when checking out the vendor code that did not pass discovered that the vendor was not going to upgrade our version of their code to run on V6R1. Which prompted a review and decision to switch to a new vendor for that functionality. We just completed that conversion on Jan 1. Now I can finally get the benefits of V6R1 and V7R1

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark S. Waterbury
Sent: Wednesday, April 27, 2011 5:51 PM
To: Midrange Systems Technical Discussion
Subject: Re: Moving from V5R4 to V7R1

Hi, Mike:


It describes the steps needed to get the PTFs to install the IBM ANZOBJCVN command that you need to run to identify any objects on your system that will not convert, because they do not have the required observability. This could be true for vendor code as well as in-house applications.

As far as I am concerned, this is a "must read" (and "must do") for anyone upgrading from V5R4 to V6R1 or V7R1.

Hope that helps,

Mark S. Waterbury

On 4/27/2011 2:11 PM, Mike Cunningham wrote:
Are there any "must read" documents for moving from V5R4 to V7R1? I found the V6R1 memo to users and the V7R1 memo to users. Also have the Getting Ready for 6.1 and beyond manual. And the 7.1 Technical Overview. Is anyone aware of a document/memo specific to skipping V6R1?
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at

This thread ...


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

This mailing list archive is Copyright 1997-2019 by 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].