Tips for Working With the V6R1 Conversion Tool

IBM recommends using the Analyze Object Conversion (ANZOBJCVN) tool to prepare for your conversion to i5/OS V6R1. ANZOBJCVN analyzes the objects on your i5/OS server and provides reports predicting how long conversion will take. The tool also notifies you of any program objects that won’t convert when you upgrade to V6R1 or migrate to a new system installed with V6R1.

I found three issues with the ANZOBJCVN tool that I’d like to share with you to make your life easier.

The first issue relates to the default setting for the maximum number of spooled output records allowed for the file QPIZARPT in library QSYS. By default, this file can have 100,000 spooled output records. Once you exceed this amount when generating program conversion reports, you’ll see the following message associated with the ANZOBJCVN *REPORT job you’re running.

Message ID . . . . . . : CPA4072
Date sent . . . . . . : 12/28/07
Time sent . . . . . . : 19:32:22

Message . . . . : Maximum number of records reached for file QPIZARPT. (C R NOMAX 1-999999)

To temporarily get around the issue, you can specify R, NOMAX, or a number up to 999999 to allow the program to complete its execution. I understand the built-in precaution of not allowing more than 100,000 spooled output records to be generated to protect disk consumption on a customer’s system. However, my experience has proven that almost no system can run with the default settings and have the reports generate without throwing this error. To get around it, change the print file attributes for the QPIZARPT file in library QSYS and specify *NOMAX for the maximum number of spooled output records, with this command:

CHGPRTF FILE(QSYS/QPIZARPT) MAXRCDS(*NOMAX)

The second issue was an annoyingly simple error. Regardless of how you run the *COLLECT portion of ANZOBJCVN, the *REPORT version will always report that you specified “/” for the objects to collect information about and the subtree parameter will always show “*ALL.”

For example, I specifically ran the tool to collect only information about all user libraries and spooled files. I explicitly specified *NONE for the OBJ parameter and *NONE for the SUBTREE parameter and, voila, the report says I collected information over *ALL for the OBJ parameter and *ALL for the SUBTREE parameter. To better explain, the command I actually submitted is:

ANZOBJCVN OPTION(*COLLECT) OBJ(*NONE) SUBTREE(*NONE)

The results in the report indicate that I submitted this command:

ANZOBJCVN OPTION(*COLLECT) OBJ(/) SUBTREE(*ALL)

It’s definitely not a showstopper, but be aware that it could skew your results if you thought you really ran the program conversion collection tool over “/” for the OBJ and *ALL for the SUBTREE parameter when, in fact, you didn’t collect any of this information.

The third issue concerns missing libraries. I recommend you check the reports to see which libraries are reported by specifying option *ALLUSR for the LIB parameter when collecting the program-conversion information. As the sidebar indicates, Domino program libraries aren’t included in the all user library selection. Check the list of libraries the tool reports back against a list of libraries on your System i server to ensure none was overlooked. The Domino conversion can be time consuming so checking for all critical libraries on your server will help ensure your estimates are accurate. For more specific conversion details related to Domino, see “Impact on Domino.”

--K.G.

< Return to main article