Re: V5R4 Object Conversion Strategy

What I have done on several occasions is this
#1 Divide the libraries into at least 2 catagories. Production Critical and
Non Critical. Non critical are development libs etc.
#2 Determine the estimated conversion time(s) for the Production Critical
libraries and depending on the system, setup those libs so run first in 2 or
3 job streams.
#3 Repeat #2 with the non critical libs.



On Mon, Nov 22, 2010 at 10:16 AM, Evan Harris <auctionitis@xxxxxxxxx> wrote:

Hi All

We've been making some plans to upgrade a bunch of machines from V5R4
to 6.1 or 7.1 depending on hardware and other factors; 7.1 is our
preferred target where it is do-able. In any case, a post upgrade
object conversion will be required after the upgrade (we understand
the ramifications of getting ANZOBJCVN done beforehand).

I seem to recall reading here a few suggestions about the best way to
approach this, but some searching of the archives has not turned up
the answers I thought I saw. We are looking to run the STROBJCVN
multi-threaded after the upgrade is complete - has anyone got any
comments on a general approach or strategy they use to manage this or
is it simply a seat of the pants judgement on a customer by customer
basis ?

I'm thinking about creating a specific job queue to run the object
conversion through then setting the number of concurrent jobs allowed
concurrently from the queue to a value estimated during the upgrade
preparation and based on the machine, number of libraries and the
conversion estimates from ANZOBJCVN. Then after the conversion we'll
just run a program to list the user libraries and submit a STROBJCVN
for each library to the conversion queue.

Anyone see any problems with that approach or have any alternative
suggestions ?

--
Regards
Evan Harris
http://www.auctionitis.co.nz
--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.