Re: V5R4 Object Conversion Strategy

[DrFranken <midrange@xxxxxxxxxxxx>]

My standard approach is to create a user defined option in PDM that 
submits the job. Place the option next to library one and then press 
F31.  I usually send them to QBATCH but use priority 7 or 8 so I can 
regulate the number concurrently running. Once the jobs are submitted I 
go into the jobq and move the primary production objects library to the 
top. I also submit the IFS conversion and move that to the top of the 
list as it's often one of the longest running.

  - Larry "DrFranken" Bolhuis

On 11/22/2010 1:16 PM, Evan Harris 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 ?